IBM Tivoli Storage Manager: Messages - IBM - United States

IBM Tivoli Storage Manager

MessagesVersion 5 Release 2

SC32-9090-00

��

IBM Tivoli Storage Manager

MessagesVersion 5 Release 2

SC32-9090-00

��

Note!Before using this information and the product it supports, be sure to read the general information under Appendix E,“Notices”, on page 959.

Fourth Edition (September 2003)

This edition applies to Version 5 Release 2 of the IBM Tivoli Storage Manager and IBM Tivoli Storage ManagerExtended Edition for AIX, HP-UX, Linux, Sun Solaris, Windows, OS/390 OS/400® PASE and z/OS (5698-ISM,5698-ISX); IBM Tivoli Storage Manager for Space Management (5698-HSM); IBM Tivoli Storage Manager for StorageArea Networks (5698-SAN); IBM Tivoli Storage Manager for Mail (5698-APE); IBM Tivoli Storage Manager forDatabases (5698-APD); IBM Tivoli Storage Manager for Application Servers (5698-APW); IBM Tivoli StorageManager for Hardware (5698-APH); IBM Tivoli Storage Manager for Enterprise Resource Planning (5698-APR); IBMTivoli Storage Manager for OS/390 (5697-ISM); IBM Tivoli Storage Manager for Mail System OS/390 Edition(5697-ILD) and to any subsequent releases until otherwise indicated in new editions or technical newsletters.

Order publications through your sales representative or the branch office serving your locality.

Your feedback is important in helping to provide the most accurate and high-quality information. If you havecomments about this book or any other Tivoli Storage Manager documentation, please see “Contacting CustomerSupport” on page viii.

© Copyright International Business Machines Corporation 1993, 2003. All rights reserved.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Preface . . . . . . . . . . . . . . . vMessages Not Appearing in This Publication . . . vSoftcopy Publications . . . . . . . . . . . vIBM Tivoli Storage Manager Publications . . . . . vReferenced z/OS™ System Publications . . . . . viiRelated IBM® Hardware Products Publications . . viiiIBM International Technical Support CenterPublications (Redbooks) . . . . . . . . . . viiiReferenced Publications . . . . . . . . . . viiiIBM Tivoli Storage Manager Web Site . . . . . viiiContacting Customer Support . . . . . . . . viii

Reporting a Problem . . . . . . . . . . ixTranslations. . . . . . . . . . . . . . . x

Summary of Changes for IBM TivoliStorage Manager Version 5 . . . . . . xiTechnical Changes for Version 5 Release 2—April2003 . . . . . . . . . . . . . . . . . xiTechnical Changes for Version 5 Release 1—March2002 . . . . . . . . . . . . . . . . xiii

Part 1. Introduction . . . . . . . . . 1

Chapter 1. Introduction . . . . . . . . 3Understanding Messages . . . . . . . . . . 3

Message Format . . . . . . . . . . . . 4

Chapter 2. Obtaining Help for IBM TivoliStorage Manager . . . . . . . . . . . 7Internet and IBMLink Assistance . . . . . . . 7

Internet . . . . . . . . . . . . . . . 7IBMLink/ServiceLink . . . . . . . . . . 7

Describing the Error with Keywords . . . . . . 7Component Identification Keyword. . . . . . 8Type-of-Failure Keyword . . . . . . . . . 8Command Keyword . . . . . . . . . . . 9Function Keyword . . . . . . . . . . . 9

Obtaining Online HELP (Get Help on ErrorMessages) . . . . . . . . . . . . . . . 9Contacting Your Service Representative . . . . . 9

Running Trace Commands. . . . . . . . . 9Messages That Do Not Appear in This Publication. . 9

Part 2. Server Messages . . . . . . 11

Chapter 3. Common and PlatformSpecific Messages(ANR0100–ANR9999). . . . . . . . . 13

Chapter 4. Client Events Logged toServer (ANE4000—4999). . . . . . . 603

Part 3. Client and Data Protectionfor Lotus Notes Messages . . . . 609

Chapter 5. Client and Data Protectionfor Lotus Notes Messages(ANS0100–ANS9999) . . . . . . . . 611

Part 4. Data Protection ProductsMessages . . . . . . . . . . . . 755

Chapter 6. Data Protection for LotusDomino (ACD0000–ACD9999) . . . . 757

Chapter 7. Data Protection forMicrosoft Exchange Server(ACN0000–ACN9999) . . . . . . . . 777

Chapter 8. Data Protection forMicrosoft SQL Server(ACO0000–ACO9999) . . . . . . . . 793

Chapter 9. Data Protection for Oracle(ANU0000–ANU9999) . . . . . . . . 809

Chapter 10. Data Protection formySAP.com Technology for DB2 UDB(BKI0000–BKI9999) . . . . . . . . . 821

Chapter 11. Data Protection formySAP.com Technology for Oracle(BKI0000–BKI9999) . . . . . . . . . 837

Chapter 12. Data Protection for EMCSymmetrix for R/3 (IDS0000–IDS0999) . 853

Chapter 13. Data Protection forEnterprise Storage Server formySAP.com Technogy for DB2 UDB(IDS1000–IDS2999) . . . . . . . . . 859

Chapter 14. Data Protection forEnterprise Storage Server formySAP.com Technolgy for Oracle(IDS1000–IDS1999) . . . . . . . . . 869

© Copyright IBM Corp. 1993, 2003 iii

Chapter 15. Data Protection forEnterprise Storage Server Databasesfor DB2 UDB (EEP0000–EEP9999) . . 879

Chapter 16. Data Protection forEnterprise Storage Server Databasesfor Oracle (EEO0000–EEO9999) . . . 895

Part 5. Appendixes . . . . . . . . 915

Appendix A. API Return Codes withExplanations. . . . . . . . . . . . 917

Appendix B. Allocating AdditionalServer Memory. . . . . . . . . . . 945

Appendix C. I/O Error CodeDescriptions for Server Messages . . 947

Completion Code and Operation Code Values . . 948Completion Code Values Common to All DeviceClasses . . . . . . . . . . . . . . 948Completion Code Values for Media Changers 949Completion Code Values for Tape and OpticalDrives . . . . . . . . . . . . . . . 950Operation Code Values for Tape Library Devices 951

Common Values for ASC and ASCQ Codes . . . 951Windows Event Log Entries . . . . . . . 954

Appendix D. Device Errors in AIXSystem Error Log . . . . . . . . . 957

Appendix E. Notices . . . . . . . . 959Programming Interface . . . . . . . . . . 960Trademarks . . . . . . . . . . . . . . 961

Glossary . . . . . . . . . . . . . 963

iv IBM Tivoli Storage Manager: Messages

Preface

IBM Tivoli Storage Manager is a client/server program that provides storagemanagement services to customers in a multivendor computer environment. TivoliStorage Manager provides an automated, centrally scheduled, policy-managedbackup, archive, and space management facility for file servers and workstations.

This publication contains explanations and suggested actions for messages issuedby the Tivoli Storage Manager server program for storage management services,the administrative client graphical user interface, administrative command lineclient, backup-archive client, API, HSM, and Data Protection products.

Messages Not Appearing in This PublicationMessage numbers in the range ANR0100–0120, and any with 9999 are notpublished in this manual. They are considered severe errors and should berecorded and included in a problem report when contacting the servicerepresentative.

Message number ANR7831I and numbers in the range ANR7900–8199 are AS/400®

platform–specific messages and are not published in this manual. You can obtainthe explanation for these messages using AS/400 commands such as WRKMSGDto get to the "Work with Message Descriptions" panel.

Softcopy PublicationsThe Tivoli Storage Manager library is available in softcopy on the followingCD-ROM:

Title Order Number

IBM Tivoli Storage Manager Publications Version 5 CD-ROM SK3T-8176

IBM Tivoli Storage Manager PublicationsThe following table lists Tivoli Storage Manager server publications.

Publication Title Order Number

IBM Tivoli Storage Management Products License Information GH09-4572

IBM Tivoli Storage Manager Messages GC32-0767

IBM Tivoli Storage Manager for AIX Administrator’s Guide GC32-0768

IBM Tivoli Storage Manager for AIX Administrator’s Reference GC32-0769

IBM Tivoli Storage Manager for AIX Quick Start GC32-0770

IBM Tivoli Storage Manager for HP-UX Administrator’s Guide GC32-0772

IBM Tivoli Storage Manager for HP-UX Administrator’s Reference GC32-0773

IBM Tivoli Storage Manager for HP-UX Quick Start GC32-0774

IBM Tivoli Storage Manager for Linux Administrator’s Guide GC23-4690

IBM Tivoli Storage Manager for Linux Administrator’s Reference GC23-4691

IBM Tivoli Storage Manager for Linux Quick Start GC23-4692

© Copyright IBM Corp. 1993, 2003 v


IBM Tivoli Storage Manager for OS/390 and z/OS Administrator’s Guide GC32-0775

IBM Tivoli Storage Manager for OS/390 and z/OS Administrator’sReference

GC32-0776

IBM Tivoli Storage Manager for OS/390 and z/OS Quick Start GC32-0777

IBM Tivoli Storage Manager for OS/400 PASE Administrator’s Guide GC23-4694

IBM Tivoli Storage Manager for OS/400 PASE Administrator’s Reference GC23-4695

IBM Tivoli Storage Manager for OS/400 PASE Quick Start GC23-4696

IBM Tivoli Storage Manager for Sun Solaris Administrator’s Guide GC32-0778

IBM Tivoli Storage Manager for Sun Solaris Administrator’s Reference GC32-0779

IBM Tivoli Storage Manager for Sun Solaris Quick Start GC32-0780

IBM Tivoli Storage Manager for Windows Administrator’s Guide GC32-0782

IBM Tivoli Storage Manager for Windows Administrator’s Reference GC32-0783

IBM Tivoli Storage Manager for Windows Quick Start GC32-0784

The following table lists Tivoli Storage Manager storage agent publications.


IBM Tivoli Storage Manager for AIX Storage Agent User’s Guide GC32-0771

IBM Tivoli Storage Manager for HP-UX Storage Agent User’s Guide GC32-0727

IBM Tivoli Storage Manager for Linux Storage Agent User’s Guide GC23-4693

IBM Tivoli Storage Manager for Sun Solaris Storage Agent User’s Guide GC32-0781

IBM Tivoli Storage Manager for Windows Storage Agent User’s Guide GC32-0785

The following table lists Tivoli Storage Manager client publications.


IBM Tivoli Storage Manager for Space Management for UNIX: User’sGuide

GC32-0794

IBM Tivoli Storage Manager for Macintosh: Backup-Archive ClientsInstallation and User’s Guide

GC32-0787

IBM Tivoli Storage Manager for NetWare: Backup-Archive ClientsInstallation and User’s Guide

GC32-0786

IBM Tivoli Storage Manager for UNIX: Backup-Archive ClientsInstallation and User’s Guide

GC32-0789

IBM Tivoli Storage Manager for Windows: Backup-Archive ClientsInstallation and User’s Guide

GC32-0788

IBM Tivoli Storage Manager Using the Application Program Interface GC32-0793

The following table lists publications for application protection products.

Publication TitleOrderNumber

IBM Tivoli Storage Manager for Application Servers: Data Protection forWebSphere Application Server Installation and User’s Guide

SC32-9075

vi IBM Tivoli Storage Manager: Messages

Publication TitleOrderNumber

IBM Tivoli Storage Manager for Databases: Data Protection for Microsoft SQLServer Installation and User’s Guide

SC32-9059

IBM Tivoli Storage Manager for Databases: Data Protection for Oracle for UNIXInstallation and User’s Guide

SC32-9064

IBM Tivoli Storage Manager for Databases: Data Protection for Oracle forWindows Installation and User’s Guide

SC32-9065

IBM Tivoli Storage Manager for Databases: Data Protection for InformixInstallation and User’s Guide

SH26-4095

IBM Tivoli Storage Manager for Enterprise Resource Planning: Data Protection forR/3 Installation and User’s Guide for DB2 UDB

SC33-6341

IBM Tivoli Storage Manager for Enterprise Resource Planning: Data Protection forR/3 Installation and User’s Guide for Oracle

SC33-6340

IBM Tivoli Storage Manager for Hardware: Data Protection for EMC Symmetrixfor R/3 Installation and User’s Guide

SC33-6386

IBM Tivoli Storage Manager for Hardware: Data Protection for Enterprise StorageServer Databases (DB2 UDB) Installation and User’s Guide

SC32-9060

IBM Tivoli Storage Manager for Hardware: Data Protection for Enterprise StorageServer Databases (Oracle) Installation and User’s Guide

SC32-9061

IBM Tivoli Storage Manager for Hardware: Data Protection for IBM ESS for R/3Installation and User’s Guide for DB2 UDB

SC33-8204

IBM Tivoli Storage Manager for Hardware: Data Protection for IBM ESS for R/3Installation and User’s Guide for Oracle

SC33-8205

IBM Tivoli Storage Manager for Mail: Data Protection for Lotus Domino forUNIX and OS/400 Installation and User’s Guide

SC32-9056

IBM Tivoli Storage Manager for Mail: Data Protection for Lotus Domino forWindows Installation

SC32-9057

IBM Tivoli Storage Manager for Mail: Data Protection for Lotus Domino, S/390Edition Licensed Program Specifications

GC26-7305

IBM Tivoli Storage Manager for Mail: Data Protection for Microsoft ExchangeServer Installation and User’s Guide

SC32-9058

Referenced z/OS™ System PublicationsThe following table lists referenced z/OS publications.


DFSMS/MVS DFSMSrmm Guide and Reference SC26-4931

DFSMS/MVS DFSMSrmm Implementation and Customization Guide SC26-4932

OS/390 Security Server (RACF) Security Administrator’s Guide SC28-1915

z/OS SecureWay Security Server RACF Security Administrator’s Guide SA22-7683

Preface vii

Related IBM® Hardware Products PublicationsThe following table lists related IBM hardware products publications.

Title Order Number

IBM Magstar 3494 Tape Library Introduction and Planning Guide GA32-0279

IBM 3490E Model E01 and E11 User’s Guide GA32-0298

IBM 3495 Tape Library Dataserver Models L20, L30, L40, and L50Operator’s Guide

GA32-0235

IBM Magstar MP 3570 Tape Subsystem Operator’s Guide GA32-0345

IBM TotalStorage Tape Device Drivers Installation and User’s Guide GC35-0154

IBM TotalStorage Enterprise Tape System 3590 Operator Guide GA32-0330

IBM Magstar 3494 Tape Library Dataserver Operator Guide GA32-0280

IBM International Technical Support Center Publications (Redbooks)The International Technical Support Center (ITSC) publishes redbooks, which arebooks on specialized topics such as using Tivoli Storage Manager to back updatabases. You can order publications through your IBM representative or the IBMbranch office serving your locality. You can also search for and order books ofinterest to you by visiting the IBM Redbooks™ home page on the World Wide Webat this address:

www.ibm.com/redbooks/

Referenced PublicationsThe following table lists other publications referenced in this manual:

Title Order Number

IBM 3494 Tape Library Dataserver User’s Guide: Media Library Device Driverfor AS/400

GC35-0153

IBM Local Area Network Technical Reference SC30-3383

LAN Technical Reference IEEE 802.2 & NETBIOS APIs SC30-3587

AS/400 System API Reference SC41-3801

IBM Tivoli Storage Manager Web SiteTivoli Storage Manager publications are available on the Tivoli Storage Managerhome page on the World Wide Web at the following address:

www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html

By accessing the Tivoli Storage Manager home page, you can keep up-to-date withthe newest product information.

Contacting Customer SupportFor support for this or any Tivoli® product, you can contact IBM CustomerSupport in one of the following ways:

viii IBM Tivoli Storage Manager: Messages

http://www.ibm.com/redbooks/

http://www.ibm.com/software/tivoli/solutions/storage/

http://www.ibm.com/software/tivoli/solutions/storage/

v Visit the Tivoli Storage Manager technical support Web site atwww.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html.

v Submit a problem management record (PMR) electronically atIBMSERV/IBMLINK. You can access IBMLINK at www.ibm.com/ibmlink/.

v Submit a problem management record (PMR) electronically atwww.ibm.com/software/support/probsub.html.

Customers in the United States can also call 1-800-IBM-SERV (1-800-426-7378).

International customers should consult the Web site for customer supporttelephone numbers.

Hearing-impaired customers should visit the TDD/TTY Voice Relay Services andAccessiblity Center Web site at www.ibm.com/able/voicerelay.html.

You can also review the IBM Software Support Guide, which is available on our Website at techsupport.services.ibm.com/guides/handbook.html.

When you contact IBM Software Support, be prepared to provide identificationinformation for your company so that support personnel can readily assist you.Company identification information is needed to register for online supportavailable on the Web site.

The support Web site offers extensive information, including a guide to supportservices (IBM Software Support Guide); frequently asked questions (FAQs); anddocumentation for all IBM Software products, including Release Notes, Redbooks,and white papers, defects (APARs), and solutions. The documentation for someproduct releases is available in both PDF and HTML formats. Translateddocuments are also available for some product releases.

All Tivoli publications are available for electronic download or order from the IBMPublications Center at www.ibm.com/shop/publications/order/.

We are very interested in hearing about your experience with Tivoli products anddocumentation. We also welcome your suggestions for improvements. If you havecomments or suggestions about our documentation, please complete our customerfeedback survey at www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html by selecting the Feedback link in the leftnavigation bar.

If you have questions or comments regarding Tivoli publications and productdocumentation, please visit www.ibm.com/software/tivoli/contact.html to send ane-mail.

Reporting a ProblemPlease have the following information ready when you report a problem:v The Tivoli Storage Manager server version, release, modification, and service

level number. You can get this information by entering the QUERY STATUScommand at the Tivoli Storage Manager command line.

v The Tivoli Storage Manager client version, release, modification, and servicelevel number. You can get this information by entering dsmc at the commandline.

Preface ix

http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html


http://www.ibm.com/ibmlink/

http://www.ibm.com/software/support/probsub.html

http://www.ibm.com/able/voicerelay.html

http://techsupport.services.ibm.com/guides/handbook.html

http://www.ibm.com/shop/publications/order/



http://www.ibm.com/software/tivoli/contact.html

v The communication protocol (for example, TCP/IP), version, and release numberyou are using.

v The activity you were doing when the problem occurred, listing the steps youfollowed before the problem occurred.

v The exact text of any error messages.

TranslationsSelected Tivoli Storage Manager publications have been translated into languagesother than American English. Contact your service representative for moreinformation about the translated publications and whether these translations areavailable in your country.

x IBM Tivoli Storage Manager: Messages

Summary of Changes for IBM Tivoli Storage Manager Version5

This section summarizes changes that have been made to the IBM Tivoli StorageManager product and this publication.

Technical Changes for Version 5 Release 2—April 2003The following changes have been made to the product for this edition:

LAN-Free Data MovementTivoli Storage Manager supports LAN-free data movement in storage areanetwork (SAN) environments. The support allows client data to movedirectly from the client system to a server-managed storage device on theSAN. This enhancement reduces data movement on the LAN so that morebandwidth is available to other applications

See Administrator’s Guide, and Administrator’s Reference for moreinformation.

Security: Firewall SupportTivoli Storage Manager currently supports environments with firewalls butthere is a security risk when remote clients (outside a firewall) are allowedto initiate contact with a server (behind a firewall). Clients normallycontact the server, but with the new firewall support, you can choose torestrict session initiation to the server. Scheduled, backup-archive clientoperations can be restricted to server-initiated sessions.

See Administrator’s Guide and Quick Start for more information.

NDMP OperationsFile Level Restore Tivoli Storage Manager currently provides backup andrecovery support for network-attached storage (NAS) file servers andutilizes Network Data Management Protocol (NDMP) to communicate withand provide backup and recovery services for NAS file servers.

Support for file level restore includes enhancements to allow tracking ofindividual files within a backed-up filesystem image. This enhancementmakes it possible to display the contents of an image backup, andindividual files within that image can be selected for restore.Implementation is achieved by generating a table of contents (TOC) duringbackup which is stored on the server.


3494 Library SupportNDMP support to the library types IBM 3494 TapeLibrary Dataserver and IBM 3495 Tape Library DataServer is nowprovided.


EMC Celerra NAS Device SupportBackup and restore operations for EMCCelerra file-servers via NDMP is now supported. This support includes allbase NDMP functions provided for NetApp file-servers as well as thefile-level restore function.

© Copyright IBM Corp. 1993, 2003 xi


Accurate SAN Device MappingDevice IDs within a SAN environment change when a bus reset or otherenvironmental changes occur. On AIX, HP-UX, Sun, and Linux platforms:with accurate SAN device mapping, Tivoli Storage Manager can nowdetect SAN changes and report that a reconfiguration is required. OnWindows platforms, With accurate SAN device mapping, Tivoli StorageManager can now detect SAN changes and automatically make theappropriate processing changes to the server definitions.


Macintosh OS X Unicode Support for Backup-Archive ClientUnicode filespaces are now supported on the Macintosh client. Bysupporting a Unicode-enabled client, the Tivoli Storage Manager server canstore file spaces with Unicode file space names, directory names, and filenames. The client can successfully process a Tivoli Storage Manageroperation even when the file spaces contain directory names or files inmultiple languages, or when the client uses a different code page from theserver.


TapeAlert Device SupportTapeAlert is a software application that provides detailed diagnosticinformation about tape and library device hardware errors. It captures thelog page from the drive or library when tapes are dismounted and issuesthe appropriate ANR error messages, allowing you to recognize problemsas early as possible.


Increased Archive Retention LimitsTivoli Storage Manager now supports increased retention times forarchives and backup sets. These new retention values will allow dataarchives to be kept longer.


StorageTek VolSafe SupportTivoli Storage Manager now distinguishes between WORM media andRead Write (RW) media by supporting the device type VOLSAFE.


Server Performance TuningThe maximum value of the server option TXNGROUPMAX has beenincreased. This increase can increase tape performance.


Communication MethodTivoli Storage Manager no longer supports the COMMMETHOD values

xii IBM Tivoli Storage Manager: Messages

PDMCONNECT, PDMPORT, or PDMNAME. The COMMMETHOD serveroption has been updated to reflect this change.

Technical Changes for Version 5 Release 1—March 2002The following changes have been made to the product for this edition:

Server-Free Data MovementServer-free data movement uses the SCSI-3 extended copy command to dofull-volume backup and restore. It provides the following advantages:v Reduces IBM Tivoli Storage Manager client and server CPU utilization.v Eliminates data movement on the LAN.v Improves performance for data movement operations.v Allows the server to handle more concurrent client connections and

server operations.


IBM Tivoli Storage Manager Device DriverThe Tivoli Storage Manager device driver (tsmscsi) now supports SCSIautochangers, optical drives, and tape drives. The following device classesare now available on HP-UX: 4MM, 8MM, DLT, DTF, ECARTRIDGE, andQIC.

See Administrator’s Guide and Quick Start for more information.

LAN-Free Data MovementTivoli Storage Manager supports LAN-free data movement in storage areanetwork (SAN) environments. The support allows client data to movedirectly from the client system to a server-managed storage device on theSAN. This enhancement reduces data movement on the LAN so that morebandwidth is available to other applications.

See Tivoli Storage Manager for Storage Area Networks Storage Agent User’sGuide for more information.

Changes in Defining Drives and Libraries

v Device names are now specified in the DEFINE PATH and UPDATEPATH commands, rather than in the DEFINE DRIVE, UPDATE DRIVE,DEFINE LIBRARY, and UPDATE LIBRARY commands

v Path names for external libraries are now specified in the DEFINE PATHcommand.


Moving Data by NodeYou can use the MOVE NODEDATA command to move data in asequential-access storage pool for one or more nodes, or move data in asingle node with selected file spaces. You can also use MOVE NODEDATAto consolidate data for offsite disaster recovery storage, or move data toanother storage pool.


Support for Simultaneous Writes to Primary and Copy Storage PoolsYou can specify copy storage pools in a primary storage pool definition.

Summary of Changes for IBM Tivoli Storage Manager Version 5 xiii

When a client backs up, archives, or migrates a file, the file is written tothe primary storage pool and is simultaneously stored into each copystorage pool.


High Availability Cluster MultiprocessingTivoli Storage Manager can now use High Availability ClusterMultiprocessing (HACMP). HACMP provides the leading AIX-basedclustering solution, which allows automatic system recovery during systemfailure detection. By using HACMP together with Tivoli Storage Manager,you can ensure server availability.


Tivoli Data Protection for New Network Data Management Protocol Support

The new Tivoli Data Protection for NDMP product now supports NDMPbackup and restore for IBM network-attached storage (NAS) file servers.Previously only Network Appliance NAS file servers were supported. TDPfor NDMP is a separately priced and licensed product.

New Network Data Management Protocol (NDMP) support now extendsto the AIX® (32-bit and 64-bit) IBM Tivoli Storage Manager server platform.The new Tivoli Data Protection for NDMP product supports NDMPbackup and restore for network-attached storage (NAS) file servers fromIBM and Network Appliance. NDMP allows a networkstorage-management application to control the backup and restore of anNDMP-compliant file server without installing third-party software on thatserver. The NAS file server does not require installation of Tivoli StorageManager software. The Tivoli Storage Manager server uses NDMP toconnect to the NAS file server to initiate, control, and monitor a file systembackup or restore operation. The NDMP support for NAS file serversenables higher performance backup to tape devices without moving thedata over the LAN. TDP for NDMP is a separately priced and licensedproduct.

New Network Data Management Protocol (NDMP) support now extendsto the Sun Solaris (32-bit and 64-bit) IBM Tivoli Storage Manager serverplatform. The new Tivoli Data Protection for NDMP product supportsNDMP backup and restore for network-attached storage (NAS) file serversfrom IBM and Network Appliance. NDMP allows a networkstorage-management application to control the backup and restore of anNDMP-compliant file server without installing third-party software on thatserver. The NAS file server does not require installation of Tivoli StorageManager software. The Tivoli Storage Manager server uses NDMP toconnect to the NAS file server to initiate, control, and monitor a file systembackup or restore operation. The NDMP support for NAS file serversenables higher performance backup to tape devices without moving thedata over the LAN. TDP for NDMP is a separately priced and licensedproduct.

New Network Data Management Protocol (NDMP) support now extendsto the HP-UX (32-bit and 64-bit) IBM Tivoli Storage Manager serverplatform. The new Tivoli Data Protection for NDMP product supportsNDMP backup and restore for network-attached storage (NAS) file serversfrom IBM and Network Appliance. NDMP allows a networkstorage-management application to control the backup and restore of an

xiv IBM Tivoli Storage Manager: Messages

NDMP-compliant file server without installing third-party software on thatserver. The NAS file server does not require installation of Tivoli StorageManager software. The Tivoli Storage Manager server uses NDMP toconnect to the NAS file server to initiate, control, and monitor a file systembackup or restore operation. The NDMP support for NAS file serversenables higher performance backup to tape devices without moving thedata over the LAN. TDP for NDMP is a separately priced and licensedproduct.


Data Validation with Cyclic Redundancy CheckingIBM Tivoli Storage Manager provides the option of specifying whether acyclic redundancy check (CRC) is performed during a client session withthe server, or for storage pools. The server validates the data by using acyclic redundancy check which can help identify data corruption. Datavalidation can be enabled for one or all of the following:v Tivoli Storage Manager client nodes at Version 5.1v Tivoli Storage Manager storage agents at Version 5.1v Storage pools

See Administrator’s Guide and IBM Tivoli Storage Manager Storage AgentUser’s Guide for more information.

New Licensing MethodThe new licensing method enables you to register the exact number oflicenses that are required, rather than in increments of 1, 5, 10, and 50.

See Administrator’s Guide for more information.

Server Performance EnhancementsThere are two new IBM Tivoli Storage Manager performanceenhancements:v AIX Asynchronous I/O Support. This feature is available via a new

option in the server options file.v AIX Direct I/O Support. This feature is available via a new option in the

server options file.


Support for Windows® XP/2002 IBM Tivoli Storage Manager Backup-ArchiveClients

Support is now added for Windows XP and Windows 2002 IBM TivoliStorage Manager backup-archive clients that run in 64-bit mode. These twoWindows platforms are a Unicode-only version of the client.


Communication MethodTivoli Storage Manager for Windows no longer supports the InternetworkPacket Exchange (IPX)/SPX and NETBIOS communication methods. TheCOMMMETHOD server option has been updated to reflect this change.

Summary of Changes for IBM Tivoli Storage Manager Version 5 xv

xvi IBM Tivoli Storage Manager: Messages

Part 1. Introduction

© Copyright IBM Corp. 1993, 2003 1

2 IBM Tivoli Storage Manager: Messages

Chapter 1. Introduction

IBM Tivoli Storage Manager (Tivoli Storage Manager) is an enterprise-wide storagemanagement application for the network. It provides automated storagemanagement services to multivendor workstations, personal computers, and localarea network (LAN) file servers. Tivoli Storage Manager includes the followingcomponents:v Serverv Administrative clientv Backup-archive clientv Space Manager (Hierarchical storage management (HSM) client)v Application programming interface (API)v Data Protection product (application product)

This chapter contains information to help you understand the messages issued bythese components.

Messages can appear on the server console, the administrative client, an operatorterminal, the administrative graphical user interface, the backup-archive client, thespace-management client, or the application clients.

Tivoli Storage Manager provides an activity log to help the administrator trackserver activity and monitor the system. The activity log contains messagesgenerated by the server, and is stored in the database. The server automaticallydeletes messages from the activity log after they have passed the specifiedretention period. Any messages sent to the server console are stored in the activitylog. Examples of the types of messages stored in the activity log include:v When client sessions start or endv When migration starts or endsv When backed up files are expired from server storagev Any output generated from background processes

See the IBM Tivoli Storage Manager Administrator’s Guide.

Understanding MessagesThe following examples illustrate the format used in this publication to describeTivoli Storage Manager messages:v Messages that begin with prefix ANE and are in range 4000–4999 originate from

the backup-archive client. These messages (or events) are sent to the server fordistribution to various event logging receivers.

v The client may send statistics to the server providing information about abackup or restore. These statistics are informational messages that may beenabled or disabled to the various event logging receivers. These messages arenot published in this manual.

v Messages that begin with prefix ANR originate from the server.v Messages that begin with prefix ANS are from one of the following clients:

– Administrative clients– Application program interface clients– Backup–archive clients– Space Manager (HSM) clients


– Data Protection for Lotus® Notes™

v Messages that begin with prefix ACD are from Data Protection for LotusDomino™.

v Messages that begin with prefix ACN are from Data Protection for Microsoft®

Exchange Server.v Messages that begin with prefix ACO are from Data Protection for Microsoft

SQL Server.v Messages that begin with prefix ANU are from Data Protection for Oracle.v Messages that begin with prefix BKI are from Data Protection for mySAP.com

for DB2® UDB and Data Protection for mySAP.com for Oracle.v Messages that begin with prefix DKP and are in range 0001–9999 are from Data

Protection for WebSphere Application Server.v Messages that begin with prefix EEO and are in range 0000–9999 are from Data

Protection for ESS for Oracle.v Messages that begin with prefix EEP and are in range 0000–9999 are from Data

Protection for ESS for DB2 UDB.v Messages that begin with prefix IDS and are in range 0000–0999 are from Data

Protection for EMC Symmetrix for R/3.v Messages that begin with prefix IDS and are in range 1000–1999 are from Data

Protection for IBM ESS for mySAP.com for DB2 UDB and Data Protection forIBM ESS for mySAP.com for Oracle.

Message FormatThe following examples describe the Tivoli Storage Manager message format:

The callouts to the right identify each part of the format.

Server installation complete.

ANR 0992 I

Message PrefixMessage NumberMessage Type*

Message Text

Explanation

System Action

User Response

Explanation: The server installation procedurehas completed successfully. The server is nowavailable for normal operation.

System Action: Server completes installationprocessing.

User Response: None.

I = InformationE = ErrorS = Severe ErrorW = WarningK = Kernel message that originates from thehierarchical storage management (HSM) client

*

The following letters give an indication of the severity of the action that generatedthe message. The severity codes and their meanings are as follows:

E Error Processing cannot continue.


W Warning Processing can continue, but problems may occur later.I Information Processing continues. User response is not necessary.

Message variables in the message text appear in italics. The server and clientmessages fall into the following categories:v Common messages that pertain to all Tivoli Storage Manager server platformsv Platform specific messages that pertain to each operating environment for the

server and the clientv Messages that pertain to application clients

How to Read a Return Code MessageMany different commands can generate the same return code. The followingexamples are illustrations of two different commands issued that result in the samereturn code; therefore, you must read the descriptive message for the command.

Example One for QUERY EVENT Command:

Example Two for DEFINE VOLUME Command:

Chapter 1. Introduction 5


Chapter 2. Obtaining Help for IBM Tivoli Storage Manager

This section describes the following:v How to obtain help with processing errors by using Internet and

IBMLink™/ServiceLinkv How to describe errors with keywordsv How to obtain online message helpv What information to have available when you contact your service

representative

Internet and IBMLink AssistanceTivoli Storage Manager message help explanations may suggest that you contactyour service representative for additional help with processing errors.

Online help is available through Internet and IBMLink/ServiceLink.

InternetYou can get additional information through an anonymous FTP server,ftp.software.ibm.com. Tivoli Storage Manager information is in the/storage/tivoli-storage-management directory.

A newsgroup, [email protected], is implemented by a third party. IBM supportsthis newsgroup on a best-effort basis only.

IBMLink/ServiceLinkIf your installation has access to IBMLink/ServiceLink, an interactive onlinedatabase program, you can:v Search for an existing authorized program analysis report (APAR) that is similar

to your problem.v Search for an available program temporary fix (PTF) for the existing APAR.v Order the PTF if it is available.v Create an Electronic Technical Response (ETR) problem report to get assistance

from an Tivoli Storage Manager service representative.

Describing the Error with KeywordsWhen you use IBMLink/Servicelink or call your service representative, accuratelydescribe the problem so that the service representative may quickly help you solvethe problem. Identify the processing error with a full set of keywords wheneverpossible. A keyword is a word or an abbreviation used to describe a single aspectof a program failure. Each keyword describes an aspect of a processing error.

The following example displays the necessary set of keywords:

56480200n R312 type command function

Where Represents56480200n Component identification keyword


Where RepresentsR312 Release level keywordtype Type-of-failure keywordcommand Command keywordfunction Function keyword

Component Identification KeywordThe component identifiers for Tivoli Storage Manager are 5698-ISM and 5698-ISX,with the exceptions listed below:

Component Component IDTivoli StorageManager for SpaceManagement

5698-HSM

Tivoli StorageManager for StorageArea Networks

5698-SAN

Tivoli StorageManager for Mail

5698-APE

Tivoli StorageManager forDatabases

5698-APD

Tivoli StorageManager forApplication Servers

5698-APW

Tivoli StorageManager forHardware

5698-APH

Tivoli StorageManager forEnterprise ResourcePlanning

5698-APR

Type-of-Failure KeywordThe following keywords identify the type of failure that may occur:

Keyword DescriptionABENDxxx Use this keyword when the system ends abnormally.INCORROUT Use this keyword when incorrect output is received or expected

output is missing.LOOP Use this keyword if a part of the program code runs endlessly;

include situations in which a part of the output repeatscontinuously.

MSGANRnnnnt (or)MSGANSnnnnt

Use this keyword when a message:

v Indicates an internal program error

v Is issued in a set of conditions that should not cause it to beissued

v Contains invalid or missing data

See “Understanding Messages” on page 3 for a description of themessage format.

WAIT Use this keyword when you receive no response within areasonable time that can be perceived as poor response or poorperformance.


Keyword Descriptionxxxxxxxxxx(Documentation)

Use this keyword when a programming problem appears to becaused by incorrect, missing, or ambiguous information in one ofthe Tivoli Storage Manager publications. Enter the order number ofthe publication in place of xxxxxxxxxx. Include the letter prefix andversion number, but omit all hyphens, for example, GC35040500.Refer to “IBM Tivoli Storage Manager Publications” on page v for alist of the Tivoli Storage Manager publications.

PERFM Use this keyword as a closing code for an APAR.

Command KeywordBuild keywords based on Tivoli Storage Manager commands. Refer toAdministrator’s Reference for a list of the commands.

Function KeywordUse keywords that refer to basic Tivoli Storage Manager functions such as backup,retrieve, archive, recover, migrate, and export-import.

Obtaining Online HELP (Get Help on Error Messages)Use the HELP command on the server console or administrative command lineclient to display information about server and administrative command line clientmessages. Use the HELP command on the backup-archive client to displayinformation about backup-archive client messages.

The Help error message number command displays the help text specific to the errormessage. You can get help information on server messages (prefixed by ANR), andadministrative command line and backup-archive client messages (prefixed byANS or ANE) except those specific to the administrative graphical user interfaceclient.

Contacting Your Service RepresentativeWhen you contact your service representative after the proper diagnosticprocedures have been followed and user specifications have been checked foraccuracy, you should have on hand the information listed in “Reporting aProblem” on page ix.

Running Trace CommandsYour service representative may request that you run trace commands to performdiagnostic functions. The output from the trace commands is classified asDiagnosis, Modification, and Tuning Information.

Messages That Do Not Appear in This PublicationSee “Messages Not Appearing in This Publication” on page v for information aboutmessages that appear online but are not documented in this publication.

Chapter 2. Obtaining Help for IBM Tivoli Storage Manager 9


Part 2. Server Messages



Chapter 3. Common and Platform Specific Messages(ANR0100–ANR9999)

This chapter contains the common and platform-specific server messages. Theorganization of the messages are grouped by the message prefix ANR anddocumented in ascending numeric order. If a message is platform specific and aduplicate, the appropriate platform name is added after the message number andit is also documented alphabetically by platform name.

ANR0100E Source file(line number): Error error codecreating table ″table name″.

Explanation: An internal error has occurred in anattempt to create a server database table. This messagealways accompanies another error message andprovides more detail about that error.

System Action: The activity that generated this errorfails.

User Response: Contact your service representative.

ANR0101E Source file(line number): Error error codeopening table ″table name″.

Explanation: An internal error has occurred in anattempt to access a server database table. This messagealways accompanies another error message andprovides more detail about that error.



ANR0102E Source file(line number): Error error codeinserting row in table ″table name″.

Explanation: An internal error has occurred in anattempt to add data to a server database table. Thismessage always accompanies another error messageand provides more detail about that error.



ANR0103E Source file(line number): Error error codeupdating row in table ″table name″.

Explanation: An internal error has occurred in anattempt to update data in a server database table. Thismessage always accompanies another error messageand provides more detail about that error.



ANR0104E Source file(line number): Error error codedeleting row from table ″table name″.

Explanation: An internal error has occurred in anattempt to remove data from a server database table.This message always accompanies another errormessage and provides more detail about that error.



ANR0105E Source file(line number): Error settingsearch bounds for table ″table name″.

Explanation: An internal error has occurred in anattempt to access data in a server database table. Thismessage always accompanies another error messageand provides more detail about that error.



ANR0106E Source file(line number): Unexpected errorerror code fetching row in table ″tablename″.

Explanation: An internal error has occurred in anattempt to access data in a server database table. Thismessage always accompanies another error messageand provides more detail about that error.



ANR0107W Source file(line number): Transactiontransaction ID was not committed due toan internal error.

Explanation: An internal error was detected duringtransaction commit. This message should be precededby another error message which provides more detailabout that error.




ANR0108E Source file(line number): could not start anew transaction.

Explanation: An error occurred while attempting tostart a new transaction. Possibly there is not enoughmemory.


User Response: Allocate additional storage to theserver. For details, issue HELP MEMORY to display theinformation online or see “Appendix A. AllocatingAdditional Server Memory”.

ANR0110E An unexpected system date has beendetected; the server is disabled. Use theACCEPT DATE command to establishthe current date as valid.

Explanation: The server has noted that the currentsystem date is suspect. It is earlier than the serverinstall date or has suddenly moved into the future by30 days or more.

System Action: The server is disable for client access.Server expiration will not execute.

User Response: If the current system date is not valid,reset the date. Use the ACCEPT DATE command toestablish the current date as valid on the server. Afterexecuting this command, you can use the ENABLESESSIONS command to enable the server for clientsessions.

ANR0111E Command: The BEGINNODEID andENDNODEID are both required to bespecified.

Explanation: The BEGINNODEID and ENDNODEIDare both required to be specified or neither of them arerequired.

System Action: The server fails the command.

User Response: Reissue the command, specifying bothBEGINNODEID and ENDNODEID, or neither of them.

ANR0112E Command: The specifiedBEGINNODEID node id is greater thanthe ENDNODEID node id.

Explanation: Either the BEGINNODEID or theENDNODEID is invalid because the value of theBEGINNODEID is greater than the ENDNODEID.

System Action: The server fails the command.

User Response: Reissue the command, specifying the

ENDNODEID to be greater than the BEGINNODEID,or both to be equal.

ANR0130E DiagnosticID: Server LOG spaceexhausted.

Explanation: There is no space to write data to theserver recovery log.


User Response: To increase the amount of log spaceavailable to the server, an authorized administrator canadd log volumes by using the DEFINE LOGVOLUMEcommand, and extend the size of the log by using theEXTEND LOG command.

ANR0131E DiagnosticID: Server DB space exhausted.

Explanation: There is no space to write data to theserver database.


User Response: To increase the amount of databasespace available to the server, an authorizedadministrator can add database volumes by using theDEFINE DBVOLUME command, and extend the size ofthe database by using the EXTEND DB command.

ANR0132E DiagnosticID: Memory allocation failed:object object name, size size.

Explanation: The server cannot obtain enoughmemory to create the object named.



ANR0133E Error loading module modname: errorstring

Explanation: The error specified by error stringoccurred when the server attempted to load modulemodname

System Action: Server operation continues, but thefunction provided by the module is not available.

User Response: Refer to the error string and correctthe condition causing the load to fail.

ANR0108E • ANR0133E


ANR0195W Attempting to remove extraneousdatabase entries for volume volume name.

Explanation: The server is attempting to removeextraneous database entries for the specified volume.

System Action: TSM will attempt to remove theextraneous database entries for this volume.

User Response: Review the completion messages forthis volume to determine if the removal of theextraneous database entries was successful or if anerror was encountered.

ANR0196I Removal of extraneous database entriesfor volume volume name was successful.

Explanation: The server successfully removedextraneous database entries for the specified volume.

System Action: System operation continues and futureoperations on the specified volume should worknormally.

User Response: The server successfully repaired thespecified volume.

ANR0197E Removal of extraneous database entriesfor volume volume name failed due tocontention with other server processesor activities.

Explanation: The server was not able to removeextraneous database entries for the specified volume.This was due to contention with another server processor activity.

System Action: System operation continues and thisvolume still has extraneous database entries.

User Response: It is possible that future serveractivities or processes will select this volume andattempt to repair it. If this occurs and the futureattempt is successful, no further action is needed. Theserver administrator should review the activity log forthe time that the repair was attempted and try todetermine what caused the contention. If you areunable to determine the cause of the contention of theproblem persists, please contact your servicerepresentative for additional assistance.

ANR0198E Removal of extraneous database entriesfor volume volume name failed.

Explanation: The server was not able to removeextraneous database entries for the specified volume.

System Action: System operation continues and thisvolume still has extraneous database entries.

User Response: The server administrator shouldreview the activity log for the time that the repair wasattempted and try to determine the cause of the failure.If you are unable to determine the cause of the

contention of the problem persists, please contact yourservice representative for additional assistance.

ANR0199W Not possible to repair volume volumename due to other database references tothis volume.

Explanation: The server was not able to removeextraneous database entries for the specified volumebecause other database references to this volume exist.

System Action: System operation continues.

User Response: The volume repair operation for thisvolume is not able to take any action because otherunexpected database references to this volume exists.For additional assistance contact your IBM servicerepresentative.

ANR0200I Recovery log assigned capacity is sizemegabytes.

Explanation: The amount of space allocated to therecovery log is shown.

System Action: None.


ANR0201I Database assigned capacity is sizemegabytes.

Explanation: The amount of space allocated to thedatabase is shown.



ANR0202W Database volume volume name variedoffline due to excessive read errors.

Explanation: The database volume shown has beenvaried offline because too many read errors have beenencountered.

System Action: If available, a mirrored copy of thevolume is used.

User Response: Correct the cause of the read errors.

ANR0203W Database volume volume name variedoffline due to excessive write errors.

Explanation: The database volume shown has beenvaried offline because too many write errors have beenencountered.


User Response: Correct the cause of the write errors.

ANR0195W • ANR0203W

Chapter 3. Common and Platform Specfic Messages 15

ANR0204W Recovery log volume volume name variedoffline due to excessive read errors.

Explanation: The recovery log volume shown hasbeen varied offline because too many read errors havebeen encountered.


User Response: Correct the cause of the read errors.

ANR0205W Recovery log volume volume name variedoffline due to excessive write errors.

Explanation: The recovery log volume shown hasbeen varied offline because too many write errors havebeen encountered.


User Response: Correct the cause of the write errors.

ANR0206W Partial write detected on databasevolume volume name, logical page logicalpage number (physical page physical pagenumber).

Explanation: During a write of a database page, anerror occurred so that the page was not completelywritten to disk.

System Action: The failed I/O operation is retried ona mirrored volume.

User Response: See accompanying messages forinformation about the volume in error.

ANR0207E Page address mismatch detected ondatabase volume volume name, logicalpage logical page number (physical pagephysical page number); actual: logical pagenumber.

Explanation: During a read of a database page, thepage does not contain the expected page address.



ANR0208W Partial write detected on recovery logvolume volume name, logical page logicalpage number (physical page physical pagenumber).

Explanation: During a write of a recovery log page,an error occurs so that the page is not completelywritten to disk.



ANR0209E Page address mismatch detected onrecovery log volume volume name, logicalpage logical page number (physical pagephysical page number); actual: logical pagenumber.

Explanation: During a read of a recovery log page, thepage does not contain the expected page address.



ANR0210S Inconsistency found in LVM data pagepage number - partial write detected.

Explanation: During a write of an LVM internal page,an error occurs so that the page is not completelywritten to disk.



ANR0211S Inconsistency found in LVM data pagepage number - page address mismatch(actual page number).

Explanation: During a read of an LVM internal page,the page does not contain the expected page address.



ANR0212E Unable to read disk definition file filespecification.

Explanation: At startup, the server cannot read theindicated file in order to obtain a list of disk volumesto mount.

System Action: Server initialization fails.

User Response: Use a text editor to recreate the file; itshould contain one line with the name of a single logor database volume. Then restart the server.

ANR0213W Unable to rewrite disk definition file.

Explanation: An error occurs trying to update the diskdefinition file.




User Response: Attempt to determine the cause of thewrite error and correct it.

ANR0214W Database volume volume name is in theoffline state - VARY ON required.

Explanation: At system startup, the server finds thatthe specified database volume is in the offline state.

System Action: The volume is not accessed.

User Response: Determine the reason for the volumebeing offline; if possible, vary it online.

ANR0215W Recovery log volume volume name is inthe offline state - VARY ON required.

Explanation: At system startup, the server finds thatthe recovery log volume shown is in the offline state.

System Action: The volume is not accessed.

User Response: Determine the reason for the volumebeing offline; if possible, vary it online.

ANR0216I Database volume volume name is in the″stale″ state - synchronization processstarted.

Explanation: At system startup, the server finds thatthe database volume shown is not synchronized.

System Action: A process is started to synchronize thevolume.


ANR0217I Recovery log volume volume name is inthe ″stale″ state - synchronizationprocess started.

Explanation: At system startup, the server finds thatthe recovery log volume shown is not synchronized.

System Action: A process is started to synchronize thevolume.


ANR0218I Unable to install database volumevolume name - capacity must be at least 5megabytes.

Explanation: An attempt has been made to add adatabase volume that is smaller than the serverminimum.

System Action: The volume is not added.

User Response: Increase the size of the volume orsupply another larger volume.

ANR0219I Unable to install recovery log volumevolume name - capacity must be at least 5megabytes.

Explanation: An attempt has been made to add arecovery log volume that is smaller than the serverminimum.

System Action: The volume is not added.

User Response: Increase the size of the volume orsupply another larger volume.

ANR0220I Synchronization of database volumevolume name started as process process ID.

Explanation: A background process was started tosynchronize the contents of the database volume shownwith its copy volume. The background process wasassigned the process ID shown.

System Action: The background process starts tosynchronize the volume and server operation continues.

User Response: The administrator may query thestatus of the background process by using the QUERYPROCESS command, or cancel the process by using theCANCEL PROCESS command.

ANR0221I Synchronization of recovery log volumevolume name started as process process ID.

Explanation: A background process was started tosynchronize the contents of the recovery log volumeshown with its copy volume(s). The backgroundprocess was assigned the process ID shown.

System Action: The background process starts tosynchronize the volume and server operation continues.

User Response: The administrator may query thestatus of the background process by using the QUERYPROCESS command, or cancel the process by using theCANCEL PROCESS command.

ANR0222E Error action disk definition file filespecification.

Explanation: An error occurred creating or changingthe disk definition file.


User Response: Attempt to determine the cause of thewrite error and correct it.

ANR0223E Error writing list of disks to diskdefinition file.

Explanation: The disk definition file cannot bewritten.

System Action: Installation ends.

ANR0214W • ANR0223E


User Response: Determine the cause of the write errorand correct it.

ANR0224E Volume volume name is specified morethan once - server installation failed.

Explanation: The specified volume name wasspecified more than once in the server installationexecution.

System Action: Installation ends.

User Response: Reinitialize the server installspecifying a unique name for each database andrecovery log volume.

ANR0230E Synchronization process failed fordatabase volume volume name.

Explanation: The process that was attempting tosynchronize the database volume shown has failed.

System Action: The volume is in the stale state.

User Response: See accompanying messages for moreinformation.

ANR0231E Synchronization process failed forrecovery log volume volume name.

Explanation: The process that was attempting tosynchronize the recovery log volume shown has failed.



ANR0232I Synchronization process canceled fordatabase volume volume name.

Explanation: The process that was attempting tosynchronize the database volume shown has beencanceled.


User Response: If desired, issue a VARY ONLINEcommand to start another synchronize process.

ANR0233I Synchronization process canceled forrecovery log volume volume name.

Explanation: The process that was attempting tosynchronize the database volume shown has beencanceled.


User Response: If desired, issue a VARY ONLINEcommand to start another synchronize process.

ANR0234I Synchronization complete for databasevolume volume name.

Explanation: The synchronization process for thedatabase volume named has finished successfully.

System Action: The volume is varied online.


ANR0235I Synchronization complete for recoverylog volume volume name.

Explanation: The synchronization process for therecovery log volume named has finished successfully.



ANR0240E Deletion process failed for databasevolume volume name.

Explanation: The process that was attempting todelete the database volume shown has failed.

System Action: The volume is not deleted.


ANR0241E Deletion process failed for recovery logvolume volume name.

Explanation: The process that was attempting todelete the recovery log volume shown has failed.



ANR0242I Deletion process canceled for databasevolume volume name.

Explanation: The process that was attempting todelete the database volume shown has been canceled.



ANR0243I Deletion process canceled for recoverylog volume volume name.

Explanation: The process that was attempting todelete the recovery log volume shown has beencanceled.



ANR0224E • ANR0243I


ANR0244I Deletion complete for database volumevolume name.

Explanation: The delete process for the databasevolume named has finished successfully.

System Action: The volume is deleted.


ANR0245I Deletion complete for recovery logvolume volume name.

Explanation: The delete process for the recovery logvolume named has finished successfully.



ANR0246E Error reading logical page logical pagenumber (physical page physical pagenumber) from database volume volumename.

Explanation: An error has been encountered whenattempting to read a page from the specified databasevolume.

System Action: The failed I/O operation is retried ona mirrored volume, if available.

User Response: See accompanying messages forinformation about the volume in error. If the errorpersists and another mirrored copy of the volume isavailable, the failing volume should be taken offline byusing the VARY OFF command, and repaired.Otherwise, halt the server and repair the volume. Thenrestart the server.

ANR0247I Database page logical page numbersuccessfully read from an alternate copyon volume volume name.

Explanation: After a read error, the server is able toread the desired page from another synchronizedmirrored volume.

System Action: Processing continues.


ANR0248E Unable to read database page logical pagenumber from any alternate copy.

Explanation: After a read error, the server is unable toread the desired page from another mirrored volumebecause no other mirrored volume is in thesynchronized state. This message is normally precededby a message indicating which volume failed.

System Action: Processing is ended.

User Response: You can repair the failed volume byhalting the server and correcting the volume errors.

ANR0249E Error reading logical page logical pagenumber (physical page physical pagenumber) from recovery log volumevolume name.

Explanation: An error has been encountered whenattempting to read a page from the specified recoverylog volume.

System Action: The failed I/O operation is retried ona mirrored volume, if available.

User Response: See accompanying messages forinformation about the volume in error. If the errorpersists and another mirrored copy of the volume isavailable, the failing volume should be taken offline, byusing the VARY OFF command, and repaired.

ANR0250I Recovery log page logical page numbersuccessfully read from an alternate copyon volume volume name.

Explanation: After a read error, the server is able toread the desired page from another synchronizedmirrored volume.



ANR0251E Unable to read recovery log page logicalpage number from any alternate copy.

Explanation: After a read error, the server is unable toread the desired page from another mirrored volumebecause no other mirrored volume was in thesynchronized state. This message is normally precededby a message indicating which volume failed.



ANR0252E Error writing logical page logical pagenumber (physical page physical pagenumber) to database volume volume name.

Explanation: An error has been encountered whenattempting to write a page to the specified databasevolume.

System Action: If a mirrored volume is available thenthe failing volume is forced into the offline state.

User Response: Repair the failing volume, and thenuse the VARY ON command to bring the volume backonline.

ANR0244I • ANR0252E


ANR0253E Unable to write database page logicalpage number to any alternate copy.

Explanation: After a write error, the server is unableto write the desired page to another mirrored volumebecause no other mirrored volume is in thesynchronized state. This message is normally precededby a message indicating which volume failed.


User Response: Repair the failed volume.

ANR0254E Error writing logical page logical pagenumber (physical page physical pagenumber) to recovery log volume volumename.

Explanation: An error has been encountered whenattempting to write a page to the specified recovery logvolume.

System Action: If a mirrored volume is available, thefailing volume is forced into the offline state.


ANR0255E Unable to write recovery log page logicalpage number to any alternate copy.

Explanation: After a write error, the server is unableto write the desired page to another mirrored volumebecause no other mirrored volume is in thesynchronized state. This message is normally precededby a message indicating which volume failed.



ANR0256E Error writing physical page physical pagenumber to restart/checkpoint area ondatabase volume volume name.




ANR0257E Error writing physical page physical pagenumber to restart/checkpoint area onrecovery log volume volume name.




ANR0258E Unable to write completerestart/checkpoint information to disk.

Explanation: While writing restart/checkpointinformation to disk, the server encounters an errorwriting to a database or recovery log volume for whichno synchronized mirrored copy is available. Thismessage is normally preceded by a message indicatingwhich volume failed.


User Response: Repair the failing volume.

ANR0259E Unable to read completerestart/checkpoint information from anydatabase or recovery log volume.

Explanation: During server restart, the server isunable to read a complete set of restart/checkpointinformation from any of the defined database orrecovery log volumes.

System Action: Server restart is ended.

User Response: Ensure that all defined database andrecovery log volumes are available for use by theserver.

ANR0260I Database page logical page numbersuccessfully resynchronized.

Explanation: After detecting a partially-writtendatabase page, the server is able to rewrite the page byusing a synchronized mirror copy.



ANR0261I Recovery log page logical page numbersuccessfully resynchronized.

Explanation: After detecting a partially-writtenrecovery log page, the server is able to rewrite the pageby using a synchronized mirror copy.





ANR0265E Log disk processing failed: sufficientmemory is not available.

Explanation: At server installation, the server isunable to process the server log disks due toinsufficient memory.

System Action: Server installation stops.

User Response: Restart the server installation processwith more memory available.

ANR0266E Database disk processing failed:sufficient memory is not available.

Explanation: At server installation, the server isunable to process the server database disks due toinsufficient memory.


User Response: Restart the server installation processwith more memory available.

ANR0267E Log volume volume name is not available.

Explanation: The specified volume cannot be foundduring installation.


User Response: Determine the reason the disk isunavailable, and correct the problem. Restart the serverinstallation process.

ANR0268E Database volume volume name is notavailable.

Explanation: The specified volume cannot be foundduring installation.


User Response: Determine the reason the disk isunavailable, andcorrect the problem. Restart the server.

ANR0269E Process for Log volume volume nameterminated - thread resource notavailable.

Explanation: During installation for the indicatedvolume, the server cannot start a thread to service I/Orequests.


User Response: Allocate additional storage to theserver. For details, issue HELP MEMORY to display theinformation online or see “Appendix A. AllocatingAdditional Server Memory”. Restart the serverinstallation process.

ANR0270E Process for Database volume volumename terminated - thread resource notavailable.

Explanation: During installation for the indicatedvolume, the server cannot start a thread to service I/Orequests.


User Response: Allocate additional storage to theserver. For details, issue HELP MEMORY to display theinformation online or see “Appendix A. AllocatingAdditional Server Memory”. Restart the serverinstallation process.

ANR0271E Maximum number of recovery logvolumes exceeded.

Explanation: More recovery log volumes have beenspecified than the server can manage.


User Response: Reduce the number of recovery logvolumes specified. Restart the server installationprocess.

ANR0272E Maximum number of database volumesexceeded.

Explanation: More database volumes have beenspecified than the server can manage.


User Response: Reduce the number of databasevolumes specified. Restart the server installationprocess.

ANR0285I Database page shadowing started usingfile file name.

Explanation: The database page shadowing functionwas started. The file specified is used to store theshadowed database pages.



ANR0286W Database page shadowing using file filename failed to start.

Explanation: The database page shadowing functioncould not start. An error has been encounteredaccessing the page shadow file specified.


User Response: Verify that there is enough space forthe page shadow file. That page shadow file requiresapproximately 65 kilobytes of space, if this space is notavailable a new location for the file should be specified.

ANR0265E • ANR0286W


ANR0287W Contents of the page shadow file filename are not valid.

Explanation: The database page shadowing functioncould not use the contents of the existing file. Restartrecovery using this file is not possible.

System Action: The server attempts to start withouthaving the database page shadow file available.

User Response: The database page shadow filecontents are not valid. This can be caused by: a partialwrite to the page shadow file itself, the file beingmanipulated by a process outside of the server, the filebeing overlayed by a different file, or the file couldhave been erased.

ANR0288W One or more database pages in the lastbatch written is corrupt - contents ofdatabase page shadow file will be usedto fix the page or pages.

Explanation: One or more pages from the last batch ofpages written to the server database has been detectedto be corrupt. The server will attempt to use thecontents of database page shadow file and replace thecorrupted database page.

System Action: Server startup continues.

User Response: A corruption of a database pagewithin the server database, is typically caused by apartial write. A partial write may occur when theserver is brought down external to normal serverprocessing. If the server terminated without a haltcommand being issued or if the machine the server isrunning on crashed unexpectedly, this may account forthe partial write. Other possible causes of a partialwrite are a disk drive failure, improperly terminatedscsi bus, or a failure in a device controller. Please try toidentify the cause of the partial write and take theappropriate action to prevent this from occurring in thefuture.

ANR0289W Damaged database pages weresuccessfully replaced using contents ofpage shadow file.

Explanation: The damaged database pages werereplaced using the corresponding pages from the pageshadow file. The pages were successfully replaced.

System Action: The server continues to restart.


ANR0290W Failure occurred attempting to replaceone or more damaged database pagesusing the contents of the page shadowfile.

Explanation: The damaged database pages could notbe replaced using the corresponding pages from thepage shadow file.

System Action: The server continues to restart.


ANR0291E Error writing to database page shadowfile.

Explanation: The server encountered an error writingto the database page shadow file. The page shadowingfor the server is currently disabled.

System Action: Database page shadowing for theserver will remain disabled until the server is haltedand restarted.

User Response: Check the file specified as thedatabase page shadow file. It may be that there is notenough space for the file. If enough space is available,check the filesystem, drive, or disk that it resides on foran indication of the error. Once the error preventing theserver from writing to the page shadow file has beenresolved, restart the server.

ANR0292W Database page shadow file file name doesnot exist.

Explanation: The server attempted to use the pageshadow file referenced but was unable to open the file.The file does not exist.

System Action: The server will continue to operateand will attempt to create this as a new database pageshadow file.


ANR0300I Recovery log format started; assignedcapacity count megabytes.

Explanation: Initial formatting of the server recoverylog has started.

System Action: The log is formatted for use by theserver.


ANR0301I Recovery log format in progress; countmegabytes of count.

Explanation: The amount of the server recovery logshown has been successfully formatted.

System Action: Formatting continues.


ANR0302I Recovery log formatting took msecondsmilliseconds.

Explanation: Formatting of the recovery log hascompleted and took the number of milliseconds shown.



ANR0287W • ANR0302I


ANR0303I Format rate: rate pages/second.

Explanation: During formatting, the formatterprocessed the number of pages indicated each second.



ANR0304I Page service time: rate ms.

Explanation: During formatting, the formatterrequired the number of milliseconds indicated toprocess each page.



ANR0305I Recovery log format complete.

Explanation: Formatting of the server recovery logcompleted successfully.



ANR0306I Recovery log volume mount in progress.

Explanation: During restart, the server is mountingrequired recovery log volumes.



ANR0307I Recovery log extend in progress; countmegabytes of count formatted.

Explanation: As a result of an EXTEND LOGcommand, the additional recovery log pages are beingformatted.

System Action: Formatting continues.


ANR0309I Recovery log extend terminated -process canceled.

Explanation: The process started as a result of anEXTEND LOG command and has been canceled.

System Action: The EXTEND command is ended.


ANR0311I Recovery log reduce in progress; countmegabytes of count moved.

Explanation: As a result of a REDUCE LOGcommand, the amount of data from the recovery logshown has been moved.

System Action: The REDUCE LOG commandcontinues.


ANR0313I Recovery log reduce terminated -process canceled.

Explanation: The process started as a result of aREDUCE LOG command and has been canceled.

System Action: The REDUCE command is ended.


ANR0314W Recovery log usage exceeds utilizationpercentage % of its assigned capacity.

Explanation: This message is issued to notify theadministrator that the server recovery log utilizationexceeds 90% or more of its assigned capacity.

System Action: Server operation continues.

User Response:v If the server is operating in NORMAL log mode,

depending upon the size of your recovery log, addrecovery log volumes, or extend the recovery log, orboth, before it fills completely. Refer to the DEFINELOGVOL, and EXTEND LOG commands for moreinformation on these operations.

v If the server is operating in ROLLFORWARD logmode:– backup the database, or– define a database backup trigger if one is not

already defined, or– lower the database backup trigger if one is

defined

Refer to the DEFINE DBBACKUPTRIGGER orUPDATE DBBACKUPTRIGGER commands.

ANR0350I Recovery checkpoint started.

Explanation: During server initialization, the processof bringing the server database back to a state ofconsistency has begun.



ANR0351I Recovery checkpoint complete.

Explanation: During server initialization, the processof bringing the server database back to a state ofconsistency has completed successfully.



ANR0303I • ANR0351I


ANR0352I Transaction recovery complete.

Explanation: During server initialization, the processof recovering any incomplete transactions hascompleted successfully.



ANR0353I Recovery log analysis pass in progress.

Explanation: During server initialization, the processof analyzing the server recovery log has begun.



ANR0354I Recovery log redo pass in progress.

Explanation: During server initialization, the processof committing incomplete transactions has begun.



ANR0355I Recovery log undo pass in progress.

Explanation: During server initialization, the processof rolling back incomplete transactions has begun.



ANR0356I Recovery log compression started.

Explanation: The process of removing unneeded datafrom the server recovery log has begun.



ANR0357I Recovery log compression ended.

Explanation: The process of removing unneeded datafrom the server recovery log has completed.



ANR0358E Database initialization failed: sufficientmemory is not available.

Explanation: During server initialization, the serverdatabase fails initialization because sufficient servermemory is not available.

System Action: Initialization fails.

User Response: Make more memory available to theserver.

ANR0359E Database initialization failed: unable toread database restart record.

Explanation: During server initialization, the serverdatabase initialization fails because the required restartrecord cannot be read.



ANR0360E Database initialization failed: databasesize mismatch; LVM size = size, expectedsize = size.

Explanation: During server initialization, the serverdatabase initialization fails because the size of thedatabase does not match its prior size.



ANR0361E Database initialization failed: errorinitializing database page allocator.

Explanation: During server initialization, the serverdatabase initialization fails because the page allocatorcannot be started.



ANR0362W Database usage exceeds utilizationpercentage % of its assigned capacity.

Explanation: This message is issued to notify theadministrator that the server database utilizationexceeds 80% or more of its assigned capacity.


User Response: Depending upon the size of yourdatabase, add database volumes, or extend thedatabase, or both, before it fills completely. The serverexpiration process may also free up database spacemaking it available to other server processes. Refer tothe EXPIRE INVENTORY, DEFINE DBVOL, andEXTEND DB commands for more information on theseoperations.

ANR0363I Database was automatically upgraded tothe server program level.

Explanation: This message is issued to notify theadministrator that the server database wasautomatically upgraded to the current server programlevel. The upgrade is performed when theUPGRADEDB parameter is specified at server start-upand the server is started over a database that waswritten by a down-level version of the server program.




User Response: None. The UPGRADEDB parameterdoes not need to be specified during future serverstart-ups.

ANR0364W Server has detected a zero bit mismatcherror.

Explanation: This message is issued to notify theadministrator that the server has detected a zero bitmismatch error during a RESTORE DB process. Therecovery process is the database must be restored witha process that includes a DSMSERV FORMAT. Eitherthe data base volumes must be formatted then aDSMSERV RESTORE DB performed from a data basebackup that does not have this problem, or aDSMSERV UNLOADDB followed by the formatting,then a DSMSERV LOADDB. Do not use DSMSERVDUMPDB on the data base for this recovery.

System Action: Server RESTORE DB continues.

User Response: Perform one of the data base recoveryactions after the RESTORE DB completes.

ANR0380W The database buffer pool recoveredfrom an overcommit of number of pagespages. Consider increasing your bufferpool size by kilobytes needed kilobytesunder current server load.

Explanation: During normal processing, additionalbuffer pool space is required beyond that specified inthe BUFPOOLSIZE in the server options file. Theadditional kilobytes of buffer pool space that arerequired are indicated in the message.

System Action: Server operation continues; theadditional buffer pool space is obtained from availableserver memory.

User Response: If the current server load is typical,consider increasing the size specified for yourBUFPOOLSIZE option by the number of kilobytesspecified in the message. To do this, you must halt theserver, change the options file, and then restart theserver.

ANR0381I Bufferpool statistics were successfullyreset.

Explanation: Bufferpool statistics, such as the CacheHit Ratio, have been reset by the RESET BUFPOOLcommand.


User Response: The QUERY DB command(FORMAT=DETAILED) can be used to to display thecurrent values for the buffer pool statistics.

ANR0382I The database maximum utilizationstatistic was successfully reset.

Explanation: The database maximum utilizationstatistic has been reset by the RESETDBMAXUTILIZATION command to the currentutilization.


User Response: The QUERY DB command(FORMAT=DETAILED) can be used to display thecurrent value for the maximum utilization.

ANR0383I The recovery log maximum utilizationstatistic was successfully reset.

Explanation: The recovery log maximum utilizationstatistic has been reset by the RESETLOGMAXUTILIZATION command to the currentutilization.


User Response: The QUERY LOG command(FORMAT=DETAILED) can be used to display thecurrent value for the maximum utilization.

ANR0384I The recovery log consumption statisticwas successfully reset.

Explanation: The recovery log consumption statistichas been reset by the RESET LOGCONSUMPTIONcommand.


User Response: The QUERY LOG command(FORMAT=DETAILED) can be used to display thecurrent value for recovery log consumption.

ANR0385I Could not free sufficient buffers toreach reduced BUFPoolsize.

Explanation: A reduction in the database buffer poolsize was requested. However, too many buffers were inuse to reach the lower buffer pool size.

System Action: Server operation continues. Whateverbuffer pool size reduction that could be achieved is ineffect. The new bufpoolsize is written to the options filefor use on the next server startup.


ANR0386I The BUFPoolsize has been changed tobuffer pool size.

Explanation: The BUFPoolsize option has beenchanged to the indicated value.





ANR0390W A server database deadlock situation hasbeen encountered: lock request fortransaction transaction ID will be deniedto resolve the deadlock.

Explanation: The server detected a deadlock situationbetween a number of processes attempting to accessdatabase information. A lock request for one of theprocesses will be denied to resolve the databasedeadlock. When server processes encounter a databasedeadlock, they usually reattempt the function that wasin progress when the deadlock was encountered. Notall process can explicitly re-try an operation. Forexample, migration and reclamation will eventuallyretry. However, something like a delete volume run in amacro will only retry if the delete command is reissuedeither in the macro or the command line.

System Action: A lock request fails for one of thedeadlocked processes. Server operation continues.

User Response: If a process can retry (like migration),then monitor the re-try attempt to see if it succeeds ornot. If it fails, contact a service representative. If theprocess or command is not able to retry on it’s own,then reissue the command or macro that caused theaction to occur. If it fails again, contact a servicerepresentative for further assistance to better isolate thedeadlock condition.

ANR0400I Session session number started for nodenode name (client platform) (communicationmethod).

Explanation: A new client session has been initiatedby the specified node. The session number, clientplatform type and communication method used by thissession are included in the message.

System Action: The server begins a communicationssession to service the client node.


ANR0401I Session session number started for nodenode name (client platform) (communicationmethod) (WDSF client).

Explanation: A new WDSF client session has beeninitiated by the specified node. The session number,client platform type and communication method usedby this session are included in the message.



ANR0402I Session session number started foradministrator administrator ID(administrator’s platform) (communicationmethod).

Explanation: A new administrator client session hasbeen initiated by the specified administrator. Thesession number, administrator’s platform type andcommunication method used by this session areincluded in the message.

System Action: The server begins a communicationssession to service the administrator client.


ANR0403I Session session number ended for nodenode name (client platform).

Explanation: A client session has completed normally.



ANR0404I Session session number ended for nodenode name (client platform) (WDSF client).

Explanation: A WDSF client session has completednormally.



ANR0405I Session session number ended foradministrator administrator ID (clientplatform).

Explanation: An administrative client session hascompleted normally.



ANR0406I Session session number started for nodenode name (client platform) (communicationmethod communication address).

Explanation: A new client session has been initiatedby the specified node. The session number, clientplatform type, communication method and addressused by this session are included in the message.





ANR0407I Session session number started foradministrator administrator ID(administrator’s platform) (communicationmethod communication address).

Explanation: A new administrator client session hasbeen initiated by the specified administrator. Thesession number, administrator’s platform type,communication method and address used by thissession are included in the message.



ANR0408I Session session number started for serverserver name (server’s platform)(communication method) for purpose.

Explanation: A new server session has been initiatedby the specified server for the specified purpose. Thesession number, server’s platform type andcommunication method used by this session areincluded in the message.



ANR0409I Session session number ended for serverserver name (client platform).

Explanation: A server has completed normally.



ANR0410E EXPORT operation to server server namerejected - administrator administrator isnot authorized to perform the importoperation on the target server.

Explanation: An export operation to the named serverwas rejected, because the administrator issuing theexport command is not defined on the target server ordoes not have sufficient authority to perform theimport operation on the target server.



ANR0411I Session session number for administratoradministrator name logged in as node nodename restored or retrieved object typeobject: node node name, filespace filespacename, object object name.

Explanation: This message logs information about anobject that was restored or retrieved by anadministrator logged in for a node.



ANR0412I Session session number for node nodename restored or retrieved object typeobject: node node name, filespace filespacename, object object name.

Explanation: This message logs information about anobject that was restored or retrieved by anadministrator logged in for a node.



ANR0413I Session session number for administratoradministrator name logged in as node nodename is restoring backup set: node nodename, set filespace name.

Explanation: This message logs information about abackup set restored by an administrator logged in for anode.



ANR0414I Session session number for node nodename is restoring backup set: node nodename, set filespace name.

Explanation: This message logs information about abackup set restored by a node.



ANR0415I Session session number proxied by storageagent name started for node node name.

Explanation: This session is started for the indicatednode and the storage agent acts as the proxy for thenode. Client node sessions are used to performLAN-free operations between the client and server.



ANR0416W Session session number for node nodename not allowed to operation using pathdata transfer path.

Explanation: This session attempted this operationusing the specified data transfer path. This operation isnot permitted for this client.


User Response: Issue QUERY NODEFORMAT=DETAILED for this node to see the currentDATA WRITE PATH or DATA READ PATH settings.

ANR0407I • ANR0416W


These settings determine if a given operation ispermitted using a specific data transfer path. If thisclient node should be permitted to perform thisoperation using this data transfer path, the UPDATENODE command should be used to correct this.

ANR0417W Session session number for node nodename terminated - data transfer path notallowed.

Explanation: This session attempted an operation thatneeded a data transfer path that this node is notallowed to use.

System Action: This client session terminates.

User Response: Refer to the ANR0416W message thatwas issued for this client session to determine whichoperation and data transfer path was attempted.

ANR0418W Session session number for administratoradministrator name (client platform) isrefused because an incorrect passwordwas submitted.

Explanation: The server refuses a request to start aclient session because an invalid password has beensubmitted by the client during sign-on processing.

System Action: The server will continue to denyaccess attempts by this client until a valid password issubmitted.

User Response: Enter the proper password. If youhave forgotten the password, contact an authorizedadministrator, who can assign a new password usingthe UPDATE ADMIN command.

ANR0419W Administrative client useridadministrative ID cannot be used whenauthentication is on.

Explanation: The server refuses a request for a client(administrative) session because the user ID specifiedcannot be used when authentication of IDs is in effect.SERVER_CONSOLE is an administrative ID that hasthis restriction.


User Response: Use an administrative ID that wasregistered for this server and that has a password.

ANR0420W Session session number for node nodename (client platform) refused - serverdisabled for user access.

Explanation: The server refuses a request for a client(backup-archive) session because the server is currentlydisabled for client access.

System Action: Server operation continues.Administrative clients are permitted access to theserver.

User Response: An authorized administrator mustissue the ENABLE command before client nodes arepermitted access to the server.

ANR0421W Session session number for node nodename (client platform) refused - sign-onprotocol violation.

Explanation: The server refuses a request for a clientsession because sign-on protocol has been violated.


User Response: This error is usually the result of aclient programming error in which the sign-on verb hasbeen incorrectly formatted and delivered to the server.This error can also result when the server is contactedby an application that is not a part of this product.

ANR0422W Session session number for node nodename (client platform) refused - nodename not registered.

Explanation: The server refuses a request to start aclient session because the client node name is notregistered in the server database.


User Response: Register the node name with theserver before establishing a session. If the server isrunning with OPEN registration, no action is required;the client prompts the user for a password andregisters the client with the server. If CLOSEDregistration is in effect on the server, an authorizedadministrator must use the REGISTER NODEcommand to register the client node name with theserver.

ANR0423W Session session number for administratoradministrator ID (client platform) refused -administrator name not registered.

Explanation: The server refuses a request to start anadministrative session because the administrator nameis not registered in the server database.


User Response: Register the administrator name withthe server before establishing a session. An authorizedadministrator must use the REGISTER ADMINcommand to register the administrator with the server.

ANR0424W Session session number for node nodename (client platform) refused - invalidpassword submitted.

Explanation: The server refuses a request to start aclient session because an invalid password has beensubmitted by the client during sign-on processing. Theserver will continue to deny access attempts by thisclient until a valid password is submitted.




User Response: Enter the proper password. If thepassword has been forgotten by the user, an authorizedadministrator can assign a new password by using theUPDATE NODE command.

ANR0425W Session session number for node nodename (client platform) refused - passwordhas expired.

Explanation: The server refuses the specified sessionbecause the administrator or client node’s passwordhas expired.


User Response: Upon receipt of this error condition,the client program immediately reconnects to the serverspecifying a password update session and prompts theuser for a new password. After the user enters a newpassword, the client reconnects to the server for normaloperations. Alternatively, an authorized administratorcan update the client password using the UPDATENODE or UPDATE ADMIN command.

ANR0426W Session session number for node nodename (client platform) refused - openregistration not permitted.

Explanation: The server refuses a client sessionbecause an open registration action has been attemptedand the server is running with CLOSED registration.


User Response: Ask an authorized administrator tosubmit the request using the REGISTER NODE orREGISTER ADMIN command.

ANR0427W Session session number for node nodename (client platform) refused - serverversion is down-level with this client.

Explanation: The server refuses a client sessionbecause the client program version level is newer thanthat supported by the server program.


User Response: Apply service to the server programto make it compatible with the newer client program,or use an older client program to contact the server.

ANR0428W Session session number for node nodename (client platform) refused - client isdown-level with this server version.

Explanation: The server refuses a client sessionbecause the client program version level is older thanthat supported by the server program. For certainproblems (such as the compression fix), once a nodeconnects to the server using the newer client, the serverrecords this fact and will not let this node back off this

client version to a version that does not include the fix.


User Response: Apply service to the client program tomake it compatible with the newer server program.

ANR0429W Session session number for node nodename (client platform) refused - maximumserver sessions (max sessions allowed)exceeded.

Explanation: The server refuses the specified client oradministrative session because the maximum numberof concurrent client sessions has been exceeded.


User Response: If necessary, increase the maximumnumber of permitted sessions. To do this, update thevalue for the MAXSESSIONS parameter in the serveroptions file and restart the server with the updatedoptions file. Note that increasing the MAXSESSIONSvalue requires additional memory resource by theserver. You may want to retry the connection at a latertime.

ANR0430W Session session number for node nodename (client platform) refused - nodename is locked.

Explanation: The server refuses the specified clientsession because the node is locked from server access(with the LOCK NODE command).


User Response: Before the client node is permitted toaccess the server, a properly authorized administratormust unlock the node with the UNLOCK NODEcommand.

ANR0431W Session session number refused -administrator administrator ID (clientplatform) is locked.

Explanation: The server refuses the specifiedadministrative session because the administrator islocked from server access (with the LOCK ADMINcommand).


User Response: Before the administrator is permittedto access the server, a properly authorizedadministrator must unlock the administrator with theUNLOCK ADMIN command.



ANR0432W Session session number for node nodename (client platform) refused -insufficient memory.

Explanation: The server ends the specified sessionbecause sufficient memory (virtual memory) is notavailable.

System Action: The server ends the session andcontinues operation.


ANR0433W Session session number for node oradministrator ID (client platform) refused -insufficient recovery log space.

Explanation: The server ends the specified client oradministrative session because sufficient log space isnot available to complete a database transaction.


User Response: To increase the amount of log spaceavailable to the server, an authorized administrator canadd log volumes using the DEFINE LOGVOLUMEcommand, and extend the size of the log using theEXTEND LOG command.

ANR0434W Session session number for node oradministrator ID (client platform) refused -insufficient database space.

Explanation: The server ends the specified client oradministrative session because sufficient database spaceis not available to complete a database transaction.


User Response: To increase the amount of databasespace available to the server, an authorizedadministrator can add database volumes using theDEFINE DBVOLUME command, and extend the size ofthe database using the EXTEND DB command.

ANR0435W Session session number for node nodename (client platform) refused - internalerror detected.

Explanation: The server ends the specified sessionbecause an internal logic error is detected.


User Response: To determine the source of the error,the administrator can examine server messages issuedprior to this message. The QUERY ACTLOG commandcan be used to view the activity log and search for

messages. If the error cannot be isolated and resolved,contact your service representative.

ANR0436W Session session number refused - a WDSFclient is attempting to access the serverusing client name client node name (clientplatform), associated with a non-WDSFclient.

Explanation: The server refuses a client sessionbecause a Workstation DataSave Facility (WDSF) clientis attempting to access the server using a node nameassociated with a non-WDSF client. When convertingfrom WDSF, WDSF client programs cannot be used toaccess the server with a specific node name once thenon-WDSF client program has been used to access theserver with that node name.


User Response: Access the server using a non-WDSFclient program for the node name.

ANR0437W Session session number for node clientnode name (client platform) encountered aninternal server error while checkinglicense compliance.

Explanation: The server encountered an internal errorin determining if the server is in compliance withlicense terms.

System Action: The client session is ended.

User Response: Use the QUERY LICENSE andQUERY STATUS commands to determine if the serveris in compliance with license terms. Start an AUDITLICENSES process to re-adjust server licenseinformation. When this process completes you mayrestart the session. If the problem persists, contact yourservice representative.

ANR0438W Session session number archive operationfor client client node name (client platform)has been denied - Server is not incompliance with license terms.

Explanation: The server refuses a client archiveoperation because the current server configuration isnot in compliance with license terms.

System Action: Server operation continues. Clientsmay perform any action except backup or archive.

User Response: Use the QUERY LICENSE commandto determine the license terms that are no longer incompliance.



ANR0439W Session session number backup operationfor client client node name (client platform)has been denied - Server is not incompliance with license terms.

Explanation: The server refuses a client backupoperation because the current server configuration isnot in compliance with license terms.

System Action: Server operation continues. Clientsmay perform any action except backup or archive.


ANR0440W Protocol error on session session numberfor node client node name (client platform) -invalid verb header received.

Explanation: The server detects a protocol error on thespecified session because an invalid verb header hasbeen received from the client. Verb headers alwaysprecede communication sent to the server from theclient or from the server to the client.

System Action: The server ends the client session.

User Response: Correct the programming error in theclient program if it has been written by yourinstallation using WDSF verbs. Otherwise, contact yourservice representative.

ANR0441W Protocol error on session session numberfor node client node name (client platform) -invalid data length received.

Explanation: The server detects a protocol error on thespecified session because an invalid verb length hasbeen received from the client.



ANR0442W Protocol error on session session numberfor node client node name (client platform) -excessively large verb received.

Explanation: The server detects a protocol error on thespecified session because an invalid verb length hasbeen received from the client.



ANR0443W Protocol error on session session numberfor node client node name (client platform) -invalid ″field name″ field found in ″verbname″ verb (offset offset position).

Explanation: The server detects a protocol error on thespecified session because an invalid field has beenfound in a verb sent from the client node.



ANR0444W Protocol error on session session numberfor node client node name (client platform) -out-of-sequence verb (type verb name)received.

Explanation: The server detects a protocol error on thespecified session because a verb has been received thatdoes not adhere to the client-server exchange sequence.


User Response: If the client generating the error is notan API client, contact your service representative. If theclient generating the error is an API client, contact theowner of the API client. If the client generating theerror is a client that you have created using WDSFverbs, correct the programming error in your clientprogram.

ANR0445W Protocol error on session session numberfor node client node name (client platform) -maximum group transaction sizeexceeded.

Explanation: The server detects a protocol error on thespecified session because the client has attempted togroup more than the maximum database updateoperations in a single database transaction.



ANR0446W Session session number client client nodename compression method unsupported -Compression forced OFF. Please obtainthe latest level of the client code.

Explanation: The client is using a compressionmethod that is no longer supported by the Server.

System Action: Server operation continues. Theclient’s backup operation continues, withoutcompressing the data.



User Response: The compression method used by theclient is no longer supported. In order to usecompression, the client needs to be upgraded to a clientservice level that supports the newer compressionmethod.

ANR0447W Session session number spacemanagement migration operation forclient client node name (client platform) hasbeen denied - Server is not incompliance with license terms.

Explanation: The server refuses a client spacemanagement migration operation because the currentserver configuration is not in compliance with licenseterms.

System Action: Server operation continues. Clientsmay perform any action except backup, archive, orspace-managed file migration.


ANR0448W Session session number spacemanagement migration operation forclient client node name (client platform) hasbeen denied - server is not licensed forspace management support.

Explanation: The server refuses a client spacemanagement migration operation because the server isnot licensed to support space-managed clients.


User Response: Licenses to support space-managedclients can be obtained from your service provider orreseller. The REGISTER LICENSE command can beused with these licenses to enable space managementsupport.

ANR0449W Session session number spacemanagement migration operation forclient client node name (client platform) isin violation of server license terms -server is not licensed for spacemanagement support.

Explanation: The server warns about a client spacemanagement migration operation because the server isnot licensed to support space-managed clients.


User Response: Licenses to support space-managedclients can be obtained from your service provider orreseller. The REGISTER LICENSE command can beused with these licenses to enable space managementsupport.

ANR0450W Session session number for server servername (client platform) refused - servername not defined for server to servercommunications.

Explanation: The server refuses a request to start aserver session because the requesting server name isnot defined in the server database, or the requestingserver definition does not have a SERVERPASSWORD.


User Response: Register the requesting server namewith the server before establishing a session, or updatethe existing requesting server definition and set aSERVERPASSWORD. An authorized administratormust use the DEFINE SERVER or UPDATE SERVERcommand to register the requesting server and set thepassword.

ANR0451W Session session number for server servername (server platform) refused - invalidpassword submitted.

Explanation: The server refuses a request to start aserver session because an invalid password has beensubmitted during sign-on processing. The server willcontinue to deny access attempts by that server untilvalid passwords are submitted.


User Response: Set the proper passwords. If thepassword has been changed on either server, anauthorized administrator can set new passwords byusing the UPDATE SERVER command with theSERVERPASSWORD parameter.

ANR0452W Session for server server name refused -server name not defined for server toserver communications.

Explanation: The server refuses a request to start aserver to server session because a server name is notdefined in the server database, or the server definitiondoes not have a SERVERPASSWORD. Server to servercommunications using the serverpassword requires thatthe each server has had a server definition for the otherserver.


User Response: Register the server names on bothboth servers before establishing a session, or update theserver’s existing server definition and set aSERVERPASSWORD. An authorized administratormust use the DEFINE SERVER or UPDATE SERVERcommand register the servers and set the passwords.



ANR0453W Server to server session refused - nopassword defined.

Explanation: The server to server session cannot beinitiated because no server password has been definedfor this server.


User Response: Define a server password with theSET SERVERPASSWORD command and retry thecommand.

ANR0454E Session rejected by server server name,reason: rejection reason.

Explanation: The server has attempted to open asession with the shown server. The session was rejectedfor the indicated reason.

System Action: The operation fails.

User Response: Check both the servers for anyadditional messages that might further describe thereason the session was rejected. For a reason ofAUTHENTICATION FAILURE, ensure that allpasswords have been set correctly on both servers. Thepassword for the server (set by SETSERVERPASSWORD on server X) and the password inthe server definition (set by DEFINE or UPDATESERVER X SERVERPASSWORD=) are the samepassword. For a reason of VERIFICATION FAILURE,use the QUERY SERVER command to determine thatthe HLADDRESS and LLADDRESS of the target serverare correct. If they are not, correct them with theUPDATE SERVER command. If they are correct,resynchronize with the target server by issuing theUPDATE SERVER FORCESYNC=YES. For a reason ofCOMMUNICATION FAILURE ensure that the targetserver is available and that TCPIP is available on bothservers. For a reason of NO RESOURCE, ensure thatthe receiving server is enabled, has sufficient DB, LOG,and memory resource to support the source serversession. For a reason of INTERNAL ERROR, use themessages on the target server to determine the problemand contact your service representative. Retry thefailing operation.

ANR0455W Invalid Command command name forSNMP session.

Explanation: An SNMP administrative sessionattempted to run a command which is not an macroinvocation. SNMP administrative sessions are onlyallowed to issue macro commands.


User Response: Enter commands through the SNMPadministrative interface which are macros defined onthe server.

ANR0456W Session rejected for server name servername at High level address Low leveladdress does not match.

Explanation: The server name at the address specifieddoes not match the name in the server definition. Theconnection is not established.

System Action: The server continues.

User Response: Ensure the HLADDRESS andLLADDRESS in the define server command are correct,and that the servername on the server being contactedmatches the name used in the DEFINE SERVERcommand.

ANR0457W Session for server server name refused -crossdefine is not allowed on thisserver.

Explanation: The server refuses a request to start aserver to server session for crossdefine because it is notallowed on this server. The server will deny anysessions for crossdefine until crossdefine is allowed onthis server.


User Response: An authorized administrator must usethe SET CROSSDEFINE ON command to allow crossregistration of servers.

ANR0458S Server server name does not supportaccess by the Storage Agent.

Explanation: The storage agent attempted to contact aDatabase Server, but the server contacted was not atthe correct level.

System Action: The Storage Agent terminates.

User Response: Specify a correct Database Server inthe devconfig file for the Storage Agent.

ANR0459W Signon for administrator administratorname refused - invalid administratorname and/or password submitted.

Explanation: The server refuses a request to start anadministrative session because an invalid administratorname and/or password has been submitted by the userduring sign-on processing. The server will continue todeny access attempts by this administrator until a validpassword is submitted, or until the administrator islocked due to maximum number of invalid passwordattempts being exceeded.


User Response: Enter the proper password. If thepassword has been forgotten by the user, an authorizedadministrator can assign a new password by using theUPDATE ADMIN command.



ANR0460W Open registration failed for sessionsession number - node name node name(client platform) already exists.

Explanation: The server refuses a client session duringopen registration because the client has specified anode name that is already registered on the server.


User Response: The client program user must specifya different node name for the client in the clientoptions file.

ANR0461W Open registration failed for sessionsession number for node node name (clientplatform) - policy domain STANDARDdoes not exist.

Explanation: The server refuses a client session duringopen registration because the STANDARD policydomain does not exist. All nodes added to the serverdatabase under open registration are automaticallyassigned to the STANDARD policy domain. This policydomain must be defined and have an active policy setto support open registration.


User Response: If you want to support openregistration, define a policy domain using the DEFINEDOMAIN command with the name STANDARD andactivate a valid policy set in the domain. You can issuethe UPDATE NODE command to move nodes todifferent policy domains after the nodes have registeredthemselves through open registration.

ANR0462W Open registration failed for sessionsession number for node node name (clientplatform) - invalid node name.

Explanation: The server refuses a client session duringopen registration because the node name specified bythe client is not valid.


User Response: Specify a node name in the optionsfile of the client program that contains valid charactersand does not exceed the maximum length in size. Referto Backup-Archive Clients Installation and User’s Guide fora description of the node name restrictions.

ANR0463W Open registration failed for sessionsession number for node node name (clientplatform) - invalid password.

Explanation: The server refuses a client session duringopen registration because the password name specifiedby the user is not valid.


User Response: Specify a password that uses valid

characters and is less than the maximum length in size.Refer to Backup-Archive Clients Installation and User’sGuide for a description of the password restrictions.

ANR0464W Open registration failed for sessionsession number for node node name (clientplatform) - exceeded number of nodesavailable under license terms.

Explanation: The server detected an attempt toregister more nodes than allowed by the terms of thecurrent license.

System Action: Server operation continues, but theREGISTER NODE command fails, and the node is notregistered.


ANR0465W Open registration failed for sessionsession number for node node name (clientplatform) - policy domain STANDARDdoes not have an ACTIVE policy set.

Explanation: The server refuses a client session duringopen registration because the STANDARD policydomain does not have an active policy set. All nodesadded to the server database under open registrationare automatically assigned to the STANDARD policydomain. This policy domain must be defined and havean active policy set to support open registration.


User Response: If you want to support openregistration, define a policy domain using the DEFINEDOMAIN command with the name STANDARD andactivate a valid policy set in the domain. You can issuethe UPDATE NODE command to move nodes todifferent policy domains after the nodes have registeredthemselves through open registration.

ANR0466E The SETSTORAGESERVER commanddid not complete successfully.

Explanation: The SETSTORAGESERVER commandencountered an error and did not complete successfully.

System Action: Storage agent operation terminates.

User Response: Please review prior error messagesand take the necessary corrective actions.

ANR0467I The SETSTORAGESERVER commandcompleted successfully.

Explanation: The SETSTORAGESERVER commandhas completed successfully, and the appropriate deviceconfiguration files have been updated.

System Action: Storage agent operation terminates.



User Response: None

ANR0468E Server-to-server export and import notallowed with server server name. Exportserver is at version export version; importserver is at version import version.

Explanation: An attempt was made to export to anoutdated server. The server on which the import isperformed must be at the same or later level than theserver from which the data was exported.

System Action: The export operation ends and serveroperation continues.

User Response: Export to a server that is at the sameor later level.

ANR0475W Session session number for node nodename (client platform) refused - node isnot allowed to initiate sessions onadministrative port.

Explanation: The server had refused to start a sessionwith the specified client node because the nodeconnected to the server on the server’s administrativeport. When different port numbers are used foradministrative and client sessions, client sessions maybe started only on the port used for client sessions.


User Response: The client option file should beupdated to specify the port to be used for clientsessions. This is typically specified by TCPPORT optionin both client and server option files. The MVS serveralso uses the ICSPORT option.

ANR0476W Session session number for node nodename (client platform) refused - node isnot allowed to initiate sessions.

Explanation: The server had refused to start a sessionwith the specified client node because the node is notallowed to initiate session. Only server initiatedsessions are allowed with this client. The SESSIONINITparameter of the REGISTER NODE and UPDATENODE commands control the ability of a client toinitiate sessions.


User Response: An administrator can use theUPDATE NODE command with the SESSIONINITparameter to sepcify that the client may initiatesessions. Alternatively, sessions can be scheduled withthe client that are stared by the server throughserver-prompted scheduling commands ( DEFINESCHEDULE, DEFINE ASSOCIATION ).

ANR0477W Session session number refused - Theclient client node name cannot access theserver with a platform type of clientplatform.

Explanation: A client with a invalid combination ofnode type and platform type has requested a sessionwith the server. For example, a node id of type NAScan only sign on with a platform type of ″TSMNAS″,all other node types cannot use this platform type.

System Action: The session request is refused. Theserver operation continues.

User Response: Verify that the Id used by a client tosign on has the proper platform type.

ANR0478W Session request refused. Server isrunning in standalone mode.

Explanation: A client has requested a session with theserver. The server is running in a mode in which itcannot start client sessions.


User Response: No response is required. To reduce ordisable the display of this message, you can update theserver options before running in standalone mode withthe COMMMETHOD NONE option. This will allow theserver to run without enabling client connections.

ANR0479W Session session number for server servername (server platform) terminated -connection with server severed.

Explanation: If server A has opened a connection withserver B, server B’s session is ended because thecommunications link has been closed by a networkerror or by server A’s program.

System Action: Server A continues operation.

User Response: If server B halts operation or in someway stops communicating with server A, this messagewill be displayed on server A indicating that theconnection was closed suddenly by server B. A networkfailure can also cause this message to be displayed. If alarge number of these messages occur simultaneously,check the network for failure and correct any problems.

ANR0480W Session session number for node nodename (client platform) terminated -connection with client severed.

Explanation: The specified client session is endedbecause the communications link has been closed by anetwork error or by the client program.


User Response: If a user breaks out of a clientprogram, this message will be displayed on the server



as the connection is suddenly closed by the client. Anetwork failure can also cause this message to bedisplayed. If a large number of these messages occursimultaneously, check the network for failure andcorrect any problems.

ANR0481W Session session number for node nodename (client platform) terminated - clientdid not respond within commtimeoutseconds seconds.

Explanation: The server ends a client session becausethe client has been holding database locks (atransaction was in progress) and the client has notresponded in the number of seconds specified by theCOMMTIMEOUT parameter in the server options file.

System Action: The server rolls back the transactionthat has been in progress and the session is ended.Server operation continues.

User Response: If a large number of these messagesappear, you may want to increment the value specifiedfor the COMMTIMEOUT value in the server optionsfile and restart the server. The amount of time that ittakes for a client to respond is dependent upon thespeed and processor load for the client and the networkload.

ANR0482W Session session number for node nodename (client platform) terminated - idle formore than idletimeout minutes minutes.

Explanation: The server ends a client session becauseit has been idle for more minutes than specified in theIDLETIMEOUT parameter in the server options file.The client program will automatically attempt toreconnect to the server when necessary.


User Response: If the problems persists, increase thevalue specified for the IDLETIMEOUT parameter in theserver options file and restart the server. Many times,the client program is idle while waiting for the user tochoose an action to perform (for example, backup,archive, restore, or retrieve files). If a user starts theclient program and does not choose an action toperform, the session will eventually time out. The clientprogram automatically reconnects to the server whenthe user chooses an action that requires serverparticipation. Note that a large number of idle sessionscan inadvertently prevent other users from connectingto the server, so care should be used when increasingthe IDLETIMEOUT parameter.

ANR0483W Session session number for node nodename (client platform) terminated - forcedby administrator.

Explanation: The server ends a client session inresponse to a CANCEL SESSION command issued byan authorized administrator.

System Action: The server rolls back any transactionsin progress for the terminated client session.


ANR0484W Session session number for node nodename (client platform) terminated -protocol violation detected.

Explanation: The server ends the specified sessionbecause a communications protocol error by the clienthas been detected.


User Response: Examine the client message todetermine the problem. Correct the programming errorin the client program. If the error cannot be isolatedand resolved, contact your service representative.

ANR0485W Session session number for node nodename (client platform) terminated -sufficient memory is not available.

Explanation: The server ends the specified sessionbecause sufficient memory (virtual memory) is notavailable.



ANR0486W Session session number for node nodename (client platform) terminated -internal error detected.

Explanation: The specified client session is ended bythe server because an internal processing error has beendetected on the server. A programming error may haveoccurred in the server program.

System Action: The session is ended and serveroperation continues.


ANR0487W Session session number for node nodename (client platform) terminated -preempted by another operation.

Explanation: The server ends a client session inresponse to a cancel request issued by a higher priorityoperation that needed the mount point that the clientwas using.

System Action: The server rolls back any transactionsin progress for the terminated client session.

User Response: Reissue the operation. If this messageappears frequently, consider increasing the mountlimitvalue for the affected device class.



ANR0488W Session session number for node nodename (client platform) terminated -transfer rate is less than (transfer rate)and more than (elapsed time since first datatransfer) minutes have elapsed since firstdata transfer.

Explanation: The server is canceling client sessionnumber session number. Depending on the state of thesession, it may take a while for the session to becanceled. The server ends a client session because it hasbeen active for more minutes than specified in theTHROUGHPUTTIMETHRESHOLD parameter in theserver options file and the data transfer rate is less thanthe amount specified with theTHROUGHPUTDATATHRESHOLD parameter in theserver options file. The client is transferring data to theserver at an abnormally slow rate and may havebecome a bottleneck for handling data from otherclients. If the client has caused log records to bewritten, it is possible that this client will prevent logspace reclamation.

System Action: The session is canceled and serveroperation continues.

User Response: If a low data transfer rate is not aproblem, the THROUGHPUTTIMETHRESHOLD orTHROUGHPUTDATATHRESHOLD parameters in theserver options file can be set to zero - this will disablethe throughput check. The change can be made withouttaking down the server and restarting it by using theSETOPT THROUGHPUTTIMETHRESHOLD or theSETOPT THROUGHPUTDATATHRESHOLDcommands. If a low data transfer rate is not expected,external causes should be investigated. This wouldinclude network problems and problems in accessingdata on the client node. The client program mayautomatically reconnect to the server, so this messagemay appear on subsequent sessions until the datatransfer problem is resolved. The default serveroperation is not to perform a throughput check.

ANR0489W Session session number refused for clientnode name - NAS type nodes are notsupported by a storage agent.

Explanation: The specified client tried to connect to astorage agent. The storage agent does not support anode that is defined as TYPE=NAS.


User Response: The client should be reconfigured tonot try LAN-free operations. This may be done bysetting UPDATE NODE ENABLELANFREE=NO for theclient.

ANR0490I Canceling session session number fornode node name (client platform) .

Explanation: The server is canceling client sessionnumber session number. This message is displayed inresponse to the CANCEL SESSION command.Depending on the state of the session, it may take awhile for the session to be canceled.



ANR0491I No matching session(s) found to cancel.

Explanation: The server cannot find any sessions tocancel matching the specifications entered in theCANCEL SESSION command.


User Response: Use the QUERY SESSION commandto ensure that the session you wish to cancel isconnected. Reissue the command using the appropriatesession number to cancel the client session.

ANR0492I All drives in use. Session session numberfor node node name (client platform) beingpreempted by higher priority operation.

Explanation: When a high priority operationattempted to find an available drive, all the drives werebeing used. To free up a drive for this operation, theclient session identified is being cancelled by thesystem.

System Action: The lower priority client session iscancelled to free up a mount point (drive).

User Response: When a drive again becomesavailable, restart the session that was cancelled. Thissession was most likely a backup/archive session andyou may just want to let it restart automatically duringits next scheduled backup window. If this messageappears frequently, you may want to increase thenumber of drives available. See the MOUNTLIMITparameter on the UPDATE DEVCLASS command.

ANR0493I Restore session session number canceled.

Explanation: The specified session was canceled withthe CANCEL RESTORE command.

System Action: The restore session is canceled andserver operation continues.




ANR0494I Volume volume name in use. Sessionsession number for node node name (clientplatform) being preempted by higherpriority operation.

Explanation: When a high priority operationattempted to acquire a specific volume, it was beingused. To free the volume for this operation, the clientsession identified is being cancelled by the system.

System Action: The lower priority client session iscancelled to free up the volume.

User Response: Restart the session that was cancelled,it will wait until the higher priority operation iffinished with the volume. This cancelled session wasmost likely a backup/archive session and you may justwant to let it restart automatically during its nextscheduled backup window.

ANR0495I Cannot cancel the specifiedEXPORT/IMPORT session.

Explanation: The server cannot cancel the sessionspecified in the CANCEL SESSION command.


User Response: Export/Import sessions cannot becanceled using CANCEL SESSION. The user shoulduse the CANCEL PROCESS command to terminate theEXPORT/IMPORT operation.

ANR0500W Transaction failed for session sessionnumber for node node name (clientplatform) - invalid password submitted.

Explanation: The server ends a password updatetransaction because the user has not correctly specifiedthe current password.


User Response: Update your password by correctlyspecifying the current password. If the currentpassword has been misplaced, the administrator canreassign a password for the client by using theUPDATE NODE or UPDATE ADMIN command.

ANR0501W Transaction failed for session sessionnumber for node node name (clientplatform) - invalid policy bindingspecified.

Explanation: The server ends a database updatetransaction for the specified session because an invalidmanagement class has been specified for a file ordirectory object.

System Action: The specified session is ended andserver operation continues.

User Response: Correct the programming error in theclient program if it has been written by your

installation using WDSF verbs. Otherwise, contact yourservice representative.

ANR0520W Transaction failed for session sessionnumber for node node name (clientplatform) - storage pool pool name is notdefined.

Explanation: The server rolls back a database updatetransaction for the specified session because thedestination specified for a management class copygroup specifies the named storage pool, but thatstorage pool does not exist.


User Response: An administrator with policyauthority over the client policy domain must correctmanagement class definitions so that copy groupdestinations refer to defined storage pools, or thespecified storage pool must be created by an authorizedadministrator.

ANR0521W Transaction failed for session sessionnumber for node node name (clientplatform) - object excluded by size instorage pool pool name and all successorpools.

Explanation: The server ends a database updatetransaction for the specified session because the size ofa file sent from the client node is larger than thatallowed in the storage pool specified in the client’smanagement class copy group. No successor storagepools to the one specified on the copy group can acceptthe large file.


User Response: If the client is not using compressionto send files to the host, turn compression on for theclient (using the UPDATE NODE command) to try andresolve the problem. Otherwise, the maximum file sizefor one or more of the storage pools in the storagehierarchy can be increased to accommodate the file. Anauthorized administrator can increase the MAXSIZEparameter by issuing the UPDATE STGPOOLcommand.

ANR0522W Transaction failed for session sessionnumber for node node name (clientplatform) - no space available in storagepool pool name and all successor pools.

Explanation: The server ends a database updatetransaction for the specified session because the storagepool specified in the client’s management class copygroup does not contain enough free space to hold thefiles sent from the client. Successor storage pools to theone specified on the copy group do not contain enoughfree space.




User Response: An authorized administrator can issuethe DEFINE VOLUME command to add storage to oneor more storage pools in the storage hierarchy. Thisaction may also involve creating storage space by usingan operating system specific utility.

ANR0523W Transaction failed for session sessionnumber for node node name (clientplatform) - error on output storagedevice.

Explanation: The server ends a database updatetransaction for the specified client because an I/O errorhas been encountered by the server in writing to adevice.


User Response: Query the activity log to findmessages preceding this one that specify the failingdevice. Storage pool volumes can be varied offline (byusing the VARY command), or the server may need tobe halted to correct the hardware problem. After theproblem is corrected, the client should retry theoperation.

ANR0524W Transaction failed for session sessionnumber for node node name (clientplatform) - data transfer interrupted.

Explanation: The database transaction associated withsession session number was aborted because datatransfer to or from data storage was interrupted by anexternal event.


User Response: Examine the messages issued prior tothis message to determine why the data transfer wasinterrupted. Attempt the client operation again if theproblem can be resolved.

ANR0525W Transaction failed for session sessionnumber for node node name (clientplatform) - storage media inaccessible.

Explanation: The server ends a transaction for thespecified session because storage volumes are notavailable in the storage pools in which the client’s filesare to be stored.

System Action: The server ends the specified sessionand server operation continues.

User Response: An authorized administrator can issuethe DEFINE VOLUME command to add storage to oneor more storage pools in the storage hierarchy. TheVARY ONLINE command can be used to vary offlinestorage volumes online in the storage hierarchy to

make them available to client nodes for file storage.

ANR0526W Transaction failed for session sessionnumber for node node name (clientplatform) - sufficient recovery log spaceis not available.

Explanation: The server ends a database updatetransaction for the specified session because sufficientlog space is not available on the server.


User Response: An authorized administrator can issuethe DEFINE LOGVOLUME command to add volumesfor use by the log, and can issue the EXTEND LOGcommand to extend the size of the log so that the newvolumes are used.

ANR0527W Transaction failed for session sessionnumber for node node name (clientplatform) - sufficient database space isnot available.

Explanation: The server ends a database updatetransaction for the specified session because sufficientdatabase space is not available on the server.


User Response: An authorized administrator can issuethe DEFINE DBVOLUME command to add volumesfor use by the database, and can issue the EXTEND DBcommand to extend the size of the database so that thenew volumes are used.

ANR0528W Transaction failed for session sessionnumber for node node name (clientplatform) - thread resource not available.

Explanation: The server ends a database updatetransaction for the specified session because sufficientmemory is not available for starting additionalprocesses on the server.



ANR0529W Transaction failed for session sessionnumber for node node name (clientplatform) - insufficient memory.

Explanation: The server ends a database updatetransaction for the specified session because sufficientmemory is not available on the server.

System Action: The server ends the specified session



and server operation continues.


ANR0530W Transaction failed for session sessionnumber for node node name (clientplatform) - internal server error detected.

Explanation: The server ends a database updatetransaction for the specified session because an internallogic error is detected.


User Response: Examine the server messages issuedprior to this message to determine the source of theerror. Issue the QUERY ACTLOG command to view theactivity log and search for messages. If the error cannotbe isolated and resolved, contact your servicerepresentative.

ANR0531W Transaction failed for session sessionnumber for node node name (clientplatform) - invalid file space identifierspecified by client.

Explanation: The server ends a database updatetransaction for the specified session because the filespace identified by the client for the transaction doesnot exist.

System Action: This action usually occurs when aclient is operating on a file space that is currently beingdeleted as a result of an administrative command orclient action. The server ends the specified session andserver operation continues.

User Response: Use the QUERY PROCESS commandto monitor and wait for any file space deletionprocesses to complete, or cancel the process if you donot want to delete the file space. Try the client actionagain after this action has been taken.

ANR0532W DiagnosticID: Transaction transaction IDwas aborted for session session numberfor node node name (client platform).

Explanation: An error has been detected during atransaction commit for the specified session. Thismessage should be preceded by other messages thatgive additional information about the failed transaction.


User Response: Check for additional messages andeliminate the condition that caused the failedtransaction. If the error cannot be isolated and resolved,contact your service representative.

ANR0533W Transaction failed for session sessionnumber - compression method used byclient not supported. Please obtain thelatest level of the client code.

Explanation: The server ends the transaction for thespecified session because the compression method thatis used by the client is no longer supported by theserver.


User Response: The client must either backup thedata with compression turned off, or upgrade to aclient that supports the newer compression method. Ifthe client is a WDSF client, upgrade to a non-WDSFclient in order to use the compression performed by theclient.

ANR0534W Transaction failed for session sessionnumber for node node name (clientplatform) - size estimate exceeded andserver is unable to obtain additionalspace in storage pool pool name.

Explanation: The server ends a database updatetransaction for the specified session because the sizeestimate provided by the client is too small. The serverhas attempted to obtain additional space in theindicated storage pool, but was unable to do so.

System Action: The specified session is ended andserver operation continues. If pool name is a randomaccess storage pool with caching enabled, it is alsopossible that additional space can be made available inthis storage pool by eliminating cached files. When theserver allocates space based on the size estimateprovided by the client, it frees space occupied bycached files if this space is needed to obtain theestimated space. However, if the server later determinesthat the file size estimate was too low, it attempts toobtain additional space that is not utilized, but does notdelete cached files to do so. If the client sending thedata has the option COMPRESSALWAYS YES set, it ispossible that a file grew during the compressionoperation and when the client sent it to the server itexceeded the space available in storage pool pool name.

User Response: This message may indicate that thereis no additional space in pool name. The following arepossible circumventions:

An authorized administrator can issue the DEFINEVOLUME command to add storage to this pool.

If the suspected cause of the failure is that pool name isa DISK storage pool and that space in use by cachedfiles was not freed, turn off caching for the storage pooland issue the MOVE DATA command for the volumesin pool pool name.

If the suspected cause of the failure is that a file grewin size during compression on the client, another



possible circumvention is to set theCOMPRESSALWAYS option in the client options file toNO and retry the operation. This may allow the clientto accurately report the file size and possibly avoid theout of space condition in the storage pool.

ANR0535W Transaction failed for session sessionnumber for node node name (clientplatform) - insufficient mount pointsavailable to satisfy the request.

Explanation: The server was unable to allocatesufficient mount points to process the transaction.

System Action: The operation is ended and serveroperation continues.

User Response: If necessary, make more mount pointsavailable.

ANR0536W Transaction failed for session sessionnumber for node node name (clientplatform) - downlevel client does notsupport format of stored files.

Explanation: A client attempts to perform anoperation involving files that are stored in a format thatis not supported by that client level.


User Response: Upgrade the client to a later level.

ANR0537E Transaction failed for session sessionnumber for node node name (clientplatform) - filespace name cannot berenamed from or to a unicode name.

Explanation: The server ends a database updatetransaction for the specified session because a file spacewas attempted to be renamed to or from unicode.

System Action: The server ends the specifiedtransaction and server operation continues.

User Response: Do not attempt to rename a unicodefile space to a non-unicode name or a non-unicode filespace to a unicode name.

ANR0538I A resource waiter has been aborted.

Explanation: The server aborts a resource waitbecause of waiting too long for a resource to becomeavailable. This could cause a process or session to fail.If this causes a process or a session to fail then therewill be other messages at this time indicating whichprocess or session has failed. Resources are internalserver resources such as locks and synchronizationobjects.

System Action: The server terminates the resourcewith request and server operation continues.

User Response: Either a server deadlock situation hasoccurred or the resource timeout value is set too low.Check the setting for the RESOURCETimeout serveroption and increase the value. If the problem persistswith a higher timeout then contact your servicerepresentative.

ANR0540W Retrieve or restore failed for sessionsession number for node node name (clientplatform) - data integrity error detected.

Explanation: The server ends a file retrieval operationfor the specified session because an internal databaseintegrity error has been encountered on the server.

System Action: The server ends the specified sessionand continues operation.


ANR0541W Retrieve or restore failed for sessionsession number for node node name (clientplatform) - error on input storage device.

Explanation: The server ends a client retrieval orrestore operation for the specified session because anI/O error has been encountered by the server inreading from a device.


User Response: Query the activity log to findmessages preceding this one that specify the device thatis failing. Storage pool volumes can be varied offline(by using the VARY OFFLINE command), or the servermay need to be shut down by using the HALTcommand to correct the hardware problem. After theproblem is corrected, the client may try the operationagain.

ANR0542W Retrieve or restore failed for sessionsession number for node node name (clientplatform) - storage media inaccessible.

Explanation: The server ends a client retrieval orrestore operation for the specified session because aneeded storage pool volume has been varied offline.


User Response: Use the VARY ONLINE command tovary offline storage volumes online in the storagehierarchy, and make them available to client nodes forfile storage.

ANR0543W Retrieve or restore failed for sessionsession number for node node name (clientplatform) - data transfer interrupted.

Explanation: The database transaction associated withsession session number was aborted because data



transfer to or from data storage was interrupted by anexternal event.


User Response: Examine the messages issued prior tothis message to determine why the data transfer wasinterrupted. Attempt the client operation again, if theproblem can be resolved.

ANR0544W Retrieve or restore failed for sessionsession number for node node name (clientplatform) - thread resource not available.

Explanation: The server ends a file retrieval or restoreoperation for the specified session because sufficientmemory is not available for starting additionalprocesses on the server.



ANR0545W Retrieve or restore failed for sessionsession number for node node name (clientplatform) - insufficient memory.

Explanation: The server ends a file retrieval or restoreoperation for the specified session because sufficientmemory is not available on the server.



ANR0546W Retrieve or restore failed for sessionsession number for node node name (clientplatform) - internal server error detected.

Explanation: The server ends a file retrieval or restoreoperation for the specified session because an internallogic error is detected in the server program.


User Response: Examine the server messages issuedprior to this message to determine the source of theerror. Use the QUERY ACTLOG command to view theactivity log and search for messages. If the error cannotbe isolated and resolved, contact your servicerepresentative.

ANR0547E Invalid data was encountered in thecommand processor output stream:output formatting terminated for the lastcommand entered.

Explanation: The server console session encounters anerror in formatting output from a command.

System Action: The command output is discardedand server operation continues.

User Response: Use the server QUERY command todetermine if the command you entered had the desiredaffect in the server. Use the QUERY ACTLOGcommand to see if a server error condition (like out ofmemory) occurred prior to the command. Resolve theerror if it is found. Contact your service representativeif you cannot resolve the error, or if an error is notfound.

ANR0548W Retrieve or restore failed for sessionsession number for node node name (clientplatform) processing file space filespacefilespace id for file file name stored asstorage repository - data integrity errordetected.

Explanation: The server ends a file retrieval operationfor the specified session because an internal databaseintegrity error has been encountered on the server.


User Response: Re-try the restore or retrieve operationand if the file is also backed up in a copy storage pool,the operation will attempt to read the file from thealternate location.

ANR0549W Transaction failed for session sessionnumber for node node name (clientplatform) - no existing restore sessionfound.

Explanation: A client attempted to start an additionalno query restore session to increase restore throughput,but the original restore session was not found.


User Response: Check the status of the originalrestore. It may have already completed or beencancelled. The QUERY SESSION command and theQUERY RESTORE commands can provide informationabout existing sessions and restore sessions which arerestartable.

ANR0550E The client operation failed for sessionsession number for node node name (clientplatform) - see previous error messages.

Explanation: The indicated operation has failed. Thismessage is always preceded by one or more other error



messages which provide more detail about why thecommand failed.


User Response: Examine the previous error messagesto determine the source of the error. Use the QUERYACTLOG command to view the activity log and searchfor messages if needed. Correct the problem and try thecommand again.

ANR0551E The client operation failed for sessionsession number for node node name (clientplatform) - lock conflict.

Explanation: An operation that requires the server tolock a system resource has been initiated. The operationcannot be executed because the resource is already inuse by another command or process.

System Action: The server does not process thecommand.

User Response: Try the command again at a latertime.

ANR0552E Client operation failed for sessionsession number for node node name (clientplatform) - destination storage poolstorage pool was skipped.

Explanation: The indicated client operation failedbecause the destination storage pool was skipped. Astorage pool may be skipped because it does not haveenough available space, or because it has a MAXSIZEvalue that is less than the size of the object to beinserted.


User Response: Ensure that the destination storagepool is available, has an adequate MAXSIZE setting,and has adequate space. The MAXSIZE setting may bechanged using the UPDATE STGPOOL command.Space may be added to the storage pool by checking inscratch volumes or defining new volumes in thestorage pool. If volumes in the destination storage poolare offline, use the VARY ONLINE command to varythem online and make them available for use. Correctthe problem and try the command again.

ANR0553E Client operation failed for sessionsession number - Administratoradministrator name does not haveadequate authority over node node name.

Explanation: The specified administrator does nothave the proper authority necessary to perform thisoperation on the specified node.

System Action: The server does not perform thequery.

User Response: Issue the command from a properlyauthorized administrator ID, or contact the systemadministrator to have additional authority granted tothe current administrator ID.

ANR0554E command name: The parameter nameparameter is only valid if theTOSERVER parameter is specified.

Explanation: The command failed because theTOSERVER parameter was not specified.

System Action: The command fails and serveroperation continues.

User Response: Reissue the command and specify theTOSERVER parameter. For information on valid valuesfor the command parameter,refer to the :cit.ADSMAdministrator’s Reference:ecit. for your particularplatform.

ANR0555E command name: The parameter nameparameter cannot be specified when theTOSERVER parameter is specified.

Explanation: The command failed because theTOSERVER parameter was not specified.


User Response: Reissue the command and omit theTOSERVER parameter. For information on valid valuesfor the parameter for the command parameter, refer tothe :cit.ADSM Administrator’s Reference:ecit. for yourparticular platform.

ANR0556E command name: DATES=RELATIVEparameter value cannot be specifiedwhen merging imported files using theMERGE=YES parameter value.

Explanation: When importing files and merging theminto existing file spaces, the DATES=RELATIVEparameter value cannnot be specified.


User Response: Reissue the command and omit theDATES=RELATIVE parameter. For information on validvalues for the parameter for the command, refer to the:cit.ADSM Administrator’s Reference:ecit. for yourparticular platform.

ANR0557I Import command: An invalid exportrecord (version version, copy type copytype, object type object type) was found.

Explanation: An invalid import record was found forthe specified version, copy type and object type. Theobject will be skipped, and import processing willcontinue.




User Response: Issue QUERY ACTLOG to determinethe source of the error.

ANR0566W Retrieve or restore failed for sessionsession number for node node name (clientplatform) - file was deleted from datastorage during retrieval.

Explanation: The server ends a file retrieval operationfor the specified session because the file has beendeleted from data storage by another process beforeretrieval is complete.


User Response: Contact your administrator to findout if DELETE FILESPACE, DELETE VOLUME, orinventory expiration processes are running; theseprocesses can delete data storage files during retrieval.Reissue the restore or retrieve operation and specify adifferent file version.

ANR0567W Retrieve or restored failed for sessionsession number for node node name (clientplatform) - insufficient mount pointsavailable to satisfy the request.

Explanation: The server was unable to allocatesufficient mount points to process the retrieve orrestore operation.



ANR0568W Session session number for admin adminname (client platform) terminated -connection with client severed.

Explanation: The specified admin session is endedbecause the communications link has been closed by anetwork error or by the client program.


User Response: If a user breaks out of a clientprogram, this message will be displayed on the serveras the connection is suddenly closed by the client. Anetwork failure can also cause this message to bedisplayed. If a large number of these messages occursimultaneously, check the network for failure andcorrect any problems.

ANR0569I Object not processed for node name:type=type, file space=filespace name,object=object name.

Explanation: An error occurred. The object for nodename, identified by type, file space and object name wasnot processed.

System Action: Server action is defined by the errorthat occurred.

User Response: Issue QUERY ACTLOG to determinethe source of the error.

ANR0570E Export command: Invalid value forDURUNITS parameter detected whileexporting administrative scheduleschedule name - default or existing valueis used during import.

Explanation: During processing of command exportcommand, an invalid value is encountered for theDURUNITS parameter for administrative scheduleschedule name.

System Action: Export processing continues, but theexported data contains an unknown DURUNITS valuefor this schedule. If this data is imported, the serveruses the default or existing DURUNITS value.

User Response: Update the DURUNITS value for thisschedule and restart the export command. Alternatively,the export data with the unknown value can be used,and the DURUNITS value can be checked and updatedafter import processing has been performed.

ANR0571E Export command: Invalid value forPERUNITS parameter detected whileexporting administrative scheduleschedule name - default or existing valueis used during import.

Explanation: During processing of command exportcommand, an invalid value is encountered for thePERUNITS parameter for administrative scheduleschedule name.

System Action: Export processing continues, but theexported data will contain an unknown PERUNITSvalue for this schedule. If this data is imported, theserver uses the default or existing PERUNITS value.

User Response: Update the PERUNITS value for thisschedule and restart the export command. Alternatively,use the export data with the unknown value, and checkand update the PERUNITS value after importprocessing has been performed.



ANR0572E Export command: Invalid value forDAYOFWEEK parameter detected whileexporting administrative scheduleschedule name - default or existing valueis used during import.

Explanation: During processing of command exportcommand, an invalid value is encountered for theDAYOFWEEK parameter for administrative scheduleschedule name.

System Action: Export processing continues, but theexported data contains an unknown DAYOFWEEKvalue for this schedule. If this data is imported, theserver uses the default or existing DAYOFWEEK value.

User Response: Update the DAYOFWEEK value forthis schedule and restart the export command.Alternatively, use the export data with the unknownvalue, and check and update the DAYOFWEEK valueafter import processing has been performed.

ANR0573I Export/import command: Processingadministrative schedule schedule name.

Explanation: The background export or importprocess to service the command export/import commandis currently processing the schedule definitioninformation for administrative schedule schedule name.

System Action: Export or import processing for thecommand continues.


ANR0574E Import command: Invalid value forDURUNITS or PERUNITS parameter inexported data for administrativeschedule schedule name.

Explanation: During preview processing of commandimport command, an invalid value is encountered for theDURUNITS or PERUNITS parameter for administrativeschedule schedule name.

System Action: Processing of the command continues.If a later command is issued that causes the data to beimported, the default or existing values are used forDURATION, DURUNITS, PERIOD, and PERUNITS.

User Response: If the data is imported with a latercommand, verify that the correct values forDURATION, DURUNITS, PERIOD, and PERUNITS areused for this schedule.

ANR0575E Import command: Invalid value forDAYOFWEEK parameter in exporteddata for administrative schedule schedulename.

Explanation: During preview processing of commandimport command, an invalid value is encountered for theDAYOFWEEK parameter for administrative scheduleschedule name.

System Action: Processing of the command continues.If a later command is issued that causes the data to beimported, the default or existing DAYOFWEEK value isused.

User Response: If the data is imported with a latercommand, verify that the correct DAYOFWEEK value isused for this schedule.

ANR0576E Import command: Invalid value forDURUNITS or PERUNITS parameter inexported data - administrative scheduleschedule name defined with defaultvalues for DURATION, DURUNITS,PERIOD, and PERUNITS.

Explanation: During processing of command importcommand, an invalid value is encountered for theDURUNITS or PERUNITS parameter for administrativeschedule schedule name.

System Action: Processing of the command continues,by using the default values for DURATION,DURUNITS, PERIOD, and PERUNITS.

User Response: Verify that the correct values havebeen used for DURATION, DURUNITS, PERIOD, andPERUNITS. Update these values, if necessary.

ANR0577E Import command: Invalid value forDAYOFWEEK parameter in exporteddata - administrative schedule schedulename defined with default DAYOFWEEKvalue.

Explanation: During processing of command importcommand, an invalid value is encountered for theDAYOFWEEK parameter for administrative scheduleschedule name.

System Action: Processing of the command continues,by using the default DAYOFWEEK value for thisschedule.

User Response: Verify that the correct DAYOFWEEKvalue has been used for this schedule. Update thisvalue, if necessary.

ANR0578E Import command: Invalid value forDURUNITS or PERUNITS parameter inexported data - existing values forDURATION, DURUNITS PERIOD, andPERUNITS for administrative scheduleschedule name were not updated.

Explanation: During processing of command importcommand, an invalid value is encountered for theDURUNITS or PERUNITS parameter for administrativeschedule schedule name.

System Action: Processing of the command continues,by using the existing values for DURATION,DURUNITS, PERIOD, and PERUNITS.




ANR0579E Import command: Invalid value forDAYOFWEEK parameter in exporteddata - existing DAYOFWEEK value foradministrative schedule schedule namewas not updated.

Explanation: During processing of command importcommand, an invalid value is encountered for theDAYOFWEEK parameter for administrative scheduleschedule name.

System Action: Processing of the command continues,by using the existing DAYOFWEEK value for thisschedule.


ANR0580E Export command: Invalid value forSPACEMGTECHNIQUE parameterdetected while exporting managementclass management class name in domaindomain name, set policy set name - defaultor existing value is used during import.

Explanation: During processing of command exportcommand, an invalid value is encountered for theSPACEMGTECHNIQUE parameter for managementclass management class name in domain domain name,policy set policy set name.

System Action: Export processing continues, but theexported data contains an unknownSPACEMGTECHNIQUE value for this managementclass. If this data is imported, the default or existingSPACEMGTECHNIQUE value is used.

User Response: Update the SPACEMGTECHNIQUEvalue for this copy group and restart the export.Alternatively, use the export data with the unknownvalue, and check and update theSPACEMGTECHNIQUE value after import processinghas been performed.

ANR0581E Export command: Invalid value forMIGREQUIRESBKUP parameterdetected while exporting managementclass management class name in domaindomain name, set policy set name - defaultor existing value is used during import.

Explanation: During processing of command exportcommand, an invalid value is encountered for theMIGREQUIRESBKUP parameter for management classmanagement class name in domain domain name, policyset policy set name.

System Action: Export processing continues, but the

exported data contains an unknown value for thismanagement class. If this data is imported, the defaultor existing MIGREQUIRESBKUP value is used.

User Response: Update the MIGREQUIRESBKUPvalue for this copy group and restart the export.Alternatively, use the export data with the unknownvalue, and check and update the MIGREQUIRESBKUPvalue after import processing has been performed.

ANR0582E Import command: Invalid value forSPACEMGTECHNIQUE parameter inexported data for management classmanagement class name in domain domainname, set policy set name.

Explanation: During preview processing of commandimport command, an invalid value is encountered for theSPACEMGTECHNIQUE parameter for managementclass management class name, in policy domain domainname, policy set policy set name.

System Action: Processing of the command continues.If a later command is issued that causes the data to beimported, the default or existingSPACEMGTECHNIQUE value is used.

User Response: None. If the data is imported with alater command, verify that the correctSPACEMGTECHNIQUE value is used for thismanagement class.

ANR0583E Import command: Invalid value forSPACEMGTECHNIQUE parameter inexported data - management classmanagement class name in domain domainname, set policy set name defined withdefault SPACEMGTECHNIQUE value.

Explanation: During processing of command importcommand, an invalid value is encountered for theSPACEMGTECHNIQUE parameter for managementclass management class name, in policy domain domainname, policy set policy set name.

System Action: Processing of the command continues,by using the default SPACEMGTECHNIQUE value forthis management class.

User Response: Verify that the correctSPACEMGTECHNIQUE value has been used for thismanagement class. Update this value, if necessary.

ANR0584E Import command: Invalid value forSPACEMGTECHNIQUE parameter inexported data - SPACEMGTECHNIQUEvalue for management class managementclass name in domain domain name, setpolicy set name was not updated.

Explanation: During processing of command importcommand, an invalid value is encountered for theSPACEMGTECHNIQUE parameter for management



class management class name, in policy domain domainname, policy set policy set name.

System Action: Processing of the command continues,by using the existing SPACEMGTECHNIQUE value forthis management class.

User Response: Verify that the correctSPACEMGTECHNIQUE value has been used for thismanagement class. Update this value, if necessary.

ANR0585E Import command: Invalid value forMIGREQUIRESBKUP parameter inexported data for management classmanagement class name in domain domainname, set policy set name.

Explanation: During preview processing of commandimport command, an invalid value is encountered for theMIGREQUIRESBKUP parameter for management classmanagement class name, in policy domain domain name,policy set policy set name.

System Action: Processing of the command continues.If a later command causes the data to be imported, thedefault or existing MIGREQUIRESBKUP value is used.

User Response: None. If the data is imported with alater command, verify that the correctMIGREQUIRESBKUP value is used for thismanagement class.

ANR0586E Import command: Invalid value forMIGREQUIRESBKUP parameter inexported data - management classmanagement class name in domain domainname, set policy set name defined withdefault MIGREQUIRESBKUP value.

Explanation: During processing of command importcommand, an invalid value is encountered for theMIGREQUIRESBKUP parameter for management classmanagement class name, in policy domain domain name,policy set policy set name.

System Action: Processing of the command continues,by using the default MIGREQUIRESBKUP value forthis management class.

User Response: Verify that the correctMIGREQUIRESBKUP value has been used for thismanagement class. Update this value, if necessary.

ANR0587E Import command: Invalid value forMIGREQUIRESBKUP parameter inexported data - MIGREQUIRESBKUPvalue for management class managementclass name in domain domain name, setpolicy set name was not updated.

Explanation: During processing of command importcommand, an invalid value is encountered for theMIGREQUIRESBKUP parameter.

System Action: Processing of the command continues,by using the existing MIGREQUIRESBKUP value forthis management class.

User Response: Verify that the correctMIGREQUIRESBKUP parameter has been used for thismanagement class. Update this value, if necessary.

ANR0588E Import command: Server is down-levelcompared to export data version versionnumber.

Explanation: An attempt is made to import data to adown-level server. The server on which the import isperformed must be at the same or later level than theserver from which the data was exported.

System Action: The import process ends and serveroperation continues.

User Response: Import to a server that is at the sameor later level than the server from which the exportwas performed.

ANR0589E Import command: Preview processingterminated abnormally - server isdown-level.

Explanation: Processing for the command importcommand in preview mode ends when it is determinedthat the server is down-level compared to the exportdata.

System Action: Import processing ends and serveroperation continues.


ANR0590E Import command: Processing terminatedabnormally - server is down-level.

Explanation: Processing for the command importcommand ends when it is determined that the server isdown-level compared to the export data.



ANR0591E Export/import command: Invalid value forFILELIST parameter - parameter value.

Explanation: The value (parameter value) specified forthe FILELIST parameter in command export/importcommand is not a valid value for this parameter.


User Response: Reissue the command and specify a



valid FILELIST parameter. For information on validvalues for the FILELIST parameter for the command,refer to the Administrator’s Reference for your particularplatform.

ANR0592E Export/import command: Invalid value fortable of contents parameter - parametervalue.

Explanation: The value (parameter value) specified forthe table of contents (TOC) parameter in commandexport/import command is not a valid value for thisparameter.


User Response: Reissue the command and specify avalid TOC parameter. For information on valid valuesfor the TOC parameter for the command, refer to theAdministrator’s Reference for your particular platform.

ANR0593E Export/import command: Invalid value forNOSPAN parameter - parameter value.

Explanation: The value (parameter value) specified forthe NOSPAN parameter in command export/importcommand is not a valid value for this parameter.


User Response: Reissue the command and specify avalid NOSPAN parameter. For information on validvalues for the NOSPAN parameter for the command,refer to the Administrator’s Reference for your particularplatform.

ANR0594E device class: NOSPAN parameter can onlybe used with a 3590 device class.

Explanation: The device class specified must be a 3590device class when NOSPAN is set to True.


User Response: Reissue the command and specify avalid NOSPAN/Device Class parameter. Forinformation on valid values for the NOSPAN parameterfor the command, refer to the Administrator’s Referencefor your particular platform.

ANR0595W The server deleted object count objectsthat were part of incomplete groups.

Explanation: After importing data that was exportedfrom another server, the server deletes any objects thatare part of incomplete groups. Incomplete groups maybe a result of importing from media written by anexport operation that failed. Incomplete groups mayalso be a result of a failed import operation.


User Response: Ensure that the export and importoperations run to completion. If any errors areobserved, correct them and re-run the export or importor both, as needed.

ANR0596W Space-managed object object name forclient node node name, filespace filespacename already exists on the server - it willbe skipped.

Explanation: While attempting to import aspaced-managed object, the server discovers that theobject already exists. The space-managed object isskipped.



ANR0597W IMPORT: Space management attributesin management class management classname for domain domain name is notdefined - default management class willbe used.

Explanation: During import processing, the serverfinds that the space management attributes for aspace-managed file being imported does not exist inthe active policy set for the domain to which the nodeis assigned.

System Action: The default management class for thenode’s policy domain is bound to the space-managedfile and import processing continues.

User Response: If you want to define the missingmanagement class, an authorized administrator maycancel the import operation, define the missing spacemanagement attributes or management class for thedomain, and process the import operation again.

ANR0598W IMPORT: Space management attributesnot found for default management classin domain domain name - space managedfiles bound to management classmanagement class name in this domaincannot be imported.

Explanation: During import processing, the serverfinds that a management class bound to aspace-managed file being imported does not exist inthe active policy set for the domain to which the nodeis assigned. When trying to rebind the space-managedfile to the default management class for the domain,the server finds that the space-managed attributes arenot defined for the default management class.

System Action: The file is not imported; importprocessing continues.

User Response: If you want to define the missingcopy group, an authorized administrator may cancelthe import operation, define the missing spacemanagement attributes or management class for the



domain, and process the import operation again.

ANR0599E Export/import command: Invalid volumename volume name specified for deviceclass device class name.

Explanation: One of the volume names specified inthe VOLUMENAMES parameter for an import orexport command is not a valid volume name for thedevice class specified in the DEVCLASS parameter.

System Action: The export or import command fails.

User Response: Specify volume names in theVOLUMENAMES parameter that are valid for thedevice class specified in the DEVCLASS parameter.

ANR0600I Export command: No matching policydomains found for exporting.

Explanation: The background export process does notfind any policy domains that match the specificationentered in the export command.

System Action: The export process continues and nopolicy domains are exported from the server.


ANR0601I Export command: No policy sets found inpolicy domain domain name forexporting.

Explanation: The background export process does notfind any policy sets defined in domains matchingdomain name.

System Action: The export process continues and nopolicy sets are exported from the domain.


ANR0602I Export command: No management classeswere found in policy domain domainname for exporting.

Explanation: The background export process does notfind any management classes defined in policydomains matching domain name.

System Action: The export process continues and nomanagement classes are exported from the domain.


ANR0603I Export command: No copy groups werefound in policy domain domain name forexporting.

Explanation: The background export process does notfind any copy groups defined in policy domainsmatching domain name.

System Action: The export process continues and nocopy groups are exported from the domain.


ANR0604I Export command: No schedules werefound in policy domain domain name forexporting.

Explanation: The background export process does notfind any schedules defined for policy domainsmatching domain name.

System Action: The export process continues and noschedules are exported for the domain.


ANR0605I Export command: No scheduleassociations were found in policydomain domain name for exporting.

Explanation: The background export process does notfind any schedule node associations defined for policydomains matching domain name.

System Action: The export process continues and noschedule associations are exported for the domain.


ANR0606I Export command: No node definitionswere found for exporting.

Explanation: The background export process does notfind any node definitions to export as specified in thecommand export command.

System Action: The export process continues.


ANR0607I Export command: No administratordefinitions were found for exporting.

Explanation: The background export process does notfind any administrator definitions to export as specifiedin the command export command.



ANR0608I Export command: No file spaces werefound for exporting.

Explanation: The background export process does notfind any file space definitions to export as specified inthe command export command.





ANR0609I Command started as process process ID.

Explanation: A background process has been startedto service the command command. The backgroundprocess is defined as process process ID.


User Response: To query the progress of thebackground process, use the QUERY PROCESScommand. To cancel the background process, use theCANCEL PROCESS command. Use the process IDnumber to specify this specific process.

ANR0610I Command started by administrator name asprocess process ID.

Explanation: A background process has started toservice the command command entered by administratoradministrator name. The background process is definedas process process ID.


User Response: To query the progress of thebackground process, use the QUERY PROCESScommand. To cancel the background process, use theCANCEL PROCESS command. Use the process IDnumber to specify this specific process.

ANR0611I Command started by administrator name asprocess process ID has ended.

Explanation: The background process to service thecommand command by administrator administrator namehas completed processing.

System Action: The specified process ends, and serveroperation continues.


ANR0612I Import command: Reading EXPORTSERVER data from server server nameexported export date export time.

Explanation: The background import process toservice the command import command is importinginformation exported from server server name with theEXPORT SERVER command on export date at exporttime.

System Action: Import processing continues.


ANR0613I Import command: Reading EXPORTPOLICY data from server server nameexported export date export time.

Explanation: The background import process toservice the command import command is importinginformation exported from server server name with the

EXPORT POLICY command on export date at exporttime.



ANR0614I Import command: Reading EXPORTADMIN data from server server nameexported export date export time.

Explanation: The background import process toservice the command import command is importinginformation exported from server server name with theEXPORT ADMIN command on export date at exporttime.



ANR0615I Import command: Reading EXPORTNODE data from server server nameexported export date export time.

Explanation: The background import process toservice the command import command is importinginformation exported from server server name with theEXPORT NODE command on export date at export time.



ANR0616I Export/import command: Previewprocessing completed successfully.

Explanation: The background export or importprocess to service the command export/import commandin preview (Preview=Yes) mode has completedsuccessfully.

System Action: Export or import processing for thecommand completes. Statistics on the projected numberand type of objects moved, together with the projectedtotal number of bytes copied, are displayed on theserver console following this message.


ANR0617I Export/import command: Processingcompleted with status status.

Explanation: The background export or importprocess to service the command export/import commandhas completed with status status. If the status isINCOMPLETE, some files have been skipped due toerrors reading or writing the file.

System Action: Export or import processing for thecommand completes. Statistics on the number and typeof objects moved, together with the total number ofbytes copied, are displayed on the server consolefollowing this message. A summary of the number offiles that were skipped is also displayed.




ANR0618I Export/import command: Previewprocessing canceled before completion.

Explanation: The background export or importprocess to service the command export/import commandin preview (Preview=Yes) mode has been canceled withthe CANCEL PROCESS command.

System Action: Export or import processing for thecommand ends. Statistics on the projected number andtype of objects moved, together with the projected totalnumber of bytes copied, are displayed on the serverconsole following this message.


ANR0619I Command: Processing canceled beforecompletion.

Explanation: The background process to service thecommand command has been canceled with theCANCEL PROCESS command.

System Action: Processing for the command commandends. Statistics on the number and type of objectsmoved, together with the total number of bytes copied,are displayed on the server console following thismessage.


ANR0620I Export/import command: Copied numberdomain(s).

Explanation: The background export or importprocess to service the command export/import commandcopies number policy domain definitions from theserver database to export media or from export mediainto the server database. Data is not actually moved ifPreview=Yes is specified in the command export/importcommand.

System Action: Export or import processing for thecommand completes. Server operation continues.


ANR0621I Export/import command: Copied numberpolicy sets.

Explanation: The background export or importprocess to service the command export/import commandcopies number policy set definitions from the serverdatabase to export media or from export media into theserver database. Data is not actually moved ifPreview=Yes is specified in the command export/importcommand.



ANR0622I Export/import command: Copied numbermanagement classes.

Explanation: The background export or importprocess to service the command export/import commandcopies number management class definitions from theserver database to export media or from export mediainto the server database. Data is not moved ifPreview=Yes is specified in the command export/importcommand.



ANR0623I Export/import command: Copied numbercopy groups.

Explanation: The background export or importprocess to service the command export/import commandcopies number copy group definitions from either theserver database to export media or from export mediainto the server database. Data is not moved ifPreview=Yes is specified in the command export/importcommand.



ANR0624I Export/import command: Copied numberschedules.

Explanation: The background export or importprocess to service the command export/import commandcopies number schedule definitions from either theserver database to export media or from export mediainto the server database. Data is not moved ifPreview=Yes is specified in the command export/importcommand.



ANR0625I Export/import command: Copied numberadministrators.

Explanation: The background export or importprocess to service the command export/import commandcopies number administrator definitions from either theserver database to export media or from export mediainto the server database. Data is not moved ifPreview=Yes is specified in the command export/importcommand.





ANR0626I Export/import command: Copied numbernode definitions.

Explanation: The background export or importprocess to service the command export/import commandcopies number client node definitions from the serverdatabase to export media or from export media into theserver database. Data is not moved if Preview=Yes isspecified in the command export/import command.



ANR0627I Export/import command: Copied filespacenumber file spaces archive number archivefiles, backup number backup files, andspacemg number space managed files.

Explanation: The background export or importprocess to service the command export/import commandcopies filespace number client file space definitions,archive number archive file copies, backup number backupfile copies, and spacemg number space-managed filesfrom either the server database to export media or fromimport media into the server database. Data is notactually moved if Preview=Yes is specified in thecommand export/import command.



ANR0629I Export/import command: Copied numberbytes of data.

Explanation: The background export or importprocess to service the command export/import commandcopies number bytes of data from the server databaseand data storage to the export media or from theexport media to the server database and data storage.Data is not moved if Preview=Yes is specified in thecommand export/import command. This figure can beused during export preview processing to estimate thenumber of removable media volumes needed to holdthe exported information from the server.



ANR0630I Export/import command: Copied numberkilobytes of data.

Explanation: The background export or importprocess to service the command export/import commandcopies number kilobytes of data from the serverdatabase and data storage to the export media or fromthe export media to the server database and datastorage. This figure can be used during export previewprocessing to estimate the number of removable media

volumes needed to hold the exported information fromthe server.



ANR0631I Export/import command: Copied numbermegabytes of data.

Explanation: The background export or importprocess to service the command export/import commandcopies number megabytes of data from the serverdatabase and data storage to the export media or fromthe export media to the server database and datastorage. This figure can be used during export previewprocessing to estimate the number of removable mediavolumes needed to hold the exported information fromthe server.



ANR0632I Export/import command: Copied numbergigabytes of data.

Explanation: The background export or importprocess to service the command export/import commandcopies number gigabytes of data from the serverdatabase and data storage to the export media or fromthe export media to the server database and datastorage. This figure can be used during export previewprocessing to estimate the number of removable mediavolumes needed to hold the exported information fromthe server.



ANR0633I Export/import command: Copied numberterabytes of data.

Explanation: The background export or importprocess to service the command export/import commandcopies number terabytes of data from the serverdatabase and data storage to the export media or fromthe export media to the server database and datastorage. This figure can be used during export previewprocessing to estimate the number of removable mediavolumes needed to hold the exported information fromthe server.





ANR0634I Export/import command: Detected numbererrors.

Explanation: The background export or importprocess to service the command export/import commanddetects number errors while copying information fromthe server database and data storage to the exportmedia or from the export media to the server databaseand data storage.


User Response: Examine the server messages issuedprior to this message to view the error. Use the QUERYACTLOG command to view the activity log and searchfor messages.

ANR0635I Export/import command: Processing nodenode name in domain domain name.

Explanation: The background export or importprocess to service the command export/import commandis currently processing the client node definitioninformation for node node name. The node will beimported to domain domain name.



ANR0636I Import command: Processing file spacefilespace name for node node name as filespace new filespace name.

Explanation: The background import process toservice the command import command is currentlyprocessing the client file space definition informationfor file space filespace name belonging to client nodenode name. The file space is imported under the namenew filespace name. During import processing, file spacesdefined for clients are not replaced, and file copyinformation in the file spaces are imported to new filespace names so that client file copies are not mixedwith existing definitions. Import processing can thencreate file spaces with names generated by the importprocessor for client nodes that existed prior to theimport operation.

System Action: Import processing for the commandcontinues.

User Response: None; however, clients may want toexamine the contents of the file space with the namenew filespace name so that they know where certain filecopies are kept.

ANR0637I Export/import command: Processing filespace filespace name for node node namefsId filespace id .

Explanation: The background export or importprocess to service the command export/import command

is currently processing client node file spaceinformation for file space filespace name belonging toclient node node name.



ANR0638I Export/import command: Processingadministrator administrator name.

Explanation: The background export or importprocess to service the command export/import commandis currently processing the administrator definitioninformation for administrator administrator name.



ANR0639I Export/import command: Processingdomain domain name.

Explanation: The background export or importprocess to service the command export/import commandis currently processing the policy domain definitioninformation for domain domain name.



ANR0640I Export/import command: Processing policyset set name in policy domain domainname.

Explanation: The background export or importprocess to service the command export/import commandis currently processing the policy set definitioninformation for policy set set name belonging to policydomain domain name.



ANR0641I Export/import command: Processingmanagement class class name in domaindomain name, set set name.

Explanation: The background export or importprocess to service the command export/import commandis currently processing the management class definitioninformation for management class class name belongingto policy set set name in policy domain domain name.





ANR0642I Export/import command: Processingbackup copy group in domain domainname, set set name, management classclass name.

Explanation: The background export or importprocess to service the command export/import commandis currently processing the backup copy groupdefinition information for management class class namebelonging to policy set set name in policy domaindomain name.



ANR0643I Export/import command: Processingarchive copy group in domain domainname, set set name, management classclass name.

Explanation: The background export process toservice the command export/import command is currentlyprocessing the archive copy group definitioninformation for management class class name belongingto policy set set name in policy domain domain name.

System Action: Export processing for the commandcontinues.


ANR0644I Export command: Processing copy groupof unknown type in domain domainname, set set name, management classclass name.

Explanation: The background export or importprocess to service the command export command iscurrently processing copy group definition informationfor management class class name belonging to policy setset name in policy domain domain name. The type ofcopy group being processed is unknown.

System Action: Export or import processing for thecommand continues. The import or export processassumes that the copy group is a backup copy group.

User Response: After policy definitions are imported,use the QUERY MGMTCLASS and QUERYCOPYGROUP commands to query the serverdefinitions for management class class name to ensurethat the copy groups defined have the desiredattributes and types. Alternatively, the copy group canbe deleted and defined with the correct type, and thenthe export command can be issued again.

ANR0645I Export/import command: Processingschedule schedule name in domain domainname.

Explanation: The background export or importprocess to service the command export/import command

is currently processing the schedule definitioninformation for schedule schedule name belonging topolicy domain domain name.



ANR0646I Export/import command: message

Explanation: The background export or importprocess to service the command export/import commandhas received the message message from the server.

System Action: Export or import processing for thecommand continues, but errors may have beenencountered.

User Response: Examine the documentation for themessage message and resolve the problem reported.

ANR0647I Cancel in progress

Explanation: The export or import operation has beencanceled and will end when resources have been freedfor the background process. This message may bedisplayed in response to a QUERY PROCESS commandfor an export or import operation.



ANR0648I Have copied the following:

Explanation: The export or import operation hascopied the number and types of objects displayed. Thismessage may be displayed in response to a QUERYPROCESS command for an export or import operation.



ANR0649I Import command: Domain domain namedoes not exist - the system will attemptto import node node name to domainSTANDARD.

Explanation: The background import process toservice the command import command is currentlyprocessing client node node name. This node wasassigned to domain domain name at the time of export.However, domain domain name does not exist on theserver to which the import is being performed.

System Action: Import processing continues, but nodenode name will be assigned to domain STANDARDduring import unless one of the following conditionsexist:v Preview=Yesv Node node name is already registered and

Replacedefs=Nov Domain STANDARD does not exist



User Response: If Preview=Yes, consider definingdomain domain name before nodes are actuallyimported. Otherwise, domain domain name can becreated after the node is imported and the UPDATENODE command can be used to assign the node todomain domain name.

ANR0650W IMPORT: Archive copygroup copy groupname in management class managementclass name for domain domain name is notdefined, default management class willbe used.

Explanation: During import processing, the serverfinds that a management class or copy group bound toan archive file being imported does not exist in theactive policy set for the domain to which the node isassigned.

System Action: The default management class for thenode’s policy domain is bound to the archive file andimport processing continues.

User Response: If you want to define the missingmanagement class, an authorized administrator maycancel the import operation, define the missingmanagement class or copy group for the domain, andprocess the import operation again.

ANR0651W IMPORT: Backup copygroup copy groupname in management class managementclass name for domain domain name is notdefined, default management class willbe used.

Explanation: During import processing, the serverfinds that a management class or copy group bound toa backup file being imported does not exist in theactive policy set for the domain to which the node isassigned.

System Action: The default management class for thenode’s policy domain is bound to the backup file copyand import processing continues.

User Response: If you want to define the missingmanagement class, an authorized administrator maycancel the import operation, define the missingmanagement class or copy group for the domain, andprocess the import operation again.

ANR0652W IMPORT: Archive copygroup not foundfor default management class in domaindomain name - archive files bound tomanagement class management class namein this domain cannot be imported.

Explanation: During import processing, the serverfinds that a management class or copy group bound toan archive file being imported does not exist in theactive policy set for the domain to which the node isassigned. When trying to rebind the archive file to thedefault management class for the domain, the server

finds that an archive copy group is not defined for thedefault management class.


User Response: If you want to define the missingcopy group, an authorized administrator may cancelthe import operation, define the missing managementclass or copy group for the domain, and process theimport operation again.

ANR0653W IMPORT: Backup copygroup not foundfor default management class in domaindomain name - backup files bound tomanagement class management class namein this domain cannot be imported.

Explanation: During import processing, the serverfinds that a management class or copy group bound toa backup file being imported does not exist in theactive policy set for the domain to which the node isassigned. When trying to rebind the backup file to thedefault management class for the domain, the serverfinds that a backup copy group is not defined for thedefault management class.


User Response: If you want to define the missingcopy group, an authorized administrator may cancelthe import operation, define the missing managementclass or copy group for the domain, and process theimport operation again.

ANR0655W Command: Retrieve or restore failed - filewas deleted from data storage duringretrieval.

Explanation: The server ends a file retrieval operationfor the specified command because the file has beendeleted from data storage by another process beforeretrieval is complete.

System Action: The server ends the command andcontinues operation.

User Response: Contact your administrator to findout if DELETE FILESPACE, DELETE VOLUME, orinventory expiration processes are running; theseprocesses can delete data storage files during retrieval.Reissue the command after these processes have beencompleted or canceled.

ANR0656W Export/import command: Skipped archivenumber archive files, backup numberbackup files, and spacemg number spacemanaged files.

Explanation: The background export or importprocess to service the command export/import commandskipped archive number archive file copies, backupnumber backup file copies, and spacemg number



space-managed files from either the server database toexport media or from import media into the serverdatabase. Data is not actually moved if Preview=Yes isspecified in the command export/import command.


User Response: Check previous messages for thenames of the files that were not exported or imported,and problem determination information.

ANR0657W Export command: Invalid authorizationrule type rule type encountered for filespace filespace name fsId filespace id innode node name - both backup andarchive will be assumed during import.

Explanation: During import processing, the serverencounters an invalid file space authorization rule typefor the indicated file space and node.


User Response: After import processing is completed,ask the user of node node name to query the access rulesand ensure that they are specified as desired. The usershould correct any rules that grant access to objects thatthe user does not want others to access.

ANR0658W Export command: The password foradministrator administrator name couldnot be obtained. The value ’passwordvalue’ will be assumed: The systemadministrator may wish to change thispassword after importing administratoradministrator name.

Explanation: During processing of command exportcommand, the export processor cannot obtain thepassword for administrator administrator name. Thevalue password value is assigned as the password for theadministrator on the export media.

System Action: Processing of the command continues.

User Response: After the administrative definition hasbeen imported to another server, an authorizedadministrator should use the UPDATE ADMINcommand to set a password for the administratoradministrator name.

ANR0659W Export command: The password for nodenode name could not be obtained. Thevalue ’password value’ will be assumed:The system administrator may wish tochange this password after importingnode node name.

Explanation: During processing of command exportcommand, the export processor cannot obtain thepassword for client node node name. The value passwordvalue is assigned as the password for the client node onthe export media.

System Action: Processing of the command continues.

User Response: After the client node definition hasbeen imported to another server, an authorizedadministrator should use the UPDATE NODEcommand to set a password for the node node name.

ANR0660E Command: Insufficient memory availablein accessing data storage.

Explanation: The server encounters a memoryshortage in accessing data storage during commandcommand operation.

System Action: The command command operationends and server operation continues.


ANR0661E Command: Internal error encountered inaccessing data storage.

Explanation: The server encounters an internal errorin accessing data storage while processing commandcommand operation.

System Action: The command command operation isended and server operation continues.

User Response: Use the QUERY ACTLOG commandto examine messages prior to this error to determinethe cause of the data storage failure. If the failure canbe found and resolved, reissue the command commandoperation. If the failure cannot be found, contact yourservice representative for assistance in resolving theproblem.

ANR0662E Command: Output error encountered inaccessing data storage.

Explanation: The command command operation endsbecause an error has been encountered by the server inwriting to a device. Possible reasons include:

v I/O error writing to a device

v No storage space.

v Incompatible storage pool data format.


User Response: Query the activity log to findmessages preceding this one to determine the cause ofthe error. After the problem is corrected, the commandcan be retried.



ANR0663E Command: Data transfer was interruptedin accessing data storage.

Explanation: The database transaction associated withcommand command operation failed because datatransfer to or from data storage was interrupted by anexternal event.


User Response: Examine the messages issued prior tothis message to determine why the data transfer wasinterrupted. Reissue the command command after theproblem is resolved.

ANR0664E Export/import command: Media notaccessible in accessing data storage.

Explanation: The server ends a transaction for anexport or import operation because storage volumes arenot available in the storage pools in which the clientfiles are to be stored.

System Action: The server ends the export or importoperation and server operation continues.

User Response: An authorized administrator can issuethe DEFINE VOLUME command to add storage to oneor more storage pools in the storage hierarchy. TheVARY ONLINE command can be used to vary offlinestorage volumes online in the storage hierarchy tomake them available for file storage.

ANR0665W Import command: Transaction failed -storage pool pool name is not defined.

Explanation: The server rolls back a database updatetransaction for an import operation because thedestination specified for a management class copygroup specifies the named storage pool, but thatstorage pool does not exist.

System Action: The import operation is ended andserver operation continues.

User Response: An administrator with policyauthority over the client policy domain must correctmanagement class definitions so that copy groupdestinations refer to defined storage pools, or thespecified storage pool must be created by an authorizedadministrator.

ANR0666W Import command: Transaction failed -object excluded by size in storage poolpool name and all successor pools.

Explanation: The server ends a database updatetransaction for an import operation because the size ofan imported file is larger than that allowed in thestorage pool specified in the bound management classcopy group for the file. No successor storage pools tothe one specified on the copy group can accept thelarge file.


User Response: The maximum file size for one ormore of the storage pools in the storage hierarchy canbe increased to accommodate the file. An authorizedadministrator can increase the MAXSIZE parameter byissuing the UPDATE STGPOOL command.Alternatively, the appropriate copygroup definition canbe updated so that a different destination storage poolis specified.

ANR0667W Import command: Transaction failed - nospace available in storage pool pool nameand all successor pools.

Explanation: The server ends an import operationbecause the storage pool specified in a managementclass copy group does not contain enough free space tohold the files being imported. Successor storage poolsto the one specified on the copy group do not containenough free space.


User Response: An authorized administrator can issuethe DEFINE VOLUME command to add storage to oneor more storage pools in the storage hierarchy.

ANR0668W Export/import command: Transaction failed- error on output storage device.

Explanation: The server ends an export or importoperation for the specified session because an I/O errorhas been encountered by the server in writing to adevice.


User Response: Query the activity log to findmessages preceding this one that specify the device thatis failing. Storage pool volumes can be varied offline(by using the VARY OFFLINE command), or the servermay need to be shut down by using the HALTcommand to correct the hardware problem. After theproblem is corrected, the client may be able to try theoperation again.

ANR0669W Export/import command: Transaction failed- data transfer interrupted.

Explanation: The database transaction associated withan export or import operation failed because datatransfer to or from data storage was interrupted by anexternal event.

System Action: The export or import operation isended and server operation continues.

User Response: Examine the messages issued prior tothis message to determine why the data transfer was



interrupted. Attempt the export/import operation againafter problem is resolved.

ANR0670W Export/import command: Transaction failed- storage media inaccessible.

Explanation: The server ends a transaction for anexport or import operation because storage volumes arenot available in the storage pools in which the clientfiles are to be stored.



ANR0671W Export/import command: Transaction failed- sufficient recovery log space is notavailable.

Explanation: The server ends a database updatetransaction for an export or import operation becausesufficient log space is not available on the server.


User Response: An authorized administrator can issuethe DEFINE LOGVOLUME command to add volumesfor use by the log, and the EXTEND LOG command toextend the size of the log so that the new volumes areused.

ANR0672W Export/import command: Transaction failed- sufficient database space is notavailable.

Explanation: The server ends a database updatetransaction for an export or import operation becausesufficient database space is not available on the server.


User Response: An authorized administrator can issuethe DEFINE DBVOLUME command to add volumesfor use by the database, and the EXTEND DBcommand to extend the size of the log so that the newvolumes are used.

ANR0673W Export/import command: Data storageretrieve or restore failed - data integrityerror detected.

Explanation: The server ends an export or importoperation because an internal database integrity errorhas been encountered on the server.

System Action: The server ends the export or import

operation and continues operation.


ANR0674W Export command: Retrieve failed - erroron input storage device.

Explanation: The server ends an export operation forthe specified session because an I/O error has beenencountered by the server in reading from a device.The object for which the I/O was issued is reported ina later message.

System Action: Export processing skips this file, andcontinues operation.

User Response: Query the activity log to findmessages preceding this one that specify the device thatis failing. Storage pool volumes can be varied offline(by using the VARY OFFLINE command), or the servermay need to be shut down with the HALT command tocorrect the hardware problem.

ANR0675E EXPORT/IMPORT: Error starting theExport/Import Session.

Explanation: The server export/import process is notable to start the session to export information from theserver or import information into the server.

System Action: The export or import process endsand server operation continues.


ANR0676E EXPORT/IMPORT: InvalidCommunications Buffer State in SEND.

Explanation: The server export/import processencounters a communications error in transferringinformation to or from the server.



ANR0677E EXPORT/IMPORT: InvalidCommunications Buffer State inRECEIVE.

Explanation: The server export/import processencounters a communications error in transferringinformation to or from the server.





ANR0678E EXPORT/IMPORT: CommunicationsFailure in Sending ″verb type″ verb.

Explanation: The server export/import processencounters a communications error in using the verbtype verb to transfer information to or from the server.



ANR0679E EXPORT/IMPORT: CommunicationsFailure in Receiving ″verb type″ verb.

Explanation: The server export/import processencounters a communications error in using the verbtype verb to transfer information to or from the server.



ANR0681E EXPORT/IMPORT: AuthenticationFailure.

Explanation: The server export/import processencounters an authentication error in transferringinformation to or from the server.



ANR0682E EXPORT/IMPORT: CommunicationsFailure in Sending ″verb type″ verb(command).

Explanation: The server export/import processencounters a communications error in using the verbtype verb to issue command command.



ANR0683E EXPORT/IMPORT: Receive Bufferoverflow.

Explanation: The server export/import processencounters an overflow error in transferringinformation to or from the server.



ANR0684E EXPORT/IMPORT: Communicationsfailure: bad verb received (verb type).

Explanation: The server encounters an invalidcommunications verb during export or importprocessing and is not able to continue processing.



ANR0685E EXPORT/IMPORT: Internal error:Invalid table output handle detected.

Explanation: The server export/import processencounters an internal error in transferring informationto or from the server.



ANR0686E Export/import command: Transactionfailure - could not start databasetransaction.

Explanation: During processing of commandexport/import command, a database transaction cannot bestarted in the server database.

System Action: Processing of the commandterminates.


ANR0687E Export/import command: Transactionfailure - could not commit databasetransaction.

Explanation: During processing of commandexport/import command, a database transaction cannot becommitted to the server database.

System Action: Processing of the command ends.




ANR0688E Export/import command: Transactionfailure - commit called when notransaction started.

Explanation: During processing of commandexport/import command, a database transaction cannot bestarted in the server database.



ANR0689W Import command: Client platform type(platform type) for imported node nodename conflicts with an existing nodewith the same name - the node will notbe imported.

Explanation: During import processing, the serverencounters an imported node definition that has thesame name as an existing node, but has a differentclient platform type (for example, OS/2 or AIX).Because file data may not be compatible acrossdifferent client platforms, the node is not imported.

System Action: Import processing continues, and thenamed node is skipped by import processing.

User Response: If you want to import the namednode, cancel the import process, rename the existingnode to a new name by using the RENAME NODEcommand, and run the import again. After you haveimported the node, use the RENAME NODE commandto set the node names as you desire.

ANR0690E Export/import command: Transactionfailure - server aborted the transaction(abort code).

Explanation: During processing of commandexport/import command, a database transaction cannot becommitted in the server database. The reason code abortcode is returned.



ANR0691E Export command: Error abort code writingexport data.

Explanation: During processing of command exportcommand, an input/output error occurs when writingthe exported information to the export media.



ANR0692E Command: Out of space on sequentialmedia, scratch media could not bemounted.

Explanation: During command command processing,the process encounters an out-of-space conditionwriting to the sequential media. Command commandends when there is no more space on the sequentialmedia for storing data and SCRATCH=NO has beenspecified on command command.

System Action: Command command processing ends.Server processing continues.

User Response: Reissue the command and specifySCRATCH=YES or specify additional volume names onthe command.

ANR0693E Import command: Error abort code readingexport data.

Explanation: During processing of command importcommand, an input/output error occurs when readingthe exported information from the export media.



ANR0694E Import command: Invalid record format(format code) detected on import.

Explanation: During processing of command importcommand, an invalid record type is detected whenreading the exported information from the exportmedia.





ANR0695E Export command: Unexpected error errorcode encountered in receiving tableoutput data.

Explanation: During processing of command exportcommand, an unexpected error is detected.



ANR0696E Export command: Output table errorencountered - 0 columns reported in thetable.




ANR0697E Export command: Output table errorencountered - not positioned to the firstcolumn in the table.




ANR0698E Export/import command: Invalid value forFILEDATA parameter - parameter value.

Explanation: The value (parameter value) specified forthe FILEDATA parameter in command export/importcommand is not a valid value for this parameter.


User Response: Reissue the command and specify avalid FILEDATA parameter. For information on validvalues for the FILEDATA parameter for the command,refer to the Administrator’s Reference for your particularplatform.

ANR0699E Export/import command: Device classDISK cannot be specified for thiscommand.

Explanation: The DEVCLASS value DISK cannot bespecified for the command export/import command.


User Response: Reissue the command and specify avalid device class. Issue the QUERY DEVCLASScommand for a list of valid device classes for theserver.

ANR0700E Export/import command: Invalid value forPREVIEW parameter - parameter value.

Explanation: The value (parameter value) specified forthe PREVIEW parameter in command export/importcommand is not a valid value for this parameter.


User Response: Reissue the command and specify avalid PREVIEW parameter. For information on validvalues for the PREVIEW parameter for the command,refer to the Administrator’s Reference for your particularplatform.

ANR0701E Export/import command: Invalid value forSCRATCH parameter - parameter value.

Explanation: The value (parameter value) specified forthe SCRATCH parameter in command export/importcommand is not a valid value for this parameter.


User Response: Reissue the command and specify avalid SCRATCH parameter. For information on validvalues for the SCRATCH parameter for the command,refer to the Administrator’s Reference for your particularplatform.

ANR0705E Export command: The VOLUMENAMESparameter must be specified whenSCRATCH=NO is specified.

Explanation: The SCRATCH parameter is specified asNO for the command export command but theVOLUMENAMES parameter is not specified. Whenscratch volumes are not allowed, the VOLUMENAMESparameter must be specified to indicate the volumesthat can be used for the command.


User Response: Reissue the command and specify avalid VOLUMENAMES parameter. For information onvalid parameter values for the command, refer to the



Administrator’s Reference for your particular platform.

ANR0706E Export command: A device class must bespecified unless PREVIEW=YES isspecified.

Explanation: The DEVCLASS parameter is notspecified in the command export command. UnlessPREVIEW=YES is specified, a DEVCLASS value mustbe specified.



ANR0707E Export command: The FILESPACEparameter cannot be specified.

Explanation: The FILESPACE parameter is specifiedfor the command export command, but the FILEDATAparameter is specified as NONE, or is not specified anddefaults to NONE. File spaces are only copied if theFILEDATA parameter is specified with a value otherthan NONE.


User Response: Reissue the command and specify avalid FILEDATA parameter. For information on validparameter values for the command, refer to theAdministrator’s Reference for your particular platform.

ANR0708E Import command: The FILESPACEparameter cannot be specified unless theFILEDATA parameter specifies that filesshould be imported.

Explanation: The FILESPACE parameter is specifiedfor the command import command, but the FILEDATAparameter is specified as NONE, or is not specified anddefaults to NONE. File spaces are only copied if theFILEDATA parameter is specified with a value otherthan NONE.


User Response: Reissue the command and specify avalid FILEDATA parameter. For information on validparameter values for the command, refer to theAdministrator’s Reference for your particular platform.

ANR0709E Command: No matching nodes registeredin the specified domains.

Explanation: The DOMAIN parameter has beenspecified for this command, but no nodes matching the

node name specification are found in the domainsspecified.


User Response: Reissue the command and specify avalid combination of node and domain names. Use theQUERY NODE command to view the names of nodesin the domains that you are interested in exporting.

ANR0710E Command: Unable to start backgroundprocess.

Explanation: The server command processor is notable to start a background process to perform thecommand command.

System Action: The command process ends andserver operation continues.


ANR0711E Import command: Unable to start importprocess.

Explanation: The server import command processor isnot able to start a background process to perform theimport operation.



ANR0712E Import command: Invalid value forDATES parameter - parameter value.

Explanation: The value (parameter value) specified forthe DATES parameter in command import command isnot a valid value for this parameter.


User Response: Reissue the command and specify avalid DATES parameter. For information on validvalues for the DATES parameter for the command,refer to the Administrator’s Reference for your particularplatform.

ANR0713E Import command: Invalid value forREPLACEDEFS parameter - parametervalue.

Explanation: The value (parameter value) specified forthe REPLACEDEFS parameter in command importcommand is not a valid value for this parameter.




User Response: Reissue the command and specify avalid REPLACEDEFS parameter. For information onvalid values for the REPLACEDEFS parameter for thecommand, refer to the Administrator’s Reference for yourparticular platform.

ANR0714E Import command: The EXTFILE deviceclass cannot be specified when theVOLUMENAMES parameter isspecified.

Explanation: An invalid combination of parametershas been entered for command import command. TheEXTFILE device class cannot be used in combinationwith the VOLUMENAMES parameter.


User Response: Reissue the command with the correctsyntax.

ANR0715E Import command: A device class must bespecified.

Explanation: The command import command has beenspecified, but does not include specification of theDEVCLASS parameter. The DEVCLASS parametermust be specified for this command.


User Response: Reissue the command and specify avalid device class. For a list of valid device classes forthe server, issue the QUERY DEVCLASS command.

ANR0716E Import command: Invalid export datadetected.

Explanation: The command import commandencounters invalid data on the export media whiletrying to import server information.


User Response: Ensure that the mounted export tapesare in the correct order (mounted in the same order asthey were mounted during export). Reissue thecommand, and mount the tapes in the correct order. Ifthe VOLUMENAMES parameter has been specified,make sure that the volume names in the command arespecified in the correct order.

ANR0717E Export/import command: Previewprocessing terminated abnormally -communications send or receive failed.

Explanation: Processing for the command export/importcommand in preview mode has been terminated when

an internal communications error is encountered in theserver.

System Action: Export/import processing is endedand server operation continues.


ANR0718E Export/import command: Processingterminated abnormally -communications send or receive failed.

Explanation: Processing for the command export/importcommand ends when an internal communications erroris encountered in the server.



ANR0719E Export/import command: Previewprocessing terminated abnormally -insufficient memory.

Explanation: Processing for the command export/importcommand in preview mode is ended because sufficientmemory is not available on the server.



ANR0720E command: Processing terminatedabnormally - insufficient memory.

Explanation: Processing for the command endsbecause sufficient memory is not available on theserver.

System Action: Command processing is ended andserver operation continues.




ANR0721E Export/import command: Previewprocessing terminated abnormally -unexpected verb received from server.

Explanation: Processing for the command export/importcommand in preview mode ends when an internalcommunications error is encountered in the server.

System Action: Export/import processing ends andserver operation continues.


ANR0722E Export/import command: Processingterminated abnormally - unexpectedverb received from server.

Explanation: Processing for the command export/importcommand ends when an internal communications erroris encountered in the server.



ANR0723E Export/import command: Previewprocessing terminated abnormally -transaction failure.

Explanation: Processing for the command export/importcommand in preview mode ends when a databasetransaction error is encountered in the server.



ANR0724E Export/import command: Processingterminated abnormally - transactionfailure.

Explanation: Processing for the command export/importcommand ends when a database transaction error isencountered in the server.



ANR0725E Export/import command: Previewprocessing terminated abnormally -authentication failure.

Explanation: Processing for the command export/importcommand in preview mode ends when an authenticationerror is encountered in the server.



ANR0726E Export/import command: Processingterminated abnormally - authenticationfailure.

Explanation: Processing for the command export/importcommand ends when an authentication error isencountered in the server.



ANR0727E Export/import command: Previewprocessing terminated abnormally -internal error.

Explanation: Processing for the command export/importcommand in preview mode ends when an internal erroris encountered in the server.





ANR0728E Export/import command: Processingterminated abnormally - internal error.

Explanation: Processing for the command export/importcommand ends when an internal error is encountered inthe server.



ANR0729E Import command: Syntax error fromcommand ’server command’.

Explanation: During processing of the commandimport command, an internal syntax error is encounteredin the server.

System Action: Import processing continues, but theindicated command will have no effect.

User Response: Examine the server messages issuedprior to this message to determine the source of theerror. Use the QUERY ACTLOG command to view theactivity log and search for messages. After importprocessing is complete, it may be necessary to issueadditional commands manually to obtain the necessarydefinitions.

ANR0730E Import command: Internal error fromcommand ’server command’.

Explanation: Processing for the command importcommand ends when an internal command error isencountered in the server.



ANR0731E Import command: Invalid value forCOMPRESSION parameter in exporteddata for node node name.

Explanation: During preview processing of commandimport command, an invalid value is encountered for theCOMPRESSION parameter for node node name.

System Action: Processing of the command continues.If a later command causes the data to be imported, thedefault or existing COMPRESSION value is used.

User Response: None. If the data is imported with alater command, verify that the correct COMPRESSIONvalue is used for this node.

ANR0732E Import command: Invalid value forARCHDELETE parameter in exporteddata for node node name.

Explanation: During preview processing of commandimport command, an invalid value is encountered for theARCHDELETE parameter for node node name.

System Action: Processing of the command continues.If a later command causes the data to be imported, thedefault or existing ARCHDELETE value is used.

User Response: None. If the data is imported with alater command, verify that the correct ARCHDELETEvalue is used for this node.

ANR0733E Import command: Invalid value forBACKDELETE parameter in exporteddata for node node name.

Explanation: During preview processing of commandimport command, an invalid value is encountered for theBACKDELETE parameter for node node name.

System Action: Processing of the command continues.If a later command causes the data to be imported, thedefault or existing BACKDELETE value is used.

User Response: None. If the data is imported with alater command, verify that the correct BACKDELETEvalue is used for this node.

ANR0734E Import command: Invalid value forCOMPRESSION parameter in exporteddata - node node name registered withdefault COMPRESSION value.

Explanation: During processing of command importcommand, an invalid value is encountered for theCOMPRESSION parameter for node node name.

System Action: Processing of the command continues,by using the default COMPRESSION value for thisnode.

User Response: Verify that the correctCOMPRESSION value has been used for this node.Update this value, if necessary.

ANR0735E Import command: Invalid value forARCHDELETE parameter in exporteddata - node node name registered withdefault ARCHDELETE value.

Explanation: During processing of command importcommand, an invalid value is encountered for theARCHDELETE parameter for node node name.

System Action: Processing of the command continues,by using the default ARCHDELETE value for this node.



User Response: Verify that the correct ARCHDELETEvalue has been used for this node. Update this value, ifnecessary.

ANR0736E Import command: Invalid value forBACKDELETE parameter in exporteddata - node node name registered withdefault BACKDELETE value.

Explanation: During processing of command importcommand, an invalid value is encountered for theBACKDELETE parameter for node node name.

System Action: Processing of the command continues,by using the default BACKDELETE value for this node.

User Response: Verify that the correct BACKDELETEvalue has been used for this node. Update this value, ifnecessary.

ANR0737E Import command: Invalid value forCOMPRESSION parameter in exporteddata - existing COMPRESSION valuefor node node name was not updated.

Explanation: During processing of command importcommand, an invalid value is encountered for theCOMPRESSION parameter for node node name.

System Action: Processing of the command continues,by using the existing COMPRESSION value for thisnode.

User Response: Verify that the correctCOMPRESSION value has been used for this node.Update this value, if necessary.

ANR0738E Import command: Invalid value forARCHDELETE parameter in exporteddata - existing ARCHDELETE value fornode node name was not updated.

Explanation: During processing of command importcommand, an invalid value is encountered for theARCHDELETE parameter for node node name.

System Action: Processing of the command continues,by using the existing ARCHDELETE value for thisnode.

User Response: Verify that the correct ARCHDELETEvalue has been used for this node. Update this value, ifnecessary.

ANR0739E Import command: Invalid value forBACKDELETE parameter in exporteddata - existing BACKDELETE value fornode node name was not updated.

Explanation: During processing of command importcommand, an invalid value is encountered for theBACKDELETE parameter for node node name.

System Action: Processing of the command continues,

by using the existing BACKDELETE value for thisnode.

User Response: Verify that the correct BACKDELETEvalue has been used for this node. Update this value, ifnecessary.

ANR0740E Import command: Invalid value for TYPEparameter in exported data for copygroup copy group name in domain domainname, set policy set name, managementclass management class name - backup isassumed.

Explanation: During processing of command importcommand, an invalid value is encountered for the TYPEparameter for copy group copy group, in policy domaindomain name, policy set policy set name, managementclass management class name.

System Action: Processing of the command continues.Based upon other copy group parameters, a copy grouptype of backup is assigned.

User Response: Verify that the assigned TYPE valueof backup for this copy group is correct.

ANR0741E Import command: Invalid value for TYPEparameter in exported data for copygroup copy group name in domain domainname, set policy set name, managementclass management class name - archive isassumed.


System Action: Processing of the command continues.Based upon other copy group parameters, a copy grouptype of archive is assigned.

User Response: Verify that the assigned TYPE valueof archive for this copy group is correct.

ANR0742E Import command: Invalid value for TYPEparameter in exported data for copygroup copy group name in domain domainname, set policy set name, managementclass management class name - this copygroup will not be imported.


System Action: Processing of the command continues.However, this copy group is not imported because aTYPE value cannot be assigned.



User Response: Manually define this copy group, ifnecessary.

ANR0743E Import command: Invalid value forMODE parameter in exported data forarchive copy group copy group name indomain domain name, set policy set name,management class management class name.

Explanation: During preview processing of commandimport command, an invalid value is encountered for theMODE parameter for archive copy group copy groupname, in policy domain domain name, policy set policy setname, management class management class name.

System Action: Processing of the command continues.If a later command causes the data to be imported, thedefault or existing MODE value is used.

User Response: None. If the data is imported with alater command, verify that the correct MODE value isused for this archive copy group.

ANR0744E Import command: Invalid value forMODE parameter in exported data forbackup copy group copy group name indomain domain name, set policy set name,management class management class name.

Explanation: During preview processing of commandimport command, an invalid value is encountered for theMODE parameter for backup copy group copy groupname, in policy domain domain name, policy set policy setname, management class management class name.

System Action: Processing of the command continues.If a later command causes the data to be imported, thedefault or existing MODE value is used.

User Response: None. If the data is imported with alater command, verify that the correct MODE value isused for this backup copy group.

ANR0745E Import command: Invalid value forSERIALIZATION parameter in exporteddata for archive copy group copy groupname in domain domain name, set policyset name, management class managementclass name.

Explanation: During preview processing of commandimport command, an invalid value is encountered for theSERIALIZATION parameter for archive copy groupcopy group name, in policy domain domain name, policyset policy set name, management class management classname.

System Action: Processing of the command continues.If a later command causes the data to be imported, thedefault or existing SERIALIZATION value is used.

User Response: None. If the data is imported with alater command, verify that the correct SERIALIZATIONvalue is used for this archive copy group.

ANR0746E Import command: Invalid value forSERIALIZATION parameter in exporteddata for backup copy group copy groupname in domain domain name, set policyset name, management class managementclass name.

Explanation: During preview processing of commandimport command, an invalid value is encountered for theSERIALIZATION parameter for backup copy groupcopy group name, in policy domain domain name, policyset policy set name, management class management classname.

System Action: Processing of the command continues.If a later command causes the data to be imported, thedefault or existing SERIALIZATION value is used.

User Response: None. If the data is imported with alater command, verify that the correct SERIALIZATIONvalue is used for this backup copy group.

ANR0747E Import command: Invalid value forMODE parameter in exported data -archive copy group copy group name indomain domain name, set policy set name,management class management class namedefined with default MODE value.

Explanation: During processing of command importcommand, an invalid value is encountered for theMODE parameter for archive copy group copy groupname, in policy domain domain name, policy set policy setname, management class management class name.

System Action: Processing of the command continues,by using the default MODE value for this archive copygroup.

User Response: Verify that the correct MODE valuehas been used for this copy group. Update this value, ifnecessary.

ANR0748E Import command: Invalid value forMODE parameter in exported data -backup copy group copy group name indomain domain name, set policy set name,management class management class namedefined with default MODE value.

Explanation: During processing of command importcommand, an invalid value is encountered for theMODE parameter for backup copy group copy groupname, in policy domain domain name, policy set policy setname, management class management class name.

System Action: Processing of the command continues,by using the default MODE value for this backup copygroup.




ANR0749E Import command: Invalid value forSERIALIZATION parameter in exporteddata - archive copy group copy groupname in domain domain name, set policyset name, management class managementclass name defined with defaultSERIALIZATION value.

Explanation: During processing of command importcommand, an invalid value is encountered for theSERIALIZATION parameter for archive copy groupcopy group name, in policy domain domain name, policyset policy set name, management class management classname.

System Action: Processing of the command continues,by using the default SERIALIZATION value for thisarchive copy group.

User Response: Verify that the correctSERIALIZATION value has been used for this copygroup. Update this value, if necessary.

ANR0750E Import command: Invalid value forSERIALIZATION parameter in exporteddata - backup copy group copy groupname in domain domain name, set policyset name, management class managementclass name defined with defaultSERIALIZATION value.

Explanation: During processing of command importcommand, an invalid value is encountered for theSERIALIZATION parameter for backup copy groupcopy group name, in policy domain domain name, policyset policy set name, management class management classname.

System Action: Processing of the command continues,by using the default SERIALIZATION value for thisbackup copy group.


ANR0751E Import command: Invalid value forMODE parameter in exported data -existing MODE value for archive copygroup copy group name in domain domainname, set policy set name, managementclass management class name was notupdated.

Explanation: During processing of command importcommand, an invalid value is encountered for theMODE parameter for archive copy group copy groupname, in policy domain domain name, policy set policy setname, management class management class name.

System Action: Processing of the command continues,by using the existing MODE value for this archive copygroup.


ANR0752E Import command: Invalid value forMODE parameter in exported data -existing MODE value for backup copygroup copy group name in domain domainname, set policy set name, managementclass management class name was notupdated.

Explanation: During processing of command importcommand, an invalid value is encountered for theMODE parameter for backup copy group copy groupname, in policy domain domain name, policy set policy setname, management class management class name.

System Action: Processing of the command continues,by using the existing MODE value for this backup copygroup.


ANR0753E Import command: Invalid value forSERIALIZATION parameter in exporteddata - existing SERIALIZATION valuefor archive copy group copy group namein domain domain name, set policy setname, management class management classname was not updated.

Explanation: During processing of command importcommand, an invalid value is encountered for theSERIALIZATION parameter for archive copy groupcopy group name, in policy domain domain name, policyset policy set name, management class management classname.

System Action: Processing of the command continues,by using the existing SERIALIZATION value for thisarchive copy group.


ANR0754E Import command: Invalid value forSERIALIZATION parameter in exporteddata - existing SERIALIZATION valuefor backup copy group copy group namein domain domain name, set policy setname, management class management classname was not updated.

Explanation: During processing of command importcommand, an invalid value is encountered for theSERIALIZATION parameter for backup copy groupcopy group name, in policy domain domain name, policyset policy set name, management class management classname.



System Action: Processing of the command continues,by using the existing SERIALIZATION value for thisbackup copy group.


ANR0755E Import command: Invalid value forACTION parameter in exported data forschedule schedule name in domain domainname.

Explanation: During preview processing of commandimport command, an invalid value is encountered for theACTION parameter for schedule schedule name in policydomain domain name.

System Action: Processing of the command continues.If a later command causes the data to be imported, thedefault or existing ACTION value is used.

User Response: If the data is imported with a latercommand, verify that the correct ACTION value isused for this schedule.

ANR0756E Import command: Invalid value forDURUNITS or PERUNITS parameter inexported data for schedule schedule namein domain domain name.

Explanation: During preview processing of commandimport command, an invalid value is encountered for theDURUNITS or PERUNITS parameter for scheduleschedule name in policy domain domain name.

System Action: Processing of the command continues.If a later command causes the data to be imported, thedefault or existing values are used for DURATION,DURUNITS, PERIOD, and PERUNITS.

User Response: If the data is imported with a latercommand, verify that the correct values forDURATION, DURUNITS, PERIOD, and PERUNITS areused for this schedule.

ANR0757E Import command: Invalid value forDAYOFWEEK parameter in exporteddata for schedule schedule name indomain domain name.

Explanation: During preview processing of commandimport command, an invalid value is encountered for theDAYOFWEEK parameter for schedule schedule name inpolicy domain domain name.

System Action: Processing of the command continues.If a later command causes the data to be imported, thedefault or existing DAYOFWEEK value is used.

User Response: If the data is imported with a latercommand, verify that the correct DAYOFWEEK value isused for this schedule.

ANR0758E Import command: Invalid value forACTION parameter in exported data -schedule schedule name in domain domainname defined with default ACTIONvalue.

Explanation: During processing of command importcommand, an invalid value is encountered for theACTION parameter for schedule schedule name in policydomain domain name.

System Action: Processing of the command continues,by using the default ACTION value for this schedule.

User Response: Verify that the correct ACTION valuehas been used for this schedule. Update this value, ifnecessary.

ANR0759E Import command: Invalid value forDURUNITS or PERUNITS parameter inexported data - schedule schedule name indomain domain name defined withdefault values for DURATION,DURUNITS, PERIOD, and PERUNITS.

Explanation: During processing of command importcommand, an invalid value is encountered for theDURUNITS or PERUNITS parameter for scheduleschedule name in policy domain domain name.

System Action: Processing of the command continues,by using the default values for DURATION,DURUNITS, PERIOD, and PERUNITS.


ANR0760E Import command: Invalid value forDAYOFWEEK parameter in exporteddata - schedule schedule name in domaindomain name defined with defaultDAYOFWEEK value.

Explanation: During processing of command importcommand, an invalid value is encountered for theDAYOFWEEK parameter for schedule schedule name inpolicy domain domain name.

System Action: Processing of the command continues,by using the default DAYOFWEEK value for thisschedule.




ANR0761E Import command: Invalid value forACTION parameter in exported data -existing ACTION value for scheduleschedule name in domain domain name wasnot updated.

Explanation: During processing of command importcommand, an invalid value is encountered for theACTION parameter for schedule schedule name in policydomain domain name.

System Action: Processing of the command continues,by using the existing ACTION value for this schedule.

User Response: Verify that the correct ACTION valuehas been used for this schedule. Update this value, ifnecessary.

ANR0762E Import command: Invalid value forDURUNITS or PERUNITS parameter inexported data - existing values forDURATION, DURUNITS PERIOD, andPERUNITS for schedule schedule name indomain domain name were not updated.

Explanation: During processing of command importcommand, an invalid value is encountered for theDURUNITS or PERUNITS parameter for scheduleschedule name in policy domain domain name.

System Action: Processing of the command continues,by using the existing values for DURATION,DURUNITS, PERIOD, and PERUNITS.


ANR0763E Import command: Invalid value forDAYOFWEEK parameter in exporteddata - existing DAYOFWEEK value forschedule schedule name in domain domainname was not updated.

Explanation: During processing of command importcommand, an invalid value is encountered for theDAYOFWEEK parameter for schedule schedule name inpolicy domain domain name.

System Action: Processing of the command continues,by using the existing DAYOFWEEK value for thisschedule.


ANR0764E Import command: Invalid lock statusdetected while importing node nodename - this node will not be locked.

Explanation: During processing of command importcommand, an invalid value is encountered for the lockstatus for node node name.

System Action: Processing of the command continues,but the node is not locked.

User Response: An administrator with the properauthorization must issue the LOCK NODE command, ifnecessary.

ANR0765E Import command: Invalid lock statusdetected while importing administratoradministrator name - this administratorwill not be locked.

Explanation: During processing of command importcommand, an invalid value is encountered for the lockstatus for administrator administrator name.

System Action: Processing of the command continues,but the administrator is not locked.

User Response: An administrator with the properauthorization must issue the LOCK ADMIN command,if necessary.

ANR0766E Export command: Invalid value for TYPEparameter detected while exporting copygroup copy group name in domain domainname, set policy set name, managementclass management class name - system willattempt to assign value during import.

Explanation: During processing of command exportcommand, an invalid value is encountered for the TYPEparameter for copy group copy group name, in domaindomain name, policy set policy set name, managementclass management class name.

System Action: Export processing continues, but theexported data contains an unknown TYPE value forthis copy group. If this data is imported, the systemattempts to assign a TYPE value based upon values forother copy group parameters.

User Response: Delete and define this copy group toeliminate the invalid data, and then restart the exportcommand. Alternatively, use the export data with theunknown value, and the system will attempt to assigna TYPE during import processing.

ANR0767E Export command: Invalid value forMODE parameter detected whileexporting copy group copy group name indomain domain name, set policy set name,management class management class name- default or existing value is usedduring import.

Explanation: During processing of command exportcommand, an invalid value is encountered for theMODE parameter for copy group copy group name indomain domain name, policy set policy set name,management class management class name.

System Action: Export processing continues, but theexported data contains an unknown MODE value for



this copy group. If this data is imported, the default orexisting MODE value is used.

User Response: Update the MODE value for this copygroup and restart the export command. Alternatively,use the export data with the unknown value, and checkand update the MODE value after import processinghas been performed.

ANR0768E Export command: Invalid value forSERIALIZATION parameter detectedwhile exporting copy group copy groupname in domain domain name, set policyset name, management class managementclass name - default or existing value isused during import.

Explanation: During processing of command exportcommand, an invalid value is encountered for theSERIALIZATION parameter for copy group copy groupname, in domain domain name, policy set policy set name,management class management class name.

System Action: Export processing continues, but theexported data contains an unknown SERIALIZATIONvalue for this copy group. If this data is imported, thedefault or existing SERIALIZATION value is used.

User Response: Update the SERIALIZATION valuefor this copy group and restart the export command.Alternatively, use the export data with the unknownvalue, and check and update the SERIALIZATIONvalue after import processing has been performed.

ANR0769E Export command: Invalid value forACTION parameter detected whileexporting schedule schedule name indomain domain name - default or existingvalue is used during import.

Explanation: During processing of command exportcommand, an invalid value is encountered for theACTION parameter for schedule schedule name indomain domain name.

System Action: Export processing continues, but theexported data will contain an unknown ACTION valuefor this schedule. If this data is imported, the default orexisting ACTION value is used.

User Response: Update the ACTION value for thisschedule and restart the export command. Alternatively,use the export data with the unknown value, and checkand update the ACTION value after import processinghas been performed.

ANR0770E Export command: Invalid value forDURUNITS parameter detected whileexporting schedule schedule name indomain domain name - default or existingvalue is used during import.

Explanation: During processing of command exportcommand, an invalid value is encountered for theDURUNITS parameter for schedule schedule name indomain domain name.

System Action: Export processing continues, but theexported data contains an unknown DURUNITS valuefor this schedule. If this data is imported, the default orexisting DURUNITS value is used.

User Response: Update the DURUNITS value for thisschedule and restart the export command. Alternatively,use the export data with the unknown value, and checkand update the DURUNITS value after importprocessing has been performed.

ANR0771E Export command: Invalid value forPERUNITS parameter detected whileexporting schedule schedule name indomain domain name - default or existingvalue is used during import.

Explanation: During processing of command exportcommand, an invalid value is encountered for thePERUNITS parameter for schedule schedule name indomain domain name.

System Action: Export processing continues, but theexported data will contain an unknown PERUNITSvalue for this schedule. If this data is imported, thedefault or existing PERUNITS value is used.

User Response: Update the PERUNITS value for thisschedule and restart the export command. Alternatively,use the export data with the unknown value, and checkand update the PERUNITS value after importprocessing has been performed.

ANR0772E Export command: Invalid value forDAYOFWEEK parameter detected whileexporting schedule schedule name indomain domain name - default or existingvalue is used during import.

Explanation: During processing of command exportcommand, an invalid value is encountered for theDAYOFWEEK parameter for schedule schedule name indomain domain name.

System Action: Export processing continues, but theexported data contains an unknown DAYOFWEEKvalue for this schedule. If this data is imported, thedefault or existing DAYOFWEEK value is used.

User Response: Update the DAYOFWEEK value forthis schedule and restart the export command.Alternatively, use the export data with the unknownvalue, and check and update the DAYOFWEEK value



after import processing has been performed.

ANR0773E Export command: Invalid lock statusdetected while exporting administratoradministrator name - this administratorwill not be locked during import.

Explanation: During processing of command exportcommand, an invalid value is encountered for the lockstatus for administrator administrator name.

System Action: Export processing continues, but theexported data contains an unknown lock status for thisadministrator. If this data is imported, theadministrator will not be locked.

User Response: An administrator with the properauthorization must issue the LOCK NODE orUNLOCK NODE command to achieve the desired lockstatus, and then restart the export command.Alternatively, use the export data with the unknownstatus, and issue a LOCK ADMIN or UNLOCKADMIN command after import processing has beenperformed.

ANR0774E Export command: Invalid value forCOMPRESSION parameter detectedwhile exporting node node name - defaultor existing value is used during import.

Explanation: During processing of command exportcommand, an invalid value is encountered for theCOMPRESSION parameter for node node name.

System Action: Export processing continues, but theexported data contains an unknown COMPRESSIONvalue for this node. If this data is imported, the defaultor existing COMPRESSION value is used.

User Response: Update the COMPRESSIONparameter for this node and restart the exportcommand. Alternatively, use the export data with theunknown value, and check and update theCOMPRESSION value after import processing has beenperformed.

ANR0775E Export command: Invalid lock statusdetected while exporting node node name- this node will not be locked duringimport.

Explanation: During processing of command exportcommand, an invalid value is encountered for the lockstatus for node node name.

System Action: Export processing continues, but theexported data contains an unknown lock status for thisnode. If this data is imported, the node will not belocked.

User Response: Lock or unlock the node to achievethe desired lock status, and then restart the exportcommand. Alternatively, use the export data with theunknown status, and lock or unlock the node after

import processing has been performed.

ANR0776E Export command: Invalid value forARCHDELETE parameter detectedwhile exporting node node name - defaultor existing value is used during import.

Explanation: During processing of command exportcommand, an invalid value is encountered for theARCHDELETE parameter for node node name.

System Action: Export processing continues, but theexported data contains an unknown ARCHDELETEvalue for this node. If this data is imported, the defaultor existing ARCHDELETE value is used.

User Response: Update the ARCHDELETE parameterfor this node and restart the export command.Alternatively, use the export data with the unknownvalue, and check and update the ARCHDELETE valueafter import processing has been performed.

ANR0777E Export command: Invalid value forBACKDELETE parameter detected whileexporting node node - default or existingvalue is used during import.

Explanation: During processing of command exportcommand, an invalid value is encountered for theBACKDELETE parameter for node node name.

System Action: Export processing continues, but theexported data contains an unknown BACKDELETEvalue for this node. If this data is imported, the defaultor existing BACKDELETE value is used.

User Response: Update the BACKDELETE parameterfor this node and restart the export command.Alternatively, use the export data with the unknownvalue, and check and update the BACKDELETE valueafter import processing has been performed.

ANR0778E Command: Error encountered in accessingdata storage - device class device classname is not defined.

Explanation: During command command processing,an error occurred because the specified device class isnot defined.

System Action: The command command is ended andserver operation continues.

User Response: Make sure the specified device class isdefined.

ANR0779E Command: Error encountered in accessingdata storage - disk volume specified.

Explanation: During command command processing,an error occurred because a specified volume is a diskvolume rather than a tape volume.




User Response: Make sure that all volumes specifiedfor the command command are tape volumes.

ANR0780E Export/import command: Process aborted -a server communications session couldnot be established.

Explanation: The server export/import processencounters an internal error in establishing anintermemory communications session with other servercomponents.


User Response: Allocate additional storage to theserver. For details, issue HELP MEMORY to display theinformation online or see “Appendix A. AllocatingAdditional Server Memory”. If the error is not resolved,contact your service representative.

ANR0781E Export/import command: Process aborted -server sign on failed.

Explanation: The server export/import processencounters an internal error in establishing anintermemory communications session with other servercomponents.



ANR0782E Export/import command: Process aborted -a server data storage session could notbe established (rc return code).

Explanation: The server export/import processencounters an internal error in establishing a sessionwith the data storage services.



ANR0783E Export/import command: Process aborted -a server data storage Export/Importstream could not be established (rcreturn code).

Explanation: The server export/import processencounters an internal error in establishing a sessionwith the data storage services.



ANR0784E Export/import command: Process aborted -internal error detected with theExport/Import level: level number.

Explanation: The server export/import processencounters an internal error in evaluating theexport/import level (SERVER, NODE, ADMIN,POLICY).



ANR0785E Import command: Invalid record typexrecord type read from export data.

Explanation: The server export/import processencounters an internal error in reading data from theexport media. An invalid record type of record type isencountered during the read operation.



ANR0786E Import command: Invalid export versionversion number in exported data.

Explanation: The server import process encounters aninternal error in reading data from the export media.An invalid export version number (version number) isencountered during the read operation.





ANR0787E Import command: Import of file spacefilespace name in node node name abortedby server (abort reason).

Explanation: The server import process encounters aninternal error in importing file space filespace name forclient node node name. The reason code abort reason isencountered.



ANR0788E Import command: Error error code duringimport of data storage data.

Explanation: The server import process encounters aninternal data storage error. The error code error code isencountered.



ANR0789E Import command: Failure in normalizingtransaction identifier for sending to theserver.

Explanation: The server import process encounters aninternal database transaction error in importinginformation into the server database.



ANR0790E Import command: Error in absorbing datarecords.

Explanation: The server import process encounters aninternal error in importing information into the serverdatabase.



ANR0791E Export/import command: Protocol error -verb ″verb type″ with length verb lengthreceived, expected ″expected type″.

Explanation: The server export or import processencounters an internal protocol error in exportinginformation from or importing information into theserver database. The verb verb type is encountered witha length of verb length when a verb type of expected typewas expected.



ANR0792E Import command: Invalid copy typeencountered in an imported file spaceauthorization rule for node node name,file space filespace name - a type ofBACKUP will be assumed.

Explanation: During import processing for commandimport command, an invalid copy type is encounteredfor an authorization rule that grants access for filespace filespace name on node node name. Authorizationrules typically specify copy types of backup or archive,depending on whether backup file access or archive fileaccess is granted by the file space owner to other users.Because the imported information for the rule isambiguous, the server assumes that the rule is forbackup data.

System Action: The import process continues.

User Response: The user for node node name shouldquery the access rules for the specified node name afterthe import process has completed, and correct or deleteany access rules that are in error or not needed.

ANR0793E Export/import command: Previewprocessing terminated abnormally -error accessing data storage.

Explanation: The server encountered an internal errorin accessing data storage while executing an import orexport preview operation.


User Response: Use the QUERY ACTLOG command



to examine messages prior to this error to determinethe cause of the data storage failure. If you find andresolve the error, retry the export or import operation.If you cannot find the error, contact your servicerepresentative for assistance in resolving the problem.

ANR0794E Export/import command: Processingterminated abnormally - error accessingdata storage.

Explanation: The server encountered an internal errorin accessing data storage while executing an import orexport operation.


User Response: Use the QUERY ACTLOG commandto examine messages prior to this error to determinethe cause of the data storage failure. If you find andresolve the error, retry the export or import operation.If you cannot find the error, contact your servicerepresentative for assistance in resolving the problem.

ANR0795E Command: Error encountered in accessingdata storage - invalid volume namespecified.

Explanation: The server encounters an error inaccessing data storage while processing commandcommand. The error occurred because an attempt hasbeen made to access a volume with an invalid name.


User Response: Issue the command with a validvolume name.

ANR0796E Command: Error encountered in accessingdata storage - insufficient number ofmount points available for removablemedia.

Explanation: During command command processing,the server cannot allocate sufficient mount points.



ANR0797E Command: Error encountered in accessingdata storage - required volume was notmounted.

Explanation: During command command processing, arequired volume cannot be mounted. The mountrequest may have been canceled.


User Response: Issue the command again and makesure the necessary volumes are accessible.

ANR0798E Import command: Error encountered inaccessing data storage - volume cannotbe used.

Explanation: During import processing, a volume hasbeen mounted but cannot be used.


User Response: Query the activity log for messagespreceding this one that give additional information.Make sure a usable volume is specified and mounted.

ANR0799E Command: Error encountered in accessingdata storage - volume already in use.

Explanation: During command command processing, avolume cannot be used because it is already defined ina storage pool, or has been previously used by anexport, database dump, or database backup operation(as recorded in the volume history) or is in use byanother process.


User Response: Specify a volume that is not in use ordefined in a storage pool, and that has not beenpreviously used for an export, database dump, ordatabase backup operation as recorded in the servervolume history information. Use the QUERY VOLUMEcommand to display the names of volumes that aredefined to server storage pools. Use the QUERYVOLHISTORY command to display the names ofvolumes that have been used for export, databasedump, or database backup operations.

ANR0800I Command command for node node namestarted as process process ID.

Explanation: A file space deletion process has startedto delete one or more file spaces for the specified node.The process is assigned the ID specified in the message.

System Action: The server starts a backgroundprocess to perform the operation in response to theDELETE FILESPACE command entered by anadministrator.

User Response: To obtain status on the file spacedeletion process, issue the QUERY PROCESS command.The process may be canceled with the CANCELPROCESS command.



ANR0801I DELETE FILESPACE filespace name fornode node name started as process processID.

Explanation: The specified client node has started afile space deletion process (on the server) to delete oneor more file spaces. The process has been assigned theID specified in the message.

System Action: The server starts a backgroundprocess to perform the operation in response to arequest from the client node.

User Response: To obtain status on the file spacedeletion process, issue the QUERY PROCESS command.The process may be canceled by an authorizedadministrator using the CANCEL PROCESS command.

ANR0802I DELETE FILESPACE filespace name(backup/archive data) for node node namestarted.

Explanation: A background server process has started(on the server) to delete the specified file spacebelonging to the node indicated. If a file space name isnot included in the message, all file spaces belonging tothe node are deleted.

System Action: The background process deletesbackup and archive objects for the specified file spacewhile server operation continues.


ANR0803I DELETE FILESPACE filespace name(backup data) for node node namestarted.

Explanation: A background server process has started(on the server) to delete backup objects in the specifiedfile space belonging to the node indicated. If a filespace name is not included in the message, then thebackup objects for all file spaces that belong to thenode are deleted.

System Action: The background process deletesbackup objects for the specified file space while serveroperation continues.


ANR0804I DELETE FILESPACE filespace name(archive data) for node node name started.

Explanation: A background server process has started(on the server) to delete archive objects in the specifiedfile space belonging to the node indicated. If a filespace name is not included in the message, then the

archive objects for all file spaces that belong to thenode are deleted.

System Action: The background process deletesarchive objects for the specified file space while serveroperation continues.


ANR0805I DELETE FILESPACE filespace namecanceled for node node name: number ofobjects objects deleted.

Explanation: A background server process that hasbeen deleting file space data for the indicated node iscanceled by the CANCEL PROCESS command. Thenumber of objects deleted before the cancel ended theoperation are reported in the message.

System Action: The server process is ended andserver operation continues.

User Response: No action is required. An authorizedadministrator can issue the DELETE FILESPACEcommand to delete remaining objects in the file space.

ANR0806I DELETE FILESPACE filespace namecomplete for node node name: number ofobjects objects deleted.

Explanation: A server process deleting file space datafor the node specified has completed. The total numberof objects deleted is reported in the message.



ANR0811I Inventory client file expiration started asprocess process ID.

Explanation: The server has started roll-off processingto remove expired client backup and archive file copies,based on the management class policy that is bound tothe files. The copy group retention and versionparameters for each file’s copy group are used by theserver to determine if copies are to be deleted from theserver. The expiration process was started as processnumber process ID, and may be queried or canceledwith the QUERY PROCESS or CANCEL PROCESScommands, respectively.

System Action: The expiration process is nowcancellable. Server operation continues.




ANR0812I Inventory file expiration process processID completed: examined number of objectsobjects, deleting number of backup objectsbackup objects, number of archive objectsarchive objects, number of DB backupvolumes DB backup volumes, and numberof recovery plan files recovery plan files.error count errors were encountered.

Explanation: Server roll-off processing has completed.The number of client objects examined and deleted,based on management class policy, are displayed in themessage. A total error count is also displayed. Thenumber of DB backup volumes deleted is based on thevalue specified on the SETDRMDBBACKUPEXPIREDAYS. The number ofrecovery plan files deleted is based on the valuespecified on the SET DRMRPFEXPIREDAYS. Serverroll-off processing deletes the DB backup volumes andrecovery plan files only if DRM is licensed on theserver and the volumes or plan files are created on theserver to server virtual volumes.

System Action: The roll-off process is ended andserver operation continues.

User Response: If the error count is not equal to 0,examine messages that may have been issued in theactivity log to determine the cause for the errors.

ANR0813I Inventory file expiration process processID canceled prior to completion:examined number of objects objects,deleting number of backup objects backupobjects, number of archive objects archiveobjects, number of DB backup volumes DBbackup volumes, and number of recoveryplan files recovery plan files. error counterrors were encountered.

Explanation: The inventory file expiration process wascanceled by an administrator. The number of objectsexamined and deleted prior to the cancelation arereported. A total error count is also displayed.

System Action: The server ends the file expirationprocess.


ANR0814I Expiration retry retry number of maximumretries in number of seconds seconds.

Explanation: Server roll-off processing hasencountered an error in attempting to remove expiredclient file copies from the server database. Theoperation will be tried again in the number of secondsindicated.

System Action: The server waits for the number ofseconds indicated and retries the file expirationoperation.

User Response: Expiration retry processing occurs

when the server database is full, the log is full, orsufficient server memory is not available to continueprocessing. Use the QUERY ACTLOG command to lookfor messages issued prior to this one that indicate thetype of error encountered. If the server is out ofdatabase space, issue the DEFINE DBVOLUME andEXTEND DB commands to add volumes to the serverdatabase and extend the database size. If the server isout of log space, issue the DEFINE LOGVOLUME andEXTEND LOG commands to add volumes to the serverlog and extend the log size. If the server is low onmemory, allocate additional storage to the server. Fordetails, issue HELP MEMORY to display theinformation online or see “Appendix A. AllocatingAdditional Server Memory”.

ANR0815I Expiration retry in progress.

Explanation: The server is retrying an operationduring client file roll-off processing. Expiration retryprocessing occurs when the server database is full, thelog is full, or sufficient server memory is not availableto continue processing.

System Action: The roll-off operation is retried.

User Response: Use the QUERY ACTLOG commandto look for messages issued prior to this one thatindicate the type of error encountered. If the server isout of database space, issue the DEFINE DBVOLUMEand EXTEND DB commands to add volumes to theserver database and extend the database size. If theserver is out of log space, issue the DEFINELOGVOLUME and EXTEND LOG commands to addvolumes to the server log and extend the log size. If theserver is low on memory, allocate additional storage tothe server. For details, issue HELP MEMORY to displaythe information online or see “Appendix A. AllocatingAdditional Server Memory”.

ANR0816I Expiration retry was successful.

Explanation: In accordance with management classpolicy, server roll-off processing has been successful inretrying a client file expiration.

System Action: Server roll-off processing continues.


ANR0818I Waiting to retry expiration because ofinsufficient resources.

Explanation: The server inventory expiration processis waiting to retry expiration processing that failedbecause of insufficient memory, database, or logresources on the server.

System Action: Server operation continues. Theexpiration processing is reattempted automatically.

User Response: Use the QUERY ACTLOG commandto examine messages issued prior to this one, whichindicated the resource that is not available to the



expiration process. Correct the shortage.


Explanation: This message is displayed in response toa QUERY PROCESS command, and indicates that aninventory expiration process has been canceled. Theprocess will end shortly.

System Action: The expiration process terminates andserver operation continues.


ANR0820I Sorting information for number objectshas been deleted.

Explanation: A background server process has deletedsorting information for number files from the serverdatabase. This process is started during initialization toremove any sorting information which is left over fromprevious export operations.

System Action: The actual backup or archive objectswere not deleted, but only information used to sortthese objects during the previous export operation.


ANR0821E Filespace identifier fsId is not valid.

Explanation: The identifier assigned for a filespace isout of range.

System Action: The file space is not added.


ANR0822I command: Filespace filespace name(fsId=filespace id) successfully renamedto new filespace name for node node name.

Explanation: The file space specified was renamed tothe new name specified for the node. This message isdisplayed in response to successful completion of theRENAME FILESPACE command.

System Action: The system renames the file space forthe node as indicated


ANR0823E command: Filespace filespace name cannotbe renamed to new filespace name, afilespace with this name already existsfor node node name.

Explanation: The file space name specified as a targetname for the command was found to already exist forthe node specified. The command fails.

System Action: Server operation continues, thecommand fails.

User Response: Reissue the command with a differenttarget filespace name

ANR0824I Delete Filespace filespace name(space-managed data) for node node namestarted.

Explanation: A background server process has started(on the server) to delete space-managed objects in thespecified file space belonging to the node indicated. If afile space name is not included in the message, then thespace-managed objects for all file spaces that belong tothe node are deleted.

System Action: The background process deletesspace-managed objects for the specified file space whileserver operation continues.


ANR0826I DELETE FILESPACE filespace name fornode node name encountered atransaction failure.

Explanation: A background server process that hasbeen deleting file space data for the indicated nodeencountered a transaction failure.

System Action: The server process is retried if themaximum number of retry attempts have not beenexceeded.

User Response: Transaction failure usually indicatesthat a database deadlock was detected during file spacedeletion. These deadlock conditions are sometimesencountered when multiple file space deletionprocesses are running at the same time. No action isrequired unless the DELETE FILESPACE terminateswithout completing the deletion process (see messageANR0828).

Another possible cause is that the reported node andfilespace have a restartable restore session active orrestartable. To determine if this was the cause of thefailure, issue the command QUERY RESTORE. If thereported node and filespace have an outstandingrestartable restore session, either:

v wait to re-issue the DELETE FILESPACE commandafter this restartable restore has completed

v cancel the restartable restore session with theCANCEL RESTORE command

ANR0827I DELETE FILESPACE filespace name willbe retried for node node name.

Explanation: A file space deletion process for the nodeindicated is being retried because an error wasencountered.

System Action: The server process is retried.




ANR0828W DELETE FILESPACE filespace name fornode node name terminated beforecompletion due to transaction failure:number of objects objects deleted.

Explanation: A background server process that hasbeen deleting file space data for the indicated node isterminated prematurely because of transaction failure.The number of objects deleted before the operationended are reported in the message.


User Response: Termination of this process because oftransaction failure usually indicates that a databasedeadlock was detected during file space deletion. Thesedeadlock conditions are sometimes encountered whenmultiple file space deletion processes are running at thesame time. The command should be started againwhen fewer file space deletion processes are active. Anauthorized administrator can issue the DELETEFILESPACE command to delete remaining files in thefile space(s).

ANR0829E Command: Invalid combination of TYPEand DATA parameters.

Explanation: The specified command has been issuedwith an invalid combination of the TYPE and DATAparameters. DATA=IMAGES can only be specified ifTYPE=ANY or TYPE=BACKUP.

System Action: Server operation continues, but thecommand is not processed.

User Response: Issue the command and specify avalid combination of parameters.

ANR0830W Management class class name in domaindomain name used by node node name infile space filespace name is no longeractive, or no longer has a BACKUP copygroup: DEFAULT management classattributes will be used for expiration.

Explanation: During policy roll-off processing, theserver has found a client file copy whose managementclass or backup copy group no longer exists.

System Action: The server obtains the DEFAULTmanagement class for the specified domain and uses itsbackup copy group version and retention parameters todetermine if file copies need to be expired.

User Response: No action is required. A policyadministrator with authority over the specified domainmay use the DEFINE COPYGROUP, DEFINEMGMTCLASS, and ACTIVATE POLICY commands todefine and activate a policy set that contains definitionsfor the missing management class or copy group.

ANR0831W The DEFAULT management class classname in domain domain name does nothave a BACKUP copy group: GRACEPERIOD will be used for expiration.

Explanation: During policy roll-off processing, theserver found a client file copy whose management classor backup copy group no longer exists. The DEFAULTmanagement class for the indicated policy domain doesnot contain a backup copy group; therefore, the serveruses the GRACE PERIOD retention value defined forthe specified policy domain to determine if client filecopies need to be expired and removed from the serverdatabase.

System Action: The server obtains the GRACEPERIOD retention values for the specified domain andthen determines if backup file copies need to beexpired.

User Response: No action is required. A policyadministrator with authority over the specified domainmay use the DEFINE COPYGROUP, DEFINEMGMTCLASS, and ACTIVATE POLICY commands todefine and activate a policy set that contains definitionsfor the missing management class or backup copygroup.

ANR0832W Management class class name in domaindomain name used by node node name infilespace filespace name is no longeractive, or no longer has an ARCHIVEcopy group: DEFAULT managementclass attributes will be used forexpiration.

Explanation: During policy roll-off processing, theserver found a client file copy whose management classor archive copy group no longer exists.

System Action: The server obtains the DEFAULTmanagement class for the specified domain and uses itsarchive copy group retention parameter to determine iffile copies need to be expired.

User Response: No action is required. A policyadministrator with authority over the specified domainmay use the DEFINE COPYGROUP, DEFINEMGMTCLASS, and ACTIVATE POLICY commands todefine and activate a policy set that contains definitionsfor the missing management class or copy group.

ANR0833W The DEFAULT management class classname in domain domain name does nothave an ARCHIVE copy group: GRACEPERIOD will be used for expiration.

Explanation: During policy roll-off processing, theserver found a client file copy whose management classor archive copy group no longer exists. The DEFAULTmanagement class for the indicated policy domain doesnot contain an archive copy group; therefore, the serveruses the GRACE PERIOD retention value defined for



the specified policy domain to determine if client filecopies need to be expired and removed from the serverdatabase.

System Action: The server obtains the GRACEPERIOD retention values for the specified domain andthen determines if archive file copies need to beexpired.

User Response: No action is required. A policyadministrator with authority over the specified domainmay use the DEFINE COPYGROUP, DEFINEMGMTCLASS, and ACTIVATE POLICYSET commandsto define and activate a policy set that containsdefinitions for the missing management class or backupcopy group.

ANR0834W Inventory client file expiration cannotstart because of insufficient memory -will retry in number of seconds seconds.

Explanation: The server inventory expiration processis pausing to retry an operation that failed becausesufficient memory is not available on the server.

System Action: Server operation continues; theexpiration process will be retried after the stated delay.


ANR0835W Management class class name in domaindomain name is no longer active, or nolonger has a BACKUP copy group, or nolonger has an ARCHIVE copy group.DEFAULT management class used todelete number of backup files backup filesand number of archive files archive files.Retention grace period used to deletenumber of backup files backup files andnumber of archive files archive files.

Explanation: During policy roll-off processing, theserver found a management class or backup copygroup or archive copy group that no longer exists.When a management class or backup copy group nolonger exists, the number of backup client file copiesthat have been deleted using the default managementclass or the retention grace period is displayed in themessage. When a management class or archive copygroup no longer exists, the number of archive clientfiles that have been deleted using the defaultmanagement class or the retention grace period isdisplayed in the message.

System Action: The server obtains the DEFAULTmanagement class for the specified domain and uses itsbackup copy group or archive copy group version andretention parameters to determine if file copies need tobe expired. If, however, the needed backup copy groupor archive copy group does not exist in the DEFAULT

management class, the server will use the retentiongrace period for the domain.

User Response: No action is required. This message isonly issued when expiration processing has beenstarted with the QUIET option to suppress detailedmessages. Expiration processing can be started withoutthe QUIET option to see the detailed messages whichwill indicate specific node and filespaces and willfurther distinguish between backup and archive copygroups. A policy administrator with authority over thespecified domain may use the DEFINE COPYGROUP,DEFINE MGMTCLASS, and ACTIVATE POLICYcommands to define and activate a policy set thatcontains definitions for the missing management classor copy group.

ANR0836W No query restore processing sessionsession id for node node name and filespacename failed to retrieve file high-level filenamelow-level file name - file beingskipped.

Explanation: The no query restore processing for thesession listed relating to the specified node name andfilespace failed to retrieve the specified file. An erroroccurred while retrieving this file so it will be skipped.

System Action: The no query restore operationcontinues.

User Response: Determine the cause of the file retievefailure and correct it. After this situation is correct, theclient can do a restore of the specific file that wasskipped.

ANR0837I The expire inventory running durationof number of minutes minutes hasexpired. The expire inventory processends.

Explanation: An ADSM Administrator or scheduleissued the command EXPIRE INVENTORY ...DURATION=xxx, where xxx is the number of minutesfor the expire inventory process to run. That xxxnumber of minutes has been reached, so the expireinventory process ends.

System Action: The expire inventory process ends.


ANR0838I Pass pass of group table conversionprocessing beginning.

Explanation: The contents of the group informationtables needs to be updated before the server can fullyinitialize. This is an informational message indicatingthat processing has begun for a particular pass of theconversion.

System Action: Server processing continues.




ANR0839I Pass pass of group table conversionprocessing complete.

Explanation: The contents of the group informationtables have been successfully converted for thespecified pass.

System Action: If all passes of the conversion arecomplete, server processing continues. If not, additionalpasses will be performed.


ANR0840I Converting group table information fornode node.

Explanation: The group table information for thedisplayed node is being converted.

System Action: Server processing continues


ANR0841I Conversion for node Node name will beundone.

Explanation: The indicated node is converted. Thisstatus will be undone before the update archiveoperation can be performed.



ANR0842E Command: the update archive operationfor node node name did not complete(result).

Explanation: The update archive operation for thespecified node did not complete.

System Action: The update archive operation ends.Server processing continues.

User Response: Check previous error messages.

ANR0843I Command: the update archive operationfor node node name completedsuccessfully.

Explanation: The update archive operation for thespecified node completed successfully.

System Action: The update archive operation ends.


ANR0844E Command: node name is not abackup-archive node.

Explanation: The specified node name is not abackup-archive node.

System Action: Processing fails for the command.Server operation continues.

User Response: Reissue the command with a validnode name.

ANR0845E Undo conversion processing for nodenode name did not complete (result).

Explanation: UNDO ARCHCONVERSION was issuedfor the specified node. The specified error occurred.


User Response: Check previous error messages.

ANR0847I CLEANUP BACKUPGROUPS evaluatednumber of groups groups, and deletedgroups deleted orphan groups withmembers deleted members deleted.

Explanation: The CLEANUP BACKUPGROUPS hasfinished processing, and has deleted the specifiednumber of orphan groups and members.



ANR0848W Expiration failed to delete file type filefile name for node node name andfilespace filespace name - file will beskipped.

Explanation: The expiration process was unable todelete the indicated file. The file will be skipped byexpiration.

System Action: The expiration process continues.

User Response: Re-try expiration to determine if thecause of the deletion failure was an intermittentproblem or if it is a permanent problem. If after asubsequent expiration attempt the file still is notdeleted, please contact your service representative.

ANR0849E Command: Not permitted for node NodeName - node of type SERVER.

Explanation: The indicated DELETE FILESPACEprocess is not started because the node specified is ofNODETYPE=SERVER. A DELETE FILESPACE mayonly be processed for nodes of this type with theTYPE=SERVER parameter specified.

System Action: The DELETE FILESPACE command isended and server processing continues.

User Response: If this filespace must be deleted,Reissue the command with the TYPE parameter set toTYPE=SERVER. Please use caution when using theTYPE=SERVER parameter as this can impact theavailability of data for the server that owns these files.



ANR0850E Command: Cannot Start process nameProcess.

Explanation: The indicated DELETE FILESPACEprocess cannot be started on the server.


User Response: This usually indicates that sufficientserver memory is not available on the server. Allocateadditional storage to the server. For details, issue HELPMEMORY to display the information online or see“Appendix A. Allocating Additional Server Memory”.

ANR0851E Cannot start delete file space thread fornode node name.

Explanation: The indicated DELETE FILESPACEprocess cannot be started on the server. Sufficientmemory on the server may not be available.



ANR0852E Command: No matching file spacesfound for node node name.

Explanation: The server did not find any file spacesfor the node indicated matching the names specified inthe command.

System Action: The server ends the command.

User Response: Enter the command with file spacenames that refer to defined file spaces for the specifiednode. Note that file space names are case sensitive.Enter them by using exactly the same uppercase andlowercase characters that match the file space namedefined on the server. Use the QUERY FILESPACEcommand to determine which file spaces are definedfor a node on the server.

ANR0853E Transaction failed in file space deletion,DELETE FILESPACE process aborted.

Explanation: A database transaction fails while theserver is deleting file space data.

System Action: The server ends the file space deletionprocess.


ANR0854E Inventory file space query failure,DELETE FILESPACE process aborted.

Explanation: The server encounters an error inquerying the inventory database during a file spacedeletion process.



ANR0855E Server LOG space exhausted, DELETEFILESPACE process aborted.

Explanation: Insufficient server log space has beenencountered during file space deletion processing.


User Response: To increase the amount of log spaceavailable to the server, an authorized administrator canadd log volumes by using the DEFINE LOGVOLUMEcommand, and can extend the size of the log by usingthe EXTEND LOG command.

ANR0856E Server database space exhausted,DELETE FILESPACE process aborted.

Explanation: Insufficient server database space hasbeen encountered during file space deletion processing.


User Response: To increase the amount of databasespace available to the server, an authorizedadministrator can add log volumes using the DEFINEDBVOLUME command and can extend the size of thedatabase using the EXTEND DB command.

ANR0857E Data storage session failure, DELETEFILESPACE process aborted.

Explanation: The server encounters an error accessingdata storage during file space deletion processing.





ANR0858E Inventory object search failure, DELETEFILESPACE process aborted.

Explanation: The server encounters an error accessingthe inventory database during file space deletionprocessing.



ANR0859E Data storage object erasure failure,DELETE FILESPACE process aborted.

Explanation: The server encounters an error inremoving file copies from data storage during file spacedeletion processing.



ANR0860E Expiration process process ID terminateddue to internal error: examined number ofobjects objects, deleting number of backupobjects backup objects, number of archiveobjects archive objects, number of DBbackup volumes DB backup volumes, andnumber of recovery plan files recovery planfiles. error count errors were encountered.

Explanation: The server encounters an internal errorduring file expiration processing. The number of filesexamined and deleted prior to the error are reported. Atotal error count is also displayed.

System Action: The server ends the expirationprocess.


ANR0861E Transaction failed in expiration,inventory expiration aborted.

Explanation: The server encounters a databasetransaction failure during policy roll-off processing.

System Action: The server ends roll-off processing.


ANR0862E Expiration processing suspended -insufficient memory.

Explanation: The server ends policy roll-off processingbecause sufficient server memory is not available.

System Action: The server ends policy roll-offprocessing and server operation continues.


ANR0863E Expiration processing suspended -insufficient DB space.

Explanation: The server ends policy roll-off processingbecause sufficient server database space is notavailable.


User Response: To increase the amount of databasespace available to the server, an authorizedadministrator can add database volumes by using theDEFINE DBVOLUME command and can extend thesize of the database using the EXTEND DB command.

ANR0864E Expiration processing suspended -insufficient LOG space.

Explanation: The server ends policy roll-off processingbecause sufficient server log space is not available.


User Response: To increase the amount of log spaceavailable to the server, an authorized administrator canadd log volumes by using the DEFINE LOGVOLUMEcommand and can extend the size of the log by usingthe EXTEND LOG command.

ANR0865E Expiration processing failed - internalserver error.

Explanation: Server retry processing during policyroll-off fails.

System Action: The server ends policy roll-offprocessing.

User Response: Examine the server messages issuedprior to this message to determine the source of the



error. Issue the QUERY ACTLOG command to view theactivity log and search for messages. If the server is outof database space, issue the DEFINE DBVOLUME andEXTEND DB commands to add volumes to the serverdatabase and extend the database size. If the server isout of log space, issue the DEFINE LOGVOLUME andEXTEND LOG commands to add volumes to the serverlog and extend the log size. If the server is low onmemory, allocate additional storage to the server. Fordetails, issue HELP MEMORY to display theinformation online or see “Appendix A. AllocatingAdditional Server Memory”. If the error cannot beisolated and resolved, contact your servicerepresentative.

ANR0866E Expiration processing retries failed - nosuccess after maximum retries retries.

Explanation: Server policy roll-off processing endsbecause retry processing has not been successful inexpiring client file copies from the server database.


User Response: Examine the server messages issuedprior to this message to determine the source of theerror. Issue the QUERY ACTLOG command to view theactivity log and search for messages. If the server is outof database space, issue the DEFINE DBVOLUME andEXTEND DB commands to add volumes to the serverdatabase and extend the database size. If the server isout of log space, issue the DEFINE LOGVOLUME andEXTEND LOG commands to add volumes to the serverlog and extend the log size. If the server is low onmemory, allocate additional storage to the server. Fordetails, issue HELP MEMORY to display theinformation online or see “Appendix A. AllocatingAdditional Server Memory”. If the error cannot beisolated and resolved, contact your servicerepresentative.

ANR0867E Unable to open policy domain for nodenode name during expiration processing.

Explanation: Policy roll-off processing on the serverencounters an error while obtaining policy informationrelated to the specified node.

System Action: The server ends roll-off processingand server operation continues.


ANR0868E Cannot find management class name forID management class ID.

Explanation: Policy roll-off processing on the serverencounters an error while obtaining policy information.



ANR0869E Cannot find policy domain for nodenode ID.

Explanation: Policy roll-off processing on the serverencounters an error while obtaining policy informationrelated to the specified node.



ANR0870E Cannot find node name for node nodeID.

Explanation: Policy roll-off processing on the serverencounters a database error in obtaining informationfor a client node.



ANR0871E Cannot find file space name for nodenode ID, file space file space ID.

Explanation: Policy roll-off processing on the serverencounters a database error in obtaining informationfor a client node.


User Response: Examine the server messages issuedprior to this message to determine the source of theerror. Issue the QUERY ACTLOG command to view theactivity log and search for messages. If the error cannot



be isolated and resolved, contact your servicerepresentative.

ANR0872E Grace Period retention for domaindomain name could not be obtained.

Explanation: Policy roll-off processing on the serverencounters a database error in obtaining GRACEPERIOD values for the specified policy domain.



ANR0873E Invalid copy type encountered inexpiring files: copytype ID

Explanation: Policy roll-off processing on the serverencounters a database error in obtaining copy groupinformation.



ANR0874E Backup object object.ID not found duringinventory processing.

Explanation: Inventory processing on the serverencounters a database error in obtaining backupinformation in data storage.

System Action: The server ends roll-off processing, orclient session(s) and server operation continues.


ANR0875E Archive object object.ID not foundduring expiration processing.

Explanation: Policy roll-off processing on the serverencounters a database error in obtaining archiveinformation in data storage.



ANR0876E Data storage erasure failed duringexpiration processing.

Explanation: Policy roll-off processing on the serverencounters a database error while deleting informationfrom data storage.



ANR0877E Copy type not backup for objectobject.ID.

Explanation: Policy roll-off processing on the serverencounters a database error in accessing inventoryinformation.



ANR0878E Entry for backup object object.ID notfound.






ANR0879E Error opening inventory file spacequery.




ANR0880E Filespace command: No matching filespaces.

Explanation: The server did not find any file spacenames matching the specifications entered in thefilespace command.


User Response: Use the QUERY FILESPACEcommand to determine which file spaces are definedon the server. Note, that file space names are casesensitive. Reissue the file space command and specifythe proper file space name (in proper case).

ANR0881E Policy Error : the GRACE PERIODarchive retention value could not beobtained for domain domain ID duringclient inventory processing.

Explanation: The server encounters an internal errorin accessing policy information.



ANR0882E Policy Error: Unable to open policydomain for node node name during clientinventory query processing.

Explanation: The server encounters an internal errorin accessing policy information.

System Action: The client operation is ended andserver operation continues.


ANR0883E Cannot obtain node name for node nodeID.

Explanation: The server encounters an internal errorin accessing client node information.



ANR0884E Error code during deletion of sortinginformation for number objects.

Explanation: A background server processencountered an internal error after deleting sortinginformation for number files from the server database.This process is started during initialization to removeany sorting information which is left over fromprevious export operations.

System Action: The backup or archive objects werenot deleted. Only the information used to sort theseobjects during the previous export operation wasdeleted. The background process was terminated beforeall sorting information had been deleted. The systemwill not perform further export processing of file datauntil this problem has been resolved.

User Response: Examine the server messages issuedprior to this message to determine the source of theerror. Issue the QUERY ACTLOG command to view theactivity log and search for messages. Then restart theserver. If the error cannot be isolated and resolved,contact your service representative.

ANR0885I Import command: Processing managementclass management class name for domaindomain name and policy set policy setname as management class newmanagement class name.

Explanation: The background import process toservice the command import command is currentlyprocessing the policy information for management classmanagement class name in domain domain name andpolicy set policy set name. The management class isimported under the name new management class name.During import processing, management classes definedas either DEFAULT or GRACE_PERIOD must berenamed so that the management class does not conflictwith existing server policy conventions. Importprocessing is then able to import file data by using therenamed management class.

System Action: Import processing for the commandcontinues.

User Response: None. However, an administrator maywant to examine the policy definitions for newmanagement class name so they are aware of themanagement classes that may be used if the policy setcontaining this management class is activated.



ANR0886E Management class class name in domaindomain name used by node node name infile space filespace name has no BACKUPcopy group with id copy group id;Expiration will not be performed forfiles from this node and filespace thatare bound to this management class andcopy group id.

Explanation: During policy roll-off processing, theserver finds a client file copy with a management classor a backup copy group that no longer exists.

System Action: The server skips the files in error.

User Response: For programming support, contactyour service representative.

ANR0887E Management class class name in domaindomain name used by node node name infile space filespace name has noARCHIVE copy group with id copy groupid; Expiration will not be performed forfiles from this node and filespace thatare bound to this management class andcopy group id.

Explanation: During policy roll-off processing, theserver finds a client file copy with a management classor an archive copy group that no longer exists.

System Action: The server skips the files in error.


ANR0888E SQL commands cannot be issued fromthe server console.

Explanation: An SQL command was issued from theserver console. SQL commands cannot be issued fromthe server console because they may require a longtime complete and the server console should beavailable to control other server functions.

System Action: The server ignores the command andcontinues processing.

User Response: Issue the SQL command from anadministrative client.

ANR0889E The server is not licensed for CentralAdministration functions. This includesthe ability to issue SQL commands.

Explanation: An SQL command was issued but theserver is not licensed to support Central Administrativefunctions, including SQL query support.


User Response: If you have purchased the CentralAdministration license, use the REGISTER LICENSE

command to enable the license on the server. If youhave not purchased the license and wish to do so,contact your service representative.

ANR0890I Export/import command: Processingoptionset optionset name.

Explanation: The background export or importprocess to service the command export/import commandis currently processing optionset definition information.



ANR0891I Export/import command: Copied numberoptionset definitions.

Explanation: The background export or importprocess to service the command export/import commandcopies number client optionset definitions from theserver database to export media or from export mediainto the server database. Data is not moved ifPreview=Yes is specified in the command export/importcommand.



ANR0892I Export command: No matching optionsetsfound for exporting.

Explanation: The background export process does notfind any client optionsets for export command.

System Action: The export process continues and nooptionsets from the server.


ANR0893I Are you sure that you want to accept thecurrent system date as valid ?

Explanation: This message is displayed when theACCEPT DATE command has been issued to confirmthat you want to accept the date on the system asvalid.

System Action: The command waits for you toconfirm the action.

User Response: Specify Yes if you want to accept thesystem date as valid, or No if you do nt want toexecute the command.

ANR0894I Current system has been accepted asvalid.

Explanation: This messages is displayed when theACCEPT DATE command has been issued and the datehas been accepted as valid by the server.



System Action: The current system date is accepted asvalid by the server


ANR0895E Command: Cannot Start process nameProcess.

Explanation: The indicated process cannot be startedon the server.

System Action: The specified command is ended andserver processing continues.


ANR0897I Node Node name has (Filespace count)filespaces. Command has resetdescriptions for (Directory count)directories and (File count) files. (Deletecount) directories were deleted.

Explanation: The indicated update archive operationhas completed processing a node to reset thedescriptions for directories and files. The informationdisplayed includes the number of filespaces processed,the number of directories and files for whichdescriptions were reset, and the number of directoriesthat were deleted because they had the same pathspecification.



ANR0898I Node Node name has (Filespace count)filespaces with (Directory count)directories and (File count) files. Thereare (Unique count) directories withdifferent path specifications and (Notreferenced) not referenced by files. Thenode is converted (Conversion status).

Explanation: The indicated update archive operationhas completed processing a node for the UPDATEARCHIVE SHOWSTATS command. The informationdisplayed includes counts for the filespaces, directoriesand files.



ANR0899I Node Node name has (Filespace count)filespaces. Command has deleted(Directory count) directories and found(File count) new files with no directories.

Explanation: The indicated update archive operationhas completed processing a node to delete directories.

The information displayed includes the number offilespaces processed, the number of directories thatwere deleted and the number of files that, now, do nothave directories.



ANR0900I Processing options file filespec.

Explanation: At server initialization, the server isreading the server options file whose name is shown inthe message.

System Action: The server reads and processes theoptions in this file.


ANR0901W Invalid option statement found in filefilespec.

Explanation: While processing the server options filenamed, the server has encountered an invalidstatement. The invalid statement type is shown in themessage. The lines following this message providemore information.

System Action: The server ignores the statement inerror. Server initialization continues. The default valueis used for any missing or ignored options.

User Response: Ignore the error, or use a text editor tocorrect the error and restart the server.

ANR0902W Unsupported keyword found in filefilespec.

Explanation: While processing the server options filenamed, the server has encountered an invalid keywordon an option statement. The lines following thismessage provide more information.

System Action: The server ignores the optionstatement in error. Server initialization continues. Thedefault value is used for any missing or ignoredoptions.


ANR0903W Excessive option statement found in filefilespec.

Explanation: While processing the specified serveroptions file, the server has encountered more of thenamed statement type than can be processed.

System Action: The server ignores the extra statement.Server initialization continues.




ANR0904W Duplicate option statement found in filefilespec.

Explanation: While processing the server options filenamed, the server has encountered a duplicatestatement of the type shown.

System Action: The server ignores the duplicatestatement. Server initialization continues.


ANR0905W Options file filespec not found.

Explanation: At server initialization, the server isunable to locate the server options file named.

System Action: The server uses the default values forall options. Server initialization continues.

User Response: If the default values are acceptable,ignore the error. Otherwise, move a valid serveroptions file to the proper location, rename a validoptions file to the proper name, or use a text editor tobuild the proper server options file, and then restart theserver.

ANR0909E Insufficient memory to process optionsfile.

Explanation: At server initialization, the server isunable to process the server options file due toinsufficient memory.

System Action: Server initialization ends.

User Response: Restart the server with more memoryavailable. Refer to the Administrator’s Guide for yourparticular platform.

ANR0910W Archive entries for nodeName are alreadyconverted.

Explanation: Archive entries for nodeName havealready been converted to the description tables. Theywill not be converted again.


User Response: To force the reconversion of thearchive entries for nodeName, use the FORCE=Yesoption to the CONVERT ARCHIVE command.

ANR0911I Archive conversion processing for nodename completed successfully. Thedescription tables have description countdescriptions, directory count directories,file count and files and object set countobject sets.

Explanation: CONVERT ARCHIVE for the specifiednode completed successfully. The node can now query

for archive objects specifying a non-wildcardeddescription.



ANR0912I Undo conversion processing for nodenode name completed successfully. Thenode is no longer converted.

Explanation: UNDO ARCHCONVERSION was issuedfor the specified node. The node will no longer use thearchive description tables.



ANR0913E Archive conversion processing for nodenode name did not complete (result).

Explanation: Archive conversion for the indicatednode did not complete because of the specified result.

System Action: Archive conversion ends. Serverprocessing continues.

User Response: Check previous messages for errorconditions.

ANR0914E Diagnostic(ID): a request failed becauseobject (object name), size (size), exceedsthe maximum size of maximum size.

Explanation: The size of the specified object exceedsthe maximum size defined for that object. The servercannot handle the new object.


User Response: Determine why the new object’slength exceeds the maximum specified for the object.Reduce the length of the object.

ANR0915E Unable to open language language namefor message formatting.

Explanation: The server is unable to open thespecified message repository.

System Action: Server initialization continues with thedefault message repository.

User Response: Ensure that a valid language isspecified in the LANGUAGE option of the serveroptions file. If a change is made to the options file,restart the server to activate changes.



ANR0916I Product Name distributed by Company isnow ready for use.

Explanation: The server has completed startupprocessing and is now ready for use.



ANR0917W Session session number for node nodename (client platform) - in domain domainname failed because of policy length.

Explanation: The client cannot handle very longpolicies.

System Action: The client operation is ended andserver operation continues.

User Response: Upgrade the client to the latest level,or activate a policy set with fewer management classes.

ANR0918E Inventory operation for node node nameterminated - lock conflict.

Explanation: During the indicated operation, theserver needs to obtain a lock that is not available.

System Action: The indicated operation ends.

User Response: Restart the operation.

ANR0919E Filespace name fsName with lengthlength was encountered for nodes nodelist.

Explanation: The specified filespace name was foundfor the nodes in the list. The name is not allowed. Theerror may occur while processing an administrativecommand or client request.


User Response: If the error occurs during processingfor an administrative command such as EXPORTNODE or RENAME FILESPACE, rename the filespacefor the nodes in the list using a valid name. If foundwhile processing a client request, contact your servicerepresentative.

ANR0920I Tracing is now active to standardoutput.

Explanation: In response to a TRACE STARTcommand, server trace records are being written to thestandard output destination (usually the serverconsole).



ANR0921I Tracing is now active to file file spec.

Explanation: In response to a TRACE STARTcommand, server trace records are being written to thefile named.



ANR0922I Trace ended.

Explanation: In response to a TRACE END command,server trace records are no longer being written.



ANR0923E Tracing is inactive.

Explanation: A TRACE END command has beenentered, but tracing is not active.

System Action: The command is ignored.

User Response: If tracing is desired, use the TRACEENABLE and TRACE START commands to activateserver tracing.

ANR0924E Tracing is already active to file file spec.

Explanation: A TRACE BEGIN command has beenentered, but tracing is already active to the file named.


User Response: If the current trace output file isacceptable, no action is required. Otherwise use theTRACE END command to stop tracing and then reissuethe TRACE BEGIN command as desired.

ANR0925E Tracing is already active to standardoutput.

Explanation: A TRACE BEGIN command has beenentered, but tracing is already active to the standardoutput destination (usually the server console).


User Response: If the current trace output destinationis acceptable, no action is required. Otherwise use theTRACE END command to stop tracing and then reissuethe TRACE BEGIN command as desired.

ANR0926E Missing or invalid TRACE commandparameter.

Explanation: The TRACE command issued containsan invalid parameter, or is missing a requiredparameter.




User Response: Reissue the command with the properparameters.

ANR0927E Unknown trace class keyword - class.

Explanation: A TRACE ENABLE command has beenentered which specifies an unknown trace class.


User Response: Reissue the TRACE command withthe correct class.

ANR0928E Unable to open trace file file spec forappending.

Explanation: A TRACE BEGIN command specifies anoutput file, but the server cannot write to that file.


User Response: Check the file for proper accesspermissions, or reissue the TRACE commandspecifying a different output file.

ANR0929E Insufficient memory to activate tracing.

Explanation: A TRACE BEGIN command has beenentered, but the server has insufficient memoryavailable to activate tracing.


User Response: If tracing is required, make morememory available to the server then restart the server.

ANR0936E Session session ID for session name failedsending verb verb name because clientnot able to handle extended qualifierattribute.

Explanation: A server was going to send the reportedverb for the indicated session but was not able to sendit. The verb could not be sent to the client because itcontains extended information about the low-levelqualifier. The extended low-level qualifier is used tostore names up to 512 bytes in length. The client thatthis verb was supposed to be sent to does not supportthe extented low-level qualifier information.

System Action: The send of the verb to the reportedsession fails and this server operation will fail andreport a communication error.

User Response: The client session reported needs tohave the installed client upgraded to TSM version 5.1.5or higher in order to support the extended low-levelqualifier.

ANR0937I Expiration process process ID is ending.

Explanation: The expiration process referenced isending either because it has been cancelled or becauseit has completed the necessary actions. This message isonly issued in the case where expiration was processinga long-running operation, such as deleting a group ofrelated files (for example, a backup group). Thismessage indicates the time when the long-runningoperation ended.



ANR0939E Error error code occurred while locatingbase object (baseIdHi.baseIdLo) for subfile(subfileIdHi.subfileIdLo): Node node name,File space filespace name, Type file type,File name file name.

Explanation: Export processing did not find the baseobject for the specified subfile. Export processing doesnot continue.

System Action: Export processing stops. Serveroperation continues.

User Response: Audit the database to correct theentries.

ANR0940I Cancel request accepted for processprocess ID.

Explanation: A CANCEL PROCESS command hasbeen entered for the specified process. Some processeswill experience a delay before they terminate. Thisdelay may be lengthy for processes that involve remotedata movement.



ANR0941I Command: Cancel for process process IDis already pending.

Explanation: A CANCEL PROCESS command hasbeen entered for the specified process, but a cancel isalready pending for that process.

System Action: The server ignores the command.


ANR0942E Command: Process process ID cannot befound.

Explanation: A CANCEL PROCESS command hasbeen entered for the specified process, but the processis not active. Either the process has already ended orthe wrong process number has been entered.




User Response: If the wrong process number has beenentered, reissue the command with the correct processnumber.

ANR0943E Command: Process process ID could not becanceled.

Explanation: A CANCEL PROCESS command hasbeen entered for the specified process, but the processspecified is an automatic process, such as migration orreclamation, that cannot be canceled.



ANR0944E Command: No active processes found.

Explanation: A QUERY PROCESS command has beenentered, and no processes are active.



ANR0945W DiagnosticID: Transaction transaction IDwas aborted for process process ID.

Explanation: An error is detected during transactioncommit for the specified process. This message shouldbe preceded by other messages that give additionalinformation about the failed transaction.



ANR0946E Archive processing fails: ObjectobjIdHi.objIdLo not found.

Explanation: Archive processing fails because thespecified object was not found. An archive request iscompleted in stages. The object may have been deletedby an archive delete request, delete filespace orexpiration that began and completed between thesestages.

System Action: System processing continues.

User Response: Check the client log for error andretry messages. Reissue the archive request if the retryfailed.

ANR0947E Error writing to trace file file spec.

Explanation: An error occurred while writing to thespecified trace file.

System Action: Trace is disabled.

User Response: Check the file for proper access

permissions, or for the out of space issue for the tracefile. Once this is corrected, reissue the TRACE BEGINcommand, specifying either the same or a differentoutput file.

ANR0948I Command: the update archive operationfor node Node name has started asbackground process process ID.

Explanation: An update archive operation has startedunder the indicated background server process with theindicated process identifier.



ANR0949I Command: the update archive operationfor node Node name has started asforeground process process ID.

Explanation: An update archive operation has startedunder the indicated foreground server process with theindicated process identifier.



ANR0950I Command: the update archive operationfor node Node name has been cancelled.

Explanation: The indicated update archive operationwas cancelled.

System Action: The update archive operation ends.Server processing continues.

User Response: No action is required. An authorizedadministrator can re-issue the command at a later time,if appropriate.

ANR0951I Command: the update archive operationfor node Node name completedsuccessfully.

Explanation: An update archive operation completedsuccessfully.

System Action: The update archive operation ends.


ANR0959I Conversion of grouping table is percentdone percent complete.

Explanation: An internal data base table is beingconverted, and the conversion process is the indicatedamount complete.





ANR0960I Process process ID waiting for mountpoint in device class device class name.

Explanation: The process whose ID is shown hasbegun to wait for a mount point that can be used for avolume in the device class shown.

System Action: The process waits for the mount point.

User Response: Respond to any mount requests.

ANR0961I Process process ID waiting for multiplemount points in device class device classname.

Explanation: The process whose ID is shown hasbegun to wait for multiple mount points that can beused for a volume in the device class shown.

System Action: The process waits for the mountpoints.


ANR0962I Process process ID waiting for mountpoints in device classes device class nameand device class name.

Explanation: The process whose ID is shown hasbegun to wait for mount points that can be used for avolume in the two device classes shown.

System Action: The process waits for the mountpoints.


ANR0963I Process process ID waiting for mount ofinput volume volume name.

Explanation: The process whose ID is shown hasbegun to wait for the mount of the input volumeshown.

System Action: The process waits for the mount.


ANR0964I Process process ID waiting for mount ofoutput volume volume name.

Explanation: The process whose ID is shown hasbegun to wait for the mount of the output volumeshown.



ANR0965I Process process ID waiting for mount ofscratch volume.

Explanation: The process whose ID is shown hasbegun to wait for the mount of a scratch volume.



ANR0966I Process process ID waiting for access toinput volume volume name.

Explanation: The process whose ID is shown hasbegun to wait for availability of the input volumeshown.

System Action: The process waits for the volume tobecome available.


ANR0967I Process process ID waiting for access tooutput volume volume name.

Explanation: The process whose ID is shown hasbegun to wait for availability of the output volumeshown.

System Action: The process waits for the volume tobecome available.


ANR0969E The server database must be formattedand loaded or restored before the servercan be started.

Explanation: The server has been restarted aftertoleration of a zero bit mismatch error. In order to startthe server, you must recover the database with aprocess that includes a DSMSERV FORMAT. Performone of the following procedures. Either do these steps:

1. Format the volumes using DSMSERV FORMAT

2. Restore the database using DSMSERV RESTORE DB

Or do these steps:

1. Unload the database using DSMSERV UNLOADDB

2. Format the volumes using DSMSERV FORMAT

3. Load the database using DSMSERV LOADDDB

Note: Do not use DSMSERV DUMPDB on the databasefor this recovery.

System Action: Server initialization stops.

User Response: Perform one of the database recoveryactions.

ANR0980E The server database must be auditedwith FIX=YES before the server can bestarted.

Explanation: The server has been restarted after aDSMSERV LOADDB command processed a databaseimage that was known to have inconsistencies. In orderto bring the database back to a consistent state, youmust run the AUDITDB command.


User Response: Issue the DSMSERV AUDITDB



FIX=YES command. For complete details on thiscommand, refer to the Administrator’s Reference.

ANR0981E The server database must be restoredbefore the server can be started.

Explanation: The server has been restarted after anincomplete RESTORE DB. In order to start the server,you must restore to the database to a consistent stateusing the DSMSERV RESTORE DB command.


User Response: Issue the DSMSERV RESTORE DBcommand. For complete details on this command, referto the Administrator’s Reference.

ANR0982E The server database must be initializedbefore the database can be loaded.

Explanation: The server database must be initializedbefore it can be loaded with the LOADDB parameter,by issuing the DSMSERV LOADFORMAT command.The server database is not currently in the initializedstate.

System Action: Server LOADDB processing stops.

User Response: Issue the DSMSERV LOADFORMATcommand. For complete details on this command, referto the Administrator’s Reference.

ANR0983W The server database was recorded by adown-level version of the serverprogram. The UPGRADEDB parameteris required to start the server andautomatically upgrade the databasecontents to the current server version.Please refer to installation instructionsfor precautionary backup proceduresprior to doing this.

Explanation: At server startup, the server hasdiscovered that the database information was writtenby an earlier version of the server program and is notcompatible with this version. To automatically upgradethe server database to this version of the serverprogram, the UPGRADEDB parameter must bespecified when starting the server.

System Action: The server ends.

User Response: Refer to installation instructions forspecific information on precautionary measures thatyou may want to take to back up the database prior toupgrading it to the current server level. After you havetaken these measures, start the server and specify theUPGRADEDB parameter. This parameter only needs tobe specified once to start the server, and should NOTbe included in any automated programs that start theserver.

ANR0984I Process process ID for process name startedin the process state at process start time.

Explanation: The process whose ID is shown has beenstarted for the process indicated by the process namerunning in the indicated state.



ANR0985I Process process ID for process namerunning in the process state completedwith completion state completion state atprocess start time.

Explanation: A completion state of FAILURE indicatesthat the operation encountered an error condition orterminated before completion. A completion state ofSUCCESS indicates that the operation ran tocompletion, but in some situations may haveencountered and reported conditions that would affectthe outcome of the operation.


User Response: If the completion state is FAILURE,then review the activity log and the event log to try todetermine the cause of the failure. If the completionstate is SUCCESS, the activity log and the event log canstill be checked for warning messages regardingconditions that could have affected the operation.

ANR0986I Process process ID for process namerunning in the process state processeditems processed items for a total of bytesprocessed bytes with a completion stateof completion state at process start time.




ANR0987I Process process ID for process namerunning in the process state processeditems processed items with a completionstate of completion state at process starttime.

Explanation: A completion state of FAILURE indicatesthat the operation encountered an error condition or



terminated before completion. A completion state ofSUCCESS indicates that the operation ran tocompletion, but in some situations may haveencountered and reported conditions that would affectthe outcome of the operation.



ANR0988I Process process ID for process namerunning in the process state processedbytes processed bytes with a completionstate of completion state at process starttime.




ANR0989E The server database must be loaded orrestored before the server can be started.

Explanation: The server is restarted after theLOADFORMAT command is run. To start the server,you must load the database by issuing the DSMSERVLOADDB or the DSMSERV RESTORE DB command.


User Response: Issue the DSMSERV LOADDB orDSMSERV RESTORE DB command. For completedetails on these commands, refer to the Administrator’sReference.

ANR0990I Server restart-recovery in progress.

Explanation: The server has been restarted after a haltor system failure. If necessary, the server performsrecovery processing in order to bring the system backto a consistent state.

System Action: Server initialization continues.


ANR0991I server shutdown complete.

Explanation: In response to a HALT command, theserver or storage agent has completed its terminationprocessing.

System Action: The server or storage agent ends.


ANR0992I Server installation complete.

Explanation: The server installation procedure hascompleted successfully. The server is now available fornormal operation.

System Action: Server completes installationprocessing.


ANR0993I Server initialization complete.

Explanation: The server has been restarted after a haltor system failure. It is now ready to resume normaloperation.

System Action: Server completes initialization.


ANR0994W This server has not been properlyinstalled.

Explanation: The server was started for normaloperation, but had not yet been installed.


User Response: Install the server properly beforestarting it.

ANR0995W This version of the server program isdown-level with respect to theinformation recorded on disk; a newerversion of the program should be used.

Explanation: At server startup, the server hasdiscovered that the disk information was written by alater version of the server program. This version of theserver program should not be used.


User Response: Start a version of the server programthat is at the same level as the prior server programused.

ANR0996W The information on disk was recordedby a down-level version of the serverprogram; re-installation is required touse this version.

Explanation: At server startup, the server hasdiscovered that the disk information was written by an



earlier version of the server program and is notcompatible with this version.


User Response: Install this version of the server tobring the information up to the level of the programbeing used.

ANR1000I Migration process process ID started forstorage pool storage pool name.

Explanation: Because the high migration threshold forthe storage pool shown has been exceeded, a processhas been started to migrate files from the storage pool.

System Action: Data is moved from this storage poolto the next (target) pool.


ANR1001I Migration process process ID ended forstorage pool storage pool name.

Explanation: A migration process for the namedstorage pool ends. This action can occur because thelow migration threshold for the storage pool has beenreached or because there are no more nodes with filesto be migrated.



ANR1002I Migration for storage pool storage poolname will be retried in number of secondsseconds.

Explanation: Because of a problem encounteredattempting migration for the named storage pool,migration is delayed but will be retried after the timeperiod shown.

System Action: The server waits for the specifiedperiod and then retries migration for the storage pool.This delay applies to a single migration process. After anumber of unsuccessful retries, the server willautomatically cancel the process. If other migrationprocesses are executing for the named storage pool,these processes will continue migration.

User Response: If possible, correct the condition thathas caused delayed migration.

ANR1003I Migration retry delay ended; checkingmigration status for storage pool storagepool name.

Explanation: Because migration for the indicatedstorage pool had been delayed due to a problem, thesystem waited before retrying. The retry wait periodhas ended, and the system will now retry migration.

System Action: Migration processing for the storagepool resumes.


ANR1004I Server formatting complete, databaseready for loading.

Explanation: The server formatting procedure hascompleted successfully. The server is ready to beloaded by issuing the DSMSERV LOADDB or theDSMSERV RESTORE DB command.

System Action: Server completes formattingprocessing.

User Response: The DSMSERV LOADDB or theDSMSERV RESTORE DB command is required to loadthe database before the server will be ready for use. Forcomplete details on these commands, refer to theAdministrator’s Reference.

ANR1020W Migration process process ID terminatedfor storage pool storage pool name -process canceled.

Explanation: During migration for the indicatedstorage pool, a process performing the migration hasbeen canceled.

System Action: The migration process is terminated. Ifother migration processes are executing for the namedstorage pool, these processes will continue migration.


ANR1021W Migration process process ID terminatedfor storage pool storage pool name -storage media inaccessible.

Explanation: During migration for the indicatedstorage pool, a required volume could not be mounted.

System Action: The indicated migration process ends.The server waits for the retry period to expire and thentries the migration again. If other migration processesare executing for the named storage pool, theseprocesses will continue migration.


ANR1022W Migration process process ID terminatedfor storage pool storage pool name -excessive read errors encountered.

Explanation: During migration for the indicatedstorage pool, read errors occur that prevented themigration from continuing.


User Response: If possible, correct the cause of theread errors.



ANR1023W Migration process process ID terminatedfor storage pool storage pool name -excessive write errors encountered.

Explanation: During migration for the indicatedstorage pool, write errors occur that prevent themigration from continuing.


User Response: If possible, correct the cause of thewrite errors.

ANR1024W Migration process process ID terminatedfor storage pool storage pool name - datatransfer interrupted.

Explanation: During migration for the indicatedstorage pool, a data transfer operation was interruptedand could not be continued.


User Response: If possible, correct the cause of theinterruption.

ANR1025W Migration process process ID terminatedfor storage pool storage pool name -insufficient space in subordinate storagepool.

Explanation: During migration for the indicatedstorage pool, the server cannot move the data from thestorage pool, because there is not enough space on thenext storage pool to hold it.

System Action: The indicated migration process ends.The server waits for the retry period to expire and thentries the migration again.

User Response: Make more space available in the nextstorage pool, or use the UPDATE STGPOOL commandto change the next storage pool to one with more space.

ANR1026W Migration process process ID terminatedfor storage pool storage pool name -unable to move file to subordinatestorage pool due to exclusion by size.

Explanation: During migration for the indicatedstorage pool, the server cannot move the data from thestorage pool, because a file is larger than what isallowed on the next storage pool.

System Action: The indicated migration process ends.The server waits for the retry period to expire and then

tries the migration again. If other migration processesare executing for the named storage pool, theseprocesses will continue migration.

User Response: Use the UPDATE STGPOOLcommand to change the next storage pool maximumfile size or to change the next storage pool target.

ANR1027W Migration process process ID terminatedfor storage pool storage pool name -sufficient recovery log space is notavailable.

Explanation: During migration for the indicatedstorage pool, the server runs out of recovery log space.


User Response: If necessary, make more serverrecovery log space available.

ANR1028W Migration process process ID terminatedfor storage pool storage pool name -sufficient database space is notavailable.

Explanation: During migration for the indicatedstorage pool, the server runs out of database space.


User Response: If necessary, make more serverdatabase space available.

ANR1029W Migration process process ID terminatedfor storage pool storage pool name - lockconflict.

Explanation: During migration for the indicatedstorage pool, the server needs to obtain a lock that isnot available.


User Response: Wait for the server to retry themigration.

ANR1030W Migration process process ID terminatedfor storage pool storage pool name - threadresource not available.

Explanation: During migration for the indicatedstorage pool, the server cannot start a thread for themigration process.

System Action: The indicated migration process ends.



The server waits for the retry period to expire and thentries the migration again. If other migration processesare executing for the named storage pool, theseprocesses will continue migration.

User Response: Wait for the server to retry themigration. If the error persists, it may indicate ashortage of server memory.

ANR1031W Migration process process ID terminatedfor storage pool storage pool name -sufficient memory is not available.

Explanation: During migration for the indicatedstorage pool, there is not enough server memoryavailable.


User Response: If necessary, make more memoryavailable to the server.

ANR1032W Migration process process ID terminatedfor storage pool storage pool name -internal server error detected.

Explanation: During migration for the indicatedstorage pool, the server encounters an internal error.



ANR1033W Migration process process ID terminatedfor storage pool storage pool name -transaction aborted.

Explanation: During migration for the indicatedstorage pool, the server detected an error whileattempting to commit a transaction. This messageshould be preceded by other messages that giveadditional information about the failed transaction.


User Response: Check for additional messages andeliminate the condition that caused the failedtransaction.

ANR1034W Files stored on volume volume namecannot be migrated - volume is offlineor access mode is ″unavailable″ or″destroyed″.

Explanation: During migration, files on the indicatedvolume cannot be migrated either because the volumehas been varied offline or because of the volume’saccess mode.

System Action: The server continues migrationprocessing, but skips files stored on the indicatedvolume.

User Response: If necessary, use the VARY ON orUPDATE VOLUME command for this volume.

ANR1040I Space reclamation started for volumevolume name, storage pool storage poolname (process number process ID).

Explanation: The percentage of reclaimable space onthe volume shown has reached the reclaim percentagespecified for the storage group; as a result, data fromthe volume is moved to another volume so that thevolume can be reclaimed.

System Action: The server starts volume spacereclamation.


ANR1041I Space reclamation ended for volumevolume name.

Explanation: Space reclamation for the volume namedis complete.



ANR1042I Space reclamation for storage poolstorage pool name will be retried innumber of seconds seconds.

Explanation: Because of a problem encounteredattempting space reclamation for the named storagepool, reclamation stops but will be retried after thetime period shown. After a number of unsuccessfulretries, the process will be automatically cancelled.

System Action: The system waits for the specifiedperiod and then retries space reclamation for thestorage pool.

User Response: If possible, correct the condition thathas stopped reclamation.



ANR1043I Space reclamation retry delay ended;checking volume reclamation status forstorage pool storage pool name.

Explanation: Because space reclamation for theindicated storage pool had been stopped due to aproblem, the system waited before retrying. The retrywait period has ended, and the system can now retryspace reclamation.

System Action: Reclamation for the pool begins.


ANR1044I Removable volume volume name isrequired for space reclamation.

Explanation: During space reclamation processing, theserver determines that a removable volume is requiredin order to complete processing.

System Action: The server attempts to mount theremovable volume.

User Response: Respond to any mount request for theindicated volume.

ANR1059I Selective restore of NAS node nodename,file system file system, started as processprocess ID by administrator administrator.Specified files and/or directory treeswill be restored to destinationdestination.

Explanation: A restore is started for the indicated filesystem of a NAS node. The operation is initiated by theadministrator shown. Selected files and/or directorytrees specified by the administrator will be restored tothe indicated destination.

System Action: The indicated process is started.


ANR1060W Error initiating space reclamation forstorage pool storage pool name - lockconflict.

Explanation: While attempting to initiate spacereclamation for the indicated storage pool, the serverneeds to obtain a lock that is not available.

System Action: Space reclamation stops. The serverwaits for the retry period to expire and then tries thereclamation again.

User Response: Wait for the server to retry thereclamation.

ANR1061W Error initiating space reclamation forstorage pool storage pool name - sufficientmemory is not available.

Explanation: During an attempt to initiate spacereclamation for the indicated storage pool, there is notenough server memory available.



ANR1062W Error initiating space reclamation forstorage pool storage pool name - internalserver error detected.

Explanation: During an attempt to initiate spacereclamation for the indicated storage pool, an internalserver error is encountered.

System Action: Space reclamation stops. The serverwill wait for the retry period to expire and then triesthe reclamation again.


ANR1063I Full backup of NAS node nodename, filesystem file system, started as processprocess ID by administrator administrator.

Explanation: A full backup is started for the indicatedfile system of a NAS node. The operation is initiated bythe administrator shown.



ANR1064I Differential backup of NAS nodenodename, file system file system, startedas process process ID by administratoradministrator.

Explanation: A differential backup is started for theindicated file system of a NAS node. Only files thathave changed since the last full backup will beprocessed. The operation is initiated by theadministrator shown.



ANR1065I Restore of NAS node nodename, filesystem file system, started as processprocess ID by administrator administrator.A full image for this file system will berestored to destination destination.

Explanation: A restore is started for the indicated filesystem of a NAS node. The operation is initiated by the



administrator shown. The restore will be performedusing a full image of this file system. The file systemwill be restored to the indicated destination.



ANR1066I Restore of NAS node nodename, filesystem file system, started as processprocess ID by administrator administrator.A full image plus a differential imagefor this file system will be restored todestination destination.

Explanation: A restore is started for the indicated filesystem of a NAS node. The operation is initiated by theadministrator shown. The restore will be performedusing a full image plus a differential image of this filesystem. The file system will be restored to the indicateddestination.



ANR1067I Operation process process ID completed.

Explanation: The indicated operation completed.

System Action: The indicated process ends.


ANR1068W Operation process process ID terminated -process cancelled.

Explanation: During the indicated operation, abackground process was cancelled.



ANR1069E Operation process process ID terminated -insufficient number of mount pointsavailable for removable media.

Explanation: During the indicated operation, theserver could not allocate sufficient mount points for thevolumes required.



ANR1070E Operation process process ID terminated -write errors encountered.

Explanation: During the indicated operation, writeerrors prevent the operation from continuing.


User Response: If possible, correct the cause of the

errors and restart the operation.

ANR1071E Operation process process ID terminated -read errors encountered.

Explanation: During the indicated operation, readerrors prevent the operation from continuing.


User Response: If possible, correct the cause of theerrors and restart the operation.

ANR1072E Operation process process ID terminated -insufficient space in destination storagepool.

Explanation: During the indicated operation, there isnot enough space available in the destination storagepool.


User Response: Make more space available in thestorage pool and restart the operation.

ANR1073E Operation process process ID terminated -sufficient recovery log space is notavailable.

Explanation: During the indicated operation, theserver runs out of recovery log space.



ANR1074E Operation process process ID terminated -sufficient database space is notavailable.

Explanation: During the indicated operation, theserver runs out of database space.



ANR1075E Operation process process ID terminated -lock conflict.

Explanation: During the indicated operation, theserver needs to obtain a lock that is not available.


User Response: Restart the operation.



ANR1076E Operation process process ID terminated -sufficient memory is not available.

Explanation: During the indicated operation, notenough server memory is available.


User Response: If necessary, make more memoryavailable to the server, and then restart the operation.

ANR1077E Operation process process ID terminated -transaction aborted.

Explanation: During the indicated operation, theserver detected an error while attempting to commit atransaction. This message should be preceded by othermessages that give additional information about thefailed transaction.



ANR1078E Operation process process ID terminated -internal server error detected.

Explanation: During the indicated operation, theserver encounters an internal error.



ANR1079I Server-free backup of node nodename,file system file system, started as processprocess ID by administrator administrator.

Explanation: The administrator initiates a server-freebackup of the node’s file system.



ANR1080W Space reclamation terminated forvolume volume name - process canceled.

Explanation: During space reclamation for theindicated volume, the process performing thereclamation has been canceled.



ANR1081W Space reclamation terminated forvolume volume name - storage mediainaccessible.

Explanation: During space reclamation for theindicated volume, a required volume cannot bemounted.



ANR1082W Space reclamation terminated forvolume volume name - insufficientnumber of mount points available forremovable media.

Explanation: During space reclamation for theindicated volume, the server could not allocatesufficient mount points for the volumes required.



ANR1083W Space reclamation terminated forvolume volume name - excessive readerrors encountered.

Explanation: During space reclamation for theindicated volume, read errors occur that preventreclamation from continuing.


User Response: If possible, determine and correct thecause of the read errors.

ANR1084W Space reclamation terminated forvolume volume name - excessive writeerrors encountered.

Explanation: During space reclamation for theindicated volume, write errors occur that preventreclamation from continuing.


User Response: If possible, determine and correct thecause of the write errors.



ANR1085W Space reclamation terminated forvolume volume name - data transferinterrupted.

Explanation: During space reclamation for theindicated volume, a data transfer operation has beeninterrupted and cannot be continued.


User Response: If possible, determine and correct thecause of the interruption.

ANR1086W Space reclamation terminated forvolume volume name - insufficient spacein storage pool.

Explanation: During space reclamation for theindicated volume, the server determines that datacannot be moved from the volume due to insufficientspace on other volumes in the storage pool.


User Response: Make more space available on othervolumes in the storage pool.

ANR1087W Space reclamation terminated forvolume volume name - sufficient recoverylog space is not available.

Explanation: During space reclamation for theindicated volume, the server runs out of recovery logspace.



ANR1088W Space reclamation terminated forvolume volume name - sufficient databasespace is not available.

Explanation: During space reclamation for theindicated volume, the server runs out of databasespace.



ANR1089W Space reclamation terminated forvolume volume name - lock conflict.

Explanation: During space reclamation for theindicated volume, the server needed to obtain a lockthat is not available.


User Response: Wait for the server to retry thereclamation.

ANR1090W Space reclamation terminated forvolume volume name - thread resourcenot available.

Explanation: During space reclamation for theindicated volume, the server cannot start a thread forthe reclamation process.


User Response: Wait for the server to retry thereclamation. If the error persists, it may indicate ashortage of server memory.

ANR1091W Space reclamation terminated forvolume volume name - sufficient memoryis not available.

Explanation: During space reclamation for theindicated volume, there was not enough servermemory available.



ANR1092W Space reclamation terminated forvolume volume name - internal servererror detected.

Explanation: During space reclamation for theindicated volume, the server encounters an internalerror.





ANR1093W Space reclamation terminated forvolume volume name - transactionaborted.

Explanation: During space reclamation for theindicated volume, the server detected an error whileattempting to commit a transaction.



ANR1094E Invalid destination storage pool storagepool name specified for storage of anobject using data mover data mover.

Explanation: While attempting to store an object usingthe indicated data mover, the server determined thatthe indicated storage pool was invalid for thisoperation. The indicated storage pool is used because itis specified as the copy group destination of theassigned management class.

This storage pool could be invalid for any of thefollowing reasons:

v The storage pool is not defined

v The storage pool is a random-access storage pool andthis operation requires a sequential-access storagepool

v The storage pool is not a primary storage pool

v The storage pool has a NATIVE or NONBLOCK dataformat, which is not supported for this operation

v The storage pool is not a NONBLOCK data format,which is required for server-free operations

v The data format of the storage pool does not matchthe data format of the data mover


User Response: This message usually indicates aconfiguration problem with either the storage pool orthe policy. Ensure that the destination storage pool hasappropriate attributes, including data format, for thisoperation. Check the copy group of the assignedmanagement class. If the destination is incorrect, eitherassign a new management class, or change thedestination in the copy group and activate the changedpolicy. Also, consider whether you must define a newstorage pool or data mover.

ANR1095E Data mover operation for node nodename and file space filespace name cannotbe started - an operation involving thisnode and file space is already inprogress.

Explanation: A request has been made to use a datamover to perform an operation involving the indicated

node and file space. The indicated file space was eitherspecified as the source for a backup operation or thedestination location for a restore operation. However, adata mover operation involving that node and filespace is already in progress; the indicated file space iseither the source for a currently running backupoperation or is the destination for a currently runningrestore operation. To avoid possible conflicts, the newoperation is not performed.


User Response: Allow the current operation tocomplete before starting a new operation for this nodeand file space.

ANR1096E Operation process process ID terminated -storage media inaccessible.

Explanation: During the indicated operation, arequired volume cannot be mounted.


User Response: If possible, correct the problem andrestart the operation.

ANR1097E Operation process process ID terminated -data transfer interrupted.

Explanation: During the indicated operation, a datatransfer operation is interrupted and cannot becontinued.


User Response: If possible, correct the problem andrestart the operation.

ANR1098E Operation process process ID terminated -file deleted from data storage duringretrieval.

Explanation: During the indicated operation, a filewas deleted from data storage during retrieval.



ANR1099E Operation process process ID terminated -thread resource not available.

Explanation: During the indicated operation, theserver cannot start a thread.


User Response: The problem may indicate a shortageof memory. If necessary, make more memory availableto the server, and then restart the operation.



ANR1100I Migration started for volume volumename, storage pool storage pool name(process number process ID).

Explanation: Because the high migration threshold forthe indicated storage pool has been exceeded,migration of files from the volume shown begins.

System Action: The system moves the data from thisvolume to the next (target) pool.


ANR1101I Migration ended for volume volumename.

Explanation: Because the low migration threshold forthe indicated storage pool has been reached, migrationof files from the indicated volume ends.



ANR1102I Removable volume volume name isrequired for migration.

Explanation: During migration processing, the serverdetermines that a removable volume is required inorder to complete processing.



ANR1103E Operation process process ID terminated -server-free input/output errorsencountered.

Explanation: During the indicated operation,input/output errors were encountered which preventthe operation from continuing.


User Response: Check previous messages for problemdetermination information.

ANR1104E Operation process process ID terminated -NDMP session errors encountered.

Explanation: During the indicated operation, theNDMP session with the NAS file server reported errorswhich prevent the operation from continuing.


User Response: Check the NDMP logs for the NASfile server and, if possible, correct the cause of theerrors and restart the operation.

ANR1106W An incorrect destination storage poolstorage pool name was specified forstoring a table of contents for an image.A table of contents will not be createdfor the image.

Explanation: While attempting to store an imageobject, the server determined that the indicated table ofcontents (TOC) destination storage pool was invalid.The indicated storage pool is used because it isspecified as the copy group TOC destination of theassigned management class.




v The storage pool has a data format other thanNATIVE or NONBLOCK

System Action: The operation continues because TOCcreation is preferred, but not required. A TOC will notbe created for the stored image object.

User Response: This message usually indicates aconfiguration problem with either the storage pool orthe policy. Ensure that the TOC destination storagepool has appropriate attributes, including data format.Check the copy group of the assigned managementclass. If the TOC destination is incorrect, either assign anew management class, or change the TOC destinationin the copy group and activate the changed policy.

ANR1107E An incorrect destination storage poolstorage pool name was specified forstorage of a table of contents for animage object. The backup operationfails.

Explanation: While attempting to store an imageobject, the server determined that the indicated table ofcontents (TOC) destination storage pool was invalid.The indicated storage pool is used because it isspecified as the copy group TOC destination of theassigned management class.




v The storage pool has a data format other thanNATIVE or NONBLOCK


User Response: This message usually indicates aconfiguration problem with either the storage pool orthe policy. Ensure that the TOC destination storagepool has appropriate attributes, including data format.Check the copy group of the assigned managementclass. If the TOC destination is incorrect, either assign anew management class, or change the TOC destination



in the copy group and activate the changed policy.

ANR1108W The server is unable to create a table ofcontents for node node name, file spacefile space in storage pool storage pool name.

Explanation: While attempting to create a table ofcontents (TOC) for the specified node and file space inthe indicated TOC destination pool, a failure occurred.

System Action: The operation continues because TOCcreation is preferred, but not required. A TOC will notbe created for the stored image object.

User Response: Look for previous messages giving aspecific reason for the failure. Take corrective action asappropriate.

ANR1109W Command: A table of contents wasrequested, but there is no table ofcontents destination storage poolspecified. The table of contents will notbe created, but the operation continues.

Explanation: While preparing to create a table ofcontents (TOC), the server determined that the TOCdestination storage pool is not specified in the backupcopy group for the assigned management class.

System Action: The operation continues because TOCcreation is preferred, but not required. A TOC will notbe created.

User Response: This message indicates aconfiguration problem with the policy. Either assign anew management class with appropriate attributes, orcorrect the assigned management class by setting theTOC destination in the backup copy group andactivating the changed policy.

ANR1110E Command: A table of contents wasrequested, but there is no table ofcontents destination storage poolspecified. The table of contents can notbe created and the operation fails.

Explanation: While preparing to create a table ofcontents (TOC), the server determined that the TOCdestination storage pool is not specified in the backupcopy group for the assigned management class.


User Response: This message indicates aconfiguration problem with the policy. Either assign anew management class with appropriate attributes, orcorrect the assigned management class by setting theTOC destination in the backup copy group andactivating the changed policy. If a TOC is not required,change the value of the TOC parameter on thecommand.

ANR1115W Error initiating migration for storagepool storage pool name - lock conflict.

Explanation: While trying to start migration for theindicated storage pool, the server needs to obtain a lockthat is not available.

System Action: Migration stops. The server waits forthe retry period to expire and then tries the migrationagain.


ANR1116W Error initiating migration for storagepool storage pool name - sufficientmemory is not available.

Explanation: While trying to start migration for theindicated storage pool, there is not enough servermemory available.



ANR1117W Error initiating migration for storagepool storage pool name - internal servererror detected.

Explanation: While trying to start migration for theindicated storage pool, the server encounters aninternal error.



ANR1120W Migration terminated for volume volumename - process canceled.

Explanation: During migration for the indicatedvolume, the process performing the migration has beencanceled.

System Action: The migration process is terminated. Ifother migration processes are executing for the namedstorage pool, these processes will continue migration.


ANR1121W Migration terminated for volume volumename - storage media inaccessible.

Explanation: During migration for the indicatedvolume a required volume cannot be mounted.





ANR1122W Migration terminated for volume volumename - insufficient number of mountpoints available for removable media.

Explanation: During migration for the indicatedvolume the server could not allocate sufficient mountpoints for the volumes required.



ANR1123W Migration terminated for volume volumename - excessive read errors encountered.

Explanation: During migration for the indicatedvolume, read errors occurred that prevent the migrationfrom continuing.


User Response: If possible, correct the cause of theread errors.

ANR1124W Migration terminated for volume volumename - excessive write errorsencountered.

Explanation: During migration for the indicatedvolume, write errors occurred that prevent themigration from continuing.


User Response: If possible, correct the cause of thewrite errors.

ANR1125W Migration terminated for volume volumename - data transfer interrupted.

Explanation: During migration for the indicatedvolume a data transfer operation was interrupted andcould not be continued.



ANR1126W Migration terminated for volume volumename - insufficient space in subordinatestorage pools.

Explanation: During migration for the indicatedvolume, the server cannot move the data from thevolume because there is not enough space on the nextstorage pool to hold it.


User Response: Make more space available in the nextstorage pool or use the UPDATE STGPOOL commandto change the next storage pool to one with more space.

ANR1127W Migration terminated for volume volumename - unable to move file tosubordinate storage pool due toexclusion by size.

Explanation: During migration for the indicatedvolume, the server cannot move the data from thevolume because a file size is larger than allowed on thenext storage pool.


User Response: Use the UPDATE STGPOOLcommand to change the next storage pool maximumfile size or to change the next storage pool target.

ANR1128W Migration terminated for volume volumename - sufficient recovery log space isnot available.

Explanation: During migration for the indicatedvolume, the server runs out of recovery log space.



ANR1129W Migration terminated for volume volumename - sufficient database space is notavailable.

Explanation: During migration for the indicatedvolume pool, the server runs out of database space.





ANR1130W Migration terminated for volume volumename - lock conflict.

Explanation: During migration for the indicatedvolume, the server needs to obtain a lock that is notavailable.



ANR1131W Migration terminated for volume volumename - thread resource not available.

Explanation: During migration for the indicatedvolume, the server cannot start a thread for themigration process.


User Response: Wait for the server to retry themigration. If the error persists, it may indicate ashortage of server memory.

ANR1132W Migration terminated for volume volumename - sufficient memory is notavailable.

Explanation: During migration for the indicatedvolume, there is not enough server memory available.



ANR1133W Migration terminated for volume volumename - internal server error detected.

Explanation: During migration for the indicatedvolume, the server encounters an internal error.



ANR1134W Migration terminated for storage poolstorage pool name - insufficient number ofmount points available for removablemedia.

Explanation: During migration for the indicatedstorage pool the server could not allocate sufficientmount points in the next storage pool.

System Action: Migration stops. The server waits for

the retry period to expire and then tries the migrationagain.


ANR1135W Migration terminated for volume volumename - transaction aborted.

Explanation: During migration for the indicatedvolume, the server detected an error while attemptingto commit a transaction.



ANR1140I Move data process started for volumevolume name (process ID process ID).

Explanation: As a result of a MOVE DATA command,a process begins to move data from the volume shown.

System Action: The server moves all data from thevolume.


ANR1141I Move data process ended for volumevolume name.

Explanation: The MOVE DATA command for thevolume shown completes.



ANR1142I Moving data for collocation clustercluster number of total clusters on volumevolume name.

Explanation: As a result of a MOVE DATA command,data moves from the volume indicated to new volumes;the message shows the total number of clusters (dataobjects) on the volume and the current cluster beingprocessed.



ANR1143W Move data process terminated forvolume volume name - process canceled.

Explanation: During move data processing for theindicated volume, the process performing the movedata was canceled. It is possible that the server mayissue this message more than once while the server isending this process.



System Action: The server ends the MOVE DATAcommand.


ANR1144W Move data process terminated forvolume volume name - storage mediainaccessible.

Explanation: During move data processing for theindicated volume, a required volume cannot bemounted.



ANR1145W Move data process terminated forvolume volume name - insufficientnumber of mount points available forremovable media.

Explanation: During move data processing for theindicated volume, the server could not allocatesufficient mount points for the volumes required.



ANR1146W Move data process terminated forvolume volume name - excessive readerrors encountered.

Explanation: During move data processing for theindicated volume, read errors occurred that preventedthe move from continuing.


User Response: If possible, correct the cause of theread errors and then reissue the MOVE DATAcommand.

ANR1147W Move data process terminated forvolume volume name - excessive writeerrors encountered.

Explanation: During move data processing for theindicated volume, write errors occurred that preventedthe move from continuing.


User Response: If possible, correct the cause of thewrite errors and then reissue the MOVE DATAcommand.

ANR1148W Move data process terminated forvolume volume name - data transferinterrupted.

Explanation: During move data processing for theindicated volume a data transfer operation wasinterrupted and could not be continued.



ANR1149W Move data process terminated forvolume volume name - insufficient spacein target storage pool.

Explanation: During move data processing for theindicated volume, the server cannot move the datafrom the volume, because there is not enough space onthe destination storage pool to hold it.


User Response: Make more space available in the nextstorage pool, or specify a storage pool with more space,and reissue the MOVE DATA command.

ANR1150W Move data process terminated forvolume volume name - unable to movefile to target storage pool due toexclusion by size.

Explanation: During move data processing for theindicated volume, the server cannot move the datafrom the volume because a file size is larger thanallowed on the next storage pool.


User Response: Use the UPDATE STGPOOLcommand to change the next storage pool maximumfile size or to change the next storage pool target, andthen reissue the MOVE DATA command.

ANR1151W Move data process terminated forvolume volume name - sufficient recoverylog space is not available.

Explanation: During move data processing for theindicated volume, the server runs out of recovery logspace.





ANR1152W Move data process terminated forvolume volume name - sufficient databasespace is not available.

Explanation: During move data processing for theindicated volume, the server runs out of databasespace.



ANR1153W Move data process terminated forvolume volume name - lock conflict.

Explanation: During move data processing for theindicated volume, the server needs to obtain a lock thatwas not available.


User Response: Reissue the MOVE DATA command.

ANR1154W Move data process terminated forvolume volume name - thread resourcenot available.

Explanation: During move data processing for theindicated volume, the server cannot start a thread forthe migration process.


User Response: Reissue the MOVE DATA command.If the error persists, it may indicate a shortage of servermemory.

ANR1155W Move data process terminated forvolume volume name - sufficient memoryis not available.

Explanation: During move data processing for theindicated volume, there is not enough server memoryavailable.


User Response: If necessary, make more memoryavailable to the server, and then reissue the MOVEDATA command.

ANR1156W Move data process terminated forvolume volume name - internal servererror detected.

Explanation: During move data processing for theindicated volume, the server encounters an internalerror.



ANR1157I Removable volume volume name isrequired for move process.

Explanation: During move data or move node dataprocessing, the server determines that the indicatedremovable volume is required in order to completeprocessing.



ANR1160W Transaction was aborted for volumevolume name.

Explanation: An error was detected during transactioncommit. This message should be preceded by othermessages that give additional information about thefailed transaction.



ANR1161W Move Data skipping damaged file onvolume volume name: Node node name,Type file type, File space filespace name,File name file name.

Explanation: During move data, a file is encounteredthat was previously found to be damaged. If this file ispart of an aggregate, the entire aggregate waspreviously marked damaged, possibly because anintegrity error was detected for some other file withinthe aggregate.

System Action: The damaged file is not moved.

User Response: Audit the indicated volume withFIX=NO to verify that the file is damaged. The auditwill reset the file status if the file is found to beundamaged during the audit. If the file is part of anaggregate, the audit will reset the aggregate status ifthe entire aggregate is found to be undamaged. If thisvolume is in a primary storage pool that has previouslybeen backed up to a copy storage pool, attempt torestore damaged files by using the RESTORESTGPOOL command.



ANR1162W Space reclamation skipping damagedfile on volume volume name: Node nodename, Type file type, File space filespacename, File name file name.

Explanation: During reclamation, a file is encounteredthat was previously found to be damaged. If this file ispart of an aggregate, the entire aggregate waspreviously marked damaged, possibly because anintegrity error was detected for some other file withinthe aggregate.

System Action: The damaged file is not moved.

User Response: Audit the indicated volume withFIX=NO to verify that the file is damaged. The auditwill reset the file status if the file is found to beundamaged during the audit. If the file is part of anaggregate, the audit will reset the aggregate status ifthe entire aggregate is found to be undamaged. If thisvolume is in a primary storage pool that has previouslybeen backed up to a copy storage pool, attempt torestore damaged files by using the RESTORESTGPOOL command.

ANR1163W Offsite volume volume name stillcontains files which could not bemoved.

Explanation: During processing of a MOVE DATAcommand or reclamation, the server determined thatthe indicated offsite volume contained one or more filesthat could not be moved. One or more files could notbe copied from the other available volumes.


User Response: Check for messages indicating reasonswhy files could not be moved. To complete the moveoperation, you have several options:

v Bring the volume back on site and reissue a MOVEDATA command to reclaim the volume.

v Make the primary volumes available and reissue aMOVE DATA command to reclaim the volume.

v Delete the files by using the DELETE VOLUMEcommand.

ANR1165E Error detected for file in storage poolstorage pool name: Node node name, Typefile type, File space filespace name, fsIdfilespace id, File name file name.

Explanation: The server has detected an error for theindicated file.

System Action: The file will be marked damaged inthe server database, and will not be accessed for futureoperations. If this file is part of an aggregate, the entireaggregate will be marked damaged. If a usable copy ofthe file exists in another storage pool, that copy may beaccessed for future operations involving the file.

User Response: If the indicated storage pool is a

primary pool, and a usable copy of the file exists in acopy storage pool, you can recreate the file in theprimary pool using the RESTORE STGPOOL command.If the indicated storage pool is a copy storage pool, it ispossible that the primary copy of the file is usable, butwas not accessed because the access mode for theprimary storage pool or volume is unavailable. If this isthe case, the primary copy of the file may be madeaccessible by changing the access mode of the primarypool or volume.

ANR1166E Move Data for offsite volume cannotcopy damaged file in storage poolstorage pool name: Node node name, Typefile type, File space filespace name, fsIdfilespace id, File name file name.

Explanation: A move data process for an offsitevolume cannot locate an undamaged copy of thespecified file in any storage pool accessible by theserver. If this file is part of an aggregate, the processcould not locate an undamaged copy of the aggregateto which the file belongs.

System Action: The file will skipped and will not bemoved from the offsite volume.

User Response: The indicated storage pool is aprimary pool that contains a damaged copy of the file.The only usable copy of the file may now only resideon the offsite volume that was involved in the movedata process. If you bring this volume back onsite, youcan recreate the file in the primary pool by using theRESTORE STGPOOL command. After the restore, youcan reissue the MOVE DATA command.

ANR1167E Space reclamation for offsite volume(s)cannot copy damaged file in storagepool storage pool name: Node node name,Type file type, File space filespacename,fsId filespace id , File name file name.

Explanation: A reclamation process of offsite volumescannot locate an undamaged copy of the specified filein any storage pool accessible by the server. If this fileis part of an aggregate, the process could not locate anundamaged copy of the aggregate to which the filebelongs.

System Action: The file is skipped and will not bemoved from the offsite volume.

User Response: The indicated storage pool is aprimary pool that contains a damaged copy of the file.The only usable copy of the file may now only resideon an offsite volume that was involved in thereclamation process, but was not totally reclaimed. Ifyou bring this volume back onsite, you can recreate thefile in the primary pool by using the RESTORESTGPOOL command.



ANR1168W Migration skipping damaged file onvolume volume name: Node node name,Type file type, File space filespace name,fsId filespace id, File name file name.

Explanation: During migration, a file is encounteredthat was previously found to be damaged. If this file ispart of an aggregate, the entire aggregate waspreviously marked damaged, possibly because anintegrity error was detected for some other file withinthe aggregate.

System Action: The damaged file will not be moved.

User Response: Audit the indicated volume withFIX=NO to verify that the file is damaged. The auditwill reset the file status if the file is found to beundamaged during the audit. If the file is part of anaggregate, the audit will reset the aggregate status ifthe entire aggregate is found to be undamaged. If thisvolume is in a primary storage pool that has previouslybeen backed up to a copy storage pool, you can alsoattempt to restore damaged files by using theRESTORE STGPOOL command.

ANR1169W Lock conflict on movement of offsitefile - file is skipped.

Explanation: During migration, reclamation, or movedata processing of a volume that is offsite, a copy ofthe file that resides in a primary disk storage pool islocked by another process.

System Action: The file is skipped and the processwill try to find another copy of the file in a copystorage pool. If another copy cannot be used, the moveoperation on the volume may be incomplete.

User Response: If a move operation was incomplete,try repeating the operation.

ANR1170E Out of Space in target copy storagepool: copy storage pool name.

Explanation: During reclamation, or move dataprocessing of a volume that is offsite, there was novolume available in the specified target copy storagepool.

System Action: The operation is terminated.

User Response: Define volumes to the copy storagepool or raise the MAXSCRATCH value.

ANR1171W Unable to move files associated withnode node name, filespace filespace namefsId filespace id on volume volume namedue to restore in progress.

Explanation: During movement of data (migration,reclamation, move data) from a sequential volume, oneor more files were encountered that were locked by arestore operation.

System Action: The files are not moved, but areskipped.

User Response: Use the QUERY RESTOREFORMAT=DETAILED command to determine if therestore operation is active or is in restartable state. Arestartable restore operation will keep the files lockedfrom movement until the RESTOREINTERVAL isreached. QUERY OPTION will display this interval.You may wish to lower the RESTOREINTERVAL tocause a restartable restore operation to be removed andfree up the locked files. The RESTOREINTERVAL is aserver option.

ANR1172E Move Data for offsite volume cannotcopy file in storage pool storage poolname: Node node name, Type file type, Filespace filespace name, fsId filespace id, Filename file name.

Explanation: A move data process for an offsitevolume cannot locate a copy of the specified file in anystorage pool accessible by the server. If this file is partof an aggregate, the process could not locate copy ofthe aggregate to which the file belongs on an accessiblevolume.

System Action: The file will skipped and will not bemoved from the offsite volume.

User Response: The indicated storage pool is aprimary pool that should contain a primary copy of thefile. Perhaps the volume on which that file resides is ona destroyed volume. The only usable copy of the filemay now only reside on the offsite volume that wasinvolved in the move data process. If you bring thisvolume back onsite, you can recreate the file in theprimary pool by using the RESTORE STGPOOLcommand. After the restore, you can reissue the MOVEDATA command.

ANR1173E Space reclamation for offsite volume(s)cannot copy file in storage pool storagepool name: Node node name, Type file type,File space filespace name, fsId filespace id,File name file name.

Explanation: A reclamation process of offsite volumescannot locate a copy of the specified file in any storagepool accessible by the server. If this file is part of anaggregate, the process could not locate a copy of theaggregate to which the file belongs on an accessiblevolume.

System Action: The file is skipped and will not bemoved from the offsite volume.

User Response: The indicated storage pool is aprimary pool that should contain a copy of the file.Perhaps the volume on which that file resides is on adestroyed volume. The only usable copy of the file maynow only reside on an offsite volume that was involvedin the reclamation process, but was not totally



reclaimed. If you bring this volume back onsite, youcan recreate the file in the primary pool by using theRESTORE STGPOOL command.

ANR1174W One or more cached files were notdeleted on volume volume name.

Explanation: The MOVE DATA command could notdelete one or more cached files on the disk volumeshown. Migration was probably running at the sametime, creating cached files while the MOVE DATAcommand was trying to delete them.

System Action: The MOVE DATA command ran tocompletion.

User Response: If you want the remaining cached filesremoved from the disk volume, reissue the MOVEDATA command.

ANR1175W Volume volume name contains files whichcould not be reclaimed.

Explanation: After reclamation of the indicatedvolume, it still contains one or more files that could notbe reclaimed. These files were skipped because of readerrors, or because the files are marked damaged.

System Action: The volume is marked unavailable soit will not be chosen again for reclamation.

User Response:

v Use the UPDATE VOLUME command to set thevolume access to readonly.

v Try using the MOVE DATA command to manuallyreclaim the volume.

v If files still exist on the volume, audit the volumeusing AUDIT VOLUME FIX=YES.

v Try using the MOVE DATA command again.

v Use the RESTORE VOLUME command to restorefiles marked damaged.

ANR1180W Access mode for volume volume namehas been set to ″unavailable″ due to fileread or integrity errors.

Explanation: During processing of a storage poolvolume, input/output or other errors occur that forcethe server to mark the volume unavailable for furtherprocessing.

System Action: The server sets the volume status tounavailable.

User Response: Correct the errors that set the volumeto unavailable, or use the DELETE VOLUME commandto remove it from the system.

ANR1181E DiagnosticID: Data storage transactiontransaction ID was aborted.

Explanation: A database transaction failed because ofan error that was detected during data storageprocessing. This message should be preceded by othermessages that give additional information about thefailed transaction.

System Action: The server operation that encounteredthis error during data storage processing fails.


ANR1186I Restore of node nodename, file system filesystem, started as process process ID byadministrator administrator. A full imagefor this file system will be restored todestination destination.

Explanation: The administrator initiates a restore ofthe node’s file system. The restore will be performedusing a full image of this file system. The file systemwill be restored to the indicated destination.



ANR1199I Removable volume volume name isrequired for audit process.

Explanation: During audit volume processing for theindicated volume, the server determines that aremovable volume is required in order to completeprocessing.



ANR1210I Backup of primary storage pool primarypool name to copy storage pool copy poolname started as process process ID.

Explanation: A process has been started to back up aprimary storage pool to the indicated copy storagepool.

System Action: For every noncached file in theprimary pool, a backup copy is made in the copy pool,if a copy of that file does not already exist.




ANR1211I Backup preview of primary storage poolprimary pool name to copy storage poolcopy pool name started as process processID.

Explanation: A preview process has been started toback up a primary storage pool to the indicated copystorage pool.

System Action: Preview information about the backupoperation is collected and displayed, but files are notbacked up.


ANR1212I Backup process process ID ended forstorage pool storage pool name.

Explanation: A backup process for the named primarystorage pool has ended.



ANR1213I Backup process process ID terminated forstorage pool storage pool name - processcanceled.

Explanation: During backup of the indicated primarystorage pool, a process performing the backup has beencanceled.

System Action: If other backup processes areexecuting for the named storage pool, these processescontinue.


ANR1214I Backup of primary storage pool primarypool name to copy storage pool copy poolname has ended. Files Backed Up:number of files, Bytes Backed Up: numberof bytes, Unreadable Files: number ofunreadable files, Unreadable Bytes: numberof bytes in unreadable files.

Explanation: Backup processing for the specifiedstorage pool has ended with the results shown.


User Response: Examine previous messages todetermine whether all backup processes endedsuccessfully.

ANR1215I Backup preview of primary storage poolprimary pool name to copy storage poolcopy pool name has ended. Files BackedUp: number of files, Bytes Backed Up:number of bytes.

Explanation: Backup preview processing for thespecified storage pool has ended with the resultsshown.



ANR1216E Command: Process process ID terminated -storage media inaccessible.

Explanation: During backup processing, a requiredvolume could not be mounted.

System Action: The indicated backup process ends.


ANR1217E Command: Process process ID terminated -insufficient number of mount pointsavailable for removable media.

Explanation: During backup processing, the servercould not allocate sufficient mount points for thevolumes required.



ANR1218E Command: Process process ID terminated -excessive read errors encountered.

Explanation: During backup processing, read errorsoccur that prevent the backup from continuing.


User Response: If possible, correct the cause of theread errors and reissue the backup command.

ANR1219E Command: Process process ID terminated -excessive write errors encountered.

Explanation: During backup processing, write errorsoccur that prevent the backup from continuing.


User Response: If possible, correct the cause of thewrite errors and reissue the backup command.

ANR1220E Command: Process process ID terminated -data transfer interrupted.

Explanation: During backup processing, a datatransfer operation was interrupted and could not becontinued.




User Response: If possible, correct the cause of theinterruption and reissue the backup command.

ANR1221E Command: Process process ID terminated -insufficient space in target copy storagepool.

Explanation: During backup processing, the servercannot copy data to the copy storage pool because notenough space is available in the copy storage pool.


User Response: Make more space available in thecopy storage pool and reissue the backup command, orreissue the backup command and specify another copystorage pool with more space.

ANR1222E Command: Process process ID terminated -sufficient recovery log space is notavailable.

Explanation: During backup processing, the serverruns out of recovery log space.



ANR1223E Command: Process process ID terminated -sufficient database space is notavailable.

Explanation: During backup processing, the serverruns out of database space.



ANR1224E Command: Process process ID terminated -lock conflict.

Explanation: During backup processing, the serverneeds to obtain a lock that is not available.


User Response: Reissue the backup command.

ANR1225E Command: Process process ID terminated -thread resource not available.

Explanation: During backup processing, the servercannot start a thread.


User Response: Reissue the backup command. If theerror persists, it may indicate a shortage of servermemory.

ANR1226E Command: Process process ID terminated -sufficient memory is not available.

Explanation: During backup processing, not enoughserver memory is available.


User Response: If necessary, make more memoryavailable to the server, and then reissue the backupcommand.

ANR1227E Command: Process process ID terminated -internal server error detected.

Explanation: During backup processing, the serverencounters an internal error.



ANR1228I Removable volume volume name isrequired for storage pool backup.

Explanation: During processing of a BACKUPSTGPOOL command, the server determines that aremovable volume is required.

System Action: Unless this is a preview process, theserver attempts to mount the removable volume.


ANR1229W Volume volume name cannot be backedup - the volume is offline, in use byanother process, not currentlymountable, or access mode is″unavailable″ or ″destroyed″.

Explanation: During storage pool backup, a volumecannot be backed up because of one of the following:

v The volume is offline

v The volume is in use by another process

v The volume cannot be be mounted

v The access mode of the volume does not allow theoperation

System Action: The server continues backupprocessing, but skips the indicated volume.

User Response: If necessary, use the VARY ON orUPDATE VOLUME command for this volume andrestart the backup command. If the volume is in use byanother process, wait for that process to complete andthen restart the backup. If the volume is not currentlymountable, verify that the drive can mount the volumeand retry the command.



ANR1230I Restore of primary storage pool primarypool name started as process process ID.

Explanation: A process has been started to restore theindicated primary storage pool.

System Action: Non-cached files that reside in thenamed primary storage pool are restored if either of thefollowing criteria are met:

v The file is stored on a volume whose access mode isdestroyed

v The primary file has been identified as havingdata-integrity errors during a previous operation


ANR1231I Restore preview of primary storage poolprimary pool name started as processprocess ID.

Explanation: A preview process has been started torestore a primary storage pool.

System Action: Preview information about the restoreoperation is collected and displayed, but files are notrestored. The restore preview includes noncached filesthat reside in the specified primary storage pool andthat meet either of the following conditions:

v The file is stored on a volume whose access mode isdestroyed

v The primary file has been identified as havingdata-integrity errors during a previous operation


ANR1232I Restore of volumes in primary storagepool primary pool name started as processprocess ID.

Explanation: A process has been started to restore oneor more volumes in the indicated primary storage pool.

System Action: Noncached files that reside onselected volumes in the primary storage pool arerestored.


ANR1233I Restore preview of volumes in primarystorage pool primary pool name started asprocess process ID.

Explanation: A preview process has been started torestore one or more volumes in the indicated primarystorage pool.

System Action: Preview information about the restoreoperation is collected and displayed, but files are notrestored. The restore preview includes noncached filesthat reside on selected volumes in the primary storagepool.


ANR1234I Restore process process ID ended forstorage pool storage pool name.

Explanation: A restore process for the named primarystorage pool has ended.



ANR1235I Restore process process ID ended forvolumes in storage pool storage poolname.

Explanation: A restore process for volumes in thenamed primary storage pool has ended.



ANR1236I Restore process process ID terminated forstorage pool storage pool name - processcanceled.

Explanation: During restore of the indicated primarystorage pool, a process performing the restore has beencanceled.

System Action: If other restore processes are executingfor the named storage pool, these processes continue.


ANR1237I Restore process process ID terminated forvolumes in storage pool storage pool nameprocess canceled.

Explanation: During restore of volumes in theindicated primary storage pool, a process performingthe restore has been canceled.

System Action: If other restore processes are executingfor the volumes, these processes continue.


ANR1238I Restore of primary storage pool primarypool name has ended. Files Restored:number of files, Bytes Restored: number ofbytes, Unreadable Files: number ofunreadable files, Unreadable Bytes: numberof bytes in unreadable files.

Explanation: Restore processing for the specifiedstorage pool has ended with the results shown.


User Response: Examine previous messages todetermine whether all restore processes endedsuccessfully.



ANR1239I Restore preview of primary storage poolprimary pool name has ended. FilesRestored: number of files, Bytes Restored:number of bytes.

Explanation: Restore preview processing for thespecified storage pool has ended with the resultsshown.



ANR1240I Restore of volumes in primary storagepool primary pool name has ended. FilesRestored: number of files, Bytes Restored:number of bytes, Unreadable Files: numberof unreadable files, Unreadable Bytes:number of bytes in unreadable files.

Explanation: Restore processing for volumes in thespecified storage pool has ended with the resultsshown.


User Response: Examine previous messages todetermine whether all restore processes endedsuccessfully.

ANR1241I Restore preview of volumes in primarystorage pool primary pool name hasended. Files Restored: number of files,Bytes Restored: number of bytes.

Explanation: Restore preview processing for volumesin the specified storage pool has ended with the resultsshown.



ANR1242E Command: Process process ID terminated -storage media inaccessible.

Explanation: During restore processing, a requiredvolume could not be mounted.

System Action: The indicated restore process ends.


ANR1243E Command: Process process ID terminated -insufficient number of mount pointsavailable for removable media.

Explanation: During restore processing, the servercould not allocate sufficient mount points for thevolumes required.



ANR1244E Command: Process process ID terminated -excessive read errors encountered.

Explanation: During restore processing, read errorsoccur that prevent the restore from continuing.


User Response: If possible, correct the cause of theread errors and reissue the restore command.

ANR1245E Command: Process process ID terminated -excessive write errors encountered.

Explanation: During restore processing, write errorsoccur that prevent the restore from continuing.


User Response: If possible, correct the cause of thewrite errors and reissue the restore command.

ANR1246E Command: Process process ID terminated -data transfer interrupted.

Explanation: During restore processing, a data transferoperation was interrupted and could not be continued.


User Response: If possible, correct the cause of theinterruption and reissue the restore command.

ANR1247E Command: Process process ID terminated -insufficient space in target primarystorage pool.

Explanation: During restore processing, the servercannot copy data to the target primary storage pool,because not enough space is available in the targetpool.


User Response: Make more space available in thetarget primary storage pool, and then reissue therestore command.

ANR1248E Command: Process process ID terminated -sufficient recovery log space is notavailable.

Explanation: During restore processing, the serverruns out of recovery log space.





ANR1249E Command: Process process ID terminated -sufficient database space is notavailable.

Explanation: During restore processing, the serverruns out of database space.



ANR1250E Command: Process process ID terminated -lock conflict.

Explanation: During restore processing, the serverneeds to obtain a lock that is not available.


User Response: Reissue the restore command.

ANR1251E Command: Process process ID terminated -thread resource not available.

Explanation: During restore processing, the servercannot start a thread.


User Response: Reissue the restore command. If theerror persists, it may indicate a shortage of servermemory.

ANR1252E Command: Process process ID terminated -sufficient memory is not available.

Explanation: During restore processing, there is notenough server memory available.


User Response: If necessary, make more memoryavailable to the server; and then reissue the restorecommand.

ANR1253E Command: Process process ID terminated -internal server error detected.

Explanation: During restore processing, the serverencounters an internal error.



ANR1254I Removable volume volume name isrequired for restore processing.

Explanation: During processing of a RESTORESTGPOOL or RESTORE VOLUME command, the serverdetermines that a removable volume is required.

System Action: Unless this is a preview process, theserver attempts to mount the removable volume.


ANR1255W Files on volume volume name cannot berestored - access mode is ″unavailable″or ″offsite″.

Explanation: During processing of a RESTORESTGPOOL or RESTORE VOLUME command, files on acopy storage pool volume cannot be restored becauseof the volume’s access mode.

System Action: The server continues restoreprocessing, but skips the indicated volume.

User Response: If the volume is stored at an offsitelocation, bring the volume onsite. Use the UPDATEVOLUME command to change the access mode for thevolume and restart the restore command.

ANR1256W Volume volume name contains files thatcould not be restored.

Explanation: During processing of a RESTORESTGPOOL or RESTORE VOLUME command, the serverdetermines that the indicated volume contains one ormore files that could not be restored. If this is apreview operation, this message indicates that arestorable backup copy cannot be found for one ormore files on the indicated volume. If this is an actualrestore operation, this message could result if any ofthe following conditions exist for a file on the indicatedvolume:

v A restorable backup copy cannot be found for thefile.

v A restorable backup copy of the file exists, but islocated on a copy storage pool volume whose accessmode is unavailable or offsite.

v During restore processing, a backup copy wasselected for restore processing, but was deleted ormoved before the file was actually restored. Thisaction could occur as a result of MOVE DATA,DELETE VOLUME, AUDIT VOLUME FIX=YES, orreclamation processing of a copy storage poolvolume while the restore was in progress.


User Response: If this was an actual restore operation,check for messages indicating that files could not berestored because a copy storage pool volume wasunavailable or offsite. Check to see if a move data,delete volume, audit volume, or reclamation processoccurred for a copy storage pool while the restore wasin progress. If either of these conditions existed, correctthe situation and reissue the restore command.



ANR1257W Storage pool backup skipping damagedfile on volume volume name: Node nodename, Type file type, File space filespacename, fsId filespace id, File name file name.

Explanation: During storage pool backup, a file isencountered that was previously found to be damaged.If this file is part of an aggregate, the entire aggregatewas previously marked damaged, possibly because anintegrity error was detected for some other file withinthe aggregate.

System Action: The damaged file will not be backedup.

User Response: Audit the indicated volume withFIX=NO to verify that the file is damaged. The auditwill reset the file status if the file is found to beundamaged during the audit. If the file is part of anaggregate, the audit will reset the aggregate status ifthe entire aggregate is found to be undamaged. If thisfile has previously been backed up to a copy storagepool, you can also attempt to restore damaged filesusing the RESTORE STGPOOL command.

ANR1258W Files on volume volume name needed formove data cannot be accessed - accessmode is ″unavailable″ or ″offsite″.

Explanation: During a move data operation on anoffsite volume, files on a storage pool volume cannotbe copied because of the volume’s access mode.

System Action: The server continues move dataprocessing, but one or more files were not moved fromthe offsite volume.

User Response: If the specified volume can be madeavailable, use the UPDATE VOLUME command tochange the access mode for the volume and reissue theMOVE DATA command.

ANR1259W Files on volume volume name needed foroffsite reclamation cannot be accessed -access mode is ″unavailable″ or ″offsite″.

Explanation: During reclamation processing of anoffsite volume, files on a storage pool volume cannotbe copied because of the volume’s access mode.

System Action: The server continues reclamation, butone or more files were not moved from an offsitevolume, which prevents it from being reclaimed.

User Response: If the specified volume can be madeavailable, use the UPDATE VOLUME command tochange the access mode for the volume and initiatereclamation again by updating the reclamationthreshold for the copy storage pool.

ANR1260W Volume volume name contains one ormore damaged, primary files.

Explanation: This message is issued during RESTORESTGPOOL processing. The indicated volume containsone or more primary, noncached files that havepreviously been found to be damaged.

System Action: If this is not a preview operation, therestore processing attempts to restore the damaged filesfrom copies located in a copy storage pool. If this is apreview operation, no system action is taken.

User Response: You can take the following actions:

v Issue the QUERY CONTENT command withDAMAGED=YES to obtain a list of damaged files onthe indicated volume.

v Audit the indicated volume with FIX=NO to verifythat the files are damaged; the audit will reset thestatus of any files that are found to be undamagedduring the audit.

v If this message was issued during a restore previewoperation, attempt to restore the damaged files usingthe RESTORE STGPOOL command.

v Audit the indicated volume with FIX=YES to deletethe damaged files from the database.

ANR1263I command: Processing completedsuccessfully.

Explanation: The background process to service thecommand command has completed successfully.

System Action: Processing for the commandcompletes. Statistics on the number and type of objectsmoved, together with the total number of bytes copied,are displayed on the server console following thismessage.








ANR1265E Salvage volume command: Processingterminated abnormally - error accessingdata storage.

Explanation: The server encountered an internal errorin accessing data storage while executing a salvagevolume operation.


User Response: Use the QUERY ACTLOG commandto examine messages prior to this error to determinethe cause of the data storage failure. If you find andresolve the error, retry the operation. If you cannot findthe error, contact your service representative forassistance in resolving the problem.

ANR1266E Salvage volume command: Processingterminated abnormally - volume not astorage pool volume.

Explanation: The server encountered an internal errorin accessing data storage while executing a salvagevolume operation.The error occurred because anattempt has been made to access a volume that was nota storage pool volume.



ANR1267I Salvage volume command: Processednumber volume(s).

Explanation: The background process to service thecommand Salvage volume command inspected numberinput volumes.

System Action: Salvage processing for the commandcompletes. Server operation continues.


ANR1268I Salvage volume command: Recoverednumber byte(s).

Explanation: The background process to service thecommand Salvage volume command recovered numberbytes worth of data.



ANR1269I Salvage volume command: Recoverednumber file(s).

Explanation: The background process to service thecommand Salvage volume command recovered numberfiles.



ANR1270I Salvage volume command: File (internal fileidentifierinternal file identifier) recovered.

Explanation: The background process to service thecommand Salvage volume command recovered a file. Thenew file was given a new, system generated namebased on the internal file identifier and the name of thevolume from which the file was recovered. The internalfile identifier is the identifier by which the file wasknown to the server before the file was deleted.



ANR1271I Salvage volume command: * number bytesrecovered from volume volume.

Explanation: The background process to service thecommand Salvage volume command recovered a file fromthe volume volume. The number of bytes recovered fromthe volume is listed.



ANR1272I Salvage volume command: * File iscomplete - it began and ended onvolume volume.

Explanation: The background process to service thecommand Salvage volume command recovered a file fromthe volume volume. The file was completely containedon volume.



ANR1273I Salvage volume command: * File isincomplete - it began on volume volumebut did not end.

Explanation: The background process to service thecommand Salvage volume command recovered a file fromthe volume volume. The file was not completelycontained on volume. Although the file began on thisvolume, it spanned out to a different volume.





ANR1274I Salvage volume command: * File isincomplete - it ended on volume volumebut did not begin there.

Explanation: The background process to service thecommand Salvage volume command recovered a file fromthe volume volume. The file was not completelycontained on volume. Although the file ended on thisvolume, it spanned in from a different volume.



ANR1275I Salvage volume command: * File isincomplete - it did not began or end onvolume volume.

Explanation: The background process to service thecommand Salvage volume command recovered a file fromthe volume volume. The file was not completelycontained on volume. It spanned in from one volumeand spanned out to a another.



ANR1276E Command: Process terminated - sufficientmemory is not available.

Explanation: During salvage processing, not enoughserver memory is available.

System Action: The salvage process ends.

User Response: If necessary, make more memoryavailable to the server, and then reissue the salvagecommand.

ANR1277E Command: Process terminated - thedefault management class in the activepolicy set in policy domain domain namedoes not contain an archive copy group.Unable to continue with salvage.

Explanation: The background process to service thecommand Salvage volume command was unable torecover any files because the default management classin the active policy set in policy domain does not containan archive copy group.

System Action: The salvage process ends.

User Response: Add an archive copy group to thedefault management class in the active policy set of thespecified domain, and then reissue the salvagecommand.

ANR1278I Occupancy is incorrect for storage poolstorage pool name. Occupancy is beingreset.

Explanation: The server has detected incorrectoccupancy information.

System Action: The server recalculates the occupancyvalue based on current storage pool information.


ANR1279I Occupancy is incorrect for volume namevolume name. Occupancy is being reset.

Explanation: The server has detected incorrectoccupancy information.

System Action: The server recalculates the occupancyvalue based on current sequential volume information.


ANR1280E Command: Process process ID terminated -transaction aborted.

Explanation: During backup processing, the serverdetected an error while attempting to commit atransaction. This message should be preceded by othermessages that give additional information about thefailed transaction.



ANR1281E Command: Process process ID terminated -transaction aborted.

Explanation: During restore processing, the serverdetected an error while attempting to commit atransaction. This message should be preceded by othermessages that give additional information about thefailed transaction.



ANR1282I Logical occupancy is incorrect forstorage pool storage pool name. Logicaloccupancy is being reset.

Explanation: The server has detected incorrect logicaloccupancy information.

System Action: The server recalculates the logicaloccupancy value based on current storage poolinformation.




ANR1283I File count is incorrect for storage poolstorage pool name - file count is beingreset.

Explanation: The server has detected an incorrectcount of the number of files within this storage pool.

System Action: The server will correct thisinformation.


ANR1284I Move node data started as processprocess ID.

Explanation: A process has been started to move databy node.

System Action: The indicated process has started.

User Response: To query the progress of the process,use the QUERY PROCESS command. To cancel thebackground process, use the CANCEL PROCESScommand. Use the process ID number to specify thisprocess.

ANR1288I Move node data process process IDended for storage pool storage pool name.

Explanation: A move node data process for the namedstorage pool has ended.



ANR1289I Move node data process process IDterminated for the storage pool storagepool name - process canceled.

Explanation: During move node data processing inthe indicated storage pool, the process performing themove node data has been canceled.

System Action: If other move node data processes areexecuting for the storage pool, these processes continue.


ANR1290I Move node data from storage poolstorage pool name to storage pool storagepool name has ended. Files Moved:number of files, Bytes Moved: number ofbytes, Unreadable Files: number ofunreadable files, Unreadable Bytes: numberof bytes in unreadable files.

Explanation: Move node processing for the specifiedstorage pool has ended with the displayed results.


User Response: Examine previous messages todetermine whether all move node data processes endedsuccessfully.

ANR1300I VARY ONLINE command initiated fordisk volume volume name.

Explanation: A VARY ONLINE command has causeda vary-on process to be started for the volumespecified.



ANR1301I VARY OFFLINE command initiated fordisk volume volume name.

Explanation: A VARY OFFLINE command has causeda vary-off process to be started for the volumespecified.

System Action: The volume is varied offline.


ANR1302E Disk volume volume name is alreadyonline.

Explanation: A VARY ONLINE command specified avolume that was already online.



ANR1303E Disk volume volume name is alreadyoffline.

Explanation: A VARY OFFLINE command specified avolume that was already offline.



ANR1304E Disk volume volume name is currently inuse.

Explanation: A VARY OFFLINE command specified avolume that is currently in use and cannot be variedoffline at this time.


User Response: Try the command again at a latertime, or attempt to determine how it is currently beingused and free it.

ANR1305I Disk volume volume name varied online.

Explanation: The specified volume has been variedonline as the result of a VARY ONLINE command.





ANR1306I Disk volume volume name varied online(read-only).

Explanation: The specified volume has been variedonline in read-only mode as the result of a VARYONLINE command.



ANR1307I Disk volume volume name varied offline.

Explanation: The specified volume has been variedoffline as the result of a VARY OFFLINE command.



ANR1308W Storage agent not sychronized withserver - restart needed.

Explanation: The storage agent has detected that apolicy, storage pool, device class, or other attributesthat is read from the server at initialization is no longervalid.

System Action: The operation of the storage agentcontinues. Depending upon what has changed on theserver the storage agent behavior may beunpredicatable and other failures may result.

User Response: The storage agent should be haltedand restarted to synchronize the storage agent with theserver.

ANR1310E Vary-on failed for disk volume volumename - insufficient memory.

Explanation: A VARY ONLINE command has beenissued for the disk volume specified, but sufficientmemory is not available to process the command.

System Action: The volume is not varied online.

User Response: Reissue the command at a later time,or make more memory available to the server.

ANR1311E Vary-on failed for disk volume volumename - unable to access disk device.

Explanation: A VARY ONLINE command has beenissued for the disk volume specified, but the server isunable to access the disk.


User Response: Attempt to determine the cause of theinability to access the volume and correct the problem.

ANR1312E Vary-on failed for disk volume volumename - error reading disk.

Explanation: A VARY ONLINE command has beenissued for the disk volume specified but the serverencounters an error reading the disk.


User Response: Attempt to determine the cause of theread error and correct the problem.

ANR1313E Vary-on failed for disk volume volumename - unsupported block size (blocksize).

Explanation: A VARY ONLINE command has beenissued for the disk volume specified, but the volume isformatted with a block size that cannot be used.


User Response: Reformat the disk with a block sizethat is an evenly divisible by 4096.

ANR1314E Vary-on failed for disk volume volumename - reduced capacity (was countblocks, now count blocks.

Explanation: A VARY ONLINE command has beenissued for the disk volume specified, but the size of thevolume does not match the size expected.


User Response: Restore the volume or otherwisecorrect the disk volume size, and reissue the command.

ANR1315E Vary-on failed for disk volume volumename - invalid label block.

Explanation: A VARY ONLINE command has beenissued for the disk volume specified, but the label blockof the volume is invalid or cannot be read.


User Response: Restore or reformat the disk volume.

ANR1316E Vary-on failed for disk volume volumename - internal error detected.

Explanation: A VARY ONLINE command has beenissued for the disk volume specified, but fails due to aninternal server error.





ANR1320W Vary-on not possible for disk volumevolume name - access state is″unavailable″.

Explanation: A VARY ONLINE command has beenissued for the disk volume specified, but the status ofthe volume is unavailable.


User Response: If necessary, use the UPDATEVOLUME command to change the status of thevolume, and reissue the command.

ANR1321W Vary-on not possible for disk volumevolume name - access state is ″destroyed″.

Explanation: A VARY ONLINE command has beenissued for the disk volume specified, but the status ofthe volume is destroyed.


User Response: If necessary, use the UPDATEVOLUME command to change the status of thevolume, and reissue the command.

ANR1330E The server has detected possiblecorruption in an object being restored ormoved. The actual values for theincorrect frame are: magic magic hdrversion ver hdr length hdrLen sequencenumber seqNum data length length serverid srvId segment id segId crc crc.

Explanation: An invalid frame has been detected. Thismay indicate corruption within the object beingrestored or moved.

System Action: The object is not restored or moved.

User Response: Please retry the failing operation. Ifthe operation fails again, please contact your servicerepresentative and provide the information from thismessage.

ANR1331E Invalid frame detected. Expected magicmagic sequence number seqNum server idservId segment id segId.

Explanation: This message indicates the expectedvalues when an invalid frame is detected.


User Response: If contacting support, please providethe information from this message.

ANR1340I Scratch volume volume name is nowdefined in storage pool storage pool name.

Explanation: The scratch volume specified has beenadded to the storage pool shown.



ANR1341I Scratch volume volume name has beendeleted from storage pool storage poolname.

Explanation: The scratch volume specified is nolonger in use and has been removed from the indicatedstorage pool.



ANR1342I Scratch volume volume name is nowpending - volume will be deleted fromstorage pool storage pool name after thereuse delay period for this storage poolhas elapsed.

Explanation: All files have been deleted from theindicated scratch volume. The volume will not beremoved from the storage pool until the reuse delaytime period for the indicated storage pool has elapsed.If the storage pool does not have a reuse tdelayspecified, the indicated volume was emptied after ithad been requested by another process. It will be in thefull or filling state if the process places more data onthe tape, or it will be removed from the storage poolafter it is no longer required.



ANR1343I Unable to delete scratch volume volumename.

Explanation: A scratch volume cannot be deleted fromthe server and returned to scratch at this time becauseall the locks have not be released. A number of retrieshave been attempted.

System Action: None

User Response: The scratch volume will beautomatically deleted when the server is restarted. Or,you may manually delete this volume later, using theDELETE VOLUME command.

ANR1344I Volume volume name cannot be reused,remove from server storage.

Explanation: A volume that was full and is nowempty cannot be reused by the server due to theWORM (Write Once - Read Many) characteristics of themedia.

System Action: The volume will have a state wherethe access mode is READONLY, the status is FULL andthe percent utilized is 0.0. The volume is consideredempty for storage pool occupancy and utilization fields.

User Response: If the volume is in a library, it must



first be removed using the CHECKOUT LIBVOLUMEcommand prior to manually deleting the volume. Usethe DELETE VOLUME command to remove thevolume from server storage.

ANR1360I Output volume volume name opened(sequence number sequence number).

Explanation: During a sequential data operation, thevolume specified has been opened for output as thevolume number shown.



ANR1361I Output volume volume name closed.

Explanation: During a sequential data operation, thevolume specified has been closed because the export ordump is complete.



ANR1362I Output volume volume name closed(full).

Explanation: During a sequential data operation, thevolume specified has been closed because the volume isfull.



ANR1363I Input volume volume name opened(sequence number sequence number).

Explanation: Because of a sequential data operation,the volume specified has been opened for input as thevolume number shown.



ANR1364I Input volume volume name closed.

Explanation: During a sequential data operation, thevolume specified has been closed because the operationis complete.



ANR1365I Volume volume name closed (endreached).

Explanation: During a sequential data operation, thevolume specified has been closed because processing ofthe volume is complete.



ANR1366W Input volume volume name contains aninvalid identifier.

Explanation: During a sequential data operation, thevolume specified has been mounted but contains aninvalid identifier.

System Action: The volume is not used.

User Response: Make sure you specified the correctvolume for the operation. If a LOADDB operation wasbeing performed on MVS, the command syntax may bespecified by using a ddname or by specifying a deviceclass name. You must use the same method that wasused when the database was originally dumped. If youdid not, this error message will be displayed. Tryloading the data base by using the other method ofsyntax (ddname).

ANR1367W Import volume volume name was writtenby a different export process.

Explanation: During an IMPORT operation, thevolume specified has been mounted but contains anexport identifier that does not match the importprocess.


User Response: Supply a volume created by theproper export process.

ANR1368W Input volume volume name containssequence number sequence number;volume sequence number sequencenumber is required.

Explanation: During a sequential data operation, thevolume specified has been mounted but contains thewrong volume sequence number.


User Response: Supply the volume with the propersequence number. The volume history file can help youchoose the correct volume.

ANR1369E Input volume volume name containsVersion 1 dump.

Explanation: During a sequential data operation, thevolume specified has been mounted but appears tocontain a version 1 database dump.

System Action: The volume is not used. The operationis terminated.

User Response: Make sure you specified the correctvolume for the operation. A Version 1 database dumpmay not be loaded into a Version 2 server. The Version1 database dump must only be loaded into a Version 1server.



ANR1370E Insufficient number of mount pointsavailable in device class device class name.

Explanation: During IMPORT or EXPORT processing,the server cannot allocate sufficient mount points forthe device class specified. The device class associatedwith the EXPORT or IMPORT drive only has a mountlimit of one. The operation needs to read or write filedata from or to the same device class because file datais being imported or exported.

System Action: The IMPORT or EXPORT command isended and server operation continues.

User Response: Make more mount points available.

ANR1400W Mount request denied for volumevolume name - mount canceled.

Explanation: The volume shown cannot be mountedbecause the mount request has been canceled.

System Action: The volume is not mounted.


ANR1401W Mount request denied for volumevolume name - mount failed.

Explanation: The volume shown cannot be mountedbecause the mount request cannot be completedsuccessfully. Possible reasons include, an error in devicespecifications to the server or the mount request timedout.


User Response: If the device specifications (DEFINEDEVCLASS and so forth) are in error, correct them andreissue the command that requested the volume to bemounted.

ANR1402W Mount request denied for volumevolume name - volume unavailable.

Explanation: The volume shown cannot be mountedbecause it is not available.



ANR1403W Scratch volume mount request denied -mount canceled.

Explanation: A scratch volume cannot be mountedbecause the mount request has been canceled.

System Action: The scratch volume is not mounted.


ANR1404W Scratch volume mount request denied -mount failed.

Explanation: A scratch volume cannot be mountedbecause the mount request cannot be completedsuccessfully. Possible reasons include, an error in devicespecifications to the server or the mount request timedout.


User Response: If the device specifications (forexample, DEFINE DEVCLASS) are in error, correctthem and reissue the command that requested thevolume to be mounted.

ANR1405W Scratch volume mount request denied -no scratch volume available.

Explanation: A scratch volume cannot be mountedbecause no scratch volume is available.



ANR1406E Simultaneous write operation could notrelease all the acquired mount points.

Explanation: A simultaneous write to a primary andcopy storage pools failed to release all the acquiredmount points. When a simultaneous write operationbegins it will attempt to acquire all of the necessarymount points. If a mount point cannot be acquired orthe simultaneous write operation has to wait for amount point, then the operation will release any mountpoints it has already acquired. This prevents thesimultaneous write operation from holding mountpoints and other mount requests from completing. Thismessage is issued if one of the previously acquiredmount points cannot be released.

System Action: At least one mount point acquired bysimultaneous write operation is not released.


ANR1409W Volume volume name already in use -skipped.

Explanation: During an export or database backup, avolume cannot be used because it is already defined ina storage pool, or has already been used by the currentoperation, or has been previously used by an export ordatabase backup operation (as recorded in the volumehistory) or is in use by another process.

System Action: The operation continues and thevolume is skipped.

User Response: Use the QUERY VOLUME commandto display the names of volumes that are defined toserver storage pools. Use the QUERY VOLHISTORYcommand to display the names of volumes that have



been used for export or database backup operations. Ifno volume names are displayed using the querycommands described above, ensure that the volumeidentified in this message has not been specified orused more than once in the operation being performed.

ANR1410W Access mode for volume volume namenow set to ″unavailable″.

Explanation: The status of the volume shown hasbeen set to unavailable.



ANR1411W Access mode for volume volume namenow set to ″read-only″ due to writeerror.

Explanation: Because of an unrecoverable write erroron the volume shown, the status of the volume hasbeen set to read-only.



ANR1412W Volume volume name access mode is″unavailable″.

Explanation: At server startup, the status of theindicated volume is unavailable.



ANR1413W Volume volume name access mode is″read-only″.

Explanation: At server startup, the status of theindicated volume is read-only.



ANR1414W Volume volume name access mode is″read-only″ due to previous write error.

Explanation: At server startup, the status of theindicated volume is read-only due to an unrecoverablewrite error, or because an administrator used theUPDATE VOLUME command to set the volume accessmode to read-only.



ANR1415W Volume volume name access mode is″destroyed″.

Explanation: At server startup, the status of theindicated volume is destroyed.



ANR1416W Volume volume name access mode is″offsite″.

Explanation: At server startup, the status of theindicated volume is offsite.



ANR1417W Access mode for volume volume namenow set to ″read-only″ due to excessiveread error.

Explanation: Because of an numerous read errors onthe volume shown, the status of the volume has beenset to read-only.


User Response: Use QUERY VOLUMEFORMAT=DETAILED for the volume to view theaccess mode and number of read errors. You may wantto use the MOVE DATA command to move theretrievable data from this volume to another volume.For the damaged files, use the RESTORE VOLUMEcommand to restore a readable copy of the file to thestorage pool.

ANR1418E command name: Export commands thattarget another server cannot be issuedfrom the server console.

Explanation: An EXPORT command that targetsanother server was issued from the server console. Thiscommand cannot be issued from the server consolebecause it requires authentication of the issuingadministrator on the target server.


User Response: Issue the command from anadministrative client.

ANR1419E command name : FROMDATE must bespecified when FROMTIME isspecified.

Explanation: A command that supports theFROMDATE and FROMTIME parameters was issuedwith the FROMTIME parameter specified, but withoutthe FROMDATE parameter. When the FROMTIME



parameter is used, the FROMDATE parameter must bespecified.


User Response: Reissue the command with both theFROMDATE and FROMTIME parameters specified.

ANR1420W Read access denied for volume volumename - volume access mode =″unavailable″.

Explanation: An attempt to access the named volumefor reading fails because the volume status isunavailable.

System Action: The volume is not used for readaccess.


ANR1421W Read access denied for volume volumename - volume offline.

Explanation: An attempt to access the named volumefor reading failed because the volume is offline.



ANR1422W Read access denied for volume volumename - volume access mode=″offsite″.

Explanation: An attempt to access the named volumefor reading failed because the volume status is offsite.



ANR1423W Scratch volume volume name is emptybut will not be deleted - volume accessmode is ″offsite″.

Explanation: The named scratch volume is empty butwill not be deleted at this time because the access modeis offsite.


User Response: After bringing the volume onsite,change the access mode to read-only so the volume willbe deleted.

ANR1424W Read access denied for volume volumename - volume access mode=″destroyed″.

Explanation: An attempt to access the named volumefor reading failed because the volume status isdestroyed.



ANR1425W Scratch volume volume name is emptybut will not be deleted - volume state is″mountablenotinlib″.

Explanation: The named scratch volume is empty butwill not be deleted at this time because the state of thevolume is MOUNTABLENOTINLIB.


User Response: When the volume is moved by MOVEMEDIA WHERESTATE=MOUNTABLENOTINLIB, thescratch empty volume is deleted.

ANR1430W Retrieval request denied for storagepool storage pool name - accessmode=″unavailable″.

Explanation: An attempt was made to retrieve a filefrom the storage pool shown, but the access mode ofthe storage pool is unavailable.

System Action: The file is not retrieved from thisstorage pool. If possible, the file is retrieved fromanother storage pool.

User Response: Consider changing the access modefor the storage pool.

ANR1431E An error occurred while writing to sideA of volume volume name. An attemptwill be made to write to side B of thisvolume.

Explanation: An error occurred while writing to sideA of a two-sided volume.

System Action: No additional data will be written toside A of this volume. Any remaining space on side Awill not be used. An attempt will be made to use thereverse side (side B) of the volume.

User Response: None required if the side B can beused successfully. However, the administrator shouldinvestigate the cause of the error and may want tomove data from this volume.

ANR1432I Updating device configurationinformation to defined files.

Explanation: The server is updating deviceconfiguration information for the files or data setsspecified with the DEVCONFIG option in the serveroptions file.





ANR1433I Device configuration informationsuccessfully written to file name.

Explanation: Device configuration information wassuccessfully written to the file specified.



ANR1434W No files have been identified forautomatically storing deviceconfiguration information.

Explanation: The server is unable to automaticallyupdate device configuration file. No files wereidentified using the DEVCONFIG option in the serveroptions file.


User Response: If you would like to have the serverautomatically record device configuration informationto assist in server recovery, use the DEVCONFIGoption in the server options file to specify where deviceconfiguration information should be written. If youupdate the options file, halt and then restart the serverso the changes can take effect.

ANR1435E Server could not write deviceconfiguration information to devconfigfile name.

Explanation: While attempting to write deviceconfiguration information to defined files, the servercannot write to the file name specified.

System Action: The server cannot write deviceconfiguration information to the specified file.

User Response: Examine error messages that mayhave been displayed prior to this message and correctany problems, if possible. Make sure that the server hasproper authority to write to the file indicated and thatthere is sufficient space in the file system for the file.On MVS, make sure that the data set has been allocatedand that the server has authority to write to the dataset. After the problem has been corrected, use theBACKUP DEVCONFIG command to write deviceconfiguration information to the file.

ANR1436E Device configuration file devconfig filename cannot be opened.

Explanation: While attempting to write deviceconfiguration information to device configuration files,the server cannot open the file name specified.

System Action: The server does not write deviceconfiguration information to the file specified.

User Response: Examine error messages that mayhave been displayed prior to this message and correctany problems, if possible. Make sure that the server has

proper authority to write to the file indicated and thatthere is sufficient space in the file system for the file.On MVS, make sure that the data set has been allocatedand that the server has authority to write to the dataset. After the problem has been corrected, use theBACKUP DEVCONFIG command to write deviceconfiguration information to the file.

ANR1437E No device configuration files could beused.

Explanation: The server attempts to read deviceconfiguration information from defined files and cannotopen any of the files.

System Action: The operation is ended.

User Response: Examine error messages that mayhave been displayed prior to this message and correctany problems, if possible. Ensure that the defineddevice configuration files have been created. If you canstart the server, you can create the files by using theBACKUP DEVCONFIG command. If you cannot startthe server, you will need to create a deviceconfiguration file by editing the file and adding theappropriate DEFINE commands for the device class,drive, and library definitions. The contents andrequirements for this file are described in theAdministrator’s Guide. Make sure that the server hasproper authority to read from the defined deviceconfiguration files.

ANR1438W Skipping device configuration file:devconfig file name.

Explanation: While attempting to read deviceconfiguration information from a defined deviceconfiguration file, the server encounters problems inprocessing the definitions included in the file.

System Action: The specified file is skipped, and thenext one specified in the server options file will beused.

User Response: Examine error messages that mayhave been displayed prior to this message tounderstand why the file could not be used. When youcan start the server again, you can refresh this file byusing the BACKUP DEVCONFIG command.

ANR1439E Allocate prohibited - transaction failed.

Explanation: While attempting to preallocate storageon a storage pool, the server detected that thetransaction for this operation has previously failed. Thiserror may occur when a large file is selected for backupand the client did not properly estimate the file size.There may not be enough space in the storage pool forthe file.

System Action: An internal error is reported by theserver and the operation being performed is ended.

User Response: Examine error messages that may



have been displayed prior to this message for moreinformation.

ANR1440I All drives in use. Process process numberbeing preempted by higher priorityoperation.

Explanation: When a high priority operationattempted to find an available drive, all the drives werein use. To make a drive available for this operation, theindicated process is being cancelled by the system.

System Action: The lower priority process is cancelledto make a mount point (drive) available.

User Response: When a drive again becomesavailable, restart the process that was cancelled. If theprocess was a migration or reclamation process, it willbe automatically restarted when needed. If this messageappears frequently, you may want to increase thenumber of drives available. See the MOUNTLIMITparameter on the UPDATE DEVCLASS command.

ANR1441I Volume volume name is in use. Processprocess number being preempted byhigher priority operation.

Explanation: When a high priority operationattempted to use a volume, it was in use. To make avolume available for this operation, the indicatedprocess is being cancelled by the system.

System Action: The lower priority process is cancelledto the volume available.

User Response: Restart the process that was cancelled.It will wait until the higher priority process is finishedwith the volume. If the cancelled process was amigration or reclamation process, it will beautomatically restarted when needed.

ANR1442E Invalid storage pool for store operation:storage pool.

Explanation: The storage pool selected for a storeoperation (for example, backup or archive) was not aNATIVE or NONBLOCK data format storage pool. Thismay be caused by an incorrect management class beingassigned to an object.


User Response: Ensure that the copy groupdestination storage pool of the assigned managementclass has the appropriate NATIVE or NONBLOCK dataformat.

ANR1450E command name: Invalid command scriptname: command script name.

Explanation: An invalid script name was specified fora DEFINE, UPDATE, or DELETE SCRIPT command.


User Response: Reenter the command specifying avalid command name.

ANR1451E command name: Invalid command:command.

Explanation: An invalid command was specified for aDEFINE, UPDATE, or DELETE SCRIPT command.


User Response: Reenter the command specifying avalid server command.

ANR1452E command name: Invalid line number: linenumber.

Explanation: An invalid line number was specified fora DEFINE, UPDATE, or DELETE SCRIPT command.


User Response: Reenter the command specifying avalid line number.

ANR1453E command name: Command script commandscript name already exists.

Explanation: The script name specified in a DEFINESCRIPT command already exists.


User Response: Reenter the command specifying adifferent command name.

ANR1454I command name: Command script commandscript name defined.

Explanation: The script name specified in a DEFINESCRIPT command was successfully defined.

System Action: None

User Response: None

ANR1455E command name: Command script commandscript name does not exist.

Explanation: The script name specified in a DEFINE,UPDATE, or DELETE SCRIPT command does not exist.


User Response: Reenter the command specifying adifferent command name.

ANR1456I command name: Command script commandscript name updated.

Explanation: The script name specified in an UPDATESCRIPT command was successfully updated.

System Action: None

User Response: None



ANR1457I command name: Command script commandscript name deleted.

Explanation: The script name specified in a DELETECOMMAND command was successfully deleted.

System Action: None

User Response: None

ANR1458I command name: Line line number wasdeleted from command script commandscript name.

Explanation: The specified line number was deletedfrom the command script as a result of a DELETESCRIPT command.

System Action: None

User Response: None

ANR1459E command name: Command script commandscript name, line line number does notexist.

Explanation: The line in command script namespecified in a UPDATE, or DELETE SCRIPT commanddoes not exist.


User Response: Reenter the command specifying adifferent line number.

ANR1460I command name: Command script commandscript name copied to new command scriptname.

Explanation: The specified command script wascopied to a new script with the COPY SCRIPTcommand.

System Action: None

User Response: None

ANR1461I command name: Executing commandscript command script name.

Explanation: The specified command script is beingexecuted as a result of a RUN command.

System Action: None

User Response: None

ANR1462I command name: Command script commandscript name completed successfully.

Explanation: The specified command script, startedwith a RUN command, has successfully completed.

System Action: None

User Response: None

ANR1463E command name: Command script commandscript name completed in error.

Explanation: The specified command script, startedwith a RUN command, encountered errors.

System Action: Part or all of the command lines inthe script ended in error. Command processing isterminated.

User Response: Examine the messages preceeding thismessage to determine the cause of the error. Correct thecommand script and reissue the command.

ANR1464E command name: Command script commandscript name, line line number, parameterparameter number was not specified:command line.

Explanation: All parameters required to execute acommand script were not specified in the RUNcommand.

System Action: The command fails.

User Response: Reenter the RUN command specifyingall required parameters.

ANR1465E command name: Command script commandscript name, line line number, parameter isinvalid: command line.

Explanation: An invalid parameter was encounteredin a command script.


User Response: Correct the script definition andreexecute the RUN command.

ANR1466I command name: Command script commandscript name, Line line number : commandline.

Explanation: The specified line for the commandscript is being executed. The contects of the line beingexecuted are displayed.

System Action: None

User Response: None

ANR1467E command name: Command script commandscript name, did not end in anon-continued line command line.

Explanation: The specified command script did notend in a line that had no continuation character (-).


User Response: Correct the specified script so that itends in a line that is not continued to the next line.



ANR1468E command name: Command script commandscript name, continued line is too long

Explanation: The specified command script withcontinuation lines is too long to be executed.


User Response: Correct the specified command scriptso that it is shorter.

ANR1469E command name: Command script commandscript name, Line line number is anINVALID command : command line.

Explanation: The specified line for the commandscript is not a valid server command. This message isdisplayed when a RUN command is executed with thePREVIEW=YES parameter specified.

System Action: Command Preview processing fails

User Response: Correct the script and reenter theRUN command.

ANR1470I command name: Command script commandscript name completed successfully(PREVIEW mode).

Explanation: The specified command script, startedwith a RUN command, has successfully completed.



ANR1471E command name: Command script commandscript name completed in error(PREVIEW mode).

Explanation: The specified command script, startedwith a RUN command, encountered errors.

System Action: Part or all of the command lines inthe command script ended in error. Commandprocessing is terminated.

User Response: Examine the messages preceeding thismessage to determine the cause of the error. Correct thescript and reissue the command.

ANR1472I command name: Command script commandscript name renamed to new commandscript name.

Explanation: The specified command script wasrenamed with the RENAME SCRIPT command.



ANR1473E command name: A command line cannotbe specified when the FILE= parameteris used.

Explanation: The FILE= parameter was specified inthe DEFINE SCRIPT command AND a command linewas also specified for the SCRIPT. When the FILE=parameter is specified, a command line cannot bespecified.


User Response: Reenter the command without thecommand line OR the FILE= parameter.

ANR1474E command name: A line number cannot bespecified when the FILE= parameter isused.

Explanation: The FILE= parameter was specified inthe DEFINE SCRIPT command AND a line numberwas also specified for the SCRIPT. When the FILE=parameter is specified, a line number cannot bespecified.


User Response: Reenter the command without theline number OR the FILE= parameter.

ANR1475E command name: File file name could not beopened.

Explanation: A filename was specified in a commandbut the specified file could not be opened by the server.


User Response: Examine any messages that mightappear prior to this one in the activity log to determineif the error can be found. If the file was to exist for useby the command, ensure that the file does exists andthat the server has proper authority to access the file. Ifthe file was to be created by the command, ensure thatthe filesystem has sufficient space and that the serverhas authority to create the file in the location specified.

ANR1476E command name: File file name contains nodata.

Explanation: The FILE= parameter was specified in acommand but the specified file did not contain scriptcommand lines.


User Response: Add script command lines to the fileor specify another file and reenter the command.



ANR1477E command name: The OUTPUTFILEparameter may only be specified whenFORMAT=RAW or FORMAT=MACROis specified.

Explanation: The OUTPUTFILE parameter wasspecified in a QUERY SCRIPT command but theFORMAT parameter did not specify RAW or MACROoutput. When outputting the QUERY to a file, youMUST specify RAW or MACRO output format.


User Response: Reenter the command specifyingtheproper value for the FORMAT parameter or do notspecify the OUTPUTFILE parameter.

ANR1478E command name: Error writing to file filename.

Explanation: An error was encountered while writingto the file specified.


User Response: Examine any messages that mightappear prior to this one in the activity log to determineif the error can be found. Ensure that the filesystem hassufficient space and that the server has authority tocreate the file in the location specified.

ANR1479I command name: Query output waswritten to file file name.

Explanation: The output from the specified query wassuccessfully written to the specified file.

System Action: The command completes successfully.


ANR1480E command name: Description text is toolong.

Explanation: The specified description text is too longfor a command that allows description text to bespecified.


User Response: Reenter the command specifying ashorter description.

ANR1481E command name: A command line ordescription must be specified.

Explanation: An UPDATE SCRIPT command wasspecified with out a command line (script line) ordescription text.


User Response: Reenter the command specifying acommand line or description text.

ANR1482I command name: Found label statement labelon line line number and continuing.

Explanation: This message is issued during a RUNcommand (VERBOSE=YES) to indicate that the targetlabel for a GOTO statement was found.

System Action: Command processing continues.


ANR1483I command name: Line line numbercondition IF(condition) is NOT true -statement is skipped.

Explanation: This message is issued during a RUNcommand (VERBOSE=YES) to indicate that the a returncode condition check failed and the IF(..) statement isskipped.



ANR1484I command name: Line line numbercondition IF(condition) is TRUE -statement will be executed.

Explanation: This message is issued during a RUNcommand (VERBOSE=YES) to indicate that the a returncode condition check succeeded and the IF(..) statementis executed.



ANR1485I command name: Ending SCRIPT withEXIT statement on line line number.

Explanation: This message is issued during a RUNcommand (VERBOSE=YES) to indicate that an EXITstatement was encountered and SCRIPT terminationwill end.

System Action: The SCRIPT command ends.


ANR1486I command name: Executing line line numberGOTO label name.

Explanation: This message is issued during a RUNcommand (VERBOSE=YES) to indicate that a GOTOstatment was encountered and processing will skip tothe named label.

System Action: SCRIPT processing continues.




ANR1487I command name: Command return code issymbolic return code (return code severity).

Explanation: This message is issued during a RUNcommand (VERBOSE=YES) to indicate the return codethat was returned from the latest command.



ANR1488E command name: Line line numbercondition IF(condition) is not a validcondition.

Explanation: This message is issued if an IF()statement in a SCRIPT does not specify propercondition values.

System Action: Command processing fails.

User Response: Reenter the command using validconditions for the IF() statement.

ANR1489E command name: Line line number is aGOTO to a label (label name) that doesnot exist or is associated with a lineprior to line line number.

Explanation: This message is issued if a GOTOstatment in a SCRIPT does not specify a label thatexists in the SCRIPT, or that does exist but is associatedwith a line prior to the line that contains the GOTOstatement.


User Response: Correct the SCRIPT definition andreenter the RUN command.

ANR1490W command name: Command script commandscript name does not contain anycommands.

Explanation: The script name specified in a RUNcommand does not contain any commands.

System Action: The RUN operation fails (has nothingto do).

User Response: Server command Scripts that containno commands will not execute. Add command lines tothe Script and reenter the RUN command.

ANR1491E Server command scripts cannot bestarted from the server console.

Explanation: A server command script RUNcommand was issued from the server console. Servercommand scripts cannot be started from the serverconsole because they may require a long time completeand the server console should be available to controlother server functions.


User Response: Start the server command script froman administrative client or schedule it for executionusing the administrative command scheduler.

ANR1492E command name: A loop has been detectedin server command script RUNcommands - command failed.

Explanation: A server command script DEFINE orUPDATE command has created a situation where oneor more scripts invoke each other in a loop that cancause the scripts to run idefinitely.

System Action: The command fails to update theserver command script.

User Response: Server command scripts can invokeeach other, but not in a fashion that causes a potentialloop in their execution. Specify the scripts in a mannerthat does not cause them to invoke each other in aloop.

ANR1493E Command: Administrator administratorname is not authorized to update ordelete command script command scriptname.

Explanation: The specified administrator has enteredthe indicated command, but this administrator does nothave the proper authority necessary to update or deletethis command script. If an administrator does not havesystem authority, they must have previously created orupdated the script.


User Response: Issue the command from a properlyauthorized administrator ID, or contact theadministrator that created the script.

ANR1494I command name: Command return code isnumeric return code.

Explanation: This message is issued during a RUNcommand (VERBOSE=YES) to indicate the numericreturn code that was returned from the latestcommand.



ANR1495E command name: command script name iscurrently running. Update or delete cannot be performed.

Explanation: An UPDATE or DELETE SCRIPT wasattempted on a script that is currently running.




User Response: Reenter the command when the scriptis not running.

ANR1496I

Explanation: The ISSUE MESSAGE command with aseverity indicator of INFORMATION was issued.



ANR1497W

Explanation: The ISSUE MESSAGE command with aseverity indicator of WARNING was issued.



ANR1498E

Explanation: The ISSUE MESSAGE command with aseverity indicator of ERROR was issued.



ANR1499S

Explanation: The ISSUE MESSAGE command with aseverity indicator of SEVERE was issued.



ANR1500I Policy domain domain name defined.

Explanation: In response to the DEFINE DOMAINcommand, the policy domain domain name has beendefined in the server database.



ANR1501I Policy domain domain name deleted.

Explanation: In response to the DELETE DOMAINcommand, the policy domain domain name has beendeleted from the server database. All policy sets,management classes, copy groups, and schedulesrelated to the domain have also been removed.



ANR1502I Policy domain domain name updated.

Explanation: In response to the UPDATE DOMAINcommand, the policy domain domain name has beenupdated in the server database.



ANR1503I Policy domain domain name copied todomain target domain.

Explanation: In response to the COPY DOMAINcommand, the policy domain domain name has beencopied to a new policy domain named target domain.All policy sets, management classes, and copy groupsare also copied to the target domain policy domain.



ANR1504I Command: No matching domains.

Explanation: The server cannot find any policydomains with names that match the specificationentered in the command command.


User Response: Reissue the command with aspecification that matches an existing policy domainname. Use the QUERY DOMAIN command to obtain alist of the names of existing policy domains.

ANR1505W The BACKUP copy group inmanagement class management class namespecifies a table of contents destinationstorage pool : storage pool name that doesnot exist. If this pool does not existwhen policy set policy set name isactivated, the creation of the table ofcontents may fail for an image backupwhen this management class is used forthe backup.

Explanation: This message may be returned from theDEFINE COPYGROUP, UPDATE COPYGROUP,VALIDATE POLICYSET or ACTIVATE POLICYSETcommand. During the indicated command processing,the server has found a backup copy group that has atable of contents (TOC) destination referring to anundefined storage pool named storage pool name. If thisstorage pool is undefined when the policy set isactivated, the creation of the TOC for an image backupwill fail if its TOC creation binds to the managementclass whose copy groups reference this pool.


User Response: To locate the copy groups that refer tothe undefined storage pool, issue the QUERYCOPYGROUP command. To change the TOC



destination to refer to an existing storage pool, issuethe UPDATE COPYGROUP command. To define thestorage pool, an authorized administrator can issue theDEFINE STGPOOL command.

ANR1506E Command: An incorrect storage poolname - storage pool name was specifiedfor the TOC destination.

Explanation: Server processing for the commandcommand fails because the storage pool name pool namespecified for the table of contents (TOC) destination is acopy pool. A copy storage pool is not a valid copygroup TOC destination.


User Response: Reissue the command using a storagepool name that is not a copy pool. For a list of namesof defined storage pools, issue the QUERY STGPOOLcommand.

ANR1507I Table of contents load retention is set tonumber of minutes minutes.

Explanation: The number of minutes that theunreferenced table of contents (TOC) data will remainloaded in the server database has been set to the valueindicated with the SET TOCLOADRETENTIONcommand.



ANR1508E Command: An incorrect table of contentsload retention retention value wasspecified.

Explanation: A SET TOCLOADRETENTIONcommand has been entered that specifies an invalidtable of contents (TOC) retention period.


User Response: Reissue the command with a validretention period.

ANR1510I Policy set set name defined in policydomain domain name.

Explanation: In response to the DEFINE POLICYSETcommand, the policy set named set name has beendefined in the policy domain named domain name in theserver database.



ANR1511I Policy set set name deleted from policydomain domain name.

Explanation: In response to the DELETE POLICYSETcommand, the policy set set name has been deleted fromthe policy domain domain name in the server database.



ANR1512I Policy set set name updated in policydomain domain name.

Explanation: In response to the UPDATE POLICYSETcommand, the policy set set name has been updated inthe policy domain domain name in the server database.



ANR1513I Policy set set name copied to set new setname in policy domain domain name.

Explanation: In response to the COPY POLICYSETcommand, the policy set set name has been copied tothe policy set new set name in the policy domain nameddomain name. All management classes and copy groupsare also copied to the policy set new set name.



ANR1514I Policy set set name activated in policydomain domain name.

Explanation: In response to the ACTIVATEPOLICYSET command, the policy set set name has beenactivated in the policy domain domain name. Allmanagement class and copy group definitions in thepolicy set will be used by clients that start sessionsafter this command is committed. Clients that currentlyhave sessions established with the server will use thepolicy definitions in the previously active policy set forthe domain.

System Action: The server replaces the activemanagement class and copy group definitions for thepolicy domain with the definitions found in thespecified policy set. These values are returned to clientnodes that start a session with the server after thiscommand is committed to the server database.


ANR1515I Policy set set name validated in domaindomain name (ready for activation).

Explanation: This message may be displayed inresponse to a VALIDATE POLICYSET command. Thepolicy set set name has been checked in the domaindomain name to see if the management class and copy



group definitions are adequate for activating the policyset. This message indicates that the policy set may beactivated. Warning messages may be issued prior tothis message if there are discrepancies in the policy setwith respect to the set that is currently active in thepolicy domain.

System Action: The server checks its definitions todetermine the policy set’s qualifications for activation.The server does not activate the policy set.

User Response: If you are satisfied with any warningmessages that may have been issued prior to thismessage concerning any possible discrepancies in thepolicy set, issue the ACTIVATE POLICYSET commandto activate the policy set in the policy domain.Otherwise, correct the discrepancies prior to activatingthe policy set. Before the ACTIVATE POLICYSETcommand is used to activate the policy set, use thevalidate command to check policy set contents.

ANR1520I Management class class name defined inpolicy domain domain name, set set name.

Explanation: In response to the DEFINEMGMTCLASS command, the management class namedclass name has been defined in the policy set set namebelonging to the policy domain named domain name.



ANR1521I Management class class name deletedfrom policy domain domain name, set setname.

Explanation: In response to a DELETE MGMTCLASScommand, the management class named class name hasbeen deleted from the policy set set name belonging tothe policy domain domain name. All copy groupsdefined for the management class are also removed.



ANR1522I Management class class name updated inpolicy domain domain name, set set name.

Explanation: In response to the UPDATEMGMTCLASS command, the management class namedclass name has been updated in the policy domaindomain name, policy set set name.



ANR1523I Management class class name copied toclass new class name in policy domaindomain name, set set name.

Explanation: In response to the COPY MGMTCLASScommand, the management class named class name hasbeen copied to a new management class named newclass name in policy set set name belonging to policydomain domain name. All copy groups defined formanagement class class name are also copied tomanagement class new class name.



ANR1530I Backup copy group group name definedin policy domain domain name, set setname, management class class name.

Explanation: In response to the DEFINECOPYGROUP command, a backup copy group namedgroup name has been defined for the management classnamed class name in the policy set set name belonging topolicy domain domain name.



ANR1531I Backup copy group group name deletedfrom policy domain domain name, set setname, management class class name.

Explanation: In response to the DELETECOPYGROUP command, the backup copy groupnamed group name has been deleted from themanagement class named class name in the policy set setname belonging to policy domain domain name.



ANR1532I Backup copy group group name updatedin policy domain domain name, set setname, management class class name.

Explanation: In response to the UPDATECOPYGROUP command, the backup copy groupnamed group name has been updated in themanagement class named class name in the policy set setname belonging to policy domain domain name.



ANR1535I Archive copy group group name definedin policy domain domain name, set setname, management class class name.

Explanation: In response to the DEFINECOPYGROUP command, an archive copy group named



group name has been defined for the management classnamed class name in the policy set set name belonging topolicy domain domain name.



ANR1536I Archive copy group group name deletedfrom policy domain domain name, set setname, management class class name.

Explanation: In response to the DELETECOPYGROUP command, the archive copy groupnamed group name has been deleted from themanagement class named class name in the policy set setname belonging to policy domain domain name.



ANR1537I Archive copy group group name updatedin policy domain domain name, set setname, management class class name.

Explanation: In response to the UPDATECOPYGROUP command, the archive copy groupnamed group name has been updated in themanagement class named class name in the policy set setname belonging to policy domain domain name.



ANR1538I Default management class set to classname for policy domain domain name, setset name.

Explanation: The default management class for thepolicy set set name in policy domain domain name hasbeen set to the management class named class name.

System Action: If this policy set is activated, clientsuse this management class for backup-archiveprocessing by default, or if other management classesspecified for binding do not exist in the policy set.


ANR1550W Management class class name is NOTdefined in policy set set name but ISdefined in the ACTIVE policy set fordomain domain name: files bound to thismanagement class will be REBOUND tothe default management class if/whenthis set is activated.

Explanation: This message may be returned from theVALIDATE POLICYSET or ACTIVATE POLICYSETcommand. During policy set validation processing, theserver has found a management class named class namein the currently active policy set, but not defined in the

policy set being validated or activated (set name). Ifpolicy set set name is activated, files bound to thismanagement class in domain domain name areautomatically rebound to the default management classin policy set set name.


User Response: If you do not want files to be reboundto the default management class, define a managementclass with the name specified in the message for thepolicy set. To define the proper copy group attributes,reference the management class definition in theACTIVE policy set or copy the management class classname from the ACTIVE policy set to policy set set nameusing the COPY MGMTCLAS command.

ANR1551W BACKUP copygroup group name inmanagement class class name is NOTdefined in policy set set name but isdefined in the ACTIVE policy set fordomain domain name: files bound to thismanagement class will no longer bebacked up if/when set name is activated.

Explanation: This message may be returned from theVALIDATE POLICYSET or ACTIVATE POLICYSETcommand. During policy set validation processing, theserver has found a backup copy group named groupname for management class class name in the currentlyactive policy set, but the copy group is not defined forthe management class in the policy set being validatedor activated (set name). If policy set set name isactivated, files bound to management class class name indomain domain name will no longer be eligible forbackup processing.


User Response: If you want files bound to thismanagement class to be eligible for backup processing,define an archive copy group for management classclass name by using the DEFINE COPYGROUPcommand.

ANR1552W ARCHIVE copygroup group name inmanagement class class name is NOTdefined in policy set set name but isdefined in the ACTIVE policy set fordomain domain name: files bound to thismanagement class will no longer bearchived if/when set name is activated.

Explanation: This message may be returned from theVALIDATE POLICYSET or ACTIVATE POLICYSETcommand. During policy set validation processing, theserver has found an archive copy group named groupname for management class class name in the currentlyactive policy set, but the copy group is not defined forthe management class in the policy set being validatedor activated (set name). If policy set set name isactivated, files bound to management class class name in



domain domain name will no longer be eligible forarchive processing.


User Response: If you want files bound to thismanagement class to be eligible for archive processing,define an archive copy group for management classclass name by using the DEFINE COPYGROUPcommand.

ANR1553W DEFAULT Management class class namein policy set domain name set name doesnot have a BACKUP copygroup: fileswill not be backed up by default if thisset is activated.

Explanation: This message may be returned from theVALIDATE POLICYSET or ACTIVATE POLICYSETcommand. During policy set validation for policy setset name in policy domain domain name, the server hasfound that the default management class named classname does not have a backup copy group. This messagewarns the administrator that activation of this policyset results in client files not being backed up, unlessthey are bound to a management class (which has acopy group) other than the default.


User Response: To define a backup copy group for themanagement class, issue the DEFINE COPYGROUPcommand. To assign a different default managementclass for the domain, issue the ASSIGNDEFMGMTCLASS command. Take either action if youwant files to be backed up by default.

ANR1554W DEFAULT Management class class namein policy set domain name set name doesnot have an ARCHIVE copygroup: fileswill not be archived by default if thisset is activated.

Explanation: This message may be returned from theVALIDATE POLICYSET or ACTIVATE POLICYSETcommand. During policy set validation for policy setset name in policy domain domain name, the server hasfound that the default management class named classname does not have an archive copy group. Thismessage warns the administrator that activation of thispolicy set will result in client files not being allowedarchive processing unless they are bound to amanagement class (which has an archive copy group)other than the default.


User Response: To define a backup copy group for themanagement class, issue the DEFINE COPYGROUPcommand. To assign a different default managementclass for the domain, issue the ASSIGNDEFMGMTCLASS command. Take either action if youwant files to be eligible for archive processing bydefault.

ANR1555W The BACKUP copy group inmanagement class management class namespecifies a destination that does notrefer to a defined storage pool: storagepool name. If this pool does not existwhen policy set policy set name isactivated, clients will fail when usingthis management class to backup files tothe server.

Explanation: This message may be returned from theVALIDATE POLICYSET or ACTIVATE POLICYSETcommand. During policy set validation for set name, theserver has found a backup copy group destination thatreferences an undefined storage pool named pool name.If this storage pool is undefined when the policy set isactivated, backup or archive operations will fail forclients with files bound to the management class whosecopy groups reference this pool.


User Response: To locate the copy groups that refer tothe undefined storage pool, issue the QUERYCOPYGROUP command. To change the destination torefer to an existing storage pool, issue the UPDATECOPYGROUP command. To define the storage pool, anauthorized administrator can issue the DEFINESTGPOOL command.

ANR1556W The ARCHIVE copy group inmanagement class management class namespecifies a destination that does notrefer to a defined storage pool: storagepool name. If this pool does not existwhen policy set policy set name isactivated, clients will fail when usingthis management class to archive files tothe server.

Explanation: This message may be returned from theVALIDATE POLICYSET or ACTIVATE POLICYSETcommand. During policy set validation for set name, theserver has found a archive copy group destination thatreferences an undefined storage pool named pool name.If this storage pool is undefined when the policy set isactivated, backup or archive operations will fail forclients with files bound to the management class whosecopy groups reference this pool.


User Response: To locate the copy groups that refer tothe undefined storage pool, issue the QUERYCOPYGROUP command. To change the destination torefer to an existing storage pool, issue the UPDATECOPYGROUP command. To define the storage pool, anauthorized administrator can issue the DEFINESTGPOOL command.



ANR1557W The space management migrationdestination in management classmanagement class name does not refer to adefined storage pool: storage pool name. Ifthis pool does not exist when policy setpolicy set name is activated, clients willfail when using this management classto migrate space-managed files to theserver.

Explanation: This message may be returned from theVALIDATE POLICYSET or ACTIVATE POLICYSETcommand. During policy set validation for set name, theserver has found a space management migrationdestination that references an undefined storage poolnamed pool name. If this storage pool is undefinedwhen the policy set is activated, space managementmigration operations will fail for clients with filesbound to the management class that references thispool.


User Response: To locate the management class thatrefers to the undefined storage pool, issue the QUERYMGMTCLASS command. To change the destination torefer to an existing storage pool, issue the UPDATEMGMTCLASS command. To define the storage pool, anauthorized administrator can issue the DEFINESTGPOOL command.

ANR1558E The space management migrationdestination in management classmanagement class name in policy set policyset name refers to copy storage pool:storage pool name. Copy storage pools arenot a valid migration destination.

Explanation: This message may be returned from theVALIDATE POLICYSET or ACTIVATE POLICYSETcommand. During policy set validation for set name, theserver has found a space management migrationdestination that references a copy storage pool namedpool name.

System Action: Server operation continues. The policyset is not activated.

User Response: To locate the management class thatrefers to the copy storage pool, issue the QUERYMGMTCLASS command. To change the destination torefer to a non-copy storage pool, issue the UPDATEMGMTCLASS command.

ANR1559E The copy group destination for typecopy group type in management classmanagement class name in policy set policyset name refers to copy storage pool:storage pool name. Copy storage pools arenot a valid copy group destination.

Explanation: This message may be returned from theVALIDATE POLICYSET or ACTIVATE POLICYSET

command. During policy set validation for set name, theserver has found a copy group destination thatreferences a copy storage pool named pool name.

System Action: Server operation continues. The policyset is not activated.

User Response: To locate the management class thatrefers to the copy storage pool, issue the QUERYMGMTCLASS command. To change the destination torefer to a non-copy storage pool, issue the UPDATEMGMTCLASS command.

ANR1560E Command: Invalid policy domain name -domain name.

Explanation: Server processing for the commandcommand fails because the policy domain name domainname specified does not contain valid characters orcontains too many characters.

System Action: Database changes for the commandare rolled back and server operation continues. Thecommand is not successful in changing the serverdatabase.

User Response: Reissue the command and specify apolicy domain name that conforms to these namerequirements. For information on the character andlength specifications for valid policy domain names,refer to the Administrator’s Reference for your particularplatform.

ANR1561E Command: Missing policy domain name.

Explanation: Server processing for the commandcommand fails because the required policy domainparameter has not been specified.


User Response: Reissue the command and specify avalid policy domain name.

ANR1562E Command: Policy domain descriptionexceeds length limit characters.

Explanation: Server processing for the commandcommand fails because the policy domain descriptionspecified is longer than the length limit number ofcharacters allowed.


User Response: Reissue the command and specify ashorter policy domain description.



ANR1563E Command: Invalid retention period forBACKRETN parameter - retention value.

Explanation: Server processing for the copy groupcommand command fails because the value (retentionvalue) specified for the BACKRETN parameter is notvalid.


User Response: Reissue the command and specify avalid BACKRETN value. For valid BACKRETN valuesfor the DEFINE COPYGROUP or UPDATECOPYGROUP commands, refer to the Administrator’sReference for your particular platform.

ANR1564E Command: Invalid retention period forARCHRETN parameter - retention value.

Explanation: Server processing for the copy groupcommand command fails because the value (retentionvalue) specified for the ARCHRETN parameter is notvalid.


User Response: Reissue the command and specify avalid ARCHRETN value. For valid ARCHRETN valuesfor the DEFINE COPYGROUP or UPDATECOPYGROUP commands, refer to the Administrator’sReference for your particular platform.

ANR1565E Command: Invalid policy set name - setname.

Explanation: Server processing for the commandcommand fails because the policy set name set namespecified does not contain valid characters or containstoo many characters.


User Response: Reissue the command and specify apolicy set name that conforms to valid namerequirements. For information on the character andlength specifications for valid policy set names, refer tothe Administrator’s Reference for your particularplatform.

ANR1566E Command: Policy set description exceedslength limit characters.

Explanation: Server processing for the commandcommand fails because the policy set description

specified is longer than the length limit number ofcharacters allowed.


User Response: Reissue the command and specify ashorter policy set description.

ANR1567E Command: Invalid management classname - class name.

Explanation: Server processing for the commandcommand fails because the management class name classname specified does not contain valid characters orcontains too many characters.


User Response: Reissue the command and specify amanagement class name that conforms to valid namerequirements. For information on the character andlength specifications for valid management class names,refer to the Administrator’s Reference for your particularplatform.

ANR1568E Command: Management class descriptionexceeds length limit characters.

Explanation: Server processing for the commandcommand fails because the management classdescription specified is longer than the length limitnumber of characters allowed.


User Response: Reissue the command and specify ashorter management class description. Refer to theAdministrator’s Guide for your particular platform formore information.

ANR1569E Command: Invalid copy group name -group name.

Explanation: Server processing for the commandcommand fails because the copy group name group namespecified does not contain valid characters or containstoo many characters.


User Response: Reissue the command and specify acopy group name that conforms to valid name



requirements. For information on the character andlength specifications for valid copy group names, referto the Administrator’s Reference for your particularplatform.

ANR1570E Command: Invalid copy frequency -frequency value.

Explanation: Server processing for the copy groupcommand command fails because the value (frequencyvalue) specified for the FREQUENCY parameter is notvalid.


User Response: Reissue the command and specify avalid FREQUENCY value. For valid FREQUENCYvalues for the DEFINE COPYGROUP or UPDATECOPYGROUP commands, refer to the Administrator’sReference for your particular platform.

ANR1571E Command: Invalid copy destination - poolname.

Explanation: Server processing for the commandcommand fails because the storage pool name pool namespecified for the copy group destination or for the tableof contents (TOC) destination does not contain validcharacters or contains too many characters.


User Response: Reissue the command and specify astorage pool name that conforms to valid namerequirements. For information on the character andlength specifications for valid storage pool names, referto the Administrator’s Reference for your particularplatform. For a list of names of defined storage pools,issue the QUERY STGPOOL command.

ANR1572E Command: Missing copy destination.

Explanation: Server processing for the copy groupcommand command fails because the required copygroup destination is not specified.


User Response: Reissue the command and specify therequired copy group destination (DEST).

ANR1573E Command: Invalid copy type - type value.

Explanation: Server processing for the copy groupcommand command fails because the value (type value)specified for the TYPE parameter is not valid.


User Response: Reissue the command and specify avalid TYPE value. For valid TYPE values for theDEFINE COPYGROUP or UPDATE COPYGROUPcommands, refer to the Administrator’s Reference foryour particular platform.

ANR1574E Command: Invalid version count forVEREXISTS parameter - version value.

Explanation: Server processing for the copy groupcommand command fails because the value (versionvalue) specified for the VEREXISTS parameter is notvalid.


User Response: Reissue the command and specify avalid VEREXISTS value. For valid VEREXISTS valuesfor the DEFINE COPYGROUP or UPDATECOPYGROUP commands, refer to the Administrator’sReference for your particular platform.

ANR1575E Command: Invalid version count forVERDELETED parameter - version value.

Explanation: Server processing for the copy groupcommand command fails because the value (versionvalue) specified for the VERDELETED parameter is notvalid.


User Response: Reissue the command and specify avalid VERDELETED value. For valid VERDELETEDvalues for the DEFINE COPYGROUP or UPDATECOPYGROUP commands, refer to the Administrator’sReference for your particular platform.

ANR1576E Command: Invalid retention period forRETEXTRA parameter - retention value.

Explanation: Server processing for the copy groupcommand command fails because the value (retentionvalue) specified for the RETEXTRA parameter is notvalid.

System Action: Database changes for the command



are rolled back and server operation continues. Thecommand is not successful in changing the serverdatabase.

User Response: Reissue the command and specify avalid RETEXTRA value. For valid RETEXTRA valuesfor the DEFINE COPYGROUP or UPDATECOPYGROUP commands, refer to the Administrator’sReference for your particular platform.

ANR1577E Command: Invalid retention period forRETONLY parameter - retention value.

Explanation: Server processing for the copy groupcommand command fails because the value (retentionvalue) specified for the RETONLY parameter is notvalid.


User Response: Reissue the command and specify avalid RETONLY value. For valid RETONLY values forthe DEFINE COPYGROUP or UPDATE COPYGROUPcommands, refer to the Administrator’s Reference foryour particular platform.

ANR1578E Command: Invalid version count forRETVER parameter - retention value.

Explanation: Server processing for the copy groupcommand command fails because the value (retentionvalue) specified for the RETVER parameter is not valid.


User Response: Reissue the command and specify avalid RETVER value. For valid RETVER values for theDEFINE COPYGROUP or UPDATE COPYGROUPcommands, refer to the Administrator’s Reference foryour particular platform.

ANR1579E Command: Invalid copy mode - modevalue.

Explanation: Server processing for the copy groupcommand command fails because the value (mode value)specified for the MODE parameter is not valid.


User Response: Reissue the command and specify avalid MODE value. For valid MODE values for theDEFINE COPYGROUP or UPDATE COPYGROUPcommands, refer to the Administrator’s Reference foryour particular platform.

ANR1580E Command: Invalid copy serializationmode - serialization value.

Explanation: Server processing for the copy groupcommand command fails because the value (serializationvalue) specified for the SERIALIZATION parameter isnot valid.


User Response: Reissue the command and specify avalid SERIALIZATION value. For validSERIALIZATION values for the DEFINE COPYGROUPor UPDATE COPYGROUP commands, refer to theAdministrator’s Reference for your particular platform.

ANR1581E Command: The option option is valid onlyfor backup copy groups.

Explanation: Server processing for the archive copygroup command command fails because the optionspecified is only valid for backup copy groupdefinitions.


User Response: Reissue the command specifying validarchive copy group options, or specify TYPE=BACKUPif the intent is to operate on a backup copy group. Forvalid archive copy group options, refer to theAdministrator’s Reference and Administrator’s Guide foryour particular platform.

ANR1582E Command: The option option is valid onlyfor archive copy groups.

Explanation: Server processing for the backup copygroup command command fails because the optionspecified is only valid for archive copy groupdefinitions.


User Response: Reissue the command specifying validbackup copy group options, or specifyingTYPE=ARCHIVE if the intent is to operate on anarchive copy group. For valid backup copy groupoptions, refer to the Administrator’s Reference andAdministrator’s Guide for your particular platform.



ANR1583E Command: Copy frequency for archivecopy groups must be CMD - frequencyvalue is not valid.

Explanation: Server processing for the archive copygroup command command fails because a value otherthan CMD has been specified for the FREQUENCYparameter. The only value that may be specified for thearchive copy group FREQUENCY parameter is CMD.


User Response: Reissue the command specifyingCMD for the FREQUENCY parameter, or omitting theFREQUENCY parameter because the default value forFREQUENCY is CMD for archive copy groups. Forvalid archive copy group options, refer to theAdministrator’s Reference and Administrator’s Guide foryour particular platform.

ANR1584E Command: Copy mode for archive copygroups must be ABSOLUTE - mode valueis not valid.

Explanation: Server processing for the archive copygroup command command fails because a value otherthan ABSOLUTE has been specified for the MODEparameter. The only value that may be specified for thearchive copy group MODE parameter is ABSOLUTE.


User Response: Reissue the command specifyingABSOLUTE for the MODE parameter, or omitting theMODE parameter because the default value for MODEis ABSOLUTE for archive copy groups. For validarchive copy group options, refer to the Administrator’sReference and Administrator’s Guide for your particularplatform.

ANR1585E Command: Policy set ACTIVE cannot bemodified.

Explanation: Server processing for the commandcommand fails because the policy set name ACTIVE isspecified. Objects in the ACTIVE policy set for adomain may only be changed through activation ofanother policy set.


User Response: Reissue the command specifying apolicy set other than ACTIVE. To copy the ACTIVEpolicy set for a policy domain to another name so thatcommands may be used to change its contents, issue

the COPY POLICYSET command. Then to activate thechanges, issue the ACTIVATE POLICYSET command.

ANR1586E Command: Invalid migration destinationpool name.

Explanation: Server processing for the commandcommand fails because the storage pool name pool namespecified for the migration destination is a copy pool. Acopy pool is not a valid migration destination.



ANR1587E Command: Invalid copy groupdestination - pool name.

Explanation: Server processing for the commandcommand fails because the storage pool name pool namespecified for the copy group destination is a copy pool.A copy pool is not a valid copy group destination.



ANR1590E Command: Policy domain domain name isnot defined.

Explanation: Server processing for the commandcommand fails because the policy domain name domainname specified does not refer to a defined policydomain in the server database.


User Response: Reissue the command specifying apolicy domain name that is defined in the serverdatabase. For a list of the names of defined policydomains in the server database, issue the QUERYDOMAIN command.

ANR1591E Command: Policy domain domain name isalready defined.

Explanation: Server processing for the commandcommand fails because the policy domain name domain



name specified refers to a policy domain that is alreadydefined in the server database.


User Response: Reissue the command specifying apolicy domain name that is not defined in the serverdatabase. For a list of the names of defined policydomains in the server database, issue the QUERYDOMAIN command.

ANR1592E Command: Policy domain domain namestill contains at least one policy set.

Explanation: Server processing for the deletecommand command fails because the policy domainname domain name specified refers to a policy domainthat still contains at least one policy set.


User Response: To delete the policy set from thepolicy domain, issue the DELETE POLICYSETcommand.

ANR1593E Command: Policy domain domain namestill contains at least one node.

Explanation: Server processing for the deletecommand command fails because the policy domainname domain name specified refers to a policy domainthat still contains at least one node. A policy domaincannot be deleted if one or more client nodes are stillassigned to the domain.


User Response: To remove remaining nodes from thepolicy domain, issue the REMOVE NODE command.After all nodes are removed, issue the delete commandagain.

ANR1594E Command: Policy domain domain namehas no active policy set.

Explanation: Server processing for the update orregister node command command fails because thepolicy domain name domain name specified refers to apolicy domain that does not have an active policy setdefined. Nodes cannot be assigned to policy domainsthat do not have an active policy set.

System Action: Database changes for the commandare rolled back and server operation continues. The

command is not successful in changing the serverdatabase.

User Response: To activate a policy set for thespecified policy domain, issue the ACTIVATEPOLICYSET command. After a policy set has beenactivated, client nodes may be assigned to the policydomain.

ANR1595E Command: Policy set set name is notdefined in policy domain domain name.

Explanation: Server processing for the commandcommand fails because the policy set name set namespecified does not refer to a defined set in policydomain domain name in the server database.


User Response: Reissue the command specifying apolicy set name that is defined in the policy domain.For a list of the names of defined policy sets in thepolicy domain, issue the QUERY POLICYSETcommand.

ANR1596E Command: Policy set set name is alreadydefined in policy domain domain name.

Explanation: Server processing for the commandcommand fails because the policy set name set namespecified refers to a policy set that is already defined inpolicy domain domain name.


User Response: Reissue the command specifying apolicy set name that is not defined in the policydomain. For a list of the names of defined policy sets inthe policy domain, issue the QUERY POLICYSETcommand.

ANR1597E policy set command: Policy set set name indomain domain name still contains atleast one management class.

Explanation: The policy set command failed because theset still contains at least one management classdefinition.


User Response: Remove the remaining managementclasses from the policy set and reissue the command.



ANR1598E Command: No default management classhas been assigned for policy set set namein domain domain name.

Explanation: Server processing for the commandcommand fails because the policy set set name in policydomain domain name does not have a defaultmanagement class assigned.


User Response: To assign a default management classin the policy set, issue the ASSIGN DEFMGMTCLASScommand.

ANR1599E Command: Management class class nameis not defined in policy domain domainname, set set name.

Explanation: Server processing for the commandcommand fails because the management class name classname specified does not refer to a defined managementclass in policy set set name belonging to policy domaindomain name.


User Response: Reissue the command specifying apolicy set name that is defined in the policy domain.For a list of the names of defined policy sets in thepolicy domain, issue the QUERY POLICYSETcommand.

ANR1600E Command: Management class class nameis already defined in policy domaindomain name, set set name.

Explanation: Server processing for the commandcommand fails because the specified management classname class name refers to a management class that isalready defined in policy set set name belonging topolicy domain domain name.


User Response: Reissue the command specifying amanagement class name that is not defined in thepolicy set. For a list of the names of definedmanagement classes in the policy domain and policyset, issue the QUERY MGMTCLASS command.

ANR1602E Command: Backup copy group group nameis not defined in policy domain domainname, set set name, management classclass name.

Explanation: Server processing for the commandcommand fails because the backup copy group namedgroup name specified for management class class namedoes not refer to a defined backup copy group inpolicy set set name belonging to policy domain domainname.


User Response: Reissue the command specifying acopy group name that is defined. For a list of thenames of defined copy groups and management classesin the policy domain or policy set, issue the QUERYCOPYGROUP command.

ANR1603E Command: Backup copy group group nameis already defined in policy domaindomain name, set set name, managementclass class name.

Explanation: Server processing for the commandcommand fails because the specified backup copy groupnamed group name refers to a copy group that isalready defined for management class (class name) inpolicy set set name belonging to policy domain domainname.


User Response: Reissue the command specifying acopy group that is not defined in the policy set. For alist of the names of defined copy groups formanagement classes in the policy domain and policyset, issue the QUERY COPYGROUP command.

ANR1604E Command: Archive copy group groupname is not defined in policy domaindomain name, set set name, managementclass class name.

Explanation: Server processing for the commandcommand fails because the archive copy group namedgroup name specified for management class class namedoes not refer to a defined archive copy group in policyset set name belonging to policy domain domain name.


User Response: Reissue the command specifying acopy group name that is defined. For a list of the



names of defined copy groups and management classesin the policy domain or policy set, issue the QUERYCOPYGROUP command.

ANR1605E Command: Archive copy group groupname is already defined in policydomain domain name, set set name,management class class name.

Explanation: Server processing for the commandcommand fails because the specified archive copy groupnamed group name refers to a copy group that isalready defined for management class class name inpolicy set set name belonging to policy domain domainname.


User Response: Reissue the command specifying acopy group that is not defined in the policy set. For alist of the names of defined copy groups formanagement classes in the policy domain and policyset, issue the QUERY COPYGROUP command.

ANR1606E Out of server LOG space in accessingpolicy tables.

Explanation: The server ends a database updatetransaction for policy information because sufficient logspace is not available on the server.

System Action: The policy operation is ended andserver operation continues.

User Response: An authorized administrator can issuethe DEFINE LOGVOLUME command to add volumesfor use by the log and can issue the EXTEND LOGcommand to extend the size of the log so that the newvolumes are used.

ANR1607E Out of server DB space in accessingpolicy tables.

Explanation: The server ends a database updatetransaction for policy information because sufficientdatabase space is not available on the server.


User Response: An authorized administrator can issuethe DEFINE DBVOLUME command to add volumesfor use by the database and can issue the EXTEND DBcommand to extend the size of the database so that thenew volumes are used.

ANR1608E Error fetching entry for domain domainname, set set name.

Explanation: An internal server database error occurswhile retrieving policy information for policy set setname in domain domain name.



ANR1609E Policy error: unable to find managementclass ID for class class name in policy setset name belonging to domain domainname.

Explanation: An internal server database error hasbeen encountered while retrieving policy informationfor management class class name in policy set set namebelonging to policy domain domain name.



ANR1610E Internal Server error: invalid copy typecopy type integer encountered in policyset validation.

Explanation: An internal server database error hasbeen encountered while validating a policy set inresponse to the VALIDATE POLICYSET or ACTIVATEPOLICYSET command.



ANR1611E Command: Invalid management classname - management class name.

Explanation: Server processing for the commandcommand fails because the specified management classname may not be used as a management class name.

System Action: Database changes for the command



are rolled back and server operation continues. Thecommand is not successful in changing the serverdatabase.

User Response: Reissue the command and specifyanother management class name.

ANR1612E Command: Management class managementclass name in policy set set name, domaindomain name specifiesMIGREQUIRESBKUP=YES, butcontains no backup copy group.

Explanation: During policy set validation or activationfor policy set set name in policy domain domain name,the server has found that the management class namedclass name specifies the MIGREQUIRESBKUP=YESparameter but does not contain a backup copy group.Policy set validation or activation fails in this casebecause it would not be possible to ensure thatspace-managed client files are backed up prior to beingmigrated to the server.


User Response: To define a backup copy group withinthe management class, issue the DEFINE COPYGROUPcommand. To change the MIGREQUIRESBKUPparameter, issue the UPDATE MGMTCLASS command.

ANR1635I The server machine GUID, machineGUID, has initialized.

Explanation: The specified globally unique identifier(GUID) has initialized for the server machine.



ANR1636W The server machine GUID changed: oldvalue (old value), new value (new value).

Explanation: The globally unique identifier (GUID)has changed for the server machine. The old and newvalues are displayed.



ANR1637W Error (error) occurred initializing theserver machine GUID.

Explanation: An error occurred while initializing theserver machine globally unique identifier (GUID).


User Response: Handle problems appropriately. Awrite error may occur because the server needs rootauthority to write the GUID. A read error may occur if

the server does not have authority to read the GUID.Other error codes are received from the GUID utility.

ANR1638W Error (error) occurred initializing theserver machine GUID. Old value wasold GUID.

Explanation: An error occurred while initializing theserver machine globally unique identifier (GUID). Theold value is displayed.


User Response: Handle problems appropriately. Awrite error may occur because the server needs rootauthority to write the GUID. A read error may occur ifthe server does not have authority to read the GUID.Other error codes are received from the GUID utility.

ANR1639I Attributes changed for node nodeName:changed attribute list.

Explanation: The TCP/IP name or address, or theglobally unique identifier (GUID) has changed for thespecified node. The old and new values are displayedfor entries that have changed.



ANR1640E There is no data mover defined for nodenode name.

Explanation: To perform the requested operation, thespecified node must have an associated data moverdefined.

System Action: The requested operation fails.

User Response: Define a data mover for the node andretry the operation.

ANR1641E command: The node node name has a typethat is not allowed for this command.

Explanation: The node is not the correct type to beused with this command.


User Response: Re-run the command with a node ofthe correct type.

ANR1642E command: The node node name is locked.

Explanation: The node is locked and cannot be usedin this command.


User Response: Unlock the node and re-run thecommand.



ANR1643I Command: All file spaces for node nodename, will be moved.

Explanation: The server will attempt to move data forall the file spaces for the specified node name based onthe criteria entered in the MOVE NODEDATAcommand.

System Action: Server moves data for the indicatednode.


ANR1644E Command: Move node data operationalready in progress for storage poolstorage pool.

Explanation: A command has been issued to movenode data for the specified storage pool but there isalready a move node data operation in progress for oneor more nodes that have been specifed for that samestorage pool.


User Response: Check the activity log for a previousMOVE NODEDATA command to determine whatprocesses for moving node data are in progress for thestorage pool. Reissue the command for the node(s) andstorage pool you desire that are not already in progress,or, reissue the command after the move node dataprocess ends.

ANR1645I Command: Data for node node name,filespace filespace name, FSID filespace IDwill be moved.

Explanation: The server will move data for thespecified filespace name and node name based on thecriteria entered in the MOVE NODEDATA command.

System Action: The server moves data for thespecified node and filespaces.


ANR1646I Command: Node Node name, no filespacesfound to move for this node.

Explanation: A node and filespace were entered in aMOVE NODEDATA command but no filespaces werefound for the specifed node.

System Action: The server continues to move otherfilespaces for any other nodes specified in the MOVENODEDATA command.


ANR1647E Cannot find file space name for nodenode ID, file space file space ID.

Explanation: The server could not obtain filespaceinformation for that node.

System Action: The server operation continues.


ANR1648W Command:This command will move datafor nodes stored in volumes in storagepool source storage pool to other volumeswithin the same storage pool; the datawill be inaccessible to users until theoperation completes.

Explanation: A MOVE NODEDATA command hasbeen entered that will move data to other volumes inthe same storage pool. While the data is being moved,it will not be available to users.

System Action: The administrator is asked whether tocontinue.

User Response: Enter 'Y' to continue or 'N' to end theprocess.

ANR1649W Command:This command will move datafor nodes stored in storage pool sourcestorage pool to storage pool destinationstorage pool; the data will be inaccessibleto users until the operation completes.

Explanation: A MOVE NODEDATA command hasbeen entered that will move data from the sourcestorage pool to the destination storage pool shown.While the data is being moved it, will not be availableto users.


User Response: Enter 'Y' to continue or 'N' to end theprocess.

ANR1650E Server server name is not defined.

Explanation: The server name was not created usingthe DEFINE SERVER command. This entry was createdusing the REGISTER NODE NODETYPE=SERVERcommand and is not a valid reference.

System Action: The current action for the device classreferring to this server fails.

User Response: The device class referring to this nodeas the SERVERNAME should be updated to refer to avalid server entry. Specifically, it should refer to an



entry created using the DEFINE SERVER command.

ANR1651E Server information for server name is notavailable.

Explanation: The information for server name was notavailable.

System Action: The current server action fails.

User Response: Please review any other messagesprior to this message to determine the cause of thefailure.

ANR1652E Server information for server name couldnot be read from a device configurationfile.

Explanation: An attempt to a server definition forserver name from any device configuration files failed.


User Response: Please verify the existence of a deviceconfiguration file and the DEFINE SERVER stanzawithin that file.

ANR1653E Resource lock acquisition for serverserver name failed.

Explanation: The acquisition of the resource lock forserver server name failed.


User Response: Retry the action referring to thedevice class that refers to this server name. If the lockfailure persists, please contact your servicerepresentative.

ANR1654E Server server name will not be written toa device configuration file.

Explanation: An error occurred accessing theinformation for server name while trying to write thisinformation to a device configuration file.

System Action: This DEFINE SERVER entry is notprocessing.

User Response: Verify that the necessary DEFINESERVER entries were written to a device configurationfile. If this error persists, please contact your servicerepresentative.

ANR1655E Failure processing password for Serverserver name when writing a deviceconfiguration file.

Explanation: An error occurred processing thepassword for server name while trying to write thisinformation to a device configuration file.

System Action: This DEFINE SERVER entry is writtento the device configuration file without the password.

User Response: The password needs to be specifiedafter PASSWORD= for this DEFINE SERVER entry inthe device configuration file.

ANR1656E Failure writing server definitions to adevice configuration file.

Explanation: An error occurred writing the serverinformation to a device configuration file.

System Action: The BACKUP DEVCONFIG actionfails.

User Response: Check that the device configurationfile exists and that the file system the file resides on isnot out of space.

ANR1657E Command: Invalid server or group nameserver or group name.

Explanation: The command shown specifies an invalidserver or server group name.


User Response: Reissue the command with a validname.

ANR1658E Command: Failure determiningNODENAME for server server name.

Explanation: The command shown was unable todetermine a node name either from the NODENAME=parameter on this command or from the server namepreviously set using the SET SERVERNAME command.


User Response: Reissue the command with a validnode name parameter or else update the server nameusing the SET SERVERNAME command so that a validname is available.

ANR1659E Command: Server or server group serveror group name is already defined.

Explanation: A DEFINE SERVER or DEFINESERVERGROUP command has been entered thatspecifies a server or server group name that alreadyexists. The name specified must be a unique name. Itmust not duplicate a node name used by a registerednode, a server name used by a defined server, or aserver group name used by a defined server group.


User Response: To define the server or server group,reissue the command and specify a different name.



ANR1660I Server server name defined successfully.

Explanation: The requested server has been defined tothe system in response to a DEFINE SERVERcommand.



ANR1661I Server server name deleted.

Explanation: In response to a DELETE SERVERcommand, the requested server has been removed fromthe system.



ANR1662I Server server name updated.

Explanation: One or more attributes of a server havebeen updated by an UPDATE SERVER command.



ANR1663E command: Server server name not defined

Explanation: The server server name is not defined tothe system.



ANR1664W Command: Server server name is currentlyin use.

Explanation: The command shown specifies a serverthat is currently in use. The server is referenced by oneor more of the following: a device class ofDEVTYPE=SERVER that specifies this server for the’SERVERNAME=’ parameter, it is defined as the eventserver, or a connection with this server is currentlyopen and in use.


User Response: Reissue the command at a later time.In order to delete the server specified, it must not becurrently connected to the server, it may not bereferenced in a device class, and it can not be definedto be the event server.

ANR1665E command: Failure updating password forserver server name.

Explanation: An error occurred updating thepassword for server name.


User Response: Re-try the command specifying adifferent password.

ANR1666E command: FILEAGGR not allowed withNODETYPE=SERVER.

Explanation: The FILEAGGR= parameter may not bespecified with the NODETYPE=SERVER parameter alsobeing specified.


User Response: Reissue the command commandwithout the FILEAGGR= parameter if this is aNODETYPE=SERVER.

ANR1667E command: Action not permitted againstnode node name.

Explanation: The command is not permitted againstthe entry for node node name. This node entry has aNODETYPE of SERVER.



ANR1668E command: Not allowed for server servername.

Explanation: The DELETE SERVER command is notpermitted for server server name. The specified server iseither the event server or else it is a node entry ratherthan a server definition.


User Response: If the specified server is the eventserver, and you want to delete it, issue the DELETEEVENTSERVER command and then reissue theDELETE SERVER command. To remove a node entry,issue the REMOVE NODE command for the specifiedname.

ANR1669I Server event server name is defined as theevent server.

Explanation: The specified server is defined.



ANR1670E Server event server name is alreadydefined as the event server. You mustissue the DELETE EVENTSERVERcommand before defining a new eventserver.

Explanation: An event server is already defined.


User Response: Delete the existing Event Server andtry the command again.



ANR1671I The event server definition has beendeleted.

Explanation: The event server definition has beendeleted.


User Response: If an event server definition isdesired, use the DEFINE EVENTSERVER command.

ANR1672I No event server is currently defined.

Explanation: A query was issued to get the name ofthe event server; however, no event server is currentlydefined.


User Response: If an event server definition isdesired, use the DEFINE EVENTSERVER command.

ANR1673I Server group group name definedsuccessfully.

Explanation: The requested server group is defined tothe system in response to a DEFINE SERVERGROUPcommand.



ANR1674I Member member name definedsuccessfully in server group group name.

Explanation: The requested member is defined in theserver group in response to a DEFINE GRPMEMBERcommand.



ANR1675I Server group server group name deleted.

Explanation: The requested server is removed fromthe system in response to a DELETE SERVERGROUPcommand.



ANR1676I Member member name deleted fromserver group server group name.

Explanation: The requested member is removed fromthe server group in response to a DELETEGRPMEMBER command,



ANR1677I Server group server group name updated.

Explanation: One or more attributes of a server groupis updated by an UPDATE SERVERGROUP command.



ANR1678I Server group original server group namerenamed new server group name.

Explanation: A server group is renamed by aRENAME SERVERGROUP command. The originalname is not valid.



ANR1679E Command: Server group server group namenot defined.

Explanation: The server server group name is notdefined to the system.


User Response: Retry the command specifying anexisting group.

ANR1680E Command: Member member name notdefined in server group server groupname.

Explanation: The member member name is not definedin server group server group name.


User Response: Retry the command specifying anexisting member of the group.

ANR1681E Command: Member member name isalready in server group server groupname.

Explanation: The member member name is defined inserver group server group name.


User Response: Retry the command and specify anew member name.

ANR1682E A group cannot be a member of itself.

Explanation: The member and group name are thesame. A group may not be a member of itself.


User Response: Retry the command and specifyanother member name.



ANR1683E Command: Member member name notdefined.

Explanation: The member member name is not definedto the system. Server group members must be adefined server or server group.


User Response: Retry the command specifyingexisting server or group.

ANR1684E Route:command: Routed commandscannot be routed.

Explanation: The command part of a routed commandmay not contain route information itself. The allowablesyntax for routed commands is “:”. The command maynot contain route information. Only one level of routingis allowed.

System Action: Routed commands where thecommand portion contains additional routinginformation are not processed.

User Response: Reissue the command withoutspecifying route information in the command portionof this routed command.

ANR1685I Server group server group copied toserver group new server group.

Explanation: This message is displayed in response tothe COPY SERVERGROUP command. The server groupnamed server group is copied to the server group namednew server group.



ANR1686I Member member name moved fromserver group group name to server groupnew group name.

Explanation: The requested member member name ismoved from server group group name to the servergroup new server group in response to a MOVEGRPMEMBER command.



ANR1687I Output for command ’command’ issuedagainst server server name follows:

Explanation: The output for the command issuedagainst the indicated server follows this message.



ANR1688I Output for command ’command’ issuedagainst server server name completed.

Explanation: This message marks the end of theoutput for the command specified that was issuedagainst the indicated server.



ANR1689E Output for command ’command’ issuedagainst server server name terminated.

Explanation: An error condition occurred causing theoutput for the command issued against the specifiedserver to be terminated.


User Response: Retry the command against therequested server once the error condition has beenresolved. If the cause of the error can not bedetermined, please contact your local servicerepresentative.

ANR1690E Error sending command ’command’ toserver server name.

Explanation: An error was encountered sending thespecified command to the server indicated.



ANR1691E Error receiving response from serverserver name for command ’command’.

Explanation: An error was encountered receiving theresponse from the server indicated for the commandthat was issued against it.



ANR1692E Response for command ’command’ fromserver server name contains invalid data.

Explanation: The output returned from the specifiedserver for the command that was issued, containsinvalid output. The command response can not beprocessed.

System Action: Output processing for this commandresponse terminates.



User Response: Please contact your local servicerepresentative.

ANR1693E Unable to issue command ’command’against server server name - failurestarting thread.

Explanation: A thread could not be started to issuethe specified command against the server indicated.

System Action: This command is not issued againstthe server specified. The process will attempt to issuethe command against any other servers that werespecified for the command routing information.

User Response: Examine the server messages issuedprior to this message to determine the source of theerror. Retry routing this command to the indicatedserver after the cause of the error has been determinedand resolved. If the error cannot be isolated andresolved, contact your service representative.

ANR1694I Server server name processed command’command’ and completed successfully.

Explanation: The server indicated processed thecommand successfully.



ANR1695W Server server name processed command’command’ but completed with warnings.

Explanation: The server indicated processed thecommand but encountered warnings. However, thewarnings did not prevent the execution of thecommand.



ANR1696E Server server name attempted to processcommand ’command’ but encounterederrors.

Explanation: The server indicated processed thecommand but encountered errors. These errorsprevented the successful completion of the command.


User Response: Examine any error messages issuedon either the server sending the command or else theserver executing the command to determine the causeof the failure. Reissue the command once these errorsare corrected.

ANR1697I Command ’command’ processed by totalnumber for servers server(s): number ofsuccessful servers successful, number ofservers with warnings with warnings, andnumber of servers with errors with errors.

Explanation: The indicated command was processedby the number of servers specified. For the totalnumber of servers, the number indicated weresuccessful, the number indicated encountered awarning condition but processed anyway, and finally,the number indicated encountered errors and could notprocess.



ANR1698I Command ’command’ was not issuedagainst any other servers.

Explanation: The indicated command was not issuedagainst any other server. Either the routing informationdid not resolve to any valid servers or else failuresoccurred issuing the command against the requiredservers.


User Response: Check to see that valid routeinformation was provided for the command or elsecheck the activity log for error messages that indicatewhy the command was not issued to the other servers.

ANR1699I Resolved route information to number ofservers server(s) - issuing commandcommand against server(s).

Explanation: The route information was resolved tothe number of servers indicated. The specifiedcommand will be issued against those servers.



ANR1700E Unable to resolve ’route information’ toany server(s).

Explanation: The route information provided for thiscommand did not resolve to any server names or groupnames. Because of this, the command will not beissued.


User Response: Examine the route informationprovided. Reissue the command providing correct routeinformation.



ANR1701E Command: No matching servers defined.

Explanation: No matching servers are found for thespecified command.


User Response: Issue the command and specifydifferent servers.

ANR1702W Skipping ’server name’ - unable toresolve to a valid server name.

Explanation: The server name specified is beingskipped because it could not be resolved to a validserver name.


User Response: Reissue the command providing thecorrect server name.

ANR1703E Failure resolving server names.

Explanation: An error occurred while resolving theserver names. Specifically, the resolution of the servernames has terminated because of a significant failure.


User Response: Check the activity log and serverconsole for other messages about the cause of thefailure. Once the cause has been resolved, reissue thecommand.

ANR1704E Failure obtaining credentials foradministrator admin name.

Explanation: An error occurred obtaining thecredentials for the administrator referenced.


User Response: Check the activity log and serverconsole for other messages about the cause of thefailure. Once the cause has been resolved, reissue thecommand.

ANR1705W Ping for server ’server name’ was not ableto establish a connection.

Explanation: The ping command was unable toestablish a connection to the server specified. Thiscould indicate a problem on the server issuing the ping,a problem with the communication connection betweenthe two servers, or else it is a problem with the otherserver.


User Response: Check the activity log and serverconsole for messages that indicate a failure or problemon the server issuing this command. Next, check thecommunication connection between the two servers.

Also, check the server definition and password on boththe server issuing the command and the serverspecified. And finally, verify that the server specified isrunning.

ANR1706I Ping for server ’server name’ was able toestablish a connection.

Explanation: The ping command was able to establisha connection to the server specified.


User Response: Check the activity log and serverconsole for messages that indicate a failure or problemon the server issuing this command. Next, check thecommunication connection between the two srevers.And finally, verify the operation of the server specified.

ANR1707I Server information not complete,crossdefine not allowed.

Explanation: The SERVERHLADDRESS,SERVERLLADDRESS or SERVERPASSWORD has notbeen set for this server. These are required for theCROSSDEFINE option on the define server command.


User Response: Use the QUERY STATUS command tofind what values need to be set. An authorizedadministratormust issue the SET SERVERHLADDRESS,SET and SERVERLLADDRESS or SETSERVERPASSWORD command to set the missingvalues.

ANR1708I Define server for Server name failedbecause the crossdefine failed.

Explanation: The define server command failedbecause the crossdefine parameter was included, andthe crossdefine was not successful.


User Response: Check this server, and the serverbeing defined for other messages indicating the reasonfor the failure.

ANR1709E Command.: Failure determining currentusage for server or group name Servername.

Explanation: The specified command failed todetermine the current use of the server name or servergroup specified.


User Response: Retry the command. If it continues tofail and the cause of the failure can not be determined,please contact your local service representative.



ANR1710E Command.: Name Name not valid for thiscommand.

Explanation: The name specified for this command isnot valid for this operation. The first case is that aserver name was specified for a command requiring aserver group name. The other case is where a servergroup name was specified for a command requiring aserver name.


User Response: Retry the command specifying theproper name.

ANR1711E Error accessing the server or servergroup name Name.

Explanation: A server operation attempted to accessthe server name or server group name specified. Anerror occurred while trying to access the informationfor this server name or server group name.

System Action: The server opteration fails.

User Response: Review the activity log to try todetermine the cause of the failure. If a cause can not bedetermines, please contact your local servicerepresentative.

ANR1712W Command routing not allowed fromserver console.

Explanation: Command routing is not allowed fromthe server console.

System Action: The command is not executed.

User Response: Reissue the command from anAdministrative client.

ANR1713I Command ’command’ issued againstserver server name.

Explanation: The specified command has been sent tothe indicated server. The command is to terminate thespecified server, no confirmation will be recieved.



ANR1714W The password for administratoradministartor name has expired. Thepassword for this administrator must beupdated on the configuration managerserver server name.

Explanation: The password for the namedadministrator has expired, but the administrator is amanaged object on this server. The password must beupdated on the named configuration manager server.

System Action: The administrator is allow access tothe server.

User Response: Change the administrator’s passwordon the named configuration manager server.

ANR1715E Event server cannot be deleted - it iscurrently active.

Explanation: The event server cannot be deleted sinceit is currently active for event logging.

System Action: The server does not delete the eventserver entry.

User Response: In order to delete the event server, itmust not be currently active for event logging. To stopevent logging to the event server issue ENDEVENTLOGGING EVENTSERVER. Then reissue theDELETE EVENTSERVER command.

ANR1716I Server cannot be crossdefined to itself,crossdefine not allowed.

Explanation: An attempt was made to crossdefine theserver to itself.



ANR1717E Command: Command failed -Non-Compatible Filespace name typeshave been specified.

Explanation: A server command has been entered butcannot be processed because Non-Compatible Filespacename types have been specified.


User Response: Specify compatible filespace names.Unicode to Unicode or Non-Unicode to Non-Unicode.

ANR1718E Command: Reconstruction of fileaggregates is supported only formovement in which the source andtarget storage pools aresequential-access.

Explanation: The indicated command specifies thatfile aggregates be reconstructed during a moveoperation for which reconstruction is not supported.Aggregates are reconstructed only when both thesource storage pool and the target storage pool aresequential-access.


User Response: Reissue the command withoutspecifying that aggregates should be reconstructed.Alternatively, specify a move operation involvingtransfer of data within a sequential-access storage poolor between two sequential-access storage pools.



ANR1719E Storage pool storage pool name specifiedon the MOVE NODEDATA command isnot a valid pool name or pool type.

Explanation: If the source storage pool specified in thecommand is a primary storage pool, then thedestination storage pool specified must also be aprimary storage pool. If the source storage pool is acopy storage pool, then the specified destinationstorage pool must be the same storage pool as thesource storage pool.

System Action: The MOVE NODEDATA process fails.

User Response: Provide a valid primary storage poolname as the destination storage pool if the source poolis a primary storage pool. If the source pool is a copystorage pool do not specify a destination pool, or,specify the same copy storage pool as the destinationpool.

ANR1720I A path from source name to destinationname has been defined.

Explanation: In response to the DEFINE PATHcommand, the path from the source name to thedestination name has been defined in the serverdatabase.



ANR1721I A path from source name to destinationname has been deleted.

Explanation: In response to the DELETE PATHcommand or to an UPDATE DEVCLASS commandwith the MOUNTLIMIT parameter, the path from thesource name to the destination name has been deletedin the server database.



ANR1722I A path from source name to destinationname has been updated.

Explanation: In response to the UPDATE PATHcommand, the path from the source name to thedestination name has been updated in the serverdatabase.



ANR1723E A path is already defined using sourcename and destination name.

Explanation: In response to the DEFINE PATHcommand, the server determines that a path with thesame source name and the same destination name

already exists in the server database.


User Response: Correct the source name ordestination name and re-enter this command.

ANR1725E resource name is not defined.

Explanation: In response to the DEFINE PATHcommand, a resource name was provided that has notbeen defined.


User Response: Define the source name or thedestination name and re-enter this command.

ANR1726E A operation using the path fromsourcename to destname is currently beingused.

Explanation: This path was in use when the commandwas entered. The attributes of a path may not bechanged while it is being used.


User Response: Wait until the operation using thispath is complete, or cancel the operation using thispath, and then reissue the command.

ANR1727E A path from sourcename to destname doesnot exist.

Explanation: The path being updated or deleted doesnot exist.


User Response: Reissue the command with a differentsource or destination name or define a new path.

ANR1728E The library libname is not a SCSI library.

Explanation: A drive that is to be used by a NAS datamover must be attached to a SCSI library.


User Response: Reissue the command with a differentdrive name.

ANR1729E A path using the data mover source namestill exists.

Explanation: In the DELETE DATAMOVER command,the data mover name supplied is either the source orthe destination in a path that still exists in the serverdatabase.


User Response: Delete the existing path and reissuethis command.



ANR1730I Data mover mover name has beendefined.

Explanation: The data mover has been defined in theserver database.



ANR1731I Data mover mover name has beendeleted.

Explanation: The data mover has been deleted in theserver database.



ANR1732I Data mover mover name has beenupdated.

Explanation: The data mover has been updated in theserver database.



ANR1733E Data mover mover name is alreadydefined.

Explanation: A DEFINE DATAMOVER command wasentered for a data mover that already exists in theserver database.


User Response: Use the UPDATE DATAMOVER tochange the attributes in this data mover. Otherwise usea different data mover name.

ANR1734E Data mover mover name is not defined.

Explanation: An UPDATE DATAMOVER commandwas entered for a data mover that does not exist in theserver database.


User Response: Correct the data mover name or usethe DEFINE DATAMOVER command to define a newdata mover.

ANR1735E Data mover data mover is currently beingused.

Explanation: A data mover was in use when thecommand was entered. The attributes of a data movermay not be changed while it is being used.


User Response: Wait until the operation using thisdata mover is complete, or cancel the operation using

this data mover, and then reissue the command.

ANR1736E Command: Parameter parameter length isinvalid.

Explanation: The specified server command has beenentered with a parameter that is longer or smaller inlength than the allowed length.


User Response: Reissue the command and enter theproper syntax.

ANR1737E Command: Device name device specifiedis invalid.

Explanation: The specified command has been enteredwith an invalid device name.

System Action: The command failed.

User Response: Reissue the command with a validdevice name.

ANR1738I Unable to begin a server-free operationwith data mover data mover name;received error error.

Explanation: The server attempted to begin aserver-free operation with the specified data mover butwas unable to do so.


User Response: The server-free data movement willfail and the client may retry the request using LAN orLAN-free data transfer.

ANR1739I Unable to update configuration of datamover data mover name; received errorerror.

Explanation: The server attempted to notify thespecified data mover that a change in the SAN requiresthat the configuration be updated. The update failedbecause the data mover was busy.


User Response: The data mover must finish itscurrent operation before the configuration can beupdated. The server-free data movement will fail andthe client will retry the request using LAN or LAN-freedata transfer.

ANR1740E For the path defined from disk nodename disk name received lun actual lunfrom client, expected expected lun.

Explanation: A client attempted to backup the disk,but the server path definition was different than thatwhich was detected by the client.




User Response: Correct the path definition from thedisk to a datamover.

ANR1741E For the path defined from disk nodename disk name received serial numberactual serial from client, expected expectedserial.

Explanation: A client attempted to backup the disk,but the server path definition was different than thatwhich was detected by the client.


User Response: Correct the path definition from thedisk to a datamover.

ANR1742E The disk node name disk name is notonline.

Explanation: An operation requested the specifieddisk. The disk cannot be used because it is not online.


User Response: Determine the reason for the diskbeing offline; if possible, update the disk status toonline.

ANR1743E The path from data mover datamovername to disk node name disk name is notonline.

Explanation: An operation requested the specifieddisk. The disk cannot be used because the path fromthe datamover to the disk is not online.


User Response: Determine the reason for the pathbeing offline; if possible, update the path status toonline.

ANR1744E The world wide name is invalid for thedestination of the path being defined.

Explanation: A path was being defined from adatamover to a destination and that destination has anincorrect world wide name specified.


User Response: Update the destination’s definitionwith the correct world wide name.

ANR1745I Unable to discover SAN devices.Function is busy.

Explanation: The SAN device discovery function isbusy. The requested query cannot be completed at thistime.


User Response: Reissue the request when currentqueries have completed.

ANR1746E The path from data mover datamovername to drive library name drive name isnot online.

Explanation: A server-free operation requested thespecified device. The device cannot be used because thepath from the datamover to the device is not online.


User Response: Determine the reason for the pathbeing offline; if possible, update the path status toonline.

ANR1747W The data mover datamover name was notfound on the SAN. The data moverdefinition has been marked offline.

Explanation: During device discovery on a storagearea network a device was not found that has the sameserial number as the data mover defined to TSM.


User Response: Verify that the serial number of thedata mover definition is correct and that the datamover is operational.

ANR1748W The disk node name disk name was notfound on the SAN. The path definitionfor this disk has been marked offline.

Explanation: During device discovery on a storagearea network a device was not found that has the sameserial number as the disk defined to TSM.


User Response: Verify that the serial number of thedisk definition is correct and that the disk isoperational.

ANR1749W The drive library name drive name was notfound on the SAN. The path definitionfor this drive has been marked offline.

Explanation: During device discovery on a storagearea network a device was not found that has the sameserial number as the drive defined to TSM.


User Response: Verify that the serial number of thedrive definition is correct and that the drive isoperational.



ANR1750E The server detected an internal error,return code = return code.

Explanation: An unexpected error occured duringserver operation.


User Response: Use the QUERY ACTLOG commandto examine messages prior to this error to determinethe cause of the data storage failure. If the failure canbe found and resolved, retry the operation. If thefailure cannot be found, contact your servicerepresentative for assistance in resolving the problem.

ANR1751I Disk disk name has been defined.

Explanation: In response to the DEFINE DISKcommand, the disk has been defined in the serverdatabase.



ANR1752E Disk disk name is already defined.

Explanation: A DEFINE DISK command was enteredfor a disk that already exists in the server database.


User Response: Use the UPDATE DISK command tochange the attributes of this disk. Otherwise, use adifferent disk name.

ANR1753E Disk disk name is currently being used.

Explanation: A disk was in use when the commandwas entered. The attributes of a disk may not bechanged while it is being used.


User Response: Wait until the operation using thisdisk is complete, or cancel the operation using thisdisk, and then reissue the command.

ANR1754E Disk disk name is not defined.

Explanation: An UPDATE, DELETE or client functionrequested the specified disk, but the disk has not beendefined to the server.


User Response: Correct the disk name or use theDEFINE DISK command to define a new disk.

ANR1755I Disk disk name has been updated.

Explanation: In response to the UPDATE DISKcommand, the disk attributes have been updated in theserver database.



ANR1756I Disk disk name has been deleted.

Explanation: In response to the DELETE DISKcommand, the disk has been deleted in the serverdatabase.



ANR1757E A path using the disk disk name stillexists.

Explanation: The name supplied in a DELETE DISKcommand is the destination in a path that still exists inthe server database.


User Response: Delete the existing path using theDELETE PATH command and re-enter the DELETEDISK command.

ANR1758E A path from disk node name disk name toa datamover cannot be determined.

Explanation: During a backup operation a path fromthe disk cannot be found.


User Response: Define a path from the disk to adatamover.

ANR1759E Command: A device with SCSIdatamover capabilities was not found inthe system configuration for datamoverdatamover name.

Explanation: The scsi address could not bedetermined for a device that is capable of performingdatamover operations.

System Action: The requested operation fails.

User Response: Verify that the hardware that canperform SCSI datamover operations is installed andpowered on.

ANR1760E Command: Command failed for nodenode name, filespace filespace name -destination storage pool storage pool wasskipped.

Explanation: The indicated command failed becausethe destination storage pool was skipped. A storagepool may be skipped because it does not have enoughavailable space, or because it has a MAXSIZE valuethat is less than the size of the object to be inserted.


User Response: Ensure that the destination storage



pool is available, has an adequate MAXSIZE setting,and has adequate space. The MAXSIZE setting may bechanged using the UPDATE STGPOOL command.Space may be added to the storage pool by checking inscratch volumes or defining new volumes in thestorage pool. If volumes in the destination storage poolare offline, use the VARY ONLINE command to varythem online and make them available for use. Correctthe problem and reissue the command.

ANR1761E Command: Command failed for nodenode name, filespace filespace name -storage media is inaccessible.

Explanation: The indicated command failed becauserequired storage media is unavailable.


User Response: Ensure that there are sufficientvolumes available for storing backups and that anyvolumes required for restore are checked in andavailable. Correct the problem and try the commandagain.

ANR1762E Command: Command failed for nodenode name, filespace filespace name -mount point unavailable.

Explanation: The indicated command failed becausesufficient mount points are not available.


User Response: Ensure that sufficient mount pointsare available and working correctly. Correct theproblem and try the command again.

ANR1763E Command: Command failed - seeprevious error messages.

Explanation: The indicated server command hasfailed. This message is always preceded by one or moreother error messages which provide more detail aboutwhy the command failed.


User Response: Examine the previous error messagesto determine the source of the error. Use the QUERYACTLOG command to view the activity log and searchfor messages if needed. Correct the problem and try thecommand again.

ANR1764E Command: Command failed - loadablemodule module name is not available.

Explanation: The indicated server command has failedbecause it requires the availability of the specifiedloadable module, but the module is not loaded.


User Response: Make sure the necessary loadable

module is available for your platform. Not all modulesare available on all platforms. If the module is availablefor your platform and is installed, contact your servicerepresentative for assistance.

ANR1765E Command:The number of copy threadsentered, copythreads, exceed thecapabilities of the datamover.

Explanation: A datamover has an upper limit of thenumber of copy threads that it is capable of executing.The copythreads parameter provided is greater thanthis limit.


User Response: Make sure the value entered for thecopythreads parameter is less than the maximum forthis datamover. Using the default for the number ofcopythreads sets the number of copythreads to thedatamover’s maximum value.

ANR1766I The number of sessions currently activefor datamover datamover, exceed thenumber of copy threads defined for thisdatamover.

Explanation: The datamover definition has a paramterthat is used to limit the number of operations involvingthat datamover. This limit was reached.

System Action: The operation continues using anothermethod.

User Response: Verify that the number of copythreads in the datamover definition is sufficient enoughto allow mutliple server-free operations, or defineanother datamover to handle additional server-freeoperations.

ANR1767W A datamover with a online path to boththe disk, nodename diskname, and thedrive, libraryname drivename cannot befound.

Explanation: To perform server-free data movement, apath must exist from the datamover to both the diskand the drive. If either path is not defined or is offlineto all datamovers defined then the data movementcannot occur via server-free.

System Action: The operation continues using anothermethod.

User Response: Define the appropriate paths from adatamover to the disks and drives. If a path is definedfrom a datamover to a drive in a library then all drivesin that library should have paths defined from thatsame datamover. A path may have to be updated tospecify online=yes.



ANR1768E Command: The device name providedconflicts with a device name that isalready in use.

Explanation: The device name provided in thecommand is already used by an existing path.

System Action: The command is not processed.

User Response: Specify a valid DEVICE parameterthat is not used by any other drive or library.

ANR1769E Command: Command failed - multipleactions between commit actions notallowed.

Explanation: A server script that performs multipleactions between commit actions is not allowed. Forexample, deletion of multiple paths before each of thedeletions is committed is not allowed.


User Response: Rewrite the script or macro so that nonew command is issued until the previous command iscommitted.

ANR1770E Processing for session session id founddestination new destination. Expectedcurrent destination.

Explanation: While processing a remote imageoperation, the specified session was working with thecurrent destination. But the server received a clientrequest with a new destination name.


User Response: From the client, quit the currentremote image request. Reissue the request, if desired.

ANR1771E The path from remote server remoteserver name to destination destination namewith the destination device type is notvalid.

Explanation: The library manager receives a commandto update the path for the remote server. The devicetype field of the destination device is not valid. Thedestination for update path from remote server must beeither drive or library.


User Response: Determine why the device type fieldof the destination device is not valid.

ANR1772E The path from source source name todestination drive name is taken offline.

Explanation: The path is now marked offline.

System Action: The path is inaccessible.

User Response: Determine the reason the path isinaccessible, such as a hardware problem. Make anyneeded corrections. Then, issue the the UPDATE PATHcommand with the ONLINE=YES option to make thepath online.

ANR1773W Unable to update the path in thedatabase path source name and drive drivename .

Explanation: The system is unable to update the pathinformation in the database table.

System Action: .


ANR1800E Missing or invalid EVENTLOGcommand parameter.

Explanation: The event logging command issuedcontains an invalid parameter, or is missing a requiredparameter.


User Response: Reissue the command with the properparameters.

ANR1801E Eventlog command: Invalid event or eventclass - Event or event class name.

Explanation: An event logging command has beenentered which specifies an unknown event or eventclass.

System Action: The command is ignored for theinvalid event or event class. Any valid events or classesspecified are processed.

User Response: Reissue the command with the correctevent or event class.

ANR1808E Unable to open event log file file spec forappending.

Explanation: The server cannot write to a file whichhas been specified for event logging.

System Action: No logging will be done to the filereceiver.

User Response: Check the file for proper accesspermissions, or specify a different file for logging.

ANR1809E Insufficient memory to activate eventlogging.

Explanation: A BEGIN EVENTLOGGING commandhas been entered, but the server has insufficientmemory available to activate logging.


User Response: If logging is required, make more



memory available to the server then restart the server.

ANR1810E Eventlog command: Invalid receiver -receiverName.

Explanation: An event logging command has beenentered which specifies an unknown event log receiver(maybe unknown just to this platform).

System Action: The command is ignored for theinvalid receiver. Any valid receivers specified areprocessed.

User Response: Reissue the command with the correctreceiver.

ANR1822I Event logging ended for the receiverNamereceiver.

Explanation: In response to an ENDEVENTLOGGING command or because an erroroccurred, event log records are no longer being outputto the specified receiver.



ANR1823I Event logging ended for all receivers.

Explanation: In response to an ENDEVENTLOGGING command, event log records are nolonger being output to any receiver.



ANR1824E Event logging is inactive for thespecified receiver.

Explanation: An END EVENTLOGGING commandhas been entered, but logging is not active for thespecified receiver.


User Response: If logging is desired, use the ENABLEEVENT and BEGIN EVENTLOGGING commands toactivate event logging.

ANR1825I Event logging active for the receiverNamereceiver.

Explanation: In response to a BEGINEVENTLOGGING command, event log records are nowbeing output to the specified receiver.



ANR1826I Event logging active for all receivers.

Explanation: In response to a BEGINEVENTLOGGING command, event log records are nowbeing output to all receivers.



ANR1827E Eventlog command: No valid receiverspecified.

Explanation: An event logging command has beenentered, and no valid receivers were specified.



ANR1828E Eventlog command: No valid eventspecified.

Explanation: An event logging command has beenentered and no valid events or event classes werespecified.


User Response: Reissue the command with the correctevents or event classes.

ANR1829E Eventlog command: Server events may notbe disabled for the activity log receiver.

Explanation: A DISABLE EVENT command has beenentered for the activity log receiver.

System Action: The command is ignored for theactivity log receiver. Any valid receivers specified areprocessed.


ANR1830E receiverName receiver options not definedin the server options file.

Explanation: A BEGIN EVENTLOGGING commandhas been entered for a receiver, but the requiredreceiver options were not specified in the serveroptions file.

System Action: Logging is not started for the specifiedreceiver.

User Response: Enter the receiver options in theserver options file and restart the server.



ANR1831I Event logging of client events ended forACTLOG receiver.

Explanation: An END EVENTLOGGING commandhas been entered for the activity log receiver.

System Action: The server no longer records clientevents in the activity log. Server events continue to berecorded in the activity log.


ANR1842E An error occurred on the receiverNamereceiver.

Explanation: An error occurred on the specifiedreceiver.

System Action: The server no longer sends events tothe receiver.

User Response: Issue a BEGIN EVENTLOGGINGcommand for the receiver to attempt to start loggingevents to the receiver again.

ANR1843I Event log receiver initialization inprogress.

Explanation: Initialization is starting for the eventlogreceivers.



ANR1844I Eventlog command command processed.

Explanation: The specified command was processed.


User Response: If any previous messages indicate thatparts of the command failed, reissue the command forthose parts only.

ANR1850E Circular event logging detected. Theevent server has previously handledevent Event number from Source trail. Toprevent looping, events which havealready been logged by the event serverare not sent again. Please correct thesituation causing circular logging toavoid wasting system resources.

Explanation: The server is attempting to log an eventwhich has previously been handled by the event serverthat is currently defined.

System Action: The event is not sent to the eventserver. Other events will still be sent, and this messagewill be issued periodically if this situation is detectedagain.

User Response: Determine what is wrong with the

server to server event logging setup, and fix theproblem.

ANR1851E The source trail for server to serverevent logging has exceeded themaximum length of Maximum sourcetraillength bytes.

Explanation: While attempting to log an event to theevent server, the server has found that the source traillength is too long.

System Action: The server continues to try to send theevent to the event server, but the source trail may betruncated and appear something like:

name1>...>namex>nameywhere,

name1 is the originator of the event.... is where intervening server name(s)

have been left off the source trail.

User Response: Most likely you are using very longserver names and/or have excessive hops from serverto server. Either use shorter server names or changeyour configuration to reduce the number of hops.

ANR1852E Unable to send header to TEC at TECserver rc return code

Explanation: A network error has occurred inattempting to send the event header to the TivoliEnterprise Console.


User Response: Verify network connections andcontact your service representative if this error persists.

ANR1853E Unable to send data to TEC at TECserver rc return code

Explanation: A network error has occurred inattempting to send the event data to the TivoliEnterprise Console.



ANR1854E Unable to flush data to TEC at TECserver rc return code

Explanation: A network error has occurred inattempting to flush data to the Tivoli EnterpriseConsole .





ANR1855E Failure validating protocol betweenclient and server for node node onsession session number

Explanation: For a node having the ″VALIDATEPROOTOCOL″ option set to either ″DATAONLY″ or″ALL″, a validation error occurred. The transaction isaborted and an indication is sent to the client indicatingthe failure.



ANR1856W Command: No volumes selected toprocess.

Explanation: No volumes were eligible for processingby the AUDIT VOLUME command based upon theparameters specified.

System Action: The AUDIT VOLUME process endswithout processing any volumes.

User Response: Review the parameters specified forthe command. If there was an error specifying aparameter, re-issue the command with the parametercorrected.

ANR1857I AUDIT VOLUME will start count repairprocesses.

Explanation: The AUDIT VOLUME command willprocess a range of volumes due to one or more of thefollowing parameters having been specified:FROMDATE, TODATE, or STGPOOL. The AUDITVOLUME processing will start a process for eachvolume that qualifies and process an AUDIT VOLUMEfor each volume with FIX=YES specified.

System Action: One or more volumes are audited andinconsistent data is discarded.


User Response: Enter 'Y' to audit the volume or 'N' tostop the process.

ANR1858I AUDIT VOLUME will start countinspect processes.

Explanation: The AUDIT VOLUME command willprocess a range of volumes due to one or more of thefollowing parameters having been specified:FROMDATE, TODATE, or STGPOOL. The AUDITVOLUME processing will start a process for eachvolume that qualifies and process an AUDIT VOLUMEfor each volume with FIX=NO specified.



ANR1859W Node node on session session id receivedCRC protocol validation informationwhen it is not configured to do so.

Explanation: The server received protocol validationinformation for the session and node specified. Thesettings for this node are not configured to performprotocol validation and any CRC information receivedwill be ignored.


User Response: The server administrator shouldevaluate whether or not this node should performprotocol validation. If so, issue the ″UPDATE NODE″command and specify the VALIDATEPROTOCOLoption with the appropriate setting to enable protocolvalidation.

If this is a TYPE=SERVER node for the target of avirtual volume operation and protocol validation is notdesired, the server definition on the source servershould be updated with VALIDATEPROTOCOL=NOset. Otherwise, if protocol validate is desired, theSERVER type node on the target server should beupdated using the ″UPDATE NODE″ command with″VALIDATEPROTOCOL=ALL″.

ANR1998E Command: Invalid value for parameterparameter - parameter value.

Explanation: The value (parameter value) specified forthe (parameter) parameter in command command is not avalid value for this parameter.


User Response: Reissue the command and specify avalid parameter value. For information on valid valuesfor the parameter for the command, refer to theAdministrator’s Reference for your particular platform.

ANR1999I Command completed successfully.

Explanation: Processing for the specified commandcompleted successfully.



ANR2000E Unknown command - command.

Explanation: The specified command is not a validserver command.


User Response: Reissue the correct command.



ANR2001E Insufficient server memory to initiatecommand.

Explanation: A command has been entered, but theserver cannot obtain enough internal memory toprocess the command.



ANR2002E Missing closing quote character.

Explanation: A server command that contains aquoted parameter has been entered, but a matchingclosing quote is missing.


User Response: Reissue the command with properlymatched quotes.

ANR2003E Illegal use of keyword parametercharacter (=) - parameter.

Explanation: A server command contains theparameter shown followed by an equal sign (=), but theparameter is not a keyword parameter.



ANR2004E Missing value for keyword parameter -parameter.

Explanation: A server command containing a keywordparameter has been entered, but the value for theparameter is missing.


User Response: Reissue the command and supply avalue for the keyword parameter.

ANR2005E Keyword parameter character (=) maynot be surrounded by blanks.

Explanation: A server command contains a keywordparameter followed by an equal sign (=), but the equalsign is preceded or followed by a blank, or both.


User Response: Reissue the command without blanksnext to the equal sign.

ANR2006E Activity log process was not started, thedefault output stream cannot be opened.

Explanation: The process that monitors the default(console) output stream and maintains the activity logcannot access that output stream.

System Action: The server does not update theactivity log.


ANR2007E Activity log process was not started, dueto an internal error.

Explanation: The process that monitors the default(console) output stream and maintains the activity logcannot start due to a server internal error.



ANR2008E Activity log process has stopped -database transaction could not bestarted.

Explanation: The process that monitors the default(console) output stream and maintains the activity logcannot continue due to a server transaction failure. Thismay be a memory shortage error.

System Action: The server stops updating the activitylog.


ANR2009E Activity log process has stopped -database error.

Explanation: The process that monitors the default(console) output stream and maintains the activity logcannot continue due to a server database error.





ANR2010W Server is out of LOG space in addingentries to the Activity Log. Consolemessages will not be logged until LOGspace is available.

Explanation: The process that monitors the default(console) output stream and maintains the activity logcannot update the activity log due to a lack of recoverylog space.



ANR2011W Server is out of DB space in addingentries to the Activity Log. Consolemessages will not be logged until DBspace is available.

Explanation: The process that monitors the default(console) output stream and maintains the activity logcannot update the activity log due to a lack of databasespace.



ANR2012W Activity log process has encounteredunexpected table data output in thedefault output stream.

Explanation: The process that monitors the default(console) output stream and maintains the activity loghas detected invalid data in the console stream.



ANR2013E The activity log process has encounteredunexpected output data in the consoleoutput stream. The process will berestarted.

Explanation: The process that monitors console outputand maintains the activity log has detected invalid data(unknown data type) in the console stream.

System Action: The server restarts the activity logrecording process. While the process is restarting, theserver may not be able to record some consolemessages in the activity log.

User Response: The server may be low on availablememory. Allocate additional storage to the server. Fordetails, issue HELP MEMORY to display theinformation online or see “Appendix A. AllocatingAdditional Server Memory”.

ANR2014E Activity log pruning process could notbe started, due to an internal error.

Explanation: The process that removes expired recordsfrom the server activity log cannot begin execution dueto a server internal error.

System Action: The server does not prune the activitylog.


ANR2015E Activity log failure - databasetransaction could not be started.

Explanation: The process that removes expired recordsfrom the server activity log has failed due to a databasetransaction failure, which may be a memory shortageerror.

System Action: The server ends activity log pruning.


ANR2016E Activity log failure - database error.

Explanation: The process that removes expired recordsfrom the server activity log has failed due to a serverdatabase error.

System Action: The server ends activity log pruning.


ANR2017I Administrator Administrator Name issuedcommand: Command

Explanation: This message records the fact that thenamed administrator issued the command specified.The messages is issued and logged to provide an audittrail for administrative commands.

System Action: Server operation continues




ANR2018E Administrator Command: Unicodeconversion failed for argument CommandArgument

Explanation: The specified command argument couldnot be converted to a Unicode string. Conversion canfail if the string includes characters that are notavailable in the server code page, or if the server has aproblem accessing system conversion routines.

System Action: Server command fails

User Response: Make sure that the server’s locale isproperly configured.

ANR2019I Command: No nodes updated.

Explanation: An UPDATE NODE command has beenentered, but no objects were updated.



ANR2020E Command: Invalid parameter - parameter.

Explanation: The specified server command has beenentered with an invalid parameter.



ANR2021E Command: Missing subcommandkeyword.

Explanation: The specified server command has beenentered without a valid subcommand (secondparameter).



ANR2022E Command: One or more parameters aremissing.

Explanation: The specified server command has beenentered without all required parameters.



ANR2023E Command: Extraneous parameter -parameter.

Explanation: The specified server command containsmore positional parameters than is allowed.



ANR2024E Command: Too many parametersspecified.

Explanation: The specified server command containsmore positional parameters than is allowed.



ANR2025E Command: Command failed - serverthread resource not available.

Explanation: A server command, which has arequirement to start a server thread, has been enteredbut cannot be executed because no server thread isavailable.


User Response: Reissue the command. If thecommand fails with the same error, wait for serveractivity to decrease and try again.

ANR2026E Command: Command failed - sufficientserver memory is not available.

Explanation: A server command has been entered butcannot be processed because sufficient memory is notavailable to the server.



ANR2027E Command: Command failed - sufficientserver recovery log space is notavailable.

Explanation: A server command has been entered butcannot be processed because sufficient recovery logspace is not available.





ANR2028E Command: Command failed - sufficientserver database space is not available.

Explanation: A server command has been entered butcannot be processed because sufficient database spaceis not available.



ANR2029E Command: Transaction failed; commandnot executed.

Explanation: A command that is part of the currenttransaction has failed; therefore, any additionalcommands fail.


User Response: Stop the administrative session,restart it, and try the command again. If this problempersists, contact your service representative.

ANR2030E Commit not accepted; transaction failed.

Explanation: A command that is part of the currenttransaction has failed; therefore, a COMMIT commandcannot be processed.

System Action: The server does not process theCOMMIT command.

User Response: Stop the administrative session,restart it, and try the command again. If this problempersists, contact your service representative.

ANR2031E Command: At least one attribute must bespecified for update.

Explanation: The specified UPDATE command hasbeen entered, but no attributes have been specified forupdating.


User Response: Reissue the UPDATE command withone or more attributes to be updated.

ANR2032E Command: Command failed - internalserver error detected.

Explanation: An internal error has occurred during anattempt to process a server command. This messagealways accompanies another error message andprovides more detail about that error.



ANR2033E Command: Command failed - lockconflict.

Explanation: A server command that requires theserver to lock a system resource has been entered. Thecommand cannot be executed because the resource isalready in use by another command or process.


User Response: Try the command again at a latertime.

ANR2034E Command: No match found using thiscriteria.

Explanation: The specified command has beenentered, but no objects that match the criteria can befound.



ANR2035E Command: Administrator administratorname is not authorized to issue thiscommand.

Explanation: The specified administrator has enteredthe indicated command, but this administrator does nothave the proper authority necessary to run thecommand. Note: This message can be issued as a resultof the server option REQSYSAUTHOUTFILE YES beingin effect.


User Response: Examine previous messages for anyadditional information. Issue the command from aproperly authorized administrator ID, or contact thesystem administrator to have additional authoritygranted to the current administrator ID.

ANR2036E Command: Process could not be started -sufficient memory is not available.

Explanation: A background process cannot be startedfor the indicated command because sufficient memoryis not available to the server.

System Action: A new process is not started toexecute this command.

User Response: Allocate additional storage to theserver. For details, issue HELP MEMORY to display the



information online or see “Appendix A. AllocatingAdditional Server Memory”.

ANR2037E Command: Process could not be started -lock conflict.

Explanation: A background process cannot be startedfor the indicated command because a required systemresource is already locked by another command orprocess.

System Action: A new process is not started toexecute this command. If other processes have beenstarted for this command, these processes may executesuccessfully.

User Response: If necessary, try the command againat a later time.

ANR2038E Command: Process could not be started -server thread resource not available.

Explanation: A background process cannot be startedfor the indicated command because no server thread isavailable.


User Response: If necessary, reissue the command. Ifthe command fails with the same error, wait for serveractivity to decrease and try again.

ANR2039E Command: Process could not be started -internal server error detected.

Explanation: A background process cannot be startedfor the indicated command because an internal errorhas occurred.



ANR2040W This command attempts to restore allfiles in storage pool storage pool whichhave previously been found to bedamaged or which reside on a volumewith access mode ″destroyed″; existingreferences to files in storage pool storagepool will be deleted from the databaseafter the files have been restored.

Explanation: Issuing the RESTORE STGPOOLcommand will result in deletion of existing files in theindicated primary storage pool after these files havebeen restored from a copy storage pool. If a volumewith access mode destroyed becomes empty because allfiles on the volume have been restored to anotherlocation, the destroyed volume will be deleted from thedatabase.


User Response: Enter 'Y' to restore the storage pool,'N' otherwise.

ANR2041W This command attempts to restore allfiles in storage pool storage pool whichreside on one of the volumes specifiedin the command; existing references tofiles on these volumes will be deletedfrom the database after the files havebeen restored.

Explanation: Issuing the RESTORE VOLUMEcommand causes the access mode of the specifiedvolumes to be updated to destroyed. Existing files willbe deleted from the specified volumes after these fileshave been restored from a copy storage pool. If avolume with access mode destroyed becomes emptybecause all files on the volume have been restored toanother location, the destroyed volume will be deletedfrom the database.


User Response: Enter 'Y' to restore the volumes, 'N'otherwise.

ANR2042E Command: Copied parameter not validfor copy storage pool volume.

Explanation: The QUERY CONTENT server commandhas been entered with an invalid parameter. COPIED isnot a valid parameter when the volume specifiedbelongs to a copy storage pool.


User Response: Reissue the command without theCOPIED parameter.



ANR2043E Command: WAIT parameter not allowedfrom server console.

Explanation: The WAIT parameter is not allowed forcommands issued from the server console.


User Response: Either reissue the command withoutthe WAIT parameter or else reissue the command froman administrator using an Administrative Client.

ANR2044E Command: Invalid option’s value -Option’s value.

Explanation: The set option command has beenentered with an invalid value.


User Response: Reissue the command with a validvalue.

ANR2045E Command: An error (error code) occurredduring a write operation.

Explanation: The server detects an error whileattempting a write operation.


User Response: Refer to the other displayed messagesto determine why the write operation has failed.

ANR2046I optionset name: Optionset optionset namedefined.

Explanation: The requested option set has been addedto the system in response to a DEFINE OPTIONSETcommand.



ANR2047E Command: Optionset optionset name isalready defined.

Explanation: A DEFINE OPTIONSET command hasbeen entered that specifies an optionset name alreadydefined to the server.


User Response: To define the optionset, reissue thecommand and specify a different optionset name.

ANR2048I Command: Optionset optionset namedeleted.

Explanation: The requested option set has beendeleted from the system in response to a DELETEOPTIONSET command.



ANR2049E Command: Optionset optionset name is notdefined.

Explanation: The command shown specifies anoptionset that is not defined in the server.



ANR2050I Command: Option option name defined inoptionset option set name.

Explanation: The requested option has been added tothe specified optionset in response to a DEFINEOPTIONSET command.



ANR2051E Command: Option option name, sequencenumber sequence number is alreadydefined in optionset option set name.

Explanation: The requested option already exists inthe optionset specified by the DEFINE CLIENTOPTcommand.



ANR2052E Command: Option option name, sequencenumber sequence number is not definedin optionset option set name.

Explanation: The requested option is not defined inthe optionset specified by the DELETE CLIENTOPTcommand.



ANR2053I Command: Option option name, sequencenumber sequence number, has beendeleted from optionset option set name.

Explanation: The requested option has been deletedfrom the specified optionset in response to a DELETECLIENTOPT command.





ANR2054I Command: Optionset optionset nameupdated.

Explanation: The requested option set has beenupdated in the system in response to an UPDATEOPTIONSET command.



ANR2055I Command: Optionset source optionset namecopied to optionset target optionset name.

Explanation: This message is displayed in response tothe COPY OPTIONSET command. The optionsetnamed source optionset name has been copied to theoptionset named target optionset name.


User Response: None. The requested option set hasbeen added to the system in response to a COPYOPTIONSET command.

ANR2056E Command: Invalid option name - optionname. Retry using the full optionname.

Explanation: The command shown specifies an invalidoption name.


User Response: Reissue the command with a validoption name.

ANR2057E Command: Invalid option value - optionvalue.

Explanation: The command shown specifies an invalidoption value.


User Response: Reissue the command with a validoption value.

ANR2058W Command: Options file Filespec not found- user needs to update the file manually.

Explanation: The server options file cannot be openedor found.

System Action: The command is processed but theoption is not updated in the options file.

User Response: Use a text editor to update the serveroptions file if the user wants to use this value when theserver restarts later. If the user does not update the file,the current value in the options file will be used whenthe server restarts.

ANR2059W Command: Error occurs when writing toFilespec - user needs to update the filemanually.

Explanation: An error occurs when trying to write thenew value to the server options file.

System Action: The command is processed but theoption is not updated in the options file.

User Response: Use a text editor to update the serveroptions file if the user wants to use this value when theserver restarts later. If the user does not update the file,the current value in the options file will be used whenthe server restarts.

ANR2060I Node node name registered in policydomain domain name.

Explanation: The requested backup-archive node hasbeen added to the system in response to a REGISTERNODE command and has been assigned to the policydomain indicated.



ANR2061I Node node name removed from policydomain domain name.

Explanation: In response to a REMOVE NODEcommand, the requested backup-archive node has beenremoved from the system.



ANR2062I Node node name renamed to new nodename.

Explanation: In response to a RENAME NODEcommand, the requested backup-archive node has beenrenamed to the new name shown.



ANR2063I Node node name updated.

Explanation: One or more attributes of abackup-archive node have been updated by anUPDATE NODE command.





ANR2064I Node node name locked.

Explanation: In response to a LOCK NODE command,the indicated backup-archive node has been locked.



ANR2065I Node node name is already locked.

Explanation: The indicated backup-archive nodereferenced in the LOCK NODE command is alreadylocked.



ANR2066I Node node name unlocked.

Explanation: In response to an UNLOCK NODEcommand, the indicated backup-archive node isunlocked.



ANR2067I Node node name is already unlocked.

Explanation: The indicated backup-archive nodereferenced in the UNLOCK NODE command is notlocked.



ANR2068I Administrator administrator ID registered.

Explanation: In response to a REGISTER ADMINcommand, the requested administrator ID has beenadded to the system.



ANR2069I Administrator administrator ID removed.

Explanation: In response to a REMOVE ADMINcommand, the requested administrator ID has beenremoved from the system.



ANR2070I Administrator administrator ID renamedto new administrator ID.

Explanation: In response to a RENAME ADMINcommand, the requested administrator ID has beenchanged to the new name shown.



ANR2071I Administrator administrator ID updated.

Explanation: One or more attributes of anadministrative user have been updated by an UPDATEADMIN command.



ANR2072I Administrator administrator ID locked.

Explanation: In response to a LOCK ADMINcommand, the indicated administrator ID has beenlocked.



ANR2073I Administrator administrator ID is alreadylocked.

Explanation: The indicated administrator IDreferenced in the LOCK ADMIN command is alreadylocked.



ANR2074I Administrator administrator ID unlocked.

Explanation: In response to an UNLOCK ADMINcommand, the indicated administrator ID is unlocked.



ANR2075I Administrator administrator ID is alreadyunlocked.

Explanation: The indicated administrator IDreferenced in the UNLOCK ADMIN command is notlocked.



ANR2076I System privilege granted toadministrator administrator ID.

Explanation: In response to a GRANT AUTHORITYcommand, system privilege class has been granted tothe indicated administrator.





ANR2077I Unrestricted policy privilege granted toadministrator administrator ID.

Explanation: In response to a GRANT AUTHORITYcommand, unrestricted policy privilege has beengranted to the indicated administrator.



ANR2078I Restricted policy privilege granted toadministrator administrator ID - policydomain domain name.

Explanation: In response to a GRANT AUTHORITYcommand, restricted policy privilege for the specifiedpolicy domain has been granted to the indicatedadministrator.



ANR2079I Unrestricted storage privilege granted toadministrator administrator ID.

Explanation: In response to a GRANT AUTHORITYcommand, unrestricted storage privilege has beengranted to the indicated administrator.



ANR2080I Restricted storage privilege granted toadministrator administrator ID - storagepool storage pool name.

Explanation: In response to a GRANT AUTHORITYcommand, restricted storage privilege for the specifiedstorage pool has been granted to the indicatedadministrator.



ANR2081I Analyst privilege granted toadministrator administrator ID.

Explanation: In response to a GRANT AUTHORITYcommand, analyst privilege class has been granted tothe indicated administrator.



ANR2082I Operator privilege granted toadministrator administrator ID.

Explanation: In response to a GRANT AUTHORITYcommand, operator privilege class has been granted tothe indicated administrator.



ANR2083I System privilege revoked foradministrator administrator ID.

Explanation: In response to a REVOKE AUTHORITYcommand, system privilege class has been revokedfrom the indicated administrator.



ANR2084I Policy privilege revoked foradministrator administrator ID.

Explanation: In response to a REVOKE AUTHORITYcommand, policy privilege class for all policy domainshas been revoked from the indicated administrator.



ANR2085I Restricted policy privilege revoked foradministrator administrator ID - policydomain domain name.

Explanation: In response to a REVOKE AUTHORITYcommand, restricted policy privilege for the specifiedpolicy domain has been revoked from the indicatedadministrator.



ANR2086I Storage privilege revoked foradministrator administrator ID.

Explanation: In response to a REVOKE AUTHORITYcommand, storage privilege class for all storage poolshas been revoked from the indicated administrator.



ANR2087I Restricted storage privilege revoked foradministrator administrator ID - storagepool storage pool name.

Explanation: In response to a REVOKE AUTHORITYcommand, restricted storage privilege for the storagepool indicated has been revoked from the indicatedadministrator.





ANR2088I Analyst privilege revoked foradministrator administrator ID.

Explanation: In response to a REVOKE AUTHORITYcommand, analyst privilege class has been revokedfrom the indicated administrator.



ANR2089I Operator privilege revoked foradministrator administrator ID.

Explanation: In response to a REVOKE AUTHORITYcommand, operator privilege class has been revokedfrom the indicated administrator.



ANR2090I Activity log retention period set tonumber of days days.

Explanation: The number of days that activity recordsare kept in the server activity log has been set to thevalue indicated with the SET ACTLOGRETENTIONcommand.



ANR2091I Accounting parameter set to value.

Explanation: Accounting record generation has beenturned on or off as indicated with the SETACCOUNTING command.



ANR2092I Password expiration period set tonumber of days days.

Explanation: The number of days that a password canbe used before it must be changed has been set to thevalue indicated with the SET PASSEXP command.



ANR2093I Registration parameter set to registrationmethod.

Explanation: Backup-archive node registration hasbeen set to the method indicated with the SETREGISTRATION command.



ANR2094I Server name set to server name.

Explanation: The name that the server displays andcommunicates to backup-archive nodes has been set tothe value indicated with the SET SERVERNAMEcommand.



ANR2095I Authentication parameter set to value.

Explanation: The requirement for a node oradministrator to enter a password when establishing asession with the server has been turned on or off asindicated with the SET AUTHENTICATION command.



ANR2096I Server now enabled for backup/archiveclient access.

Explanation: The server has been made available foruse by backup-archive clients with the ENABLEcommand.



ANR2097I Server now disabled for backup/archiveclient access.

Explanation: The server has been made unavailablefor use by backup-archive clients with the DISABLEcommand.



ANR2098E Command: Invalid URL specification -url.

Explanation: The specified URL is too long.


User Response: Reissue the command and enter ashorter URL value

ANR2099I Administrative userid admininstratorname defined for OWNER access to nodenode name.

Explanation: An administrator with the specifiedname was created having OWNER access to the clientnode. This administrator is created for accessing theclient node from an interactive interface.





ANR2100I Activity log process has started.

Explanation: The automatic server process thatremoves expired server activity log records has begunprocessing.



ANR2101I Activity log process stopped, activity logretention set to 0.

Explanation: A SET ACTLOGRETENTION commandhas set the retention period to zero days. As a result,activity logging stops.

System Action: The activity log process stopsrecording console output in the server activity log.


ANR2102I Activity log pruning started: removingentries prior to date time.

Explanation: Server activity log records older than thedate and time indicated are being removed from theactivity log.



ANR2103I Activity log pruning completed: numberof records records removed.

Explanation: All expired (older than the log archiveretention value) server activity log records have beenremoved; the number of records deleted is shown.



ANR2104I Activity log process restarted - recoveredfrom an insufficient space condition inthe Log or Database.

Explanation: The process that records data in theserver activity log has failed because of insufficientspace in the server recovery log or database; space isnow available and the process is again recording data.

System Action: Activity logging resumes.


ANR2105W Command: Node was registered in excessof license terms - node registration willfail after 120% of the licensed quantityof nodes have been registered.

Explanation: The server has detected the addition of anode in excess of the terms under which the server islicensed. The REGISTER NODE command will fail after

120% of the licensed number of nodes have beenregistered.


User Response: Use the QUERY LICENSE commandto determine the license terms that are no longer incompliance. You may remove nodes to reduce thenumber of registered nodes or purchase additionalclient node connections. If additional nodes have beenpurchased, issue the AUDIT LICENSES command toresynchronize the server configuration with licenseterms.

ANR2106I Server HALT command: Quiescingdatabase update activity.

Explanation: The server is quiescing transactions thatupdate the database so that the database is in aconsistent state when the server is halted. This actionoccurs when HALT QUIESCE is specified to halt theserver with the database in a consistent state.

System Action: When database update transactionactivity has been stopped, the server program ends.


ANR2107I Server HALT command: Database updateactivity is now quiesced.

Explanation: The server has stopped all databaseupdate transaction activity. This action occurs whenHALT QUIESCE is specified to halt the server with thedatabase in a consistent state.

System Action: The server program ends.


ANR2108I Server HALT command: Reattempting toquiesce database update activity.

Explanation: The server is quiescing transactions thatupdate the database so that the database is in aconsistent state when the server is halted. The previousattempt at quiescing database activity failed because ofthe current transaction load on the server. The quiesceoperation is being reattempted. This action occurs whenHALT QUIESCE is specified to halt the server with thedatabase in a consistent state.

System Action: When database update transactionactivity has been stopped, the server program ends.


ANR2109I Server HALT command: Database updatetransaction activity could not besuccessfully quiesced.

Explanation: After repeated attempts, server databaseupdate transaction activity could not be quiesced. Theserver is not halted with the HALT QUIESCE



command. Attempts to quiesce database updatetransaction activity can fail if heavy transaction load ison the server when a HALT QUIESCE command isentered.


User Response: You may disable the server, cancel allclient sessions accessing the server, cancel all processes,and reenter the HALT QUIESCE command to stopserver processing. The HALT command may also beused to stop server processing without quiescingdatabase transaction update activity. Server recoverylogic will be used when the server is restarted toreconcile database transaction activity.

ANR2110I Command started as process process ID.

Explanation: A background process has been startedto service the command command. The backgroundprocess is defined as process process ID.

System Action: The server processes the indicatedcommand.

User Response: To query the progress of thebackground process, use the QUERY PROCESScommand. To cancel the background process, use theCANCEL PROCESS command. Use the process IDnumber to specify this process.

ANR2111W Command: There is no data to process forstorage pool.

Explanation: The indicated command does not haveany data to process. This can occur if the commandspecifies an empty volume or pool. The command endswithout starting a background process.



ANR2112E Command: Volume volume name is not ina primary storage pool.

Explanation: The command indicated specifies thename of a volume that does not belong to a primarystorage pool. The command syntax requires that avolume in a primary storage pool be specified.


User Response: Reissue the command with a volumein a primary pool.

ANR2113E Command: Volume volume name does notbelong to the same storage pool (storagepool name) as previously listed volumes.

Explanation: The indicated command accepts a list ofone or more volumes which belong to the same storagepool. The named volume does not belong to the same

storage pool as the previously listed volumes.


User Response: Issue the command with a list ofvolumes that belong to the same storage pool.

ANR2114I Command: Access mode for volumevolume name updated to ″destroyed″.

Explanation: A RESTORE VOLUME command hasupdated the access mode of the indicated volume todestroyed.

System Action: Restore processing continues.


ANR2115E Command: Access mode for volumevolume name cannot be changed to″destroyed″ - volume is still online.

Explanation: A RESTORE VOLUME command cannotchange the access mode of the indicated volume todestroyed because the volume is still online.


User Response: Issue the VARY OFFLINE command,and reissue the RESTORE VOLUME command.

ANR2116E Command: Access mode for volumevolume name cannot be changed to″destroyed″ - volume does not belong toa primary storage pool.

Explanation: The access mode for the indicatedvolume cannot be changed to destroyed because thevolume does not belong to a primary storage pool.

System Action: The access mode for this volume isnot changed.


ANR2117E Command: Access mode for volumevolume name cannot be changed to″offsite″ - volume either does not belongto a copy storage pool or from a deviceclass of DEVTYPE=SERVER.

Explanation: The access mode for the indicatedvolume cannot be changed to offsite because thevolume either does not belong to a copy storage poolor is of a device class with a DEVTYPE of SERVER.

System Action: The access mode for this volume isnot changed.




ANR2118E Storage pool storage pool name specifiedon the MOVE DATA command is not avalid poolname and or pooltype forvolume volume name.

Explanation: If the volume belongs to a primarystorage pool, then the storage pool specified must alsobe a primary storage pool. If the volume belongs to acopy storage pool, then the specified storage pool mustbe the same storage pool as that of the volume.

System Action: The MOVE DATA process fails.

User Response: Provide a valid primary storage poolname if the volume belongs to a primary storage pool.If the volume belongs to a copy storage pool, removethe storage pool name from the command.

ANR2119I The Option option has been changed inthe options file.

Explanation: The option is updated in the serveroptions file.

System Action: Server continues.


ANR2120E Command: Invalid platform name -platform name.

Explanation: The command shown specifies an invalidplatform name.


User Response: Reissue the command with a validplatform name.

ANR2121W ATTENTION: More than amount changedunit megabytes, gigabytes or terabytes of thedatabase has changed and the lastdatabase backup was more than hoursname hours ago. Use the BACKUP DBcommand to provide for databaserecovery.

Explanation: The server issues this warning when asignificant amount of database change activity hasoccurred and the server database has not been backedup.


User Response: To provide for server databaserecovery should a hardware or software problem affectyour database, use the BACKUP DB command to backup the database.

ANR2122E command name: The DOMAINSparameter cannot be specified when theNODES parameter is specified.

Explanation: Both the NODES and DOMAINSparameters were specified. The NODES parameter maybe specified, or the DOMAINS parameter may bespecified, but both should not be specified at the sametime.


User Response: Reenter the command specifyingeither the NODES parameter or the DOMAINSparameter, but not both.

ANR2123E command name: The NODES parametercannot be specified when theDOMAINS parameter is specified.

Explanation: Both the NODES and DOMAINSparameters were specified. The NODES parameter maybe specified, or the DOMAINS parameter may bespecfied, but both should not be specified at the sametime.


User Response: Reenter the command specifyingeither the NODES parameter or the DOMAINSparameter, but not both.

ANR2124E command name: Invalid Client authorityspecified: authority.

Explanation: An invalid client authority was specifiedin a GRANT AUTHORITY or REVOKE AUTHORITYcommand when the CLASS=NODE parameter wasspecified.


User Response: Reenter the command specifying avalid client authority.

ANR2125I command name: Administratoradministrator name was granted OWNERauthority for client client name.

Explanation: The named administrator was grantedOWNER authority over the named client node as theresult of a GRANT AUTHORITY command.



ANR2126I command name: Administratoradministrator name was granted ACCESSauthority for client client name.

Explanation: The named administrator was grantedACCESS authority over the named client node as theresult of a GRANT AUTHORITY command.





ANR2127I command name: Owner authority for nodeclient node was revoked for administratoradministrator.

Explanation: OWNER authority over the named clientnode was revoked from the named administrator as aresult of a REVOKE AUTHORITY command.



ANR2128I command name: Access authority for nodeclient node was revoked for administratoradministrator.

Explanation: ACCESS authority over the named clientnode was revoked from the named administrator as aresult of a REVOKE AUTHORITY command.



ANR2129I Administrative userid admininstratorname defined ONLY for authority overnode node name has been removed.

Explanation: The specified administrator has beenremoved because the client node was removed and theadministrator onyly had OWNER access to thespecified node.



ANR2130S Early Product Version has Expired.Server is HALTing.

Explanation: This server is pre-release version of theserver. The pre-release version’s expiration date hasbeen reached.

System Action: The server halts.

User Response: Install the product version of theserver.

ANR2131I Server password set.

Explanation: The password that the server uses toallow other servers to communicate with it has beenset, changed or removed with the SETSERVERPASSWORD command.



ANR2132I Server hladdress set to hladdress.

Explanation: The high level address that other serversuse to communicate with this server has been set to thevalue indicated with the SET SERVERHLADDRESScommand.



ANR2133I Server lladdress set to lladdress.

Explanation: The low level address that other serversuse to communicate with this server has been set to thevalue indicated with the SET SERVERLLADDRESScommand.



ANR2134I Server url set to url.

Explanation: The url that other servers use tocommunicate with this server has been set to the valueindicated with the SET SERVERURL command.



ANR2135I Crossdefine set to state.

Explanation: The ability for another server toautomatically define itself to this server has beenturned on or off as indicated with the SETCROSSDEFINE command.



ANR2136I Administrator administrator name alreadyhas POLICY access for domain policydomain name.

Explanation: The named administrator already hasPOLICY authority over the named policy domain. Anattempt to grant client authority over this domain isignored.

System Action: The policy domain is skipped.


ANR2137I Administrator administrator name alreadyhas POLICY access for domain policydomain name to which node node namebelongs.

Explanation: The named administrator already hasPOLICY authority over the named policy domain. Anattempt to grant client authority for a client in thisdomain is ignored.



System Action: The client is skipped.


ANR2138I Minimum password length set to length.

Explanation: The minimum length of a password anode or administrator may send to the server isindicated with the SET MINPWLENGTH command.



ANR2139E Command: The value supplied for theminimum password length is not valid -length.

Explanation: A SET MINPWLENGTH command hasbeen entered that specifies a value for the length is notvalid. Valid values are from 0 to 64, inclusive.



ANR2140E Command: Invalid activity log retentionperiod - retention value.

Explanation: A SET ACTLOGRETENTION commandhas been entered that specifies an invalid log retentionperiod.



ANR2141E Command: Invalid password expirationperiod - days value.

Explanation: A SET PASSEXP command has beenentered that specifies an invalid days value.


User Response: Reissue the command with apassword expiration period.

ANR2142E Command: Invalid server name - servername.

Explanation: A SET SERVERNAME command hasbeen entered that specifies an invalid server name.


User Response: Reissue the command with a validserver name.

ANR2143E Command: Invalid node name - nodename.

Explanation: The command shown specifies an invalidnode name.


User Response: Reissue the command with a validnode name.

ANR2144E Command: Invalid password - password.

Explanation: The command specifies an invalid nodepassword.


User Response: Ensure that the password adheres tonaming convention rules and meets the requiredminimum password length as set by youradministrator. Then, reissue the command with a validpassword.

ANR2145E Command: Contact information exceedsmaximum characters characters.

Explanation: A REGISTER NODE or REGISTERADMIN command has been entered that specifies acontact information value that is too long. Themaximum valid length is shown in the command.


User Response: Reissue the command with lesscontact information.

ANR2146E Command: Node node name is notregistered.

Explanation: The command shown specifies a nodethat is not registered with the server.



ANR2147E Command: Node node name is alreadyregistered.

Explanation: A REGISTER NODE command has beenentered that specifies a node name already registeredwith the server.


User Response: To register the node, reissue thecommand and specify a different node name.



ANR2148E Command: Administrator administrator IDis not registered.

Explanation: The command shown specifies anadministrator ID that is not registered with the server.



ANR2149E Command: Administrator administrator IDis already registered.

Explanation: A REGISTER ADMIN command hasbeen entered that specifies an administrator ID alreadyregistered with the server.


User Response: To register the administrator, reissuethe command and specify a different administrator ID.

ANR2150E Command: Node node name is currentlyaccessing the server.

Explanation: The command shown specifies a nodethat has an active session with the server.


User Response: Reissue the command at a later time,or if necessary, cancel the current session and reissuethe command.

ANR2151E Command: Administrator administrator IDis currently accessing the server.

Explanation: An UPDATE ADMIN or REMOVEADMIN command has been entered that specifies anadministrator ID that is having an active session withthe server.


User Response: Reissue the command at a later time,or if necessary, cancel the current session and reissuethe command.

ANR2152E Command: Inventory references still existfor node node name.

Explanation: A REMOVE NODE command has beenentered for a node for which the server is still storingbackup or archive data, or both.


User Response: To remove the node, delete all of itsfile spaces from the server and reissue the command.

ANR2153E Command: Invalid file space name -filespace name.

Explanation: The specified server command has beenentered with a file space name that is longer thanallowed.


User Response: Reissue the command with a valid filespace name.

ANR2154E Command: Invalid administrator name -administrator ID.

Explanation: The command shown specifies an invalidadministrator ID.


User Response: Reissue the command with a validadministrator ID.

ANR2155E Command: Invalid privilege class -privilege class.

Explanation: A command specifies an invalidadministrative privilege class.


User Response: Reissue the command with a validprivilege class.

ANR2156E Command: Administrator administrator IDhas already been granted systemprivilege.

Explanation: A GRANT AUTHORITY command hasbeen issued to grant system authority to anadministrator ID that already has system authority.



ANR2157E Command: Other privileges cannot begranted with system privilege.

Explanation: A GRANT AUTHORITY command hasbeen issued to grant system authority to anadministrator ID, and at the same time to grant otherprivileges.


User Response: Reissue the GRANT AUTHORITYcommand specifying only system privilege class.



ANR2158E Command: Policy domains cannot bespecified for unrestricted policyadministrator administrator ID.

Explanation: A REVOKE AUTHORITY command hasbeen issued to revoke an administrator’s policyauthority over a specific policy domain, but theadministrator has unrestricted policy authority.



ANR2159E Command: Storage pools cannot bespecified for unrestricted storageadministrator administrator ID.

Explanation: A REVOKE AUTHORITY command hasbeen issued to revoke an administrator’s storageauthority over a specific storage pool, but theadministrator has unrestricted storage authority.



ANR2160E Command: No new privileges granted toadministrator administrator ID.

Explanation: A GRANT AUTHORITY command hasbeen issued to grant authority to an administrator ID,but the administrator already has all privilegesspecified.



ANR2161E Command: Only system privilege can berevoked for administrator administratorID.

Explanation: A REVOKE AUTHORITY command hasbeen issued to revoke one or more of anadministrator’s privileges, but the administrator hassystem authority.



ANR2162E Command: No privileges revoked foradministrator administrator ID.

Explanation: A REVOKE AUTHORITY command hasbeen issued to revoke authority from an administratorID, but the administrator does not have any of theprivileges specified.



ANR2163E Command: Command is invalid foradministrator ID.

Explanation: The command specified cannot be issuedfor the server console. For instance, the server consoleadministrator ID cannot be removed.



ANR2164E Command: Command rejected -administrator ID is the only systemadministrator.

Explanation: A REMOVE ADMIN or REVOKEAUTHORITY command has been issued to remove orrevoke the authority of the last administrator who hadsystem authority.


User Response: To remove or revoke this ID, grantsystem authority to another administrator ID beforereissuing the command.

ANR2165E Command: Invalid begin date - date.

Explanation: A QUERY ACTLOG command has beenentered that specifies an invalid begin date as a searchcriteria.


User Response: Reissue the command with a validbegin date.

ANR2166E Command: Invalid begin time - time.

Explanation: A QUERY ACTLOG command has beenentered that specifies an invalid begin time as a searchcriteria.


User Response: Reissue the command with a validbegin time.

ANR2167E Command: Invalid end date - date.

Explanation: A QUERY ACTLOG command has beenentered that specifies an invalid end date as a searchcriteria.


User Response: Reissue the command with a validend date.



ANR2168E Command: Invalid end time - time.

Explanation: A QUERY ACTLOG command has beenentered that specifies an invalid end time as a searchcriteria.


User Response: Reissue the command with a validend time.

ANR2169E Command: Invalid message number -message number.

Explanation: A QUERY ACTLOG command has beenentered that specifies an invalid message number as asearch criteria.


User Response: Reissue the command with a validmessage number.

ANR2170E Command: Invalid message search stringargument - search string.

Explanation: A QUERY ACTLOG command has beenentered that specifies an invalid search string as asearch criteria.


User Response: Reissue the command with a validsearch string.

ANR2171E Command: Invalid time range - Begin:date time End: date time.

Explanation: A QUERY ACTLOG command has beenentered that specifies an invalid beginning and endingdate/time range. This error can occur when thebeginning date/time is not before the endingdate/time.


User Response: Reissue the command with a validdate/time range.

ANR2172E Command: No matching administrators.

Explanation: The command shown specified anadministrator ID that does not match any administratorregistered with the server.


User Response: If desired, reissue the command witha different administrator ID.

ANR2173E Command: Location information exceedsmaximum characters characters.

Explanation: A DEFINE or UPDATE VOLUMEcommand has been entered that specifies a locationinformation value that is too long. The maximum validlength is shown in the command.


User Response: Reissue the command with lesslocation information.

ANR2174E Administrator administrator ID is notregistered. Schedule schedule name is notprocessed and is marked as failed.

Explanation: The command shown specifies anadministrator ID that is not registered with the server.The schedule and related command are not processed.


User Response: Update the command schedule with avalid administrator ID which has the proper authorityto execute the scheduled command.

ANR2175I Invalid password limit set to passwordattempts limit attempts.

Explanation: The maximum number of consecutiveinvalid passwords a node or administrator may send tothe server is indicated with the SET INVALIDPWLIMITcommand.



ANR2176E Command: The value supplied for theinvalid password attempts limit is notvalid - password attempts limit.

Explanation: A SET INVALIDPWLIMIT command hasbeen entered that specifies a value for the consecutiveinvalid password attempts limit that is not valid. Validvalues are from 0 to 9999, inclusive.



ANR2177I node/admin name has count invalidsign-on attempts. The limit is limit.

Explanation: The server detected an invalid passwordfor the specified node during sign-on processing. Thenode currently has sent count consecutive invalidpasswords. The maximum allowed is limit. The serverwill lock the node when limit is reached.



System Action: The node or administrator session willbe refused.

User Response: Before the client node is permitted toaccess the server, a properly authorized administratormust unlock the node or administrator with theUNLOCK NODE or UNLOCK ADMIN command.

ANR2178E node/admin name has been locked. Invalidsign-on attempt limit (limit) reached.

Explanation: The specified node has been locked bythe server. The limit for consecutive invalid passwordshas been reached.

System Action: The node or administrator session willbe refused.

User Response: Before the client node is permitted toaccess the server, a properly authorized administratormust unlock the node or administrator with theUNLOCK NODE or UNLOCK ADMIN command.

ANR2179E Administrator administrator should havebeen locked, but was not.

Explanation: The indicated administrator reached thelimit for consecutive invalid passwords and shouldhave been locked. If it were locked, there would be nomeans to execute commands requiring systemauthority.

System Action: The administrator session will berefused.

User Response: Sign-on again using the correctpassword.

ANR2180W Unable to update last access date foradministrator administrator ID -insufficient recovery log space.

Explanation: While establishing an administrativesession for the indicated ID, the server is unable toupdate the administrator’s date of last access due toinsufficient recovery log space.

System Action: The server establishes theadministrative session, but the last access date is notupdated.


ANR2181W Unable to update last access date foradministrator administrator ID -insufficient database space.

Explanation: While establishing an administrativesession for the indicated ID, the server cannot update

the administrator’s date of last access due toinsufficient database space.



ANR2182W Unable to update last access date foradministrator administrator ID - internalserver error.

Explanation: While establishing an administrativesession for the indicated ID, the server cannot updatethe administrator’s date of last access due to a serverinternal error.



ANR2183W DiagnosticID: Transaction transaction IDwas aborted.




ANR2184W DiagnosticID: Transaction transaction IDwas aborted for command command.

Explanation: An error was detected during transactioncommit for the specified server command. Thismessage should be preceded by other messages thatgive additional information about the failed transaction.





ANR2185W Transaction was aborted for commandcommand.




ANR2186W Transaction was aborted for sessionsession number for node node name (clientplatform).




ANR2187W Transaction was aborted for node/adminname.

Explanation: An error is detected during a transactioncommit for the specified node or administrator name.This message should be preceded by other messagesthat give additional information about the failedtransaction.



ANR2188W A Transaction was aborted. The activityis terminating.

Explanation: An error is detected during a transactioncommit. This message should be preceded by othermessages that give additional information about thefailed transaction.

System Action: The activity that generated this errorends.

User Response: Check for additional messages andeliminate the condition that caused the failedtransaction. If the error cannot be isolated and resolved,

contact your service representative.

ANR2189W DiagnosticID: Transaction transaction IDwas aborted for node/admin name.

Explanation: An error is detected during a transactioncommit for the specified node or administrator name.This message should be preceded by other messagesthat give additional information about the failedtransaction.



ANR2190E command: Device class DISK cannot bespecified for this command.

Explanation: The DEVCLASS value DISK cannot bespecified for the command.



ANR2191E command: Volume list contains definedand undefined volumes.

Explanation: The list of volumes specified on theSALVAGE VOLUME command must all be defined tothe server, or all not defined to the server.


User Response: Reissue the command and specify avalid list of volumes.

ANR2192E Command: Unable to start backgroundprocess.

Explanation: The server command processor is notable to start a background process to perform thecommand command.





ANR2193E Command: Invalid option set name -option set name.

Explanation: The command shown specifies an invalidoption set name.


User Response: Reissue the command with a validoption set name.

ANR2194E Command: Invalid option set description- too long.

Explanation: The command shown specifies an invaliddescription. The description is too long.


User Response: Reissue the command with a validdescription.

ANR2195E Command: Invalid option sequencenumber - option sequence number name.

Explanation: The command shown specifies an invalidoption sequence number.


User Response: Reissue the command with a validoption sequence number.

ANR2196E Command: Option name and/or Optionvalue is missing for define.

Explanation: The specified DEFINE command hasbeen entered, but no attributes have been specified forthe definition.


User Response: Reissue the DEFINE command withone or more attributes to be defined

ANR2197E Command: The value supplied for theWEB authentication time out is notvalid - time-out value.

Explanation: A SET WEBAUTHTIMEOUT commandhas been entered that specifies a value that is not valid.Valid values are from 0 to 9999, inclusive.



ANR2198I Command: Web authentication time-outset to time-out value minutes.

Explanation: The time-out value that determines howoften WEB browser administrative users need tore-authenticate with the server has been set with theSET WEBAUTHTIMEOUT command to the valuedisplayed.



ANR2199I Password expiration period for nodenode name set to number of days days.

Explanation: The number of days that the node’spassword can be used before it must be changed hasbeen set to the value indicated with the SET PASSEXPcommand.



ANR2200I Storage pool storage pool name defined(device class device class name).

Explanation: A DEFINE STGPOOL command hascreated the storage pool indicated of the device classshown.



ANR2201I Storage pool storage pool name deleted.

Explanation: A DELETE STGPOOL command hasdeleted the storage pool indicated.



ANR2202I Storage pool storage pool name updated.

Explanation: An UPDATE STGPOOL command hasupdated the storage pool indicated.



ANR2203I Device class device class name defined.

Explanation: A DEFINE DEVCLASS command hascreated the device class indicated.





ANR2204I Device class device class name deleted.

Explanation: A DELETE DEVCLASS command hasdeleted the device class indicated.



ANR2205I Device class device class name updated.

Explanation: An UPDATE DEVCLASS command hasupdated the device class indicated.



ANR2206I Volume volume name defined in storagepool storage pool name (device class deviceclass name).

Explanation: A DEFINE VOLUME command hasdefined the volume indicated in the storage poolshown that belongs to the device class shown.



ANR2207I Volume volume name updated.

Explanation: An UPDATE VOLUME command hasupdated the volume indicated.



ANR2208I Volume volume name deleted fromstorage pool storage pool name.

Explanation: The volume indicated has been deletedby one of the following:v A DELETE VOLUME command was issued.v The volume was empty and the volume’s access

mode was updated to destroyed.v The volume was empty, scratch, and offsite, and the

access mode was changed to readwrite, readonly, orunavailable.

v The volume was scratch, not offsite, and wasemptied by DELETE FILESPACE, RECLAMATION,or RESTORE VOLUME/STGPOOL.



ANR2209W Volume volume name contains no data.

Explanation: The AUDIT VOLUME or MOVE DATAcommand entered specifies a volume that contains nodata.



ANR2210I Vary online initiated for disk volumevolume name.

Explanation: A VARY ONLINE command for thevolume shown is being processed, and if no errorsoccur the volume will be varied online.



ANR2211I Vary offline initiated for disk volumevolume name.

Explanation: A VARY OFFLINE command for thevolume shown is being processed and, if no errorsoccur, the volume will be varied offline.



ANR2212I Command: No volumes updated.

Explanation: An UPDATE VOLUME command hasbeen entered, but no objects were updated.



ANR2213I Command: Storage pool storage pool namerenamed to storage pool name.

Explanation: A RENAME STGPOOL command hasbeen entered. The rename of the storage pool wassuccessful.



ANR2214E Command: Invalid backup set name -backup set name.

Explanation: The command shown specifies an invalidbackup set name.


User Response: Reissue the command with a validbackup set name.

ANR2215E Command: Description text is too long.

Explanation: The specified description text is too longfor a command that allows description text to bespecified.

System Action: The command fails

User Response: Reissue the command specifying ashorter description



ANR2216E Command: Device class must be asequential device class.

Explanation: The device class specified on thecommand is not a sequential device class.


User Response: Reissue the command specifying thename of a sequential device class

ANR2217E Command: Invalid backup set retentionperiod - retention value.

Explanation: Server processing for the backup setcommand command fails because the value (retentionvalue) specified for the RETENTION parameter is notvalid.


User Response: Reissue the command specifying avalid RETENTION value.

ANR2218E Command: A device class must bespecified.

Explanation: The DEVCLASS parameter is notspecified in the command command name. A DEVCLASSvalue must be specified.


User Response: Reissue the command specifying avalid device class. Issue the QUERY DEVCLASScommand for a list of valid device classes for theserver.

ANR2219I Discard Data process ended for volumevolume name - volume is not deletedfrom storage pool storage pool namebecause the volume access is offsite.

Explanation: The process that deleted data for thevolume shown has ended, but the volume has not beendeleted because the volume access is marked as offsite.


User Response: To delete the volume, change thevolume access to readwrite, readonly, or unavailable.

ANR2220W This command will delete volumevolume name from its storage pool afterverifying that the volume contains nodata.

Explanation: A DELETE VOLUME command with theDiscarddata=No option has been entered.

System Action: The system asks whether you wish tocontinue with the command.

User Response: To process the DELETE VOLUME

command, enter 'Y' to continue or 'N' to stop theprocess.

ANR2221W This command will result in thedeletion of all inventory references tothe data on volume volume name, therebyrendering the data unrecoverable.

Explanation: A DELETE VOLUME command with theDiscarddata=Yes option has been entered.


User Response: To process the DELETE VOLUMEcommand, enter 'Y' to continue or 'N' to stop theprocess.

ANR2222I Discard Data process started for volumevolume name (process ID process ID).

Explanation: As a result of a DELETE VOLUMEcommand with the Discarddata=Yes option, the processwhose ID is displayed has begun to delete the data onthe volume shown.

System Action: The server deletes the data on thevolume.


ANR2223I Discard Data process ended for volumevolume name - volume deleted fromstorage pool storage pool name.

Explanation: The process that deleted data for thevolume shown has ended, and the volume has beendeleted.



ANR2224W Discard Data process terminated forvolume volume name - process canceled.

Explanation: The process that was deleting data forthe volume shown, in preparation for deleting thevolume, has been canceled.

System Action: The server does not delete thevolume.


ANR2225W Discard Data process terminated forvolume volume name - volume stillcontains data.

Explanation: The process that was deleting data forthe volume shown, in preparation for deleting thevolume, has ended. However, the volume containsdata.





ANR2226W Discard data process terminated forvolume volume name - sufficient recoverylog space is not available.

Explanation: The process that was deleting data forthe volume shown, in preparation for deleting thevolume, has ended due to a shortage of recovery logspace.



ANR2227W Discard data process terminated forvolume volume name - sufficient memoryis not available.

Explanation: The process that was deleting data forthe volume shown, in preparation for deleting thevolume, has ended due to a shortage of memory.



ANR2228W Discard data process terminated forvolume volume name - lock conflictdetected.

Explanation: The process that was deleting data forthe volume shown, in preparation for deleting thevolume, has ended due to a locking conflict.


User Response: Reissue the command at a later time.If this problem persists, contact your servicerepresentative.

ANR2229W Discard data process terminated forvolume volume name - internal servererror detected.

Explanation: The process that was deleting data forthe volume shown, in preparation for deleting thevolume, has ended due to a server internal error.

System Action: The server does not delete the volume


ANR2232W This command will move all of the datastored on volume volume name to othervolumes within the same storage pool;the data will be inaccessible to usersuntil the operation completes.

Explanation: A move data has been entered that willmove data from the indicated volume to other volumesin the same storage pool. While the data is beingmoved, it will not be available to users.


User Response: Enter 'Y' to continue with thecommand or 'N' to end the process.

ANR2233W This command will move all of the datastored on volume volume name to othervolumes in storage pool storage poolname; the data will be inaccessible tousers until the operation completes.

Explanation: A move data has been entered that willmove data from the indicated volume to volumes inthe storage pool shown. While the data is being movedit will not be available to users.


User Response: Enter 'Y' to continue with thecommand or 'N' to end the process.

ANR2234W This command will halt the server; ifthe command is issued from a remoteclient, it may not be possible to restartthe server from the remote location.

Explanation: A HALT command has been entered.


User Response: Enter 'Y' to halt the server or 'N' toleave the server activated.

ANR2235W This command will removeadministrator adminName. Thisadministrator has defined or updatedschedules. Removing this authorityWILL cause these schedules to fail.

Explanation: A REMOVE ADMINISTRATORcommand has been entered for an administrator thatowns administrative schedules. If you confirm that youwant to proceed with this command, the schedulesowned by this administrator will fail when executed inthe future.


User Response: To process the REMOVE



ADMINISTRATOR command, enter 'Y' to continue or'N' to stop the process. To deal with schedules owneedby the administratirr, use the QUERY SCHEDULEcommand OR an SQL SELECT statement on theADMIN_SCHEDULES table to determine whichschedules were last updated by the administrator. Usethe UPDATE SCHEDULE command to update thoseschedules under an administrator that has authority toexecute them, or use the DELETE SCHEDULEcommand to remove the schedules.

ANR2236W This command has removedadministrator adminName. Thisadministrator has defined or updatedschedules. This WILL cause theseschedules to fail in the future.

Explanation: A REMOVE ADMINISTRATORcommand has been entered and the administratorremoved owns administrative schedules. The scheduleswill fail when executed in the future because they donot belong to a valid administrator.

System Action: The system removes the administrator.

User Response: Use the QUERY SCHEDULEcommand OR an SQL SELECT statement on theADMIN_SCHEDULES table to determine whichschedules were last updated by the administrator. Usethe UPDATE SCHEDULE command to update thoseschedules under an administrator that has authority toexecute them, or use the DELETE SCHEDULEcommand to remove the schedules.

ANR2237W This command has revoked privilegesfor administrator adminName. Thisadministrator has defined or updatedschedules. This may cause theseschedules to fail in the future.

Explanation: A REVOKE AUTHORITY command hasbeen entered.

System Action: The system removes the authority.


ANR2238W This command will result in thedeletion of all inventory references tothe data on filespaces that match thepattern filespace name for node node name,whereby rendering the dataunrecoverable.

Explanation: A DELETE FILESPACE command hasbeen entered.


User Response: To process the DELETE FILESPACEcommand, enter 'Y'; otherwise, enter 'N'.

ANR2239W This command will revoke privilegesfor administrator adminName. Thisadministrator has defined or updatedschedules. Revoking this authority maycause schedules to fail.

Explanation: A REVOKE AUTHORITY command hasbeen entered.


User Response: To process the REVOKE AUTHORITYcommand, enter 'Y' to continue or 'N' to stop theprocess.

ANR2240I Database volume volume name defined.

Explanation: A DEFINE DBVOLUME command hasdefined the database volume indicated.



ANR2241I Database volume copy volume namedefined.

Explanation: A DEFINE DBCOPY command hasdefined the database volume indicated.



ANR2242I Database volume copy volume namedefined; synchronization process started(process ID process ID).

Explanation: A DEFINE DBCOPY command hasadded the volume shown as a database copy volume.The process whose ID is displayed will copy data tothe new volume to synchronize it with existingvolumes.



ANR2243I Database volume volume name deleted.

Explanation: A DELETE DBVOLUME command hasdeleted the database volume indicated.



ANR2244I Delete process initiated for databasevolume volume name (process id processID).

Explanation: In response to a DELETE DBVOLUMEcommand, the process with the process ID shown hasbeen started to delete the volume.





ANR2245I Database volume volume name variedonline.

Explanation: A VARY ONLINE command has put thedatabase volume indicated into an online state.



ANR2246I Vary online process initiated fordatabase volume volume name (processID process ID).

Explanation: In response to a VARY ONLINEcommand, the process with the process ID shown hasbeen started to vary on the database volume indicated.



ANR2247I Database volume volume name variedoffline.

Explanation: A VARY OFFLINE command has put theindicated database volume into an offline state.



ANR2248I Database assigned capacity has beenextended.

Explanation: An EXTEND DB command has increasedthe storage capacity of the database.



ANR2249I Database extension process initiated(process ID process ID).

Explanation: In response to an EXTEND DBcommand, the process with the process ID shown hasbeen started to extend the database.



ANR2250I Database assigned capacity has beenreduced.

Explanation: A REDUCE DB command has decreasedthe storage capacity of the database.



ANR2251I Database reduction process initiated(process ID process ID).

Explanation: In response to a REDUCE DB command,the process with the process ID shown has been startedto reduce the database.



ANR2252W Database volume copy volume name islarger than volume volume name by countmegabyte(s).

Explanation: A DEFINE DBCOPY command hasdefined a database copy volume whose size is largerthan the volume it mirrors by the amount shown.

System Action: The excess capacity is ignored.


ANR2253W The database volume copy to be defined(volume name) is larger than volumevolume name; use of the volume willresult in count megabyte(s) of unusablespace.

Explanation: A DEFINE DBCOPY command isattempting to define a database copy volume whosesize is larger than the volume it mirrors by the amountshown. The excess capacity would not be used.


User Response: Enter 'Y' to define the copy, 'N'otherwise.

ANR2254E Command: The VOLUMENAMESparameter must be specified whenSCRATCH=NO is specified.

Explanation: The SCRATCH parameter is specified asNO for the command Command but theVOLUMENAMES parameter is not specified. Whenscratch volumes are not allowed, the VOLUMENAMESparameter must be specified to indicate the volumesthat can be used for the command.


User Response: Reissue the command and specify avalid VOLUMENAMES parameter.

ANR2255E Command: The VOLUMENAMESparameter must be specified.

Explanation: The VOLUMENAMES parameter mustbe specified to indicate the volumes that can be usedfor the command.




User Response: Reissue the command and specify avalid VOLUMENAMES parameter.

ANR2256E Command: The RETENTION parametermust be specified.

Explanation: The RETENTION parameter must bespecified to indicate the retention period to be used forthe command.


User Response: Reissue the command and specify avalid RETENTION parameter.

ANR2257E Command: Administrator administratorname is not authorized to issue thiscommand for node node name.

Explanation: The specified administrator has enteredthe indicated command, but this administrator does nothave the proper authority necessary to run thecommand for the indicated node. Note: This messagecan be issued as a result of the server optionREQSYSAUTHOUTFILE YES being in effect.

System Action: The server does not process thecommand for the indicated node. If multiple nodeswere specified on the command, the server maycontinue processing the command for the other nodes.

User Response: Examine previous messages for anyadditional information. Issue the command from aproperly authorized administrator ID, or contact thesystem administrator to have additional authoritygranted to the current administrator ID.

ANR2258E Command: Invalid summary retentionperiod - retention value.

Explanation: A SET SUMMARYRETENTIONcommand has been entered that specifies an invalidretention period.



ANR2259I Summary retention period set to numberof days days.

Explanation: The number of days that activity sumaryrecords are kept in the server database has been set tothe value indicated with the SETSUMMARYRETENTION command.



ANR2260I Recovery log volume volume namedefined.

Explanation: A DEFINE LOGVOLUME command hasdefined the recovery log volume indicated.



ANR2261I Recovery log volume copy volume namedefined.

Explanation: A DEFINE LOGCOPY command hasdefined the recovery log volume indicated.



ANR2262I Recovery log volume copy volume namedefined; synchronization process started(process ID process ID).

Explanation: A DEFINE LOGCOPY command hasadded the volume shown as a log copy volume. Theprocess whose ID is displayed copied data to the newvolume to synchronize it with existing volumes.



ANR2263I Recovery log volume volume namedeleted.

Explanation: A DELETE LOGVOLUME command hasremoved the recovery log volume indicated.



ANR2264I Delete process initiated for recovery logvolume volume name (process id processID).

Explanation: In response to a DELETE LOGVOLUMEcommand, the process with process ID shown has beenstarted to delete the volume.



ANR2265I Recovery log volume volume name variedonline.

Explanation: A VARY ONLINE command has put therecovery log volume indicated into an online state.





ANR2266I Vary online process initiated forrecovery log volume volume name(process ID process ID).

Explanation: In response to a VARY ONLINEcommand, the process with process ID shown has beenstarted to vary on the recovery log volume indicated.



ANR2267I Recovery log volume volume name variedoffline.

Explanation: A VARY OFFLINE command has put therecovery log volume indicated into an offline state.



ANR2268I Recovery log assigned capacity has beenextended.

Explanation: An EXTEND LOG command hasincreased the storage capacity of the recovery log.



ANR2269I Recovery log extension process initiated(process ID process ID).

Explanation: In response to an EXTEND LOGcommand, the process with the process ID shown hasbeen started to extend the recovery log.



ANR2270I Recovery log assigned capacity has beenreduced.

Explanation: A REDUCE LOG command hasdecreased the storage capacity of the recovery log.



ANR2271I Recovery log reduction process initiated(process ID process ID).

Explanation: In response to a REDUCE LOGcommand, the process with the process ID shown hasbeen started to reduce the recovery log.



ANR2272W Recovery log volume copy volume nameis larger than volume volume name bycount megabytes.

Explanation: A DEFINE LOGCOPY command hasdefined a recovery log copy volume whose size islarger than the volume it mirrors by the amountshown.

System Action: The excess capacity is ignored.


ANR2273W The recovery log volume copy to bedefined (volume name) is larger thanvolume volume name; use of the volumewill result in count megabytes ofunusable space.

Explanation: A DEFINE LOGCOPY command isattempting to define a recovery log copy volume whosesize is larger than the volume it mirrors by the amountshown. The excess capacity would not be used.


User Response: Enter 'Y' to define the copy or 'N' tostop the process.

ANR2274I Data Base Space trigger defined andenabled.

Explanation: The database space trigger has beendefined with a DEFINE SPACETRIGGER command.The percentage of utilization specified with theFULLPCT parameter is used to automatically expandthe database.



ANR2275I Data Base Space trigger defined, but isdisabled.

Explanation: A database space trigger has beendefined, but because the space expansion percentage iscurrently set to 0, the space trigger is disabled.


User Response: To activate the space trigger, use theUPDATE SPACETRIGGER command to set the spaceexpansion percentage to a value greater than 0.

ANR2276I Data Base Space trigger updated andenabled.

Explanation: An UPDATE SPACETRIGGER commandhas successfully completed for the data base spacetrigger. The updated parameters specified on thecommand are used to automatically trigger spaceexpansion for the database.





ANR2277I Database Space trigger updated, butdisabled.

Explanation: An UPDATE SPACETRIGGER commandhas successfully completed for the data base spacetrigger. However, the space expansion percentage iscurrently set to 0, which disables the space trigger.


User Response: To activate the space trigger, use theUPDATE SPACETRIGGER command with theSPACEexpansion parameter to set a value greater thanzero.

ANR2278I Database Space trigger deleted.

Explanation: A DELETE SPACETRIGGER commandhas successfully completed for the database spacetrigger. Space expansions are no longer triggeredautomatically for the database.



ANR2279I Recovery Log Space trigger defined andenabled.

Explanation: The recovery log space trigger has beendefined with a DEFINE SPACETRIGGER command.The percentage of utilization specified with theFULLPCT parameter is used to automatically expandthe recovery log.



ANR2280I Full database backup started as processprocess ID.

Explanation: A background process was started tobackup the contents of the database. The full databasebackup process was assigned the process ID shown.

System Action: The database backup process startsand server operation continues.

User Response: The administrator may query thestatus of the database backup process by using theQUERY PROCESS command, or cancel the process withthe CANCEL PROCESS command.

ANR2281I Incremental database backup started asprocess process ID.

Explanation: A background process was started tobackup the contents of the database. The incrementaldatabase backup process was assigned the process IDshown.


User Response: The administrator may query thestatus of the database backup process by using theQUERY PROCESS command, or cancel the process withthe CANCEL PROCESS command.

ANR2282I Database backup trigger defined andenabled.

Explanation: A database backup trigger has beendefined with a DEFINE DBBACKUPTRIGGERcommand. The percentage of recovery log utilizationspecified with the LOGFULLPCT parameter is used toautomatically trigger database backups.



ANR2283I Database backup trigger defined, but isdisabled.

Explanation: A database backup trigger has beendefined, but because the recovery log mode is currentlyset to NORMAL, the database backup trigger isdisabled. Database backups can only be triggered whenthe log mode is set to ROLLFORWARD with a SETLOGMODE command.


User Response: To activate the database backuptrigger, use the SET LOGMODE ROLLFORWARDcommand.

ANR2284I Database backup trigger updated andenabled.

Explanation: An UPDATE DBBACKUPTRIGGERcommand has successfully completed. The updatedparameters specified on the command are used toautomatically trigger database backups.



ANR2285I Database backup trigger updated, butdisabled.

Explanation: An UPDATE DBBACKUPTRIGGERcommand has successfully completed, but because therecovery log mode is currently set to NORMAL, thedatabase backup trigger is disabled. Database backupscan only be triggered when the log mode is set toROLLFORWARD with a SET LOGMODE command.


User Response: To activate the database backuptrigger, use the SET LOGMODE ROLLFORWARDcommand.



ANR2286I Database backup trigger deleted.

Explanation: A DELETE DBBACKUPTRIGGERcommand has successfully completed. Databasebackups are no longer triggered automatically byrecovery log utilization.



ANR2287I Snapshot database backup started asprocess process ID.

Explanation: A background process was started tobackup the contents of the database. The snapshotdatabase backup process was assigned the process idshown.


User Response: The administrator may query thestarted process by using the QUERY PROCESScommand, or may cancel the process using theCANCEL PROCESS command.

ANR2288I Subfile set to state.

Explanation: The SET SUBFILE command has beenused to specify whether this server will allow clients toback up subfiles. If a value of CLIENT is specified,clients are given the option of backing up subfiles. If avalue of NO is specified, clients are not allowed to backup subfiles.



ANR2289I Administrative userid admininstratorname defined for authority over nodenode name has not been removed.

Explanation: The specified administrator was notremoved.



ANR2290W Changing the log mode to NORMALwill prevent roll-forward recovery.

Explanation: The system has determined thatchanging the recovery log mode from ROLLFORWARDto NORMAL mode will cause the log records beingkept for ROLLFORWARD and single database volumerestore processing to be discarded. Without these logrecords, only point-in-time database restores can beperformed.


User Response: Enter 'Y' to change the LOGMODE,'N' otherwise.

ANR2291W Changing the log mode to NORMALwill disable the database backup trigger.

Explanation: Changing the recovery log mode fromROLLFORWARD to NORMAL disables the settingspecified in the DEFINE DBBACKUPTRIGGERcommand. Database backups can only be triggeredwhen the recovery log mode is set to ROLLFORWARDwith the SET LOGMODE command.


User Response: Enter 'Y' to change the log mode, 'N'otherwise. Responding 'Y' does not delete the DEFINEDBBACKUPTRIGGER settings.

ANR2292W Changing the log mode toROLLFORWARD will enable thedatabase backup trigger.

Explanation: Changing the recovery log mode fromNORMAL to ROLLFORWARD causes a previouslyissued DEFINE DBBACKUPTRIGGER command tobecome effective, and immediately start a full databasebackup. Database backups can only be triggered whenthe recovery log mode is set to ROLLFORWARD with aSET LOGMODE command.


User Response: Enter 'Y' to change the log mode, 'N'otherwise.

ANR2293I Only point-in-time database recovery isnow possible.

Explanation: An administrator has changed therecovery log mode from ROLLFORWARD to NORMALwith a SET LOGMODE command. Only point-in-timedatabase restores can be performed. ROLLFORWARDdatabase restores and individual database volumerestores are not possible.



ANR2294I Log mode set to log mode.

Explanation: The mode for saving recovery logrecords has been set as indicated by the SETLOGMODE command. When set to NORMAL, onlythose log records needed to resume database processingif a system failure occurs are saved. When set toROLLFORWARD, all log records created since the lastdatabase backup are saved. ROLLFORWARD modealso enables the database backup trigger to be used toautomatically start database backups based on the



percentage of recovery log utilization.



ANR2295I Log mode set to ROLLFORWARD;database backup trigger enabled.

Explanation: The mode for saving recovery logrecords has been set to ROLLFORWARD, and apreviously defined database backup trigger has beenenabled. All log records created since the last databasebackup are saved in this mode. The database backuptrigger will automatically start a database backup basedon the percentage of recovery log utilization.



ANR2296I Log mode set to NORMAL; databasebackup trigger disabled.

Explanation: The mode for saving recovery logrecords has been set to NORMAL mode, and thedefined database backup trigger is disabled. Only thoselog records needed to resume database processing if asystem failure occurs are saved in this mode. Databasebackups can only be started using the BACKUP DBcommand.



ANR2297I Command: Optionset optionset name,option option name, sequence number oldsequence number, has been changed tonew sequence number.

Explanation: The requested option sequence numberhas been updated in response to an UPDATECLIENTOPT command.



ANR2298I Command: Optionset optionset name,option option name, sequence number oldsequence number, is not updated.

Explanation: The requested option sequence numberis not updated in response to an UPDATE CLIENTOPTcommand.


User Response: Reissue the UPDATE CLIENTOPTcommand with a valid old sequence number.

ANR2299I Password expiration period foradministrator administrator name set tonumber of days days.

Explanation: The number of days that theadministrator’s password can be used before it must bechanged has been set to the value indicated with theSET PASSEXP command.



ANR2300E Could not open ″file spec″ the server helpfile.

Explanation: The named help file could not beaccessed.

System Action: The requested help text is notdisplayed.

User Response: Contact the system administrator.

ANR2301E Errors were encountered while settingup the index to the help text.

Explanation: Either insufficient memory or a help fileread failure has occurred during setup of the helpindex.

System Action: The server does not display therequested help text.


ANR2302E The argument operand is not valid forthe HELP command.

Explanation: The argument supplied on the HELPcommand is not an integer or the name of a command.

System Action: The server does not process the HELPcommand.

User Response: Issue the HELP command with nooperands and select from the numbered list displayedin response.

ANR2303E There is no help section numberedsection number.

Explanation: The numeric operand supplied on theHELP command is either less than 1 or greater than thehighest-numbered entry in the help index.


User Response: Issue the HELP command with nooperands and select from the numbered list (helpindex) displayed in response.



ANR2304E I/O error reading ″help file name″ the fileof help text.

Explanation: An error is detected when reading helptext from the named file.

System Action: The server ends display of the helptext.


ANR2305E No such command/subcommand:command subcommand.

Explanation: The operands you entered for the HELPcommand do not match any named entry into the fileof help text.


User Response: Check your input for a misspelledcommand or subcommand name.

ANR2306E No help text could be found for thiscommand/subcommand: command.

Explanation: The operands you entered for the HELPcommand, although valid command/subcommandnames, do not match any named entry into the file ofhelp text.



ANR2307E No help text could be found for thismessage: message ID.

Explanation: The message ID you entered for the helpcommand does not match any message entry in the fileof help text.

System Action: The help command is not processed.


ANR2308W Audit Volume marking damaged file asdamaged on volume volume name: Nodenode name, Type file type, File spacefilespace name, fsId filespace id, File Namefile name is number version of totalversions versions.

Explanation: As the result of an AUDIT VOLUMEcommand that specified FIX=YES for the volumeshown, the file whose information is displayed ismarked as damaged in the server. The file is marked asdamaged because it can be recovered from a copyknown to exist in a COPY storage pool. If this filebelongs to an aggregate, the entire aggregate is markeddamaged, and this message will be issued for every filein the aggregate. The version numbers for the file are

numbered from most recent (1) to least recent (n, wheren is the total number of versions.

System Action: The file is marked as damaged in theserver database.

User Response: To recover the damaged file use theRESTORE STGPOOL or RESTORE VOLUME command.

ANR2309E The server log mode is currently set toroll-forward. You may run out of logspace when auditing the server in thismode. Specify LOGMODE=NORMALto set the log mode to NORMAL for theaudit operation, orLOGMODE=ROLLFORWARD to forcethe audit operation with the logmodeset to roll-forward.

Explanation: An AUDITDB operation was specifiedand the server log mode is set to roll-forward mode.When in roll-forward mode, the server may run out oflog space during the AUDITDB operation, requiring anemergency extend of the recovery log to re-start theserver. The recommended log mode for executing anAUDITDB operation is NORMAL.

System Action: The AUDITDB operation fails

User Response: To force the server log mode toNORMAL for the AUDITDB operation, specifyLOGMODE=NORMAL on the AUDITDB command.Specify LOGMODE=ROLLFORWARD on theAUDITDB command to allow the audit to run with aroll-forward log mode setting.

ANR2310W This command will compare allinventory references to volume volumename with the actual data stored on thevolume and will report anydiscrepancies; the data will beinaccessible to users until the operationcompletes.

Explanation: During the execution of an AUDITVOLUME command, any data the volume namedwould be unavailable to users.





ANR2311W This command will discard anyinventory references to volume volumename associated with missing orinconsistent stored data, therebyrendering the data unrecoverable; thevalid data on the volume will beinaccessible to users until the operationcompletes.

Explanation: During the execution of an AUDITVOLUME command, any data the volume namedwould be unavailable to users. After the command hasended, any inconsistent data found will be discarded.



ANR2312I Audit Volume (Repair) process startedfor volume volume name (process IDprocess ID).

Explanation: As the result of an AUDIT VOLUMEcommand that specified FIX=YES for the volumeshown, the process whose ID is displayed has begunauditing the volume.

System Action: The volume is audited andinconsistent data is discarded.


ANR2313I Audit Volume (Inspect Only) processstarted for volume volume name (processID process ID).

Explanation: As the result of an AUDIT VOLUMEcommand that specified FIX=NO for the volumeshown, the process whose ID is displayed has begunauditing the volume.

System Action: The volume is audited andinconsistent data is displayed.


ANR2314I Audit volume process ended for volumevolume name; file count files inspected, filecount damaged files deleted, file countdamaged files marked as damaged.

Explanation: The AUDIT VOLUME commandspecifying FIX=YES for the volume shown has ended.The number of files audited and the number ofinconsistent files deleted or marked as damaged aredisplayed. The number of files marked as damagedincludes all files belonging to aggregates that weremarked damaged during the audit. Files are marked asdamaged in primary storage pools and not deletedwhen backup copies for the files are known to exist inCOPY storage pools.


User Response: To recover files that have beenmarked as damaged on the volume, use the RESTORESTGPOOL or RESTORE volume command.

ANR2315I Audit volume process ended for volumevolume name; file count files inspected, filecount damaged files found and markedas damaged.

Explanation: The AUDIT VOLUME commandspecifying FIX=NO for the volume shown has ended.The number of files audited and the number ofinconsistent files found are displayed. The number offiles marked damaged includes all files belonging toaggregates that were marked damaged during theaudit. Inconsistent files are marked as damaged in thedatabase and can be recovered by using the RESTORESTGPOOL or RESTORE VOLUME command if copiesof the files reside in a COPY storage pool. AnotherAUDIT VOLUME command may be able to access thefiles and reset the damaged indicator in the database ifthe audit volume process cannot access the files due tohardware problems (for example, dirty tape heads).


User Response: If you suspect that files wereinaccessible because of hardware problems such asdirty tape heads, correct the hardware problem andreissue the AUDIT VOLUME FIX=NO command forthis volume. To remove damaged file references, issuethe AUDIT VOLUME command and specify FIX=YES.

ANR2316W Audit Volume deleting damaged file onvolume volume name: Node node name,Type file type, File space filespace name,fsId filespace id, File Name file name isnumber version of total versions versions.

Explanation: As the result of an AUDIT VOLUMEcommand that specified FIX=YES for the volumeshown, the file whose information is displayed isdeleted from the server. The version numbers for thefile are numbered from most recent (1) to least recent(n, where n is the total number of versions.

System Action: The file is deleted.


ANR2317W Audit Volume found damaged file onvolume volume name: Node node name,Type file type, File space filespace name,fsId filespace id, File name file name isnumber version of total versions versions.

Explanation: As the result of an AUDIT VOLUMEcommand that specified FIX=NO for the volumeshown, the file whose information is displayed is foundto be in error and not accessible. If this file belongs toan aggregate, the entire aggregate is marked damaged,



and this message will be issued for every file in theaggregate. The version numbers for the file arenumbered from most recent (1) to least recent (n, wheren is the total number of versions.



ANR2318W Audit volume process terminated forvolume volume name - process canceled.

Explanation: During processing of an AUDITVOLUME command for the volume shown, the processperforming the audit was canceled.

System Action: The AUDIT VOLUME command isended.


ANR2319W Audit volume process terminated forvolume volume name - error readingdevice.

Explanation: During processing of an AUDITVOLUME command for the volume shown, anunrecoverable read error occurred on the volume.


User Response: Attempt to correct the cause of theread error, and reissue the command.

ANR2320W Audit volume process terminated forvolume volume name - data transferinterrupted.

Explanation: During processing of an AUDITVOLUME command for the volume shown, a datatransfer operation has been interrupted and cannot becontinued.


User Response: If possible, determine and correct thecause of the interruption, and reissue the command.

ANR2321W Audit volume process terminated forvolume volume name - storage mediainaccessible.

Explanation: During processing of an AUDITVOLUME command for the volume shown, a requiredvolume cannot be mounted.



ANR2322W Audit volume process terminated forvolume volume name - sufficient recoverylog space is not available.

Explanation: During processing of an AUDITVOLUME command for the volume shown, the serverdoes not have sufficient recovery log space to continue.


User Response: If necessary, make more recovery logspace available to the server.

ANR2323W Audit volume process terminated forvolume volume name - sufficient databasespace is not available.

Explanation: During processing of an AUDITVOLUME command for the volume shown, the serverdoes not have sufficient database space to continue.


User Response: If necessary, make more databasespace available to the server.

ANR2324W Audit volume process terminated forvolume volume name - thread resourcenot available.

Explanation: During processing of an AUDITVOLUME command for the volume shown, the servercannot start a thread for the audit process.


User Response: Reissue the AUDIT VOLUMEcommand. If the error persists, it may indicate ashortage of server memory.

ANR2325W Audit volume process terminated forvolume volume name - sufficient memoryis not available.

Explanation: During processing of an AUDITVOLUME command for the volume shown, the serverdoes not have enough memory available to completethe command.


User Response: If necessary make more memoryavailable to the server.

ANR2326W Audit volume process terminated forvolume volume name - lock conflictdetected.

Explanation: During processing of an AUDITVOLUME command for the volume shown, the server



cannot obtain a required lock.


User Response: Reissue the command.

ANR2327W Audit volume process terminated forvolume volume name - internal servererror detected.

Explanation: During processing of an AUDITVOLUME command for the volume shown, an internalserver error occurs.



ANR2332W Object object.ID deleted by anotherprocess during execution of an AUDITVOLUME command for volume volumename.

Explanation: During processing of an AUDITVOLUME command, a data storage object was deletedfrom the volume that was being audited. The AUDITVOLUME process was unable to locate this object onthe specified volume. Normally, this action is notconsidered an error condition, because the object wasprobably deleted by a process such as a DELETEFILESPACE command.

System Action: Processing of the AUDIT VOLUMEcommand continues.

User Response: Check the activity log to verify thatsome process (such as a DELETE FILESPACEcommand) was in progress during the AUDITVOLUME command that would account for the deletedobject. If no such process can be identified, contact yourservice representative.

ANR2333W Missing or incorrect informationdetected by AUDIT VOLUME forvolume volume name.

Explanation: An AUDIT VOLUME command detectsmissing or incorrect information for the specifiedvolume.

System Action: Audit processing continues.

User Response: Reissue the audit command withFIX=YES so that the information can be created orcorrected.

ANR2334W Missing or incorrect informationdetected by AUDIT VOLUME forvolume volume name - information willbe created or corrected.

Explanation: An AUDIT VOLUME process detectsmissing or incorrect information for the specifiedvolume. Because FIX=YES has been specified for theaudit command, the information is created or corrected.



ANR2335W Audit Volume has encountered an I/Oerror for volume volume name whileattempting to read: Node node name,Type file type, Filespace filespace name,fsId filespace id, File Name file name.

Explanation: The AUDIT VOLUME processencountered an I/O error for the specified volumewhile attempting to read the specified file. If this filebelongs to an aggregate, the entire aggregate is markeddamaged, and this message will be issued for every filein the aggregate.


User Response: Identify and resolve the I/O error forthe volume if possible. Verify that the volume’s deviceis functioning properly and that the volume is usable.For example, if the volume is a tape volume, make surethe drive is clean or that the tape volume is usable bytesting it by using a different drive.

ANR2336W Audit Volume terminated for volumevolume name - insufficient number ofmount points available for removablemedia.

Explanation: During Audit Volume for the indicatedvolume, the server could not allocate sufficient mountpoints for the volume required.

System Action: Audit Volume stops.


ANR2339E Command: Object sets still exist for nodenode name.

Explanation: A REMOVE NODE command has beenentered for a node for which the server is still storingbackup sets. To remove a node, the node must not haveany files or backup sets stored on the server.


User Response: To remove the node, delete all backupsets from the server and reissue the command.



ANR2340E Command: Invalid storage pool name -storage pool name.

Explanation: The command indicated contains aninvalid storage pool name.


User Response: Reissue the command with a validstorage pool name.

ANR2341E Command: Missing next storage poolname.

Explanation: The command indicated requires astorage pool name, but none has been entered.


User Response: Reissue the command with a storagepool name.

ANR2342E Command: Storage pool descriptionexceeds maximum characters characters.

Explanation: The command indicated contains astorage pool description that exceeds the maximumlength allowed.


User Response: Reissue the command with a validstorage pool description.

ANR2343E Command: Invalid device class name -device class name.

Explanation: The command indicated contains aninvalid device class name.


User Response: Reissue the command with a validdevice class name.

ANR2344E Command: The ″option″ option is notvalid for device class device class name.

Explanation: The command indicated specifies anoption shown that is not valid for a storage pool thatbelongs to the device class shown.


User Response: Reissue the command with optionsappropriate to the device class.

ANR2345E Command: Invalid volume name - volumename.

Explanation: The command indicated contains aninvalid volume name.


User Response: Reissue the command with a validvolume name.

ANR2346E Command: Volume name ″volume name″ isnot valid for device class device classname.

Explanation: The command indicated specifies thename of a volume that cannot be used with the deviceclass shown.


User Response: Reissue the command with a validvolume name.

ANR2347E Command: Volume name ″volume name″ isambiguous; resolves to multiple definedvolume names.

Explanation: The command shown was entered with avolume name pattern that matches more than onevolume. The command can only process a singlevolume.


User Response: Reissue the command with a morespecific volume name.

ANR2348E Command: The ″option″ option is notvalid for a volume assigned to a primarystorage pool.

Explanation: The command indicated specifies anoption that is not valid for a volume in a primarystorage pool.


User Response: Reissue the command with validoptions for a volume in a primary storage pool.

ANR2349E Command: The ″option″ option is notvalid for a volume assigned to a copystorage pool.

Explanation: The command indicated specifies anoption that is not valid for a volume in a copy storagepool.




User Response: Reissue the command with validoptions for a volume in a copy storage pool.

ANR2350E Command: Device class device class nameis already defined.

Explanation: The command indicated has attemptedto define a device class that already exists.



ANR2351E Command: Device class device class nameis not defined.

Explanation: The command indicated references adevice class that does not exist.



ANR2352E Command: Device class device class namemay not be deleted.

Explanation: A DELETE DEVCLASS commandspecifies the class name DISK, which is asystem-defined device class and may not be deleted.



ANR2353E Command: Device class device class namemay not be updated.

Explanation: An UPDATE DEVCLASS commandspecifies the class name DISK, which is asystem-defined device class and may not be changed.



ANR2354E Command: Device class device class nameis still referenced by one or morestorage pools, or database backup orexport volumes.

Explanation: The DELETE DEVCLASS command hasattempted to delete a device class that has storagepools assigned to it, or is referenced by databasebackup or export volumes.


User Response: Issue Q DEVCLASS to view thestorage pool reference count, Q STGPOOL to determinewhich pool references the device class, and Q VOLHIST

to locate database backup or export volume references.

ANR2355E Command: Required parameter ismissing - missing parameter.

Explanation: The specified server command has beenentered without the required parameter. The requiredparameter is shown.



ANR2356E Command: Incompatible parametersspecified - first parameter, secondparameter.

Explanation: The specified server command has beenentered with mutually exclusive parameters. The twoparameters are listed.



ANR2357E Command: The DISK device class is notsupported for copy storage pools.

Explanation: An attempt is made to define a copystorage pool using a device of DISK. Copy storagepools can only be assigned to a sequential device class.


User Response: Reissue the command specifying asequential device class.

ANR2358E Command: Device class device class nameis still referenced in the volume historyfile.

Explanation: The DELETE DEVCLASS command hasattempted to delete a device class that is associate withentries in the volume history file. These entries are forvolumes that contain database backup or export data.


User Response: Use the DELETE VOLHIST commandto remove that entries before deleting the device class.

ANR2359E Command: Volume name ″volume name″must be specified with a DISKSTGPOOL.

Explanation: The command indicated specifies thename of a volume that must be specified with a diskstorage pool.




User Response: Reissue the command with a validvolume name and storage pool.

ANR2360E Command: Device class device class namemay not be used for database backup.

Explanation: The command specifies the DISK deviceclass, which cannot be used for database backup,backup trigger, or restore operations.


User Response: Reissue the command with a validdevice class.

ANR2361E Command: A full database backup isrequired.

Explanation: A BACKUP DB command specified anincremental backup, but a full backup is required.


User Response: Reissue the command specifying afull backup.

ANR2362E Command: Database backup is notcurrently possible - compressed logrecords exist in the current transactioncheckpoint.

Explanation: A BACKUP DB command was issuedbut a database backup cannot be started. Logcompression has recently taken place, and thecompressed log records are still part of the currenttransaction checkpoint. After these log records are nolonger part of the current checkpoint a backup can takeplace.


User Response: Reissue the command at a later time.

ANR2363E Command: One of the followingparameter must be supplied but ismissing - missing parameter, missingparameter, missing parameter, missingparameter.

Explanation: The specified server command has beenentered without one of the mutually exclusive requiredparameters. One of the parameters from the list mustbe specified.



ANR2364E Command: Missing reclaim-storage poolname.

Explanation: The command indicated requires astorage pool name, but none has been entered.


User Response: Reissue the command with a storagepool name.

ANR2365I Backupset backup set name for node nodename has been deleted.

Explanation: The backup set has been deleted.

System Action: The server has deleted the backupset.


ANR2366I Backupset backup set name for node nodename would have been deleted.

Explanation: The backup set would have been deletedas the result of a DELETE BACKUPSET command, butthe PREVIEW=YES parameter was specified.


User Response: If the backup set is to be deleted,reissue the command without specifyingPREVIEW=YES.

ANR2367I Retention period for backupset backupset name for node node name has beenupdated.

Explanation: The backup set’s retention period hasbeen updated.

System Action: The server has updated thebackupset’s retention period.


ANR2368I Retention period for backupset backupset name for node node name would havebeen updated.

Explanation: The backup set’s retention period wouldhave been updated as the result of an UPDATEBACKUPSET command, but the PREVIEW=YESparameter was specified.


User Response: If the backup set is to be updated,reissue the command without specifyingPREVIEW=YES.



ANR2369I Database backup volume and recoveryplan file expiration starting underprocess process ID.

Explanation: The server has started expirationprocessing to remove expired database backup volumesand recovery plan files created on a remote server. Thismessage is issued only if DRM is licensed on theserver. The DB backup volumes expired is based on thevalue specified on the SETDRMDBBACKUPEXPIREDAYS. The recovery plan filesexpired is based on the value specified on the SETDRMRPFEXPIREDAYS. Server inventory expirationprocessing deletes the DB backup volumes andrecovery plan files only if the volumes or plan files arecreated on the server to server virtual volumes.

System Action: Server operation continues. Theexpiration process is cancellable.


ANR2370E Command: Database backup trigger isalready defined.

Explanation: The database backup trigger cannot bedefined because it is already defined.


User Response: Use the UPDATEDBBACKUPTRIGGER command to modify thedatabase backup trigger parameters.

ANR2371E Command: Database backup trigger isnot defined.

Explanation: The database backup trigger cannot beupdated or deleted because it is not currently defined.



ANR2372E Command: Database Space trigger isalready defined.

Explanation: The database space trigger cannot bedefined because it is already defined.


User Response: Use the UPDATE SPACETRIGGERcommand to modify the indicated space triggerparameters.

ANR2373E Command: Database backup trigger isnot defined.

Explanation: The database space trigger cannot beupdated or deleted because it is not currently defined.



ANR2374E Command: Recovery Log Space trigger isalready defined.

Explanation: The recovery log space trigger cannot bedefined because it is already defined.


User Response: Use the UPDATE SPACETRIGGERcommand to modify the indicated space triggerparameters.

ANR2375E Command: Recovery Log trigger is notdefined.

Explanation: The recovery log space trigger cannot beupdated or deleted because it is not currently defined.



ANR2376I Recovery Log Space trigger defined, butis disabled.

Explanation: A recovery log space trigger has beendefined, but because the space expansion percentage iscurrently set to 0, the space trigger is disabled.


User Response: To activate the space trigger, use theUPDATE SPACETRIGGER command to set the spaceexpansion percentage to a value greater than 0.

ANR2377I Recovery Log Space trigger updated andenabled.

Explanation: An UPDATE SPACETRIGGER commandhas successfully completed for the recovery log spacetrigger. The updated parameters specified on thecommand are used to automatically trigger spaceexpansion for the database.





ANR2378I Recovery Log Space trigger updated, butdisabled.

Explanation: An UPDATE SPACETRIGGER commandhas successfully completed for the recovery log spacetrigger. However, the space expansion percentage iscurrently set to 0, which disables the space trigger.


User Response: To activate the space trigger, use theUPDATE SPACETRIGGER command with theSPACEexpansion parameter to set a value greater thanzero.

ANR2379I Recovery Log Space trigger deleted.

Explanation: A DELETE SPACETRIGGER commandhas successfully completed for the recovery log spacetrigger. Space expansions are no longer triggeredautomatically for the recovery log.



ANR2380E Command: Storage pool storage pool nameis not defined.

Explanation: The command indicated specifies thename of a nonexistent storage pool.


User Response: Reissue the command with a validstorage pool name.

ANR2381E Command: Storage pool storage pool nameis already defined.

Explanation: A DEFINE STGPOOL command specifiesthe name of a storage pool that already exists.



ANR2382E Command: Storage pool storage pool namestill contains at least one volume.

Explanation: A DELETE STGPOOL command specifiesa storage pool that has volumes assigned to it.


User Response: Delete the volume belonging to thestorage pool and reissue the command.

ANR2383E Command: Storage pool storage pool nameis currently in use by clients and/or datamanagement operations.

Explanation: The command indicated references astorage pool that is in use.


User Response: Reissue the command at a later time.

ANR2384E Command: Next or Reclaim storage poolstorage pool name introduces a cycle intothe storage pool chain.

Explanation: A DEFINE STGPOOL or UPDATESTGPOOL command specifies a next storage pool thateventually points to the pool being processed.


User Response: Reissue the command with a differentnext pool value.

ANR2385E Command: Storage pool storage pool nameis in use as the next or reclaim pool forone or more other storage pools.

Explanation: A DELETE STGPOOL command specifiesa pool that is the next pool or the reclaim pool forother storage pools.


User Response: If necessary, update other storagepools so that they do not reference the pool to bedeleted, and reissue the command.

ANR2386E Command: High migration thresholdmust be set greater than or equal to thelow migration threshold.

Explanation: A DEFINE or UPDATE STGPOOLcommand has attempted to set the storage pool lowmigration threshold (LOWMIG) parameter greater thanthe high migration threshold (HIGHMIG).


User Response: Reissue the command with a lowmigration threshold less than or equal to the highmigration threshold.

ANR2387E Command: Storage pool storage pool nameis not a primary pool.

Explanation: The command indicated specifies thename of a storage pool which is not a primary pool.The command syntax requires that a primary storagepool name be specified.




User Response: Reissue the command with a validprimary storage pool name.

ANR2388E Command: Storage pool storage pool nameis not a copy pool.

Explanation: The command indicated specifies thename of a storage pool which is not a copy pool. Thecommand syntax requires that a copy storage poolname be specified.


User Response: Reissue the command with a validcopy storage pool name.

ANR2389E Command: The ″option″ option is notvalid for a primary storage pool.

Explanation: The command indicated specifies anoption that is not valid for a primary storage pool.


User Response: Reissue the command with optionsappropriate for a primary storage pool.

ANR2390E Command: The ″option″ option is notvalid for a copy storage pool.

Explanation: The command indicated specifies anoption that is not valid for a copy storage pool.


User Response: Reissue the command with optionsappropriate for a copy storage pool.

ANR2391E Command: Server could not write deviceconfiguration information to file name.

Explanation: The BACKUP DEVCONFIG commanddoes not successfully complete because the servercannot write to the file name specified.


User Response: Make sure that the server has properauthority to write to the file indicated and thatsufficient space is available in the file system for thefile. On MVS, make sure that the data set has beenallocated and that the server has authority to write tothe data set.

ANR2392E Command: An internal error wasencountered in writing deviceconfiguration information to file name.

Explanation: The BACKUP DEVCONFIG commanddoes not successfully complete because the servercannot write to the file name specified.


User Response: Examine error messages on the serverconsole that may have been displayed prior to thismessage and correct any problems, if possible. Makesure that the server has proper authority to write to thefile indicated and that sufficient space is available inthe file system for the file. On MVS, make sure that thedata set has been allocated and that the server hasauthority to write to the data set.

ANR2393I Command: Server device configurationinformation was written to file name.

Explanation: This message is displayed in response tothe BACKUP DEVCONFIG command and indicatesthat device configuration information was successfullywritten to the file name indicated.

System Action: The server records deviceconfiguration information to the file name specified


ANR2394I Command: Server device configurationinformation was written to all deviceconfiguration files.

Explanation: This message is displayed in response tothe BACKUP DEVCONFIG command and indicatesthat device configuration information was successfullywritten to all files that were specified in the serveroptions file.

System Action: The server records deviceconfiguration information to the device configurationfiles.


ANR2395I Command: Device configuration fileshave NOT been defined for automaticrecording - specify a file name fordevice configuration information.

Explanation: This message is displayed in response tothe BACKUP DEVCONFIG command and indicatesthat device configuration information cannot be writtenbecause no files were specified in the options file.

System Action: The device configuration informationis not written. Server operation continues.

User Response: Reissue the BACKUP DEVCONFIGcommand and specify the name of a file to which you



would like to have device configuration informationrecorded. If desired, you may configure files thatshould be automatically updated with theDEVCONFIG option and restart the server.

ANR2396E Command: An I/O error was encounteredin writing device configurationinformation to one or more of thedefined device configuration files.

Explanation: The BACKUP DEVCONFIG commanddoes not complete successfully because the servercannot write to one or more of the defined deviceconfiguration files.



ANR2397E Command: An internal server error wasencountered in writing deviceconfiguration information to one ormore of the defined deviceconfiguration files.

Explanation: The BACKUP DEVCONFIG commanddoes not complete successfully because the servercannot write to one or more of the defined deviceconfiguration files.


User Response: Examine error messages on the serverconsole that may have been displayed prior to thismessage and correct any problems, if possible. Contactyour service representative if you are unable to resolvethe problem.

ANR2398E Command: The device configuration filecontains a statement with invalidsyntax.

Explanation: While processing the deviceconfiguration information, an invalid statement hasbeen encountered.

System Action: The server ends the operation beingperformed.

User Response: Examine error messages on the serverconsole that may have been displayed prior to thismessage and correct any problems if you haveconstructed the device configuration file manually.Make sure the statements are in the proper order. Ifyou let the server construct the device configuration file

automatically, restart the server, refresh the deviceconfiguration file by issuing the BACKUP DEVCONFIGcommand, and reissue the operation. If the problempersists, contact your service representative.

ANR2399E Command: Storage pool storage pool nameis not a sequential pool.

Explanation: The command indicated specifies thename of a storage pool which is not a sequential pool.All storage pools are either fixed disk or sequentialarchival. All tape devices, as well as optical and filedevice classes, are sequential.


User Response: Reissue the command with a validsequential storage pool name.

ANR2400E Command: Volume volume name is alreadydefined in a storage pool or has beenused previously to store export, databasedump, or database backup information.

Explanation: The command indicated specifies thename of a storage pool volume that already exists orhas been used to store server export, database dump,or database backup information as recorded in theserver volume history file.


User Response: Specify a volume that is not in use, isnot defined in a storage pool, and which has not beenpreviously used for an export, a database dump, ordatabase backup operation as recorded in the servervolume history information. Use the QUERY VOLUMEcommand to display the names of volumes that aredefined to server storage pools. Use the QUERYVOLHISTORY command to display the names ofvolumes that have been used for export, a databasedump, or database backup operations.

ANR2401E Command: Volume volume name is notdefined in a storage pool.

Explanation: The command indicated specifies thename of a storage pool volume that does not exist.



ANR2402E Command: Volume volume name is alreadyonline.

Explanation: A VARY ONLINE command specifies thename of a volume that is already online.





ANR2403E Command: Volume volume name is notonline.

Explanation: The command indicated specifies thename of a volume that is not online.



ANR2404E Command: Volume volume name is notavailable.

Explanation: The command indicated has attemptedto access a volume that cannot be found.


User Response: Check the spelling of the volumename to ensure it is correct. If the volume does notexist, preallocate it with the appropriate mechanism forthe operating system on which the server is running.

ANR2405E Command: Volume volume name iscurrently in use by clients and/or datamanagement operations.

Explanation: The command indicated specifies thename of a data storage volume that is currently in use.



ANR2406E Command: Volume volume name stillcontains data.

Explanation: The indicated command tries to delete adata storage volume that contains data.



ANR2407E Command: Maximum number ofmirrored copies exceeded.

Explanation: A DEFINE LOGCOPY or DEFINEDBCOPY command has attempted to add a mirrorvolume, but the maximum number of mirrors for thetarget volume already exists.



ANR2408E Command: Capacity of volume volumename must be at least as large ascapacity of volume volume name.

Explanation: A DEFINE LOGCOPY or DEFINEDBCOPY command has attempted to add a mirrorvolume, but the size of the volume to be added is lessthan the size of the target volume.


User Response: Use a larger mirror volume.

ANR2409E Command: Capacity of volume volumename must be at least 5 megabytes.

Explanation: A define command for a database or logvolume or copy has specified a volume that is toosmall to be used by the server for a database or logvolume. The minimum size for one of these volumes is5 megabytes.


User Response: Reissue the command and specify avolume that is at least 5 megabytes in size.

ANR2410E Command: Unable to access volumevolume name - access mode is set to″unavailable″.

Explanation: The command shown specifies thevolume whose name is displayed, but the volumecannot be accessed because its status is unavailable.


User Response: If necessary, reset the status of thevolume and reissue the command.

ANR2411E Command: Unable to access associatedvolume volume name - access mode is setto ″unavailable″.

Explanation: The command shown would requireaccess to the volume whose name is displayed (becausedata from the volume specified in the command spansinto this volume); the volume shown cannot beaccessed because its status is unavailable.





ANR2412E Command: Audit operation already inprogress for volume volume name.

Explanation: The command shown specifies thevolume whose name is displayed, but that volume iscurrently in use by an audit volume operation.


User Response: Reissue the command after the auditvolume operation ends.

ANR2413E Command: Audit operation already inprogress for associated volume volumename.

Explanation: The command shown would requireaccess to the volume whose name is displayed (becausedata from the volume specified in the command spansinto this volume); the volume shown cannot beaccessed because it is in use by an audit volumeoperation.


User Response: Reissue the command after the auditvolume operation ends.

ANR2414E Command: Deletion operation already inprogress for volume volume name.

Explanation: The command shown specifies thevolume whose name is displayed, but that volume iscurrently in use by a delete volume operation.


User Response: Reissue the command after the deletevolume operation ends.

ANR2415E Command: Deletion operation already inprogress for associated volume volumename.

Explanation: The command shown would requireaccess to the volume whose name is displayed (becausedata from the volume specified in the command spansinto this volume); the volume shown cannot beaccessed because it is in use by a delete volumeoperation.


User Response: Reissue the command after the deletevolume operation ends.

ANR2416E Command: Move Data operation alreadyin progress for volume volume name.

Explanation: The command shown specifies thevolume whose name is displayed, but that volume iscurrently in use by a move data operation.


User Response: Reissue the command after the movedata process ends.

ANR2417E Command: Move Data operation alreadyin progress for associated volume volumename.

Explanation: The command shown would requireaccess to the volume whose name is displayed (becausedata from the volume specified in the command spansinto this volume); the volume shown cannot beaccessed because it is in use by a move data operation.


User Response: Reissue the command after the movedata operation ends.

ANR2418E Command: Migration operation alreadyin progress for volume volume name.

Explanation: The command shown specifies thevolume whose name is displayed, but that volume iscurrently in use by a migration operation.


User Response: Reissue the command after themigration ends.

ANR2419E Command: Migration operation alreadyin progress for associated volume volumename.

Explanation: The command shown would requireaccess to the volume whose name is displayed (becausedata from the volume specified in the command spansinto this volume); the volume shown cannot beaccessed because it is in use by a migration operation.


User Response: Reissue the command after themigration ends.

ANR2420E Command: Space reclamation operationalready in progress for volume volumename.

Explanation: The command shown specifies thevolume whose name is displayed, but that volume is



currently in use by a reclamation operation.


User Response: Reissue the command after thereclamation ends.

ANR2421E Command: Space reclamation operationalready in progress for associatedvolume volume name.

Explanation: The command shown would requireaccess to the volume whose name is displayed (becausedata from the volume specified in the command spansinto this volume); the volume shown cannot beaccessed because it is in use by a reclamation operation.


User Response: Reissue the command after thereclamation ends.

ANR2422E Command: Volume volume name is not adefined disk volume.

Explanation: The command shown specifies a volumename that does not match any known disk volume.


User Response: Reissue the command with the correctvolume name.

ANR2423E Command: Volume volume name is stillonline.

Explanation: An UPDATE VOLUME commandspecifies access=unavailable for a disk volume that isstill online.


User Response: Issue the VARY OFFLINE command,and reissue the UPDATE VOLUME command.

ANR2424E Command: Unable to access volumevolume name - access mode is set to″destroyed″.

Explanation: The command shown specifies thevolume whose name is displayed, but the volumecannot be accessed because its status is destroyed.



ANR2425E Command: Unable to access volumevolume name - access mode is set to″offsite″.

Explanation: The command shown specifies thevolume whose name is displayed, but the volumecannot be accessed because its status is offsite.



ANR2426I Backupset backup set name defined fornode node name.

Explanation: The backup set has been defined for theindicated node.

System Action: The server has defined the backupset.


ANR2427E Backupset backup set name for node nodename was not deleted. Device class deviceclass name was not found.

Explanation: The specified backup set was not deletedbecause the device class used to generate it was notfound.

System Action: The backup set is not deleted.

User Response: If the device class was inadvertentlydeleted, redefine it, then delete the backup set again.

ANR2428E Backupset backup set name for node nodename has not been deleted due to errorerror code.

Explanation: The backup set has not been deleted.

System Action: The server has not deleted thebackupset.

User Response: Check related error messages.

ANR2429E Command: Maximum database capacityexceeded.

Explanation: Do not allocate any volume that wouldcause the database to exceed 500GB. A subsequentDEFINE DBVOLUME command for that volume wouldfail.





ANR2430E Command: Volume volume name is alreadydefined as a database volume.

Explanation: A DEFINE DBVOLUME commandspecifies the name of a database volume that alreadyexists.



ANR2431E Command: Volume volume name is not adefined database volume.

Explanation: A DELETE DBVOLUME commandspecifies the name of a database volume that does notexist.



ANR2432E Command: Maximum number ofdatabase volumes exceeded.

Explanation: A DEFINE DBVOLUME command hasattempted to add more database volumes than theserver can manage.



ANR2433E Command: A database define, delete,extend, reduce, or backup operation isalready in progress.

Explanation: The specified command has been enteredwhile a command that is modifying or backing up thedatabase is already active.


User Response: Wait for other activity to end, andreissue the command.

ANR2434E Command: Insufficient space on otherdatabase volumes to delete volumevolume name.

Explanation: A DELETE DBVOLUME command hasbeen entered, but the data on the volume to be deletedcannot be copied to other volumes due to insufficientfree space.


User Response: Make more database space available,and reissue the command.

ANR2435E Command: Unable to delete databasevolume volume name - mirrored copiesnot synchronized.

Explanation: A DELETE DBVOLUME command hasbeen entered, but mirrors of the volume to be deletedare not up to date.


User Response: Try the command at a later time (afterdatabase volumes have been synchronized).

ANR2436E Command: Insufficient space to extenddatabase by requested amount.

Explanation: An EXTEND DB command has beenentered, but not enough allocated, unused space isavailable to the database to add the amount of spacerequested.


User Response: Make more database space available,and reissue the command.

ANR2437E Command: Output error encounteredwhile attempting to extend database.

Explanation: An EXTEND DB command has beenentered, but an I/O error occurs during the command.


User Response: Reissue the command. If the problempersists, identify and remove or repair the volume thatcaused the error.

ANR2438E Command: Insufficient database spacewould be available following areduction by the requested amount.

Explanation: A REDUCE DB command has beenentered, but the database does not have enough freespace to reduce by the amount specified.



ANR2439E Command: Unable to vary databasevolume volume name offline - mirroredcopies not synchronized.

Explanation: A VARY OFFLINE command has beenentered, but mirrors of the volume to be varied are notup to date.




User Response: Try the command at a later time (afterdatabase volumes have been synchronized).

ANR2440E Command: Unable to vary databasevolume volume name offline - only copy.

Explanation: A VARY OFFLINE command has beenentered, but the database volume has no mirrors andtherefore contains the only copy of the data on thatvolume.



ANR2441E Command: Volume volume name is alreadydefined as a recovery log volume.

Explanation: A DEFINE LOGVOLUME commandspecifies the name of a recovery log volume thatalready exists.



ANR2442E Command: Volume volume name is not adefined recovery log volume.

Explanation: A DELETE LOGVOLUME commandspecifies the name of a recovery log volume that doesnot exist.



ANR2443E Command: Maximum number of recoverylog volumes exceeded.

Explanation: A DEFINE LOGVOLUME commandattempts to add more recovery log volumes than theserver can manage.



ANR2444E Command: A recovery log define, delete,extend, or reduce operation is already inprogress.

Explanation: The specified command has been enteredwhile a command that is modifying the recovery log isalready active.


User Response: Wait for other activity to end, andreissue the command.

ANR2445E Command: Insufficient space on otherrecovery log volumes to delete volumevolume name.

Explanation: A DELETE LOGVOLUME command hasbeen entered, but the data on the volume to be deletedcannot be copied to other volumes due to insufficientfree space.


User Response: Make more recovery log spaceavailable, and reissue the command.

ANR2446E Command: Unable to delete recovery logvolume volume name - mirrored copiesnot synchronized.

Explanation: A DELETE LOGVOLUME command hasbeen entered, but mirrors of the volume to be deletedare not up to date.


User Response: Try the command at a later time (afterrecovery log volumes have been synchronized).

ANR2447E Command: Insufficient space to extendrecovery log by requested amount.

Explanation: An EXTEND LOG command has beenentered, but there is not enough allocated, unusedspace available to the recovery log to add the amountof space requested.


User Response: Make more recovery log spaceavailable, and reissue the command.

ANR2448E Command: Output error encounteredwhile attempting to extend recovery log.

Explanation: An EXTEND LOG command has beenentered, but an I/O error occurs during the command.


User Response: Reissue the command. If the problempersists, identify and remove or repair the volume thatcaused the error.

ANR2449E Command: Insufficient recovery log spacewould be available following areduction by the requested amount.

Explanation: A REDUCE LOG command has beenentered, but the recovery log does not have enough freespace to reduce by the amount specified.





ANR2450E Command: Unable to vary recovery logvolume volume name offline - mirroredcopies not synchronized.

Explanation: A DELETE LOGVOLUME command hasbeen entered, but mirrors of the volume to be deletedare not up to date.


User Response: Try the command at a later time (afterrecovery log volumes have been synchronized).

ANR2451E Command: Unable to vary recovery logvolume volume name offline - only copy.

Explanation: A VARY OFFLINE command has beenentered, but the recovery log volume has no mirrorsand contains the only copy of the data on that volume.



ANR2452E Command: Maximum recovery logcapacity exceeded.

Explanation: Do not allocate any volume that wouldcause the recovery log to exceed 13GB. A subsequentDEFINE LOGVOLUME command for that volumewould fail.



ANR2453E Command: Unable to reduce recovery log- log mode must be set to NORMAL.

Explanation: A REDUCE LOG command has beenentered, but the recovery log mode of the server iscurrently set to ROLLFORWARD. The recovery log canonly be reduced when the log mode is set to NORMALwith a SET LOGMODE command.


User Response: Set the log mode to NORMAL withthe SET LOGMODE command, reissue the REDUCELOG command, and set the log mode back toROLLFORWARD with the SET LOGMODE command.If you change the log mode to NORMAL, you can onlyrecover your database to the time of the last completedatabase backup.

ANR2454E Command: Unable to reduce database -LOGMODE must be set to NORMAL.

Explanation: A REDUCE DB command has beenentered, but the recovery log mode of the server iscurrently set to ROLLFORWARD. The database canonly be reduced when log mode is set to NORMALwith the SET LOGMODE command.


User Response: Set the log mode to NORMAL withthe SET LOGMODE command, reissue the REDUCEDB command, and reset the log mode toROLLFORWARD with the SET LOGMODE command.If you change the log mode to NORMAL, you can onlyrecover your database to the time of the last completedatabase backup.

ANR2455E Command: Unable to access associatedvolume volume name - access mode is setto ″destroyed″.

Explanation: The specified command would requireaccess to the volume whose name is displayed (becausedata from the volume specified in the command spansinto this volume); the volume shown cannot beaccessed because its status is destroyed.



ANR2456E Command: Unable to access associatedvolume volume name - access mode is setto ″offsite″.

Explanation: The command shown would requireaccess to the volume whose name is displayed (becausedata from the volume specified in the command spansinto this volume); the volume shown cannot beaccessed because its status is offsite.



ANR2457E Command: Backup of primary storagepool primary pool name to copy storagepool copy pool name already in progress.

Explanation: The command shown specifies a backupoperation that is already in progress.


User Response: Reissue the command after thecurrent backup operation ends.



ANR2458E Command: Restore of primary storagepool primary pool name (or volumes inthat storage pool) already in progress.

Explanation: The command shown cannot beprocessed because a restore operation involving theindicated storage pool is already in progress. Either aRESTORE STGPOOL command is in progress for theindicated storage pool or a RESTORE VOLUMEcommand is in progress for volumes that belong to theindicated storage pool.


User Response: Reissue the command after thecurrent restore operation ends.

ANR2459E Command: Volume volume name cannot beupdated - a restore operation involvingthat volume is in progress.

Explanation: The indicated volume has an accessmode of destroyed. Either a RESTORE STGPOOLcommand or a RESTORE VOLUME command is inprogress to restore the contents of the indicatedvolume.


User Response: If necessary, cancel the restoreprocessing and update the volume.

ANR2460E Command: Server could not writesequential volume history informationto File name.

Explanation: The BACKUP VOLHISTORY commanddoes not complete successfully because the servercannot write to the file name specified.


User Response: Make sure that the server has properauthority to write to the file indicated and thatsufficient space is available in the file system for thefile. On MVS, make sure that the data set has beenallocated and that the server has authority to write tothe data set.

ANR2461E Command: An internal error wasencountered in writing sequentialvolume history information to file name.

Explanation: The BACKUP VOLHISTORY commanddoes not complete successfully because the servercannot write to the file name specified.


User Response: Examine error messages on the server

console that may have been displayed prior to thismessage and correct any problems, if possible. Makesure that the server has proper authority to write to thefile indicated and that sufficient space is available inthe file system for the file. On MVS, make sure that thedata set has been allocated and that the server hasauthority to write to the data set.

ANR2462I Command: Server sequential volumehistory information was written to filename.

Explanation: This message is displayed in response tothe BACKUP VOLHISTORY command and indicatesthat sequential volume history information wassuccessfully written to the file name indicated.

System Action: The server records sequential volumehistory information to the file name specified.


ANR2463I Command: Server sequential volumehistory information was written to allconfigured history files.

Explanation: This message is displayed in response tothe BACKUP VOLHISTORY command and indicatesthat sequential volume history information wassuccessfully written to all files that were specified inthe server options file.

System Action: The server records sequential volumehistory information to the configured files.


ANR2464I Command: Volume history files haveNOT been defined for automatic historyrecording - specify a file name forrecording history information.

Explanation: This message is displayed in response tothe BACKUP VOLHISTORY. It indicates that sequentialvolume history information cannot automatically bewritten because no files were defined in the serveroptions file for recording this information.

System Action: The sequential volume historyinformation is not written. Server operation continues.

User Response: Reissue the BACKUP VOLHISTORYcommand and specify the name of a file for recordingsequential volume history information. If desired, youmay configure files that should be automaticallyupdated with the VOLUMEHISTORY parameter andrestart the server.



ANR2465E Command: An I/O error was encounteredin writing sequential volume historyinformation to one or more of thedefined volume history files.

Explanation: The BACKUP VOLHISTORY commanddoes not complete successfully because the servercannot write to one or more of the defined volumehistory files.



ANR2466E Command: An internal server error wasencountered in writing sequentialvolume history information to one ormore of the defined volume historyfiles.

Explanation: The BACKUP VOLHISTORY commanddoes not complete successfully because the servercannot write to one or more of the defined volumehistory files.


User Response: Examine error messages on the serverconsole that may have been displayed prior to thismessage and correct any problems, if possible. Contactyour service representative if you are unable to resolvethe problem.

ANR2467I Command: number of entries deletedsequential volume history entries weresuccessfully deleted.

Explanation: The DELETE VOLHISTORY commandsuccessfully deleted the number of entries specified.



ANR2468E Command: An internal server error wasencountered while deleting serversequential volume history information.

Explanation: The DELETE VOLHISTORY commandfails because an internal server error has beenencountered.

System Action: The DELETE VOLHISTORY commandfails, and server operation continues.

User Response: Examine the messages in the activitylog or server console that were displayed prior to theerror to see if the error can be resolved. Contact yourservice representative if this error cannot be resolved.

ANR2469E Command: Invalid volume history type:history type.

Explanation: The command failed because an invalidsequential volume history type was specified for theTYPE= parameter.

System Action: The command fails, and serveroperation continues.

User Response: Refer to the Administrator’s Referencefor an explanation of the valid types for this command.Reissue the command and specify a valid type value.

ANR2470I Message output being re-directed to filefile name.

Explanation: The message output is being redirectedto the specified file instead of being displayed at theconsole.



ANR2471E Message output re-direction to file filename failed - unable to open file.

Explanation: An error occurs while trying to open thefile. The message output will not be redirected to thespecified file.


User Response: Determine the cause of the file openfailure and take corrective action.

ANR2472E Command: Invalid volume specified:volume name.

Explanation: The command failed because thesequential history volume specified is not a DB DUMP,DB BACKUP, or EXPORT volume.


User Response: Reissue the command and specify avalid volume name.

ANR2473I Command for volume volume namecompleted.

Explanation: The command completed and thevolume history file has been updated.

System Action: The server records sequential volumehistory information.




ANR2474E Command: Input volume names must bespecified with the VOLumenames=parameter.

Explanation: The command failed because inputvolume names were not specified with theVOLumenames parameter.


User Response: On some platforms, or with certaindevice classes, the server cannot prompt to mountinput removable media volumes, so the names of therequired volumes must be specified in the command.Reissue the command specifying the name(s) ofvolumes that should be mounted for input.

ANR2475E Command: File file name could not beopened.

Explanation: The DSMSERV command could not becompleted successfully because the file specified (tocontain the list of volumes to be used) cannot beopened.

System Action: The DSMSERV command fails.

User Response: Examine the file name that wasspecified in the DSMSERV command. Correct thespecification, if necessary, so that it specifies the nameof a file that exists and is accessible by the serverprogram. Reissue the DSMSERV command if this canbe corrected. Contact your service representative if thiserror cannot be resolved.

ANR2476I License storage auditing is disabled, nooutput available.

Explanation: The license storage occupancy function iscurrently disabled.


User Response: To obtain storage occupancy results,remove the NOAUDITSTORAGE or AUDITSTORAGENO option from the server options file, then restart theserver and issue the AUDIT LICENSES command.

ANR2477I License storage auditing is disabled,storage values may be outdated andshould be ignored.

Explanation: The license storage occupancy function iscurrently disabled.


User Response: To obtain storage occupancy results,remove the NOAUDITSTORAGE or AUDITSTORAGENO option from the server options file, then restart theserver and issue the AUDIT LICENSES command.

ANR2478E Command: Command cannot be executedin this session.

Explanation: The command indicated is not supportedby the session in which it was invoked. For example, aDEFINE CURSOR command can not be invoked fromthe server’s primary console.


User Response: The command must be issued from astandard administrator session.

ANR2479E Command: Invalid SQL cursor name -SQL cursor name.

Explanation: The command indicated contains aninvalid SQL cursor name.


User Response: Reissue the command with a validSQL cursor name.

ANR2480E Command: SQL cursor name SQL cursorname is already defined.

Explanation: The command indicated specifies an SQLcursor name that has already been defined.


User Response: Reissue the command and specify adifferent cursor name.

ANR2481E Command: SQL cursor name SQL cursorname is not defined.

Explanation: The command indicated specifies an SQLcursor name that has not been defined.


User Response: Use the DEFINE CURSOR commandto first define the cursor.

ANR2482E Command: SQL cursor SQL cursor name isalready open.

Explanation: The command indicated failed becausean SQL cursor is already open.


User Response: Use the CLOSE CURSOR commandto first close the current cursor.



ANR2483E Command: No SQL cursor is currentlyopen.

Explanation: The command indicated failed becauseno SQL cursor is currently open.


User Response: Use the OPEN CURSOR command tofirst open a cursor.

ANR2484E Command: Invalid SQL date-time displayformat - SQL date-time display formatname.

Explanation: The command indicated contains aninvalid SQL date-time display format name.


User Response: Reissue the command with a validSQL date-time format name.

ANR2485E Command: Invalid SQL display format -SQL display format name.

Explanation: The command indicated contains aninvalid SQL display format name.


User Response: Reissue the command with a validSQL display format name.

ANR2486E Command: Invalid SQL characterarithmetic mode - SQL arithmetic mode.

Explanation: The command indicated contains aninvalid SQL arithmetic mode name.


User Response: Reissue the command with a validSQL arithmetic mode name.

ANR2487E Command: An SQL expression isrequired.

Explanation: The command indicated requires that anSQL expression be provided through the SQL keywordparameter.


User Response: Reissue the command specifying anSQL expression.

ANR2488W List file list file name could not beopened.

Explanation: While attempting to read or write asequential file list, the server was unable to open thefile name specified.

System Action: The server does not use the list file.

User Response: Examine error messages that mayhave been displayed prior to this message and correctany problems, if possible. For OUTFILE files, makesure that the server has proper authority to write to thefile indicated and that there is sufficient space in thefile system for the file. On OS/390 and z/OS, makesure that the server has authority to write to the dataset.

ANR2489W An error was encountered writing tovolume list file volume list file name.

Explanation: While attempting to write to thesequential file for a volume list an error occurs on thefile name specified. The volume list is not be completeand should not be used for input.

System Action: The server stops writing to the file.

User Response: Examine error messages that mayhave been displayed prior to this message and correctany problems, if possible. Make sure that the server hasproper authority to write to the file indicated and thatthere is sufficient space in the file system for the file.On MVS, make sure that the server has authority towrite to the data set. Obtain the volume list fromconsole messages, the QUERY VOLHISTORY commandor the volume history file, if it is used.

ANR2490E Command: NODENAMES andSERVERNAMES parameters cannotboth be specified in the same command.

Explanation: The command indicated failed becauseboth the nodenames parameter and the servernamesparameter were specified.


User Response: Determine whether you want theaction taken for one or more nodes or for one or moreservers and reenter the command with only the correctparameter specified.

ANR2491I Volume Creation Process starting forvolume name, Process Id process ID.

Explanation: As a result of a DEFINE VOLUME,DEFINE DBVOLUME, or DEFINE LOGVOLUMEcommand with the SIZE=xxx parameter, a new volumeis being created. The process whose ID is displayed hasbegun to create the volume shown.

System Action: The server creates the volume andadds it to the server.




ANR2500I Schedule schedule name defined in policydomain domain name.

Explanation: This message is displayed in response tothe DEFINE SCHEDULE command. The schedulenamed schedule name has been defined in the policydomain named domain name in the server database.



ANR2501I Schedule schedule name deleted frompolicy domain domain name.

Explanation: This message is displayed in response tothe DELETE SCHEDULE command. The schedulenamed schedule name has been deleted from the policydomain named domain name in the server database.



ANR2502I Schedule schedule name updated inpolicy domain domain name.

Explanation: This message is displayed in response tothe UPDATE SCHEDULE command. The schedulenamed schedule name has been updated in the policydomain named domain name in the server database.



ANR2503I Schedule schedule name in domain domainname copied to schedule new schedulename in domain new domain name.

Explanation: This message is displayed in response tothe COPY SCHEDULE command. The schedule namedschedule name in policy domain domain name has beencopied to the schedule named new schedule name in thepolicy domain named new domain name. Nodeassociations have not been copied.



ANR2504I Schedule schedule name deleted.

Explanation: This message is displayed in response tothe DELETE SCHEDULE command. The schedulenamed schedule name has been deleted from the serverdatabase.



ANR2505I number of schedules schedules weredefined for command.

Explanation: number of schedules were generated andnodes successfully associated for the command issued.


User Response: If the number is less than expected,check the nodeList and domainList combination specifiedto the DEFINE CLIENTACTION command. Schedulesare generated when at least one node in the nodeListexists in a domain in the domainList.

ANR2506I Node node name associated withschedule schedule name in policy domaindomain name processed. rc=return code.

Explanation: This message is displayed in response tothe DEFINE CLIENTACTION WAIT=YES command.Node node name is associated with the schedule namedschedule name in policy domain domain name has beenprocessed. name The result is indicated in the returncode return code.


User Response: If the return code is non-zero, issuethe QUERY ACTLOG command to to view the activitylog and search for the error messages. After the errorhas been resolved, restart the scheduled operations.

ANR2507I Schedule schedule name for domaindomain name started at start timestamp fornode node name completed successfullyat timestamp.

Explanation: The scheduled operation for the domainname and schedule name specified was processed. It wasprocessed for node node name and completedsuccessfully at the indicated time.


User Response: This message is intended to report thecompletion state of a scheduled client action. Thismessage indicates that the scheduled action completedsuccessfully.

ANR2508E Trace Tsmtrcfm failed: A tracefile nameis required.

Explanation: Trace Tsmtrcfm doesn’t output to console

System Action: Trace won’t start without a tracefilename for Trace Tsmtrcfm

User Response: Issue the command with a tracefilename.



ANR2510I Node node name associated withschedule schedule name in policy domaindomain name.

Explanation: This message is displayed in response tothe DEFINE ASSOCIATION command. Node node nameis associated with the schedule named schedule name inpolicy domain domain name. Schedule schedule name isnow applied to node node name.



ANR2511I Node node name disassociated fromschedule schedule name in policy domaindomain name.

Explanation: This message is displayed in response tothe DELETE ASSOCIATION command. Node node nameis no longer associated with the schedule namedschedule name in policy domain domain name.



ANR2512I Event records deleted: record count.

Explanation: This message is displayed in response tothe DELETE EVENT command. A total of record countevent records have been deleted from the database.



ANR2513I Schedule schedule name copied toschedule new schedule name.

Explanation: This message is displayed in response tothe COPY SCHEDULE command. The schedule namedschedule name has been copied to the schedule namednew schedule name.



ANR2520I Scheduled sessions set to percentpercent.

Explanation: This message is displayed in response tothe SET MAXSCHEDSESSIONS command. It indicatesthe percentage of total server sessions that can be usedfor the processing of scheduled work.



ANR2521I Event record retention period set to daysdays.

Explanation: This message is displayed in response tothe SET EVENTRETENTION command. It indicates thenumber of days for which event records are retained inthe database.



ANR2522I Randomization set to percent percent.

Explanation: This message is displayed in response tothe SET RANDOMIZE command. It indicates thepercentage of the startup window over which the starttimes for individual clients are distributed.



ANR2523I Schedule query period set to hourshour(s).

Explanation: This message is displayed in response tothe SET QUERYSCHEDPERIOD command. It indicatesthe number of hours between attempts by the client tocontact the server for scheduled commands.



ANR2524I Schedule query period reset to valuedetermined by each client.

Explanation: This message is displayed in response tothe SET QUERYSCHEDPERIOD command.



ANR2525I Maximum number of command retriesset to retries.

Explanation: This message is displayed in response tothe SET MAXCMDRETRIES command. It indicates themaximum number of times the client scheduler retriesa command after a failed attempt to process ascheduled command.



ANR2526I Maximum number of command retriesreset to value determined by each client.

Explanation: This message is displayed in response tothe SET MAXCMDRETRIES command.





ANR2527I Retry period set to minutes minutes.

Explanation: This message is displayed in response tothe SET RETRYPERIOD command. It indicates thenumber of minutes between attempts by the clientscheduler to retry, after a failed attempt, to contact theserver or to process a scheduled command.



ANR2528I Retry period reset to value determinedby each client.

Explanation: This message is displayed in response tothe SET RETRYPERIOD command.



ANR2529I Scheduling mode set to POLLING.

Explanation: This message is displayed in response tothe SET SCHEDMODES command. With client-pollingscheduling, a client queries the server at prescribedtime intervals to obtain scheduled work or to ensurethat the schedules the client is waiting to process havenot changed.



ANR2530I Scheduling mode set to PROMPTED.

Explanation: This message is displayed in response tothe SET SCHEDMODES command. Withserver-prompted scheduling, the server contacts theclient when scheduled work needs to be performed anda session is available.



ANR2531I Scheduling mode set to ANY.

Explanation: This message is displayed in response tothe SET SCHEDMODES command. The server nowallows clients to run in either the client-polling or theserver-prompted scheduling mode.



ANR2532I Schedule schedule name updated.

Explanation: This message is displayed in response tothe UPDATE SCHEDULE command. The schedulenamed schedule name has been updated in the serverdatabase.



ANR2533I Client action schedule duration set todays days.

Explanation: This message is displayed in response tothe Set CLIENTACTDuration command. It indicates thenumber of days for which schedules and associationsgenerated by the DEFine CLIENTAction are retained inthe database.



ANR2534I Client action schedule schedule name wasnot executed by node name in domainname.

Explanation: Immediate client action schedule namewas not executed by node node name, which is indomain domain name. The schedule is being deleted.



ANR2535E Command: The node node name cannot beremoved or renamed because it has anassociated data mover.

Explanation: You attempted to remove or rename anode that has an associated data mover.

System Action: The server does not remove or renamethe node.

User Response: To remove or rename the node, deletethe associated data mover and reissue the command.

ANR2536E Command: The ″option″ option is notvalid with the storage pool’s dataformat.

Explanation: The command indicated includes anoption that is not valid with the specified (or defaulted)data format for the storage pool.


User Response: Reissue the command with optionsappropriate for the desired data format of the storagepool.



ANR2537E Command: Device class device class namehas a device type that is not allowed forthis operation.

Explanation: The device class in the indicatedcommand has a device type that is not allowed for thisoperation.


User Response: Choose a different device class andreissue the command.

ANR2538E Command: Backup set cannot begenerated for NAS node node name.

Explanation: Backup sets cannot be generated forNAS nodes.



ANR2539E Command: Storage pool Storage Pool Namedoes not have a valid data format.

Explanation: The data format of the indicated storagepool is not valid for the requested operation. Thestorage pool must have NATIVE or NONBLOCK dataformat. The server is unable to perform the requestedoperation.


User Response: Choose a different storage pool withthe appropriate data format and reissue the command.

ANR2540E Command: The ″option″ device class is notvalid with the storage pool’s dataformat.

Explanation: The command indicated specifies adevice class that is not valid with the specified (ordefaulted) data format for the storage pool.


User Response: Reissue the command with a dataclass appropriate for the desired data format of thestorage pool.

ANR2550W command name: Administrative scheduleschedule name does not have validactivation information.

Explanation: This message is displayed during adatabase audit and indicates that the ’ACTIVE=YES orNO’ information is not recorded correctly for anadministrative schedule in the server database.

System Action: Server database audit operationcontinues.

User Response: Execute the AUDITDB operationspecifying FIX=YES so that the activation informationcan be corrected.

ANR2551I command name: Administrative scheduleschedule name does not have validactivation information - activationinformation will be deleted.

Explanation: This message is displayed during adatabase audit and indicates that the ’ACTIVE=YES orNO’ information is not recorded correctly for anadministrative schedule in the server database. Theaudit operation corrects this discrepancy by removingthe invalid activation information.


User Response: The named administrative schedulewill now appear to be inactive in the server database(as if ACTIVE=NO was specified). If you want thisschedule to be active, execute the UPDATE SCHEDULEcommand with the ACTIVE=YES parameter to activatethe schedule when the server is restarted.

ANR2560I Schedule manager started.

Explanation: The schedule manager is started whenthe server is initialized. The schedule managermaintains entries of scheduled operations.



ANR2561I Schedule prompter contacting node name(session session number) to start ascheduled operation.

Explanation: The schedule prompter contacts theclient scheduler for node node name because ascheduled operation should be started for that node.



ANR2562I Automatic event record deletion started.

Explanation: A process has been started to deleteevent records for which the retention period haselapsed.



ANR2563I Removing event records dated prior todate time.

Explanation: Events that were scheduled to start priorto date time are automatically deleted unless theirstartup window has not yet elapsed.





ANR2564I Automatic event record deletion ended -record count records deleted.

Explanation: The event deletion process has ended. Atotal of record count event records have been deletedfrom the database.



ANR2565I schedules schedules for immediate clientactions have been deleted.

Explanation: A total of schedules that were generatedby the DEFINE CLIENTACTION command haveexpired and been deleted from the database.



ANR2566E An error occurred while deletingimmediate client action schedules.

Explanation: Processing did not complete for deletingschedules that were generated by the DEFINECLIENTACTION command.


User Response: Check the activity log for othermessages that might relate to this failure. Correct anymemory or space problems.

ANR2567W Schedule prompter skipped contactattempt with node name to start ascheduled operation.

Explanation: The schedule prompter skipped thecontact attempt with the client scheduler for node nodename because the start-up window has passed for thatnode, or the node was locked.


User Response: Check the length of the schedulestart-up window to see if it needs to be increased.Check the activity log for ANR2716E messages. Thesemessages are associated with failures to contact a clientscheduler. If there are an excessive number of thesemessages the schedule window could have elapsedwaiting for TCP/IP timeouts from these failedattempts. Also, check to see if the client node is locked.The contact attempt would be skipped for a lockednode.

ANR2570W A scheduled session has been denied.The schedule manager is not active.

Explanation: The client scheduler attempts to connectwith the server, but it is denied a session because theschedule manager is not active.

System Action: Server operation continues, but centralscheduling is not operational.

User Response: Issue the QUERY OPTION commandto determine if the option DISABLESCHEDS YES hasbeen specified in the server options file. If so,scheduling can be enabled by updating the serveroptions file with DISABLESCHEDS NO and restartingthe server. If DISABLESCHEDS YES was not specfiedin the server options file, determine the source of theerror by examining the QUERY ACTLOG command toview the activity log and search for messages. After theerror has been resolved, restart the server to restorecentral scheduler operations. If the error cannot beisolated and resolved, contact your servicerepresentative.

ANR2571W Scheduled session from node node name(platform name) has been denied,scheduled sessions are not currentlyavailable.

Explanation: The client scheduler for node node nameattempts to connect with the server, but is denied asession. All sessions that have been allocated forscheduled operations are already in use.


User Response: Issue the QUERY OPTION commandto determine if the option DISABLESCHEDS YES hasbeen specified in the server options file. If so,scheduling can be enabled by updating the serveroptions file with DISABLESCHEDS NO and restartingthe server. If DISABLESCHEDS YES was not specfiedin the server options file, change the total number ofsessions by altering the MAXSESSIONS parameter inthe server options file and then restarting the server.The percentage of sessions that are available forscheduled operations can be increased by using the SETMAXSCHEDSESSIONS command.

ANR2572W Schedule prompter session to node nodename has been denied, scheduledsessions are not currently available.

Explanation: The server attempts to prompt the clientscheduler for node node name, but all sessions that havebeen allocated for scheduled operations are already inuse.

System Action: The server continues to attemptcontact with the client scheduler until the startupwindow for the scheduled event has elapsed.

User Response: To change the total number ofsessions, alter the MAXSESSIONS parameter in the



server options file and then restart the server. Thepercentage of sessions that are available for scheduledoperations can be increased by using the SETMAXSCHEDSESSIONS command.

ANR2573W Sufficient memory is not available forthe central scheduler - will retry innumber of seconds seconds.

Explanation: The server suspends central schedulerprocessing because sufficient server memory is notavailable.

System Action: Server operation continues; thescheduler operation will be retried after the specifieddelay.


ANR2574W Insufficient recovery log space availablefor the central scheduler - will retry innumber of seconds seconds.

Explanation: The server suspends central schedulerprocessing because sufficient recovery log space is notavailable.


User Response: To increase the amount of log spaceavailable to the server, an authorized administrator canadd log volumes by using the DEFINE LOGVOLUMEcommand, and can extend the size of the log by usingthe EXTEND LOG command.

ANR2575W Insufficient database space available forthe central scheduler - will retry innumber of seconds seconds.

Explanation: The server suspends central schedulerprocessing because sufficient database space is notavailable.


User Response: To increase the amount of databasespace available to the server, an authorizedadministrator can add database volumes by using theDEFINE DBVOLUME command, and can extend thesize of the log by using the EXTEND DB command.

ANR2576W An attempt was made to update anevent record for a scheduled operationwhich has already been executed -multiple client schedulers may be activefor node node name.

Explanation: The server has attempted to update anevent record for a scheduled operation for the specifiedclient node. However, the existing event record showsthat this scheduled operation has already beenexecuted, either successfully or unsuccessfully. Two ormore client schedulers may be running for this node.

System Action: Server operation continues. Theexisting event record is not modified. No furtherprocessing is performed for this scheduled operation.

User Response: Contact the user for this client node,and make sure that only one client scheduler isrunning.

ANR2577I Schedule schedule name defined.

Explanation: This message is displayed in response tothe DEFINE SCHEDULE command. The schedulenamed schedule name in the server database.



ANR2578W Schedule schedule name in domain domainname for node node name has missed itsscheduled start up window.

Explanation: This message is displayed when thescheduled startup window for this schedule has passedand the schedule has not begun.

System Action: Server operation continues. Thescheduled operation is not processed by the server.

User Response: Ensure that a scheduled session fornode node name has been initiated from the client to theserver. Refer to Administrator’s Guide and Administrator’sReference for more information on setting up schedulingoperations.

ANR2579E Schedule schedule name in domain domainname for node node name failed (returncode return code).

Explanation: This message is displayed when a clientreports failure in executing a scheduled action. Thereturn code reported by the client is displayed.


User Response: Examine the node’s schedule log todetermine the cause for the failure.



ANR2580E Schedule schedule name in domain domainname for node node name failed.

Explanation: This message is displayed when theserver finds that a scheduled start window has elapsedfor a client schedule and the client is not currentlyrunning the schedule.


User Response: Examine the node’s schedule log todetermine the cause for the failure. Ensure that theclient scheduler is started.

ANR2581W Schedule schedule name of anadministrative command has missed itsscheduled start up window.

Explanation: This message is displayed when thescheduled startup window for this schedule has passedand the schedule has not begun.

System Action: Server operation continues. Thescheduled operation is not processed by the server.

User Response: Ensure that the duration and periodspecified in the schedule are long enough to allow theschedule to start. Refer to Administrator’s Guide andAdministrator’s Reference for more information on settingup scheduling operations.

ANR2600E Command: Invalid schedule name -schedule name.

Explanation: The specified command has been issuedwith an invalid schedule name.


User Response: Issue the command with a validschedule name.

ANR2601E Command: Schedule description exceedsmaximum length characters.

Explanation: The specified command has been issuedwith a description that exceeds the maximum length.


User Response: Issue the command and specify avalid description.

ANR2602E Command: Invalid action - action.

Explanation: The specified command has been issuedwith an invalid action.


User Response: Issue the command and specify avalid action.

ANR2603E Command: Options string exceedsmaximum length characters.

Explanation: The specified command has been issuedwith an options string that exceeds the maximumlength.


User Response: Issue the command with a validoptions string.

ANR2604E Command: Objects string exceedsmaximum length characters.

Explanation: The specified command has been issuedwith an objects string that exceeds the maximumlength.


User Response: Issue the command with a validobjects string.

ANR2605E Command: Invalid priority - priority.

Explanation: The specified command has been issuedwith an invalid priority.


User Response: Issue the command and specify avalid priority.

ANR2606E Command: Invalid start date - date.

Explanation: The specified command has been issuedwith an invalid start date.


User Response: Issue the command and specify avalid start date.

ANR2607E Command: Invalid start time - time.

Explanation: The specified command has been issuedwith an invalid start time.


User Response: Issue the command and specify avalid start time.

ANR2608E Command: Invalid duration - duration.

Explanation: The specified command has been issuedwith an invalid duration.




User Response: Issue the command and specify avalid duration.

ANR2609E Command: Invalid duration units -duration units.

Explanation: The specified command has been issuedwith an invalid value for duration units.


User Response: Issue the command and specify avalid value for duration units.

ANR2610E Command: Invalid period - period.

Explanation: The specified command has been issuedwith an invalid period.


User Response: Issue the command and specify avalid period.

ANR2611E Command: Invalid period units - periodunits.

Explanation: The specified command has been issuedwith an invalid value for period units.


User Response: Issue the command and specify avalid value for period units.

ANR2612E Command: Invalid day of week - day ofweek.

Explanation: The specified command has been issuedwith an invalid value for day of the week.


User Response: Issue the command and specify avalid value for day of the week.

ANR2613E Command: Invalid expiration - date.

Explanation: The specified command has been issuedwith an invalid expiration date.


User Response: Issue the command and specify avalid expiration date.

ANR2614E Command: Invalid combination of thefollowing parameters: duration, durationunits, period, period units.

Explanation: The specified command has been issuedwith an invalid combination of the DURATION,DURUNITS, PERIOD, and PERUNITS parameters. Thismessage may be displayed if the duration of thestartup window for the schedule is not shorter than theperiod between windows. This message may also bedisplayed if DURUNITS=INDefinite is specified, butPERUNITS=Onetime is not specified.


User Response: Issue the command and specify avalid combination of parameters.

ANR2615E Command: Expiration date date haselapsed.

Explanation: The specified command has been issuedwith an elapsed expiration date date.


User Response: Issue the command and specify anexpiration date that has not already elapsed.

ANR2616E Command: Start date start date must beearlier than expiration date expiration.

Explanation: The specified command has been issuedwith a start date that is not earlier than the expirationdate.


User Response: Issue the command using a schedulestart date that is earlier than the expiration date.

ANR2617E Command: Schedule schedule name is notdefined in policy domain domain name.

Explanation: The specified command has been issuedwith a schedule name that has not been defined in theindicated policy domain.


User Response: Issue the command using a schedulethat has already been defined for this domain.

ANR2618E Command: Schedule schedule name isalready defined in policy domain domainname.

Explanation: The specified command has been issuedwith a schedule name that has already been defined forthe indicated policy domain.




User Response: Issue the command using a schedulethat has not already been defined for this domain.

ANR2619E Command: Currently defined periodperiod is invalid with updated periodunits.

Explanation: The specified command has been issuedwith a value for period units that is not allowed withthe existing period.


User Response: Issue the command and specify a newperiod.

ANR2620E Command: Currently defined durationduration is invalid with updatedduration units.

Explanation: The specified command has been issuedwith a value for duration units that is not allowed withthe existing duration.


User Response: Issue the command and specify a newduration.

ANR2621E Command: No matching schedules.

Explanation: The specified command has been issuedbut no matching schedules have been found.


User Response: Issue the command and specifydifferent schedules.

ANR2622E Command: No new node associationsadded.

Explanation: The specified command has been issuedbut no new node associations are defined.

System Action: Server operation continues, but thecommand has no effect.

User Response: Issue the command and specifydifferent nodes.

ANR2623E Command: No node associations deleted.

Explanation: The specified command has been issuedbut no node associations are deleted.



ANR2624E Command: No matching nodes registered.

Explanation: No matching nodes are found for thespecified command.



ANR2625E Command: No matching nodes registeredin policy domain domain name.

Explanation: The specified command has been issued,but no matching nodes are registered in the indicatedpolicy domain.



ANR2626E Command: Invalid value for replace -replace.

Explanation: The specified command has been issuedwith an invalid value for replace.


User Response: Issue the command using a validvalue for replace.

ANR2627E Command: Invalid value for format -format.

Explanation: The specified command has been issuedwith an invalid value for format.


User Response: Issue the command using a validvalue for format.

ANR2628E Command: Invalid date - date.

Explanation: The specified command has been issuedwith an invalid date.


User Response: Issue the command with a valid date.



ANR2629E Command: Invalid time - time.

Explanation: The specified command has been issuedwith an invalid time.


User Response: Issue the command with a valid time.

ANR2630E Command: Event deletion is already inprocess.

Explanation: The specified command has been issuedwhile event deletion is already in progress.


User Response: Wait for event deletion to completebefore issuing the command.

ANR2631E Command: Invalid begin date - date.

Explanation: The specified command has been issuedwith an invalid begin date.


User Response: Issue the command with a valid begindate.

ANR2632E Command: Invalid begin time - date.

Explanation: The specified command has been issuedwith an invalid begin time.


User Response: Issue the command with a valid begintime.

ANR2633E Command: Invalid end date - date.

Explanation: The specified command has been issuedwith an invalid end date.


User Response: Issue the command with a valid enddate.

ANR2634E Command: Invalid end time - time.

Explanation: The specified command has been issuedwith an invalid end time.


User Response: Issue the command with a valid endtime.

ANR2635E Command: Invalid time range - Begin:begin End: end.

Explanation: The specified command has been issuedwith an invalid time range. This occurs if the date andtime for the beginning of the time range (begin) do notprecede the date and time for the end of the time range(end).


User Response: Issue the command with a valid timerange.

ANR2636E Command: Invalid value for exceptionsonly - exceptions only.

Explanation: The specified command has been issuedwith an invalid value for exceptions only.


User Response: Issue the command with a valid valuefor exceptions only.

ANR2640E Command: Invalid percentage of sessionsfor scheduled processing - value.

Explanation: The specified command has been issuedwith an invalid value.


User Response: Issue the command with a validvalue.

ANR2641E Command: Invalid event record retentionperiod - value.




ANR2642E Command: Invalid percentage forrandomization - value.






ANR2643E Command: Invalid schedule query period- value.




ANR2644E Command: Invalid maximum number ofcommand retries - value.




ANR2645E Command: Invalid retry period - value.




ANR2646E Command: Invalid scheduling mode -value.




ANR2647E Command: Invalid type - type.

Explanation: The specified command has been issuedwith an invalid type.


User Response: Issue the command with a valid type.

ANR2648E Command: Type string exceeds maximumlength characters.

Explanation: The specified command has been issuedwith a type string that exceeds the maximum length.


User Response: Issue the command with a valid typestring.

ANR2649E Command: Schedule schedule name is notdefined.

Explanation: The specified command has been issuedwith a schedule name that has not been defined.


User Response: Issue the command with a schedulethat has already been defined.

ANR2650E Command: Schedule schedule name isalready defined.

Explanation: The specified command has been issuedwith a schedule name that has already been defined.


User Response: Issue the command with a schedulename that has not already been defined.

ANR2651E Command: Invalid combination of one ormore of the following parameters: cmd,type, action, objects, options.

Explanation: The specified command has been issuedwith an invalid combination of the CMD, ACTION,OBJECTS, and OPTIONS parameters. This message isdisplayed when the CMD parameter is specified andTYPE=CLIENT is not specified, or whenTYPE=ADMIN is specified, and one or more of thefollowing is specified: ACTION, OBJECTS, orOPTIONS.


User Response: Issue the command with a validcombination of parameters.

ANR2652E Command: Invalid combination of one ormore of the following parameters:active, cmd, type.

Explanation: The specified command has been issuedwith an invalid combination of the TYPE, CMD, orACTIVE parameters. This message is displayed whenTYPE=CLIENT is specified and one or more of thefollowing is specified: ACTIVE, CMD.


User Response: Issue the command with a validcombination of parameters.



ANR2653W Command: Node node name cannot beprocessed because it is not registered ordoes not belong to the specifieddomain.

Explanation: This command cannot be processed forthe indicated node. Either the node is not registered orit is not assigned to the required domain.

System Action: The indicated node is not processed,but other nodes may be processed if specified by thiscommand.

User Response: If the node name was enteredincorrectly, reissue the command with the correct nodename.

ANR2654E Command: The NODES parameter cannotbe used when querying administrativeschedules.

Explanation: A QUERY SCHEDULE command hasbeen issued with TYPE=ADMINISTRATIVE and theNODES parameter both specified. The NODESparameter cannot be specified when queryingadministrative schedules.


User Response: Issue the command without theNODES parameter.

ANR2655E Command: Invalid client action scheduleduration - days.

Explanation: The specified command has been issuedwith an invalid number of days. Valid values are 1 to9999 inclusive. days specifies the length of time duringwhich a schedule defined by the DEFine CLIENTActioncommand must be executed by an associated node.After that, the schedule will be deleted from thedatabase.


User Response: Reissue the command with a validnumber of days.

ANR2700E Schedule manager aborted.

Explanation: The schedule manager has endedbecause of an error condition and is not able tomaintain entries for scheduled operations.

System Action: Server operation continues, but thecentral scheduler is not operational.

User Response: To determine the source of the error,examine server messages issued prior to this message.Issue the QUERY ACTLOG command to view theactivity log and search for messages. After the error hasbeen resolved, restart the server to restore central

scheduler operations. If the error cannot be isolated andresolved, contact your service representative.

ANR2701E The schedule manager could not bestarted: diagcode.

Explanation: The schedule manager cannot be startedduring initialization because sufficient memory is notavailable. Diagnostic code diagcode is issued.



ANR2702E The schedule prompter could not bestarted: diagcode.

Explanation: The schedule prompter cannot be startedduring initialization because sufficient memory is notavailable. Diagnostic code diagcode is issued.



ANR2703E Schedule prompter aborted.

Explanation: The schedule prompter ends because of aprocessing error.

System Action: Server operation continues, butprompted scheduling is not operational.

User Response: To determine the source of the error,examine server messages issued prior to this message.Issue the QUERY ACTLOG command to view theactivity log and search for messages. After the error hasbeen resolved, restart the server to restore centralscheduler prompting operations. If the error cannot beisolated and resolved, contact your servicerepresentative.

ANR2707E Out of server log space in centralscheduler.

Explanation: The server ends a database updatetransaction for the central scheduler because sufficientlog space is not available on the server.

System Action: Server operation continues, but thedatabase update fails.

User Response: An authorized administrator can usethe DEFINE LOGVOLUME command to add volumesfor use by the log and can issue the EXTEND LOGcommand to extend the size of the log so that the newvolumes are used.



ANR2708E Out of server database space in centralscheduler.

Explanation: The server ends a database updatetransaction for the central scheduler because sufficientdatabase space is not available on the server.


User Response: An authorized administrator can usethe DEFINE DBVOLUME command to add volumesfor use by the database and can use the EXTEND DBcommand to extend the size of the database so that thenew volumes are used.

ANR2709E Schedule manager : Unable to startevent record deletion.

Explanation: Event record deletion cannot be startedbecause sufficient memory is not available.

System Action: Server operation continues, but eventrecords are not automatically deleted after theirretention period has elapsed.


ANR2712E Node node1 requested schedulinginformation for node node2 - sessionrejected.

Explanation: A request for pending scheduledoperations has been sent from the client scheduler fornode node1. However, the request is for schedulinginformation concerning another node node2.

System Action: Server operation continues, but theclient scheduler for node node1 will not be able toprocess pending operations.

User Response: Try restarting the client scheduler fornode node1. If the problem persists, contact your servicerepresentative to resolve the client program error.

ANR2713E Node node1 trying to start scheduledoperation for node node2 - sessionrejected.

Explanation: The client scheduler for node node1 hasattempted to execute a scheduled operation for anothernode, node2.

System Action: Server operation continues, but thescheduled operation is not processed.

User Response: Try restarting the client scheduler fornode node1. If the problem persists, contact your servicerepresentative to resolve client program error.

ANR2714E Node node1 trying to report scheduledoperation results for node node2 -session rejected.

Explanation: The client scheduler for node node1 hasattempted to report the results of a scheduled operationusing another node name, node2.

System Action: Server operation continues, but theresults that were sent from node node1 are not be storedin the server’s database.

User Response: Try restarting the client scheduler fornode node1. If the problem persists, contact your servicerepresentative to resolve the client program error.

ANR2715E Client node node id unable to registervalid address for server prompting: typeaddress type (high address low address).

Explanation: The client scheduler for node node id hasattempted to register an invalid address forserver-prompted central scheduling. The address wastype address type with high-level field high address andlow-level field low address. The only valid address typeis 1.

System Action: Server operation continues, but thenode node id will not be prompted to performscheduled operations.

User Response: Verify that the address type andaddress are correct for this client. The only validaddress type is 1 (for TCP/IP). Make sure the clientscheduler is not using an invalid address obtained fromthe client’s options file or from the command line whenthe client scheduler was started.

ANR2716E Schedule prompter was not able tocontact client node name using typeaddress type (high address low address).

Explanation: The server has attempted to prompt theclient scheduler for node node name because ascheduled operation should be started. The server isunable to contact the client by using address typeaddress type, with high-level field high address andlow-level field low address.

System Action: Server operation continues, but nodenode name is not prompted to start the scheduledoperation. If operations should be started for othernodes, the server will attempt to prompt the clientschedulers for these nodes. This error is usually causedby network outages or the client scheduler program notbeing run on the client node.

User Response: Verify that the address type andaddress are correct for this client. The only validaddress type is 1 (for TCP/IP). Make sure the clientscheduler is not using an invalid address, obtained atthe time the client scheduler was started, from eitherthe client’s options file or from the command line.Verify that the client scheduler for node node name is



running and that the necessary communication links tothat scheduler are operational.

ANR2717E Schedule prompter cannot contact clientnode name using address type (addresstype).

Explanation: The server attempts to prompt the clientscheduler for node node name because scheduled workshould be started. However, either the server does notsupport address type address type needed forserver-prompted scheduling, or the communicationmethod is not currently available. The only validaddress type is 1 (for TCP/IP).

System Action: Server operation continues, but theserver does not prompt node node name.

User Response: If the server does not support theaddress type specified, clients may only use the pollingmode of scheduling. If the communication method istemporarily not available, prompted mode schedulingwill resume after the communication problem is fixedand service restored. If the problem persists, contactyour service representative.

ANR2718W Schedule manager disabled.

Explanation: The schedule manager has been disabledbecause the DISABLESCHEDS YES option wasspecified in the server options file.

System Action: Server operation continues, but thecentral scheduler is not operational.

User Response: To enable the schedule manager,specify DISABLESCHEDS NO in the server options fileand restart the server.

ANR2750I Starting scheduled command schedulename ( scheduled command ).

Explanation: This message is displayed when theserver starts the execution of a scheduled command.The name of the schedule and the actual commandscheduled is displayed.

System Action: Server operation continues, thescheduled command is processed.


ANR2751I Scheduled command schedule namecompleted successfully.

Explanation: This message is displayed when theserver successfully completes processing of a scheduledcommand.



ANR2752E Scheduled command schedule namefailed.

Explanation: This message is displayed when theserver encounters a failure in processing a scheduledcommand.

System Action: Server operation continues. Thescheduled command is ended.

User Response: Examine messages issued prior to thismessage and use the UPDATE SCHEDULE commandto correct the scheduled command. The QUERY EVENTcommand may also be used to determine the cause ofthe failure for this scheduled command.

ANR2753I (Schedule name):command response

Explanation: This message is used to display theserver response to a scheduled command. The name ofthe command schedule is included at the beginning ofthe message in parentheses.

System Action: Server operation continues. Thescheduled command is ended.


ANR2754E DEFINE SCHEDULE or UPDATESCHEDULE parameter CMD=’command’- Unknown command.

Explanation: The specified command is not a validserver command.

System Action: The DEFINE SCHEDULE or UPDATESCHEDULE command is not processed.

User Response: Reissue the correct command.

ANR2755E DEFINE SCHEDULE or UPDATESCHEDULE parameter CMD=’command’- not eligible for scheduling.

Explanation: The specified command is not eligible forscheduling.

System Action: The DEFINE SCHEDULE or UPDATESCHEDULE command is not processed.


ANR2756I Scheduled command schedule namestarted successfully.

Explanation: This message is displayed when theserver successfully starts processing of a backgroundprocess for a scheduled command.





ANR2757E Command: The NODES parameter cannotbe used when querying events foradministrative schedules.

Explanation: A QUERY EVENT command has beenissued with TYPE=ADMINISTRATIVE and the NODESparameter both specified. The NODES parametercannot be specified when querying events foradministrative schedules.


User Response: Issue the command without theNODES parameter.

ANR2758E Please specifiy a tracefile name withless than 37 characters if it is fullyqualified or 26 characters if it is notfully qualified.

Explanation: The .template file adds 9 more charactersto the end of the filename.


User Response: Reduce the filename length to aworking range for s390 system

ANR2780W Command: Updates for nodes previouslyprocessed during this command will berolled back.

Explanation: An error has occurred during anUPDATE NODE operation. If the UPDATE NODEcommand was processing more than one node, updatesfor nodes which were previously processed will berolled back.


User Response: Correct the error and reissue thecommand.

ANR2800E The license manager cannot be started:diagcode.

Explanation: The license manager cannot be startedduring initialization because sufficient memory is notavailable. Diagnostic code diagcode is issued.



ANR2803I License manager started.

Explanation: The license manager is started when theserver is initialized. The license manager monitorslicense compliance.



ANR2804W Insufficient memory is available for thelicense manager - will retry in number ofseconds seconds.

Explanation: The server suspends license managerprocessing because sufficient server memory is notavailable.

System Action: Server operation continues; the licensemanager operation will be retried after the specifieddelay.


ANR2805W Insufficient recovery log space availablefor the license manager - will retry innumber of seconds seconds.

Explanation: The server suspends license managerprocessing because sufficient recovery log space is notavailable.


User Response: To increase the amount of log spaceavailable to the server, an authorized administrator canadd log volumes using the DEFINE LOGVOLUMEcommand, and can extend the size of the log using theEXTEND LOG command.

ANR2806W Insufficient database space available forthe license manager - will retry innumber of seconds seconds.

Explanation: The server suspends license managerprocessing because sufficient database space is notavailable.


User Response: To increase the amount of databasespace available to the server, an authorizedadministrator can add database volumes using theDEFINE DBVOLUME command, and can extend thesize of the log using the EXTEND DB command.

ANR2807E Out of server log space in licensemanager.

Explanation: The server ends a database updatetransaction for the license manager because sufficientrecovery log space is not available on the server.




User Response: An authorized administrator can usethe DEFINE LOGVOLUME command to add volumesfor use by the log and can issue the EXTEND LOGcommand to extend the size of the log so that the newvolumes are used.

ANR2808E Out of server database space in licensemanager.

Explanation: The server ends a database updatetransaction for the license manager because sufficientdatabase space is not available on the server.


User Response: An authorized administrator can usethe DEFINE DBVOLUME command to add volumesfor use by the database and can use the EXTEND DBcommand to extend the size of the database so that thenew volumes are used.

ANR2811I Audit License completed - Server is incompliance with license terms.

Explanation: The results from the AUDIT LICENSEScommand indicate the server is in compliance with theterms of the current license.



ANR2812W License Audit completed - ATTENTION:Server is NOT in compliance withlicense terms.

Explanation: The results from the AUDIT LICENSEScommand indicate the server is not in compliance withthe terms of the current license.

System Action: Server operation continues, but theREGISTER NODE command or backup-archiverequests, or both, will fail.


ANR2813I Server is licensed for a capacity ofcapacity gigabytes and number of clientsclients.

Explanation: This message is issued during serverstartup.



ANR2814I Audit command: License audit periodchanged to number of days days.

Explanation: This message is displayed in response tothe SET LICENSEAUDITPERIOD command used tochange the interval in days between automatic licenseaudits.



ANR2815E Command: Invalid value specified forinterval between license audits - value.




ANR2816E Command: License audit or registeroperation already in progress.

Explanation: The server is currently performing aregister license or license audit.

System Action: The server does not process thespecified command.

User Response: Reissue the command after the licenseaudit process or the register license command ends.Only one REGISTER LICENSE command or AUDITLICENSE process can be running at a time. TheREGISTER LICENSE command and the AUDITLICENSE process may not run at the same time.

ANR2817I Command: License audit started asprocess process ID.

Explanation: A background process has been startedto audit the server for license compliance.

System Action: The server checks the existingconfiguration for the server and compares it against thevalues for which the server is licensed.

User Response: The administrator may query thestatus of the background process by using the QUERYPROCESS command, or cancel the process with theCANCEL PROCESS command.

ANR2818I Command: Licensed capacity is capacityGB with number of clients clients.

Explanation: This message displays the licenseinformation that existed before issuing the REGISTERLICENSE command.





ANR2819I Command: Licensed capacity changed tocapacity GB with number of clients clients.

Explanation: The license information has beenchanged to the indicated values with the REGISTERLICENSE command.


User Response: To implement the changed licenseinformation, issue an AUDIT LICENSES command orwait until an automatic license audit occurs.

ANR2820I Automatic license audit started asprocess process ID.


System Action: The server checks storage utilizationand registered nodes for the server and licensed factors,comparing these against the values for which the serveris licensed.

User Response: The administrator may query thestatus of the background process using the QUERYPROCESS command.

ANR2821E Automatic license audit could not bestarted: diagcode.

Explanation: The license manager cannot start anautomatic process to audit server licenses becausesufficient memory is not available. Diagnostic codediagcode is issued.




Explanation: The license audit operation has beencancelled and will end when resources have been freedfor the background process. This message may bedisplayed in response to a QUERY PROCESS commandfor an AUDIT LICENSES operation.



ANR2823I Have audited number of nodes nodes

Explanation: An AUDIT LICENSES operation is inprogress. The process has audited the specified numberof nodes. This message may be displayed in responseto a QUERY PROCESS command for an AUDITLICENSES operation.



ANR2824I License audit process process numbercanceled - number of nodes nodes audited.

Explanation: A background server process to auditserver licenses has been canceled by using theCANCEL PROCESS command. The number of nodesthat have been audited before the operation ended arereported in the message.



ANR2825I License audit process process numbercompleted successfully - number of nodesnodes audited.

Explanation: A background server process to auditserver licenses has completed successfully afterauditing the specified number of nodes.



ANR2826I License audit process process numberterminated in error - number of nodesnodes audited.

Explanation: A background server process to auditserver licenses encounters an error and is ended. Thenumber of nodes that have been audited before theoperation ended is reported in the message.



ANR2832I Command: The License Manager has notyet completed initialization - pleaseretry this command later.

Explanation: While attempting to process the specifiedlicense command, the server detects that the licensingcomponent of the server had not completedinitialization. The licensing facility used on someplatforms may require some time to initialize becausenetwork calls are involved, and waits may occur.

System Action: Server operation continues; thecommand is not processed.

User Response: Reissue the command after waiting 10minutes. If this message is displayed after a number ofretry attempts, contact your service representative.



ANR2833I Command: Auditing license definitions.

Explanation: The server has started to audit databasedefinitions that describe licensing information.



ANR2834W License Audit completed - WARNING:Server is NOT in compliance withlicense terms.

Explanation: The results from the AUDIT LICENSEScommand indicate that the server is not in compliancewith the terms of the current license.

System Action: Server operation continues, but theREGISTER NODE command fails.

User Response: Use the QUERY LICENSE commandto determine the license terms that are no longer incompliance. Remove nodes or purchase additionalclient node connections. After these actions have beentaken, reissue the AUDIT LICENSES command toresynchronize the server configuration with licenseterms.

ANR2836I Command: License audit started asprocess process ID.


System Action: The server checks registered nodes forthe server and compares this against the value forwhich the server is licensed.

User Response: The administrator may query thestatus of the background process using the QUERYPROCESS command, or cancel the process with theCANCEL PROCESS command.

ANR2839I Automatic license audit started asprocess process ID.


System Action: The server checks registered nodesand compares them against the value for which theserver is licensed.

User Response: The administrator may query thestatus of the background process by using the QUERYPROCESS command.

ANR2841W Server is NOT IN COMPLIANCE withlicense terms.

Explanation: This message is issued periodically whenthe server configuration does not comply with theterms for which it is licensed.


User Response: Use the QUERY LICENSE commandto display the current server configuration with respectto licensed terms to discover which factors of theconfiguration do not conform to your license. Contactyour service representative to obtain more licenses, ifrequired.

ANR2852I Current license information:

Explanation: This message is issued during aREGISTER LICENSE command to display the currentlicensing information for the server before the newlicense has been interpreted by the command. Messagesappearing after this message display the factors underwhich the server is currently licensed.



ANR2853I New license information:

Explanation: This message is issued during aREGISTER LICENSE command to display the updatedlicensing information for the server after the newlicense has been interpreted by the command. Messagesappearing after this message display the updatedfactors under which the server is licensed.


User Response: Check to make sure that the newlicense information includes the updates that youintended for the REGISTER LICENSE command. If thelicense terms do not change, check the parameters andreissue the command, if you find that it was notentered correctly. If the REGISTER LICENSE commanddoes not produce the desired updates in terms oflicensing, contact your service representative.

ANR2855I Server is licensed to support TivoliSpace Manager clients.




ANR2860I Server is licensed to support TivoliDisaster Recovery Manager.






ANR2900W The character string ’string’ wastruncated during assignment.

Explanation: Truncation occurred during assignmentof an SQL character string. For example, the expressionCAST( ’Hello’ AS CHAR(2) ) will result in truncationbecause the string ’Hello’ (length 5) can not fit in thetarget type CHAR(2) without loss of trailing characters.

System Action: This warning can occur before or afterSQL query processing, but does not terminate queryprocessing.


ANR2901W The result of character stringconcatenation was truncated.

Explanation: Truncation occurred when theconcatenation of character strings resulted in a lengththat exceeds the maximum character string length (250for data type CHAR, and 2000 for data typeVARCHAR).

System Action: This warning can occur before or afterSQL query processing, but does not terminate queryprocessing.


ANR2902E Insufficient memory was available toprocess the SQL statement.

Explanation: Sufficient memory was not available tocomplete the processing of an SQL query.

System Action: The SQL query is terminated.


ANR2903E An SQL parser stack overflow occurredwhile processing token ’token’.

Explanation: The internal stack used by the SQLquery parser has overflowed. This typically occurswhen too many column names or expressions havebeen specified in the SELECT clause.



ANR2904E Unexpected SQL key word token -’token’.

Explanation: A syntax error occurred because an SQLkey word was found that can not legally be used at thespecified position within the SQL statement. Examplesof SQL key words are SELECT, FROM, and WHERE.



ANR2905E Unexpected SQL identifier token -’token’.

Explanation: A syntax error occurred because an SQLidentifier was found that can not legally be used at thespecified position within the SQL statement. Examplesof SQL identifiers are table names and column names.



ANR2906E Unexpected SQL literal token - ’token’.

Explanation: A syntax error occurred because an SQLliteral token was found that can not legally be used atthe specified position within the SQL statement.Examples of SQL literal tokens are ’abc’, 1.567, andDATE ’1/1/96’.



ANR2907E Unexpected SQL operator token - ’token’.

Explanation: A syntax error occurred because an SQLoperator token was found that can not legally be usedat the specified position within the SQL statement.Examples of SQL operator tokens are +, *, <, and =.



ANR2908E Unexpected SQL punctuation token -’token’.

Explanation: A syntax error occurred because an SQLpunctuation token was found that can not legally beused at the specified position within the SQL statement.Examples of SQL punctuation tokens are the period,the comma, and the parenthesis.



ANR2909E The SQL statement is incomplete;additional tokens are required.

Explanation: A syntax error occurred because,although the syntax of the SQL query expression wascorrect up to the end of the string, the parser expectedadditional tokens in order to form asyntactically-correct SQL statement.





ANR2910E Invalid SQL token - ’token’.

Explanation: An invalid SQL token was found. Forexample, the token formed by the character sequence″::!″ is not a valid SQL token.



ANR2911E Invalid SQL numeric literal token -’token’.

Explanation: An invalid SQL numeric literal tokenwas found. For example, the floating point literal″1.456E″ is not valid.



ANR2912E Invalid character string literal token -’token’.

Explanation: An invalid SQL character string literaltoken was found. For example, the hexadecimal literalX’78FG’ is not valid because it contains the character’G’.



ANR2913E Invalid SQL identifier token - ’token’.

Explanation: An invalid SQL identifier token wasfound. For example, the character sequence ″ABC.123″is not a valid identifier because the second part of theidentifier, ″123″, does not begin with a letter.



ANR2914E SQL identifier token ’token’ is too long;name or component exceeds 18characters.

Explanation: An SQL identifier token was found thatexceeds the maximum length of 18 characters percomponent.



ANR2915E The SQL token beginning with ’token’ ismissing an ending delimiter.

Explanation: An SQL token was found that is missingits ending delimiter. For example, each of the tokens’abc, ″abc, and X’abc is missing its ending delimiter.



ANR2916E The SQL data types data type and datatype are incompatible for operator’operator’.

Explanation: The data types of the operands are notcompatible when used with the specified operator. Forexample, the expression 3 + ’abc’ is not valid becausethe operand data types INTEGER and CHAR(3) are notcompatible for the addition operator ″+″.



ANR2917E The SQL data type of expression’expression’ is data type; expecting aninteger expression.

Explanation: An SQL expression of data typeSMALLINT, INTEGER, or DECIMAL with scale zero isexpected.



ANR2918E The SQL data type of expression’expression’ is data type; expecting aBoolean expression.

Explanation: An SQL expression of data typeBOOLEAN is expected.



ANR2919E The SQL data type of expression’expression’ is data type; expecting anumeric expression.

Explanation: An SQL expression of numeric data typeSMALLINT, INTEGER, DECIMAL, NUMERIC, REAL,FLOAT, or DOUBLE_PRECISION is expected.



ANR2920E The SQL data type of expression’expression’ is data type; expecting anumeric or interval expression.

Explanation: An SQL expression of numeric data type(SMALLINT, INTEGER, DECIMAL, NUMERIC, REAL,FLOAT, DOUBLE) or of interval data type (INTERVAL)is expected.





ANR2921E The SQL data type of expression’expression’ is data type; expecting acharacter string expression.

Explanation: An SQL expression of character stringtype CHAR or VARCHAR is expected.



ANR2922E The SQL data type of expression’expression’ is data type; expecting a date,timestamp, character string date,character string timestamp, or intervalexpression.

Explanation: An SQL expression was expected of oneof the types DATE, TIMESTAMP, CHAR, VARCHAR,or INTERVAL as the operand to the EXTRACTfunction. In the case of CHAR or VARCHAR, theexpression must be a valid character stringrepresentation of a date or a timestamp.



ANR2923E The SQL data type of expression’expression’ is data type; expecting a time,timestamp, character string time,character string timestamp, or intervalexpression.

Explanation: An SQL expression was expected of oneof the types TIME, TIMESTAMP, CHAR, VARCHAR, orINTERVAL as the operand to the EXTRACT function.In the case of CHAR or VARCHAR, the expressionmust be a valid character string representation of atime or a timestamp.



ANR2924E The SQL data type of expression’expression’ is data type; expecting a dateor character string date expression.

Explanation: An SQL expression was expected of oneof the types DATE, CHAR, or VARCHAR. In the caseof CHAR or VARCHAR, the expression must be a validcharacter string representation of a date.



ANR2925E The SQL data type of expression’expression’ is data type; expecting a timeor character string time expression.

Explanation: An SQL expression was expected of oneof the types TIME, CHAR, or VARCHAR. In the case of

CHAR or VARCHAR, the expression must be a validcharacter string representation of a time.



ANR2926E The SQL data type of expression’expression’ is data type; expecting a date,timestamp, character string date, orcharacter string timestamp expression.

Explanation: An SQL expression was expected of oneof the types DATE, TIMESTAMP, CHAR, orVARCHAR. In the case of CHAR or VARCHAR, theexpression must be a valid character stringrepresentation of a date or a timestamp.



ANR2927E The SQL data type of expression’expression’ is data type; expecting aninterval containing a single date-timefield.

Explanation: An SQL expression was expected of datatype INTERVAL YEAR, INTERVAL MONTH,INTERVAL DAY, INTERVAL HOUR, INTERVALMINUTE, or INTERVAL SECOND, all of which containa single date-time field. Multi-field interval types (forexample, INTERVAL DAY TO SECOND) are notallowed.



ANR2928E A number can not be converted to SQLdata type INTERVAL if the intervalcontains multiple date-time fields.

Explanation: An attempt was made to convert anumber to the data type INTERVAL, but the targetinterval contains multiple date-time fields (for example,INTERVAL DAY TO SECOND). Only the single-fieldinterval types INTERVAL YEAR, INTERVAL MONTH,INTERVAL DAY, INTERVAL HOUR, INTERVALMINUTE, or INTERVAL SECOND can be specified.



ANR2929E The expression ’expression’ is not aninteger constant.

Explanation: An integer constant such as 1 or -9 isexpected. For example, the DECIMAL function requiresthat the precision and scale operands be integerconstants. A decimal constant such as 1.67 is not valid.





ANR2930E A subquery used in an SQL expressionmust specify a single result column.

Explanation: A subquery used in an expression cannot specify multiple result columns. For example, theexpression X > (select A,B from T) is invalid because itspecifies two result columns (A and B).



ANR2931E A subquery expression may not containa reference to a column name that iscontained in an outer query expression.

Explanation: A subquery contains a reference to acolumn name in an outer query expression.



ANR2932E The maximum nesting depth forsubquery expressions has beenexceeded.

Explanation: Too many nested subqueries werespecified.



ANR2933E The WHERE clause must not contain anaggregate function.

Explanation: The use of the aggregate functionsCOUNT, MAX, MIN, SUM, AVG, VARIANCE, orSTDDEV in the WHERE clause is not allowed.



ANR2934E The result data type of a CASEexpression can not be determined; atleast one non-null THEN or ELSEexpression must be specified.

Explanation: The result data type of a CASEexpression can not be determined because all of theTHEN expressions and the ELSE expression (if present)specifies the NULL key word.



ANR2935E The date-time field field is not present inthe expression ’expression’ (data type datatype).

Explanation: The specified date-time field (YEAR,MONTH, DAY, HOUR, MINUTE, or SECOND) is notcontained in the data type of the expression.



ANR2936E The SQL aggregate function function cannot be nested within another aggregatefunction.

Explanation: One of the aggregate functions COUNT,MAX, MIN, SUM, AVG, VARIANCE, or STDDEV wasfound nested within another aggregate expression.



ANR2937E An SQL subquery expression can not benested within an aggregate function.

Explanation: An expression containing a subquerywas found nested within one of the aggregate functionsCOUNT, MAX, MIN, SUM, AVG, VARIANCE, orSTDDEV.



ANR2938E The column ’column’ is not allowed inthis context; it must either be named inthe GROUP BY clause or be nestedwithin an aggregate function.

Explanation: A column reference was specified that isneither a column specified in a GROUP BY clause noris a column nested in one of the aggregate functionsCOUNT, MAX, MIN, SUM, AVG, VARIANCE, orSTDDEV. The use of the column reference is prohibitedbecause either 1) the GROUP BY clause has beenspecified, 2) the HAVING clause has been specified, or3) at least one aggregate function is present.



ANR2939E The reference ’reference’ is an unknownSQL table name.

Explanation: The specified table reference is not oneof the base tables defined by the server’s database. Therows of the table SYSCAT.TABLES can be selected toobtain a list of all of the valid base tables.





ANR2940E The reference ’reference’ is an unknownSQL column name.

Explanation: The specified column reference is notone of the base table columns defined by the server’sdatabase. The rows of the table SYSCAT.COLUMNScan be selected to obtain a list of all of the valid basetable columns. If a two-part (compound) columnreference such as X.Y is specified, then the correlationname X must be one of the active correlation names forthe query.



ANR2941E The column reference ’column reference’matches more than one SQL columnname.

Explanation: The specified column reference isambiguous because it matches the columns associatedwith multiple tables.



ANR2942E The column reference ’column reference’ isnot allowed in this context because it ispart of an outer SQL query expression.

Explanation: The specified column reference is notallowed because it names a columns of some outerquery expression. Such references are not allowed whencontained within the expressions of the HAVING andSELECT clauses.



ANR2943E The column reference ’column reference’ isa duplicate of another SQL columnname in the same list.

Explanation: A duplicate column reference wasspecified within the same GROUP BY or ORDER BYlist of columns.



ANR2944E The reference ’reference’ is an unknownSQL scalar function name.

Explanation: The specified function reference is notthe name of a valid scalar function.



ANR2945E Too few arguments are specified forSQL scalar function function.

Explanation: Too few function arguments werespecified. For example, the expression LEFT(x) isinvalid because the LEFT function requires at least twoarguments.



ANR2946E Too many arguments are specified forSQL scalar function function.

Explanation: Too many function arguments werespecified. For example, the expression UPPER(x,y) isinvalid because the UPPER function requires exactlyone argument.



ANR2947E Division by zero was detected foroperator ’operator’.

Explanation: An attempt to divide by the number zerowas detected for the specified SQL operator. The mostlikely cause of the problem is that one of the values ofa column is zero, and that column is used in thedenominator of a division operation. To protect againstthis case the NULLIF function can be used. Forexample, instead of the expression 1/X, specify1/NULLIF(X,0), which will set the expression to nullwhenever the value if X is zero.



ANR2948E The value ’value’ can not be assigned orconverted to SQL data type data type.

Explanation: A value could not assigned or convertedto a value in the specified SQL data type because either1) the data type of the value can not be legally cast tothe target data type (for example, data type TIME cannot be converted to data type INTEGER); 2) theassignment of the value results in overflow in thetarget data type (for example, the decimal value12345678.34 can not be assigned to data typeDECIMAL(3,2) because the precision of the target typeis exceeded); or 3) the syntax of a character string valueis not appropriate for the target data type (for example,the string ’abc’ can not be converted to data typeDATE).





ANR2949E Arithmetic overflow occurred for SQLoperator ’operator’.

Explanation: An arithmetic overflow occurred for thespecified operator. Examples of this include: 1) theapplication of the unary negation operator to thesmallest INTEGER value (-2147483648) causes overflowbecause the result can not be represented in 2’scomplement; 2) the sum of the set of INTEGER columnvalues applied to the SUM aggregate function can notbe represented within the precision of INTEGER type.



ANR2950E Arithmetic or date-time overflowoccurred for SQL operator ’operator’ forvalues ’value’ (data type data type) and’value’ (data type data type).

Explanation: An arithmetic or date-time overflowoccurred for the specified operator. The values thatcaused the overflow (and their SQL data types) aredisplayed.



ANR2951E The value ’value’ (data type data type) isnot a valid argument for operator’operator’.

Explanation: An invalid value was specified as anargument to an SQL operator. For example, theexpression SQRT(-1) is not valid because the argumentto the SQRT function is negative.



ANR2952E The value ’value’ (data type data type) isnot a valid character stringrepresentation of an SQL date or atimestamp for operator ’operator’.

Explanation: An invalid character stringrepresentation of a DATE or TIMESTAMP wasspecified. For example, the string ’abc’ is neither a validdate nor a timestamp.



ANR2953E The value ’value’ (data type data type) isnot a valid character stringrepresentation of an SQL time or atimestamp for operator ’operator’.

Explanation: An invalid character stringrepresentation of a TIME or TIMESTAMP was

specified. For example, the string ’g pm’ is neither avalid time nor a timestamp.



ANR2954E An SQL subquery used in a scalarexpression must yield a table thatcontains at most one row.

Explanation: This error results when a subquery usedin a scalar expression returns multiple rows, therebymaking it ambiguous as to which value should bereturned.


User Response: Respecify the subquery (for example,using the WHERE clause) so that the subquery returnsat most one row.

ANR2955E The SQL character string expression’expression’ must return a singlecharacter.

Explanation: A single-character character string wasexpected for the ESCAPE clause of the LIKE operator,for the trim character of the TRIM operator, or for thepad character of the LEFT or RIGHT function. Forexample, the string ’Hello’ is invalid because it containsmultiple characters.



ANR2956E Unable to access SQL base table ’table’.

Explanation: An error occurred when attempting toread rows from one of the SQL base tables. Thismessage is typically preceded by another errordescribing the condition.



ANR2957E An error occurred inserting a row in anSQL temporary table. The serverdatabase size may need to be increased

Explanation: An error occurred when attempting toinsert a row into a temporary table being used for anSQL query. This message is typically preceded byanother error describing the condition. In many casesthis error can be resolved by increasing the size of theserver database. Free space in the database is used tostore temporary tables created during the execution ofan SQL SELECT query.





ANR2958E SQL temporary table storage has beenexhausted.

Explanation: The result of an SQL query could not becomputed because temporary table storage space wasunavailable. By issuing the QUERY DB command andviewing the Maximum Reduction parameter, you candetermine the amount of space that is available fortemporary table storage space. If the parameter is lessthan 4, the storage space becomes exhausted and theSQL query can no longer run. Complex SQL queriessuch as the ORDER BY clause, the GROUP BY clause,and the DISTINCT operator can cause additionaltemporary table space to be required.


User Response: If your database is full, increase thesize of the database. If your database is fragmented(Where the Available space parameter is greater than 4,but the Maximum Reduction parameter is less than 4),you must either unload and load your database or addavolume.

ANR2959E SQL temporary table row is too wide.

Explanation: A row could not be inserted into an SQLtemporary table because the row is too wide. This canoccur if 1) there are too many columns in the row beinginserted, or 2) the sum of the lengths of the columns inthe row is too wide. Temporary tables are used when 1)the ORDER BY clause is specified; 2) the GROUP BYclause is specified; or 3) the DISTINCT operator isspecified.


User Response: Reduce the number of columnsspecified in the ORDER BY and/or GROUP BY clauses.

ANR2960E Unexpected SQL enumerated type nametoken - ’token’.

Explanation: A syntax error occurred because an SQLenumerated type name was found that can not legallybe used at the specified position within the SQLstatement. A list of all of the enumerated types declaredby the server can be found in the SQL catalog tableSYSCAT.ENUMTYPES.



ANR2961E Invalid SQL enumerated type name -’name’.

Explanation: A syntax error occurred because an SQLenumerated type name was expected, but the specifiedname is not one of the declared enumerated types. Forexample, the literal expression XXX::YYYY is illegalbecause XXX is not a valid enumerated type name. Alist of all of the enumerated types declared by the

server can be found in the SQL catalog tableSYSCAT.ENUMTYPES.



ANR2962E Unable to resolve SQL enumerated typefor value ’value’.

Explanation: A syntax error occurred because anunqualified SQL enumerated value name was specified,but, because that value name is a member of more thanone enumerated type, its type could not be resolved.For example, the enumerated value name YES belongsto more than one enumerated type, and so the resulttype of the expression YES = YES can not be resolved.A list of all of the enumerated types declared by theserver can be found in the SQL catalog tableSYSCAT.ENUMTYPES.



ANR2963W This SQL query may produce a verylarge result table, or may require asignificant amount of time to compute.

Explanation: An SQL query has been posed that couldpotentially cause a very large number of rows to bereturned and displayed, or may involve a large amountof processing time before the first result table row canbe generated.


User Response: Enter 'Y' to continue with SQL queryprocessing or 'N' to terminate the query.

ANR2964E The reference ’reference’ is not a columnof the SQL result table.

Explanation: The ORDER BY clause specified acolumn that is not part of the result table for the SQLquery. Only those columns named in the select list arepart of the result table.



ANR2965E An SQL temporary table cannot bebuilt. required columns columns areneeded. maximum columns is themaximum.

Explanation: A temporary table required columns wideis needed to complete processing for an SQL query. Themaximum degree of an SQL table is maximum columns.The table will not be created.




User Response: If the ORDER BY and/or GROUP BYclauses were specified, reduce the number of columnsneeded for the result table.

ANR2966E Command/process: Database temporarytable storage has been exhausted.

Explanation: The named command or operation couldnot be completed because insufficient temporary tablestorage space was available. Free space in the serverdatabase is used to store temporary tables createdduring the execution of the named command orprocess.

System Action: The named command or process isterminated.

User Response: Extend the server datbase (afteradding database volumes if necessary) and rerun thecommmand or process.

ANR2996I The server log is log full percentagepercent full. The server is no longerdelaying transactions.

Explanation: The server log utilization wasdangerously high and the server was delayingtransactions. The log utilization is now at a lower leveland the server is no longer delaying transactions.


User Response: Continue to monitor server activityand log usage. If log usage is low enough, you mayconsider reducing the amount of space allocated to thelog.

ANR2997W The server log is log full percentagepercent full. The server will delaytransactions by delay time milliseconds.

Explanation: The server log utilization is very high. Inorder to prevent the server log from becoming full, theserver will begin delaying transactions by the specifiedamount of time.


User Response: Monitor server activity and log usage.If possible, delay adding new work to the server load.

ANR2998W The server log is log full percentagepercent full. The server has cancelledthe oldest transaction in the log.

Explanation: The server log utilization is dangerouslyhigh. In order to prevent the server log from becomingexhausted, the server has cancelled the oldesttransaction in the log. Once the server activityassociated with this transaction is able to performcleanup processing, log space will be freed.


User Response: Monitor server activity and log usage.If possible, delay adding new work to the server load.

ANR3000E Command: Command can only be issuedon a configuration manager.

Explanation: The command can only be issued on aserver that is a configuration manager.

System Action: Server operation continues. Thecommand is not processed.

User Response: Issue this command from aconfiguration manager.

ANR3001E Command: Command can only be issuedon a managed server.

Explanation: The command can only be issued on amanaged server.


User Response: Issue this command from a managedserver.

ANR3002E Command: Profile name exceeds maximumlength characters.

Explanation: The profile name specified in thecommand is longer than the maximum length allowed.


User Response: Select a profile name that does notexceed the maximum length.

ANR3003E Command: Profile description exceedsmaximum length characters.

Explanation: The profile description specified in thecommand is longer than the maximum length allowed.


User Response: Select a description that does notexceed the maximum length.

ANR3004E Command: The configuration managername exceeds maximum length characters.

Explanation: The configuration manager namespecified in the command is longer than the maximumlength allowed.


User Response: Select a configuration manager namethat does not exceed the maximum length.



ANR3005E Command: The server name exceedsmaximum length characters.

Explanation: The configuration manager namespecified in the command is longer than the maximumlength allowed.


User Response: Select a configuration manager namethat does not exceed the maximum length.

ANR3006E Command: The configuration refreshinterval value must be between minimumvalue and maximum value.

Explanation: The specified command has been issuedwith an invalid refresh interval.


User Response: Issue the command and specify avalid refresh interval value.

ANR3007E Command: The option option must bespecified.

Explanation: When the command is issued on a aserver that is neither a configuration manager nor amanaged server, the specified option must be supplied.


User Response: Reissue the command with thespecified option.

ANR3010W This command will delete an object thatis associated with one or more profileson a configuration manager. Subsequentconfiguration refresh processing willdelete the object on managed serversthat subscribe to a profile with whichthe object is associated.

Explanation: A command has been entered that willdelete an object from a configuration manager. Sincethis object is associated with one or more profiles on aconfiguration manager, configuration refresh processingwill delete this object on subscribing managed servers.


User Response: To process the command, enter 'Y' tocontinue or 'N' to stop the process.

ANR3011E command: Subscription for profile profilename was not deleted because one ormore objects could not be discarded.

Explanation: This message was issued because one ormore objects could not be discarded by the indicatedcommand. A previous message gives an explanation foreach object that could not be discarded.

System Action: The system may discard some of themanaged objects that are associated with profile profilename The subscription itself is not deleted.

User Response: Examine previous messages todetermine the action that must be taken beforeremaining objects can be discarded. Alternatively, youcan delete the subscription without using theDISCARDOBJECTS=YES option.

ANR3012I command: Configuration manager stateset to state.

Explanation: The command has successfully set theconfiguration manager state.

System Action: The command succeeded.


ANR3013W command: Configuration manager statealready set to state.

Explanation: The specified state is already in force onthe server.


User Response: This server is already set to thespecified state. If the state should be set differently,reissue the command specifying the new state value.

ANR3014E command: One or more subscriptions stillexist.

Explanation: A configuration manager state cannot beset to OFF is one or more subscription still exist. Theserver still has a record of one or more subscriptions toits profiles.


User Response: Use the QUERY SUBSCRIBERScommand to determine which subscriptions still exist.The DELETE SUBSCRIBER command can be used toremove the record of these subscriptions. You mayinstead want to delete the actual subscription(s) on themanaged server(s). When there are no moresubscriptions recorded on the configuration manager,you must then delete all the profiles. Once the profileshave been deleted, you can reissue the command.



ANR3015E command: One or more profiles stillexist.

Explanation: A configuration manager state cannot beset to OFF is one or more profiles still exist.


User Response: Use the QUERY PROFILE commandto determine which profiles still exist on theconfiguration manager then use the DELETE PROFILEcommand. After all the profiles have been deleted,reissue the command.

ANR3016I command: Configuration refresh intervalset to interval.

Explanation: The command has successfully set theconfiguration refresh interval to the specified value.Automatic configuration refresh processing willimmediatly be attempted and then will again beperformed after the specified number of minutes ofelapsed.



ANR3017I command: Profile profile name defined.

Explanation: The command has successfully define aprofile.



ANR3018E command: Profile profile name alreadyexists.

Explanation: The profile specified already exists onthe configuration manager.


User Response: Decide on another profile name andreissue the command.

ANR3019I command: Profile profile name updated.

Explanation: The command has successfully updateda profile.



ANR3020E command: Profile profile name not found.

Explanation: The profile specified could not be found.


User Response: Check to see if the profile name wasspecified correctly on the command. Use the QUERYPROFILE command to check to see if the profile existson the configuration manager. Reissue the commandwith the correct profile name.

ANR3021I command: Profile profile name copied toprofile profile name.

Explanation: The command has successfully copiedthe first profile to the newly created second profile. Allthe profile associations were also copied.



ANR3022E command: The profile lock timeoutinterval value must be between minimumvalue and maximum value.

Explanation: The specified command has been issuedwith an invalid lock timeout interval.


User Response: Issue the command and specify avalid lock timeout interval value.

ANR3023I command: Profile profile name locked.

Explanation: The command has successfully lockedthe profile. No configuration information can bepropogated to the subscribers of the profile until it isunlocked.



ANR3024W command: Profile profile already lockedwith timeout interval greater thaninterval.

Explanation: An attempt was made to lock thespecified profile. The profile is already locked with atimeout interval greater than the value specifed.

System Action: The profile remains locked with theoriginal timeout interval.

User Response: If you want to lower the timeoutinterval, unlock the profile and then lock the profileagain specifying the lower value.

ANR3025I command: Profile profile name unlocked.

Explanation: The command has successfully unlockedthe profile. Configuration information can now bepropogated to the subscribers of the profile.





ANR3026I command: Profile profile name deleted.

Explanation: The command has successfully deletedthe profile from the configuration manager.



ANR3027E command: One or more subscriptions stillexist to profile profile name.

Explanation: An attempt was made to delete a profilethat still has subscriptions defined on one or moremanaged servers. The configuration manager still has arecord of one or more subscriptions to the profiles.


User Response: Use the QUERY SUBSCRIBERScommand to determine which subscriptions still exist.Use the DELETE SUBSCRIPTION command on themanaged server(s) to delete the subscriptions, and thenreissue the DELETE PROFILE command on theconfiguration manager. Alternatively, the FORCE=YESoption can be used on the DELETE PROFILE commandto delete the profile even if there are subscriptions tothe profile. In this case, messages will be issued whenthe managed server requests updates for that profile,informing the managed server that the profile has beendeleted.

ANR3028E command: Profile profile name is locked.

Explanation: The specifed command cannot beperformed on a locked profile.


User Response: Unlock the profile using theUNLOCK PROFILE command and then reissue thecommand.

ANR3029E command: Profile name not specified.

Explanation: A profile name must be specifed on thiscommand using the PROFILE= parameter.


User Response: Reissue the command and specify aprofile name.

ANR3030I command: Subscription defined forprofile profile name.

Explanation: The command has successfully defined asubscription to the specified profile. A refresh of theconfiguration information has been initiated.



ANR3031W command: Subscription for profile profilename already exists.

Explanation: A subscription already exists for thespecified profile.


User Response: Check to make sure you specified thecorrection profile name, and reissue the command ifneeded.

ANR3032E command: Server name not specified.

Explanation: A server name must be specifed on thiscommand using the SERVER= parameter. Thisidentifies the configuration manager.


User Response: Reissue the command and specify aserver name.

ANR3033E command: Server server is not themanaged server’s configurationmanager.

Explanation: A server name was specified on thecommand which does not match the currentconfiguration manager. A managed server may onlyhave one configuration manager.


User Response: Reissue the command and leave offthe server parameter. It will default to use the currentconfiguration manager. A QUERY SUBSCRIPTION willdisplay the configuration manager currently in use.

ANR3034E command: Server server cannot be used asthis server’s configuration manager.

Explanation: A server name was specified on thecommand which cannot be used as a configurationmanager.


User Response: Find out the currect name for theconfiguration manager and then reissue the command.

ANR3035I command: Subscriber subscriber namedeleted.

Explanation: The command has successfully deleted asubscriber from the record kept in the configurationmanager. If the subscriber (managed server) still has asubscription to a valid profile, the record of the



subscription will reappear when it performs its nextconfiguration refresh.



ANR3036E command: Subscriber subscriber name notfound.

Explanation: The specified subscriber name was notfound in the configuration manager’s records as being avalid subscriber of any profiles.


User Response: Check to see that the subscriber(managed server) name is correction. If you think thename is correct, perhaps the managed server has notyet successfully contacted the configuration manager toinform it that the subscription exists.

ANR3037I command: Subscription deleted forprofile profile name.

Explanation: The command has successfully deleted asubscription for the specified profile. A refresh of theconfiguration information has been initiated.



ANR3038E command: Subscription for profile profilename not found.

Explanation: A subscription was not found for thespecified profile.


User Response: Check to see that the profile namewas specified correctly. Issue the QUERYSUBSCRIPTION command to check to see whichprofiles have subscriptions. Reissue the command withthe correct profile name.

ANR3039E command: No matching administratorsfound in configuration.

Explanation: No administrator definitions were foundon the configuration manager that match the admin(s)specified on the DEFINE PROFASSOCIATIONcommand.


User Response: Use the QUERY ADMIN command tocheck which administrators that are defined on theserver and then reissue to DEFINEPROFASSOCIATION command.

ANR3040I command: All administrators associatedwith profile profilename.

Explanation: The command has successfullyassociated all the administrators with the specifiedprofile. All administrator definitions will beautomatically propogated to managed servers whichsubscribe to the profile. If an administrator is added tothe configuration manager in the future, its definitionwill also be automatically propogated to the managedservers.



ANR3041I command: Administrator admin associatedwith profile profilename.

Explanation: The command has successfullyassociated the administrator with the specified profile.The administrator definition will be automaticallypropogated to managed servers which subscribe to theprofile.



ANR3042W command: No additional administratorsassociated with profile profilename.

Explanation: No additional administrator wereassociated with the profile. The administrator(s)specified are already associated with the profile.


User Response: Use the QUERY ADMIN command tocheck which administrators are defined on the serverand then reissue to DEFINE PROFASSOCIATIONcommand. The QUERY PROFASSOCIATIONFORMAT=DETAILED can be used to see whichadministrators are already associated with the profile.

ANR3043E command: No matching domains foundin configuration.

Explanation: No domain definitions were found onthe configuration manager that match the domain(s)specified on the DEFINE PROFASSOCIATIONcommand.


User Response: Use the QUERY DOMAIN commandto check which domains that are defined on the serverand then reissue to DEFINE PROFASSOCIATIONcommand.



ANR3044I command: All domains associated withprofile profilename.

Explanation: The command has successfullyassociated all the domains with the specified profile.All domain definitions will be automaticallypropogated to managed servers which subscribe to theprofile. If a domain is added to the configurationmanager in the future, its definition will also beautomatically propogated to the managed servers.



ANR3045I command: Domain domain associated withprofile profilename.

Explanation: The command has successfullyassociated the domain with the specified profile. Thedomain definition will be automatically propogated tomanaged servers which subscribe to the profile.



ANR3046W command: No additional domainsassociated with profile profilename.

Explanation: No additional domains were associatedwith the profile. The domain(s) specified are alreadyassociated with the profile.


User Response: Use the QUERY DOMAIN commandto check which domains are defined on the server andthen reissue to DEFINE PROFASSOCIATIONcommand. The QUERY PROFASSOCIATIONFORMAT=DETAILED can be used to see whichdomains are already associated with the profile.

ANR3047E command: No matching admin schedulesfound in configuration.

Explanation: No admin schedule definitions werefound on the configuration manager that match theadmin schedule(s) specified on the DEFINEPROFASSOCIATION command.


User Response: Use the QUERY SCHEDULETYPE=ADMIN command to check which adminschedules are defined on the server and then reissue toDEFINE PROFASSOCIATION command.

ANR3048I command: All admin schedulesassociated with profile profilename.

Explanation: The command has successfullyassociated all the admin schedules with the specifiedprofile. All admin schedule definitions will beautomatically propogated to managed servers whichsubscribe to the profile. If an admin schedule is addedto the configuration manager in the future, itsdefinition will also be automatically propogated to themanaged servers.



ANR3049I command: Admin Schedule admin scheduleassociated with profile profilename.

Explanation: The command has successfullyassociated the admin schedule with the specifiedprofile. The admin schedule definition will beautomatically propogated to managed servers whichsubscribe to the profile.



ANR3050W command: No additional adminscheduless associated with profileprofilename.

Explanation: No additional admin schedules wereassociated with the profile. The admin schedule(s)specified are already associated with the profile.


User Response: Use the QUERY SCHEDULETYPE=ADMIN command to check which adminschedules are defined on the server and then reissue toDEFINE PROFASSOCIATION command. The QUERYPROFASSOCIATION FORMAT=DETAILED can beused to see which admin schedules are alreadyassociated with the profile.

ANR3051E command: No matching scripts found inconfiguration.

Explanation: No script definitions were found on theconfiguration manager that match the script(s) specifiedon the DEFINE PROFASSOCIATION command.


User Response: Use the QUERY SCRIPT command tocheck which scripts that are defined on the server andthen reissue to DEFINE PROFASSOCIATIONcommand.



ANR3052I command: All scripts associated withprofile profilename.

Explanation: The command has successfullyassociated all the scripts with the specified profile. Allscript definitions will be automatically propogated tomanaged servers which subscribe to the profile. If ascript is added to the configuration manager in thefuture, its definition will also be automaticallypropogated to the managed servers.



ANR3053I command: Script script associated withprofile profilename.

Explanation: The command has successfullyassociated the script with the specified profile. Thescript definition will be automatically propogated tomanaged servers which subscribe to the profile.



ANR3054W command: No additional scriptsassociated with profile profilename.

Explanation: No additional scripts were associatedwith the profile. The script(s) specified are alreadyassociated with the profile.


User Response: Use the QUERY SCRIPT command tocheck which scripts are defined on the server and thenreissue to DEFINE PROFASSOCIATION command. TheQUERY PROFASSOCIATION FORMAT=DETAILEDcan be used to see which scripts are already associatedwith the profile.

ANR3055E command: No matching client option setsfound in configuration.

Explanation: No client option set definitions werefound on the configuration manager that match theclient option set(s) specified on the DEFINEPROFASSOCIATION command.


User Response: Use the QUERY CLOPTSET commandto check which client option sets that are defined onthe server and then reissue to DEFINEPROFASSOCIATION command.

ANR3056I command: All client option setsassociated with profile profilename.

Explanation: The command has successfullyassociated all the client option sets with the specifiedprofile. All client option set definitions will beautomatically propogated to managed servers whichsubscribe to the profile. If a client option set is addedto the configuration manager in the future, itsdefinition will also be automatically propogated to themanaged servers.



ANR3057I command: Client option set client optionset associated with profile profilename.

Explanation: The command has successfullyassociated the client option set with the specifiedprofile. The client option set definition will beautomatically propogated to managed servers whichsubscribe to the profile.



ANR3058W command: No additional client optionsets associated with profile profilename.

Explanation: No additional client option sets wereassociated with the profile. The client option set(s)specified are already associated with the profile.


User Response: Use the QUERY CLOPTSET commandto check which client option sets are defined on theserver and then reissue to DEFINEPROFASSOCIATION command. The QUERYPROFASSOCIATION FORMAT=DETAILED can beused to see which client option sets are alreadyassociated with the profile.

ANR3059E command: No matching servers found inconfiguration.

Explanation: No server definitions were found on theconfiguration manager that match the server(s)specified on the DEFINE PROFASSOCIATIONcommand.


User Response: Use the QUERY SERVER command tocheck which servers that are defined on the server andthen reissue to DEFINE PROFASSOCIATIONcommand.



ANR3060I command: All servers associated withprofile profilename.

Explanation: The command has successfullyassociated all the servers with the specified profile. Allserver definitions will be automatically propogated tomanaged servers which subscribe to the profile. If aserver is added to the configuration manager in thefuture, its definition will also be automaticallypropogated to the managed servers.



ANR3061I command: Server server associated withprofile profilename.

Explanation: The command has successfullyassociated the server with the specified profile. Theserver definition will be automatically propogated tomanaged servers which subscribe to the profile.



ANR3062W command: No additional serversassociated with profile profilename.

Explanation: No additional servers were associatedwith the profile. The server(s) specified are alreadyassociated with the profile.


User Response: Use the QUERY SERVER command tocheck which servers are defined on the server and thenreissue to DEFINE PROFASSOCIATION command. TheQUERY PROFASSOCIATION FORMAT=DETAILEDcan be used to see which servers are already associatedwith the profile.

ANR3063E command: No matching server groupsfound in configuration.

Explanation: No server group definitions were foundon the configuration manager that match the servergroup(s) specified on the DEFINE PROFASSOCIATIONcommand.


User Response: Use the QUERY SERVERGROUPcommand to check which server groups that aredefined on the server and then reissue to DEFINEPROFASSOCIATION command.

ANR3064I command: All server groups associatedwith profile profilename.

Explanation: The command has successfullyassociated all the server groups with the specifiedprofile. All server group definitions will beautomatically propogated to managed servers whichsubscribe to the profile. If a server group is added tothe configuration manager in the future, its definitionwill also be automatically propogated to the managedservers.



ANR3065I command: Server group server groupassociated with profile profilename.

Explanation: The command has successfullyassociated the server group with the specified profile.The server group definition will be automaticallypropogated to managed servers which subscribe to theprofile.



ANR3066W command: No additional server groupsassociated with profile profilename.

Explanation: No additional server groups wereassociated with the profile. The server group(s)specified are already associated with the profile.


User Response: Use the QUERY SERVERGROUPcommand to check which server groups are defined onthe server and then reissue to DEFINEPROFASSOCIATION command. The QUERYPROFASSOCIATION FORMAT=DETAILED can beused to see which server groups are already associatedwith the profile.

ANR3067E command: No matching administratorsassociated with profile profile.

Explanation: No matching administrator definitionsare associated with the specified specified profile.


User Response: Use the QUERY PROFASSOCIATIONcommand to check which administrators are associatedwith the profile and then reissue to DELETEPROFASSOCIATION command.



ANR3068I command: All administrator associationsdeleted from profile profilename.

Explanation: The command has successfully deletedall administrators associations from the specifiedprofile. This will automatically delete theseadministrators from the managed servers that aresubscribed to this profile.



ANR3069I command: Administrator associationadmin deleted from profile profilename.

Explanation: The command has successfully deletedan administrator association from the specified profile.This will automatically delete this administrator fromthe managed servers that are subscribed to this profile.



ANR3070E command: No matching domainsassociated with profile profile.

Explanation: No matching domain definitions areassociated with the specified specified profile.


User Response: Use the QUERY PROFASSOCIATIONcommand to check which domains are associated withthe profile and then reissue to DELETEPROFASSOCIATION command.

ANR3071I command: All domain associationsdeleted from profile profilename.

Explanation: The command has successfully deletedall domains associations from the specified profile. Thiswill automatically delete these domains from themanaged servers that are subscribed to this profile.



ANR3072I command: Domain association domaindeleted from profile profilename.

Explanation: The command has successfully deleted adomain association from the specified profile. This willautomatically delete this domain from the managedservers that are subscribed to this profile.



ANR3073E command: No matching admin schedulesassociated with profile profile.

Explanation: No matching admin schedule definitionsare associated with the specified specified profile.


User Response: Use the QUERY PROFASSOCIATIONcommand to check which admin schedules areassociated with the profile and then reissue to DELETEPROFASSOCIATION command.

ANR3074I command: All admin scheduleassociations deleted from profileprofilename.

Explanation: The command has successfully deletedall admin schedules associations from the specifiedprofile. This will automatically delete these adminschedules from the managed servers that are subscribedto this profile.



ANR3075I command: Admin schedule associationadmin schedule deleted from profileprofilename.

Explanation: The command has successfully deletedan admin schedule association from the specifiedprofile. This will automatically delete this adminschedule from the managed servers that are subscribedto this profile.



ANR3076E command: No matching scripts associatedwith profile profile.

Explanation: No matching script definitions areassociated with the specified specified profile.


User Response: Use the QUERY PROFASSOCIATIONcommand to check which scripts are associated withthe profile and then reissue to DELETEPROFASSOCIATION command.

ANR3077I command: All script associations deletedfrom profile profilename.

Explanation: The command has successfully deletedall scripts associations from the specified profile. Thiswill automatically delete these scripts from themanaged servers that are subscribed to this profile.





ANR3078I command: Script association script deletedfrom profile profilename.

Explanation: The command has successfully deleted ascript association from the specified profile. This willautomatically delete this script from the managedservers that are subscribed to this profile.



ANR3079E command: No matching client option setsassociated with profile profile.

Explanation: No matching clent option set definitionsare associated with the specified specified profile.


User Response: Use the QUERY PROFASSOCIATIONcommand to check which client option sets areassociated with the profile and then reissue to DELETEPROFASSOCIATION command.

ANR3080I command: All client option setassociations deleted from profileprofilename.

Explanation: The command has successfully deletedall client option sets associations from the specifiedprofile. This will automatically delete these clientoption sets from the managed servers that aresubscribed to this profile.



ANR3081I command: Client option set associationclient option set deleted from profileprofilename.

Explanation: The command has successfully deleted aclient option set association from the specified profile.This will automatically delete this client option set fromthe managed servers that are subscribed to this profile.



ANR3082E command: No matching serversassociated with profile profile.

Explanation: No matching server definitions areassociated with the specified specified profile.


User Response: Use the QUERY PROFASSOCIATION

command to check which servers are associated withthe profile and then reissue to DELETEPROFASSOCIATION command.

ANR3083I command: All server associations deletedfrom profile profilename.

Explanation: The command has successfully deletedall servers associations from the specified profile. Thiswill automatically delete these servers from themanaged servers that are subscribed to this profile.



ANR3084I command: Server association serverdeleted from profile profilename.

Explanation: The command has successfully deleted aserver association from the specified profile. This willautomatically delete this server definition from themanaged servers that are subscribed to this profile.



ANR3085E command: No matching server groupsassociated with profile profile.

Explanation: No matching server group definitions areassociated with the specified specified profile.


User Response: Use the QUERY PROFASSOCIATIONcommand to check which server groups are associatedwith the profile and then reissue to DELETEPROFASSOCIATION command.

ANR3086I command: All server group associationsdeleted from profile profilename.

Explanation: The command has successfully deletedall server groups associations from the specified profile.This will automatically delete these server groups fromthe managed servers that are subscribed to this profile.



ANR3087I command: Server group association servergroup deleted from profile profilename.

Explanation: The command has successfully deleted aserver group association from the specified profile. Thiswill automatically delete this server group from themanaged servers that are subscribed to this profile.





ANR3088W This command will cause the deletionof objects on any managed serversubscribed to profile profile name.

Explanation: A DELETE PROFASSOCIATIONcommand option has been entered. This action will notonly delete the association from the profile, but it willalso result in the deletion of managed object(s) on anymanaged server subscribing to this profile. The deletionof these objects will occurr during the nextconfiguration refresh for that managed server.


User Response: To process the DELETEPROFASSOCATION command, enter 'Y' to continue or'N' to stop the command.

ANR3089E command: Command failed -Server-to-server communication errorwith server server name.

Explanation: The specified command failed whileattempting to communicate with the indicated server.


User Response: Verify that the indicated server nameis correctly defined. Try reissuing the command. Usethe server PING command to see if the other server isup. If the problem persists, consult with your networkadministrator.

ANR3090E command: Server server name is not aconfiguration manager.

Explanation: The specified command failed because ittried to contact the specified server, and discovered thatthe server is not a configuration manager.


User Response: Reissue the command and specify acorrect configuration manager name.

ANR3091E command: Profile list not specified.

Explanation: The specified command failed becauseyou did not specify a profile list on the command.


User Response: Reissue the command specifying aprofile list.

ANR3092I command: Subscriber notificationprocessing has begun.

Explanation: A NOTIFY SUBSCRIBER process hasbegun. The managed server(s) are being contacted,asking them to immediately perform a configurationrefresh.

System Action: Server operation continues. Thecommand succeeded.


ANR3093I command: No matching profiles orsubscriptions were found.

Explanation: No subscriptions were found for theprofiles specified. Either the profiles do not exist, orthere are no subscriptions to the profiles.


User Response: Use the QUERY PROFILE andQUERY SUBSCRIBER command to determine whichprofiles exist and which profiles have subscribers.Reissue the command specifying the correct profilename(s).

ANR3150E Configuration refresh failed withconfiguration manager server name. Willretry in minutes minutes.

Explanation: While receiving configurationinformation from the specified configuration manager,processing failed because of a communications error.

System Action: Server operation continues. Theconfiguration refresh process was stopped and will beautomatically retried.

User Response: Perhaps the configuration manager isnot active. If the problem continues, contact theadministrator for the configuration manager, or contacta network administrator. The refresh will automaticallyretry several times and then give up until theconfiguration refresh interval is reached again.

ANR3151E Configuration refresh failed withconfiguration manager server name.

Explanation: While receiving configurationinformation from the specified configuration manager,processing failed.

System Action: Server operation continues. Theconfiguration refresh process was stopped.

User Response: Examine the activity log for othermessages that may explain why the configurationrefresh failed. The refresh will attempted again whenthe configuration refresh interval is reached.



ANR3152I Configuration refresh started withconfiguration manager server name.

Explanation: Configuration refresh processing hasstarted. A server-to-server session was opened toreceive configuration information from theconfiguration manager. Updates will be sent for objectsassociated with any subscribed-to profiles.

System Action: Refresh processing continues.


ANR3153I Configuration refresh endedsuccessfully with configuration managerserver name.

Explanation: Configuration refresh processing endedsuccessfully. All updates have been made to managedobjects associated with any subscribed-to profiles.

System Action: Server processing continues. The nextautomatic refresh will start when the configurationrefresh interval is reached.


ANR3154E Communication error on notify tomanaged server server name. Will retry inminutes minutes.

Explanation: While attempting a notify subscriberrequest to the specified managed server, acommunications error was detected.

System Action: Server operation continues. The notifysubscriber request was stopped and will beautomatically retried.

User Response: Perhaps the managed server is notactive. If the problem continues, contact theadministrator for the managed server, or contact anetwork administrator. The notify subscriber requestwill automatically retry several times and then give up.

ANR3155E Error attempting notify subscribersrequest to managed server server.

System Action: Server operation continues. The notifysubscriber request failed.

User Response: Examine the activity log for othermessages that may explain why the notify subscriberrequest failed.

ANR3156E Configuration refresh failed formanaged server server name.

Explanation: While sending configuration informationto the specified managed server, processing failed.

System Action: Server operation continues. Theconfiguration refresh process ended.

User Response: Examine the activity log of both the

managed server and the configuration manager forother messages that may explain why the configurationrefresh failed. The refresh will attempted again by themanaged server when its configuration refresh intervalis reached.

ANR3157I Configuration refresh started formanaged server server name.

Explanation: Configuration refresh processing hasstarted. A server to server session was opened by themanaged server to receive configuration informationfrom the configuration manager. Updates will be sentfor objects associated with any subscribed-to profiles.

System Action: Refresh processing continues.


ANR3158I Configuration refresh endedsuccessfully for managed server servername.

Explanation: Configuration refresh processing endedsuccessfully. All updates have been made to managedobjects associated with any subscribed-to profiles onthe managed server.



ANR3159E Managed server server name has newerversion for profile profile name.

Explanation: While sending configuration informationto the specified managed server, it has been detectedthat the managed server has a newer version ofconfiguration information for the specified profile thandoes the configuration manager. This condition canhappen if the configuration manager’s database hasbeen restored to an earlier point in time. Anotherpossibility is that the profile was deleted on theconfiguration manager and a new profile by the samename was created.

System Action: Server operation continues. Noconfiguration information for this profile will be sent tothe managed server until this condition is corrected.

User Response: Before correcting the situation, youmay want to use QUERY PROFILE to examine theprofile associations defined on both the configurationmanager and the managed server. To correct thesituation, on the managed server delete thesubscription to the profile and define the subscriptionagain. This will cause the managed server to berefreshed at the configuration manager’s current level.



ANR3160E Unable to receive confirmation ofrefresh from managed server server name.

Explanation: While sending configuration informationto the specified managed server, a communication erroroccurred when trying to receive confirmation from themanaged server that information was processedsuccessfully.

System Action: Server operation continues.Configuration refresh processing ended.

User Response: Determine if communication can beestablished with the managed server by using theserver PING command. Use the NOTIFYSUBSCRIBERS command to force the configurationrefresh to retry.

ANR3161E Premature end of configuration refreshfor managed server server server name.

Explanation: While sending configuration informationto the specified managed server, processing endedprematurely because of on error.


User Response: Examine the activity log on themanaged server for any error messages that mightexplain why the refresh failed. Use the NOTIFYSUBSCRIBERS command on the configuration managerto force the configuration refresh to retry.

ANR3162E Managed server server name abortedconfiguration refresh processing due toa low memory condition.

Explanation: While sending configuration informationto the specified managed server, processing endedprematurely because of a low memory condition on themanaged server.


User Response: Make more memory available to themanaged server.

ANR3163E Managed server server name abortedconfiguration refresh processing due toan internal error.

Explanation: While sending configuration informationto the specified managed server, processing endedprematurely because of an internal error on themanaged server.


User Response: Examine the activity log of themanaged server for messages that explain the cause ofthe internal error.

ANR3164E Managed server server name abortedconfiguration refresh processing due toa lock conflict.

Explanation: While sending configuration informationto the specified managed server, processing endedprematurely because of a lock conflict on the managedserver.


User Response: Use the NOTIFY SUBSCRIBERScommand to retry the configuration refresh. If thisproblem persists, contact your service representative.

ANR3165E Managed server server name abortedconfiguration refresh processing due toa protocol error.

Explanation: While sending configuration informationto the specified managed server, processing endedprematurely because of a protocol error detected on themanaged server.


User Response: Use the NOTIFY SUBSCRIBERScommand to retry the configuration refresh. If thisproblem persists, contact your service representative.

ANR3166E Unable to receive configuration refreshinformation from server server name.

Explanation: While receiving configurationinformation from the specified configuration manager,processing ended prematurely because of acommunications error.


User Response: Use the server PING command to seeif the configuration manager can be reached. If theproblem persists, contact your network administrator.

ANR3167E Configuration manager server nameaborted configuration refresh processingdue to a low memory condition.

Explanation: While receiving configurationinformation from the specified configuration manager,processing ended prematurely because of a lowmemory condition on the configuration manager.


User Response: Notify the administrator of theconfiguration manager.



ANR3168E Configuration manager server nameaborted configuration refresh processingdue to an internal error.

Explanation: While receiving configurationinformation from the specified configuration manager,processing ended prematurely because of an internalerror on the configuration manager.


User Response: Examine the activity log of theconfiguration manager for messages that explain thecause of the internal error.

ANR3169E Configuration manager server nameaborted configuration refresh processingdue to a lock conflict.

Explanation: While receiving configurationinformation from the specified managed server,processing ended prematurely because of a lock conflicton the configuration manager.


User Response: Retry the configuration refresh byissuing the SET CONFIGREFRESH command (usingthe current refresh interval value). If this problempersists, contact your service representative.

ANR3170E Configuration manager server nameaborted configuration refresh processingdue to a protocol error.

Explanation: While receiving configurationinformation from the specified configuration manager,processing ended prematurely because of a protocolerror detected on the configuration manager.


User Response: Retry the configuration refresh byissuing the SET CONFIGREFRESH command (usingthe current refresh interval value). If this problempersists, contact your service representative.

ANR3171E Configuration refresh withconfiguration manager server name hadto skip processing for one or moreobjects.

Explanation: While receiving configurationinformation from the specified configuration manager,it became necessary to skip the creation or deletion ofone or more objects.


User Response: Examine the managed server’s

activity log for earlier messages that identfy the object,and take the actions identified in those messages.Configuration refresh processing will not completesuccessfully until the problem is clear up.

ANR3172W Subscription exists for deleted profileprofile name.

Explanation: While receiving configurationinformation from the configuration manager, it hasbeen detected that the managed server has asubscription to an profile that no longer exists on theconfiguration manager. This condition can exist becausethe profile was deleted with FORCE=YES on theconfiguration manager. This out-of-synch condition canalso occur because one of the server’s database wasregressed because of a restore db.


User Response: The DELETE SUBSCRIPTIONcommand is used to correct this situation. You need todecide if you want the managed objects to remain onthe server. If you want them to be deleted, specifyDISCARD=YES. If you want the objects to remain onthe managed server as local objects, specifyDISCARD=NO.

ANR3173E Server has newer version for profileprofile name than the configurationmanager server name.

Explanation: While receiving configurationinformation from the configuration manager, it hasbeen detected that the managed server has a newerversion of configuration information for the specifiedprofile than does the configuration manager. Thiscondition can happen if the configuration manager’sdatabase has been restored to an earlier point in time.Another possibility is that the profile was deleted onthe configuration manager with FORCE=YES and anew profile by the same name was created.

System Action: Server operation continues. Noconfiguration information for this profile will be sent tothe managed server until this condition is corrected.

User Response: Before correcting the situation, youmay want to use QUERY PROFILE to examine theprofile associations defined on both the configurationmanager and the managed server. To correct thesituation, on the managed server delete thesubscription to the profile and define the subscriptionagain. This will cause the managed server to berefreshed at the configuration manager’s current level.

ANR3174E Communication error with managedserver server name.

Explanation: While receiving or sending informationto the specified managed server, a communcations errorwas experienced.



System Action: Server operation continues. Theoperation in progress fails.

User Response: If this error happens often, consultwith your network administrator. Also check to see thatthe managed server is up.

ANR3175W Profile profile name is locked and couldnot be refreshed from configurationmanager server name.

Explanation: While receiving configuration refreshinformation from the specified managed server, it wasdetected that a subscribed-to profile is locked.

System Action: Server operation continues. Refreshprocessings skips over this profile.

User Response: Normally, the profile will later beunlocked automatically, or by an administrator. If youthink that it should not be locked, have ask theconfiguration manager admin to unlock it using theUNLOCK PROFILE command.

ANR3176W Profile profile name is locked and couldnot be refreshed for managed serverserver name.

Explanation: While sending configuration refreshinformation to the specified managed server, it wasdetected that a subscribed-to profile is locked.

System Action: Server operation continues. Refreshprocessings skips over this profile.

User Response: If the profile should no longer belocked, use the UNLOCK PROFILE command tounlock it.

ANR3177W Server level does not support object inprofile profile name.

Explanation: While receiving configuration refreshinformation from the configuration manager, an objectwas received that is not supported on this managedserver.

System Action: Server operation continues. Refreshprocessings skips over this object. The refresh for theprofile fails.

User Response: The configuration manager is at ahigher release level than the managed server. Themanaged server subscribed to a profile that contains anunsupported object. Delete the subscription to thisprofile until service can be applied to the server tobring it to a higher release level.

ANR3200E command: Command cannot be executed- domain domain name is a managedobject.

Explanation: The specified command cannot beexecuted because it would alter the contents of the

indicated managed domain. With the exception ofpolicy set activation, a managed domain can only bemodified using configuration information propagatedfrom the configuration manager.



ANR3201E command: Domain domain name is amanaged object and cannot be deleted.

Explanation: The indicated domain is a managedobject and cannot be deleted on the managed server.


User Response: To delete this object, you can deletethe subscription to the configuration profiles withwhich domain domain name is associated.

ANR3202E command: Domain domain name is amanaged object and cannot be updated.

Explanation: The indicated domain is a managedobject and cannot be updated on the managed server.


User Response: To update this object, you can deletethe subscription to the configuration profiles withwhich domain domain name is associated.

ANR3203E command: Policy set set name in domaindomain name is a managed object andcannot be deleted.

Explanation: The indicated policy set is a managedobject and cannot be deleted on the managed server.



ANR3204E command: Policy set set name in domaindomain name is a managed object andcannot be updated.

Explanation: The indicated policy set is a managedobject and cannot be updated on the managed server.





ANR3205E command: Management class class name indomain domain name, policy set set nameis a managed object and cannot bedeleted.

Explanation: The indicated management class is amanaged object and cannot be deleted on the managedserver.



ANR3206E command: Management class class name indomain domain name, policy set set nameis a managed object and cannot beupdated.

Explanation: The indicated management class is amanaged object and cannot be updated on themanaged server.



ANR3207E command: Backup copy group group namein domain domain name, policy set setname, management class class name is amanaged object and cannot be deleted.

Explanation: The indicated backup copy group is amanaged object and cannot be deleted on the managedserver.



ANR3208E command: Archive copy group group namein domain domain name, policy set setname, management class class name is amanaged object and cannot be deleted.

Explanation: The indicated archive copy group is amanaged object and cannot be deleted on the managedserver.



ANR3209E command: Backup copy group group namein domain domain name, policy set setname, management class class name is amanaged object and cannot be updated.

Explanation: The indicated backup copy group is amanaged object and cannot be updated on themanaged server.



ANR3210E command: Archive copy group group namein domain domain name, policy set setname, management class class name is amanaged object and cannot be updated.

Explanation: The indicated archive copy group is amanaged object and cannot be updated on themanaged server.



ANR3211E command: Client schedule schedule namein domain domain name is a managedobject and cannot be deleted.

Explanation: The indicated client schedule is amanaged object and cannot be deleted on the managedserver.



ANR3212E command: Client schedule schedule namein domain domain name is a managedobject and cannot be updated.

Explanation: The indicated client schedule is amanaged object and cannot be updated on themanaged server.





ANR3213E command: Administrative scheduleschedule name is a managed object andcannot be deleted.

Explanation: The indicated administrative schedule isa managed object and cannot be deleted on themanaged server.


User Response: To delete this object, you can deletethe subscription to the configuration profiles withwhich the object is associated.

ANR3214E command: Administrative scheduleschedule name is a managed object andcannot be updated, except to activate ordeactivate the schedule.

Explanation: The indicated administrative schedule isa managed object and cannot be updated on themanaged server, except to change the active state of theschedule.


User Response: To update this object, you can deletethe subscription to the configuration profiles withwhich the object is associated.

ANR3215W Managed domain domain name containsat least one node and cannot bediscarded.

Explanation: This message is issued while processinga DELETE SUBSCRIPTION command withDISCARDOBJECTS=YES. The indicated domain cannotbe discarded on the managed server because it stillcontains one or more nodes.

System Action: Domain domain name is not deleted.Policy sets, management classes, copy groups, andclient schedules belonging to this domain are also notdeleted.

User Response: Before this domain can be deleted,nodes in the domain must be removed or assignedanother domain.

ANR3216W Managed administrative scheduleschedule name is active and cannot bediscarded.

Explanation: This message is issued while processinga DELETE SUBSCRIPTION command withDISCARDOBJECTS=YES. The indicated administrativeschedule cannot be discarded on the managed serverbecause it is in the active state.

System Action: Administrative schedule schedule nameis not deleted.

User Response: Before this administrative schedulecan be deleted, it must be deactivated using the UpdateSchedule command.

ANR3217E command: Administrator administratorname is a managed object and cannot beremoved.

Explanation: The indicated administrator is amanaged object and cannot be removed on themanaged server.


User Response: To remove this administrator, you candelete the subscription to the configuration profileswith which the object is associated.

ANR3218E command: Administrator administratorname is a managed object and cannot beupdated.

Explanation: The indicated administrator is amanaged object and cannot be updated on themanaged server.


User Response: To update this administrator, you candelete the subscription to the configuration profileswith which the object is associated.

ANR3219E command: Administrator administratorname is a managed object and cannot berenamed.

Explanation: The indicated administrator is amanaged object and cannot be renamed on themanaged server.


User Response: To rename this administrator, you candelete the subscription to the configuration profileswith which the object is associated.

ANR3220E command: Administrator administratorname is a managed object - authoritycannot be granted.

Explanation: The indicated administrator is amanaged object. Authority cannot be granted to thisadministrator on the managed server.


User Response: To grant authority to thisadministrator, you can delete the subscription to theconfiguration profiles with which the object isassociated.



ANR3221E command: Administrator administratorname is a managed object - authoritycannot be revoked.

Explanation: The indicated administrator is amanaged object. Authority of this administrator cannotbe revoked on the managed server.


User Response: To revoke authority of thisadministrator, you can delete the subscription to theconfiguration profiles with which the object isassociated.

ANR3222W Managed administrator administratorname is the only system administratorand cannot be discarded.

Explanation: This message is issued while processinga DELETE SUBSCRIPTION command withDISCARDOBJECTS=YES. The indicated administratorcannot be discarded on the managed server because itis the only system administrator.

System Action: Administrator administrator name isnot deleted.

User Response: Before this administrator can bedeleted, another administrator must be given systemauthority.

ANR3223W Managed administrator administratorname is currently accessing the serverand cannot be discarded.

Explanation: This message is issued while processinga DELETE SUBSCRIPTION command withDISCARDOBJECTS=YES. The indicated administratorcannot be discarded on the managed server because ithas an active session with the server.

System Action: Administrator administrator name isnot deleted.

User Response: Quit or cancel all sessions for thisadministrator before discarding the administratordefinition.

ANR3224E command: Command script commandscript name is a managed object andcannot be deleted.

Explanation: The indicated command script is amanaged object and cannot be deleted on the managedserver.


User Response: To delete this script, you can deletethe subscription to the configuration profiles withwhich the object is associated.

ANR3225E command: Command script commandscript name is a managed object andcannot be updated.

Explanation: The indicated command script is amanaged object and cannot be updated on themanaged server.


User Response: To update this script, you can deletethe subscription to the configuration profiles withwhich the object is associated.

ANR3226E command: Command script commandscript name is a managed object andcannot be renamed.

Explanation: The indicated command script is amanaged object and cannot be renamed on themanaged server.


User Response: To rename this script, you can deletethe subscription to the configuration profiles withwhich the object is associated.

ANR3227E command: Option set optionset name is amanaged object and cannot be deleted.

Explanation: The indicated option set is a managedobject and cannot be deleted on the managed server.


User Response: To delete this option set, you candelete the subscription to the configuration profileswith which the object is associated.

ANR3228E command: Option set optionset name is amanaged object and cannot be updated.

Explanation: The indicated option set is a managedobject and cannot be updated on the managed server.


User Response: To update this option set, you candelete the subscription to the configuration profileswith which the object is associated.

ANR3229E command: Command cannot be executed- option set optionset name is a managedobject.

Explanation: The specified command cannot beexecuted because it would alter the contents of theindicated managed option set.





ANR3230E command: Server group group name is amanaged object and cannot be deleted.

Explanation: The indicated server group is a managedobject and cannot be deleted on the managed server.


User Response: To delete this server group, you candelete the subscription to the configuration profileswith which the object is associated.

ANR3231E command: Server group group name is amanaged object and cannot be updated.

Explanation: The indicated server group is a managedobject and cannot be updated on the managed server.


User Response: To update this server group, you candelete the subscription to the configuration profileswith which the object is associated.

ANR3232E command: Server group group name is amanaged object and cannot be renamed.

Explanation: The indicated server group is a managedobject and cannot be renamed on the managed server.


User Response: To rename this server group, you candelete the subscription to the configuration profileswith which the object is associated.

ANR3233E command: Command cannot be executed- server group group name is a managedobject.

Explanation: The specified command cannot beexecuted because it would alter the membership of theindicated managed server group.



ANR3234E command: Server server name is amanaged object and cannot be deleted.

Explanation: The indicated server is a managed objectand cannot be deleted on the managed server.


User Response: To delete this object, you can deletethe subscription to the configuration profiles withwhich the object is associated.

ANR3235E command: Server server name is amanaged object - one or more specifiedattributes cannot be updated.

Explanation: Because the indicated server is amanaged object, certain attributes cannot be updatedon the managed server. These attributes are:SERVERPASSWORD, HLADDRESS, LLADDRESS,COMMMETHOD, DESCRIPTION, URL, andALLOWREPLACE.


User Response: You can restrict the update toattributes that can be updated on the managed server.For example, the PASSWORD, NODENAME,FORCESYNC, and DELGRACEPERIOD attributes canbe updated, even if the server is a managed object.Alternatively, you can delete the subscription to theconfiguration profiles with which the object isassociated, so that the server is no longer a managedobject.

ANR3236W Server server name is currently in useand cannot be discarded.

Explanation: This message is issued while processinga DELETE SUBSCRIPTION command withDISCARDOBJECTS=YES. The indicated server cannotbe discarded on the managed server because servername is in use. This could occur if the managed serverhas an active connection to server name or if themanaged server has a device class withDEVTYPE=SERVER that refers to server name.

System Action: Server server name is not deleted.

User Response: Before server name can be deleted, themanaged server must not have a connection to thatserver and the managed server cannot have anydevice-class references to that server.

ANR3237W Server server name is the event serverand cannot be discarded.

Explanation: This message is issued while processinga DELETE SUBSCRIPTION command withDISCARDOBJECTS=YES. The indicated server cannotbe discarded because it is the event server for themanaged server.

System Action: Server server name is not deleted.

User Response: Before server name can be deleted, theDELETE EVENTSERVER command must be used toremove the event server reference to server name.



ANR3238E command: This object cannot be renamedbecause it is associated with one ormore configuration profiles.

Explanation: This message is issued on aconfiguration manager when an attempt is made torename an object that is associated with one or moreconfiguration profiles. Associated objects cannot berenamed because the enterprise configuration facilitydoes not support renaming of objects.


User Response: If you must change the object nameyou can delete the object, define it with a new name,and then define a profile association to the new object(unless a wildcard profile association already exists).This will cause the object to be deleted and re-definedon managed servers with subscriptions to the profileswith which this object is associated.

ANR3350W Locally defined domain domain namecontains at least one node and cannot bereplaced with a definition from theconfiguration manager.

Explanation: During configuration refresh processingthe indicated locally defined domain could not bereplaced with a definition from the configurationmanager. The domain definition was not replacedbecause the domain still contains one or more assignednodes.

System Action: Refresh processing continues, but thisdomain is not replaced. The system will attempt toreplace the local domain during later configurationrefresh operations.

User Response: If you want existing nodes to beassigned to the domain from the configurationmanager, you can temporarily assign them to anotherdomain. After the domain definition has successfullybeen propagated from the configuration manager,reassign the nodes to the new domain. Alternatively, ifyou want to prevent further attempts to replace thelocal domain definition during configuration refreshprocessing, delete the subscription to the profiles withwhich domain domain name is associated.

ANR3351W Managed domain domain name containsat least one node and cannot be deletedduring configuration refresh processing.

Explanation: During configuration refresh processing,the enterprise configuration facility attempted toremove the indicated domain because it has beendeleted from the configuration manager or because theprofile association no longer exists. The domain couldnot be deleted on the managed server because it stillcontains one or more nodes.

System Action: Refresh processing continues, but this

domain is not deleted. The system will attempt todelete the domain during later configuration refreshoperations.

User Response: Assign nodes in this domain toanother domain. Alternatively, you can delete thesubscription to the profiles with which domain domainname is associated.

ANR3352I Locally defined domain domain namereplaced during configuration refreshprocessing.

Explanation: During configuration refresh processing,a local domain definition was replaced with adefinition from the configuration manager. The systemalso deleted all policy sets, management classes, copygroups, and client schedules belonging to the locallydefined domain and added definitions from theconfiguration manager.



ANR3353I Managed domain domain name deletedduring configuration refresh processing.

Explanation: During configuration refresh processing,the indicated managed domain was removed from themanaged server. This occurred either because thedomain has been deleted from the configurationmanager or because the profile association no longerexists. The system also deleted all policy sets,management classes, copy groups, and client schedulesbelonging to the managed domain.



ANR3354W Locally defined administrative scheduleschedule name is active and cannot bereplaced with a definition from theconfiguration manager.

Explanation: During configuration refresh processingthe indicated locally defined administrative schedulecould not be replaced with a definition from theconfiguration manager. The schedule definition was notreplaced because the schedule is in the active state.

System Action: Refresh processing continues, but thisadministrative schedule is not replaced. The systemwill attempt to replace the local administrativeschedule during later configuration refresh operations.

User Response: If you want this administrativeschedule to be replaced with the schedule definitionfrom the configuration manager, deactivate the localschedule using the Update Schedule command. Afterthe administrative schedule definition has successfullybeen propagated from the configuration manager, youcan activate the new schedule. Alternatively, if you



want to prevent further attempts to replace the localschedule definition during configuration refreshprocessing, delete the subscription to the profiles withwhich the schedule name is associated.

ANR3355W Managed administrative scheduleschedule name is active and cannot bedeleted during configuration refreshprocessing.

Explanation: During configuration refresh processing,the enterprise configuration facility attempted toremove the indicated administrative schedule because ithas been deleted from the configuration manager orbecause the profile association no longer exists. Theschedule could not be deleted on the managed serverbecause the schedule is in the active state.

System Action: Refresh processing continues, but thisschedule is not deleted. The system will attempt todelete the administrative schedule during laterconfiguration refresh operations.

User Response: If you want this administrativeschedule to be deleted in accordance with changes thathave been made on the configuration manager,deactivate the managed schedule using the UpdateSchedule command. Alternatively, if you want toprevent further attempts to delete the managedschedule definition during configuration refreshprocessing, delete the subscription to the profiles withwhich the schedule name is associated.

ANR3356I Locally defined administrative scheduleschedule name replaced duringconfiguration refresh processing.

Explanation: During configuration refresh processing,a local administrative schedule definition was replacedwith a definition from the configuration manager.



ANR3357I Managed administrative scheduleschedule name deleted duringconfiguration refresh processing.

Explanation: During configuration refresh processing,the indicated managed administrative schedule wasremoved from the managed server. This occurred eitherbecause the schedule has been deleted from theconfiguration manager or because the profileassociation no longer exists.



ANR3358W Locally defined administratoradministrator name is the only systemadministrator and cannot be replacedwith a definition from the configurationmanager.

Explanation: During configuration refresh processingthe indicated locally defined administrator could not bereplaced with a definition from the configurationmanager. The administrator definition was not replacedbecause it is the only system administrator and thedefinition from the configuration manager does notinclude system authority.

System Action: Refresh processing continues, but thisadministrator definition is not replaced. The systemwill attempt to replace the local administratordefinition during later configuration refresh operations.

User Response: If you want this administratordefinition to be replaced with a definition from theconfiguration manager, you can grant system authorityto another administrator. Alternatively, if you want toprevent further attempts to replace the localadministrator definition during configuration refreshprocessing, delete the subscription to the profiles withwhich administrator administrator name is associated.

ANR3359W Managed system administratoradministrator name is the only systemadministrator and cannot be deletedduring configuration refresh processing.

Explanation: During configuration refresh processing,the enterprise configuration facility attempted toremove the indicated administrator because it has beendeleted from the configuration manager or because theprofile association no longer exists. The administratorcould not be deleted on the managed server because itis the only system administrator.

System Action: Refresh processing continues, but thisadministrator is not deleted. The system will attempt todelete the administrator during later configurationrefresh operations.

User Response: Grant system authority to anotheradministrator. Alternatively, you can delete thesubscription to the profiles with which administratoradministrator name is associated.

ANR3360W Managed system administratoradministrator name is the only systemadministrator - authority cannot berevoked during configuration refreshprocessing.

Explanation: During configuration refresh processing,the enterprise configuration facility attempted to revokeauthority for the indicated administrator becauseauthority has been revoked on the configurationmanager. The authority of the administrator could not



be revoked on the managed server because this is theonly system administrator.

System Action: Refresh processing continues, butauthority is not revoked for this administrator. Thesystem will attempt to revoke administrator duringlater configuration refresh operations.

User Response: Grant system authority to anotheradministrator. Alternatively, you can delete thesubscription to the profiles with which administratoradministrator name is associated.

ANR3361I Locally defined administratoradministrator name replaced duringconfiguration refresh processing.

Explanation: During configuration refresh processing,a local administrator definition was replaced with adefinition from the configuration manager.



ANR3362I Managed administrator administratorname deleted during configurationrefresh processing.

Explanation: During configuration refresh processing,the indicated managed administrator was removedfrom the managed server. This occurred either becausethe administrator has been deleted from theconfiguration manager or because the profileassociation no longer exists.



ANR3363W Managed administrator administratorname is currently accessing the serverand cannot be deleted duringconfiguration refresh processing.

Explanation: During configuration refresh processing,the enterprise configuration facility attempted toremove the indicated administrator because it has beendeleted from the configuration manager or because theprofile association no longer exists. The administratorcould not be deleted on the managed server because itcurrently has an active session with the server.

System Action: Refresh processing continues, but thisadministrator is not deleted. The system will attempt todelete the administrator during later configurationrefresh operations.

User Response: Quit or cancel all sessions for theindicated administrator. Alternatively, you can deletethe subscription to the profiles with whichadministrator administrator name is associated.

ANR3364W Administrator administrator name hasbeen removed. This administrator hasdefined or updated administrativeschedules that will fail when executed.

Explanation: This message is issued duringconfiguration refresh processing or as a result of aDELETE SUBSCRIPTION command with theDISCARDOBJECTS=YES option. The indicatedmanaged administrator was removed from the server,but this administrator owns one or more administrativeschedules. These schedules will fail when executed inthe future because they do not belong to a validadministrator.

System Action: The indicated administrator wasremoved.

User Response: Use the QUERY SCHEDULEcommand OR an SQL SELECT statement on theADMIN_SCHEDULES table to determine whichschedules were last updated by the administrator. Usethe UPDATE SCHEDULE command to update thoseschedules under an administrator that has authority toexecute them, or use the DELETE SCHEDULEcommand to remove the schedules.

ANR3365I Locally defined command scriptcommand script name replaced duringconfiguration refresh processing.

Explanation: During configuration refresh processing,a local command script definition was replaced with adefinition from the configuration manager.



ANR3366I Managed command script command scriptname deleted during configurationrefresh processing.

Explanation: During configuration refresh processing,the indicated managed command script was removedfrom the managed server. This occurred either becausethe script has been deleted from the configurationmanager or because the profile association no longerexists.



ANR3367I Locally defined option set option set namereplaced during configuration refreshprocessing.

Explanation: During configuration refresh processing,a local option set definition was replaced with adefinition from the configuration manager.





ANR3368I Managed option set option set namedeleted during configuration refreshprocessing.

Explanation: During configuration refresh processing,the indicated managed option set was removed fromthe managed server. This occurred either because theoption set has been deleted from the configurationmanager or because the profile association no longerexists.



ANR3369I Locally defined server group group namereplaced during configuration refreshprocessing.

Explanation: During configuration refresh processing,a local server group definition was replaced with adefinition from the configuration manager.



ANR3370I Managed server group group namedeleted during configuration refreshprocessing.

Explanation: During configuration refresh processing,the indicated managed server group was removed fromthe managed server. This occurred either because theserver group has been deleted from the configurationmanager or because the profile association no longerexists.



ANR3371W Server group group name cannot bedefined during configuration refreshprocessing because a server alreadyexists with this name.

Explanation: During configuration refresh processing,the enterprise configuration facility attempted to definethe indicated server group on a managed server. Theserver group could not be defined because a serverdefinition with the same name already exists on themanaged server.

System Action: Refresh processing continues, but thisserver group is not defined. The system will attempt todefine the server group during later configurationrefresh operations.

User Response: You can delete the subscription to theprofile with which the indicated server group isassociated or delete the conflicting server definition on

the managed server. Alternatively, you can rename theserver group on the configuration manager, after firstdeleting the profile association for that server group.

ANR3372I Locally defined server server namereplaced during configuration refreshprocessing.

Explanation: During configuration refresh processing,a local server definition was replaced with a definitionfrom the configuration manager.



ANR3373I Server server name deleted duringconfiguration refresh processing.

Explanation: During configuration refresh processing,the definition for managed object server name wasremoved from the managed server. This occurred eitherbecause server name has been deleted from theconfiguration manager or because the profileassociation no longer exists.



ANR3374I Server group group name replaced withserver server name during configurationrefresh processing.

Explanation: During configuration refresh processing,a server group definition was replaced with a serverdefinition from the configuration manager. The serverhas the same name as the deleted server group.



ANR3375W Server server name is currently in usecannot be deleted during configurationrefresh processing.

Explanation: During configuration refresh processing,the enterprise configuration facility attempted toremove the indicated server definition because it hasbeen deleted from the configuration manager orbecause the profile association no longer exists. Theindicated server could not be deleted on the managedserver because server name is in use. This could occur ifthe managed server has an active connection to servername or if the managed server has a device class withDEVTYPE=SERVER that refers to server name.

System Action: Refresh processing continues, but thisserver definition is not deleted. The system will attemptto delete the server during later configuration refreshoperations.

User Response: Before server name can be deleted, the



managed server must not have a connection to thatserver and the managed server cannot have anydevice-class references to that server.

ANR3376W Server server name is the event serverand cannot be deleted duringconfiguration refresh processing.

Explanation: During configuration refresh processing,the enterprise configuration facility attempted toremove the indicated server definition because it hasbeen deleted from the configuration manager orbecause the profile association no longer exists. Theindicated server could not be deleted on the managedserver because it is the event server for the managedserver.

System Action: Refresh processing continues, but thisserver definition is not deleted. The system will attemptto delete the server during later configuration refreshoperations.

User Response: Before server name can be deleted, theDELETE EVENTSERVER command must be used toremove the event server reference to server name.

ANR3377W Replacement of local server server namewith a definition from the configurationmanager is not allowed.

Explanation: During configuration refresh processing,the enterprise configuration facility attempted toreplace the indicated server definition with a definitionfrom the configuration manager. This operation couldnot be performed because ALLOWREPLACE=NO forthe indicated server.

System Action: Refresh processing continues, but thisserver definition is not replaced. The system willattempt to replace the server definition during laterconfiguration refresh operations.

User Response: Before the local server definition forserver name can be replaced with a definition from theconfiguration manager, the UPDATE SERVERcommand must be used to set the ALLOWREPLACEattribute to ON.

ANR3470I Command: Auditing enterpriseconfiguration definitions.

Explanation: The server has started to audit databasedefinitions used by the enterprise configuration facility.



ANR3471E Audit command: Enterprise configurationglobal attributes are missing.

Explanation: A database audit process finds that theglobal attributes used by the enterprise configurationfacility are missing.


User Response: Reissue the audit command withFIX=YES specified so that the enterprise configurationglobal attributes can be recreated.

ANR3472I Audit command: Enterprise configurationglobal attributes are missing - attributeswill be recreated using availabledatabase information or default values.

Explanation: A database audit process finds that theglobal attributes used by the enterprise configurationfacility are missing. Because FIX=YES has beenspecified on the AUDIT command, these attributes willbe recreated using available information from thedatabase or default values.


User Response: When the audit completes, you canuse the QUERY STATUS command to examine thevalues set for the enterprise configuration globalattributes. Then use the appropriate SET command tochange the attributes, if desired.

ANR3473E Audit command: Enterprise configurationglobal attribute(s) are incorrect.

Explanation: A database audit process finds thatglobal attributes used by the enterprise configurationfacility are incorrect.


User Response: Reissue the audit command withFIX=YES specified so that the enterprise configurationglobal attributes can be corrected.

ANR3474I Audit command: Enterprise configurationglobal attribute(s) are incorrect -attributes will be corrected usingavailable database information ordefault values.

Explanation: A database audit process finds thatglobal attributes used by the enterprise configurationfacility are incorrect. Because FIX=YES has beenspecified on the AUDIT command, these attributes willbe corrected using available information from thedatabase or default values.


User Response: When the audit completes, you canuse the QUERY STATUS command to examine thevalues set for the enterprise configuration global



attributes. Then use the appropriate SET command tochange the attributes, if desired.

ANR3475E Audit command: Extraneous profileinformation found.

Explanation: A database audit process findsextraneous configuration profile information.


User Response: Reissue the audit command withFIX=YES so that the information is deleted.

ANR3476E Audit command: Extraneous profileinformation found - information will bedeleted.

Explanation: A database audit process findsextraneous configuration profile information. BecauseFIX=YES has been specified for the audit command, theextraneous information will be deleted.



ANR3477E Audit command: Profile information isinconsistent.

Explanation: A database audit process detectsinconsistent configuration profile information. Thisinformation can be corrected.


User Response: Reissue the audit command withFIX=YES so that the information can be corrected.

ANR3478E Audit command: Profile information isinconsistent - it will be corrected.

Explanation: A database audit process detectsinconsistent configuration profile information. BecauseFIX=YES has been specified for the audit command, theinformation will be corrected.



ANR3479E Audit command: Profile associationinformation is missing.

Explanation: A database audit process detects missingprofile association information. This information can berecreated.


User Response: Reissue the audit command withFIX=YES so that the information can be recreated.

ANR3480E Audit command: Profile associationinformation is missing - it will berecreated.

Explanation: A database audit process detects missingprofile association information. Because FIX=YES hasbeen specified for the audit command, the informationwill be recreated.



ANR3481E Audit command: Extraneous profileassociation information found.

Explanation: A database audit process findsextraneous profile association information.


User Response: Reissue the audit command withFIX=YES so that the information is deleted.

ANR3482E Audit command: Extraneous profileassociation information found -information will be deleted.

Explanation: A database audit process findsextraneous profile association information. BecauseFIX=YES has been specified for the audit command, theextraneous information will be deleted.



ANR3483E Audit command: Subscription informationis inconsistent.

Explanation: A database audit process detectsinconsistent profile subscription information. Thisinformation can be corrected.


User Response: Reissue the audit command withFIX=YES so that the information can be corrected.

ANR3484E Audit command: Profile subscriptioninformation is inconsistent - it will becorrected.

Explanation: A database audit process detectsinconsistent profile subscription information. BecauseFIX=YES has been specified for the audit command, theinformation will be corrected.





ANR3485E Audit command: Profile subscriptionswere found to more than oneconfiguration manager.

Explanation: A database audit process determines thata managed server has subscriptions to more than oneconfiguration manager. This may cause the enterpriseconfiguration facility to behave in an unpredictablemanner.


User Response: Delete subscriptions for all but oneconfiguration manager. To do this, it may be necessaryto delete subscriptions to all configuration managersand then define the desired subscriptions.

ANR3500I Backup set for node node name as setname being generated.

Explanation: The named object set is being created forthe specified node.

System Action: The server generates a backup set.


ANR3501I Backup set for node name as set namecompleted successfully - processed filesfiles.

Explanation: The named object set was successfullycreated for the specified node. The number of filesprocessed is specified.



ANR3502W Backup set for node name as set namecompleted with file processing errors -processed files files with error files filesskipped.

Explanation: The named object set was successfullycreated for the specified node. However, duringprocessing errors were encountered accessing some files- these files were skipped.


User Response: Evaluate other server messages for anindication of why the files where skipped. Files can beskipped because of failures locking those files, havingno files to process, or for other more serious problems.First, retry the command and see if it completeswithout any skipped files. If you are unable to generatethe backup set without skipping files, please contactyour local service representative for assistance.

ANR3503E Generation of backup set for node nameas set name failed.

Explanation: The named object for the specified nodewas not created. An error was encountered causing thecreation of this object set not to complete successfully.


User Response: Evaluate other messages that wereissued and try to determine the cause of the failure.After determining the cause of the failure, retry thecommand. If the cause can not be determined, pleasecontact your local service representative.

If ANR3504W was received, than an error occurredwhile logging the volumes used to the server volumehistory. It is possible to issue a DEFINE BACKUPSETlisting these volumes. That would cause the server tocreate the necessary entries for this backup set on thisserver.

ANR3504W Backup set for node name as set name wasnot able to log the volumes used for thisoperation to the server volume history.

Explanation: The named object for the specified nodewas created. However, when the process attempted toadd the volumes, used for this operation to the volumehistory for the server, an error occurred and this couldnot be completed.


User Response: Review other messages issued todetermine which volumes where used for to generatethis backup set. The volumes can be inserted into theserver volume history for use by issuing a DEFINEBACKUPSET and listing these volumes. This will alsoallow this backup set to be queried from a client aswell since there is not a server entry for this backupset. Only issue the DEFINE BACKUPSET if thisgenerate backup set operation completed successfully.

ANR3505I Backup set for node name as set nameused volume volume name.

Explanation: The named object for the specified nodeused the specified volume.




Explanation: This message is displayed in response toa QUERY PROCESS command, and indicates that agenerate backupset process has been canceled. Theprocess will end shortly.

System Action: The process terminates and serveroperation continues.




ANR3508W Generation of backup set for node nameas set name failed - no filespaces toprocess.

Explanation: The named object for the specified nodewas not created. No filespaces were available toprocess.


User Response: Reissue the command against a nodethat has filespaces associated with it. If no filespacesexist for a given node, than there is no file data towrite to the backupset.

ANR3509E Command: Error encountered in accessingdata storage - device class device classname is not defined.

Explanation: During command command processing,an error occurred because the specified device class isnot defined.


User Response: Make sure the specified device class isdefined.

ANR3510E Command: Error encountered in accessingdata storage - disk volume specified.

Explanation: During command command processing,an error occurred because a specified volume is a diskvolume rather than a tape volume.


User Response: Make sure that all volumes specifiedfor the command command are tape volumes.

ANR3511E Command: Error encountered in accessingdata storage - invalid volume namespecified.

Explanation: The server encounters an error inaccessing data storage while processing commandcommand. The error occurred because an attempt hasbeen made to access a volume with an invalid name.



ANR3512E Command: Error encountered in accessingdata storage - insufficient number ofmount points available for removablemedia.

Explanation: During command command processing,the server cannot allocate sufficient mount points.



ANR3513E Command: Output error encountered inaccessing data storage.

Explanation: The command command operation endsbecause an error has been encountered by the server inwriting to a device. Possible reasons include:

v I/O error writing to a device

v No storage space.


User Response: Query the activity log to findmessages preceding this one to determine the cause ofthe error. After the problem is corrected, the commandcan be retried.

ANR3514E Command: Data transfer was interruptedin accessing data storage.

Explanation: The database transaction associated withcommand command operation failed because datatransfer to or from data storage was interrupted by anexternal event.


User Response: Examine the messages issued prior tothis message to determine why the data transfer wasinterrupted. Reissue the command command after theproblem is resolved.


Explanation: During command command processing, avolume cannot be used because it is already defined ina storage pool, or has been previously used by anexport, database dump, or database backup operation(as recorded in the volume history) or is in use byanother process.


User Response: Specify a volume that is not in use ordefined in a storage pool, and that has not beenpreviously used for an export, database dump, ordatabase backup operation as recorded in the servervolume history information. Use the QUERY VOLUMEcommand to display the names of volumes that aredefined to server storage pools. Use the QUERYVOLHISTORY command to display the names ofvolumes that have been used for export, databasedump, or database backup operations.



ANR3516E Command: Out of space on sequentialmedia, scratch media could not bemounted.

Explanation: During command command processing,the process encounters an out-of-space conditionwriting to the sequential media. Command commandends when there is no more space on the sequentialmedia for storing data and SCRATCH=NO has beenspecified on command command.

System Action: Command command processing ends.Server processing continues.

User Response: Reissue the command and specifySCRATCH=YES or specify additional volume names onthe command.

ANR3517E Command: Error encountered in accessingdata storage - required volume was notmounted.

Explanation: During command command processing, arequired volume cannot be mounted. The mountrequest may have been canceled.


User Response: Issue the command again and makesure the necessary volumes are accessible.





ANR3519E Command: Insufficient memory availablein accessing data storage.

Explanation: The server encounters a memoryshortage in accessing data storage during commandcommand operation.



ANR3520E Command: Internal error encountered inaccessing data storage.

Explanation: The server encounters an internal errorin accessing data storage while processing commandcommand operation.


User Response: Use the QUERY ACTLOG commandto examine messages prior to this error to determinethe cause of the data storage failure. If the failure canbe found and resolved, reissue the command commandoperation. If the failure cannot be found, contact yourservice representative for assistance in resolving theproblem.

ANR3521W BackupSet command: Data storage retrieveor restore failed - data integrity errordetected.

Explanation: The server ends an backup set operationbecause an internal database integrity error has beenencountered on the server.

System Action: The server ends the backup setoperation and continues operation.


ANR3522W Command: Retrieve or restore failed - filewas deleted from data storage duringretrieval.

Explanation: The server ends a file retrieval operationfor the specified command because the file has beendeleted from data storage by another process beforeretrieval is complete.

System Action: The server ends the command andcontinues operation.

User Response: Contact your administrator to findout if DELETE FILESPACE, DELETE VOLUME, orinventory expiration processes are running; theseprocesses can delete data storage files during retrieval.Reissue the command after these processes have beencompleted or canceled.

ANR3523W Backup set command: Retrieve failed -error on input storage device.

Explanation: The server ends a backup set operationfor the specified session because an I/O error has beenencountered by the server in reading from a device.The object for which the I/O was issued is reported ina later message.

System Action: Backup set processing skips this file,and continues operation.

User Response: Query the activity log to findmessages preceding this one that specify the device that



is failing. Storage pool volumes can be varied offline(by using the VARY OFFLINE command), or the servermay need to be shut down with the HALT command tocorrect the hardware problem.

ANR3524W Backup set command: Transaction failed -data transfer interrupted.

Explanation: The database transaction associated witha backup set operation failed because data transfer toor from data storage was interrupted by an externalevent.

System Action: The backup set operation is endedand server operation continues.

User Response: Examine the messages issued prior tothis message to determine why the data transfer wasinterrupted. Attempt the backup set operation againafter problem is resolved.

ANR3525W Backup set command: Transaction failed -storage media inaccessible.

Explanation: The server ends a transaction for anbackup set operation because storage volumes are notavailable in the storage pools in which the client filesare to be stored.

System Action: The server ends the backup setoperation and server operation continues.


ANR3526E Backup set command: Error encountered inaccessing data storage - volume cannotbe used.

Explanation: During backup set processing, a volumehas been mounted but cannot be used.

System Action: The backup set operation is endedand server operation continues.

User Response: Query the activity log for messagespreceding this one that give additional information.Make sure a usable volume is specified and mounted.

ANR3527E Backup set command operation terminated- it is acting on an empty volume orvolume content is not as expected.

Explanation: The volume content it is acting on not asexpected or it is an empty volume

System Action: The command operation is ended.

User Response: Issue the command again and make

sure the expected content is in the volumes or thevolume is not empty.

ANR3528E Backup set command: Media not accessiblein accessing data storage.

Explanation: The server ends a transaction for abackup set operation because storage volumes are notavailable in the storage pools in which the client filesare to be stored.

System Action: The server ends the backup setoperation and server operation continues.


ANR3529W Generate backupset skipping damagedfile on volume volume name: Node nodename, Type file type, File space filespacename, fsId filespace id, File name file name.

Explanation: During generate backupset process, a fileis encountered that was previously found to bedamaged. If this file is part of an aggregate, the entireaggregate was previously marked damaged, possiblybecause an integrity error was detected for some otherfile within the aggregate.

System Action: The damaged file is not added to thebackupset.

User Response: Audit the indicated volume withFIX=NO to verify that the file is damaged. The auditwill reset the file status if the file is found to beundamaged during the audit. If the file is part of anaggregate, the audit will reset the aggregate status ifthe entire aggregate is found to be undamaged. If thefile is reset to the undamaged state and it is importantthat the file be included in the backupset, rerun thegenerate backupset command. If, however, the auditdoes not clear the damaged state of the file and if thisvolume is in a primary storage pool that has previouslybeen backed up to a copy storage pool, attempt torestore damaged files by using the RESTORESTGPOOL command. If it is still important that the filebe included in the backupset, rerun the generatebackupset command.

ANR3540E Object set set node:set name was notfound for session session number, node.

Explanation: The indicated session id requested torestore the object set. The object set was not found onthe server.

System Action: The error is returned to the client.




ANR3541E Error error code occurred opening objectset set node:set name for session sessionnumber, node.

Explanation: An error occurred while opening theindicated object set.

System Action: An error is returned to the client.

User Response: Correct the problem reported byprevious messages, if possible.

ANR3542E Error error code occurred reading objectset set node:set name for session sessionnumber, node.

Explanation: An error occurred while reading theindicated object set.


User Response: Correct the problem reported byprevious messages, if possible.

ANR3543E Error error code occurred while sendingentries from object set set node:set namefor session session number, node.

Explanation: An error occurred while sending entriesfor the indicated object set.


User Response: Correct the problem reported by otherprior or subsequent messages related to this session,and try the operation again.

ANR3550E Definition of backup set set name fornode name failed because it has anunknown format.

Explanation: The named object for the specified nodewas not defined. It was generated on a server that is ata higher level than this server and contains data thatcannot be properly interpreted by this server.


User Response: Define the object on a server that iscompatible with the server that generated the object, orupgrade this server to be compatible with the serverthat generated the object.

ANR3601W Policy Domain release failed for domaindomain id due to communications failure.

Explanation: The storage agent was attempting toinform the database server that it was finished with thedomain indicated by the domain id, but was unable tocommunicate with the database server. The cachedpolicy information will be cleaned up when the storageserver terminates or re-starts or when the databaseserver re-starts.

System Action: The storage agent continues operation.

The policy information is deleted from the storageagent policy cache.

User Response: Policy caches are cleaned up on thestorage agent or server re-start. Networkcommunication between the storage agent and databaseserver should be checked.

ANR3602E Unable to communicate with databaseserver.

Explanation: The storage agent was attempting tocommunicate with the database server but was unableto do so.

System Action: The storage agent operation fails.

User Response: Check the configuration of the storageagent and server to ensure that communicationparameters are correct. Ensure that the database serveris running and is accepting messages.

ANR3603E Storage AgentStorage Agent name wasunable to load policy information due toa protocol error.

Explanation: While receiving policy information froma database server, processing ended prematurelybecause of a protocol error.

System Action: Server operation continues. Policy isloaded from the database server database.

User Response: If this problem persists, contact yourservice representative.

ANR3604E This command is not supported in thecurrent operating environment.

Explanation: A command was issued that is validunder most circumstances, but not in the current serverenvironment.


User Response: Issue commands which are allowed inthe current environment.

ANR3605E Unable to communicate with storageagent.

Explanation: The database server was attempting tocommunicate with the storage agent but was unable todo so.

System Action: The database server operation fails.

User Response: Check the configuration of the storageagent and server to ensure that communicationparameters are correct.



ANR3606E The storage agent was communicatingwith the database server on a restorerequest with verb verb name andreceived return code return code.

Explanation: The storage agent and database serverwere coordinating a restore request. Whilecommunicating using the indicated verb ( an internalrequest mechanism between the storage agent anddatabase server ), an unexpected return code wasreceived. The verb name and return code are providedfor Tivoli support personnel.

System Action: Database server and storage agentcontinue. The restore request fails, but may be retriedby the client.

User Response: Check the configuration of the storageagent and server to ensure that communicationparameters are correct. If this problem persists, contactyour service representative.

ANR3607E The storage agent was communicatingwith the client on a restore request withverb verb name and received return codereturn code.

Explanation: The storage agent was communicatingwith a client for a restore request. Whilecommunicating using the indicated verb ( an internalrequest mechanism between the storage agent andclient ), an unexpected return code was received. Theverb name and return code are provided for Tivolisupport personnel.

System Action: Database server and storage agentcontinue. The restore request fails, but may be retriedby the client.

User Response: Check the configuration of the storageagent and client to ensure that communicationparameters are correct. If this problem persists, contactyour service representative.

ANR3608E The storage agent was communicatingwith the database server on a restorerequest. An unexpected request (id verb )was received from the database server.

Explanation: The storage agent and database serverwere coordinating a restore request. Whilecommunicating, the indicated verb ( an internal requestmechanism between the storage agent and databaseserver ), was unexpected. The verb number is providedfor Tivoli support personnel.

System Action: Database server and storage agentcontinue. The restore request may fail, but may beretried by the client.

User Response: If this problem persists, contact yourservice representative.

ANR3609E The storage agent was handling arestore request. A failure occurred instarting a new thread. The return codereturn code from the failing routine maybe useful to Tivoli service.

Explanation: The storage agent was handling a restorerequest. A new thread could not be started. Without thenew thread the request could not be handled.

System Action: Database server and storage agentcontinue. The restore request has failed.

User Response: Ensure that there is sufficient systemmemory for the storage agent to operate properly.Insufficient memory or paging/swap space can causeproblems in starting threads. If this problem persists,contact your service representative.

ANR3610I Domain Identifier domain identifier wasnot found.

Explanation: The server was cleaning up cachedpolicy information after a restore request. A domainwith the indicated identifier was not found in aninternal list.

System Action: Database server and storage agentcontinue.

User Response: No response is required if themessage is the result of starting a storage agent. Thestorage agent requests that the server purge cachedinformation that it was using previously. It is possiblethat information tracking policy caching has becomestale. In this case, no response is required. If themessage occurs without a storage agent connecting tothe server, contact your service representative.

ANR3611E Storage Agent unable to contact server.

Explanation: The storage agent was attempting tocontact the server to start a session or run a command.The storage agent was unable to contact the server tostart a transaction.

System Action: The storage agent continuesprocessing. The server may be down or there may be acommunications problem.

User Response: No response is required if themessage is the result of stopping a server. Ensure thatthe server with which the storage agent communicatesis running and that there is connectivity between thesystems. The server must be restarted before you canstart a new administrator session with the storageagent.



ANR3999E Failure validating database load:expected numRecs records and numBV bitvectors - loaded actNumRecs records andactNumBV bit vectors.

Explanation: The database load process has endedand the number of records, the number of bit vectors,or both the number of records or number of bit vectorsloaded, failed to validate.

System Action: The LOAD DB process completes witha failure. The server database is not in a usable state.

User Response: A number of possible causes exist. Torecover from this situation, first retry the database loadprocess. If the error reoccurs, check the activity log orother system logs to determine if there is a hardware ormedia error. If a hardware or media error exists, correctthe error and retry the load process. If a hardware ormedia error does not exist, it is likely the dump orunload of the server database has encounted an errorsesulting in the dump/unload server database image asbeing unusable or that there is an error in the logic forload db processing. Contact your service representativefor assistance.

ANR4000I Dump command: Database dump processstarted.

Explanation: The database dump process has started.

System Action: The server dumps the contents of thedatabase to a file or removable media.


ANR4001I Dump command: Database dump processcompleted.

Explanation: The database dump process has ended.

System Action: The server completes processing.


ANR4002I Dump command: Database dump processterminated due to error (error indicator).

Explanation: The database dump process has endedprematurely due to an error.

System Action: The server ends dump processing.

User Response: Examine previously issued messagesto determine if an error can be corrected, such as anoutput error. If you cannot resolve the error, contactyour service representative.

ANR4003I Load command: Database load processstarted.

Explanation: The database load process has started.

System Action: The server loads the contents of thedatabase from a file or removable media.


ANR4004I Load command: Database load processcompleted.

Explanation: The database load process has ended.

System Action: The server completes processing.


ANR4005E Load command: Database load processterminated due to error (error indicator).

Explanation: The database load process has endedprematurely due to an error.

System Action: The server ends load processing.

User Response: Examine previously issued messagesto determine if an error can be corrected, such as asyntax error. If you cannot resolve the error, contactyour service representative.

ANR4006I Command: Volume volume number writtenby process is volume name.

Explanation: A sequential data process wrote to thevolume named in the series of one or more volumesthat were used to store output. The volume’s positionin the series in indicated by the volume numberreported.

System Action: The server ends processing.


ANR4007E Command: A transaction error wasencountered in recording volume usagehistory.

Explanation: The command process encounters adatabase transaction error in recording the names of thevolumes used for the process in the server database.

System Action: The server ends processing.

User Response: Examine previously issued messagesto determine if there is an error that can be corrected,such as a syntax error. If you cannot resolve the error,contact your service representative. The volumes usedby the process are valid for the corresponding inputprocess, but are not recorded in sequential volumehistory lists generated by the server.

ANR4008W Load command: Database object objectname does not exist.

Explanation: The database load process attempts todelete a database object, but the object does not exist.

System Action: Database processing continues.




ANR4009E Load command: Database object objectname cannot be deleted because it is inuse by another process.

Explanation: The database load process attempts todelete a database object, but the object is currentlybeing used by another process.

System Action: Database processing ends.

User Response: Reissue the command. If it fails,contact your service representative.

ANR4010E Dump/load command: Database dump/loadprocessing failed - insufficient memory.

Explanation: The database dump/load process failsdue to insufficient memory.

System Action: Database processing ends.

User Response: Allocate additional storage to theserver. There are two ways to do this:

v Increase the size of the server’s virtual machine (forVM), or region size (for MVS). For AIX, ensure thatthere is sufficient paging space. You may also useSMIT to determine if the number of applications iscausing a memory shortage. For OS/2, ensure thatthere is sufficient space for the OS/2 SWAPPER.DATfile. Check your CONFIG.SYS for the SWAPPATHstatement to determine where your SWAPPER.DATfile is located and then determine how much space isleft on the drive.

v Decrease the amount of space allocated to theserver’s database or log buffer pool. To do this,update the value of the BUFPOOLSIZE orLOGPOOLSIZE parameters in the server options fileand restart the server. Note that each page causes anadditional 4K page to be allocated for the specifiedbuffer pool. Reducing the pool sizes requires moreI/O to service the same amount of data; someperformance degradation may result.

ANR4011W Dump command: Database page pagenumber is invalid - it will be skipped.

Explanation: The specified page is invalid, and it willnot be used during dump processing.



ANR4012W Dump command: Database page pagenumber is damaged.

Explanation: The specified database page is damaged;it will not be dumped.



ANR4013I Dump command: Dumped number ofentries database entries (cumulative).

Explanation: This message indicates the number ofdatabase entries that have been dumped so far duringdatabase dump processing.



ANR4014E Load command: The specified inputvolume does not contain a serverdatabase dump.

Explanation: The specified volume does not contain adump created from the database dump command.

System Action: Processing ends.


ANR4015E Load command: Invalid record format(format code) detected.

Explanation: During processing of command loadcommand, an invalid record type is detected whenreading the dumped information from the dumpmedia.


User Response: Examine the server messages issuedprior to this message to determine the source of theerror. On MVS or VM, the LOADDB command syntaxmay be specified by using a ddname or by specifying adevice class name. You must use the same method thatwas used when the database was originally dumped. Ifyou did not, this error message will be displayed. Tryloading the database by using the other method ofsyntax (devclass). If the error cannot be isolated andresolved, contact your service representative.

ANR4016E Load command: Invalid header sequencenumber detected in database dump.Expected expected sequence number; Actualactual sequence number.

Explanation: During processing of command loadcommand, an invalid sequence number is detected whenreading the dumped information from the dumpmedia.


User Response: Examine previously issued servermessages to determine the source of the error. If theerror cannot be isolated and resolved, contact yourservice representative.



ANR4017E Load command: Invalid record type recordtype read from database dump data.

Explanation: The server database load processencounters an invalid record in reading data from thedump media.

System Action: The database load process ends.

User Response: Examine previously issued servermessages to determine the source of the error. If theerror cannot be isolated and resolved, contact yourservice representative.

ANR4018E Load command: Load processing failed -insufficient recovery log space.

Explanation: The load process fails due to insufficientrecovery log space.

System Action: Database load processing ends.

User Response: Reinstall the server and specify alarger recovery log and reissue the database loadcommand.

ANR4019E Load command: Load processing failed -insufficient database space.

Explanation: The load process fails due to insufficientdatabase space.

System Action: Load processing ends.

User Response: Reinstall the server and specify alarger database and reissue the database loadcommand.

ANR4020E Load command: Batch database insertfailed.

Explanation: The database load process fails when itattempts to insert a batch of rows into the database.

System Action: Database load processing ends.

User Response: Examine the messages issued prior tothis one to determine if an error can be corrected. Youmay wish to reinstall the server with a new recoverylog and database and reissue the load command. If theproblem persists, contact your service representative.

ANR4021E Dump/load command: Error (error code)occurred during an open operation.

Explanation: An error occurs while attempting anopen operation on the dump media for a databasedump/load operation.


User Response: Refer to the other displayed messagesto determine why the operation failed; correct theproblem and restart the process.

ANR4022E Dump command: Error (error code)occurred during a write operation.

Explanation: The server database dump processencounters an error while writing to the dump media.

System Action: Server processing continues, the dumpprocessing ends.


ANR4023E Load command: Error (error code) occurredduring a read operation.

Explanation: The server database load processencounters an error reading from the dump media.

System Action: The database load operation ends.


ANR4025I Dumped number of pages database pages,number of bit vectors bit vectors, andnumber of database entries database entries;number of bad pages bad database pageshave been encountered; number of bytescopied.

Explanation: This message is displayed in response toa QUERY PROCESS command executed against anonline database dump process. The message displaysinformation about the progress of the dump.

System Action: Database dump processing continues.

User Response: None. You may cancel the dumpprocess with the CANCEL PROCESS command.

ANR4026I Dump command: Process process number,database dump has completed.

Explanation: The online server database dump processstarted as process process number has completed.

System Action: Database dump processing ends.


ANR4027I Dump command: Process process number,database dump was canceled.

Explanation: The online server database dump processstarted as process process number has been canceledwith the CANCEL PROCESS command.

System Action: Database dump processing ends.




ANR4028I Dump command: Process process number,Database dump terminated due to anerror (error code).

Explanation: The online database dump process hasended prematurely due to an error.

System Action: The server ends dump processing.

User Response: Examine the messages issued prior tothis message to see if an error can be corrected, such asoutput error. If you cannot resolve the error, contactyour service representative.

ANR4029I Dump command: Database checkpointstarted.

Explanation: The database dump process is flushingupdated database pages from the database buffer poolto stable storage so that they can be dumped.

System Action: Database dump processing continues.


ANR4030I Dump command: Database checkpointcompleted.

Explanation: The database dump process has flushedall updated pages from the database buffer pool tostable storage.

System Action: Database load processing continues.


ANR4031I Dump/load command: Copied number ofpages database pages.

Explanation: This message is displayed at the end of aserver database dump or load command to indicate thenumber of database pages copied.

System Action: Database dump or load processingends.


ANR4032I Dump/load command: Copied number ofrecords database records.

Explanation: This message is displayed at the end of aserver database dump or load command to indicate thenumber of database records copied.



ANR4033I Dump/load command: Copied number of bitvectors bit vectors.

Explanation: This message is displayed at the end of aserver database dump or load command to indicate thenumber of database bit vectors copied.



ANR4034I Dump/load command: Encountered numberof bit vectors bad database pages.

Explanation: This message is displayed at the end of aserver database dump or load command to indicate thenumber of invalid database pages that have beenencountered.



ANR4035I Dump/load command: Encountered numberof bit vectors bad database records.

Explanation: This message is displayed at the end of aserver database dump or load command to indicate thenumber of invalid database records that have beenencountered.



ANR4036I Dump/load command: Copied number of bitvectors database entries.

Explanation: This message is displayed at the end of aserver database dump or load command to indicate thenumber of database entries that have been copied.



ANR4037I Dump/load command: number of bit vectorscopied.

Explanation: This message is displayed at the end of aserver database dump or load command to indicate thenumber of bytes that have been copied.





ANR4038I Load command: Loading databaseinformation dumped on dump date atdump time.

Explanation: At the beginning of a server databaseload process, this message indicates the date and timethat the dump took place for the database informationthat is loaded into the server.



ANR4039I Load command: Loaded number of entriesdatabase entries (cumulative).

Explanation: This message indicates the number ofdatabase entries that have been loaded so far duringdatabase load processing.



ANR4040I Audit command: Auditing client node andadministrator definitions.

Explanation: This message is displayed during adatabase audit and indicates that the client node andadministrator definitions are being examined by thedatabase audit process.



ANR4041I Audit command: Node node name isassigned to Domain domain name, butnot verified by server database policyentries.

Explanation: A database audit process finds a nodeassigned to a policy domain that is not recordedproperly in policy database entries.


User Response: If FIX=YES has not been specified forthe audit command, you may want to run thiscommand again, and specify FIX=YES so that the auditprocess can correct the policy domain assignment forthe node.

ANR4042I Audit command: Node node name isassigned to Domain domain name, butnot found in server database policyentries - attempting to assign the nodeto domain domain name.

Explanation: A database audit process finds a nodeassigned to a policy domain that cannot be referencedin database policy entries. Because FIX=YES has beenspecified for the audit command, the audit function

will attempt to correct the policy domain assignmentfor the node.


User Response: When the audit command completes,you may want to check the domain assignment for thisnode, and reassign the node to a different policydomain, if desired.

ANR4043I Audit command: Node node nameassignment failed - will attempt toassign the node to domain domain name.

Explanation: A database audit process finds a nodeassigned to a policy domain that cannot be located indatabase policy entries. Because FIX=YES has beenspecified for the audit command, the audit function isattempting to assign the node to an existing policydomain. The function attempts to assign the node tothe domain name specified.


User Response: When the audit command completes,you may want to check the domain assignment for thisnode, and reassign the node to a different policydomain, if desired.

ANR4044I Audit command: Could not assign Nodenode name to a policy domain; use theUPDATE NODE command to assign apolicy domain for this node.

Explanation: A database audit process cannot find anappropriate policy domain for assigning the specifiednode.


User Response: When the audit command completes,use the UPDATE NODE command to assign thespecified node to an appropriate policy domain.

ANR4045I Audit command: Invalid compressionvalue encountered for node node name.

Explanation: A database audit process encounters aninvalid node compression value for the node indicated.


User Response: If FIX=YES has not been specified forthe audit command, you may want to run thiscommand again, and specify FIX=YES so that the auditprocess can correct the problem.

ANR4046I Audit command: Invalid compressionvalue encountered for node node namethe default value will be set.

Explanation: A database audit process encounters aninvalid node compression value for the node indicated.Because FIX=YES has been specified, the audit function



sets the node’s compression value to the default value.


User Response: If you want the compression value forthe specified node to be set to a value other than thedefault, use the UPDATE NODE command to changethe value after the audit command has completed.

ANR4047I Audit command: Invalid archive deletevalue encountered for node node name.

Explanation: A database audit process encounters aninvalid archive delete permission value for the nodeindicated.



ANR4048I Audit command: Invalid archive deletevalue encountered for node node namethe default value will be set.

Explanation: A database audit process encounters aninvalid archive delete permission value for the nodeindicated. Because FIX=YES has been specified, theaudit function sets the node’s archive delete permissionvalue to the default value.


User Response: If you want the archive delete valuefor the specified node to be set to a value other thanthe default, use the UPDATE NODE command tochange the value after the audit command hascompleted.

ANR4049I Audit command: Invalid backup deletevalue encountered for node node name.

Explanation: A database audit process encounters aninvalid backup delete permission value for the nodeindicated.



ANR4050I Audit command: Invalid backup deletevalue encountered for node node namethe default value will be set.

Explanation: A database audit process encounters aninvalid backup delete permission value for the nodeindicated. Because FIX=YES has been specified, theaudit function sets the node’s backup delete permissionvalue to the default value.


User Response: If you want the backup delete valuefor the specified node to be set to a value other thanthe default, use the UPDATE NODE command tochange the value after the audit command hascompleted.

ANR4051I Audit command: Invalid lock stateencountered for node node name.

Explanation: A database audit process encounters aninvalid lock state value for the node indicated.



ANR4052I Audit command: Invalid lock stateencountered for node node name thenode will be unlocked.

Explanation: A database audit process encounters aninvalid lock state value for the node indicated. BecauseFIX=YES has been specified, the audit function sets thenode’s lock state to unlocked.


User Response: If you want the lock state for thespecified node to be set to a value other than unlocked,use the LOCK NODE command to change the valueafter the audit command has completed.

ANR4053I Audit command: Invalid Node conversionstate encountered for node node name.

Explanation: A database audit process encounters aninvalid Node conversion state value for the nodeindicated.


User Response: If FIX=YES has not been specified forthe audit command, you may want to run thiscommand again, and specify FIX=YES so that the auditprocess can correct the problem. However, next timethis node logs onto the server, the node conversionstate will be reset.

ANR4054I Audit command: Invalid conversion stateencountered for node node name thenode will be reset.

Explanation: A database audit process encounters aninvalid conversion state value for the node indicated.Because FIX=YES has been specified, the audit functionresets the conversion state.





ANR4055I Audit command: Invalid lock stateencountered for administratoradministrator name.

Explanation: A database audit process encounters aninvalid lock state value for the administrator indicated.



ANR4056I Audit command: Invalid lock stateencountered for administratoradministrator name the administrator willbe unlocked.

Explanation: A database audit process encounters aninvalid lock state value for the administrator indicated.Because FIX=YES has been specified, the audit functionsets the administrator’s lock state to unlocked.


User Response: If you want the lock state for thespecified administrator to be set to a value other thanunlocked, use the LOCK ADMIN command to changethe value after the audit command has completed.

ANR4057E Audit command: Administrative globalattributes are missing.

Explanation: A database audit process finds that theglobal attributes used for server administrativeactivities are missing.


User Response: Reissue the audit command withFIX=YES specified so that the administrative globalattributes can be recreated.

ANR4058I Audit command: Administrative globalattributes are missing - default valueswill be used to recreate the attributes.

Explanation: A database audit process finds that theglobal attributes used for server administrativeactivities are missing. Because FIX=YES has beenspecified on the AUDIT command, default attributevalues will be used to recreate the administrative globalattributes.


User Response: When the audit completes, you canuse the QUERY STATUS command to examine thevalues set for the administrative global attributes, anduse the appropriate SET command to change theattributes, if desired.

ANR4059E Audit command: Administrative IDassignments are incorrect.

Explanation: A database audit process finds that theglobal attributes used for server administrativeactivities are incorrect.


User Response: Reissue the audit command withFIX=YES specified so that the administrative globalattributes can be corrected.

ANR4060I Audit command: Administrative IDassignments are incorrect - value(s) willbe corrected.

Explanation: A database audit process finds that theglobal attributes used for server administrativeactivities are incorrect. Because FIX=YES has beenspecified on the AUDIT command, the attribute valuewill be corrected in the server database.



ANR4061E Audit command: Administrative globalattribute(s) are incorrect.

Explanation: A database audit process finds that theglobal attributes used for server administrativeactivities are incorrect.


User Response: Reissue the audit command withFIX=YES specified so that the administrative globalattributes can be corrected.

ANR4062I Audit command: Administrative globalattribute(s) are incorrect - default valueswill be set.

Explanation: A database audit process finds that theglobal attributes used for server administrativeactivities are incorrect. Because FIX=YES has beenspecified on the AUDIT command, default attributevalues will be used to correct the administrative globalattributes.





ANR4063E Audit command: Client node node numbernot found in the server database.

Explanation: A database audit process finds a clientnode reference that is not defined correctly in theserver database.


User Response: If the audit command has not beenissued with FIX=YES specified, reissue the auditfunction specifying FIX=YES so that the error can becorrected.

ANR4064I Audit command: Client node node numbercreated as node node name assigned topolicy domain domain name in the serverdatabase.

Explanation: A database audit process finds a clientnode reference that is not defined correctly in theserver database. Because FIX=YES has been specifiedfor the audit command, the audit function creates anew node definition for the node with the namespecified.


User Response: After the AUDIT commandcompletes, use the QUERY NODE command toexamine the node that was added. Use the RENAMENODE command to rename the corrected node and theUPDATE NODE command to set attributes for thecorrected node, such as its password. You can issue theQUERY FILESPACE command for the node, todetermine which node and platform type wasoriginally represented by the corrected node.

ANR4065E Audit command: Administratoradministrator number not found in theserver database.

Explanation: A database audit process finds anadministrator reference that is not defined correctly inthe server database.


User Response: Reissue the audit command andspecify FIX=YES so that the error can be corrected.

ANR4066I Audit command: Administratoradministrator number not found in theserver database - reference will beremoved.

Explanation: A database audit process finds anadministrator reference that is not defined correctly inthe server database. The invalid reference will beremoved from the database.


User Response: After the audit command completes,

review your administrator definitions with the QUERYADMIN command. You can then use the REGISTERADMIN and UPDATE ADMIN commands to changeany definitions desired.

ANR4067E Audit command: Domain domain namereferenced by an administrator authoritydoes not exist.

Explanation: A database audit process finds a policyadministrator reference to a policy domain that doesnot exist.



ANR4068I Audit command: Policy domain domainname referenced by an administratorauthority does not exist - the authoritywill be removed.

Explanation: A database audit process finds a policyadministrator reference to a policy domain that doesnot exist. Because FIX=YES has been specified, theauthority will be removed.


User Response: After the audit command completes,review your administrator definitions with the QUERYADMIN command. You can then use the REGISTERADMIN, UPDATE ADMIN, and GRANT AUTHORITYcommands to change any definitions.

ANR4069E Audit command: Storage pool storage poolname referenced by an administratorauthority does not exist.

Explanation: A database audit process finds a storageadministrator reference to a storage pool that does notexist.



ANR4070I Audit command: Storage pool storage poolname referenced by an administratorauthority does not exist - the authoritywill be removed.

Explanation: A database audit process finds a policyadministrator reference to a storage pool that does notexist. Because FIX=YES has been specified, theauthority will be removed.


User Response: After the audit command completes,review your administrator definitions with the QUERYADMIN command. You can then use the REGISTER



ADMIN, UPDATE ADMIN, and GRANT AUTHORITYcommands to change any definitions.

ANR4071I Audit command: Invalid sign-on attemptsis not valid for node/administrator name.

Explanation: A database audit process encounters aninvalid sign-on attempts value that is not valid for thenode or administrator indicated.



ANR4072I Audit command: Invalid file aggregationinformation encountered for node nodename.

Explanation: A database audit process encountersinvalid information used for controlling aggregation offiles for the node indicated.



ANR4073I Audit command: Invalid file aggregationinformation encountered for node nodename - information will be corrected.

Explanation: A database audit process encountersinvalid information used for controlling aggregation offiles for the node specified. Because FIX=YES has beenspecified, the audit function corrects the information.



ANR4074I Dump/load command: Encountered numberof entries bad database entries.

Explanation: This message is displayed at the end of aserver database dump or load command to indicate thenumber of invalid database entries that have beenencountered.



ANR4075I Audit command: Auditing policydefinitions.

Explanation: This message is displayed during adatabase audit and indicates that the server policyinformation (domain, policy set, management classes,

and copy groups) are being examined by the databaseaudit process.



ANR4076E Audit command: Invalid client node countdetected for policy domain domain name.

Explanation: A database audit process finds that thecount of nodes recorded for the specified policydomain do not match the actual number of nodesassigned to the domain.



ANR4077I Audit command: Invalid client node countdetected for policy domain domain namecount will be corrected.

Explanation: A database audit process finds that thecount of nodes recorded for the specified policydomain do not match the actual number of nodesassigned to the domain. Because FIX=YES has beenspecified for the command, the node count willautomatically be corrected.



ANR4078E Audit command: Invalid activationindicators encountered for policydomain domain name.

Explanation: A database audit process finds incorrectpolicy set activation entries for the specified policydomain.



ANR4079I Audit command: Invalid activationindicators encountered for policydomain domain name - entry will becorrected.

Explanation: A database audit process finds incorrectpolicy set activation entries for the specified policydomain. Because FIX=YES has been specified for theaudit command, the entry will be corrected.





ANR4080E Audit command: Invalid grace periodbackup retention value encountered forpolicy domain domain name.

Explanation: A database audit process finds anincorrect grace period retention value for the specifiedpolicy domain.



ANR4081I Audit command: Invalid grace periodbackup retention value encountered forpolicy domain domain name - defaultvalue will be set.

Explanation: A database audit process finds anincorrect grace period retention value for the specifiedpolicy domain. Because FIX=YES has been specified forthe audit command, the default value will be set.



ANR4082E Audit command: Invalid grace periodarchive retention value encountered forpolicy domain domain name.

Explanation: A database audit process finds anincorrect grace period retention value for the specifiedpolicy domain.



ANR4083I Audit command: Invalid grace periodarchive retention value encountered forpolicy domain domain name - defaultvalue will be set.

Explanation: A database audit process finds anincorrect grace period retention value for the specifiedpolicy domain. Because FIX=YES has been specified forthe audit command, the default value will be set.



ANR4084E Audit command: Invalid administratorupdate information encountered forpolicy domain domain name.

Explanation: A database audit process finds incorrectlast updated information for the specified policydomain.


User Response: Reissue the audit command and

specify FIX=YES so that the error can be corrected.

ANR4085I Audit command: Invalid administratorupdate information encountered forpolicy domain domain name - informationwill be corrected.

Explanation: A database audit process finds incorrectlast updated information for the specified policydomain. Because FIX=YES has been specified for thecommand, the information is corrected.



ANR4086E Audit command: Invalid node node numberfound assigned to domain domain name.

Explanation: A database audit process finds a nodenumber assigned to a policy domain that does notreference a valid client node definition.



ANR4087I Audit command: Invalid node node numberfound assigned to domain domain namereference will be deleted.

Explanation: A database audit process finds a nodenumber assigned to a policy domain that does notreference a valid client node definition. BecauseFIX=YES has been specified for the audit command, thereference will be deleted.



ANR4088E Audit command: Default managementclass management class name specified forpolicy set policy set name in domaindomain name does not exist.

Explanation: A database audit process finds a policyset with a default management class specified that doesnot exist.



ANR4089I Audit command: Default managementclass management class name specified forpolicy set policy set name in domaindomain name does not exist - thereference will be removed.

Explanation: A database audit process finds a policyset with a default management class specified that does



not exist. Because FIX=YES has been specified for theaudit command, the reference will be removed from thepolicy set.


User Response: When the audit command completes,examine the policy set specified, and set a new defaultmanagement class for the set. If the policy set is theACTIVE policy set, you must activate a new policy setfor the domain with a valid default management class.

ANR4090E Audit command: Active Policy set fordomain domain name does not contain avalid default management class - policywill fail for this domain. Please correctthe ACTIVE policy set.

Explanation: A database audit process finds an activepolicy set for the specified policy domain that does nothave a valid active management class specified.


User Response: When the audit command completes,you must activate a new policy set for the domain witha valid default management class.

ANR4091E Audit command: Invalid administratorupdate information encountered forpolicy set set name in policy domaindomain name.

Explanation: A database audit process finds incorrectlast updated information for the specified policy set.



ANR4092I Audit command: Invalid administratorupdate information encountered forpolicy set set name in policy domaindomain name - information will becorrected.

Explanation: A database audit process finds incorrectlast updated information for the specified policy set.Because FIX=YES has been specified for the command,the information is corrected.



ANR4093E Audit command: A management classidentifier is not defined formanagement class management class namein policy set set name, domain domainname.

Explanation: A database audit process finds incorrectinformation for the specified management class.



ANR4094E Audit command: A management classidentifier is not defined formanagement class management class namein policy set set name, domain domainname - an identifier will be generatedfor this management class.

Explanation: A database audit process finds incorrectinformation for the specified management class. Theaudit process generates an identifier, because FIX=YEShas been specified for the audit command.



ANR4095E Audit command: An invalid managementclass identifier (actual identifier) wasencountered for management classmanagement class name in policy set setname, domain domain name (expectedexpected identifier).

Explanation: A database audit process finds incorrectinformation for the specified management class.



ANR4096E Audit command: An invalid managementclass identifier (actual identifier) wasencountered for management classmanagement class name in policy set setname, domain domain name (expectedexpected identifier) - the correct identifierwill be stored.

Explanation: A database audit process finds incorrectinformation for the specified management class. Theaudit process corrects the identifier, because FIX=YEShas been specified for the audit command.



ANR4097E Audit command: Invalid administratorupdate information encountered formanagement class management class namein policy set set name in policy domaindomain name.

Explanation: A database audit process finds incorrectlast updated information for the specified managementclass.





ANR4098I Audit command: Invalid administratorupdate information encountered formanagement class management class namein policy set set name in policy domaindomain name - information will becorrected.

Explanation: A database audit process finds incorrectlast updated information for the specified managementclass. Because FIX=YES has been specified for thecommand, the information is corrected.



ANR4099E Audit command: Copy group copy groupname in management class managementclass name, policy set set name, domaindomain name has an invalid name ortype.

Explanation: A database audit process encounters acopy group that has an invalid name or copy grouptype.


User Response: If FIX=YES has not been specified forthe audit command, reissue the command specifyingFIX=YES so that the error can be corrected.

ANR4100I Audit command: Attempting to reinsertthe copy group as a BACKUP copygroup.

Explanation: A database audit process encounters acopy group that has an invalid name or copy grouptype. The process attempts to reinsert the definition asa backup copy group.



ANR4101I Audit command: A backup copy groupalready exists - the invalid copy groupwill be deleted.

Explanation: A database audit process encounters acopy group that has an invalid name or copy grouptype. While attempting to reinsert the copy group as abackup copy group, the process discovers that abackup copy group already exists for the managementclass. The copy group is deleted.


User Response: After the audit command completes,you may examine the server copy groups using theQUERY COPYGROUP command, and correct them

with the DEFINE COPYGROUP and UPDATECOPYGROUP commands if desired.

ANR4102I Audit command: Attempting to reinsertthe copy group as an ARCHIVE copygroup.

Explanation: A database audit process encounters acopy group that has an invalid name or copy grouptype. The process attempts to reinsert the definition asan archive copy group.



ANR4103I Audit command: An archive copy groupalready exists - the invalid copy groupwill be deleted.

Explanation: A database audit process encounters acopy group that has an invalid name or copy grouptype. While attempting to reinsert the copy group as anarchive copy group, the process discovers that a backupcopy group already exists for the management class.The copy group is deleted.


User Response: After the audit command completes,you may examine the server copy groups using theQUERY COPYGROUP command, and correct themwith the DEFINE COPYGROUP and UPDATECOPYGROUP commands, if desired.

ANR4104E Audit command: An invalid managementclass identifier (actual identifier) wasencountered for a copy group inmanagement class management class name,policy set set name, domain domain name(expected expected identifier).

Explanation: A database audit process finds incorrectinformation for the specified copy group.



ANR4105E Audit command: An invalid managementclass identifier (actual identifier) wasencountered for a copy group inmanagement class management class name,policy set set name, domain domain name(expected expected identifier) - the correctidentifier will be stored.

Explanation: A database audit process finds incorrectinformation for the specified copy group. The auditprocess corrects the identifier, since FIX=YES has beenspecified for the audit command.





ANR4106E Audit command: An invalid copy groupidentifier (actual identifier) wasencountered for a copy group inmanagement class management class name,policy set set name, domain domain name(expected expected identifier).

Explanation: A database audit process finds incorrectinformation for the specified copy group.



ANR4107E Audit command: An invalid copy groupidentifier (actual identifier) wasencountered for copy group name copygroup name (expected expected identifier).

Explanation: A database audit process finds incorrectinformation for the specified copy group name.



ANR4108E Audit command: Invalid backup copygroup attributes encountered for copygroup copy group name in managementclass management class name, policy set setname, domain domain name.

Explanation: A database audit process encountersinvalid backup copy group attributes for the specifiedcopy group.


User Response: If FIX=YES has not been specified forthe audit command, reissue the command specifyingFIX=YES so that the inconsistency can be corrected.

ANR4109I Audit command: Invalid backup copygroup attributes encountered for copygroup copy group name in managementclass management class name, policy set setname, domain domain name - the copygroup will be corrected using defaultattributes.

Explanation: A database audit process encountersinvalid backup copy group attributes for the specifiedcopy group. Because FIX=YES has been specified forthe command, the copy group will be corrected usingdefault values for the attributes found in error.


User Response: After the audit command completes,examine the copy group by using the QUERY

COPYGROUP command, and correct attributes withthe UPDATE COPYGROUP command, if desired.

ANR4110E Audit command: Invalid archive copygroup attributes encountered for copygroup copy group name in managementclass management class name, policy set setname, domain domain name.

Explanation: A database audit process encountersinvalid archive copy group attributes for the specifiedcopy group.


User Response: If FIX=YES has not been specified forthe audit command, reissue the command and specifyFIX=YES so that the inconsistency can be corrected.

ANR4111I Audit command: Invalid archive copygroup attributes encountered for copygroup copy group name in managementclass management class name, policy set setname, domain domain name - the copygroup will be corrected using defaultattributes.

Explanation: A database audit process encountersinvalid archive copy group attributes for the specifiedcopy group. Because FIX=YES has been specified forthe command, the copy group will be corrected usingdefault values for the attributes found in error.


User Response: After the audit command completes,examine the copy group by using the QUERYCOPYGROUP command, and correct the attributeswith the UPDATE COPYGROUP command, if desired.

ANR4112W Audit command: Storage pool storage poolname, specified as a destination for copygroup copy group name in managementclass management class name, policy set setname, domain domain name, does notexists.

Explanation: A database audit process encounters astorage pool specified for the destination of thespecified copy group that is not defined in the serverdatabase. If this copy group is used in an active policyset, then backup or archive operations will fail whenattempting to put client data in the destination.


User Response: After the audit command completes,use the DEFINE STGPOOL command to define themissing storage pool or the UPDATE COPYGROUPcommand to update the copy group to refer to anexisting storage pool.



ANR4113E Audit command: Invalid administratorupdate information encountered forcopy group copy group name inmanagement class management class name,policy set set name, policy domain domainname.

Explanation: A database audit process finds incorrectlast updated information for the specified copy group.



ANR4114I Audit command: Invalid administratorupdate information encountered forcopy group copy group name inmanagement class management class name,policy set set name, policy domain domainname - information will be corrected.

Explanation: A database audit process finds incorrectlast updated information for the specified copy group.Because FIX=YES has been specified for the command,the information is corrected.



ANR4115E Audit command: Policy domain domainname is referenced, but not formallydefined.

Explanation: A database audit process finds areference to the specified policy domain, but thedomain is not formally defined in the server database.



ANR4116I Audit command: Policy domain domainname is referenced, but not formallydefined - a policy domain with defaultattributes will be defined with thisname.

Explanation: A database audit process finds areference to the specified policy domain, but thedomain is not formally defined in the server database.Because FIX=YES has been specified, a new policydomain with this name will be defined by the auditprocessor.


User Response: After the audit command hascompleted, you can view the attributes for this policydomain using the QUERY DOMAIN command, andupdate attributes with the UPDATE DOMAINcommand, if desired.

ANR4117E Audit command: Policy set set name indomain domain name is referenced, butnot formally defined.

Explanation: A database audit process finds areference to the specified policy set, but the set is notformally defined in the server database.



ANR4118I Audit command: Policy set set name indomain domain name is referenced, butnot formally defined - a policy set withthis name will be created.

Explanation: A database audit process finds areference to the specified policy set, but the set is notformally defined in the server database. BecauseFIX=YES has been specified, the audit process willcreate a new policy set with this name.


User Response: After the audit command hascompleted, you can view the attributes for this policyset by using the QUERY POLICYSET command, andupdate attributes with the UPDATE POLICYSETcommand, if desired.

ANR4119E Audit command: Management class classname in policy set set name, domaindomain name is referenced, but notformally defined.

Explanation: A database audit process finds areference to the specified management class, but theclass is not formally defined in the server database.



ANR4120I Audit command: Management class classname in policy set set name, domaindomain name is referenced, but notformally defined - the management classwill be created.

Explanation: A database audit process finds areference to the specified management class, but theclass is not formally defined in the server database.Because FIX=YES has been specified for the auditcommand, the audit process defines a managementclass in the server with this name.


User Response: After the audit command hascompleted, you can view the attributes for thismanagement class by using the QUERY MGMTCLASS



command, and update attributes with the UPDATEMGMTCLASS command, if desired.

ANR4122E Audit command: The instance count formanagement class class name does notagree with the actual management classdata (number of instances instances).

Explanation: A database audit process finds areference count for the specified management class thatdid not match the actual number of instances for thisclass.



ANR4123I Audit command: The instance count formanagement class class name does notagree with the actual management classdata (number of instances instances) - thenumber will be corrected.

Explanation: A database audit process finds areference count for the specified management class thatdoes not match the actual number of instances for thisclass. The audit process corrects the count becauseFIX=YES has been specified for the audit command.



ANR4124E Audit command: The instance count forcopy group copy group name does notagree with the actual copy group data(number of instances instances).

Explanation: A database audit process finds areference count for the specified copy group that doesnot match the actual number of instances for this copygroup.



ANR4125I Audit command: The instance count forcopy group copy group name does notagree with the actual copy group data(number of instances instances) - thenumber will be corrected.

Explanation: A database audit process finds areference count for the specified copy group that doesnot match the actual number of instances for this copygroup. The audit process corrects the count becauseFIX=YES has been specified for the audit command.



ANR4126E Audit command: Policy global attributescannot be found.

Explanation: A database audit process is not able tolocate the global attributes for policy information in theserver database.



ANR4127I Audit command: Policy global attributescannot be found - attributes willrecreated.

Explanation: A database audit process is not able tolocate the global attributes for policy information in theserver database. Because FIX=YES has been specifiedfor the audit command, the attributes will beregenerated.



ANR4128E Audit command: Policy global high-watermarks do not match the identifiers inuse.

Explanation: A database audit process finds theattributes used to track policy identifiers are incorrect.



ANR4129E Audit command: Policy global high-watermarks do not match the identifiers inuse - they will be corrected.

Explanation: A database audit process finds theattributes used to track policy identifiers are incorrect.Because FIX=YES has been specified for the auditcommand, the attributes will be corrected.



ANR4130W Audit Volume updating objectinformation for volume volume name:Node node name, Type file type, File spacefilespace name, fsId filespace id , File Namefile name.

Explanation: As the result of an AUDIT VOLUMEcommand that specified FIX=YES for the volumeshown, object information for the specified file will beupdated.

System Action: The object information is updated.




ANR4131W Audit Volume found incorrect objectinformation for volume volume name:Node node name, Type file type, File spacefilespace name, fsId filespace id, File namefile name.

Explanation: As the result of an AUDIT VOLUMEcommand that specified FIX=NO for the volumeshown, object information for the specified file is foundto be in error.



ANR4132I Audit volume process ended for volumevolume name; file count files inspected, filecount damaged files deleted, file countdamaged files marked as damaged, filecount objects updated.

Explanation: The AUDIT VOLUME commandspecifying FIX=YES for the volume shown has ended.The number of files audited, the number of inconsistentfiles deleted or marked as damaged, and the number ofupdated objects are displayed. The number of filesmarked as damaged includes all files belonging toaggregates that were marked damaged during theaudit. Files are marked as damaged in primary storagepools and not deleted when backup copies for the filesare known to exist in COPY storage pools.


User Response: To recover files that have beenmarked as damaged on the volume, use the RESTORESTGPOOL or RESTORE volume command.

ANR4133I Audit volume process ended for volumevolume name; file count files inspected, filecount damaged files found and markedas damaged, file count objects needupdating.

Explanation: The AUDIT VOLUME commandspecifying FIX=NO for the volume shown has ended.The number of files audited, the number of inconsistentfiles found, and the number of files with incorrectobject information are displayed. The number of filesmarked damaged includes all files belonging toaggregates that were marked damaged during theaudit. Inconsistent files are marked as damaged in thedatabase and can be recovered by using the RESTORESTGPOOL or RESTORE VOLUME command if copiesof the files reside in a COPY storage pool. AnotherAUDIT VOLUME command may be able to access thefiles and reset the damaged indicator in the database ifthe audit volume process cannot access the files due tohardware problems (for example, dirty tape heads).


User Response: If you suspect that files wereinaccessible because of hardware problems such as

dirty tape heads, correct the hardware problem andreissue the AUDIT VOLUME FIX=NO command forthis volume. To remove damaged file references andupdate the object information, issue the AUDITVOLUME command and specify FIX=YES.

ANR4135I Audit command: Auditing centralscheduler definitions.

Explanation: This message is displayed during adatabase audit and indicates that the server schedulinginformation is examined by the database audit process.



ANR4136I Audit command: Auditing serverinventory.

Explanation: This message is displayed during adatabase audit and indicates that server informationabout client file spaces is currently being examined bythe database audit process.



ANR4137I Audit command: Auditing inventory filespaces.

Explanation: This message is displayed during adatabase audit and indicates that server informationabout client file spaces is currently being examined bythe database audit process.



ANR4138I Audit command: Auditing inventorybackup objects.

Explanation: This message is displayed during adatabase audit and indicates that server informationabout client backup objects is currently being examinedby the database audit process.



ANR4139I Audit command: Auditing inventoryarchive objects.

Explanation: This message is displayed during adatabase audit and indicates that server informationabout client archive objects is currently being examinedby the database audit process.





ANR4140I Audit command: Database audit processstarted.

Explanation: This message is displayed during adatabase audit and indicates that the audit process hasstarted.



ANR4141I Audit command: Database audit processcompleted.

Explanation: This message is displayed during adatabase audit and indicates that the database audithas successfully completed.

System Action: Audit processing ends.


ANR4142I Audit command: Database audit processterminated in error.

Explanation: This message is displayed during adatabase audit and indicates that the audit processended prematurely due to an internal server databaseerror.

System Action: Audit processing ends.

User Response: Examine the messages issued prior tothis one to see if the error can be corrected. If thesituation cannot be resolved, contact your servicerepresentative.

ANR4143E Audit command: Central scheduler globalattributes cannot be found.

Explanation: A database audit process cannot locatethe global attributes for scheduling information in theserver database.



ANR4144I Audit command: Central scheduler globalattributes cannot be found - attributeswill be recreated.

Explanation: A database audit process cannot locatethe global attributes for scheduler information in theserver database. Because FIX=YES has been specifiedfor the audit command, the attributes will beregenerated.



ANR4145E Audit command: One or more centralscheduler attributes are incorrect.

Explanation: A database audit process finds that theglobal attributes used for server scheduling activitiesare incorrect.


User Response: Reissue the audit command andspecify FIX=YES so that the administrative globalattributes can be corrected.

ANR4146I Audit command: One or more centralscheduler global attribute(s) areincorrect - default values will be set.

Explanation: A database audit process finds that theglobal attributes used for server scheduling activitiesare incorrect. Because FIX=YES has been specified onthe AUDIT command, default attribute values will beused to correct the scheduling global attributes.



ANR4147E Audit command: Policy domain domainname referenced by schedule schedulename does not exist.

Explanation: A database audit process finds aschedule that references a policy domain that is notdefined in the server database.



ANR4148I Audit command: Policy domain domainname referenced by schedule schedulename does not exist - the schedule willbe deleted.

Explanation: A database audit process finds aschedule that references a policy domain that is notdefined in the server database. Because FIX=YES hasbeen specified for the audit command, the specifiedschedule will be deleted from the server database.





ANR4149E Audit command: One or more attributesfor schedule schedule name in policydomain domain name are incorrect.

Explanation: A database audit process finds one ormore invalid attributes for the specified schedule.



ANR4150I Audit command: One or more attributesfor schedule schedule name in policydomain domain name are incorrect -default values will be set.

Explanation: A database audit process finds one ormore invalid attributes for the specified schedule.Because FIX=YES has been specified for the auditcommand the invalid attributes will be set to defaultvalues.


User Response: When the audit completes, you canuse the QUERY SCHEDULE command to examine thevalues set for the schedule, and use the UPDATESCHEDULE command to change any attributes desired.

ANR4151E Audit command: Schedule schedule name inpolicy domain domain name not found,but is referenced by a client node.

Explanation: A database audit process finds aschedule reference from a client node for a schedulethat is not defined in the server database.



ANR4152I Audit command: Schedule schedule name inpolicy domain domain name not found,but is referenced by a client node - theschedule association will be deleted.

Explanation: A database audit process finds aschedule reference from a client node for a schedulethat is not defined in the server database. BecauseFIX=YES has been specified for the audit command, theschedule association will be deleted from the serverdatabase.



ANR4153E Audit command: Schedule schedule name inpolicy domain domain name references aclient node that does not exist.

Explanation: A database audit process finds aschedule that references a client node that is notdefined in the server database.



ANR4154I Audit command: Schedule schedule name inpolicy domain domain name references aclient node that does not exist - thenode reference will be deleted.

Explanation: A database audit process finds aschedule that references a client node that is notdefined in the server database. Because FIX=YES hasbeen specified for the audit command, the referencewill be removed from the server database.



ANR4155E Audit command: Invalid administratorupdate information encountered for aschedule assignment.

Explanation: A database audit process finds incorrectlast updated information for a schedule-nodeassignment.



ANR4156I Audit command: Invalid administratorupdate information encountered for aschedule assignment - information willbe corrected.

Explanation: A database audit process finds incorrectlast updated information for a schedule-nodeassignment. Because FIX=YES has been specified forthe command, the information is corrected.



ANR4157E Audit command: Scheduling callbackaddress is registered for a client nodethat does not exist.

Explanation: A database audit process finds aserver-prompted-scheduling callback address for a nodethat does not exist.





ANR4158I Audit command: Scheduling callbackaddress is registered for a client nodethat does not exist - callbackinformation will be deleted.

Explanation: A database audit process finds aserver-prompted-scheduling callback address for a nodethat does not exist. Because FIX=YES has been specifiedfor the command, the callback information will bedeleted from the server database.



ANR4159I Audit command: An inventoryauthorization rule specifies an invalidnode (node ID) or file space (filespace ID)- the rule will be deleted.

Explanation: A database audit process finds thateither a node ID or file space ID is invalid for anauthorization rule. Since FIX=YES has been specified,the invalid authorization rule will be deleted.



ANR4160I Audit command: An inventoryauthorization rule specifies an invalidnode (node ID) or file space (filespace ID).

Explanation: A database audit process finds thateither a node ID or file space ID is invalid for anauthorization rule.



ANR4161I Audit command: Inventory globalattributes could not be found - they willbe created.

Explanation: A database audit process cannot find theinventory global attributes. Because FIX=YES has beenspecified for the command, the information is correctedby the creation of the global attributes.



ANR4162I Audit command: Inventory globalattributes could not be found.

Explanation: A database audit process cannot find theinventory global attributes.



ANR4163I Audit command: Invalid object IDhigh-water mark encountered forinventory global attributes - the valuewill be corrected.

Explanation: A database audit process finds that theobject ID high-water mark for the inventory globalattributes is invalid. Because FIX=YES has beenspecified for the command, the object ID high-watermark is determined by the current inventory and setaccordingly.



ANR4164I Audit command: Invalid object IDhigh-water mark encountered forinventory global attributes.

Explanation: A database audit process finds that theobject ID high-water mark for the inventory globalattributes is invalid.



ANR4165I Audit command: An inventory nodeassignment entry was not found fornode node ID - an entry will be created.

Explanation: A database audit process cannot find thenode assignment entry corresponding to the specifiednode. Since FIX=YES has been specified for thecommand, the required inventory entry will be createdusing default values.



ANR4166I Audit command: An inventory nodeassignment entry was not found fornode node ID.

Explanation: A database audit process cannot find thenode assignment entry corresponding to the specifiednode.





ANR4167I Audit command: The file spacehigh-water mark for node node ID isincorrect - the value will be corrected.

Explanation: A database audit process finds that a filespace high-water mark is incorrect for the specifiednode ID. Since FIX=YES has been specified for thecommand, the information is corrected.



ANR4168I Audit command: The file spacehigh-water mark for node node ID isincorrect.

Explanation: A database audit process finds that a filespace high-water mark is incorrect for the specifiednode ID.



ANR4169I Audit command: The file spacehigh-water mark for node node ID isincorrect - the value will be corrected.

Explanation: A database audit process finds that anauthorization rule high-water mark is incorrect for thespecified node ID. Since FIX=YES has been specified forthe command, the information is corrected.



ANR4170I Audit command: The authorization rulehigh-water mark for node node ID isincorrect.

Explanation: A database audit process finds that anauthorization rule high-water mark is incorrect for thespecified node ID.



ANR4171I Audit command: Primary backup entry foran expiring object (object.ID) cannot befound - the expiring object entry will bedeleted.

Explanation: A database audit process cannot find theprimary backup entry for the specified expiring object.Because FIX=YES has been specified for the command,the information is corrected by deleting the expiringobject entry.



ANR4172I Audit command: Primary backup entry foran expiring object (object.ID) cannot befound.

Explanation: A database audit process cannot find theprimary backup entry for the specified expiring object.



ANR4173I Audit command: Primary archive entry foran expiring object (object.ID) cannot befound - the expiring object entry will bedeleted.

Explanation: A database audit process cannot find theprimary archive entry for the specified expiring object.Because FIX=YES has been specified for the command,the information is corrected by deleting the expiringobject entry.



ANR4174I Audit command: Primary archive entry foran expiring object (object.ID) cannot befound.

Explanation: A database audit process cannot find theprimary archive entry for the specified expiring object.



ANR4175I Audit command: Invalid copy typeencountered for an expiring objectsentry (object.ID) - the expiring objectentry will be deleted.

Explanation: A database audit process finds that thecopy type for the specified expiring object is invalid.Because FIX=YES has been specified for the command,the information is corrected by deleting the expiringobject entry. The entry will be recreated later if it isnecessary.



ANR4176I Audit command: Invalid copy typeencountered for an expiring objectsentry (object.ID).

Explanation: A database audit process finds that thecopy type for the specified expiring object is invalid.





ANR4177I Audit command: Primary backup entry foran object (object.ID) cannot be found -entry will be deleted.

Explanation: A database audit process cannot find thespecified primary backup object. Because FIX=YES hasbeen specified for the command, the entry is deleted.



ANR4178I Audit command: Primary backup entry foran object (object.ID) cannot be found.

Explanation: A database audit process cannot find thespecified primary backup object.



ANR4179I Audit command: Primary archive entry foran object (object.ID) cannot be found -entry will be deleted.

Explanation: A database audit process cannot find thespecified primary archive object. Because FIX=YES hasbeen specified for the command, the entry is deleted.



ANR4180I Audit command: Primary archive entry foran object (object.ID) cannot be found.

Explanation: A database audit process cannot find thespecified primary archive object.



ANR4181I Audit command: Invalid copy typeencountered for object object.ID - objectfound as a backup object - correctingthe invalid copy type

Explanation: A database audit process encounters aninvalid copy type for the specified object ID but finds acorresponding backup object for the entry. BecauseFIX=YES has been specified for the command, theinvalid copy type is corrected.



ANR4182I Audit command: Invalid copy typeencountered for object object.ID - objectfound as an archive object - correctingthe invalid copy type

Explanation: A database audit process encounters aninvalid copy type for the specified object ID but finds acorresponding archive object for the entry. BecauseFIX=YES has been specified for the command, theinvalid copy type is corrected.



ANR4183I Audit command: Invalid copy typeencountered for object object.ID -primary archive entry created for objectusing default values.

Explanation: A database audit process encounters aninvalid copy type for the specified object ID and isunable to find corresponding primary backup orprimary archive objects. Because FIX=YES has beenspecified for the command, a primary archive entry iscreated using default values.



ANR4184I Audit command: Invalid copy typeencountered for object object.ID.

Explanation: A database audit process encounters aninvalid copy type for the specified object ID and isunable to find corresponding primary backup orprimary archive objects.



ANR4185I Audit command: Object entry for backupobject object.ID not found - entry will becreated.

Explanation: A database audit process cannot find anobject entry for the specified backup object. BecauseFIX=YES has been specified for the command, an objectentry is created using default values.



ANR4186I Audit command: Object entry for backupobject object.ID not found.

Explanation: A database audit process cannot find anobject entry for the specified backup object.





ANR4187I Audit command: Inventory object fieldsfor object object.ID do not match theprimary backup entry - the object willbe updated.

Explanation: A database audit process determines thatthe object fields for the specified object ID do notmatch the fields for the corresponding primary backupobject. Because FIX=YES has specified for thecommand, the incorrect object fields will be corrected.



ANR4188I Audit command: Inventory object fieldsfor object object.ID do not match theprimary backup entry.

Explanation: A database audit process determines thatthe object fields for the specified object ID do notmatch the fields for the corresponding primary backupobject.



ANR4189I Audit command: Expiring entry forinactive backup object object.ID notfound - the entry will be created.

Explanation: A database audit process cannot find anexpiring entry for the specified inactive backup entry.Because FIX=YES has been specified for the command,an expiring entry will be created.



ANR4190I Audit command: Expiring entry forinactive backup object object.ID notfound.

Explanation: A database audit process cannot find anexpiring entry for the specified inactive backup entry.



ANR4191I Audit command: Object entry for archiveobject object.ID not found - entry will becreated.

Explanation: A database audit process cannot find anobject entry for the specified archive object. BecauseFIX=YES has been specified for the command, the

information is corrected by creating an object entry.



ANR4192I Audit command: Object entry for archiveobject object.ID not found.

Explanation: A database audit process cannot find anobject entry for the specified archive object.



ANR4193I Audit command: Inventory object fieldsfor object object.ID do not match theprimary archive entry - the object willbe updated.

Explanation: A database audit process determines thatthe object fields for the specified object ID do notmatch the fields for the corresponding primary archiveobject. Because FIX=YES has been specified for thecommand, the incorrect object fields will be corrected.



ANR4194I Audit command: Inventory object fieldsfor object object.ID do not match theprimary archive entry.

Explanation: A database audit process determines thatthe object fields for the specified object ID do notmatch the fields for the corresponding primary archiveobject.



ANR4195I Audit command: Expiring entry forarchive object object.ID not found - theentry will be created.

Explanation: A database audit process cannot find anexpiring entry for the specified archive object. BecauseFIX=YES has been specified for the command, anexpiring entry will be created.



ANR4196I Audit command: Expiring entry forarchive object object.ID not found.

Explanation: A database audit process cannot find anexpiring entry for the specified archive object.





ANR4197I Audit command: File space entry filespaceID not found for node node ID.

Explanation: A database audit process cannot find afile space entry for the specified node.



ANR4198I Audit command: File space entry filespaceID not found for node node name - anentry will be created.

Explanation: A database audit process cannot find afile space entry for the specified node. BecauseFIX=YES has been specified for the command, a filespace entry has been created.



ANR4199I Audit command: File space entry filespaceID not found for node node name -unable to create an entry.

Explanation: A database audit process cannot find afile space entry for the specified node. BecauseFIX=YES has been specified for the command, the auditprocess has attempted to create a file space entry but isnot successful.


User Response: Contact your system administrator.

ANR4200I Audit command: Expiring entry node IDand file space filespace ID does not matchthe object entry for object ID object.ID -the entry will be deleted.

Explanation: A database audit process determines thatthe specified expiring object entry does not match thecorresponding object entry for the specified object ID.Because FIX=YES has been specified for the command,the expiring object entry is deleted.



ANR4201I Audit command: Expiring entry node IDand file space filespace ID does not matchthe object entry for object ID object.ID.

Explanation: A database audit process determines thatthe specified expiring object entry does not match thecorresponding object entry for the specified object ID.



ANR4202I Audit command: The base date forexpiration processing of entry object.ID isnot valid - the entry will be deleted.

Explanation: A database audit process determines thatthe specified expiring object has a date that is not valid.Because FIX=YES has been specified for the command,the expiring object entry is deleted.



ANR4203I Audit command: The base date forexpiration processing of object object.IDis not valid.

Explanation: A database audit process determines thatthe specified expiring object has a date value that is notvalid.



ANR4204I Audit command: One or more date valuesfor a backup entry object.ID is not valid.

Explanation: A database audit process determines thatone or more of the date values is improperly formattedor contains incorrect information for the specifiedbackup object.



ANR4205I Audit command: The insertion date valuefor archive entry object.ID is not valid.

Explanation: A database audit process determines thatthe insertion date for the specified archive object isimproperly formatted or contains incorrect information.



ANR4206I Audit command: Object entry for expiringobject object.ID not found - expiringobject entry will be deleted.

Explanation: A database audit process cannot find anobject entry corresponding to the specified expiringobject. Because FIX=YES has been specified for thecommand, the expiring object entry for the specifiedobject ID is deleted.





ANR4207I Audit command: Object entry for expiringobject object.ID not found.

Explanation: A database audit process cannot find anobject entry corresponding to the specified expiringobject.



ANR4208I Audit command: An inventory nodeassignment entry is not valid for nodenode ID - the entry will be deleted.

Explanation: A database audit process finds that anode assignment entry for the specified node ID is notvalid. Since FIX=YES has been specified for thecommand, the required inventory entry is deleted.



ANR4209I Audit command: An inventory nodeassignment entry was not found fornode node ID.

Explanation: A database audit process finds that anode assignment entry for the specified node ID is notvalid.



ANR4210I Audit command: Auditing physicalvolume repository definitions.

Explanation: This message is displayed during adatabase audit and indicates that the physical volumerepository definitions are being examined by thedatabase audit process.



ANR4211I Audit command: Drive entry library namefor library drive name in the physicalvolume repository is invalid.

Explanation: A database audit process finds that adrive entry is missing a corresponding library entry.



ANR4212I Audit command: An object entry forlibrary library name and drive drive namein the physical volume repository isinvalid - the entry will be deleted.

Explanation: A database audit process finds that adrive entry is missing a corresponding library entry.Because FIX=YES has been specified for the command,the invalid drive entry is deleted.



ANR4213I Audit command: A device type for librarylibrary name and drive drive name in thephysical volume repository is invalid.

Explanation: A database audit process finds that adevice type for the specified library and drive isinvalid.


User Response: Contact the system administrator sothat appropriate action may be taken.

ANR4214I Audit command: A drive model forlibrary library name and drive drive namein the physical volume repository isinvalid.

Explanation: A database audit process finds that thedrive model for the specified library and drive isinvalid.


User Response: Contact the system administrator sothat appropriate action may be taken.

ANR4215I Audit command: An object entry forlibrary library name and volume volumename in the physical volume repositoryis invalid.

Explanation: A database audit process finds that alibrary inventory entry is missing a correspondinglibrary entry.



ANR4216I Audit command: An object entry forlibrary library name and volume volumename in the physical volume repositoryis invalid - the entry will be deleted.

Explanation: A database audit process finds that alibrary inventory entry is missing a correspondinglibrary entry. Because FIX=YES has been specified for



the command, the invalid library inventory entry isdeleted.



ANR4217I Audit command: The volume status forlibrary library name and volume volumename in the physical volume repositoryis invalid.

Explanation: A database audit process finds that thevolume status for the specified library and volume isset to scratch. This is incorrect because storage agenthas a volume name for the library and volumeindicating that it should have a volume status ofprivate.



ANR4218I Audit command: The volume status forlibrary library name and volume volumename in the physical volume repositoryis invalid - the volume status will bechanged to private.

Explanation: A database audit process finds that thevolume status for the specified library and volume isset to scratch. This is incorrect because storage agentshas a volume name for the library and volume whichindicates that it should have a volume status of private.Because FIX=YES has been specified for the command,the incorrect volume status is set to private.



ANR4219I Audit command: A library type specifiedfor library library name in the physicalvolume repository is invalid.

Explanation: A database audit process finds that thelibrary type for the specified library is invalid.



ANR4220I Audit command: A library type specifiedfor library library name in the physicalvolume repository is invalid - thelibrary type has been changed to thedefault of library type default.

Explanation: A database audit process finds that thelibrary type for the specified library is invalid. BecauseFIX=YES has been specified for the command, the

information is corrected by changing the library type tothe default type.



ANR4221I Audit command: An error (error code) wasfound with archive description for node(node identifier), description (description),objects (old object count,new object count),count (old directory count,new directorycount) - entry will be deleted or updated.

Explanation: A database audit process has found anerror with the specified archive description. BecauseFIX=YES has been specified for the command, the entryis deleted or updated.



ANR4222I Audit command: An error (error code) wasfound with archive description for node(node identifier), description (description),objects (old object count,new object count),count (old directory count,new directorycount).

Explanation: A database audit process has found anerror with the specified archive description.



ANR4223I Audit command: An error (error code) wasfound with converted archive object fornode (node identifier), description(description identifier), object (object.ID),filespace (filespace identifier) - entry willbe deleted.

Explanation: A database audit process has found anerror with the specified converted archive object.Because FIX=YES has been specified for the command,the entry is deleted.



ANR4224I Audit command: An error (error code) wasfound with converted archive object fornode (node identifier), description(description identifier), object (object.ID),filespace (filespace identifier).

Explanation: A database audit process has found anerror with the specified converted archive object.





ANR4225I Audit command: table entry for archiveobject (object.ID), node (node identifier),description (description), filespace(filespace identifier) not found - the entrywill be created.

Explanation: A database audit process cannot find aconverted table table entry for the specified archiveobject. Because FIX=YES has been specified for thecommand, an entry will be created.



ANR4226I Audit command: table entry for archiveobject (object.ID), node (node identifier),description (description), filespace(filespace identifier) not found.

Explanation: A database audit process cannot find aconverted table table entry for the specified archiveobject.



ANR4227E Audit command: Inconsistent informationdetected for file aggregate (Aggregate.ID).

Explanation: A database audit process findsinconsistent information for a file aggregate. Thisproblem cannot be corrected by the audit process, butthe file data is not deleted.



ANR4228E Audit command: Missing or incorrectinformation detected for file aggregate(Aggregate.ID).

Explanation: A database audit process detects missingor incorrect information for a file aggregate. Thisinformation can be corrected.



ANR4229E Audit command: Missing or incorrectinformation detected for file aggregate(Aggregate.ID) - It will be corrected.

Explanation: A database audit process detects missingor incorrect information for a file aggregate. Because

FIX=YES has been specified for the audit command, theerror will be corrected.



ANR4230I Audit command: Auditing data storagedefinitions.

Explanation: This message is displayed during adatabase audit and indicates that the data storagedefinitions are being examined by the database auditprocess.



ANR4231E Audit command: Invalid device classstrategy strategy for device class deviceclass name.

Explanation: A database audit process finds a deviceclass with an invalid access strategy.


User Response: Reissue the audit command withFIX=YES so that the access strategy can be corrected.

ANR4232E Audit command: Invalid device classstrategy strategy for device class deviceclass name - information will becorrected.

Explanation: A database audit process finds a deviceclass with an invalid access strategy. Because FIX=YEShas been specified for the audit command, the accessstrategy will be corrected for this device class.



ANR4233E Audit command: Pool ID information ismissing or incorrect for storage poolstorage pool name.

Explanation: A database audit process finds a storagepool whose pool ID information is missing or incorrect.


User Response: Reissue the audit command withFIX=YES so that the access strategy can be corrected.

ANR4234E Audit command: Pool ID information ismissing or incorrect for storage poolstorage pool name - information will becreated or corrected.

Explanation: A database audit process finds a storagepool whose pool ID information is missing or incorrect.Because FIX=YES has been specified for the audit



command, the pool ID information will be created orcorrected for this storage pool.



ANR4235E Audit command: Device class IDreferenced by storage pool storage poolname is not defined - data in this poolmay not be available.

Explanation: A database audit process finds a storagepool which references a device class ID which is notdefined.



ANR4236E Audit command: An invalid accessstrategy was encountered for storagepool storage pool name.

Explanation: A database audit process encounters aninvalid device access strategy for the specified storagepool.


User Response: Reissue the audit command withFIX=YES so that the attribute can be corrected.

ANR4237E Audit command: An invalid accessstrategy was encountered for storagepool storage pool name - the strategy willbe corrected.

Explanation: A database audit process encounters aninvalid device access strategy for the specified storagepool. Because FIX=YES has been specified for thecommand, the storage pool access strategy will becorrected.


User Response: After the audit command completes,examine the storage pool using the QUERY STGPOOLcommand, and verify that the correct information isdisplayed for this storage pool.

ANR4238E Audit command: Storage pool storage poolname specifies an undefined pool ID forits next storage pool.

Explanation: The specified storage pool references aninvalid pool ID as its next storage pool.


User Response: Use the UPDATE STGPOOLcommand to update the next pool. Alternatively, if theaudit command is reissued with FIX=YES, the referenceto the next pool will be deleted.

ANR4239E Audit command: Storage pool storage poolname specifies an undefined pool ID forits next storage pool - reference will bedeleted.

Explanation: The specified storage pool references aninvalid pool ID as its next storage pool. BecauseFIX=YES has been specified for the command, thereference is deleted. The specified storage pool will nothave a next pool.


User Response: After the audit command completes,use the UPDATE STGPOOL command to assign a nextstorage pool, if desired.

ANR4240E Audit command: An invalid attribute wasencountered for storage pool storage poolname.

Explanation: A database audit process encounters aninvalid attribute for the specified storage pool.



ANR4241E Audit command: An invalid attribute wasencountered for storage pool storage poolname - the attribute will be assigned itsdefault value.

Explanation: A database audit process encounters aninvalid attribute for the specified storage pool. BecauseFIX=YES has been specified for the command, thestorage pool will be corrected using the default valuefor the attribute.


User Response: After the audit command completes,examine the storage pool using the QUERY STGPOOLcommand, and correct attributes with the UPDATESTGPOOL command, if desired.

ANR4242E Audit command: Invalid administratorupdate information encountered forstorage pool storage pool name.

Explanation: A database audit process finds incorrectinformation pertaining to the last update for thespecified storage pool.





ANR4243E Audit command: Invalid administratorupdate information encountered forstorage pool storage pool name -information will be corrected.

Explanation: A database audit process finds incorrectinformation pertaining to the last update for thespecified storage pool. Because FIX=YES has beenspecified for the command, the information iscorrected.



ANR4244E Audit command: Storage pool IDreferenced by volume volume name is notdefined - data on this volume may notbe available.

Explanation: A database audit process finds a datastorage volume which references a storage pool ID thatis not defined.


User Response: You can attempt to move data on thespecified volume to other volumes using the MOVEDATA command; then delete the specified volume andredefine it. If this does not work, contact your servicerepresentative.

ANR4245E Audit command: An invalid accessstrategy was encountered for volumevolume name.

Explanation: A database audit process encounters aninvalid device access strategy for the specified volume.


User Response: Reissue the audit command withFIX=YES so that the strategy can be corrected.

ANR4246E Audit command: An invalid accessstrategy was encountered for volumevolume name - the strategy will becorrected.

Explanation: A database audit process encounters aninvalid device access strategy for the specified volume.Because FIX=YES has been specified for the command,the access strategy will be corrected for this volume.



ANR4247E Audit command: Missing information forvolume volume name cannot be created.Delete the volume after optionallymoving any files from the volume.

Explanation: A database audit process encountersmissing database information for the specified volume.Since FIX=YES has been specified for the auditcommand, an attempt is made to create the missinginformation where possible. However, some of theinformation cannot be created, and the volume must bedeleted.

System Action: The access mode for the volume is setto UNAVAILABLE to prevent further attempts to writeto this volume. Audit processing continues.

User Response: After audit processing completes, anadministrator should take the following actions toeliminate the volumev (Optional) Use the UPDATE VOLUME command to

set the access mode for the volume to READWRITE.It may then be possible to use the MOVE DATAcommand to move files from the volume so thatthese files can be accessed by the server.

v (Required) Use the DELETE VOLUME command todelete the volume from the database.

ANR4248E Audit command: Missing or incorrectinformation for storage volume volumename.

Explanation: A database audit process finds a datastorage volume for which information is missing orincorrect.



ANR4249E Audit command: Missing or incorrectinformation for storage volume volumename - information will be created orcorrected.

Explanation: A database audit process finds a datastorage volume for which information is missing orincorrect. Since FIX=YES has been specified for theaudit command, the information will be created orcorrected.



ANR4250E Audit command: Extraneous referencefound.

Explanation: A database audit process finds areference to a nonexistent entity such as a storage poolor volume.




User Response: Reissue the audit command withFIX=YES so that the non-existant entity is recreated, ifpossible. If recreation is not possible, the extraneousreference is deleted.

ANR4251E Audit command: Extraneous referencefound - information will be recreated ordeleted.

Explanation: A database audit process finds areference to a nonexistent entity such as a storage poolor volume. Since FIX=YES has been specified for theaudit command, the nonexistant entity will berecreated, if possible. If recreation is not possible, theextraneous information will be deleted.



ANR4252E Audit command: Data storage globalattributes cannot be found.

Explanation: A database audit process is not able tolocate the global attributes for data storage in theserver database.



ANR4253E Audit command: Data storage globalattributes cannot be found - attributeswill be recreated.

Explanation: A database audit process is not able tolocate the global attributes for data storage in theserver database. Because FIX=YES has been specifiedfor the audit command, the attributes will beregenerated.



ANR4254E Audit command: Data storage high-watermarks do not match the identifiers inuse.

Explanation: A database audit process finds that theinformation used to track data storage identifiers isincorrect.



ANR4255E Audit command: Data storage high-watermarks do not match the identifiers inuse - they will be corrected.

Explanation: A database audit process finds that theinformation used to track data storage identifiers isincorrect. Because FIX=YES has been specified for theaudit command, the error will be corrected.



ANR4256I Audit command: Auditing data storagedefinitions for disk volumes.

Explanation: This message is displayed during adatabase audit and indicates that the databaseinformation relating to data storage disk volumes isbeing examined by the database audit process.



ANR4257E Audit command: A correctabledata-integrity error was detected onvolume volume name.

Explanation: A database audit process finds adata-integrity error for a file stored on the specifiedvolume. This error is correctable.



ANR4258E Audit command: A data-integrity errorwas detected on volume volume name -the error will be corrected.

Explanation: A database audit process finds acorrectable data-integrity error for a file stored on thespecified volume. Because FIX=YES has been specifiedfor the audit command, the error will be corrected.



ANR4259E Audit command: Invalid data encounteredfor a file in data storage - data can becorrected.

Explanation: A database audit process finds invaliddata for a file in data storage. The error should becorrectable.





ANR4260E Audit command: Invalid data encounteredfor a file in data storage - the error willbe corrected.

Explanation: A database audit process finds invaliddata for a file in data storage. Because FIX=YES hasbeen specified for the audit command, the error will becorrected.



ANR4261E Audit command: Invalid accessinformation was encountered forvolume volume name.

Explanation: A database audit process encountersinvalid access information for the specified volume.


User Response: After audit processing has completed,use the UPDATE VOLUME command to set the accessinformation for this volume. Or reissue the auditcommand with FIX=YES, which sets access to thedefault value.

ANR4262E Audit command: Invalid accessinformation was encountered forvolume volume name - the informationwill be corrected.

Explanation: A database audit process encountersinvalid access information for the specified volume.Because FIX=YES has been specified for the command,the information will be corrected by setting the defaultvalue.


User Response: After audit processing has completed,use the UPDATE VOLUME command to set the accessinformation for this volume, if desired.

ANR4263I Audit command: Auditing data storagedefinitions for sequential volumes.

Explanation: This message is displayed during adatabase audit and indicates that the databaseinformation relating to data storage sequential volumesis being examined by the database audit process.



ANR4264I Audit command: Auditing fileinformation.

Explanation: This message is displayed during adatabase audit and indicates that information on storedfiles is being examined by the database audit process.



ANR4265I Audit command: Auditing disk fileinformation.

Explanation: This message is displayed during adatabase audit and indicates that information on filesstored on disk media is being examined by thedatabase audit process.



ANR4266I Audit command: Auditing sequential fileinformation.

Explanation: This message is displayed during adatabase audit and indicates that information on filesstored on sequential media is being examined by thedatabase audit process.



ANR4267E Audit command: A storage poolcontaining file data cannot be located -file data may not be accessible.

Explanation: This message is displayed during adatabase audit and indicates that the storage poolcontaining a file’s data cannot be located or is notdefined. This problem cannot be corrected by the auditprocess, but the file data is not deleted.



ANR4268E Audit command: A storage volumecontaining file data cannot be located -file data may not be accessible.

Explanation: This message is displayed during adatabase audit and indicates that the storage volumecontaining a file’s data cannot be located or is notdefined. This problem cannot be corrected by the auditprocess, and the file data is deleted.



ANR4269E Audit command: Extraneous file datareference found.

Explanation: A database audit process finds areference to a file that no longer exists.


User Response: Reissue the audit command withFIX=YES so that the information can be deleted.



ANR4270E Audit command: Extraneous file datareference found - information will bedeleted.

Explanation: A database audit process finds areference to a file that no longer exists. BecauseFIX=YES has been specified for the audit command, theinformation will be deleted.



ANR4271E Audit command: Missing or incorrectoccupancy information detected.

Explanation: A database audit process detects missingor incorrect occupancy information for a data storagepool or a data storage volume.



ANR4272E Audit command: Missing or incorrectoccupancy information detected -information will be created or corrected.

Explanation: A database audit process detects missingor incorrect occupancy information for a data storagepool or a data storage volume. Because FIX=YES hasbeen specified for the audit command, the informationwill be created or corrected.



ANR4273E Audit command: A data-integrity errorwas detected on volume volume name -Issue the AUDIT VOLUME command tocorrect the error.

Explanation: A database audit process finds adata-integrity error for a file stored on the specifiedvolume.


User Response: Issue the AUDIT VOLUME commandon the specified volume to correct the data-integrityerror.

ANR4274E Audit command: A correctabledata-integrity error was detected.

Explanation: A database audit process finds adata-integrity error for a stored file. This error can becorrected.




ANR4275E Audit command: A data-integrity errorwas detected - it will be corrected.

Explanation: A database audit process finds adata-integrity error for a stored file. Because FIX=YEShas been specified for the audit command, the errorwill be corrected.



ANR4276E Audit command: Invalid file storageinformation detected - file data is notaccessible.

Explanation: A database audit process finds invalidfile storage information for a stored file, and it cannotbe corrected.


User Response: Issue the AUDIT VOLUME commandon all your volumes to correct the data-integrity error.

ANR4277E Audit command: Invalid file storageinformation detected.

Explanation: A database audit process finds invalidfile storage information for a stored file. Thisinformation can be corrected.



ANR4278E Audit command: Invalid file storageinformation detected - It will becorrected.

Explanation: A database audit process finds invalidfile storage information for a stored file. BecauseFIX=YES has been specified for the audit command, theerror will be corrected.



ANR4279E Audit command: Administratoradministrator number assigned to morethan just system authority class.

Explanation: A database audit process finds that anadministrator is assigned to other authority classes.Being assigned with 'SYSTEM' authority supersedes allother classes and the other privilege class entriesshould be deleted.






ANR4280I Audit command: Administratoradministrator number assigned to morethan just system authority class - theother class entries will be deleted.

Explanation: A database audit process finds that anadministrator is assigned to other authority classes.Being assigned with 'SYSTEM' authority supersedes allother classes and the other privilege class entriesshould be deleted. Because FIX=YES has been specifiedfor the command, any authority class other than systemwill be deleted.



ANR4281E Audit command: Administratoradministrator number assigned as anunrestricted policy administrator is alsoassigned as a restricted administrator fordomain domain name.

Explanation: A database audit process finds thespecified administrator is assigned as an unrestrictedpolicy administrator. The specified administrator is alsoassigned as the restricted administrator for thespecified policy domain. The unrestricted policyadministration class supersedes any restricted policyclass definitions for an administrator. Theadministrator’s authority needs to be corrected.



ANR4282I Audit command: Administratoradministrator number assigned as anunrestricted policy administrator is alsoassigned as administrator for domaindomain name - restricted class entry willbe deleted.

Explanation: A database audit process finds thespecified administrator is assigned as an unrestrictedpolicy administrator. The specified administrator is alsoassigned as the restricted administrator for thespecified policy domain. The unrestricted policyadministration class supersedes any restricted policyclass definitions for an administrator. Because FIX=YEShas been specified for the command, the restrictedadministrator policy class will be deleted.



ANR4283E Audit command: Administratoradministrator number assigned as anunrestricted storage administrator is alsoassigned as a restricted administrator forstorage pool storage pool name.

Explanation: A database audit process finds thespecified administrator is assigned as an unrestrictedstorage administrator. The specified administrator isalso assigned as the restricted administrator for thespecified storage pool. The unrestricted storageadministration class supersedes any restricted storageclass definitions for an administrator. Theadministrator’s authority needs to be corrected.



ANR4284I Audit command: Administratoradministrator number assigned as anunrestricted storage administrator is alsoassigned as a restricted administrator forstorage pool storage pool name - restrictedclass entry will be deleted.

Explanation: A database audit process finds thespecified administrator is assigned as an unrestrictedstorage administrator. The specified administrator isalso assigned as the restricted administrator for thespecified storage pool. The unrestricted storageadministration class supersedes any restricted storageclass definitions for an administrator. Because FIX=YEShas been specified for the command, the restrictedadministrator storage class will be deleted.



ANR4285E Audit command: A data-integrity errorwas detected on a storage volume forobject (Object.ID).

Explanation: A database audit process found adata-integrity error for a file stored on a storagevolume, but the specific volume name is not known. Iffix=yes was specified, the audit process will attempt tocorrect the data-integrity error.



ANR4286E Audit command: A correctable storageallocation error detected for volumevolume name.

Explanation: A database audit process finds incorrectblock allocation information for the specified storagevolume; the error can be corrected.





ANR4287E Audit command: Storage allocation errordetected for volume volume name - It willbe corrected.

Explanation: A database audit process finds incorrectblock allocation information for the specified storagevolume; the error will be corrected.



ANR4288E Audit command: Multiple files allocatedthe same disk storage block on volumevolume name.

Explanation: A database audit process finds multiplefiles allocated the same disk storage block on thespecified volume; this error cannot be corrected by theaudit process.



ANR4289E Audit command: Multiple files allocatedthe same disk storage block on volumevolume name.

Explanation: A database audit process finds multiplefiles allocated the same disk storage block on thespecified volume; this error cannot be corrected by theaudit process.



ANR4290I Audit command: License global attributescould not be found - they will becreated.

Explanation: A database audit process cannot find thelicense global attributes. Because FIX=YES has beenspecified for the command, the information is correctedby the creation of the global attributes.



ANR4291I Audit command: License global attributescould not be found.

Explanation: A database audit process cannot find thelicense global attributes.



ANR4292I Audit command: Invalid table activecolumn encountered for license globalattribute - the value will be corrected.

Explanation: A database audit process finds that theactive column license global attribute is invalid.Because FIX=YES has been specified for the command,the active column is reset to a proper value.



ANR4293I Audit command: Invalid table activecolumn encountered for license globalattributes.

Explanation: A database audit process finds that theactive column license global attribute is invalid.



ANR4294I Audit command: A license nodeassignment entry was not found fornode node ID - an entry will be created.

Explanation: A database audit process cannot find thenode assignment entry corresponding to the specifiednode. Since FIX=YES has been specified for thecommand, the required license entry will be createdusing default values.



ANR4295I Audit command: A license nodeassignment entry was not found fornode node ID.

Explanation: A database audit process cannot find thenode assignment entry corresponding to the specifiednode.



ANR4296I Audit command: An invalid license nodeassignment entry was found for nodenode ID - the entry will be deleted.

Explanation: A database audit process finds that thelicense node assignment entry is invalid. BecauseFIX=YES has been specified for the command, the nodeentry is deleted.





ANR4297I Audit command: An invalid license nodeassignment entry was found for nodenode ID.

Explanation: A database audit process finds that thelicense node assignment entry is invalid.



ANR4298I Expiration thread already processing -unable to begin another expirationprocess.

Explanation: The expiration thread is alreadyprocessing. The processing expiration thread is eitheran EXPIRE INVENTORY command or is the automaticbackground expiration process. In either case, anotherexpiration process cannot be started until the currentexpiration process completes or is canceled.

System Action: Current expiration process continues.

User Response: Use the QUERY PROCESS commandto determine the status of the current expirationprocess.

ANR4299I Audit command: Invalid audit intervalencountered for license global attribute -the value will be set to the default.

Explanation: A database audit process finds that theaudit interval license global attribute is invalid. BecauseFIX=YES has been specified for the command, the auditinterval is reset to the default value.



ANR4300I Audit command: Invalid audit intervalencountered for license globalattributes.

Explanation: A database audit process finds that theaudit interval license global attribute is invalid.



ANR4301I Audit command: Invalid last audit dateencountered for license global attribute -the value will be set to 0.

Explanation: A database audit process finds that thelast audit date license global attribute is invalid.Because FIX=YES has been specified for the command,the last audit date is set to 0. The next execution ofAUDIT LICENSES will set a new last audit date.



ANR4302I Audit command: Invalid last audit dateencountered for license global attribute.

Explanation: A database audit process finds that thelast audit date license global attribute is invalid.



ANR4303E Audit command: Inventory references forobject(Object.ID) deleted.

Explanation: A database audit process deleted allinventory references for the specified object ID. Thisprocess corrects a data-integrity error if FIX=YES wasspecified.



ANR4304E Audit command: object name missing entryfor cluster cluster ID - cluster entriesdeleted.

Explanation: A database audit process is missing acorresponding entry for the specified comparison objectand cluster ID. This process indicates a data-integrityerror for the database cluster information. If FIX=YESwas specified, the invalid cluster information will bedeleted.



ANR4305E Audit command: object name missing entryfor cluster cluster ID.

Explanation: A database audit process is missing acorresponding entry for the specified comparison objectand cluster ID. This indicates a data-integrity error forthe database cluster information.



ANR4306I AUDITDB: Processed number of entriesdatabase entries (cumulative).

Explanation: This message indicates the number ofdatabase entries that have been processed duringdatabase audit processing.

System Action: Database audit processing continues.




ANR4307I Audit command: Auditing inventoryexternal space-managed objects.

Explanation: This message is displayed during adatabase audit and indicates that server informationabout external space-managed client objects is currentlybeing examined by the database audit process.



ANR4308I Audit command: External space-managedentry for node node ID and file spacefilespace ID is missing a correspondingspace-managed object entry - theexternal space-managed entry will bedeleted.

Explanation: A database audit process finds that anexternal space-managed entry is missing acorresponding space-managed entry. Because FIX=YEShas been specified, the orphaned externalspace-managed entry is deleted.



ANR4309I Audit command: External space-managedentry for node node ID and file spacefilespace ID is missing a correspondingspace-managed object entry.

Explanation: A database audit process finds that anexternal space-managed entry is missing acorresponding space-managed entry.



ANR4310I Audit command: Auditing inventoryspace-managed objects.

Explanation: This message is displayed during adatabase audit and indicates that server informationabout space-managed client objects is currently beingexamined by the database audit process.



ANR4311I Audit command: Object entry forspace-managed object object.ID notfound - entry will be created.

Explanation: A database audit process cannot find anobject entry for the specified space-managed object.Because FIX=YES has been specified for the command,an object entry is created by using default values.



ANR4312I Audit command: Object entry forspace-managed object object.ID notfound.

Explanation: A database audit process cannot find anobject entry for the specified backup object.



ANR4313I Audit command: Space-managed object(object ID) for node node ID and filespace filespace ID has one or moreincorrect fields - the values will becorrected.

Explanation: A database audit process determinedthat one or more field values for the specifiedspace-managed object is not valid. Because FIX=YESwas specified the values are corrected.



ANR4314I Audit command: Space-managed object(object ID) for node node ID and filespace filespace ID has one or moreincorrect fields.

Explanation: A database audit process determinedthat one or more field values for the specifiedspace-managed object is not valid.



ANR4315I Audit command: Space-managed object(object ID) for node node ID and filespace filespace ID is missing thecorresponding external space managedentry - the entry will be created.

Explanation: A database audit process determines thatthe space-managed object entry is missing acorresponding external space managed entry. BecauseFIX=YES was specified, the missing entry will becreated.





ANR4316I Audit command: Space-managed object(object ID) for node node ID and filespace filespace ID is missing thecorresponding external space managedentry.

Explanation: A database audit process determines thatthe space-managed object entry is missing acorresponding external space-managed entry.



ANR4317I Audit command: External space-managedobject (object ID) for node node ID andfile space filespace ID has one or moreincorrect fields - the values will becorrected.

Explanation: A database audit process determinedthat one or more field values for the specified externalspace-managed object is not valid. Because FIX=YESwas specified, the values will be corrected.



ANR4318I Audit command: External space-managedobject (object ID) for node node ID andfile space filespace ID has one or moreincorrect fields.

Explanation: A database audit process determinedthat one or more field values for the specified externalspace-managed object is not valid.



ANR4319I Audit command: Space-managed objectnot found for object object.ID - objectentry will be deleted.

Explanation: A database audit process cannot find aspace-managed object entry for the specified object.Because FIX=YES was specified the object entry will bedeleted.



ANR4320I Audit command: Space-managed objectnot found for object object.ID.

Explanation: A database audit process cannot find aspace-managed object entry for the specified object.



ANR4321I Audit command: Invalid copy typeencountered for object object.ID - objectfound as an space-managed object -correcting the invalid copy type

Explanation: A database audit process encounters aninvalid copy type for the specified object ID, but findsa corresponding space-managed object for the entry.Because FIX=YES has been specified for the command,the invalid copy type is corrected.



ANR4322E Audit command: Management class classname in policy set set name, domaindomain name does not have a valid spacemanagement technique defined.

Explanation: A database audit process finds amanagement class that does not have a valid valuespecified.



ANR4323E Audit command: Management class classname in policy set set name, domaindomain name does not have a valid spacemanagement technique defined - thedefault value will be set.

Explanation: A database audit process finds amanagement class that does not have a valid valuespecified. Because FIX=YES was specified for theAUDITDB operation, the default space managementtechnique value will be set for the management classspecified.


User Response: Refer to the DEFINE MGMTCLASScommand in the Administrator’s Reference for validvalues.

ANR4324E Audit command: Management class classname in policy set set name, domaindomain name does not have a validAUTOMIGNONUSE value specified.






ANR4325E Audit command: Management class classname in policy set set name, domaindomain name does not have a validAUTOMIGNONUSE value defined - thedefault value will be set.

Explanation: A database audit process finds amanagement class that does not have a valid valuespecified. Because FIX=YES was specified for theAUDITDB operation, the default AUTOMIGNONUSEvalue will be set for the management class specified.



ANR4326E Audit command: Management class classname in policy set set name, domaindomain name does not have a validMIGREQUIRESBKUP value specified.




ANR4327E Audit command: Management class classname in policy set set name, domaindomain name does not have a validMIGREQUIRESBKUP value defined -the default value will be set.

Explanation: A database audit process finds amanagement class that does not have a valid valuespecified. Because FIX=YES was specified for theAUDITDB operation, the default MIGREQUIRESBKUPvalue will be set for the management class specified.



ANR4328W Audit command: Storage pool storage poolname, specified as a space managementdestination for management classmanagement class name, policy set setname, domain domain name, does notexist.

Explanation: A database audit process encounters astorage pool specified for the space managementdestination of the specified management class that isnot defined in the server database. If this managementclass is used in an active policy set, then migrationoperations will fail when attempting to put client datain the destination.


User Response: After the audit command completes,use the DEFINE STGPOOL command to define themissing storage pool or the UPDATE MGMTCLASScommand to update the management class to refer toan existing storage pool.

ANR4329I Audit command: Inactive reference foundfor active backup entry (Object.ID) - theinactive reference will be deleted.

Explanation: A database audit process found that anactive backup entry for the specified object has acorresponding inactive backup entry. Since FIX=YESwas specified for the command, the information iscorrected by deleting the inactive backup object entry.



ANR4330I Audit command: Inactive reference foundfor active backup entry (Object.ID).

Explanation: A database audit process found that anactive backup entry for the specified object has acorresponding inactive backup entry.



ANR4331E command process terminated, nomatching device classes.

Explanation: The server did not find any device classnames matching the specifications entered in theRECONCILE VOLUMES command.


User Response: Use the QUERY DEVCLASScommand to determine which device classes aredefined on the server and reissue the RECONCILEVOLUMES command.

ANR4332W This command will compare all volumesused by the specified device class(es)with the actual data stored on theassociated server for those volumes andwill report any discrepancies; the datawill be inaccessible to users until theoperation completes.

Explanation: During the execution of a RECONCILEVOLUMES command, any data a volume namedwould be unavailable to users.


User Response: Enter 'Y' to reconcile the volumes or'N' to stop the process.



ANR4333W This command will discard anyreferences to volumes used by thespecified device class(es) that aremissing from the associated server,thereby rendering the dataunrecoverable; the valid volumes willbe inaccessible to users until theoperation completes.

Explanation: During the execution of a RECONCILEVOLUMES command, any data on a volume beingreconciled would be unavailable to users. After thecommand has ended, any inconsistent volumes foundwill be discarded.


User Response: Enter 'Y' to reconcile the volumes or'N' to stop the process.

ANR4334I command (Repair) process started,process ID process ID.

Explanation: As the result of a RECONCILEVOLUMES command that specified FIX=YES, theprocess whose ID is displayed has begun reconcilingthe volumes associated with the given device class.

System Action: The volumes are reconciled andinvalid volumes are displayed.


ANR4335I command (Inspect Only) process started,process ID process ID.

Explanation: As the result of a RECONCILEVOLUMES command that specified FIX=NO, theprocess whose ID is displayed has begun reconcilingthe volumes associated with the given device class.

System Action: The volumes are reconciled andinconsistent volumes are displayed.


ANR4336W command process ended, process IDprocess ID.

Explanation: The RECONCILE VOLUMES commandfor the specified device class has ended.


User Response: For complete details on the results ofthe RECONCILE VOLUMES command, examine theprevious messages.

ANR4337W command process terminated - processcanceled.

Explanation: During processing of a RECONCILEVOLUMES command, the process performing thereconcile was canceled.

System Action: The RECONCILE VOLUMEScommand is ended.


ANR4338W command process terminated - sufficientrecovery log space is not available.

Explanation: During processing of a RECONCILEVOLUMES command, the source server does not havesufficient recovery log space to continue.


User Response: If necessary, make more recovery logspace available to the source server.

ANR4339W command process terminated - sufficientdatabase space is not available.

Explanation: During processing of a RECONCILEVOLUMES command, the source server does not havesufficient database space to continue.


User Response: If necessary, make more databasespace available to the source server.

ANR4340W command process terminated - threadresource not available.

Explanation: During processing of a RECONCILEVOLUMES command, the source server cannot start athread for the reconcile process.


User Response: Reissue the RECONCILE VOLUMEScommand. If the error persists, it may indicate ashortage of source server memory.

ANR4341W command process terminated - sufficientmemory is not available.

Explanation: During processing of a RECONCILEVOLUMES command, the source server does not haveenough memory available to complete the command.


User Response: If necessary make more memoryavailable to the source server.



ANR4342W command process terminated - lockconflict detected.

Explanation: During processing of a RECONCILEVOLUMES command, the source server cannot obtain arequired lock.


User Response: Reissue the RECONCILE VOLUMEScommand.

ANR4343W command process terminated - internalserver error detected.

Explanation: During processing of a RECONCILEVOLUMES command, an internal server error occurson the source server.



ANR4344I command started for device class deviceclass (process ID process ID).

Explanation: The RECONCILE VOLUMES processwhose ID is displayed has started reconciling volumesassociated with the given device class.

System Action: The volumes are reconciled andinconsistent volumes are displayed.


ANR4345I command completed for device classdevice class; (process ID process ID);volume count volumes inspected, volumecount invalid volumes found, volumecount volumes deleted.

Explanation: The RECONCILE VOLUMES processwhose ID is displayed has finished reconciling volumesassociated with the given device class. The number ofvolumes reconciled and the number of invalid volumesfound or deleted are displayed.


User Response: For complete details on the results ofthe RECONCILE VOLUMES command for the showndevice class, examine the previous messages.

ANR4346I command completed for device classdevice class; (process ID process ID);volume count volumes inspected, volumecount invalid volumes found.

Explanation: The RECONCILE VOLUMES processwhose ID is displayed has finished reconciling volumesassociated with the given device class. The number of

volumes reconciled and the number of invalid volumesfound are displayed.


User Response: For complete details on the results ofthe RECONCILE VOLUMES command for the showndevice class, examine the previous messages. If yoususpect that volumes were inaccessible because ofcommunications problems, correct the problems andretry the RECONCILE VOLUMES command. If theerrors are valid, reissue the reconcile volumescommand with FIX=YES so that the source server canattempt to correct the information.

ANR4352I Contacting Server server name

Explanation: This message is displayed in response toa QUERY PROCESS command, and indicates that areconciliation process is attempting to obtain volumeinformation from the shown server.

System Action: The reconciliation process continues.



Explanation: This message is displayed in response toa QUERY PROCESS command, and indicates that areconciliation process has been canceled. The processwill end shortly.

System Action: The reconciliation process terminatesand server operation continues.


ANR4354W command: Source server not authorizedto reconcile target server server name.

Explanation: During processing of a RECONCILEVOLUMES command, the source server was notpermitted to reconcile volume on the shown targetserver.


User Response: If the source server should havepermission to reconcile volumes on the shown targetserver, issue the UPDATE SERVER command withFORCESYNC=YES to cause the target server to acceptreconcile operations for the source server. Reissue theRECONCILE VOLUMES command.

ANR4355W command: Volume volume name not valid,source server missing correspondingentry for target server.

Explanation: As the result of a RECONCILEVOLUMES command, the volume shown was reportedby the target server and it has no matching volume onthe source server.




User Response: The database on either the source ortarget server has been regressed by either a RESTOREDATABASE operation or some system facility externalto the server. Investigate the action that caused one orboth of the databases to be regressed to there currentcondition. If a newer database images exist for thatserver, consider restoring the server to that point intime. If the condition of the database on each server isacceptable and the RECONCILE VOLUMES commandwas issued with FIX=NO, reissue the RECONCILEVOLUMES command with FIX=Yes to have the volumedeleted from the target server.

ANR4356W command: Volume volume name not valid,target server missing correspondingentry for source server.

Explanation: As the result of a RECONCILEVOLUMES command, the volume shown was found onthe source server and it has no matching volume on thetarget server.


User Response: The database on either the source ortarget server has been regressed by either an RESTOREDATABASE operation or some system facility externalto the server. Investigate the action that caused one orboth of the databases to be regressed to there currentcondition. If a newer database images exist for thatserver, consider restoring the server to that point intime. If the RECONCILE VOLUMES command wasissued with FIX=Yes and the volume is defined in astorage pool, the access mode of the volume willchanged to unavailable to prevent attempted mountson the source server. If the condition of the database oneach server is acceptable, issue the DELETE VOLUMEor DELETE VOLHISTORY command on the sourceserver to remove the volume from the database.

ANR4357W command: Volume volume name not valid,target server volume refers to deviceclass device class that does not exist onthe source server.

Explanation: As the result of a RECONCILEVOLUMES command, the volume shown was found onthe target server and it is associated with the deviceclass shown. The source server has NO correspondingdevice class.


User Response: The database on either the source ortarget server has been regressed by either an RESTOREDATABASE operation or some system facility externalto the server. Investigate the action that caused one orboth of the databases to be regressed to their currentcondition. If a newer database image exist for thatserver, consider restoring the server to that point intime. In the case of a volume in the VOLHISTORY, thedevice class may have been deleted from the sourceserver. If possible, issue the DEFINE DEVCLASS

command to correct the situation. If the condition ofthe database on each server is acceptable and theRECONCILE VOLUMES command was issued withFIX=NO, reissue the RECONCILE VOLUMEScommand with FIX=Yes to have the volume deletedfrom the target server.

ANR4358W command: Volume volume name not valid,the attributes of the volume on targetserver do not match the attributes on thesource server.

Explanation: As the result of a RECONCILEVOLUMES command, the volume shown was found onboth the source and target server, but the attributesdescribing the volume does not match.


User Response: The database on either the source ortarget server has been regressed by either a RESTOREDATABASE operation or some system facility externalto the server. Investigate the action that caused one orboth of the databases to be regressed to there currentcondition. If a newer database image exist for thatserver, consider restoring the server to that point intime. If the condition of the database on each server isacceptable, additional actions will have to be takenbecause RECONCILE VOLUMES FIX=YES is unable tocorrect this situation. In the case of a volume in theVOLHISTORY, an IMPORT PREVIEW=YES or aRESTORE DATABASE PREVIEW=YES will determinethe integrity of the volume. If the volume is in error, aDELETE VOLHISTORY will remove the volume fromboth the source and target servers. In the case of avolume in a storage pool, an AUDIT VOLUMEFIX=NO will determine the integrity of the volume. Iferrors are found, an AUDIT VOLUME FIX=YES maymake some data on the volume accessible. Otherwise,issue the DELETE VOLUME command on the sourceserver to remove the volume from both the source andtarget servers.

ANR4359W command: Volume volume name not valid,the size of the volume on target serverdoes not match the size on the sourceserver.

Explanation: As the result of a RECONCILEVOLUMES command, the volume shown was found onboth the source and target server, but the size of thevolume does not match.


User Response: The database on either the source ortarget server has been regressed by either an RESTOREDATABASE operation or some system facility externalto the server. Investigate the action that caused one orboth of the databases to be regressed to there currentcondition. If a newer database image exist for thatserver, consider restoring the server to that point intime. If the condition of the database on each server is



acceptable, additional actions will have to be takenbecause RECONCILE VOLUMES FIX=YES is unable tocorrect this situation. In the case of a volume in theVOLHISTORY, an IMPORT PREVIEW=YES or aRESTORE DATABASE PREVIEW=YES will determinethe integrity of the volume. If the volume is in error, aDELETE VOLHISTORY will remove the volume fromboth the source and target servers. In the case of avolume in a storage pool, an AUDIT VOLUMEFIX=NO will determine the integrity of the volume. Iferrors are found, an AUDIT VOLUME FIX=YES maymake some data on the volume accessible. Otherwise,issue the DELETE VOLUME command on the sourceserver to remove the volume from both the source andtarget servers.

ANR4360W command: Volume volume name not valid,the type of the volume on target serverdoes not match the type on the sourceserver.

Explanation: As the result of a RECONCILEVOLUMES command, the volume shown was found onboth the source and target server, but the type of thevolume does not match. For example, the volume onthe target server is defined in a storage pool, but thetarget server indicates that volume was used for aDATABASE BACKUP.


User Response: The database on either the source ortarget server has been regressed by either an RESTOREDATABASE operation or some system facility externalto the server. Investigate the action that caused one orboth of the databases to be regressed to there currentcondition. If a newer database image exists for thatserver, consider restoring the server to that point intime. If the condition of the database on each server isacceptable, additional actions will have to be takenbecause RECONCILE VOLUMES FIX=YES is unable tocorrect this situation. These actions may have to beperformed on one or both servers. Use the QUERYVOLHISTORY and QUERY VOLUME commands onboth servers to determine the volume type on eachserver. In the case of a volume in the VOLHISTORY, aDELETE VOLHISTORY on the appropriate server thatwill remove the volume on that server. In the case of avolume in a storage pool, the DELETE VOLUMEcommand on the appropriate server will remove thevolume on that server.

ANR4361W command: Volume volume name not valid,the target server has reported damage toall or part of the volume.

Explanation: As the result of a RECONCILEVOLUMES command, the volume shown was found onboth the source and target server, but the target serverhas reported damage to all or part of the volume.


User Response: On the target server, an audit withFIX=NO of the volumes in the storage pool used by thesource server will indicate what which volume on thetarget server is damaged. This AUDIT VOLUMEcommand may be able to reset the damaged indicatorin the database if the damage was temporary due tohardware problems (for example, dirty tape heads). Ifthe volume on the target server is in a primary storagepool that has previously been backed up to a copystorage pool, attempt to correct the damage by usingthe RESTORE STGPOOL command. If attempts tocorrect the damage on the target server fail, an AUDITVOLUME command FIX=YES from the source serverwill mark as damaged in the source server databaseeach file that is inaccessible and those files will not beaccessed for future operations. If the files are part of anaggregate, the entire aggregate will be markeddamaged. If a usable copy of the file exists in anotherstorage pool, that copy may be accessed for futureoperations involving the file.

ANR4362W command: Invalid volume volume namedeleted from server server name fordevice class device class.

Explanation: As the result of a RECONCILEVOLUMES command that specified FIX=YES, thevolume shown whose information is displayed isdeleted from the target server.



ANR4363W command: Volume volume name accesschanged to access mode.

Explanation: As the result of a RECONCILEVOLUMES command that specified FIX=YES, theaccess mode of the source volume has been changed tothe value shown.

System Action: The volume’s access mode is changed.

User Response: Review any additional messagesissued by the RECONCILE VOLUMES command andcorrect the errors that set the volume to unavailable, oruse the DELETE VOLUME command to remove it fromthe system.

ANR4364W command: Unable to connect to targetserver server name.

Explanation: During processing of indicatedcommand, the source server was unable to maintaincommunications with the shown target server.

System Action: The command process continues.

User Response: Check both the source server and thetarget server for any additional messages that mightfurther describe the communications problem.



ANR4365W command: Prefix for volume volume namedoes not match the device class prefix.

Explanation: As the result of a RECONCILEVOLUMES command, the volume shown was found onboth the source and target server, but the beginningportion of the high-level archive file name (the prefix)on the target server does not match the prefix in thedevice class on the source server.


User Response: Verify that the prefix in the deviceclass on the source server is correct and update it ifnecessary. Use the RECONCILE VOLUMES FIX=YEScommand on the source server to rename the targetarchive objects to match the device class on the sourceserver.

ANR4366I command: Prefix for volume volume namewas changed to match the device classprefix.

Explanation: As the result of a RECONCILEVOLUMES FIX=YES command, the beginning portionof the high-level archive file name (the prefix) on thetarget server was changed to match the prefix in thedevice class on the source server.

System Action: The prefix is corrected.


ANR4367E Audit command: A storage volumecontaining file data cannot be located -file data may not be accessible.

Explanation: This message is displayed during adatabase audit and indicates that the storage volumecontaining a file’s data cannot be located or is notdefined.


User Response: Reissue the audit command withFIX=YES and the server will attempt to recreate themissing volume definition. If the server cannot recreatethe missing volume information, the server will deletethe inaccessible file data.

ANR4368I Audit command: Attributes for groupgroup.ID and member member.ID are notcorrect - the attributes are corrected.

Explanation: A database audit process determines thatattributes for the specified group ID and member ID donot match attributes for the corresponding primarybackup object. Because FIX=YES was specified for thecommand, the incorrect attributes are corrected.



ANR4369I Audit command: Attributes for groupgroup.ID and member member.ID are notcorrect.

Explanation: A database audit process determines thatattributes for the specified group ID and member ID donot match attributes for the corresponding primarybackup object.


User Response: The AUDITDB process should bere-issued with FIX=YES specified.

ANR4370E The source server is not authorized tocreate volumes on target server servername.

Explanation: The source server has attempted tocreate a volume on the shown target server, but theoperation failed because the source server does nothave the authority to create volumes.


User Response: If the source server should havepermission to create volumes on the shown targetserver, issue the UPDATE SERVER command withFORCESYNC=YES to cause the target server to acceptvolume create operations for the source server. Retrythe failing operation.

ANR4371E Information on the source server doesnot match information on target serverserver name.

Explanation: The source server has determined thatinformation contained on the shown target server nolonger matches information contained on the sourceserver.


User Response: Issue the RECONCILE VOLUMEScommand to determine the problem. If possible, correctthe problem and retry the failing operation.

ANR4372E The password on the source server doesnot match the password on target serverserver name.

Explanation: The source server has attempted toupdate both the source password and the targetpassword. An error occurred that prevented the sourceserver from updating the target server. The passwordsno longer match.


User Response: On the target server, issue theUPDATE NODE command to change the password. Onthe source server, issue the UPDATE SERVERcommand to change the password to match the new



password on the target server. Retry the failingoperation.

ANR4373E Session rejected by target server servername, reason: rejection reason.

Explanation: The source server has attempted to opena session with the shown target server. The session wasrejected for the indicated reason.


User Response: Check both the source server and thetarget server for any additional messages that mightfurther describe the reason the session was rejected. Fora reason of AUTHENTICATION FAILURE, ensure thatboth the source and target servers are using the samepassword. For a reason of NO RESOURCE, ensure thatthe target server is enabled, has sufficient DB, LOG,and memory resource to support the source serversession and that the node name of the source server isnot locked or in use. If this is a routed command, checkto make sure that the administator id being used toroute the command is not locked or in use. For areason of LICENSE FAILURE, ensure that the targetserver is properly licensed to support the source serversession. For a reason of DOWN LEVEL, ensure that thetarget server program is a level new enough to supportthe source server session. For a reason of NODE TYPE,the source server is not allowed to establish a sessionwith the given target server. The NODETYPE on thetarget server is CLIENT. The NODENAME parameterof the server definition on the source server is incorrect.The NODETYPE parameter of the registered node onthe target server is incorrect and should beNODETYPE=SERVER. For a reason of INTERNALERROR, use the messages on the target server todetermine the problem and contact your servicerepresentative. Retry the failing operation.

ANR4374E Session failure, source server detectedan internal error.

Explanation: The source server ends the sessionbecause an internal logic error is detected.

System Action: The source server ends the sessionand continues operation.

User Response: To determine the source of the error,the administrator can examine server messages issuedprior to this message. The QUERY ACTLOG commandcan be used to view the activity log and search formessages. If the error cannot be isolated and resolved,contact your service representative.

ANR4375E Session failure, source server hasinsufficient memory.

Explanation: The source server ends the sessionbecause sufficient memory (virtual memory) is notavailable.



ANR4376E Session failure, target server server nameis locked on the source server.

Explanation: The source server ends the sessionbecause shown target server is locked from sourceserver access.


User Response: Before the source server is permittedto access the target server, a properly authorizedadministrator must unlock the target server.

ANR4377E Session failure, target server server nameis not defined on the source server.

Explanation: The source server ends the sessionbecause shown target server is not defined on thesource server.


User Response: Before the source server is permittedto access the target server, the target server must beproperly defined.

ANR4378E For device class device class, the retry of asession with target server server name hastimed out.

Explanation: The source server has attempted tore-establish a session with the shown target server, butthe RETRYPERIOD from the given device class hasbeen exceeded.

System Action: The source server ends the operation.

User Response: Determine it the target server ishaving a problem or considering increasing theRETRYPERIOD value.

ANR4379E The source server was unable to updatethe password on target server servername.

Explanation: The source server has attempted toupdate the target password. An error occurred thatprevented the source server from updating the targetserver.


User Response: On the target server, determine thecause of the problem and correct it. It may be necessaryfor an administrator to correct the passwords with the



following actions. On the target server, issue theUPDATE NODE command to change the password. Onthe source server, issue the UPDATE SERVERcommand to change the password to match the newpassword on the target server. Retry the failingoperation.

ANR4380E The source server was unable to updatethe server validation key on targetserver server name.

Explanation: The source server has attempted toupdate it’s server validation key on the target server.An error occurred that prevented the source serverfrom updating the target server.


User Response: On the target server, determine thecause of the problem and correct it. It may be necessaryfor an administrator to correct the keys with thefollowing actions. On the source server, issue theUPDATE SERVER command with FORCESYNC=YES tocause an attempt to synchronize the keys on both thesource and target servers. Retry the failing operation.

ANR4381E The source server was unable to registerwith target server server name.

Explanation: The source server has attempted toregister with the shown target server. An error occurredthat prevented the source server from registering withthe target server.


User Response: Ask an authorized administrator tosubmit the request on the use of the target server usingREGISTER NODE command. Retry the failingoperation.

ANR4382E Session failure, policy information fromtarget server server name is incomplete,missing policy object.

Explanation: The source server ends the sessionbecause the shown target server has provided policyinformation which is incomplete. The missing policyobject is shown.


User Response: Use the appropriate commands on thetarget server to complete the policy definitions beingused by the source server. Retry the failing operation.

ANR4383E Session failure, target server server namehas aborted current transaction; reason:abort reason.

Explanation: The source server ends the sessionbecause the shown target server has aborted the current

transaction for the given reason.


User Response: Check both the source server and thetarget server for any additional messages that mightfurther describe the reason the transaction was aborted.Retry the failing operation.

ANR4384E Node node name is not allowed toestablish a session as a target server.

Explanation: The node specified has attempted toestablish a session with this system and this is notpermitted due to the NODETYPE for this node.


User Response: To allow the specified node toestablish a session as a target server, the node must beregistered with a NODETYPE of SERVER. Or elsechange the node name on the target server to a nodename that is allowed to establish a session using anode name that was registered with theNODETYPE=SERVER parameter specified.

ANR4385I Session retry in progress with targetserver server name.

Explanation: The source server is attempting tore-establish a session with the shown target server.Session retry processing occurs when the source serverhas lost the connection with a target server and aRETRYPERIOD value is specified,

System Action: The source server attempts to contactthe target server.

User Response: Determine if the target server ishaving a problem and considering canceling theoperation on the source server or correcting theproblem with the target server.

ANR4386I Session retry was successful for targetserver server name.

Explanation: The source server has re-establish asession with the shown target server.

System Action: Source server processing continues.


ANR4387E Session session number for node nodename (client platform) refused - nodename not registered as TYPE=CLIENT.

Explanation: The server refuses a request to start aclient session because the client node name is notregistered as a node of TYPE=CLIENT. This node nameis already in use either as a server definition as definedby a DEFINE SERVER command or else as a node ofTYPE=SERVER using the REGISTER NODE command.




User Response: Issue a QUERY NODE TYPE=SERVERor a QUERY SERVER to determine which serverdefinition already is using this node name. This clientshould be registered using the REGISTER NODETYPE=CLIENT command and specify a name that isnot in use by any other nodes or server defined to thisserver.

ANR4388W No expiration process to cancel.

Explanation: The CANCEL EXPIRATION commandwas issued but there were no expiration processescurrently running.



ANR4389I Expiration process cancelled.

Explanation: The CANCEL EXPIRATION commandwas issued and successfully cancelled the currentprocess.



ANR4390E CANCEL EXPIRATION failed - unableto cancel expiration process.

Explanation: The CANCEL EXPIRATION commandwas issued but encountered an error. Due to this error,the command was unable to cancel the process.


User Response: Issue the command QUERY PROCESSto determine the process number for the expirationprocess and then issue the command CANCELPROCESS for that process number. This will cancel thecurrent expiration process.

ANR4391I Expiration processing node node name,filespace filespace name, fsId filespace id,domain domain name, and managementclass management class name - for typetype files.

Explanation: Expiration processing is currentlyevaluating information for the node, filespace, domainname, and management class specified for the file typeindicated.



ANR4395I Audit command: Invalid node typeencountered for node node name.

Explanation: A database audit process encounters aninvalid node type for the node indicated, and FIX=YESwas not specified.


User Response: You may want to run this commandagain, specifying FIX=YES so that the audit process cancorrect the problem.

ANR4396I Audit command: Invalid node typeencountered for node node name. Thedefault type will be set.

Explanation: A database audit process encounters aninvalid node type for the node indicated. BecauseFIX=YES has been specified, the audit function sets thenode’s type to the default value.


User Response: If you want the node type for thespecified node to be other than the default, you mustremove and re-register the node with the correct typeafter the audit command has completed.

ANR4397E Audit command: An invalid data formatwas encountered for storage pool storagepool name.

Explanation: A database audit process encounters aninvalid data format for the specified storage pool.



ANR4398E Audit command: An invalid data formatwas encountered for storage pool storagepool name - the data format will beassigned its default value.

Explanation: A database audit process encounters aninvalid data format for the specified storage pool.

System Action: Because FIX=YES has been specifiedfor the command, the audit process assigns the defaultvalue to the data format. Audit processing continues.

User Response: If you want the data format for thespecified storage pool to be other than the default, youmust delete and re-define the storage pool with thedesired type after the audit command has completed.

ANR4399I Expiration processing node node name -for backupset type files.

Explanation: Expiration processing is currentlyevaluating information for backup sets for the nodespecified.





ANR4402I Database Dump command: Databaseupdate activity resumed

Explanation: Database update activities that weresuspended by the database dump process are restarted.



ANR4403I Database Load command: Database dumpimage is consistent - a database audit(AUDITDB) will NOT be required ifthis load completes successfully.

Explanation: The database dump that is currentlybeing loaded by the LOADDB process is a consistentdatabase image. This process implies that a databaseaudit (AUDITDB) will not be required if the loadcompletes successfully.

System Action: Server database load processingcontinues.

User Response: None

ANR4404I Database Load command: Loaded aconsistent dump image - a databaseaudit (AUDITDB) is NOT required.

Explanation: The database dump image loaded by theLOAD command was consistent. A database audit(AUDITDB) is not required. The server may be startednormally.

System Action: Server database load processingcompletes.


ANR4405I Database Load command: Loaded aninconsistent dump image - a databaseaudit (AUDITDB) IS REQUIRED withFIX=YES.

Explanation: The database dump image loaded by theLOAD command was not consistent. A database audit(AUDITDB) with FIX=YES is required to return thedatabase to a consistent state.

System Action: Server database load processingcompletes.

User Response: To check the database forinconsistencies and correct any inconsistencies, use thedatabase audit (AUDITDB) utility as described in theAdministrator’s Reference.

ANR4406I Audit command: Client option Clientoption name sequence number optionsequence number is not a member of anoptionset. The option will be deleted.

Explanation: A database audit process found that thespecified client option does not have a correspondingoptionset. The option is deleted.



ANR4407I Audit command: Client option Clientoption name sequence number optionsequence number is not a member of anoptionset.

Explanation: A database audit process found that thespecified client option does not have a correspondingoptionset. The option is deleted.



ANR4408I Audit command: Client option Clientoption name sequence number optionsequence number in optionset optionsetname is not a valid option. The optionwill be deleted.

Explanation: A database audit process found that thespecified client option is not a valid option. The optionis deleted.



ANR4409I Audit command: Client option Clientoption name sequence number optionsequence number in optionset option set isnot a valid option.

Explanation: A database audit process found that thespecified client option is not a valid option.



ANR4410I Triggered space expansion will beretried in number of seconds seconds.

Explanation: Because of a problem encounteredduring a triggered space expansion for the databaseand/or recovery log, the current expansion stops butwill be retried after the time period shown.

System Action: The system waits for the specifiedperiod and then retries to expand the database and/orrecovery log.



User Response: If possible, correct the condition thatstopped the expansion. If the problem persists, contactyour service representative.

ANR4411I Triggered space expansion retry delayended; checking space trigger criteria.

Explanation: Because a triggered space expansion hadbeen stopped due to a problem, the system waitedbefore retrying. The retry wait period has ended, andthe system can now retry to expand space for thedatabase and/or recovery log.

System Action: Space expansion begins.


ANR4412I Data Base and Recovery Log Spaceexpansion triggered.

Explanation: A triggered space expansion had started.

System Action: Space expansion begins.


ANR4413I Recovery Log Space expansion IsNeeded, megabytes needed Megabytesneeded.

Explanation: The recovery log is above the utilizationpercentage defined in a DEFINE SPACETRIGGER LOGcommand. An expansion of the indicated number ofmegabytes are needed to be above the space triggerutilization value.

System Action: Space expansion begins if supportedon this platform.


ANR4414I Data Base Space expansion Is Needed,megabytes needed Megabytes needed.

Explanation: The database is above the utilizationpercentage defined in a DEFINE SPACETRIGGER DBcommand. An expansion of the indicated number ofmegabytes are needed to be above the space triggerutilization value.

System Action: Space expansion begins if supportedon this platform.


ANR4415I Data Base and Recovery Log SpaceExpansion Completed.

Explanation: A triggered space expansion hadcompleted.

System Action: Normal operations resume.


ANR4416W Unable to Determine Maximum Numberof Data Base Volume Copies, rc=returncode.

Explanation: The Data Base Space Trigger was in theprocessing of expanding the data base by creating newdatabase volumes. In doing so, the maximum numberof copy volumes for any database volume isdetermined. The process of determining this valuefailed.

System Action: Server operation continues. Noadditional database copy volumes are created duringthis database space expansion.

User Response: Use the Query DBVOL command todetermine if your database volume configuration issatisfactory. You may use the DEFINE DBCOPYcommand to define additional database volume copies,if necessary.

ANR4417W Unable to Create Data Base CopyVolume Data Base Copy Volume forvolume Data Base Volume.

Explanation: The Data Base Space Trigger was in theprocessing of expanding the data base by creating newdatabase volumes. In doing so, database copy volumesare created for mirroring. The indicated database copyvolume could not be created for the primary databasevolume named.

System Action: Server operation continues. Adatabase copy volume is not created for the indicatedprimary volume.

User Response: Use the Query DBVOL command todetermine if your database volume configuration issatisfactory. You may use the DEFINE DBCOPYcommand to define additional database volume copies,if necessary.

ANR4418W Unable to Define Data Base CopyVolume Data Base Copy Volume forvolume Data Base Volume.

Explanation: The Data Base Space Trigger was in theprocessing of expanding the data base by creating newdatabase volumes. In doing so, database copy volumesare created for mirroring. The indicated database copyvolume was created for the primary database volumenamed, but could be registered with the server.

System Action: Server operation continues. Adatabase copy volumes is not registered for theindicated primary volume. The database copy volumestill exists on the system.

User Response: Use the Query DBVOL command todetermine if your database volume configuration issatisfactory. You may use the DEFINE DBCOPYcommand to retry the definition of the databasevolume copy, if necessary.



ANR4419W Unable to Determine Maximum Numberof Recovery Log Volume Copies,rc=return code.

Explanation: The Recovery Log Space Trigger was inthe processing of expanding the recovery log bycreating new recovery log volumes. In doing so, themaximum number of copy volumes for any recoverylog volume is determined. The process of determiningthis value failed.

System Action: Server operation continues. Noadditional recovery log copy volumes are createdduring this recovery log space expansion.

User Response: Use the QUERY LOGVOL commandto determine if your recovery log volume configurationis satisfactory. You may use the DEFINE LOGCOPYcommand to define additional recovery log volumecopies, if necessary.

ANR4420W Unable to Create Recovery Log CopyVolume Recovery Log Copy Volume forvolume Recovery Log Volume.

Explanation: The Recovery Log Space Trigger was inthe processing of expanding the recovery log bycreating new database volumes. In doing so, recoverylog copy volumes are created for mirroring. Theindicated recovery log copy volume could not becreated for the primary recovery log volume named.

System Action: Server operation continues. A recoverylog copy volume is not created for the indicatedprimary volume.

User Response: Use the QUERY LOGVOL commandto determine if your recovery log volume configurationis satisfactory. You may use the DEFINE LOGCOPYcommand to define additional recovery log volumecopies, if necessary.

ANR4421W Unable to Define Recovery Log CopyVolume Recovery Log Copy Volume forvolume Recovery Log Volume.

Explanation: The Recovery Log Space Trigger was inthe processing of expanding the recovery log bycreating new recovery log volumes. In doing so,recovery log copy volumes are created for mirroring.The indicated recovery log copy volume was createdfor the primary recovery log volume named, but couldbe registered with the server.

System Action: Server operation continues. A recoverylog copy volume is not registered for the indicatedprimary volume. The recovery log copy volume stillexists on the system.

User Response: Use the QUERY LOGVOL commandto determine if your recovery log volume configurationis satisfactory. You may use the DEFINE LOGCOPYcommand to retry the definition of the recovery logvolume copy, if necessary.

ANR4422I AUDITDB: Insufficient database spaceto optimze audit processing.

Explanation: A database audit process found thatinsufficient database space is available to optimizeaudit processing. If the audit can process, it will takemuch longer to complete than if the space wasavailable.

System Action: Audit processing continues ofpossible, but may terminate if very little space isavailable.

User Response: Use the dsmserv extend db commandto increase the size of the server datbase and restart thedatabase audit function.

ANR4423I AUDITDB: Insufficient database spaceto continue audit processing.

Explanation: A database audit process found thatinsufficient database space is available to continueaudit processing.

System Action: Audit processing terminates.

User Response: Use the dsmserv extend db commandto increase the size of the server datbase and restart thedatabase audit function.

ANR4424W Database has reached Maximum Size inSpace Trigger.

Explanation: The Data Base Space Trigger wasspecified with a maximum size for the data base. Thatvalue has been reached for the size of the database.

System Action: Server operation continues. Noadditional database space expansion will occur as aresult of the database space trigger.

User Response: None. You may review the spacetrigger settings and use the UPDATE SPACETRIGGERDB command to adjust space trigger values.

ANR4425W Recovery Log has reached MaximumSize in Space Trigger.

Explanation: The Recovery Log Space Trigger wasspecified with a maximum size for the recovery log.That value has been reached for the size of the recoverylog.

System Action: Server operation continues. Noadditional recovery log expansion will occur as a resultof the recovery log space trigger.

User Response: None. You may review the spacetrigger settings and use the UPDATE SPACETRIGGERLOG command to adjust space trigger values.



ANR4426W Recovery Log can no longer beExpanded by the Space Trigger.

Explanation: The Recovery Log Space Trigger wasgoing to automatically expand the recovery log.Expanding the recovery log would cause the recoverylog’s size to exceed 13GB, which is beyond the servermaximum limit for the recovery log.

System Action: Server operation continues, but therecovery log is not automatically expanded. Noadditional recovery log expansion will occur as a resultof the recovery log space trigger.

User Response: None. You may review the spacetrigger settings and use the UPDATE SPACETRIGGERLOG command to adjust space trigger values. You mayalso backup the data base and/or setup a databasebackup trigger to cause the database to be backed upmore often. Backing up the database will decrease therecovery log utilization and you then use the REDUCELOG and DELETE LOGVOLUME command todecrease the size of the recovery log.

ANR4427W One or more Recovery Log Volumesdiffer in number of copy volumes.

Explanation: The Recovery Log Space Trigger was inthe processing of expanding the recovery log bycreating new volumes. . In doing so, copy volumes arecreated for mirroring, and existing volumes areexamined for mirroring. One or more recovery logvolumes was found to have a different number of copyvolumes than other volumes of the same type. It isrecommended that the same number of copy volumesbe created for each volume of the same type (databaseor log).


User Response: Use the QUERY LOGVOL commandto determine if your volume configuration issatisfactory. You may use the DEFINE LOGCOPYcommand to define additional copy volumes, ifnecessary. You may use the DELETE LOGCOPYcommand to delete unnecessary copy volumes.

ANR4428W One or more Data Base Volumes differsin number of copy volumes.

Explanation: The Data Base Space Trigger was in theprocessing of expanding the data base by creating newvolumes. In doing so, copy volumes are created formirroring, and existing volumes are examined formirroring. One or more data base volumes was foundto have a different number of copy volumes than othervolumes of the same type. It is recommended that thesame number of copy volumes be created for eachvolume of the same type (database or log).


User Response: Use the Query DBVOL command todetermine if your volume configuration is satisfactory.

You may use the DEFINE DBCOPY command to defineadditional copy volumes, if necessary. You may use theDELETE DBCOPY command to delete unnecessarycopy volumes.

ANR4429W Unable to Define Recovery Log VolumeRecovery Log Volume.

Explanation: The Recovery Log Space Trigger was inthe processing of expanding the recovery log bycreating new recovery log volumes. The indicatedrecovery log volume was created, but could not beregistered with the server.

System Action: Server operation continues. A recoverylog volume is not registered with the server. Therecovery log copy volume still exists on the system.

User Response: Use the Query LOGVOL command todetermine if your recovery log volume configuration issatisfactory. You may use the DEFINE LOGCOPYcommand to retry the definition of the recovery logvolume copy, if necessary. There will be an additionalmessage in the activity log prior to this messageindicating the reason for the failure.

ANR4430W Unable to Define Data Base VolumeData Base Volume.

Explanation: The Data Base Space Trigger was in theprocessing of expanding the data base by creating newdatabase volumes. The indicated database volume wascreated, but could not be registered with the server.

System Action: Server operation continues. Adatabase volume is not registered with the server. Thedatabase volume still exists on the system.

User Response: Use the Query DBVOL command todetermine if your database volume configuration issatisfactory. You may use the DEFINE DBVOLUMEcommand for the database volume named, to retry thedefinition of the database volume copy, if necessary.There will be an additional message in the activity logprior to this message indicating the reason for thefailure.

ANR4431I Recovery Log now Eligible forExpansion.

Explanation: The Recovery Log Space Trigger haspreviously hit a point where expanding the recoverylog would have caused the recovery log’s size toexceed 13GB, which is beyond the server maximumlimit for the recovery log. This caused automaticrecovery log expansion to be halted. The recovery logsize has shrunk but once again needs expansion and isnow eligible for expansion.

System Action: Server operation continues, and theautomatic recovery log expansion will proceed.

User Response: None. None.



ANR4432W Data Base can no longer be Expandedby the Space Trigger.

Explanation: The Data Base Space Trigger was goingto automatically expand the data base. Expanding thedatabase would cause the size of the database toexceed 500GB, which is beyond the server maximumlimit for the database.

System Action: Server operation continues, but thedatabase is not automatically expanded. No additionaldatabase expansion will occur as a result of therecovery log space trigger until the database size is lessthan the maximum size and the trigger attributes allowit to be expanded to a size less than the maxium.

User Response: None. You may review the spacetrigger settings and use the UPDATE SPACETRIGGERDB command to adjust space trigger values. You mayalso reduce the database size, if possible.

ANR4433I Data Base now Eligible for Expansion.

Explanation: The Data Base Space Trigger haspreviously hit a point where expanding the databasewould have caused the size of the database to exceed500GB, which is beyond the server maximum limit forthe database. This caused automatic database expansionto be halted. The database size has shrunk or the spacetrigger values have been adjusted to allow expansion.

System Action: Server operation continues, andautomatic database expansion may proceed.


ANR4434E Audit command: Password expirationfound for unknown client node nodename.

Explanation: A database audit process finds apassword expiration period for a client node, but theclient node is not defined correctly in the serverdatabase.



ANR4435I Audit command: Password expirationperiod deleted for unknown client nodenode name.

Explanation: A database audit process finds apassword expiration period for a client node, but theclient node is not defined correctly in the serverdatabase. Because FIX=YES has been specified for theaudit command, the audit function deletes thepassword expiration period.



ANR4436E Audit command: Invalid passwordexpiration password expiration period forclient node node name.

Explanation: A database audit process finds an invalidpassword expiration period for a client node.



ANR4437I Audit command: Invalid passwordexpiration period password expirationperiod deleted for client node node name.

Explanation: A database audit process finds an invalidpassword expiration period for a client node. BecauseFIX=YES has been specified for the audit command, theaudit function deletes the password expiration period,causing the default, global password expiration periodto take effect for the client node.


User Response: After the AUDIT commandcompletes, use the QUERY NODE command toexamine the node that was updated. Use the UPDATENODE command to set the correct password expirationperiod for the node.

ANR4438E Audit command: Password expirationfound for unknown administratoradministrator name.

Explanation: A database audit process finds apassword expiration period for an administrator, butthe administrator is not defined correctly in the serverdatabase.



ANR4439I Audit command: Password expirationperiod deleted for unknownadministrator administrator name.

Explanation: A database audit process finds apassword expiration period for an administrator, butthe administrator is not defined correctly in the serverdatabase. Because FIX=YES has been specified for theaudit command, the audit function deletes thepassword expiration period.





ANR4440E Audit command: Invalid passwordexpiration password expiration period foradministrator administrator name.

Explanation: A database audit process finds an invalidpassword expiration period for an administrator.



ANR4441I Audit command: Invalid passwordexpiration period password expirationperiod deleted for administratoradministrator name.

Explanation: A database audit process finds an invalidpassword expiration period for an administrator.Because FIX=YES has been specified for the auditcommand, the audit function deletes the passwordexpiration period, causing the default, global passwordexpiration period to take effect for the administrator.


User Response: After the AUDIT commandcompletes, use the QUERY ADMIN command toexamine the administrator that was updated. Use theUPDATE ADMIN command to set the correct passwordexpiration period for the administrator.

ANR4442E Audit command: Extended attributeextended attribute type is not a validattribute type.

Explanation: A database audit process finds anextended attribute type that is not supported.



ANR4443I Audit command: Invalid extendedattribute extended attribute type has beendeleted.

Explanation: A database audit process finds anextended attribute type that is not supported. BecauseFIX=YES has been specified for the audit command, theaudit function deletes extended attribute.



ANR4444W Command: Input volume volume namecannot be processed.

Explanation: During a DSMSERV DISPLAYDBBACKUPVOLUME command, the server cannotdisplay the necessary information about the specifiedbackup volume.

System Action: The volume is not processed.Processing continues for all the volumes in the givenvolume list.

User Response: Examine previous error messages forthe cause of failure.

ANR4445I Context parameter set to value.

Explanation: Determines if context reporting will begenerated when an ANR9999D error occures. This isturned on or off with the SET CONTEXTmessagingcommand.



ANR4446I Audit command: Auditing addressdefinitions.

Explanation: This message is displayed during adatabase audit and indicates that the name addressdefinitions are being examined by the database auditprocess.



ANR4447E Audit command: An invalid data movertype was encountered for data movername.

Explanation: A database audit process encounters aninvalid data mover type for the specified data mover.



ANR4448E Audit command: An invalid data movertype was encountered for data moverdatamover name - the data mover entrywill be removed.

Explanation: A database audit process encounters aninvalid data mover type for the specified data mover.

System Action: Because FIX=YES has been specifiedfor the command, the data mover entry will beremoved. Audit processing continues.

User Response: If you want the data mover entry tobe defined you must redefine this data mover after theaudit command has completed.



ANR4449E Audit command: An invalid data moverattribute was encountered for data movername.

Explanation: A database audit process encountered aninvalid data mover attribute for the specified datamover.



ANR4450E Audit command: An invalid data moverattribute was encountered for datamover data mover name - the data moverentry will be removed.

Explanation: A database audit process encounters aninvalid data mover attribute for the specified datamover.

System Action: Because FIX=YES has been specifiedfor the command, the data mover entry will beremoved. Audit processing continues.

User Response: If you want the data mover entry tobe defined you must redefine this data mover after theaudit command has completed.

ANR4451E Audit command: An invalid disk attributewas encountered for disk name.

Explanation: A database audit process encountered aninvalid disk attribute for the specified disk.



ANR4452E Audit command: An invalid disk attributewas encountered for disk name - the diskentry will be removed.

Explanation: A database audit process encounters aninvalid disk attribute for the specified disk. BecauseFIX=YES has been specified for the command, the diskentry will be removed.


User Response: If you want the disk entry to bedefined you must redefine this disk after the auditcommand has completed.

ANR4453E Audit command: An invalid sourceattribute was encountered for sourcename and destination destination name

Explanation: A database audit process encountered aninvalid source attribute in a path definiton with thespecified source name and destination name.



ANR4454E Audit command: An invalid sourceattribute was encountered for sourcename and destination destination name -the path entry will be removed.

Explanation: A database audit process encounters aninvalid source attribute in a path definition with thespecified source name and destination name. BecauseFIX=YES has been specified for the command, the pathentry will be removed.


User Response: If you want the TSM server to usethis path you must redefine the source name, verify thedestination name exists, and then redefine the pathafter the audit command has completed.

ANR4455E Audit command: An invalid destinationattribute was encountered for sourcename and destination destination name

Explanation: A database audit process encountered aninvalid destination attribute in a path definiton withthe specified source name and destination name.



ANR4456E Audit command: An invalid destinationattribute was encountered for sourcename and destination destination name -the path entry will be removed.

Explanation: A database audit process encounters aninvalid destination attribute in a path definition withthe specified source name and destination name.Because FIX=YES has been specified for the command,the path entry will be removed.


User Response: If you want the TSM server to usethis path you must redefine the source name, verify thedestination name exists, and then redefine the pathafter the audit command has completed.

ANR4457E Audit command: KEEPMP found forunknown client node node name.

Explanation: A database audit process found aKEEPMP setting for a client node, but the client node isnot defined correctly in the server database.


User Response: If the audit command has not beenissued with FIX=YES specified, reissue the audit



function specifying FIX=YES so that the error can becorrected.

ANR4458I Audit command: KEEPMP setting deletedfor unknown client node node name.

Explanation: A database audit process found aKEEPMP setting for a client node, but the client node isnot defined correctly in the server database. BecauseFIX=YES has been specified for the audit command, theaudit function has deleted the KEEPMP setting.



ANR4459E Audit command: Invalid KEEPMP settingKEEPMP setting for client node nodename.

Explanation: A database audit process found aninvalid KEEPMP setting for a client node.



ANR4460I Audit command: Invalid KEEPMP settingKEEPMP setting deleted for client nodenode name.

Explanation: A database audit process found aninvalid KEEPMP setting for a client node. BecauseFIX=YES has been specified for the audit command, theaudit function has deleted the KEEPMP setting, causingthe default, KEEPMP setting to take effect for the clientnode.


User Response: After the AUDIT commandcompletes, use the QUERY NODE command toexamine the node that was updated. Use the UPDATENODE command to set the correct KEEPMP setting forthe node.

ANR4461E Audit command: TCP name, address andGUID found for unknown client nodenode name.

Explanation: A database audit process found a TCPname, address and globally unique identifer for a clientnode, but the client node is not defined correctly in theserver database.



ANR4462I Audit command: TCP name, address andGUID deleted for unknown client nodenode name.

Explanation: A database audit process found a TCPname, address and globally unique identifer for a clientnode, but the client node is not defined correctly in theserver database. Because FIX=YES has been specifiedfor the audit command, the audit function deletes theTCP name, address and GUID.



ANR4463E Audit command: Invalid TCP name,address or GUID length invalid length forclient node node name.

Explanation: A database audit process found aninvalid TCP name, address or globally unique identiferlength for a client node.



ANR4464I Audit command: Invalid TCP name,address or GUID length invalid lengthdeleted for client node node name.

Explanation: A database audit process found aninvalid TCP name, address or globally unique identiferlength for a client node. Because FIX=YES has beenspecified for the audit command, the audit functionsets the TCP name, address and GUID to blank. Thevalues will be reset when the client signs on to theserver.


User Response: After the AUDIT commandcompletes, use the QUERY NODE command toexamine the node that was updated. The values shouldbe blank.

ANR4465I Audit command: An incorrect transactiongroup size was found for node nodename.

Explanation: A database audit process encountersinvalid information used for controlling the transactiongroup size for the node indicated.





ANR4466I Audit command: An incorrect transactiongroup was found for node node name.This information will be corrected.

Explanation: A database audit process encountersinvalid information used for controlling the transactiongroup size for the node specified. Because FIX=YES hasbeen specified, the audit function corrects theinformation.



ANR4467E Audit command: Data Path Type Path wasfound for unknown client node nodename.

Explanation: A database audit process found a DataPath setting for a client node, but the client node is notdefined correctly in the server database.



ANR4468I Audit command: The Data Path Type Pathsetting was deleted for unknown clientnode node name.

Explanation: A database audit process found a DataPath setting for a client node, but the client node is notdefined correctly in the server database. BecauseFIX=YES has been specified for the audit command, theaudit function has deleted the KEEPMP setting.



ANR4471E Audit command: Invalid TCP address (server-prompted scheduling ) or lengthinvalid length for client node node name.

Explanation: A database audit process found aninvalid TCP address or length for a client node’sserver-prompted scheduling..



ANR4472I Audit command: Invalid TCP name orlength for server-promptedscheduling.invalid length deleted forclient node node name.

Explanation: A database audit process found aninvalid TCP name or length for a client node’sserver-prompted scheduling attributes. BecauseFIX=YES has been specified for the audit command, theaudit function sets the TCP information to blank. Thevalues must be reset with the UPDATE NODEcommand.


User Response: After the AUDIT commandcompletes, use the QUERY NODE command toexamine the node that was updated. The values shouldbe blank.

ANR4473E Audit command: Node missing fromsession initiation attribute for clientnode node name.

Explanation: A database audit process found a sessioninitiation value for a client node’s server-promptedscheduling but the node definition was missing.



ANR4474I Audit command: Node missing fromsession initiation value forserver-prompted scheduling. Attributedeleted for client node node name.

Explanation: A database audit process found a valuefor a client node’s server-prompted session iniiatingattributes, but the node definition was mising. BecauseFIX=YES has been specified for the audit command, theaudit function sets the value to the default. Theattribute must be redefined with the REGISTER orUPDATE NODE commands.


User Response: After the AUDIT commandcompletes, use the QUERY NODE command toexamine the node that was updated.

ANR4475E Audit command: Node missing fromclient address attribute for client nodenode name.

Explanation: A database audit process found clientnode addressing information for a client node’sserver-prompted scheduling but the node definitionwas missing.





ANR4476I Audit command: Node missing fromsession initiation value forserver-prompted scheduling. Attributedeleted for client node node name.

Explanation: A database audit process found clientnode addressing information for a client node’sserver-prompted scheduling but the node definitionwas missing.

Because FIX=YES has been specified for the auditcommand, the audit function deletes the value. Theinformation must be redefined with the REGISTER orUPDATE NODE commands.


User Response: After the AUDIT commandcompletes, use the QUERY NODE command toexamine the node that was updated.

ANR4477E Audit command: An invalid data path typepath setting was found for client nodenode name.

Explanation: A database audit process found anincorrect data path setting for a client node.


User Response: If the audit command has not beenissued with FIX=YES specified, reissue the auditfunction, specifying FIX=YES so that the error can becorrected.

ANR4478I Audit command: An incorrect data pathtype path setting was deleted for clientnode node name.

Explanation: A database audit process found aninvalid data path setting for a client node. BecauseFIX=YES has been specified for the audit command, theaudit function has deleted the Data Path setting,causing the default Data Path setting to take effect forthe client node.


User Response: After the AUDIT commandcompletes, use the QUERY NODE command toexamine the node that was updated. Use the UPDATENODE command to set the correct data path setting forthe node.

ANR4500I Writing sequential volume historyinformation to defined files.

Explanation: The server is updating all sequentialvolume history files defined in the server options filewith information on sequential volume usageinformation. The files updated are those specified withthe VOLUMEHISTORY option in the server optionsfile.



ANR4501I Sequential volume history informationsuccessfully written to file name.

Explanation: The server is updating all sequentialvolume history files defined in the server options filewith information on sequential volume usageinformation. Volume history information wassuccessfully written to the file specified.



ANR4502W No files have been defined forautomatically storing sequential volumehistory information.

Explanation: The server is attempting to update allsequential volume history files defined in the serveroptions file with information on sequential volumeusage information. Because no files were configured forreceiving this information, the automatic operationfails.


User Response: To have the server automaticallyrecord sequential volume history information to assistin server recovery, use the VOLUMEHISTORY optionin the server options file to specify where historyinformation should be written. If you update theoptions file, restart the server.

ANR4510E Server could not write sequentialvolume history information to volumehistory file name.

Explanation: While attempting to write sequentialvolume history information to defined history files, theserver could not write to the file name specified.

System Action: The server does not write volumehistory information to the file specified

User Response: Examine error messages that mayhave been displayed prior to this message and correctany problems, if possible. Make sure that the server hasproper authority to write to the file indicated and thatthere is sufficient space in the file system for the file.On MVS, make sure that the data set has been allocated



and that the server has authority to write to the dataset. After the problem has been corrected, use theBACKUP VOLHISTORY command to write sequentialvolume history information to the file.

ANR4511E Volume history file volume history filename could not be opened.

Explanation: While attempting to write sequentialvolume history information to or read information fromdefined history files, the server cannot open the filename specified.

System Action: The server does not write volumehistory information to or read volume historyinformation from the file specified

User Response: Examine error messages that mayhave been displayed prior to this message and correctany problems, if possible. Make sure that the server hasproper authority to write to the file indicated and thatthere is sufficient space in the file system for the file.On MVS, make sure that the data set has been allocatedand that the server has authority to write to the dataset.

ANR4512E A database transaction failure wasencountered in processing sequentialvolume history information.

Explanation: While attempting to process sequentialvolume history information, the server encountered adatabase transaction error.

System Action: The operation fails. Usage for asequential volume was not properly recorded for laterreference.

User Response: Examine error messages that mayhave been displayed prior to this message and correctany problems, if possible. If this does not resolve theproblem, contact your support representative.

ANR4513E A database lock conflict wasencountered in processing sequentialvolume history information.

Explanation: While attempting to process sequentialvolume history information, the server encountered adatabase locking conflict.

System Action: The operation fails. This usuallymeans that usage for a sequential volume was notproperly recorded for later reference

User Response: Examine error messages that mayhave been displayed prior to this message and correctany problems, if possible. If this does not resolve theproblem, contact your support representative.

ANR4514E Sufficient database space is notavailable for the server while processingsequential volume history information.

Explanation: While attempting to process sequentialvolume history information, the server found thatsufficient database space was not available for updates.


User Response: To increase the amount of databasespace available to the server, an authorizedadministrator can add database volumes by using theDEFINE DBVOLUME command, and extend the size ofthe database by using the EXTEND DB command.

ANR4515E Sufficient recovery log space is notavailable for the server while processingsequential volume history information.

Explanation: While attempting to process sequentialvolume history information, the server finds thatsufficient recovery log space is not available forupdates.


User Response: To increase the amount of databasespace available to the server, an authorizedadministrator can add database volumes by using theDEFINE LOGVOLUME command, and extend the sizeof the database by using the EXTEND LOG command.

ANR4516E Server could not read sequential volumehistory information from any definedfiles.

Explanation: While attempting to read sequentialvolume history information from defined history files,the server finds that it cannot open any of the filesdefined in the server options file.

System Action: The server does not read volumehistory information. If the current server task requiresthis information, the task ends.

User Response: Examine error messages that mayhave been displayed prior to this message and correctany problems, if possible. Make sure that the server hasproper authority to read from the defined volumehistory files. If you are doing a database restore, issueRESTORE DB DEVCLASS=VOL.

ANR4517E No files have been defined for storingsequential volume history information -information cannot be read.

Explanation: The server is attempting to read from atleast one of the volume history files defined in theserver options file. Since no files were defined for this



information the read operation fails.

System Action: Server operation ends.

User Response: You can restore the databasespecifying the volume names for each restore operation(in order) up to the desired point-in-time. If a volumehistory file is available, specify its name in the serveroptions file and retry the operation.

ANR4518E Volume history file file name line linenumber does not have the proper format- read operation fails.

Explanation: The server is attempting to read from avolume history file and encounters a record that doesnot have the proper format.

System Action: Server operation terminates.

User Response: Examine the file specified todetermine if the invalid record can be located andcorrected. If the file is corrupted or does not containvalid volume history entries, it cannot be used for thedesired operation.

ANR4519W Volume History File does not reflectlatest Storage Agent Updates

Explanation: The storage agent failed to have thevolume history file on the server updated with thelatest changes from the storage agent.

System Action: The storage agent continuesprocessing.

User Response: To bypass the problem, a BACKUPVOLHIST command can be issued from an adminclient connected to the server. The problem may be dueto a temporary loss of communication with the server.

ANR4549I Database dump command: A databasedump is already in progress.

Explanation: This message is issued in response to adatabase dump command and indicates that a databasedump cannot be started because a dump is already inprogress.

System Action: Server operation continues. Therequested database dump is not started.

User Response: Only one database dump can bestarted at one time. Use the QUERY PROCESScommand to monitor the dump that is in progress.When completed, issue the database dump commandto start another database dump if required.

ANR4550I Full database backup (process process ID)complete, number of database pages pagescopied.

Explanation: A full database backup process hascompleted. The output volumes used in this backup

may be used during a database restore operation.



ANR4551I Incremental database backup (processprocess ID) complete, number of databasepages pages copied.

Explanation: An incremental database backup processhas completed. The output volumes used in thisbackup may be used in conjunction with any precedingvolumes in the backup series during a database restoreoperation.



ANR4552I Full database backup triggered; startedas process process ID.

Explanation: A background process, triggered by theLOGFULLPCT parameter on a DEFINEDBBACKUPTRIGGER command, was started to backup the full contents of the database. The full databasebackup process is assigned the process ID shown.


User Response: The administrator may query thestatus of the database backup process by using theQUERY PROCESS command, or cancel the process byusing the CANCEL PROCESS command.

ANR4553I Incremental database backup triggered;started as process process ID.

Explanation: A background process, triggered by theLOGFULLPCT parameter on a DEFINEDBBACKUPTRIGGER command, was started toincrementally back up the contents of the database. Theincremental database backup process was assigned theprocess ID shown.


User Response: The administrator may query thestatus of the database backup process by using theQUERY PROCESS command, or cancel the process byusing the CANCEL PROCESS command.

ANR4554I Backed up number of pages backed up ofnumber of pages to back up in currentoperation database pages.

Explanation: Periodically, during a database backup,the server displays the number of pages backed up.





ANR4555I Database backup process process IDcanceled.

Explanation: The database backup process wascanceled by an administrator with the CANCELPROCESS command.

System Action: The database backup process is ended.


ANR4556W Attention: the database backupoperation did not free sufficientrecovery log space to lower utilizationbelow the database backup trigger. Therecovery log size may need to beincreased or the database backup triggerparameters may need to be adjusted.

Explanation: A database backup process hascompleted. The server is running in roll-forward modeand the recovery log utilization remains above thatspecified in the database backup trigger.

System Action: A database backup operation will betriggered. Unless this situation is corrected, databasebackups will be triggered rapidly, one after the other.

User Response: If a database backup operation doesnot free up enough recovery log space to resetutilization below the database backup trigger, therecovery log needs to be extended or the databasebackup trigger updated to a higher log full percentageor a higher log free percentage or a higher minimuminterval.

ANR4560I Triggered database backup will beretried in number of seconds seconds.

Explanation: Because of a problem encounteredduring a triggered database backup, the current backupstops but will be retried after the time period shown.

System Action: The system waits for the specifiedperiod and then retries a database backup.

User Response: If possible, correct the condition thatstopped the database backup. If the problem persists,contact your service representative.

ANR4561I Triggered database backup retry delayended; checking database backup triggercriteria.

Explanation: Because a triggered database backup hadbeen stopped due to a problem, the system waitedbefore retrying. The retry wait period has ended, andthe system can now retry the database backup.

System Action: Database backup begins.


ANR4562I Database backup criteria is no longermet; triggered database backupcanceled.

Explanation: Because a triggered database backup hadbeen stopped due to a problem, the system waitedbefore retrying. The retry wait period has ended, andthe system determined that the criteria for triggering adatabase backup was no longer met.

System Action: The system waits until the databasebackup trigger criteria is met before triggering anotherdatabase backup.


ANR4563I Unable to trigger database backup - adatabase define, delete, extend, reduce,or backup operation is already inprogress.

Explanation: A database backup was triggered, but acommand that is modifying or backing up the databaseis already active.

System Action: The backup stops and the server waitsfor the retry period to expire and then tries thedatabase backup again.


ANR4564I Unable to trigger database backup -sufficient memory is not available.

Explanation: A database backup was triggered, butthere is not enough server memory available.



ANR4565E Unable to trigger database backup -thread resource not available.

Explanation: A database backup was triggered, butthe server cannot start a thread for the backup process.


User Response: If the error persists, it may indicate ashortage of server memory. Allocate additional servermemory.

ANR4570E Database backup/restore terminated -device class device class name not defined.

Explanation: During database backup or restoreprocessing, an error occurred because the specifieddevice class is not defined.



System Action: If the database backup was startedwith the BACKUP DB command, the database backupis ended and server operation continues. If the databasebackup was triggered automatically, the backup stopsand the server waits for the retry period to expire andthen tries the database backup again. A databaserestore is terminated.

User Response: For database backup, make sure thespecified device class is defined. For database restoreprocessing, make sure the device class has a definitionin a device configuration file that is pointed to in theserver options file.

ANR4571E Database backup/restore terminated -insufficient number of mount pointsavailable for removable media.

Explanation: During database backup or restore, theserver cannot allocate sufficient mount points for thevolumes required.

System Action: If the database backup was startedwith the BACKUP DB command, the database backupis ended and server operation continues. If the databasebackup was triggered automatically, the backup stopsand the server waits for the retry period to expire andthen tries the database backup again. A databaserestore is ended.

User Response: For database backup, make moremount points available if necessary. For databaserestore processing, make sure the device class hassufficient mount points defined in the deviceconfiguration information file that is pointed to in theserver options file.

ANR4572E Database restore terminated - excessiveread errors encountered.

Explanation: During database restore, read errorsoccur that prevent the restore from continuing.

System Action: Database restore processing stops.

User Response: Use a different device for the restoreoperation. If the problem persists, contact your servicerepresentative.

ANR4573E Database backup terminated - excessivewrite errors encountered.

Explanation: During database backup, write errorsoccur that prevent the backup from continuing.

System Action: If the database backup was startedwith the BACKUP DB command, the database backupis ended and server operation continues. If the databasebackup was triggered automatically, the backup stopsand the server waits for the retry period to expire andthen tries the database backup again.

User Response: If possible, determine and correct thecause of the write errors. If the problem cannot be

corrected, contact your service representative.

ANR4574E Database backup/restore terminated -data transfer interrupted.

Explanation: During a database backup or restoreoperation, a data transfer operation has beeninterrupted and cannot be continued.

System Action: If the database backup was startedwith the BACKUP DB command, the database backupis ended and server operation continues. If the databasebackup was triggered automatically, the backup stopsand the server waits for the retry period to expire andthen tries the database backup again. A databaserestore is ended.

User Response: If possible, determine and correct thecause of the interruption. If the problem cannot becorrected, contact your service representative.

ANR4575E Database backup/restore terminated -sufficient recovery log space is notavailable.

Explanation: During a database backup or restoreoperation, the server runs out of recovery log space.


User Response: For database backup, make moreserver recovery log space available, if necessary. Fordatabase restore, contact your service representative.

ANR4576E Database backup/restore terminated -sufficient database space is notavailable.

Explanation: During a database backup or restoreoperation, the server runs out of database space.

System Action: If the database backup was startedwith the BACKUP DB command, the database backupis ended and server operation continues. If the databasebackup was triggered automatically, the backup stopsand the server waits for the retry period to expire andthen tries the database backup again. The databaserestore process attempts to set the database capacity tothe required capacity to hold the database beingrestored. If this fails, the restore operation is ended.

User Response: For database backup, make moreserver database space available, if necessary. Fordatabase restore, make sure that the size of the onlinedatabase is at least the same capacity as the databasebeing restored.



ANR4577E Database backup terminated - volumealready in use.

Explanation: During a database backup operation, avolume cannot be used because it is already defined ina storage pool, or has been previously used by anexport, a database dump, or a database backupoperation (as recorded in the volume history) or is inuse by another process.

System Action: If the database backup was startedwith the BACKUP DB command, the database backupis ended and server operation continues. If the databasebackup was triggered automatically, the backup stopsand the server waits for the retry period to expire andthen tries the database backup again.

User Response: Specify a volume that is not in use ordefined in a storage pool, and that has not beenpreviously used for an export, a database dump, or adatabase backup operation as recorded in the servervolume history information. The QUERY VOLUMEcommand may be used to display the names ofvolumes that are defined to server storage pools. TheQUERY VOLHISTORY command may be used todisplay the names of volumes that have been used forexport, database dump, or database backup operations.

ANR4578E Database backup/restore terminated -required volume was not mounted.

Explanation: During a database backup or restoreoperation, a required volume cannot be mounted,because the mount request was canceled.


User Response: Issue the command again or wait forthe server to retry the backup and make sure thenecessary volumes are accessible. If you are restoring adatabase to a given date or doing a roll-forwardrestore, restart the entire restore operation. If you arerestoring a single database backup with COMMIT=NO,reissue the restore command. If you are restoring adatabase backup with COMMIT=YES, restore thecomplete backup series from the beginning.

ANR4579E Database backup/restore terminated -thread resource not available.

Explanation: During a database backup or restoreoperation, the server cannot start a thread for thebackup process.

System Action: If the database backup was startedwith the BACKUP DB command, the database backupis ended and server operation continues. If the database

backup was triggered automatically, the backup stopsand the server waits for the retry period to expire andthen tries the database backup again. A databaserestore is terminated.

User Response: Retry the command or wait for theserver to retry the backup if it was started by thebackup trigger. If the error persists, it may indicate ashortage of server memory.

ANR4580E Database backup/restore terminated -insufficient memory available.

Explanation: During a database backup or restoreoperation, there was not enough server memoryavailable.



ANR4581W Database backup/restore terminated -internal server error detected.

Explanation: During a database backup or restoreoperation, the server encounters an internal error.



ANR4582E Database restore terminated - volumecannot be used.

Explanation: During a database restore operation, avolume has been mounted but cannot be used.

System Action: The restore operation is terminated.

User Response: If a volume list was specified on thecommand, make sure the correct volume is beingspecified and mounted. If no volume list was specified,contact your service representative.

ANR4583E Database backup terminated - outputmedia full and scratch media could notbe mounted.

Explanation: During a database backup operation, anout-of-space condition occurred writing to the



sequential media, and a scratch volume cannot bemounted.

System Action: The database backup is ended andserver operation continues.

User Response: Reissue the command and specifyadditional volume names on the command, or specifySCRATCH=YES.

ANR4584E Database restore terminated -incomplete input volume list.

Explanation: The list of volumes needed for therestore operation was incomplete. At least one volumeneeded for the restore operation is missing from theend of the list.

System Action: The database restore is terminated.

User Response: If you are using a DSMSERVRESTORE DB command with the VOLUMENAMESparameter specified, verify that all the volumes withina database backup operation are included in the list.Ensure that all the volume names are specified in thecorrect sequential order. For a restore withCOMMIT=NO, reissue the last restore command. For arestore with COMMIT=YES, restart the restore from thebeginning of the full backup. If you are using aDSMSERV RESTORE DB command with the TODATEparameter specified, the server created a list of volumesneeded for the restore operation. Examine the volumehistory files to try to determine the error or use adifferent volume history file if available. You can alsorestore the database by specifying the volume namesfor each restore operation up to the desired point intime.

ANR4590I Backup type backup series backup seriesnumber operation backup operation in seriesstream backup stream within operation(always 1) sequence backup volumesequence number in operation taken on dateat time.

Explanation: During a DSMSERV DISPLAYDBBACKUPVOL command, the server displays thenecessary information about a backup volume.

System Action: Processing continues for all volumesin the given volume list.

User Response: You can use this information to createa list of volumes for a database restore when a volumehistory backup file is not available.

ANR4600I Processing volume history file file name.

Explanation: During a DSMSERV RESTORE DBcommand with the TODATE parameter specified, theserver is processing the listed file in order to build alist of volumes needed for the restore operation.



ANR4601E Incomplete volume list found forTODATE date time - retrying.

Explanation: During a DSMSERV RESTORE DBcommand with the TODATE parameter specified, theserver created a list of volumes needed for the restoreoperation, but the list was incomplete.

System Action: The server tries to build the list againusing a different volume history file specified in theserver options file. If no other volume history files areavailable, the server stops processing.

User Response: If the problem persists, examine thevolume history files to try and determine the error. Youcan also restore the database by specifying the volumenames for each restore operation up to the desiredpoint in time.

ANR4602E No volumes found for TODATE datetime.

Explanation: No volumes were found in the volumehistory files that meet the date and time parametersspecified.


User Response: Reissue the command with a validdate and time.

ANR4610E Database volume DB volume name notfound in current configuration.

Explanation: The command specified the name of anonexistent database volume.


User Response: Reissue the command with a validdatabase volume name.

ANR4611E Unable to restore database and rollforward updates - log mode was notpreviously set to ROLLFORWARD.

Explanation: The command specified that the databasebe restored and all updates rolled forward to the mostcurrent state. This process cannot be accomplishedbecause the server recovery log mode was not set toROLLFORWARD; therefore, no update informationexists.


User Response: Reissue the command and specify apoint in time (TODATE/TOTIME) for restore.



ANR4612E Unable to restore database and rollforward updates.

Explanation: The command specified that the databasebe restored and all updates rolled forward to the mostcurrent state. This process cannot be accomplishedbecause the internal list of volumes for the most recentfull/incremental backup series is not available. Possiblereasons include:

v No full backup was taken after setting the recoverylog mode to ROLLFORWARD with a SETLOGMODE command.

v Only snapshot database backups were created.


User Response: Reissue the command and specify apoint in time (TODATE/TOTIME) for restore.

ANR4619I Snapshot database backup seriessnapshot database backup series usingdevice class device class.

Explanation: The device class used for the snapshotdatabase backup is shown.



ANR4620I Database backup series Backup seriesoperation backup operation device classdevice class.

Explanation: The device class used for the backup isshown.



ANR4621I Database backup device class device class.

Explanation: The device class for the backup isshown.



ANR4622I Volume volume sequence number in backupoperation: volume name.

Explanation: The volume sequence and name for afull or an incremental database backup are shown.



ANR4623I Stream stream number in backup operationvolume volume sequence number in backupstream: Volume name.

Explanation: The stream number, volume sequenceand name for a full or an incremental database backupare shown.



ANR4630I Starting point-in-time database restore(commit).

Explanation: A point-in-time database restore with aspecified list of volumes has started. When this restoreis complete, the database will be committed to thepoint in time of this backup.


User Response: If you inadvertently specifiedCOMMIT=YES, restart the restore process from thebeginning, starting with restoring the full backup(backup operation 0).

ANR4631I Point-in-time database restore (commit)complete, restore date date time.

Explanation: A point-in-time database restore with aspecified list of volumes is complete. The date shown isthe date to which the database has been restored.



ANR4632I Starting point-in-time database restore(no commit).

Explanation: A point-in-time database restore with aspecified list of volumes has started. When this restoreis complete, the database will not yet be usable.


User Response: To complete a database restore wherea volume list is specified, specify COMMIT=YES on thecommand when restoring the last set of backupvolumes. If you forgot to specify COMMIT=YES on thecommand, issue the last restore command again withCOMMIT=YES.

ANR4633I Point-in-time database restore (nocommit) complete.

Explanation: A point-in-time database restore with aspecified list of volumes is complete. The database isnot yet usable.


User Response: To complete a database restore wherea volume list is specified, specify COMMIT=YES on the



command when restoring the last set of backupvolumes. If you forgot to specify COMMIT=YES on thecommand, issue the last restore command again withCOMMIT=YES.

ANR4634I Starting point-in-time database restoreto date date time.

Explanation: A point-in-time database restore with theTODATE parameter specified has begun. When thisrestore is complete, the database will be committed tothe point in time of this backup.



ANR4635I Point-in-time database restore complete,restore date date time.

Explanation: A point-in-time database restore with theTODATE parameter specified has completed. Thedatabase is committed to the point in time of thisbackup, which may be different than the TODATEspecified. If this is the case, an additional message willbe displayed.



ANR4636I Starting roll-forward database restore.

Explanation: A roll-forward database restore hasbegun. When this restore is complete, the database willbe returned to its most recent state.



ANR4637I Roll-forward database restore complete.

Explanation: A roll-forward database restore hasended. All database backups in the most currentbackup series have been restored, and all updates tothe database since the most recent backup have beenrolled forward. The database has been returned to itsmost recent state.



ANR4638I Restore of backup series backup seriesnumber operation backup operation in seriesin progress.

Explanation: During a DSMSERV RESTORE DB, theserver displays the backup series and operationcurrently being restored.



ANR4639I Restored number of pages restored ofnumber of pages to restore from currentbackup operation database pages.

Explanation: Periodically, during a DSMSERVRESTORE DB, the server displays the number of pagesrestored from the current backup being restored.



ANR4640I Restored number of database pages pagesfrom backup series backup series numberoperation backup operation in series.

Explanation: At the end of each restored backup, theserver displays the number of database pages restored.



ANR4641I Sequential media log redo pass inprogress.

Explanation: During a DSMSERV RESTORE DB, theprocess of committing incomplete database updates hasbegun.



ANR4642I Sequential media log undo pass inprogress.

Explanation: During a DSMSERV RESTORE DB, theprocess of rolling back incomplete transactions hasbegun.



ANR4643I Processed number of log records logrecords.

Explanation: Periodically, during the commit of apoint-in-time restore or while rolling forward updatesduring a roll forward restore, the server displays thenumber of log records processed.



ANR4644I A full backup will be required for thenext database backup operation.

Explanation: During a point-in-time restore of adatabase, this message is displayed to notify theadministrator that the next database backup takenduring normal operation must be a full backup. Thisprocess is normal for point-in-time database restores.




User Response: At the next server restart, do a fulldatabase backup. A full database backup is startedautomatically if a DBBACKUPTRIGGER is defined.

ANR4645I The restore date reflects the most recentbackup available up to the specifiedTODATE.

Explanation: During a DSMSERV RESTORE DB withthe TODATE parameter, the date of the restored backupwas not identical to the date specified on thecommand. The backup series that was restored is themost recent backup series up to and including thespecified date.


User Response: Make sure the date of the restoreddatabase is satisfactory. If it is not, restore the databaseagain by specifying a different TODATE or by restoringindividual database backups.

ANR4646I Database capacity required for restore isnumber of megabytes megabytes.

Explanation: During a point-in-time restore of adatabase, the size of the database being restored isdisplayed. The available capacity of the online databasevolumes must be at least this size.



ANR4647I Database available capacity is number ofmegabytes megabytes.

Explanation: During a point-in-time restore of adatabase, the available capacity of the online databasevolumes is displayed. This capacity must be as large asthe size of the database being restored.

System Action: If the available capacity of the onlinedatabase volumes is not at least this size, the restorecannot continue.

User Response: If the available capacity of the onlinedatabase is not sufficient, reinstall the server with therequired database size, and try the restore operationagain.

ANR4648I Extending database assigned capacity tonumber of megabytes megabytes.

Explanation: During a point-in-time restore of adatabase, the assigned capacity of the online databaseis smaller than that of the database being restored.However, the available capacity of the online databasevolumes is sufficient for restore.

System Action: The assigned capacity of the onlinedatabase is extended to the size required for restore.


ANR4649I Reducing database assigned capacity tonumber of megabytes megabytes.

Explanation: During a point-in-time restore of adatabase, the assigned capacity of the online databaseis larger than that of the database being restored.

System Action: The assigned capacity of the onlinedatabase is reduced to the size required for restore.


ANR4650E Restore of backup series current seriesoperation current operation is not insequence; last restored backup wasseries previous series operation previousoperation.

Explanation: During a DSMSERV RESTORE DB, abackup volume was mounted that is not in the correctsequence.


User Response: Ensure volume names are specified inthe correct sequential order. For a restore withCOMMIT=NO, reissue the last restore command. For arestore with COMMIT=YES, restart the restore from thebeginning of the full backup.

ANR4651E Restore of backup series current seriesoperation current operation is not insequence; backup is part of another logepoch.

Explanation: During a DSMSERV RESTORE DB, abackup volume was mounted that is not in the correctsequence. The current backup operation cannot berestored in this series because it belongs to the samebackup series from another point in time.


User Response: Restart the database restore from thebeginning of the full backup. Omit all backups from theoffending backup and later from the restore.

ANR4657E SNMP: Failed to connect to server ataddress address, port port.

Explanation: The SNMP client was attempting to runa session with the server at the indicated address andport number in response to an SNMP Get Request,which causes a Server Script to be run. The subagentfailed to connect to the server.

System Action: The SNMP subagent ends this attemptto run the script and continues operation.

User Response: Ensure that the indicated server is upand able to initiate admin clients using the TCP/IPprotocol.



ANR4659E SNMP: Communications failure: badverb received (verb type).

Explanation: The SNMP client encountered an invalidcommunications verb during a session with the serverand is not able to continue processing the session.

System Action: The SNMP session ends and subagentoperation continues.


ANR4660I Connected to SNMP subagent at SNMPsubagent address on port port number.

Explanation: The server has successfully connected tothe SNMP subagent at the indicated address and port.

System Action: The server will now register with thesubagent.


ANR4661E SNMP communication with thesubagent failed because a threadresource was not available.

Explanation: The server could not continue withSNMP communication to the SNMP subagent becausesufficient memory is not available for startingadditional processes on the server.

System Action: The server discontinues SNMPprocessing and server operation continues.

User Response: Allocate additional storage to theserver. For details, issue HELP MEMORY to display theinformation online or see the appendix “ AllocatingAdditional Server Memory”.

ANR4662W Failure sending message to SNMPsubagent.

Explanation: The server experienced an error returncode from TCP/IP while sending to the SNMPsubagent. This message is also issued when the SNMPsubagent has an error sending a verb to the serverwhen acting as an SNMP client. This may be a normalevent if either side of the connection is abruptly ended,as in the case of terminating the subagent program. Theerror is reflected in another message for TCP/IP whichfurther describes the error.

System Action: The session is ended. Server operationcontinues. If a message is being forwarded to an SNMPmanaging node, the message is not sent. If a heartbeatmessage was being sent to the subagent, this heartbeatmessage is lost and the server attempts to re-start itssession with the SNMP subagent.

User Response: If the session is ended as a result ofintentionally stopping either the subagent, no responseis required. Otherwise, ensure that the TCP/IP protocolstack is functioning by using the tools that come with

the particular TCP/IP suite on the platform in use.

ANR4663W Failure receiving message from SNMPsubagent.

Explanation: The server experienced an error returncode from TCP/IP while receiving data from the SNMPsubagent. This may be a normal event if either side ofthe connection is abruptly ended, as in the case ofterminating the subagent program. The error isreflected in another message for TCP/IP which furtherdescribes the error.

System Action: The session is ended. Server operationcontinues. If a heartbeat message was being sent to thesubagent, this heartbeat message is lost and the serverattempts to re-start its session with the SNMPsubagent. If the server was attempting to register to theSNMP subagent, heartbeat messaging will be disableduntil the server is re-started.

User Response: If the session is ended as a result ofintentionally stopping either the subagent, no responseis required. Otherwise, ensure that the TCP/IP protocolstack is functioning by using the tools that come withthe particular TCP/IP suite on the platform in use.

ANR4664W Failure in registering with SNMPsubagent.

Explanation: The server experienced a problem whileattempting to register with the SNMP subagent. Thismay be due to problems with communication or theSNMP subagent being unavailable.

System Action: Heartbeat messaging will be disableduntil the server is re-started.

User Response: Ensure that the subagent is runningand that the TCP/IP protocol stack is functioning byusing the tools that come with the particular TCP/IPsuite on the platform in use.

ANR4665W Failure retrying registration with SNMPsubagent.

Explanation: The server experienced a problem whileattempting to re-register with the SNMP subagent afterlosing contact. This may be due to problems withcommunication or the SNMP subagent beingunavailable.

System Action: Registration is re-tried for a number ofattempts before giving up.




ANR4666W Failure sending heartbeat message toSNMP subagent.

Explanation: The server experienced a problem whileattempting to send a heartbeat message to the SNMPsubagent. This may be due to problems withcommunication or the SNMP subagent beingunavailable.

System Action: The server will attempt to contact theSNMP subagent again and re-synchronize.


ANR4667W Failure retrying heartbeat message toSNMP subagent.

Explanation: The server experienced a problem whileattempting to send a heartbeat message to the SNMPsubagent. This may be due to problems withcommunication or the SNMP subagent beingunavailable.

System Action: The server attempted to contact theSNMP subagent again and re-synchronize, but this toofailed. Heartbeat functions are disabled until the serveris re-started.

User Response: Ensure that the subagent is runningand that the TCP/IP protocol stack is functioning byusing the tools that come with the particular TCP/IPsuite on the platform in use. Re-start the server if theheartbeat function is required.

ANR4668I Connection successfully re-establishedwith SNMP subagent.

Explanation: The server experienced a problem whileattempting to send a heartbeat message to the SNMPsubagent.

System Action: The server was able to successfullyresynchronize with the SNMP subagent.


ANR4669W Heartbeat message was not accepted bySNMP subagent.

Explanation: The server experienced a problem whileattempting to send a heartbeat message to the SNMPsubagent. The SNMP subagent was unable to accept theheartbeat message. If the subagent was stopped andre-started, this is a normal message.

System Action: The server will attempt to contact theSNMP subagent again and re-synchronize.

User Response: Ensure that the subagent is runningand that the TCP/IP protocol stack is functioning byusing the tools that come with the particular TCP/IP

suite on the platform in use.

ANR4670W Failure in opening session with SNMPsubagent.

Explanation: The server experienced a problem whileattempting to open a session with the SNMP subagent.

System Action: Processing continues. Heartbeat andmessage forwarding function will not be available.

User Response: Ensure that the subagent is runningand that the TCP/IP protocol stack is functioning byusing the tools that come with the particular TCP/IPsuite on the platform in use. If heartbeat and messageforwarding functions are required, re-start the server.

ANR4671W SNMP subagent did not acceptregistration of this server.

Explanation: The server experienced a problem whileattempting to open a session with the SNMP subagent.The subagent is available but disallowed registration bythis server.

System Action: Processing continues. Heartbeat andmessage forwarding function will not be available.

User Response: It may be necessary to stop thesubagent and re-start it. Then stop the server andre-start it if heartbeat and message forwardingfunctions are required.

ANR4672W SNMP message forwarding to theSNMP subagent was not started becausea thread resource was not available.

Explanation: The server could not continue withSNMP communication to the SNMP subagent formessage forwarding because sufficient memory is notavailable for starting additional processes on the server.

System Action: The server discontinues SNMPmessage processing and server operation continues.

User Response: Allocate additional storage to theserver. For details, issue HELP MEMORY to display theinformation online or see the appendix “AllocatingAdditional Server Memory”.

ANR4673E Insufficient memory for subagentinitialization (the portion of initializationwhere the allocation of memory failed).

Explanation: The SNMP subagent could not initializedue to the inability to obtain the required memory.

System Action: Initialization of the subagent fails.

User Response: Allocate additonal storage to thesubagent.



ANR4674E Error starting DPI thread - Return code:Return code received from called routine.

Explanation: The SNMP subagent could not start theDPI thread.



ANR4675E Server/subagent protocol violation -invalid (where the protocol breakdownoccurred).

Explanation: The SNMP subagent received anunexpected request from the server.

System Action: The subagent will stop processingrequests from the server sending the invalid requests.


ANR4676E Unable to register another server.

Explanation: The SNMP subagent received a requestto register a new server and was unable to allocate thememory necessary to register the new server.

System Action: The subagent will not register the newserver.


ANR4677I Session established with server name:The name of the registered server..

Explanation: The SNMP subagent completed theregistration of the identified server.

System Action: The subagent will wait for additionalrequests from the server.


ANR4678I Session closed with server name: Thename of the deregistered server..

Explanation: The SNMP subagent completed thederegistration of the identified server.



ANR4679W Messages are no longer being forwardedto the SNMP subagent.

Explanation: The server has encountered multipleerrors in forwarding messages to the SNMP subagent.Messages are no longer being forwarded.

System Action: The server continues operating, butmessages are no longer being forwarded.

User Response: Message forwarding can bere-initialized by either stopping the server and

re-starting it. Message forwarding will also bere-started if the heartbeat function is in use and theserver re-synchronizes with the subagent. Thisre-synchronization occurs if the subagent, dsmsnmp, isstopped for longer than a single heartbeat interval (theheartbeat interval is a server option and appears in theoutput of the QUERY OPT command) and thenrestarted.

ANR4680I DPI subagent (The subagent name.):″Connected″ or ″reconnected″, ready toreceive requests.

Explanation: The subagent has successfully connectedor reconnected to the SNMP agent.

System Action: The subagent is ready to receiverequests from servers.


ANR4681W Connect to SNMP agent failed, willkeep trying.

Explanation: The subagent has failed in an attempt toconnect to the SNMP agent.

System Action: The subagent keeps retrying theconnection.

User Response: Make sure that the SNMP daemon isup, running and correctly configured.

ANR4682W A SNMP agent connection erroroccurred. Attempting to re-establishconnection.

Explanation: An error has occurred in thecommunication between the subagent and the SNMPagent.

System Action: The subagent will attempt toreconnect.


ANR4683E Unable to open trace file ’file name’.

Explanation: An error occurred while opening the filefor writing trace data.

System Action: The subagent continues operationwithout tracing.

User Response: Ensure there is adequate space on thedrive from which you are running the subagent andretry the program.



ANR4684E Trap request failed - RC: Return code fromthe trap request. Server index: Server indexnumber..

Explanation: An error occurred while attempting toprocess a trap request from a server. data.

System Action: The subagent processing continues.


ANR4685E Insufficient memory for subagentinitialization.

Explanation: The SNMP subagent could not initializedue to the inability to obtain the required memory.


User Response: Allocate additional memory to thesubagent.

ANR4686E Insufficient memory for subagent traceinitialization.

Explanation: The SNMP subagent trace could notinitialize due to the inability to obtain the requiredmemory.


User Response: Allocate additional memory to thesubagent.

ANR4687E Server/subagent protocol violation -expecting registration request. Receivedrequest: The value of the request that wasreceived.

Explanation: The SNMP subagent was expecting aregistration request. It actually received somethingother than a registration request.



ANR4688E Server/subagent protocol violation -incorrect request header version.

Explanation: The SNMP subagent received a requestfrom a server that was not at the same maintenancelevel as the subagent.


User Response: Ensure the server and subagent are atthe same maintenance level. If they are, contact yourservice representative.

ANR4689E Invalid request type received (The valueof the request that was received.).

Explanation: The SNMP subagent received anunexpected request from the server.



ANR4690E Unexpected request type (The value of therequest that was received.) in trap dataheader.

Explanation: The SNMP subagent received an invalidtrap request from a server.



ANR4691I DPI subagent (The subagent name.):connected, ready to receive requests.

Explanation: The subagent has successfully connectedto the SNMP agent.

System Action: The subagent is ready to receiverequest from servers.


ANR4692I DPI subagent (The subagent name.):reconnected, ready to receive requests.

Explanation: The subagent has successfullyreconnected to the SNMP agent.

System Action: The subagent is ready to receiverequest from servers.


ANR4693I Interface Driver information will beloaded in quiet mode: Only warningand error messages will be displayed.

Explanation: The server is loading information neededfor the Administrative WEB Interface. To minimizemessage traffic, only error and warning messages willbe displayed.

System Action: When the command completes, WEBadministrative information will be loaded into theserver.




ANR4694E SNMP Subagent Port Confirmation HasFailed.

Explanation: The server was communicatingconfiguration data to the SNMP subagent. An erroroccurred in the exchange. The server could notcommunicate interface information to the subagent.

System Action: The server continues operation. TheSNMP administrative interface is inoperative.

User Response: The most likely cause of this problemis a temporary network failure. The server should bere-started to retry the connection to the SNMPsubagent. If this problem occurs repeatedly, pleasecontact you service representative.

ANR4695E SNMP: Communications Failure inReceiving ″verb type″ verb.

Explanation: The SNMP client encountered acommunications error in using the verb type verb totransfer information to or from the server and anSNMP client.

System Action: The SNMP session ends and serveroperation continues.

User Response: This may not be a problem if theSNMP subagent was terminated while the session wasin progress. Otherwise, ensure that TCP/IPcommunications is running normally.

ANR4697E SNMP: Failed to authenticate to serverat address address, port port.

Explanation: The SNMP client was attempting to runa session with the server at the indicated address andport number in response to an SNMP Get Request,which causes a Server Script to be run. The subagentconnected to the indicated server, but failed inauthentication.

System Action: The SNMP subagent ends this attemptto run the script and continues operation.

User Response: Ensure that the indicated server hasan an administrative id of SNMPADMIN and that thisadminstrative id has sufficient authority to run thescript and commands it contains.

ANR4698E SNMP: Communications Failure inSending ″verb type″ verb (command).

Explanation: The SNMP client encountered acommunications error in using the verb type verb toissue command command.

System Action: The SNMP client session ends andsubagent operation continues.


ANR4699E SNMP: Receive Buffer overflow.

Explanation: The SNMP client encountered anoverflow error in transferring information to or fromthe server.

System Action: The SNMP client session ends andsubagent operation continues.


ANR4700I The server move batch size has been setto new batch size. Move operations thatstart after this point will use the newvalue.

Explanation: A SETOPT commmand was used to setthe value for the move batch size value. This settingdetermines the maximum number of files that aremoved on the server in one database transaction,dependent also on the setting for the move sizethrshold. The setting influences file movement forserver migration, reclmation, storage pool backup, andmove data operations.

System Action: The server uses this new setting formove operations that are started after this message isissued.


ANR4701I The server move size threshold has beenset to new threshold. Move operationsthat start after this point will use thenew value.

Explanation: A SETOPT commmand was used to setthe value for the move size threshold value. Thissetting determines the maximum number of megabytesthat are moved on the server in one databasetransaction, dependent also on the setting for the movebatch size. The setting influences file movement forserver migration, reclmation, storage pool backup, andmove data operations.

System Action: The server uses this new setting formove operations that are started after this message isissued.


ANR4702I The server transaction group maximumhas been set to new value. Client sessionsthat are started after this point will usethe new value.

Explanation: A SETOPT commmand was used to setthe value for the maxmimum number of files that canbe sent from the client in a single database transaction.

System Action: The server uses this new setting forclient sessions that are started after this message isissued.




ANR4703E Invalid key ring filename Key RingFilename

Explanation: The key ring filename specified did notcontain the .kyr extention.


User Response: Rename your key ring filename tocontain the .kyr extention. Reexcute the command withthe new filename.

ANR4704I Key ring filename and password havebeen set. Restart the server to use thenew settings

Explanation: The key ring filename have been set tothe new value specified in the DEFINE KEYRINGcommand.


User Response: Restart the server to use the new keyring information.

ANR4705I The server IDL definitions have notbeen installed. These definitions willneed to be installed for the WebAdministrator interface to work.

Explanation: The server attempted to query the serverIDL interface and found no definitions defined. Becauseof this error the HTTP engine returns a 404 not foundmessage.


User Response: If you would like to use the serverweb administrator interface you will need to:

1. Halt the server.

2. Issue the command DSMSERV RUNFILEdsmserv.idl. For AS/400 command see next step.

3. For AS/400, issue the command STRSVRADSMSVRMODE(*PRPWEB).

4. Restart the server.

ANR4706W Unable to open file Filename to satisfyweb session Session ID.

Explanation: A web browser requested a file and theserver could not find the file on the local file system.Special note, some files requested from the server arenot vaild and are caused by a browser error. Forexample, a request for CommandLineBeanInfo.class isnot a valid file request. However, a request of a GIFimage or HTML page should not produce this error.


User Response: Verify that permission for the file areset correctly and file exists.

ANR4707E Import/Loaddb command operationterminated - incomplete input volumelist.

Explanation: The list of volumes needed to processthe command was incomplete. At least one volumeneeded for the operation is missing from the end of thelist.

System Action: The command operation is ended.

User Response: Issue the command again and makesure the necessary volumes are included in the volumelist.

ANR4708I Native SSL support has been disabled,please use the web proxy.

Explanation: Starting in this version of this productnative Secure Socket Layer support has been removed.This feature has been replace with the web proxy.Support for non-secure http request (COMMMETHODHTTP) has not been disabled.


User Response:

1. Remove COMMMETHOD HTTPS from your optionfile.

2. Install and configure the web proxy. See Quick StartAppendices for more information on how to installand configure the web proxy.

ANR4709W Intervention required to mount volumeVolume Name on Library Manager ServerServer Name.

Explanation: A volume mount is awaiting operatorintervention on the specified library manager server.

System Action: The volume mount operation waitsfor operator intervention.

User Response: Refer to the server consol and/iractivity log on the named library manaer server todetermine the action that needs to be performed tocomplete the mount operation.

ANR4710W Library manager Server Name could notbe contacted to control library LibraryName.

Explanation: The specified library manager servercould not be contacted for control of the named library.

System Action: The server will continue to contact thenamed library manager server. Volume mounts in thelibrary will fail until communication is successful.

User Response: Determine why the named server isnot running or why the network preventscommunication with te named server.



ANR4712E Command: The DEVCLASS parameter isonly valid for volume history typesDBBACKUP or DBSNAPSHOT.

Explanation: The command failed because an invalidvolume history type was specified for the TYPE=parameter.


User Response: Re-issue the command and specify avalid type value.

ANR4713E Command: The ″option″ string is not validfor the Hex Filespace Field.

Explanation: The command indicated specifies a valuethat is not valid for the Hex Filespace parameter.


User Response: Reissue the command with a validentry for the Hex Filespace parameter.

ANR4714I Command filename for filespace filespacename of node node name started asprocess process ID.

Explanation: A file deletion process has started todelete one or more files from the given filespace for thefor given node. The process is assigned the ID specifiedin the message.

System Action: The server starts a backgroundprocess to perform the operation in response to theDELETE FILE command entered by an administrator.

User Response: To obtain status on the file deletionprocess, issue the QUERY PROCESS command. Theprocess may be canceled with the CANCEL PROCESScommand.

ANR4715I DELETE FILE file name (backup/archivedata) for filespace filespace name of nodenode name started.

Explanation: A background server process has started(on the server) to delete files from the given filespacefor the given node.

System Action: The background process deletesbackup and archive objects that match the given filename while server operation continues.

User Response: To obtain status on the file deletionprocess, issue the QUERY PROCESS command. Theprocess may be canceled by an authorizedadministrator using the CANCEL PROCESS command.

ANR4716I DELETE FILE file name (backup data) forfilespace filespace name of node node namestarted.


System Action: The background process deletesbackup objects that match the given file name whileserver operation continues.


ANR4717I DELETE FILE file name (archive data) forfilespace filespace name of node node namestarted.


System Action: The background process deletesarchive objects that match the given file name whileserver operation continues.


ANR4718I DELETE FILE file name canceled forfilespace filespace name of node node name: number of objects objects deleted.

Explanation: A background server process that hasbeen deleting files for the given fliespace of the givennode is canceled by the CANCEL PROCESS command.The number of objects deleted before the cancel endedthe operation are reported in the message.


User Response: No action is required. An authorizedadministrator can issue the DELETE FILE command todelete the remaining files desired.

ANR4719I DELETE FILE file name complete forfilespace filespace name of node node name: number of objects objects deleted.

Explanation: A server process deleting file space datafor the node specified has completed. The total numberof objects deleted is reported in the message.





ANR4723E Storage Agent storage agent name isincompatible with this server. Pleaseupdate the storage agent to the samelevel as this server.

Explanation: A downlevel storage agent has connectto this server. The storage agent version, release, andfix level must exactly match, otherwise data corruptionmay occur. For example, a version 4.1.0.0 storage agentcannot connect to a version 4.2.0.0 server.

System Action: Upgrade the storage agent to the samelevel as the server.


ANR4724E During the backup of node node (Nodeid) filespace filespace name (filespace id) adeletion activity occurred.

Explanation: During full or incremental backupprocessing, files were deleted from the file space. Thefiles were not deleted by expiration, but by some otherprocess, DELETE FILESPACE, DELETE VOLUME,AUDIT VOLUME, or some other administratorcommand that can cause files to be deleted. The filespace image on the server will not be consistent withthe client until an incremental backup is completed forthe node.

System Action: The server will continue processing.

User Response: An incremental backup should bedone for the client node.

ANR4725E Source file(line number): Server lockLocktype, mode Lockmode failed.

Explanation: An internal error occurred in an attemptto obtain a lock during processing.


User Response: Retry the process. If the process failscontact your service representative.

ANR4726I The support module has been loaded.

Explanation: The module indicated has beensuccessfully loaded. Operations involving this modulemay be performed by the server.

System Action: Functions which depend on thismodule may now be performed on the server.


ANR4727E Server Server name is incompatible withthis server. Please update the server tothe same level as this storage agent.

Explanation: The storage agent attempted to connectto a downlevel server. The server version, release, and

fix level must exactly match, otherwise data corruptionmay occur. For example, a version 4.2.0.0 storage agentcannot connect to a version 4.1.0.0 server.

System Action: Upgrade the TSM server to the samelevel as the storage agent.


ANR4728E Server connection to file server Fileserver name failed. Please check theattributes of the file server specifiedduring definition of the datamover.

Explanation: The server attempted to connect to a fileserver. The connection failed because of one of thefollowing possible reasons:

v One of the parameters specified during datamoverdefinition was incorrect: TCP/IP address of the fileserver, user id, password, TCP/IP port

v File server does not support requested NDMPversion

v File server is not accessible

v NDMP server limits the number of opened NDMPsessions

v An unsupported model of the filer server wasdetected

System Action: TSM server backup/restore of the fileserver fails.

User Response: Check if file server is accessiblethrough the network; check each of the attributesspecified during datamover definition; check NDMPversions supported by the file server; check the numberof open NDMP sessions with the file server, verify thatfile server model is supported by TSM server.

ANR4729E Server connection to file server Fileserver name failed. The level of the fileserver operating system is unsupportedby TSM server. Please upgrade the fileserver to the level of the operatingsystem supported by the server.

Explanation: The TSM server was trying to connect toa file server with an unsupported level of the operatingsystem. The server can establish NDMP connectiononly to a file server with supported level of theoperating system. Please check the following site forsupported levels of file server operating systems:http://www.tivoli.com/storage

System Action: The TSM server backup/restore of thefile server fails.

User Response: Upgrade the file server to a supportedlevel of the operating system.



ANR4730E Command: Exceeded allowed number ofcopy storage pools in list.

Explanation: The COPYSTGPOOLS parametercontains a list that exceeds the maximum limit.


User Response: Retry the command with fewer copystorage pools in the list.

ANR4731E Command: Copy storage pool storage poolname is not defined.

Explanation: A DEFINE STGPOOL or UPDATESTGPOOL command contained a copy storage poolthat is not defined.


User Response: Verify that the copy storage poolname stated in the error message is correct. Correct theproblem by using a copy storage pool that alreadyexists or define the copy storage pool. Retry thecommand.

ANR4732E Command: The storage pool storage poolname is not a copy storage pool.

Explanation: A DEFINE STGPOOL or UPDATESTGPOOL command contained a copy storage poolname that is not a copy storage pool.


User Response: Remove the storage pool name fromthe list and retry the command.

ANR4733E Command: The copy storage poolcontains a copy storage pool name thatintroduces a cycle into the storage poolchain.

Explanation: A DEFINE STGPOOL or UPDATESTGPOOL command contained a copy storage poolthat eventually points to the pool being processed.


User Response: Remove the storage pool name fromthe copy storage pool list and retry the command.

ANR4734W Copy storage pool Copy Storage PoolName was removed from the copystorage pool list because of a failure forsession Session Id.

Explanation: The named copy storage pool wasremoved from the storage pool list for the currentsession backup/archive/space management operationbecause of an error. This removal is only for the sessionindicated in the message and does not effect othersession operation.


User Response: The error that occured could be oneof many failure. Look for the following items in theactive log or on the server console. 1. Is the namedcopy storage pool currently unavailable? 2. Have anyI/O error occured on the destination devices (disk ortape drives)? 3. Is the mount limit on the device classcorrectly set?

ANR4735W Server-free processing is not available.Initialization failed.

Explanation: An error occurred while initializingserver-free processing. Server-free data transfer is notavailable to backup and restore images.

System Action: Client backup and restore imagerequests will use lan-based data transfer.

User Response: Check for messages during serverinitialization and correct the error.

ANR4736E Set serverfree is not allowed whenserver-free is not available.

Explanation: Server-free processing did not initialize.Changing the status is not allowed.


User Response: Server-free status may be changedwhen the status is ON or OFF.

ANR4737E Transaction failed for session sessionnumber for node node name (clientplatform) - the copy continue attribute forstorage pool storage pool name preventedfurther retries.

Explanation: During a backup session one or morecopy storage pools associated with the indicatedstorage pool had a failure. The operation was haltedbecause the copy continue option for the indicatedstorage pool caused the process to stop.


User Response: Verify the following: 1. Does thedevice class(es) have enough mount points to satisfythe request? 2. Was the node’s MAXNUMMP valuehigh enough to acquire needed mount points to satisfythe request? 3. Were there any errors reported duringthe transaction regarding I/O or related issues? Thisproblem could also be solved by updating the storagepool’s COPYCONTINUE option to YES using theUPDATE STGPOOL command. Setting this attribute toYES will allow the transaction to continue if one ormore of the above errors occurred.



ANR4738E Command: Storage pool storage pool nameis in use in the copy storage poolparameter for one or more other storagepools.

Explanation: A DELETE STGPOOL command specifiesa pool that is listed as one of the copy storage pool forother storage pools’ COPYSTGPOOLS parameter.


User Response: If necessary, update other storagepools so that they do not reference the pool to bedeleted, and reissue the command.

ANR4739E Either the high level address ( hladdress), low level address( lladdress ), or bothwere entered in error.

Explanation: The high level or low level addressessupplied are incorrect.


User Response: Both the high level address and lowlevel address are required for an address to be valid.Since the high level address and low level address hadnot been defined prior to this update, both are requiredfor the update to succeed. Either the high level addressor low level address is missing from this command.Reissue the command and supply the missing addressrepresented by a ″?″ in this message.

ANR4740W Either the high level address, low leveladdress, or both were never entered forthe specified node( nodename ) and thesession initiation status is beingchanged.

Explanation: When the session initiation status of anode is changed by using the SESSIONINIT parameteron the UPDATE NODE command, the scheduling tableis updated to reflect the address specified with HLAand LLA keywords of the UPDATE NODE command.If one or both of these keywords have never been usedto provide addressing information for the node,server-initiated scheduling will not be able to contactthis node.

System Action: The server does not update thescheduling table. Subsequent server initiated sessionswith the node are likely to fail, unless an additionalUPDATE NODE command provides both theHLADDRESS and LLA parameters with correct addressinformation.

User Response: Both the high level address and lowlevel address are required for an address to be valid.Issue the UPDATE NODE command for this node withcomplete addressing information through theHLADDRESS parameter for the node address, and the

LLADDRESS parameter for the node listen portinformation.

ANR4797E Drive driveName is missing pathinformation. Please check that allrelated paths are defined properly.

Explanation: A drive does not have sufficient pathinformation for the operation to complete. This istypically due to a path not being defined.

System Action: The server fails the storage operation.

User Response: Verify that all applicable paths aredefined for the drive. Also verify that the informationcontained in the paths is correct.

ANR4798E Server-free operation type operation had atarget failure. Please refer toaccompanying messages and MessageReference Manual for furtherinformation.

Explanation: The server-free operation encountered atarget failure. This is typically due to one of threeconditions: 1. A SCSI error was encountered in eitherthe source, target or datamover. 2. There was a problemwith the HBA issuing the SCSI command 3. An I-Oerror caused the operation to time out.

System Action: The server does not complete theserver-free operation and attempts to trigger a failoveroperation by the client.

User Response: If a SCSI error was encountered,please refer to the sense information and correct for theindicated problem. If the HBA had an error whileissuing command, please refer to the accompanyingmessage for appropriate action. If the operation timedout, please verify the datamover operation and SANconnections.

ANR4799E The server-free operation type from devicesource name through data mover datamover name to device target name failedafter issue.

Explanation: The server-free operation failed afterissuing the SCSI command. This is typically due to thevalue for the HBA (host bus adapter) scatter-gatther listnot being large enough.

System Action: The server does not perform theserverfree operation. The server will attempt either aLAN-Free or classic LAN operation.

User Response: Please perform either or both of thefollowing steps to allow serverfree operations. 1.Change the serverfree batchsize to a lower value. 2.Change the MAXIMUMSGLIST value for the HBAwithin the Windows registry.



ANR4800E The server-free operation from devicesource name through data mover datamover name to device target nameencountered an I/O error. The followinginformation was returned from sensedevice name: KEY=Key value ASC=Ascvalue ASCQ=Ascq value SENSE=Sense info

Explanation: The server-free process did not completedue to an I/O error.

System Action: The server will attempt to recoverfrom the error and if possible retry the server-free datatransfer.

User Response: The device reference manual providedwith the device usually contains tables that explain thevalues of the KEY, ASC, and ASCQ fields. If theproblem persists, contact your device servicerepresentative and provide the internal code values andsense data from this message.

ANR4801E The server-free operation from devicesource name through data mover datamover name to device target nameencountered an error. This senseinformation is typically generated byconfiguration issues, please verify thedevice definitions.

Explanation: The server-free process did not completedue to the target being unreachable.

System Action: The server will fail the transfer.

User Response: For the devices involved in thisoperation, please verify that the device and pathdefintions are correct. If this message has been issuedafter the definitions have been verified, please verifythat the hardware is operating correctly and that thedata mover can see both target devices.

ANR4802I Password expiration period for nodenode name has been reset.

Explanation: The node’s password expiration periodhas been reset to the common password expirationperiod.



ANR4803I Password expiration period foradministrator administrator name hasbeen reset.

Explanation: The administrator’s password expirationperiod has been reset to the common passwordexpiration period.



ANR4804I Node node name already uses thecommon password expiration period.

Explanation: The node’s password expiration period iscurrently set to the common password expirationperiod.



ANR4805I Administrator administrator name alreadyuses the common password expirationperiod.

Explanation: The administrator’s password expirationperiod is currently set to the common passwordexpiration period.



ANR4806W The password expiration period for nodename cannot be reset to the commonpassword expiration period.

Explanation: The node’s password expiration periodcould not be reset to the common password expirationperiod at this time.


User Response: Attempt to reset the node’s passwordexpiration period at a later time.

ANR4807W The server is unable to resetadministrator name password expirationperiod to the common passwordexpiration period.

Explanation: The administrator’s password expirationperiod could not be reset to the common passwordexpiration period at this time.


User Response: Attempt to reset the node’s passwordexpiration period at a later time.

ANR4808W The password expiration period for alladministrators and nodes has been resetto the common password expirationperiod.

Explanation: All administrators not managed by aprofile and nodes on this server have had theirpassword expiration period reset to the commonpassword expiration period.





ANR4820E Command The creation date and creationtime are both required to be specified.

Explanation: The server-free process did not completedue to the target being unreachable.

System Action: The server will fail the command.

User Response: Reissue the command, specifying bothcreation date and creation time, or neither of them.

ANR4821E Command: The creation date - date. is notvalid

Explanation: The specified command has been issuedwith an invalid creation date.


User Response: Issue the command with a validcreation date.

ANR4822E Command: The creation time date is notvalid.

Explanation: The specified command has been issuedwith an invalid creation time.


User Response: Issue the command with a validcreation time.

ANR4823E The loading or reading of a table ofcontents for node node name, file spacefile space name failed because sufficientmemory is not available.

Explanation: The server ends a table of contents(TOC) loading or reading for the specified node andfile space because sufficient memory is not available onthe server.

System Action: The TOC loading or reading is endedand server operation continues.

User Response: Allocate additional storage to theserver. For details, issue HELP MEMORY to display theinformation online or see “Appendix. AllocatingAdditional Server Memory”.

ANR4824E The loading or reading of a table ofcontents for node node name, file spacefile space name failed because of a lockconflict.

Explanation: The server ends a table of contents(TOC) loading or reading for the specified node andfile space because the requested resource is already inuse by another process.


User Response: Try the operation again at a latertime.

ANR4825E More than one table of contents isrequested but they are not for the samenode node name and same file space filespace name.

Explanation: The server ends a table of contents(TOC) loading for the requested TOCs. The requestedTOCs have to be for the same file space in the samenode name.


User Response: Try the TOC loading specifying theTOCs in the same node for the same filespace.

ANR4826E The object for the table of contents isnot found in the server for node nodename, file space file space name.

Explanation: The server ends a table of contents(TOC) loading or reading for the object in the specifiednode and file space, because the server cannot find theobject for the TOC.

System Action: The TOC loading or reading is endedand server operation continues. The TOC object couldbe deleted from the server during server expiration orvolume deletion operation.

User Response: Make sure a correct TOC object isspecified.

ANR4827E The loading of a table of contents fornode node name, file space file space namefailed because a thread resource notavailable.

Explanation: The server ends a table of contents(TOC) loading for the specified node and file spacebecause sufficient memory is not available for startingadditional processes on the server.

System Action: The TOC loading is ended and serveroperation continues.

User Response: Allocate additional storage to theserver. For details, issue HELP MEMORY to display theinformation online or see “Appendix. AllocatingAdditional Server Memory”.

ANR4828E The loading or reading of a table ofcontents for node node name, file spacefile space name failed because an internalserver error was detected.

Explanation: The server ends a table of contents(TOC) loading or reading for the specified node andfile space because an internal logic error is detected.

System Action: The TOC loading or reading is ended



and server operation continues.


ANR4829E The loading or reading of a table ofcontents for node node name, file spacefile space name failed. The transaction isstopped.


System Action: The table of contents (TOC) loading orreading is ended and server operation continues.


ANR4830E The loading or reading of a table ofcontents for node node name, file spacefile space name failed. Insufficient mountpoints are available to satisfy therequest.

Explanation: The server was unable to allocatesufficient mount points to read the table of contents(TOC).



ANR4831E The loading or reading of a Table ofContents for node node name, file spacefile space name failed. The input volumeis already in use.

Explanation: During the TOC loading or readingoperation, the requested input volume is already in useby another process.


User Response: Try the operation again at a latertime.

ANR4832E The loading or reading of a table ofcontents for node node name, file spacefile space name failed. The requiredvolume was not mounted.

Explanation: During the table of contents (TOC)loading or reading operation, a required volume cannotbe mounted. The mount request may have beencanceled.


User Response: Try the TOC loading or reading againand make sure the necessary volumes are accessible.

ANR4833W The loading or reading of a table ofcontents for node node name, file spacefile space name failed. The file wasdeleted from server storage.

Explanation: During the table of contents (TOC)loading or reading operation the file has been deletedfrom server storage by another process before theloading or reading is complete.


User Response: Contact your administrator to findout if DELETE FILESPACE, DELETE VOLUME, orinventory expiration processes are running; theseprocesses can delete files in server storage during TOCloading or reading.

ANR4834E The loading or reading of a table ofcontents for node node name, file spacefile space name failed. The data transfer isinterrupted.

Explanation: The server ends a table of contents(TOC) loading or reading for the specified node andfile space because data transfer to or from data storagewas interrupted by an external event.

System Action: The TOC reading is ended and serveroperation continues.

User Response: Examine the messages issued prior tothis message to determine why the data transfer wasinterrupted. Attempt the operation again if the problemcan be resolved.

ANR4835E The reading of a table of contents fornode node name, file space file space namefailed. A data integrity error wasdetected.

Explanation: The server stops reading a table ofcontents (TOC) for the specified node and file spacebecause a data integrity has been encountered on theserver.




User Response: Examine the messages issued prior tothis message and contact your service representative.

ANR4836E The reading of a table of contents fornode node name, file space file space namefailed. There was an error in readingfrom a device.

Explanation: The server ends a table of contents(TOC) reading for the specified node and file spacebecause an I/O error has been encountered by theserver in reading from a device.


User Response: Examine the messages issued prior tothis message that specify the device that is failing. Theserver may need to be shut down with a HALTcommand to correct the hardware problem.

ANR4837I The loading for the table of contents fornode node name, file space file space namestarted.

Explanation: The loading for the table of contents(TOC) in the specified node and file space has beenstarted.



ANR4838I The loading for the table of contents fornode node name, file space file space namewas successful: total entries loadednumber of entries.

Explanation: The loading for the table of contents(TOC) in the specified node and file space has beensuccessfully finished.



ANR4839E The loading for the table of contents fornode node name, file space file space namefailed. See previous messages.

Explanation: The loading for the table of contents(TOC) in the specified node and file space has failed.

System Action: The TOC loading is ended and theserver operation continues.

User Response: Examine the messages issued prior tothis message to determine the source of the problem.

ANR4840I The loading for the table of contents fornode node name, file space file space namewas cancelled.

Explanation: The loading for the table of contents(TOC) in the specified node and file space has beencancelled by the user.



ANR4841E The loading for the table of contents fornode node name, file space file space namefailed. An invalid object type detected.

Explanation: The loading for the table of contents(TOC) in the specified node and file space failedbecause the object type given is different than the onein the server database.


User Response: Re-try the Table of Contents loading,specifying a valid object type.

ANR4842E The loading of a table of contents fornode node name failed. The file spacename was not found.

Explanation: The server ends a table of contents(TOC) loading for the specified node because the servercould not find the file space name for the TOC object tobe loaded.

System Action: The TOC loading is ended and serveroperation continues.

User Response: The file space could be deleted duringthe TOC loading operation. Issue QUERY FILESPACEcommand to verify if the file space is deleted. Makesure the correct file space name is specified. You canissue a QUERY FILESPACE to ensure that the file spaceexists. Re-issue the request with the correct file spacename.

ANR4843I Command: Displayed number of objectsobjects, number of errors errors wereencountered.

Explanation: QUERY TOC has completed. Thenumber of objects displayed and the error count aredisplayed.

System Action: The QUERY TOC command ends andserver operation continues.

User Response: If the error count is not equal to 0,examine the object name displayed. The error countrepresents the number of objects that have their namesdisplayed as ’...’. This is because the conversion from aUTF-8 to a local code page for the file name failed. If



this is the case, re-issue the QUERY TOC commandwith FORMAT=DETAILED. The object name will bedisplayed in a hexadecimal format when theFORMAT=DETAILED is specified. The file may containan invalid character and may need to be renamed. Anew backup copy has to be made for the renamed fileso that the file can be displayed correctly and restoredlater.

ANR4844I Command: The specified table ofcontents for node node name, file spacefile space name contains no entries.

Explanation: The specified table of contents (TOC)exists, but it is empty. No entries are displayed.



ANR4860W The correct value of ARCHRETENTIONfor domain domain name will not be sentto the managed servers. Please upgradethe managed servers to be at least thesame level as that of the configurationmanager.

Explanation: The configuration manager has anARCHRETENTION value that is greater than themanaged server can manage. This is because themanaged server is at a lower level than theconfiguration manager. The value of theARCHRETENTION for the indicated domain is set tothe maximum value that the managed server canprocess.


User Response: To correctly send the value of theARCHRETENTION to the managed servers, pleaseupgrade the managed servers to at least the same levelas that of the configuration manager.

ANR4861W The correct value of RETVER for thearchive copy group domain name policy setname mgmt class name cg name will not besent to the managed servers. Upgradethe managed servers to at least the samelevel as that of the configurationmanager.

Explanation: The configuration manager has aRETVER value that is greater than what the managedserver can process. This is because the managed serveris at a lower level than the configuration manager. Thevalue of the RETVER for the indicated copy group isset to NOLIMIT in the managed server.


User Response: To correctly send the value ofRETVER for the copy group to the managed servers,please upgrade the managed servers to at least thesame level as that of the configuration manager.

ANR4870W Audit command: Storage pool storage poolname, specified as a Table of Contents(TOC) destination for copy group copygroup name in management classmanagement class name, policy set setname, domain domain name, does notexist.

Explanation: A database audit process finds a storagepool specified for the Table of Contents (TOC)destination of the specified copy group that is notdefined in the server database. If this copy group isused in an active policy set, then the NDMP backupwith a TOC creation operation may fail whenattempting to put TOC entries in the destination.


User Response: After the audit command completes,use the DEFINE STGPOOL command to define themissing storage pool, or the UPDATE COPYGROUPcommand to update the copy group to refer to anexisting storage pool.

ANR4946W The character encoding of NDMP filehistory messages for node node name, filesystem file system name is unknown. TheTivoli Storage Manager server will usethe UTF-8 encoding to build a table ofcontents.

Explanation: While initializing a backup with a tableof contents (TOC) for the specified node and filesystem, the TSM server determines that the characterencoding of file history information from the NAS fileserver is unknown. The Tivoli Storage Manager serverwill assume file history information is encoded asUTF-8 in order to build a TOC.

If the character encoding is not UTF-8 and non-Englishcharacters are present, the names will be improperlydisplayed and probably unreadable, making recoverydifficult.

System Action: The operation continues.

User Response: Verify that the encoding of file historyinformation is UTF-8. For Network Appliance NAS fileservers, verify that the volume language for thespecified node and file space is UTF-8, or a subset ofUTF-8 (for example 7-bit ASCII).

ANR4947E The server is unable to translate theUnicode path name while building tableof contents for node node name, filespace file space name. Table of contentscreation fails.

Explanation: While creating a table of contents (TOC),the server attempted to translate the Unicode pathname in the file history message from UCS-2 to UTF-8.The translation failed.

System Action: The TOC creation fails.



User Response: Verify that the required support fortranslations between UCS-2 and UTF-8 is properlyinstalled and configured on the system where the TivoliStorage Manager is running. Try the operation again.

ANR4948E The list file named list file name containsmore than max entry count entries.

Explanation: While reading a list file, the serverdetects that the number of entries exceeds themaximum allowed.


User Response: Consider breaking up the operationinto multiple commands, each handling a subset of therequired entries.

ANR4949E The server is unable to write to tabletable name because there is not enoughtemporary space in the database. Tableof contents operation for node nodename, file space file space name fails.

Explanation: While operating on a table of contents(TOC), the server attempted to insert data into thespecified temporary database table, but there is notenough temporary space in the server’s database.

System Action: The TOC operation fails.

User Response: Ensure that sufficient temporary spaceis available in the server’s database. To increase theamount of database space available to the server, anauthorized administrator can add database volumes byusing the DEFINE DBVOLUME command, and extendthe size of the database by using the EXTEND DBcommand.

ANR4950E The server is unable to retrieve NDMPfile history information while buildingtable of contents for node node name, filespace file space name. NDMP node ID isNDMP node ID. Table of contentscreation fails.

Explanation: While creating a table of contents (TOC),the server attempted to retrieve information containedin a previous NDMP file history message. Theinformation was not found. This could be caused by aproblem with the NAS file server that is sending filehistory messages. The NDMP node ID reported in themessage is the node ID referenced in the currentNDMP file history message.

System Action: The TOC creation fails.

User Response: Verify that the NDMP server isproperly sending file history information. Otherwise,contact your service representative.

ANR4951E The writing of a table of contents fornode node name, file space file space namefailed. The object is excluded fromstorage pool pool name and all successorpools because of its size.

Explanation: The server ends a table of contents(TOC) creation for the specified node. The size of theTOC is larger than that allowed in the storage poolspecified by the TOC destination attribute of theassigned management class backup copy group. Nosuccessor storage pools to the one specified on the copygroup can accept the large TOC.

System Action: The TOC creation is ended and serveroperation continues.

User Response: Increase the maximum file size forone or more of the storage pools in the storagehierarchy to accommodate the TOC. An authorizedadministrator can increase the MAXSIZE parameter byissuing the UPDATE STGPOOL command.

ANR4952E The writing of a table of contents fornode node name, file space file space namefailed. No space is available in storagepool pool name and all successor pools.

Explanation: The server ends a table of contents(TOC) creation for the specified node. The storage poolspecified by the TOC destination attribute of thebackup copy group in the assigned management classdoes not contain enough free space to hold the TOC.No successor storage pools to the one specified on thecopy group contain enough free space.


User Response: An authorized administrator can issuethe DEFINE VOLUME command to add storage to oneor more storage pools in the storage hierarchy. Thisaction may also involve creating storage space by usingan operating system-specific utility.

ANR4953E The writing of a table of contents fornode node name, file space file space namefailed. The server encountered an errorwhen writing to the storage device.

Explanation: The server ends a table of contents(TOC) creation for the specified node because an I/Oerror has been encountered by the server in writing toa device.


User Response: Query the activity log to findmessages preceding this one that specify the failingdevice. Storage pool volumes can be varied offline (byusing the VARY command), or the server may need tobe halted to correct the hardware problem. After theproblem is corrected, try the operation again.



ANR4954E The writing of a table of contents fornode node name, file space file space namefailed. The data transfer wasinterrupted.

Explanation: The server ends a table of contents(TOC) creation for the specified node because datatransfer to or from data storage was interrupted by anexternal event.


User Response: Examine the messages issued prior tothis message to determine why the data transfer wasinterrupted. Attempt the operation again if the problemcan be resolved.

ANR4955E The writing of a table of contents fornode node name, file space file space namefailed. The storage media is notavailable.

Explanation: The server ends a table of contents(TOC) creation for the specified node because storagevolumes are not available in the storage pools in whichthe TOC is to be stored.


User Response: An authorized administrator can issuethe DEFINE VOLUME command to add storage to oneor more storage pools in the storage hierarchy. TheVARY ONLINE command can be used to vary offlinestorage volumes online in the storage hierarchy tomake them available for TOC storage.

ANR4956E The writing of a table of contents fornode node name, file space file space namefailed. The server does not havesufficient recovery log space.

Explanation: The server ends a table of contents(TOC) creation for the specified node because sufficientlog space is not available on the server.



ANR4957E The writing of a table of contents fornode node name, file space file space namefailed. The server does not havesufficient database space.

Explanation: The server ends a table of contents(TOC) creation for the specified node because sufficientdatabase space is not available on the server.


User Response: An authorized administrator can issuethe DEFINE DBVOLUME command to add volumesfor use by the database. Also,an administrator can issuethe EXTEND DB command to extend the size of thedatabase so that the new volumes are used.

ANR4958E The writing of a table of contents fornode node name, file space file space namefailed. The server is unable to start anew thread.

Explanation: The server ends a table of contents(TOC) creation for the specified node because sufficientmemory is not available for starting additionalprocesses on the server.


User Response: Allocate additional storage to theserver. For details, issue HELP MEMORY to display theinformation online, or see “Appendix. AllocatingAdditional Server Memory”.

ANR4959E The writing of a table of contents fornode node name, file space file space namefailed. The server does not havesufficient memory.

Explanation: The server ends a table of contents(TOC) creation for the specified node because sufficientmemory is not available on the server.


User Response: Allocate additional storage to theserver. For details, issue HELP MEMORY to display theinformation online, or see “Appendix. AllocatingAdditional Server Memory”.

ANR4960E The writing of a table of contents fornode node name, file space file space namefailed. The server detected an internalerror.

Explanation: The server ends a table of contents(TOC) creation for the specified node because aninternal logic error is detected.





ANR4961E The writing of a table of contents fornode node name, file space file space namefailed. The server could not commit thetransaction.


System Action: The table of contents (TOC) creation isended and server operation continues.


ANR4962E The writing of a table of contents fornode node name, file space file space namefailed. The server does not havesufficient mount points available tosatisfy the request.

Explanation: The server was unable to allocatesufficient mount points to write the table of contents(TOC).



ANR4963E The writing of a table of contents fornode node name, file space file space namefailed. See previous messages.

Explanation: The server ends a table of contents(TOC) creation for the specified node because aprevious error has occurred.



ANR4980I Auditing Interface Driver definitions.

Explanation: The server is beginning an audit of thedefinitions for Web interface.

System Action: The server will audit all definitionsfor the Web interface and report any problems.


ANR4981E Interface Driver audit completed -Inconsistencies were found.

Explanation: The server found errors during the auditof the definitions for Web interface.

System Action: The Web Interface is not correctlyinstalled. The Web Admin will not work correctly, butthe server may be run without any problems.

User Response: Ensure you are using the correct IDLfile for the server level you are running. Examine errormessages that may have been displayed before and/orafter this message and correct any problems, if possible.If the cause of this can not be determined or resolved,contact your support representative.

ANR4982I Interface Driver audit completed -definitions are consistent.

Explanation: The server successfully completed theinstallation of the definitions for the Web interface.

System Action: The Web Interface is now installed.The server may be run without any problems.


ANR4983I Auditing Interface Driver Groups.

Explanation: The server is auditing the driver groups.

System Action: The server will audit the drivergroups and proceed to the next step.


ANR4984E Error description

Explanation: The server found errors during the auditof the definitions for Web interface.

System Action: The audit will fail.

User Response: Ensure you are using the correct IDLfile for the server level you are running. Examine errormessages that may have been displayed before thismessage and correct any problems, if possible. If thecause of this can not be determined or resolved, contactyour support representative. If you contact yoursupport representative, the entire text of this messageshould be reported.

ANR4985I Auditing Interface Driver GroupMembers.

Explanation: The server is auditing the driver groupmembers.

System Action: The server will audit the driver groupmembers and proceed to the next step.




ANR4986I Auditing Interface Driver Classes.

Explanation: The server is auditing the driver classes.

System Action: The server will audit the driverclasses and proceed to the next step.


ANR4987E Audit processing failed: sufficientmemory is not available for processing.

Explanation: At RUNFILE time, the server is unableto process the IDL data due to insufficient memory.

System Action: Server runfile stops.

User Response: Restart the server runfile process withmore memory available.

ANR4988I Auditing Interface Driver ComplexClass containers.

Explanation: The server is auditing the driver classcontainers.

System Action: The server will audit the driver classcontainers and proceed to the next step.


ANR4989I Auditing Interface Driver Operations.

Explanation: The server is auditing the driveroperations.

System Action: The server will audit the driveroperations and proceed to the next step.


ANR4990I Auditing Interface Driver OperationParameters.

Explanation: The server is auditing the driveroperation parameters.

System Action: The server will audit the driveroperation parameters and proceed to the next step.


ANR4991I Auditing Interface Driver Tasks.

Explanation: The server is auditing the driver tasks.

System Action: The server will audit the driver tasksand proceed to the next step.


ANR4992I Auditing Interface Driver TaskMembers.

Explanation: The server is auditing the driver taskmembers.

System Action: The server will audit the driver taskmembers and proceed to the next step.


ANR4993E The client platform platform name iscurrently not supported by the TSMStorage Agent.

Explanation: At this point in time the storage agentdoes not accept the incomming client platform.



ANR4994E Query whether the volume volume nameis in the library library name failed.

Explanation: An attempt to query if the indicatedvolume is in the specified library failed. It could be thelibrary is offline or the library manager is down in alibrary sharing environment.

System Action: The requested operation failed.

User Response: Re-attempt the request when thelibrary is brought up or when the library manager isup and running in a library sharing environment.

ANR5000E (S/390) Unable to load tape deletion exit.

Explanation: The tape deletion exit module specifiedin the options file cannot be loaded.


User Response: Ensure that the tape deletion exitmodule is in the system linklist or in theJOBLIB/STEPLIB for the server.

ANR5010E (S/390) Unable to initialize disk driver -internal error code from IUCV.

Explanation: The server’s disk driver cannot beinitialized because the error code has been receivedfrom the IUCV DECLARE BUFFER function.


User Response: For a description of the reported errorcode, refer to the IUCV documentation in the CPProgramming Services publication for your specificoperating system.

ANR4986I • ANR5010E (S/390)


ANR5011E (S/390) Unable to open disk vaddr -invalid virtual device address.

Explanation: A disk cannot be opened for processingbecause the specified virtual address is beyond thesupported range. Virtual addresses must be specified inthe range 0001 to FFFF.


User Response: Specify a valid virtual address.

ANR5012E (S/390) Unable to open disk vaddr - errorcode received from FILEDEF.

Explanation: A disk cannot be opened for processingbecause the error code has been received from theFILEDEF command. The server enters one FILEDEFcommand per open disk so that the CMS DISKIDfunction may be used.


User Response: For a description of the FILEDEFerror code, refer to the CMS Command Referencepublication for your operating system.

ANR5013E (S/390) Unable to open disk vaddr -virtual disk not attached.

Explanation: A disk cannot be opened because thevirtual disk is not attached to the server’s virtualmachine.


User Response: Ensure that the VM DASD volumecontaining the disk is online, and that the disk isproperly linked to the server’s virtual machine.

ANR5014E (S/390) Unable to open disk vaddr - errorcode received from DISKID.

Explanation: A disk cannot be opened for processingbecause the error code has been received from theDISKID function.


User Response: For a description of the DISKID errorcode, refer to the CMS Command Reference publicationfor your operating system.

ANR5015E (S/390) Unable to open disk vaddr -internal error code connecting to BlockI/O System Service.

Explanation: A disk cannot be opened for processingbecause the IUCV CONNECT error code is receivedwhen attempting to connect to the CP DASD Block I/OSystem Service.


User Response: For a description of the IUCV

CONNECT error code, refer to the IUCVdocumentation in the CP Programming Servicespublication for your specific operating system.

ANR5016E (S/390) Unable to open disk vaddr - devicetype not supported.

Explanation: A disk cannot be opened for processingbecause its device type is not supported.


User Response: Use only the disk devices supportedby the CP DASD Block I/O System Service.

ANR5017E (S/390) Unable to open disk vaddr - blocksize not supported.

Explanation: A disk cannot be opened for processingbecause its formatted block size is not supported.


User Response: Use only the disks formatted withblock sizes supported by the CP DASD Block I/OSystem Service.

ANR5018E (S/390) Unable to open disk vaddr - IUCVpath already exists to device.

Explanation: A disk cannot be opened because a pathalready exists for this device to the CP DASD BlockI/O System Service.



ANR5019E (S/390) Unable to open disk vaddr -internal error code from Block I/OSystem Service.

Explanation: A disk cannot be opened for processingbecause the connection to the CP DASD Block I/OSystem Service has been severed with error code.


User Response: For a description of the severed errorcode, refer to the documentation for the CP DASDBlock I/O System Service in the CP ProgrammingServices publication for your specific operating system.

ANR5020E (S/390) Unable to open disk vaddr - deviceis read-only.

Explanation: A disk cannot be opened for processingbecause it is accessible only as a read-only device. Allserver disks must be accessible in read/write mode.


User Response: Ensure that the disk is properlylinked in read/write mode.

ANR5011E (S/390) • ANR5020E (S/390)


ANR5021E (S/390) Unable to perform I/O to diskvaddr - internal error code on IUCV send.

Explanation: The IUCV SEND error code is receivedwhen the server attempts to perform I/O to a disk.


User Response: For a description of the IUCV SENDerror code, refer to the IUCV documentation in the CPProgramming Services publication for your specificoperating system.

ANR5022E (S/390) Unable to perform I/O to diskvaddr - permanent error writing to blockblock.

Explanation: The server encounters a permanent errorwhile writing to the specified disk and block.


User Response: Reformat or replace the disk.

ANR5023E (S/390) Unable to perform I/O to diskvaddr - permanent error reading fromblock block.

Explanation: The server encounters a permanent errorwhile reading from the specified disk and block.


User Response: Reformat or replace the disk.

ANR5024E (S/390) Unable to perform I/O to diskvaddr - format error detected.

Explanation: The server encounters a format error onthe specified disk.


User Response: Reformat the disk by using theDSMDISK exec.

ANR5025E (S/390) Disk vaddr has been reset and isno longer available.

Explanation: A disk is reset during operation becausea CP RESET or DETACH command has been enteredfrom the server’s console.

System Action: The disk is marked off-line.

User Response: Ensure that the disk is properlyreattached to the server’s virtual machine.

ANR5026E (S/390) Open of data set dsn failed, returncode rc, reason code reason.

Explanation: Data set dsn cannot be opened.


User Response: Verify that dsn is a VSAM linear data

set. If dsn is a valid VSAM linear data set, contact yourservice representative.

ANR5027E (S/390) Open of DDNAME ddname failed,insufficient memory.

Explanation: The server is unable to open ddnameddname due to a lack of storage.


User Response: Increase the region for the server orlower the MAXSESSIONS parameter in the serveroptions file. There are three ways to do this:

1. On VM, increase the size of the server’s virtualmachine. This requires that the default storage sizebe updated in the server’s CP directory entry.

2. On MVS, increase the size of the REGIONparameter on the JOB or EXEC statement of the JCLused to start the server.

3. Reduce the maximum number of client sessionspermitted. To do this, edit the server options fileand reduce the value specified for theMAXSESSIONS statement. Note that each clientsession causes an additional 64KB of memory to beallocated.

4. Decrease the amount of space allocated to theserver’s database buffer pool. To do this, edit theserver options file and reduce the value specifiedfor the BUFPOOLSIZE statement. Note that eachbuffer pool page causes an additional 4KB ofmemory to be allocated.

Note that the server must be shut down (with theHALT command) before changes can be made to theserver options file.

ANR5028E (S/390) Open of data set dsn failed; zeropages in data set.

Explanation: The VSAM linear data set dsn has nospace. This message appears when:v you issue def vol|dbvol|logvol for a volume that has

not been formatted using the dsmfmt utilityv you run the dsmfmt utility against a data set that is

too smallv an existing data set has been corrupted


User Response: Run the dsmfmt utility, or reallocatethe VSAM linear data set as appropriate.

ANR5030E (S/390) Dynamic allocation of data set dsnfailed, return code rc, error codeerror-code, info code info-code.

Explanation: The dynamic allocation of data set dsnfails. The return code rc, error code error-code andinformation code info-code, are in decimal and can befound in the Dynamic Allocation section of MVS/ESAProgramming: Authorized Assembler Services Guide.

ANR5021E (S/390) • ANR5030E (S/390)



User Response: Ensure that the data set dsn isavailable for allocation by the server.

ANR5032E (S/390) Unable to free DDNAME dsn,return code rc, error code error-code, infocode info-code.

Explanation: The dynamic deallocation of data set dsnfails. The return code rc, error code error-code andinformation code info-code are in decimal and can befound in the Dynamic Allocation section of MVS/ESAProgramming: Authorized Assembler Services Guide.



ANR5033E (S/390) Close of ddname dsn failed, returncode rc, reason code reason.

Explanation: Data set dsn cannot be closed.


User Response: Verify that dsn is a VSAM linear dataset. If dsn is a valid VSAM linear data set, contact yourservice representative.

ANR5034E (S/390) Unable to allocate processor forddname dsn.

Explanation: The number of simultaneous tapessupported by the server has been exceeded.


User Response: Contact your service representativefor a fix that allows additional tapes.

ANR5035E (S/390) Dynamic allocation of tape unitunit failed, return code rc, error codeerror-code, info code info-code.

Explanation: The dynamic allocation of a tape unitunit fails. The return code rc, error code error-code, andinformation code info-code are in decimal and can befound in the Dynamic Allocation section of MVS/ESAProgramming: Authorized Assembler Services Guide.


User Response: Examine the MVS messages precedingthis message. They should explain the cause of theallocation problem; otherwise, contact your servicerepresentative.

ANR5036E (S/390) Open of tape unit unit (ddnameddname) failed, return code rc.

Explanation: Open of ddname ddname fails.


User Response: Examine the MVS messages preceding

this message. The ANR1401W message and the volumename will explain the problem. If necessary, contactyour service representative.

ANR5037E (S/390) Unable to acquire processor, dsn.

Explanation: The number of simultaneous tapessupported by the server has been exceeded.


User Response: Contact your service representativefor a fix that allows additional tapes.

ANR5038E (S/390) Volume volume cannot beprocessed this level of the operatingsystem.

Explanation: The volume was created on a level of theoperating system that had BSAM Large Block support,and cannot be processed on this level of the operatingsystem.


User Response: Mark storage volume pool volumesunavailable until the operating system is upgraded toOS/390 R10 or higher. Do not use database backup ordatabase dump volumes until the system is upgradedto OS/390 R10 or higher.

ANR5039E (S/390) Unable to open disk vaddr - IUCVMAXCONN value exceeded.

Explanation: The disk at virtual address vaddr cannotbe opened due to a lack of IUCV connections.


User Response: Increase the IUCV MAXCONN valuein the server CP directory entry and restart the server.

ANR5040E (S/390) Data set name dsn containsqualifier qual that is longer than 8characters.

Explanation: Data set dsn qualifier qual is too long.Data set qualifiers must be 1 to 8 characters long.


User Response: Specify data set name qualifiers witha maximum of 8 characters.

ANR5041E (S/390) Data set name dsn contains a nullqualifier.

Explanation: Data set dsn contains null qualifier(either 2 consecutive periods or an ending periodwithout a subsequent qualifier). Data set qualifiersmust be 1 to 8 characters long.


User Response: Specify valid data set name qualifiers.

ANR5032E (S/390) • ANR5041E (S/390)


ANR5042E (S/390) Data set name dsn containsqualifier qual that does not begin, withan alpha character.

Explanation: Data set dsn qualifier qual does not beginwith an alpha character. Data set qualifiers must startwith an alpha character.


User Response: Specify data set name qualifiers thatbegin with an alpha character.

ANR5043E (S/390) Data set name dsn containsqualifier qual that contains a characterthat is not alphanumeric.

Explanation: Data set dsn qualifier qual contains acharacter that is not alphanumeric. Data set qualifiersmust contain only alphanumeric characters.


User Response: Specify data set name qualifiers thatcontain only alphanumeric characters.

ANR5044E (S/390) Cannot format data set dsn. Dataset is not empty.

Explanation: The server will not format dsn because itis not empty.


User Response: Verify that dsn is the correct data setyou’d like to format. The server formats empty datasets only.

ANR5045E (S/390) Failed to open dataset dsn. Errordetected with the VSAM high-used(VSAM high-used value) or high-allocated(VSAM high-allocated value) values.

Explanation: The server did not open dataset dsn. TheVSAM high-used and high-allocated attributes areoutside of the range expected by the server. The valuesmay have been corrupted by moving the dataset usinganything other than a logical move.

System Action: Volume is marked read-only, or notbrought on-line. Server operation continues.

User Response: Issue listcat entry(dsn) all to check thehigh-used and high-allocated values. If you moved thedataset, verify that a logical move was performed.Correct any user errors. Otherwise, contact your servicerepresentative.

ANR5046I (S/390) Dynamic allocation of tape unitunit was cancelled by the operator.

Explanation: The dynamic allocation of a tape unitunit was cancelled by the operator.

System Action: Server operation continues, tapemount fails.


ANR5048E (S/390) Tape dataset allocation of blocksize changed from server value to currentvalue.

Explanation: The server allocated the block size of itstape data set as server value, but it has been changed tocurrent value.

System Action: Current tape operation fails.

User Response: Check for MVS or system applicationmessages preceding this message that indicate whatcaused the change to the block size. Check for anysystem exits that may change the block size (forexample, IEFDB401). Ensure that the server can use itsoriginal value for the block size.

ANR5049E (S/390) Tape data set allocation of data setorganization changed from hex servervalue to hex current value.

Explanation: The server allocated the data setorganization of its tape data set as server value, but ithas been changed to current value in the data controlblock (DCB).


User Response: Check for MVS or system applicationmessages preceding this message that indicate whatcaused the change to the data set organization. Checkfor any system exits that may change the data setorganization (for example, IEFDB401). Ensure that theserver can use its original value for the data setorganization. See MVS/DFP V3R3 Macro Instructions forData Sets for valid values.

ANR5050E (S/390) Tape data set allocation of recordformat changed from hex server value tohex current value.

Explanation: The server allocated the record format ofits tape data set as server value, but it has been changedto current value in the data control block (DCB).


User Response: Check for MVS or system applicationmessages preceding this message that indicate whatcaused the change to the record format. Check for anysystem exits that may change the record format (forexample, IEFDB401). Ensure that the server can use itsoriginal value for the record format. See MVS/DFPV3R3 Macro Instructions for Data Sets for valid values.

ANR5042E (S/390) • ANR5050E (S/390)


ANR5051E (S/390) Tape data set allocation of logicalrecord length changed from server valueto current value.

Explanation: The server allocated the logical recordlength of its tape data set as server value, but it has beenchanged to current value.


User Response: Check for MVS or system applicationmessages preceding this message that indicate whatcaused the change to the logical record length. Checkfor any system exits that may change the logical recordlength (for example, IEFDB401). Ensure that the servercan use its original value for the logical record length.

ANR5060E (S/390) Unable to open VTAM ACBName name, rc code.

Explanation: The server cannot be identified to VTAMwith the ACB name specified.

System Action: Server operation continues. Supportfor the 3270 and SNALU6.2 COMMmethods isdisabled. The server periodically tries to open the ACBand when successful, the 3270 and SNALU6.2COMMmethods are enabled.

User Response: For a description of the reported errorcode, refer to VTAM Programming. If the ACB has beentemporarily varied off, no action is required. The serverperiodically tries to open the ACB. If the ACB is notdefined and the COMMmethods 3270 or SNALU6.2 arenot supported for any clients, shut down the serverwith the HALT command and set the LUNAMEstatement in the server options file to *NONE*. IfCOMMmethods 3270 or SNALU6.2 are supported,contact your VTAM (network) administrator to ensurethat the ACB name has been properly defined in amember of SYS1.VTAMLST.

ANR5061E (S/390) Unable to issue SETLOGON forVTAM ACB Name name, rc code, reasreason, rpl: rtncd return code fdb2 feedback.

Explanation: The server detects an error whileinforming VTAM that it is ready to accept a session.

System Action: Server operation continues. Supportfor the 3270 and SNALU6.2 COMMmethods isdisabled. The server periodically tries to reissue theSETLOGON instruction.

User Response: For a description of the reported errorcode, refer to VTAM Programming.

ANR5062E (S/390) Unable to allocate number of bytesbytes for VTAM control blocks.

Explanation: The server is unable to access the storageit needs to support the COMMmethods 3270 andSNALU6.2.

System Action: The COMMmethods 3270 andSNALU6.2 are disabled. If the storage for the globalcontrol block cannot be accessed, these COMMmethodsremain disabled until the server is shut down with theHALT command and restarted. Otherwise, the serverperiodically tries to access the needed storage andwhen successful, the 3270 and SNALU6.2COMMmethods are enabled. Server operationcontinues.

User Response: If the support for the COMMmethods3270 and SNALU6.2 is needed immediately, shut downthe server (with the HALT command), resolve thestorage problem, and restart the server. If theCOMMmethods 3270 and SNALU6.2 are not used, shutdown the server, set the LUNAME to *NONE*, andrestart the server.

ANR5063E (S/390) Unable to allocate session numberfor LU LU ID.

Explanation: The server is unable to assign a sessionnumber to the incoming session.

System Action: Server operation continues. The serverrejects the incoming session.

User Response: If the MAXSESSIONS statement in theserver options file has been set correctly, the end-user(client) must wait until there is a free session beforeretrying to connect with the server. If theMAXSESSIONS statement is in error, shut down theserver, correct the MAXSESSIONS statement, restart theserver, and have the client retry connecting with theserver.

ANR5064E (S/390) Unable to allocate number of bytesbytes for VTAM session with LU LU ID.

Explanation: The server is unable to access the storageneeded to support the incoming 3270 dial-in session.

System Action: Server operation continues. Theincoming session is rejected.

User Response: Allocate additional storage to theserver virtual machine. There are four ways to do this:




4. Decrease the amount of space allocated to theserver’s database buffer pool. To do this, edit theserver options file and reduce the value specified

ANR5051E (S/390) • ANR5064E (S/390)


for the BUFPOOLSIZE statement. Note that eachbuffer pool page causes an additional 4 KB ofmemory to be allocated.

Note that the server must be shut down (with theHALT command) to allow changes made to the serveroptions file to take place.

ANR5065E (S/390) Unable to open session with LULU ID CID conversation ID, rc code reasonreason, rpl: rtncd return code fdb2 feedback.

Explanation: The server encounters an error whileaccepting an incoming session by way of a VTAMOPNDST instruction. The session is rejected.


User Response: For a description of error code, referto VTAM Programming.

ANR5066E (S/390) Unable to close session with LULU ID CID conversation ID, rc code reasonreason, rpl: rtncd return code fdb2 feedback.

Explanation: The server encounters an error whileending a session.


User Response: For a description of the error code,refer to VTAM Programming.

ANR5067E (S/390) Unable to close VTAM ACBName name, rc code.

Explanation: The server detects an error while closingthe ACB for the specified name.

System Action: The server proceeds with HALTcommand processing.


ANR5068E (S/390) Unable to receive on session withLU LU ID CID conversation ID, rc codereason reason, rpl: rtncd return code fdb2feedback sense sense code.

Explanation: The server encounters an error whilereceiving data on the session.

System Action: Server operation continues, and thesession is ended.


ANR5069E (S/390) Unable to send on session withLU LU ID CID conversation ID, rc codereason reason, rpl: rtncd return code fdb2feedback sense sense code.

Explanation: The server encounters an error whilesending data on the session.

System Action: Server operation continues, and thesession is ended.


ANR5070I (S/390) 3270 Dial-in driver terminated asrequested.

Explanation: The server’s 3270 dial-incommunications driver is ending as requested.

System Action: Server operation continues withsupport for the 3270 COMMmethod disabled.


ANR5071W (S/390) Application resource name wasdefined to VTAM with APPC=NO.

Explanation: The specified VTAM application hasbeen defined with APPC=NO. This definition, may benormal for your installation if SNALU6.2 is not used bythe clients. If this is true, then this message can beignored.

System Action: Server operation continues. Supportfor the SNALU6.2 is disabled.

User Response: If clients are using SNALU6.2, definethe VTAM application with APPC=YES. For the serverto recognize the new definition, you must stop theserver by using the HALT command and restart theserver.

ANR5080I (S/390) IUCV driver ready for connectionwith clients.

Explanation: The server’s IUCV communicationsdriver is ready to receive connection requests fromclients.

System Action: Server operation continues. The IUCVis enabled.


ANR5081E (S/390) Unable to initialize IUCV driver -code code.

Explanation: The server’s IUCV communicationsdriver cannot initialize itself because it received theerror code code when entering the IUCV DECLAREBUFFER function.


ANR5065E (S/390) • ANR5081E (S/390)


User Response: For a description of the reported errorcode, refer to the IUCV documentation in the CPProgramming Services publication for your specificoperating system, and the TCP/IP for MVS Programmer’sReference for your version of TCP/IP.

ANR5082W (S/390) IUCV connection terminated -insufficient memory.

Explanation: An IUCV connection request is refusedby the server’s IUCV communications driver becausesufficient memory is not available to construct asession.








ANR5083E (S/390) IUCV connection terminated -error code accepting connect request.

Explanation: The server’s IUCV communicationsdriver is unable to accept a new connection from aclient because error code has been received from theIUCV ACCEPT function.


User Response: For a description of the IUCVACCEPT error code, refer to the IUCV documentationin the CP Programming Services publication for yourspecific operating system, and the TCP/IP for MVSProgrammer’s Reference for your version of TCP/IP.

ANR5084W (S/390) IUCV connection terminated -server HALT in progress.

Explanation: The server’s IUCV communicationsdriver refuses a request for a client connection becausethe HALT command has been entered.

System Action: The server rejects the session andproceeds with HALT command processing.


ANR5085I (S/390) IUCV driver unable to start. Serverterminating.

Explanation: The server is unable to start the threadto monitor the status of the IUCV communicationsdriver.

System Action: The server shuts down.

User Response: If sufficient storage is available whenthis error occurs, contact your service representative.On MVS, ensure the region size parameter on the JCLis at least 128MB. Otherwise if on VM, ensure that theserver virtual machine is at least 128MB in size.

ANR5086I (S/390) IUCV driver terminated.

Explanation: The IUCV communications driver hasshut down.

System Action: Server operation continues. Supportfor the IUCV COMMmethod is disabled. The serverperiodically tries to restart the IUCV communicationsdriver.


ANR5087I (S/390) IUCV driver starting.

Explanation: The server is reporting that it is in theprocess of starting the IUCV communications driver.

System Action: The server attempts to initiate aprocess that will monitor the status of the IUCVcommunications driver.


ANR5088E (S/390) Unable to establish a wrapconnection - return code code.

Explanation: The server is unable to establish anIUCV connection with itself.

System Action: Server operation continues. Supportfor the IUCV COMMmethod is disabled. The serverwill periodically retry the connect.

User Response: For a description of this IUCVCONNECT error code, refer to the IUCVdocumentation in the CP Programming Servicespublication for your specific operating system, and the

ANR5082W (S/390) • ANR5088E (S/390)


TCP/IP for MVS Programmer’s Reference for your versionof TCP/IP.

ANR5089I (S/390) IUCV driver terminated asrequested.

Explanation: The server’s IUCV communicationsdriver is ending as requested.

System Action: Server operation continues withsupport for the ADMIUCV COMMmethod disabled.


ANR5090I (S/390) TCP/IP driver ready for connectionwith clients on port port number.

Explanation: The server’s TCP/IP communicationsdriver is ready to receive connection requests fromclients.

System Action: Server operation continues. Supportfor the TCP/IP COMMmethod is enabled.


ANR5091E (S/390) Unable to initialize TCP/IP driver- insufficient memory.

Explanation: The server’s TCP/IP communicationsdriver is unable to initialize itself due to insufficientmemory (virtual storage).




2. On MVS, increase the size of the REGIONparameter on the EXEC or JOB statement of the JCLused to start the server.




ANR5092E (S/390) Unable to initialize TCP/IP driver- error creating acceptor socket.

Explanation: The server’s TCP/IP communicationsdriver is unable to create its critical listening socket,and so TCP/IP communications cannot be initialized.

System Action: Server initialization continues. TCP/IPcommunications initialization will be retried.

User Response: Check that TCP/IP is running, andthat TCPName in the options file matches the TCP/IPsubsystem name you intend to use.

ANR5093E (S/390) Unable to establish TCPconnection - accept error.

Explanation: The server’s TCP/IP communicationsdriver detects an internal error while attempting toaccept a new client connection.


User Response: Report the error to your servicerepresentative.

ANR5094W (S/390) Unable to establish TCPconnection - insufficient memory.

Explanation: A TCP/IP connection request has beenrefused by the server’s TCP/IP communications driverbecause sufficient memory is not available to constructa session.


User Response: Allocate additional storage to theserver virtual machine. There are three ways to do this:




4. Decrease the amount of space allocated to theserver’s database buffer pool. To do this, edit theserver options file and reduce the value specifiedfor the BUFPOOLSIZE statement. Note that eachbuffer pool page causes an additional 4 KB ofmemory to be allocated.


ANR5089I (S/390) • ANR5094W (S/390)


ANR5095W (S/390) Unable to establish TCPconnection - server HALT in progress.

Explanation: The server’s TCP/IP communicationsdriver refuses a request for a client connection becausethe HALT command has been entered.



ANR5096W (S/390) Unable to initialize OE BPXTCP/IP driver - TCP/IP is down level.

Explanation: Although the OS/390 is at V2R5 orabove the level of TCP/IP is below V3R4 level, and soOE BPX TCP/IP communications cannot be initialized.

System Action: Server initialization continues. TCP/IPcommunications is initialized, instead of OE BPXTCP/IP.

User Response: Make sure the TCP/IP V3R4 or aboveis installed and running in the system if OE BPXTCP/IP communication is to be used.

ANR5097I (S/390) TCP/IP driver terminated asrequested.

Explanation: The server’s TCP/IP communicationsdriver is ending as requested.

System Action: Server operation continues withsupport for the TCP/IP COMMmethod disabled.


ANR5098I (S/390) TCP/IP driver starting.

Explanation: The server is in the process of startingthe TCP/IP communications driver.

System Action: The server tries to initiate a threadthat will monitor the status of the TCP/IPcommunications driver.


ANR5099E (S/390) Unable to initialize TCP/IP driver- error using Port socket number (rc =code).

Explanation: The server’s TCP/IP communicationsdriver detects an internal error while attempting to usethe specified TCP/IP port number.

System Action: The server stops listening for TCP/IPsessions. Server operation continues without supportfor the TCP/IP communications method. The servertries to restart the communications method periodically.


ANR5100E (S/390) Unable to initialize TCP/IP driver-error listening on Portsocket number (rc =code).

Explanation: The server’s TCP/IP communicationsdriver detects an internal error while attempting tolisten for a connection on the TCP/IP port.

System Action: The server ends the TCP/IP acceptorprocess. Server operation continues without support forthe TCP/IP COMMmethod. The server periodicallytries to restart the acceptor process.


ANR5101W (S/390) TCP/IP communications driverterminating.

Explanation: The server’s TCP/IP communicationsdriver has shut down.

System Action: Server operation continues withoutsupport for the TCP/IP COMMmethod option. Theserver periodically tries to restart the TCP/IPcommunications driver if the server is not in theprocess of shutting down.

User Response: If the server is not in the process ofshutting down, this message may indicate that theTCP/IP server is not available or that a server internalerror has occurred. Review the console log to determineif an internal error has occurred. If an internal error hasoccurred, contact your service representative. If theTCP/IP server is unavailable, correct the problem andthe server will automatically reinitiate the TCP/IPcommunications driver.

ANR5102W (S/390) Error received for connectionconnection number (socket socket number).TCP/IP driver will stop, then re-start.

Explanation: The server’s TCP/IP communicationsdriver received an error for the specified connection.

System Action: The server stops the TCP/IPcommunications driver, and restarts thecommunications driver.

User Response: This process may take up to 5minutes. If the condition persists, report the problem toyour service representative.

ANR5103I (S/390) CLIO/S (IBM)TCP/IP driver readyfor service on port clio port number.

Explanation: The server’s CLIO/S TCP/IPcommunications driver is ready to handle connectionrequests to and from AIX clients using COMMmethodCLIO through an IBM TCP/IP host network.

System Action: Server operation continues. Supportfor the TCPName and CLIOPort server options isenabled.

ANR5095W (S/390) • ANR5103I (S/390)



ANR5104E (S/390) Unable to initialize CLIO/S(IBM)TCP/IP driver - error creatinglistening socket.

Explanation: The server’s CLIO/S communicationdriver is unable to create its critical listening socket;therefore, CLIO/S (IBM)TCP/IP communication cannotbe initialized.

System Action: Server initialization continues.CLIO/S (IBM)TCP/IP communication initialization willbe retried every minute. This message will besuppressed after being issued for the third time;however, attempts to initialize CLIO/S communicationswill continue every minute until message ANR5103I isissued indicating CLIO/S driver is ready for service.

User Response: Check that TCP/IP is running, andthat TCPName, in the options file, matches the name ofthe target TCP/IP address space.

ANR5105I (S/390) Interlink TCPaccess driver is readyfor service on port interlink port number.

Explanation: The server’s Interlink TCPaccesscommunications driver is ready to receive connectionrequests from clients connected through InterlinkTCPaccess.

System Action: Server operation continues. Supportfor the ICSSname and ICSPort server options isenabled.


ANR5106E (S/390) Unable to initialize InterlinkTCPaccess driver - error opening listenendpoint.

Explanation: The server’s Interlink TCPaccess driveris unable to create its critical listen endpoint; InterlinkTCPaccess communication cannot be initialized.

System Action: Server initialization continues.Interlink TCPaccess communications will be retriedevery minute and this message will suppressed afterbeing issued three times.

User Response: Check that TCPaccess is running andthat ICSSname, in the options file, matches theTCPaccess subsystem name you intend to use. TheICSSname option should match the SSN parameter ofthe PROC statement in the TCPaccess startupprocedure. Refer to Interlink TCPaccess publications fordetails.

ANR5107E (S/390) Unable to initialize CLIO/S(IBM)TCP/IP driver - error bindingacceptor socket socket number (rc = code).

Explanation: The server’s TCP/IP communicationsdriver detects an error while attempting to bind theacceptor socket.

System Action: The server ends the TCP/IP acceptorprocess. Server operation continues without support forthe TCP/IP COMMmethod. The server tries to restartthe acceptor process periodically.

User Response: Check that TCP/IP is running andthat TCPName, in the options file, matches the name ofthe target TCP/IP address space.

ANR5108E (S/390) The CLIO/S functions have notbeen linked into this module.

Explanation: The server cannot find the CLIO/Sfunctions required to support CLIO (IBM)TCP/IPcommunications.

System Action: The connection to the server fails.

User Response: The cause of this error is the omissionof the required post-SMP/E link-edit step to mergeCLIO functions from SYS1.SFCFLIB(FCFIADSM). Beforeretrying the operation, ensure that your installation hasperformed the required post install link-edit step. Findthe ADSM SAMPLIB and use member ANRCLIOK foran example of the required post-SMP/E link edit toload ANRSERV with CLIO/S communication code.

ANR5109E (S/390) The CLIO/S communication drivercannot be started.

Explanation: The server is unable to start the CLIO/Scommunication driver because either TCPPort andCLIOPort server options are the same value orTCPName is coded with *NONE*.

System Action: The CLIO/S communication optionwill not be available and server initialization continues.

User Response: Check the server options file to ensureCLIOPort and TCPPort values are different. If theCLIOPort and TCPPort options are specified correctly,check the TCPName option to ensure *NONE* is notcoded for this option. Specify a unique CLIOPort valueand ensure a valid TCPName parameter is coded toallow the (IBM)TCP/IP CLIO/S communication driverto start. CLIOPort has no default value; however,TCPPort and TCPName default to 1500 and TCPIPrespectively. This message can be eliminated if CLIO/Scommunication is not required by removing theCLIOPort option from the server option file andrecycling the server.

ANR5104E (S/390) • ANR5109E (S/390)


ANR5110I (S/390) 3270 Dial-in driver ready forconnection with clients.

Explanation: The server’s 3270 dial-incommunications driver is ready to receive connectionrequests from clients.

System Action: Server operation continues. Supportfor the 3270 COMMmethod is enabled.


ANR5111E (S/390) Unable to initialize 3270 dial-indriver - error defining GRAF devices.

Explanation: The server’s 3270 dial-incommunications driver is unable to define one or moreCP GRAF devices, and is therefore unable to initializeitself.



ANR5112W (S/390) Unable to define additionalGRAF devices for dial-in.

Explanation: The server’s 3270 dial-incommunications driver is unable to define additionalCP GRAF devices, and may not be able to acceptsubsequent connections from clients.



ANR5113W (S/390) 3270 dial-in session terminated -insufficient memory.

Explanation: A 3270 dial-in connection request hasbeen refused by the server’s 3270 communicationsdriver because sufficient memory is not available toconstruct a session.






4. Decrease the amount of space allocated to theserver’s database buffer pool. To do this, edit theserver options file and reduce the value specified

for the BUFPOOLSIZE statement. Note that eachbuffer pool page causes an additional 4 KB ofmemory to be allocated.


ANR5114W (S/390) 3270 dial-in session terminated -device does not support structuredfields.

Explanation: The server’s 3270 communications driverhas refused a client connection request because the 3270device initiating the connection does not supportstructured fields.


User Response: Retry the 3270 connection from adevice that properly supports structured fields.

ANR5115W (S/390) 3270 dial-in session terminated -emulator not supported.

Explanation: The server’s 3270 dial-incommunications driver has refused a connectionrequest from a client, because the client’s 3270 emulatordoes not or is not configured for the level of 3270extended data stream support that the server requires.


User Response: Retry the 3270 connection by using asupported emulator program, such as the OS/2Communications Manager, or the IBM PersonalCommunications/3270 program.

ANR5116I (S/390) 3270 Dial-in driver unable to start.Server terminating.

Explanation: The server is unable to start the threadthat monitors the status of the 3270 dial-incommunications driver.


User Response: If sufficient storage is available whenthis error occurs, contact your service representative.Otherwise for VM, ensure that the storage for theserver virtual machine is at least 128MB. For MVS,ensure the region size parameter on the JCL is at least128MB.

ANR5117I (S/390) 3270 Dial-in driver terminated.

Explanation: The 3270 dial-in communications driverhas shut down.

System Action: Server operation continues. Supportfor the 3270 COMMmethod is disabled. The serverperiodically tries to restart the 3270 dial-incommunications driver.

ANR5110I (S/390) • ANR5117I (S/390)



ANR5118I (S/390) 3270 Dial-in driver starting.

Explanation: The server is reporting that it is in theprocess of starting the 3270 dial-in communicationsdriver.

System Action: The server tries to initiate a processthat will monitor the status of the 3270 dial-incommunications driver.


ANR5120I (S/390) APPC driver unable to start.Server terminating.

Explanation: The server is unable to start the threadthat monitors the status of the APPC communicationsdriver.


User Response: If sufficient storage is available whenthis error occurs, contact your service representative.Otherwise for VM, ensure that storage for the servervirtual machine is at least 128MB. For MVS, ensure theregion size parameter on the JCL is at least 128MB.

ANR5121I (S/390) APPC driver ready for connectionswith clients on resource resource name.

Explanation: The server’s APPC communicationsdriver is reporting that it is ready to receive connectionrequests from clients.

System Action: Server operation continues. Supportfor the SNALU6.2 COMMmethod is enabled.


ANR5122I (S/390) APPC driver terminated.

Explanation: The APPC communications driver hasshut down.

System Action: Server operation continues. Supportfor the SNALU6.2 COMMmethod is disabled. Theserver periodically tries to restart the APPCcommunications driver.


ANR5123I (S/390) APPC driver starting.

Explanation: The server is reporting that it is in theprocess of starting the APPC communications driver.

System Action: The server tries to initiate a threadthat will monitor the status of the APPCcommunications driver.


ANR5124E (S/390) APPC driver unable to declare asresource resource name, rc code, reasonreason.

Explanation: The server cannot connect to the *IDENT(the Identify System Service) to identify itself as theresource manager for the resource specified.

System Action: Server operation continues. Supportfor the SNALU6.2 COMMmethod is disabled. Theserver periodically tries to restart the APPCcommunications driver.

User Response: Ensure that the following IUCVstatement is present in the CP directory entry for theserver: IUCV *IDENT appc-resource GLOBALREVOKE.

ANR5125E (S/390) APPC connection terminated -error code accepting connect request.

Explanation: The server’s APPC communicationsdriver is unable to accept a new connection from aclient, because error code has been received from theIUCV ACCEPT function.


User Response: For a description of the IUCVACCEPT error code, refer to the IUCV documentationin the CP Programming Services publication for yourspecific operating system.

ANR5126W (S/390) APPC connection terminated -server HALT in progress.

Explanation: The server’s APPC communicationsdriver refuses a request for a client connection becausethe HALT command has been entered.



ANR5127W (S/390) APPC connection terminated -insufficient memory.

Explanation: An IUCV connection request is refusedby the server’s APPC communications driver becausesufficient memory is not available to construct asession.





ANR5118I (S/390) • ANR5127W (S/390)





ANR5128E (S/390) Unable to allocate session numberfor LU LU ID.

Explanation: The server is unable to assign a sessionnumber to the incoming session.

System Action: Server operation continues. The serverrejects the incoming session.

User Response: If the MAXSESSIONS statement in theserver options file has been set correctly, the end-user(client) must wait until there is a free session beforeretrying to connect with the server. If theMAXSESSIONS statement is in error, shut down theserver, correct the MAXSESSIONS statement, restart theserver, and have the client retry to connect with theserver.

ANR5129W (S/390) VTAM APPC (LU62) conversationterminated - server HALT in progress.

Explanation: The server’s APPC communicationsdriver rejects a conversation because the HALTcommand has been entered.

System Action: The server rejects the conversationand proceeds with HALT command processing.


ANR5130W (S/390) VTAM APPC (LU62) conversation(conversation ID) with LU LU IDterminated - insufficient memory.

Explanation: An APPC conversation has beenterminated by the server’s APPC communicationsdriver because sufficient memory is not available tosupport this conversation.

System Action: Server operation continues. Theconversation is deallocated.


1. Increase the size of the REGION parameter on theJOB or EXEC statement of the JCL used to start theserver.




ANR5131I (S/390) APPC driver terminated asrequested.

Explanation: The server’s APPC communicationsdriver is reporting that it is terminating as requested.

System Action: Server operation continues withsupport for the SNALU6.2 COMMmethod disabled.


ANR5132W (S/390) VTAM APPC (LU62) support isnot available with current session.

Explanation: The server’s VTAM APPC (LU6.2)communications driver is not available. Clients that usethe SNALU6.2 communications method cannotestablish a session with the server. Refer to ANR5071W,which was displayed prior to this message, foradditional information. If the SNALU6.2communication method is not used, ignore thismessage and message ANR5071W.

System Action: Server operation continues withoutsupport for the SNALU6.2 COMMmethod.

User Response: Verify that the server application isdefined correctly to VTAM. APPC=YES must bespecified with the VTAM APPL macro when definingthe server application when SNALU6.2 support is used.

ANR5133W (S/390) VTAM APPC (LU62) connectrequest rejected.

Explanation: A client’s VTAM APPC (LU6.2) connectrequest was rejected because the LU6.2 communicationsdriver is not available. This process may be the resultof the server application not being defined correctly toVTAM. The application must be defined withAPPC=YES with the APPL macro to enable SNALU6.2support on the server.

ANR5128E (S/390) • ANR5133W (S/390)


System Action: VTAM message IST663I and otherrelated messages are displayed; server operationcontinues.

User Response: Verify that the server application isdefined correctly to VTAM. APPC=YES must bespecified with the VTAM APPL macro when definingthe server application.

ANR5140I (S/390) HTTP (IBM) communications islistening for clients on port port number.

Explanation: The server’s HTTP (IBM) TCP/IPcommunications driver is ready to receive connectionrequests from Web clients.

System Action: Server operation continues. Supportfor Web Client HTTP communication is enabled.


ANR5142I (S/390) TCP/IP Administrative driverready for connection with clients onport port number.

Explanation: The server’s TCP/IP communicationsdriver for administrators is ready to receive connectionrequests from administrative clients and other systems.



ANR5143I (S/390) TCP Access Administrative driverready for connection with clients onport port number.

Explanation: The server’s TCP Access communicationsdriver for administrators is ready to receive connectionrequests from administrative clients and other systems.



ANR5148I (S/390) HTTP (TCPaccess) driver islistening for clients on port port number.

Explanation: The server’s HTTP (TCPaccess) TCP/IPcommunications driver is ready to receive connectionrequests from Web clients.

System Action: Server operation continues. Supportfor Web Client HTTP over TCPaccess is enabled.


ANR5200S (S/390) Unable to connect to the *MSGSystem Service, rc = code.

Explanation: The server receives return code code fromthe IUCV CONNECT function when connecting to the*MSG System Service.


User Response: Determine the cause of the error code,correct the problem, and restart the server. For adescription of the reported error code, refer to theIUCV documentation in the CP Programming Servicespublication, or the publication for your operatingsystem that contains documentation for the IUCVCONNECT function.

ANR5201S (S/390) Error code from *MSG SystemService path path ID.

Explanation: An error occurs on the IUCV path to the*MSG System Service.


User Response: Determine the cause of the error code,correct the problem, and restart the server. For adescription of the reported error code, refer to theIUCV documentation in the CP Programming Servicespublication, or the publication for your operatingsystem that contains IUCV documentation.

ANR5202E (S/390) Unable to communicate with anyNotify user ID.

Explanation: The server is unable to send a messageto any user ID specified on the NOTIFY option in theDSMSERV OPT file.


User Response: Have someone with an authorizedNOTIFY user ID log on to the system.

ANR5203E (S/390) Unable to communicate with anyMount Operator.

Explanation: The server is unable to send a messageto any user ID specified on the MOUNTOP option inthe DSMSERV OPT file.


User Response: Have someone with an authorizedMOUNTOP user ID log on to the system.

ANR5204I (S/390) Autolog-response

Explanation: The result of the XAUTOLOG commandfor the mount exit virtual machine is Autolog-response.



ANR5205I (S/390) From userid: msg.

Explanation: The message msg has been received froma nonauthorized user ID userid.


User Response: If the user ID userid is a server mountoperator, ensure that the user ID is in the MOUNTOP

ANR5140I (S/390) • ANR5205I (S/390)


list in the server options file.

ANR5208I (S/390) Dismounting volume volser(updated).

Explanation: The volume volser is dismounted afterbeing updated (written to) by the server. Possiblereasons for the dismount include:v The volume was found idle and the drive was

needed for another volumev The volume is dismounted as a result of the

DISMOUNT VOLUME commandv The volume is dismounted because of a previously

reported error condition.



ANR5209I (S/390) Dismounting volume volser(read-only access).

Explanation: The volume volser is dismounted afterread-only access by the server. Possible reasons for thedismount include:v The volume was found idle and the drive was

needed for another volumev The volume is dismounted as a result of the

DISMOUNT VOLUME commandv The volume is dismounted because of a previously

reported error condition.



ANR5210I (S/390) Request number: Mount devclassvolume ID at vaddr mode within number ofminutes minutes.

Explanation: The server has requested a volume bemounted.

System Action: The running task waits until themount is satisfied or canceled.

User Response: Use the DSMOP command to satisfyor cancel the mount request.

ANR5211I (S/390) Request number: Mount devclassvolume ID at vaddr mode (format) withinnumber of minutes minutes.

Explanation: The server has requested a volume witha specific format be mounted.



ANR5212I (S/390) Request number: Mount devclassvolume ID at vaddr mode via Exit Machinemachine name.




ANR5213I (S/390) Request number: Mount devclassvolume ID at vaddr mode (format) via ExitMachine machine name.

Explanation: The server has requested a volume witha specific format be mounted.



ANR5214I (S/390) Request number: Mount devclassvolume ID at vaddr mode waiting foravailable Exit Machine.




ANR5215I (S/390) Request number: Mount devclassvolume ID at vaddr mode (format) waitingfor available Exit Machine.




ANR5216I (S/390) Type volser is expected to bemounted (mode).

Explanation: The server requires the volume volser bein read/write or read/only mode as indicated by modeon a device type indicated by type.


User Response: Locate the specified volume and beprepared to make it available to the server.

ANR5208I (S/390) • ANR5216I (S/390)


ANR5217I (S/390) Dismounting volume volser -retention minute mount retentionexpired.

Explanation: The volume volser is dismounted becausethe MOUNTRETENTION value retention specified forthis device class has elapsed without activity on thisvolume.



ANR5218I (S/390) Detaching tape device vaddr - notrequested by server.

Explanation: The virtual address vaddr is detachedbecause it has not been requested by the server.


User Response: Check the virtual address requestedby the server for tape mounts. Reissue the CP ATTACHcommand and specify the correct virtual address.

ANR5220I (S/390) Deleting type volser from StoragePool pool.

Explanation: The volume volser of device type type hasbeen removed from storage pool pool.


User Response: The server no longer uses the volumespecified. You can return the volume to the scratchpool.

ANR5221I (S/390) Request: Delete type volser via ExitMachine userid.

Explanation: The deletion of volume volser of devicetype type is scheduled for Mount Exit Virtual Machineuserid as request number request.



ANR5222I (S/390) Request: Delete type volser waitingfor available Exit Machine.

Explanation: The deletion of volume volser of devicetype type is waiting for an available Mount Exit VirtualMachine userid as request number request.



ANR5223E (S/390) Deletion Exit for volser (storagepool pool) failed - unknown Rc=rc.

Explanation: The deletion of volume volser in storagepool pool fails.


User Response: Contact service representative.

ANR5224E (S/390) Deletion Exit for volser (storagepool pool) failed - ExitRc=rc,Rc=abend-indicated.

Explanation: The deletion of volume volser in storagepool pool fails.


User Response: If the exit return code rc is nonzero,check the documentation for the tape deletion exitspecified in the server options file. If the tape deletionexit has abended, the indicator abend-indicated isnonzero.

ANR5225E (S/390) Deletion Exit for volser (storagepool pool) failed - unable to get deviceclass information.

Explanation: The deletion of volume volser in storagepool pool has failed due to an internal server error.



ANR5226E (S/390) Deletion Exit for volser (storagepool pool) failed - unable to startbackground thread.

Explanation: The deletion of volume volser in storagepool pool has failed due to an internal server error.



ANR5227E (S/390) Deletion Exit for volser (storagepool pool) failed - insufficient memory.

Explanation: The deletion of volume volser in storagepool pool fails due to lack of available storage.


User Response: Increase the region or virtual machinesize for the server or reduce the MAXSESSIONS valuein the server options file.

ANR5228I (S/390) Deleting type volser from volumehistory (previous use volume).

Explanation: The volume volser in device type type hasbeen deleted from the volume history. It was previouslyused for previous use.


User Response: The server no longer tracks thevolume specified. You can return the volume to thescratch pool.

ANR5217I (S/390) • ANR5228I (S/390)


ANR5229W (S/390) RACROUTE Delete failed forvolser, SAF return code System AuthorizedFacility return code, return code RACFreturn code, reason code RACF reason code.

Explanation: The deletion of the profile for volumevolser failed. The return codes and reason code are theresult of a RACROUTE call. The codes are in hex. TheSAF return code is designated as x0yy where yy is theSAF return code and x indicates the call as follows:

x=1 RACROUTE REQUEST=DEFINE, TYPE=DELETE,CLASS='TAPEVOL', ENTITY=volume

x=2 RACROUTE REQUEST=STAT, CLASS='TAPEVOL'

x=3 RACROUTE REQUEST=DEFINE, TYPE=DELETE,CLASS='DATASET', VOLSER=volume, ENTITY=tapedataset name

The failure of the profile deletion is not an error if thevolume did not have a profile. No profile will exist fora volume if the server was not set up to request aprofile (DEVCLASS parameter PROTECTION=NO)when the volume was first used, or if the server neverused the volume.


User Response: If the RACF profile exists for thevolume, check the system log for error messages to findthe cause of the problem. The profile for the volumespecified in the message will have to be deleted byissuing the appropriate RACF commands. ForInformation on the return codes and reason code, seeExternal Security Interface (RACROUTE) Macro Referencefor MVS.

ANR5230I (S/390) Request number: Starting ExitMachine mountvm to mount devclassvolume ID.

Explanation: The server has autologged a mount exitvirtual machine to handle a mount request.

System Action: The server autologs a mount exitvirtual machine.


ANR5231I (S/390) Request number: Starting ExitMachine mountvm to delete devclassvolume ID.

Explanation: The server autologs a mount exit virtualmachine to handle a mount delete request.

System Action: The server autologs a mount exitvirtual machine.


ANR5232W (S/390) [XAUTOLOG] mountvm failedwith return code code.

Explanation: An error occurs during XAUTOLOG of amount exit virtual machine.

System Action: The server retries the command. If thecommand continues to fail, the mount exit machine ismarked off-line, and another mount exit machine isused.

User Response: If the mount exit machine is placed inthe off-line status, determine the cause, correct theproblem, and use the DSMOP or administrator READYEXIT command to restore the mount exit machine tothe ready status.

ANR5233E (S/390) Exit Machine mountvm takenoffline - nn command attempts failed.

Explanation: The number of XAUTOLOG attemptshas exceeded an internal threshold. The mount exitvirtual machine is no longer used.

System Action: The server marks the mount exitvirtual machine off-line.

User Response: To make the mount exit machineavailable, determine the cause of the autolog failure.Correct the problem and use the DSMOP oradministrator READY EXIT command to restore themount exit machine to the ready status.

ANR5234E (S/390) All Exit Machines are ″Offline″.

Explanation: All the defined mount exit virtualmachines have been placed in the off-line status by theserver.

System Action: Any mount requests by the server arequeued.

User Response: Determine the cause of the autologfailures of all the mount exit virtual machines, correctany problems and use the DSMOP or administratorREADY EXIT command to make the mount exitmachines available.

ANR5240E (S/390) Request number: Mount for volumeID has timed out.

Explanation: The mount request has not been satisfiedin the requested time.

System Action: The server cancels the mount request.


ANR5241E (S/390) Exit Machine mountvm not loggedon, mount for volume ID cancelled.

Explanation: A mount exit virtual machine has loggedoff without satisfying the server’s mount request.

System Action: The server cancels the mount request.

ANR5229W (S/390) • ANR5241E (S/390)



ANR5250E (S/390) Command: User user ID notauthorized.

Explanation: An unauthorized user has attempted toenter a DSMOP command.


User Response: If the user should be authorized, addthat user ID on the REPLYOP option in the DSMSERVOPT file.

ANR5251E (S/390) Command: Invalid request numberrequest number.

Explanation: A DSMOP command has been enteredwith an incorrect request number.


User Response: Enter the command with the correctrequest number.

ANR5252E (S/390) Command: No match found for thisrequest number.

Explanation: The request number specified by theDSMOP command is not in the list of outstandingmount requests.


User Response: Enter the command with the correctrequest number.

ANR5253E (S/390) Request: Invalid device address -raddr.

Explanation: The response to server request numberrequest has specified an invalid real device addressraddr.


User Response: Respond to the request again, byspecifying a valid real device address.

ANR5254E (S/390) Command: CP command commandname failed.

Explanation: A DSMOP CANCEL REQUEST or aDSMOP REPLY command fails.

System Action: The server tries to enter the CPcommand command and receives a nonzero return code.

User Response: If you have entered a DSMOPCANCEL REQUEST, force the mount exit virtualmachine to cancel the mount request with the FORCEoption. To use the DSMOP CANCEL REQUEST

command when running the mount exit, the servermust have FORCE privilege. If you have entered aDSMOP REPLY command, attach the device to theserver with the ATTACH option. To use the DSMOPREPLY command, the server must have ATTACHprivilege.

ANR5255E (S/390) Command: No matching ExitMachines were found ″Offline″.

Explanation: A READY EXIT command has beenissued and all Mount Exit Virtual Machines are ready.



ANR5256E (S/390) Command: Invalid match patternspecified for Exit Machine name.

Explanation: A DSMOP READY command has beenentered specifying a user ID that is not a definedmount exit virtual machine.


User Response: Enter the command and specify thecorrect mount exit virtual machine name.

ANR5257I (S/390) Command: No requestsoutstanding.

Explanation: A DSMOP QUERY MOUNTS commandhas been entered when no mount requests areoutstanding.



ANR5258E (S/390) Command: Command not validwhen Exit is active.

Explanation: A DSMOP REPLY command has beenentered by a reply operator when the mount exit isactive.


User Response: The DSMOP REPLY command isinvalid when the mount exit is used. When usingmount exit machines, all mount requests are issuedfrom the mount exit machines using your installation’sprocedures.

ANR5259E (S/390) Command: Command not validwhen Exit is not active.

Explanation: A DSMOP READY command or aDSMOP QUERY EXITS command has been enteredwhen the mount exit is not being used.

ANR5250E (S/390) • ANR5259E (S/390)




ANR5260E (S/390) Command: Volume volume notfound.

Explanation: A DISMOUNT VOLUME command wasissued, but the volume to be dismounted cannot befound.


User Response: Ensure that the correct volume nameis entered.

ANR5261E (S/390) Command: Volume volume is not″Idle″.

Explanation: A DISMOUNT VOLUME command hasbeen issued, but the volume is in use and cannot bedismounted.


User Response: If it is necessary to dismount thevolume, cancel the session or process that is using thevolume, and reissue the command.

ANR5262E (S/390) Command: Device raddr not found.

Explanation: A DISMOUNT DEVICE command hasbeen issued, but the device to be dismounted cannot befound.


User Response: Ensure that the correct device hasbeen specified.

ANR5263E (S/390) Command: Device raddr is not″Idle″.

Explanation: A DISMOUNT DEVICE command hasbeen issued, but the device is in use and cannot bedismounted.


User Response: If it is necessary to dismount thedevice, cancel the session or process that is using thevolume, and reissue the command.

ANR5264I (S/390) Command not executed - passwordhas expired.

Explanation: An administrative command has beenissued, but the administrator’s password has expired.


User Response: Update your password by starting anadministrative client session. Alternatively, the serversystem administrator may use the UPDATE ADMINcommand to update an administrator’s password.

ANR5265I (S/390) Command not executed -administrator name is locked.

Explanation: An administrative command has beenissued, but the administrator’s user ID is locked fromaccessing the server.


User Response: The server system administrator canissue the UNLOCK ADMIN command to restore accessto a server administrative user ID.

ANR5266I (S/390) Command not executed -insufficient memory.

Explanation: An administrative command has beenissued, but there is insufficient memory to execute thecommand.


User Response: Increase the region or virtual machinesize for the server or lower the MAXSESSIONSparameter in the server options file and restart theserver.

ANR5267I (S/390) Command not executed - internalerror detected.

Explanation: An administrative command has beenissued, but there is a detected internal processing errorthat prevents the command from executing.


User Response: Look for preceding messageconcerning access to administrative user ID informationwithin the server and contact your servicerepresentative.

ANR5268I (S/390) Command not executed -insufficient recovery log space.

Explanation: An administrative command has beenissued, but there is insufficient recovery log space tocomplete the database transaction.


User Response: To increase the amount of log spaceavailable to the server, an authorized admininstratorcan add log volumes using the DEFINE LOGVOLUMEcommand, and extend the size of the log using theEXTEND LOG command.

ANR5269I (S/390) Command not executed -insufficient database space.

Explanation: An administrative command has beenissued, but there is insufficient database space tocomplete the database transaction.


ANR5260E (S/390) • ANR5269I (S/390)


User Response: To increase the amount of databasespace available to the server, an authorizedadmininstrator can add database volumes using theDEFINE DBVOLUME command, and extend the size ofthe database using the EXTEND DB command.

ANR5270I (S/390) SMFWTM macro return code 40(buffer shortage).

Explanation: SMFWTM completed with return code40.

System Action: The server continues to operate.

User Response: Increase SMF buffer limit or disableserver accounting.

ANR5280I (S/390) Command accepted.

Explanation: A DSMOP REPLY command is accepted.

System Action: The server processes the DSMOPREPLY command.


ANR5281I (S/390) Request request number for volumeID canceled by user ID.

Explanation: A mount request is successfully canceled.

System Action: The system cancels the mount request.


ANR5282I (S/390) Request request number for volumeID cancelled (PERM) by user ID.

Explanation: A mount request is successfully canceledwith the PERM option.

System Action: The system cancels the mount requestand marks the volume as unavailable.


ANR5283I (S/390) Exit Machine mountvm status set to″Ready″.

Explanation: A DSMOP READY command has beenentered.

System Action: The server changes the status of themount exit virtual machine to ready.


ANR5284I (S/390) Requests outstanding:

Explanation: The list of currently outstanding mountrequests follows.

System Action: The server lists all outstanding mountrequests or the one specified on the DSMOP QUERYcommand.


ANR5285I (S/390) Exit Machine Status:

Explanation: The list of mount exit virtual machinestatus follows.

System Action: The server lists the status of all mountexit virtual machines or the status of the one specifiedon the DSMOP QUERY command.


ANR5286I (S/390) Exit Machine mountvm: ″Ready″.

Explanation: The status of a mount exit virtualmachine is ready.



ANR5287I (S/390) Exit Machine mountvm: ″Busy″.

Explanation: The status of a mount exit virtualmachine is busy.



ANR5288I (S/390) Exit Machine mountvm: ″Offline″.

Explanation: The status of a mount exit virtualmachine is off-line.



ANR5289I (S/390) Volume volume (class class)mounted mode on raddr, status: ″Idle″.

Explanation: Volume volume, which is of device classclass and is mounted at address raddr in mode mode, iseligible for dismounting or reuse.



ANR5290I (S/390) Volume volume (class class)mounted mode on raddr, status: ″In Use″.

Explanation: Volume volume, which is of device classclass and is mounted at address raddr in mode mode, isin use by the server.



ANR5270I (S/390) • ANR5290I (S/390)


ANR5291I (S/390) Volume volume (class class)mounted mode on raddr, status:″Dismounting″.

Explanation: Volume volume, which is in device classclass and is mounted at address raddr in mode mode, isin the process of dismounting.



ANR5292I (S/390) number volume(s) found.

Explanation: A QUERY MOUNT command has beenissued; number volumes are mounted.



ANR5293I (S/390) Cancelling mount for volumevolume.

Explanation: A CANCEL MOUNT command has beenissued for volume volume. The CANCEL command isbeing processed.


User Response: Query the activity log to verify thatthe mount request has been cancelled.

ANR5294I (S/390) Volume volume (class class)mounted mode, status: ″Idle″.

Explanation: Volume volume, which is in device classclass in mode mode, is eligible for dismounting or reuse.



ANR5295I (S/390) Volume volume (class class)mounted mode, status: ″In Use″.

Explanation: Volume volume, which is in device classclass in mode mode, is in use by the server.



ANR5296I (S/390) Volume volume (class class)mounted mode, status: ″Dismounting″.

Explanation: Volume volume, which is in device classclass in mode mode, is in the process of dismounting.



ANR5297I (S/390) Volume volume (class class)mounted mode, status: ″In Retry″.

Explanation: Volume volume, which is in device classclass in mode mode, is currently in RETRY. An attemptis being made to re-establish communications withanother server. If the volume remains in retry status forthe amount of time specified by the device class retryperiod, the operation will fail and the volume will beautomatically dismounted.



ANR5300I (S/390) Verifying volume label volume IDon device real address.

Explanation: The server is verifying the volume labelof a mounted read/write volume again prior todismounting the volume.

System Action: The server performs the reverificationof the volume label as an integrity check of the volume.


ANR5301I (S/390) Request number: Verifying volumelabel volume ID on device device.

Explanation: The server is verifying the volume labelof a mounted volume during the mount process.

System Action: The server ensures that the volumemounted is acceptable.


ANR5302I (S/390) Request number: Assigning volumevolume ID to SCRTCH.

Explanation: The server has assigned the mountedvolume to be used as the requested scratch volume.

System Action: The server dynamically adds thevolume label of the mounted volume to the storagepool.


ANR5303I (S/390) Request number: Assigning volumevolume ID to EXPORT.

Explanation: The server has assigned the mountedvolume to be used as the requested export volume.

System Action: The server uses the volume for theEXPORT operation.


ANR5291I (S/390) • ANR5303I (S/390)


ANR5304I (S/390) Request number: Assigning volumevolume ID to IMPORT.

Explanation: The server has assigned the mountedvolume to be used as the requested import volume.

System Action: The server uses the volume for theIMPORT operation.


ANR5305E (S/390) Request number: Device real addressis not a supported devclass device.

Explanation: A device is attached to the server tosatisfy a mount request, but it is the wrong deviceclass. For example, a CARTRIDGE device has beenused when the request is for a REEL device.

System Action: The server dismounts the volume,detaches the device, and requests the original volumeagain.

User Response: Make sure the device used to satisfy amount request is the same type as the device requested.

ANR5306E (S/390) Request number: Device real addressnot capable.

Explanation: The server requested a volume with aspecific density or format. The device used to satisfythe mount cannot write using the requested density orformat.


User Response: Mount the volume on a devicecapable of the requested density or format.

ANR5307E (S/390) Request number: Volume on realaddress is write protected.

Explanation: The mounted volume is not enabled forwriting.


User Response: Enable the volume for writing andreply to the mount again.

ANR5308E (S/390) Request number: Volume on realaddress is not write protected.

Explanation: The mounted volume is not writeprotected.


User Response: Disable the volume for writing andreply to the mount again.

ANR5309E (S/390) Request number: Volume on realaddress has no VOL1 label.

Explanation: The mounted volume does not have astandard label.


User Response: Make sure you are mounting thecorrect volume. All volumes must have a standardVOL1 label.

ANR5310E (S/390) Volume on real address has noVOL1 label - volume integritycompromised.

Explanation: During volume unmount labelreverification, the server finds no VOL1 label.

System Action: The server marks the volume asunavailable.

User Response: The volume cannot be used becausethe VOL1 label has been overwritten. All active data onthe volume cannot be recovered. Delete the volumefrom the storage pool with the DELETE VOLUMEcommand by using the DISCARD=YES option. To usethis volume again, the volume must be initialized witha VOL1 label. The volume may then be redefined in thestorage pool.

ANR5311E (S/390) Request number: Volume label onraddr (volume ID found) does not matchvolume ID expected.

Explanation: During mount processing, the volume IDread on the mounted volume does not match thespecifically requested partially full volume.


User Response: Make sure you are mounting thecorrect volume.

ANR5312E (S/390) Volume label on raddr (volume IDfound) does not match volume ID expected- volume integrity compromised.

Explanation: During volume unmount labelreverification, the server finds a different VOL1 label.

System Action: The server marks the volume asunavailable.

User Response: The volume cannot be used becausethe VOL1 label has been overwritten by a differentVOL1 label. All active data on the volume cannot be

ANR5304I (S/390) • ANR5312E (S/390)


recovered. Delete the volume from the repository withthe DELETE VOLUME command by using theNORECLAIM option. To use this volume again, thevolume must be initialized with a VOL1 label. Thevolume may then be redefined in the repository.

ANR5313I (S/390) Request number: Mount for volumeID complete on device real address.

Explanation: A volume mount has successfullycompleted.

System Action: The task waiting for a volume mountresumes.


ANR5314E (S/390) Request number: Permanent I/Oerror on device real address.

Explanation: A permanent I/O error occurred whenthe device was opened.


User Response: Mount the volume on a differentdevice.

ANR5315E (S/390) Read Data Check on device realaddress.

Explanation: A data check occurred during a readoperation.

System Action: The server redrives the I/O by usingDiagnose X'20' or Diagnose X'A8'.


ANR5316E (S/390) Write Data Check on device realaddress.

Explanation: A data check occurred during a writeoperation.

System Action: The server redrives the I/O by usingDiagnose X'20' or Diagnose X'A8'.


ANR5317I (S/390) Make device real address ready.

Explanation: The device is in a not ready condition.

System Action: The server sends an interventionrequired message to the mount operator user IDs listedin the DSMSERV OPT file.

User Response: Make the device ready.

ANR5318I (S/390) Intervention cleared on device realaddress.

Explanation: The device requiring operatorintervention is now ready.

System Action: The task waiting for the devicecontinues.


ANR5319I (S/390) Intervention required on devicereal address.

Explanation: The device requires operatorintervention.

System Action: The task waits until the device ismade ready.

User Response: Make the device ready.

ANR5320I (S/390) Volume volume ID already in use.

Explanation: A tape volume has been mounted for useby the server; after mounting the volume, the serverdetermined that the volume was already in use by theserver and could not be used to satisfy the currentmount request.

System Action: The server dismounts the volume,detaches the device, and reissues the original request.

User Response: Mount a volume not already in useby the server.

ANR5321I (S/390) End of volume reached for volumeID on device real address.

Explanation: During processing of a read/write tapevolume, the end of the tape volume has been reached.

System Action: The volume is marked read-only andkept mounted for later use.


ANR5322I (S/390) Permanent error on volume volumeID on device real address.

Explanation: During processing of a tape volume, apermanent I/O error occurred.

System Action: The server places the volume in anI/O error state. If the volume was being used forwriting, it is marked read-only.


ANR5323I (S/390) Assigning volume volume ID toSCRTCH.

Explanation: The server has assigned the mountedvolume to be used as the requested scratch volume.

System Action: The server dynamically adds the

ANR5313I (S/390) • ANR5323I (S/390)


volume label of the mounted volume to the storagepool.


ANR5324I (S/390) Assigning volume volume ID toEXPORT.

Explanation: The server has assigned the mountedvolume to be used as the requested export volume.

System Action: The server uses the volume for theEXPORT operation.


ANR5325I (S/390) Assigning volume volume ID toIMPORT.

Explanation: The server has assigned the mountedvolume to be used as the requested import volume.

System Action: The server uses the volume for theIMPORT operation.


ANR5326E (S/390) Volume label on raddr (volume IDfound) does not match volume ID expected.

Explanation: During mount processing, the volume IDread on the mounted volume does not match thespecifically requested partially full volume.


User Response: Make sure you are mounting thecorrect volume.

ANR5327I (S/390) Request number: Assigning volumevolume ID to DUMPDB.

Explanation: The server has assigned the mountedvolume to be used as the requested DUMPDB volume.

System Action: The server uses the volume for theDUMPDB operation.


ANR5328I (S/390) Request number: Assigning volumevolume ID to LOADDB.

Explanation: The server assigns the mounted volumefor use as the requested LOADDB volume.

System Action: The server uses the volume for theLOADDB operation.


ANR5329I (S/390) Assigning volume volume ID toDUMPDB.

Explanation: The server assigns the mounted volumefor use as the requested DUMPDB volume.

System Action: The server uses the volume for theDUMPDB operation.


ANR5330I (S/390) Assigning volume volume ID toLOADDB.

Explanation: The server assigns the mounted volumefor use as the requested LOADDB volume.

System Action: The server uses the volume for theLOADDB operation.


ANR5331S (S/390) Volume volume ID damaged -recovery required.

Explanation: The server detects an error on thespecified volume. The volume has been unexpectedlyrepositioned during write processing. Data may havebeen lost.

System Action: The server halts the process that isusing the volume and marks the volume as read-only.

User Response: For EXPORT, DBBACKUP, orDBDUMP tapes, restart the export, backup, or dumpoperation. Do not use the tape for an IMPORT,DBRESTORE, or DBLOAD operation. If the tape is astorage pool volume, you can attempt to recover thedata with the following steps:

1. To identify any missing data, issue the AUDITVOLUME command by specifying FIX=NO.

2. If recoverable data exists on the tape, deletereferences to the missing data from the database byissuing the AUDIT VOLUME command andspecifying FIX=YES.

3. Issue the MOVE DATA command to remove alldata from the damaged tape after the AUDIT(FIX=YES) has completed.

NOTE: Issuing an audit command on a damagedvolume can result in a large number of loggedmessages.

ANR5332I (S/390) Request number: Assigning volumevolume ID to DBBKUP.

Explanation: The server assigns the mounted volumefor use as the requested DBBKUP volume.

System Action: The server uses the volume for theDBBKUP operation.


ANR5324I (S/390) • ANR5332I (S/390)


ANR5333I (S/390) Assigning volume volume ID toDBBKUP.

Explanation: The server assigns the mounted volumefor use as the requested DBBKUP volume.

System Action: The server uses the volume for theDBBKUP operation.


ANR5334W (S/390) Volume volume ID reached end oftape.

Explanation: The server has detected end of tape forthe specified volume. The volume reached the end oftape before the maximum capacity value specified inthe device class was reached.

System Action: The server requests another volume ifone is available. The current process stops writing tothe specified volume.

User Response: Reduce the maximum capacity in thedevice class. The QUERY VOLUME command willindicate the actual capacity of the volume after it is full.Use the UPDATE DEVCLASS command to change themaximum capacity for the device class.

ANR5335E (S/390) Volume volume ID already used.

Explanation: A tape volume is mounted as scratch foruse by the server. After mounting the volume, theserver determines that the volume has already beenused by the server and cannot be used to satisfy thecurrent mount request. Mounting the volume as scratchmay have destroyed some of the data previouslywritten on that volume.

System Action: The server dismounts the volume,detaches the device, and reissues the original request.

User Response: Mount a volume not already in useby the server. The damaged volume must be replaced,restored, or deleted from the volume history file.

v If the volume is an Export, Database Dump orDatabase Backup volume that contains data that isno longer needed, use the DELETE VOLHISTORYcommand to make the volume available to the serverfor reuse.

v If the volume mounted is an Export or DatabaseDump, the tapes are no longer good and anotherexport or dump must be taken. If the tape is acurrent Database Backup volume, a full backup mustbe done to insure a complete backup exists.

v If the volume is a storage pool volume, audit thevolume. If it is a primary volume and a copypoolexists, restore the volume. If it is a copypool volume,backup the storage pool again to insure a backupcopy exists for all files.

It is strongly recommended that you use theDEVCLASS EXPIRATION or RETENTION parameterto protect your tapes and prevent damage to tapes youcreate in the future.

ANR5336E (S/390) Volume volume ID must beread-only on 3590 device.

Explanation: The server requests a volume in a modeother than read-only. The 3590 device that is used tosatisfy the mount cannot be used to write to thevolume.

System Action: The server cancels the currentoperation.

User Response: Update the volume access toREADONLY or insure that a device of the type used tocreate the volume is used to satisfy the mount.

ANR5337I (S/390) Assigning volume volume ID tobackup set.

Explanation: The server has assigned the mountedvolume to be used as the requested backup set volume.

System Action: The server uses the volume for thebackup set operation.


ANR5338E (S/390) DEVCLASS device class mountedDevice real address, device not capable.

Explanation: The server requested a volume with aspecific format. The device used to satisfy the mountcannot write using the requested format.


User Response: Check the devclass UNIT parameter,and insure the device requested matched the formattype defined.

ANR5350E (S/390) Error locating block block numberon device real address.

Explanation: A Locate Block CCW failed.

System Action: The server marks the volume in anI/O error condition and requests another volume bemounted.

User Response: This failure may be due to a hardwareproblem. Reset the error condition with the UPDATEVOLUME command. If the problem persists, use theDELETE VOLUME command with the DISCARD=NOoption to remove the volume from the storage pool.

ANR5333I (S/390) • ANR5350E (S/390)


ANR5351E (S/390) Error reading BlockID on devicereal address.

Explanation: A Read Block ID CCW failed.



ANR5352E (S/390) Synchronize failed on device realaddress.

Explanation: A Synchronize CCW failed.

System Action: The server marks the volume in anI/O error condition, and requests another volume bemounted.

User Response: Reply to the new mount request.Reset the error condition with the UPDATE VOLUMEcommand. The integrity of the original volume mayhave been compromised. To delete the volume, issuethe DELETE VOLUME command with theDISCARD=NO option.

ANR5353E (S/390) Load Display failed on device realaddress.

Explanation: A Load Display CCW failed.

System Action: Server operation continues. No text isloaded into the display window.


ANR5354E (S/390) Block block number sequence erroron device real address.

Explanation: During a read operation, the block ID ofthe block being read does not match the block IDstored in the data block header.

System Action: The server places the volume in anI/O error state.

User Response: The integrity of the volume may havebeen compromised. Reset the error condition with theUPDATE VOLUME command and attempt theoperation on a different tape drive. If the problempersists, you can delete the volume with the DELETEVOLUME command, by using the DISCARD=NOoption.

ANR5355E (S/390) Reload cartridge on device realaddress.

Explanation: The cartridge is not inserted correctly, orthe tape is not processed correctly.

System Action: The task waits until the drive is madeready. An intervention required message is sent to themount operator user IDs.

User Response: Make the drive ready.

ANR5356E (S/390) Unload cartridge on device realaddress.

Explanation: The drive cannot maintain tape tensionand control tape movement during an unloadoperation.

System Action: The task waits until the drive is madeready. An intervention required message is sent to themount operator user IDs.

User Response: Make the drive ready.

ANR5357E (S/390) Manual Rewind/Rewind-Unloadon device real address.

Explanation: The Rewind Unload switch or theRewind switch on the drive has been pressed.

System Action: The server verifies the volume labeland attempts to reposition the tape and continueoperation. If the volume label verification fails, theserver marks the volume in the unavailable state. If thereposition fails, the server marks the volume in the I/Oerror state.

User Response: If the server succeeds in its recovery,no action is required. If recovery is unsuccessful, youcan reset the error status of the volume with theUPDATE VOLUME command. Volume integrity mayhave been compromised. Issue the DELETE VOLUMEcommand with the DISCARD=NO option to try torecover any data.

ANR5358E (S/390) Request number: I/O Error atbeginning of tape on real address.

Explanation: An I/O error has occurred attempting tomount a tape volume; the beginning of the volumecannot be detected.

System Action: The server places the volume in anI/O error state.

User Response: The integrity of the volume may havebeen compromised. Reset the error condition with theUPDATE VOLUME command and attempt theoperation on a different tape drive. If the problempersists, you can delete the volume with the DELETEVOLUME command, by using the DISCARD=NOoption.

ANR5351E (S/390) • ANR5358E (S/390)


ANR5359E (S/390) Request number: Cartridge LengthError on device real address.

Explanation: A tape cartridge has been mounted thatis too short for processing on the drive.


User Response: Reply to the new mount request. Ifnecessary, reset the error condition with the UPDATEVOLUME command. The integrity of the originalvolume may have been compromised. To delete thevolume, issue the DELETE VOLUME command withthe DISCARD=NO option.

ANR5360E (S/390) Request number: Cartridge LengthIncompatible on device real address.

Explanation: A tape cartridge has been mounted on adrive and the tape is too long to be processed on thedrive or has been initialized to the wrong length.



ANR5361E (S/390) Request number: Cartridge FormatIncompatible on device real address.

Explanation: A tape cartridge has been mounted on adrive, but the tape format cannot be processed on thedrive.



ANR5362E (S/390) Request number: Cartridge LengthViolation on device real address.

Explanation: A tape cartridge has been mounted on adrive but the tape is too long to be processed on thedrive.



ANR5363E (S/390) Request number: CartridgeCompaction Incompatible on device realaddress.

Explanation: A tape cartridge has been mounted on adrive but the tape compression algorithm ID is notcompatible with the drive.



ANR5364E (S/390) Record sequence error on devicereal address.

Explanation: During processing of a tape volume, therecord tape number read does not match that expectedby the drive.

System Action: The server marks the volume in anI/O error condition.


ANR5365E (S/390) Volume fenced on device realaddress.

Explanation: During processing of a tape volume,errors have occurred that caused the tape drive to losethe ability to process the volume.

System Action: The server marks the volume in anI/O error condition.

User Response: Unload and reload the tape to resetthe drive. Reset the error condition with the UPDATEVOLUME command. This failure may be due to ahardware problem. If the problem persists, use theDELETE VOLUME command with the DISCARD=NOoption to remove the volume from the storage pool.

ANR5359E (S/390) • ANR5365E (S/390)


ANR5366E (S/390) Request number: Volume volume IDdata set name ″label dsn″ in HDR1 labelcannot be overwritten with Export dataset name ″export dsn″.

Explanation: During mount processing of an EXPORTtape volume, the server encountered a nonblank dataset name in the HDR1 label. Normally, the serverwrites the export dsn in this field.


User Response: Most tape volume initializationprograms only write VOL1 label. If your tape volumeinitialization program also writes a HDR1 label, thedata set name in the HDR1 label must be blank. Besure that the volume in question is the proper tapevolume, and reinitialize it with only a VOL1 label, orwith a blank data set name in the HDR1 label.

ANR5367I (S/390) Request number: Volume volume IDdata set name ″label dsn″ in HDR1 labelwill be overwritten with Export data setname ″export dsn″.

Explanation: During mount processing of an EXPORTtape volume, the server encountered a nonblank dataset name in the HDR1 label. This data set name will beoverwritten with export dsn.

System Action: The server continues with mountprocessing.


ANR5368E (S/390) Request number: Volume volume IDdata set name ″label dsn″ in HDR1 labelcannot be overwritten with DUMPDBdata set name ″dumpdb dsn″.

Explanation: During mount processing of anDUMPDB tape volume, the server encountered anonblank data set name in the HDR1 label. Normally,the server would write the dumpdb dsn in this field.


User Response: Most tape volume initializationprograms only write a VOL1 label. If your tape volumeinitialization program also writes a HDR1 label, thedata set name in the HDR1 label must be blank. Besure the volume in question is the correct tape volume,and reinitialize it with only a VOL1 label, or with ablank data set name in the HDR1 label.

ANR5369I (S/390) Request number: Volume volume IDdata set name ″label dsn″ in HDR1 labelwill be overwritten with DUMPDB dataset name ″dumpdb dsn″.

Explanation: During mount processing of anDUMPDB tape volume, the server encountered anonblank data set name in the HDR1 label. This dataset name will be overwritten with dumpdb dsn.



ANR5370E (S/390) Invalid block header on devicereal address.

Explanation: During a read operation, the blockheader of the block read does not contain datarecognized by the server.

System Action: The server may place the volume inan I/O error state.

User Response: The integrity of the volume may havebeen compromised. Reset the error condition with theUPDATE VOLUME command and attempt theoperation on a different tape drive. If the problempersists, try to audit the volume by using the AUDITVOLUME command to see if any files on the volumecan be recovered. If not, you can delete the volumewith the DELETE VOLUME command, by using theDISCARD=NO option.

If a LOADDB operation was being performed, specifythe command syntax by either using a ddname or byspecifying a device class name. You must use the samemethod that was used when the data base wasoriginally dumped. Otherwise, this error message isdisplayed. Try loading the data base by using the othermethod of syntax (ddname). Also, verify that youspecified the correct volume name. The integrity of thevolume may have been compromised. In this case, thevolume cannot be used by the LOADDB operation.

ANR5371E (S/390) Request number: Volume volume IDdata set name ″label dsn″ in HDR1 labelcannot be overwritten with DBBKUPdata set name ″dbbkup dsn″.

Explanation: During mount processing of a DBBKUPtape volume, the server encountered a nonblank dataset name in the HDR1 label. Normally, the serverwrites the dbbkup dsn in this field.


User Response: Most tape volume initializationprograms only write VOL1 label. If your tape volumeinitialization program also writes a HDR1 label, thedata set name in the HDR1 label must be blank. Be

ANR5366E (S/390) • ANR5371E (S/390)


sure that the volume in question is the proper tapevolume, and reinitialize it with only a VOL1 label, orwith a blank data set name in the HDR1 label.

ANR5372I (S/390) Request number: Volume volume IDdata set name ″label dsn″ in HDR1 labelwill be overwritten with DBBKUP dataset name ″dbbkup dsn″.

Explanation: During mount processing of a DBBKUPtape volume, the server encountered a nonblank dataset name in the HDR1 label. This data set name will beoverwritten with dbbkup dsn.



ANR5373I (S/390) Cannot allocate tape drive of unittype unit type for tape volume ID. ReplyC (cancel), R (retry), or W (wait).

Explanation: The server attempts to allocate a tapedrive. The allocation attempt fails because noacceptable tape drive is available. An acceptable tapedrive has the unit type indicated in the message.

Before more attempts are made to allocate the tapedrive, the operator is prompted to indicate whether ornot the tape drive allocation request can be satisfied.The unit type and the VOLSER of the tape volumevolser to be used for the pending request are providedin the message text.

System Action: If the operator replies ’R’ (meaningretry), the server will retry the tape drive allocation. Ifno acceptable drive is available after retrying theallocation, the server will reissue this message.

If the operator replies ’W’ (meaning wait), the serverwill retry the tape drive allocation. If the allocationrequest cannot be satisfied immediately, the server willwait while MVS Allocation Recovery issues messageIEF238D. After IEF238D is issued, none of the followingcan occur in the server until the allocation completes oris canceled:

v dynamic allocations or deallocations

v file opens or closes

v tape volume changes between read mode and writemode

If the operator replies ’C’ (meaning cancel), the serverwill fail the tape drive allocation and its associatedserver request.

Any other reply will cause the server to reissue thismessage. Determine if there are any tape drives whichcan be used to satisfy this request (either online oroffline) prior to responding to this message.


ANR5374I (S/390) Tape volume volume ID on realaddress real address has had anunsolicited interrupt, and may havebeen dismounted.

Explanation: An unsolicited interrupt is received forthe drive where the volume is mounted. The drive isnot ready or its state cannot be determined, so the tapemay have been dismounted.

System Action: If the server can recover withoutpossibility of data loss, it will reverify the label andcontinue operations. If the label is not verified or dataloss is possible with continued use, the next operationwill fail and the tape will be dismounted.

User Response: Check the tape drive.

ANR5404I (S/390) SERVER volume volume namemounted.

Explanation: The server has mounted the givenvolume.

System Action: Read or write operations, or both, willcommence for the volume.


ANR5405I (S/390) End-of-volume reached forSERVER volume volume name.

Explanation: The server has detected anend-of-volume condition for the given volume.

System Action: The volume is marked full. If moredata must be stored, the server accesses anothervolume.


ANR5410I (S/390) FILE volume volume namemounted.

Explanation: The server has opened the given file tosimulate a tape volume.



ANR5411I (S/390) End-of-volume reached for FILEvolume volume name.


System Action: The volume is marked full. If moredata must be stored, the server accesses anothervolume.


ANR5372I (S/390) • ANR5411I (S/390)


ANR5412I (S/390) FILE volume volume nameMAXCAPACITY larger than allowedmaximum. Overriding maximumcapacity to FILE maximum capacityMB.

Explanation: The maximum capacity specified for thelisted volume is larger than the maximum allowed forthe FILE device class.

System Action: The volume capacity is set to themaximum allowed for the FILE device class.

User Response: Update the device class of the volumeMAXCAPACITY value to less than or equal themaximum allowed for the FILE device class.

ANR5413E (S/390) Dynamic allocation of FILEvolume volume on unit=unit volser=volserreturned rc=rc, info code=info code, errorcode=error code.

Explanation: The dynamic allocation of FILE volumevolume on unit unit and volume serial volser fails. Theserver uses the unit and volser device class parameterswhen allocating new FILE volumes, and alwayscatalogs the actual MVS data sets. If these parametersare not defined, Dynamic Allocation uses systemdefaults to select a device on which to create the MVSsequential data set.

For previously allocated FILE volumes, the serverallows Dynamic Allocation to locate the actual MVSdata set using catalog services.

The return code rc, information code info code and errorcode error code are in decimal and can be found in theDynamic Allocation section of MVS/ESA Programming:Authorized Assembler Services Guide.


User Response: For new FILE volumes, verify that alldevice class parameters are defined correctly and arecompatible, and that space is available on the targetDASD.

ANR5414E (S/390) Error error code returned whileopening FILE volume volume

Explanation: The BSAM OPEN fails. Error code errorcode is returned. Check for accompanying MVS errormessages.

Error codes greater than eight are MVS ABEND codes,documented in MVS/ESA System Codes, GC28-1486.


User Response: For previously allocated FILEvolumes, verify that the MVS data set used for theFILE volume exists on the physical device designatedby the catalog. Check the accompanying MVS systemmessages.

ANR5415W (S/390) SFS CSL call CSL name failedwith return code rc, reason code rs.optional (file or directory being processed)

Explanation: A call to an SFS CSL routine failed.

System Action: See following server messages.

User Response: Check the return and reason codes inthe System Messages and Codes manual, ″CallableServices Library (CSL) Reason Codes″ section, forinformation on the problem and on the action neededto correct it.

ANR5416E (S/390) Minidisk device class cannot beused with SFS file file name.

Explanation: A device class of DEVTYPE=FILE isdefined with FILEMODE= where the file mode letter isassociated with an SFS directory. Device classes definedwith DEVTYPE=FILE and FILEMODE= parameters canonly be associated with an accessed minidisk (CMS filemode letter A-Z).

System Action: File is not used.

User Response: When using a minidisk, define theDEVTYPE=FILE device class with the FILEMODE=parameter. When using an SFS directory, use theDIRECTORY= parameter.

ANR5417E (S/390) File file name already exists, itcannot be created.

Explanation: The server attempted to create a new fileusing file name but received indication that the filealready exists. The server will create a new file after itdetermines that the file named file name is not in itsdatabase. The server will append to an existing filewith the name file name only if it exists in its database.The server will not overwrite an existing file.


User Response: The file named file name must eitherbe renamed or erased.

ANR5418E (S/390) File file name cannot be used.

Explanation: The server found that the file file nameexists in its database, but either was accessed asread-only or the file did not exist on the minidiskidentified by the file mode letter or the file did notexist in the SFS directory.


User Response: Make sure the minidisk is accessedwith the file mode letter specified for the device classdefined with DEVTYPE=FILE FILEMODE=?. If the fileis in an SFS directory, make sure the SFS directory stillexists and the server user ID has been grantedread/write authority to the directory and to the filenamed command. If the volume status is read/write and

ANR5412I (S/390) • ANR5418E (S/390)


the volume is not full, write access is required. If thefile does not exist, the server cannot use the volume.Storage volumes should be deleted using the DELETEVOLUME command with DISCARDDATA=YES.Volumes for IMPORT, LOAD or RESTORE DB cannotbe used.

ANR5419E (S/390) Filemode or directory filemode ordirectory name cannot be used.

Explanation: The server determined that a minidiskwith the file mode letter filemode or that the SFSdirectory directory name were not available for use.

System Action: Server operation continues but file isnot used.

User Response: Ensure that a minidisk is accessedwith the file mode letter filemode or that an SFSdirectory directory directory exists and that the serveruser ID has been granted read/write authority to thedirectory and all files in that directory.

ANR5420W (S/390) FILE FILE name not deleted fromsystem, return code return code.

Explanation: A volume associated with a device classdefined with DEVTYPE=FILE was deleted from theserver, but the associated CMS file or MVS data setFILE name could not be deleted.

System Action: Server operation continues. No otherattempts will be made to delete the volume from thesystem.

User Response: If the volume was created and neverused, a CMS file or an MVS dataset may not have beencreated and no action is required. If the CMS file or theMVS dataset FILE name exists it will have to be deletedmanually.

ANR5450E (S/390) Error opening filespec.

Explanation: An error occurred while attempting anopen operation.


User Response: Refer to the other displayed messagesto determine why the open operation failed. Correct theproblem and restart the process.

ANR5451E (S/390) An error (error code) occurredduring a write operation.

Explanation: An error occurred while attempting awrite operation.


User Response: Refer to the other displayed messagesto determine why the write operation failed. Correctthe problem and restart the process.

ANR5452E (S/390) An error (error code) occurredduring a read operation.

Explanation: An error occurred while attempting aread operation.


User Response: Refer to the other displayed messagesto determine why the read operation failed. Correct theproblem and restart the process.

ANR5453E (S/390) Device type volume volume namecannot be overwritten by EXPORToperation.

Explanation: The specified volume already exists orcontains data. The server does not allow new exportdata to be written to the volume.

System Action: The server detects that the givenvolume already contains some data that would beoverwritten by the requested export operation.

User Response: If the specified volume does notcontain any valuable data, delete it and retry the exportoperation.

ANR5454E (S/390) Device type volume volume namecannot be overwritten by DUMPDBoperation.

Explanation: The specified volume already exists orcontains data. The server does not allow new dumpdata to be written to the volume.

System Action: The server detects that the givenvolume already contains some data that would beoverwritten by the requested dump operation.

User Response: If the specified volume does notcontain any valuable data, delete it and retry the dumpoperation.

ANR5455E (S/390) Device type volume volume namecannot be overwritten by BACKUP DBoperation.

Explanation: The specified volume already exists orcontains data. The server does not allow new backupdata to be written to the volume.

System Action: The server detects that the givenvolume already contains some data that would beoverwritten by the requested backup operation.

User Response: If the specified volume does notcontain any valuable data, delete it and retry thebackup operation.

ANR5419E (S/390) • ANR5455E (S/390)


ANR5456E (S/390) Device type volume volume namecannot be overwritten by backup setoperation.

Explanation: The specified volume already exists orcontains data. The server does not allow new backupset data to be written to the volume.

System Action: The server detects that the givenvolume already contains some data that would beoverwritten by the requested backup set operation.

User Response: If the specified volume does notcontain any valuable data, delete it and retry thebackup set operation.

ANR5499E (S/390) Command: Required parameter wasnot specified parameter.

Explanation: The command command has been issued,but without a required parameter. If two parametersare listed, the command requires at least one of theparameters.


User Response: Reissue the command and specify themissing parameter and any additional parameters thatare required for the command. The HELP DEFINE orHELP UPDATE commands may be used to obtainsyntax assistance.

ANR5500E (S/390) Command: Device type notspecified.

Explanation: The command command has been issued,but without the DEVTYPE keyword.


User Response: Reissue the command, and specify theDEVTYPE keyword and any additional parameters thatare required for the command. The HELP DEFINE orHELP UPDATE commands may be used to obtainsyntax assistance.

ANR5501E (S/390) Command: ″attribute″ is invalid fordevice type.

Explanation: The command command has been issuedwith an incompatible combination of device type andattribute.


User Response: Reissue the command, and specify acompatible set of attributes. The HELP DEFINE orHELP UPDATE commands may be used to obtainsyntax assistance.

ANR5502E (S/390) Command: ″LENGTH″ is invalidwith 3480 and 3480XF formats.

Explanation: The command command has been issuedwith an incompatible combination of device type,FORMAT, and LENGTH. A length specification isinvalid with 3480 and 3480XF formats.


User Response: Reissue the command, and specify acompatible set of attributes. For 3480 and 3480XFformats, reenter the command without a LENGTHkeyword. The HELP DEFINE or HELP UPDATEcommands may be used to obtain syntax assistance.

ANR5503E (S/390) Command: Invalid parameter forupdate - parameter.

Explanation: The command command has been issued.However, the parameter is not an attribute that must beupdated.


User Response: Reissue the command, and specify acompatible set of attributes. The HELP UPDATEcommand may be used to obtain syntax assistance.

ANR5504E (S/390) Command: ″new attribute″ conflictswith existing ″old attribute″.

Explanation: The command command has been issued.However, new attribute conflicts with old attribute inupdating the device class.


User Response: Reissue the command, and specify acompatible set of attributes. You may have to specifyadditional keywords to update the device class in acompatible manner. The HELP UPDATE command maybe used to obtain syntax assistance.

ANR5505E (S/390) Command: ″MOUNTLIMIT″ is lessthan current number of mountedvolumes.

Explanation: The command command has been issuedthat specifies a MOUNTLIMIT smaller than the existingnumber of volumes that are already allocated.


User Response: You may wait until volumes are nolonger in use to reissue the command. Alternatively,you may cancel sessions or processes that are usingvolumes; then issue DISMOUNT commands to freeallocated volumes before reissuing the command. TheQUERY MOUNT command can be issued to determinewhich volumes are mounted for use by the server.

ANR5456E (S/390) • ANR5505E (S/390)


ANR5506E (S/390) Command: Conflicting parameters″parm1″ and ″parm2″.

Explanation: The command command has been issuedthat specifies conflicting parameters parm1 and parm2.Conflicting parameters include specifying FORMATand LENGTH with DENSITY, and RETENTION withEXPIRATION.


User Response: Reissue the command, and specify acompatible set of parameters. The HELP DEFINE orHELP UPDATE commands may be used to obtainsyntax assistance.

ANR5507E (S/390) Command: Device type ″devtype″not supported on this platform.

Explanation: An unsupported device type has beenspecified for command. In MVS, for example, the REELdevice type is not supported.


User Response: Specify a valid device type for theplatform. The HELP DEFINE command may be used toobtain syntax assistance.

ANR5508E (S/390) Device class device class notdefined in device configuration file.

Explanation: The issued command requires that thespecified device class be defined in the deviceconfiguration file. The definition was not found.


User Response: Reissue the command, and specify avalid device class. You may also want to refresh yourdevice configuration file by issuing the BACKUPDEVCONFIG command.

ANR5509E (S/390) Command: Parameter Parameter islarger than the allowed maximum ofMaximum valueM.

Explanation: The specified parameter is larger thanthe allowed maximum for this device class.


User Response: Reissue the command, and specify aparameter less than or equal to the allowed maximum.

ANR5510E (S/390) Data set name dsn is not valid.

Explanation: Data set name dsn is not valid.


User Response: Reissue the server command, andspecify a valid data set name.

ANR5511E (S/390) Unit name unit is not valid.

Explanation: Unit name unit is not valid.


User Response: Reissue the server command, andspecify a valid unit name.

ANR5512E (S/390) Volume serial volser is not valid.

Explanation: Volume serial volser is not valid.


User Response: Reissue the server command, andspecify a valid volume serial.

ANR5513E (S/390) Expiration date expdt is not valid.

Explanation: Expiration data expdt is not valid.


User Response: Reissue the server command, andspecify a valid expiration date.

ANR5514E (S/390) Retention period retpd is not valid.

Explanation: Retention period retpd is not valid.


User Response: Reissue the server command, andspecify a valid retention period.

ANR5515I (S/390) Library library name defined.

Explanation: The designated library has beensuccessfully defined.

System Action: The library is defined and recorded inthe database.


ANR5516E (S/390) Command: Incorrect library namelibrary name.

Explanation: The designated library name is incorrect;either it contains too many characters, or some of thecharacters are incorrect.


User Response: Reissue the command using a validlibrary name.

ANR5517E (S/390) Command: Library library name isalready defined.

Explanation: The designated library cannot be definedbecause it already exists.


User Response: If you want to define an additional

ANR5506E (S/390) • ANR5517E (S/390)


library, reissue the command with a different libraryname.

ANR5518E (S/390) Command: Incorrect value forparameter parameter.

Explanation: An incorrect value has been provided forthe specified parameter.


User Response: Reissue the command, and specify avalid parameter value.

ANR5519I (S/390) Library library name updated.

Explanation: The designated library has beensuccessfully updated.

System Action: The library is updated and recordedin the database.

User Response: If you want to update an additionallibrary, reissue the command with a different libraryname.

ANR5520I (S/390) Library library name deleted.

Explanation: The designated library has beensuccessfully deleted.

System Action: The library is deleted and removedfrom the database.


ANR5953W (S/390) Unable to generate accountingrecord - ACCT option not specified inCP directory.

Explanation: The SET ACNT ON command has beenentered, but the server is unable to generate anaccounting record because the ACCT option has notbeen specified in the server’s CP directory entry.

System Action: Server operation continues. Noaccounting record is generated.

User Response: Add the ACCT option to the server’sCP directory entry. To suppress these messages untilthe CP directory can be updated, enter the SET ACNTOFF command.

ANR5954W (S/390) Unable to generate accountingrecord - insufficient memory.

Explanation: The SET ACNT ON command has beenentered, but the server is unable to generate anaccounting record due to a lack of memory (virtualstorage). In some cases a 4096-byte buffer is requiredfor accounting operations, and it is this buffer thatcannot be allocated.

System Action: Server operation continues. Noaccounting record is generated.


1. Increase the size of the server’s virtual machine.This requires that the default storage size beupdated in the server’s CP directory entry.

2. Reduce the maximum number of client sessionspermitted. To do this, edit the DSMSERV OPT fileand reduce the value specified for theMAXSESSIONS statement. Note that each clientsession causes an additional 64KB of memory to beallocated.

3. Decrease the amount of space allocated to theserver’s database buffer pool. To do this, edit theDSMSERV OPT file and reduce the value specifiedfor the BUFPOOLSIZE statement. Note that eachbuffer pool page causes an additional 4 KB ofmemory to be allocated.

Note that the server must be shut down (with theHALT command) before changes can be made to theDSMSERV OPT file.

ANR5956E (S/390) C library not available, unable tocontinue.

Explanation: The C/370 or LE/370 library is notavailable.


User Response: Make the C/370 or LE/370 libraryavailable to the server.

ANR5957W (S/390) C library is at level level.

Explanation: The C run-time library is at a lower level(level) than expected.

System Action: Server attempts to continue operation.

User Response: Ensure that the proper level of theC/370 or LE/370 library is installed and available tothe server.

ANR5958E (S/390) SVM is at level level, the serverrequires at least required-level, unable tocontinue.

Explanation: The SVM run-time library is at levellevel, but the server requires at least level required-level.


User Response: Check the required PTFs for theserver. Ensure that the proper level of SVM is installed.

ANR5959E (S/390) Server not running APFauthorized. The server and allJOBLIB/STEPLIB libraries (C libraryand other libraries) must be authorized.

Explanation: The server is not running with MVSauthorization.

ANR5518E (S/390) • ANR5959E (S/390)



User Response: Ensure that all library data setsrequired by the server are authorized.

ANR5960E (S/390) Unable to initialize kernel -virtual machine requires ECMODEcapability.

Explanation: The CP directory entry for the serverdoes not contain an OPTION ECMODE statement.


User Response: Add an OPTION ECMODE statementto the CP directory entry for the server.

ANR5961E (S/390) Insufficient memory for serverinitialization.

Explanation: The server program cannot allocateenough memory (virtual storage) to fully initializeitself.

System Action: Server initialization fails. The server isnot started.

User Response: Allocate additional storage to theserver virtual machine or reduce the storage requiredby the server. There are three ways to do this:

1. Increase the size of the server’s virtual machine.This requires that the default storage size beupdated in the server’s CP directory entry.

For MVS, increase the region size; 40M is therecommended minimum size for the server butlarger servers require more.

2. Reduce the maximum number of client sessionspermitted. To do this, edit the DSMSERV OPT fileand reduce the value specified for theMAXSESSIONS statement. Note that each clientsession causes an additional 64KB of memory to beallocated.

3. Decrease the amount of space allocated to theserver’s database buffer pool. To do this, edit theDSMSERV OPT file and reduce the value specifiedfor the BUFPOOLSIZE statement. Note that eachbuffer pool page causes an additional 4 KB ofmemory to be allocated.

Note that the server must be shut down (with theHALT command) before changes can be made to theDSMSERV OPT file.

ANR5962I (S/390) DSMSERV generated at time ondate.

Explanation: The server module has been generated atthe indicated date and time.



ANR5963I (S/390) Server termination complete.

Explanation: The server has completed shut down.



ANR5964E (S/390) Server unable to mark itselfnon-swappable. Return code rc fromSYSEVENT TRANSWAP.

Explanation: The server cannot issue a SYSEVENTTRANSWAP macro.



ANR5965I (S/390) Console command: command

Explanation: A server command command has beenreceived from an MVS operator console.



ANR5967W (S/390) Accounting record not produced,return code rc.

Explanation: There was a problem generating theaccounting record.



ANR5980E (S/390) Unable to initialize PDM driver -insufficient memory.

Explanation: The server’s PDM communicationsdriver is unable to initialize itself due to insufficientmemory (virtual storage).



1. Increase the size of the REGION parameter on theEXEC or JOB statement of the JCL used to start theserver.



ANR5960E (S/390) • ANR5980E (S/390)



ANR5981I (S/390) InfoSpeed/PDM communicationenabled on port port number.

Explanation: The server’s PDM communicationsdriver is ready to receive connection requests fromclients.



ANR5982E (S/390) InfoSpeed accept error rc = rc onport port number.

Explanation: The server’s InfoSpeed communicationsdriver has received an error from the ACCEPTfunction.

System Action: Server operation continues andInfoSpeed communications will be retried.


ANR5983I (S/390) Unable to use SCRATCH volumesfor LAN-free storage operation.

Explanation: The z/OS server prohibits SCRATCHvolume selection for LAN-free activity. For a volumeselection to satisfy a LAN-Free request, it must bewritten to by the Tivoli Storage Manager z/OS version5.2 server at least once. After this occurs, the volumebecomes eligible for LAN-Free operations.

System Action: Session ends.

User Response: It is necessary to define volumesdestined for LAN-Free storage requests. Allowing thez/OS server to allocate a SCRATCH volume whenpopulating a LAN-Free storage pool will render thevolume ineligible for LAN-Free selection. Theadministrator should maintain a storage pool of emptyor filling volumes in order to satisfy LAN-Freerequests.

ANR5984E (S/390) Command: One or more paths arestill defined to library library name.

Explanation: The designated library cannot be deletedbecause there are still paths defined to it.


User Response: Delete all paths to this library, andreissue the command.

ANR5985E (S/390) Command: Library library name isnot defined.

Explanation: The designated library has not beendefined.


User Response: Reissue the command using adifferent library name, or define the library beforeretrying the command.

ANR6200I Command name: Level compression auditlevel compression audit started asprocess process ID.

Explanation: A compression audit at the specifiedlevel has been started as a background server processwith the process identifier reported.

System Action: Server operation continues. Thebackground audit attempts to identify client files thatmay be affected by the client compression problem.


ANR6201I Command name: Level compression auditlevel compression audit starting asbackground process process ID.

Explanation: A compression audit at the specifiedlevel was started as a background server processhaving the process identifier reported.

System Action: Server operation continues. Thebackground audit attempts to identify client files thatmay be affected by the client compression problem.


ANR6202I Command name: Verifying candidatesfrom last audit.

Explanation: A compression audit has started to verifythe client file candidates that were identified in aprevious compression audit execution. The verificationprocess eliminates compression candidates that are nowfound to be expired by policy on the server.

System Action: The audit operation continues.


ANR6203I Command name: Starting level audit levelcompression audit from qualifyingentries in the candidates list.

Explanation: A compression audit is starting to checkqualifying candidates from the candidates list for theaudit level specified. Client files that were identified ascompression candidates at a lower level will be tested,subject to the qualifications that were specified for thecommand.


ANR5981I (S/390) • ANR6203I


User Response: The compression candidate list can bedisplayed with the QUERY COMPRESSION command.The QUERY PROCESS command can be used tomonitor the progress of the audit operation.

ANR6204I Command name: Process process ID, levelaudit level audit, ended successfully -compression suspects = total number ofcompression suspects.

Explanation: A compression audit ended and isreporting the total number of suspect client files thathave been found.

System Action: The audit operation completes.

User Response: The compression candidate list can bedisplayed with the QUERY COMPRESSION command.

ANR6205I Command name: Process process ID,continuing Level 1 compression auditwith object object ID high ordernumber.object ID low order number.

Explanation: A level 1 compression audit is starting toevaluate client files for signs that they may be affectedby the client compression problem. Since a previouslevel 1 audit has been executed, this audit will continuewhere the last audit stopped starting with the objectwhose identifier is specified.



ANR6206I Command name: Process process ID,starting base level 1 compression audit.

Explanation: A level 1 compression audit is starting toevaluate client files for signs that they may be affectedby the client compression problem. The audit startswith the first client file found on the server, even ifprevious level 1 audits have been executed.

System Action: The audit operation continues


ANR6207I Command name: Process process ID, levelaudit level analysis detected candidatefile high-level object name low-level objectname in file space client filespace name fornode client node name.

Explanation: A compression audit has found acandidate file at the audit level specified. The name ofthe client node, file space, and file are displayed. This

message is issued whenever a candidate file is detectedduring a compression audit that was started with theVERBOSE=YES parameter specified.



ANR6208I Command name: Process process ID, wascancelled - number of candidate filescandidate files were found in number offiles examined files examined prior tocancellation.

Explanation: A compression audit operation wascanceled with the CANCEL PROCESS command beforecompletion. The number of candidate files that werefound prior to the cancellation are displayed.

System Action: The audit operation ends.

User Response: The compression audit may berestarted with the AUDIT COMPRESSION command.The compression candidate list can be displayed withthe QUERY COMPRESSION command.

ANR6209I Command name: Process process ID, levelaudit level audit completed successfully -number of candidate files candidate fileswere found in number of files examinedfiles examined.

Explanation: A compression audit operationcompleted successfully. The number of candidate filesthat were found are displayed.



ANR6210I Command name: Process process ID, levelaudit level audit completed successfully -number of candidate files candidate fileswere found.

Explanation: A compression audit operationcompleted successfully. The number of candidate filesthat have been found are displayed.





ANR6211I Command name: Process process ID, levelaudit level analysis detected candidatefile object name in file space client filespacename for node client node name.

Explanation: A compression audit has found acandidate file at the audit level specified. The name ofthe client node, file space, and file are displayed. Thismessage is issued whenever a candidate file is detectedduring a compression audit that was started with theVERBOSE=YES parameter specified.



ANR6212I Command name: Process process ID, levelaudit level analysis eliminated levelcandidate level candidate file object namein filespace client filespace name for nodeclient node name from candidate status.

Explanation: A compression audit at the levelspecified has eliminated a candidate file throughfurther analysis. The name of the client node, file space,and file are displayed. This message is issued whenevera candidate file is eliminated from consideration duringa compression audit that was started with theVERBOSE=YES parameter specified.



ANR6213I Command name: Process process ID, wascancelled - number of files promotedcandidate files were promoted ascandidates at level audit level, number offiles eliminated files were eliminated ascandidates, and number of files expiredcandidates were eliminated because theywere found to be expired on the server.

Explanation: A compression audit operation wascancelled with the CANCEL PROCESS commandbefore completion. The number of candidate files thatwere promoted as candidates at this level of audit,eliminated as candidates at this level of audit, andfound to be expired before the cancellation arereported.


User Response: The compression audit can berestarted with the AUDIT COMPRESSION command.The compression candidate list can be displayed withthe QUERY COMPRESSION command.

ANR6214I Command name: Process process ID,completed successfully - number of filespromoted candidate files were promotedas candidates at level audit level, numberof files eliminated files were eliminated ascandidates, and number of files expiredcandidates were eliminated because theywere found to be expired on the server.

Explanation: A compression audit operationcompleted successfully. The number of candidate filesthat were promoted as candidates at this level of audit,eliminated as candidates at this level of audit, andfound to be expired are reported.



ANR6215I Command name: Backup for file high-levelobject name low-level object name infilespace client filespace name for nodeclient node name could not be forced.

Explanation: It is not possible to force a backup forthe specified file using the FORCE BACKUP command.This file was either backed up using an API client or byan ADSM version 2 client or higher.

System Action: The force backup operation continues,the state of the compression record for this file isupdated.

User Response: If the file was backed up using aVersion 2 client, or higher, you may remove this entryas a candidate, using the REMOVE COMPRESSIONcommand. If the file was backed up using an APIclient, notify the client owner to again back this file up.Do not remove this entry until it becomes an ″inactive″entry.

ANR6220I Delete compression operation started asprocess process ID.

Explanation: A compression deletion operation wasstarted as a background server process with theindicated identifier.



ANR6221I Force backup operation started asprocess process ID.

Explanation: A force backup operation was started asa background server process with the indicatedidentifier.





ANR6222I Command name: Process process ID wascancelled - number of files files wereprocessed prior to cancellation.

Explanation: The indicated process was cancelledprior to completion. This message displays theindicated number of files that were processed beforethe operation was cancelled.

System Action: The process ends.

User Response: The operation may be restarted byreissuing the indicated command.

ANR6223I Delete compression process process IDhas completed - number of files files weredeleted.

Explanation: The indicated process has completedprocessing. All database references have been deletedfor the indicated number of files.



ANR6224I Force backup process process ID hascompleted - number of files files weremarked for forced backup.

Explanation: The indicated process has completedprocessing. The indicated number of files have beenmarked for forced backup. These files will be backedup during the next incremental backup.



ANR6225I File identifier removed as a suspect forcompression errors.

Explanation: The file with the specified identifier hasbeen removed from the database informationconcerning files with possible compression errors.Other database information concerning the file is notaffected.



ANR6226I Command name: Started as backgroundprocess process ID.

Explanation: A compression cleanup operation hasbeen started to remove compression candidateinformation and temporary database entries from theserver database. Client files are not affected by thisoperation.


User Response: The CANCEL PROCESS commandcan be used to cancel the compression cleanup

operation. The QUERY PROCESS command may beused to query the status of the operation.

ANR6227I cleanup process name operation starting asprocess process ID.

Explanation: A compression cleanup operation hasbeen started to remove compression candidateinformation and temporary database entries from theserver database. Client files are not affected by thisoperation.


User Response: The CANCEL PROCESS commandcan be used to cancel the compression cleanupoperation. The QUERY PROCESS command may beused to query the status of the operation.

ANR6228W Cleanup process name: Process process IDhas been cancelled - cleanup processingis incomplete.

Explanation: A compression cleanup operation hasbeen cancelled prior to successful completion.


User Response: The CLEANUP COMPRESSIONcommand can be used to restart the cleanup operation.

ANR6229I Cleanup process name: Process process IDcompleted successfully.

Explanation: A compression cleanup operation hassuccessfully completed.

System Action: The cleanup process ends.


ANR6300E Command name: Insufficient servermemory available for the operation.

Explanation: A compression testing routine cannotcontinue because sufficient memory is not available onthe server.


User Response: Increase the memory available to theserver by increasing the server region size, virtualmachine size, paging space available on the system, orrelocating the memory swap file, depending upon theplatform on which the server is executing. Additionalmemory may also be made available by limiting serveractivity (sessions, migration, and other activities) whilethis operation is processing.



ANR6301E Command name: Invalid LEVEL specified.This command only supports a value of1 or 2 for the LEVEL parameter.

Explanation: An invalid LEVEL= parameter has beenspecified for the command.


User Response: Reissue the command specifying avalue of 1 or 2 for the LEVEL parameter.

ANR6302E Command name: Process process ID, failed- number of candidate files candidate fileswere found in number of files examinedfiles examined prior to failure.

Explanation: A compression audit operation failedbefore completion. The number of candidate files thatwere found prior to the failure are displayed.


User Response: Examine message that appear beforethis message on the server console or in the activity logto determine the source of the failure. If the error canbe corrected, re-execute the compression audit. If thefailure cannot be determined or corrected, contact yourservice representative. The compression candidate listcan be displayed with the QUERY COMPRESSIONcommand.

ANR6303E Command name: Process process ID, failed- number of files promoted candidate fileswere promoted as candidates at levelaudit level, number of files eliminated fileswere eliminated as candidates, andnumber of files expired candidates wereeliminated because they were found tobe expired on the server.

Explanation: A compression audit operation failedbefore completion. The number of candidate files thatwere promoted as candidates at this level of audit,eliminated as candidates at this level of audit, andfound to be expired before the audit failure arereported.


User Response: Examine message that appear beforethis message on the server console or in the activity logto determine the source of the failure. If the error canbe corrected, re-execute the compression audit. If thefailure cannot be determined or corrected, contact yourservice representative. The compression candidate listcan be displayed with the QUERY COMPRESSIONcommand.

ANR6304E Command name: Command cannot beprocessed until compression audit isperformed.

Explanation: The indicated command cannot beprocessed until a compression audit is performed usingthe AUDIT COMPRESSION command.


User Response: Issue the AUDIT COMPRESSIONcommand and then repeat the attempted operation.

ANR6305E Command name: File identifier is not asuspect for compression errors.

Explanation: The file with the specified identifier isnot listed in the database as a suspect for compressionerrors. The file cannot be removed from the suspect list.


User Response: Use the QUERY COMPRESSIONcommand to obtain the correct identifier for the file tobe removed.

ANR6306E Cleanup process name: Process process IDfailed due to server error - cleanupprocessing is incomplete.

Explanation: A compression cleanup operation hasfailed before successful completion.

System Action: The cleanup process ends.

User Response: Examine messages that appear on theserver console or in the server activity log prior to thismessage to determine the cause of the error. If the errorcan be identified and corrected, restart the cleanupoperation with the CLEANUP COMPRESSIONcommand. If the error cannot be corrected, contact yourservice representative.

ANR6600E Command: Invalid machine name -machine name.

Explanation: The machine name specified in thecommand is invalid.


User Response: Issue the command again and specifya valid machine name.

ANR6601E Command: Description informationexceeds maximum length characters.

Explanation: The description specified in thecommand exceeds the maximum length of allowablecharacters.




User Response: Issue the command again and specifya valid description.

ANR6602E Command: Recovery instructions filename exceeds maximum length characters.

Explanation: The recovery instructions file namespecified in the command exceeds the maximum lengthof allowable characters.


User Response: Issue the command again and specifya valid recovery instructions file name.

ANR6603E Command: Characteristics file nameexceeds maximum length characters.

Explanation: The characteristics file name specified inthe command exceeds the maximum length ofallowable characters.


User Response: Issue the command again and specifya valid characteristics file name.

ANR6604E Command: Invalid building identifier -building.

Explanation: The building identifier specified in thecommand is invalid.


User Response: Issue the command again and specifya valid building identifier.

ANR6605E Command: Invalid floor identifier - floor.

Explanation: The floor identifier specified in thecommand is invalid.


User Response: Issue the command again and specifya valid floor identifier.

ANR6606E Command: Invalid room identifier - room.

Explanation: The room identifier specified in thecommand is invalid.


User Response: Issue the command again and specifya valid room identifier.

ANR6607E Command: Machine machine name isalready defined.

Explanation: The machine specified in the commandis already defined to the server.


User Response: Issue the command again and specifyanother machine.

ANR6608E Command: A machine containing a serveris already defined.

Explanation: The ADSMSERVER=YES parameterspecified in the command is invalid because anothermachine has already been defined with this parameter.Only one machine can be defined to the server ascontaining a server.


User Response: Issue the command again and do notspecify ADSMSERVER=YES as a parameter.

ANR6609I Machine machine name defined.

Explanation: A DEFINE MACHINE command hasadded the requested machine to the server.



ANR6610E Command: Invalid recovery media name -recovery media name.

Explanation: The recovery media name specified inthe command is invalid.


User Response: Issue the command again and specifya valid recovery media name.

ANR6611E Command: Location information exceedsmaximum length characters.

Explanation: The location specified in the commandexceeds the maximum length of allowable characters.


User Response: Issue the command again and specifya valid location.



ANR6612I Machine machine name updated.

Explanation: An UPDATE MACHINE command hasupdated one or more attributes of a machine.



ANR6613I Machine machine name deleted.

Explanation: A DELETE MACHINE command hasdeleted the requested machine from the server.



ANR6614E Command: Machine machine name is notdefined.

Explanation: The machine specified in the commandis not defined to the server.


User Response: Issue the command again and specifya valid machine.

ANR6615E Command: Failed to open input file - filename.

Explanation: The input file specified in the commandcannot be opened by the server.


User Response: Issue the command again and specifyan input file that is in a file system accessible by theserver.

ANR6616E Command: Invalid sequence number -sequence number.

Explanation: The sequence number specified in thecommand is invalid.


User Response: Issue the command again and specifya valid sequence number.

ANR6617W Command: Node node name cannot beprocessed because it is not registered.

Explanation: The node indicated in the messagecannot be processed because it is not registered.

System Action: The indicated node is not processed,but another node can be processed if specified by thiscommand.

User Response: Issue the command again and specifya valid registered node.

ANR6618E Command: No matching node registered.

Explanation: The node specified in the command doesnot match any node registered to the server.


User Response: Issue the command again and specifya valid node.

ANR6619I Node node name associated with machinemachine name.

Explanation: A DEFINE MACHNODEASSOCIATIONcommand has associated the specified node with thespecified machine. The node node name is associatedwith the machine machine name.



ANR6620E Command: Machine and node associationis already defined.

Explanation: The machine and node associationspecified in the command is already defined to theserver.

System Action: The server operation continues, butthe command has no effect.

User Response: Issue the command again and specifya valid node.

ANR6621I Node node name disassociated frommachine machine name.

Explanation: A DELETE MACHNODEASSOCIATIONcommand has deleted the requested association fromthe server. The node node name is not associated withthe machine machine name.



ANR6622E Command: Recovery media recovery medianame is not defined.

Explanation: The recovery media specified in thecommand is not defined to the server.


User Response: Issue the command again and specifya valid recovery media.



ANR6623W Command: Machine machine name cannotbe processed because it is not defined.

Explanation: The machine indicated in the message isnot defined to the server.

System Action: The indicated machine is notprocessed, but another machine can be processed ifspecified by this command.


ANR6624E Command: No matching machinedefined.

Explanation: The machine specified in the commanddoes not match any machine defined to the server.



ANR6625I Machine machine name associated withrecovery media recovery media name.

Explanation: A DEFINERECOVERYMEDIAMACHASSOCIATION commandhas associated the specified machine with the specifiedrecovery media. The machine machine name isassociated with the recovery media recovery media name.



ANR6626E Command: Recovery media/machineassociation is already defined.

Explanation: The recovery media/machine associationspecified in the command is already defined to theserver.



ANR6627I Machine machine name disassociatedfrom recovery media recovery media name.

Explanation: A DELETERECOVERYMEDIAMACHASSOCIATION commandhas deleted the requested association from the server.Machine machine name is not associated with therecovery media recovery media name.



ANR6628E Command: Volume list exceeds maximumlength characters.

Explanation: The volume list specified in thecommand exceeds the maximum length of allowablecharacters.


User Response: Issue the command again and specifya valid volume list.

ANR6629E Command: Product name exceedsmaximum length characters.

Explanation: The product name specified in thecommand exceeds the maximum length of allowablecharacters.


User Response: Issue the command again and specifya valid product name.

ANR6630E Command: Product information exceedsmaximum length characters.

Explanation: The product information specified in thecommand exceeds the maximum length of allowablecharacters.


User Response: Issue the command again and specifyvalid product information.

ANR6631E Command: Missing volume list for bootrecovery media.

Explanation: Boot recovery media cannot be definedto the server without specifying a volume list.


User Response: Issue the command again and specifythe volume list for the boot recovery media.

ANR6632I Recovery media recovery media namedefined.

Explanation: A DEFINE RECOVERYMEDIA commandhas defined the recovery media to the server.





ANR6633I Recovery media recovery media nameupdated.

Explanation: An UPDATE RECOVERYMEDIAcommand has updated one or more attributes of therecovery media.



ANR6634I Recovery media recovery media namedeleted.

Explanation: A DELETE RECOVERYMEDIAcommand has deleted the requested recovery mediafrom the server.



ANR6635E Command: Recovery media recovery medianame is already defined.

Explanation: The recovery media specified in thecommand is already defined to the server.


User Response: Issue the command again and specifya different recovery media.

ANR6636E Command: The characteristics specifiedfor machine machine name exceedsmaximum length characters.

Explanation: The characteristics specified in thecommand exceeds the maximum length of allowablecharacters.


User Response: Issue the command again and specifyvalid characteristics.

ANR6637E Command: The recovery instructionsspecified for machine machine nameexceeds maximum length characters.

Explanation: The recovery instructions specified in thecommand exceeds the maximum length of allowablecharacters.


User Response: Issue the command again and specifyvalid recovery instructions.

ANR6638E Command: The characteristics formachine machine name are alreadydefined.

Explanation: The characteristics for the machinespecified in the command are already defined to theserver.


User Response: If the specified machine is defined tothe server, issue an UPDATE MACHINE command toupdate the existing characteristics. If the machine is notdefined to the server, run AUDIT DRM FIX to deletethe characteristics.

ANR6639E Command: The recovery instructions formachine machine name are alreadydefined.

Explanation: The recovery instructions for themachine specified in the command are already definedto the server.


User Response: If the specified machine is defined tothe server, issue an UPDATE MACHINE command toupdate the existing recovery instructions. If themachine is not defined to the server, run AUDIT DRMFIX to delete the recovery instructions.

ANR6640E Command: Cannot delete volume list forboot recovery media.

Explanation: A volume list cannot be deleted for bootrecovery media. A volume list must exist for each bootrecovery media defined to the server.


User Response: To delete the volume list, issue anUPDATE RECOVERYMEDIA command and specify arecovery media type of OTHER and VOLUMES=″″. Tochange the recovery media type to BOOT, issue anUPDATE RECOVERYMEDIA command and specify thevolume list containing the boot recovery media andTYPE=BOOT.

ANR6641E Command: No association found formachine and node pair specified.

Explanation: No association found for the machineand node pair specified in the command.


User Response: Issue the command again and specifya valid machine and node pair.



ANR6642E Command: No association found forrecovery media and machine pairspecified.

Explanation: No association found for the recoverymedia and machine pair specified in the command.


User Response: Issue the command again and specifya valid recovery media and machine pair.

ANR6643E Command: Invalid parameter value -parameter value.

Explanation: The parameter issued in the command isinvalid.


User Response: Issue the command again and specifya valid parameter.

ANR6644E Command: A character string must bespecified.

Explanation: The INSERT command is invalid. Acharacter string must be specified.


User Response: Issue the command again and specifya valid character string.

ANR6645W Node node name has already beenassociated with machine machine name.

Explanation: The node specified in the DEFINEMACHNODEASSOCIATION command is invalid. Thenode is already associated with another machine shownin the message. A node can only be associated with onemachine.

System Action: The indicated node is not processed,but another node can be processed if specified by thecommand.

User Response: Issue the command again and specifya valid node name.

ANR6646I Audit command: Auditing disasterrecovery manager definitions.

Explanation: This message is displayed during adatabase audit and indicates that the disaster recoverymanager definitions are being examined by thedatabase audit process.



ANR6647E Audit command: DRM global attributesare missing.

Explanation: A database audit process finds that theglobal attributes used for server DRM activities aremissing.


User Response: Issue the command again and specifyFIX=YES to recreate the DRM global attributes.

ANR6648I Audit command: DRM global attributesare missing - default values will be usedto recreate the attributes.

Explanation: A database audit process finds that theglobal attributes used for server DRM activities aremissing. Because FIX=YES has been specified on theAUDIT command, default attribute values will be usedto recreate the administrative global attributes.



ANR6649E Audit command: DRM machine IDassignments are incorrect.

Explanation: A database audit process finds that theglobal attributes machine ID used for server DRMactivities are incorrect.


User Response: Reissue the audit command withFIX=YES specified so that the DRM global attributescan be corrected.

ANR6650I Audit command: DRM machine IDAssignments are incorrect - values willbe corrected.

Explanation: A database audit process finds that theglobal attributes machine ID used for server DRMactivities are incorrect. Since FIX=YES has beenspecified on the AUDIT command, the attribute valuewill be corrected in the server database.


User Response: None

ANR6651I Audit command: Invalid priority valueencountered for machine machine name.

Explanation: A database audit process encounters aninvalid priority value for the machine indicated.


User Response: Issue the command again and specifyFIX=YES to correct the priority. Or, issue an UPDATEMACHINE command and specify a new priority value.



ANR6652I Audit command: Invalid priority valueencountered for machine machine name -the default value will be set.

Explanation: A database audit process encounters aninvalid machine priority value for the machineindicated. Because FIX=YES has been specified, theaudit function sets the machine priority value to thedefault value.


User Response: To override the default value, issue anUPDATE MACHINE command to change the valueafter the audit command has completed.

ANR6653I Audit command: Invalid building valueencountered for machine machine name.

Explanation: A database audit process encounters aninvalid building value for the machine indicated.


User Response: Issue the command again and specifyFIX=YES to correct the building value. Or, issue anUPDATE MACHINE command and specify a newbuilding value.

ANR6654I Audit command: Invalid building valueencountered for machine machine name -the building value will be removed.

Explanation: A database audit process encounters aninvalid building value for the machine indicated.Because FIX=YES has been specified, the audit functionremoves the machine building value.


User Response: To set the building value to anothervalue, issue an UPDATE MACHINE command after theaudit command has completed.

ANR6655I Audit command: Invalid floor valueencountered for machine machine name.

Explanation: A database audit process encounters aninvalid floor value for the machine indicated.


User Response: Issue the command again and specifyFIX=YES to correct the floor value. Or, issue anUPDATE MACHINE command and specify a new floorvalue.

ANR6656I Audit command: Invalid floor valueencountered for machine machine name -the floor value will be removed.

Explanation: A database audit process encounters aninvalid floor value for the machine indicated. Because

FIX=YES has been specified, the audit function removesthe machine floor value.


User Response: To set the floor value to anothervalue, issue an UPDATE MACHINE command after theaudit command has completed.

ANR6657I Audit command: Invalid room valueencountered for machine machine name.

Explanation: A database audit process encounters aninvalid room value for the machine indicated.


User Response: Issue the command again and specifyFIX=YES to correct the room value. Or, issue anUPDATE MACHINE command and specify a newroom value.

ANR6658I Audit command: Invalid room valueencountered for machine machine name -the room value will be removed.

Explanation: A database audit process encounters aninvalid room value for the machine indicated. BecauseFIX=YES has been specified, the audit function removesthe machine room value.


User Response: To set the room value for the specifiedmachine to another value, use the UPDATE MACHINEcommand after the audit command has completed.

ANR6659I Audit command: Invalid server valueencountered for machine machine name.

Explanation: A database audit process encounters aninvalid server value for the machine indicated.


User Response: Issue the command again and specifyFIX=YES to correct the server value. Or, issue anUPDATE MACHINE command and specify a newserver value.

ANR6660I Audit command: Invalid server valueencountered for machine machine name -the default value will be set.

Explanation: A database audit process encounters aninvalid server value for the machine indicated. BecauseFIX=YES has been specified, the audit function sets themachine server value to the default value.


User Response: To override the default value, issue anUPDATE MACHINE command to change the valueafter the audit command has completed.



ANR6661I Audit command: Multiple machines areindicated as servers. Only one machineshould have the server indicator set toYES.

Explanation: A database audit process encountersmore than one machine with the server indicator set toYES.


User Response: For a list of machines with the serverindicator set to YES, issue a QUERY MACHINEADSMSERVER=YES command. Issue an UPDATEMACHINE command for each machine that is not aserver.

ANR6662I Audit command: Characteristics formachine machine name not found.

Explanation: A database audit process finds acharacteristics reference from a machine forcharacteristics that are not in the server database.


User Response: Issue an UPDATE MACHINEcommand to load the characteristics into the databaseafter the audit command has completed.

ANR6663I Audit command: Recovery instructions formachine machine name not found.

Explanation: A database audit process finds arecovery instructions reference from a machine forrecovery instructions that are not in the serverdatabase.


User Response: Issue an UPDATE MACHINEcommand to load the recovery instructions into thedatabase after the audit command has completed.

ANR6664I Audit command: Invalid access valueencountered for recovery media recoverymedia name.

Explanation: A database audit process encounters aninvalid access value for the recovery media indicated.


User Response: Issue the command again and specifyFIX=YES to correct the access value. Or, issue anUPDATE RECOVERYMEDIA command and specify anew access value.

ANR6665I Audit command: Invalid access valueencountered for recovery media recoverymedia name - the default value will beset.

Explanation: A database audit process encounters aninvalid access value for the recovery media indicated.Because FIX=YES has been specified, the audit functionsets the recovery media access value to the defaultvalue.


User Response: To override the default value, issue anUPDATE RECOVERYMEDIA command to change thevalue after the audit command has completed.

ANR6666I Audit command: Invalid type valueencountered for recovery media recoverymedia name.

Explanation: A database audit process encounters aninvalid type value for the recovery media indicated.


User Response: Issue the command again and specifyFIX=YES to correct the type value. Or, issue anUPDATE RECOVERYMEDIA command and specify anew type value.

ANR6667I Audit command: Invalid type valueencountered for recovery media recoverymedia name - the default value will beset.

Explanation: A database audit process encounters aninvalid type value for the recovery media indicated.Because FIX=YES has been specified, the audit functionsets the recovery media type value to the default value.


User Response: To override the default value, issue anUPDATE RECOVERYMEDIA command to change thevalue after the audit command has completed.

ANR6668E Audit command: Machine is not found forinternal machine ID machine ID, whichis referenced by recovery media.

Explanation: A database audit process finds recoverymedia that references a machine that is not defined inthe server database.


User Response: Issue the command again and specifyFIX=YES to correct recovery media attributes.



ANR6669I Audit command: Machine is not found forinternal machine ID machine ID, whichis referenced by recovery media - themachine reference will be deleted.

Explanation: A database audit process finds recoverymedia that references a machine that is not defined inthe server database. Because FIX=YES has beenspecified for the audit command, the reference will beremoved from the server database.



ANR6670E Audit command: Recovery media notfound for internal recovery media IDrecovery media ID, which is referenced bya machine.

Explanation: A database audit process finds a machinethat references recovery media that is not defined in theserver database.


User Response: Issue the command again and specifyFIX=YES to correct the recovery media attributes.

ANR6671I Audit command: Recovery media notfound for internal recovery media IDrecovery media ID, which is referenced bya machine - the recovery mediareference will be deleted.

Explanation: A database audit process finds mmachine that references recovery media that is notdefined in the server database. Because FIX=YES hasbeen specified for the audit command, the referencewill be deleted from the server database.



ANR6672E Audit command: Client node not foundfor internal node ID node ID, which isreferenced by a machine.

Explanation: A database audit process finds a machinethat references a client node that is not defined in theserver database.


User Response: Issue the command again and specifyFIX=YES to correct the machine attributes.

ANR6673I Audit command: Client node not foundfor internal node ID node ID, which isreferenced by a machine - the clientnode reference will be deleted.

Explanation: A database audit process finds a machinethat references a client node that is not defined in theserver database. Because FIX=YES has been specifiedfor the audit command, the reference will be removedfrom the server database.



ANR6674E Audit command: Machine not found forinternal machine ID machine ID, whichis referenced by a client node.

Explanation: A database audit process finds a clientnode that references a machine that is not defined inthe server database.



ANR6675I Audit command: Machine not found forinternal machine ID machine ID, whichis referenced by a client node - themachine reference will be deleted.

Explanation: A database audit process finds a clientnode that references a machine that is not defined inthe server database. Because FIX=YES has beenspecified for the audit command, the reference will beremoved from the server database.



ANR6676E Audit command: Machine not found forinternal machine ID machine ID, whichis referenced by characteristics.

Explanation: A database audit process findscharacteristics that reference a machine that is notdefined in the server database.



ANR6677I Audit command: Machine not found forinternal machine ID machine ID, whichis referenced by characteristics - themachine reference will be deleted.

Explanation: A database audit process findscharacteristics that reference a machine that is notdefined in the server database. Because FIX=YES has



been specified for the audit command, the referencewill be removed from the server database.



ANR6678E Audit command: Machine not found forinternal machine ID machine ID, whichis referenced by recovery instructions.

Explanation: A database audit process finds recoveryinstructions that reference a machine that is not definedin the server database.



ANR6679I Audit command: Machine not found forinternal machine ID machine ID, whichis referenced by recovery instructions -the machine reference will be deleted.

Explanation: A database audit process finds recoveryinstructions that reference a machine that is not definedin the server database. Because FIX=YES has beenspecified for the audit command, the reference will beremoved from the server database.



ANR6680E Audit command: Missing or invalidinternal database attribute encounteredfor machine machine name.

Explanation: A database audit process finds an invalidattribute for the specified machine.



ANR6681I Audit command: Missing or invalidinternal database attribute encounteredfor machine machine name - the attributewill be corrected.

Explanation: A database audit process finds an invalidattribute for the specified machine. Because FIX=YEShas been specified for the audit command the invalidattribute will be corrected.



ANR6682I Command command ended: number ofvolumes volumes processed.

Explanation: The indicated command ended. The totalnumber of volumes successfully processed is shown inthe message.

System Action: The indicated command ends.


ANR6683I Command: Volume volume name wasmoved from from state state to to state.

Explanation: Volume volume name is successfullymoved from state1 to state2 by the indicated command.

System Action: The indicated volume is moved to thedestination state.


ANR6684I Command: Volume volume name wasdeleted.

Explanation: The MOVE DRMEDIA *WHERESTATE=COURIERRETRIEVE commanddisplays the message. Volume volume name is deletedfrom the server database. For database backup volume,after its expiration days have elapsed, the volumehistory record is deleted when it is returned onsite. Foran empty scratch copy storage pool volume, thevolume record is deleted when it is returned onsite.

System Action: The volume record is deleted from theserver database.

User Response: Issue the CHECKIN LIBVOLUMEcommand for each volume returned onsite if thevolume is reused by the server.

ANR6685E Command: Volume volume name notdefined.

Explanation: Volume volume name is not defined to theserver.

System Action: The indicated command is notprocessed if the volume name is explicitly specified onthe command. If a volume pattern is specified on thecommand, the volume shown is not processed, but theother volumes are processed.

User Response: Reissue the command specifying avalid volume name.

ANR6686E Command: Volume volume name in use.

Explanation: The MOVE DRMEDIA *WHERESTATE=MOUNTABLE command displays themessage. Volume volume name is used for anotheroperation.

System Action: The command is not processed if thevolume is explicitly specified on the command. If a



volume pattern is specified on the command, theindicated volume is not processed, but the othervolumes are processed.

User Response: Wait until the conflicting volumeactivity has completed, and then reissue the command.If the volume is currently mounted, but idle, dismountthe volume by using a DISMOUNT VOLUMEcommand and then retry this operation.

ANR6687E Command: Executable command stringexceeds maximum length characters.

Explanation: The length of the executable commandstring specified with the CMD parameter exceeds themaximum length of allowable characters (255).

System Action: The server stops processing thecommand.

User Response: Issue the command again and specifya valid executable command with the CMD parameter.

ANR6688E command: The specified command failedbecause the entry/exit port of librarylibrary name is full. Please remove thevolume(s) from the entry/exit port andre-issue the command name command.

Explanation: The indicated operation has failedbecause the entry/exit port of the specified library isfull.


User Response: Remove the volume(s) from theentry/exit port and re-issue the command to processany remaining eligible volumes.

ANR6690E Command: Copy storage pool cstgp namenot defined for Offsite Recovery Media.

Explanation: The MOVE DRMEDIA or QUERYDRMEDIA command displays the message. Theindicated command was issued with a copy storagepool name specified, but the specified pool name is notdefined to DRM for Offsite Recovery Media.

System Action: The indicated command is notprocessed.

User Response: Reissue the command, after definingthe specified copy storage pool to DRM for OffsiteRecovery Media.

ANR6691E Command: No match is found for thismove.

Explanation: The indicated command was issued, butno matching volumes are defined to the server or thevolume specified is not managed by the command.


User Response: Reissue the command specifying thevalid volume.

ANR6694E Command: The ORM state state is invalidfor a volume with access mode accessmode.

Explanation: The indicated command specifies anOffsite Recovery Media state that is invalid for avolume with the access mode shown. SpecifyCOURIER or COURIERRETRIEVE for a volume thathas access mode of OFFSITE.


User Response: Reissue the command specifyingCOURIER or COURIERRETRIEVE as the state for avolume that has access mode of OFFSITE.

ANR6695E Command: Device class device class namenot defined for volume volume name.

Explanation: The MOVE DRMEDIA or QUERYDRMEDIA command displays the message. Thevolume being processed has associated with the deviceclass name shown that is not defined to the server.

System Action: The command is not processed if thevolume is explicitly specified on the command. If avolume pattern is specified on the command, theindicated volume is not processed, but the othervolumes not associated with the indicated class areprocessed.

User Response: Reissue the command after theindicated device class is defined to the server.

ANR6696I command: operation for volume volumename in library library name starting.

Explanation: The indicated operation is being startedfor the volume shown in the given library.

System Action: The server starts the operation inresponse to the indicated command entered by anadministrator.

User Response: For SCSI library users, remove thevolume from the slot and issue a REPLY command,along with the request ID, to tell the server the volumewas removed from the library.

ANR6697I command: operation for volume volumename in library library name completedsuccessfully.

Explanation: The indicated operation has completedsuccessfully for the volume shown in the given library.

System Action: The volume is either deleted from thelibrary inventory (if its status is something other thanDATA) or marked not present (if its status is DATA).




ANR6698E command: operation for volume volumename in library library name failed.

Explanation: The indicated operation has failed for thevolume shown in the given library. This messageshould be preceded by another error message whichprovides more detail about the error.

System Action: The volume is not processed.

User Response: Check for additional message andeliminate the condition that caused the failure, thenretry the command.

ANR6699I Cancel in progress.

Explanation: The MOVE DRMEDIA command hasbeen canceled and will end when resources have beenfreed for the background process. This message may bedisplayed in response to a QUERY PROCESS commandfor a MOVE DRMEDIA command.



ANR6700I Command command completedsuccessfully.

Explanation: The indicated command completedsuccessfully.



ANR6701E Command: Invalid courier name - couriername.

Explanation: The indicated command has beenentered with an invalid courier name.


User Response: Reissue the command with a validcourier name.

ANR6702E Command: Invalid expiration days value- days value.

Explanation: The indicated command has beenentered that specifies an invalid expiration days value.


User Response: Reissue the command with a validexpiration days value.

ANR6703E Command: Invalid recovery plan prefix -prefix.

Explanation: The indicated command has beenentered with an invalid recovery plan prefix.


User Response: Reissue the command with a validrecovery plan prefix.

ANR6704E Command: Invalid plan instructionsprefix - prefix.

Explanation: The indicated command has beenentered with an invalid plan instructions prefix.


User Response: Reissue the command with a validplan instructions prefix.

ANR6705E Command: Invalid character for volumepostfix - postfix character.

Explanation: The indicated command has beenentered with an invalid character that is to be added tothe volumes names in the recovery plan file.


User Response: Reissue the command with a validcharacter.

ANR6706E Command: Invalid vault name - vaultname.

Explanation: The indicated command has beenentered with an invalid vault name.


User Response: Reissue the command with a validvault name.

ANR6711E Audit command: An invalid databasebackup series expiration daysencountered.

Explanation: A database audit process encounters aninvalid value for database backup series expirationdays.


User Response: Issue the command again and specifyFIX=YES to correct the expiration days. Or, issue anSET DRMDBBACKUPEXPIREDAYS command andspecify a new expiration days value.



ANR6712I Audit command: An invalid databasebackup series expiration daysencountered - the default value will beset.

Explanation: A database audit process encounters aninvalid value for database backup series expirationdays. Because FIX=YES has been specified, the auditfunction sets the expiration days value to the defaultvalue.


User Response: To override the default value, issue aSET DRMDBBACKUPEXPIREDAYS command tochange the value after the audit command hascompleted.

ANR6713E Audit command: An invalid check labelvalue encountered.

Explanation: A database audit process encounters aninvalid check label value.


User Response: Issue the command again and specifyFIX=YES to correct the check label value. Or, issue aSET DRMCHECKLABEL command and specify a newcheck label value.

ANR6714I Audit command: An invalid check labelvalue encountered - the default valuewill be set.

Explanation: A database audit process encounters aninvalid check label value. Because FIX=YES has beenspecified, the audit function sets the check label valueto the default value.


User Response: To override the default value, issue aSET DRMCHECKLABEL command to change the valueafter the audit command has completed.

ANR6715E Audit command: An invalid file processvalue encountered.

Explanation: A database audit process encounters aninvalid file process value.


User Response: Issue the command again and specifyFIX=YES to correct the file process value. Or, issue aSET DRMFILEPROCESS command and specify a newfile process value.

ANR6716I Audit command: An invalid file processvalue encountered - the default valuewill be set.

Explanation: A database audit process encounters aninvalid file process value. Because FIX=YES has beenspecified, the audit function sets the file process valueto the default value.


User Response: To override the default value, issue aSET DRMFILEPROCESS command to change the valueafter the audit command has completed.

ANR6717E Audit command: Extraneous DRM globalattribute encountered.

Explanation: A database audit process finds anonexistent DRM global attribute.


User Response: Issue the command again and specifyFIX=YES to delete the extraneous attribute.

ANR6718I Audit command: Extraneous DRM globalattribute encountered - the attribute willbe deleted.

Explanation: A database audit process finds anonexistent DRM global attribute. Since FIX=YES hasbeen specified, the extraneous attribute will be deleted.



ANR6719E Audit command: DRM machine IDassignments not found.

Explanation: A database audit process finds no entriesin server database for DRM internal machine IDassignments.


User Response: Issue the command again and specifyFIX=YES to correct the error.

ANR6720I Audit command: DRM machine IDassignments not found - entry will becreated.

Explanation: A database audit process finds no entriesin server database for DRM internal machine IDassignments. Because FIX=YES has been specified forthe audit command, the audit function creates an entryin the server database for the machine ID assignments.





ANR6721E Audit command: DRM recovery media IDassignments not found.

Explanation: A database audit process finds no entriesin server database for DRM internal recovery media IDassignments.


User Response: Issue the command again and specifyFIX=YES to correct the error.

ANR6722I Audit command: DRM recovery media IDassignments not found - entry will becreated.

Explanation: A database audit process finds no entriesin server database for DRM internal recovery media IDassignments. Because FIX=YES has been specified forthe audit command, the audit function creates an entryin the server database for the recovery media IDassignments.



ANR6723E Audit command: Prefix for DRM recoveryplan not found.

Explanation: A database audit process finds no entriesin server database for DRM recovery plan prefixdefinitions.


User Response: Issue the audit command again andspecify FIX=YES to correct the error.

ANR6724I Audit command: Prefix for DRM recoveryplan not found - entry will be created.

Explanation: A database audit process finds no entriesin server database for DRM recovery plan prefixdefinitions. Because FIX=YES has been specified for theaudit command, the audit function creates an entryusing the default value in the server database for therecovery plan file prefix.


User Response: To override the default value, issue aSET DRMPLANFILEPREFIX command to change thevalue after the audit command has completed.

ANR6725E Audit command: Prefix for DRM recoveryplan instructions not found.

Explanation: A database audit process finds no entriesin server database for DRM recovery plan instructionsprefix definitions.


User Response: Issue the audit command again and

specify FIX=YES to correct the error.

ANR6726I Audit command: Prefix for DRM recoveryplan instructions not found - entry willbe created.

Explanation: A database audit process finds no entriesin server database for DRM recovery plan instructionsprefix definitions. Because FIX=YES has been specifiedfor the audit command, the audit function creates anentry using the default value in the server database forthe recovery plan instructions file prefix.


User Response: To override the default value, issue aSET DRMPLANINSTRPREFIX command to change thevalue after the audit command has completed.

ANR6727E Audit command: Postfix for DRMreplacement volumes names not found.

Explanation: A database audit process finds no entriesin server database for DRM postfix definitions forreplacement volumes names.



ANR6728I Audit command: Postfix for DRMreplacement volumes names not found -entry will be created.

Explanation: A database audit process finds no entriesin server database for DRM postfix definitions forreplacement volumes names. Because FIX=YES hasbeen specified for the audit command, the auditfunction creates an entry using the default value in theserver database for the replacement volumes postfix.


User Response: To override the default value, issue aSET DRMPLANVPOSTFIX command to change thevalue after the audit command has completed.

ANR6729E Audit command: Primary storage pools tobe restored by DRM not found.

Explanation: A database audit process finds no entriesin server database for primary storage pools to berestored by DRM.





ANR6730I Audit command: Primary storage pools tobe restored by DRM not found - entrywill be created.

Explanation: A database audit process finds no entriesin server database for primary storage pools to berestored by DRM. Because FIX=YES has been specifiedfor the audit command, the audit function creates anentry using the default value in the server database forthe primary storage pools to be restored by DRM.


User Response: To override the default value, issue aSET DRMPRIMSTGPOOL command to change thevalue after the audit command has completed.

ANR6731E Audit command: Copy storage pools to bemanaged by DRM not found.

Explanation: A database audit process finds no entriesin server database for copy storage pools to bemanaged by DRM.



ANR6732I Audit command: Copy storage pools to bemanaged by DRM not found - entrywill be created.

Explanation: A database audit process finds no entriesin server database for copy storage pools to bemanaged by DRM. Because FIX=YES has been specifiedfor the audit command, the audit function creates anentry using the default value in the server database forthe copy storage pools to be managed by DRM.


User Response: To override the default value, issue aSET DRMCOPYSTGPOOL command to change thevalue after the audit command has completed.

ANR6733E Command: Cannot complete initializationfor process name process.

Explanation: The indicated process fails duringprocess initialization.

System Action: The indicated command is ended andserver processing continues.


ANR6734E Command: Volume volume name notprocessed: library library name notdefined.

Explanation: The indicated volume is not processedsince the designated library has not been defined or hasbeen deleted.

System Action: The volume is not processed.

User Response: Reissue the command using adifferent library name, or define the library beforeretrying the command.

ANR6735E Audit command: Courier information forORM not found.

Explanation: A database audit process finds no entriesin server database for courier name definitions used byDRM Offsite Recovery Media (ORM).



ANR6736I Audit command: Courier information forORM not found - entry will be created.

Explanation: A database audit process finds no entriesin server database for courier name definitions used byDRM Offsite Recovery Media (ORM). Because FIX=YEShas been specified for the audit command, the auditfunction creates an entry using the default value in theserver database for the courier name definitions.


User Response: To override the default value, issue aSET DRMCOURIERNAME command to change thevalue after the audit command has completed.

ANR6737E Audit command: Vault name for ORM notfound.

Explanation: A database audit process finds no entriesin server database for vault name definitions used byDRM Offsite Recovery Media (ORM).



ANR6738I Audit command: Vault name for ORM notfound - entry will be created.

Explanation: A database audit process finds no entriesin server database for vault name definitions used byDRM Offsite Recovery Media (ORM). Because FIX=YEShas been specified for the audit command, the auditfunction creates an entry using the default value in theserver database for the vault name definitions.




User Response: To override the default value, issue aSET DRMVAULTNAME command to change the valueafter the audit command has completed.

ANR6739E Audit command: Database backup seriesexpiration days for ORM not found.

Explanation: A database audit process finds no entriesin server database for database backup series expirationdays definitions used by DRM Offsite Recovery Media(ORM).



ANR6740I Audit command: Database backup seriesexpiration days for ORM not found -entry will be created.

Explanation: A database audit process finds no entriesin server database for database backup series expirationdays definitions used by DRM Offsite Recovery Media(ORM). Because FIX=YES has been specified for theaudit command, the audit function creates an entryusing the default value in the server database for thedatabase backup series expiration days definitions.


User Response: To override the default value, issue aSET DRMDBBACKUPEXPIREDAYS command tochange the value after the audit command hascompleted.

ANR6741E Audit command: Check label indicator forORM not found.

Explanation: A database audit process finds no entriesin server database for check label definitions used byDRM Offsite Recovery Media (ORM).



ANR6742I Audit command: Check label indicator forORM not found - entry will be created.

Explanation: A database audit process finds no entriesin server database for check label definitions used byDRM Offsite Recovery Media (ORM ). BecauseFIX=YES has been specified for the audit command, theaudit function creates an entry using the default valuein the server database for the check label definitions.


User Response: To override the default value, issue aSET DRMCHECKLABEL command to change the valueafter the audit command has completed.

ANR6743E Audit command: File process indicator forORM not found.

Explanation: A database audit process finds no entriesin server database for file process definitions used byDRM Offsite Recovery Media (ORM).



ANR6744I Audit command: File process indicator forORM not found - entry will be created.

Explanation: A database audit process finds no entriesin server database for file process definitions used byDRM Offsite Recovery Media (ORM). Because FIX=YEShas been specified for the audit command, the auditfunction creates an entry using the default value in theserver database for the file process definitions.


User Response: To override the default value, issue aSET DRMFILEPROCESS command to change the valueafter the audit command has completed.

ANR6745E Audit command: DRM recovery media IDassignments are incorrect.

Explanation: A database audit process finds that theglobal attributes recovery media id used for serverDRM activities are incorrect.


User Response: Reissue the audit command withFIX=YES specified so that the DRM global attributescan be corrected.

ANR6746I Audit command: DRM recovery media IDassignments are incorrect - values willbe corrected.

Explanation: A database audit process finds that theglobal attributes recovery media ID used for serverDRM activities are incorrect. Since FIX=YES has beenspecified on the AUDIT command, the attribute valuewill be corrected in the server database.



ANR6747I Number of volumes processed: number

Explanation: The MOVE DRMEDIA command hasprocessed the number of volumes displayed. Thismessage may be displayed in response to a QUERYPROCESS command for a MOVE DRMEDIA command.





ANR6748I Number of volumes processed: number.Checking out volume volume name fromlibrary library name.

Explanation: The MOVE DRMEDIA commanddisplays the number of volumes already processed andthe name of the volume currently being checked outfrom the indicated library. This message may bedisplayed in response to a QUERY PROCESS commandfor a MOVE DRMEDIA command.



ANR6749I Command: process process ID terminatedbefore completion - process canceled.

Explanation: The indicated background processperforming the command shown has been canceled.

System Action: If other processes are executing, theseprocesses continue.


ANR6750E Disaster recovery manager operationcommand being processed is denied - serveris not in compliance with license terms.

Explanation: The server refuses a disaster recoverymanager operation because the current serverconfiguration is not in compliance with the licenseterms.

System Action: Server operation continues. Disasterrecovery operations cannot be performed until theserver is licensed for the Tivoli Disaster RecoveryManager product.

User Response: Issue a QUERY LICENSE commandto determine which license terms are not in compliance.

ANR6751E Disaster recovery manager operationcommand being processed is denied - serveris not licensed for disaster recoverymanager support.

Explanation: The server refuses a disaster recoverymanager operation because the server is not licensed tosupport the disaster recovery manager.


User Response: Obtain the license to support thedisaster recovery manager from your service provideror reseller. Issue the REGISTER LICENSE commandwith this license to enable the disaster recoverymanager support.

ANR6752W Disaster recovery manager operationCommand being processed is in violation ofserver license terms - server is notlicensed for disaster recovery managersupport.

Explanation: The server warns about a disasterrecovery manager operation because the server is notlicensed to support disaster recovery manager.


User Response: Obtain the license to support disasterrecovery manager from your service provider orreseller. Issue the REGISTER LICENSE command withthis license to enable disaster recovery managersupport.

ANR6753E command being processed encountered aninternal server error while checkinglicense compliance.

Explanation: The server encountered an internal errorin determining whether the server is in compliancewith license terms.


User Response: Issue the QUERY LICENSE andQUERY STATUS commands to determine if the serveris in compliance with license terms. Start an AUDITLICENSES process to adjust server license information.When this process completes, start the session again. Ifthe problem persists, contact your servicerepresentative.

ANR6754I Machine machine name characteristicsdeleted.

Explanation: A DELETE MACHINE command hasdeleted the requested characteristics from the server.



ANR6755I Machine machine name recoveryinstructions deleted.

Explanation: A DELETE MACHINE command hasdeleted the requested recovery instructions from theserver.



ANR6756E Machine machine name characteristics notdefined to the server.

Explanation: A DELETE MACHINE command cannotdelete the requested characteristics from the server. Thecharacteristics for the specified machine are not definedto the server.




User Response: Issue the command again and specifya machine that has characteristics defined to the server.

ANR6757E Machine machine name recoveryinstructions not defined to the server.

Explanation: A DELETE MACHINE command cannotdelete the requested recovery instructions from theserver. The recovery instructions for the specifiedmachine are not defined to the server.


User Response: Issue the command again and specifya machine that has recovery instructions defined to theserver.

ANR6758E Command: Only one character string canbe specified.

Explanation: The INSERT command is invalid. Eithera characteristics string can be specified or a recoveryinstructions string can be specified on the command.Both types of strings cannot be specified on thecommand at the same time.


User Response: Issue the command again and specifyone valid character string.

ANR6759E Disaster recovery manager operationcommand being processed is denied -disaster recovery manager support is notavailable for server platform platform.

Explanation: The server refuses a disaster recoverymanager operation because disaster recovery managersupport is not available for the indicated serverplatform.



ANR6760E Command: Executable command lineexceeds maximum length characters forvolume volume name.

Explanation: While writing to a command file, one ofthe following conditions occurred:

v The length of the command line written to thecommand file exceeds the LRECL specified for MVSor exceeds the default length for the command linewritten (255).

v The length of the command created after replacingthe substitution variables &VOL, &VOLDSN, &NL,and &LOC exceeds the server allowable commandline length (1500).


User Response: Issue the command again and specifya valid executable command with the CMD parameter.

In the case where volumes are being ejected from thelibrary, it is possible the server database does not reflectthe true state of the volume. For MOVE DRMEDIA,rerun the command after determining the cause of theerror. For MOVE MEDIA, an update volume commandshould be issued setting the access of the volume toread only.

If this message is issued by a MOVE or QUERYDRMEDIA command and the volume record has beendeleted from the server database, you can not use theMOVE or QUERY DRMEDIA commands to create thecommand file entry for this volume. In this case, youmust manually issue the proper command.

ANR6761E Command: WHERESTATE parameter isrequired.

Explanation: The indicated command specifies avolume name containing a pattern matching characterand the TOSTATE parameter. The WHERESTATEparameter is not specified. The specification is invalid.Pattern-matching for volume names is only allowedwhen the WHERESTATE parameter is specified.


User Response: Reissue the command specifying aspecific volume name or by specifying theWHERESTATE parameter along with the TOSTATEparameter.

ANR6762E Command: The specified destination statetostate is invalid for volume volume namein current state state.

Explanation: The indicated command specifies adestination state that is invalid for the volume nameshown in the indicated current state.

System Action: The server does not process thevolume.

User Response: Issue the command again and specifya valid destination state for the volume name shown.

ANR6763I Command: The specified command hasbeen written to file ’file name’.

Explanation: The command string specified with theCMD parameter on the command shown is written to



the indicated file for each volume successfullyprocessed.


User Response: Execute the commands written to thefile.

ANR6764E command: Command file name exceedsmaximum characters characters.

Explanation: The file name specified for containingthe executable commands generated by DRM exceedsthe maximum valid length shown.


User Response: Reissue the command specifying avalid file name.

ANR6765E Command: Invalid not mountablelocation name - not mountable name.

Explanation: The indicated command has beenentered with an invalid not mountable location name.


User Response: Reissue the command with a validnot mountable location name.

ANR6766E Command: No command string isspecified for FORMAT=CMD.

Explanation: The indicated command has beenentered with a FORMAT=CMD to write a commandstring to a file, but no command string is specified.


User Response: Reissue the command specifying acommand string to be written to a file.

ANR6767E Command: Invalid command file name -command file name.

Explanation: The indicated command has beenentered with an invalid command file name.


User Response: Reissue the command with a validcommand file name.

ANR6768E command: Prefix exceeds maximumcharacters characters.

Explanation: The prefix specified for recovery planfiles or for plan instructions files exceeds the maximumvalid length. The maximum valid length is shown inthe message.


User Response: Reissue the command specifying avalid prefix.

ANR6769E Audit command: Not mountable nameinformation for ORM not found.

Explanation: A database audit process finds no entriesin server database for not mountable location namedefinitions used by DRM Offsite Recovery Media(ORM).



ANR6770I Audit command: Not mountable nameinformation for ORM not found - entrywill be created.

Explanation: A database audit process finds no entriesin server database for not mountable location namedefinitions used by DRM Offsite Recovery Media(ORM). Because FIX=YES has been specified for theaudit command, the audit function creates an entryusing the default value in the server database for thecourier name definitions.


User Response: To override the default value, issue aSET DRMNOTMOUNTABLENAME command tochange the value after the audit command hascompleted.

ANR6771E Audit command: Command file nameinformation for ORM not found.

Explanation: A database audit process finds no entriesin server database for command file name definitionsused by DRM Offsite Recovery Media (ORM).



ANR6772I Audit command: Command file nameinformation for ORM not found - entrywill be created.

Explanation: A database audit process finds no entriesin server database for command file name definitionsused by DRM Offsite Recovery Media (ORM). BecauseFIX=YES has been specified for the audit command, theaudit function creates an entry using the default valuein the server database for the command file namedefinitions.


User Response: To override the default value, issue a



SET DRMCMDFILENAME command to change thevalue after the audit command has completed.

ANR6773E Command: Unable to open file ’commandfile name’ for output.

Explanation: An error occurred while opening thecommand file name shown. The file name shown in themessage is specified with the indicated command, theSET command, or the default name generated by theindicated command.

System Action: The server does not process theindicated command.

User Response: Examine error messages that mayhave been displayed prior to this message and correctany problems, if possible. Make sure that the server hasproper authority to write to the file indicated. In AIX,make sure that the file name specified in the commandor in the SET command is a full path file name, not adirectory path name. In MVS, make sure that the filename specified in the command or in the SETcommand is a valid MVS file name. Reissue thecommand after determining the cause of the error.

ANR6774E Command: Invalid volume transitionstates - from ’specified WHERESTATE’state to ’specified TOSTATE’ state.

Explanation: The TOSTATE specified is an invaliddestination state for the WHERESTATE specified.


User Response: Issue the command again and specifya valid destination state.

ANR6775E Command: Error writing to file ’file name’for volume volume name.

Explanation: An error occurred while writing to thefile name shown for the indicated volume.


User Response: Examine error messages that mayhave been displayed prior to this message and correctany problems, if possible. Make sure that the server hasproper authority to write to the file indicated. Reissuethe command after determining the cause of the error.

In the case where volumes are being ejected from thelibrary, it is possible the server database does not reflectthe true state of the volume. For MOVE DRMEDIA,rerun the command after determining the cause of theerror. For MOVE MEDIA, an update volume commandshould be issued setting the access of the volume toread only.

If this message is issued by a MOVE or QUERYDRMEDIA command and the volume record has been

deleted from the server database, you can not use theMOVE or QUERY DRMEDIA commands to create thecommand file entry for this volume. In this case, youmust manually issue the proper command.

ANR6776E Command: Could not delete file: file name

Explanation: The indicated command failed but thefile created could not be deleted.


User Response: Delete the file shown.

ANR6777E Command: Command file ’file name’already in use.

Explanation: The command indicated references acommand file name that is in use. The command filename shown is selected for use by the server in thefollowing order:

v The file name specified on the indicated command.

v The file name specified on the SET command.

v The file name generated by the server (AIX only).


User Response: Reissue the command at a later timeor reissue the command specifying a differentcommand file name.

ANR6778E Command: Volume volume name notprocessed: device type device type notsupported.

Explanation: The indicated volume is not processedbecause the device type shown is not supported by thefunction.

System Action: The indicated volume is notprocessed.


ANR6779E Disaster recovery manager operationcommand being processed is denied -disaster recovery manager support is notavailable for server platform.

Explanation: The server refuses a disaster recoverymanager operation because disaster recovery managersupport is not available for the server platform.



ANR6780E Audit command: An invalid recovery planfile expiration days encountered.

Explanation: A database audit process encounters aninvalid value for recovery plan file expiration days.




User Response: Issue the command again and specifyFIX=YES to correct the expiration days. Or, issue anSET DRMRPFEXPIREDAYS command and specify anew expiration days value.

ANR6781I Audit command: An invalid recovery planfile expiration days encountered - thedefault value will be set.

Explanation: A database audit process encounters aninvalid value for recovery plan file expiration days.Because FIX=YES has been specified, the audit functionsets the expiration days value to the default value.


User Response: To override the default value, issue aSET DRMRPFEXPIREDAYS command to change thevalue after the audit command has completed.

ANR6782E Audit command: Recovery plan fileexpiration days not found.

Explanation: A database audit process finds no entriesin server database for recovery plan file expiration daysdefinitions.



ANR6783I Audit command: Recovery plan fileexpiration days not found - entry willbe created.

Explanation: A database audit process finds no entriesin server database for recovery plan file expiration daysdefinitions. Because FIX=YES has been specified for theaudit command, the audit function creates an entryusing the default value in the server database for therecovery plan file expiration days definitions.


User Response: To override the default value, issue aSET DRMRPFEXPIREDAYS command to change thevalue after the audit command has completed.

ANR6784I Number of volumes processed: numbervolumes processed. Volumes sent to librarylibrary name for checkout: number volumessent.

Explanation: The MOVE DRMEDIA command hasprocessed the number of volumes shown. Currently, theMOVE DRMEDIA command has sent for processingthe number of volumes shown to the library shown.This message may be displayed in response to aQUERY PROCESS command for a MOVE DRMEDIAcommand.



ANR6785W Warning: The ADSM V3 DisasterRecovery Manager Disk Image Dumpfunction is not supported in the TivoliDisaster Recovery Manager. The ADSMV3 DRM Disk Image Restore functionhas been stabilized with no newmaintenance or hardware supportplanned.

Explanation: None.

System Action: DRM Disk Image Dump and Restorefunction continues.


ANR6900I Command: The recovery plan file filename was created.

Explanation: The recovery plan file was created.



ANR6901I Number of plan stanzas processed:number.

Explanation: The PREPARE command has processedthe number of stanzas displayed. This message may bedisplayed in response to a QUERY PROCESS commandfor a PREPARE command.



ANR6902I Number of plan stanzas processed:number. Currently processing stanza:recovery plan stanza name.

Explanation: The PREPARE command displays thenumber of stanzas already processed and the name ofthe stanza currently being processed. This message maybe displayed in response to a QUERY PROCESScommand for a PREPARE command.



ANR6903I Cancel in progress.

Explanation: The PREPARE command has beencanceled and will end when resources have been freedfor the background process. This message may bedisplayed in response to a QUERY PROCESS commandfor a PREPARE command.





ANR6904I Sending recovery plan file to targetserver.

Explanation: The PREPARE command is sending therecovery plan file to the target server. This messagemay be displayed in response to a QUERY PROCESScommand for a PREPARE command.



ANR6905I Command: Recovery plan file RPF volumename was created. Specified device classdevice class name.

Explanation: The recovery plan file was created on thetarget server.



ANR6912W Command: The database was not backedup.

Explanation: No backups have been made of theserver data base.

System Action: Stanzas in the recovery plan do notinclude database recovery information.

User Response: Backup the server data base byissuing the BACKUP DB command.

ANR6913W Command: No volumes with backup dataexist in copy storage pool storage poolname.

Explanation: A copy storage pool does not containany volumes with usable data.

System Action: Stanzas in the recovery plan do notinclude recovery information for any volumes in thestorage pool.

User Response: Determine why this storage pool hasno volumes with usable data.

ANR6915W Command: Storage pool storage pool namestorage pool type is not defined to theserver.

Explanation: A storage pool that is not defined to theserver was specified by SET DRMPRIMSTGPOOL, SETDRMCOPYSTGPOOL, or on the PREPARE commandline.

System Action: Stanzas in the recovery plan do notinclude recovery information for the storage pool.

User Response: Correct the storage pool specificationor define the storage pool to the server.

ANR6916W Command: No copy storage pools aredefined.

Explanation: The server has no copy storage poolsdefined.

System Action: Recovery plan file will not containcopy storage pool information.

User Response: Define copy storage pools in theserver.

ANR6918W Command: Recovery instructions file filename not found.

Explanation: A source file for recovery instructionswas not found.

System Action: The recovery plan will not containrecovery instructions.

User Response: To get recovery instructions in therecovery plan, ensure the corresponding instructionssource file exists. If it does, check authorizations to thefile.

ANR6920W Command: Generated replacementvolume name volume name is not validfor server device type device type.Original volume name: volume name.Stanza is stanza name.

Explanation: Appending the replacement volumename postfix (as defined with SETDRMPLANVPOSTFIX) to the original volume namehas created a name that is not valid for the serverdevice type shown.

System Action: Replacement volume name is used inthe recovery plan stanza.

User Response: Devise a naming convention thatallows the use of the replacement volume name postfixor at restore time manually update the generatedrecovery plan with a legal replacement name. Foradditional information and related commands, refer tothe Administrator’s Reference for your particularplatform.

ANR6921W Command: Cannot locate server optionsfile ’file name’.

Explanation: The Prepare command cannot open thespecified server options file.

System Action: VOLHISTORY and DEVCONFIGoptions are added to the recovery plan file stanzaDSMSERV.OPT.FILE.




ANR6922W Command: No machine information wasdefined for the machine that containsserver server name.

Explanation: The machine information has not beensaved in the server data base.

System Action: The recovery plan file does notcontain the machine and recovery media informationstanzas.

User Response: If you want to include the machineinformation in the recovery plan file, issue the DEFINEMACHINE command to save the machine informationin the server data base and reissue the PREPAREcommand.

ANR6923W Command: No recovery media definedfor machine machine name.

Explanation: No recovery media has been defined tothe server for the specified machine.

System Action: The recovery plan file does notcontain the machine recovery media stanza.

User Response: If you want to include the machinerecovery media information in the recovery plan file,issue the DEFINE RECOVERYMEDIA command.Reissue the PREPARE command after the appropriatecommands have been issued to define the recoverymedia. For additional information and relatedcommands, refer to the Administrator’s Reference foryour particular platform.

ANR6924W Command: No recovery instructionsdefined for machine machine name.

Explanation: No recovery instructions have beendefined to the server for the specified machine.

System Action: The recovery plan file does notcontain the machine recovery instructions stanza.

User Response: If you want to include the machinerecovery instructions in the recovery plan file, issue theINSERT command. Reissue the PREPARE commandafter the appropriate commands have been issued todefine the recovery media. For additional informationand related commands, refer to the Administrator’sReference for your particular platform.

ANR6925W Command: No machine characteristicsdefined for machine machine name.

Explanation: No characteristics have been defined tothe server for the specified machine.

System Action: The recovery plan file does notcontain the machine characteristics stanza.

User Response: If you want to include the machinerecovery instructions in the recovery plan file, issue theINSERT command. Reissue the PREPARE command

after the appropriate commands have been issued todefine the recovery media. For additional informationand related commands, refer to the Administrator’sReference for your particular platform.

ANR6926W Command: There is at least one invalidgenerated volume name associated withstorage pool storage pool server devicetype device type in stanza stanza name.

Explanation: Appending the replacement volumename postfix (as defined with SETDRMPLANVPOSTFIX) to the original volume namehas created a name that is not valid for the serverdevice type shown.

System Action: Replacement volume name is used inthe recovery plan stanza.

User Response: Devise a naming convention thatallows the use of the replacement volume name postfixor at restore time manually update the generatedrecovery plan with a legal replacement name. Foradditional information and related commands, refer tothe Administrator’s Reference for your particularplatform.

ANR6927W Command: Primary storage pool storagepool name, storage pool data format, is notmanaged by DRM.

Explanation: A primary storage pool withDATAFORMAT=NETAPPDUMP was specified by SETDRMPRIMSTGPOOL or on the PREPARE commandline.

System Action: Stanzas in the recovery plan do notinclude recovery information for the storage pool.

User Response: Correct the storage pool specification.

ANR6928W Command: No eligible primary storagepools match the specified storage poolname storage pool name .

Explanation: The storage pool specified by SETDRMPRIMSTGPOOL or on the PREPARE commandline does not match any eligible primary storage pool.Possible reasons include:

v Primary storage pools were not defined.

v Primary storage pools were defined, but their dataformat is NETAPPDUMP.

v The name specified does not match eligible primarystorage pool names.

System Action: Stanzas in the recovery plan do notinclude recovery information for the storage pools.

User Response: Correct the storage pool specificationor define eligible storage pools to the server.



ANR6929W Command: No eligible primary storagepools are defined to the server.

Explanation: The server has no eligible primarystorage pools defined.

System Action: Recovery plan file will not containprimary storage pool information.

User Response: Define eligible primary storage poolsto the server.

ANR6937E command: parameter name parameter notallowed from the command line.

Explanation: The parameter shown is not allowedfrom the command line interface.


User Response: Reissue the command with theparameter from the web.

ANR6938I No information found for stanza stanzaname.

Explanation: No information found for recovery planfile stanza shown.

System Action: The server does not display theinformation for the stanza.

User Response: None

ANR6939E Command: Invalid recovery plan filestanza name - stanza name.

Explanation: The specified recovery plan file stanzaname is invalid.


User Response: Issue the command again and specifya valid recovery plan file stanza name.

ANR6940E command command not allowed fromserver console.

Explanation: The indicated command is not allowedto be issued from the server console.


User Response: Reissue the command from anadministrator using an Administrative Client.

ANR6941E Query recovery plan file content iswaiting for mount point in device classdevice class name.

Explanation: Query recovery plan file content hasbegun to wait for a mount point that can be used for avolume in the device class shown.

System Action: The function waits for the mountpoint.


ANR6942E Query recovery plan file content iswaiting for access to input volumevolume name.

Explanation: Query recovery plan file content hasbegun to wait for availability of the input volumeshown.

System Action: The function waits for the volume tobecome available.


ANR6943E Query recovery plan file content iswaiting for mount of input volumevolume name.

Explanation: Query recovery plan file content hasbegun to wait for the mount of the input volumeshown.

System Action: The function waits for mount.


ANR6944E Command: Invalid recovery plan filename - recovery plan file name.

Explanation: The recovery plan file name specified inthe command is invalid.


User Response: Issue the command again and specifya valid recovery plan file name.

ANR6945E Command: Cannot find filespace filespacename for recovery plan file recovery planfile name.

Explanation: The server cannot find the filespace(ADSM.SERVER) for recovery plan file specified in theserver.

System Action: The retrieve operation ends, and theserver operation continues.

User Response: Issue QUERY FILESPACE commandon the target server to see if there is any filespacescreated for the recovery plan file. The filespace namefor the recovery plan file is ADSM.SERVER.

ANR6946E Command: Retrieve failed for recoveryplan file name - error on input storagedevice.

Explanation: The server ends an retrieve operationbecause an I/O error has been encountered by theserver in reading from a device.




User Response: Query the activity log to findmessages preceding this one that specify the device thatis failing. The server may need to be shut down withthe HALT command to correct the hardware problem.

ANR6947E Command: Data storage retrieve failedfor recovery plan file name - data integrityerror detected.

Explanation: The server ends the retrieve operationbecause an internal database integrity error has beenencountered on the server.



ANR6948E Command: Cannot find the recovery planfile for Recovery plan file name.

Explanation: The server cannot find the specifiedrecovery plan file.


User Response: Issue the command again and specifya valid recovery plan file name. Use the QUERYRPFILE command to view the name of the recoveryplan file that you are interested in displaying itscontent.

ANR6949E Command: No matching device classdefined.

Explanation: The device class specified in thecommand does not match any device class defined tothe server.


User Response: Issue the command again and specifya valid device class.

ANR6950E Command: The recovery plan file was notcreated.

Explanation: Due to a processing error, a recoveryplan file was not created.

System Action: Recovery plan file not created.

User Response: Examine error messages that mayhave been displayed prior to this message and correctany problems, if possible. Reissue the command, afterdetermining the cause of the error.

ANR6951E Command: Recovery plan file file namewas not created.

Explanation: Due to a processing error, a recoveryplan file was not created.


User Response: Examine error messages that mayhave been displayed prior to this message and correctany problems, if possible. Make sure that the server hasproper authority to write to the file indicated and thatthere is sufficient space in the file system for the file.Reissue the command, after determining the cause ofthe error.

ANR6952E Command: File name file name alreadyexists.

Explanation: File already exits.


User Response: Determine why file already exists. Ifpossible, delete it. Reissue the command, afterdetermining the cause of the error.

ANR6953E Command: File write error.

Explanation: An error occurred while writing to therecovery plan file.

System Action: The recovery plan file was notcreated.

User Response: Examine error messages that mayhave been displayed prior to this message and correctany problems, if possible. Make sure that there issufficient space in the file system for the file. Reissuethe command after determining the cause of the error.

ANR6954E Command: Unable to open file ’file name’for output.

Explanation: An error occurred while opening therecovery plan file for output.


User Response: Examine error messages that mayhave been displayed prior to this message and correctany problems, if possible. Make sure that the server hasproper authority to write to the file indicated. Reissuethe command after determining the cause of the error.

ANR6959E Command: Plan instructions prefix’instructions prefix’ is not valid.

Explanation: The prefix specified for recoveryinstructions is not valid.





ANR6960E Command: Recovery plan prefix ’planprefix’ is not valid.

Explanation: The prefix specified for the recovery planfile is too long.



ANR6962E Command: Query database failed.

Explanation: A server database query error occurred.This message always accompanies another errormessage and provides more detail about that error.


User Response: Issue a QUERY ACTLOG commandto view the activity log and search for messages. If theerror cannot be isolated and resolved, contact yourservice representative.

ANR6963E Command: Query log failed.




ANR6964E Command: Query storage pool failed.

Explanation: An server database query error occurred.This message always accompanies another errormessage and provides more detail about that error.



ANR6965E Command: Query volume failed.




ANR6966E Command: Query database volume failed.




ANR6967E Command: Query log volume failed.




ANR6968E Command: Query volume history failed.




ANR6969E Command: Query device class failed.






ANR6970E Command: A recovery plan file is alreadybeing created.

Explanation: The server command processor will notstart a background process to execute anotherPREPARE command.


User Response: Reissue the command after the firstPREPARE command has completed.

ANR6971E Command: Could not delete plan file planfile name.

Explanation: Prepare command failed but the plan filecreated could not be deleted.


User Response: Delete the plan file.

ANR6972E Command: Query machine failed.

Explanation: A server machine query error occurred.This message always accompanies another errormessage and provides more detail about that error.



ANR6973E Command: Query recovery media failed.

Explanation: A server recovery media query erroroccurred. This message always accompanies anothererror message and provides more detail about thaterror.



ANR6974E Command: Unable to open file file name.

Explanation: An error occurred while PREPARE wasattempting to open the local recovery plan file copy inorder to send it to the target server.

System Action: The recovery plan file is not stored onthe target server.

User Response: Examine error messages that mayhave been displayed prior to this message and correctany problems, if possible. Reissue the command afterdetermining the cause of the error.

ANR6975E Command: Unable to read file file name.

Explanation: An error occurred while PREPARE wasattempting to read the local recovery plan file copy inorder to send it to the target server.

System Action: The recovery plan file is not stored onthe target server.

User Response: Examine error messages that mayhave been displayed prior to this message and correctany problems, if possible. Reissue the command afterdetermining the cause of the error.

ANR6976E Command: The recovery plan file was notstored on another server and the localcopy file name cannot be deleted.

Explanation: Due to a processing error, a recoveryplan file was not stored on target server and the localcopy of the plan file cannot be deleted.

System Action: PREPARE processing ends.

User Response: Examine error messages that mayhave been displayed prior to this message and correctany problems, if possible. After determining the causeof the error, re-issue the PREPARE command anddelete the local recovery plan file.

ANR6977E Command: Device class name device classname exceeds maximum characterscharacters.

Explanation: The command shown has been enteredand specifies a device class name that is too long. Themaximum valid length for a device class name isshown in the message.


User Response: Reissue the command specifying avalid device class name.

ANR6978E Command: Invalid device class device classname.

Explanation: The specified device class cannot be usedby the command shown. Possible reasons include:

v The device class is not defined.

v The device class is defined but not of type SERVER.

v The name specified is an invalid device class name.


User Response: Reissue the command with a validdevice class.



ANR6979E Command: Recovery plan file was notcreated. Specified device class device classname.

Explanation: A recovery plan file cannot be notcreated using the specified device class.


User Response: Examine error messages that mayhave been displayed prior to this message and correctany problems, if possible. Reissue the command, afterdetermining the cause of the error.

ANR6980E Command: Prefix prefix exceeds maximumcharacters characters.

Explanation: The command shown has been enteredand specifies a plan or instructions prefix that is toolong. The maximum valid length is shown in themessage.


User Response: Reissue the command specifying ashorter prefix.

ANR6984E Command: Out of space on sequentialmedia, scratch media could not bemounted. Specified device class deviceclass name; maximum capacity: number ofbytes bytes.

Explanation: During command PREPARE processing,the process encounters an out-of-space conditionwriting to the sequential media. Command PREPAREends when there is no more space on the sequentialmedia for storing data.

System Action: Command PREPARE processing ends.Server processing continues.

User Response: Increase the device class maximumcapacity and reissue the PREPARE command. If anobject was created on the target server, issue theRECONCILE VOLUMES FIX=YES to delete the objectfrom the target server.


Explanation: During command command processing, avolume cannot be used because it is already defined ina storage pool, or has been previously used by anexport, database dump, database backup, or DRMprepare operation or is in use by another process.


User Response: Re-issue the PREPARE command.

ANR6986E Command: The DELETELATESTparameter is only valid for volumehistory types RPFILE orRPFSNAPSHOT.

Explanation: The command failed because an invalidvolume history type was specified for the TYPE=parameter.


User Response: Re-issue the command and specify avalid type value.

ANR7800I DSMSERV generated at time on date.

Explanation: The server module was generated at theindicated date and time.



ANR7800I (HP-UX) DSMSERV generated at time ondate.




ANR7800I (Linux) DSMSERV generated at time ondate.




ANR7800I (PASE) DSMSERV generated at time ondate.




ANR7800I (Solaris) DSMSERV generated at time ondate.




ANR6979E • ANR7800I (Solaris)


ANR7800I (Windows) DSMSERV generated at timeon date.




ANR7801I Subsystem (master) PID is processidentifier.

Explanation: The server kernel extension process hasthe indicated process identifier.



ANR7801I (HP-UX) Subsystem (master) process ID isprocess identifier.

Explanation: The server’s master HP-UX process hasthe indicated process identifier.



ANR7801I (Linux) Subsystem process ID is processidentifier.

Explanation: The server process has the indicatedprocess identifier.



ANR7801I (PASE) Subsystem (master) PID is processidentifier.

Explanation: The server kernel extension process hasthe indicated process identifier.



ANR7801I (Solaris) Subsystem process ID is processidentifier.

Explanation: The server process has the indicatedprocess identifier.



ANR7802E Shared memory segments for a serverrunning in the current directory alreadyexist. The -F parameter can be used tooverwrite.

Explanation: Shared memory segments are created foreach instance of the server based on the currentdirectory. This message indicates that the sharedmemory segments already exist. A server is presentlyrunning from the current directory or a server runningfrom the current directory ended abnormally.

System Action: The server terminates.

User Response: If the server running in the currentdirectory terminated abnormally, start dsmserv with the-F parameter to force the existing shared memorysegments to be overwritten. If you want to runmultiple instances of the server, each instance must berun from a separate directory with a separatedsmserv.dsk file and have separate log, database, andstorage volumes.

ANR7802E (PASE) Shared memory segments for aserver running in the current directoryalready exist. The -F parameter can beused to overwrite.

Explanation: Shared memory segments are created foreach instance of the server based on the currentdirectory. This message indicates that the sharedmemory segments already exist. A server is presentlyrunning from the current directory or a server runningfrom the current directory ended abnormally.

System Action: The server terminates.

User Response: If the server running in the currentdirectory terminated abnormally, start dsmserv with the-F parameter to force the existing shared memorysegments to be overwritten. If you want to runmultiple instances of the server, each instance must berun from a separate directory with a separatedsmserv.dsk file and have separate log, database, andstorage volumes.

ANR7803E Attempt to overwrite a shared memorysegment, as directed with the -Fparameter, FAILED.

Explanation: The server has been started with the -Fparameter and unsuccessfully attempted to overwriteexisting shared memory segments. This error occurswhen the user that starts the server with -F parameteris not the owner of the shared memory segments andlacks the required authority.

System Action: Server terminates.

User Response: Resolve the authorization problemand restart the server.

ANR7800I (Windows) • ANR7803E


ANR7803E (PASE) Attempt to overwrite a sharedmemory segment, as directed with the -Fparameter, FAILED.

Explanation: The server has been started with the -Fparameter and unsuccessfully attempted to overwriteexisting shared memory segments. This error occurswhen the user that starts the server with -F parameteris not the owner of the shared memory segments andlacks the required authority.


User Response: Resolve the authorization problemand restart the server.

ANR7804I An server is already running from thisdirectory.

Explanation: The server has attempted to open theadsmserv.lock file in the current directory but failed todo so because an existing server already has the fileopen.


User Response: Examine the contents of theadsmserv.lock file. The process ID for the server that isrunning is recorded in this file. Two servers cannot bestarted from the same directory. You may remove theadsmserv.lock file and attempt to start the server ONLYif the recorded process ID is NOT currently runningdsmserv. The 'ps -e' AIX command can be used todisplay processes that are currently running.

ANR7804I (HP-UX) A server is already running fromthis directory.



User Response: Examine the contents of theadsmserv.lock file. The process ID for the server that isrunning is recorded in this file. Two servers cannot bestarted from the same directory. You may remove theadsmserv.lock file and attempt to start the server ONLYif the recorded process ID is NOT currently runningdsmserv. The 'ps -e' command can be used to displayprocesses that are currently running.

ANR7804I (PASE) An server is already running fromthis directory.



User Response: Examine the contents of theadsmserv.lock file. The process ID for the server that isrunning is recorded in this file. Two servers cannot bestarted from the same directory. You may remove theadsmserv.lock file and attempt to start the server ONLYif the recorded process ID is NOT currently runningdsmserv. The 'ps -e' PASE command can be used todisplay processes that are currently running.

ANR7805E Volume volume name is in use by anotherserver.

Explanation: The server has attempted to open a diskvolume but has discovered that the volume is in use byanother server.

System Action: The open operation fails for thevolume.

User Response: To prevent concurrent RAW volumeaccess by more than one server, files are created in the/tmp directory to 'lock' these volumes. The names ofthese temporary files are/tmp/adsm.disk.dev.<volumename> where<volumename> is the name of the RAW volumedefined in the /dev directory. Please note that the namefor the logical volume as defined in SMIT isrepresented in the /dev directory with a leading 'r'character (for example, a raw volume defined in SMITas dsmstg1 will be represented in the /dev directory asthe file /dev/rdsmstg1).

You may use the AIX 'ps -e' command to determine ifother dsmserv processes are running. You may removethe temporary lock files and attempt to re-start theserver ONLY if there are no other dsmserv processesrunning

ANR7805E (Linux) Volume volume name is in use byanother server.



User Response: To prevent concurrent RAW volumeaccess by more than one server, files are created in the/tmp directory to 'lock' these volumes. The names ofthese temporary files are/tmp/adsm.disk.dev.<volumename> where<volumename> is the name of the RAW volumedefined in the /dev directory. Please note that the namefor a RAW logical volume as defined in Solaris is in the/dev directory with a leading 'r' character (for example,a raw volume defined in Solaris on a regular SCSIdrive as dsk/c0t0d0s0 will be represented in the /devdirectory as the file /dev/rdsk/c0t0d0s0). For aREGULAR DISK volume, the server automaticallylocks/unlocks a volume. Different linked file namespointing to the same volume will cause this message

ANR7803E (PASE) • ANR7805E (Linux)


since the server locks the linked volume, not the linkname itself.

You may use the Solaris 'ps -ef | grep dsmserv'command to determine if other dsmserv processes arerunning. You may remove the temporary lock files forRAW volumes and attempt to re-start the server ONLYif there are no other dsmserv processes are running.

ANR7805E (PASE) Volume volume name is in use byanother server.



User Response: To prevent concurrent RAW volumeaccess by more than one server, files are created in the/tmp directory to 'lock' these volumes. The names ofthese temporary files are/tmp/adsm.disk.dev.<volumename> where<volumename> is the name of the RAW volumedefined in the /dev directory. Please note that the namefor the logical volume as defined in SMIT isrepresented in the /dev directory with a leading 'r'character (for example, a raw volume defined in SMITas dsmstg1 will be represented in the /dev directory asthe file /dev/rdsmstg1).

You may use the PASE 'ps -e' command to determine ifother dsmserv processes are running. You may removethe temporary lock files and attempt to re-start theserver ONLY if there are no other dsmserv processesrunning

ANR7805E (Solaris) Volume volume name is in use byanother server.



User Response: To prevent concurrent RAW volumeaccess by more than one server, files are created in the/tmp directory to 'lock' these volumes. The names ofthese temporary files are/tmp/adsm.disk.dev.<volumename> where<volumename> is the name of the RAW volumedefined in the /dev directory. Please note that the namefor a RAW logical volume as defined in Solaris is in the/dev directory with a leading 'r' character (for example,a raw volume defined in Solaris on a regular SCSIdrive as dsk/c0t0d0s0 will be represented in the /devdirectory as the file /dev/rdsk/c0t0d0s0). For aREGULAR DISK volume, the server automaticallylocks/unlocks a volume. Different linked file namespointing to the same volume will cause this message

since the server locks the linked volume, not the linkname itself.

You may use the Solaris 'ps -ef | grep dsmserv'command to determine if other dsmserv processes arerunning. You may remove the temporary lock files forRAW volumes and attempt to re-start the server ONLYif there are no other dsmserv processes are running.

ANR7806W Unable to open file file.

Explanation: The server was unable to open theindicated file.

System Action: The operation that was to use theindicated file fails. A subsequent unnumbered messagehad details from the system.

User Response: Determine the reason for being unableto open the file and re-attempt the operation. Commonreasons for being unable to open the file includeproviding the wrong name, having insufficientauthorization to open the file and not being the file’sowner.

ANR7806W (HP-UX) Unable to open file file.




ANR7806W (Linux) Unable to open file file.




ANR7806W (PASE) Unable to open file file.


System Action: The operation that was to use theindicated file fails. A subsequent unnumbered message

ANR7805E (PASE) • ANR7806W (PASE)


had details from the system.


ANR7806W (Solaris) Unable to open file file.




ANR7806W (Windows) Unable to open file file.



User Response: Determine the reason for being unableto open the file and re-attempt the operation. Commonreasons for being unable to open the file includeproviding the wrong name, having insufficientauthorization to open the file and not being the file’sowner. The file may be already opened by the server oranother program.

ANR7807W Unable to get information for file file.

Explanation: The server was unable to get informationabout the indicated file.

System Action: The operation that was to use theindicated file fails. A subsequent, unnumbered messagehas details from the system.

User Response: Determine the reason for being unableto access the file and re-attempt the operation.Common reasons for being unable to access the fileinclude providing the wrong name, having insufficientauthorization to open the file and not being the file’sowner.

ANR7807W (HP-UX) Unable to get information forfile file.




ANR7807W (Linux) Unable to get information forfile file.



User Response: Determine the reason for being unableto access the file and re-attempt the operation.Common reasons for being unable to access the fileinclude providing the wrong name, having insufficientauthorization to open the file, not being the file’sowner, or too many soft links to the file. If trying toaccess a RAW partition, the server must be started withsuperuser privileges.

ANR7807W (PASE) Unable to get information forfile file.




ANR7807W (Solaris) Unable to get information forfile file.



User Response: Determine the reason for being unableto access the file and re-attempt the operation.Common reasons for being unable to access the fileinclude providing the wrong name, having insufficientauthorization to open the file, not being the file’sowner, or too many soft links to the file. If trying to

ANR7806W (Solaris) • ANR7807W (Solaris)


access a RAW partition, the server must be started withsuperuser privileges.

ANR7808W root user authority required fornon-default scheduling policy.

Explanation: The server was unable to use thescheduling policy specified in the options file. Theserver must be running with root authority to use anyscheduling policy other than the default.

System Action: Operation continues but with thedefault scheduling policy.

User Response: Run the server with root authority ordon’t specify a scheduling policy in the options file.

ANR7808W (PASE) root user authority required fornon-default scheduling policy.

Explanation: The server was unable to use thescheduling policy specified in the options file. Theserver must be running with root authority to use anyscheduling policy other than the default.

System Action: Operation continues but with thedefault scheduling policy.

User Response: Run the server with root authority ordon’t specify a scheduling policy in the options file.

ANR7809I Using scheduling policy policy.

Explanation: All threads in the server will use thespecified scheduling policy.

System Action: Operations continue

User Response: None

ANR7809I (PASE) Using scheduling policy policy.

Explanation: All threads in the server will use thespecified scheduling policy.

System Action: Operations continue

User Response: None

ANR7810W Unable to create a new child process.

Explanation: The server cannot create a new childthread.

System Action: Server processing continues. Othererror messages from the server component aredisplayed.

User Response: Ensure that sufficient paging space isavailable for AIX. If the server has been started from anon-root user ID, ensure that the AIX process limit peruser is sufficient for the server. The server requiresapproximately 24 processes, in addition to one processper client session, and one process for each backgroundoperation. Each thread started by the server is an AIX

process. To change the number of processes per user,use the SMIT menus for System Environment, andchoose Change / Show Characteristics of OperatingSystem. You may also use SMIT to determine if thenumber of applications is causing a memory shortage.It may be necessary to decrease the maximum numberof client sessions by changing the MAXSESSIONSoption in the server options file.

ANR7810E (HP-UX) Error creating console inputthread.

Explanation: Unable to start console input thread.

System Action: Server operation stops.

User Response: See other issued messages.

ANR7810E (Linux) Error creating console inputthread.




ANR7810W (PASE) Unable to create a new childprocess.



User Response: Ensure that sufficient paging space isavailable for PASE. If the server has been started from anon-root user ID, ensure that the PASE process limitper user is sufficient for the server. The server requiresapproximately 24 processes, in addition to one processper client session, and one process for each backgroundoperation. Each thread started by the server is a PASEprocess. To change the number of processes per user,use the SMIT menus for System Environment, andchoose Change / Show Characteristics of OperatingSystem. You may also use SMIT to determine if thenumber of applications is causing a memory shortage.It may be necessary to decrease the maximum numberof client sessions by changing the MAXSESSIONSoption in the server options file.

ANR7810E (Solaris) Error creating console inputthread.




ANR7808W • ANR7810E (Solaris)


ANR7811I Direct I/O will be used for all eligibledisk files.

Explanation: All disk files which meet eligibilityrequirements will be opened with the O_DIRECT flag.

System Action: Operations continue.

User Response: None

ANR7811E (HP-UX) Insufficient memory for consoleinitialization.

Explanation: The server is unable to allocate enoughmemory for console initialization.


User Response: Ensure that there is sufficient pagingspace for HP-UX. It may be necessary to reduce themaximum number of client sessions by changing theMAXSESSIONS option in the server options file.

ANR7811E (Linux) Insufficient memory for consoleinitialization.



User Response: Ensure that there is sufficient pagingspace. It may be necessary to reduce the maximumnumber of client sessions by changing theMAXSESSIONS option in the server options file.

ANR7811E (Solaris) Insufficient memory for consoleinitialization.



User Response: Ensure that there is sufficient pagingspace for Sun Solaris. It may be necessary to reduce themaximum number of client sessions by changing theMAXSESSIONS option in the server options file.

ANR7812I Direct I/O will not be used for any diskfiles.

Explanation: The AIXDIRECTIO option was specifiedas NO, so no disk files will be opened with theO_DIRECT flag.

System Action: Server processing continues, but nodisk files will use the Direct I/O feature of AIX.

User Response: None

ANR7812E (HP-UX) Insufficient memory to bufferconsole input. The following input linewas discarded: discarded console input.

Explanation: An error occurs during an attempt toallocate a buffer to hold the specified console input.

System Action: The console input is discarded.

User Response: Ensure that there is sufficient pagingspace for HP-UX. It may be necessary to reduce themaximum number of client sessions by changing theMAXSESSIONS option in the server options file.

ANR7812E (Linux) Insufficient memory to bufferconsole input. The following input linewas discarded: discarded console input.



User Response: Ensure that there is sufficient pagingspace. It may be necessary to reduce the maximumnumber of client sessions by changing theMAXSESSIONS option in the server options file.

ANR7812E (Solaris) Insufficient memory to bufferconsole input. The following input linewas discarded: discarded console input.



User Response: Ensure that there is sufficient pagingspace for Sun Solaris. It may be necessary to reduce themaximum number of client sessions by changing theMAXSESSIONS option in the server options file.

ANR7813W (Linux) Unable to create a new childthread.



User Response: Ensure that sufficient swap space isavailable for Solaris. The amount of swap available canbe obtained by executing 'swap -l'. If the number offree blocks is low, you can add swap files while thesystem is running by executing 'mkfile' and then 'swap-a'. See the Solaris man pages on 'mkfile' and 'swap' formore details.

If the server has been started from a non-root user ID,ensure that the process limit per user is sufficient toaccomodate the server. You can tune the 'maxusers=##'parameter in the /etc/system file to increase thenumber of number of users that can be on the system

ANR7811I • ANR7813W (Linux)


at one time. This will also force the kernel to allocatemore memory/swap for user-processes.

A system reboot with the 'reconfigure' option isrequired for the new user settings to take effect. It maybe necessary to decrease the maximum number ofclient sessions by changing the MAXSESSIONS optionin the server options file.

ANR7813W (Solaris) Unable to create a new childthread.



User Response: Ensure that sufficient swap space isavailable for Solaris. The amount of swap available canbe obtain by executing ’swap -l’. If the number of freeblocks is low, you can add swap files while the systemis running by executing ’mkfile’ and then ’swap -a’. Seethe Solaris man pages on ’mkfile’ and ’swap’ for moredetails. If the server has been started from a non-rootuser ID, ensure that the Solaris process limit per user issufficient for the server. You can tune the ’maxusers=##’parameter in the /etc/system file to increase thenumber of number of users that can be on the systemat one time. This will also force the kernel to allocatemore memory/swap for user-processes. A systemreboot with the ’reconfigure’ option is required for thenew user settings to take effect. It may be necessary todecrease the maximum number of client sessions bychanging the MAXSESSIONS option in the serveroptions file.

ANR7820E Insufficient memory to buffer consoleinput; the following input line wasdiscarded: discarded console input.

Explanation: An error occurs during an attempt toallocate a buffer large enough to read console input.


User Response: Ensure that sufficient paging space isavailable for AIX. You may also use SMIT to determineif the number of applications is causing a memoryshortage. It may be necessary to decrease the maximumnumber of client sessions by changing theMAXSESSIONS option in the server options file.

ANR7820S (HP-UX) Server thread thread IDterminated in response to programabort.

Explanation: The thread has ended due to a programabort.

System Action: The server completes terminationprocessing.

User Response: Note the associated messages andcontact your service representative.

ANR7820S (Linux) Thread thread ID terminated inresponse to program abort.



User Response: Note the associated messages and callyour service representative.

ANR7820E (PASE) Insufficient memory to bufferconsole input; the following input linewas discarded: discarded console input.

Explanation: An error occurs during an attempt toallocate a buffer large enough to read console input.


User Response: Ensure that sufficient paging space isavailable for PASE. You may also use SMIT todetermine if the number of applications is causing amemory shortage. It may be necessary to decrease themaximum number of client sessions by changing theMAXSESSIONS option in the server options file.

ANR7820S (Solaris) Server thread thread IDterminated in response to programabort.



User Response: Note the associated messages and callyour service representative.

ANR7820W (Windows) Insufficient Space Availablefor file file name.

Explanation: The server was attempting to create a filewith the indicated name. There was insufficient spacefor the file on the disk.

System Action: Server processing continues. The filecreation request fails.

User Response: Specify a file name on a drive withsufficient space or change the space request to a valueconsistent with the drive.

ANR7821E Error reading from standard input.

Explanation: An error occurs during an attempt toread from standard input.

System Action: The console input thread isterminated.

ANR7813W (Solaris) • ANR7821E


User Response: Correct the standard input problemand restart the server.

ANR7821I (HP-UX) Server thread thread IDterminated in response to externalsignal.

Explanation: The thread has ended due to an externalsignal.



ANR7821I (Linux) Thread thread ID terminated inresponse to external signal.




ANR7821E (PASE) Error reading from standardinput.

Explanation: An error occurs during an attempt toread from standard input.

System Action: The console input thread isterminated.

User Response: Correct the standard input problemand restart the server.

ANR7821I (Solaris) Server thread thread IDterminated in response to externalsignal.




ANR7821W (Windows) Unable to create directorywhen creating volume file name.

Explanation: The server was attempting to create a filewith the indicated name. A new directory was beingcreated as well, but its creation failed.


User Response: Specify a file name in an existingdirectory or change the name request to specify adifferent directory name.

ANR7822E Error creating console input thread.




ANR7822I (HP-UX) Server thread thread IDterminated in response to servershutdown.

Explanation: The thread has ended due to a servershutdown.



ANR7822I (Linux) Thread thread ID terminated inresponse to server shutdown.




ANR7822E (PASE) Error creating console inputthread.




ANR7822I (Solaris) Server thread thread IDterminated in response to servershutdown.




ANR7822W (Windows) File Already exists whencreating volume file name.

Explanation: The server was attempting to create a filewith the indicated name. The file already exists.


User Response: Specify a new file name. The serverwill not use an existing file name when creating a file.

ANR7821I (HP-UX) • ANR7822W (Windows)


ANR7823E Insufficient memory for consoleinitialization.

Explanation: Unable to allocate enough memory forconsole initialization.



ANR7823S (Linux) Internal error internal errordetected.

Explanation: An internal error is detected duringserver initialization or operation.



ANR7823E (PASE) Insufficient memory for consoleinitialization.

Explanation: Unable to allocate enough memory forconsole initialization.



ANR7823W (Windows) Unable to create file file name.

Explanation: The server was attempting to create a filewith the indicated name. The system reported an errorin creating the file.

System Action: The server continues processing. Thefile creation request fails.

User Response: Specify a new file name.

ANR7824E Error loading Async I/O supportmodule.

Explanation: The server attempted to load the AsyncI/O support module, but the load failed. Refer toaccompanying error message for details on the loadfailure.

System Action: Server operation continues, butwithout Async I/O support.

User Response: Ensure that the correct supportmodule exists in the server bin directory and that theaio subsystem has been configured on AIX, and that

AIX was rebooted after the configuration.

ANR7824S (HP-UX) Server operation terminated.

Explanation: An error occurs that causes serveroperation to stop.



ANR7824S (Linux) Server operation terminated.




ANR7824E (PASE) Error loading Async I/O supportmodule.

Explanation: The server attempted to load the AsyncI/O support module, but the load failed. Refer toaccompanying messages for The reason for the failure.Two possible reasons for the failure are that the moduledoes not exist in the correct location or that you havenot enabled the aio subsystem under PASE.

System Action: Server operation continues, butwithout Async I/O support.

User Response: Ensure that the correct supportmodule exists in the server bin directory and that theaio subsystem has been configured on PASE, and thatPASE was rebooted after the configuration.

ANR7824S (Solaris) Server operation terminated.




ANR7824W (Windows) Unable to write volume filename.

Explanation: The server was attempting to create a filewith the indicated name. The server was able topartially write to the file before running out of space.

System Action: The server continues processing. Thefile creation request fails. The file is still present on thesystem.

User Response: Specify a new file name where thereis sufficient space.

ANR7823E • ANR7824W (Windows)


ANR7825E (Linux) Server unable to allocate a sharedmemory segment of size Client requestedshared memory size.

Explanation: A shared memory client has requested ashared memory segment size that Solaris is unable tofulfill.

System Action: Client is not allowed to logon

User Response: See the shared memory tuning guidefor Solaris (a Sun document). You may need to increasethe number/size of shared memory segments and/ormessage queues.

ANR7825E (Solaris) Server unable to allocate ashared memory segment of size Clientrequested shared memory size.

Explanation: A shared memory client has requested ashared memory segment size that Solaris is unable tofulfill.

System Action: Client is not allowed to logon

User Response: See the shared memory tuning guidefor Solaris (a Sun document). You may need to increasethe number/size of shared memory segments and/ormessage queues.

ANR7825W (Windows) Unable to create volume filename. Return code= return code.

Explanation: The server was attempting to create a filewith the indicated name. The attempt failed with theindicated return code. The return code is an internalcode from the server.


User Response: Specify a new file name. The returncode may also be provided to your servicerepresentative for interpretation.

ANR7826W (Windows) Creation of Volume file namefailed. Process was cancelled.

Explanation: The server was attempting to create a filewith the indicated name. The attempt was cancelled bya cancel process command.


User Response: The DEFINE command may bere-entered.

ANR7830E (Linux) Invalid RAW Partition Name: Avalid raw partition name is in the formof /dev/.../rdsk/.../* , where ... means 0 ormore directories.

Explanation: Use the proper format for specifying aRaw partition. The ... means zero or more directories.

System Action: Inform the user to use the right RAWpartition specification.

User Response: Have user reenter the RAW partitionwith the proper partition name.

ANR7830E (Solaris) Invalid RAW Partition Name: Avalid raw partition name is in the formof /dev/.../rdsk/.../* , where ... means 0 ormore directories.

Explanation: Use the proper format for specifying aRaw partition. The ... means zero or more directories.

System Action: Inform the user to use the right RAWpartition specification.

User Response: Have user reenter the RAW partitionwith the proper partition name.

ANR7831E (Linux) raw partition name has an existingfilesystem.

Explanation: The RAW partition specified has anexisting Solaris file system on it. Writing to thisPartition may/and most likely will destroy thisfilesystem.

System Action: Warn the user that an existingfilesystem for the raw partition specified may bedestroyed if written to.

User Response: Determine if user still wants the validfilesystem data. If not, user needs to destroy thefilesystem by either formatting the partition, create aprogram to destroy the filesystem header informationso that the server will not be able to detect thefilesystem header information, or rearrange the startingand ending blocks of a partition by using the Solarisformat() command. The user can read the format()function in the Sun manuals for further details onfilesystems.

ANR7831E (Solaris) raw partition name has an existingfilesystem.

Explanation: The RAW partition specified has anexisting Solaris file system on it. Writing to thispartition will most likely destroy this filesystem.

System Action: Warn the user that an existingfilesystem for the raw partition specified may bedestroyed if written to.

User Response: Determine if user still wants the validfilesystem data. If not, user needs to destroy the

ANR7825E (Linux) • ANR7831E (Solaris)


filesystem by either formatting the partition, create aprogram to destroy the filesystem header informationso that the server will not be able to detect thefilesystem header information, or rearrange the startingand ending blocks of a partition by using the Solarisformat() command. The user can read the format()function in the Sun manuals for further details onfilesystems.

ANR7832I The thread process ID terminated withexit code program exit code.

Explanation: The process has ended with theindicated exit code. This error is due to the problemcaused and indicated by a preceding message.



ANR7832E (Linux) raw partition name corresponds to aprotected filesystem, such as / or /usr.

Explanation: The RAW partition specified has anexisting file system on it. This filesystem is the / or/usr partition. If the SERVER writes to it, it will mostlikely crash the whole operating system.

System Action: Disallow access to this raw partition.

User Response: Have user specify another RAWpartition that is not the / or /usr. It may be possiblethat this is not the actual / or /usr partition of the bootdisk. Check, using the Solaris format() command, ifyour partition name tag is labeled incorrectly as / or/usr.

ANR7832I (PASE) The thread process ID terminatedwith exit code program exit code.

Explanation: The process has ended with theindicated exit code. This error is due to the problemcaused and indicated by a preceding message.



ANR7832E (Solaris) raw partition name corresponds toa protected filesystem, such as / or /usr.

Explanation: The RAW partition specified has anexisting file system on it. This filesystem is the / or/usr partition. If the SERVER writes to it, it will mostlikely crash the whole operating system.


User Response: Have user specify another RAWpartition that is not the / or /usr. It may be possiblethat this is not the actual / or /usr partition of the bootdisk. Check, using the Solaris format() command, if

your partition name tag is labeled incorrectly as / or/usr.

ANR7833S The process thread ID terminated inresponse to program abort.




ANR7833E (Linux) symbolic links has too manysymbolic links - the maximumallowable is 10.

Explanation: The file specified has too many symboliclinks. The server will follow at most 10 links beforeending this symbolic link name resolution.

System Action: Disallow access to this file.

User Response: Have the user specify the actual file,where the file is not a symbolic link. Using ls -l, onecan see if the file is a symbolic link.

ANR7833S (PASE) The process thread ID terminatedin response to program abort.




ANR7833E (Solaris) symbolic links has too manysymbolic links - the server onlysupports a maximum of 10.

Explanation: The file specified has too many symboliclinks. The server will follow at most 10 links beforeending this symbolic link name resolution.

System Action: Disallow access to this file

User Response: Have the user specify the actual file,where the file is not a symbolic link. Using ls -l, onecan see if the file is a symbolic link.

ANR7834I The thread thread ID terminated inresponse to external signal.






ANR7834E (Linux) Specified raw partition name rawpartition cannot contain the 0th diskcylinder.

Explanation: The raw partition specified has the 0thdisk cylinder. The server should not be allowed towrite into the 0th cylinder. If allowed, the disk labelwould be corrupted.


User Response: Have the system administrator changethe starting cylinder of this partition to a numbergreater than 0.

ANR7834I (PASE) The thread thread ID terminated inresponse to external signal.




ANR7834E (Solaris) Specified raw partition name rawpartition cannot contain the 0th diskcylinder.

Explanation: The raw partition specified has the 0thdisk cylinder. The server should not be allowed towrite into the 0th cylinder. It allowed, the disk labelwould be corrupted.

System Action: Disallow access to this raw partition

User Response: Have the system administrator changethe starting cylinder of this partition to a numbergreater than 0.

ANR7834I (Windows) The server thread thread ID (tidWindows NT thread ID) terminated inresponse to external signal.

Explanation: The thread has terminated due to anexternal signal.



ANR7835I The server thread thread ID terminatedin response to server shutdown.




ANR7835E (Linux) Specified raw partition name rawpartition is too big for this operatingsystem to handle.

Explanation: The raw partition specified has greaterthan 2GB and the operating system is running belowSolaris 2.6. Operating system below Solaris 2.6 cannothandle files natively more than 2GB. For operatingsystem that is at Solaris 2.6 or above, the limit is 1TB.


User Response: Have the system administrator changethe RAW partition size to be less than 2GB (4194303512-byte disk blocks) for Solaris 2.5.1 or below, lessthan 1TB (2147483647 512-byte disk blocks) for Solaris2.6 and above.

ANR7835I (PASE) The server thread thread IDterminated in response to servershutdown.




ANR7835E (Solaris) Specified raw partition name rawpartition is too big for this operatingsystem to handle.

Explanation: The raw partition specified has greaterthan 2GB and the operating system is running belowSolaris 2.6. Operating system below Solaris 2.6 cannothandle files natively more than 2GB. For operatingsystem that is at Solaris 2.6 or above, the limit is 1TB.

System Action: Disallow access to this raw partition

User Response: Have the system administrator changethe RAW partition size to be less than 2GB (4194303512-byte disk blocks) for Solaris 2.5.1 or below, lessthan 1TB (2147483647 512-byte disk blocks) for Solaris2.6 and above.

ANR7835I (Windows) The server thread thread ID (tidWindows NT thread ID) terminated inresponse to server shutdown.

Explanation: The thread has terminated due to aserver shutdown.



ANR7834E (Linux) • ANR7835I (Windows)


ANR7836S Server initialization terminated.

Explanation: An error occurs that causes serverinitialization to end.



ANR7836S (PASE) Server initialization terminated.

Explanation: An error occurs that causes serverinitialization to end.



ANR7837S Internal error internal error detected.



User Response: Contact your service representative.The user needs to extend the log file with dsmservextend log logname size when he gets ANR7837S,LOGSEG871 errors.

ANR7837S (PASE) Internal error internal errordetected.




ANR7837S (Windows) Internal error The internal errorthat was detected. detected.

Explanation: An internal error was detected duringserver initialization or operation.

System Action: Server operation will halt.


ANR7838S Server operation terminated.




ANR7838S (PASE) Server operation terminated.




ANR7841S Insufficient kernel memory available.

Explanation: An error occurs due to insufficient kernelmemory.



ANR7841S (PASE) Insufficient kernel memoryavailable.

Explanation: An error occurs due to insufficient kernelmemory.



ANR7842S Monitor kernel extension not initialized.

Explanation: The monitor kernel extension is notinitialized.



ANR7842S (PASE) Monitor kernel extension notinitialized.

Explanation: The monitor kernel extension is notinitialized.



ANR7843W Unable to determine real memory size.

Explanation: The server checks the amount of realmemory in the system to optimize use of storage in thedatabase buffer pool. The server uses Object DataManager (ODM) to determine how much real memoryis installed on the system. The routines used to callODM failed or were unable to return the real memorysize.

System Action: Server operation continues. The serverallows the data base buffer pool size to grow withougtaking into account real memory.

User Response: The server may need to run as a rootuser to obtain this information.

ANR7836S • ANR7843W


ANR7843W (HP-UX) Unable to determine realmemory size.

Explanation: The server checks the amount of realmemory in the system to optimize use of storage in thedatabase buffer pool. The routines used to obtain thisinformation returned a failing return code or wereunable to return the real memory size.



ANR7843W (Linux) Unable to determine realmemory size.

Explanation: The server checks the amount of realmemory in the system to optimize use of storage in thedatabase buffer pool. The server uses Object DataManager (ODM) to determine how much real memoryis installed on the system. The routine s used to callODM failed or were unable to return the real memorysize.



ANR7843W (PASE) Unable to determine realmemory size.

Explanation: The server checks the amount of realmemory in the system to optimize use of storage in thedatabase buffer pool. The server uses Object DataManager (ODM) to determine how much real memoryis installed on the system. The routines used to callODM failed or were unable to return the real memorysize.



ANR7843W (Solaris) Unable to determine realmemory size.




ANR7843W (Windows) Unable to determine realmemory size.




ANR7849I Server operation terminated - kernelextension has been reset.

Explanation: The kernel extension has beenreinitialized by the server in response to a previouscondition for which a message has been issued.



ANR7849I (PASE) Server operation terminated -kernel extension has been reset.

Explanation: The kernel extension has beenreinitialized by the server in response to a previouscondition for which a message has been issued.



ANR7850I The process process ID has terminated onsignal signal number (signal name).

Explanation: The specified process has ended due tothe specified signal.



ANR7850I (PASE) The process process ID hasterminated on signal signal number (signalname).

Explanation: The specified process has ended due tothe specified signal.



ANR7843W (HP-UX) • ANR7850I (PASE)


ANR7851S Error resetting handler for signal signalnumber (signal name).

Explanation: An error occurs resetting the specifiedsignal handler.



ANR7851S (PASE) Error resetting handler for signalsignal number (signal name).

Explanation: An error occurs resetting the specifiedsignal handler.



ANR7852I (Windows) The current process affinitymask is: 0xThe process affinity mask..

Explanation: The server is running on the processorsindicated by the mask.



ANR7853W (Windows) Could not obtain the currentprocess affinity mask. Reason: NT returncode..

Explanation: A problem was encounterd whileobtaining the current process affinity.



ANR7854W (Windows) The process affinity mask(0xAffinity mask.) specified indsmserv.opt is out of range.

Explanation: The affinity mask value was out ofrange.



ANR7855W (Windows) Could not set new processaffinity mask. Reason: NT return code.

Explanation: A problem was encounterd in setting anew process affinity mask.



ANR7856W (Windows) The affinity mask (0xNTreturn code.) was set to a value other thanwhat was requested

Explanation: A new affinity mask was set but onverification it was found not to match what wasrequested.



ANR7860W Insufficient Space Available for file filename.

Explanation: The server was attempting to create a filewith the indicated name. There was insufficient spacefor the file in the filesystem.


User Response: Specify a file name in a filesystemwith sufficient space or change the space request to avalue consistent with the filesystem.

ANR7860W (HP-UX) Insufficient Space Available forfile file name.




ANR7860W (Linux) Insufficient Space Available forfile file name.




ANR7860W (PASE) Insufficient Space Available forfile file name.



User Response: Specify a file name in a filesystem

ANR7851S • ANR7860W (PASE)


with sufficient space or change the space request to avalue consistent with the filesystem.

ANR7860W (Solaris) Insufficient Space Available forfile file name.




ANR7861W Unable to create directory when creatingvolume file name.



User Response: Specify a file name in an existingdirectory or or change the name request to specify adifferent directory name.

ANR7861W (HP-UX) Unable to create directory whencreating volume file name.




ANR7861W (Linux) Unable to create directory whencreating volume file name.




ANR7861W (PASE) Unable to create directory whencreating volume file name.




ANR7861W (Solaris) Unable to create directory whencreating volume file name.




ANR7862W File Already exists when creatingvolume file name.




ANR7862W (HP-UX) File Already exists whencreating volume file name.




ANR7862W (Linux) File Already exists when creatingvolume file name.




ANR7860W (Solaris) • ANR7862W (Linux)


ANR7862W (PASE) File Already exists when creatingvolume file name.




ANR7862W (Solaris) File Already exists whencreating volume file name.




ANR7863W Unable to create file file name.




ANR7863W (HP-UX) Unable to create file file name.




ANR7863W (Linux) Unable to create file file name.




ANR7863W (PASE) Unable to create file file name.




ANR7863W (Solaris) Unable to create file file name.




ANR7864W Unable to write volume file name.




ANR7864W (HP-UX) Unable to write volume filename.




ANR7864W (Linux) Unable to write volume file name.




ANR7864W (PASE) Unable to write volume file name.




ANR7862W (PASE) • ANR7864W (PASE)


ANR7864W (Solaris) Unable to write volume filename.




ANR7865W Unable to create volume file name.Return code=return code.

Explanation: The server was attempting to create a filewith the indicated name. The attempt failed with theindicated return code. The return code is an the serverinternal code.



ANR7865W (HP-UX) Unable to create volume filename. Return code=return code.

Explanation: The server was attempting to create a filewith the indicated name. The attempt failed with theindicated return code. The return code is a serverinternal code.



ANR7865W (Linux) Unable to create volume filename. Return code=return code.

Explanation: The server was attempting to create a filewith the indicated name. The attempt failed with theindicated return code. The return code is an internalcode from the server.



ANR7865W (PASE) Unable to create volume file name.Return code=return code.

Explanation: The server was attempting to create a filewith the indicated name. The attempt failed with theindicated return code. The return code is an the serverinternal code.



ANR7865W (Solaris) Unable to create volume filename. Return code=return code.

Explanation: The server was attempting to create a filewith the indicated name. The attempt failed with theindicated return code. The return code is a serverinternal code.



ANR7866W Creation of Volume file name failed.Process was cancelled.




ANR7866W (HP-UX) Creation of Volume file namefailed. Process was cancelled.




ANR7866W (Linux) Creation of Volume file namefailed. Process was cancelled.



ANR7864W (Solaris) • ANR7866W (Linux)



ANR7866W (PASE) Creation of Volume file namefailed. Process was cancelled.




ANR7866W (Solaris) Creation of Volume file namefailed. Process was cancelled.




ANR7870W Unable to initialize odm query. Errormessage from odm is odm message.

Explanation: The server uses the AIX Object DataManager (ODM) to check information about AIX. Forexample, the server uses ODM to detemine how muchreal memory is installed on the system. The routineused to initialize an ODM query failed. ODM returnedan error message as indicated.

System Action: Server operation continues. The servermakes assumptions concerning information it could notobtain.


ANR7870W (PASE) Unable to initialize odm query.Error message from odm is odm message.

Explanation: The server uses the PASE Object DataManager (ODM) to check information about PASE. Forexample, the server uses ODM to detemine how muchreal memory is installed on the system. The routineused to initialize an ODM query failed. ODM returnedan error message as indicated.



ANR7871W Unable to complete odm query. Errormessage from odm is odm message.

Explanation: The server uses the AIX Object DataManager (ODM) to check information about AIX. Forexample, the server uses ODM to detemine how muchreal memory is installed on the system. The routineused to perform and ODM query failed. ODM returnedan error message as indicated.



ANR7871W (PASE) Unable to complete odm query.Error message from odm is odm message.

Explanation: The server uses the PASE Object DataManager (ODM) to check information about PASE. Forexample, the server uses ODM to detemine how muchreal memory is installed on the system. The routineused to perform and ODM query failed. ODM returnedan error message as indicated.



ANR8190I HTTP driver ready for connection withclients on port port number.

Explanation: The server is now able to accept sessionswith clients that use the HTTP protocol on theindicated port number.



ANR8190I (HP-UX) HTTP driver ready forconnection with clients on port portnumber.




ANR8190I (Linux) HTTP driver ready for connectionwith clients on port port number.



ANR7866W (PASE) • ANR8190I (Linux)



ANR8190I (PASE) HTTP driver ready for connectionwith clients on port port number.




ANR8190I (Solaris) HTTP driver ready forconnection with clients on port portnumber.




ANR8191W HTTP driver unable to initialize due toerror in using port port, reason codereason code.

Explanation: While initializing HTTP communications,the server has failed to connect to a master TCP/IPsocket on which to listen for clients. The reason code isthe return code from the TCP/IP bind API.

System Action: Server operation continues, but theserver cannot accept sessions from administrativeclients using HTTP protocol.

User Response: Ensure that no other application isusing the port number specified in the server optionsfile with the HTTPPORT option. If TCP/IP is also inuse for client sessions, ensure that the same portnumber is not specified for both TCP/IP and HTTPcommunications. This may be done by issuing theTCP/IP netstat -s command. If the server is broughtdown and then started immediately, you may be withinthe TCP/IP one minute timeout period for portreusage. Bring down the server, wait one minute, andthen restart the server. If that does not work, it may benecessary to restart Windows NT.

ANR8191W (HP-UX) HTTP driver unable toinitialize due to error in using Port port,reason code reason code.



User Response: Ensure that no other application isusing the port number specified in the server optionsfile with the HTTPPORT option. If TCP/IP is also inuse for client sessions, ensure that the same portnumber is not specified for both TCP/IP and HTTPcommunications. This may be done by issuing theTCP/IP netstat -s command. If the server is broughtdown and then started immediately, you may be withinthe TCP/IP one minute timeout period for portreusage. Bring down the sever, wait one minute, andthen restart the server. If that does not work, it may benecessary to restart HP-UX.

ANR8191W (Linux) HTTP driver unable to initializedue to error in using port port, reasoncode reason code.



User Response: Ensure that no other application isusing the port number specified in the server optionsfile with the TCPPORT or TCPADMINPORT options. IfTCP/IP is also in use for client sessions, ensure that thesame port number is not specified for both TCP/IP andHTTP communications. This may be done by issuingthe TCP/IP netstat -s command. If the server is broughtdown and then started immediately, you may be withinthe TCP/IP one minute timeout period for portreusage. Bring down the sever, wait one minute, andthen restart the server.

ANR8191W (PASE) HTTP driver unable to initializedue to error in using Port port, reasoncode reason code.



User Response: Ensure that no other application isusing the port number specified in the server optionsfile with the HTTPPORT option. If TCP/IP is also inuse for client sessions, ensure that the same portnumber is not specified for both TCP/IP and HTTPcommunications. This may be done by issuing theTCP/IP netstat -s command. If the server is broughtdown and then started immediately, you may be withinthe TCP/IP one minute timeout period for portreusage. Bring down the server, wait one minute, andthen restart the server. If that does not work, it may benecessary to restart Windows NT.

ANR8190I (PASE) • ANR8191W (PASE)


ANR8191W (Solaris) HTTP driver unable toinitialize due to error in BINDing toPort port, reason code reason code.



User Response: Ensure that no other application isusing the port number specified in the server optionsfile with the PORT option. If TCP/IP is also in use forclient sessions, ensure that the same port number is notspecified for both TCP/IP and HTTP communications.This may be done by issuing the TCP/IP netstat -scommand. If the server is brought down and thenstarted immediately, you may be within the TCP/IPone minute timeout period for port reusage. Bringdown the sever, wait one minute, and then restart theserver.

ANR8192I (HP-UX) HTTPS driver ready forconnection with clients on port portnumber.

Explanation: The server is now able to accept sessionswith clients that use the HTTPS protocol on theindicated port number.



ANR8192I (Linux) HTTPS driver ready forconnection with clients on port portnumber.




ANR8192I (Solaris) HTTPS driver ready forconnection with clients on port portnumber.




ANR8193W (HP-UX) HTTPS driver unable toinitialize due to error in using Port port,reason code reason code.

Explanation: While initializing HTTPScommunications, the server has failed to connect to amaster TCP/IP socket on which to listen for clients.The reason code is the return code from the TCP/IPbind API.

System Action: Server operation continues, but theserver cannot accept sessions from administrativeclients using HTTPS protocol.

User Response: Ensure that no other application isusing the port number specified in the server optionsfile with the HTTPSPORT option. If TCP/IP is also inuse for client sessions, ensure that the same portnumber is not specified for both TCP/IP and HTTPScommunications. This may be done by issuing theTCP/IP netstat -s command. If the server is broughtdown and then started immediately, you may be withinthe TCP/IP one minute timeout period for portreusage. Bring down the sever, wait one minute, andthen restart the server. If that does not work, it may benecessary to restart HP-UX.

ANR8193W (Linux) HTTPS driver unable toinitialize due to error in using port port,reason code reason code.



User Response: Ensure that no other application isusing the port number specified in the server optionsfile with the HTTPSPORT option. If TCP/IP is also inuse for client sessions, ensure that the same portnumber is not specified for both TCP/IP and HTTPScommunications. This may be done by issuing theTCP/IP netstat -s command. If the server is broughtdown and then started immediately, you may be withinthe TCP/IP one minute timeout period for portreusage. Bring down the sever, wait one minute, andthen restart the server. If that does not work, it may benecessary to restart Solaris

ANR8193W (Solaris) HTTPS driver unable toinitialize due to error in BINDing toPort port, reason code reason code.





User Response: Ensure that no other application isusing the port number specified in the server optionsfile with the PORT option. If TCP/IP is also in use forclient sessions, ensure that the same port number is notspecified for both TCP/IP and HTTPS communications.This may be done by issuing the TCP/IP netstat -scommand. If the server is brought down and thenstarted immediately, you may be within the TCP/IPone minute timeout period for port reusage. Bringdown the sever, wait one minute, and then restart theserver. If that does not work, it may be necessary torestart Solaris

ANR8194W (HP-UX) HTTPS driver unable toinitialize due to error in secure datainitialization, reason code reason code.

Explanation: While initializing HTTPScommunications, the server has failed initialize of thesecure data certificate information.


User Response: Ensure the keyring file name andkeyring file password are correct and that the passwordhas not expired. Check for earlier SKIT messages whichmay indicate the real problem. Replace keyring ifnecessary and re-start the server.

ANR8200I TCP/IP driver ready for connection withclients on port port number.

Explanation: The server is now able to accept sessionswith clients that use the TCP/IP protocol on theindicated port number.



ANR8200I (HP-UX) TCP/IP driver ready forconnection with clients on port portnumber.

Explanation: The server is now able to accept sessionswith clients using the TCP/IP protocol on the indicatedport number.



ANR8200I (Linux) TCP/IP driver ready forconnection with clients on port portnumber.




ANR8200I (PASE) TCP/IP driver ready forconnection with clients on port portnumber.

Explanation: The server is now able to accept sessionswith clients that use the TCP/IP protocol on theindicated port number.



ANR8200I (Solaris) TCP/IP driver ready forconnection with clients on port portnumber.




ANR8200I (Windows) TCP/IP driver ready forconnection with clients on port portnumber.

Explanation: The server can now accept sessions withclients using the TCP/IP protocol on the indicated portnumber.



ANR8201W Unable to initialize TCP/IP driver -insufficient memory.

Explanation: Because the operating system rejects amemory allocation request, the server cannot startcommunications through TCP/IP.

System Action: Server operation continues, but theserver cannot accept sessions from clients using theTCP/IP protocol.


ANR8194W (HP-UX) • ANR8201W


ANR8201E (HP-UX) Unable to initialize TCP/IPdriver - socket creation failed; error errorcode.

Explanation: The server is unable to initialize theTCP/IP driver due to a socket creation error.

System Action: Server operation continues, butTCP/IP support is inoperative.

User Response: Ensure that TCP/IP is operational onyour system by using the ping command with yourTCP/IP address as a target. If TCP/IP is not active onyour system, you must activate it; then halt and restartthe server.

ANR8201E (Linux) Unable to initialize TCP/IP driver- socket creation failed; error error code.




ANR8201W (PASE) Unable to initialize TCP/IPdriver - insufficient memory.




ANR8201E (Solaris) Unable to initialize TCP/IPdriver - socket creation failed; error errorcode.




ANR8201W (Windows) Unable to initialize TCP/IPdriver - insufficient memory.

Explanation: The server is unable to communicate byway of TCP/IP. A memory allocation request has beenrejected by the operating system.


User Response: Ensure that there is sufficient spacefor the Windows paging file. Click on the system iconin the Windows control panel and then click on thevirtual memory button. Refer to the online help forinstructions on how to increase the amount of virtualmemory.

ANR8202W Unable to initialize TCP/IP driver - errorcreating acceptor socket. Reason codereason code.

Explanation: Because TCP/IP rejects a request for asocket on which to listen, the server cannot startcommunications through TCP/IP.


User Response: Ensure that TCP/IP is operational onyour system by using the ping command with yourTCP/IP address as a target. If TCP/IP is not started,use the HALT command from a server prompt to stopthe server and restart it.

ANR8202E (HP-UX) Unable to initialize TCP/IPdriver - socket bind operation for portTCP port number failed; error error code.

Explanation: The server is unable to initialize theTCP/IP driver due to a socket binding error.


User Response: Ensure that TCP/IP is operational onyour system by using the ping command with yourTCP/IP address as a target. If TCP/IP is not active onyour system, you must activate it; then halt and restartthe server. This message may also result from morethan one server running on the same machine with thesame TCP/IP port number. Make sure that thedsmserv.opt file TCPPort option is different for eachserver.

ANR8202E (Linux) TCP/IP driver unable to initializedue to error in using port TCP portnumber; error error code.


System Action: Server operation continues, but

ANR8201E (HP-UX) • ANR8202E (Linux)


TCP/IP support is inoperative.

User Response: Ensure that TCP/IP is operational onyour system by using the ping command with yourTCP/IP address as a target. If TCP/IP is not active onyour system, you must activate it; then halt and restartthe server. This message may also result from morethan one server running on the same machine with thesame TCP/IP port number. Make sure that thedsmserv.opt file TCPPort option is different for eachserver. Make sure TCPPORT and HTTPORT andTCPADMINPORT do not specify or default to the samevalues.

ANR8202W (PASE) Unable to initialize TCP/IPdriver - error creating acceptor socket.Reason code reason code.

Explanation: Because TCP/IP rejects a request for asocket on which to listen, the server cannot startcommunications through TCP/IP.


User Response: Ensure that TCP/IP is operational onyour system by using the ping command with yourTCP/IP address as a target. If TCP/IP is not started,use the HALT command from a server prompt to stopthe server and restart it.

ANR8202E (Solaris) Unable to initialize TCP/IPdriver - socket bind operation for portTCP port number failed; error error code.



User Response: Ensure that TCP/IP is operational onyour system by using the ping command with yourTCP/IP address as a target. If TCP/IP is not active onyour system, you must activate it; then halt and restartthe server. This message may also result from morethan one server running on the same machine with thesame TCP/IP port number. Make sure that thedsmserv.opt file TCPPort option is different for eachserver.

ANR8202W (Windows) Unable to initialize TCP/IPdriver - error creating acceptor socket.

Explanation: The server is unable to communicate byway of TCP/IP. TCP/IP has rejected a request for asocket on which the server listens.


User Response: Ensure that TCP/IP is operational on

your system by using the ping command with yourTCP/IP address as a target. If TCP/IP is not started,issue the HALT command to stop the server, and thenrestart the server.

ANR8203W Unable to establish TCP connection -accept error.

Explanation: The server cannot accept a client sessiondue to a failure in TCP/IP.


User Response: Ensure that TCP/IP is operational onyour system by using the ping command with yourTCP/IP address as a target. If TCP/IP is not started,use the HALT command from a server prompt toterminate the server and restart it.

ANR8203E (HP-UX) Unable to initialize TCP/IPdriver - listen operation failed; errorerror code.

Explanation: The server is unable to initialize theTCP/IP driver due to a socket listen error.



ANR8203E (Linux) Unable to initialize TCP/IP driver- listen operation failed; error error code.




ANR8203W (PASE) Unable to establish TCPconnection - accept error.

Explanation: The server cannot accept a client sessiondue to a failure in TCP/IP.


User Response: Ensure that TCP/IP is operational onyour system by using the ping command with your



TCP/IP address as a target. If TCP/IP is not started,use the HALT command from a server prompt toterminate the server and restart it.

ANR8203E (Solaris) Unable to initialize TCP/IPdriver - listen operation failed; errorerror code.




ANR8203W (Windows) Unable to establish TCPconnection - accept error.

Explanation: The server cannot accept a client sessiondue to failure in TCP/IP.


User Response: Ensure that TCP/IP is operational onyour system by using the ping command with yourTCP/IP address as a target. If TCP/IP is not started,issue the HALT command to stop the server, and thenrestart the server.

ANR8204W Unable to establish TCP connection -insufficient memory.

Explanation: The server cannot accept a client sessiondue to a memory allocation request failure.

System Action: Server operation continues, but thesession request for this session fails.

User Response: Ensure that sufficient paging space isavailable for AIX. You may also use SMIT to determineif the number of applications is causing a memoryshortage. You may also decrease the maximum numberof sessions that the server can accept with theMAXSESSIONS option in the server options file.

ANR8204E (HP-UX) Unable to initialize TCP/IPdriver - thread creation failed.

Explanation: The server is unable to initialize theTCP/IP driver due to an error creating a server thread.


User Response: This error often results from a lack ofmemory. Ensure that your system has sufficient pagingspace to support the current activities.

ANR8204E (Linux) Unable to initialize TCP/IP driver- thread creation failed.




ANR8204W (PASE) Unable to establish TCPconnection - insufficient memory.



User Response: Ensure that sufficient paging space isavailable for PASE. You may also use SMIT todetermine if the number of applications is causing amemory shortage. You may also decrease the maximumnumber of sessions that the server can accept with theMAXSESSIONS option in the server options file.

ANR8204E (Solaris) Unable to initialize TCP/IPdriver - thread creation failed.




ANR8204W (Windows) Unable to establish TCPconnection - insufficient memory.

Explanation: The server is unable to accept a clientsession due to a memory allocation request failure.


User Response: Ensure that there is sufficient spacefor the Windows paging file. Click on the system iconin the Windows control panel and then click on thevirtual memory button. Refer to the online help forinstructions on how to increase the amount of virtualmemory. You may also wish to cut down on themaximum number of sessions that the server canaccept with the MAXSESSIONS option in the serveroptions file.

ANR8203E (Solaris) • ANR8204W (Windows)


ANR8205W Unable to establish TCP connection -server HALT in progress.

Explanation: The server cannot accept a client sessiondue to server HALT processing that is in progress.



ANR8205E (HP-UX) Terminating TCP/IP driver -accept operation failed; error error code.

Explanation: The server is unable to initialize theTCP/IP driver due to a socket accept error.



ANR8205E (Linux) Terminating TCP/IP driver -socket accept operation failed; error errorcode.




ANR8205W (PASE) Unable to establish TCPconnection - server HALT in progress.




ANR8205E (Solaris) Terminating TCP/IP driver -socket accept operation failed; error errorcode.



User Response: Ensure that TCP/IP is operational onyour system by using the ping command with your

TCP/IP address as a target. If TCP/IP is not active onyour system, you must activate it; then halt and restartthe server.

ANR8205W (Windows) Unable to establish TCPconnection - server HALT in progress.

Explanation: The server is unable to accept a clientsession due to server HALT processing that is inprogress.



ANR8206W Socket socket (session session number)closed abruptly.

Explanation: The server detects that the indicatedsession on the specified TCP/IP socket is closed outsideof the server.

System Action: Server operation continues, but thesession is ended.


ANR8206E (HP-UX) Unable to establish TCP/IPsession - invalid host address IP hostaddress (port port number).

Explanation: The server is unable to establish asession because the designated address or port numberis not valid.


User Response: Ensure that the specified host name isvalid and is accessible over the network. If theTCPCLIENTPort option is specified for the remotesystem, ensure it does not conflict with anotherapplication.

ANR8206E (Linux) Unable to establish TCP/IPsession - invalid host address IP hostaddress (port port number).




ANR8205W • ANR8206E (Linux)


ANR8206W (PASE) Socket socket (session sessionnumber) closed abruptly.

Explanation: The server detects that the indicatedsession on the specified TCP/IP socket is closed outsideof the server.

System Action: Server operation continues, but thesession is ended.


ANR8206E (Solaris) Unable to establish TCP/IPsession - invalid host address IP hostaddress (port port number).




ANR8206I (Windows) TCP/IP administrative driverready for connection with clients onport port number.

Explanation: The server can now accept sessions withadministrative clients using the TCP/IP protocol on theindicated port number.



ANR8207W TCP/IP driver unable to initialize due tosocket initialization error.

Explanation: While initializing TCP/IPcommunications, the server fails to set up an interfacewith TCP/IP.


User Response: Ensure that TCP/IP has been startedand is active on your system. You may issue theTCP/IP ping command to your own address to verifythat TCP/IP is both started and active.

ANR8207E (HP-UX) Unable to establish TCP/IPsession with IP host address due tomemory shortage.

Explanation: The server is unable to establish asession because of a memory shortage condition.


User Response: Ensure that your system has sufficientpaging space to support the current level of systemactivities.

ANR8207E (Linux) Unable to establish TCP/IPsession with IP host address due tomemory shortage.




ANR8207W (PASE) TCP/IP driver unable to initializedue to socket initialization error.

Explanation: While initializing TCP/IPcommunications, the server fails to set up an interfacewith TCP/IP.



ANR8207E (Solaris) Unable to establish TCP/IPsession with IP host address due tomemory shortage.




ANR8207W (Windows) TCP/IP driver unable toinitialize due to socket initializationerror.

Explanation: While initializing TCP/IPcommunications, the server has failed to set up aninterface with TCP/IP for Windows.


User Response: Ensure that TCP/IP is properlyinstalled on your system. Ensure that TCP/IP has beenstarted on your system. Issue the TCP/IP pingcommand to your own address to verify that TCP/IP isboth installed and active.

ANR8206W (PASE) • ANR8207W (Windows)


ANR8208W TCP/IP driver unable to initialize due toerror in using port port, reason codereason code.

Explanation: While initializing TCP/IPcommunications, the server fails to connect to a mastersocket on which to listen for clients. The reason code isthe return code from the TCP/IP bind API.


User Response: Ensure that no other application isusing the port number specified in the server optionsfile with the HTTPPORT option by issuing the TCP/IPnetstat command. If HTTP is also in use for clientsessions, ensure that the same port number is notspecified for both TCP/IP and HTTP communications.If the server was brought down and client sessionswere active, it may be necessary to terminate the clientsessions on the client systems before the port can befreed.

ANR8208E (HP-UX) Unable to establish TCP/IPsession with IP host address - socketcreation failed; error error code.

Explanation: The server is unable to establish asession because of a socket creation error.



ANR8208E (Linux) Unable to establish TCP/IPsession with IP host address - socketcreation failed; error error code.




ANR8208W (PASE) TCP/IP driver unable to initializedue to error in using Port port, reasoncode reason code.

Explanation: While initializing TCP/IPcommunications, the server fails to connect to a mastersocket on which to listen for clients. The reason code isthe return code from the TCP/IP bind API.

System Action: Server operation continues, but the

server cannot accept sessions from clients using theTCP/IP protocol.

User Response: Ensure that no other application isusing the port number specified in the server optionsfile with the TCPPORT option by issuing the TCP/IPnetstat command. If HTTP is also in use for clientsessions, ensure that the same port number is notspecified for both TCP/IP and HTTP communications.If the server was brought down and client sessionswere active, it may be necessary to terminate the clientsessions on the client systems before the port can befreed.

ANR8208E (Solaris) Unable to establish TCP/IPsession with IP host address - socketcreation failed; error error code.




ANR8208W (Windows) TCP/IP driver unable toinitialize due to error in using Port port,reason code reason code.

Explanation: While initializing TCP/IPcommunications, the server has failed to connect to amaster socket on which to listen for clients. The reasoncode is the return code from the TCP/IP bind API.


User Response: Ensure that no other application isusing the port number specified in the server optionsfile with the TCPPORT option. If HTTP is also in usefor client sessions, ensure that the same port number isnot specified for both TCP/IP and HTTPcommunications. This may be done by issuing theTCP/IP netstat -s command. If the server is broughtdown and then started immediately, you may be withinthe TCP/IP one minute timeout period for portreusage. Bring down the server, wait one minute, andthen restart the server. If that does not work, it may benecessary to restart Windows.

ANR8209W TCP/IP driver unable to initialize due toerror in LISTENing on the specifiedPort, reason code reason code.

Explanation: While attempting to listen for sessionrequests from clients using TCP/IP, TCP/IP returns anerror. The reason code is the return code from theTCP/IP listen API.



System Action: Server operation continues, but theserver cannot accept additional sessions from clientsusing the TCP/IP protocol.

User Response: Ensure that TCP/IP is runningproperly by issuing the TCP/IP netstat -s and pingcommands to other nodes on your network. It may bepossible to bring the server down and restart it toallow additional client sessions to start.

ANR8209E (HP-UX) Unable to establish TCP/IPsession with IP host address - connectionrefused.

Explanation: The server is unable to establish asession because the remote system refused theconnection request.


User Response: Ensure that the specified remotesystem is operational and is properly configured to runTCP/IP. Ensure that the client options file specifies thecorrect TCPServeraddress and TCPPort of the serveryou are attempting to contact.

ANR8209E (Linux) Unable to establish TCP/IPsession with IP host address - connectionrefused.




ANR8209W (PASE) TCP/IP driver unable to initializedue to error in LISTENing on thespecified Port, reason code reason code.




ANR8209E (Solaris) Unable to establish TCP/IPsession with IP host address - connectionrefused.




ANR8209W (Windows) TCP/IP driver unable toinitialize due to error in LISTENing onthe specified Port, reason code reasoncode.



User Response: Ensure that TCP/IP is runningproperly. This may be done by issuing the TCP/IPnetstat -s and ping commands to other nodes on yournetwork. It may be possible to correct this condition byrestarting the server.

ANR8210W TCP/IP driver is terminating due toerror in accepting a new session, reasoncode reason code.

Explanation: While attempting to accept a sessionrequest from a client using TCP/IP, TCP/IP returns anerror. The reason code is the return code from theTCP/IP accept API.


User Response: Ensure that TCP/IP is runningproperly. This may be done by issuing the TCP/IPnetstat -s and ping commands to other nodes on yournetwork. It may be possible to bring the server downand restart it to allow additional client sessions to start.

ANR8210E (HP-UX) Unable to establish TCP/IPsession with IP host address - connectionrequest timed out.

Explanation: The server is unable to establish asession because the remote system did not respond tothe connection request.


ANR8209E (HP-UX) • ANR8210E (HP-UX)


User Response: Ensure the following:

v The specified remote system is operational and isproperly configured to run TCP/IP.

v The client options file specifies the correctTCPServeraddress and TCPPort of the server you areattempting to contact.

v Necessary gateways and routers are functioningproperly.

ANR8210E (Linux) Unable to establish TCP/IPsession with IP host address - connectionrequest timed out.







ANR8210W (PASE) TCP/IP driver is terminating dueto error in accepting a new session,reason code reason code.




ANR8210E (Solaris) Unable to establish TCP/IPsession with IP host address - connectionrequest timed out.







ANR8210W (Windows) TCP/IP driver is terminatingdue to error in accepting a new session,reason code reason code.




ANR8211W TCP/IP driver is terminating due toerror in creating a new thread.

Explanation: The server cannot initialize due to theinability to create a new thread of execution.

System Action: Server operation continues, butTCP/IP communications is inoperative.

User Response: The most likely cause is a lack ofmemory. Ensure that sufficient paging space is availablefor AIX. You may also use SMIT to determine if thenumber of applications is causing a memory shortage.You may also decrease the maximum number ofsessions that the server can accept with theMAXSESSIONS option in the server options file.

ANR8211E (HP-UX) Unable to establish TCP/IPsession with IP host address -system/network unreachable.

Explanation: The server is unable to establish asession because the remote system or network isunreachable.


User Response: Ensure that the specified remotesystem is operational and is properly configured to runTCP/IP. Also, ensure that necessary gateways androuters are functioning properly.

ANR8210E (Linux) • ANR8211E (HP-UX)


ANR8211E (Linux) Unable to establish TCP/IPsession with IP host address -system/network unreachable.




ANR8211W (PASE) TCP/IP driver is terminating dueto error in creating a new thread.



User Response: The most likely cause is a lack ofmemory. Ensure that sufficient paging space is availablefor PASE. You may also use SMIT to determine if thenumber of applications is causing a memory shortage.You may also decrease the maximum number ofsessions that the server can accept with theMAXSESSIONS option in the server options file.

ANR8211E (Solaris) Unable to establish TCP/IPsession with IP host address -system/network unreachable.




ANR8211W (Windows) TCP/IP driver is terminatingdue to error in creating a new thread.

Explanation: The server cannot initialize due itsinability to create a new thread of execution.


User Response: The most likely cause is a lack ofmemory. Ensure that there is sufficient space for theWindows paging file. Click on the system icon in theWindows NT control panel and then click on thevirtual memory button. Refer to the online help forinstructions on how to increase the amount of virtualmemory. You may also wish to cut down on themaximum number of sessions that the server can

accept with the MAXSESSIONS option in the serveroptions file.

ANR8212W Unable to resolve address for node name.

Explanation: The server attempts to obtain a TCP/IPaddress for the indicated node name. The attempt isunsuccessful.

System Action: The attempt to communicate with theindicated node fails. Server operation continues.

User Response: Ensure that the node name is properlyspecified and that it is accessible over the network. Usethe TCP/IP ping command for this purpose.

ANR8212E (HP-UX) Unable to establish TCP/IPsession with IP host address - connectfailed; error error code.

Explanation: The server is unable to establish asession because of a connection error.


User Response: Ensure that the specified remotesystem is operational and is properly configured to runTCP/IP.

ANR8212E (Linux) Unable to establish TCP/IPsession with IP host address - connectfailed; error error code.




ANR8212W (PASE) Unable to resolve address fornode name.




ANR8212E (Solaris) Unable to establish TCP/IPsession with IP host address - connectfailed; error error code.






ANR8212W (Windows) Unable to resolve address fornode name.




ANR8213W Session open with node name timed out.

Explanation: The server attempts to contact theindicated node name. The attempt is unsuccessful.

System Action: The attempt to communicate with theindicated node fails.


ANR8213E (HP-UX) Session Session identifier aborteddue to send error; error error code.

Explanation: The session between the server and thespecified client system experienced a disruptive errorsending data.

System Action: The session with the remote system isended.


ANR8213E (Linux) Session Session identifier aborteddue to send error; error error code.

Explanation: The session between the server and thespecified client system experienced a fatal error sendingdata.



ANR8213W (PASE) Session open with node nametimed out.




ANR8213E (Solaris) Session Session identifier aborteddue to send error; error error code.

Explanation: The session between the server and thespecified client system experienced a fatal error sendingdata.



ANR8213W (Windows) Session open with node nametimed out.




ANR8214E Session open with IP host address faileddue to connection refusal.




ANR8214E (HP-UX) Session Session identifier aborteddue to zero-length message.

Explanation: The session between the server and thespecified client system experienced a disruptive errorreceiving data.



ANR8212W (Windows) • ANR8214E (HP-UX)


ANR8214E (Linux) Session Session identifier aborteddue to zero-length message.

Explanation: The session between the server and thespecified client system experienced a fatal errorreceiving data.



ANR8214E (PASE) Session open with IP host addressfailed due to connection refusal.




ANR8214E (Solaris) Session Session identifier aborteddue to zero-length message.




ANR8214E (Windows) Session open with IP hostaddress failed due to connection refusal.




ANR8215W Session open with IP host address failedas unreachable.

Explanation: The server is unable to establish asession because the remote system is unreachable.


User Response: Ensure that the IP host address isproperly specified and that it is accessible over thenetwork. Use the TCP/IP ping command for thispurpose.

ANR8215E (HP-UX) Session Session identifier aborteddue to receive error; error error code.

Explanation: The session between the server and thespecified client system experienced a disruptive errorreceiving data.



ANR8215E (Linux) Session Session identifier aborteddue to receive error; error error code.




ANR8215W (PASE) Session open with IP host addressfailed as unreachable.




ANR8215E (Solaris) Session Session identifier aborteddue to receive error; error error code.






ANR8215W (Windows) Session open with IP hostaddress failed as unreachable.




ANR8216W Error sending data on socket socketnumber. Reason return code.

Explanation: The server experiences an error returncode from TCP/IP while sending data over theindicated socket. This may be a normal event if eitherside of the connection is abruptly ended.

System Action: The session is ended. Server operationcontinues.

User Response: If the session is ended as a result ofintentionally stopping either the client or server, noresponse is required. Otherwise, ensure that the clientand server can communicate through such means asTelnet or FTP applications, which are part of theTCP/IP suite.

ANR8216E (HP-UX) Unable to establish TCP/IPsession with IP host address due to threadcreation error.

Explanation: The server is unable to establish asession because of an error creating a thread.



ANR8216E (Linux) Unable to establish TCP/IPsession with IP host address due to threadcreation error.




ANR8216W (PASE) Error sending data on socketsocket number. Reason return code.




ANR8216E (Solaris) Unable to establish TCP/IPsession with IP host address due to threadcreation error.




ANR8216W (Windows) Error sending data on socketsocket number. Reason return code.




ANR8217W Error receiving data on socket socketnumber. Reason return code.

Explanation: The server experiences an error returncode from TCP/IP while receiving data on theindicated socket. This may be a normal event if eitherside of the connection is abruptly ended.



ANR8215W (Windows) • ANR8217W


ANR8217W (HP-UX) TCP/IP driver is unable to setthe window size to TCPWindowsize forclient client. The default value will beused.

Explanation: The server cannot set the window sizefor the indicated client to the requested size shown.The server uses the default window size for theindicated session. There may be a lack of memory forTCP/IP buffers.

System Action: Server operation continues and thesession continues with the default window size.

User Response: Retry the session with a smallerwindow size in the options file. Issue the QUERYOPTION command to determine the setting of theserver TCPWindowsize.

ANR8217W (Linux) Unable to initialize TCP/IPdriver - insufficient memory.



User Response: Ensure that sufficient paging space isavailable for Solaris. You may also use ps -ef todetermine if the number of applications is causing amemory shortage. It may be necessary to decrease themaximum number of client sessions by changing theMAXSESSIONS option in the server options file.

ANR8217W (PASE) Error receiving data on socketsocket number. Reason return code.




ANR8217W (Solaris) Unable to initialize TCP/IPdriver - insufficient memory.



server cannot accept sessions from clients using theTCP/IP protocol.

User Response: Ensure that sufficient paging space isavailable for Solaris. You may also use ps -ef todetermine if the number of applications is causing amemory shortage. It may be necessary to decrease themaximum number of client sessions by changing theMAXSESSIONS option in the server options file.

ANR8217W (Windows) Error receiving data onsocket socket number. Reason return code.




ANR8218W Session terminated when no data wasread on socket socket number.

Explanation: The server is unable to read data on theindicated socket. This may be a normal event if eitherside of the connection is abruptly ended.



ANR8218W (HP-UX) TCP/IP driver is unable to usethe TCP/IP NODELAY option for clientclient.

Explanation: The server cannot set TCP/IP NODELAYfor the indicated client. The session proceeds withTCP/IP Delay processing in effect. This causes TCP/IPto buffer data prior to sending it to clients.

System Action: Server operation continues and thesession continues with the delay processing on.

User Response: Further details for use in contactingyour service representative can be obtained by issuingthe following trace commands from an administrativesession or from the server console (properadministrative authority is required): TRACE ENABLETCPINFO TRACE BEGIN tcptrace.out. After a sessionstarts and displays message ANR8218W, issue the

ANR8217W (HP-UX) • ANR8218W (HP-UX)


following commands: TRACE FLUSH TRACE END.This will create trace data in file tcptrace.out and willterminate the trace. This file should be supplied to yourserver representative on request.

ANR8218W (Linux) Unable to resolve address fornode name.




ANR8218W (PASE) Session terminated when no datawas read on socket socket number.

Explanation: The server is unable to read data on theindicated socket. This may be a normal event if eitherside of the connection is abruptly ended.



ANR8218W (Solaris) Unable to resolve address fornode name.




ANR8218W (Windows) Session terminated when nodata read on socket socket number.

Explanation: The server cannot read on the indicatedsocket. This may be a normal event if either side of theconnection is abruptly ended.


User Response: If the session is ended as a result ofintentionally stopping either the client or server, noresponse is required. Otherwise, ensure that the clientand server can communicate through such means as

Telnet or FTP applications, which are part of theTCP/IP suite.

ANR8219W TCP/IP driver is unable to accept a newsession with client at address TCP/IPaddress due to an error in creating a newthread.

Explanation: The server cannot accept a client sessionwith the client at the indicated address due to aninability to create a new thread.

System Action: Server operation continues, the sessionrequest fails.

User Response: The most likely cause is lack ofmemory. Ensure that sufficient paging space is availablefor AIX. You may also use SMIT to determine if thenumber of applications is causing a memory shortage.You may also decrease the maximum number ofsessions that the server can accept with theMAXSESSIONS option in the server options file.

ANR8219W (HP-UX) Unable to initialize TCP/IPdriver - insufficient memory.



User Response: Ensure that sufficient paging space isavailable for HP-UX. You may also use SMIT todetermine if the number of applications is causing amemory shortage. It may be necessary to decrease themaximum number of client sessions by changing theMAXSESSIONS option in the server options file.

ANR8219W (Linux) Unable to establish TCPconnection - insufficient memory.



User Response: Ensure that sufficient paging space isavailable for Solaris. You may also use 'swap -l' todetermine the amount of swap available. You may alsodecrease the maximum number of sessions that theserver can accept with the MAXSESSIONS option inthe server options file.

ANR8218W (Linux) • ANR8219W (Linux)


ANR8219W (PASE) TCP/IP driver is unable to accepta new session with client at addressTCP/IP address due to an error in creatinga new thread.



User Response: The most likely cause is lack ofmemory. Ensure that sufficient paging space is availablefor PASE. You may also use SMIT to determine if thenumber of applications is causing a memory shortage.You may also decrease the maximum number ofsessions that the server can accept with theMAXSESSIONS option in the server options file.

ANR8219W (Solaris) Unable to establish TCPconnection - insufficient memory.



User Response: Ensure that sufficient paging space isavailable for Solaris. You may also use ’swap -l’ todetermine the amount of swap available. You may alsodecrease the maximum number of sessions that theserver can accept with the MAXSESSIONS option inthe server options file.

ANR8219W (Windows) TCP/IP driver is unable toaccept a new session due to error increating a new thread.

Explanation: The server cannot accept a client sessiondue to the inability to create a new thread.


User Response: The most likely cause is a lack ofmemory. Ensure that there is sufficient space for theWindows paging file. Click on the system icon in theWindows NT control panel and then click on thevirtual memory button. Refer to the online help forinstructions on how to increase the amount of virtualmemory. You may also wish to to cut down on themaximum number of sessions that the server canaccept with the MAXSESSIONS option in the serveroptions file.

ANR8220W TCP/IP driver is unable to set thewindow size to TCPWindowsize for clientclient. The default value will be used.

Explanation: The server cannot set the window sizefor the indicated client to the requested size shown.The server uses the default window size for the

indicated session. There may be a lack of memory forTCP/IP buffers.



ANR8220W (HP-UX) Unable to establish TCPconnection - insufficient memory.



User Response: Ensure that sufficient paging space isavailable for HP-UX. You may also use SMIT todetermine if the number of applications is causing amemory shortage. You may also decrease the maximumnumber of sessions that the server can accept with theMAXSESSIONS option in the server options file.

ANR8220W (Linux) TCP/IP driver is unable to setthe window size to TCPWindowsize forclient client. The default value will beused.




ANR8220W (PASE) TCP/IP driver is unable to set thewindow size to TCPWindowsize for clientclient. The default value will be used.






ANR8220W (Solaris) TCP/IP driver is unable to setthe window size to TCPWindowsize forclient client. The default value will beused.




ANR8220W (Windows) TCP/IP driver is unable tocontact node name due to an outputsocket initialization error.

Explanation: The server attempts to contact theindicated node name. The attempt is unsuccessful dueto the inability to initialize a local socket.


User Response: Ensure that TCP/IP is operatingproperly on this node and that it can communicateremotely. Use the TCP/IP ping command for thispurpose.

ANR8221W TCP/IP driver is unable to use theTCP/IP NODELAY option for clientclient.



User Response: Further details for use in contactingyour service representative can be obtained by issuingthe following trace commands from an administrativesession or from the server console (properadministrative authority is required): TRACE ENABLETCPINFO TRACE BEGIN. After a session starts anddisplays message ANR8221W, issue the commandsTRACE FLUSH TRACE END. This will create tracedata in file tcptrace.out and will terminate the trace.This file should be supplied to your servicerepresentative on request.

ANR8221I (HP-UX) TCP/IP administrative driverready for connection with clients onport port number.




ANR8221W (Linux) TCP/IP driver is unable to usethe TCP/IP NODELAY option for clientclient.

Explanation: The server cannot set TCP/IP NODELAYfor the indicated client. The session proceeds withTCP/IP delay processing in effect. This causes TCP/IPto buffer data prior to sending it to clients.

System Action: Server operation continues and thesession continues with delay processing on.

User Response: Further details for use whencontacting your service representative can be obtainedby issuing the following trace commands from anadministrative session or from the console (properadministrative authority is required): TRACE ENABLETCPINFO TRACE BEGIN tcptrace.out. After a sessionstarts and displays message ANR8221W, issue thefollowing commands: TRACE FLUSH TRACE END.This will create trace data in file tcptrace.out and willterminate the trace. This file should be supplied to yourservice representative on request.

ANR8221W (PASE) TCP/IP driver is unable to usethe TCP/IP NODELAY option for clientclient.



User Response: Further details for use in contactingyour service representative can be obtained by issuingthe following trace commands from an administrativesession or from the server console (properadministrative authority is required): TRACE ENABLETCPINFO TRACE BEGIN. After a session starts anddisplays message ANR8221W, issue the commandsTRACE FLUSH TRACE END. This will create tracedata in file tcptrace.out and will terminate the trace.This file should be supplied to your servicerepresentative on request.

ANR8220W (Solaris) • ANR8221W (PASE)


ANR8221W (Solaris) TCP/IP driver is unable to usethe TCP/IP NODELAY option for clientclient.



User Response: Further details for use in contactingyour service representative can be obtained by issuingthe following trace commands from an administrativesession or from the server console (properadministrative authority is required): TRACE ENABLETCPINFO TRACE BEGIN tcptrace.out After a sessionstarts and displays message ANR8221W, issue thefollowing commands: TRACE FLUSH TRACE ENDThis will create trace data in file tcptrace.out and willterminate the trace. This file should be supplied to yourservice representative on request.

ANR8221W (Windows) TCP/IP driver is unable toset the window size to TCPWindowsizefor session session, client client. Thedefault value will be used.

Explanation: The server cannot set the window sizefor the indicated session/client to the requested sizeshown. The server will use the default window size forthe indicated session.


User Response: The most likely cause is lack ofmemory for TCP/IP buffers. You may retry with asmaller TCP window size in the options file. You canissue the QUERY OPTION command to display thecurrent setting of the TCP window size.

ANR8222W TCP/IP driver is unable to set thewindow size to TCPWindowsize for theserver master socket. The default valuewill be used.

Explanation: The server cannot set the window sizefor the socket on which the server listens to therequested size shown. The server uses the defaultwindow size for listening for sessions. There may be alack of memory for TCP/IP buffers.

System Action: Server operation continues with thedefault window size.

User Response: Restart the server with a smallerwindow size in the options file if necessary. Issue theQUERY OPTION command to determine the setting ofthe server TCPWindowsize.

ANR8222W (HP-UX) TCP/IP administrative driverwas unable to initialize due to errorusing Port port, reason code reason code.

Explanation: While initializing TCP/IPcommunications for administrative sessions, the serverhas failed to connect to a master socket to listen forclients. The reason code is the return code from theTCP/IP bind API.

System Action: Server operation continues, but theserver cannot accept administrative sessions fromclients using the TCP/IP protocol. This also includesserver-server sessions, storage agent to server sessions,and library client to server sesssions.

User Response: Ensure that no other application isusing the port number specified in the server optionsfile with the TCPADMINPORT option. If HTTP is alsoin use for client sessions, ensure that the same portnumber is not specified for both TCP/IP and HTTPcommunications. To do this, issue the TCP/IP netstatcommand.If the server was brought down and clientsessions were active, it can be necessary to terminatethe client sessions on the client systems before the portcan be freed.

ANR8222W (Linux) Unable to establish TCPconnection - server HALT in progress.




ANR8222W (PASE) TCP/IP driver is unable to set thewindow size to TCPWindowsize for theserver master socket. The default valuewill be used.




ANR8222W (Solaris) Unable to establish TCPconnection - server HALT in progress.





session request for this session fails.


ANR8222W (Windows) TCP/IP driver is unable touse the TCP/IP NODELAY option forclient client.



User Response: Further details for use in contactingyour service representative can be obtained by issuingthe following trace commands from an administrativesession or from the server console (properadministrative authority is required): TRACE ENABLETCPINFO TRACE BEGIN tcptrace.out After a sessionstarts and displays message ANR8222W, issue thefollowing commands: TRACE FLUSH TRACE ENDThis will create trace data in file tcptrace.out and willterminate the trace. This file should be supplied to yourservice representative on request.

ANR8223W Unable to connect to remote systemRemoteSystem due to unexpected returncode ReturnCode

Explanation: The server was unable to connect to aremote system due to an unexpected return code fromthe connect Application Programming Interface.Common return code are handled with specificmessages. This return code was unexpected.

System Action: Server operation continues but theconnection to the remote system fails.

User Response: TCP/IP return code are listed in file/usr/include/sys/errno.h and may provide a pointerto the underlying problem. /usr/include/sys/errno.his part of fileset bos.adt.include.

ANR8223W (Linux) TCP/IP driver is unable to accepta new session with client at addressTCP/IP address due to an error in creatinga new thread.



User Response: The most likely cause is lack ofmemory. Ensure that sufficient paging space is availablefor Solaris. You may also use ps -ef to determine if thenumber of applications is causing a memory shortage.You may also decrease the maximum number ofsessions that the server can accept with the

MAXSESSIONS option in the server options file.

ANR8223W (PASE) Unable to connect to remotesystem RemoteSystem due to unexpectedreturn code ReturnCode

Explanation: The server was unable to connect to aremote system due to an unexpected return code fromthe connect Application Programming Interface.Common return code are handled with specificmessages. This return code was unexpected.

System Action: Server operation continues but theconnection to the remote system fails.

User Response: TCP/IP return code are listed in file/usr/include/sys/errno.h and may provide a pointerto the underlying problem. /usr/include/sys/errno.his part of fileset bos.adt.include.

ANR8223W (Solaris) TCP/IP driver is unable toaccept a new session with client ataddress TCP/IP address due to an error increating a new thread.



User Response: The most likely cause is lack ofmemory. Ensure that sufficient paging space is availablefor Solaris. You may also use ps -ef to determine if thenumber of applications is causing a memory shortage.You may also decrease the maximum number ofsessions that the server can accept with theMAXSESSIONS option in the server options file.

ANR8223W (Windows) Failed to connect to system ataddress address port port.

Explanation: The server attempted to contact theindicated node name at the specified port. The attemptis unsuccessful. The target port is not valid at the targetnode.


User Response: Ensure that the node name still hasTCP/IP running and that the client is active inSCHEDULE mode. If the server is attempting contactwith the SNMP subagent, ensure that the hostname andport number for the subagent is correct in the serveroptions file.

ANR8222W (Windows) • ANR8223W (Windows)


ANR8224W TCP/IP Administrative driver wasunable to initialize due to error in usingport port, reason code reason code.

Explanation: While initializing TCP/IPcommunications for administrative sessions, the serverhas failed to connect to a master socket on which tolisten for clients. The reason code is the return codefrom the TCP/IP bind API.

System Action: Server operation continues, but theserver cannot accept administrative sessions fromclients using the TCP/IP protocol. This also includesserver to server sessions, storage agent to serversessions, and library client to server sesssions.

User Response: Ensure that no other application isusing the port number specified in the server optionsfile with the TCPADMINPORT, TCPPORT, orHTTPPORT options. If HTTP is also in use for clientsessions, ensure that the same port number is notspecified for both TCP/IP and HTTP communications.This may be done by issuing the TCP/IP netstatcommand.If the server was brought down and clientsessions were active, it may be necessary to terminatethe client sessions on the client systems before the portcan be freed.

ANR8224W (Linux) TCP/IP driver is unable to setthe window size to TCPWindowsize forthe server master socket. The defaultvalue will be used.




ANR8224W (PASE) TCP/IP Administrative driverwas unable to initialize due to error inusing Port port, reason code reason code.


System Action: Server operation continues, but theserver cannot accept administrative sessions fromclients using the TCP/IP protocol. This also includesserver-server sessions, storage agent to server sessions,and library client-server sesssions.

User Response: Ensure that no other application is

using the port number specified in the server optionsfile with the TCPADMINPORT option. If HTTP is alsoin use for client sessions, ensure that the same portnumber is not specified for both TCP/IP and HTTPcommunications. This may be done by issuing theTCP/IP netstat command.If the server was broughtdown and client sessions were active, it may benecessary to terminate the client sessions on the clientsystems before the port can be freed.

ANR8224W (Solaris) TCP/IP driver is unable to setthe window size to TCPWindowsize forthe server master socket. The defaultvalue will be used.




ANR8224W (Windows) TCP/IP Administrative driverwas unable to initialize due to error inusing Port port, reason code reason code.


System Action: Server operation continues, but theserver cannot accept administrative sessions fromclients using the TCP/IP protocol. This also includesserver to server sessions, storage agent to serversessions, and library client to server sessions.

User Response: Ensure that no other application isusing the port number specified in the server optionsfile with the TCPADMINPORT option. If HTTP is alsoin use for client sessions, ensure that the same portnumber is not specified for both TCP/IP and HTTPcommunications. Do this by issuing the TCP/IP netstat-s command. If the server is brought down and thenstarted immediately, you can be within the TCP/IP oneminute timeout period for port reusage. Bring downthe server, wait one minute, and then restart the server.If that does not work, it may be necessary to restartWindows.

ANR8224W • ANR8224W (Windows)


ANR8225I TCP/IP administrative driver ready forconnection with clients on port portnumber.




ANR8225W (Linux) TCP/IP Administrative driverwas unable to initialize due to error inusing port port, reason code reason code.



User Response: Ensure that no other application isusing the port number specified in the server optionsfile with the TCPADMINPORT, TCPPORT, orHTTPPORT options. If HTTP is also in use for clientsessions, ensure that the same port number is notspecified for both TCP/IP and HTTP communications.To do this, issue the TCP/IP netstat command.If theserver was brought down and client sessions wereactive, it may be necessary to terminate the clientsessions on the client systems before the port can befreed.

ANR8225I (PASE) TCP/IP administrative driverready for connection with clients onport port number.




ANR8225I (Solaris) TCP/IP administrative driverready for connection with clients onport port number.




ANR8226I (Linux) TCP/IP administrative driverready for connection with clients onport port number.




ANR8226W (Solaris) TCP/IP Administrative driverwas unable to initialize due to error inusing port port, reason code reason code.

Explanation: The TCP/IP administrative driver wasunable to initialize due to an error in running the BINDAPI to port port, reason code reason code.


System Action: Server operation continues, but theserver cannot accept administrative sessions fromclients using the TCP/IP protocol. This also includesserver-server sessions, storage agent to server sessions,and library client-server sesssions.

User Response: Ensure that no other application isusing the port number specified in the server optionsfile with the TCPADMINPORT or TCPPORT options. IfHTTP is also in use for client sessions, ensure that thesame port number is not specified for both TCP/IP andHTTP communications. To do this, issue the TCP/IPnetstat command. If the server was brought down andclient sessions were active, it can be necessary toterminate the client sessions on the client systemsbefore the port can be freed.

ANR8226W (Windows) Unable to initializeNETBIOS driver on adapter networkadapter number.

Explanation: The server cannot obtain sufficientNETBIOS resources to initialize communications on theindicated network adapter.

System Action: Server operation continues, but theserver will not accept sessions from clients that use theNETBIOS protocol.

User Response: Ensure that NETBIOS is configuredon the system. Ensure that all NETBIOS resources arenot already in use. If the LAN Server or LANRequester application is running, you have NETBIOSconfigured. In that case, starting the server prior tostarting LAN Server or LAN Requester may allow theserver to obtain the necessary NETBIOS resources.

ANR8225I • ANR8226W (Windows)


ANR8227W (Windows) NETBIOS connectionterminated - insufficient memory,network adapter network adapter number.

Explanation: The server cannot listen for clientsessions on the specified network adapter due to amemory allocation request failure.

System Action: Server operation continues, but thesessions will not be accepted on the specified adapter.Other network adapters remain unaffected.

User Response: The most likely cause is a lack ofmemory. Ensure that there is sufficient space for theWindows paging file. Click on the system icon in theWindows NT control panel and then click on thevirtual memory button. Refer to the online help forinstructions on how to increase the amount of virtualmemory.

ANR8228W (Windows) NETBIOS connectionterminated - server HALT in progress.




ANR8229W (Windows) Unable to add server nameserver name to adapter network adapternumber.

Explanation: The server cannot initializecommunications processing using the NETBIOSprotocol on the indicated network adapter because theserver name cannot be added as a NETBIOS name onthe adapter.

System Action: Server operation continues, but clientsessions from clients using the NETBIOS protocol willnot be accepted on this adapter. Other adapters are notaffected.

User Response: The most likely cause for this messageis the presence of another system on the network thatis using the same name for NETBIOS communications.This may be another server or client or a LANRequester node. Changing or adding theNETBIOSNAME option for this adapter in your serveroptions file and restarting the server may allow thisadapter to be used with NETBIOS communications.

ANR8230W (Windows) Insufficient memory to startNETBIOS session on adapter networkadapter number.

Explanation: The server cannot accept a client sessiondue to a memory allocation request failure on thespecified adapter.

System Action: Server operation continues, but thesession request fails.

User Response: The most likely cause is a lack ofmemory. Ensure that there is sufficient space for theWindows paging file. Click on the system icon in theWindows NT control panel and then click on thevirtual memory button. Refer to the online help forinstructions on how to increase the amount of virtualmemory. You may also wish to cut down on themaximum number of sessions that the server canaccept with the MAXSESSIONS or theNETBIOSSESSIONS option, or both, in the serveroptions file.

ANR8231W (Windows) Unable to create thread toaccept NETBIOS sessions.


System Action: Server operation continues, butNETBIOS communications is inoperative.


ANR8232W (Windows) Unable to create thread tolisten for NETBIOS sessions on adapternetwork adapter number.

Explanation: The server cannot initialize due to theinability to create a new thread of execution to monitorthe indicated network adapter.

System Action: Server operation continues, butNETBIOS communications is inoperative on theindicated adapter. Other adapters remain unaffected.




ANR8233W (Windows) Unable to create thread tohandle NETBIOS session session numberon adapter network adapter number.

Explanation: The server cannot start a new clientsession on the indicated adapter due to an inability tostart a separate thread of execution for the indicatedsession.

System Action: Server operation continues, but thissession request fails.


ANR8235W (Windows) Requested number ofNETBIOS sessions are not available onadapter network adapter number,proceeding with available sessions.

Explanation: The server cannot acquire the requestednumber of NETBIOS sessions for the indicated adapter.The server attempts to acquire the number of NETBIOSsessions as indicated by the NETBIOSSESSIONSparameter of the server options file or, if this option isnot specified, by the MAXSESSIONS option.

System Action: Server operation continues, but themaximum number of NETBIOS sessions is limited tothe number of sessions that are acquired.

User Response: Ensure that the required number ofNETBIOS resources are not already in use. If the LANServer or LAN Requester application is running, youhave NETBIOS configured. In that case, starting theserver prior to starting LAN Server or LAN Requestermay allow the server to obtain the requested NETBIOSresources.

ANR8236W (Windows) Failure while listening forNETBIOS sessions on adapter networkadapter number, NETBIOS listen returncode=listen return code.

Explanation: The server cannot listen for NETBIOSsessions on the indicated adapter. The indicated listenreturn code was received from the NETBIOS listen API.If the return code is 24, (hex 18), the listen is retried.

System Action: Server operation continues. If thereturn code is 24 (hex 18), a new listen is setup becausereturn code 24 indicates a temporary failure. Otherwise,no additional NETBIOS sessions will start using the

indicated adapter until the problem is corrected and theserver is restarted.

User Response: A NETBIOS listen failure is anindication of a network problem, an adapter problem,or a NETBIOS configuration problem. The followingsystem configuration and system environment listenreturn codes (in hex) and resolution actions for a listenfailure are found in the IBM Local Area NetworkTechnical Reference:

Return Code Description11 The local session table is full. The

maximum number of sessions are inuse. Change NETBIOS configuration toincrease the maximum number ofsessions.

19 Name conflict. Ensure that the ServerNETBIOS name is not in use elsewhereon the network.

22 There are too many commands pending.The maximum number of sessions are inuse. Change NETBIOS configuration toincrease the maximum number ofsessions.

35 The operating system resources areexhausted. A reboot is probablyrequired.

ANR8260I (Windows) Named Pipes driver ready forconnection with clients.

Explanation: The server is now able to accept sessionswith clients using the Named Pipes protocol.



ANR8261W (Windows) Named Pipes connectionterminated - insufficient memory.


System Action: Server operation continues. NamedPipes communications is inoperative.

User Response: The most likely cause is a lack ofmemory. Ensure that there is sufficient space for theWindows paging file. Click on the system icon in theWindows NT control panel and then click on thevirtual memory button. Refer to the online help forinstructions on how to increase the amount of virtualmemory. You may also wish to cut down on themaximum number of sessions that the server canaccept with the MAXSESSIONS option in the serveroptions file.



ANR8262W (Windows) Named Pipes driver isterminating due to error in creating anew thread.


System Action: Server operation continues, butNamed Pipes communications is inoperative.

User Response: The most likely cause is a lack ofmemory. Ensure that there is sufficient space for theWindows paging file. Click on the system icon in theWindows NT control panel and then click on thevirtual memory button. Refer to the online help forinstructions on how to increase the amount of virtualmemory. You may also wish to cut down on themaximum number of sessions that the server canaccept with the MAXSESSIONS option in the serveroptions file.

ANR8263W (Windows) Error sending data on NamedPipes, session session number.WriteFileReturn code is return code.

Explanation: The server experiences an error returncode from the WriteFile Windows NT API whilewriting data to Named Pipes over the indicatedsession. This may be a normal event if either side of theconnection is abruptly ended.


User Response: If the session is ended as a result ofintentionally stopping either the client or server, noresponse is required.

ANR8264W (Windows) Error reading data on NamedPipes, session session number. ReadFilereturn code is return code.

Explanation: The server experiences an error returncode from the ReadFile Windows API while readingdata from Named Pipes in the indicated session. Thismay be a normal event if either side of the connectionis ended abruptly.



ANR8265W (Windows) Error open Named PipesNamed Pipes name, CreateNamedPipereturn code return code.

Explanation: The server experiences an error returncode when trying to open the indicated Named Pipesname for Named Pipes communication with a client.The return code shown is returned by the WindowsCreateNamedPipe API.

System Action: The session is ended. Server operationcontinues. Named Pipes communications is inoperative.

User Response: The server may have run out of filehandles. Stop and restart the server to reenable NamedPipes communications. It is not normal to run out offile handles. A system or logic error may be theunderlying cause.

ANR8266W (Windows) Error accepting connectionon Named Pipes Named Pipes name,ConnectNamedPipe return code returncode.

Explanation: The server experiences an error returncode when trying to complete a connection on theindicated Named Pipes name for Named Pipescommunication with a client. The return code shown isreturned by the Windows ConnectNamedPipe API.


User Response: A system problem may be preventinguse of Named Pipes. Stop and restart the server toreenable Named Pipes communications.

ANR8267W (Windows) Error initializing a securitydescriptor for Named Pipes Named Pipesname, reason: System message.

Explanation: The server experiences an error returncode when trying to initialize the indicated NamedPipe for Named Pipes communication with a client.The reason shown is returned by the WindowsFormatMessage API.


User Response: Administrator Privileges are required.Login using an account wit h Administrator privilegesand restart the server to reenable Named Pipescommunications.

ANR8268W (Windows) Named Pipe communicationswere not enabled due to an errorlooking up the following Windowsgroup name: Windows group name. Usethe Windows User manager to add thespecified group. Members of the groupwill then use Windows unified logon toaccess the server over Named pipes.

Explanation: The server experiences an error returncode when trying to initialize the indicated NamedPipe for Named Pipes communication with a client.The system could not find the Windows Account namespecified in the server options file.


User Response: To use Windows unified logon specify



the name of a valid Windows account or group name.Restart the server to reenable Named Pipescommunications.

ANR8269W (Windows) Error opening Named PipeNamed Pipes name, reason: System message.

Explanation: The server experiences an error returncode when trying to open the indicated Named Pipename for Named Pipes communication with a client.The reason shown is returned by the WindowsFormatMessage API.


User Response: Consider the reason text and takeappropriate action. Stop and restart the server toreenable Named Pipes communications.

ANR8273I (Windows) Shared memory driver readyfor connection with clients.

Explanation: The server is now able to accept sessionswith clients using the shared memory protocol.



ANR8274W (Windows) Shared memorycommunications driver is terminatingdue to error in creating a new thread.


System Action: Server operation continues, but sharedmemory communications is inoperative.

User Response: The most likely cause is a lack ofmemory. Ensure that there is sufficient space for theWindows paging file. Click on the system icon in theWindows NT control panel and then click on thevirtual memory button. Refer to the online help forinstructions on how to increase the amount of virtualmemory.

ANR8275W (Windows) Shared memory connectionterminated - insufficient memory.


System Action: Server operation continues. Sharedmemory communications is inoperative.

User Response: The most likely cause is a lack ofmemory. Ensure that there is sufficient space for theWindows paging file. Click on the system icon in theWindows NT control panel and then click on thevirtual memory button. Refer to the online help forinstructions on how to increase the amount of virtualmemory. You may also wish to cut down on the

maximum number of sessions that the server canaccept with the MAXSESSIONS option in the serveroptions file.

ANR8276W (Windows) Shared memory connectionterminated - unable to initialize. Keychannel key, Reason: reason code.

Explanation: The server cannot accept a client sessiondue being unable to initialize shared memory.

System Action: Server operation continues. Sharedmemory communications are inoperative.

User Response: Try a different shared memorysession.

ANR8280I (Windows) HTTP driver ready forconnection with clients on port portnumber.

Explanation: The server can now accept sessions withclients using the HTTP protocol on the indicated portnumber.



ANR8281W (Windows) HTTP driver unable toinitialize due to error in BINDing toPort port, reason code reason code.



User Response: Ensure that no other application isusing the port number specified in the server optionsfile with the PORT option. If TCP/IP is also in use forclient sessions, ensure that the same port number is notspecified for both TCP/IP and HTTP communications.This may be done by issuing the TCP/IP netstat -scommand. If the server is brought down and thenstarted immediately, you may be within the TCP/IPone minute timeout period for port reusage. Bringdown the sever, wait one minute, and then restart theserver. If that does not work, it may be necessary torestart Windows.

ANR8282I (HP-UX) SNMP driver ready forconnection with subagent on port portnumber.

Explanation: The server can now accept sessions withSNMP subagents on the indicated port number.


ANR8269W (Windows) • ANR8282I (HP-UX)



ANR8282I (Linux) SNMP driver ready for connectionwith subagent on port port number.




ANR8282I (Solaris) SNMP driver ready forconnection with subagent on port portnumber.




ANR8282I (Windows) HTTPS driver ready forconnection with clients on port portnumber.

Explanation: The server can now accept sessions withclients using the HTTPS protocol on the indicated portnumber.



ANR8283W (HP-UX) SNMP driver unable toinitialize due to error in using Port port,reason code reason code.

Explanation: While initializing TCP/IPcommunications, the server has failed to connect to amaster TCP/IP socket on which to listen to SNMPsubagents. The reason code is the return code from theTCP/IP bind API.

System Action: Server operation continues, but theserver cannot accept sessions from SNMP subagents torun macro commands.

User Response: Ensure that no other application isusing the port number specified in the server optionsfile with the SNMPSUBAGENT PORT option. IfTCP/IP or HTTP is also in use for client sessions,ensure that the same port number is not specified forTCP/IP or HTTP communications and SNMPcommunications. This may be done by issuing theTCP/IP netstat command.

ANR8283W (Linux) SNMP driver unable to initializedue to error in BINDing to Port port,reason code reason code.

Explanation: While initializing TCP/IPcommunications, the server has failed to connect to a

master TCP/IP socket on which to listen to SNMPsubagents. The reason code is the return code from theTCP/IP bind API.


User Response: Ensure that no other application isusing the port number specified in the server optionsfile with the PORT option. If TCP/IP or HTTP is also inuse for client sessions, ensure that the same portnumber is not specified for TCP/IP or HTTPcommunications and SNMP communications.

ANR8283W (Solaris) SNMP driver unable toinitialize due to error in BINDing toPort port, reason code reason code.



User Response: Ensure that no other application isusing the port number specified in the server optionsfile with the PORT option. If TCP/IP or HTTP is also inuse for client sessions, ensure that the same portnumber is not specified for TCP/IP or HTTPcommunications and SNMP communications.

ANR8283W (Windows) HTTPS driver unable toinitialize due to error in BINDing toPort port, reason code reason code.



User Response: Ensure that no other application isusing the port number specified in the server optionsfile with the PORT option. If TCP/IP is also in use forclient sessions, ensure that the same port number is notspecified for both TCP/IP and HTTPS communications.This may be done by issuing the TCP/IP netstat -scommand. If the server is brought down and thenstarted immediately, you may be within the TCP/IPone minute timeout period for port reusage. Bringdown the sever, wait one minute, and then restart theserver. If that does not work, it may be necessary torestart Windows.

ANR8282I (Linux) • ANR8283W (Windows)


ANR8284E The Shared Memory CommunicationsProtocol could not initialize.

Explanation: The server was unable to initialize theShared Memory Communications Protocol due to anerror.

System Action: Server operation continues withoutShared Memory Communications.

User Response: Examine previous error messages forthe cause of the failure.

ANR8284E (PASE) The Shared MemoryCommunications Protocol could notinitialize.




ANR8284E (Solaris) The Shared MemoryCommunications Protocol could notinitialize.




ANR8284W (Windows) HTTPS driver unable toinitialize due to error in secure datainitialization, reason code reason code.

Explanation: While initializing HTTPScommunications, the server has failed to initialize thesecure data certificate information.


User Response: Ensure the keyring file name andkeyring file password are correct and that the passwordhas not expired. Check for earlier SKIT messages whichmay indicate the real problem. Replace keyring ifnecessary and re-start the server.

ANR8285I Shared Memory driver ready forconnection with clients on port port

Explanation: The server is now able to accept sessionswith clients using the Shared Memory protocol.



ANR8285I (HP-UX) Shared Memory driver ready forconnection with clients on port port




ANR8285I (Linux) Shared Memory driver ready forconnection with clients on port port




ANR8285I (PASE) Shared Memory driver ready forconnection with clients on port port




ANR8285I (Solaris) Shared Memory driver ready forconnection with clients on port port




ANR8285I (Windows) SNMP driver ready forconnection with subagent on port portnumber.




ANR8284E • ANR8285I (Windows)


ANR8286W Unable to initialize Shared Memorydriver - insufficient memory.

Explanation: Because the operating system rejected amemory allocation request, the server cannot startcommunications through the Shared Memory protocol.

System Action: Server operation continues, but theserver cannot accept sessions from clients using theShared Memory protocol.

User Response: Ensure that there is sufficient pagingspace for AIX. You may also use SMIT to determine ifthe number of applications is causing a memoryshortage. It may be necessary to cut down on themaximum number of client sessions by changing theMAXSESSIONS option in the server options file.

ANR8286W (HP-UX) Unable to initialize SharedMemory driver - insufficient memory.



User Response: Ensure that there is sufficient pagingspace for HP-UX. You may also use SAM to determineif the number of applications is causing a memoryshortage. It may be necessary to cut down on themaximum number of client sessions by changing theMAXSESSIONS option in the server options file.

ANR8286W (Linux) Unable to initialize SharedMemory driver - insufficient memory.



User Response: Ensure that there is sufficient swapspace for Solaris. It may be necessary to cut down onthe maximum number of client sessions by changingthe MAXSESSIONS option in the server options file.

ANR8286W (PASE) Unable to initialize SharedMemory driver - insufficient memory.



User Response: Ensure that there is sufficient paging

space for PASE. You may also use SMIT to determine ifthe number of applications is causing a memoryshortage. It may be necessary to cut down on themaximum number of client sessions by changing theMAXSESSIONS option in the server options file.

ANR8286W (Solaris) Unable to initialize SharedMemory driver - insufficient memory.



User Response: Ensure that there is sufficient swapspace for Solaris. It may be necessary to cut down onthe maximum number of client sessions by changingthe MAXSESSIONS option in the server options file.

ANR8286W (Windows) SNMP driver unable toinitialize due to error in BINDing toPort port, reason code reason code.



User Response: Ensure that no other application isusing the port number specified in the server optionsfile with the PORT option. If TCP/IP or HTTP is also inuse for client sessions, ensure that the same portnumber is not specified for TCP/IP or HTTPcommunications and SNMP communications. This maybe done by issuing the TCP/IP netstat -s command. Ifthe server is brought down and then startedimmediately, you may be within the TCP/IP oneminute timeout period for port reusage. Bring downthe sever, wait one minute, and then restart the server.If that does not work, it may be necessary to restartWindows.

ANR8287W Unable to initialize Shared Memorydriver - error creating acceptor socket.Reason code reason code.

Explanation: Because TCP/IP rejected a request for asocket on which to listen, the server cannot startcommunications through Shared Memory.


User Response: If TCP/IP is not started, use the



HALT command from any server prompt to stop theserver, and restart it.

ANR8287W (HP-UX) Unable to initialize SharedMemory driver - error creating acceptorsocket. Reason code reason code.



User Response: If TCP/IP is not started, use theHALT command from any server prompt to stop theserver, and restart it.

ANR8287W (Linux) Unable to initialize SharedMemory driver - error creating acceptorsocket. Reason code reason code.



User Response: If TCP/IP is not started, use theHALT command from any prompt to stop the server,and restart it.

ANR8287W (PASE) Unable to initialize SharedMemory driver - error creating acceptorsocket. Reason code reason code.



User Response: If TCP/IP is not started, use theHALT command from any server prompt to stop theserver, and restart it.

ANR8287W (Solaris) Unable to initialize SharedMemory driver - error creating acceptorsocket. Reason code reason code.



User Response: If TCP/IP is not started, use the

HALT command from any server prompt to stop theserver, and restart it.

ANR8288W Unable to establish Shared Memoryconnection - insufficient memory.



User Response: Ensure that there is sufficient pagingspace for AIX. You may also use SMIT to determine ifthe number of applications is causing a memoryshortage. You may also wish to cut down on themaximum number of sessions that the server canaccept with the MAXSESSIONS option in the serveroptions file.

ANR8288W (HP-UX) Unable to establish SharedMemory connection - insufficientmemory.



User Response: Ensure that there is sufficient pagingspace for HP-UX. You may also use SAM to determineif the number of applications is causing a memoryshortage. You may also wish to cut down on themaximum number of sessions that the server canaccept with the MAXSESSIONS option in the serveroptions file.

ANR8288W (Linux) Unable to establish SharedMemory connection - insufficientmemory.



User Response: Ensure that there is sufficient swapspace for Solaris. You may also wish to cut down onthe maximum number of sessions that the server canaccept with the MAXSESSIONS option in the serveroptions file.

ANR8288W (PASE) Unable to establish SharedMemory connection - insufficientmemory.



ANR8287W (HP-UX) • ANR8288W (PASE)


User Response: Ensure that there is sufficient pagingspace for PASE. You may also use SMIT to determine ifthe number of applications is causing a memoryshortage. You may also wish to cut down on themaximum number of sessions that the server canaccept with the MAXSESSIONS option in the serveroptions file.

ANR8288W (Solaris) Unable to establish SharedMemory connection - insufficientmemory.



User Response: Ensure that there is sufficient swapspace for Solaris. You may also wish to cut down onthe maximum number of sessions that the server canaccept with the MAXSESSIONS option in the serveroptions file.

ANR8289W Shared Memory driver is terminatingdue to error in creating a new thread.


System Action: Server operation continues, but SharedMemory communications is inoperative.

User Response: The most likely cause is a lack ofmemory. Ensure that there is sufficient paging space forAIX. You may also use SMIT to determine if thenumber of applications is causing a memory shortage.You may also wish to cut down on the maximumnumber of sessions that the server can accept with theMAXSESSIONS option in the server options file.

ANR8289W (HP-UX) Shared Memory driver isterminating due to error in creating anew thread.



User Response: The most likely cause is a lack ofmemory. Ensure that there is sufficient paging space forHP-UX. You may also use SAM to determine if thenumber of applications is causing a memory shortage.You may also wish to cut down on the maximumnumber of sessions that the server can accept with theMAXSESSIONS option in the server options file.

ANR8289W (Linux) Shared Memory driver isterminating due to error in creating anew thread.



User Response: The most likely cause is a lack ofmemory. Ensure that there is sufficient swap space forSolaris. You may also wish to cut down on themaximum number of sessions that the server canaccept with the MAXSESSIONS option in the serveroptions file.

ANR8289W (PASE) Shared Memory driver isterminating due to error in creating anew thread.



User Response: The most likely cause is a lack ofmemory. Ensure that there is sufficient paging space forPASE. You may also use SMIT to determine if thenumber of applications is causing a memory shortage.You may also wish to cut down on the maximumnumber of sessions that the server can accept with theMAXSESSIONS option in the server options file.

ANR8289W (Solaris) Shared Memory driver isterminating due to error in creating anew thread.



User Response: The most likely cause is a lack ofmemory. Ensure that there is sufficient swap space forSolaris. You may also wish to cut down on themaximum number of sessions that the server canaccept with the MAXSESSIONS option in the serveroptions file.

ANR8290W Error sending data through SharedMemory. Reason return code.

Explanation: The server experienced an error returncode while sending data through shared memory. Thismay be a normal event if either side of the connectionis abruptly ended.


User Response: If the session is ended as a result of

ANR8288W (Solaris) • ANR8290W


intentionally stopping either the client or server, noresponse is required.

ANR8290W (HP-UX) Error sending data throughShared Memory. Reason return code.




ANR8290W (Linux) Error sending data throughShared Memory. Reason return code.




ANR8290W (PASE) Error sending data throughShared Memory. Reason return code.




ANR8290W (Solaris) Error sending data throughShared Memory. Reason return code.




ANR8290I (Windows) IPX/SPX driver ready forconnection with clients on socket IPXsocket number.

Explanation: The server is now able to accept sessionswith clients using the IPX/SPX protocol on theindicated socket number.



ANR8291W Error receiving data through SharedMemory. Reason return code.

Explanation: The server experienced an error returncode while receiving data through the Shared Memoryprotocol. This may be a normal event if either side ofthe connection is abruptly ended.



ANR8291W (HP-UX) Error receiving data throughShared Memory. Reason return code.




ANR8291W (Linux) Error receiving data throughShared Memory. Reason return code.




ANR8291W (PASE) Error receiving data throughShared Memory. Reason return code.


ANR8290W (HP-UX) • ANR8291W (PASE)




ANR8291W (Solaris) Error receiving data throughShared Memory. Reason return code.




ANR8291W (Windows) Unable to bind to IPX/SPXmaster socket. Return code = return code.

Explanation: The server cannot initiatecommunications on the socket number designated forits use.

System Action: Server operation continues, butcommunications using the IPX/SPX protocol isinoperative.

User Response: Ensure that SPX has been configuredto run on this system through the requesterconfiguration program. Ensure that there is no otherinstance of the server running on the same system thatis using the same socket number. This is likely to be thecase if the return code is zero. Also ensure that thenumber of SPX sessions (as specified in your NET.CFGfile) has not been exceeded through other applicationsusing the IPX/SPX protocol.

ANR8292W Session terminated when no data wasread through Shared Memory.

Explanation: The server is unable to read data fromShared Memory. This may be a normal event if eitherside of the connection is abruptly ended.



ANR8292W (HP-UX) Session terminated when nodata was read through Shared Memory.




ANR8292W (Linux) Session terminated when no datawas read through Shared Memory.




ANR8292W (PASE) Session terminated when no datawas read through Shared Memory.




ANR8292W (Solaris) Session terminated when nodata was read through Shared Memory.




ANR8292W (Windows) IPX/SPX connectionterminated - insufficient memory.



User Response: The most likely cause is a lack ofmemory. Ensure that there is sufficient space for theWindows paging file. Click on the system icon in theWindows NT control panel and then click on thevirtual memory button. Refer to the online help forinstructions on how to increase the amount of virtualmemory. You may also wish to cut down on themaximum number of sessions that the server can

ANR8291W (Solaris) • ANR8292W (Windows)


accept with the MAXSESSIONS option in the serveroptions file.

ANR8293W Shared Memory driver unable toinitialize due to socket initializationerror.

Explanation: While initializing Shared Memorycommunications, the server failed to set up an interfacewith TCP/IP.



ANR8293W (HP-UX) Shared Memory driver unableto initialize due to socket initializationerror.




ANR8293W (Linux) Shared Memory driver unable toinitialize due to socket initializationerror.




ANR8293W (PASE) Shared Memory driver unable toinitialize due to socket initializationerror.



server cannot accept sessions from clients using theShared Memory protocol.


ANR8293W (Solaris) Shared Memory driver unableto initialize due to socket initializationerror.




ANR8293W (Windows) IPX/SPX driver unable toinitialize due to error in LISTENing onthe master socket, return code = returncode.

Explanation: While attempting to listen for sessionrequests from clients using IPX/SPX, the serverencountered an error.

System Action: Server operation continues, but theserver cannot accept additional sessions from clientsusing the IPX/SPX protocol.

User Response: Ensure that IPX/SPX is still runningproperly and that it has not been intentionally orunintentionally stopped. This may be done by usingthe getipxad command to determine if an endpoint canstill be opened and bound; also determine if you canstill connect to a NetWare server.

ANR8294W Shared Memory session unable toinitialize.

Explanation: While initializing a Shared Memorycommunications session, an error occurred duringinitial setup.

System Action: Server operation continues, but thesession is terminated.

User Response: Contact your service representativefor assistance in resolving the error.

ANR8294W (HP-UX) Shared Memory session unableto initialize.


ANR8293W • ANR8294W (HP-UX)




ANR8294W (Linux) Shared Memory session unableto initialize.




ANR8294W (PASE) Shared Memory session unableto initialize.




ANR8294W (Solaris) Shared Memory session unableto initialize.




ANR8294W (Windows) Unable to establish IPX/SPXconnection - accept error. Return code =tli error.

Explanation: The server cannot accept a client sessiondue to a failure in accepting the connection fromIPX/SPX.

System Action: Server operation continues, but thissession request fails.

User Response: Ensure that SPX has been configuredto run on this system through the requesterconfiguration program. Ensure that there is no otherinstance of the server running on the same system thatis using the same socket number. Also ensure that thenumber of SPX sessions has not been exceeded throughother applications using the IPX/SPX protocol, such asNetWare applications.

ANR8295W Shared Memory driver unable toinitialize due to error in BINDing toPort port, reason code reason code.

Explanation: While initializing Shared Memorycommunications, the server failed to connect to amaster socket on which to listen for clients. The reasoncode is the return code from the TCP/IP bind API.


User Response: Ensure that no application is usingthe port number specified in the server options filewith the SHMPORT option by issuing the TCP/IPnetstat command. If the server was brought down andclient sessions were active, it may be necessary toterminate the client sessions on the client systemsbefore the port can be freed.

ANR8295W (HP-UX) Shared Memory driver unableto initialize due to error in using Portport, reason code reason code.




ANR8295W (Linux) Shared Memory driver unable toinitialize due to error in BINDing toPort port, reason code reason code.




ANR8294W (Linux) • ANR8295W (Linux)


ANR8295W (PASE) Shared Memory driver unable toinitialize due to using Port port, reasoncode reason code.




ANR8295W (Solaris) Shared Memory driver unableto initialize due to error in BINDing toPort port, reason code reason code.




ANR8295W (Windows) Error sending data on sessionsession number. Reason return code.

Explanation: The server experiences an error returncode from IPX/SPX while sending data on theindicated session. This may be a normal event if eitherside of the connection is abruptly ended.


User Response: If the session is ended as a result ofintentionally stopping either the client or server, noresponse is required. Otherwise, ensure that IPX/SPX isstill active.

ANR8296W Shared Memory driver unable toinitialize due to error in LISTENing onthe specified Port, reason code reasoncode.


System Action: Server operation continues, but theserver cannot accept additional sessions from clientsusing the Shared Memory protocol.


ANR8296W (HP-UX) Shared Memory driver unableto initialize due to error in LISTENingon the specified Port, reason code reasoncode.




ANR8296W (Linux) Shared Memory driver unable toinitialize due to error in LISTENing onthe specified Port, reason code reasoncode.




ANR8295W (PASE) • ANR8296W (Linux)


ANR8296W (PASE) Shared Memory driver unable toinitialize due to error in LISTENing onthe specified Port, reason code reasoncode.




ANR8296W (Solaris) Shared Memory driver unableto initialize due to error in LISTENingon the specified Port, reason code reasoncode.




ANR8297W Shared Memory driver is terminatingdue to error in accepting a new session,reason code reason code.

Explanation: While attempting to accept a sessionrequest from a client using the Shared Memoryprotocol, TCP/IP returns an error. The reason code isthe return code from the TCP/IP accept API.



ANR8297W (HP-UX) Shared Memory driver isterminating due to error in accepting anew session, reason code reason code.




ANR8297W (Linux) Shared Memory driver isterminating due to error in accepting anew session, reason code reason code.




ANR8297W (PASE) Shared Memory driver isterminating due to error in accepting anew session, reason code reason code.




ANR8297W (Solaris) Shared Memory driver isterminating due to error in accepting anew session, reason code reason code.

Explanation: While attempting to accept a sessionrequest from a client using the Shared Memoryprotocol, TCP/IP returns an error. The reason code is

ANR8296W (PASE) • ANR8297W (Solaris)


the return code from the TCP/IP accept API.



ANR8300E I/O error on library library name(OP=internal code, CC=internal code,KEY=internal code, ASC=internal code,ASCQ=internal code, SENSE=sense data,Description=error description). Refer toAppendix D in the ’Messages’ manualfor recommended action.

Explanation: An I/O error has occurred whileoperating on the designated library device.


User Response: Ensure that the DEVICE parameterassociated with the library was identified correctly inthe DEFINE PATH command, and that the librarydevice is currently powered on and ready. If the libraryhas an access door, make sure it is closed. The drive orlibrary reference manual provided with the deviceusually contain tables that explain the values of theKEY, ASC, and ASCQ fields. If the problem persists,contact your service representative and provide theinternal code values and sense data from this message.

ANR8300W (PASE) Exit type EXIT exit name cannot belocated.

Explanation: The *PGM object with the specified exitname cannot be located on the system.

System Action: Server operation continues. The serverissues additional error messages when this conditionprevents it from completing an operation.

User Response: Correct the problem with thespecified exit program and use the UPDATE EXITcommand to notify the server that the exit has beenchanged.

ANR8301E I/O error on library library name(OP=internal code, SENSE=internal code).

Explanation: An I/O error has occurred whileoperating on the designated library device.


User Response: Ensure that the DEVICE parameterassociated with the library was identified correctly inthe DEFINE PATH command, and that the librarydevice is currently powered on and ready. If the libraryhas an access door, make sure it is closed. If the

problem persists, contact your service representativeand provide the internal code values from thismessage.

ANR8301W (PASE) Exit type EXIT exit name cannot beaccessed.

Explanation: The *PGM object with the given exitname cannot be accessed by the server. The attemptfails because the server does not have the authoritynecessary to access the designated *PGM object.



ANR8302E I/O error on drive drive name(OP=internal code, Error Number=internalcode, CC=internal code, KEY=internal code,ASC=internal code, ASCQ=internal code,SENSE=sense data, Description=errordescription). Refer to Appendix D in the’Messages’ manual for recommendedaction.

Explanation: An I/O error has occurred whileoperating on the designated drive.


User Response: Ensure that the DEVICE parameterassociated with the drive was identified correctly in theDEFINE PATH command, and that the device iscurrently powered on and ready. The drive or libraryreference manual provided with the device usuallycontain tables that explain the values of the KEY, ASC,and ASCQ fields. If the problem persists, contact yourservice representative and provide the internal codevalues and sense data from this message.

ANR8302W (PASE) Exit type EXIT is not defined.

Explanation: The designated exit has not been definedto the server.

System Action: Server operation continues. The serverissues additional error messages if this conditionprevents the server from completing an operation.


ANR8300E • ANR8302W (PASE)


ANR8303E I/O error on drive drive name(OP=internal code, SENSE=internal code).

Explanation: An I/O error has occurred whileoperating on the designated drive.


User Response: Ensure that the DEVICE parameterassociated with the drive was identified correctly in theDEFINE PATH command, and that the device iscurrently powered on and ready. If the problempersists, contact your service representative andprovide the internal code values from this message.

ANR8303E (PASE) Exit type EXIT exit name returned anon-zero result: exit result.

Explanation: The specified exit returned a non-zeroresult to the server. If the exit result is not either 0 or 1,the server will issue a value of U.


User Response: Evaluate the specified exit and thegiven result to determine if the result is appropriate. Ifnecessary, correct any problems in the exit and use theUPDATE EXIT command to notify the server that theexit has been changed.

ANR8304E Time out error on drive drive name inlibrary library name.

Explanation: A time out condition occurred whilewaiting for the given drive to become ready so thatautomated library operations could be performed.


User Response: Ensure that the DEVICE parameterassociated with the drive was identified correctly in theDEFINE PATH command, and that the device iscurrently powered on and ready.

ANR8304E (PASE) Time out error on drive drive namein library library name.

Explanation: A time out condition occurred whilewaiting for the given drive to become ready so thatautomated library operations could be performed.


User Response: Ensure that the DEVICE parameterassociated with the drive was identified correctly in theDEFINE DRIVE command, and that the device iscurrently powered on and ready.

ANR8305E Library library name is not ready or notoperational.

Explanation: The specified automated library device iseither not ready or not in an operational state.

System Action: Initialization of the library device fails.

User Response: Ensure that the library is powered onand ready for automated operations. Furtherinitialization attempts for the given library will usuallybe postponed until the next attempt is made to accessthe library for an automated operation. During serverstartup, however, initialization may be retried after ashort waiting period.

ANR8305I (PASE) Media Library Device library nameis ready for operations.

Explanation: The initialization process for the givenlibrary has completed successfully, and the library isready for use.

System Action: The library is made ready for use.


ANR8306I Request number: Insert device type volumevolume name mount mode into the slotwith element number slot element oflibrary library name within time limitminutes; issue ’REPLY’ along with therequest ID when ready.

Explanation: A CHECKIN LIBVOLUME or a LABELLIBVOLUME command is in progress, and thespecified volume is needed. The server expects thevolume to be inserted into the slot with the specifiedelement number of the given library within the timelimit specified in the message. For the slot and elementnumber diagram of your library, refer to thedocumentation provided with the current ptf level orrefer to the Administrator’s Guide for your release andplatform.

System Action: The server waits until a REPLYcommand is issued, or until the time limit expires.

User Response: Insert the volume into the slot andissue a REPLY command, along with the request ID, totell the server that the volume has been inserted.

ANR8306E (PASE) Initialization failed for MediaLibrary Device library name.Theinitialization will be retried in delay timeminutes.

Explanation: The initialization process for the givenlibrary has failed. It is tried again automatically afterthe specified amount of time has elapsed.

System Action: The initialization is tried again later.

User Response: Ensure that the library device is

ANR8303E • ANR8306E (PASE)


powered on and ready. If the library has an accessdoor, make sure it is in the closed position.

ANR8307I Request number: Remove device typevolume volume name from slot withelement number slot name of librarylibrary name; issue ’REPLY’ along withthe request ID when ready.

Explanation: A CHECKOUT LIBVOLUME commandhas completed. You can remove the volume from theslot with the specified element number and store itoutside the library. For the slot and element numberdiagram of your library, refer to the documentationprovided with the current ptf level or refer to theAdministrator’s Guide manual for your release andplatform.

System Action: The server waits until a REPLYcommand is issued.

User Response: Remove the volume from the slot andstore it in a safe place. Issue a REPLY command, alongwith the request ID, to tell the server that the volumehas been removed. The volume can be returned to thelibrary with the CHECKIN LIBVOLUME command.

ANR8307E (PASE) Initialization failed for MediaLibrary Device library name.

Explanation: The initialization process for the givenlibrary has failed and will not be retried until the nexttime the server needs to access the library. Checkpreviously issued messages for additional information.

System Action: The library is made temporarilyunavailable.

User Response: Make sure the library is powered onand attached.

ANR8308I Request number: device type volume volumename is required for use in library libraryname; CHECKIN LIBVOLUME requiredwithin time limit minutes.

Explanation: A mount request has been made for avolume that is defined in a storage pool, but which iscurrently checked out of the given library.

System Action: The server waits until it detects thatthe volume has been checked into the library, or thetime limit expires.

User Response: Obtain the required volume, andinsert it into the library by issuing a CHECKINLIBVOLUME command. Use the SWAP=YES option ofthe CHECKIN LIBVOLUME command if the library iscurrently full; this process allows the server to select anappropriate volume to be swapped out in order tomake room for the required volume.

ANR8308I (PASE) Request number: device type volumevolume name is required for use inlibrary library name; CHECKINLIBVOLUME required within time limitminutes.

Explanation: A mount request has been made for avolume that is defined in a storage pool, but which iscurrently checked out of the given library.

System Action: The server waits until it detects thatthe volume has been checked into the library, or thetime limit expires.

User Response: Obtain the required volume, andinsert it into the library by issuing a CHECKINLIBVOLUME command. Use the SWAP=YES option ofthe CHECKIN LIBVOLUME command if the library iscurrently full; this process allows the server to select anappropriate volume to be swapped out in order tomake room for the required volume.

ANR8309E Mount attempt failed - library libraryname is not defined.

Explanation: An attempt has been made to mount avolume, but the attempt fails because the specifiedlibrary is not defined.


User Response: Ensure that the LIBRARY attribute ofthe device class associated with the mount operationidentifies a defined library. If not, correct the value ofthe LIBRARY attribute, or define the specified libraryand retry the operation.

ANR8309W (PASE) Access state for volume volumename in library library name has been setto ″unavailable″.

Explanation: The specified volume encountered anerror during mount processing that makes it unusable.The access state of the volume in the library volumeinventory is changed to unavailable so that the volumeis not selected for future mounts.

One of the following may be the cause of the error:

v The volume may already be queued for use in themedia library device

v The volume may be mounted in another taperesource that is not available to the media librarydevice

v The volume was marked not available, or in error bythe library device manager

v The volume identifier may be a duplicate

v The volume may have been manually ejected fromthe library device

System Action: The server sets the volume accessstate to unavailable. If the server operation requires ascratch volume, processing continues with another

ANR8307I • ANR8309W (PASE)


scratch volume. If the server operation required thegiven volume, the operation is terminated.

User Response: Check previously issued servermessages for additional information regarding theerror. Check the spooled files of the system user thatstarted the server for messages that describe theproblem with the given volume. The Display TapeCartridge (DSPTAPCTG) command can be used todisplay the attributes of a tape volume.

Once the problem is corrected, update the access stateof the volume to available by using the UPDATELIBVOL command. An audit of the server library willalso result in a re-evaluation of the condition of thevolume. If the volume is usable, its access state will bechanged to available. An audit of the server libraryoccurs automatically during server initialization or anaudit of the library can be started with the AUDITLIBRARY command.

ANR8310E An I/O error occurred while accessinglibrary library name.

Explanation: An I/O error occurs while accessing thedesignated library.


User Response: Ensure that the DEVICE parameterassociated with the library is identified correctly in theDEFINE PATH command, and that the library iscurrently powered on and ready. If the library has anaccess door, make sure it is closed. After checking andcorrecting these potential problems, retry the operation.

ANR8310E (PASE) An I/O error occurred whileaccessing library library name.

Explanation: An I/O error occurs while accessing thedesignated library.


User Response: Ensure that the DEVICE parameterassociated with the library is identified correctly in theDEFINE LIBRARY command, and that the library iscurrently powered on and ready. If the library has anaccess door, make sure it is closed. After checking andcorrecting these potential problems, retry the operation.

ANR8311E An I/O error occurred while accessingdrive drive name for low-level operationoperation, errno = drive errno.

Explanation: An I/O error occurs while performingthe operation on the specified drive.


User Response: Ensure that the DEVICE parameterassociated with the drive is identified correctly in theDEFINE PATH command, and that the drive iscurrently powered on and ready. After checking and

correcting these potential problems, retry the operation.

ANR8311E (PASE) Command: Device device name isnot defined in library library name.

Explanation: The designated device has not beendefined in the given library.


User Response: Reissue the command and specify adifferent device name. If appropriate, use the DEFINEDRIVE command to place the device in the specifiedlibrary before reissuing the command.

ANR8312E Volume volume name could not belocated in library library name.

Explanation: The designated volume cannot be foundat its expected location in the given library.


User Response: Perform an AUDIT LIBRARYoperation on the designated library, which forces theserver to reevaluate its inventory information forvolumes in the library.

ANR8312E (PASE) Command: Volume volume namecannot be mounted on device devicename.

Explanation: The attributes of the designated volumedo not match the attributes of the specified device. Thevolume cannot be mounted on the device.


User Response: Reissue the command and specify adifferent device name.

ANR8313E Volume volume name is not present inlibrary library name.

Explanation: A mount request is made for the givenvolume in the specified library, but the volume is notcurrently checked into the library.

System Action: The mount operation fails. If thevolume is being mounted for storage pool I/O (asopposed to import/export I/O), its ACCESS attribute ischanged to UNAVAILABLE to prevent further mountrequests.

User Response: Issue a CHECKIN LIBVOLUMEcommand to return the volume into the library, andupdate the volumes ACCESS attribute to READONLYor READWRITE using the UPDATE VOLUMEcommand. Retry the mount request.



ANR8313E (PASE) Volume volume name is not presentin library library name.

Explanation: A mount request is made for the givenvolume in the specified library, but the volume is notcurrently checked into the library.

System Action: The mount operation fails. If thevolume is being mounted for storage pool I/O (asopposed to import/export I/O), its ACCESS attribute ischanged to UNAVAILABLE to prevent further mountrequests.

User Response: Issue a CHECKIN LIBVOLUMEcommand to return the volume into the library, andupdate the volumes ACCESS attribute to READONLYor READWRITE using the UPDATE VOLUMEcommand. Retry the mount request.

ANR8314E Library library name is full.

Explanation: A library operation fails because all ofthe library’s storage locations are occupied.


User Response: Issue a CHECKOUT LIBVOLUMEcommand to make room in the library. Retry the libraryoperation.

ANR8314E (PASE) Command: Device device name isnot available in library library name.

Explanation: The designated device is not available tocarry out an attempted operation in the given library.The device can be unavailable for the followingreasons:

v The device is already in use by the server

v The device is already be in use by another job oranother system

v The system status of the device makes it unavailableto the server

v The device is unavailable for the reason indicated inan additional message issued by the server


User Response: If another device is available in thelibrary, reissue the command using that device name. Ifthere are idle volumes mounted in the library, use theDISMOUNT VOLUME command to free a device, andthen reissue the command using that device name. Ifthe MOUNTWAIT value of the device class permits it,wait until a device is available in the library, and thenreissue the command using that device name.

ANR8315E Command: The device type of drive drivename is not supported in library typelibraries.

Explanation: Drives of the type identified in thecommand are not supported in the given type oflibrary.


User Response: Determine whether the drive andlibrary combination is supported by the installed levelof the server. If so, contact your service representative.

ANR8315E (PASE) Command: The device type ofdrive drive name is not supported inlibrary type libraries.

Explanation: Drives of the type identified in thecommand are not supported in the given type oflibrary.


User Response: Determine whether the drive andlibrary combination is supported by the installed levelof the server. If so, contact your service representative.

ANR8316E Selecting swap volume to be checkedout of library library name.

Explanation: A CHECKIN LIBVOL command wasissued for a library that has no empty slots to hold thenew cartridge. The SWAP=YES parameter was includedin the command.

System Action: A CHECKOUT LIBVOL commandwill be automatically be issued, specifying either ascratch volume or, if there are none, a volume with thelowest number of mounts.

User Response: Use a supported type of drive.volume from the library and store it in a safe place.Issue a REPLY command to tell the server that thevolume has been removed. The volume can beintroduced back into the library with the CHECKINLIBVOLUME command.

ANR8316E (PASE) Selecting swap volume to bechecked out of library library name.

Explanation: A CHECKIN LIBVOL command wasissued for a library that has no empty slots to hold thenew cartridge. The SWAP=YES parameter was includedin the command.

System Action: A CHECKOUT LIBVOL commandwill be automatically be issued, specifying either ascratch volume or, if there are none, a volume with thelowest number of mounts.

User Response: Use a supported type of drive.volume from the library and store it in a safe place.Issue a REPLY command to tell the server that the

ANR8313E (PASE) • ANR8316E (PASE)


volume has been removed. The volume can beintroduced back into the library with the CHECKINLIBVOLUME command.

ANR8317I The volume in device type drive drivename must be manually ejected.

Explanation: This device type does not automaticallyeject the volume when it is dismounted and requiresthat the volume be manually ejected from the drive.


User Response: Physically eject the volume from thedrive.

ANR8317I (PASE) Request number: Waiting for mountof device type volume volume name mountmode on drive drive name in librarylibrary name.

Explanation: The server is waiting for the specifiedvolume mount to complete.

System Action: The server waits for the mount tocomplete.


ANR8318I Request number: Mount side side of devicetype volume volume name mount mode indrive drive name of library library namewithin time limit< minutes.

Explanation: The server requires that the specifiedvolume be mounted as requested. Since the volume istwo-sided, this message specifies which side (A or B) isneeded by the server for I/O operations.

System Action: The server waits for the volume to bemounted.

User Response: Mount the volume in the specifieddrive.

ANR8318I (PASE) Request number: Mount side side ofdevice type volume volume name mountmode in drive drive name of library libraryname within time limit</ mv> minutes.

Explanation: The server requires that the specifiedvolume be mounted as requested. Since the volume istwo-sided, this message specifies which side (A or B) isneeded by the server for I/O operations.



ANR8319I Request number: Insert device type volumevolume name mount mode into librarylibrary name within time limit minute(s).

Explanation: A CHECKIN LIBVOLUME command isin progress, and the specified volume is needed. Theserver expects the volume to be inserted into thelibrary with the convenience I/O station mechanism.

System Action: The server waits until the volume isin the library, or until the time limit expires.

User Response: Insert the specified volume into thelibrary. If the volume has already been inserted into thelibrary, no user action is necessary.

ANR8319I (PASE) Request number: Insert device typevolume volume name mount mode intolibrary library name within time limitminute(s).

Explanation: A CHECKIN LIBVOLUME command isin progress, and the specified volume is needed. Theserver expects the volume to be inserted into thelibrary with the convenience I/O station mechanism.

System Action: The server waits until the volume isin the library, or until the time limit expires.

User Response: Insert the specified volume into thelibrary. If the volume has already been inserted into thelibrary, no user action is necessary.

ANR8320I Request number: Insert device type volumevolume name mount mode in drive drivename of library library name within timelimit minute(s); issue ’REPLY ’ alongwith the request ID when ready.

Explanation: A CHECKIN LIBVOLUME or a LABELLIBVOLUME command is in progress, and thespecified volume is needed. The server expects thevolume to be inserted in the designated drive of thegiven library within the time limit specified in themessage.


User Response: Insert the volume into the drive, andthen issue a REPLY command, along with the requestID, to tell the server that the volume has been inserted.

ANR8320I (PASE) Request number: Insert device typevolume volume name mount mode in drivedrive name of library library name withintime limit minute(s); issue ’REPLY ’ alongwith the request ID when ready.

Explanation: A CHECKIN LIBVOLUME command isin progress, and the specified volume is needed. Theserver expects the volume to be inserted in thedesignated drive of the given library within the timelimit specified in the message.

ANR8317I • ANR8320I (PASE)



User Response: Insert the volume into the drive, andthen issue a REPLY command, along with the requestID, to tell the server that the volume has been inserted.

ANR8321I Request number: Remove device typevolume volume name from drive drivename of library library name; issue’REPLY’ along with the request ID whenready.

Explanation: A CHECKOUT LIBVOLUME or aLABEL LIBVOLUME command has completed. You canremove the specified volume from the designated driveand store it outside the library.


User Response: Remove the volume from the driveand store it in a safe place. Issue a REPLY command,along with the request ID, to tell the server that thevolume has been removed. The volume can be returnedto the library with the CHECKIN LIBVOLUMEcommand.

ANR8321I (PASE) Request number: Remove device typevolume volume name from drive drivename of library library name; issue’REPLY’ along with the request ID whenready.

Explanation: A CHECKOUT LIBVOLUME commandhas completed. You can remove the specified volumefrom the designated drive and store it outside thelibrary.


User Response: Remove the volume from the driveand store it in a safe place. Issue a REPLY command,along with the request ID, to tell the server that thevolume has been removed. The volume can be returnedto the library with the CHECKIN LIBVOLUMEcommand.

ANR8322I Request number: Remove device typevolume volume name from entry/exit portof library library name; issue ’REPLY’along with the request ID when ready.

Explanation: A CHECKOUT LIBVOLUME commandhas completed. You can remove the specified volumefrom the entry/exit port of the given library and storeit elsewhere.


User Response: Remove the volume from the libraryand store it in a safe place. Issue a REPLY command,

along with the request ID, to tell the server that thevolume has been removed. The volume can be returnedto the library with the CHECKIN LIBVOLUMEcommand.

ANR8322I (PASE) Request number: Remove device typevolume volume name from entry/exit portof library library name; issue ’REPLY’along with the request ID when ready.

Explanation: A CHECKOUT LIBVOLUME commandhas completed. You can remove the specified volumefrom the entry/exit port of the given library and storeit elsewhere.


User Response: Remove the volume from the libraryand store it in a safe place. Issue a REPLY command,along with the request ID, to tell the server that thevolume has been removed. The volume can be returnedto the library with the CHECKIN LIBVOLUMEcommand.

ANR8323I Request number: Insert device type volumevolume name mount mode into entry/exitport of library library name within timelimit minute(s); issue ’REPLY’ along withthe request ID when ready.

Explanation: A CHECKIN LIBVOLUME or a LABELLIBVOLUME cmmand is in progress, and the specifiedvolume is needed. Mount the volume in the entry/exitport of the given library within the time limit specifiedin the message.


User Response: Insert the volume into the library’sentry/exit port; and issue a REPLY command, alongwith the request ID, to tell the server that the volumehas been inserted.

ANR8323I (PASE) Request number: Insert device typevolume volume name mount mode intoentry/exit port of library library namewithin time limit minute(s); issue’REPLY’ along with the request ID whenready.

Explanation: A CHECKIN LIBVOLUME command isin progress, and the specified volume is needed. Mountthe volume in the entry/exit port of the given librarywithin the time limit specified in the message.


User Response: Insert the volume into the library’sentry/exit port; and issue a REPLY command, alongwith the request ID, to tell the server that the volumehas been inserted.



ANR8324I Device type volume volume name isexpected to be mounted (mount mode).

Explanation: The specified volume is expected to bemounted in the near future so the server can access itfor reading or writing.


User Response: If the volume is stored offline, retrieveit so that it is readily accessible when the serverrequests that it be mounted.

ANR8324I (PASE) Device type volume volume name isexpected to be mounted (mount mode).

Explanation: The specified volume is expected to bemounted in the near future so the server can access itfor reading or writing.


User Response: If the volume is stored offline, retrieveit so that it is readily accessible when the serverrequests that it be mounted.

ANR8325I Dismounting volume volume name -mount retention period minute mountretention expired.

Explanation: The specified volume is dismountedbecause the given mount retention period has expired.

System Action: The volume is dismounted.


ANR8325I (PASE) Dismounting volume volume name- mount retention period minute mountretention expired.

Explanation: The specified volume is dismountedbecause the given mount retention period has expired.

System Action: The volume is dismounted.


ANR8326I Request number: Mount device type volumevolume name mount mode in drive drivename of library library name within timelimit minutes.

Explanation: If the volume name includes the namesEXP, IMP, DUMP, or DBBK, the request is for a scratchvolume.



ANR8326I (PASE) Request number: Mount device typevolume volume name mount mode in drivedrive name of library library name withintime limit minutes.

Explanation: If the volume name includes the namesEXP, IMP, DUMP, or DBBK, the request is for a scratchvolume.


User Response: Mount the volume in the specifieddrive within the time limit. If this is a request for aSCRATCH mount, use the REPLY command to indicateto the server that a volume has been mounted.

ANR8327E Command: Cannot cancel request requestnumber.

Explanation: The request, whose number is specifiedby the given command, cannot be canceled. Therequested operation must be completed.

System Action: The cancel request command is notprocessed.

User Response: Proceed with the requested operation.

ANR8327E (PASE) Command: Cannot cancel requestrequest number.

Explanation: The request, whose number is specifiedby the given command, cannot be canceled. Therequested operation must be completed.

System Action: The cancel request command is notprocessed.

User Response: Proceed with the requested operation.

ANR8328I Request number: device type volume volumename mounted in drive drive name.

Explanation: The server verifies that a requestedvolume has been mounted properly in the given drive.

System Action: The volume is accessed for reading orwriting, or both.


ANR8328I (PASE) Request number: device type volumevolume name mounted in drive drivename.

Explanation: The server verifies that a requestedvolume has been mounted properly in the given drive.

System Action: The volume is accessed for reading orwriting, or both.




ANR8329I Device type volume volume name ismounted mount mode in drive drive name,status: IDLE.

Explanation: In response to a QUERY MOUNTcommand, the server indicates that the given volume ismounted in the specified drive. The volume is currentlyidle, meaning no active operations are being performed.If the volume remains in the idle state for the amountof time specified by the device class mount retentionperiod, it will be automatically dismounted.



ANR8329I (PASE) Device type volume volume name ismounted mount mode in drive drive name,status: IDLE.

Explanation: In response to a QUERY MOUNTcommand, the server indicates that the given volume ismounted in the specified drive. The volume is currentlyidle, meaning no active operations are being performed.If the volume remains in the idle state for the amountof time specified by the device class mount retentionperiod, it will be automatically dismounted.



ANR8330I Device type volume volume name ismounted mount mode in drive drive name,status: IN USE.

Explanation: In response to a QUERY MOUNTcommand, the server indicates that the given volume ismounted in the specified drive. The volume is currentlyin use, meaning that read or write operations, or both,are being performed.



ANR8330I (PASE) Device type volume volume name ismounted mount mode in drive drive name,status: IN USE.

Explanation: In response to a QUERY MOUNTcommand, the server indicates that the given volume ismounted in the specified drive. The volume is currentlyin use, meaning that read or write operations, or both,are being performed.



ANR8331I Device type volume volume name ismounted mount mode in drive drive name,status: DISMOUNTING.

Explanation: In response to a QUERY MOUNTcommand, the server indicates that the given volume ismounted in the specified drive. The volume is currentlybeing dismounted by the server.



ANR8331I (PASE) Device type volume volume name ismounted mount mode in drive drive name,status: DISMOUNTING.

Explanation: In response to a QUERY MOUNTcommand, the server indicates that the given volume ismounted in the specified drive. The volume is currentlybeing dismounted by the server.



ANR8332I Device type volume volume name ismounted mount mode, status: IDLE.

Explanation: In response to a QUERY MOUNTcommand, the server indicates that the given volume ismounted for I/O operations. The volume is currentlyidle, meaning no active operations are being performed.If the volume remains in the idle state for the amountof time specified by the device class mount retentionperiod, it will be automatically dismounted.



ANR8332I (PASE) Device type volume volume name ismounted mount mode, status: IDLE.

Explanation: In response to a QUERY MOUNTcommand, the server indicates that the given volume ismounted for I/O operations. The volume is currentlyidle, meaning no active operations are being performed.If the volume remains in the idle state for the amountof time specified by the device class mount retentionperiod, it will be automatically dismounted.



ANR8333I Device type volume volume name ismounted mount mode, status: IN USE.

Explanation: In response to a QUERY MOUNTcommand, the server indicates that the given volume ismounted for I/O operations. The volume is currently inuse, meaning that read or write operations, or both arebeing performed.





ANR8333I (PASE) Device type volume volume name ismounted mount mode, status: IN USE.

Explanation: In response to a QUERY MOUNTcommand, the server indicates that the given volume ismounted for I/O operations. The volume is currently inuse, meaning that read or write operations, or both arebeing performed.



ANR8334I Number of matches matches found.

Explanation: This is a summary message for theQUERY MOUNT command. It indicates the totalnumber of mount points that have been reported in thecommand output.



ANR8334I (PASE) Number of matches matches found.

Explanation: This is a summary message for theQUERY MOUNT command. It indicates the totalnumber of mount points that have been reported in thecommand output.



ANR8335I Request number: Verifying label of devicetype volume volume name in drive drivename.

Explanation: The server verifies the label of thevolume that has been requested by an earlier mountmessage. This is done to ensure that the correct volumehas been mounted by the operator.

System Action: The server reads the volume label andchecks it for validity.


ANR8335I (PASE) Request number: Verifying label ofdevice type volume volume name in drivedrive name.

Explanation: The server verifies the label of thevolume that has been requested by an earlier mountmessage. This is done to ensure that the correct volumehas been mounted by the operator.



ANR8336I Verifying label of device type volumevolume name in drive drive name.

Explanation: The server verifies the label of a volumethat is needed for read or write operations, or both.This is done to ensure that the correct volume has beenmounted.



ANR8336I (PASE) Verifying label of device typevolume volume name in drive drive name.

Explanation: The server verifies the label of a volumethat is needed for read or write operations, or both.This is done to ensure that the correct volume has beenmounted.



ANR8337I Device type volume volume name mountedin drive drive name.

Explanation: The server verifies that the specifiedmount request has been completed properly. Read orwrite operations, or both, can be performed on thevolume.

System Action: The label of the volume has beenverified.


ANR8337I (PASE) Request number volume volume namemounted in drive drive name.

Explanation: The server verifies that the specifiedmount request has been completed properly. Read orwrite operations, or both, can be performed on thevolume.

System Action: The label of the volume has beenverified.


ANR8338E Device type volume volume name cannotbe overwritten by EXPORT operation.

Explanation: The specified volume already exists orcontains data, so that the server cannot allow newexport data to be written to it.


User Response: If the specified volume does not

ANR8333I (PASE) • ANR8338E


contain any valuable data, delete it and retry the exportoperation.

ANR8338E (PASE) Device type volume volume namecannot be overwritten by EXPORToperation.

Explanation: The specified volume already exists orcontains data, so that the server cannot allow newexport data to be written to it.


User Response: If the specified volume does notcontain any valuable data, delete it and retry the exportoperation.

ANR8339E Device type volume intended volume namein drive drive name was replaced withvolume incorrect volume name.

Explanation: The server detects that a previouslymounted and verified volume (the desired volume) hasbeen replaced with a different volume (the incorrectvolume). No further read or write operations, or both,can occur on the given drive, because data corruptionmay occur.

System Action: The server dismounts the volumefrom the drive.

User Response: Mount the correct volume again if itis in a manual library and retry the operation.

ANR8339E (PASE) Device type volume intended volumename in drive drive name was replacedwith volume incorrect volume name.

Explanation: The server detects that a previouslymounted and verified volume (the desired volume) hasbeen replaced with a different volume (the incorrectvolume). No further read or write operations, or both,can occur on the given drive, because data corruptionmay occur.

System Action: The server dismounts the volumefrom the drive.

User Response: Mount the correct volume again if itis in a manual library and retry the operation.

ANR8340I Device type volume volume namemounted.




ANR8340I (PASE) Device type volume volume namemounted.




ANR8341I End-of-volume reached for device typevolume volume name.


System Action: The volume is marked full. If moredata must be stored, the server will access anothervolume for it.


ANR8341I (PASE) End-of-volume reached for devicetype volume volume name.


System Action: The volume is marked full. If moredata must be stored, the server will access anothervolume for it.


ANR8342I Request request number for volumevolume name canceled by administratorname.

Explanation: A mount request is canceled by the givenadministrator.



ANR8342I (PASE) Request request number for volumevolume name canceled by administratorname.

Explanation: A mount request is canceled by the givenadministrator.



ANR8343I Request request number for volumevolume name canceled (PERMANENT) byadministrator name.

Explanation: A mount request is successfully canceledwith the PERMANENT option.

System Action: The system cancels the mount requestand marks the volume as unavailable.

ANR8338E (PASE) • ANR8343I


Date post:	03-Feb-2022
Category:	Documents
Upload:	others
View:	7 times
Download:	0 times

IBM Tivoli Storage Manager: Messages - IBM - United States

Documents