IBM Spectrum Protect: Server Messages and Error Codes...Messages, err or codes, and r eturn codes ar...

IBM Spectrum ProtectVersion 8.1.5

Server Messages and Error Codes

IBM

Note:Before you use this information and the product it supports, read the information in “Notices” on page 691.

This edition applies to version 8, release 1, modification 5 of IBM Spectrum Protect (product numbers 5725-W98,5725-W99, 5725-X15, 5725-X18) and to all subsequent releases and modifications until otherwise indicated in neweditions.

© Copyright IBM Corporation 1993, 2018.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

About this publication . . . . . . . . vWho should read this publication . . . . . . . vPublications . . . . . . . . . . . . . . v

Chapter 1. Introduction to messages . . 1IBM Spectrum Protect server and client messagesformat . . . . . . . . . . . . . . . . 1Interpreting return code messages . . . . . . . 2

Example one for QUERY EVENT command . . . 3Example two for DEFINE VOLUME command . . 3

Chapter 2. ANE messages . . . . . . . 5ANE messages list . . . . . . . . . . . . 5

Chapter 3. ANR messages . . . . . . 35ANR messages list . . . . . . . . . . . . 35

Chapter 4. Descriptions of I/O codesin server messages. . . . . . . . . 677Completion code and operation code valuesoverview . . . . . . . . . . . . . . . 678

Device drivers completion codes: Commoncodes . . . . . . . . . . . . . . . 678Device drivers completion codes: Mediachangers . . . . . . . . . . . . . . 679Device drivers completion codes: Tape drives 681

Descriptions of standard ASC and ASCQ codes . . 682ASC and ASCQ codes in the Windows EventLog. . . . . . . . . . . . . . . . 686

Chapter 5. Device error codes in theAIX system error log . . . . . . . . 687

Appendix. Accessibility features forthe IBM Spectrum Protect productfamily. . . . . . . . . . . . . . . 689

Notices . . . . . . . . . . . . . . 691

Glossary . . . . . . . . . . . . . 695

© Copyright IBM Corp. 1993, 2018 iii

iv IBM Spectrum Protect: Server Messages and Error Codes

About this publication

IBM Spectrum Protect™ is an enterprise-wide storage management application forthe network. It provides automated storage management services to multi-vendorworkstations, personal computers, and local area network (LAN) file servers.

This publication contains explanations and suggested actions for messages issuedby the IBM Spectrum Protect server.

Who should read this publicationThe target audience for this publication is system administrators who service theIBM Spectrum Protect components. In this publication, it is assumed that you havea working knowledge of the IBM Spectrum Protect server and client components.

PublicationsThe IBM Spectrum Protect product family includes IBM Spectrum ProtectSnapshot, IBM Spectrum Protect for Space Management, IBM Spectrum Protect forDatabases, and several other storage management products from IBM®.

To view IBM product documentation, see IBM Knowledge Center.

© Copyright IBM Corp. 1993, 2018 v

http://www.ibm.com/support/knowledgecenter

vi IBM Spectrum Protect: Server Messages and Error Codes

Chapter 1. Introduction to messages

Messages, error codes, and return codes are issued by the IBM Spectrum Protectserver and clients.

Messages and codes can appear on the server console, the administrative client, anoperator terminal, the administrative graphical user interface, the backup-archiveclient, or the hierarchical storage managment client (HSM client).

IBM Spectrum Protect 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

Some messages have no explanations and are not published. The client can sendstatistics to the server providing information about a backup or restore. Thesestatistics are informational messages that can be enabled or disabled to the variousevent logging receivers. These messages are not published.Related tasks:

Using the activity log (V7.1.1)

IBM Spectrum Protect server and client messages formatIBM Spectrum Protect server and client messages consist of the following elements:v A three-letter prefix. Messages have different prefixes to help you identify the

IBM Spectrum Protect component that issues the message. Typically, allmessages for a component have the same prefix. Sometimes a component issuesmessages with two or three different prefixes.For example, backup-archive clients issue messages with the ANS prefix.Backup-archive client events that are logged to the server have the ANE prefix.Server common and server platform-specific messages have the ANR prefix.

v A numeric message identifier.v A one-letter severity code. The following codes indicate the severity of the action

that generated the message:

Code Severity MeaningS Severe The product or a product function cannot continue. User

response is required.E Error An error is encountered during processing. Processing might

stop. User response might be required.W Warning Processing continues, but problems might occur later as a result

of the warning.I Information Processing continues. User response is not necessary.

© Copyright IBM Corp. 1993, 2018 1

https://www.ibm.com/support/knowledgecenter/SSGSG7_7.1.1/com.ibm.itsm.srv.doc/t_activ_log_using.html

v Message text that is displayed on screen and written to message logs.v Explanation, System Action, and User Response texts. These texts elaborate on

the message text, and are available in the product messages publications and inthe command line help.

The following image presents a typical IBM Spectrum Protect server message.

The callouts identify each element of the message.

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

*

Message variables in the message text appear in italics.

Interpreting return code messagesMany 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.

In these examples, two different commands yield the same return code, but theyalso return descriptive messages that are unique to each command. The twocommands are q event standard dddd and def vol cstg05 primary. Both yield ageneric message with return code:ANS5102I: Return Code 11.

But the first command also yields a descriptive message:ANR2034I: QUERY EVENT: No match found for this query.

And the second command also yields a unique, descriptive message:ANRxxxx: DEFINE VOLUME: Storage pool CSTG05 is not defined.

2 IBM Spectrum Protect: Server Messages and Error Codes

Example one for QUERY EVENT command

Example two for DEFINE VOLUME command

Chapter 1. Introduction to messages 3

Chapter 2. ANE messages

ANE messages are issued by the server. All messages with the ANE prefix areclient events logged to the server.

ANE messages listMessages are listed in ascending numerical order. All elements of the message aredocumented.

For a list of new, changed, and deleted server messages, see the following files inthe server installation directory:

Release_msg_chgsThis file contains all new, changed, and deleted messages from theprevious server version to the current version.

Maint_msg_chgsThis file contains all new, changed, and deleted messages from the currentserver version to the current release.

These files are in the installation_directory\doc directory for Windowsoperating systems and the installation_directory/server/bin/ directory for allother operating systems.

These files are also available in New, changed, and deleted server messages on theIBM Spectrum Protect wiki.

ANE4000E Error processing 'filespace-name': filespace does not exist.

Explanation: The specified file space (domain) isincorrect or does not exist on the workstation. If themessage results from the BACKUP IMAGE commandwith the -MODE=INCREMENTAL option, it means thatyou have entered the name of a raw logical volume.The MODE=INCREMENTAL option is not valid forraw logical volumes.

System action: Processing stops.

User response: Try the operation again, specifying anexisting domain (drive letter or file system name). Ifthe message resulted from improper use of theMODE=INCREMENTAL option, try the commandagain, omitting that option.

ANE4001E The file space for domain 'filespace-name'could not be found on the IBMSpectrum Protect server.

Explanation: The specified file space was expected tobe found on the server, but it no longer exists. It ispossible that a command was issued to delete the filespace from the server while the current operation wasin progress.

System action: IBM Spectrum Protect processingstops.

User response: Try the operation again. If the problemrecurs, check the error log for any other messages thatmight indicate a reason for the failure. Try to correctany indicated problems, then try the operation again. Ifthe problem persists, contact IBM technical support forfurther assistance.

ANE4002E Error processing 'filespace-name': volumelabel does not exist

Explanation: The selected drive does not have a label.

System action: IBM Spectrum Protect is unable to dothe requested operation without a drive or labelentered.

User response: If the drive is a floppy drive, place adisk with a volume label in it and retry the operation.If the disk is a hard drive, ensure the drive has avolume label, and retry the operation.

ANE4003E Error processing 'filespace-name':duplicate volume label encountered

Explanation: The selected drive has a duplicatevolume label. Because IBM Spectrum Protect uses the


https://www.ibm.com/developerworks/community/wikis/home#!/wiki/Tivoli%20Storage%20Manager/page/New%2C%20changed%2C%20and%20deleted%20server%20messages

volume label to keep track of backup/archiveinformation, it cannot back up or archive files from adrive with a duplicate volume label.

System action: IBM Spectrum Protect cannot select thedrive.

User response: If the volume needs to be available tothe system, exit IBM Spectrum Protect, and assign avolume label to the drive. Restart IBM SpectrumProtect and retry the operation.

ANE4004E Error processing 'filespacenamepath-namefile-name': destination fileor directory is write locked

Explanation: The file or directory being restored orretrieved from the server cannot be written to becausethe destination is write locked. Another operationmight have the file open and will not allow it to beupdated.

System action: File skipped.

User response: Either determine which operation hasthe file write locked, or restore the file to another nameor location.

ANE4005E Error processing 'filespacenamepath-namefile-name': file not found

Explanation: The file being processed for backup,archive or migrate no longer exists on the client.Another process deletes the file before it can be backedup, archived or migrated by IBM Spectrum Protect.


User response: None.

ANE4006E Error processing 'filespacenamepath-namefile-name': directory pathnot found

Explanation: The operating system returned a "pathnot found" status when IBM Spectrum Protectattempted to access the directory. You either havespecified a directory that does not exist, as shown inthe message (path-name), or the directory beingprocessed no longer exists on the client because anotherprocess deleted it before it could be backed up orarchived by IBM Spectrum Protect.

System action: The directory is skipped, processingcontinues

User response: Recheck all spelling and punctuation,particularly the placement of directory delimiters (forexample, "\"). Correct the syntax if it is incorrect, thenretry the operation. Ensure that the path is specifiedcorrectly and that the directory actually exists. Retrythe command with the corrected path and directoryname. If you cannot correct the directory name, use the

Exclude option to exclude the directory from theoperation.

ANE4007E Error processing 'filespacenamepath-namefile-name': access to theobject is denied

Explanation: Access to the specified file or directory isdenied. You tried to read from or write to a file andyou do not have access permission for either the file orthe directory.

System action: Processing stopped.

User response: Ensure that you specified the correctfile or directory name, correct the permissions, orspecify a new location.

ANE4008E Error processing 'filespacenamepath-namefile-name': file istemporarily unavailable

Explanation: File is temporarily unavailable.


User response: Check and see if file is locked by otherprocess. If not, retry the command.

ANE4009E Error processing 'filespacenamepath-namefile-name': disk fullcondition

Explanation: No more files can be restored orretrieved because the destination disk is full.

System action: The client prompts you for action:

v Retry this object

v Skip this object

v Abort the action

User response: Select the appropriate action for thisobject. Create some free space on the destination diskbefore you retry the operation. Another option is torestore or retrieve the file to another disk.

ANE4010E Error processing 'filespacenamepath-namefile-name': stale NFS handle

Explanation: An NFS file system becomes stale.

System action: File system skipped.

User response: Verify that the NFS file system ismounted. If the problem persists, unmount andremount the file system, then try the operation again.

ANE4011E Error processing 'filespacenamepath-namefile-name': no file handlesavailable

Explanation: All file handles for your system arecurrently in use. No more are available.

ANE4004E • ANE4011E



User response: Either free some file handles by endingother processes, or modify your system setup to allowfor more files to be open at the same time.

ANE4012E 'filespace namepath-namefile-name' alreadyexists. It will be skipped.

Explanation: The client tried to restore or retrieve thespecified file, but the file already existed in the targetrestore location and the user chose not to replace theexisting file.

System action: The file is skipped, a message islogged in dsmerror.log, and restore or retrieveprocessing continues with the next object.

User response: The file was skipped because eitherREPLACE NO was in effect, causing all existing filesand directories to be skipped, or REPLACE PROMPTwas in effect, and when prompted, the user chose toskip this file or all existing directories and files. Noadditional action is necessary if the decision to skip thefile was deliberate. Otherwise the operation can beretried using either REPLACE ALL REPLACEPROMPT.

ANE4013E Error processing 'filespacenamepath-namefile-name': invalid filehandle

Explanation: An internal system error occurred. A fileoperation failed because an invalid file handle waspassed.


User response: Report the problem to your systemadministrator, and then retry the operation.

ANE4014E Error processing 'filespacenamepath-namefile-name': unknown systemerror (error-code) encountered. Programending.

Explanation: An unrecognized and unexpectederror-code occurred within the client program. This is aprogramming failure and the client program ends.

System action: processing stops.

User response: Try the operation again. If the problemcontinues, report the error to your IBM SpectrumProtect administrator.

ANE4015E Error processing 'filespacenamepath-namefile-name': unexpected IBMSpectrum Protect error (error-code)encountered

Explanation: An unexpected error occurred. Thismight be a low-level system or communication error

that IBM Spectrum Protect cannot handle or recoverfrom.


User response: Try the operation again. If the problemcontinues, look for other indications of systemproblems to determine where the problem exists. Mostsystems have error or event logs which may containadditional information. See your system administratoror IBM Spectrum Protect administrator for further help.

ANE4016E Error processing 'filespacenamepath-namefile-name': file is beingexecuted; write permission denied

Explanation: The current file cannot be opened towrite to because it is currently being run by anotheroperation.


User response: Stop the operation that is running thefile and retry the operation, or restore or retrieve thefile to a different name or directory.

ANE4017E Error processing 'filespacenamepath-namefile-name': too manysymbolic links were detected whileresolving name

Explanation: While trying to resolve the file name, toomany symbolic links were found.


User response: Ensure that you do not have a loopingsymbolic link for the file.

ANE4018E Error processing 'filespacenamepath-namefile-name': file name toolong

Explanation: The file name specified is too long to behandled by IBM Spectrum Protect.

System action: File is skipped.

User response: See the appropriate Using theBackup-Archive Client book for the particular operatingsystem, for the file names that are handled by IBMSpectrum Protect.

ANE4019E Error processing 'filespacenamepath-namefile-name': file system islocked by system

Explanation: File system cannot be accessed because itis locked by the system.

System action: IBM Spectrum Protect cannot completethe operation.

User response: See your system administrator.


Chapter 2. ANE messages 7

ANE4020E The data format for object 'filespacenamepath-namefile-name' is unknown. Theunknown format usually occurs whenthe file was backed up or archived by alater version of IBM Spectrum Protect.

Explanation: When a file is backed up or archived,IBM Spectrum Protect includes some additionalinformation about the file. This message is issued ifIBM Spectrum Protect cannot recognize the informationduring a restore or retrieve operation. The most likelycause is that the file was backed up or archived with anewer version of IBM Spectrum Protect. If the file wasbacked up from a case-preserving but not case-sensitivefile system, the file name might be displayed withincorrect casing. The incorrect casing does nototherwise affect processing since the file is skipped.

System action: The file is not restored or retrieved.Processing continues with the next file.

User response: Try the restore or retrieve operationagain with a current version of the IBM SpectrumProtect client software. If the problem persists, contactIBM technical support for further assistance.

ANE4021E Error processing 'filespacenamepath-namefile-name': file system notready

Explanation: The file system/drive was not ready foraccess.


User response: Ensure that the drive is available toIBM Spectrum Protect, and then retry the operation.

ANE4022E Error processing 'filespacenamepath-namefile-name': file system isinvalid.

Explanation: The drive was not available for access.


User response: Ensure that the drive is operational,and then try the operation again. If this is unsuccessful,check the error log.

ANE4023E Error processing 'filespacenamepath-namefile-name': file input/outputerror

Explanation: An error was found while reading fromor writing to the file.


User response: Check your system to ensure that it isoperating properly. For OS/2, run CHKDSK /F for thefailing drive which can be found in dsmerror.log.

ANE4024E Error processing 'filespacenamepath-namefile-name': file write error

Explanation: An error was found while writing to thefile.


User response: Check your system to ensure that it isoperating properly.

ANE4025E Error processing 'filespacenamepath-namefile-name': file exceeds useror system file limit

Explanation: A file being backed up/restored orarchived/retrieved exceeds system set limits for thisuser. Shown below are the filesize limits correspondingto various platforms.

AIX 68,589,453,312 (64GB)

HP-UX 1,099,511,627,775 (1TB-1)

Linux 2,147,483,647 (2GB)

Mac pre-OS92,147,482,624 (2GB-1K)

Mac OS918,446,744,073,709,551,616 (16EB)

NetWare4,294,963,200 (4GB -4KB)

NUMA-Q DYNIX/ptx4.5 1,095,216,660,480 (1TB-4GB)

OS/390 4,294,967,295 (4GB)

SGI 18,446,744,073,709,551,615 (16EB-1)

Solaris 2.6 or higher 1,099,511,627,775 (1TB-1)

Tru64 UNIX1,099,511,627,776 (1TB)

UnixWare2,147,483,647 (2GB)

Windows ME (FAT32)4,294,967,295 (4GB)

Windows NT/2000 (NTFS)17,592,185,978,880 (16TB-64K)


User response: Ensure that the system limits are setproperly.

ANE4026W Error processing 'filespacenamepath-namefile-name': size of 'file-size'exceeded the maximum file size limit onyour system

Explanation: You tried to restore or retrieve a file that

ANE4020E • ANE4026W


has exceeded the maximum file size limitation on yoursystem.

System action: IBM Spectrum Protect cannot restoreor retrieve the file.

User response: Restore or retrieve this file on a systemthat supports the file size. See your systemadministrator.

ANE4027S Error processing 'filespacenamepath-namefile-name': internal programmessage 'value' encountered

Explanation: An unexpected catastrophic programfailure occurred, indicated by value.


User response: Retry the operation. If the problemcontinues, see your system administrator or servicerepresentative.

ANE4028E Error processing 'filespacenamepath-namefile-name': cannot createfile/directory entry

Explanation: The directory path for files beingrestored or retrieved cannot be created.


User response: Ensure that you have the properauthorization to create the directory for file beingrestored or retrieved.

ANE4029E Error processing 'filespacenamepath-namefile-name': unable to builda directory path; a file exists with thesame name as a directory

Explanation: IBM Spectrum Protect tried to create adirectory path, but is unable to because a file exists thathas the same name as a directory.


User response: Remove the file that has the samename as the directory. Refer to the last restore/retrieveoperation and check all directories along the path.

ANE4030E Error processing 'filespacenamepath-namefile-name': disk space limitfor this process reached

Explanation: The disk space allocated for the clientowner is full.


User response: Free up disk space and retry therestore or retrieve operation.

ANE4031E Error processing'file_space_namepath_namefile_name'. Nameexceeds an internal IBM SpectrumProtect limit.

Explanation: During a file operation, IBM SpectrumProtect encountered a filename where at least onecomponent of the file name (file_space_name,path_name or directory_name or file_name) exceededan internal IBM Spectrum Protect maximum. Theinternal IBM Spectrum Protect limits should not beconfused with the operating system limits forfile_space_name, path_name or directory_name,file_name.

Shown below are the IBM Spectrum Protect internal filename limits for various platforms.

AIX HP-UX SolarisFile_space_name 1024Path_name or directory_name 1023File_name 256

LinuxFile_space_name 1024Path_name or directory_name 768File_name 256

Windows XP/2000/2003File_space_name 1024Path_name or directory_name 248File_name 248

System action: The file is skipped.

User response: Reduce the size of the filename so thatit is smaller that the IBM Spectrum Protect internallimits.

ANE4032E Error processing 'filespacenamepath-namefile-name': file is notcompressed.

Explanation: A file that was flagged as compressedwas not compressed, and the system failed.


User response: See your system administrator toreport this problem. This error is a system failure.

ANE4033E Error processing 'filespacenamepath-namefile-name': file compressedon a different client machine that hasmore memory

Explanation: You are trying to restore a file that wasbacked up and compressed on another clientworkstation that had more memory than your clientworkstation. You cannot restore this file. When the fileis restored, it is expanded and your workstation doesnot have enough memory.

System action: IBM Spectrum Protect canceled theoperation.

ANE4027S • ANE4033E


User response: Obtain a machine with more memoryand retry the operation.

ANE4034E Error processing 'filespacenamepath-namefile-name': unknown systemerror

Explanation: An unknown error occurred. This mightbe a low-level system or communication error that IBMSpectrum Protect cannot handle or recover from.


User response: Retry the operation. If the problemcontinues, determine where the problem exists. Seeyour system administrator for further help.

ANE4035W File 'filespace namepath-namefile-name'currently unavailable on server.

Explanation: You tried to restore or retrieve a file thatis currently not available from the IBM SpectrumProtect server.

System action: IBM Spectrum Protect Cannot restoreor retrieve the file.

User response: Try to restore or retrieve after the filewas made available on the server. See your systemadministrator.

ANE4036E An error occurred saving the registrykey.

Explanation: The active registry key cannot be copiedto the ADSM.SYS staging directory.

System action: Registry backup operation terminates.

User response: Check the space available on theWindows boot partition to ensure there enough spaceto contain a copy of the Windows registry. This mightrequire several megabytes of free space. Also check theWindows permissions on the ADSM.SYS stagingdirectory and ensure that the Windows user underwhich you are running IBM Spectrum Protect has fullaccess to that directory and its contents.

ANE4037E Object 'file-namefile-namefile-name'changed during processing. Objectskipped.

Explanation: The specified file-name was skippedduring backup, archive, or migrate because it waschanging during the attempt to process it.

System action: IBM Spectrum Protect skipped theobject.

User response: If you want the file backed up,archived, or migrated, retry the operation. If it fails,determine why the object is being changed. For moreinformation on backing up, archiving, or migratingchanging objects, see your system administrator.

ANE4038E An error occurred processing file system'filespace name'.

Explanation: File system 'filespace name' is corrupted orcontains one or more corrupted directories and cannotbe processed.

System action: File system is skipped.

User response: Check your system to ensure that it isoperating properly. For the Windows environment, runCHKDSK utility for the failing drive. More informationabout corrupted directories can be found indsmerror.log.

ANE4039E Error processing 'filespacenamepath-namefile-name': compressed fileis corrupted and cannot be expanded.

Explanation: The compressed file cannot be expandedcorrectly due to one of the following reasons:

There is a problem on the tape.

There is a communications problem.

The compressed file was corrupted on the IBMSpectrum Protect Server.


User response: 1) The compressed file is corruptedbecause there is a problem on the tape. To know if thisis the problem, please issue the following command onthe IBM Spectrum Protect Server: audit volume<volume_name> fix=no If there is any problemreported, you could move the data from that volume toa new one (see command MOVE DATA) and try againthe restore. 2) There are communications problemsbetween the IBM Spectrum Protect Server and the IBMSpectrum Protect Client and the results is that the file iscorrupted during the transmission. If you use a gigabitethernet adapter on the Server please upgrade the carddriver (AIX platform) or add provided by SUNsuggested changes to some system network optionswhich have resolved this problem (SUN platform). 3)Please verify with your network support if during therestore there are no any problems between the IBMSpectrum Protect Client/Server that is originating thefile corruption.

ANE4040E Error processing 'filespacenamepath-namefile-name': file systemfilespace name has exceeded its spacemanagement quota.

Explanation: IBM Spectrum Protect detects that thefile system has exceeded its quota. No more data canbe migrated out of this file system.

System action: IBM Spectrum Protect will not migratefiles from this file system.

User response: Recall some files, or ask the systemadministrator to increase the quota for this file system.



ANE4041E A Windows Server 2008 or 2008 R2VMware guest cannot be restored with anon-Windows data mover.

Explanation: A Windows data mover must run certaincommands to complete the restore of the ActiveDirectory. Non-Windows data movers do not have thenecessary tools to complete this operation. WindowsVMware guests that are at Windows Server 2012 orhigher are not affected by this restriction.


User response: Use a Windows data mover tocomplete this action.

ANE4042E Object name 'filespacenamepath-namefile-name' contains one ormore unrecognized characters and is notvalid.

Explanation: The file name, directory name, orvolume label syntax is incorrect.


User response: Check the disk for errors.

ANE4044E Error processing 'filespace-namepath-namefile-name': Case-sensitive nameconflict exists.

Explanation: While processing the specified file on theworkstation, another file name was encountered with asimilar name which only differed in case. TheBackup-Archive client does not allow names whichdiffer only in case on this platform and cannotguarantee the integrity of the file, so the file is skipped.

System action: This object will be skipped.

User response: Rename the file in question to aunique name.

ANE4045E Error processing 'filespace-namepath-namefile-name': Case-sensitive nameconflict exists. The directory tree will beskipped.

Explanation: While processing the specified file on theworkstation, another object name was encountered witha similar name which only differed in case. TheBackup-Archive client does not allow names whichdiffer only in case on this platform and cannotguarantee the integrity of the file, so the directory andall of the objects contained within it are skipped.


User response: Rename the file in question to aunique name.

ANE4046E There is an error processing'filespace-namepath-namefile-name': theobject is corrupted and unreadable.

Explanation: You tried to read from or write to a fileor directory that is corrupted. The corrupted file isskipped. If this is a directory, the objects contained inthe directory and its subdirectories are skipped.


User response: Check your system to ensure that thefilespace is not corrupted by using system tools likechkdsk (Windows) or fsck (UNIX).

ANE4047E There is a read error on'file-namefile-namefile-name'. The file isskipped.

Explanation: The specified file-name was skippedduring backup archive because the file could not beread.

If you are performing a JFS2 snapshot based operation,it is possible that the snapshot was not large enough tocontain all the changes made to the filesystem after thesnapshot was created. This could cause the snapshot tobecome invalid thereby preventing IBM SpectrumProtect client from reading the snapshot.

System action: IBM Spectrum Protect skipped the file.

User response: Check your system to ensure that it isoperating properly.

If you are performing a JFS2 snapshot based operation,please use the default snapshotcachesize of 100% andensure that the volume group has sufficient disk spaceto allocate snapshots at least as large as the file systemand retry the operation.

ANE4048W LAN-Free connection failed.

Explanation: ENABLELANFREE option is set to YESfor this session, but an attempt to establish LAN-Freeconnection failed.

System action: The IBM Spectrum Protect client willfailover to non LAN-Free support.

User response: Review the IBM Spectrum Protecterror.log for LAN-Free failures. Check your LAN-Freesetup and verify that all components are workingproperly.

ANE4049I Established LAN-Free connection.

Explanation: ENABLELANFREE option is set to YESfor this session and the IBM Spectrum Protect clientsuccessfully established LAN-Free connection withserver, after the LAN-Free connection was broken.

System action: The IBM Spectrum Protect client willcommunicate with the server via LAN-Free.

ANE4041E • ANE4049I


User response: Review the IBM Spectrum Protecterror.log for LAN-Free errors. Check your LAN-Freesetup and verify that all components are workingproperly.

ANE4050W Scheduled action 'schedule-action' did notexecute for schedule 'schedule-name' asthe IBM Spectrum Protect administratorhas been disabled from executing thescheduled action on the client.

Explanation: One or more of the client options -schedcmddisabled, srvprepostscheddisabled,srvprepostsnapdisabled, restretrscheddisabled, havebeen set to YES on the client thereby preventing theIBM Spectrum Protect administrator from executing oneof the following scheduled actions on the client -preschedule, postschedule, presnapshot, postsnapshotor scheduled operating system commands, restore orretrieve operations.

System action: The scheduled operation will not beexecuted and a message will be logged to IBMSpectrum Protect Server indicating this.

User response: None required.

ANE4051E Error processing 'filespacenamepath-namefile-name': The decryptionoption is in effect, but the user IDunder which back-up or archive is beingrun is not authorized to decrypt thisencrypted-file-system (EFS) file.

Explanation: The file being processed is encrypted byan encrypted file system (EFS). The option is specifiedto back-up or archive the file in decrypted form. Theuser ID under which the back-up or archive is beingrun does not have decryption rights for this file.


User response: There are three possible ways to makedecryption work:

v Re-encrypt the file under the encryption key of agroup to which both the owner and theback-up/archive user IDs belong

v Add the back-up/archive user ID to the list of usersauthorized to decrypt this file

v Run the back-up or archive under the owner's userID, if possible

ANE4052E Error processing 'filespacenamepath-namefile-name':Encrypted-file-system (EFS) file cannotbe restored, because file system doesnot support restore from the raw-EFSback-up data, or possibly because therestore function does not have writeaccess to the directory.

Explanation: The file being processed is encrypted by

an encrypted file system (EFS). The file was backed upin the raw encrypted format. Either the targetfilesystem does not support the encrypted format, orrestore does not have write access to the directory towhich the file is to be restored.

System action: The restore is terminated.

User response:

v The file cannot be restored to this location if the filesystem is not the AIX Enhanced Journaled FileSystem (JFS2)

v If the file is JFS2 but EFS is not enabled, then EFSmust be enabled before the file can be restored

v If the user ID under which restore is being run doesnot have write permission for the directory, thepermissions must be changed or the restore must berun under a different user ID

ANE4053E Error processing 'filespace path filename':The file cannot be restored because thefile system or operating system does notsupport the Encrypting File System(EFS) data.

Explanation: The specified object was backed-up asraw Encrypting File System (EFS) data. The client istrying to restore or retrieve the object to a destinationthat does not support the EFS data. The location mightnot support the EFS data for one of the followingreasons:

v The operating system does not provide the support,or is a release that does not include the support

v EFS support has not been activated on the operatingsystem

v The target file system does not support the EFS data

System action: The object is not restored or retrieved.Processing continues with the next object.

User response: If this file must be restored, restore itto an AIX operating system environment supportingEFS data.

ANE4054E Error processing 'filespacenamepath-namefile-name': The encryptionkey is not loaded.

Explanation: The file being processed is encrypted byan encrypted file system (EFS). The option is specifiedto backup or archive the file in decrypted form. Theencryption key, required to decrypt the file, is notloaded in the kernel keyring.


User response: There are three situations in which thisproblem can occur:

v You just performed initial activation of EFS on theAIX system, and have not logged out. AIX does loadthe keys for the session running at the time of initialactivation. Solution: Logout and login again.

ANE4050W • ANE4054E


v The login password has been changed recently, andyou normally run with the EFS password the sameas the login password. AIX does not automaticallychange the EFS password when you change the loginpassword. Solution: Issue 'efskeymgr -n' to set theEFS password to be the same as the login password.

v You need to run the decrypting backup when theEFS password is different from the login password.Solution: Issue 'efskeymgr -o ksh' to launch a newshell with the keys loaded. AIX will prompt you forthe EFS password as you launch the shell. Run thebackup from the new shell.

ANE4055E Cannot update file space 'filespace-name':the file space version on the IBMSpectrum Protect server is notcompatible with this client

Explanation: The file space on the IBM SpectrumProtect server is not compatible with this client. This iscaused by performing a backup or archive operationwith a client and then using a down-level client andattempting a backup or archive operation targeting thesame file space.This problem occurs specifically after a Windows orAIX client V6.1 or higher performs a backup or archiveoperation and then a subsequent backup or archiveoperation is attempted with a client V5.5 or lower.


User response: Use the correct level of the client.

ANE4056E Object 'object-name' returned by the IBMSpectrum Protect server has a high-levelname that exceeds the maximum lengthof 6000 characters. The file or directorycannot be processed.

Explanation: The IBM Spectrum Protect serverreturned information about a backup or archive versionwith a high level name that exceeds 6000 characters.The high-level name is the directory path that containsthe object (file or directory).

This message is displayed when all of the followingconditions are true:

v The object was backed up or archived by a version6.1 or lower IBM Spectrum Protect client.

v The object was backed up or archived to a version5.5 or lower IBM Spectrum Protect server.

v IBM Spectrum Protect client version 6.2 or higher isattempting to perform an operation that causes theIBM Spectrum Protect server to return informationabout this object to the client. Note: Duringincremental backup, the server returns information tothe client about active backup versions which is usedto determine which files have changed.

Beginning with IBM Spectrum Protect server version6.1, the maximum high level name length was reduced

from 8192 characters to 6000 characters. Objects withhigh level names that exceed 6000 characters are notsupported for backup or archive. Beginning with IBMSpectrum Protect backup-archive client version 6.2, themaximum high level name length was similarlyreduced.

System action: The file or directory specified in themessage is skipped. Processing will continue with thenext object.

User response: Contact your IBM Spectrum Protectserver administrator for further assistance.

ANE4057W Unable to process object 'fs' with nestedfile system mounted on it duringsnapshot based backup.

Explanation: Snapshot based backup of objects withmounted file systems on them are not supported.

System action: The backup operation continueswithout specified object.

User response: To prevent this behaviour unmountfile system from specified object and retry theoperation.

ANE4058I A write failure occurred whileattempting to save node replicationfailover values to the options file.

Explanation: A write failure is often a result ofinsufficient access permissions to the options file, butcould also be caused by the lack of available diskspace. The replication server connection informationcan not be saved and failover will not be possible.

System action: The operation failed.

User response: Check the local disk for possiblecauses of the write error, and check to see thatsufficient access to the options file is configured.

ANE4059I The option USEREPLICATIONFailoveris set to NO. The node will not fail overto the secondary server

Explanation: This option will prevent the node fromconnecting to the replication server in the event of afailure of the primary server.

System action: The client will not connect to theprimary server and processing stops.

User response: No response is required.

ANE4061I Connected to secondary server secondaryserver; in fail over mode. Home server is:home server;

Explanation: The node is configured for replicationand has successfully connected to the secondary server.This message is to notify the server administrator that a



node has connected to the secondary server in fail overmode.

System action: Processing continues.


ANE4063W IBM Spectrum Protect applicationprotection cannot copy the applicationmetafile 'App-Metadata-File-Name' fromthe following VM: 'VM-Name'.Individual database restore from thisbackup is not supported.Check health of application writers anddatabases

Explanation: The application metafile was not foundon the guest machine.

System action: The operation completes. However, theapplication metafile was not copied.

User response: Make sure that the application VSSwriters are running on this guest machine, and theapplication database is in the state to allow the backup.For Exchange check that databases are mounted. ForSQL check databases are online. Then try the operationagain.

ANE4064I Restoring vCloud Director vApp 'vappname' from Organization VDC 'org vdcname' from organization 'org name'Target vApp name is 'restored vapp name'Restore VAPP command started. Totalnumber of vApps to process: vapps numto restore

Explanation: The restore vApp operation completed.

System action: This message is for informationalpurposes only.

User response: No action is required.

ANE4065E Proxy rejected: data mover node 'dmnode' has not been granted proxyauthority for target node 'target_node',associated with Organization vDC'OVDC name' of Organization 'Org Name'.

Explanation: The operation requires that a proxyaccess for the data center node is granted to the datamover node.

System action: Operation is canceled for the specifiedvApp.

User response: Run configuration wizard orconfiguration editor to configure proper nodesrelashionship.

ANE4066I Snapshot operation attempt x of y forthe guest virtual machine 'VM' failedusing "sType" snapshot.Reattempting snapshot with "sType2"snapshot.

Explanation: The snapshot operation has failed. Asnapshot retry operation has been scheduled.

System action: Retrying snapshot.

User response: Check the error log for any othermessages that might indicate a reason for the failure.Correct any problems and try the operation again.

ANE4067E Snapshot operation attempt x of y forthe guest virtual machine 'VM' failedusing "sType" snapshot.Backup failed.

Explanation: All snapshot retry attempts of the guestvirtual machine failed.


User response: Check the error log for any messagesthat indicate a reason for the failure. Correct anyproblems and try the operation again. If the problempersists, search the Support web site(http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html) for knownsolutions.

ANE4068I Restored virtual machine 'VM' wasbacked up using a "VMware Tools withfile system quiescing and applicationquiescing disabled" snapshot.This is equivalent to a "crash-consistent"backup.

Explanation: The restored virtual machine was backedup using a "VMware Tools with file system quiescingand application quiescing disabled" snapshot.Application Protection feature is not available.

System action: Restore of the VM continues.

User response: None

ANE4069E The Windows domain credentialscannot be found. Use the DataProtection for VMware vSphere GUIconfiguration editor to set the Windowsdomain credentials.

Explanation: The required Windows domainadministrator credentials were not set.


User response: Set the Windows domainadministrator credentials in the Data Protection forVMware vSphere GUI configuration editor.



ANE4070E Windows domain credentials areincorrect. Verify the credentials and usedsmc SET PASSWORD -type=DOMAIN'domain\userid' 'password' to updatethe username and password.

Explanation: The supplied credentials are incorrect.The system failed to authenticate to the Windowsdomain using these credentials.

System action: Processing stops

User response: Use dsmc SET PASSWORD-type=DOMAIN 'domain\userid' 'password' to updatethe username and password. And then retry theoperation.

ANE4071E 'VM-Name' cannot be restored because itwas backed up with a newer version ofthe client.

Explanation: The client version that attempted torestore the virtual machine is earlier than the clientversion that backed up the virtual machine. The virtualmachine cannot be restored with an earlier clientversion.

System action: The virtual machine is not restored.Processing continues with the next virtual machine.

User response: Upgrade the client to a version that iscompatible with the client version that backed up thevirtual machine.

ANE4072E Error processing 'filespacenamepath-namefile-name': unable to createsymbolic link; a file or directory existswith the same name as the symboliclink

Explanation: IBM Spectrum Protect tried to create asymbolic link, but is unable to because a file ordirectory exists that has the same name as the symboliclink.


User response: Remove the file or the directory thathas the same name as the symbolic link. Refer to thelast restore/retrieve operation.

ANE4073W Snapshot operation attempt x of y forthe guest virtual machine 'VM' failedusing "sType" snapshot.Reattempting snapshot with "sType2"snapshot.

Explanation: The snapshot operation has failed. Asnapshot retry operation with different snapshot typehas been scheduled.

System action: Retrying snapshot with differentsnapshot type.

User response: Check the error log for any othermessages that might indicate a reason for the failure.Correct any problems and try the operation again.

ANE4077E File 'filespace namepath-namefile-name' isencrypted by Microsoft EFS andcontains at least one sparse data stream.The operating system does not supportrestore for this file so it is not backedup or restored.

Explanation: An error in the Microsoft Windows APIprevents successful restore of files that meet thefollowing conditions:

v The file is encrypted by Microsoft Encrypting FileSystem (EFS) at the time it was backed up

v The file includes at least one data stream (alternate"named" stream or unnamed stream) that is sparse

v The operating system is any edition of Microsoft XP,Microsoft Windows Server 2003, or MicrosoftWindows Server 2003 R2

Because the file cannot be restored, IBM SpectrumProtect does not back it up. The problem isdocumented by Microsoft at http://support.microsoft.com/kb/2525290.

System action: The file is not backed up or restored.Processing continues with the next object or ends ifthere are no further objects.

User response: If this message is issued during abackup operation, you can do the following:

v Disable EFS encryption for the file so that it can bebacked up.

v If a backup copy of the file is not necessary, you canexclude it from backup.

ANE4078E Content file content.spsig is missing, isdamaged or failed the signature check.

Explanation: The file content.spsig is missing. Or thefile is damaged or the signature of the file does notmatch. See client log file for more information.


User response: Make sure that the data in theOperations Center, such as the client package orUpdate Manager package, is correct or download thecorrect version in the Operations Center.

ANE4079E One or more files failed the signaturecheck.

Explanation: The signature of one or more files doesnot match the contents of content.spsig. See the clientlog file for more information.


User response: Make sure that the data in theOperations Center, such as the client package or



Update Manager package, is correct or download thecorrect version in the Operations Center.

ANE4081E Error processing 'filespace-name': filespace type is not supported.

Explanation: The specified file space type is notcurrently supported by IBM Spectrum Protect on thisplatform.

System action: The unsupported file system isskipped. Processing continues with the next file system.

User response: Refer to the documentation forinformation on what file space types are supported.

ANE4083I New node password has beengenerated.

Explanation: The client logged in using administrativeid rather than node name. New random node passwordhas been generated and recorded.



ANE4084E Error processing 'filespace-namepath-namefile-name': cannot get file status.

Explanation: While processing the file, the lstat() callset EOVERFLOW error code.

System action: This file will be skipped.

User response: The file is skipped. Processingcontinues with the next file.

ANE4085I Assigned 'number' objects from previoussystemstate backup to the newsystemstate backup.

Explanation: Objects in the previous System Statebackup have not changed and were assigned to thenew System State backup.



ANE4086W Failed to assign unchanged objects fromprevious systemstate backup to the newsystemstate backup. Objects will bebacked up.

Explanation: Objects in the previous System Statebackup have not changed and should be assigned tothe new systemstate backup. Due to error assignoperation failed and objects will be backed up.


User response: Retry the operation. If the problempersists, contact IBM Spectrum Protect technicalsupport.

ANE4087E An attempt to load data for the wizardfailed.For more information, please see the logfile.

Explanation: An attempt to load data for the wizardfailed as the remote agent is probably unavailable.


User response: Check the log for reason for thefailure.

ANE4089W File server file-server-name has beenupgraded to Data ONTAP version'version.modifcation.submodification'.Perform a full incremental backup byspecifying optioncreatenewbase=migrate as soon aspossible.

Explanation: The file server has been upgraded to aversion that supports unicode file names forincremental backup using snapshot difference. Performa full incremental in order to backup any files withunicode names that may have been skipped by theprevious version of the IBM Spectrum Protect client.


User response: Perform a full incremental byspecifying the command line optioncreatenewbase=migrate with the snapdiff option assoon as possible.

ANE4090I File server file-server-name has beenupgraded to Data ONTAP version'version.modifcation.submodification'.Perform a full incremental backup byspecifying optioncreatenewbase=migrate as soon aspossible.

Explanation: The file server has been upgraded to aversion that supports unicode file names forincremental backup using snapshot difference. Performa full incremental in order to backup any files withunicode names that may have been skipped by theprevious version of the IBM Spectrum Protect client.


User response: Perform a full incremental backup byspecifying the command line optioncreatenewbase=migrate with the snapdiff option assoon as possible.

ANE4092E Data mover platform is not supportedfor instant access/restore operations.

Explanation: The instant access/restore operationfailed.

System action: The instant access/restore operation



failed. The reason for the failure is unsupportedplatform.

User response: The instant access/restore operationshould be performed from a supported data moverplatform.

ANE4099E The system volume cannot beidentified. Therefore the system statecannot be backed up.

Explanation: The system volume contains thehardware-specific system state files that are needed tostart Windows, such as Ntldr, Boot.ini, Ntdetect.com orBootmgr. If the system volume cannot be identified,then these files cannot be backed up. Therefore it is notpossible to back up the system state.

System action: Systemstate backup stops.

User response: Try the operation again. If the problempersists, obtain a service trace that captures theproblem and contact IBM technical support foradditional assistance. Your IBM Spectrum Protectadministrator can help you configure the trace.

ANE4137E Error processing 'filespacenamepath-namefile-name': exceededmaximum number of links allowed

Explanation: Link cannot be restored or retrievedbecause the destination file system has exceededmaximum number of links allowed.


v Skip this object

v Abort the action

User response: Select the appropriate action for thisobject. Restore or retrieve the link to another filesystem.

ANE4148E Full VM backup of Virtual Machine'vmname' failed with RC rc

Explanation: The Full VM backup of virtual machinefailed.

System action: The full backup of the virtual machinefinished with failures. The next virtual machine in thevmlist will be processed. The reason for the failure iswritten to the local client error log.

User response: Check the local client error log forreason for the failure.

ANE4150E Incremental backup of Virtual Machine'vmname' failed with RC rc

Explanation: The incremental backup of virtualmachine volumes failed.

System action: The backup of the virtual machinefinished with failures. The next virtual machine in the

vmlist will be processed. The reason for the failure iswritten to the local client error log.


ANE4151E Failure mounting Virtual Machine'vmname'. RC=rc

Explanation: The VMware failed to mount virtualmachine disk.

System action: The backup of the virtual machine cannot continue. The next virtual machine in the vmlistwill be processed. Refer to dsmerror.log for detailederror message for the reason for the failure.

User response: Refer to dsmerror.log for detailed errormessage.

ANE4152E Failure initializing VMware virtualmachine environment. RC=rc. Refer toIBM Spectrum Protect error log fordetailed error messages.

Explanation: Failure initializing VMware virtualmachine environment. Refer to IBM Spectrum Protecterror log for detailed error messages.

System action: The backup can not continue.

User response: Refer to IBM Spectrum Protect errorlog for detailed messages.

ANE4153E Hostname could not be found forVirtual Machine 'vmname'

Explanation: The backup of virtual machine failed.

System action: The backup of the virtual machinefinished with failures. The next virtual machine in thevmlist will be processed. The reason for the failure iswritten to the local client error log.


ANE4154E Possible cause Virtual Machine is notrunning and does not have a static IPaddress.






ANE4155E Virtual Machine 'vmname' could not befound on VMware server.




ANE4156E File level VM backup of virtual machine'vmname' not supported.File level VM backup not support onnon Windows platform guest OS.Platform type: 'platform'.



User response: Back up the virtual machine using theVMBACKUPType=FULLvm option.

ANE4159E Backup of Virtual Machine 'vmname'failed. rc=rc.




ANE4160E Proxy Rejected: Proxy authority has notbeen granted to Agent Node: 'agent_node'for Target Node: 'target_node'.


System action: The backup of the virtual machinefinished with failures. The next virtual machine in thevmlist will be processed. The reason for the failure isthe node has not been granted proxy authority toaccess the node named by the backup proxy node. TheIBM Spectrum Protect administrator must first grantproxy authority.

User response: The IBM Spectrum Protect serveradministrator must grant proxy authority for this node.See the administrator command "Grant Proxynode".

ANE4161E Duplicate virtual machine name'vmname' was detected in the samebackup operation. Backup of virtualmachine 'vmfullname' can not continuewithout a unique object name.



User response: Choose a unique name for the virtualmachine.

ANE4162E The virtual machine'virtual-machine-name' has not beenpreviously backed up.

Explanation: The specified virtual machine has notbeen previously backed up, so can not be specified forrestore.

System action: The specified virtual machine isskipped, and the next virtual machine in the restore listis processed.

User response: Verify the virtual machine name to berestored, and re-try the operation.

ANE4164W Compression is currently enabled, butthe virtual machine backup for'virtual-machine-name' is not compressedbecause client-side deduplication is notbeing used.

Explanation: Compression can only be used withvirtual machine CTL and Data files when the files arestored in a storage pool that is enabled for client-sidededuplication. This message is issued when the client isconfigured for compression and virtual machine CTL orData files are directed to a storage pool that is notenabled for client-side deduplication.

System action: Backup continues, and data is notcompressed.

User response: If you intend to compress virtualmachine CTL and Data files, then update yourconfiguration so that both types of files are directed tostorage pools that are enabled for client-sidededuplication. If you intend to compress virtualmachine Data files but not CTL files, then update yourconfiguration so that the Data files are directed to astorage pool that is enabled for client-sidededuplication. Set the VMSKIPCTLCOMPRESSION toYES in your client options file. If you do not intend touse compression, then set COMPRESSION NO in yourclient options file.



ANE4165E Creating a Virtual Machine, but thehostname 'virtual-machine-name' was notfound.

Explanation: The Virtual Machine being creating musthave a valid hostname to be created.

System action: Check the virtual machine hostnamespecified for correctness.

User response: Correct the virtual machine hostnamespecified and retry the restore.

ANE4166E Creating a Virtual Machine, but thedatacenter 'virtual-machine-name' was notfound. The name may be incorrect ormay be located in a VMware folder andrequire the folder name such asvmfolder/dcname.

Explanation: The Virtual Machine being created musthave a valid datacenter to be created.


User response: Check the virtual machine datacenterspecified for correctness. If the datacenter is containedin a folder then the full datacenter name, complete withthe folder path, must be specified, such asvmfolder/dcname.

ANE4167E Creating a Virtual Machine, but thedatastore 'virtual-machine-name' was notfound.

Explanation: The Virtual Machine being creating musthave a valid datastore to be created.

System action: Check the virtual machine datastorespecified for correctness.

User response: Correct the virtual machine datastorespecified and retry the restore.

ANE4168E VMware has reported an error via theirSOAP interface. On the Detailed StatusReport panel, view the last errormessage reported. Also check the errorlog for more information about theproblem that occurred.

Explanation: The command to VMware failed tocomplete. The error returned is displayed on theRestore or Backup summary panel under the Last ErrorMessage section.

System action: An error occurred, and the operationfailed.

User response: Check the reported error and correctthe problem. Usually the reason for the error is auser-supplied value which is not valid for theoperation.

ANE4169E A write failure occurred on the localdisk proxy used to temporarily store thevirtual machine virtual diskinformation. The write failure can becaused by the lack of available diskspace on the drive used to store thisinformation. The VMBACKDIR optioncan be used to assign a different disklocation for this purpose. Check thedrive being used and ensure that thereis enough space available for thisoperation.

Explanation: There was a write error from the localdisk used to store the virtual machine virtual diskinformation. Usually the write error is due to lack ofdisk space, lack of write permissions, or some similarproblem with the local disk. The VMBACKDIR optioncan be used to assign a different disk location if thelocal drive does not have enough free space for theoperation.

System action: A disk write error occurred, and theoperation failed.

User response: Check the local disk for possiblecauses of the write error, and use the VMBACKDIRoption to assign another disk if needed.

ANE4170E Can not create a Virtual Machine onVMware release 'release-version-target'which was backed up from VMwarerelease 'release-version-source'.

Explanation: The Virtual Machine being created wasbacked up from a version of VMware which is notcompatible with the target VMware release versionbeing used for the restore.


User response: Restore the Virtual Machine to aVMware system which is compatible with the levelfrom which the Virtual Machine was backed up.

ANE4174E Full VM backup of VMware VirtualMachine 'vmname' failed with RC=rcmode=full_or_incr, target nodename='target_node_name', data movernode name='data_mover_node_name'






ANE4177E Full restore of VMware virtual machine'vmname' failed with RC=rc,mode='restore_or_revert', target nodename='target_node_name', data movernode name='data_mover_node_name'

Explanation: The full restore of the virtual machinefailed.

System action: The full restore of the virtual machinefinished with failures. The next virtual machine in thevmlist will be processed. The reason for the failure iswritten to the local client error log.


ANE4179I IBM Spectrum Protect applicationprotection did not truncate the MicrosoftSQL Server logs on VM 'VM'.

Explanation: The SQL server logs were not truncatedbecause the following option was specified for thisvirtual machine: INCLUDE.VMTSMVSS vnameOPTIONS=KEEPSQLLOG

System action: The operation completes.

User response: Remove the OPTIONS=KEEPSQLLOGoption to enable truncation of the SQL logs when abackup completes.

ANE4187W CPU and Memory Resource Allocationconfiguration settings cannot be restoredwhen the IBM Spectrum Protect datamover node is connected directly to aVirtual Center managed ESX/ESXi host.These settings have been skipped.

Explanation: The VMware vStorage APIs do notsupport the restore of CPU and Memory ResourceAllocation configuration settings when connecteddirectly to an ESX/ESXi host that is managed by aVirtual Center.

System action: CPU and Memory Resource Allocationconfiguration settings are skipped. Processingcontinues.

User response: Virtual machine CPU and MemoryResource Allocation configuration settings will berestored when the IBM Spectrum Protect data movernode connects directly to a vCenter Server. Modify theVMCHOST to connect the IBM Spectrum Protect datamover to a vCenter Server.

ANE4191E Restore VM operation failed using 'san'transport mode. In some cases switchingfrom SAN to network-based VMrestores can be successful.

Explanation: Restore VM operations that fail usingSAN transport mode can often be successful over aLAN path. If a restore vm operation fails using the

'SAN' transport mode, set the client optionVMVSTORTRANSPORT to "nbd:nbdssl" and try therestore vm operation again.

System action: Restore VM operation failed using 'san'transport mode. Restore may be successful using'nbd:nbdssl' transport modes.

User response: Restore VM operation failed using'san' transport mode. In some cases network-based VMrestores can be successful when using 'nbd' or 'nbdssl'transport modes. The VMVSTORTRANSPORT optioncan used to restrict the IBM Spectrum Protect client touse only the specified transport modes.

ANE4193E vApp 'vApp name' cannot be processedbecause data mover 'dm node' cannotconnect to the target node 'target_node'.

Explanation: The operation requires that a proxyaccess for the data center node is granted to the datamover node.

System action: Operation is canceled for the specifiedvApp.

User response: Look for errors in error log and correctany problems. Run configuration wizard orconfiguration editor to ensure proper nodesconfiguration.

ANE4194E Encryption is currently enabled, but isnot supported for incremental foreverbackups of virtual machines(-MODE=IFFULL or-MODE=IFINCREMENTAL) .

Explanation: Client encryption of virtual machineincremental forever backups (-mode=IFFULL or-mode=IFINCREMENTAL) is not supported. In orderto avoid the unintentional storage of unencrypted dataon the server, the backup operation stops.

System action: The virtual machine backup stops.

User response: Remove the encryption options for thisoperation and run it again. You can use Secure SocketsLayer (SSL) encryption to encrypt the data over thenetwork. If the backup data must be encrypted in IBMSpectrum Protect storage pools, use an alternativebackup method such as full and incremental backups(-mode=FULL and -mode=INCREMENTAL), orin-guest backups.

ANE4195E The target node for Organization VDC'OrgVDC name' in Organization 'Orgname' was not found. As a result, vApp'vApp name' cannot be backed up.

Explanation: Either the IBM Spectrum Protect nodefor the specified organization VDC was not found onthe IBM Spectrum Protect server, or information aboutthe Organization VDC node was not found in theProvider VDC node.



System action: Back up of the specified vApp stops.Processing continues to the next vApp.

User response: Go to the Configuration page and click'Run the Configuration Wizard' to verify that allrequired IBM Spectrum Protect nodes are registered onthe IBM Spectrum Protect server. If required, register anew data mover node. Make sure that the organizationVDC belongs to the provider VDC that this data movernode protects.

ANE4199W File 'file name' is not backed up as partof the system state because cluster disk'volume name' is not accessible.

Explanation: The indicated file or directory wasreturned by VSS as part of the backup file list of thewriter. However, the cluster disk where the file islocated is not accessible. The reasons for this problemcan be that the cluster disk is offline or belongs toanother node.

System action: The file is not backed up. Processingcontinues.

User response: This problem is documented inMicrosoft knowledge base topic 980794http://support.microsoft.com/default.aspx?scid=kb;EN-US;980794. The topic includes a hotfix. With the hotfix,you can specify a registry key that contains a list of oneor more files to be excluded from VSS enumeration.IBM Spectrum Protect does not back up files that arenot enumerated by VSS. If the volume is broughtonline to the node performing the system state backup,then it cannot be backed up. You must remove thevolume from the registry key and restart the systembefore you can back up the volume.If you do not want to implement the hotfix for thisproblem, IBM Spectrum Protect continues to issue thismessage.

ANE4200E The virtual machine 'vmname' could notbe backed up because the data usage ofdatastore 'datastore' exceeded thedatastore threshold of percentusedpercent.

Explanation: The data usage of the datastore used bythe virtual machine exceeds the threshold set by theVMDATASTORETHRESHOLD option.

System action: The virtual machine is not backed up.

User response: Reduce the data usage of the datastoreor increase the threshold in the VMDATASTORETHRESHOLDoption. Then, back up the virtual machine again.

ANE4202E The Deployment Manager failed toinstall language pack: language packname. The Microsoft Installer error codewas error code.

Explanation: The previous language pack has been

uninstalled, and the installation of the new languagepack failed.


User response: For more information about Windowsinstaller error messages, go to the Microsoft DeveloperNetwork (MSDN) technical library athttp://msdn.microsoft.com/en-us/library and searchon "Windows Installer Error Messages".

Check the install log on the client computer.

ANE4204E The Operating System of the clientcomputer: 'os name' is not supported bythe target version: 'target version'

Explanation: The operating system level of the clientcomputer is no longer supported by the target level.


User response: Check the release documentation forinformation on supported operating system levels.

ANE4206E The Deployment Manager received anerror while extracting from installationimage: image name.

Explanation: The installation image might be missing,corrupted, or there might be insufficient disk space onthe client computer.

System action: Deployment Manager stops.

User response: Make sure that there is sufficient diskspace on the client computer.

Make sure that all of the Windows self extracting clientimages on the client computer are valid.

ANE4207E The Deployment Manager was unableto initiate the final connection betweenthe server and the updatedbackup-archive client.

Explanation: After the automatic client deployment,the dsmc query session command from the updatedbackup-archive client was not successful.

System action: The Deployment Manager processends.

User response: Log on to the client computer andcheck the backup-archive client error log.

ANE4210E The Deployment Manager failed toinstall package: 'client package name'. TheMicrosoft Installer error code was'system architecture'

Explanation: The previous client package has beenuninstalled, and the installation of the new clientpackage failed.




User response: Check the technote for MicrosoftInstaller error code description: http://www-01.ibm.com/support/docview.wss?uid=swg21050782&rs=663


ANE4212E The Deployment Manager failed torestart service: servicename

Explanation: After the automatic client deployment,the IBM Spectrum Protect client services failed to start.


User response: Log on to the client machine andcheck the backup-archive client error log.

ANE4213E Automatic restart of the client computerwas required because reason

Explanation: The Deployment Manager determinedthat the deployment requires restarting the client.

Automatic restart is not enabled. The DeploymentManager process cancels the deployment.

The current client is not uninstalled or updated.

System action: Deployment Manager cancels the clientdeployment and stops

User response: Reschedule the client deployment.

ANE4215E The automatic deployment path fromthe current client code version 'sourceversion' to the client package version'target version' is not supported.

Explanation: None


User response: Refer to the Backup-Archive Clientdocumentation in the information center.

Reschedule the client deployment with an appropriatetarget level.

ANE4217E The Deployment Manager received anerror while setting up the client API.The standard API function beinginvoked is API setup function name.

Explanation: The Deployment Manager process failedwhen setting up the client API.


User response: Check the error log on the clientcomputer.

ANE4218E The Deployment Manager received anerror while initializing the client API.The standard API function beinginvoked was API setup function name.

Explanation: The Deployment Manager process failedwhen initializing the client API.



ANE4219E The Deployment Manager received anerror while creating a pipe for thestandard output of the child process.

Explanation: The Deployment Manager failed tocreate a pipe for the standard output of the childprocess.



ANE4220E The Deployment Manager is unable todetermine if IBM Spectrum Protectprocesses are still running.

Explanation: The Deployment Manager could notdetermine whether all IBM Spectrum Protect processeswere shut down successfully.

System action: Reschedule with automatic restart(autoreboot) enabled.

User response: None

ANE4221E The architecture of the package: 'packagearchitecture' does not match the currentclient: 'system architecture'

Explanation: The setup script was unable to retrievethe matching package from the server.


User response: Ensure that the client packages for allarchitectures are available on the server.

ANE4222E The Deployment Manager is unable toread information in file: file name.

Explanation: Deployment Manager failed to open afile containing required system information.





ANE4227E The Deployment Manager failed toinstall package: 'client package name'. Theclient computer is out of disk space. TheMicrosoft Installer error code was 'errorcode'

Explanation: The previous client package has beenuninstalled, and the installation of the new clientpackage failed because the client computer is out ofdisk space.




ANE4228E The Deployment Manager failed toinstall language pack: 'language packname'. The client computer is out of diskspace. The Microsoft Installer error codewas 'error code'

Explanation: The previous language pack has beenuninstalled, and the installation of the new languagepack failed because the client computer is out of diskspace.




ANE4229I The client computer is required torestart to complete the newBackup-Archive client installation.

Explanation: The deployment of the newbackup-archive client will not be complete until theclient computer is restarted. The restart is scheduled tohappen immediately after all language packs aredeployed.

System action: The Deployment Manager processcontinues. The client computer will be shut down andrestarted after all language packs are deployed, orimmediately if there are no language pack to install.

User response: None

ANE4230I The client computer will be shut downand restarted immediately.

Explanation: The Deployment Manager needs torestart the client computer to complete the clientdeployment. It is possible the other messages providedetails of the deployment.

System action: The Deployment Manager processcontinues. The client computer will be shut down andrestarted immediately after all language packs aredeployed, or immediately if there are no language packto install.

User response: None

ANE4232E Self-extracting installation image: imagename cannot be found.

Explanation: The Deployment Manager could not findthe required installation image.

System action: Processing stops. Client deploymentwill be cancelled.

User response: Check the server's activity log or thescheduler log on the client computer. Reshcedule theclient deployment.

ANE4234E The deployment for language packsfailed.

Explanation: The Deployment Manager failed toinstall one or more language packs. It is possible theother messages provide details of the installation.

System action: The Deployment Manager processcontinues.

User response: Check the error log and installation onthe client computer. Identify the language packs thatfailed to install and manually deploy them.

ANE4235I The deployment manager cannot logevents to the server.

Explanation: The Deployment Manager is unable tolog events to the server. It is possible the othermessages provide details of the communications.

System action: The Deployment Manager processcontinues. Events will be logged locally on the clientmachine only.

User response: Check network connection and theerror log on the client computer.

ANE4242E The setup script encountered a warningor error while retrieving the clientpackage for the architecture architecture.The error level is error level error level.

Explanation: It is possible that the client package isnot available on the server.


User response: Ensure that client packages for allarchitectures are available on the server. Check thebackup-archive client error log for more detailed errormessages.



ANE4248E The client is already at the target level:target version.

Explanation: Processing stopped because theautomatic client deployment feature does not supportthe installation of a client to a workstation that isalready at its target level.

System action: Your current backup-archive client isnot affected.

User response: Refer to the Backup-Archive Clientdocumentation in the information center.

Reschedule the client deployment with an appropriatetarget level.

ANE4251W writername file 'filename': not found.

Explanation: The indicated VSS writer file or directorywas returned by VSS as part of the backup file list ofthe writer. However, the object does not exist on thedisk..

System action: Processing stops ifSKIPMISSINGSYSWFILES option is set to NO.Processing continues if SKIPMISSINGSYSWFILESoption is set to YES.

User response: Verify that this file can be skippedduring system state backup.

ANE4252W architecture, schedule-name, domain-name :The client deployment was notcompleted pending the restart of theclient computer. The deploymentmanager did not restart the clientcomputer automatically because theAUTODEPLOY option was set toNOREBOOT.

Explanation: The previous client has been uninstalled,and the installation of the new client was notcompleted pending the restart of the client computer.The architecture of the client, schedule name, anddomain name are identified at the beginning of themessage text.

System action: The Deployment Manager processcompletes.

User response: Manually restart the client computeras soon as possible.

ANE4253E There was not enough disk space on theclient computer. Required space: packagespace bytes; available space: system spacebytes.

Explanation: The deployment manager determinedthere was insufficient free disk space for the clientdeployment.


User response: Free up required disk space andreschedule the client deployment.

ANE4254E The deployment manager detected anHSM client on the workstation that itneeds to deploy the Backup-Archiveclient to.

Explanation: An attempt was made to deploy theBackup-Archive client to a workstation that already hasthe HSM client installed. The Backup-Archive clientcannot be deployed to a workstation that has the HSMclient.


User response: Uninstall the HSM client andreschedule the Backup-Archive client deployment.

ANE4255E There is not enough memory for thedeployment manager to create thesystem information object

Explanation: The system information object could notbe created because there is not enough available RAMto temporarily write the data into.


User response: Close all unneeded applications on theclient workstation and reschedule the deployment.

ANE4256E The DSMI_DIR environment variable isnot defined.

Explanation: The deployment manager cannot initiatea connection to the server because the DSMI_DIRenvironment variable is not set. This error can occur ifthe deployment manager is started without using theclient scheduler.


User response: Read the available documentation todetermine how to use the client scheduler to create aclient deployment task.

ANE4257E The deployment manager cannot parseinformation in file: file name.

Explanation: The deployment manager could notparse or extract the required information from thespecified file.


User response: Check the error log file on the clientworkstation.



ANE4258E The deployment manager received theWindows "OpenSCManager failed" errormessage.

Explanation: The deployment manager could notconnect to the Windows service control manager tostart the client scheduler. In general, this error occursbecause the user who is initiating the task does nothave sufficient authority.


User response: Ensure that the user who starts theclient scheduler has administrative privileges.

ANE4259E The client scheduler is not started as aroot user.

Explanation: The client scheduler requires root userprivileges to upgrade the client code.


User response: Log in as root and start the clientscheduler.

ANE4260E The installation file system is notwriteable.

Explanation: The deployment manager cannot writeto the installation file system.


User response: Check the installation file systempermissions. It is possible that the current client noderuns in a virtualized environment using the client codeinstalled in a shared storage of the physicalenvironment. Reschedule the client deployment withthe client node in the physical environment.

ANE4261E The deployment manager cannotupgrade the Backup-Archive Client.

Explanation: The Backup-Archive Client cannot beupgraded because either the current location is not thedefault installation location or the DSM_DIR,DSMI_DIR, DSM_CONFIG and DSMI_CONFIGenvironment variables are defined with a relative pathand not an absolute path.


User response: Check the installation directory of thecurrent Backup-Archive Client. If the Backup-ArchiveClient is not installed in the default location, manuallyupgrade the Backup-Archive Client. If the DSM_DIR,DSMI_DIR, DSM_CONFIG and DSMI_CONFIGenvironment variables are defined with a relative path,define them with an absolute path and try the clientdeployment again.

ANE4262E The preview of the client installationfailed.

Explanation: The deployment manager did notuninstall the current client. The client code isunchanged.


User response: Check the deployment manager logand trace files on the client workstation for specificissues identified during the preview. Reschedule adeployment after any issues are resolved.

ANE4263E The deployment manager failed touninstall the backup-archive client.

Explanation: The deployment manager received anerror while uninstalling the current client.


User response: Check the deployment manager logand trace files on the client workstation for moredetails on the error. You might have to manuallyuninstall the client.

ANE4264E The deployment manager failed toinstall the backup-archive client.

Explanation: The current client was uninstalled andthe deployment manager received an error whileinstalling the new client code.


User response: Check the deployment manager logand trace files on the client workstation for moredetails on the error. Manully install the new client afterthe issue is resolved.

ANE4265I Client deployment options are notspecified in the scheduler command orfrom client services.

Explanation: The default client options file will beused. The deployment manager might not report thecorrect server and node information when reportingstatus.


User response: Avoid initiating the client deploymentdirectly from the command-line, instead, always startthe client scheduler as a Windows service.

ANE4266I The deployment manager failed toinstall non-English language pack(s).

Explanation: The previous packages were uninstalled,and the installation of one or more new language packswere not successful.




User response: Check the deployment trace file on theclient workstation for specific language packinformation.

ANE4267I The deployment manager failed toinstall the hardware plugin package.

Explanation: The previous package was uninstalled.The installation of the new hardware plugin packagefailed.


User response: Check the deployment trace file on theclient workstation.

ANE4268I The deployment manager failed toinstall the journal-based backuppackage.

Explanation: The previous journal-based backuppackage was uninstalled. The new journal basedbackup package installation failed.


User response: Check the deployment trace file on theclient workstation.

ANE4269W The deployment manager is stoppingthe scheduler or the CAD processes.

Explanation: Before deploying the new client, thedeployment manager must stop the scheduler andCAD processes. After the deployment, the processesmust be restarted.


User response: The client scheduler is interruptedduring the deployment.

ANE4270I The deployment manager and the newclient installation packages weredownloaded to directory: file name.

Explanation: The download directory containseverything required to complete the new clientdeployment. Deployment log and trace files can befound in the log/ sub-directory.


User response: Obtain log and trace files from thedownload directory for problem determination. Thefiles are found within the log/ sub-directory.

ANE4271E The deployment package is missing oneor more required installation imagefiles.

Explanation: The client deployment package mightnot have been imported correctly to the server. It ispossible that the deployment package is not retrieved

completely to the client computer, due to a lack of diskspace.


User response: Ensure that client packages areavailable on the server and there is sufficient disk spaceon the client computer. Check the backup-archive clienterror log file for more detailed error messages.

ANE4272E The processor type of the package:package processor type does not match thecurrent client: system processor type..

Explanation: The processor type supported by theclient package that you want to deploy does not matchthe processor type of the workstation that you aretrying to deploy the client to. It is not always possiblefor the deployment manager to connect to the serverand report the error.


User response: Verify that you are using the correctclient package for the processor architecture of thecomputer that you want to upgrade. Then restart thedeployment.

ANE4273E The deployment manager detected ajournal based backup (JBB) client on theworkstation where it needs to deploythe Backup-Archive Client.

Explanation: An attempt was made to deploy theBackup-Archive Client to a workstation that alreadyhas the JBB client installed. On some platforms, theBackup-Archive Client cannot be deployed to aworkstation that has the JBB client installed.


User response: Uninstall the JBB client and reschedulethe Backup-Archive Client deployment.

ANE4274E The deployment manager cannot stopthe scheduler or the CAD processes.

Explanation: The deployment manager tried to shutdown the Backup-Archive Client scheduler or CADprocesses but the Backup-Archive Client might be busywith other tasks.


User response: Reschedule the Backup-Archive Clientdeployment.

ANE4275E The deployment manager cannot restartthe scheduler or the CAD processes.

Explanation: Before exiting, the deployment managercould not restart the Backup-Archive Client scheduleror CAD processes. The deployment manager stopped

ANE4267I • ANE4275E


the processes prior to the client upgrade.


User response: Log on to the Backup-Archive Clientworkstation and check the error log file. If you have setenvironment variables make sure they are not definedusing relative path.

ANE4276E The deployment manager cannot obtaininformation about the scheduler or theCAD processes.

Explanation: The deployment manager needs processinformation in order to stop and restart theBackup-Archive Client scheduler or CAD processes.


User response: Log on to the Backup-Archive Clientworkstation and check the error log file and thedeployment manager error log file.

ANE4277E The target operating system versiontarget operating system does not meet theminimum required version minimumrequired version

Explanation: The operating system version is earlierthan the version required by the automatic deploymentpackage.

System action: The deployment is canceled.

User response: Ensure that the version beingdeployed is supported by the target operating system.

ANE4278E The deployment manager cannot obtaininformation about the Logical VolumeSnapshot Agent (LVSA).

Explanation: The deployment manager needs todetermine whether an LVSA is installed on the clientworkstation.


User response: Log on to the Backup-Archive Clientworkstation and check the error log file and thedeployment manager error log file.

ANE4280E Automatic client deployment is notallowed on the client workstation.

Explanation: One or more of the running clientservices include AUTODEPLOY = NO in the optionfile.


User response: Change the AUTODEPLOY option onthe client and reschedule the client deployment.

ANE4281E The update manager cannot remove theTIVsmCapi package from non-globalzone(s): zone name.

Explanation: APAR IC57433 prevents the removal ofthe TIVsmCapi package on Solaris on a sparse-root,non-global zone if uninstalling is done from the globalzone.


User response: Manually uninstall the client directlyfrom the non-global zones and reschedule thedeployment.

ANE4282E Sparse-root non-global zone(s) werefound with Backup-Archive Client thatwas installed from the non-global zone:zone names.

Explanation: One or more non-global zones aresharing the /usr file system with the global zone. TheBackup-Archive Client is installed in the global zonewith the -G parameter and also installed manually inthe non-global zone(s). You cannot update theBackup-Archive Client in the global zone because itwill update the version of GSKit that is shared with thesparse-root non-global zones that are not part of theautomatic deployment.


User response: Manually upgrade the Backup-ArchiveClient or install it from the global zone without usingthe -G parameter. This ensures that you have the sameversion between the global zone and the sparse-rootnon-global zones, and you can then deploy the clientautomatically on all such zones.

ANE4283E There is not enough disk space on pathto uncompress GSKit packages.Required space: req_space bytes;available space: avail_space bytes.

Explanation: The deployment manager determinedthat there is not enough free disk space to uncompressGSKit packages.


User response: Free up the required amount of diskspace and reschedule the automatic client deployment.

ANE4284E The deployment is cancelled because anautomatic client deployment task wasscheduled for a sparse-root, non-globalzone that shares the /usr file systemwith the global zone.

Explanation: The automatic client deployment taskthat was attempted is not supported and will becancelled.




User response: Install the Backup-Archive Client fromthe global zone or manually upgrade theBackup-Archive Client.

ANE4285E The update restore operation to anexisting virtual machine 'VmName'failed. The virtual machine is not inpower off state.

Explanation: The update restore operation to anexisting virtual machine is not supported for a runningmachine and will be aborted.

System action: Restore aborted.

User response: Turn off the virtual machine andre-run the update restore command.

ANE4290E Only one virtual machine can beselected for restore.

Explanation: Restoring multiple virtual machines isnot allowed. Only one virtual machine can be selectedfor restore.

System action: No processing occurs.

User response: Select only one virtual machine forrestore.

ANE4291E Virtual Machine could not be found onVMware server.




ANE4292E No virtual machine found.

Explanation: No virtual machine found with name orspecified in domain option.


User response: Specify a correct VM name or domainoption.

ANE4293E Backup of VMware vApp 'vApp name' inOrganization VDC 'Org VDC name' oforganization 'Org name' failed.

Explanation: The vApp backup operation failed. Thiserror message is a summary message and does notcontain detailed information.

System action: The configuration information andVMs for the specified vApps are not backed up.Processing continues to the next vApp.

User response: Check the previous messages in thedsmerror.log file for more details about this vApp .

ANE4295W The virtual machine 'vmname' wasbacked up using the Windows VSSsystem provider. You must manuallyrevert or delete the shadow copy on therestored volumes or you may experiencedegraded performance and anout-of-space condition.

Explanation: At backup time, application protectionwas not able to back up the VM within the 10-secondVSS limit. Therefore, the Windows VSS system providerwas used. If you are restoring the application, thevolume will be automatically reverted. However, if youare restoring the entire VM, you must manually revertor delete the shadow copy.

System action: The virtual machine is restored,including the system provider shadow copy.

User response: Verify that the restore was successful,and the data is not corrupt. If the data is not corrupt,you can delete the shadow copy. However, if the datais corrupt, revert the shadow copy to restore dataintegrity. You can figure out which shadow copy todelete or revert by looking for thedsmShadowCopyID.txt file in the root directory of eachrestored volume. Then, use the diskshadow delete orrevert command.

ANE4296I architecture, schedule-name, domain-name:The Deployment Manager process wasstarted successfully. DeploymentManager Version Information: version

Explanation: The Deployment Manager process wasstarted as a post schedule command. This is the firstmessage from the Deployment Manager. Thearchitecture of the client, schedule name, and domainname are identified at the beginning of the messagetext.

System action: Deployment Manager continues toprocess.

User response: None

ANE4297W architecture, schedule-name, domain-name:Client deployment was completed withwarnings:

Explanation: This is a generic warning message. It ispossible the other messages provide details of thedeployment. The architecture of the client, schedulename, and domain name are identified at the beginningof the message text.

System action: The Deployment Manager processcompletes.

User response: Check the warning messages from theserver administration center, the server activity log, or



error log on the client computer for more information.

ANE4298E architecture, schedule, new_device_type: Theclient deployment was cancelled. Theprevious event causing the cancellationis:

Explanation: This is a generic message that the clientdeployment was cancelled. The Deployment Managerdoes not uninstall or update the current client. It ispossible the other messages provide details of thedeployment. The architecture of the client, schedulename, and domain name are identified at the beginningof the message text.


User response: Check the warning messages from theserver administration center, the server activity log, orerror log on the client computer for more information.

ANE4299E architecture, schedule-name, domain-name:The client deployment failed. Theprevious event causing the failure is:event

Explanation: This is a generic message that the clientdeployment failed. It is possible that other messagesprovide details of the failure. The architecture of theclient, schedule name, and domain name are identifiedat the beginning of the message text.


User response: Check the warning messages from theserver administration center, the server activity log, orerror log on the client computer for more information.

ANE4300I architecture, schedule-name, domain-name:Client deployment was completedsuccessfully.

Explanation: The Deployment Manager processcompletes.


User response: None

ANE4301I IBM Spectrum Protect detectedMicrosoft Active Directory DomainController on virtual machine 'VM'.

Explanation: The virtual machine contains MicrosoftActive Directory Domain Controller.

System action: IBM Spectrum Protect saved additionalinformation about this virtual machine.

User response: None

ANE4302W IBM Spectrum Protect failed to detect ifMicrosoft Active Directory DomainController on virtual machine 'VM'.

Explanation: There was an error while checking if thevirtual machine contains Microsoft Active DirectoryDomain Controller.

System action: IBM Spectrum Protect continuesbacking up this virtual machine.

User response: Check IBM Spectrum Protect error logfor additional information.

ANE4303E The vCloud Director vApp 'vapp-name'has not been previously backed up.

Explanation: The specified vCloud Director vApp hasnot been previously backed up, so can not be specifiedfor restore.

System action: The specified vCloud Director vApp isskipped, and the next vApp in the restore list isprocessed.

User response: Verify the vCloud Director vApp nameto be restored, and re-try the operation.

ANE4304I IBM Spectrum Protect could not detectthe IBM Spectrum Protect for VirtualEnvironments license. Active DirectoryDomain Controller will not be protectedon VM 'VM'.

Explanation: The virtual machine contains MicrosoftActive Directory Domain Controller, but a IBMSpectrum Protect for Virtual Environments license isnot detected. The Domain Controller will not beprotected.

System action: Install IBM Spectrum Protect forVirtual Environments 7.1 or later to protect ActiveDirectory.

User response: None

ANE4305W Backup of VMware vApp 'vApp name' inOrganization VDC 'Org VDC name' oforganization 'Org name' completed. SomeVMs were not backed up.mode: 'Incremental Forever - full_or_incr'target node name: 'target_node_name'data mover node name:'data_mover_node_name'VMs backup status: number of VM backedup out of number of VMs in vApp VMsbacked up successfully.

Explanation: The vApp backup operation completedsuccessfully. However, one or more VMs for thespecified vApp were not backed up. These VMs willnot be created during the restore operation.

System action: Processing continues to the next vApp.



User response: Check the dsmerror.log file for thisvApp for more information about this message. Resolvethe problem, then try the operation again.

ANE4308E Full VM backup of 'hypervisor' VirtualMachine 'vmname' failed with RC=rcmode=full_or_incr, target nodename='target_node_name', data movernode name='data_mover_node_name'




ANE4311E Full VM restore of 'hypervisor' VirtualMachine 'vmname' failed with RC=rctarget node name='target_node_name',data mover nodename='data_mover_node_name'

Explanation: The Full VM restore of the virtualmachine failed.

System action: The full restore of the the virtualmachine finished with failures. The next virtualmachine in the vmlist will be processed. The reason forthe failure is written to the local client error log.


ANE4441E 'fs' is a 'fstype' file system, which is not asupported file system type for filebackup, image backup or archive.

Explanation: The specified file system is notsupported for any type of backup. IBM SpectrumProtect does not support backup and archive or imagebackup for this type of volume.

System action: The file system is skipped. Processingcontinues with the next file system.

User response: Refer to the IBM Spectrum Protectclient manual for a complete list of supported filesystems.

ANE4442E 'VM-Name' a backup cannot be createdbecause the virtual machine hasassigned disk with duplicate diskidentifiers.

Explanation: The client detected that the virtualmachine has assigned disk with duplicate diskidentifiers. The disk may have been copied. A backup

cannot be created on a virtual machine that haveduplicate disk identifiers.

System action: The virtual machine is not backuped.Processing continues with the next virtual machine.

User response: Check that the virtual disks hasdiffrent disk identifiers and update the virtual machineconfiguration to match any changes to the file system.If the problem persists, contact an administrator of theHyper-V server.

ANE4443E 'fs' is a CSVFS file system, which is nota supported file system type for filebackup, image backup or archive.

Explanation: Microsoft Cluster Shared Volumes FileSystems (CSVFS) are NTFS or ReFS volumes that areadded to Cluster Shared Volumes. These volumes areintended for Hyper-V and expanded support for SQL,not for regular file data. IBM Spectrum Protect does notsupport file level backup and archive or image backupfor CSVFS volumes.

System action: The file system is skipped. Processingcontinues with the next file system.

User response: Refer to the IBM Spectrum Protectclient manual for a complete list of supported filesystems.

ANE4446E A file restore mount operation forhypervisor type Virtual Machine 'vmname'failed. The data center node name is'data center node name', the mount proxynode name is 'mount proxy node name'.

Explanation: The file restore mount operation of thevirtual machine failed.

System action: The mount of the virtual machinefinished with failures.

User response: Review the local client error log forthe reason for the failure.

ANE4449E A cleanup of the file restore mount ofhypervisor type Virtual Machine 'vmname'failed. The data center node name is'data center node name', the mount proxynode name is 'mount proxy node name'.

Explanation: The cleanup of file restore mountoperation of the virtual machine failed.

System action: The cleanup of mount of the virtualmachine finished with failures.

User response: Review the local client error log forthe reason for the failure.



ANE4450E The mount proxy platform is notsupported for file restore mountoperations.

Explanation: The file restore mount operation failed.The mount proxy platform is unsupported or the IBMSpectrum Protect Recovery Agent is not correctlyinstalled and configured.

System action: The file restore mount operation failed.

User response: Ensure that the IBM Spectrum ProtectRecovery Agent is installed and configured correctlyand run the file restore mount operation from asupported mount proxy platform.

ANE4451E The Windows iSCSI service is notavailable.

Explanation: The Windows iSCSI service is notavailable on the mount proxy machine. It is either notstarted or is not installed or configured correctly.

System action: Processing stops. The file restoremount operation fails.

User response: Ensure that the iSCSI service is up andrunning on the mount proxy machine.

ANE4900W Schedule 'schedule-name' has opened anew session with the server.

Explanation: A scheduled event endsbecause of aconnection failure. The scheduled event had to berestarted outside its normal startup window tocontinue the operation.

System action: The scheduled event is completedusing more than one session.

User response: None required. If this is a recurrentcondition, you may want to check for networkproblems.

ANE4901E The following object contains one ormore unmatched quotation marks andcannot be processed: 'filespace pathfilename'.

Explanation: The file name in the file list containsunmatched quotes. If a line in the file list begins with asingle or double quotation mark this quotation mark isconsidered to be an opening quotation mark. Thecorresponding closing quotation mark of the same typemust be at the end of the line. If there is no closingquotation mark or the closing quotation mark has beenencountered in the middle of the line, it is an invalidinput.

System action: The object is skipped.

User response: Correct the specification of the object.

ANE4904E Instant access of VMware VirtualMachine 'vmname' failed. target nodename='target_node_name', data movernode name='data_mover_node_name'

Explanation: The instant access of the virtual machinefailed.

System action: The instant access of the the virtualmachine finished with failures. The reason for thefailure is written to the local client error log.


ANE4907E Instant restore of VMware VirtualMachine 'vmname' failed. target nodename='target_node_name', data movernode name='data_mover_node_name'

Explanation: The instant restore of the virtual machinefailed.

System action: The instant restore of the the virtualmachine finished with failures. The reason for thefailure is written to the local client error log.


ANE4910E Cleanup of VMware Virtual Machine'vmname' failed. target nodename='target_node_name', data movernode name='data_mover_node_name'

Explanation: The cleanup of the virtual machinefailed.

System action: The cleanup of the the virtual machinefinished with failures. The reason for the failure iswritten to the local client error log.


ANE4915I Object increased in size duringcompression: filespace pathfilename

Explanation: The file increased in size duringcompression.

System action: Processing contiues.


ANE4917E A failure occurred while accessing theVMware libraries. The required files forthe virtual machine backup were notfound.The files are installed only if the clientis defined as a data mover in IBMSpectrum Protect for VirtualEnvironments.



Explanation: A failure occurred while accessing theVMware libraries for the virtual machine environment.

System action: The backup operation cannot continue.

User response: Install the IBM Spectrum Protect forVirtual Environments package to use the client to backup virtual machines.

ANE4936E The snapshot of virtual machine'vmname' failed and a snapshot cannotbe attempted again.

Explanation: The snapshot of the virtual machinefailed with a permanent error. Such as the Hyper-Vwriter is not responding. Another snapshot attempt willnot be made.

System action: The snapshot of the virtual machinefinished with an error. Processing continues to the nextvirtual machine.

User response: Check the Windows event log for thereason for the failure.

ANE4937I Resending file file in a new transactionsession to recover from the transmissionerror.

Explanation: None.

System action: The file is resent.


ANE4938I Virtual machine: 'vm-name' disk:'disk-name' is excluded by size.

Explanation: The option file or command givenexcluded the disk from backup processing.

System action: The disk is not processed.

User response: If the disk is intentionally excluded,then this message is expected behavior. Otherwisemodify the command or option file to include the disk.

ANE4942E The file specification 'string' is invalid.

Explanation: The operating system indicated that thefile specification is invalid. One possible reason is thatthe file specification contains unrecognized characters.Another possible cause is incorrect use of quotationmarks in the file specification.


User response: Enter a correct file specification asdescribed in the Using the Backup-Archive Client bookfor the particular operating system. Ensure that the filespecification contains valid characters. Verify correctuse of quotation marks for specifications that containblanks spaces. If multiple file specifications are used,make sure that any use of quotation marks does not

cause the file specifications to be treated as a single filespecification.

ANE4944I Virtual machine: 'vm-name' disk:'disk-name' is excluded by user.

Explanation: The option file or command givenexcluded the disk from backup processing.

System action: The disk is not processed.

User response: If the disk is intentionally excluded,then this message is expected behavior. Otherwisemodify the command or option file to include the disk.

ANE4946W Warning: virtual machine: 'vm-name'disk: 'disk-name' excluded by user, wasnot found.

Explanation: The specified virtual disk does not existon the virtual machine.


User response: Use the "dsmc backup vm ..."command with the -preview option to display a listingof the disk labels which exist on the virtual machine.Since the disk was specified to be excluded from thebackup, the backup will continue. However it ispossible that a disk will included in the backup whichwas not desired, check the spelling of the disk label,and correct the disk label if an undesired disk is nowincluded in the backup operation.

ANE4947E Error: virtual machine: 'vm-name' disk:'disk-name' included by user, was notfound.

Explanation: The specified virtual disk does not existon the virtual machine.


User response: Use the "dsmc backup vm ..."command with the -preview option to display a listingof the disk labels which exist on the virtual machine.Check the spelling of the disk label and correct the disklabel and then retry the 'backup vm' operation.

ANE4948E A specified virtual disk was not foundon the virtual machine.

Explanation: You must specify a virtual disk labelname which exists on the virtual machine.


User response: For a backup operation, use the "dsmcbackup vm ..." command with the -preview option todisplay a listing of the disk labels which exist on thevirtual machine. For a restore operation, use the "dsmcquery vm ..." command with the -detail option todisplay a listing of the disk labels which exist on thevirtual machine backup. Check the spelling of the disk



label and correct the disk label and then retry theoperation.

ANE4972W File server file-server-name has beenupgraded to Data ONTAP version'version.modifcation.submodification'. Thisversion does not support unicode filenames for snapshot differenceincremental backup. Upgrade to aversion that supports unicode file namesas soon as possible.

Explanation: The file server has been upgraded from aversion that supports unicode file names forincremental backup using snapshot difference to aversion that does not. If you have upgraded from DataONTAP version 7.3.3 (or later) to 8.0, you lose theability to back up files with unicode file names whenperforming snapshot difference incremental backup.

System action: Processing continues. However, fileswith unicode names are not backed up.

User response: Upgrade to a version that supportsunicode file names as soon as possible. If you haveupgraded from Data ONTAP version 7.3.3 (or later) to8.0, upgrade to 8.1 (or later). If it is not possible toupgrade at this time, you can suppress this warningmessage by renaming the file space on the IBMSpectrum Protect server and performing a snapshotdifference incremental backup.

ANE4973E An error occurred accessing NTFSsecurity information for file 'filespacenamepath-namefile-name'

Explanation: An access denied error occurred whileattempting to access NTFS security info rmation.


User response: See your system administrator orbypass the failing check by using SkipNTSecu rityoption.

ANE4974E Error processing 'filespacenamepath-namefile-name': a required NTprivilege is not held.

Explanation: The user account running IBM SpectrumProtect does not possess a required NT user right/privilege for performing the current operation.


User response: Your system administrator has theauthority to grant the needed privilege.

ANE4987E Error processing 'filespacenamepath-namefile-name': the object is inuse by another process

Explanation: The specified file is being used by

another process. You tried to read from or write to afile that is currently being used by another process.


User response: Ensure that the file is not locked byanother process. If the file is not locked, retry thecommand.

ANE4988W File 'filespace namepath-namefile-name' iscurrently unavailable on server and hasbeen skipped.

Explanation: You tried to restore or retrieve a file thatis currently not available from the IBM SpectrumProtect server. This is most likely a temporarycondition.

System action: IBM Spectrum Protect cannot restoreor retrieve the file.

User response: Try to restore or retrieve the file againafter the file becomes available on the server. If theproblem persists, see your IBM Spectrum Protectadministrator for assistance.

ANE4989E Error processing 'filespacenamepath-namefile-name': the directory isin use by another process. All objects inthe directory and any of itssubdirectories are skipped.

Explanation: The specified directory is being used byanother process. You tried to read from or write to adirectory that is currently being used by anotherprocess. The objects contained in the directory and itssubdirectories are not backed up.

System action: Processing stopped for that directory.If other files and directories were also specified in thisbackup, they are processed

User response: Ensure that you specified the correctdirectory name, correct the permissions, or specify anew location.If the directory name is correct, retry thebackup when no process has exclusive use of thedirectory.

ANE4991I Application Type Application Message IdApplication Message

Explanation: This is a message sent by the applicationyou are currently running with IBM Spectrum Protect.

System action: IBM Spectrum Protect logs theapplication message.

User response: Refer to the documentation for theapplication that you are using.

ANE4972W • ANE4991I


ANE4992W Application Type Application Message IdApplication Message




ANE4993E Application Type Application Message IdApplication Message




ANE4994S Application Type Application Message IdApplication Message




ANE4997E Error processing 'filespacenamepath-namefile-name': file system quotareached condition - no space left.

Explanation: No more files can be restored orretrieved because the quota of the destination filesystem has been reached.


v Retry this object

v Skip this object

v Abort the action

User response: Select the appropriate action for thisobject. Create some free space or increase the quota onthe destination file system before you retry theoperation. Another option is to restore or retrieve thefile to another file system.

ANE4998E Link information for file 'filename' couldnot be obtained: access to the object isdenied.

Explanation: Access to the specified file link is denied.You tried to read information for file link and you donot have access permission for this object.

System action: Processing of System State stops.

User response: Try the operation again. If the problempersists, contact IBM technical support for additionalassistance.

ANE4999I The following message was too long tolog to the server: 'shortened message withmessage number'

Explanation: The message text and inserts are toolarge to send to the server in the available internalbuffer.

System action: The message number message is writtento the local client error log, then shortened and sent tothe server as a part of this message. The message isreduced in length by substituting '...' in the middle ofthe original message.

User response: The message referred to has beenshortened, but describes the error that occurred. See thedocumentation for that message for more information.

ANE4992W • ANE4999I


Chapter 3. ANR messages

ANR messages are issued by the server. Some ANR messages are common to alloperating systems, and some are specific to a single operating system.

ANR messages listMessages are listed in ascending numerical order. All elements of the message aredocumented.

For a list of new, changed, and deleted server messages, see the following files inthe server installation directory:

Release_msg_chgsThis file contains all new, changed, and deleted messages from theprevious server version to the current version.

Maint_msg_chgsThis file contains all new, changed, and deleted messages from the currentserver version to the current release.

These files are in the installation_directory\doc directory for Microsoft Windowsoperating systems and the installation_directory/server/bin/ directory for allother operating systems.

These files are also available in New, changed, and deleted server messages on theIBM Spectrum Protect wiki.

ANR0010W Unable to open message catalog forlanguage language. The default languagemessage catalog will be used.

Explanation: The message catalog for the specifiedlanguage could not be found.

System action: The server continues to initialize withthe default English message catalog.

User response: To resolve the issue, complete thefollowing steps:

v If you specified a LANGUAGE option in the serveroptions file, verify that you specified a supportedlanguage.

v If you specified environment variables for thesystem locale, ensure that you specified a supportedlocale and that the locale is installed on your system.

v Ensure that the IBM Spectrum Protect languagepackage for the specified language is installed onyour system.

v Restart the server.

ANR0011W Unable to set locale to first locale. Usinglocale second locale for messageformatting.

Explanation: The first locale could not be set.

System action: The server continues to initialize usingthe second locale.


v If you specified a LANGUAGE option in the serveroptions file, ensure that you specified a supportedlocale and that the locale is installed on your system.

v If you specified environment variables for thesystem locale, ensure that you specified a supportedlocale and that the locale is installed on your system.

v Restart the server.

ANR0098W This system does not meet theminimum memory requirements.

Explanation: The minimum memory required is 12GB. 16 GB is required if you are using datadeduplication. At least 32 GB is needed for heavilyused servers. Using 32 GB or more of memoryenhances performance of the IBM Spectrum Protectserver database inventory.

If you plan to run multiple instances, each instancerequires the memory listed for one server. Multiply thememory for one server by the number of instancesplanned for the system.


https://www.ibm.com/developerworks/community/wikis/home#!/wiki/Tivoli%20Storage%20Manager/page/New%2C%20changed%2C%20and%20deleted%20server%20messages

Node replication processing requires additionalmemory. Use a minimum of 32 GB of memory for nodereplication without data deduplication. Nodereplication with data deduplication requires aminimum of 64 GB of memory. You will require anactive log at least 64 GB in size to run replication. Ifreplication and deduplication are both being used, anactive log at least 128 GB in size is required.

System action: Server operation continues.

User response: Increase the amount of memory on thesystem.

ANR0099W This operating system is not supported.

Explanation: The system has detected one of thefollowing items:

v a release of the operating system that is notsupported

v the required maintenance for the operating system isnot installed

See the software requirements section in theinformation center for more details.


User response: See the software requirements sectionin the information center and upgrade to a supportedoperating system.

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 occurred when a serverdatabase table was being accessed. This error messagealways accompanies another error message whichprovides more details about the error.


User response: If the server or storage agent stops inresponse to a HALT command, you can ignore thiserror message.

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

Explanation: An internal error occurred when datawas added to a server database table. This errormessage always accompanies another error messagewhich provides more details about the error.


User response: An error occurred when a row wasinserted into a server database table. Typically, thiserror causes an error code value of 1202 to bedisplayed. An error code value of 1202 indicates thatthe record being inserted already exists in the database.This type of error might be caused by a timing issuewith the server or a synchronization issue involvingserver processes, client sessions, or other server actions.Review the activity log file to determine whatoperations were in progress and were affected by thiserror. Try the operation again and change the timing sothat it does not run with the same processes or actionsas when the error occurred.

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

Explanation: An internal error occurred when datawas updated in a server database table. This errormessage always accompanies another error messagewhich provides more details about the error.


User response: An error occurred when a row wasinserted into a server database table. Typically, thiserror causes an error code value of 1114 to bedisplayed. An error code value of 1114 indicates thatthe record being updated does not exist in thedatabase. This type of error might be caused by atiming issue with the server or a synchronization issueinvolving server processes, client sessions, or otherserver actions. Review the activity log file to determinewhat operations were in progress and were affected bythis error. Try the operation again and change thetiming so that it does not run with the same processesor actions as when the error occurred.

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

Explanation: An internal error occurred when datawas being removed from a server database table. Thiserror message always accompanies another errormessage which provides more details about the error.


User response: An error occurred when a row wasdeleted from a server database table. Typically, thiserror causes an error code value of 1114 to be

ANR0099W • ANR0104E


displayed. An error code value of 1114 indicates thatthe record being deleted does not exist in the database.This type of error might be caused by a timing issuewith the server or a synchronization issue involvingserver processes, client sessions, or other server actions.Review the activity log file to determine whatoperations were in progress and were affected by thiserror. Try the operation again and change the timing sothat it does not run with the same processes or actionsas when the error occurred.

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

Explanation: An internal error occurred when datawas being accessed from a server database table. Thiserror message always accompanies another errormessage which provides more details about the error.


User response: Review the activity log file todetermine what operations were in progress and wereaffected by this error. Try the operation again andchange the timing so that it does not run with the sameprocesses or actions as when the error occurred.

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

Explanation: An internal error occurred when datawas being accessed from a server database table. Thiserror message always accompanies another errormessage which provides more details about the error.


User response: Review the activity log to determinewhat operations were in progress and were affected bythis error. Try the operation again and change thetiming so that it does not run with the same processesor actions as when the error occurred.

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

Explanation: An internal error was detected duringtransaction commit. This message is typically precededby another error message which provides more detailsabout the error.


User response: Review the activity log to determinewhat operations were in progress and were affected bythis error. Try the operation again and change thetiming so that it does not run with the same processesor actions as when the error occurred.

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: See the documentation for theoperating system about how to increase memory for anapplication.

ANR0109E Attempt number att_num Unable to loadcryptography module from 'icc location'.

Explanation: An error occurred while attempting toload the cryptography module.

System action: The application will not start.

User response: Verify that the ICC cryptographydirectory is located in either the application rootdirectory or the directory specified in the platformspecific environment variable (the DSMSERV_DIR forUnix platforms or the Windows registry).

ANR0110E An unexpected system date has beendetected; the server is disabled. Verifythe system date and use the ACCEPTDATE command to establish the currentdate 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 disabled for client, serverand administrative access. Most server processes willnot 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 ALL command to enable the server forsessions. Accepting an invalid date can cause any of thefollowing problems:Premature deletion of dataExcessive retention of dataScheduling problemsEvent record problemsPassword expiration problems.

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.

ANR0105E • ANR0111E

Chapter 3. ANR messages 37

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.


User response: Reissue the command, specifying theENDNODEID to be greater than the BEGINNODEID,or both to be equal.

ANR0113E Command: The storage pool list specifiedwith the parameter parameter nameincludes storage pool storage pool namemore than once.

Explanation: The storage pool name specified hasbeen specified more than once. The name occurs morethan once in the COPYSTGPOOLS list, more than oncein the ACTIVEDATAPOOLS list, more than once in thePROTECTLOCALSTGPOOLS list, or it has beenspecified in multiple lists.

System action: The command fails.

User response: Reissue the command specifyingunique storage pool names.

ANR0114E Command: The NUMBER parameter isrequired on this command. The currentdefault value is 0.

Explanation: The NUMBER parameter is required forthe FORMAT LFVOLUME COMMAND when theLFVOLUMEFORMATCOUNT option is set to 0.

System action: The command is not executed.

User response: Either reissue the command with theNUMBER parameter or else use the the SETOPTcommand to change the LFVOLUMEFORMATCOUNTvalue.

ANR0115W The server script script name attemptedto start more parallel commands thanare allowed for a single script. A singlescript is limited to parallel command limitparallel commands.

Explanation: The server waits for all previous parallelcommands started by the script to complete. When allprevious parallel commands are complete, the serverallows the script to continue. The script can attempt tostart more parallel commands.

System action: The server waits for all previous

parallel commands before allowing the script tocontinue.

User response: If you need to start more parallelcommands than the script limit allows, modify thescript to invoke multiple scripts in parallel, each ofwhich can start multiple parallel commands, up to thescript limit.

ANR0116W The server script script name attemptedto start more parallel commands thanare allowed for the server. The server islimited to parallel command limit parallelcommands.

Explanation: The server waits for all previous parallelcommands started by the script to complete. When allprevious parallel commands are complete, the serverallows the script to continue. The script can attempt tostart more parallel commands. If the limit is exceeded,the command will run serially.

System action: The server waits for all previousparallel commands before allowing the script tocontinue.

User response: Reduce the number of parallelcommands or scripts that are running on the server atany one time.

ANR0117E The server contains stored data. Archivedata retention protection cannot bechanged.

Explanation: The archive data retention protectionstate cannot be changed while the server contains anybackup, archive, or space-managed data.


User response: In order to change the archive dataretention protection state, the server must contain nobackup, archive, or space-managed data. Eitherre-initialize the server database, or delete all storeddata and try the command again.

ANR0118W The client option client option is notvalid and will not be sent to the client.Use the INCLEXCL option instead.

Explanation: The client options INCLUDE andEXCLUDE are not valid and have been replaced by thecombined INCLEXCL. If INCLUDE and EXCLUDE areused in client option sets, use the INCLEXCL optionalong with the specific include or exclude option thatyou want the clients to use.

System action: The option is ignored and is not sentto the client. The server continues processing.

User response: Client options INCLUDE andEXCLUDE are not valid; use the INCLEXCL optionalong with the specific include or exclude option thatyou want the clients to use.

ANR0112E • ANR0118W


ANR0119W The client option client option is notvalid and will not be sent to the client.Delete it from client option sets.

Explanation: The client option is not supported bythis server and should be deleted from the client optionset.

System action: The option is ignored and is not sentto the client. The server continues processing.

User response: Delete the option from the option set.Check the documentation for a possible replacement forthe option.

ANR0120I Archive data retention protection is setto state of archive data retention protection.

Explanation: The archive data retention protectionstate has been set.



ANR0121E command is not allowed when archivedata retention is enabled.

Explanation: The specified command is not allowedwhen archive data retention protection is enabled onthe server.



ANR0122E command: A node cannot be assigned toa new domain when archive dataretention is enabled.

Explanation: A previously defined node cannot beassigned to a new domain when archive data retentionprotection is enabled on the server.



ANR0123E command: A device type of SERVER isnot allowed when archive data retentionis enabled.

Explanation: The specified device type is not allowedwhen archive data retention protection is enabled onthe server.



ANR0124W Object object name (object id hi ) for nodenode name (node id), filespace filespacename (filespace id) is retention protectedand can not be deleted.

Explanation: The specified object can not be deletedbecause:

v Archive retention protection is enabled and theobject's retention period has not elapsed, or

v The object is part of a deletion hold.



ANR0125W DELETE FILESPACE filespace name fornode node name contains retentionprotected data and cannot be deleted.

Explanation: The specified file space cannot be deletedbecause it contains one or more objects that must beretained for one of the following reasons:

v Archive retention protection is enabled and theobject's retention period has not elapsed.


System action: The file space is not deleted.


ANR0126W DELETE VOLUME: Volume volume namecontains retention protected data andcan not be deleted.

Explanation: The specified volume cannot be deletedbecause it contains one or more objects that must beretained because of one of the following:

v Archive retention protection is enabled and theobject's retention period has not elapsed.




ANR0127E command to another server is notallowed when data retention protectionis enabled on the target server.

Explanation: The specified command is not allowedwhen data retention protection is enabled on the targetserver.



ANR0128E Command: The list of storage poolsspecified with the parameter parametername includes storage pool storage poolname, which is already in use by anotherstorage pool.



Explanation: The specified storage pool name isalready being used to protect another storage pool. Youcannot protect multiple storage pools using the samecontainer-copy storage pool.


User response: Reissue the command specifyingunique storage pool names.

ANR0129I Database upgrade completedsuccessfully.

Explanation: The requested database upgradeoperation completed successfully.



ANR0130E Diagnostic(ID): 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, evaluate the directories andfilesystem assigned to the ACTIVELOGDIR,ARCHIVELOGDIR, and ARCHFAILOVERLOGDIR. Anout of log space condition may occur because theACTIVELOGDIR location is full. Alternatively, an outof log condition may occur if the log files in theACTIVELOGDIR which are no longer active can not bearchived to the ARCHIVELOGDIR andARCHFAILOVERLOGDIR locations. If necessary, alarger ARCHIVELOGDIR or ARCHFAILOVERLOGDIRcan be specified by updating this option in thedsmserv.opt file and then restarting the server.

ANR0131E Diagnostic(ID): Server DB spaceexhausted.

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 DBSPACE command. Once additional spacehas been added for the database, the server databasemanager will automatically extend into that space anduse it.

ANR0132E Diagnostic(ID): 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.

ANR0134I Cloud tiering process process ID forstorage rule stgrule_name started fromstorage pool source_stgpool totgt_stgpool_type storage pooltarget_stgpool.

Explanation: The server has started cloud tierprocessing to move older client backup, archive andspace managed file copies. The cloud tiering processwas started as process number process ID. To query theprocess, use the QUERY PROCESS command. To cancelthe process, use the CANCEL PROCESS command.

System action: Server operation continues. The cloudtiering process can be canceled, if necessary.


ANR0135I Cloud tiering process process ID fromstorage pool source_stgpool startedsearching for eligible file spaces.

Explanation: The cloud tiering process began a searchfor file spaces with eligible data that must be moved tothe target storage pool.



ANR0136I Table updating statistics performedsuccessfully for processed tables of totaltables.

Explanation: The server periodically performsmaintenance on the database tables. The maintenanceprocessing allows the database to update statisticsdetermine how to best access a given table. The

ANR0129I • ANR0136I


maintenance processing will periodically process alltables for the server.


User response: No user action required.

ANR0137E Source file(line number): Error error codeallocating num rows database rows.

Explanation: An internal error has occurred in anattempt to allocate storage for the requested number ofdatabase rows indicated.



ANR0138E Value primary logs for number ofprimary logs is invalid.

Explanation: The command has been issued with aninvalid number of primary logs.

System action: Server installation stops.

User response: Reissue the command with a validnumber of primary logs.

ANR0139I Cloud tiering process process IDidentified number of files files for nodenode name, file space filespace name to tierfrom storage pool source_stgpool tostorage pool target_stgpool.

Explanation: The cloud tiering process identified olderfiles that must be moved to the target storage pool.

System action: Server operation continues as files aremoved.


ANR0140I Command: success. Node node_id_1 isgranted proxy authority to nodenode_id_2.

Explanation: The command was successful.

System action: The server performs the command.


ANR0141E Command: failed. Node node_id_1 was notgranted proxynode authority to nodenode_id_2.

Explanation: The command fails if either of the nodesdo not exist, or if the administrator issuing thecommand does not have sufficient authority.


User response: Verify that both nodes exist and that

the administrator has sufficient authority, then issue thecommand again.

ANR0142I Command: success. Proxynode authorityfor node node_id_1 has been revokedfrom node node_id_2.

Explanation: The command was successful.

System action: The server performs the command.


ANR0143E Command: failed. Proxynode authorityfor node node_id_1 has not been revokedto node node_id_2.

Explanation: The command fails if the administratorissuing the command does not have sufficient authority.


User response: Check the help for the command andverify that the administrator has either system orunrestricted policy authority; then issue the commandagain.

ANR0144E Command: failed. Node node_id_1 was notgranted proxynode authority to nodenode_id_2 because node node_id_missinghas not been defined to the server.

Explanation: The command failed because one of thenodes has not been defined to the server.


User response: Verify that both nodes have beendefined to the server and then issue the commandagain.

ANR0145E Command: failed. Node node_id_1 alreadyhas been granted proxynode authority tonode node_id_2.

Explanation: The command failed because a proxyrelationship between the two nodes already exists.

System action: The server fails the command, butdoes not change the existing association.


ANR0146E Command: failed. Node node_id_1 was notgranted proxynode authority to itself.

Explanation: The command failed because a nodecannot have a proxy relationship defined to itself.





ANR0147E Command: failed. Proxy node authorityfor node node_id_1 to node node_id_2 wasnot revoked because nodenode_id_missing has not been defined tothe server.

Explanation: The command failed because one of thenodes has not been defined to the server.


User response: Verify that both nodes have beendefined to the server, and then issue the commandagain.

ANR0148I Command: No proxy relationships werefound.

Explanation: No proxy relationships were found.

System action: None.


ANR0149E Filespace filespace for node node_namewas deleted concurrently with thecommand.

Explanation: The command failed. The requestedfilespace was deleted concurrently with the command.

System action: The server will fail the command.

User response: Retry the command.

ANR0150E Failed to open object object_name. Therewas an error decrypting thepassword_type password.

Explanation: The server could not open the objectspecified due to the error encountered while decryptingthe password.

System action: The server will fail the relatedcommand or action.

User response: Reset the password using theappropriate UPDATE command and retry the failingcommand or action.

ANR0151W Database manager fails to start. Formore information about the failure,issue the db2start command.

Explanation: The server was unable to start thedatabase manager. The following are possible causes:

v The database manager license key is invalid ormissing.

v The server instance password was changed.

System action: Server initialization stops.

User response: For more information about the failure,try to start the database manager by issuing thedb2start command, as in this example:

C:\Users\admin>db2start. You might receive messagessimilar to the following ones: SQL1397N The DB2service failed to logon. SQL1032N No start databasemanager command was issued. SQLSTATE=57019. Todetermine the cause of the failure, evaluate recentchanges to the server and review the system error logs.Information can be found in the DB2 diagnostic log file.If you are starting a DB2 server on a Windowsplatform, you can set the logon account for a DB2service by using the Services dialog box from theControl Panel.

ANR0152I Database manager successfully started.

Explanation: The server was successfully able to startthe database manager.

System action: The server operations continue.


ANR0153I Database manager already running.

Explanation: The server database manager is alreadyrunning.

System action: The server continues startup.


ANR0154E Command: The active data pool list thatyou specified with theACTIVEDESTINATION parameterincludes active data pool active data poolname that is a duplicate. All names mustbe unique.

Explanation: You may enter up to 10 unique activedata pool names specified with theACTIVEDESTINATION parameter.


User response: Reissue the command specifyingunique active-data pool names.

ANR0155E Command: The number of active datapool names specified with theACTIVEDESTINATION parametercannot exceed 10.

Explanation: The maximum number of active datapool names that you can specify with theACTIVEDESTINATION parameter is 10. You may enterup to 10 unique names, separated by commas.


User response: Reissue the command specifying up to10 unique active-data pool names separated only bycommas.



ANR0156E Command: The pool active data pool namewith pool ID pool ID is not an activepool.

Explanation: The storage pool specified is not anactive-data pool. Only active-data pools are allowed tobe specified in the ACTIVEDESTINATION parameter.


User response: Reissue the command specifying ten orfewer active-data pool names.

ANR0157W Database operation table operation fortable table name failed with result codeop code and tracking ID: id.

Explanation: An error occurred during the specifiedtable operation for the table indicated.


User response: If there were no operational failures asa result of issue, then this was anticipated and theserver was able to continue appropriately. If thisresulted in a failure for a client session or serverprocess, this information is needed to help diagnose theissue. In the even of a failure, please contact your IBMservice representative for further assistance.

ANR0158W Database operation table operation fortable table name failed with operationcode op code and tracking id trackingnumber. The data for column columnnumber is: column data.

Explanation: An error occurred during the specifiedtable operation for the table indicated.


User response: If there were no operational failures asa result of issue, then this was anticipated and theserver was able to continue appropriately. If thisresulted in a failure for a client session or serverprocess, this information is needed to help diagnose theissue. In the even of a failure, please contact your IBMservice representative for further assistance.

ANR0159E Diagnostic(ID): Database deadlockdetected on DB2 Statement Handle.

Explanation: The database server detected a deadlocksituation and rolled back the outstanding work on thisstatement handle. When server processes encounter adatabase deadlock, they usually reattempt the workthat was in progress when the deadlock wasencountered. Not all processes can explicitly try anoperation again. For example, migration andreclamation will eventually be tried again. However,something such as a delete volume run in a macro willonly be tried again if the delete command is reissued

either in the macro or the command line.

System action: The work being done on the statementhandle is rolled back. Some processes will attempt toretry the request. Others will just stop. Server operationcontinues.

User response: If a process can retry (like migration),then monitor the re-try attempt to see if it succeeds ornot. If the process or command is not able to retry onit's own, then reissue the command or macro thatcaused the action to occur.

ANR0160I Displaying segment segment number oftotal segments for client object objectidentifier with text: object name.

Explanation: Display a client object, such as a file ordirectory, that uses a long fully qualified name. Thename is displayed in smaller segments until the entirename is shown. The segment numbers are incrementedfrom 1 to N until all the segments for this object nameare displayed.

System action: The fully qualified name for this objectis displayed.


ANR0161I Displaying segment segment number formessage insert insert identifier with textsegment text.

Explanation: Display a segment of a message insertthat was too long to be displayed within the specifiedmessage. There may be one or more segmentsdisplayed for a given message insert.

System action: The entire message insert segment isdisplayed.


ANR0162W Supplemental database diagnosticinformation: dbReturnCode:dbState:dbCode(dbErrorMessage).

Explanation: The dbReturnCode, dbState, and dbCode aredisplayed as supplemental information. Thisinformation should be used in conjunction with anyother database error or warning messages issues toassist with diagnosing a given issue.


User response: None. This is supplementalinformation corresponding to another database error orwarning message issued.



ANR0163E Diagnostic(ID): Database insufficientmemory detected on DB2 StatementHandle.

Explanation: The database server detected aninsufficient memory condition and rolled back theoutstanding work on this statement handle.

System action: The work being done on the statementhandle is rolled back. Server operation continues.


ANR0165I Inventory file expiration startedprocessing for node nodename, filespacefilespace name, copygroup copygroup andobject type type.

Explanation: Inventory file expiration processingstarted processing for the node name and filespace nameindicated. For this node name and filespace name theindicated copygroup and object types are currentlybeing evaluated.

System action: Inventory file expiration continues.

User response: This message is for informationalpurposes only and is only displayed if the expirationprocessing is executed with QUIET=NO.

ANR0166I Inventory file expiration finishedprocessing for node nodename, filespacefilespace name, copygroup copygroup andobject type type with processingstatistics: examined examined, deleteddeleted, retrying retrying, failed failed andskipped skipped.

Explanation: Inventory file expiration processingfinished processing for the node name and filespace nameindicated. For this node name and filespace name theindicated copygroup and object types were evaluated.And the ending statistics show the number of objectsexamined, deleted, retried, skipped and those thatfailed to be processed.


User response: This message is for informationalpurposes only and is only displayed if the expirationprocessing is executed with QUIET=NO.

ANR0167I Inventory file expiration process processID processed for minutes minutes.

Explanation: Server expiration processing ran for theindicated number of minutes.



ANR0168I Analyst authority for administratoradmin name will be ignored. Analystauthority is not supported on thisserver.

Explanation: Analyst authority is not supported forservers at V6.1 or later.

System action: The operation continues.


ANR0169E An unexpected error has occurred andthe IBM Spectrum Protect server isstopping.

Explanation: The IBM Spectrum Protect serverencountered an error from which it cannot recover, andthe server is halting. Other messages will be issuedalong with this message indicating the specific errorconditions which have occurred.

System action: The server halts.

User response: Follow the instructions indicated inany associated messages, then start the server.

ANR0170E Diagnostic(ID): Error detected on DB2Statement Handle, database restartrequired.

Explanation: The IBM Spectrum Protect serverencountered an error on the database and needs toissue a DB2 RESTART DB to the database manager. Allconnections to the database server are severed, anduncompleted operations are aborted. The IBMSpectrum Protect server will then restart the databaseand attempt to continue. If the database managercannot be restarted, the IBM Spectrum Protect serverwill halt. Other messages may be issued along with thismessage indicating the specific error conditions whichhave occurred.

System action: The server continues, or if it cannotrestart the database, it halts.

User response: If the server is able to recover, noaction is needed, except to restart operations that wereaborted. However, if the server cannot recover, it willhalt. Follow the instructions indicated in any associatedmessages, then start the server. If the server still cannotbe started, manually issue the DB2 RESTART DBcommand, then attempt to start the IBM SpectrumProtect server again.

ANR0171I Diagnostic(ID): Error detected on DB2Statement Handle, database in evaluationmode.

Explanation: The IBM Spectrum Protect serverencountered an error on the database and will takeaction to determine the type of error and whether ornot it can recover from the error.

ANR0163E • ANR0171I


System action: Server processing continues.

User response: This is an information message. As theIBM Spectrum Protect server attempts to resolve theerror, it might issue other messages. Follow theinstructions indicated in any associated messages.

ANR0172I Diagnostic(ID): Error encounteredperforming action action.

Explanation: The IBM Spectrum Protect serverencountered an error performing the specified databaseaction. This error caused the action to fail andprevented the server from being able to continue.

System action: Server processing terminates, therequested action fails.

User response: Review other messages issued todetermine the actual error and then take steps toremedy that failure before retrying the operation.

ANR0173I The database failed action action becauseof insufficient system memory available.

Explanation: The IBM Spectrum Protect serverencountered an error while performing the specifiedaction. Specifically, the server database did not havesufficient memory to communicate with the serverdatabase or was unable to acquire the memory neededfor the server buffer pools.

System action: Server processing terminates, therequested action fails.

User response: In most cases, this indicates a lack ofavailable resources on the system. This may be a lackof physical resources or it may be an environmentsetting that prevents the server from having access tothe needed resources. For instance, on Linux systems,this may be caused by the SHMMAX value (maximumallowed shared memory) being set too low. On Linux,this can be viewed using the command "ipcs -l".Similarly, for Linux, this value can be increased usingthe command "sysctl -w kernel.shmmax=nnn" wherennn is the new maximum memory value to assign tobe used for shared memory. As a generalrecommendation, this value should be set toapproximately 1.25 GB or higher depending upon theactual physical memory (RAM) available on thatsystem.

ANR0174E Diagnostic(ID): Maximum DB2connections reached on DB2 Handle.

Explanation: There are no more available connectionsto the server database.


User response: To increase the number of databaseconnections available to the server, the DB2

administrator can modify the IDBACK parameter in theDSNzPARM settings.

ANR0175E Diagnostic(ID): Space exhausted for oneor more of the following: DB, LOG, orinstance directory.

Explanation: The space assigned to the serverdatabase, the recovery log, or instance directory hasbeen exhausted.

System action: The server terminates.

User response: Review the filesystems or other spaceassigned to the server for the database, recovery log orinstance directory. If the space assigned to the databaseis full, restart the server and add additional databasespace using the EXTEND DBSPACE command or usethe DSMSERV EXTEND DBSPACE utility. If the serverACTIVELOGDIR is full, update this server option to anew location that has space available for the server touse for logging changes to the database. If the serverinstance directory is full, remove unneeded files or elseextend this filesystem.

Please note that the server should be configured withthe database, activelog, and archivelogs using differentdirectories and storage devices. For example, if thedatabase and activelog are configured to use the samedirectory and underlying storage device, this mayadversely impact performance. This may alsocompromise the server's ability to manage the databaseand active log space effectively. Similarly, the server'sinstance directory should also be monitored andmanaged with some amount of space available. Theserver instance directory is used to record and log someserver and database actions.

ANR0185E The data in primary storage pool name cannot be copied to active data pool name.The active-data pool is not defined to adomain.


User response: Define the active-data pool to adomain using the ACTIVEDESTINATION parameter oneither the DEFINE DOMAIN or UPDATE DOMAINcommand.

ANR0186E There is insufficient authority to startthe database manager.

Explanation: If the server is starting, then the user IDunder which the dsmserv process is running does nothave authority to start the database manager. If theserver is running, it does not have sufficient authorityto perform the server operations.

System action: The server process ends, and theserver stops if it is running.

User response: Ensure that the user ID under whichthe server is running is authorized to start the database

ANR0172I • ANR0186E


manager. Take the following actions:

v Log in to the user ID for your IBM Spectrum Protectinstance and start the server.

– To run the server using the root user ID on aUNIX system, add the root user ID to the primarygroup of the IBM Spectrum Protect instance userID.

– Or, to run the server using the instance user ID ona UNIX system, when using the automatic start,specify the -u option when you start the server.

ANR0187E Database db name was not found.

Explanation: The server attempted to open thedatabase, but it was not found by the databasemanager. If this occurs immediately after formatting anew database, it could mean the format operationfailed.

System action: The server process ends.

User response: Ensure that you format the databasebefore starting it the first time. Ensure that all databaseand log directories are online and available.

ANR0188E Fail to start the database manager.Database manager license not found

Explanation: Could not find database manager license.



ANR0189E Fail to start the database manager.Database manager license has expired

Explanation: Database manager license has expired.



ANR0190I Inventory file expiration startedprocessing node node name for backupsets.

Explanation: Expiration processing is currentlyevaluating information for backup sets for the nodespecified.


User response: This message is for informationalpurposes only and is only displayed if the expirationprocessing is invoked with QUIET=NO.

ANR0191I Inventory file expiration finishedprocessing node node name for backupsets with processing statistics: examinedexamined, deleted deleted, retryingretrying, and failed failed.

Explanation: Expiration processing has finishedprocessing backup sets for the node specified.Theending statistics show the number of objects examined,deleted, and those that failed to be processed.


User response: This message is for informationalpurposes only and is only displayed if the expirationprocessing is invoked with QUIET=NO.

ANR0193E The REPAIR EXPIRATION TYPE=typecommand cannot be issued from theserver console.

Explanation: The specified REPAIR EXPIRATIONcommand was issued from the server console. Thiscommand cannot be issued from the server consolebecause the administrator must be prompted tocontinue processing the command.

System action: The server ignores the command andcontinues processing.

User response: Issue the command from anadministrative client.

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: IBM Spectrum Protect will attempt toremove the extraneous 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 this



volume 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 thecontention 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.

ANR0200E PROTECT STGPOOL process process IDfailed due to insufficient space indestination storage pool.

Explanation: The destination stgpool had insufficientspace.

System action: The indicated process ends.

User response: Make more space available in thestorage pool and restart the operation.

ANR0201I The access mode for storage pooldirectory Directory Name in storage poolPool Name was changed to Access Mode.

Explanation: The access mode is changed for thespecified storage pool directory.

System action: Client nodes and server processescannot access the storage pool.

User response: To change the access mode, issue theUPDATE STGPOOLDIR command.

ANR0202I The parameter name has been set but thechanges will not be effective until thenext start

Explanation: The Database configuration has beenupdated but has not taken effect. This setting will takeeffect on next server start.

System action: This server parameter does not takeeffect until next start. The server continues processing.


ANR0203E MOVE CONTAINER process process IDterminated for container name -insufficient space in directory directoryname.

Explanation: During MOVE CONTAINER processing,the server could not allocate sufficient space in thestorage pool directory for the container.


User response: Make more space available in thestorage pool, and re-issue the MOVE CONTAINERcommand.

ANR0204I The container state for container name isupdated from previous state to currentstate.

Explanation: The server updates the container state.


User response: Review the other messages issued todetermine if further action is required.

ANR0205W Command name skipped data extent IDChunk ID because it is marked damaged.

Explanation: During command processing, the serverskipped a chunk that was marked damaged.



ANR0206E Command name process process ID faileddue to insufficient space in destinationstorage pool.

Explanation: The indicated process failed because thedestination storage pool has insufficient space.


User response: Make more space available in thestorage pool and reissue the command.



ANR0207W Command name skipped object ID ObjectID because one or more extents aremarked damaged.

Explanation: During command processing, the serverskipped an object because a data extent (chunk) wasmarked damaged.



ANR0208I Cloud tiering process process IDidentified a total of number of files filesand number of bytes bytes to move fromstorage pool source_stgpool to storagepool target_stgpool.

Explanation: The cloud tiering process finishedsearching for older files that must be moved to thetarget storage pool.

System action: Server operation continues as the filesare moved.


ANR0209W Tiering process process ID stopped - thetarget storage pool has insufficientspace.

Explanation: The server cannot tier the data becauseeither the target storage pool has insufficient space tostore the data or the access for the storage pool isunavailable or read-only.

System action: The process of tiering the data fromthe local storage pool to a target storage pool isstopped.

User response: Make more space available in thetarget storage pool, or specify a storage pool with morespace, and reissue the START STGRULE command.

ANR0211W The shredding process was unable toshred a deleted file.

Explanation: The shredding process encountered anerror that prevents a file from being shredded. Seeprevious error messages for more details.

System action: The file is not shredded. The next timethe shredding process runs, it will attempt to shred thefile again.

User response: If there are files that can not beshredded due to integrity or corruption errors orunrecoverable I/O errors, run the following commands:

1. Set for manual shredding, if not already done:SETOPT SHREDDING MANUAL

2. Run manual shredding with IOERROR parameter:SHRED DATA IOERROR=SHREDSUCCESS

3. Reset for automatic shredding, if desired: SETOPTSHREDDING AUTOMATIC

If an entire disk volume has failed and all files on it areno longer accessible, run the following commands:

1. Set the volume access to destroyed: UPDATEVOLUME volname ACCESS=DESTROYED

2. Delete the volume and the data: DELETE VOLUMEvolname DISCARDDATA=YES

3. Set for manual shredding, if not already done:SETOPT SHREDDING MANUAL

4. Run manual shredding with IOERROR parameter:SHRED DATA IOERROR=SHREDSUCCESS

5. Reset for automatic shredding, if desired: SETOPTSHREDDING AUTOMATIC

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.

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.

ANR0225S Invalid use of the -S command-lineoption.

Explanation: The -S option cannot be specified on thecommand line if the database ID file (dsmserv.dbid) isintact. This option is to be used only if the ID file doesnot exist.

System action: The server does not start.

User response: Start the server without specifying the-S command-line option.

ANR0226S The database ID file could not be foundfor server startup.

Explanation: The server's database ID file(dsmserv.dbid) could not be found. This file is createdwhen the database is formatted, is stored in thedirectory from which the format is performed, and isrequired for normal server operation.


User response: Ensure that you are starting the serverfrom the correct instance directory, and that the

ANR0207W • ANR0226S


dsmserv.dbid file exists and can be read. If nodsmserv.dbid file exists, restart the server with the -Soption to create a new database ID file.

ANR0227S Incorrect database opened. Servercannot start.

Explanation: The ID of the database opened does notmatch the ID stored in the database ID file(dsmserv.dbid).


User response: Ensure that you are in the properinstance directory for the database being opened, andthat the environment is set up correctly. The instancedirectory is generally the directory from which youformatted the database, or, if on UNIX, have specifiedwith the -i command-line option.

When the ID of the database that is opened does notmatch the ID that is stored in the database ID file(dsmserv.dbid), the server will not start. Use the -S(skip DB ID check) parameter after deleting thedsmserv.dbid file. After the initial use of the -Sparameter in a restore scenario, the server creates anew dsmserv.dbid file in the instance directory.

ANR0228S Error errno opening the database ID filefor server startup.

Explanation: The server's database ID file(dsmserv.dbid) could not be opened. The errnoindicates the reason for the failure.


User response: Ensure that you are starting the serverfrom the correct instance directory, and that thedsmserv.dbid file has the correct ownership andpermission. If the file is empty, erase the file, andrestart the server with the -S command-line option togenerate a new database ID file.

ANR0229W Server is unable to add entries to theActivity Log. Console messages will notbe logged until database access isavailable.

Explanation: The process that monitors the default(console) output stream and maintains the activity logcannot update the activity log. The error is due to theinability of the server to access the server database.

System action: The server does not update the activitylog. The activity log will continue to run and attemptto recover from this situation.

User response: Access to the server database istemporarily unavailable. The server database managerwill attempt to recover from this situation andreestablish access to the server database. When accessto the server database is reestablished, the activity logprocessing will continue. If the server database access

fails to be reestablished, additional messages will beissued providing more information.

ANR0236E Fail to start the database manager due toan I/0 error. Check for filesystem fullconditions, file permissions, andoperating system errors.

Explanation: The IBM Spectrum Protect serverencountered an I/O error while attempting to start thedatabase manager.


User response: Review the filesystems assigned to theserver for the database and recovery log.

ANR0237E Fail to start the database manager. Anunexpected system error occurred.

Explanation: An unexpected system error occurred.

Some common reasons for this error are:

v The system name where you ran the server has beenchanged

v The system date and time is set incorrectly



ANR0238E A database recovery task is prohibitingactivation of db name with sqlcodedbCode.

Explanation: While attempting to activate the databasean error occurred because the database was busyperforming a BACKUP, RESTORE or was inROLLFORWARD pending state. Examine the sqlcode todetermine the condition that is preventing the databasefrom activating. The following sqlcodes are most likelyto occur during the activate database step and willprevent the server from starting. SQLE_RC_BKP_PEND( -1116 ) indicates a database BACKUP is pending andmust complete prior to activating the database. Oncethe database BACKUP is complete,the database can beactivated by starting the server.SQLE_RC_ROLLFWD_PEND ( -1117 ) indicates adatabase Roll Forward operation is pending and mustcomplete before activating the database. After the RollForward recovery step is complete, the database can beactivated by starting the server.SQLE_RC_BKP_INPROG ( -1118 ) occurs when anattempt to activate the database fails because adatabase BACKUP was in progress. Prior to activatingthe database, it is necessary to rerun database BACKUP.Once the database BACKUP completes successfully, thedatabase can be activated by starting the server.SQLE_RC_RST_INPROG ( -1119 ) shows that adatabase RESTORE was in progress when the databasefailed to activate. The RESTORE database must berestarted and allowed to complete successfully beforeactivating the database. Once the database RESTORE in

ANR0227S • ANR0238E


complete, the database can be activated by starting theserver. SQLE_RC_BR_INPROG ( -1120 ) means thateither a database BACKUP or RESTORE must completebefore activating the database. Ensure that either aBACKUP or RESTORE operation completes successfullybefore activating the database.

System action: The server is not started because thedatabase cannot be activated.

User response: See message explanation for moreinformation.

ANR0239E The DB2 instance name instance namemay not be valid or is not configuredproperly. The return code was sqlcode

Explanation: IBM Spectrum Protect Server attemptedto connect using the database instance set by theDB2INSTANCE environment variable, but the attemptfailed.

System action: The server is not started because thedatabase instance is not valid.

User response: Verify that the database instance existsand that it is configured properly. You can list DB2instances by issuing the db2ilist command from theinstance directory, under the DB2 installation directory.Example: c:\Program Files\tivoli\tsm\db2\instance\db2ilist

ANR0264E A database file IO error is prohibitingactivation of db name with sqlcodedbCode.

Explanation: While attempting to activate the databasean IO error occurred when processing a database file.The problem may have occurred in one of thefollowing situations: The system cannot open, readfrom, or write to a database file. The system cannotcreate the database because an error occurred while thesystem was creating a database file or a directory forthe database. The system cannot drop the databasebecause an error occurred while the system wasdeleting a database file or a directory for the database.The system cannot create the database because aninterrupt was received while the system was creatingor deleting a database file or a directory for thedatabase. The system cannot locate the databasesubdirectory or database configuration file duringconnect. Problem causes are ordered in terms of theirfrequency of occurrence: A log file cannot be found inthe active log path directory. There may be a problemwith the database directory the operation is beingattempted on. There may be inadequate disk space tocomplete the operation. The database cannot be used.

System action: The server is not started because thedatabase cannot be activated.

User response: Appropriate responses for the problemcauses described above are: To verify if a log file ismissing, check the db2diag.log for the presence of a

logging error (return code contains SQLO_FNEX). Ifpresent, this error will contain the name of the missinglog file. Ensure that the file is located in the active logpath directory. If the file cannot be located, restore androll-forward the database to an earlier point in timereferenced in a log file preceding the missing log file(use a timestamp that is earlier than that of the missingfile). There may be a problem with the databasedirectory. Check the integrity of the directory. Examplesof potential problems include: permissions issues,mount point problems, corruption. Increase filesystemsize.

ANR0273W Not initializing library library namebecause the library is set offline .

Explanation: The External Library is set offline. It willnot be used for new transactions until it is set onlineagain.

System action: This server skips the initialization ofthe library. The server continues processing.

User response: Refer to the UPDATE PATH commandfor details on changing the online option.

ANR0274E Attempt to access library library namefailed, because the library is set offline.

Explanation: The Library is set offline. It will not beused for new transactions until it is set online again.

System action: This mount fails.

User response: Refer to the UPDATE PATH commandfor details on changing the online option.

ANR0275I Detected schema change for table table,attempting to reconcile.

Explanation: The schema for the table referenced doesnot match the server definition for this table. Theschema difference for this table will be reconciled.

System action: Server startup continues if the schemadifference was successfully reconciled. Server startupwill fail if the schema reconciliation failed.

User response: The schema for this table will attemptto be reconciled. Specifically, the server will try tomodify the table in the database to match the schemathat was expected. A message will be issued indicatingthe success or failure of the schema reconciliation.

ANR0276I Schema reconciliation for table tablesucceeded.

Explanation: The schema differences for this tablewere successfully reconciled.


User response: None



ANR0277E Schema reconciliation for table tablefailed.

Explanation: The server was unable to reconcile theschema differences for the indicated table.

System action: Server operation terminates.

User response: Contact your IBM servicerepresentative.

ANR0278S The database manager cannot create thedatabase because of a virtual memoryshortage.

System action: Server operation stops.

User response: Stop other applications running on thesystem, especially those that use large amounts ofshared memory.

ANR0279S Database manager failed to start due toincorrect service logon credentials.

Explanation: The server was unable to start thedatabase manager because the database managerservice credentials (userid and/or password) areincorrect.


User response: Correct the logon properties for thedatabase manager service by using the Services dialogbox from the Control Panel.

ANR0293I Reorganization for table table namestarted.

Explanation: The server is performing an onlinereorganization for the table referenced.

System action: The server will continue to operate.

User response: Monitor the available log space in theactive log and archive log storage paths. If the logspace available to the filesystem begins to fill up, thenperform a BACKUP DATABASE command with theTYPE=FULL parameter in order to initiate pruning ofthe archive log space.

ANR0294I Reorganization for table table nameended.

Explanation: The server online reorganization for thetable referenced has ended.


User response: Review the available log space in theactive log and archive log storage paths. If the logspace available to the filesystem has to filled up or isclose to filling up, then perform a BACKUPDATABASE command with the TYPE=FULL parameterin order to initiate pruning of the archive log space.

ANR0297I A full database backup might berequired. The last log number used islast log used and the first log numberused is first log used. The log file size islog file size megabytes. The maximum logfile size is maximum log file sizemegabytes.

Explanation: When the log space used since the lastdatabase backup exceeds the maximum log file size,either a full database backup is required, or themaximum log file size must be increased.



ANR0298S Authority is insufficient to access thedatabase.

Explanation: If the server is starting, then the user IDunder which the dsmserv process is running does nothave sufficient authority to access the database. If theserver is running and a server operation failed, then theuser ID does not have sufficient authority to performthe operation.

System action: If the server is starting, the dsmservprocess ends. If the server is running, the server stops.

User response: Ensure that the user ID under whichthe server is running is either the instance user ID, or isauthorized to access the database.

ANR0299I A full database backup will be started.The archive log space used is archivelog% and the archive log space usedthreshold is arch log threshold%.

Explanation: When the archive log space used exceedsthe threshold, a full database backup will be started.



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.


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 notalready defined, or

– lower the database backup trigger if one isdefined

Refer to the DEFINE DBBACKUPTRIGGER orUPDATE DBBACKUPTRIGGER commands.

ANR0316W A full backup for database DB Namecannot be started. This backup isrequired.

Explanation: An automatic full backup was attemptedfor this database. However, the device class fordatabase backups has not been specified.

System action: The database backup operation is notstarted.

User response: Issue the SET DBRECOVERYcommand to specify the default device class forautomatic database backups. Then, issue the BACKUPDB command and specify TYPE=FULL to back up thedatabase.

ANR0317I Reorganization of indices for table tablename started.

Explanation: The server is performing an onlinereorganization for the indices of the referenced table.


User response: Monitor the available log space in theactive log and archive log storage paths. If the logspace available to the filesystem begins to fill up, thenperform a BACKUP DATABASE command with theTYPE=FULL parameter in order to initiate pruning ofthe archive log space.

ANR0318I Reorganization of indices for table tablename ended with sqlCode dbCode.

Explanation: The server online reorganization for theindices for the table referenced has ended.


User response: Review the available log space in theactive log and archive log storage paths. If the logspace available to the filesystem has to filled up or isclose to filling up, then perform a BACKUPDATABASE command with the TYPE=FULL parameterin order to initiate pruning of the archive log space.

ANR0319W The file system for the database archivelog has insufficient free space.

Explanation: The usage of the file system for thedatabase archive log has exceeded theARCHLOGUSEDTHRESHOLD. Space is used by filesthat are not database archive log files, and the

BACKUP DB command cannot free space in thefilesystem..


User response: Create sufficient free space on the filesystem so that usage does not exceed theARCHLOGUSEDTHRESHOLD.

ANR0320W Storage agent storage agent is not able touse device class device class for storagepool storagepool for LAN-Free datamovement operations.

Explanation: The storage agent referenced is not ableto perform LAN-Free data movement operations usingthis storage pool and device class. The storage agent isback-level and is not able to support LAN-Freeoperations using this device class.

System action: LAN-Free data movement operationsare not performed. The operations are either sent viathe LAN or else proxied by the storage agent directlyto the server.

User response: In IBM Spectrum Protect version 5.3, achange was made to the way the FILE and deviceclasses are supported. This change prevents back-levelstorage agents from being able to use these deviceclasses. The storage agent should be upgraded to thesame version and release as the server. Until thestorage agent is upgraded, any LAN-Free datamovement operations that are attempted will be doneusing the LAN.

ANR0321W Storage agent storage agent name atversion storage agent VRMF does notsupport operation operationName,although the server server name atversion server VRMF can support it.

Explanation: The storage agent is at an earlier versionthan the server and is not able to use advancedfunctions that were requested by a client.

System action: The operation is not allowed.

User response: The storage agent must be upgradedto a version, release, and level that supports thisoperation. Typically, the problem is that the storageagent and server are not at the same version andrelease. For example, if the server is version 5.3.0.0 andthe storage agent is version 5.2.3.0, the storage agentneeds to be upgraded to version 5.3.0.0 to perform therequested function.

If this was a restore or retrieve operation and the clientnode DATAREADPATH setting was ANY or LANFREE,the server will override this to be LAN only. This willcause the operation to fail on the storage agent andmessage ANR0416W to be issued. Retry the operationafter performing one of the following actions:

v Halt the storage agent, upgrade the storage agentprogram, and then restart the storage agent.

ANR0316W • ANR0321W


v Set the ENABLELANFREE client option to NO, andthen restart the client

If this was a no-query restore operation, the data wasnot restored by the storage agent using LAN-Free datatransfer. If the client node is allowed to read data overthe LAN, the data was restored over the LAN. If theoperation failed because the client node is not allowedto read data over the LAN, consider updating theDATAREADPATH setting for this node by using theUPDATE NODE command.

If this was an operation performed by an agent nodewith proxy node authority to a target node, the sessionfailed with a protocol error. The operation wasattempted by a version 5.3 or higher client and server,but the storage agent is not able to support thisoperation. To allow an agent node to performoperations for a target node, the storage agent must beupgraded to version 5.3.0 or later.

ANR0322E The NEWSTGPOOL parameter is notvalid for deduplicated volume volumename.

Explanation: The volume contains one or morededuplicated objects and must be restored to theoriginal storage pool.


User response: To restore the volume to the originalstorage pool, reissue the RESTORE VOLUME commandwithout the NEWSTGPOOL parameter.

ANR0323E The NEWSTGPOOL parameter is notvalid for deduplicated storage pool poolname.

Explanation: The storage pool contains deduplicatedobjects and must be restored to the original storagepool.


User response: To restore the storage pool to theoriginal storage pool, reissue the RESTORE STGPOOLcommand without the NEWSTGPOOL parameter.

ANR0324E command: Replication parameters cannotbe used with the TYPE=SERVERparameter.

System action: The command failed.

User response: Reissue the command withoutreplication parameters. Replication parameters includeREPLSTATE, REPLMODE, BKREPLRULEDEFAULT,ARREPLRULEDEFAULT and SPREPLRULEDEFAULT.

ANR0325E command: Operation is not allowedbecause node nodename is a replica.

Explanation: The specified node is a replica of a nodeon another server, created using the REPLICATE NODEcommand.

You can restore or retrieve data from this node, but youcannot store new data or alter existing data in any way.

System action: Client sessions that attempt to storenew data or change existing data will be terminatedwith a protocol error. IMPORT operations will skip thenode.

User response: Perform the operation on the server onwhich the original node resides.

ANR0326E command: The ROLEOVERRIDEparameter cannot be used with eitherthe TYPE=SERVER or TYPE=NASparameter.


User response: Reissue the command without theROLEOVERRIDE parameter.

ANR0327I Replication of node node list completed.Files current: files current. Filesreplicated: files replicated of files toreplicate. Files updated: files updated offiles to update. Files deleted: files deleted offiles to delete. Amount replicated: amountreplicated of amount to replicate. Amounttransferred: amount transferred. Elapsedtime: elapsed time.

Explanation: The replication process has completed.The meanings of the numbers are:

v Files current indicates the number of files that do notneed to be replicated.

v Files replicated indicates the number of filessuccessfully replicated out of the number of files thatwe attempted to replicate.

v Files updated indicates the number of files whichhad meta-data updated on the target server out ofthe number of files that needed an update.

v Files deleted indicates the number of files deletedfrom the target server out of the number that neededto be deleted.

v Amount replicated indictaes the size of the files thatwere replicated out of the size of the files thatneeded to be replicated

v Amount transferred indicates the number of bytestransferred for the files that were replicated. Forcompressed files, the number of bytes transferred isthe compressed size in bytes. The total number ofbytes transferred can be less than the amountreplicated if data deduplication or compression isused to reduce the amount of data transferred.



v Elapsed time indicate how long the process ran



ANR0328I Replication preview of node(s) node listcompleted. Files current: files current.Files to be replicated: files to replicate.Files to be updated: files to update. Filesto be deleted: files to delete. Amount toreplicated: amount to replicate. Estimatedrun time: estimated runtime.

Explanation: The replication process has completed inpreview mode. The meanings of the numbers are:

v Files current indicates the number of files that do notneed to be replicated.

v Files to be replicated indicates the number of filesrequiring replication.

v Files to be updated indicates the number of filesrequiring a meta-data update.

v Files to be deleted indicates the number of files to bedeleted from the target server.

v Amount to be replicated indicates the size of the filesthat require replication.

v Estimated run time is an estimate of how long theprocess will run.



ANR0329I Starting replication of data type data fornode node name, filespace ID filespace id.

Explanation: The replication process has startedprocessing data for the specified node and file spaceID.



ANR0330W Session session number for node nodename (client platform) refused - invalidauthentication protocol requested.

Explanation: The server refuses a request to start asession because an invalid authentication protocol wasrequested during sign-on processing. This might be dueto a down-level client, server, or storage agent that isaccessing a server or storage agent that is configured todisallow such attempts.


User response: Upgrade the accessing client, server, orstorage agent to version 6.3 or later, or re-configure theserver to allow access from down-level clients, servers,or storage agents.

ANR0331W Replication session for server server namerefused - server is down-level.

Explanation: The server specified for replicationcannot be used because it is not at the current level.


User response: Upgrade the server to version 6.3 orlater, or specify a different server for replication.

ANR0332E Replication mode source repl mode ofnode node name is incompatible withmode target repl mode on server servername.

Explanation: The replication mode of the indicatednode is incompatible. If the source mode is SEND, thetarget mode must be RECV. If the source mode isSYNCSEND, the target mode must be SYNCRECV. Thesource mode cannot be anything other than SEND orSYNCSEND.

System action: The replication of the node's data fails.Server operation continues.

User response: Use the UPDATE NODE command toput the node in the proper state on both the source andtarget servers.

ANR0333E Server server name is disabled foroutbound sessions. The session requestis rejected.

Explanation: The DISABLED SESSION SERVERcommand disabled outbound sessions for the indicatedserver. Sessions to this server are not permitted.

System action: The session request fails. Serveroperation continues.

User response: Issue the QUERY STATUS commandto view the servers that are disabled for inbound andoutbound sessions. Issue the ENABLE SESSIONSSERVER command to make the server available foroutbound sessions.

ANR0334E Server server name is disabled forinbound sessions. The session request isrejected.

Explanation: The DISABLED SESSION SERVERcommand disabled inbound sessions for the indicatedserver. The indicated server is not permitted to initiatesessions to this server.

System action: The session request fails. Serveroperation continues.

User response: Issue the QUERY STATUS commandto view the servers that are disabled for inbound andoutbound sessions. Issue the ENABLE SESSIONSSERVER command to make the server available forinbound sessions.



ANR0335I Schema reconciliation for table table inprogress; pct% completed.

Explanation: The schema for this table is reconciling.

System action: Schema reconciliation will continue forthis table.

User response: None

ANR0336I Runstats for table table name started.

Explanation: The server is performing an onlinerunstats on the referenced table.



ANR0337I Runstats for table table name ended withsqlCode dbCode.

Explanation: The server online runstats for the tablereferenced has completed.


User response: For a non-zero sqlCode, consult theDB2 Information Center for details.

ANR0338E Database create terminated.

Explanation: DB2 detected a problem during thecreate database operation. The source of the problemmight be a DB2 limitation. When "No File SystemCaching" is used to create a table space with DatabaseManaged Storage containers, DB2 only supports storagedevices with a sector size of 512 Bytes on AIX, Solaris,Linux, Windows, and a sector size of 1024 Bytes onHP-UX.

System action: The create database operation isterminated.

User response: See the db2diag.log file for additionalinformation to confirm the DB2 limitation. Change thesector size to 512 Bytes on AIX, Solaris, Linux,Windows, and to 1024 Bytes on HP-UX.

ANR0339E command: Outbound replication isdisabled.

Explanation: Replication operations originating fromthis server are disabled.

System action: Processing ends.

User response: Use the ENABLE REPLICATIONcommand to re-enable the use of replication.

ANR0340E command: Outbound replicationoperations are disabled because thedatabase was restored.

Explanation: The database for this server wasrestored. Data that was on this server but that is notreferenced by the restored database is no longeraccessible. To prevent this server from deleting copiesof data that might exist on the target replicationservers, replication operations originating from thisserver are disabled.


User response: Disabling replication after a databaserestore is a precautionary step to alert the user of thepotential that a restored database might contain nodeinventory that could result in the loss of filespace dataon a target replication server that is using nodereplication. If replication was not used on this serverbefore the database restore, issue the ENABLEREPLICATION command to resume replicationoperations.

To preserve the data that exists on target replicationservers, determine whether copies of data that are onthe target replication server are needed. If they are, youmust replicate data that is on the target replicationserver to the source replication server. After thereplication is complete, issue the ENABLEREPLICATION command to resume replicationoperations.

For example, suppose that PRODSRV is the sourcereplication server. The data belonging to client nodeNODE1 was replicated from PRODSRV to DRSRV, thetarget replication server. The database on PRODSRVwas restored.

To resume replication, complete the following steps:

1. On PRODSRV and DRSRV, remove NODE1 fromreplication by issuing the following command:REMOVE REPLNODE NODE1.

2. Update NODE1 definitions. When replicationoccurs, DRSRV will send the data to PRODSRV thatwas lost because of the database restore.

a. On DRSRV, issue the following command:UPDATE NODE NODE1REPLSTATE=ENABLEDREPLMODE=SYNCSEND.

b. On PRODSRV, issue the following command:UPDATE NODE NODE1REPLSTATE=ENABLEDREPLMODE=SYNCRECEIVE.

3. On DRSRV, set the replication rules to match thoseon PRODSRV. For example, if only archive data wasbeing replicated from PRODSRV to DRSRV, set therules on DRSRV to replicate only archive data fromDRSRV to PRODSRV. Backup and space-manageddata will not be replicated to PRODSRV.



4. On DRSRV, set the target replication server byissuing the following command: SET REPLSERVERPRODSRV.

5. On DRSRV, replicate data belonging to NODE1 byissuing the following command: REPLICATE NODENODE1. Replication processing changes thereplication mode of NODE1 to SEND on DRSRVand to RECEIVE on PRODSRV.

6. On PRODSRV and DRSRV, remove NODE1 fromreplication by issuing the following command:REMOVE REPLNODE NODE1.

7. Update NODE1 definitions:

a. On PRODSRV, issue the following command:UPDATE NODE NODE1REPLSTATE=ENABLEDREPLMODE=SYNCSEND.

b. On DRSRV, issue the following command:UPDATE NODE NODE1REPLSTATE=ENABLEDREPLMODE=SYNCRECEIVE.

8. On PRODSRV, enable replication by issuing thefollowing command: ENABLE REPLICATION.

9. On PRODSRV, replicate data belonging to NODE1by issuing the following command: REPLICATENODE NODE1. Replication processing changes thereplication mode of NODE1 to SEND on PRODSRVand to RECEIVE on DRSRV.

The original replication configuration is restored.PRODSRV has all the data that was lost because of thedatabase restore.

REMEMBER: To replicate data that was on DRSRV, youset the target replication server to PRODSRV. In youroriginal configuration, if you were replicating data fromDRSRV to another server, for example, BKUPDRSRV,you must reset the target replication server. To reset thetarget replication server, issue the following commandon DRSRV: SET REPLSERVER BKUPDRSRV.

ANR0341E command with keyword keyword is notallowed when archive data retentionprotection is enabled.

Explanation: The specified command with thespecified keyword is not allowed when archive dataretention protection is enabled on the server.



ANR0343W File space filespace name could not becreated by node $$_TSMDBMGR_$$.$$_TSMDBMGR_$$ node name isreserved for IBM Spectrum Protectdatabase backup and restore.


User response: Node $$_TSMDBMGR_$$ is only usedfor IBM Spectrum Protect database backup or restore.The server does not create a file space with this specialnode since there is no running database backup orrestore session.

User response: Use another node name to create thisfilespace.

ANR0344E The server failed to restore the database.Missing ARCHIVELOGDIR value in theserver option file.

Explanation: While attempting to restore the database,the IBM Spectrum Protect server detects a missingvalue for ARCHIVELOGDIR in the server option file.

System action: Server database restore stops.

User response: Before reissuing the command torestore the database, check the following items:

v Ensure that ARCHIVELOGDIR option has a validvalue.

v Ensure that the command is using the correct optionsfile for the server. If you are using the -o option withthe command to specify a server options file, ensurethat the name and location of the file is correct.

ANR0345E The database manager cannot startwhile file file name exists.

System action: The server stops.

User response: Remove or rename the specified fileand restart the server.

ANR0347E Database database name is reporting adrive is invalid and the database can notbe removed.

Explanation: This message is issued to notify theadministrator that the server has detected that the APIis reporting an invalid drive condition during aREMOVE DB process.

System action: Server REMOVE DB stops.

User response: Interrogate the database, correct theproblem then issue the command again.

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.



ANR0361I Recovery is in progress following adatabase failure.

Explanation: During server initialization, the databasemanager indicated that the database requires failurerecovery. A database failure can occur in the event of apower outage or other abnormal termination of thedatabase manager. Failure recovery can take extensivetime, depending on how many transactions in the logrequire examination.

System action: The server initialization is delayedwhile the database is recovered.


ANR0365E Database database name is currently inuse and can not be removed.

Explanation: This message is issued to notify theadministrator that the server has detected that thedatabase is currently in use during a REMOVE DBprocess.


User response: Drop all database connections thenissue the command again.

ANR0366I Database database name was removedsuccessfully.

Explanation: This message is issued to notify theadministrator that the server has removed the serverdatabase successfully.


User response: The server database was removed. Inorder to run the IBM Spectrum Protect server, you needto format a new database using the 'DSMSERVFORMAT' command.

ANR0367W The server failed to format the databasedatabase name. This database namealready exists.

Explanation: While attempting to format a database,the IBM Spectrum Protect server has found that thisdatabase name already exists.

System action: Server format stops.

User response: Before reissuing the command toformat a new database, check the following items:

v Remove the old database using command 'DSMSERVREMOVEDB DB_NAME'.


ANR0369I Stopping the database manager becauseof a server shutdown.

System action: Stopping the server's databasemanager.


ANR0370E Diagnostic(ID) During the formatoperation, the server cannot create filesin one or more directories that youspecified for log type. Ensure that the filesystem where the directory is locatedhas sufficient space.

Explanation: Space is not available for the server towrite data to the directory.

System action: The format operation stops.

User response: Before reissuing the command toformat a new database, check the following items:

v Check whether the format operation created adatabase but did not remove the database after thefailure. If the database that was created was notremoved, use the utility DSMSERV REMOVEDBdb_name to remove it.

v Check that space is available to the directories thatyou specified forACTIVELOGDIR,ARCHIVELOGDIR, andARCHFAILOVERLOGDIR. Ensure that the amountof space meets requirements. For example, thedirectory for ACTIVELOGDIR must have at least 8GB space available.

v Remove any files that are in the directories that youwant to use for the recovery logs.

ANR0371E Error setting environment variableenvironment variable name with value value- return code return code value.

Explanation: The server is unable to set the content ofthe environment variable on the operating system tothe value specified in the message. The return code inthe message is the last error code set in the operatingsystem. The return code, or, last error code is a systemerror code as a result of the failed function call to setthe environment variable.

System action: The server operation stops.

User response: Refer to the list of system error codesprovided by the operating system to determine thecause of the problem. Resolve the problem and retrythe server operation.

ANR0372E Database database name is currentlydamaged and can not be removed.

Explanation: This message is issued to notify theadministrator that the server has detected that thedatabase is damaged during a REMOVE DB process.





ANR0373E Database database name is reporting aFile error and can not be removed.

Explanation: This message is issued to notify theadministrator that the server has detected that thedatabase is reporting a File error during a REMOVE DBprocess.



ANR0374E Database database name is invalid andcan not be removed.

Explanation: This message is issued to notify theadministrator that the server has detected that the APIis reporting an Invalid DB error during a REMOVE DBprocess.



ANR0375E Database database name is reporting anauthorization error and can not beremoved.

Explanation: This message is issued to notify theadministrator that the server has detected that thedatabase is reporting an authorization error during aREMOVE DB process.



ANR0376E Database database name is not found andcan not be removed.

Explanation: This message is issued to notify theadministrator that the server has detected that the APIis reporting the DB cannot be found during a REMOVEDB process.



ANR0377E Database database name is reporting adrive is not found and can not beremoved.

Explanation: This message is issued to notify theadministrator that the server has detected that the API

is reporting a database drive cannot be found during aREMOVE DB process.



ANR0378W Database database name is reporting adrive is not found and can not beremoved.

Explanation: This message is issued to notify theadministrator that the server has detected that the APIis reporting a warning during a REMOVE DB process.

System action: Server REMOVE DB completedsuccessfully.

User response: The drop database command hascompleted successfully, however, there are some nodeswhere the database alias or database name was notfound. It is possible that DROP DATABASE AT NODEwas already performed on these nodes.

ANR0379W A server database deadlock situation hasbeen encountered; the lock request forthe lock name lock, key name will bedenied to 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 the server processes encounter adatabase deadlock, they usually try to run the functionthat was in progress when the deadlock wasencountered again. Not all process can explicitly try anoperation again. For example, migration andreclamation will eventually try again. However,something like a delete volume run in a macro willonly be tried again 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 be retried (likemigration), monitor the retry effort to see if it succeeds.If the process or command cannot be retried, reissuethe command or macro that caused the action.

Consider what other processes are running at the timethe deadlock is reported. For example, if a process isstarted manually, as opposed to running as part of yourregularly scheduled server maintenance tasks, thatprocess may have caused the deadlock. You might haveto adjust the scheduling of your server maintenancetasks to avoid the problem.



ANR0387I Evaluating node node name using storageagent storage agent for LAN-free datamovement.

Explanation: The server is evaluating whether thenode and storage agent can use storage pools capableof LAN-free data movement.

System action: The server evaluates the storage pooldestinations available to this node and reports whichstorage pools can and cannot be used for LAN-freedata movement.

User response: Review the results of this processing todetermine if the appropriate LAN-free environment isconfigured.

ANR0388I Node node name using storage agentstorage agent has capable count storagepools capable of LAN-free datamovement and not capable count storagepools not capable of LAN-free datamovement.

Explanation: The server has completed evaluation ofthe LAN-free and non-LAN-free storage pooldestinations for this node using this storage agent. Theserver determined that there are capable count storagepools that are capable of LAN-free data movement. Italso determined that there are not capable count storagepools that cannot be used for LAN-free datamovement.


User response: Review the other messages issued todetermine which storage pools are capable of LAN-freedata movement and those which are not capable ofLAN-free data movement for this node using thisstorage agent.

ANR0389W Node node name has data pathrestrictions.

Explanation: The node name has data path restrictions.The registered node has data write path, data readpath, or both, configured to not allow LAN-freeoperations.


User response: Issue the command QUERY NODEnode name F=D and evaluate the data read path anddata write path settings. To store data or read datausing LAN-free data movement, set the data write pathto ANY or LANFREE.

ANR0390W A server database deadlock situation hasbeen encountered; the lock request fortransaction transaction ID will be denied.

Explanation: The server detected a deadlock situationbetween a number of processes that were attempting toaccess database information. A lock request for one of

the processes is 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 try an operation again. Forexample, migration and reclamation will eventually betried again. However, something such as a deletevolume run in a macro will only be tried again if thedelete command is reissued either in the macro or thecommand line.

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

User response: If a process can try again (likemigration), then monitor the subsequent attempt to seeif it succeeds or not. If it fails, contact a servicerepresentative. If the process or command is not able toautomatically try again, then reissue the command ormacro that caused the action to occur. If it fails again,contact a service representative for further assistance tobetter isolate the deadlock condition.

ANR0397I Session session number for nodeagent_node has begun a proxy session fornode target_node.

Explanation: A client session has begun proxyoperations.

System action: The server granted a proxy session toa client node.


ANR0398W Session session number for nodeagent_node has failed to begin a proxysession for node target_node.

Explanation: A client session attempted to begin aproxy operation. The server failed the client request.This can occur if the agent node does not have a proxyassociation with the target node.

System action: The server blocks the proxyauthorization attempt.


ANR0399I Session session number for nodeagent_node has ended a proxy session fornode target_node.

Explanation: A proxy session has been ended. Theserver terminates a session if there is an error in theprotocol. On the other hand, the client can alsoterminate the session.

System action: The server, or the client, has ended aproxy session for a client node.




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.


ANR0401W Session session number for administratoradmin name (client platform) refused -server version is down-level with thisclient.

Explanation: The server refuses an administrativeclient session because the client program version levelis newer than that supported by the server program.


User response: Apply service to the server program tomake it compatible with the newer client program, oruse an older client program to contact the server.

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.



ANR0404W Session session number for administratoradmin name (client platform) refused -client is down-level with this serverversion.

Explanation: The server refuses the administrativeclient session because the client program version levelis older than that supported by the server program. Forcertain problems (such as the compression fix), once anadministrative client connects to the server using the

newer client, the server records this fact and will not letthis administrative client back off this client version toa version that does not include the fix.


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

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.

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


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(Userid=user id), restored orretrieved object type object: node nodename, filespace filespace name, object objectname.

Explanation: This message logs information to theactivity log about an object that was restored orretrieved by a user logged in for a node. A user IDwith no value indicates that an administrative or rootuser on the platform initiated the restore.



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.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 a

ANR0409I • ANR0418W


client session because an invalid password has beensubmitted by the client during sign-on processing.

System action: The server will continue to deny accessattempts 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 SESSION command before clientnodes are permitted 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 not

registered in the server database. On newer serversoperating with newer clients, the client platform fieldcontains the communication method and address.


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. On newerservers operating with newer clients, the client platformfield contains the communication method and address.


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 - nodepassword has expired.

Explanation: The server refuses the specified sessionbecause the client node's password has 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 normal



operations. Alternatively, an authorized administratorcan update the client password using the UPDATENODE 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 program tomake it compatible with the newer client program, oruse 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 the 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 thisclient 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 updated

options 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 or by the LDAPdirectory server).

System action: Server operations continue.

User response: Before the client node is permitted toaccess the server, a properly authorized administratormust unlock the node. Nodes using LOCALauthentication can be unlocked with the UNLOCKNODE command. Nodes using LDAP authenticationcan be unlocked from within the LDAP directoryserver.

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 or by the LDAP directory server).


User response: Before the administrator is permittedto access the server, a properly authorizedadministrator must unlock the administrator.Administrators using LOCAL authentication can beunlocked with the UNLOCK ADMIN command.Administrators using LDAP authentication can beunlocked from within the LDAP directory server.

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) wasrefused because of insufficient recoverylog space.



Explanation: If a log runs out of space, the currenttransaction is rolled back. The server issues an errormessage and halts. You cannot restart the server untilthe recovery log size is increased.


User response: Monitor archive logs and active logs. Ifthe recovery log space is insufficient, monitor thearchive log space first. If the archive log space is full ornearly full, run a full database backup to removearchive logs and consider adding more disk space tothe archive log directory. If the archive log space is notfull and the active log space is full or nearly full,update the value of the ACTIVELOGSIZE option in thedsmserv.opt file. Set the value of the ACTIVELOGSIZEoption to the new maximum size of the active log.

ANR0434W Session session number for node oradministrator ID (client platform) wasrefused because of insufficient databasespace.

Explanation: The server ends the specified client oradministrative session because of insufficient databasespace.

System action: The server ends the session, butcontinues operation.

User response: To increase the amount of databasespace that is available to the server, issue the EXTENDDBSPACE command. Add one or more directories tothe database.

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 formessages. If the error cannot be isolated and resolved,contact your service representative.

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 and QUERY

STATUS commands to determine if the server is incompliance with license terms. Start an AUDITLICENSES process to readjust 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 command todetermine 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) -invalid stream mode switch.

Explanation: The server detects a protocol error on thespecified session because the client has attempted anillegal stream operation.


User response: Correct the programming error in theclient program if it has been written by yourinstallation. Otherwise, contact your servicerepresentative.

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 to

group 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. The client'sbackup operation continues, without compressing thedata.

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 orre-seller. 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 orre-seller. 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,or a password or node name is not setup for virtualvolume use on the source server.


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. For a virtual volume environment, thesource server must have a definition for the targetserver which includes a node name and password.

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 source server namerefused. Server source server name is notdefined for server-to-servercommunications on server target servername.

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 that use the SERVERPASSWORDrequire that each server has a server definition for theother server.


User response: Register the server names on bothservers before establishing a session, or update theserver's existing server definition and set aSERVERPASSWORD. An authorized administratormust use the DEFINE SERVER or UPDATE SERVERcommand to 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 the SETSERVERPASSWORD command and retry thecommand.

ANR0454E Session rejected by server target servername, reason: rejection reason.

Explanation: The server tried to open a session withthe named server. The session was rejected for theindicated reason.

System action: The operation fails.

User response: Check both the servers for anyadditional messages that might further describe thereason the session was rejected. The rejection reasonwill be in the form of "diagnostic code - reason". Thediagnostic code is only intended for use by yourservice representative. The following responses apply tothe specified rejection reasons.

v No Resource: Ensure that the receiving server isenabled and has sufficient database, log, andmemory resource to support the server session.

v Verifier expired: Ensure that the administrator'spassword is current on both servers.

v Admin not registered: Ensure that the administratoris registered on the target server.

v Inbound sessions disabled: Ensure that the targetserver has not disabled this server with the DISABLESESSIONS SERVER command.



v Down Level: Ensure that this server's level is currentwith respect to the target server's level.

v Admin in use: Ensure that the administrator is notbeing updated on the target server.

v Language not available: Ensure that requiredlanguages are installed on the target server.

v Admin locked: Ensure that the administrator is notlocked on either server.

v License Failure: Ensure that appropriate licenses areregistered.

v Admin on client port: Use the UPDATE SERVERcommand to set the admin port for the target server.

v SSL Required: Ensure that SSL is properlyconfigured.

v Authentication Failure: Ensure that all passwordshave been set correctly on both servers. Thepassword for the server (set by SETSERVERPASSWORD on server X) and the passwordin the server definition (set by DEFINE or UPDATESERVER X SERVERPASSWORD=) are the samepassword.

v Verification Failure: Use the QUERY SERVERcommand to determine that the HLADDRESS andLLADDRESS of the target server are correct. If theyare not, correct them with the UPDATE SERVERcommand. If they are correct, resynchronize with thetarget server by issuing the UPDATE SERVERFORCESYNC=YES command.

v Communication Failure: Ensure that the target serveris available and that TCPIP is available on bothservers. Use the QUERY SERVER command todetermine that the HLADDRESS and LLADDRESS ofthe target server are correct. If they are not, correctthem with the UPDATE SERVER command.

v Node Type: Either the TYPE of the registered nodeon the target server is not SERVER or theNODENAME parameter of the server definition onthe source server is incorrect.

v Internal error: Use the messages on the target serverto determine the problem.

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 server name -the server name at High level address, Lowlevel address 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. Storage Agents can also request server toserver sessions when setting up to access librariesthrough library client servers or library servers.


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 Authentication Protocol error on sessionsession number for 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 authenticationexchange 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 an IBM-provided client, please ensure that it isat the current software level.



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 specify adifferent node name for the client in the client optionsfile.

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 options fileof the client program that contains valid characters anddoes not exceed the maximum length in size.

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 validcharacters and is less than the maximum length in size.

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 messages andtake 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

ANR0460W • ANR0467I


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.

ANR0469W Session session number for node nodename (client platform) refused - client isnot configured for archive retentionprotection.

Explanation: The server refuses a client sessionbecause the client is not configured for archiveretention protection.


User response: Either disable archive retentionprotection on the server or configure the client forarchive retention protection.

ANR0470W Session session number for administratoradministrator name refused -administrator password has expired.

Explanation: The server refuses the specified sessionbecause the administrator's password has 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 UPDATEADMIN command.

ANR0472E The database manager did not start. Atablespace container is inaccessible.

Explanation: The server was unable to start thedatabase manager.


User response: Before restarting the server, check thefollowing items:

v Reboot the system.

v Check that the directories for dbdir, log, or devicesexists and that the file system is mounted (if it is ona separate file system).

v Make sure that the hardware and networkconnection are working properly.

v Fix any errors in the system log or db2diag.log.

ANR0473W Session session number for administratoradministrator ID (client platform) refused -administrator name does not have thecorrect level of authority over clientnode.

Explanation: The server refuses a request to start anadministrative session because the administrator namedoes not have appropriate authority over the node.


User response: Use command GRANT AUTHORITYto grant appropriate authority to the currentadministrator ID.

ANR0474W Session session number for administratoradministrator ID (administrator platform)was refused because administrators arenot allowed to initiate sessions on theclient port.

Explanation: The server did not start the specifiedadministrative session because the administratorconnected to the server on the server port that is usedfor client sessions, and the optionADMINONCLIENTPORT is set to NO. When differentport numbers are used for administrative and clientsessions (controlled by the TCPPORT andTCPADMINPORT options), and optionADMINONCLIENTPORT is set to NO, administrativesessions can be started only on the port used foradministrative sessions (as specified by theTCPADMINPORT option).


User response: Update the client options file tospecify the port to be used for administrative sessions.This is typically specified by the TCPADMINPORToption in both client and server option files.

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 option



in 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 the UPDATENODE command with the SESSIONINIT parameter tospecify that the client may initiate sessions.Alternatively, sessions can be scheduled with the clientthat are stared by the server through server-promptedscheduling commands ( DEFINE SCHEDULE, DEFINEASSOCIATION ).

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 with

server 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 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.

ANR0481W Session session number for node nodename (client platform) was terminated. Theclient did not respond withincommtimeout seconds seconds.

Explanation: The server ends a client session becausethe client was holding database locks during atransaction. The client did not respond within thenumber of seconds specified by the COMMTIMEOUTserver option.

System action: The server rolls back the transactionthat was in progress and the session is ended. Serveroperation continues.

User response: If this message appears frequently,consider incrementing the value specified for theCOMMTIMEOUT option. Use the SETOPT command tochange the value of the COMMTIMEOUT optionwithout stopping or restarting the server. This updatechanges the amount of time that the server waits for anexpected client message during an operation thatcauses a database update.

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 to



reconnect 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.

If this session is a proxied LAN-Free session for astorage agent, this error may be the result of a mountpoint or volume preemption on the storage agent.Review the messages logged by the storage agent todetermine if a storage agent action caused this to occur.

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.


User response: See the documentation for the

operating system about how to increase memory for anapplication.

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.

User response: If this session is a proxied LAN-Freesession for a storage agent, this error may be the resultof a mount point or volume preemption on the storageagent. Review the messages logged by the storageagent to determine if a storage agent action caused thisto occur.

If the cause of the error can not be determined afterreviewing the activity log, contact your servicerepresentative.

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 be



written, 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 re-configured 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 command toensure that the session you wish to cancel is connected.Reissue the command using the appropriate session

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 becomes available,restart the session that was cancelled. This session wasmost likely a backup/archive session and you may justwant to let it restart automatically during its nextscheduled backup window. If this message appearsfrequently, you may want to increase the number ofdrives available. See the MOUNTLIMIT parameter onthe 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 should



use the CANCEL PROCESS command to terminate theEXPORT/IMPORT operation.

ANR0496E Session session number operation forclient client node name (client platform) hasbeen denied because verb (type verbname) is not allowed when archiveretention is active.

Explanation: The server refuses the specified clientoperation because archive retention protection is active.


User response: Do not send the specified operation tothe server when archive retention protection is active.

ANR0497W Session request refused fromnon-Express client.

Explanation: A non-Express client has requested asession with the Express server. Only connections froman Express client will be accepted by an Express server.



ANR0498W Session session number refused for clientnode name because restore DB is inprogress.

Explanation: Restore DB is in progress, onlyconnection from Client related to restore DB areallowed.

System action: The session request is refused. Theserver Restore DB operation continues.


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 update

transaction 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.


ANR0502E Transaction failed for session sessionnumber for node node name (clientplatform) - A storage pool for the targetdestination is associated with a deviceclass that has a Centera device type.

Explanation: The server ends a database updatetransaction for the specified session because an invalidmanagement class has been specified. Centera devicetypes may be used only for archive objects.


User response: Ensure that Centera device types areassociated with device classes that are used only forarchive operations. The UPDATE COPYGRP commandcan be used to update copy groups associated withspace management and/or backup storage pools sothat they point to valid destinations.

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

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



ANR0504I Session session number for node nodename(Userid=user id), restored orretrieved object type object: node nodename filespace filespace name, object objectname, version version of total version.

Explanation: This message logs information to theactivity log about an object that was restored orretrieved by a user logged in for a node. A user IDwith no value indicates that an administrative or rootuser on the platform initiated the restore.





ANR0505E The database manager encountered anull value for column name during thedata fetching.

Explanation: The server received an unexpected datavalue.

System action: The server cannot process thecommand.

User response: Before reissuing the command, try thefollowing actions:

v Reboot the system.

v Check that the directories for dbdir, log, or devicesexists and that the file system is mounted (if it is ona separate file system).

v Make sure that the hardware and networkconnection are working properly.

v Fix any errors in the system log or db2diag.log.

ANR0506I A full backup has been started fordatabase DB Alias. This backup isrequired.

Explanation: This level of the IBM Spectrum Protectserver uses a new version of the database manager thathas a new format for log files. Database backupscreated prior to this level of the server cannot be usedto restore the database. A new database backup imageis needed to ensure that the database is protected.

System action: A full database backup is started.


ANR0507E Protocol error on session session numberfor node client node name (client platform)because an owner was not properlyprovided for the indicated node.

Explanation: The session does not adhere to theclient-server exchange sequence, therefore the serverdetected a protocol error on the specified session.


User response: If the client runs in a non-standardenvironment, the server detects that the owner field isnot being sent properly. It is not recommended to runthe client in a non-standard environment.

ANR0508E An automatic full database backup fordatabase DB Alias has failed.

Explanation: A full database backup failed. Thismessage always accompanies one or more othermessage that provides more details about the error.

System action: The server operation continues.

User response: Examine the server messages that wereissued prior to this message to determine the source ofthe error. Issue the QUERY ACTLOG command to view

the activity log and search for messages.

ANR0509E The database restore failed on DB Aliasdue to the log format differencesbetween database manager versions.

Explanation: The database restore failed because thebackup image was produced by a previous version ofthe database manager.

System action: The database restore terminates.

User response: If you need to restore the databaseimmediately, uninstall the upgraded server, re-installthe previous version of the server, then run the restorecommand. Otherwise, start the upgraded server. Theupgraded server creates a new backup imageautomatically. After the database backup completes, runthe server restore utility again.

ANR0510I Session session number opened inputvolume volume name.

Explanation: The indicated session has opened thespecified volume for input processing.



ANR0511I Session session number opened outputvolume volume name.

Explanation: The indicated session has opened thespecified volume for output processing.



ANR0512I Process process number opened inputvolume volume name.

Explanation: The indicated process has opened thespecified volume for input processing. You may or maynot see an associated ANR0515I message for thisprocess/volume combination, since some volumes areshared between multiple processes.



ANR0513I Process process number opened outputvolume volume name.

Explanation: The indicated process has opened thespecified volume for output processing. You may notsee an associated ANR0515I message for thisprocess/volume combination, since some volumes areshared between multiple processes.





ANR0514I Session session number closed volumevolume name.

Explanation: The indicated session has finished usingthe specified volume.



ANR0515I Process process number closed volumevolume name.

Explanation: The indicated process has finished usingthe specified volume. It is possible that the processindicated was not the process that opened the volume.



ANR0516E SQL processing for statement statementfailed.

Explanation: The indicated select statement failed. Thefailure was caused by a syntax error with the statementitself.

System action: The select statement failed.

User response: Review the server activity log formessage ANR0162W for an explanation of the errorthat caused this statement to fail.

ANR0517E command: The DEDUPLICATIONparameter cannot be used with eitherthe TYPE=SERVER or TYPE=NASparameter.


User response: Reissue the command without theDEDUPLICATION parameter.

ANR0518W NDMP restore failed for session sessionnumber for node node name (clientplatform), file space filespace.

Explanation: The server ends a restore operation forthe specified NAS node because an error has beenencountered on the server. Some common reasons forthe error are:

v The input volume is unavailable

v The storage pool is unavailable

v Data is corrupted on the input volume

v Hardware or media failure has occurred

v The server database is corrupted

System action: The server ends the restore operation.

User response: Examine any prior error messages todetermine the source of the error. Use the QUERYACTLOG command to view the activity log and search

for messages if needed. Correct any problem and trythe restore again. If the data is also backed up in acopy storage pool, the retry operation will attempt toread the file from the alternate location. If retry of therestore operation continues to fail contact your servicerepresentative.

ANR0519E A retrieve or restore operation failed forsession session number for node node name(client platform). An invalid partial objectrequest was received.

Explanation: The server ended a file retrieve or restoreoperation for the specified session because an invalidvalue for the offset, length, or both was received fromthe client application for the object being retrieved orrestored.

System action: The server ends the specified operationand server operation continues.

User response: Specify an offset, length, or bothwithin the bounds of the object to be retrieved orrestored, and rerun the application.

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 policy authorityover the client policy domain must correct managementclass definitions so that copy group destinations referto defined storage pools, or the specified storage poolmust be created by an authorized administrator.

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 and



resolve 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 addstorage to one or more storage pools in the storagehierarchy. Ensure that you size the file system based onthe amount of data that you manage. Add storagespace by using operating system tools. On the UPDATESTGPOOL command, specify the ACCESS parameter asREADWRITE to ensure that client nodes and serverprocesses can read and write to the storage pool.

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 find messagespreceding this one that specify the failing device.Storage pool volumes can be varied offline (by usingthe VARY command), or the server may need to behalted 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 tomake them available to client nodes for file storage.

ANR0526W A transaction failed for session sessionnumber for node node name (clientplatform) because of insufficient recoverylog space.




ANR0527W A transaction failed for session sessionnumber for node node name (clientplatform) because of insufficient databasespace.

Explanation: The server ends a database updatetransaction for the specified session because the serverhas insufficient database space.

System action: The server ends the specified session,but server operation continues.

User response: To increase the amount of databasespace that is available to the server, issue the EXTEND



DBSPACE command. Add one or more directories tothe database.

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.



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 that wereissued prior to this message to determine the source ofthe error. Issue the QUERY ACTLOG command to viewthe activity log and search for messages that indicatethe source of the error.

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 or

client 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 Diagnostic(ID): 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 the datawith compression turned off, or upgrade to a client thatsupports the newer compression method. If the client isa WDSF client, upgrade to a non-WDSF client in orderto use the compression performed by the client.

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. Sizeestimate was size estimate.

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.


If pool name is a random access storage pool withcaching enabled, it is also possible that additional spacecan be made available in this storage pool by



eliminating cached files. When the server allocatesspace based on the size estimate provided by the client,it frees space occupied by cached files if this space isneeded to obtain the estimated space. However, if theserver later determines that the file size estimate wastoo low, it attempts to obtain additional space that isnot utilized, but does not delete cached files to do so.

If the client sending the data has the optionCOMPRESSALWAYS YES set, it is possible that a filegrew during the compression operation and when theclient sent it to the server it exceeded the spaceavailable 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, anotherpossible 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 or validate your device class and libraryconfiguration.

ANR0536W Transaction failed for session sessionnumber for node node name (clientplatform) - down-level 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.

ANR0539W Transaction failed for session sessionnumber for node node name. This nodehas exceeded its maximum number ofmount points.

Explanation: The server ends the transaction becausethe node requires mount points to store data, andeither the node is not allowed to acquire any mountpoints, or the node is already using the maximumnumber of mount points allowed for the node. Themaximum number of mount points a node is allowedto use on the server is controlled by the setting of theMAXNUMMP parameter on the REGISTER NODE orUPDATE NODE command.


User response: If the number of mount points that thenode is allowed to use on the server are alreadyacquired, reduce the number of client sessions for thespecified node that are running concurrently. Forexample, decrease the value of the client optionRESOURCEUTILIZATION. If sufficient mount points(for example, drives) are available to satisfy the datastore operations, issue the UPDATE NODE commandto increase the value of the MAXNUMMP parameter.



If the node is not allowed to acquire any mount points(the node's MAXNUMMP option is set to zero), issuethe UPDATE NODE command to change the value ofthe MAXNUMMP parameter.

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 find messagespreceding this one that specify the device that is failing.Storage pool volumes can be varied offline (by usingthe VARY OFFLINE command), or the server may needto be shut down by using the HALT command tocorrect the hardware problem. After the problem iscorrected, the client may try the operation again.

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 orthe storage pool is unavailable.


User response: Use the VARY ONLINE command tovary offline storage volumes online in the storagehierarchy and make them available to client nodes forfile storage. If all volumes are online, check theACCESS parameter of the storage pool. If the accessmode is UNAVAILABLE, use the UPDATE STGPOOLcommand to update it to READONLY or READWRITE.

ANR0543W Retrieve or restore failed for sessionsession number for node node name (clientplatform) - data transfer interrupted.

Explanation: The database transaction associated with

session 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.

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 discarded andserver 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 filespace(fsId filespace id) for file file name storedas storage repository - error detected.

Explanation: The server ends a file retrieval operationfor the specified session because an error has beenencountered on the server. Some common reasons forthe error are:





v Database corruption


User response: Try the restore or retrieve operationagain, and if the file is also backed up in a copy storagepool, the operation will attempt to read the file fromthe alternate location. If retry of the restore or retrieveoperation continues to fail examine any prior errormessages to determine the source of the error. Use theQUERY ACTLOG command to view the activity logand search for messages if needed. Correct the problemand try the restore or retrieve again.

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 original restore.

It may have already completed or been cancelled. TheQUERY SESSION command and the QUERY RESTOREcommands can provide information about existingsessions and restore sessions which are restartable.

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 errormessages 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 on the(client platform) operating system becauseof a lock conflict.

Explanation: An operation that requires the server tolock a system resource has been initiated. The operationcannot be completed because the resource is in use byanother command or process.

System action: Server operations continue, but theserver does not process the command.

User response: To resolve the issue, take one of thefollowing actions: - If the failed command was run in alocal area network (LAN) environment, run thecommand again later. - If the failed command was runin a LAN-free environment, run the VALIDATELANFREE command and review the output: If theLAN-Free capable column displays a value of YES,retry the failed command. If the LAN-Free capablecolumn displays a value of NO, correct theconfiguration to support LAN-free data movement forthe storage agent and retry the failed command.Alternatively, retry the failed command in a LANenvironment.

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 the query.

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.

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.

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 cannot be specified.


User response: Reissue the command and omit theDATES=RELATIVE parameter.

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.

ANR0558W Import processing did not create aproxynode association for nodesnode_id_target and node_id_agent.

Explanation: Import processing did not create aproxynode association between the two nodes. Theassociation fails if either of the nodes does not exist onthe server, or if import processing was not allowed tocomplete.

System action: The server does not create thespecified proxynode association.

User response: Verify that both nodes were importedproperly and issue the import command again. Or, usethe GRANT PROXYNODE command to manuallycreate the proxynode association.

ANR0559E Too many domains are specified on theEXPORT NODE command.

Explanation: The maximum length of the domain listcannot exceed approximately 1400 characters.

System action: The EXPORT command is ended.

User response: If you specified DOMAIN=* on thecommand, issue the command again without specifyingthe domain to let it default to all domains. If youspecified a domain list, then split up the EXPORT intomultiple export commands to reduce the number ofdomains specified on the command.

ANR0560E Import command: Unable to decryptencrypted password or key.

Explanation: The server is not able to decrypt thepassword associated with a node or administrator, orthe client encryption key associated with an objectbeing imported. The password or key was encryptedwith the AES encryption standard, but the server doesnot support AES.

System action: The object is not imported.

User response: Rerun the export command, specifyingthe ENCryptionstrength=DES option. Or, rerun the



import on a server that supports AES.

ANR0561E Export command: Process aborted - signon to server, target server name, failed.

Explanation: The server export process encounteredan error in establishing a communication session withthe target server.

System action: The export process ends and serveroperation continues.

User response: Check the activity log and serverconsole for messages that indicate a failure or problemon the server issuing this command and on the targetserver. Next, check the server definition, administratorname, and password on both the server issuing thecommand and the server specified. Also, check thecommunication connection between the two servers.And finally, verify that the target server specified isrunning. If the problem is not resolved, contact yourservice representative.

ANR0562I Export command: Data transfer complete,deleting temporary data.

Explanation: The server export process has completedwriting data to the target media or server. Temporarydata used during the operation is now being deletedfrom the database.

System action: The export process continues until alltemporary data is removed.


ANR0563W NDMP restore failed for node node name,file space filespace.

Explanation: The server ends a restore operation forthe specified NAS node because an error has beenencountered on the server. Some common reasons forthe error are:





v The server database is corrupted

System action: The server ends the restore operation.

User response: Examine any prior error messages todetermine the source of the error. Use the QUERYACTLOG command to view the activity log and searchfor messages if needed. Correct any problem and trythe restore again. If the data is also backed up in acopy storage pool, the retry operation will attempt toread the file from the alternate location. If retry of therestore operation continues to fail contact your servicerepresentative.

ANR0564E Restartable restore request failed forsession session number, restartable restoresession restore session number - sessionsare active from the original restore.

Explanation: A client attempted to restart a restartableno query restore session; However, sessions from theoriginal no query restore invocation are still active.Both the current and restartable restore sessionnumbers are shown.

System action: The restartable restore request is endedand server operation continues. The restore'srestartability status does not change.

User response: Check the status of the original restore.The QUERY RESTORE command can be used to showthe status of restartable restores. The restartable restoresession number is the one for which sessions werefound to be running. Sessions may be active on eitherthe server or a storage agent. Restartable restores maybe cancelled by issuing the CANCEL RESTOREcommand, after which the restore may be retried. OnceCANCEL RESTORE is issued for a restore session, it isnot eligible to be restarted.

ANR0565W Retrieve or restore failed for sessionsession number for node node name (clientplatform). The storage volume volumename is 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, and make themavailable to client nodes for file storage.

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 find outif 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.


User response: If necessary, make more mount pointsavailable.

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 this

schedule 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 - default



or 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 theexported 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 correct

SPACEMGTECHNIQUE 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 managementclass 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 correct



MIGREQUIRESBKUP 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.



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.

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.

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.

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 run again the export orimport or 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 missing copygroup, an authorized administrator may cancel theimport operation, define the missing spacemanagement attributes or management class for thedomain, 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.

System action: The export process continues.


ANR0608E Command: Command failed - seeprevious error messages or view theactivity log.

Explanation: The indicated import command hasfailed. This message is always preceded by one or moreother error messages which provide more detail aboutwhy the command failed.



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 theEXPORT 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 mediavolumes 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 server

database 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 commandis 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 commandis 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=Yes

v Node node name is already registered andReplacedefs=No

v 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 serverfinds that an archive copy group is not defined for thedefault management class.


User response: If you want to define the missing copygroup, an authorized administrator may cancel theimport operation, define the missing management classor copy group for the domain, and process the importoperation 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 missing copygroup, an authorized administrator may cancel theimport operation, define the missing management classor copy group for the domain, and process the importoperation again.

ANR0654I Restartable export command with exportidentifier exportID started as processprocess ID.

Explanation: A background process was started toservice the command command. The backgroundprocess is defined as process process ID.


User response: To query the progress of thebackground server-to-server export process, issue theQUERY PROCESS or QUERY EXPORT command. Tosuspend the process, issue the SUSPEND EXPORTcommand. To cancel the background process, issue theCANCEL PROCESS command. Use the process IDnumber to specify this specific process.

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 find outif 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 numberspace-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 operation endsand 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 command toexamine messages prior to this error to determine thecause of the data storage failure. If the failure can befound 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 find messagespreceding this one to determine the cause of the error.After the problem is corrected, the command can beretried.

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 was



interrupted. 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 policy authorityover the client policy domain must correct managementclass definitions so that copy group destinations referto defined storage pools, or the specified storage poolmust be created by an authorized administrator.

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 or moreof the storage pools in the storage hierarchy can beincreased 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 find messagespreceding this one that specify the device that is failing.Storage pool volumes can be varied offline (by usingthe VARY OFFLINE command), or the server may needto be shut down by using the HALT command tocorrect the hardware problem. After the problem iscorrected, the client may be able to try the operationagain.

ANR0669W Export/import command: Transaction faileddata 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 wasinterrupted. 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: To increase the amount of log spacethat is available to the server, evaluate the directoriesand file systems that are assigned to theACTIVELOGDIRECTORY, ARCHIVELOGDIRECTORY,and ARCHFAILOVERLOGDIRECTORY options in thedsmserv.opt file. An out of log space condition mightoccur because the ACTIVELOGDIRECTORY location isfull.

Alternatively, an out of log space condition might occurif there are log files in the ACTIVELOGDIRECTORYlocation that are no longer active and cannot bearchived to the ARCHIVELOGDIRECTORY andARCHFAILOVERLOGDIRECTORY locations. Ifnecessary, specify a larger directory for theARCHIVELOGDIRECTORY orARCHFAILOVERLOGDIRECTORY options in thedsmserv.opt file and then restart the server.

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: To increase the amount of databasespace that is available to the server, issue the EXTENDDBSPACE command to add one or more directories tothe database.

ANR0673W Export/import command: Data storageretrieve or restore failed - error detected.

Explanation: The server ends an export or importoperation because an error has been encountered on theserver. Some common reasons for the error are:






System action: The server ends the export or importoperation and continues operation.

User response: Examine any prior error messages todetermine the source of the error. Use the QUERYACTLOG command to view the activity log and searchfor messages if needed. Correct the problem and try therestore or retrieve again.

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 find messagespreceding this one that specify the device that is failing.Storage pool volumes can be varied offline (by usingthe VARY OFFLINE command), or the server may needto be shut down with the HALT command to correctthe 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 ends andserver operation continues.


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 command terminates.


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.



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.


User response: Examine the server messages issuedprior to this message to determine the source of the



error. Use the QUERY ACTLOG command to view theactivity log and search for messages. If the error cannotbe isolated and resolved, contact your servicerepresentative.

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.

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.

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.



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.

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.

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.



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.



ANR0709E Command: No matching nodes registeredin the specified domains.

Explanation: The DOMAIN parameter has beenspecified for this command, but no nodes matching thenode 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 and serveroperation continues.


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.



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.

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 whenan internal communications error is encountered in theserver.

System action: Export/import processing is endedand server operation continues.

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 cannot

be isolated and resolved, contact your servicerepresentative.

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.

User response: Examine the server messages issuedprior to this message to determine the source of theerror. Use the QUERY ACTLOG command to view the



activity log and search for messages. If the error cannotbe isolated and resolved, contact your servicerepresentative.

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.


User response: Examine the source and target servermessages issued prior to this message to determine thesource of the error. Use the QUERY ACTLOGcommand to view the activity log and search formessages. If the error cannot be isolated and resolved,contact your service representative.

ANR0725E Export/import command: Previewprocessing terminated abnormally -authentication failure.

Explanation: Processing for the command export/import

command 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.


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 cannot



be isolated and resolved, contact your servicerepresentative.

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, the

default 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 correct COMPRESSIONvalue has been used for this node. Update this value, ifnecessary.

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 correct COMPRESSIONvalue has been used for this node. Update this value, ifnecessary.

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, management

class 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 value ofbackup 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 value ofarchive 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 the



MODE 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 group

copy 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 the



SERIALIZATION 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, management

class 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 the

ACTION 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 value



has 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 import

command, 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 forthis 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 value forthis 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 this

schedule 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 valueafter 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 proper



authorization 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 COMPRESSION parameterfor this node and restart the export command.Alternatively, use the export data with the unknownvalue, and check and update the COMPRESSION valueafter import processing has been performed.

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 achieve thedesired lock status, and then restart the exportcommand. Alternatively, use the export data with theunknown status, and lock or unlock the node afterimport 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: See the documentation for the



operating system about how to increase memory for anapplication.

If the error is not resolved, contact your servicerepresentative.

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.



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.



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.





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 toexamine messages prior to this error to determine thecause 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 command toexamine messages prior to this error to determine thecause of the data storage failure. If the import or exportoperation involves a session with another server, runthe QUERY ACTLOG command to examine messageson the other server as well. Messages on the otherserver can help you troubleshoot the error on the localserver. If you find and resolve the error, retry theexport or import operation. If you cannot find the error,contact your service representative for assistance inresolving 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 background processto perform the operation in response to the DELETEFILESPACE command entered by an administrator.

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 background processto perform the operation in response to a request fromthe 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 thearchive 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 and serveroperation continues.

User response: No action is required. An authorizedadministrator can issue the DELETE FILESPACEcommand to delete remaining objects in the file space.



ANR0806I The filespace name file space was deletedfor node node name: number of objectsobjects were deleted.

Explanation: A server process deleted file space datafor the specified node. The total number of deletedobjects is reported in the message.

System action: The deletion process is complete, butserver operations continue.


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: processed number of nodesnodes, 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.retry count objects were retried errorcount errors were encountered andskipped count objects were skipped.

Explanation: Server expiration processing hascompleted. The number of client objects examined anddeleted, based on management class policy, aredisplayed in the message. A total error count is alsodisplayed. A count of objects skipped due to replicationbeing required is also included. The number of DBbackup volumes deleted is based on the value specifiedon the SET DRMDBBACKUPEXPIREDAYS. Thenumber of recovery plan files deleted is based on thevalue specified on the SET DRMRPFEXPIREDAYS.Server expiration processing deletes the DB backupvolumes and recovery plan files only if DRM islicensed on the server and the volumes or plan files arecreated on the server 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 the

activity log to determine the cause for the errors.

ANR0813I Inventory file expiration process processID canceled prior to completion:processed number of nodes nodes,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. retry countobjects were retried error count errorswere encountered and skipped countobjects were skipped.

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 and a skipped is alsodisplayed.

System action: The server ends the file expirationprocess.



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 sometimes

encountered 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).

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 a validcombination 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, DEFINE

MGMTCLASS, 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 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 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 copies



that 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 DEFAULTmanagement 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 retrievefailure and correct it. After this situation is correct, theclient can do a restore of the specific file that wasskipped.

ANR0837I Inventory file expiration process processID was terminated after exceeding theduration limit of duration minutes:processed number of nodes nodes,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. retry countobjects were retried error count errorswere encountered and skipped count

objects were skipped.

Explanation: An administrator or schedule issued thecommand EXPIRE INVENTORY ... DURATION=xxx,where xxx is the number of minutes for the expireinventory process to run. That xxx number of minuteshas been reached, so the expire inventory process ends.

System action: The expire inventory process 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.

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: Try expiration again to determine ifthe cause of the deletion failure was an intermittentproblem or if it is a permanent problem. If after asubsequent expiration attempt the file still is notdeleted, 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.

See the documentation for the operating system abouthow to increase memory for an application.

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.

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.

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.




ANR0856E Server database space exhausted,DELETE FILESPACE process aborted.

Explanation: Insufficient server database space hasbeen encountered during file space deletion processing.



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.


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 error cannotbe isolated and resolved, contact your servicerepresentative.

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. retry count objects were retried anderror 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 expiration process.


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.


ANR0865E Expiration processing failed - internalserver error.

Explanation: Server retry processing during policyroll-off fails.

System action: The server ends policy roll-offprocessing.

User response: Issue the QUERY ACTLOG commandto view the activity log and search for messages.Examine the server messages issued prior to thismessage to determine the source of the error.

The following issues can cause this message to occur:

v The server is out of database space. To increase theamount of database space that is available to theserver, issue the EXTEND DBSPACE command toadd one or more directories to the database.

v The server is out of log space. To increase theamount of log space that is available to the server,evaluate the directories and file systems that areassigned to the ACTIVELOGDIRECTORY,ARCHIVELOGDIRECTORY, andARCHFAILOVERLOGDIRECTORY options in thedsmserv.opt file. An out of log space condition mightoccur because the ACTIVELOGDIRECTORY locationis full. Alternatively, an out of log space conditionmight occur if there are log files in theACTIVELOGDIRECTORY location that are no longeractive and cannot be archived to theARCHIVELOGDIRECTORY andARCHFAILOVERLOGDIRECTORY locations. Ifnecessary, specify a larger directory for theARCHIVELOGDIRECTORY orARCHFAILOVERLOGDIRECTORY options in thedsmserv.opt file and then restart the server.

v The server is low on memory. To increase theamount of memory that is available to the server, seethe operating system documentation that describeshow to increase memory for an application.

If the error cannot be isolated and resolved, contactyour service representative.

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.

System action: The server ends policy roll-offprocessing and server operation continues.

User response: Issue the QUERY ACTLOG commandto view the activity log and search for messages.Examine the server messages issued prior to thismessage to determine the source of the error.

The following issues can cause this message to occur:

v The server is out of database space. To increase theamount of database space that is available to theserver, issue the EXTEND DBSPACE command toadd one or more directories to the database.

v The server is out of log space. To increase theamount of log space that is available to the server,evaluate the directories and file systems that areassigned to the ACTIVELOGDIRECTORY,ARCHIVELOGDIRECTORY, andARCHFAILOVERLOGDIRECTORY options in thedsmserv.opt file. An out of log space condition mightoccur because the ACTIVELOGDIRECTORY locationis full. Alternatively, an out of log space conditionmight occur if there are log files in theACTIVELOGDIRECTORY location that are no longeractive and cannot be archived to theARCHIVELOGDIRECTORY andARCHFAILOVERLOGDIRECTORY locations. Ifnecessary, specify a larger directory for the



ARCHIVELOGDIRECTORY orARCHFAILOVERLOGDIRECTORY options in thedsmserv.opt file and then restart the server.

v The server is low on memory. To increase theamount of memory that is available to the server, seethe operating system documentation that describeshow to increase memory for an application.

If the error cannot be isolated and resolved, contactyour service representative.

ANR0867E Unable to open policy domain for nodenode name during server operation.

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 processing andserver 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.



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.


User response: Examine the server messages issuedprior to this message to determine the source of theerror. Issue the QUERY ACTLOG command to view the



activity log and search for messages. If the error cannotbe isolated and resolved, contact your servicerepresentative.

ANR0874E Backup object object 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.



ANR0879E Error opening inventory file spacequery.

Explanation: Policy roll-off processing on the serverencounters a database error in accessing inventoryinformation.



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 FILESPACE commandto determine which file spaces are defined on theserver. Note, that file space names are case sensitive.Reissue the file space command and specify the properfile 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 were notdeleted. Only the information used to sort these objectsduring the previous export operation was deleted. Thebackground process was terminated before all sortinginformation had been deleted. The system will notperform further export processing of file data until thisproblem 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 the



server. 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 no archivecopy group with id copy group id. Serveroperation will not be performed for filesfrom this node and filespace that arebound 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 specified files.


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.


User response: Issue the SQL command from anadministrative client.

ANR0889I Deleted count statistics reports aboutdata deduplication for node node name.

Explanation: The server processed DELETEDEDUPSTATS for the specified node, with the totalnumber of deleted statistics reports about datadeduplication specified in this message.

System action: The deletion of data deduplicationstatistics is complete for the node, and serveroperations continue.


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 nooption sets 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. Accepting an invalid date can cause any of thefollowing problems:Premature deletion of dataExcessive retention of dataScheduling problemsEvent record problemsPassword expiration problems.

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 not want toexecute the command.

ANR0894I Current system has been accepted asvalid.

Explanation: This message 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. The server will begin processingusing the current system date.

User response: Issue the ENABLE SESSIONS ALLcommand to allow client, server and administrativesessions to start.

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.

User response: This usually indicates that sufficientserver memory is not available on the server.

See the documentation for the operating system abouthow to increase memory for an application.

ANR0896I Generated count statistics reports aboutdata deduplication for node node name inpool pool name.

Explanation: The server processed GENERATEDEDUPSTATS for the specified node and pool, with thetotal number of generated statistics reports about datadeduplication specified in this message.

System action: The generation of data deduplicationstatistics is complete for the node and pool specified inthe command, and server operations continue.


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 or invalid valuefound in file filespec.

Explanation: While processing the server options filenamed, the server has encountered an invalid keywordor an invalid value on an option statement. The linesfollowing this message provide more information.

System action: The server ignores the optionstatement in error. Server initialization continues. Thedefault value is used for any missing or ignoredoptions.

User response: Ignore the error, or use a text editor tocorrect the error and restart the server.

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.

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's lengthexceeds the maximum specified for the object. Reducethe 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.

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 with thecorrect 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 IBM SpectrumProtect version 5.1.5 or higher in order to support theextended low-level qualifier.

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 (baseId) for subfile (subfileId):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.


User response: If the process is a REPLICATE NODEprocess and is on the target server, it cannot becanceled if the process is in progress and the sourceserver is available. The target server monitorscommunications with the source server. If 5 minuteshave expired since the last communications, the targetserver assumes that the source server is no longeravailable, and the process is canceled. To view thelength of time during which the process has been idle,issue the QUERY PROCESS command and specify theprocess ID for the replication process.

ANR0944E Command: No active processes found.

Explanation: A QUERY PROCESS command has beenentered, and no processes are active.



ANR0946E Archive processing fails: Object objId notfound.

Explanation: Archive processing fails because thespecified object was not found. An archive request iscompleted in stages. The object may have been deleted

by 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 and retrymessages. Reissue the archive request if the retry failed.

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 accesspermissions, 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.

ANR0950I Session Session number for node Nodename is using inline server datadeduplication or inline compression.

Explanation: Inline data deduplication or inlinecompression was used for the specified node andsession.

System action: Data was deduplicated by the serveras it was written to the container storage pool.


ANR0951I Session Session number for node Nodename processed files processed files byusing inline data deduplication orcompression, or both. The number oforiginal bytes was bytes processed. Inlinedata deduplication reduced the data bybytes reduced by dedup bytes and inlinecompression reduced the data by bytesreduced by compression bytes.

Explanation: Data deduplication or compressionprocessing, or both, is complete for the specified node.

System action: Statistics are displayed for thespecified node.


ANR0952W The filespace Filespace name cannot beincluded in the backup set because itcontains encrypted data.

Explanation: Data from the filespace cannot beincluded in the backup set because the filespacecontains encrypted data.

System action: The filespace is skipped.




ANR0955I DELETE FILESPACE filespace name fornode node name failed deletion becauseof a restartable restore session.

Explanation: The reported node and filespace have arestartable restore session active or restartable. Afilespace cannot be deleted while the restartable restoresession exists.

System action: The server process is retried if themaximum number of retry attempts have not beenexceeded.

User response: Use the QUERY RESTORE commandto view active and restartable restores sessions for thisfilespace. Either wait for the sessions to complete orcancel the sessions with the CANCEL RESTOREcommand, and reissue the DELETE FILESPACEcommand. To view restartable restore sessions issue thecommand QUERY RESTORE. Either:

v wait to reissue the DELETE FILESPACE commandafter this restartable restore has completed

v cancel the restartable restore session with theCANCEL RESTORE command

ANR0958I CLEANUP BACKUPGROUPS evaluatedobjectcount group objects, founderrorcount errors, and deleted deletedgroup objects with completion statestate.

Explanation: The CLEANUP BACKUPGROUPS utilityended with the presented state.



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.




ANR0981E The server database must be restoredbefore the server can be started.

Explanation: This message is issued in one of twocases: 1) The server has been restarted after anincomplete RESTORE DB. In order to start the server,you must restore the database to a consistent stateusing the DSMSERV RESTORE DB command; 2)During server operation, an error condition occurredsuch that the IBM Spectrum Protect server cannotcontinue. This message is issued, and the server halts.Before you can start the server again, you need to usethe DSMSERV RESTORE DB command to restore thedatabase.

System action: Server initialization stops, or the serverstops.

User response: If there are other messages issued withthis error message which have instructions associatedwith them, follow the instructions in those messages.Then issue the DSMSERV RESTORE DB command.After the DSMSERV RESTORE DB command completessuccessfully, restart the IBM Spectrum Protect server.

ANR0982I Session Session number for node Nodename is using server-side encryption.

Explanation: Server-side encryption was used for thespecified node and session.

System action: Data was encrypted by the server as itwas written to the container storage pool.


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 to

be 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 SUCCESS indicatesthat the operation ran successfully. A completion stateof FAILURE indicates that the operation encounteredan error condition or ended before completion. Acompletion state of COMPLETED indicates that theoperation ran to completion; however, conditions mighthave occurred that can affect the outcome of theoperation.

System action: If the completion state is SUCCESS orCOMPLETED, no action is required. If the completionstate is FAILURE, investigate the cause.

User response: If the completion state is FAILURE,review the activity and event logs to determine thecause of the failure and correct the issue. If thecompletion state is COMPLETED, you can optionallyreview the activity and event logs to find possiblewarning or error messages about conditions that mighthave 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.

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. The total bytes that isreported is the number of bytes of source data that wasprocessed in the transaction. It does not include anymeta data that might be in the output.


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 can



still be checked for warning messages regardingconditions that could have affected the operation.

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 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.

ANR0988I Process process ID for process namerunning in the process state processedbytes processed bytes with a completionstate of completion state at process starttime.

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.

ANR0989E The server database must be inserted orrestored before the server can be started.

Explanation: The server is restarted after theLOADFORMAT command is run. To start the server,you must upgrade the database by issuing DSMSERVINSERTDB or else the database needs to be restoredusing the DSMSERV RESTORE DB command.


User response: Issue the DSMSERV INSERTDB orDSMSERV RESTORE DB command. Alternatively, theserver can be installed using the DSMSERV FORMATcommand in order to prepare it for regular use without

needing to upgrade an earlier version server with theDSMSERV INSERTDB command or restoring thedatabase with the DSMSERV RESTORE DB command.

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's database formatting complete.

Explanation: The server formatting procedure hascompleted successfully. The server is now available fornormal operation.

System action: Server completes formattingprocessing.


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.


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; reinstallation is required touse this version.

Explanation: At server startup, the server hasdiscovered that the disk information was written by anearlier 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 nameautomatically or manually,highMig=highMig value, lowMig=lowMigvalue, duration=duration.

Explanation: Because the high migration threshold forthe storage pool shown has been exceeded, a processhas been started to migrate files from the storage pool.Note: a duration value of No means that the durationis not specified and hence the migration runs withoutduration.

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, there are no more nodes with files to bemigrated, there are no more volumes to be migrated, orthe duration specified has been reached.



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.

ANR1013I During a store operation, the server isswitching to a next pool in the storagehierarchy. The next storage pool willinherit the simultaneous writeconfiguration from the destinationprimary storage pool.

Explanation: If during a backup, archive, clientmigration, or server import operation, the server mustwrite data to a next pool in a storage pool hierarchy,the following rules will apply:

1. If the destination storage pool specified in themanagement class copy group has one or morecopy storage pools associated with it forsimultaneous write operations:

a. The server will write the data to the next storagepool and to the copy pools that are associatedwith the original destination primary storagepool.

b. The setting of the COPYCONTINUE attribute ofthe original destination primary pool will beinherited by the next pool.

c. If the next pool is configured for simultaneouswrite operations, the copy storage poolsassociated with the next pool will be ignored aswell as the value of its COPYCONTINUEattribute.



2. If the primary storage pool specified in themanagement class copy group does not have copypools associated with it for simultaneous writeoperations:

a. The server will write the data to the next storagepool.

b. If the next pool is configured for simultaneouswrite operations, the copy pools associated withthe next pool will be ignored.


User response: None. Refer to IBM Knowledge Centerfor details about simultaneous write configurations.

ANR1014W The pool type storage pool pool name iseither not available, or does not haveenough space for a simultaneous writeoperation.

Explanation: During a backup, archive, clientmigration, or import operation that is usingsimultaneous write, the server cannot write data to thespecified storage pool. Possible reasons include:

v The storage pool is unavailable.

v There is not enough space available in the specifiedstorage pool.

System action: The result of the simultaneous writeoperation depends on the setting of theCOPYCONTINUE attribute of the original destinationprimary pool destination:

v If the value of the COPYCONTINUE attribute of thedestination primary pool is YES, the server will stopwriting to the failing copy pool for the remainder ofthe session, but continue storing files into a primarypool in the storage hierarchy and any otherremaining copy pools.

v If the value of the COPYCONTINUE attribute of thedestination primary pool is NO, the server will failthe transaction and discontinue the operation.

User response: Ensure the copy storage pool is set forREADWRITE access. If needed, make more spaceavailable in the copy storage pool. After the problem iscorrected, take one of the following actions:

v If the value of the COPYCONTINUE attribute of thedestination primary pool is YES, issue the BACKUPSTGPOOL commands to back up any files inprimary storage pools in the storage pool hierarchythat have not been copied to the copy pool thatfailed.

v If the value of the COPYCONTINUE attribute of thedestination primary pool is NO, run thesimultaneous write operation again.

ANR1015I Storage pool pool name has pending bytesduplicate bytes pending removal.

Explanation: The number of bytes indicated have beenidentified as duplicate bytes in the storage pool, but thevolumes on which the data resides have not yet beenreclaimed.

System action: None

User response: None

ANR1016W Fibre Channel adapters on the systemcannot be opened.

Explanation: Due to problems with the HBAAPI orFibre Channel HBA driver, the HBAAPI functioncannot open any Fibre Channel host bus adapters(HBAs) on the system.


User response: The IBM Spectrum Protect SANdiscovery function is not working. Check your FibreChannel host bus adapter (HBA) vendor and upgradeyour HBAAPI or Fibre Channel HBA driver version.For a list of supported HBAs and required driver levelsby operating system, see techdoc 1193154 athttp://www.ibm.com/support/docview.wss?uid=swg21193154.

ANR1018I Volume deduplication process process IDstarted for storage pool storage pool name,identify processes=number of identifyprocesses.

Explanation: A volume deduplication process wasstarted for the storage pool shown.



ANR1019W Unable to get the node attributes fornode name.

Explanation: The HBAAPI function cannot obtain thenode's attributes. Removing devices from the SANwithout reconfiguring the system can cause thisproblem.


User response: SAN discovery is not working for thisdevice. Check the device configuration on the system.

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. If



http://www.ibm.com/support/docview.wss?uid=swg21193154


other 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.

User response: One possible cause for this failure isthat the access state for the target volume or storagepool for this operation is not set to READWRITE.Check the access state for the requested output volumeand storage pool and ensure they are set toACCESS=READWRITE.

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.


User response: Use the UPDATE STGPOOL commandto change the next storage pool maximum file size or tochange 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.

System action: The indicated migration process ends.



The server waits for the retry period to expire and thentries the migration again.

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.


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.

ANR1045E Reclamation has ended for volumevolume name. The files on the volume aretoo large for the target storage pool,storage pool name.

Explanation: During reclamation for the indicatedvolume, the server cannot move the data from thevolume because a file is larger than allowed for theindicated storage pool.

System action: Reclamation of the volume stops. Ifother reclamation processes are running, theseprocesses will continue the reclamation.

User response: Use the UPDATE STGPOOL commandto change the value of the MAXSIZE parameter for thestorage pool. Specify the value as NOLIMIT, or specifya value larger than the largest file to be reclaimed.

ANR1046E command: Database upgrade notcurrently supported for this serverbecause it uses backup sets.

Explanation: The current version of the IBM SpectrumProtect 6.1 server does not support backup sets.However, the server being upgraded uses backup sets,and so cannot be upgraded at this time. Note that thisis a temporary limitation that will be lifted in a futureIBM Spectrum Protect 6.1 Server Fix Pack.

System action: The command ends without insertingany data into the database.

User response: Rerun the command using a version ofthe IBM Spectrum Protect 6.1 server that supportsbackup sets.

ANR1047E command: Database upgrade notcurrently supported for this serverbecause it uses NAS backups withTOCs.

Explanation: The current version of the IBM SpectrumProtect 6.1 server does not support NAS backups thatuse a table of contents (TOC). However, the serverbeing upgraded uses TOCs, and so cannot be upgradedat this time. Note that this is a temporary limitationthat will be lifted in a future IBM Spectrum Protect 6.1Server Fix Pack.


User response: Rerun the command using a version ofthe IBM Spectrum Protect 6.1 server that supports NASbackups with TOCs.



ANR1048E command: Protocol error -out-of-sequence verb (type verb name)received.

Explanation: The server detects a protocol error whileupgrading the database because a verb has beenreceived that does not adhere to the defined verbsequence. This error may be the result of using aversion of the DSMUPGRD utility that is notcompatible with the IBM Spectrum Protect 6.1 versionto which you are upgrading.


User response: Rerun the command using a version ofthe server compatible with the version of DSMUPGRDused to extract the data. Or reextract the data using anolder version of DSMUPGRD that is compatible withthe version of the server.

ANR1049W The server is unable to obtainnumber-formatting information from thesystem-locale attributes. The serversubstitutes alternate number formatnmbrFmt.

Explanation: The server is unable to format somenumbers because it is unable to obtain a valid thousandand decimal separator value from the system locale.

System action: The server continues. An alternatenumber format is used. Numbers are displayed using acomma character as the thousand separator and aperiod character as the decimal separator.

User response: Check whether errors occurred duringserver initialization that might indicatea probleminitializing the locale . Check whether the server isrunning in a locale supported by the server. If it is not,restart the server in a supported locale.

ANR1053E Command: Invalid process number -processIdvalue

Explanation: A QUERY EXPORT command wasissued that specifies an invalid process number.

System action: The server does not process thecommand.

User response: Reissue the command with a validprocess number.

ANR1054E Command: Invalid export operation state- export state

Explanation: A QUERY EXPORT command wasissued that specifies an invalid export state.


User response: Reissue the command with a validexport operation state.

ANR1055E Command: Invalid export sessionidentifier name - export sess name.

Explanation: The issued command specifies an invalidexport session identifier.


User response: Reissue the command with a validexport session identifier.

ANR1056E command name: The PROCESS parameteris not valid if an export identifier isspecified.

Explanation: The command failed because of aninvalid combination of arguments.

System action: The command fails and serveroperations continue.

User response: Reissue the command with a valid setof parameters.

ANR1057E command name: The PROCESS parameteris not valid when the STATE parameteris specified with a value ofINITIALIZING or SUSPENDED

Explanation: The command failed because of aninvalid combination of arguments.


User response: Reissue the command with a valid setof parameters.

ANR1058E command name: TODATE must bespecified when TOTIME is specified.

Explanation: A command supporting the TODATEand TOTIME parameters was issued with the TOTIMEparameter specified but without the TODATEparameter. When the TOTIME parameter is used, theTODATE parameter must be specified.


User response: Reissue the command and specify boththe TODATE and TOTIME parameters.

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.

System action: Space reclamation stops. The serverwaits for the retry period to expire and then tries thereclamation again.


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 theadministrator 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.



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.



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.



ANR1080W Space reclamation is ended for volumevolume name. The process is canceled.

Explanation: During space reclamation for theindicated volume, the process performing thereclamation has been canceled.

System action: Space reclamation of the volume stops.If other reclamation processes are running, theseprocesses will continue the reclamation.


ANR1081E Space reclamation is ended for volumevolume name. Storage media isinaccessible.

Explanation: During space reclamation for the



indicated volume, a required volume cannot bemounted.

System action: Space reclamation of the volume stops.If other reclamation processes are executing, theseprocesses will continue the reclamation.


ANR1082E Space reclamation is ended for volumevolume name. There is an 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.



ANR1083E Space reclamation is ended for volumevolume name. Excessive read errors wereencountered.

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.

ANR1084E Space reclamation is ended for volumevolume name. Excessive write errors wereencountered.

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.

ANR1085E Space reclamation is ended for volumevolume name. Data transfer wasinterrupted.

Explanation: During space reclamation for theindicated volume, a data transfer operation has beeninterrupted and cannot be continued.

System action: Space reclamation of the volume stops.If other reclamation processes are running, these

processes will continue the reclamation.

User response: If possible, determine and correct thecause of the interruption.

ANR1086E Space reclamation is complete forvolume volume name. The storage poolhas insufficient space.

Explanation: During space reclamation for theindicated volume, data could not be moved from thevolume due to insufficient space on other volumes inthe storage pool.

System action: Space reclamation of the volume stops.If other reclamation processes are running, theseprocesses continue the reclamation.

User response: Make more space available on othervolumes in the storage pool. If necessary, define thenext storage pool.

ANR1087E Space reclamation is ended for volumevolume name. Sufficient recovery logspace is not available.

Explanation: During space reclamation for theindicated volume, the server runs out of recovery logspace.

System action: Space reclamation stops.


ANR1088E Space reclamation is ended for volumevolume name. Sufficient database space isnot available.

Explanation: During space reclamation for theindicated volume, the server runs out of databasespace.

System action: Space reclamation stops.


ANR1089E Space reclamation is ended for volumevolume name. There is a 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 try thereclamation again.



ANR1090E Space reclamation is ended for volumevolume name. Thread resource is notavailable.

Explanation: During space reclamation for theindicated volume, the server cannot start a thread forthe reclamation process.


User response: Wait for the server to try thereclamation again. If the error persists, it might indicatea shortage of server memory.

ANR1091E Space reclamation is ended for volumevolume name. Sufficient memory is notavailable.

Explanation: During space reclamation for theindicated volume, there was not enough servermemory available.



ANR1092E Space reclamation is ended for volumevolume name. An internal server errorwas detected.

Explanation: During space reclamation for theindicated volume, the server encounters an internalerror.


User response: Examine the server messages that wereissued prior to this message to determine the source ofthe error. Issue the QUERY ACTLOG command to viewthe activity log and to look for messages that indicatethe source of the error. Correct any errors that mighthave caused the space reclamation to fail and try theoperation again.

ANR1093E Space reclamation is ended for volumevolume name. The transaction is ended.

Explanation: During space reclamation for theindicated volume, the server detected an error whileattempting to commit a transaction.


User response: Check for additional messages and

eliminate the condition that caused the failedtransaction.

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 indicatednode 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 to



complete 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.



ANR1104E Operation process process ID terminated -NAS datamover NAS datamover namereported NDMP session errors.

Explanation: During the indicated operation, theNDMP session with the NAS file server reported errorswhich prevent the operation from continuing.


User response: For details about how to identify thecause of the terminated NDMP operations, see the NASfile-server documentation. Check the NDMP logs forthe NAS file server and, if possible, correct the cause ofthe errors 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 destinationin 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 a configurationproblem with the policy. Either assign a newmanagement 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.



User response: This message indicates a configurationproblem with the policy. Either assign a newmanagement 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.

ANR1111E Command: An incorrect message number,message number, was specified.

Explanation: A MSGSTACKTRACE ENABLE orMSGSTACKTRACE DISABLE command has beenentered that specifies an invalid message number.Messages must be between 3 and 8 digits. No lettersare allowed on message numbers.


User response: Reissue the command with a validmessage number.

ANR1112W Command: No table of contentsdestination storage pool available forbackup set for node Node name (datatype data type). The table of contentswill not be created.




System action: The operation continues because TOCcreation is preferred, but not required. A TOC will notbe created.

User response: This message indicates a configurationproblem with the policy. Either assign a newmanagement class with appropriate attributes, orcorrect the assigned management class by setting theTOC destination in the backup copy group andactivating the changed policy.

ANR1113E Command: No table of contentsdestination storage pool available forbackup set for node Node name (datatype data type). The backup set will notbe generated.



User response: This message indicates a configurationproblem with the policy. Either assign a newmanagement 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.

ANR1114E Command: No nodes or data types areeligible for a backup set operation.

Explanation: None of the specified nodes or datatypes are eligible to be included in the backup set forthe GENERATE BACKUPSET or DEFINE BACKUPSETcommand.


User response: Check previous messages for problemdetermination information.

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.

User response: Wait for the server to retry themigration.

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.



ANR1118I Command: Table of contents successfullygenerated for node Node name, backupset backup set name.

Explanation: You requested a table of contents to begenerated for the specified backup set and data type.The table of contents was successfully generated.



ANR1119W Command: Table of contents alreadyexists for node Node name, backup setbackup set name (data type data type). Thetable of contents will not be created.

Explanation: You requested a table of contents to begenerated for the specified backup set and data type,but the table of contents already exists.

System action: The server will not generate a table ofcontents for this backup set and data type.

User response: If the specified backup set name anddata type are not correct, re-issue the command withthe correct parameters.

ANR1120W Migration is ended for volume volumename. The process is canceled.

Explanation: During migration for the indicatedvolume, the process performing the migration has beencanceled.

System action: The migration process stops. If other



migration processes are running, these processes willcontinue migration.


ANR1121E Migration is ended for volume volumename - storage. Media is inaccessible.

Explanation: During migration for the indicatedvolume a required volume cannot be mounted.

System action: Migration of the volume stops. If othermigration processes are running, these processes willcontinue migration.

User response: One possible cause for this failure isthat the access state for the target volume or storagepool for this operation is not set to READWRITE.Check the access state for the requested output volumeand storage pool and ensure they are set toACCESS=READWRITE.

ANR1122E Migration is ended for volume volumename. An insufficient number of mountpoints are available for removablemedia.

Explanation: During migration for the indicatedvolume the server could not allocate sufficient mountpoints for the volumes required.



ANR1123E Migration is ended for volume volumename. Excessive read errors wereencountered.

Explanation: During migration for the indicatedvolume, read errors occurred that prevent the migrationfrom continuing.


User response: If possible, correct the cause of theread errors.

ANR1124E Migration is ended for volume volumename. Excessive write errors wereencountered.

Explanation: During migration for the indicatedvolume, write errors occurred that prevent themigration from continuing.


User response: If possible, correct the cause of thewrite errors.

ANR1125E Migration is ended for volume volumename. Data transfer is interrupted.

Explanation: During migration for the indicatedvolume a data transfer operation was interrupted andcould not be continued.



ANR1126E Migration is ended for volume volumename. There is insufficient space insubordinate storage 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, or the next storage pool is not defined.


User response: Ensure that the next storage pool isdefined, and make more space available in the nextstorage pool. Use the UPDATE STGPOOL command tochange the next storage pool to one with more space.

ANR1127E Migration is ended for volume volumename. - The server is unable to movefiles to subordinate storage poolsbecause the files are too large.

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 STGPOOL commandto change the next storage pool maximum file size or tochange the next storage pool target.

ANR1128E Migration is ended for volume volumename. Sufficient recovery log space isnot available.

Explanation: During migration for the indicatedvolume, the server runs out of recovery log space.

System action: Migration stops.




ANR1129E Migration is ended for volume volumename. Sufficient database space is notavailable.

Explanation: During migration for the indicatedvolume pool, the server runs out of database space.



ANR1130E Migration is ended for volume volumename. There is a lock conflict.

Explanation: During migration for the indicatedvolume, the server needs to obtain a lock that is notavailable.


User response: Wait for the server to try the migrationagain.

ANR1131E Migration is ended for volume volumename. A thread resource is not available.

Explanation: During migration for the indicatedvolume, the server cannot start a thread for themigration process.


User response: Wait for the server to try the migrationagain. If the error persists, it might indicate a shortageof server memory.

ANR1132E Migration is ended for volume volumename. Sufficient memory is notavailable.

Explanation: During migration for the indicatedvolume, there is not enough server memory available.



ANR1133E Migration is ended for volume volumename. An internal server error isdetected.

Explanation: During migration for the indicatedvolume, the server encounters an internal error.



ANR1134E Migration is ended for storage poolstorage pool name. There is an insufficientnumber of mount points available forremovable media.

Explanation: During migration for the indicatedstorage pool the server could not allocate sufficientmount points in the next storage pool.



ANR1135E Migration is ended for volume volumename. The transaction is ended.

Explanation: During migration for the indicatedvolume, the server detected an error while attemptingto commit a transaction.



ANR1136W Operation process process ID completed -There is no data to process for thedifferential backup of NAS node nodename, file space file space.

Explanation: The NAS file server reported zero bytesstored at the conclusion of an NDMP backup of thespecified file space. The command ends withoutupdating the server's database.



ANR1137E Operation process process ID terminated -object excluded by size in destinationstorage pool and all successor pools.

Explanation: During the indicated operation, the sizeof a file sent from the client node is larger than thatallowed in the destination storage pool. No successorstorage pools can accept the large file.


User response: Increase the maximum file size for oneor more of the storage pools in the storage hierarchy toaccommodate the file. An authorized administrator canincrease the MAXSIZE parameter by issuing theUPDATE STGPOOL command.



ANR1139E The command name command failedbecause some data was missing.

Explanation: An attempt to gather database statisticsfrom the database manager failed. This failure canoccur if either of these conditions is met:

v The buffer pool monitor switch(DFT_MON_BUFPOOL) has been set to 'OFF.' Thebuffer pool monitor switch controls the collection ofdatabase statistics.

v The file systems or drives are in a remote network.There might be a network problem causing theserver fail to collect the statistics of those volumes.

System action: The command fails, and the serveroperation continues.

User response: Take one of the following actions, andthen try running the QUERY DBSPACE commandagain:

v Stop and restart the server.

v Set the buffer pool monitor switch to 'ON' using thisDB2 command: 'db2 update dbm cfg usingDFT_MON_BUFPOOL ON'.

v If you cannot obtain drive or file system statistics byrunning operating system commands, fix theproblem, then try running the command again.

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 or the access forthe storage pool is either unavailable or readonly.


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.

System action: The server ends the MOVE DATA orMOVE NODEDATA command.

User response: Use the UPDATE STGPOOL commandto change the next storage pool maximum file size or tochange the next storage pool target, and then reissuethe MOVE DATA or MOVE NODEDATA 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, the serverwas unable to obtain the volume specified because alock was not available or a restartable restore is activefor data on the volume and has it locked. .


User response: Check for restartable restores byissuing the QUERY RESTORE command. If the volumespecified contains any data from the node and filespaceidentifed by the QUERY RESTORE command, theMOVE DATA command will fail. The restartablerestores must complete or be cancelled before theMOVE DATA command can succeed.

If the volume does not contain data from the node andfilespace identified by the QUERY RESTORE command,the 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. Ifthe 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 the



indicated 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 The move process is skipping adamaged file on volume volume name:Node node name, Type file type, File spacefilespace name, File name file name.

Explanation: During the move process, 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 anerror was detected for some other file within theaggregate.

System action: The damaged file is not moved.

User response: Perform the following actions:

v Audit the indicated volume with FIX=NO to verifythat the file is damaged. The audit will reset the filestatus if the file is found to be undamaged duringthe audit. If the file is part of an aggregate, the auditwill reset the aggregate status if the entire aggregateis found to be undamaged.

v If this volume is in a primary storage pool that haspreviously been backed up to a copy storage pool,attempt to restore damaged files by using theRESTORE STGPOOL 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.

The server might not move some files if the storagepool is collocated and the volume being moved orreclaimed contains files that require different outputvolumes. The server will skip these files and nomessages are issued identifying the skipped files. Thefiles are skipped to honor the collocation attribute ofthe storage pool.

If the files in the storage pool are deduplicated, theycould be skipped due to the unavailability of an on-sitecopy. This can occur if the file has been logicallydeleted from all other storage pools due to either policyretention settings, or explicit deletion, but must remain



in the offsite storage pool due to deduplicationdependencies.


User response: Check for messages that indicate whyfiles 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. If thestorage pool is deduplicated and all primary storagepool volumes are available, this is the recommendedsolution.

v Make the primary volumes available and reissue aMOVE DATA command to reclaim the volume.

v Delete the files by using the DELETE VOLUMEcommand.

If the server is skipping files to honor the collocationattribute of the storage pool, run the MOVE DATAcommand, or wait until reclamation runs again. Ineither case, the server will move files to the appropriateoutput volumes until the volume being moved orreclaimed is empty. It might take more than oneattempt to totally empty the volume.

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 aprimary 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 the

server. 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 volumevolume name cannot copy damaged file instorage pool storage pool name: Node nodename, 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 the



RESTORE 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 process willtry to find another copy of the file in a copy storagepool. 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. If you received this message due to aMOVE DATA operation, reissue the MOVE DATAcommand after the restore operation has completed inorder to move any remaining files.

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 totallyreclaimed. 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.

ANR1176I Moving data for collocation set setnumber of total sets on volume volumename.

Explanation: As a result of a move operations, such asMOVE DATA, MOVE NODEDATA, migration, orreclamation, the server is moving data from the volumeindicated to new volumes. This message shows thetotal sets of data on the volume to be processed.Depending upon the collocation setting of thedestination storage pool, a set can be file spaces thatbelong to the same collocation group, file spaces for anode, or a single filespace.



ANR1178I Copying active files from primarystorage pool primary pool name to activedata pool active data pool name started asprocess process ID.

Explanation: A process has been started to copy activedata from a primary storage pool to the indicatedactive data.

System action: For every noncached, active file in theprimary pool, a copy is made in the active data pool, ifa copy of that file does not already exist.


ANR1179I Preview of copying active files fromprimary storage pool primary pool name toactive data pool active data pool namestarted as process process ID.

Explanation: A preview process has been started to

copy active data from a primary storage pool to theindicated active data pool.

System action: Preview information about the COPYACTIVEDATA operation is collected and displayed, butfiles are not copied.


ANR1181E Diagnostic(ID): 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.


ANR1182I Removable volume volume name isrequired for a restore request fromsession session id.

Explanation: A restore request will need a removablevolume. This message is issued as soon as the serverdetermines that the volume will be needed. A mountrequest will be made when the volume is actuallyneeded for processing. When the first passdetermination of needed volumes is complete, messageANR1183I will be issued. However, it is possible thatadditional volumes will be needed later, as indicated inthe explanation for message ANR1183I. This message isnot issued for DISK device class volumes nor is itissued for FILE device class volumes.

System action: The server continues processing.


ANR1183I Initial determination of removablevolumes required for a restore requestfrom session session id is complete.Additional volumes may still berequired.

Explanation: The first pass determination of neededvolumes is complete for the indicated restore session. Itis possible that additional volumes will be needed asindividual objects are restored. This can happen for avariety of reasons. Examples of such reasons include: 1.An object spanning from one volume to another, wherethe second volume is not needed for any other objectsduring this restore session. 2. An object is found to bedamaged and a copy storage pool volume is needed tocomplete the restore. 3. A volume is unavailable and acopy storage pool volume is needed to complete therestore.



System action: The server continues processing.

User response: Respond to any mount request for anyadditional volumes.

ANR1184I Copy active data process process IDended for storage pool storage pool name.

Explanation: A COPY ACTIVEDATA process for thenamed primary storage pool has ended.



ANR1185I Copy active data process process IDterminated for storage pool storage poolname - process canceled.

Explanation: While copying active data from theindicated primary storage pool, a process performingthe operation has been canceled.

System action: If other copy active data processes areexecuting for the named storage pool, these processescontinue.


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.



ANR1189I Removable volume volume name isrequired for copying active data.

Explanation: During processing of a COPYACTIVEDATA command, the server determines that aremovable volume is required.

System action: Unless this is a preview process, theserver attempts to mount the removable volume.


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 are executingfor the named storage pool, these processes continue.


ANR1214I The backup of the primary pool nameprimary storage pool to the copy poolname copy storage pool is complete.Number of files backed up: number ofbacked up files. Number of bytes backedup: number of backed up bytes.



Deduplicated bytes backed up: number ofbacked up dedup bytes. Unreadable files:number of unreadable files. Unreadablebytes: number of unreadable bytes.

Explanation: Backup processing for the specifiedstorage pool ended with the displayed results.


User response: Examine previous messages todetermine whether all backup processes endedsuccessfully.

ANR1215I The backup preview of the primary poolname primary storage pool to the copypool name copy storage pool is complete.Number of files backed up: number ofbacked up files. Number of bytes backedup: number of backed up bytes. Number ofdeduplicated bytes backed up: number ofbacked up dedup bytes.

Explanation: Backup preview processing for thespecified storage pool ended with the displayed results.



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 stopped -insufficient number of mount pointsavailable for removable media.

Explanation: During backup processing, the servercould not allocate sufficient mount points for thevolumes required.


User response: If necessary, make more mount pointsavailable. To prevent sessions or processes from havingto wait for a mount point, increase the value of theMOUNTLIMIT parameter in the device-class definition.Set the value of the MOUNTLIMIT parameter highenough to allow all server processes using deduplicatedstorage pools to open the number of volumes specifiedby the NUMOPENVOLSALLOWED option.

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 storage poolpool name.

Explanation: During backup processing, the servercannot copy data to the specified copy or active-datastorage pool because not enough space is available inthe specified copy or active-data storage pool, or, theaccess for the copy or active-data storage pool is eitherunavailable or readonly.


User response: Make more space available in the copyor active-data storage pool and reissue the backupcommand, or reissue the backup command and specifyanother copy or active-data storage pool with morespace.

ANR1222E Command: Process process ID wasterminated because of insufficientrecovery log space.



User response: Monitor archive logs and active logs. Ifthe recovery log space is insufficient, monitor thearchive log space first. If the archive log space is full ornearly full, run a full database backup to removearchive logs and consider adding more disk space tothe archive log directory. If the archive log space is notfull and the active log space is full or nearly full,



update the value of the ACTIVELOGSIZE option in thedsmserv.opt file. Set the value of the ACTIVELOGSIZEoption to the new maximum size of the active log.

ANR1223E Command: Process process ID wasterminated because of insufficientdatabase space.

Explanation: During backup processing, the serverruns out of database space.

System action: The specified backup process ends.


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.



ANR1229W Volume volume name is inaccessibletherefore it cannot be backed up to acopy storage pool or copied to anactive-data storage pool.

Explanation: During storage pool backup or thecopying of active data, the contents of a volume cannotbe backed up or copied if one of the followingconditions exists:

v The volume is offline.

v The volume is in use by another process.

v The volume cannot 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: Take one of the following actions:

v If the volume is offline, issue the VARY ONLINEcommand for the indicated volume.

v If the access mode of the volume is unavailable, issuethe UPDATE VOLUME command to change theaccess mode to readwrite or readonly. If the accessmode of the volume is destroyed, verify with anadministrator whether the access mode should beupdated. If it should, issue the UPDATE VOLUMEcommand to change the access mode to readwrite orreadonly.

v If the volume is in use by another process, wait forthat process to complete, and then retry the BACKUPSTGPOOL command or the COPY ACTIVEDATAcommand.

v If the volume is not currently mountable, verify thatthe drive can mount the volume, and then retry theBACKUP STGPOOL command or the COPYACTIVEDATA 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 on selectedvolumes in the primary storage pool are restored.


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 The restore of the primary pool nameprimary storage pool is complete.Number of files restored: number ofrestored files. Number of bytes restored:number of restored bytes. Number ofdeduplicated bytes restored: number ofrestored dedup bytes. Number ofunreadable files: number of unreadablefiles. Number of unreadable bytes:number of unreadable bytes.

Explanation: Restore processing for the specifiedstorage pool ended with the displayed results.


User response: Examine previous messages todetermine whether all restore processes endedsuccessfully.

ANR1239I The restore preview of the primary poolname primary storage pool is complete.Number of files restored: number ofrestored files. Number of bytes restored:number of restored bytes. Number ofdeduplicated bytes restored: number ofrestored dedup bytes.



Explanation: Restore preview processing for thespecified storage pool ended with the displayed results.



ANR1240I The restore of volumes in the primarypool name primary storage pool iscomplete. Number of files restored:number of restored files. Number of bytesrestored: number of restored bytes. Numberof deduplicated bytes restored: number ofrestored dedup bytes. Number ofunreadable files: number of unreadablefiles. Number of unreadable bytes:number of unreadable bytes.

Explanation: Restore processing for volumes in thespecified storage pool ended with the displayed results.


User response: Examine previous messages todetermine whether all restore processes endedsuccessfully.

ANR1241I The restore preview of volumes in theprimary pool name primary storage pool iscomplete. Number of files restored:number of restored files. Number of bytesrestored: number of restored bytes. Numberof deduplicated bytes restored: number ofrestored dedup bytes.

Explanation: Restore preview processing for volumesin the specified storage pool ended with the displayedresults.



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.

User response: Verify that the copy and primarystorage pools and volumes being accessed are available.Check the ACCESS parameter for both of the storagepools and all related volumes to ensure the ACCESSstate is not preventing access.

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.



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.

v A restorable backup copy of the file exists, but is ona copy storage pool volume that cannot be accessedsince no drive path exists.


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=YES. The audit will verify whether or not the fileis damaged and perform one of the following actions:

v If the the file is found to be undamaged, the auditwill reset the file status. If the file is part of anaggregate, the audit will reset the aggregate status ifthe entire aggregate is found to be undamaged.

v If the file is found to be damaged and the file hadnot previously been backed up to a copy storagepool, the audit will delete the file.

v If the file is found to be damaged and the file haspreviously been backed up to a copy storage pool,the audit will report the file as damaged and youmust use the RESTORE STGPOOL command torecover the file.

ANR1258W Files on volume volume name needed formove data cannot be accessed - accessmode is "unavailable", "offsite", or"destroyed".

Explanation: During a move data operation, files on astorage pool volume cannot be copied because of thevolume's access mode. The server cannot move data ona volume that has an access mode of "unavailable","offsite", or "destroyed".

System action: The server continues move dataprocessing, but one or more files were not moved fromthe 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 or MOVE NODEDATA 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 command toexamine messages prior to this error to determine thecause 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 The process of moving node data fromthe storage pool name storage pool to thestorage pool name storage pool iscomplete. Number of files moved:number of moved files. Number of bytesmoved: number of moved bytes. Number ofdeduplicated bytes moved: number ofmoved dedup bytes. Number of unreadablefiles: number of unreadable files. Numberof unreadable bytes: number of unreadablebytes.

Explanation: The process of moving node data for thespecified storage pool ended with the displayed results.


User response: Examine previous messages todetermine whether all of the move node data processesended successfully.

ANR1293E Space-reclamation process processnumber: Fifty files in offsite storage-poolvolumes do not have copies inaccessible storage pools.

Explanation: More files in offsite storage-pool volumesmight exist for which copies cannot be located. If this isthe case, message ANR1173E is not displayed.

System action: The IBM Spectrum Protect server skipsfiles that do not have copies. The server does not movethe files from offsite storage-pool volumes.

User response: To view detailed information about allthe files that are skipped during the space-reclamationprocess, enable trace AFUNAVAILABLE and look in thetrace log.

ANR1294I Process process ID skipped skipped filesfiles on volume volume name because ofdeduplicated files.

Explanation: While moving or copying files from thesequential FILE volume shown to a DISK storage pool,files that had deduplicated extents were encountered.As a result, the files were skipped.

The sequential FILE volume shown is assigned to astorage pool that has deduplication enabled or at onetime had deduplication enabled. Some of the files onthe volume have deduplicated extents and can not bemoved or copied to the DISK storage pool.

System action: The server moves or copies all filesfrom the volume that do not have deduplicated extents.Those files that do have deduplicated extents areskipped.

User response: If attempting a MOVEDATA/NODEDATA to move the files withdeduplicated extents to the DISK storage pool, onemust first perform a MOVE DATA/NODEDATA toanother sequential storage pool that does not havededuplication enabled. This move will restore thededuplicated files to their complete state in the targetstorage pool. Once all deduplicated data has beenmoved, perform a MOVE DATA or MOVENODEDATA to the DISK storage pool from the targetstorage pool. It is recommended to use a FILE storagepool as the target.

If attempting a RESTORE STGPOOL/VOLUME to copythe files with deduplicated extents, one must firstperform a RESTORE STGPOOL/VOLUME to anothersequential storage pool that does not havededuplication enabled. This will restore thededuplicated files to their complete state in the targetstorage pool. Once all deduplicated data has beenrestored, perform a MOVE DATA/NODEDATA to theDISK storage pool from the target storage pool. It is



recommended to use a FILE storage pool as the target.

ANR1295W An attempt to set end reclamation datefor WORM volume volume name to endreclamation date failed. end reclamationdate set to SnapLock retention date.

Explanation: IBM Spectrum Protect computes andattempts to set the end reclamation date for a volumebased on the RETMIN and RETVER COPYGROUPattributes. When setting the end reclamation date forthe named volume, the Network Appliance SnapLockfile system was unable to fulfil the request. It was,however, able to set the date to the Snaplock retentiondate, which is farther in the future than the requesteddate. This is probably due to how the SnapLock NASfile server's retention date is configured.

This warning message is only issued once per volume,when this condition is detected when data is firstplaced on the volume.


User response: Verify that the IBM Spectrum ProtectCOPYGROUP attributes and the retention settings ofthe Network Appliance file system are consistent withyour requirements for WORM volume storage.

ANR1296W Storage pool storage pool name does notcontain WORM FILE volumes.

Explanation: This message might be issued during thedefinition or updating of a storage pool, or duringBACKUP or RESTORE STGPOOL commands, or inother such situations when it is determined that dataon WORM volumes might be moved to other media. Itnames a storage pool that does not contain WORMFILE volumes.

When it is issued during the DEFINE and UPDATESTGPOOL commands, it indicates that the storage poolbeing defined or updated is being configured withWORM FILE volumes (Reclamationtype is SnapLock),but other storage pools being specified on the storagepool definition (for example, the Next or Reclaim orCopy storage pool parameters) do not contain WORMFILE volumes (Reclamationtype is Threshold). Suchconfigurations might cause data on those WORM FILEvolumes to be moved to a storage pool that does notsupport WORM FILE volumes.

For other situations, this message might be issuedwhen there will be a movement of data from a storagepool with WORM FILE volumes (Reclamationtype isSnapLock) to a storage pool that does not have WORMFILE volumes (Reclamationtype is Threshold).

The server allows this type of movement, but thecustomer needs to be aware that if data is moved froma WORM FILE volume to another type of media, thedata may no longer be protected from inadvertent ormalicious deletion. In addition, if this data is onWORM volumes to meet data retention and protection

requirements for certain legal purposes and is movedto other media, the data might no longer meet thoserequirements.

System action: The command continues.

User response: Verify that the storage pools beingused meet your requirements for data protection andretention.

ANR1297E Storage pools withRECLAMATIONTYPE=SNAPLOCK canonly be defined on servers with archivedata retention protection enabled.

Explanation: Defining storage pools withRECLAMATION=SNAPLOCK is only supported on aserver with archive data protection enabled.

System action: The define storage pool commandfails.

User response: Define the storage pool withRECLAMATIONTYPE=THRESHOLD on this server. Orelse enable archive data retention protection on thisserver, and try the command again.

ANR1298W The server encountered an error inattempting to delete an object in aCentera storage device. The Centerarepresentation of the name is Centeraobject string. The server was keepingtrack of the object in volume id volumeid. The return code received was returncode.

Explanation: The server failed to delete an object in aCentera storage device after server records concerningthe object were deleted. The object is no longeraccessible through the server. The object continues tooccupy space in the Centera storage device. The returncode that is returned is either from the server interfaceto Centera services, or it can be directly from theCentera device.

System action: The server continues operation, andthe object is logically deleted within the server, butcontinues to occupy space in the Centera device.

User response: The server can continue to operate inspite of this error. Centera service can be required if thevolume of unpurged objects becomes a problem.

ANR1299E The server encountered an invalidstorage format while attempting apartial object retrieve for object seg_id.

Explanation: A partial object retrieve was attemptedon a file that was stored in a format that does notsupport partial object retrieves.

System action: The transaction ends and the retrieverequest fails.



User response: Try the retrieve again, using a regularor full retrieve instead of a partial object retrieve.

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 Incorrect bytes read bytes read for offsetoffset.

Explanation: The read operation fails. Check previousmessages in the activity log for a message that showsan I/O error or warnings.



ANR1309W Shred value zero for storage pool storagepool name may render deleted data nonshreddable.

Explanation: This message is issued during the defineor update of a storage pool when a SHRED value ofzero has been found with a storage pool in the storagepool hierachy.

The server allows this type of operation, but theadministrator needs to be aware that if data is stored ormoved to the affected storage pool, the data cannot beshredded after deletion.

When it is issued during the DEFINE command, itindicates that the storage pool definition is beingconfigured with a non zero SHRED value, howeverother storage pools being specified on the definition(for example, the Next or Reclaim or Copy storage poolparameters) have a SHRED value of zero.

When issued during the UPDATE command, itindicates the specified storage pool may be altering the

SHRED value from non zero to zero or that thespecified Copy, Next or Reclaim storage pool has aSHRED value zero. Such configurations may result indata to become non shreddable if data from theprimary random access storage pool is moved to one ofthe storage pools with a zero SHRED value.


User response: Verify that the storage pools beingused meet your requirements for data protection.

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.



ANR1317E Command: Storage pool storage pool nameis not a shreddable pool.

Explanation: The command indicated specifies thename of a storage pool which is not a shreddable pool.The command syntax requires thatSHREDTONOSHRED=YES be specified when data ismoved from a shreddable storage pool to a nonshreddable storage pool.


User response: Reissue the command withSHREDTONOSHRED=YES.

ANR1318I The process of copying active data fromthe primary pool name primary storagepool to the active data pool name activedata pool is complete. Number ofcopied files: number of copied files.Number of copied bytes: number of copiedbytes. Number of copied deduplicatedbytes: number of copied dedup bytes.Number of unreadable files: number ofunreadable files. Number of unreadablebytes: number of unreadable bytes.

Explanation: The process of copying active data for

the specified storage pool ended with the displayedresults.


User response: Examine previous messages todetermine whether all copy active data processes endedsuccessfully.

ANR1319I The preview of copying active data fromthe primary pool name primary storagepool to the active data pool name activedata pool is complete. Number of filescopied: number of copied files. Number ofcopied bytes: number of copied bytes.Number of copied deduplicated bytes:number of copied dedup bytes.

Explanation: The preview of copy active dataprocessing for the specified storage pool ended withthe displayed results.



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.

ANR1322W The shredding mode is already shreddingmode.

Explanation: A SETOPT SHREDDING command wasissued to change the shredding mode, but the newmode is the same as the existing mode.

System action: The shredding mode is unchanged.




ANR1323E Command SHRED DATA is invalid forautomatic shredding mode.

Explanation: A SHRED DATA command was issuedwhile shredding mode is set to Automatic.


User response: Set the shredding mode to Manual orwait for automatic shredding to shred the data.

ANR1324E Process process number is already runninga SHRED DATA.

Explanation: A SHRED DATA command was issuedwhile another SHRED DATA process is still executing.Only a single SHRED DATA process is allowed at anytime.


User response: Wait for the current SHRED DATAprocess to finish, and issue the command again.

ANR1325W Shreddable object for node name:type=type, file space=filespace name,object=object name skipped.

Explanation: The object for node name, identified bytype, file space and object name was found in ashreddable storage pool and is skipped, however theEXPORT continues.

System action: The server process continues exportingand will skip all shreddable objects.

User response: Specify theALLOWSHREDDABLE=YES parameter when exportingobjects from a shreddable storage pool. Using thisoption forces EXPORT to process all objects, includingobjects found in shreddable storage pools.

ANR1326I Shredding process complete aftershredding shredded bytes bytes andskipping skipped bytes bytes.

Explanation: The shredding process has completed.The amount of data successfully shredded and theamount of data that was skipped are reported.

System action: Server operation continues. If any datawas skipped, the server will attempt to shred it thenext time shredding runs.


ANR1327I Automatic shredding stopped. Totalbytes shredded was shredded bytes andtotal bytes skipped was skipped bytesbytes.

Explanation: The automatic shredding process hasended. The amount of data successfully shredded andskipped during automatic shredding is reported.

System action: Server operation continues. If any datawas skipped, the server will attempt to shred it thenext time shredding runs.


ANR1328E The server has detected an attempt torestore or retrieve a shredded object.

Explanation: An attempt was made to retrieve orrestore an object which has already been shredded. Thiscan happen if your datasbase was recently restored,and data which existed at the time of the databasebackup has since been erased and shredded.


User response: Perform an AUDIT VOLUMEoperation on the volume containing the shredded data.

ANR1329I Automatic shredding started.

Explanation: The automatic shredding of deletedobjects is starting.



ANR1330E The server has detected possiblecorruption in an object that is beingrestored or moved. The actual values forthe incorrect 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 was detected. Thismight indicate corruption within the object that is beingrestored or moved.

System action: The object is not restored or moved.

User response: Retry the failing operation. If theoperation fails again, review additional informationthat is available for this message: Search for"ANR1330E" in the product information(http://www.ibm.com/support/knowledgecenter/SSEQVQ/).

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.



ANR1332W Shredding cancelled prior tocompletion. Total bytes shredded wasshredded bytes and total bytes skippedwas skipped bytes bytes.

Explanation: The shredding process was cancelledeither because the specified duration has elapsed, orbecause the CANCEL PROCESS command was used tocancel it. The amount of data successfully shreddedand skipped is reported.

System action: Server operation continues. If any datawas skipped or not processed, the server will attemptto shred it the next time shredding runs.


ANR1335E command: Database database name cannotbe the target of an upgrade because it isnot empty.

Explanation: The DSMSERV INSERTDB operationcannot insert data into the specified database becausethe database already contains data from another server.

Possible causes for this error include:

v The wrong database was specified in theDATABASEALIAS option in the server's options file.

v The database was formatted using the DSMSERVFORMAT command instead of the DSMSERVLOADFORMAT command.

System action: The DSMSERV INSERTDB commandterminates.

User response: Verify that the correct database nameis specified in the server's options file. If the correctdatabase is specified, and the database is not in use bya different IBM Spectrum Protect server, then drop thedatabase and recreate it using the DSMSERVLOADFORMAT command before rerunning theDSMSERV INSERTDB command.

ANR1336I command: Ready for connections fromthe source server. Remaining time:remaining time

Explanation: The command has completed itsinitialization, and is ready to begin receiving databaseinformation from the source server.

System action: The command will continue to waituntil the source server establishes a server-to-serverconnection and begins sending database information, oruntil the specified amount of time has passed.

User response: Initiate a session from the sourceserver.

ANR1337I A trigger type trigger has been removed.

Explanation: The DSMSERV INSERTDB commandencountered a database backup trigger, a databasespace trigger, or recovery log space trigger, andremoved it as part of the database upgrade process.

System action: The trigger is deleted from theupgraded database.


ANR1338E One or more constraint violations weredetected. Examine log file log file namefor details.

Explanation: The DSMSERV INSERTDB commandencountered one or more instances where data beinginserted into the database violated a constraint or wasotherwise invalid. Information about the error, alongwith the data that caused the error, was logged in thespecified log file.

System action: The offending row was not insertedinto the database. Instead, the contents of the row werewritten to the specified log file along with additionalinformation about the specific error.

User response: Because some data was not insertedinto the database, the database is in an inconsistentstate. The server should not be started until theproblem is corrected.

Contact your service representative for assistance incorrecting the problem. You may be directed toexamine the log file, and in some cases, correct theerroneous data and insert it into the database.However, due to the sensitive nature of the database,you should never attempt to do this unless directed todo so by your service representative.

ANR1339W Session session id underestimated a sizeallocation request - additional spaceMBmore space was allocated to allow theoperation to continue.

Explanation: This session required additional spacemegabytes of space in order for the operation tocontinue. The client is responsible for accuratelyreporting the size of a file to be stored to the server.The size reported by the client is used to reserve spacein the DISK storage pool to store this file. If this size isunderestimated, the server may not be able to allocatethe additional space needed for this file to continuewith this operation.

System action: None, the operation was able tocontinue.

User response: The installed version of the client forthis node should be evaluated. In most cases, if a clienthas underestimated the sizes of files reported to theserver, this may have been corrected in a newer versionof the client. If this is an application using the IBM



Spectrum Protect API that is not an IBM product,contact the vendor for the application to have thiscorrected.

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 the volume from server storage.

Explanation: A volume that was full and is nowempty cannot be reused by the server because thevolume is on WORM media.

System action: The volume is in a state where theaccess mode is READONLY, the status is FULL, and thepercent utilized is 0. The server considers the volumeto be empty when calculating the occupancy andutilization fields for the volume.

User response: The volume remains in the library andin the storage pool, with the attributes described in theSystem Action section. If this is not a volume in aRECLAMATIONTYPE=SNAPLOCK storage pool, youmay remove the volume by performing these steps:

1. Remove the volume from the storage pool byissuing the DELETE VOLUME command.

2. Remove the volume from the library by issuing theCHECKOUT LIBVOLUME command.

If this is a volume in aRECLAMATIONTYPE=SNAPLOCK storage pool, youcannot remove the volume. Rather, allow IBMSpectrum Protect reclamation processing to delete thevolume.

ANR1345I Volume volume name cannot be reusedby other applications and will remain inthe storage pool.

Explanation: A WORM (write-once-read-many)volume that has been written by the server cannot beused by other applications. This volume was not fulland has been emptied due to expiration, deletecommands, or transaction failure.

System action: The volume remains in the storagepool to be reused by IBM Spectrum Protect, unless it ismanually deleted. The remaining space on the volumewill be used in the normal course of server operation.

User response: If the volume is no longer to be used,manually delete it from the storage pool.

ANR1346E 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.





ANR1347E Export/import command: Processingterminated abnormally - error accessingdata storage.

Explanation: The server encountered an internal errorin accessing data storage while executing an import orexport operation.



ANR1348I Export Operation information for numberobjects has been deleted.

Explanation: A background server process deletedexport operation information for number files from theserver database. This process started duringinitialization to remove any unneeded exportinformation.

System action: The actual backup or archive objectswere not deleted. Only information used to sort theseobjects during the previous export operation wasdeleted.


ANR1349E Error code during deletion of exportoperation information for numberobjects.

Explanation: A background server processencountered an internal error after deleting exportoperation information for number files from the serverdatabase. This process started during initialization toremove any sorting information which is left over fromprevious export operations.

System action: The backup or archive objects were notdeleted. Only the information used to sort these objectsduring the previous export operation was deleted. Thebackground process was terminated before all sortinginformation was deleted. The system will not performfurther export processing of file data until this problemis 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.

ANR1350E Command: Invalid time range specified.FROM: fromdate fromtime TO: todatetotime.

Explanation: A command was issued that specifies aninvalid FROM and TO date or time range. This errorcan occur when the FROM date or time is not beforethe TO date or time.


User response: Reissue the command with a validdate or time range.

ANR1351I Export/import command: Processingsuspended with status status.

Explanation: The background process to service thecommand command was suspended with a SUSPENDcommand.

System action: Processing for the command commandstops. Statistics on the number and type of objectsmoved, together with the total number of bytes copied,are displayed on the server console following thismessage.


ANR1352I Command started by administrator name asprocess process ID has been suspended.

Explanation: The background process to service thecommand command by administrator administrator namesuspended processing.

System action: The specified process suspends, andserver operations continue.


ANR1353I Command: Cannot cancel the EXPORToperation with export identifier exportId.The operation is currently active.

Explanation: The server cannot cancel the exportoperation specified in the CANCEL EXPORT commandbecause it is currently running as an active process.


User response: Only suspended EXPORT operationsmay be cancelled by issuing the CANCEL EXPORTcommand. Issue the QUERY EXPORT command toidentify the current state of the EXPORT operation.

ANR1354I command name: The EXPORTIDentifierparameter is not supported when theFILEDATA parameter is set to NONE.Running as non-restartable export.

Explanation: The EXPORTIDentifier parameter isignored while the command continues.



System action: The command runs and serveroperations continue.


ANR1355I command name: An export operationalready exists with theEXPORTIDentifier export ID.

Explanation: The export command fails.


User response: Reenter the export command with anunused export identifier.

ANR1356I Command: Cannot restart the EXPORToperation with export identifier exportId.The operation is currently active.

Explanation: The server cannot restart the exportoperation specified in the RESTART EXPORT commandbecause the export operation is currently running as anactive process.


User response: Only suspended Export operationsmay be restarted using RESTART EXPORT command.Issue the QUERY EXPORT command to identify thecurrent state the EXPORT operation.

ANR1357I command name: The EXPORTIDentifierparameter is not supported when thePREVIEWIMPORT parameter isspecified. Running as non-restartableexport.

Explanation: The EXPORTIDentifier parameter isignored while the command continues.

System action: The command runs and serveroperations continue.


ANR1358I Export Identifier: Export Id

Explanation: This is a restartable export operation thatcan be referenced by the displayed EXPORTIDentifierparameter.

System action: Server operations continue


ANR1359I Suspend in progress

Explanation: The server-to-server export operation hasbeen suspended and will stop when resources havebeen freed for the background process. This messagemay be displayed in response to a QUERY PROCESScommand for an export operation.



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 the properexport 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.

ANR1371I Command: The export operation withexport identifier Export Id has beendeleted.

Explanation: The suspended server-to-server exportoperation has been deleted. This operation may nolonger be restarted. This message is be displayed inresponse to a CANCEL EXPORT command.



ANR1372I Suspend export request accepted forexport process with export IdentifierExport Id ( process process ID).

Explanation: A SUSPEND EXPORT command hasbeen entered for the specified server-to-server exportprocess. Some processes will experience a delay beforethey suspend. This delay may be lengthy for processesthat involve remote data movement.



ANR1373I Process process Id for Command has beensuspended on source server.

Explanation: The background import process has beensuspended on the source server.



ANR1374I Process process Id for Command has beencanceled on source server.

Explanation: The background import process has beencanceled on the source server.





ANR1375I Command: Cannot suspend the exportoperation export Id because the currentstate is not valid.

Explanation: This message is returned in response to aSUSPEND EXPORT command which specified anexport operation that is not currently suspendible. Theexport operation may not be running, or it may be inthe process of being suspended.

System action: The specified command fails, andserver operation continues.


ANR1376I Analyst authority has been revoked foradministrator administrator name.

Explanation: The DSMSERV INSERTDB commandencountered an administrator with analyst authority,and revoked the authority as part of the databaseupgrade process.

System action: The analyst authority is revoked.


ANR1377I Analyst authority has been revoked foradministrator id administrator id.

Explanation: The DSMSERV INSERTDB commandencountered an administrator with analyst authority,and revoked the authority as part of the databaseupgrade process.

System action: The analyst authority is revoked.


ANR1378I command: No connection was receivedafter session wait time minutes.

Explanation: The command waited the specifiedamunt of time for the source server to connect, but noconnection was established.

System action: The command terminates.

User response: Rerun the command. Either specify alarger value for the SESSWAIT parameter, or establish aconnection from the source server more quickly.

ANR1379I command: Read bytes bytes and inserteddatabase entries database entries in elapsedtime (read rate megabytes per hour).

Explanation: The command read the indicatednumber of bytes, and wrote the indicated number ofdatabase entries.



ANR1380I The buffer pool monitor switch isenabled.

Explanation: The server has turned the buffer poolmonitor switch to 'ON'.

System action: Server continues processing.


ANR1381W The buffer pool monitor switch isdisabled 'OFF'. A manual update mightbe needed.

Explanation: The server failed to turn the buffer poolmonitor switch to 'ON'.


User response: No action is required at this time. Buta manual update might be needed before executingcommand 'Q DBS' or 'Q DB F=D'. Refer to message1139I.

ANR1382E The server failed with error code returncode when attempting to update adatabase parameter.

Explanation: Cannot update a database parameterwith the value specified in the server options file.

System action: The server initialization fails.

User response: Examine the server messages issuedprior to this message to determine the source of theerror. Contact your service representative for further

ANR1383I Memory usage by the database manageris limited to instance memory in MBMB.

Explanation: The memory dedicated to the databasemanager was set successfully.



ANR1384E The update to set memory used by IBMSpectrum Protect server database toinstance memory in MBMB failed.

Explanation: Attempt to set memory dedicated to IBMSpectrum Protect server database failed.


User response: Collect all messages prior to this oneand contact your service representative for furtherassistance.



ANR1385E The database name is either invalid ormissing in the server option file.

Explanation: While attempting to format a database,the IBM Spectrum Protect server has found that thedatabase name is either invalid or missing.

System action: Server format stops.

User response: Before reissuing the command toformat the database, check the following items:

v Ensure that the server options file has a valid namefor for IBM Spectrum Protect server database. Thedatabase name is specified with theDATABASEALIAS option. The database name is aunique character string containing from one to eightletters, numbers, or keyboard characters. The namecan contain any of the following characters: a-z, A-Z,0-9, @, #, and $.


ANR1386I Beginning schema verification for thedatabase insert process.

Explanation: The database insert process is verifyingthat the database schema is correct.

System action: The server will verify the correctnessof the database schema before inserting any databaserecords.


ANR1387I Schema verification for the databaseinsert process has completed.

Explanation: The database insert process hassuccessfully verified that the database schema iscorrect.

System action: If CHECKSCHEMA=YES was specifiedthen the database insert process will begin insertingrecords into the database.


ANR1388E Schema verification for the databaseinsert process detected inconsistencies.

Explanation: Inconsistencies were detected duringdatabase schema verification.

System action: The database insert process terminates.


ANR1389I The database insert process isterminating becauseCHECKSCHEMA=ONLY was specified.

Explanation: The database insert process isterminating after verifying the database schemabecause the CHECKSCHEMA=ONLY parameter wasspecified.


User response: Rerun the command withoutspecifying the CHECKSCHEMA=ONLY parameter.

ANR1390E Column source column name (sourcecolumn number) in legacy table sourcetable name is mapped to an invalidcolumn (target column number) in targettable target table name (maximum columnis table size).

Explanation: The database insert process has detecteda discrepency while verifying the data base schema. Acolumn in the source database table was mapped to aninvalid column in the target table. The target columnnumber is higher than the number of columns in thetarget table.



ANR1391E Column source column name (sourcecolumn number) in legacy table sourcetable name is mapped to the wrongcolumn target column name (target columnnumber) in target table target table name.

Explanation: The database insert process has detecteda discrepency while verifying the data base schema. Acolumn in the source database table was mapped to thewrong column in the target table.



ANR1392E Column target column name (target columnnumber) in target table target table name isnot set by upgrade, but does not allowNULLs and has no default value.

Explanation: The database insert process has detecteda discrepency while verifying the data base schema. Acolumn in the target database table is not set, does nothave a default value and does not allow NULLs.





ANR1393I Memory usage by the database manageris set to AUTOMATIC.

Explanation: The memory dedicated to IBM SpectrumProtect server database was set to automaticsuccessfully.



ANR1394E The update to set memory used by IBMSpectrum Protect server database toAUTOMATIC failed.

Explanation: Attempt to set memory dedicated to IBMSpectrum Protect server database to automatic failed.


User response: Collect all messages prior to this oneand contact your service representative for furtherassistance.

ANR1395I Insertdb command: Process process number,database insert, has completed.

Explanation: The database insert process processnumber has completed.

System action: Database insert processing ends.


ANR1396E Insertdb command: Process process number,database insert, has completed witherrors.

Explanation: The database insert process processnumber has completed, but errors were encountered bythe process.

System action: Database insert processing ends.

User response: Review any messages that were issuedby the process, and take corrective action asappropriate.

ANR1397I Insertdb command: Found number ofdatabase objects database objects.

Explanation: This message indicates the total numberof database objects that were found during databaseinsert processing.



ANR1398I Insertdb command: Processed number ofdatabase objects database objects.

Explanation: This message indicates the total numberof database objects that were successfully processedduring database insert processing.



ANR1399I Insertdb command: Failed to processnumber of database objects databaseobjects.

Explanation: This message indicates the total numberof database objects that were not successfully processedduring database insert processing.



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.


User response: If the attempted mount occurs in alibrary sharing environment and the library managerwas recently recycled, try again in five minutes. In thiscase the library manager and library client need a fewminutes to reestablish communication and synchronizethe mounting information between the two servers.

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.


ANR1407W Scratch volume mount request denied -storage pool pool name has reachedmaxscratch limit.

Explanation: A scratch volume cannot be mountedbecause the storage pool has reached the maximumscratch volume limit allowed by the MAXSCRATCHparameter.

System action: A scratch volume is not mounted.

User response: Use the UPDATE STGPOOL poolnameMAXSCRATCH=xx command command to increase thenumber of scratch volumes allowed in the storage pool.

ANR1408I Insertdb command: PREVIEW=YES wasspecified. No data will be inserted intothe database.

Explanation: PREVIEW=YES was specified on theINSERTDB command. Database data will be read andchecked for errors, but no data will be written into thedatabase.



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 havebeen 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 isDESTROYED.

Explanation: At server startup, the status of theindicated volume is DESTROYED. This status canresult because the access mode was set to DESTROYEDby a storage administrator. This status can also resultbecause the server determined that the databaserecords associated with this volume are damaged andset the status of the volume to DESTROYED. If this isthe case, the server also issues an ANR1316E message.


User response: You can issue the RESTORE VOLUMEserver command to restore the volume if a storage poolbackup is available.

ANR1416I command: Read bytes bytes and inserteddatabase entries database entries in elapsedtime (read rate megabytes per hour).Checked database objects of database objectsdatabase objects.

Explanation: The command read the indicatednumber of bytes, and wrote the indicated number ofdatabase entries. The command has checked theintegrity of the indicated number of database tables.



ANR1417W Access mode for volume volume namenow set to "read-only" due to excessiveread error.

Explanation: Because of an numerous read errors on

the 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.



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 FROMTIMEparameter 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 is 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.

System action: The volume is not deleted.

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. Possible reasonsinclude, a MOVE MEDIA command was used to checkthe volume out of the library and the volume wassubsequently checked into the library using CHECKINLIBVOL without first running a MOVE MEDIAcommand to update the volume state back toMOUNTABLEINLIB state. If this should happen, theQUERY MEDIA will display the volume to be inMOUNTABLEINLIB state since QUERY MEDIA doesverify if the volume is actually in the library beforedisplaying the state of the volume.

System action: The volume is not deleted.

User response: The following steps may be used if thevolume is to be deleted:

1. Run CHECKOUT LIBVOL to check the affectedvolume out of the library, the REMOVE=NO optionmay be used to prevent actual volume movement

2. Run MOVE MEDIA * STG=*WHERESTATE=MOUNTABLENOTINLIBWHERESTATUS=EMPTY. When the volume ismoved by MOVE MEDIAWHERESTATE=MOUNTABLENOTINLIB, thescratch empty volume is deleted

3. Check the volume back into the library usingCHECKIN LIBVOL command

ANR1426I All legacy FILE volumes have beenmarked FULL.

Explanation: As part of the conversion of the databaseto IBM Spectrum Protect version 5.3, all existingnon-full volumes of devtype FILE have been markedFULL to keep them from being extended.

System action: All FILE volumes that were notalready FULL have been marked FULL and cannot beappended to.


ANR1427E No legacy FILE volumes were markedFULL.

Explanation: As part of the conversion of the databaseto IBM Spectrum Protect Version 5.3, all existingnon-full volumes of devtype FILE were attempted to bemade FULL. However, a database error prevented theconversion, and the status of these volumes remainsunchanged.

System action: The volumes are not marked FULL.

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. Contact yourservice representative for further assistance.

ANR1428W Shredding access denied for volumevolume name - volume is offline.

Explanation: An object on the indicated volumecannot be shredded because the volume is offline.

System action: The object is not shredded at this time.When the volume is put back online, another attemptwill be made to shred the object.

User response: Determine why the volume is offline,and, if possible, place the volume back online.



ANR1429E Transaction failed for Import process -invalid file space filespace name for nodenode name was detected.

Explanation: During import processing, the serverencounters an invalid file space name.

System action: This action usually occurs when theimport is operating on a file space that is currentlybeing deleted as a result of an administrative commandor client action. The server ends import operation.

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 importoperation again after this action has been taken.

ANR1430W Retrieval request denied for storagepool storage pool name due to the accessstate of the storage pool.

Explanation: An attempt was made to retrieve a filefrom the storage pool shown, but the access mode ofthe storage pool does not allow for retrieve requests.

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 mode forthe 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 may havebeen displayed prior to this message and correct anyproblems, 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 may havebeen displayed prior to this message and correct anyproblems, 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 may havebeen displayed prior to this message and correct anyproblems, if possible. Ensure that the defined deviceconfiguration files have been created. If you can startthe 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. Make sure that the serverhas proper 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 may havebeen displayed prior to this message to understandwhy the file could not be used. When you can start theserver again, you can refresh this file by using theBACKUP 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 havebeen 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 becomes available,restart the process that was cancelled. If the processwas a migration or reclamation process, it will beautomatically 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 group destinationstorage pool of the assigned management class has theappropriate NATIVE or NONBLOCK data format.

ANR1443W Process process ID terminated fromsession session id. A potentialdrive-contention deadlock was detected.

Explanation: See message.




ANR1444E No device configuration file is defined.

Explanation: No device configuration file is defined.Check DEVCONFIG option in server options file.

System action: The specified configuration parameteris skipped.

User response: Add the DEVCONFIG option to theserver options file, specifying a valid file or data setname to use for the device configuration file.

ANR1445I Insertdb command: Throughput wasmegabytes per hour megabytes per hour.

Explanation: This message indicates the totalthroughput (megabytes/hour) during database insertprocessing.



ANR1446I RUNSTATS: Table updating statisticsstarted.

Explanation: This message indicates the updatestatistics for all tables started.



ANR1447W command name: The server is not able tobegin a new thread to execute thecommand on line line number in parallel.The command will run serially.

Explanation: This message is issued during a RUNcommand to indicate that thread resources are notavailable to run the command in parallel. Thecommand will be executed serially.

System action: The SCRIPT continues.

User response: Increase the resources available to theserver or reduce the number of parallel commands orscripts that are running on the server at any one time.

ANR1448I command name: Beginning serial SCRIPTcommand execution on line line number.

Explanation: This message is issued during a RUNcommand (VERBOSE=YES) to indicate that a SERIALcommand was encountered and following SCRIPTcommands will be executed serially.

System action: The SCRIPT command continues.

User response: See the output of the commandsfollowing the SERIAL command to determine theirresults.

ANR1449I command name: Beginning parallelSCRIPT command execution on line linenumber.

Explanation: This message is issued during a RUNcommand (VERBOSE=YES) to indicate that aPARALLEL command was encountered and followingSCRIPT commands will be executed in parallel.

System action: The SCRIPT command continues.

User response: See the output of the commandsfollowing the PARALLEL command to determine theirresults.

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.

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 in thescript 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.


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

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 the RUNcommand.

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 in thecommand script ended in error. Command processingis 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 the linenumber 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 is specified.

Explanation: The OUTPUTFILE parameter wasspecified in a QUERY SCRIPT command but theFORMAT parameter did not specify RAW output.When outputting the QUERY to a file, you MUSTspecify RAW 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 GOTOstatement 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 GOTOstatement 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 tocomplete and the server console should be available tocontrol other 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. Define, update ordelete can not be performed.

Explanation: An DEFINE, UPDATE or DELETESCRIPT was attempted on a script that is currentlyrunning.




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) is an invaliddestination storage pool type. A copy storage pool oran active-data storage pool is not a valid copy groupTOC destination.


User response: Reissue the command using a storagepool name that is not a copy pool or active-data pool.For a list of names of defined storage pools, issue theQUERY STGPOOL command.

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.

ANR1509E Error writing option option name to filefile name.

Explanation: An error was encountered while writingan option entry to server option file.

System action: The format command fails.

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 to

update the server option file then reissue the formatcommand.

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 the



policy 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 copygroup 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.

ANR1516E Command: Storage pool storage pool nameis not enabled for deduplication.

Explanation: The command indicated specifies thename of a storage pool which does not havededuplication enabled. The command requires thatdeduplication be enabled on the storage pool before thecommand can execute.


User response: Update the storage pool to allow datadeduplication by specifying the parameterDEDUPLICATE=YES. But only do so if you wish tohave duplicates of data in the storage pool removed.

ANR1517I Insertdb command: Processed number ofdatabase records database records.

Explanation: This message indicates the total numberof database records that were successfully insertedduring database insert processing.



ANR1518I Insertdb command: Read number of bytesbytes.

Explanation: This message indicates the total numberof bytes that were successfully read during databaseinsert processing.



ANR1519I Insertdb command: Elapsed time waselapsed time.

Explanation: This message indicates the total amountof time that elapsed during database insert processing.



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 has



been 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.



ANR1524I Insertdb command: Beginning databaseupdate phase.

Explanation: The database insert process hascompleted inserting database records, and has begunmaking updates to the inserted records.



ANR1525I command: Updated database entries ofdatabase entries database entries in elapsedtime.

Explanation: The command has updated the indicatednumber of database entries.



ANR1526I Insertdb command: Building indices andchecking table integrity.

Explanation: The database insert process has begun tocreate indices and check the integrity of the databasetables.



ANR1527I command: Checked database objects ofdatabase objects database objects in elapsedtime.

Explanation: The command has checked the integrityof the indicated number of database tables.



ANR1528I RUNSTATS: Table updating statisticscompleted in elapsed time.

Explanation: This message indicates the updatestatistics for all tables completed.



ANR1529I Process process ID skipped File statededuplicated extent Extent id on volumeVolume name.

Explanation: While moving or copying deduplicatedextents from a sequential FILE volume, extents wereencountered that were marked deleted or damaged. Asa result, the extents were skipped.

System action: The server moves or copies all extentsfrom the volume that are not marked damaged ordeleted. The damaged or deleted extents are skipped.

User response: If the deduplicated extent was markeddamaged, audit the indicated volume with FIX=NO toverify whether the file is damaged. The audit will resetthe file status if the deduplicated extent is notdamaged.

If the deduplicated extent has been marked deleted, itis not copied to another storage pool.

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.





ANR1533E command: The target client version thatwas specified is not valid. The valuename value: value in the form V.R.M.F. (Version, Release, Modification, and FixLevel ) is incorrect.

Explanation: During pre-processing of commandcommand, an invalid value was encountered for theclient target level. The correct client target level shouldbe formatted like 6.2.0.0

System action: The register/update node fails.

User response: Specify the correct client target level,then reissue the command.

ANR1534I Process process ID skipped Num Filesdeduplicated files on volume Volumename because copies of the files werenot found.

Explanation: The DEDUPREQUIRESBACKUP serveroption is set to YES. If the value of this option is YES(the default), files within a deduplicated storage poolmust be backed up to a non-deduplicated copy storagepool before the files can be moved.

System action: The operation skips the files withoutcopies and continues the operation.

User response: Ensure that all files in the primarystorage pool are backed up to a non-deduplicated copystorage pool. You can also change the value of theDEDUPREQUIRESBACKUP server option to NO.However, doing so can result in unrecoverable data lossif a data-integrity error occurs. As a best practice, donot change the default.

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 namedgroup 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.


ANR1539S A previous database upgrade did notsucceed. The server cannot start.

Explanation: A DSMSERV INSERTDB command usedto upgrade from IBM Spectrum Protect V5 failed orwas cancelled. The result is a database that does notcontain all of the data from the original database. Theserver cannot be run with an incomplete database.

System action: The server will not start.

User response: Rerun the DSMSERV INSERTDBcommand.

ANR1540E Import command: The processing stopped.The connection with the source server isbroken.

Explanation: The communications link with the sourceserver broke because of a network error or because thesource-server export process stopped.

System action: The import process ends.

User response: Examine the activity log of the sourceserver to determine if the export process stopped. Anetwork failure can also cause this message to bedisplayed. If many communication error messagesoccur simultaneously, check the network for failure andcorrect any problems.



ANR1541E Export command: The processing stopped.The connection with the target server isbroken.

Explanation: The communications link with the targetserver broke because of a network error or because thetarget-server import process stopped.

System action: The export process ends.

User response: Examine the activity log of the targetserver to determine if the import process stopped. Anetwork failure can also cause this message to bedisplayed. If many communication error messagesoccur simultaneously, check the network for failure andcorrect any problems.

ANR1542E Import command: Preview processingstopped. The connection with the sourceserver is broken.

Explanation: The communications link with the sourceserver broke because of a network error or because thesource-server export process stopped.

System action: The import process ends.

User response: Examine the activity log of the sourceserver to determine if the export process stopped. Anetwork failure can also cause this message to bedisplayed. If many communication error messagesoccur simultaneously, check the network for failure andcorrect any problems.

ANR1543E Export command: Preview processingstopped. The connection with the targetserver is broken.

Explanation: The communications link with the targetserver broke because of a network error or because thetarget-server import process stopped.

System action: The export process ends.

User response: Examine the activity log of the targetserver to determine if the import process stopped. Anetwork failure can also cause this message to bedisplayed. If many communication error messagesoccur simultaneously, check the network for failure andcorrect any problems.

ANR1544I The DEDUPTIER3FILESIZE optionvalue is temporarily updated from oldvalue to new value.

Explanation: The value for the DEDUPTIER3FILESIZEoption must be greater than or equal to the value forthe DEDUPTIER2FILESIZE option. The value for theDEDUPTIER3FILESIZE option is increased to match thevalue for the DEDUPTIER2FILESIZE option until theserver is restarted or until the value for theDEDUPTIER3FILESIZE option is updated with theSETOPT command.


User response: Use the SETOPT command to updatethe value for either the DEDUPTIER2FILESIZE optionor the DEDUPTIER3FILESIZE option. Ensure that thevalue for the DEDUPTIER3FILESIZE option is greaterthan or equal to the value for theDEDUPTIER2FILESIZE option when you are specifyingthe values.

ANR1545W The diagpath ( path ) file system or diskis becoming full. Space available: spaceavailable MB of total space MB. Percentfull: file system used ratio percent.

Explanation: The file system or disk containing thedb2diag.log file is becoming full. This could causeproblems with the server if other DB2 or serverdatabases are in this space.


User response: Add space to the file system or free upspace on the file system or disk.

ANR1546W Available space for the directory (path) isless than 1 GB. If there is no spaceavailable the server can no longerfunction correctly.

Explanation: There is less than 1 GB of available spacein the file system or disk where the server databasefiles are located. When a server is initially created, withthe DSMSERV FORMAT utility or with theconfiguration wizard, a server database and recoverylog are created. In addition, files are created to holddatabase information used by the database manager.The specified path is the location of the databaseinformation used by the database manager. If there isno space available, the server can no longer functioncorrectly.


User response: Add space to the file system or free upspace on the file system or disk.

ANR1547W The server failed to update theDBDIAGLOGSIZE server option due toinsufficient available space. Requiredspace: new value megabytes; availablespace: system free space megabytes. Thecurrent value:current value megabytes.

Explanation: There was not enough free space in thefilesystem or drive to create db2diag.log files.

System action: The update fails but the servercontinues.

User response: Because the value in the server optionand logattr.chk have been updated, you must changethem to the current value so that they are consistentwith the value stored in the database manager. Free the



required disk space and update the DBDIAGLOGSIZEoption.

ANR1548E The server failed to format or initializebecause the available space (freespacebytes) in the diagnostic datadirectory path path is less than 2MB toallocate db2diag.log files;

Explanation: There was not enough free space in thediagnostic directory to allocate 2MB db2diag.log files.


User response: Free the required disk space in thediagnostic directory to at least 2MB and then run thecommand again.

ANR1549W Transaction failed for session sessionnumber for node node name (clientplatform). The next storage pool pool namefor the primary storage pool pool namecannot be a target for LAN-free backup.

Explanation: The server rolled back a database updatetransaction for the specified session because thespecified next storage pool of the specified primarystorage pool cannot be a target for LAN-free backup.


User response: An authorized administrator can issuethe UPDATE STGPOOL command for the specifiedprimary storage pool to remove the specified nextstorage pool from the parameter NEXTSTGPOOLS.Alternatively, an authorized administrator can enableLAN-free backup to the specified next storage pool.

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 thepolicy 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: attempting toarchive files specifiying thismanagement class will fail if set name isactivated.

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, attempting to archive files specifiying thismanagement class will fail. Existing archives bound tothis management class on the IBM Spectrum Protectserver will be expired based on the defmgmtclassvalues, or the archive retention grace period for thepolicy domain, if the default management class doesnot contain an archive copygroup.


User response: To archive files specifying thismanagement class, define an archive copy group for



management class class name by using the DEFINECOPYGROUP command.

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 exist

when 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 class



to 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 POLICYSETcommand. 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 that

refers 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 command arerolled 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.

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.

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.

System action: Database changes for the command arerolled back and server operation continues. The



command is not successful in changing the serverdatabase.

User response: Reissue the command and specify avalid ARCHRETN value.

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.

ANR1566E Command: Policy set description exceedslength limit characters.

Explanation: Server processing for the commandcommand fails because the policy set descriptionspecified 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.

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.

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 namerequirements.

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.

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.



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.

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.

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.

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.


User response: Reissue the command and specify avalid RETEXTRA value.

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.

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.

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.



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.

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.

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.

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 specifying CMDfor the FREQUENCY parameter, or omitting theFREQUENCY parameter because the default value forFREQUENCY is CMD for archive copy groups.

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.

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, issuethe 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.


User response: Reissue the command using a storagepool name that is not a copy pool. For a list of names



of defined storage pools, issue the QUERY STGPOOLcommand.

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,active-data pool, or container-copy pool. A copy pool,active-data pool, or container-copy pool is not a validcopy group destination.


User response: Reissue the command and specify thename of a primary storage pool. The storage pool thatyou specify for the copy group destination cannot be acopy pool, active-data pool, or container-copy pool. Fora list of the storage pool names that are defined, issuethe QUERY STGPOOL command.

ANR1588W The value of theACTIVEDESTINATION parameterreceived from the configuration managerspecifies a storage pool storage pool namefor domain domain name that is notdefined on the managed server.

Explanation: If the storage pool on the managedserver is undefined, the value of theACTIVEDESTINATION parameter for domain domainname is not updated.


User response: Define an active-data storage pool onthe managed server with the same name as that on theconfiguration manager.

ANR1589E Error reason code updating databasemanager security plugin file name.

Explanation: The server was unable to update thedatabase manager security plugin. This plugin controlsaccess to the database manager from the IBM SpectrumProtect server. The reason code is the errno from thefopen subroutine for the file. Some common reasoncodes are:

v 26 - The file is in use.

v 13 - Permission to write to the file is denied. OnWindows, this reason code can also indicate that thefile is in use.

For other reason codes, refer to your operating systemreference guide for errno values.


User response: Manually copy the file from the

installation directory to the location identified in themessage, and restart the server. On AIX, you might alsoneed to run the /usr/sbin/slibclean command as rootafter halting the server but before copying the file. Thisprocedure will unload the plugin from the kernelmemory.

ANR1590E Command: Policy domain domain name isnot defined.

Explanation: Server processing for the commandcommand fails because the policy domain name domainname does not refer to a defined policy domain in theserver database. If you used the REPLICATE NODEcommand, this message applies to the target server.


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 domainname 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 the policydomain, issue the DELETE POLICYSET command.



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.


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) in

policy 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 thenames 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.



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.



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.


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=YES



parameter 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.

ANR1613E Command: Invalid retention initiation -retention initiation value.

Explanation: Server processing for the copy groupcommand command fails because the value (retentioninitiation value) specified for the RETINIT parameter isnot valid.


User response: Issue the command again and specifya valid RETINIT value.

ANR1614E Command: Invalid number of days forRETMIN parameter - days value.

Explanation: The command fails.


User response: Issue the command again and specifya valid RETMIN value.

ANR1615E Command: RETVER of NOLIMIT cannotbe specified with RETINIT value ofEVENT.

Explanation: Server processing for the copy groupcommand command fails because the retain versionsvalue of NOLIMIT is not allowed with the retentioninitiation value of EVENT. If this is the UPDATE copygroup command, at least one of the values might havebeen defined already.


User response: Issue the command again and specifya valid RETVER or RETMIN value.

ANR1616W Command: the specified RETMIN value(new days) will be ignored because theRETINIT value is CREATION fordomain policy set management class.

Explanation: Processing for the copy group commandcommand detected that a retain minimum number ofdays value was specified either with the retentioninitiation value of CREATION, or the current retentioninitiation value stored for the copy group isCREATION. The retain minimum number of daysvalue is not used when the retention initiation value isCREATION. The copy group will be defined orupdated, but the RETMIN value will not be stored.

System action: The copy group is defined or updatedand system operation continues.

User response: The copy group will be defined orupdated, but the retain minimum number of daysvalue will not be stored. If you want to specify aretention initiation value of EVENT, issue the updatecommand again.

ANR1617W Command: the new RETVER value (newdays) is less than the value previouslystored (old days) for domain policy setmanagement class.

Explanation: Processing for the copy group commandcommand detected that the new number of days toretain versions is less than the number of dayscurrently stored for the copy group. If archive retentionprotection is active, the policy set might not activatebecause the retain versions value is not allowed todecrease.

System action: The copy group is updated and systemoperation continues.

User response: The copy group will be updated, butthe copy group might fail validation when the policyset is validated or activated.

ANR1618W Command: the new RETMIN value (newdays) is less than the value previouslystored (old days) for domain policy setmanagement class.

Explanation: Processing for the copy group commandcommand detected that the new retain minimumnumber of days is less than the number of dayscurrently stored for the copy group. The policy setmight not activate when archive retention protection isactive, because the retain minimum days value is notallowed to decrease.

System action: The copy group is updated and systemoperation continues.

User response: The copy group will be updated, butthe copy group might fail validation when the policyset is validated or activated.



ANR1619E The RETVER of NOLIMIT is notallowed with the RETINIT value ofEVENT for domain policy set managementclass.

Explanation: This message can be returned from theVALIDATE POLICYSET or ACTIVATE POLICYSETcommand. During policy set validation processing, theserver has found the the copy group in the policy hasspecified an invalid combination of options. Retainversions of NOLIMIT and retention initiation ofEVENT are not allowed. The policy will not bevalidated or activated.


User response: Update the RETVER or REINIT valuesin the copy group.

ANR1620E The new RETVER value (new days) isless than the value in the ACTIVEpolicy (old days) for domain policy setmanagement class.

Explanation: This message can be returned from theVALIDATE POLICYSET or ACTIVATE POLICYSETcommand. During policy set validation processing, theserver has found that archive retention protection isactive and the copy group has a retain versions valueless than the value in the ACTIVE policy set. Thepolicy will not be validated or activated.


User response: Update the RETVER value in the copygroup.

ANR1621E The new RETMIN value (new days) isless than the value in the ACTIVEpolicy (old days) for domain policy setmanagement class.

Explanation: This message can be returned from theVALIDATE POLICYSET or ACTIVATE POLICYSETcommand. During policy set validation processing, theserver has found that archive retention protection isactive and the the copy group has a retain minimumdays value that is less than the value in the ACTIVEpolicy set. The policy will not be validated or activated.


User response: Update the RETMIN value in the copygroup.

ANR1622E Management class class name is notdefined in policy set set name, but isdefined in the active policy set fordomain domain name. Archive retentionprotection is active, so validation fails.

Explanation: This message can be returned from theVALIDATE POLICYSET or ACTIVATE POLICYSETcommand. During policy set validation processing, the

server found a management class named class name inthe currently active policy set, but not defined in thepolicy set being validated or activated (set name). Whenarchive retention protection is active, all managementclassses in the active policy set must be included in thepolicy set being validated. Policy validation will fail.


User response: Define a management class with thename specified in the message for the policy set. Todefine the proper copy group attributes, reference themanagement class definition in the active policy set orcopy the management class class name from the activepolicy set to the policy set set name, using the COPYMGMTCLAS command.

ANR1623E Management class class name in policyset set name for domain domain name doesnot have an archive copy group. Archiveretention protection is active, sovalidation fails.

Explanation: This message can be returned from theVALIDATE POLICYSET or ACTIVATE POLICYSETcommand. During policy set validation processing, theserver found a management class named class name inthe policy set being validated or activated (set name).The management class does not have an archive copygroup. When archive retention protection is active, allmanagement classses in the policy set being validatedmust have an archive copy group. Policy validationwill fail.


User response: Define an archive copy group inspecified management class, then try the validationagain.

ANR1625E command: Server is down-level comparedto the version of data being insertedinto the database: data version.

Explanation: The DSMSERV INSERTDB commandencountered data written by a version of theDSMUPGRD EXTRACTDB command that is newerthan what is supported by the server version.


User response: Rerun the command using a version ofthe server compatible with the version of DSMUPGRDused to extract the data. Or reextract the data using anolder version of DSMUPGRD that is compatible withthe version of the server.

ANR1626I The previous message (message numbermessage number) was repeated repeat counttimes.

Explanation: The message issued prior to this messagewas issued repeatedly.



System action: The duplicate messages weresuppressed.


ANR1627I The previous message was repeatedrepeat count times.

Explanation: The message issued prior to this messagewas issued repeatedly.

System action: The duplicate messages weresuppressed.


ANR1628I The database manager is using port portnumber for server connections.

Explanation: The server configures the databasemanager environment to use the indicated port forconnections from the server. Initially, connections fromthe server do not use TCP/IP. After the number ofconnections exceeds a pre-determined threshold,connections are made through TCP/IP to the specifiedport. If the port is being used by another application,the database manager cannot receive connections fromthe server after the change to TCP/IP connections isnecessary. After this situation occurs, future connectionsto the database manager might fail.



ANR1629W command: This command will result inending the replication relationship forall nodes that match the pattern nodepattern. Replication will no longer beperformed for the specified node(s).

Explanation: A REMOVE REPLMODE command withprevent the specified nodes from being replicated. Thereplication relationship is removed for each node. Nonode data is removed from this or any of the otherreplication servers.

System action: The system asks whether you wish tocontinue with the REMOVE REPLNODE command.

User response: To process the REMOVE REPLNODEcommand, enter 'Y' to continue or 'N' to stop theprocess.

ANR1630W command: node name is not configured forreplication.

Explanation: The node specified in the command isnot configured for replication. A node is configured forreplication if the replication state of the node isENABLED or DISABLED. To determine the replicationstate, issue the QUERY NODE FORMAT=DETAILEDcommand.

System action: The operation continues but the nodeis skipped for this operation.

User response: Verify that the nodes specified in thecommand are configured for replication and try thecommand again. Nodes may be configured forreplication with the UPDATE NODE command.

ANR1631I command: Replication state informationfor the specified nodes have beenremoved.

Explanation: All replication state information for thespecified node has been removed from the databaseand the node is no longer configured for replication. Ifthe node was a target of a replication operation it maynow be used to accept client data.



ANR1632E command: Command failed. Replicationstate information for the specified nodescould not be removed.

Explanation: A REMVOVE REPLNODE commandfailed to complete. The replication state for thespecified node is not changed.


User response: The server reported a problem runningthe REMOVE REPLNODE command. Seeaccompanying messages for further information.

ANR1633E Command: Node node name is set up forreplication and cannot be renamed orremoved.

Explanation: You cannot rename or remove a nodethat is configured for replication from a source serveror that is created on a target server as a result ofreplication.

System action: The requested operation fails.

User response: To rename or remove the node, youmust first remove the node from replication by issuingthe REMOVE REPLNODE command on the serverfrom which the node is to be removed.

ANR1634I Default replication server name set toserver name.

Explanation: The name of the defaulttarget-replication server was set to the value that wasspecified with the SET REPLSERVER command. If youdid not specify a value with the command, the existingtarget replication server was removed, and client nodedata will not be replicated.





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 ifthe 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.


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.


ANR1646E Command: The datamover type data movertype can only be used with a data formatof NETAPPDUMP.

Explanation: The data format specified is not valid fora datamover of type data mover type.


User response: Reissue the command and specify avalid parameter value.

ANR1647E Cannot find file space name for nodenode ID, file space file space ID.

Explanation: The server could not obtain filespaceinformation for that node.



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.

ANR1650W The server is trying to replicate faileddata again for node node name, file spacefile space name. This might impactreplication performance.

Explanation: The replication process is processingpreviously failed data again for the specified node andfile space ID.


User response: You can view the activity log toidentify why replication failed. If possible, resolve anyissues that caused replication to fail.

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.

ANR1653E Resource lock acquisition for serverserver name failed.

Explanation: The acquisition of the resource lock forserver server name failed.

System action: The current action for the device classreferring to this server fails.

User response: Retry the action referring to the deviceclass that refers to this server name. If the lock failurepersists, please contact your service representative.

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.

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 name- server or group name.

Explanation: The command shown specifies an invalidserver or server group name.


User response: Reissue the command with a validname.

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 for one or more of the followingpurposes:

v The server is referenced by a device class ofDEVTYPE=SERVER that specifies this server for the'SERVERNAME=' parameter.

v The server is defined as the target replication server.

v A connection with this server is currently open.


User response: Reissue the command at a later time.In order to delete the server specified, it must not becurrently connected, it must not be referenced in adevice class, and it must not be defined as the targetreplication server.

ANR1666E command: FILEAGGR not allowed withTYPE=SERVER.

Explanation: The FILEAGGR= parameter may not bespecified with the TYPE=SERVER parameter also beingspecified.


User response: Reissue the command commandwithout the FILEAGGR= parameter if this node is oftype 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 atype 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 is desired,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 is desired,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 a newmember 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 specifying existingserver 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 "route : command". Thecommand may not contain route information. Only onelevel of routing is allowed.

System action: The command is 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 issued oneither 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 to resolveto 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 or using credentialsfor administrator admin name.

Explanation: An error occurred obtaining or using thecredentials for the administrator referenced.


User response: If the administratorSERVER_CONSOLE was being used for a PING orVALIDATE LANFREE command, the command mayfail. The administrator SERVER_CONSOLE is not ableto perform these commands where the source server,the target server, or both servers have authenticationenabled. Another way in which credentials could not beused is in configuration by the Operations Center. Thecommand should be retried using an administratorother than SERVER_CONSOLE.

Check the activity log and server console for othermessages about the cause of the failure. Once the causehas been resolved, reissue the command.

ANR1705W A ping request to server 'server name'was not able to establish a connectionby using administrator credentials.

Explanation: The failure could indicate a problem onthe source or target server, or in the connectionbetween the servers.

System action: No connection was established.

User response: To identify and resolve the issue,complete the following steps: 1. Check the activity logand server console for messages that indicate a failureor problem on the source server. 2. Check thecommunication connection between the servers. 3.Verify the administrator definition and password onboth servers. 4. Verify that the target server is running.5. Correct any identified issues.

ANR1706I A ping request to server 'server name'was able to establish a connection byusing administrator credentials.

Explanation: The administrator credentials are valid.



System action: The connection was established.


ANR1707E 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 authorizedadministrator must issue the SETSERVERHLADDRESS, SET and SERVERLLADDRESSor SET SERVERPASSWORD command to set themissing values.

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. This message can beissued when the CROSSDEFINE attribute for a server isset to OFF. This message can be issued as the result ofan explicit command or an automatic definition in thecase of a storage agent to server connection.


User response: Check this server, and the server beingdefined for other messages indicating the reason for thefailure. Check the crossdefine settings using the QUERYSTATUS command. If crossdefine is set to OFF, it canbe changed with the SET CROSSDEFINE ONcommand.

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 operation 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.


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 destination

storage 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 namealready exists in the server database.


User response: Correct the source name or destinationname and re-enter this command.



ANR1724W Command: Server server name is currentlyin use.

Explanation: The command shown specifies a serverthat is currently in use. The server is referenced in aPATH used for LANFree access to a FILE device typedrive in a shared library.


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, it can not be defined to bethe event server, and it cannot be referenced within aPATH definition as a FILE device type drive.

ANR1725E The source or destination name name isinvalid and the command commandfailed.

Explanation: The source or destination name is invalidin the DEFINE PATH, DELETE PATH, or PERFORMLIBACTION command.


User response: Issue the command again with a validsource or destination name.

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 or VTLlibrary.

Explanation: A drive that is to be used by a NAS datamover must be attached to a SCSI or VTL 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 usingthis 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.


User response: Reissue the command with a validdevice name.

ANR1738W The database backup does not contain acopy of the server master encryptionkey. The server master encryption keywill not be restored.

Explanation: This databackup backup was completedin a server level that does not support encryption.


User response: None

ANR1739E The database backup contains a copy ofthe server master encryption key but nopassword was provided.

Explanation: To restore the server master encryptionkey, a password must be specified on the DSMSERVRESTORE DB command.


User response: ToRestore the server master encryptionkey, specify a password on the DSMSERV RESTOREDB command. If you do not want to restore the master

encryption key, you must specify theRESTOREKeys=No value.

ANR1740W The database backup does not contain acopy of the server master encryptionkey. The server master encryption keywill not be restored.

Explanation: The server master encryption key wasnot stored when the database was backed up.


User response: To store a copy of the server masterencryption key during database backup, you mustspecify the PROTECTKEYS and PASSWORDparameters on the SET DBRECOVERY or BACKUP DBcommand.

ANR1741E The server master encryption key in thedatabase backup cannot be read. Thepassword might be incorrect, or theencryption key might be invalid.

Explanation: The server master encryption key storedin the database backup cannot be read. To access themaster encryption key, a password is required. If thepassword is incorrect, the master encryption key cannotbe accessed. If the password is correct, the masterencryption key is not being read properly.


User response: Verify that the password is correct andretry the command. If the password is correct, you canskip restoring the master encryption key. To skiprestoring the master encryption key, you must specifythe RESTOREKeys=No value on the DSMSERVRESTORE DB command. Warning: If you skip restoringthe master encryption key, you will be unable toretrieve data stored in any encrypted storage pool, andno new data will be allowed to be stored in anyencrypted storage pool.

ANR1742I The server master encryption key wasrestored successfully.

Explanation: The server master encryption key wasrestored to the server password file.

System action: N/A

User response: None

ANR1743E The parm parameter is required to beenabled when PASSWORD is specified.

Explanation: The PASSWORD parameter is only usedwhen the specified parameter has an enabled value.


User response: Remove the PASSWORD parameter orenable the keys parameter. To enable the keys



parameter for the SET DB RECOVERY or BACKUP DBcommands, set the PROTECTKEYS parameter to YES.To enable the keys parameter for the DSMSERVRESTORE DB utility, set the RESTOREKEYS parameterto YES or ONLY.

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 The HBA is busy and SAN devicescannot be discovered.

Explanation: The SAN device discovery function isbusy. The requested HBA API query cannot becompleted at this time. This type of timeout isgenerally caused by a bad HBA adapter in a systemwith multiple HBAs.


User response: Check all HBA adapters on the systemand ensure that all of them are functioning correctly.Reissue the QUERY SAN command.

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.

ANR1747E The library libname is not a ZOSMEDIAenabled library.

Explanation: Defining a PATH to a library using theZOSMEDIASERVER parameter requires the library be aZOSMEDIA library ( e.g., DEFINE LIB libnameLIBTYPE=ZOSMEDIA ).


User response: Reissue the command with the correctlibrary name.

ANR1748E The PASSWORD parameter is requiredwhen parm is enabled.

Explanation: The PASSWORD parameter is requiredwhen the specified parameter has an enabled value.


User response: Add the PASSWORD parameter ordisable the keys parameter. To disable the keysparameter for the SET DB RECOVERY or BACKUP DBcommands, set the PROTECTKEYS parameter to NO.To disable the keys parameter for the DSMSERVRESTORE DB utility, set the RESTOREKEYS parameterto NO.

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 IBM SpectrumProtect.


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 command toexamine messages prior to this error to determine thecause of the data storage failure. If the failure can befound and resolved, retry the operation. If the failurecannot be found, contact your service representative forassistance in resolving the problem.

ANR1758I Repaired extents damaged extents indirectory container pools.

Explanation: The server repaired the specified numberof extents.



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.




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 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 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 points areavailable and working correctly. Correct the problemand try the command again.

ANR1763E Command: Command failed - seeprevious error messages or view theactivity log.

Explanation: The indicated server command hasfailed. This message is always preceded by one or more

other error messages which provide more detail aboutwhy the command failed.



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 loadablemodule 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.

ANR1766E Command: NAS device datamover reportsa drive affinity for drive tape drive thatdoes not match this data mover.

Explanation: A NAS device returned an affinityidentifier for a tape drive that does not match therecorded affinity identifier for the data mover.


User response: Check the High Level Address for thedata mover and verify that it is a node managementnetwork interface on the NAS cluster. Verify that theinterface is located on the appropriate node cluster.

ANR1767I Process process number for NAS nodenode name will use NAS data moverdatamover

Explanation: An alternate NAS data mover wasselected for the current NAS operation.



System action: The NAS operation continues.


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 parameter thatis 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 field ofthe 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: .


ANR1774E The Query Status command failed, andserver initialization has not completed.Allow server initialization to complete,and then try the command again.

Explanation: The command Query Status failedbecause server initialization has not completed.


User response: Allow server initialization to complete,and then try the command again.

ANR1775I Data mover mover name has beendefined, however a connection to thedata mover failed. Please check theattributes of the file server specified inthe definition of the data mover.

Explanation: The data mover has been defined in theserver database, however the server cannot connect tothe file server associated with the data mover. Theconnection failed because of one of the followingpossible 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 is not accessible

v NDMP server limits the number of opened NDMPsessions

System action: The data mover is defined to theserver.

User response: Check that the file server associatedwith the data mover is accessible through the network;check each of the attributes specified during datamoverdefinition; check the number of open NDMP sessionswith the file server.



ANR1776I Data mover mover name has beenupdated, however a connection to thedata mover failed. Please check theattributes of the file server specified inthe update command.

Explanation: The data mover has been updated in theserver database, however the server cannot connect tothe file server associated with the data mover. Theconnection failed because of one of the followingpossible reasons:

v One of the parameters specified during datamoverupdate was incorrect: TCP/IP address of the fileserver, user id, password, TCP/IP port



System action: The data mover definition is updated.

User response: Check that the file server associatedwith the data mover is accessible through the network;check each of the attributes specified in the datamoverupdate command; check the number of open NDMPsessions with the file server.

ANR1777W Command: New cluster node cluster nodeon NAS cluster nas cluster is assignedsame cluster affinity as cluster nodeexisting cluster node

Explanation: A NAS cluster device reported a clusternode with a cluster affinity identifier that is the sameas an existing data mover.


User response: Check the data movers reported in themessage and updata any existing device paths definedfor these data movers based upon the currentconfiguration of the NAS cluster.

ANR1778E Command: Invalid or missing parameter.

Explanation: The specified server command has beenentered with an invalid parameter, or, is missing arequired parameter.



ANR1779I backupset process name process completed:successful count backupset(s) weregenerated or defined out of total countbackupset(s) requested by thecommand's specifications.

Explanation: A GENERATE or DEFINE BACKUPSETcommand has finished successfully, and the backupsetsdescribed in previous messages have been created.

System action: The backupsets described have beencreated.


ANR1780I Command: The network-attached storage(NAS) cluster cluster name has tapedevices attached to cluster node clusternode

Explanation: The server has discovered tape drivesattached to a node in a NAS cluster during a DEFINEDATAMOVER or UPDATE DATAMOVER command.



ANR1781I Command: The network-attached storage(NAS) cluster cluster name requires newdata mover, cluster node, for tape driveaccess.

Explanation: The server has discovered a node withinin a NAS cluster with attached tape drives. A new datamover will be defined to provide access to the attachedtape drives.


User response: When a datamover is created by theserver for node within a cluster you should identify thetape drives attached to the node. Define paths from thenew datamover to each drive you want to use forbackup of the NAS cluster.

ANR1782I Representational State Transfer (REST)services are starting at time.

Explanation: After the REST services start,applications that use REST services can query andmanage the storage environment by connecting to theOperations Center.

System action: Server operation continues as the RESTservices are started.

User response: You can disable the REST services byremoving the monitoring administrator. To remove themonitoring administrator, issue the followingadministrative command: set monitoringadmin ""

ANR1783I Representational State Transfer (REST)services were stopped at time.

Explanation: After the REST services are stopped,applications that use REST services can no longer queryand manage the storage environment by connecting tothe Operations Center.

System action: Server operation continues after theREST services are stopped.

User response: You can enable the REST services byadding a monitoring administrator. For example, to add



a monitoring administrator who is named JANE, issuethe following administrative command: setmonitoringadmin jane

ANR1786W HBAAPI not able to get adapter name.

Explanation: The HBAAPI function getAdapterNamefailed. The server will continue to access next adapter ifit exists.


User response: The IBM Spectrum Protect SANdiscovery will not work with this Host Bus Adapter.For the list of supported HBAs and required driverlevels by operating system, see techdoc 1193154 athttp://www.ibm.com/support/docview.wss?uid=swg21193154.

ANR1787W Unable to open adapter adapter name.

Explanation: The HBAAPI function to open the hostbus adapter (HBA) failed.


User response: The IBM Spectrum Protect SANdiscovery will not work with this Host Bus Adapter.For the list of supported HBAs and required driverlevels by operating system, see techdoc 1193154 athttp://www.ibm.com/support/docview.wss?uid=swg21193154.

ANR1788W Unable to retrieve the adapter attributesfor adapter name.

Explanation: The HBAAPI function failed to retrievethe adapter' attributes. This problem is caused by anonfunctional Fibre Channel adapter on the system.Check this adapter to ensure it works properly. Thisproblem also can be caused by other non Fibre Channeltypes of adapters on the system, such as, a SAS or aparallel SCSI adapter. This message can be ignored ifyou are using a non Fibre Channel adapter.


User response: SAN discovery does not work for thisadapter. For the list of supported HBAs and requireddriver levels by operating system, see techdoc 1193154at http://www.ibm.com/support/docview.wss?uid=swg21193154

ANR1789W Get HBA target mapping failed.

Explanation: The HBAAPI function to get the targetmapping failed.


User response: SAN discovery will not work for thisadapter. For the list of supported HBAs and requireddriver levels by operating system, see techdoc 1193154at http://www.ibm.com/support/

docview.wss?uid=swg21193154.

ANR1790W SAN discovery failed.

Explanation: SAN discovery failed.


User response: SAN discovery failed. This may be aproblem with the HBA firmware, HBA or the HBAverdor's HBAAPI driver. For the list of supportedHBAs and required driver levels by operating system,see techdoc 1193154 at http://www.ibm.com/support/docview.wss?uid=swg21193154.

ANR1791W HBAAPI wrapper library file name failedto load or is missing.

Explanation: This library is provided by IBMSpectrum Protect. It is required for discovery of deviceson a SAN.

v For windows, the HBAAPI wrapper library ishbaapi.dll.

v For AIX, the HBAAPI wrapper library islibHBAAPI.a.

v For Solaris, the HBAAPI wrapper library islibhbaapi32.so for 32 bit application andlibhbaapi64.so for 64 bit application.

v For Linux, the HBAAPI wrapper library islibhbaapi32.so for 32 bit application andlibhbaapi64.so for 64 bit application.


User response: Make sure the HBAAPI wrapperlibrary for this platform is in the same directory as theIBM Spectrum Protect server executable. AIX is theonly exception with HBAAPI wrapper librarylibHBAAPI.a in /usr/lib.

ANR1792W HBAAPI vendor library failed to load oris missing.

Explanation: The HBAAPI vendor library failed toload or is missing. This HBAAPI library is provided bythe Host Bus Adapter (HBA) vendor. It is required forIBM Spectrum Protect server to discover devices on theSAN.


User response: Ensure the HBAAPI file exists on thesystem. If the driver level on your system is notsupported, go to the HBA vendor's website anddownload/install the HBA driver. For the list ofsupported HBAs and required driver levels byoperating system, see techdoc 1193154 athttp://www.ibm.com/support/docview.wss?uid=swg21193154. The following is anexample of some of the HBA vendor's HBAAPI file:

v For UNIX systems, This HBAAPI vendor library'slocation is indicated in /etc/hba.conf. For example:















qla2x00 /usr/lib/libqlsdm.socom.emulex.emulexapilibrary

/usr/lib/libemulexhbaapi.so

v For Windows systems, verify the location of theHBAAPI vendor library by checking LibraryFile in:

HKEY_LOCAL_MACHINESOFTWARE

SNIAHBA

<HBAAPI library>

ANR1793W IBM Spectrum Protect SAN discovery isnot supported on this platform or thisversion of OS.

Explanation: SAN discovery for this platform iscurrently not supported.


User response: SAN discovery will not work for thisplatform.

v For AIX, we only support AIX5.2F and above

v For HP, we do not support this platform yet.

v For Linux, we do not support Linux-zOS yet.

v For Windows, we do not support Windows 2003 64bit yet.

For the list of supported HBAs and required driverlevels by operating system, see techdoc 1193154 athttp://www.ibm.com/support/docview.wss?uid=swg21193154.

ANR1794W IBM Spectrum Protect SAN discovery isdisabled by options.

Explanation: SAN discovery is disabled by optionSANDISCOVERY OFF or SANDISCOVERYUNSCANNEDPATHOFF.


User response: SAN discovery is currently disabledeither by default by the SANDISCOVERY OFF optiondepending on the platform or by the SANDISCOVERYUNSCANNEDPATHOFF option. For the list ofsupported HBAs and required driver levels byoperating system, see techdoc 1193154 athttp://www.ibm.com/support/docview.wss?uid=swg21193154.

ANR1795I The device driver has been updatedsuccessfully for device old device name.The new device name is new device name.

Explanation: This message is displayed in response tothe CHANGE DEVDRIVER command. The devicedriver for device old device name has been updatedsuccessfully.



ANR1796E Invalid device name device name.

Explanation: The device name is not in the form ofTAPEx or CHANGERx.


User response: Change the device name to TAPEx orCHANGERx and retry the command.

ANR1797E Device device name is not supported bythe IBM Spectrum Protect device driver.

Explanation: Device device name is not supported bythe IBM Spectrum Protect device driver. The hardwareID was not found in the IBM Spectrum Protect devicedriver INF file, i.e. tsmlb.inf and tsmmt.inf.


User response: Access the IBM Spectrum Protect Website at www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html and navigateto the device support information for the server'soperating system. Verify if the device is supported. Ifthe device is supported by the IBM Spectrum Protectdevice driver, contact your service representative.

ANR1798E Device driver update failed for devicedevice name.

Explanation: The CHANGE DEVDRIVER operationfailed for device device name.



ANR1799E The IBM Spectrum Protect device driveris not installed, or one or more devicedriver files are missing.

Explanation: The server command has failed becausethe IBM Spectrum Protect device driver is not installed,or one or more device driver files are missing.


User response: Make sure the IBM Spectrum Protectdevice driver is installed. and the following files are notmissing. %WINDIR%\system32\drivers\tsmscsi.sys (ortsmscsi64.sys for 64-bit Windows), %WINDIR%\inf\tsmmt.inf, and %WINDIR%\inf\tsmlb.inf.

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 the







invalid event or event class. Any valid events or classesspecified are processed.

User response: Reissue the command with the correctevent or event class.

ANR1802E Device device name was not found.

Explanation: The device was not found in the deviceinformation set. The vendor ID and/or product ID, ordevice name may be invalid, or the device has beenremoved from the system.


User response: Reissue the command with the correctvendor ID and product ID, or device name.

ANR1803W SAN discovery module module name isnot installed correctly.

Explanation: The server attempted to load the SANdiscovery module, but the permissions or ownership ofthe file are incorrect.

System action: Server operation continues, butwithout SAN discovery function.

User response: Ensure that the SAN discovery moduleis executable, has the setuid bit turned on, and isowned by root. The SAN discovery module is called'dsmqsan' and must reside in the server or storageagent executable directory.

ANR1804W Command: Process process numberskipping volume volume name in storagepool pool name because the volume is inuse by another process.

Explanation: The command shown specifies thevolume to be processed, but that volume is currentlybeing used by another operation.

System action: The server skips the volume andprocesses the next available volume.

User response: Check the activity log to determinewhich operation was using the volume. If the operationusing the volume is complete reissue the Command toprocess the skipped volume.

ANR1805I This export command does not workwith either container or cloud storagepools. Object Object Name is skipped.

Explanation: Container storage pools cannot be usedfor storage pool backup, reclamation, migration,collocation, export, import, or simultaneous-write.

System action: The server skips the object andprocesses the next available object.

User response: Use another method or storage pooltype to store the data.

ANR1806I Some data is skipped because theoperation cannot be completed forcontainer or cloud storage pools.

Explanation: Container or cloud storage pools cannotbe used for storage pool backup, reclamation,migration, collocation, export, import, NDMP, generatebackupset or simultaneous-write.



ANR1807I Table updating statistics performedsuccessfully for processed table.

Explanation: Runstat successfully run on that table.


User response: No user action required.

ANR1808I Object Object ID is skipped because theoperation cannot be completed for cloudstorage pools.

Explanation: Cloud storage pools cannot be used forstorage pool backup, reclamation, migration,collocation, or simultaneous-write.



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 morememory 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.



ANR1811W The Host Bus Adapter API packagemight not be installed.


User response: The HBA API does not provide thenumber of Fibre Channel adapters from the hostsystem. The HBA API file version that is on youroperating system might not be supported or the HBAAPI package might not be installed. Go to the HBAvendor website to obtain the latest version of the HBAAPI. For a list of supported HBAs and required HBAAPI levels by operating system, see techdoc 1193154 athttp://www.ibm.com/support/docview.wss?uid=swg21193154.

ANR1812E DELETE FILESPACE filespace name fornode node name failed deletion becauseof a replication in progress.

Explanation: The reported filespace belonging to thereported node is currently being replicated as part of aREPLICATE NODE command. A filespace cannot bedeleted while the replication is in progress.

System action: The DELETE FILESPACE ends with astate of FAILURE.

User response: Use the QUERY PROCESS commandto view active REPLICATE NODE processes. Eitherwait for the replication to complete or cancel thereplication process with the CANCEL PROCESS orCANCEL REPLICATION commands, and reissue theDELETE FILESPACE command.

ANR1813W Filespace filespace name for node nodename is a replication replication role.

Explanation: The reported filespace is either thesource or target of a replicated node. The DELETEFILESPACE command will delete the data on thisserver, but will not delete the data on any otherreplication servers.

System action: The DELETE FILESPACE commandcontinues.

User response: If this message indicates this filespaceis the source of replicated data, then login to all serverscontaining replicated data from this filespace and issuethe DELETE FILESPACE command to remove the datafrom those servers. If this message indicates thisfilespace is the target of replicated data, ensure that thefilespace on the source server is either deleted, orupdated to no longer replicate to this server.

ANR1814W The database manager cannot load thesecurity plugin file name.

Explanation: The database manager cannot load thesecurity plugin. This plugin controls access to thedatabase manager from the IBM Spectrum Protectserver.


User response: Inspect the DB2 diagnostic log file toidentify the reason the database manager cannot loadthe security plugin. Correct the problem and restart theserver.

ANR1815W Check target server for storage problemsduring replication of node node list.

Explanation: During the replication process for thespecified nodes, there were problems storing data atthe replication target server.


User response: Check the activity log of the targetserver for specific error messages relating to datastorage during the replication process.

ANR1816W The names of one or more files weretruncated. Examine log file log file namefor details.

Explanation: The DSMSERV INSERTDB commandattempted to insert a database row describing a filewhose path name is longer than the maximum pathname supported by IBM Spectrum Protect V6. The IBMSpectrum Protect V5 server supported path names ofup to 8000 bytes, but the V6 server does not allow pathnames to be longer than 6000 bytes.

System action: The name of the file was replaced by asystem-generated name. Information needed to restorethe file to its original name was written to the specifiedlog file.

The log file contains two sections. The first section listsfiles whose names were truncated. The second sectionidentifies the node names and filespace names of thetruncated files.

The first section is identified by the header "--Truncated Files --". Each line of this section identifiesone file whose name was truncated. The line consists offour fields, separated by tabs:

v Node ID - a numeric identifier for the node thatowns the file.

v Filespace ID - a numeric identifier for the file'sfilespace.

v New Name - the system generated name that wasassigned to the file.

v Original Name - the original name of the file.

The second section is identified by the header "-- Nodeand Filespace Names --". Each line in this section mapsthe node ID and filespace ID associated with one ormore of the files in the first section to a node name andfilespace name that can be specified on a restorecommand. The line consists of four fields, separated bytabs:





v Node ID - a numeric identifier for the node thatowns the file.

v Node Name - the name of the node associated withthe node ID.

v Filespace ID - a numeric identifier for the file'sfilespace.

v Filespace Name - the name of the filespace associatedwith the filespace ID.

User response: Inspect the contents of the specifiedlog file. If necessary, use the information in the log fileto restore the files to their original name.

ANR1817W command: No valid nodes wereidentified for import on target servertgtServerName.

Explanation: During a server-to-server export, theimport process on the target server reported that noneof the node definitions in the export data were valid forimport. No node data was imported on the targetserver.


User response: Check for warning or error messageson the target server and handle as needed.

ANR1818W command: No valid nodes wereidentified for import.

Explanation: During a server import process none ofthe node definitions in the import data were valid forimport. No node data was imported.


User response: Check for warning or error messagesduring the import process on the server and handle asneeded.

ANR1819E Permission denial to device device name.

Explanation: A read-only attribute is assigned tonon-root users and their tape device files. If thisattribute is not changed, non-root users cannot storedata to tape devices. This only affects HP-UX, Linux,and Solaris operating systems.

System action: The open operation fails.

User response: Issue the CHMOD system commandto change the read-only attribution for specific tapedevice files and run the previously failed operationagain. See Technote 1321130 for details about resolvingthis problem: https://www-304.ibm.com/support/docview.wss?uid=swg21321130

ANR1820E The server could not connect to thedatabase manager by using TCP/IP portport number.

Explanation: The server attempted to connect to thedatabase by using TCP/IP, but it was not able to do so.


User response: First, verify that the port number isnot already in use. Possible methods include:

v On Unix systems, inspect /etc/services for anoccurance of the port number.

v Use the netstat command to determine if a service islistening on the port number.

If a conflict is detected, specify a different port numberon the DBMTCPPORT option in the server options fileand restart the server.

If no conflict is found, use the "db2 get databasemanager config" command to verify that theSVCENAME configuration parameter is set to the portnumber identified by the message. If not, then use the"db2 update database manager config usingSVCENAME port number" command to manuallyupdate the configuration parameter. Ensure that thevalue specified is also specified on the DBMTCPPORTserver option. Restart the server.

Finally, use the "db2set" command to verify that theDB2COMM environment variable is set to "TCPIP". Ifnot, then use the "db2set DB2COMM=TCPIP"command to set the environment variable and restartthe server.

ANR1821W Event logging is not started for thereceiverName receiver.

Explanation: In response to a BEGINEVENTLOGGING command, recording of event logrecords to the specified receiver was attempted. Theevent logging for the specified receiver is alreadystarted because either the receiver is currently runningor the receiver was terminated previously and is still inthe process of writing the messages that were queuedup for processing.


User response: Check to see if the event log receiver isalready started by issuing the QUERY STATUScommand, and checking the Active Receivers field.Some event log receivers such as FILETEXT,FILETEXTEXIT, USEREXIT, and Tivoli receiver, can bestarted during server initialization if they areconfigured in the server options file.

v If the event log receiver is already started you do nottake any further action.

v If the event log receiver is not currently running thenwait and try to start it again after a short delay.



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.



ANR1827E Eventlog command: No valid receiverspecified.

Explanation: An event logging command has beenentered, and no valid receivers were specified.



ANR1828W Session session number for node, admin, orserver name (client platform) refused -protocol protocol required.

Explanation: No TLS/SSL connection was established,therefore the server did not start a session because anTLS/SSL connection with a higher protocol is required.


User response: Configure the client or target server touse a higher TLS/SSL protocol. This may requireimporting a new server certificate on the client or targetserver. For example, import the cert256.arm instead ofthe cert.arm file.

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 the serveroptions 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 Fasp monitor collector finished andexiting.

Explanation: The Fasp monitor processing collector isterminating processing because the Fasp monitoring



function has been set to off or the system is shuttingdown.

System action: None, the Fasp monitor collectorterminates.

User response: The Fasp status processing was turnedoff using the SET MONITORFASP command.

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 theserver 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 change

your 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 "VALIDATEPROTOCOL" 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 a



parameter, 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 NODEcommand 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, the

SERVER type node on the target server should beupdated using the UPDATE NODE command withVALIDATEPROTOCOL=ALL.

ANR1860E Drive with serial serial element elementport port and target target lun lun doesnot match with the library libraryPath .

Explanation:

System action:

User response:

ANR1861E Drive with element element port port andtarget target lun lun does not match withthe library libraryPath .

Explanation:

System action:

User response:

ANR1862W command: This command will remove allreplication information for the serverwith ID Unique ID.

Explanation: All replication information stored on thisserver that references the indicated server will bedeleted. Subsequent replications to the indicated servermay cause data to be re-sent.

System action: The system asks whether you wish tocontinue with the REMOVE REPLSERVER command.

User response: To process the REMOVE REPLSERVERcommand, enter 'Y' to continue or 'N' to stop theprocess.

ANR1863E library libraryPath and serial serial doesnot support Read Element Statuscommand. It is very old and should bereplaced with newer model.

Explanation:

System action:

User response:

ANR1864E library libraryPath does not support ReadElement Status command and it doesnot have a serial number. It is very oldand should be replaced with newermodel.

Explanation:

System action:

User response:



ANR1865I export command : Summary forRestartable Export operation exportidentifier :

Explanation: A summary of the total number ofobjects transmitted in the restartable export operationwith export identifier is displayed following thismessage.

System action: Export processing for the commandends. Server operation continues.


ANR1866I Export/import command: Processingsuspended with status status.

Explanation: The background process to service thecommand command was suspended with a SUSPENDcommand.

System action: Processing for the command commandstops. Statistics on the number and type of objectsmoved, together with the total number of bytes copied,are displayed on the server console following thismessage.


ANR1867I 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.


ANR1868I 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.



ANR1869W 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 numberspace-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.

ANR1870I 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.



ANR1871I 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 mediavolumes needed to hold the exported information fromthe server.





ANR1872I 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.



ANR1873I 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.



ANR1874I 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.



ANR1875I 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.

ANR1876W Export/import command: Detected anunexpected value, value, for thedata-transfer path option setting for nodenode name. The default value of 'ANY' isused for the node.

Explanation: The export or import operation detectedan unexpected data-transfer path value for the node. Asa result, the default value of 'ANY' is used for the nodeand indicated data-transfer path option.


User response: If the data-transfer path setting of'ANY' is acceptable for the node, do nothing further. Ifyou must change the setting, use the UPDATE NODEcommand.

ANR1877E NAS backup process terminated - NASfile server NAS file server name reportedillegal arguments.


User response: Verify the that the filespace exists onthe NAS file server. If backing up a NAS virtualfilespace verify that the path specified in the virtualfilespace exists.

For details about how to identify the cause of theterminated NDMP operations, see the NAS file-serverdocumentation. Check the NDMP logs for the NAS fileserver and correct the cause of the errors and restartthe operation.

ANR1878E A database manager configurationparameter cannot be updated. The valueof the DIAGSIZE parameter is greaterthan the amount of free space availablein the database manager's diagnosticdata directory.

Explanation: The error occurred because the currentvalue of the DIAGSIZE database manager configurationparameter is greater than the amount of free space inthe drive or the file system that contains the diagnosticdata directory.

System action: The operation fails. Depending on theconfiguration parameter that is being updated, theserver might stop.

User response: Complete one of the following options:

v Specify a smaller value for DIAGSIZE.



v Change the location of the diagnostic data directoryto a drive or file system that has more free space.

v Increase the amount of free space on the drive or filesystem containing the diagnostic data directory.

To check the current setting of the DIAGSIZEconfiguration parameter, issue the following databasecommand:

db2 get dbm cfg

and search for "DIAGSIZE".

To change the value of the DIAGSIZE configurationparameter, issue the following command:

db2 update dbm cfg using DIAGSIZE new_size

new_size is the value, in megabytes, of the DIAGSIZEconfiguration parameter. The value must be 2 orgreater.

For more information, see "Locating DB2 diagnostic logfiles" in the product information (http://www.ibm.com/support/knowledgecenter/SSEQVQ/).

ANR1879E command: Multiple replication server IDsmatch the specified ID pattern.

Explanation: During a REMOVE REPLSERVERcommand, a wildcard was used for the replicationserver ID. This resulted in more than 1 matching serverID. To avoid accidental erasure of replicationinformation, only a single replication server ID can beremoved at a time.

System action: The command is terminated by theserver.

User response: Issue the REMOVE REPLSERVERcommand with a more specific replication server IDvalue such that only one matching server ID is selected.

ANR1880W Server transaction was canceled becauseof a conflicting lock on table table name.

Explanation: The server online reorganization for thereferenced table could not be completed because of alock conflict between the reorganization process and aserver process. The server process was canceled toallow the reorganization process to be completed. Insome cases, the server might need to cancel multipleserver processes to resolve the lock conflict.Consequently, this message might be displayedmultiple times as server processes are forced to stop. Inaddition, other server application error messages mightbe displayed as the lock conflicts are resolved.

System action: The server will continue to operate;however, until the lock conflict is resolved, no newreorganizations will be started.

User response: Review the server activity log anddetermine whether a critical server operation wascanceled that should be restarted. If so, restart theserver operation.

ANR1881E Command or operation: Failure because theLDAPUSER password is expired.

Explanation: The password credentials for the useraccount specified as the LDAPUSER are expired andneed to be updated.


User response: The administrator for the LDAPdirectory server must update the password for theLDAPUSER account in the LDAP directory server.Then, after the LDAP administrator updates thepassword, issue the LDAPPASSWORD command tomatch the new password. Reissue the command thatfailed.

ANR1882E Command or operation: A password wasreset and must change while accessingthe LDAP administrator or node entryadmin or node name with administrator/nodename or LDAPUSER credentials.

Explanation: The password credentials used for thisoperation were reset and you must update thepassword on the LDAP directory server.

System action: The operation requires a passwordupdate.

User response: If the operation used the LDAPUSERcredentials, update the password for the user accountspecified as the LDAPUSER in the LDAP directoryserver. If the operation used node or administratorcredentials, a password expiration status is issued toforce a password update.

ANR1883E Command or operation: An access failureoccurred while accessing the LDAPadministrator or node entry admin or nodename with administrator/node name orLDAPUSER credentials.

Explanation: The command failed after the IBMSpectrum Protect server accessed an entry in the LDAPdirectory server and received a locked account error.


User response: If the operation used the LDAPUSERcredentials, unlock the user account specified as theLDAPUSER in the LDAP directory server. If theoperation used a node or administrator credentials,unlock the node or administrator by issuing theUPDATE NODE or UPDATE ADMIN command with apassword or directly unlock the node or administratoraccount in the LDAP directory server.



ANR1884E Command or operation: An authenticationfailure occurred with the LDAPdirectory server when the LDAPUSERcredentials were used.

Explanation: The IBM Spectrum Protect server tried toauthenticate and access was denied.


User response: Validate that the LDAPUSER, theLDAPPASSWORD, and the LDAPURL are set to thecorrect values. Correct any invalid setting and reissuethe command or operation.

ANR1885E Command or operation: Permission wasdenied when the LDAP administrator ornode entry admin or node name wasaccessed as administrator/node name orLDAPUSER.

Explanation: The command failed after the IBMSpectrum Protect server authenticated with the LDAPdirectory server as the LDAPUSER. Permission wasdenied when the server tried to add, modify or deletean entry in the LDAP directory server.


User response: The user specified by the LDAPUSERneeds full access control over the distinguished name(DN) specified in the LDAPURL server option. Correctthe access control rights of the LDAPUSER or provide adifferent LDAPUSER who has full access control rightsover the IBM Spectrum Protect server's DN.

ANR1886E Entry entry name was not found in theLDAP directory server.

Explanation: The command failed because the IBMSpectrum Protect server tried an operation on an LDAPentry that was not found on the LDAP directory server.


User response: The IBM Spectrum Protect server triedan operation with the LDAP directory server and theoperation failed because the entry could not be found.To insert a new entry for this node or administrator,issue an UPDATE NODE or UPDATE ADMINcommand and provide a password.

ANR1887E Command or operation: Failure whenworking with the LDAP directoryserver.

Explanation: The command or operation failedbecause of an error returned by the LDAP directorysterver.


User response: The IBM Spectrum Protect server ranan operation with the LDAP directory server and the

operation failed. Specific error details are contained inprevious messages. The common causes of LDAPfailures are as follows:

v A communication error occurred with the LDAPdirectory server

v The LDAPURL is invalid or missing (wronghostname or base DN)

v The LDAPUSER is invalid or missing (wrong valueor locked)

v The LDAPPASSWORD is invalid or missing (wrongvalue or expired)

Update the LDAP directory server settings or contactyour LDAP administrator to resolve this issue

ANR1888W Session session number for node nodename (client platform) refused - clientrequires SSL connection with thisserver.

Explanation: No SSL connection was established,therefore the server did not start a client sessionbecause the client node or admin requires an SSLconnection.


User response: Configure the client to use SSL orupdate the node or admin definition on the server suchthat SSL is not required (update SSLREQUIREDparameter). If the node is created withSSLREQUIRED=SERVERONLY, a corresponding admindefinition is created with SSLREQUIRED=YES. To use anon-SSL session with a storage agent, rename theadmin with the identical name by issuing the RENAMEADMIN command.

ANR1889W Session session number was terminatedduring backup for node node name (clientplatform), with file space filespace id orname because a restore operation is inprogress.

Explanation: During a file backup operation, theserver ends a node session because one or more filesare locked by a restore operation.

System action: The backup session is terminated bythe server.

User response: Issue the QUERY RESTORE commandwith FORMAT=DETAILED to determine if the restoreoperation is active or is in a restartable state. Arestartable restore operation keeps files locked until theamount of time that is specified for theRESTOREINTERVAL server option is reached. You canlower this value to free up locked files. Issue theQUERY OPTION command to display the currentsetting for the RESTOREINTERVAL option.

If you received this message due to a client backupoperation, restart the operation after the restore



operation has completed in order to move anyremaining files. You can also cancel the restartablerestore session with the CANCEL RESTORE command.

ANR1890W Backup operation for session sessionnumber node client node name failed dueto root-only restriction.

Explanation: The backup operation failed because anon-root user attempted the operation. A restriction isin place to disallow backup operations by non-rootusers for the indicated node.

System action: The backup operation is terminated. Amessage is issued by the client. For clients that arelevels prior to 6.3, message ANS0350E may appear.

User response: Retry the backup operation as the rootuser.

ANR1891E Command or operation: The operationcannot be completed when theLightweight Directory Access Protocol(LDAP) mode is set to Integrated.

Explanation: In Integrated mode, the LDAP directorycannot be modified, except to delete users or changepasswords. To delete users or change passwords, theuser ID that is specified with the SET LDAPUSERcommand must have sufficient authority.


User response: Run the operation by using LDAPutilities instead of server commands.

ANR1892W Process process ID for process namecompleted with a completion state ofSUCCESS but warning or more-severemessages were issued.

Explanation: The process completed with acompletion state of SUCCESS but warning messages ormore-severe messages were issued by this process. Thisprocess may not have completed all of the processing.


User response: Review the messages in the activityand event logs that were issued by this process.Determine if the conditions that caused these messagesto be issued had an affect on the operation.

ANR1893E Process process ID for process namecompleted with a completion state ofFAILURE.

Explanation: The process completed with a state ofFAILURE.


User response: Review the messages in the activityand event logs that were issued by this process.

Determine the conditions that caused these messages tobe issued, resolve those issues and retry the operation.

ANR1894E command: Processing for node node name,file space file space name failed becauseof a lock conflict.

Explanation: The server could not obtain a resourcethat is required to process the indicated file space.

System action: The command continues, butprocessing of the indicated file space fails.

User response: To increase the probability of acquiringall of the necessary resources, issue the indicatedcommand when server activity is relatively low.

ANR1895W Command or operation: The password forthe node node name now usescase-sensitive passwords.

Explanation: The node is authenticating with anLDAP directory server. The LDAP authenticationpassword policy is dictated by the LDAP directoryserver and this usually requires passwords to becase-sensitive.



ANR1896E Unable to allocate volume volume namebecause it is still referenced in thevolume history.

Explanation: The volume cannot be allocated becausethe active volume history record shows the volume asbeing in use.

System action: The active volume history recordshows the volume as being in use.

User response: The volume is being managed by theserver or it might be incorrectly referenced in thevolume history table due to out-of-date records. Tocheck the records and confirm the volume historystatus, issue the QUERY VOLHISTORY command. Ifthere is an invalid volume history record, use theDELETE VOLHISTORY command to remove therecord. If the DELETE VOLHISTORY command fails,contact IBM Software Support to remove the record.

ANR1897I LDAP password removed.

Explanation: The password that the server uses toauthenticate with the LDAP server was removed by theSET LDAPPASSWORD command.





ANR1898I LDAP user name removed.

Explanation: The LDAP user distinguished name(DN) that the server uses to authenticate with theLDAP server was removed by the SET LDAPUSERcommand.



ANR1899W Command or operation: Unable to workwith the LDAP directory server.

Explanation: The command or operation finished, butthe IBM Spectrum Protect server did not work with theLDAP directory server because the LDAP directoryserver configuration is incomplete. If a node oradministrator was being created or updated on theLDAP server, you cannot use it to logon until theserver is able to use LDAP directory serverinformation.

System action: The operation finished, butinformation was not added to the LDAP directoryserver.

User response: An operation was run on the IBMSpectrum Protect server with the LDAP directoryserver. The operation succeeded, but information wasnot added to the LDAP directory server because theLDAP directory server configuration is incomplete.Common incomplete configuration scenarios are asfollows:

v LDAPURL values were not provided in the serveroptions file

v The LDAPUSER is invalid (wrong value or locked)

v The LDAPPASSWORD is invalid (wrong value orexpired)

Update the LDAP directory server information orcontact your LDAP administrator to resolve this issue.After completing the LDAP configuration, when youadd a node or admin with LDAP authentication, youare required to submit a new password when you logon to the IBM Spectrum Protect server.

ANR1900E Path between server server source andlibrary parm is not allowed.

Explanation: You must specify a path from the currentserver to the library when you are defining the library.You cannot specify a path from a different server.


User response: Reissue the command with a differentsource or destination name or define a new path.

ANR1901I The specified session is associated withprocess name process process id and cannot be cancelled.

Explanation: The server can not cancel the sessionbecause it is associated with a running process.


User response: The session can only be cancelled bycancelling the associated process. Use the CANCELPROCESS command to cancel a process.

ANR1902W Node node name on server server name isnot enabled for replication. It will notbe replicated.

Explanation: The server is not able to replicate thespecified node because the node on the specified targetserver is not enabled for replication.

System action: The node is not replicated to thespecified server. Server operation continues.

User response: Enable the node on the target serverfor replication and rerun the replication command.

ANR1903E Export export name is not defined.

Explanation: An NFS client attempted to mount thespecified name as a mount point. The specified name isnot currently being exported by the server.

System action: The server does not provide an exportof the specified directory.

User response: Ensure that an NFS ADDEXPORTcommand was issued for the specified node.

ANR1904E Missing or invalid value for option. Avalid directory needs to be defined forthis.

Explanation: The server detects a missing or invalidvalue for a server option. A valid directory needs to bedefined for this option.


User response: Correct the error and restart the server.

ANR1905E Path dir name for parm does not exist oris not empty.

Explanation: The directory specified does not exist oris not empty.


User response: Reissue the command with a validpath name.



ANR1906E Command: failed to extend the databasespace.

Explanation: A failure occurred during the extenddatabase space. This occurred during the processing ofa 'EXTEND DBSPACE' command.


User response: Review error messages to determinethe cause of the failure and retry the 'EXTENDDBSPACE' once the issue has been resolved. If unableto determine the cause of the failure or to resolve it,please contact your IBM service representative forfurther assistance.

ANR1907E The server can not resolve absolute pathof directory dir name. That path mightnot exist.

Explanation: The directory specified does not exist oris not accessible.

System action: The server operation stops.


ANR1908W Invalid value for parameter parameter -parameter valueMB. The default valuedefault valueMB is used for thisparameter.

Explanation: The value (parameter value) specified forthe (parameter) parameter is not a valid. The server usesthe default value for this parameter.

System action: Processing of the command continuesby using the default value.

User response: Verify that the correct value have beenused. Update the value, if necessary.

ANR1909W Invalid value for option name option -option valuetype. The default value defaultvaluetype is used for this option.

Explanation: The value (option value) specified for the(option) option is not valid. The server uses the defaultvalue for this parameter.



ANR1910E Directory directory name is alreadydefined for other path in the command.

Explanation: While processing the commandargument list, a duplicate path name has beenencountered.


User response: Issue the command again, specifying adirectory that is not in the argument list.

ANR1911W Invalid value for option name option -option valuetype . The default valuedefault valuetype is used for this option.

Explanation: The value (option value) specified for the(option) option is not valid. The server uses the defaultvalue for this parameter.



ANR1912I Stopping the activity log because of aserver shutdown.

System action: Stopping the activity log because of aserver shutdown.


ANR1913I command successfully started number ofprocesses IDENTIFY processes.

System action: The server successfully started theindicated number of IDENTIFY processes.

User response: Review the status of the identifyprocesses using the QUERY PROCESS or QUERYACTLOG commands.

ANR1914I command successfully ended number ofprocesses IDENTIFY processes.

System action: The server successfully ended theindicated number of IDENTIFY processes.

User response: Review the status of the identifyprocesses using the QUERY ACTLOG command.

ANR1915I Autocopy process process ID startedtransferring data to target storage poolstorage pool name.

Explanation: An autocopy process to the namedactive-data or copy storage pool has started.



ANR1916I Autocopy process process ID endedsuccessfully for storage pool storage poolname. Files Transferred: number of files,Bytes Transferred: number of bytes.

Explanation: An autocopy process to the namedactive/copy storage pool has ended successfully.





ANR1917E Autocopy process process ID failed forstorage pool storage pool name. FilesBacked Up: number of files,BytesBackedUp: number of bytes. Result code:return code.

Explanation: An autocopy process to the namedactive/copy storage pool has ended in failure.


User response: Check the activity log for messagesthat were issued prior to completion. The messagesmay give more information about the failure.

ANR1918I Autocopy process process ID stopped forstorage pool Storage pool name because ofa server error.

Explanation: An autocopy process to the namedactive-data or copy storage pool has been disabled.


User response: Check the activity log for messagesthat were issued before the process stopped. Themessages may give more information about the failure.

ANR1919W Autocopy process process ID wasdisabled for storage pool Storage poolname . At least one storage pool in thehierarchy is enabled for deduplication.

Explanation: All autocopy processes have beendisabled because at least one target storage pool isenabled for deduplication.


User response: Either disable deduplication for allstorage pools in the storage-pool hierarchy or removethe deduplicated storage pool from the autocopystorage-pool hierarchy.

ANR1920W A query for the number of HBAadapters has timed out with a currentvalue of timeout value.

Explanation: The HBAAPI function to get the numberof HBA adapters failed with a time out.


User response: Check all of the HBA adapters on thesystem and ensure that they are configured correctly.Increase the SANDISCOVERYTIMEOUT value and tryagain. If the SANDISCOVERYTIMEOUT option is notset, set it with a higher value.

ANR1921W A query for the name of an HBAadapter has timed out with a currentvalue of timeout value.

Explanation: The HBAAPI function to get a namefrom an FC adapter failed with a time out.


User response: Check all of the HBA adapters on thesystem and ensure that they are configured correctly. Ifthere is an FC adapter that is not functional, remove itfrom the system and reconfigure the HBA driver. Ifthere is no device on an FC port, increase theSANDISCOVERYTIMEOUT value and try again. If theSANDISCOVERYTIMEOUT option is not set, set it witha higher value.

ANR1922W A request to open an HBA adaptertimed out with a current value of timeoutvalue.

Explanation: The HBAAPI function to open an FCadapter failed with a time out.


User response: Check all of the HBA adapters on thesystem and ensure that they are configured correctly. Ifthere is an FC adapter that is not functional, remove itfrom the system and reconfigure the HBA driver. Ifthere is no device on an FC port, increase theSANDISCOVERYTIMEOUT value and try again. If theSANDISCOVERYTIMEOUT option is not set, set it witha higher value.

ANR1923W A query for fibre channel adapterattributes has timed out after timeoutvalue seconds.

Explanation: A request to the HBAAPI library toobtain attributes for a fibre channel (FC) adapter hasfailed to respond within the allotted time.


User response: Ensure all fibre channel adapters onthe system are configured correctly. If there is anadapter that is non-functional, remove it from thesystem. If there is no device on an adapter port,increase the SANDISCOVERYTIMEOUT value to allowthe operating system sufficient time to respond. If theSANDISCOVERYTIMEOUT option is not set, set it witha value higher than the default value.

ANR1924W A query for fibre channel (FC) portattributes has timed out after timeoutvalue seconds.

Explanation: A request to the HBAAPI library toobtain port attributes for a fibre channel (FC) adapterhas failed to respond within the allotted time.




User response: Ensure all fibre channel adapters onthe system are configured correctly. If there is anadapter that is not functional, remove it from thesystem. If there is no device attached to a particularadapter, increase the SANDISCOVERYTIMEOUT valueto allow the operating system sufficient time torespond. If the SANDISCOVERYTIMEOUT option isnot set, set it with a value higher than the defaultvalue.

ANR1925W A query for the fibre channel (FC) targetmapping has timed out after timeoutvalue seconds.

Explanation: A request to the HBAAPI library toobtain target mappings for a fibre channel (FC) adapterhas failed to respond within the allotted time.


User response: There might be too many devices to bediscovered, given the allotted time. If theSANDISCOVERYTIMEOUT option is set, increase thevalue. If the SANDISCOVERYTIMEOUT option is notset, set the option to a value higher than the defaultvalue.

ANR1926W A SCSI inquiry has timed out aftertimeout value seconds.

Explanation: A request to the HBAAPI library toquery SCSI devices has failed to respond within theallotted time.


User response: Ensure all devices connected to thefibre channel (FC) adapters are operational. Removenon-functional devices from the SAN and reconfigurethe devices on the system. If there is no device on anFC port, increase the SANDISCOVERYTIMEOUT valueand try again. If the SANDISCOVERYTIMEOUT optionis not set, set it with a value higher than the defaultvalue.

ANR1927W Autocopy process process ID stopped forstorage pool Storage pool name . The dataformat or device type was notcompatible with the data format ordevice type of the primary pool.

Explanation: An autocopy process to the namedactive-data or copy storage pool was disabled.


User response: Use the QUERY STGPOOL commandto check the data format of the storage pools. Use theQUERY DEVCLASS command to check the devicetypes of the device classes associated with the storagepools.

ANR1928W The file descriptor table for the SANdiscovery process is full.

Explanation: There might be too many paths thathave been changed and updated by the SAN discoveryprocess.


User response: Use one of the following methods toresolve this problem:

v Use the SANREFRESHTIME option to increase theamount of time elapsed before the cached SANdiscovery information is refreshed. For example:setopt sanrefreshtime 600.

v Increase the nofiles (descriptors) in ulimit andrestart the IBM Spectrum Protect server.

ANR1929E Replication of node node name to targetreplication server target server failed. Thereplication mode of the source node isSYNCSEND, and the node is notdefined on the target replication server.

Explanation: In order to replicate a node that is inSync Send mode the target node must exist on thetarget replication server and be in Sync Receive mode.

System action: The replication of the node's data fails.Server operation continues.

User response: Issue the REMOVE REPLNODEcommand for the node on the source server, and thenissue the UPDATE NODE command and specifyENABLED or DISABLED. The replication mode of thenode on the source replication server is automaticallyset to SEND after the UPDATE NODE command isissued. After issuing the command, try the replicationoperation again.

ANR1930E command: There are no eligiblefilespaces for node node name.

Explanation: The specified node has no applicablefilespaces to be processed by the command.


User response: Check the command settings for thefilespaces belonging to the node and retry thecommand.

ANR1931E command: No replication-eligible datawas found for the specified nodes andfile spaces.

System action: The operation ends.

User response: Verify that the specified nodes havedata and file spaces. Verify that replication is enabledfor data types in file spaces that you want to replicate.To determine the replication status for a file space, usethe QUERY FILESPACE command .



ANR1932I command: A NAS backup image for nodenode name, file space filespace name wasskipped for replication.

Explanation: The replication process has determinedthat a NAS backup image is not eligible for replicationbecause the image, or one of its dependent files isstored in a non-native storage pool.

System action: Replication processing continues.


ANR1933W Replication of BACKUP data for filespace filespace name on node node nameskipped because of a restore operationon target server target server.

Explanation: During replication processing, the filespace on target replication server has a pending restoreoperation. Files can not be stored into the file spacewhile the pending restore is active.

System action: The files are not replicated on thetarget replication server.

User response: Use the QUERY RESTORE commandand specify the FORMAT=DETAILED parameter todetermine if the restore operation is restartable ontarget replication server. A restartable restore operationlocks the files. The files cannot be moved until thevalue for the RESTOREINTERVAL server option isreached. Use the QUERY OPTION command to displaythe RESTOREINTERVAL value. You can lower theRESTOREINTERVAL value to remove a restartablerestore operation earlier in the replication process andto unlock the file space. Reissue the REPLICATE NODEcommand after the restore operation has completed toreplicate any remaining files.

ANR1934W REPLICATE NODE: Node node name isdisabled.

Explanation: The requested node is disabled forreplication, and has been skipped.

System action: The replication proceeds, but this nodeis skipped.

User response: Enable the node for replication usingthe UPDATE NODE command and retry theREPLICATE NODE command.

ANR1935W Session session number for node nodename (client platform) refused because theserver initialization is not complete aftertimeout value minutes.

Explanation: The specified session is refused becausethe server initialization did not complete within thespecified time.

System action: The session is ended and serverinitialization continues.

User response: Allow some time for the serverinitialization to complete and retry the session. If thismessage occurs regularly, consider increasing the valueof the SESSIONSERVERINITTIMEOUT option in theserver options file.

ANR1936E Replication of data type data for filespace filespace name (fsId filespace id) onnode node name failed with reason:reason.

Explanation: The server could not replicate thespecified file space for the reason indicated in themessage text.

System action: The command continues, butreplication of the file space fails.

User response: Review the reason for the failure andcorrect the problem, if possible. Then rerun theREPLICATE NODE command.

ANR1937I Failover Session session num for replicanode nodename (platform) is enabled forstore operations.

Explanation: The specified replica node is in failovermode and is now elgible for store operations.

System action: Any store operations request by theclient on this session will be allowed to proceed.


ANR1938W The next storage pool is no longerdefined for source pool storage pool name.

Explanation: The storage pool that is being migratedno longer has a next storage pool to migrate data to.

System action: The migration fails because there is notarget storage pool.

User response: Ensure that the storage pool beingmigrated has a next storage pool before running anyfurther migration operations.

ANR1939W Session session number for node nodename (client platform) No failover serverinformation currently exists for thisnode.

Explanation: No failover server is identified for thenode. The client removes any failover configurationthat is stored in the client options file.


User response: To ensure that failover can occur,replicate this node to a secondary server.



ANR1940E Source file(line number): Unique IDgeneration failed with Return code.

Explanation: An internal error occurred when aunique ID is created. This error message alwaysaccompanies another error message which providesmore details about the error.


User response: Review the reason for the failure andcorrect the problem, if possible.

ANR1941I Replicating option set option set namefrom source server source server name.

Explanation: A new option set which is referenced bya replicated node is is created by the replication processfrom the definition on the source replication server.



ANR1942W Option set option set name already exists.Skipping for replication from sourceserver source server name.

Explanation: A new option set which is referenced bya replicating node is not replicated because an optionset with the same name already exists on this server.The option set is not a replica of the option set for thesource server.


User response: In order to repicate the required optionset, consider copying the option set to an option setwith a different name an update the replicating node toreference the new option set.

ANR1943I Replicated option set option set namebeing updated with option set fromsource server source server name.

Explanation: An existing replicated option set on thisserver is updated with an option set with the samename from the source server.


User response: None

ANR1944I Replicating option set option set namewith option count options needed bynode referencing node to server targetserver.

Explanation: An option set on this server is replicatedto a target server because it is referenced by a nodewhich is being replicated.


User response: None

ANR1945I Option set option set name successfullyreplicated to server target server.

Explanation: An option set on this server has beensuccessfully replicated to the target server.


User response: None

ANR1946W Option set option set name already existson target server target server and is notreplicated.

Explanation: An option set on this server could not bereplicated to the target server because an option setwith the same name already exists on the target server.


User response: A node that is replicated references anoption set that exists on both the source and targetservers. Determine which option set is used on thetarget server. When you decide which option to use,rename the definition on the other server by copying itto a new option set name and deleting the originaloption set.

ANR1947E Replication of option set option set nameto target server target server failed. Seeactivity log on target server for possibleerrors.

Explanation: An error occurred on the target serverwhile replicating the specified option set.


User response: Check the activity log of the targetserver for possible errors.

ANR1948W Volume mount request for volume namedenied - server operation cannot waitfor the volume.

Explanation: If an operation acquired a volume and asecond operation waits for that same volume, the firstoperation does not wait to acquire any other volumes.If the first operation was allowed to wait for anothervolume, a deadlock could occur.

System action: Server operations continue, volumeacquisition may be tried again, including attempts tomount scratch tapes, but the server operation does notwait to acquire the volume.

User response: If the server operation succeeds, noaction is required. However, if the operation fails, youneed to supply more scratch tapes to the storage pool.



ANR1949W Session session number for node nodename (client platform) refused - the nodehas a unicode filespace but the clientdoes not use unicode.

Explanation: The server cannot accept the clientsession because the client's platform does not useunicode and the node already contains a unicodefilespace. The server records whether or not the client'sdata is unicode, and does not let the node change thisattribute.

System action: Server operation continues, but thenode session is refused.

User response: Logon to the server from a client witha platform that uses unicode data. For example, theoriginal platform that was used to create the existingfilespaces for this node. Alternatively, if the client nodeneeds to change to the platform that is currently beingattempted, remove the existing filespaces that containunicode data and try the node connection again.

ANR1950W Device type device type in device classdevice class is not supported during amigration from z/OS to AIX, or fromz/OS to Linux on System z. The deviceclass will be skipped.

Explanation: During a migration from z/OS to AIX,or from z/OS to Linux on System z, a device class wasencountered that had a device type that is notsupported on the target platform.

System action: The device class will not be added tothe target database.

User response: No action is required..

ANR1951W Device class device class uses a recordingformat format (format code) that is notsupported for device type device type.FORMAT=DRIVE will be used instead.

Explanation: During a migration from z/OS to AIX,or from z/OS to Linux on System z, a device class wasencountered that uses a recording format that is notsupported by the device type on the target platform.

System action: The recording format will be replacedwith FORMAT=DRIVE.

User response: Verify whether FORMAT=DRIVEsupports your media type. If not, update the deviceclass, specifying a supported recording format.

ANR1952I Library library name was added to thedefinition of device class device class.

Explanation: During a migration from z/OS to AIX,or from z/OS to Linux on System z, a device classdefinition was updated to include a library that will beused for accessing media through the z/OS MediaServer.

System action: The device class will be modified touse the new library.


ANR1953E command: target platform cannot be thetarget of a database upgrade from sourceplatform.

Explanation: A cross-platform database upgrade is notsupported between the indicated source and targetplatforms.

System action: The INSERTDB command stops.

User response: Rerun the INSERTDB command on asupported platform.

ANR1954W Library definition library was not sent todownlevel storage agent stagent.

Explanation: The storage agent has requested adefinition for a library type that is not supported andthe server has not sent the definition.

System action: The storage agent does not process thelibrary definition.

User response: Upgrade the storage agent to a levelthat supports the library type.

ANR1955E The level of DB2 installed on thesystem (current db2 level) is lower thanthe required level (required db2 level).

Explanation: The DB2 level on the system does notmeet the requirements for this server. The serverpackage includes the required DB2 level which isinstalled along with the server. If the DB2 level isincorrect, it is possible that DB2 failed to upgradeduring the server upgrade process.


User response: To resolve the issue, complete thefollowing steps: :

v 1. Verify the level of DB2 installed on the system:Run 'db2level'

v 2. Review the installation log files to determine theproblem that caused the DB2 upgrade failure.

v 3. Fix the problem and install the server again.

v Do not alter the DB2 software that is installed withIBM Spectrum Protect installation packages and fixpacks. Do not install or upgrade to a differentversion, release, or fix pack of DB2 software. If youare unable to fix the problem, contact IBM SoftwareSupport.



ANR1956W The password for the administratoradministrator name is expired.

Explanation: The administrator is attempting to opena session to a remote server. The password is expiredon the local server.

System action: Operation continues. The remotesession may be refused.

User response: Update the password at your earliestconvenience.

ANR1957W Command or operation: The password forthe administrator administrator name nowuses case-sensitive passwords.

Explanation: The administrator is authenticating withan LDAP directory server. The LDAP authenticationpassword policy is dictated by the LDAP directoryserver and this usually requires passwords to becase-sensitive.



ANR1958I Command: Administrator administrator IDis already registered and locked.

Explanation: An import process is trying to import anadministrator ID that is registered and locked on theserver.

System action: The process continues withoutimporting the ID.

User response: Unlock admin ID ADMIN_CENTER orlog off the administrator. Try the operation again.

ANR1959I Status monitor collecting current data attime.

Explanation: The status monitor processing iscollecting a current set of data for the server at theindicated time.

System action: The process collects the monitoredstatus data elements.

User response: The monitor status processing isenabled using the SET MONITORSTATUS command.The interval with which it collects data is controlled bythe SET STATUSREFRESHINTERVAL. If the status datais being collected too frequently, increase the collectioninterval. Note that the administrative graphical userinterface relies upon this data, do not turn off the statusmonitor processing if this interface will be used for theadministration of IBM Spectrum Protect.

ANR1960I Status monitor finished collecting dataat time and will sleep for refreshintervalminutes.

Explanation: The status monitor processing finished adata collection cycle and will sleep for the indicatednumber of minutes before waking up and attemptingto process again.

System action: The status monitor data collectionprocess is idle.

User response: The monitor status processing isenabled using the SET MONITORSTATUS command.The interval with which it collects data is controlled bythe SET STATUSREFRESHINTERVAL. If the status datais being collected too frequently, increase the collectioninterval. Note that the administrative graphical userinterface relies upon this data, do not turn off the statusmonitor processing if this interface will be used for theadministration of IBM Spectrum Protect.

ANR1961I Status monitor collector finished andexiting.

Explanation: The status monitor processing collector isterminating processing because the status monitoringfunction has been set to off.

System action: None, the status monitor collectorterminates.

User response: The monitor status processing wasturned off using the SET MONITORSTATUS command.As a result of this, the administrative graphical userinterface will not be able to manage this server.

ANR1962W command: This command is being routedto one or more servers, so its potentialeffect cannot be determined. Dependingon the parameters that you specify, thecommand can be destructive or canproduce a large amount of output.Destructive commands can halt theserver, delete data, or change dataplacement or retention policies.

Explanation: The command is destructive or producesa large amount of output.

System action: IBM Spectrum Protect prompts theuser to continue.

User response: Enter 'Y' to continue with thecommand. Enter 'N' if you do not want to continuewith the command.

ANR1963E command: This command cannot beissued from the server console.

Explanation: This command cannot be issued from theserver console because it may require a long time tocomplete and the server console should be available tocontrol other server functions.





ANR1964W command: This command may produce alarge amount of output.

Explanation: A command has been invoked that couldpotentially produce a large amount of output.


User response: Enter 'Y' to continue with thecommand or 'N' to terminate the command.

ANR1965E Command: You requested to add orremove filespace filespace name for thenode collocation group collocation groupname. Filespaces cannot be added to orremoved from node collocation groups.

Explanation: The command was issued and thespecified collocation group exists. However, thecollocation group is a node collocation group and afilespace cannot be added to or removed from a nodecollocation group.

System action: Server operations continue, but thecommand is not processed.

User response: Issue the command and specify aregistered collocation group that can contain filespacecollocation group members.

ANR1966E Command: Specify the filespace name forthe collocation group collocation groupname.

Explanation: You did not provide the filespace namefor the filespace collocation group. When you add orremove a collocation group member in a filespacecollocation group, you must provide the filespace namefor the collocation group.


User response: Issue the command again and specifythe filespace name for the filespace collocation group.

ANR1967E Command: The filespace name cannot bea wildcard character when you specifythe NAMEType parameter for afilespace collocation group.

Explanation: The command was issued, but there is amismatch between the filespace name and theNAMEType value. When you specify the NAMETypevalue, the filespace name must be partially-qualified orfully-qualified.


User response: Issue the command and specify apartially-qualified or fully-qualified filespace name incombination with the NAMEType parameter.

ANR1968E Command: The filespace name filespacename is not valid. The filespace namemust be the wildcard character whenyou specify the CODETType parameter

Explanation: The command was issued, but there is amismatch between the filespace name and theCODEType value. When you specify the CODETypevalue, the filespace name must be a wildcard character.


User response: Issue the command and specify awildcard character for the filespace name incombination with the NAMEType parameter.

ANR1969E Command: filespace name is not a validfilespace ID. Filespace IDs must benumeric values when the NAMETypeparameter is FSID.

Explanation: The command was issued, but the list offilespace IDs are not numeric. When you specify theNAMEType=FSID parameter, the filespace names in thefilespace name list must contain only numbers.


User response: Issue the command and specify a listof filespace IDs that contain only numbers.

ANR1970E Command: An invalid node name listnode name was specified. A single nodename must be specified when workingwith filespace collocation groupmembers.

Explanation: The command was issued, but the list ofnode names is invalid. When working with filespacecollocation group members, only one node name can bespecified.


User response: Issue the command and specify asingle node name.

ANR1971W Command: No matching file space wasfound for file space filespace name onnode node name using the specifiedNAMEType and CODEType parameters.

Explanation: The server did not find a matching filespace name or file space ID for the file space and node



that are specified in the command.


User response: Enter the command with file spacenames or file space IDs that refer to defined file spacesfor the specified node. Note that file space names arecase sensitive. Enter the file space names by usingexactly the same upper- and lowercase characters thatmatch the file space name that is defined on the server.File space name searches are also sensitive toNAMEType (SERVER, UNICode, FSID) and CODEType(BOTH, UNICode, NONUNIcode) parameters. Issue theQUERY FILESPACE command to determine which filespaces and file space IDs are defined for a node on theserver.

ANR1972W Command: No new file space associationswere added to the collocation group.

Explanation: The specified command was issued butno new file space associations are defined for thecollocation group.

System action: Server operations continue, but thecommand has no effect.

User response: Issue the command and specifydifferent filespaces.

ANR1973W Command: Nodes in the NODEparameter list node list may not containwildcard characters when dealing withfilespace groups. No filespaceassociations were deleted from thecollocation group.

Explanation: The specified command was issued butno file space associations are deleted.


User response: Issue the command and specify a validclient node without wildcards.

ANR1974W Command: Filespaces in the FILESPACEparameter list filespace list are notassociated with the filespace collocationgroup collocgroup name. No filespaceassociations were deleted from thecollocation group.

Explanation: The specified command was issued butno file space associations are deleted.


User response: Issue the command and specifydifferent filespaces.

ANR1975W Node node name is already associatedwith node collocation group nodecollocation group name. File spaces thatbelong to same node name cannot beadded to the user specified collocation groupcollocation group.

Explanation: This message is displayed in response tothe DEFINE COLLOCMEMBER command that is usedfor creating file space collocation group members. Nodenode name is already associated with the nodecollocation group name collocation group name and filespaces that belong to a node that is already in a nodecollocation group cannot be added to a file spacecollocation group. The indicated file spaces are notprocessed.


User response: If the node name was enteredincorrectly, issue the command again with the correctnode name.

ANR1976I Command: number of filespace members aredefined in the collocation groupcollocation group name.

Explanation: A DEFINE COLLOCMEMBER commandcreated the specified number of filespace members inthe indicated collocation group.



ANR1977I File space filespace name on node nodename is associated with filespacecollocation group collocation group name.

Explanation: This message is displayed in response tothe DEFINE COLLOCMEMBER command. File spacefilespace name on node node name is associated with thefilespace collocation group name collocation group name.



ANR1978W File space filespace name on node nodename is already associated to filespacecollocation group collocation group name.

Explanation: This message is displayed in response tothe DEFINE COLLOCMEMBER command. Filespacefilespace name is already associated with a filespacecollocation group with the name collocation group name.The indicated filespace is not processed. The otherfilespaces can be processed if specified by thecommand.


User response: If the filespace name was entered



incorrectly, issue the command again with the correctfilespace name.

ANR1979W Node node name is already associated toone or more filespace collocation groupsand cannot be associated to a nodecollocation group.

Explanation: This message is displayed in response tothe DEFINE COLLOCMEMBER command. Node nodename is already associated with at least one filespacecollocation group name. The indicated node is notprocessed. The other nodes can be processed ifspecified by the command.


User response: If the node name was enteredincorrectly, issue the command again with the correctnode name.

ANR1980I File space filespace name is disassociatedfrom filespace collocation groupcollocation group name.

Explanation: This message is displayed in response tothe DELETE COLLOCMEMBER command. Filespacefilespace name is no longer associated with the filespacecollocation group name collocation group name.



ANR1981I Command: number of filespace filespacemembers were deleted from filespacecollocation group collocation group name.

Explanation: A DELETE COLLOCMEMBER commandhas deleted the specified number of filespace membersfrom the indicated collocation group.



ANR1982W File space filespace name exists on nodenode name but the filespace is not amember of the specified collocationgroup collocation group name.

Explanation: This message is displayed in response tothe DELETE COLLOCMEMBER command. Filespacefilespace name is not associated with a filespacecollocation group with the name collocation group name.The indicated filespace is not processed. The otherfilespaces can be processed if specified by thecommand.


User response: If the filespace name was enteredincorrectly, issue the command again with the correctfilespace name.

ANR1983W The collocation group collocgroup nameexists, but the node name in theparameter list node name is notassociated with the collocation group.No filespaces are associated with thecollocation group.

Explanation: The specified command was issued butno file spaces are associated with the collocation group.


User response: Issue the command and specifydifferent nodes.

ANR1984E command: Replication server server nameis in use by an active replication processand cannot be removed.

Explanation: When you issue the REMOVEREPLSERVER command, the replication server that youspecify to remove is in use by an active replicationprocess. You cannot remove a replication server that isused in an active replication process.

System action: The command is stopped by theserver.

User response: Issue the QUERY PROCESS commandfrom the source replication server or the targetreplication server to identify active replicationprocesses. Issue the CANCEL PROCESS command fromthe source replication server to stop the replicationprocess. If running this command on a targetreplication server, log on to the source replicationserver and issue the CANCEL PROCESS command.When the replication process stops, reissue theREMOVE REPLSERVER command.

ANR1985E The remote monitoring admin adminname does not exist.

Explanation: The administrator used to monitorremote servers does not exist.

System action: Remote monitoring sessions will beended.

User response: Use the SET MONITORINGADMINcommand to set a new administrator for monitoringremote servers.

ANR1986E The remote monitoring server groupgroup name does not exist.

Explanation: The server group being remotelymonitored does not exist.

System action: Remote monitoring sessions will beended.

User response: Use the SETMONITOREDSERVERGROUP command to set a new



group for monitoring remote servers.

ANR1987E A communication error occurred duringsession session number with monitoredserver server name.

Explanation: The communication error occurred whilethe system was receiving information from thespecified monitored server.

System action: The monitoring that was in progressfailed. The server will attempt to re-establishcommunications with the monitored server.

User response: If this error occurs frequently, consultyour network administrator. Also review the activitylog on both servers for messages that are related toremote monitoring.

ANR1988W The remote monitoring session forserver server name was refused - server isdown-level.

Explanation: The specified remote server cannot bemonitored because it must be V6.3.4 or later.


User response: Upgrade the specified remote server orremove it from the remote monitoring server groupusing the DELETE GRPMEMBER command.

ANR1989W Remote monitoring of server server namecould not be started. Will retry inminutes minutes.

Explanation: An error occurred while attempting tomonitor the specified remote server.

System action: Server operation continues. Thespecified remote server is not being monitored. Theserver will attempt to start monitoring again after thespecified number of minutes.

User response: Check previous messages in theactivity log. Verify that the specified remote server isrunning and is available on the network. If you nolonger want this remote server to be monitored, removeit from the remote monitoring server group using theDELETE GRPMEMBER command.

ANR1990I Remote monitoring started for serverserver name.

Explanation: The specified remote server is now beingmonitored.



ANR1991I Remote monitoring ended for serverserver name.

Explanation: The specified remote server is no longerbeing monitored.



ANR1992E Command: The parameter parameter ismissing.

Explanation: The specified server command has beenentered without all required parameters. At least thenamed parameter is missing.



ANR1993I command has been removed.

Explanation: The specified command was a validserver command, but is no longer needed due to newcapabilities in the IBM Spectrum Protect server. Thecommand has been removed.



ANR1994I Activity log pruning started: removingdelete megabytes M based on current sizecurrent size megabytes M and retentionsetting retention size megabytes M.

Explanation: Server activity log exceeds the retentionsize by the delete megabytes specified. The activity logpruning will delete as many records as necessary toreduce the current activity log size by the deletemegabytes size.



ANR1995E Command: Invalid Formatsize value -formatsize value for device class DeviceClass

Explanation: A value was specified for the Formatsizeparameter which is larger than the maximum capacityvalue for the device class indicated in the message. Thedevice class is associated with the storage poolspecified in the DEFINE VOLUME command and is aFILE device type. The maximum capacity value of thedevice class is the limit of data that the server willwrite to the volume.


User response: Reissue the command with a



Formatsize value which is less than the maximumcapacity value of the storage pool. The maximumcapacity can be displayed with the QUERY DEVCLASSclassname F=D command.

ANR1996E Command: Invalid volume name prefix -volume name. Room for additionalcharacters is required.

Explanation: The command is being used for multiplevolume names. The suffix for the names is beinggenerated in the indicated command. When the suffixis taken into account, the specified name is too long bythe indicated number of characters. Three charactersmust be allowed for the suffix.


User response: Reissue the command with a prefixshort enough to allow for the suffix. Three extracharacters are needed for the suffix.

ANR1997E Command: The Formatsize parametermust be specified when more than 1volume is created.

Explanation: The command specified the createion ofmore than one volume with the Numberofvolumesparameter. When multiple volumes are created, theFormatsize parameter must also be specified to providethe size of the volumes. Each volume will be createdwith the same size.


User response: Reissue the command with theFormatsize parameter or define a single volumewithout the Formatsize parameter.

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.

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 the activitylog.


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.

System action: The server does not update the activitylog.


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.

System action: The server stops updating the activitylog.


ANR2010W The active log space is full. Consolemessages cannot be logged until logspace becomes available.




ANR2011W The server ran out of database spacewhile entries were being added to theactive log. Console messages will not belogged until database space becomesavailable.

Explanation: The process that monitors the consoleoutput stream and maintains the active log cannotupdate the active log because of insufficient databasespace.

System action: The server fails to update the activelog.


ANR2012W Error encountered for storage pooldirectory: STGPOOLDIRECTORY instorage pool: STGPOOL.

Explanation: The server encountered an erroraccessing the specified directory.

System action: If appropriate, the operation isattempted in another directory.

User response: Evaluate the warning and takeappropriate corrective action.

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 log



recording process. While the process is restarting, theserver may not be able to record some consolemessages in the activity log.


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. If youissued a RENAME FILESPACE command, the newfilespace name might be too long.

System action: The server command fails.

User response: Ensure that the server locale isconfigured correctly. If you issued a RENAMEFILESPACE command, consider specifying a shortername for the new filespace.

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 the commandfails with the same error, wait for server activity todecrease 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.


User response: To increase the amount of log spacethat is available to the server, evaluate the directoriesand file systems that are assigned to theACTIVELOGDIRECTORY, ARCHIVELOGDIRECTORY,

and ARCHFAILOVERLOGDIRECTORY options in thedsmserv.opt file. An out of log space condition mightoccur because the ACTIVELOGDIRECTORY location isfull.


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. For certain operations, like SQLcommands, this message can be issued when thedatabase has space, but it is unusable for the currentrequest due to the DB allocation history. In this case,the database query will show a Maximum Reduction of0.



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, restartit, and try the command again. If this problem persists,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, restartit, and try the command again. If this problem persists,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 later time.

ANR2034E Command: No match found using thiscriteria.

Explanation: The specified command has beenentered, but no objects that match the criteria can befound. In some cases when using the SELECTcommand, this message is issued when there iscontention for a record.


User response: Verify that all the specified parametervalues are correct. If a mistake is found, correct it andreissue the command. If you issued a SELECTcommand, in some cases issuing the command againwill yield a match.

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 to executethis command.


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 to executethis command. If other processes have been started forthis command, these processes may executesuccessfully.

User response: If necessary, try the command again ata 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 server



activity 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 pool type 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 or active-data type 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 in

the 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.





ANR2081E The STGPOOLDIRECTORYSTGPOOLDIRECTORY in STGPOOLSTGPOOL is full.

Explanation: The operating system reported spaceproblem with a directory.

System action: The write will be attempted to anotherdirectory.

User response: Ensure adaquate storage is assigned tothe storage pool directory or a next pool is defined.

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.



ANR2088E An I/O error ocurred while readingcontainer container name in storage poolstorage pool name.

Explanation: One or more data extents cannot beaccessed in the container.

System action: The operation fails and serveroperation continues. Depending upon the operationbeing performed, the data extent being accessed ismarked damaged so it can be repaired.

User response: For more information about the I/Oerror, see the server's First Failure Data Capture (FFDC)log. Issue the AUDIT CONTAINER command tovalidate the contents of the container. If the AUDITCONTAINER command detects damaged extents,repair the storage pool and retry the failing operation.

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 set to value formanagement by management style.

Explanation: The server activity log has been set tothe value indicated with the SET ACTLOGRETENTIONcommand for the indicated management style. If themanagement style is DATE, the value is the number ofdays that messages will be kept in the activity logbefore being deleted. If the management style is SIZE,the value is the size in megabytes that the activity log



will be allowed to occupy in the server database.



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.



ANR2097E Unable to retrieve the master encryptionkey from the server password file,password file name.

Explanation: The master encryption key could not beread from the password file in which it was stored. Thefollowing list contains possible reasons:

v The password file was created by a different serverinstance.

v The password file was created before the databasewas formatted.

v The server password changed, and the password filewas restored from a point in time prior to thechange.

System action: Server initialization continues. Datastored in encrypted storage pools cannot be retrieved.New data cannot be written to encrypted storage pools.

User response: Confirm that the correct password fileis present in the server's instance directory.

v If the server is not configured to encrypt data instorage pools either delete or rename the passwordfile. Restart the server.

v If the server database was reformatted, either deleteor rename the password file. Restart the server.

v If the server password changed, either restore thedatabase to a point in time prior to the change, orreset the password back to the previous value.

ANR2098E Command: Invalid URL specification -url.

Explanation: The specified URL is too long.


User response: Reissue the command and enter a URLvalue that is 200 characters or less.

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 processing is now restarted.

Explanation: The process that records data in theserver activity log had suspended logging messagesbecause of insufficient space in the server recovery logor database or because access to the database failed.The condition that caused the activity log processing tofail has been resolved and the activity log processing isable to resume.

System action: Activity log processing 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 is

licensed. The REGISTER NODE command will fail after120% of the licensed number of nodes have beenregistered.


User response: Use the QUERY LICENSE command todetermine 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. The



server is not halted with the HALT QUIESCEcommand. 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 a storage pool with no volumes, or with novolumes that contain data. This can also occur if thereare no volumes in the storage pool with an access stateof READWRITE or READONLY.

System action: The command ends without starting abackground process.

User response: Issue the QUERY VOLUME F=Dcommand to verify that there is at least one volume inthe storage pool that contains data, and that the storagepool volumes have an access state of READWRITE orREADONLY.

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 samestorage 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 is notchanged.


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 is notchanged.


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 specifying eitherthe NODES parameter or the DOMAINS parameter, butnot 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 specifying eitherthe NODES parameter or the DOMAINS parameter, butnot 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 only had OWNER access to the specifiednode.



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.


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 a passwordexpiration 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 nodeor administrator password.


User response: Ensure that the password adheres tonaming convention rules and meets the minimumpassword length requirement as set by youradministrator. Ensure that the new password isdifferent from the old password. If you areauthenticating to an LDAP directory server ensure thatthe new password meets all other password policyrules specified by the LDAP directory server. Reissuethe command with a valid password.

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 less contactinformation.

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.



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 and any virtual file space mappingdefinitions 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. Note that the maximum length of a unicodefile space name is eight characters less than themaximum length of a non-unicode file space name.


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 an administrator'sprivileges, but the administrator has system 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 valid enddate.

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 valid endtime.

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 with adifferent 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.

User response: To increase the amount of log space

that is available to the server, evaluate the directoriesand file systems that are assigned to theACTIVELOGDIRECTORY, ARCHIVELOGDIRECTORY,and ARCHFAILOVERLOGDIRECTORY options in thedsmserv.opt file. An out of log space condition mightoccur because the ACTIVELOGDIRECTORY location isfull.


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 updatethe administrator's date of last access due to insufficientdatabase 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 Diagnostic(ID): Transaction transaction IDwas aborted.

Explanation: An error was detected during transactioncommit that caused this transaction to be aborted. Thismessage may have been preceded by other messages



that give additional information about the failedtransaction.


User response: Check for additional messages andeliminate the condition that caused the failedtransaction. If this was encountered while the serverwas halting then this can be ignored. During serverHALT processing, existing in-flight transactions may beaborted as a normal part of server shutdownprocessing. If the error cannot be isolated and resolved,contact your service representative.

ANR2184W Diagnostic(ID): 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.


ANR2189W Diagnostic(ID): 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.

System action: The command process ends and serveroperation continues.


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.

ANR2196W An existing server password file,password file name, was found during adatabase format operation. It wasrenamed to new password file name.

Explanation: A password file already exists. The filecannot be used by the new instance of the serverdatabase. You might need it later, however, if thedatabase is restored to an earlier point in time.

System action: The password file was renamed.

User response: If the database will be restored to anearlier point in time, save the renamed password file.After the database is restored, rename the password fileto 'dsmserv.pwd' and place it in the server instancedirectory.

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 accessmode was updated to destroyed.

v The volume was empty, scratch, and offsite, and theaccess mode was changed to readwrite, readonly, orunavailable.

v The volume was scratch, not offsite, and wasemptied by DELETE FILESPACE, RECLAMATION,or RESTORE VOLUME/STGPOOL.

v The volume was an empty scratch WORM FILEvolume and deleted by RECLAMATION since theretention of the volume has expired.



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.

ANR2219E Command: Storage pool cloud url exceeds870 characters.

Explanation: The command indicated contains astorage pool cloud url that exceeds the maximumlength allowed.


User response: Reissue the command with a validstorage pool cloud url.

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 VOLUMEcommand, 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.If the volume being deleted containsdeduplicated data, the server invalidatesall files that reside in the storage poolthat are dependent upon the data storedon this volume. Files on other volumesmight be marked as damaged and resultin warning messages when that data isaccessed.

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 the volume.


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.



Alternatively, an out of log space condition might occurif there are log files in the ACTIVELOGDIRECTORYlocation that are no longer active and cannot bearchived to the ARCHIVELOGDIRECTORY and

ARCHFAILOVERLOGDIRECTORY locations. Ifnecessary, specify a larger directory for theARCHIVELOGDIRECTORY orARCHFAILOVERLOGDIRECTORY options in thedsmserv.opt file and then restart the server.

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. Ifthis 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.



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 REMOVEADMINISTRATOR command, enter 'Y' to continue or'N' to stop the process. To deal with schedules ownedby the administrator, 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 SCHEDULE commandOR 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.

ANR2240E Command: Storage pool cloud identityexceeds 255 characters.

Explanation: The command indicated contains astorage pool cloud identity that exceeds the maximumlength allowed.


User response: Reissue the command with a validstorage pool cloud identity.

ANR2241E Command: Storage pool cloud passwordexceeds 255 characters.

Explanation: The command indicated contains astorage pool cloud password that exceeds themaximum length allowed.


User response: Reissue the command with a validstorage pool cloud password.

ANR2242E Command: The cloud url for the cloudstorage pool contains no information.

Explanation: There is no valid cloud url in thiscommand.

System action: The IBM Spectrum Protect server doesnot process the command.

User response: Reissue the command with a validcloud url.

ANR2243E Command: Provide the cloud storage poolidentity.

Explanation: A cloud storage pool identity isnecessary for this command.


User response: Reissue the command with a validcloud storage pool identity.

ANR2244I Activity Summary pruning started:removing entries prior to date time.

Explanation: Server activity summary records olderthan the date and time indicated are being removedfrom the activity summary.



ANR2245I Activity summary pruning completed:number of records records removed.

Explanation: All expired (older than the summaryarchive retention value) server activity summaryrecords have been removed; the number of recordsdeleted is shown.



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.



ANR2248E Command: The cloud storage poolpassword is missing.

Explanation: A cloud storage pool password isnecessary for this command.


User response: Reissue the command with a validcloud storage pool password.

ANR2249I Storage pool storage pool name is defined.

Explanation: A DEFINE STGPOOL command hascreated the storage pool.



ANR2250E command: Operation is not allowedbecause node nodename isdecommissioned.

Explanation: You might be able to restore or retrievedata from a decommissioned client node, but youcannot store new data or alter existing data.

System action: Client sessions that attempt to storenew data or change existing data will be terminatedwith a protocol error.




ANR2251S The ACCESS setting for storage poolpoolname was changed from access toUNAVAILABLE. The pool is enabled forencryption, but the master encryptionkey for the server is not available.

Explanation: The server either does not have a masterencryption key or the master encryption key is notavailable. Encrypted storage pool data cannot be readfrom or written to the storage pool.

System action: The storage pool ACCESS setting waschanged to UNAVAILABLE.

User response: Verify that the server key database,dsmkeydb.kdb, and its password stash file,dsmkeydb.sth, exist and can be read by the server. Ifnecessary, recover the password file from a backup.

After the server password file becomes available to theserver, restart the server and issue the UPDATESTGPOOL command to change the ACCESS setting toits original value.

ANR2252S The ACCESS setting for storage poolpoolname was changed from access toUNAVAILABLE. The pool is enabled forencryption, but the master encryptionkey for the server was reset.

Explanation: The master encryption key used toprotect data in encrypted storage pools changed,possibly because the server key database,dsmkeydb.kdb, was deleted. The server cannot readexisting data that was encrypted because it no longerhas access to the encryption key used to protect thedata.

System action: The storage pool ACCESS setting waschanged to UNAVAILABLE.

User response: Rename the server key database,dsmkeydb.kdb, and its password stash file,dsmkeydb.sth, and recover an earlier version of thepassword file from a backup. Restart the server. Issuethe UPDATE STGPOOL command to change thestorage pool ACCESS setting back to its original value.

ANR2253E Command: You cannot specify theENCRYPT=YES parameter because theserver master encryption key isunavailable.

Explanation: Encryption cannot be enabled for astorage pool because the server master encryption keyis not available.


User response: Reissue the command and specifyENCRYPT=NO.

If encryption is required, review the activity log forerrors related to either the server master encryption keyor the server password file. Correct any problems thatprevent the master encryption key being read from theserver password file.

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.



ANR2255E Command: The VOLUMENAMESparameter must be specified.

Explanation: The VOLUMENAMES parameter mustbe specified to indicate the volumes that can be usedfor the command.



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 a

ANR2251S • ANR2257E


properly 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.



ANR2260W The version of IBM Spectrum Protect isnot compatible with this operatingsystem.

Explanation: The command cannot be processed onthis operating system.


User response: Use an operating system that iscompatible with IBM Spectrum Protect to issue thiscommand. For information about operating systemsthat are supported by IBM Spectrum Protect, seetechnote 1243309 "Overview - IBM Spectrum ProtectSupported Operating Systems" (http://www-01.ibm.com/support/docview.wss?uid=swg21243309).

ANR2261W The server password file, password filename, was not found. A new masterencryption key will be created andstored in a new password file.

Explanation: The master encryption key cannot beread from the password file because the file does notexist.

System action: A new master encryption key will becreated and stored in the server password file.

User response: If storage pool encryption is not inuse, no action is required.

If existing storage pools contain encrypted data, restorethe server password file. Restore it to a version thatcontains the master encryption key that was used to

protect the encrypted storage pool data. Restart theserver.

ANR2262E Unable to read from the serverpassword file, password file name; reason:error reason.

Explanation: The server could not read the masterencryption key from the server password file.


User response: Correct the problem identified in theerror reason and restart the server.

ANR2263E Unable to write to the server passwordfile, password file name; reason: errorreason.

Explanation: The server could not write the masterencryption key to the server password file.


User response: Correct the problem identified in theerror reason and restart the server.

ANR2264E Corruption detected reading from theserver password file, password file name.The master encryption key cannot beread.

Explanation: The server detected corruption in theserver password file while attempting to read themaster encryption key. The master encryption keycould not be read.


User response: Recover the password file from abackup. Restart the server.

ANR2265E The SERVERPASSWORD cannot beblank.

Explanation: Encryption does not work if thepassword is not set.


User response: Set the server password.

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.



ANR2268W ENCRYPTED value encryption value wasnot changed when theCLOUDLOCATION parameter wasupdated to cloudlocation value.

Explanation: The ENCRYPTION value does notautomatically change when you change theCLOUDLOCATION value in the UPDATE STGPOOLcommand.


User response: If you want to turn encryption off,change the ENCRYPTION value to OFF.

ANR2269E The PROTECTKEYS=NO parametercannot be specified on the SETDBRECOVERY command because oneor more storage pools are enabled forencryption.

Explanation: The SET DBRECOVERY command failedbecause PROTECTKEYS=NO was specified and one ormore storage pools are enabled for encryption.


User response: Issue the SET DBRECOVERYcommand without the PROTECTKEYS=NO parameter.

ANR2270E The PROTECTKEYS parameter is notenabled.

Explanation: The master encryption key must be setbefore you enable the PROTECTKEYS parameter.


User response: Issue the SET SERVERPASSWORDcommand to set and protect the master encryption key.

ANR2272W This command will result in thedeletion of all inventory references todamaged data in stgpool stgpool.

Explanation: A REMOVE DAMAGE command hasbeen entered.


User response: To process the REMOVE DAMAGE

command, enter 'Y' to continue or 'N' to stop theprocess.

ANR2273E A protection or replication operationfailed because a container is notavailable.

Explanation: The server cannot complete the operationbecause it cannot access data in a container.

System action: The operation fails and serveroperation continues.

User response: For details about the problem, see thefirst-failure data capture (FFDC) log for the server. Bydefault, the log is named dsmffdc.log and is in theserver instance directory. Validate the data in thecontainer that caused the problem by issuing theAUDIT CONTAINER command. If the commandresults show that the container is damaged, repair thestorage pool by using the REPAIR STGPOOLcommand. Then, retry the operation that failed.

ANR2274W Operation is not allowed because theVM backed up to filespace filespacenameis decommissioned.

Explanation: The filespace is a decommissioned VMand will not be processed by this command.

System action: Processing will continue with the nextfilesystem in the list.


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.

ANR2276W The administrative user ID administratorname matches a node name. Thematching names can cause passwordmanagement issues if you areauthenticating users with a LightweightDirectory Access Protocol (LDAP) serverin integrated mode.

Explanation: Integrated mode means that usersauthenticate with an LDAP server by using IDs that aredefined on that server. If you are using integratedmode, and have a matching administrative user ID andnode name, they resolve to a single LDAP user ID. Inthis situation, automatic password changes mightupdate the same password twice. As a result, the



password might become unknown to theadministrative user ID. Alternatively, password updateoperations might fail.

System action: System operations continue.

User response: To avoid password managementissues, complete the following steps: 1. Remove thespecified administrative user ID by using the REMOVEADMIN command. For example, if the administrator isADMIN6, issue the following command: remove adminadmin6 2. Register a different administrative user IDfor client owner operations by using the REGISTERADMIN command. For example, if the administrator isADMIN6 and you want to authenticate with an LDAPserver, issue the following command: register adminadmin6 authentication=ldap 3. Grant client ownerprivileges to the new administrative user ID by usingthe GRANT AUTHORITY command. For example, ifthe administrator is ADMIN6 and the node name isNODE2, issue the following command: grant authorityadmin6 classes=node authority=owner node=node2

ANR2277W The server master encryption key wasnot found. A new master encryption keywill be created.

Explanation: The master encryption key cannot beread, or an issue is preventing its detection.

System action: A new master encryption key will becreated and stored in the server key database.

User response: If storage pool encryption is not inuse, or if the server never had a master encryption key,no action is required.

If existing storage pools contain encrypted data,complete the following steps:

1. Restore the server key database to a version thatcontains the master encryption key that was used toprotect the encrypted storage pool data.

2. Restart the server.

ANR2278I The server master encryption key wasmoved from the server password file,password file name, to the server keydatabase.

Explanation: The master encryption key is stored in anew location. It is now stored in the server keydatabase.

System action: The server password file is deleted,and server operations continue.


ANR2279W A server password file, password filename, was found during an upgradeoperation. The file was renamed to newpassword file name.

Explanation: A server password file was found andrenamed, and its contents were moved to the serverkey database, dsmkeydb.kdb. The server password fileis no longer needed by the server. However, if youneed to restore the server database to a point in timebefore this upgrade, the password file is required.

System action: The password file was renamed, andserver operations continue.

User response: Optionally, to help ensure that theserver database can be restored to a point in timebefore this upgrade, complete the following steps:

1. Save the renamed password file.

2. After the database is restored, rename the passwordfile to dsmserv.pwd and place it in the serverinstance directory.

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.

ANR2282E Command name has already been startedfor storage pool Stgpool.

Explanation: An audit container process has alreadybeen started for the storage pool.

System action:

User response: Wait for the current audit containerprocess to complete.



ANR2283E Command: Storage pool bucket nameexceeds 63 characters.

Explanation: The command contains a storage poolbucket name that exceeds the maximum lengthallowed.


User response: Reissue the command with a validstorage pool bucket name.

ANR2284S The server master encryption key haschanged. Passwords protected with theprevious master encryption key are notavailable.

Explanation: The master encryption key used toprotect administrator and node passwords changed,possibly because the server password file was deleted.The server cannot read existing passwords that wereencrypted because it no longer has access to theencryption key used to protect the passwords.

System action: The server cannot authenticateadministrators and nodes defined with theAUTHENTICATION=LOCAL parameter.

User response: Rename the server password file andrecover an earlier version of the password file from abackup. Restart the server.

If the server password file cannot be recovered, startthe server in the foreground and issue the UPDATEADMIN or UPDATE NODE command from the serverconsole to set the password for affected administratorsand nodes, respectively.

ANR2285S The server master encryption key cannotbe read. Storage pool data andpasswords encrypted with this key willbe unavailable until the key is restoredfrom a backup.

Explanation: The master encryption key cannot beread, possibly because the server password file wasdeleted. The server cannot read existing passwords thatwere encrypted because it no longer has access to theencryption key used to protect the passwords. Theserver cannot read storage pool data that wasencrypted because it no longer has access to theencryption key used to protect the data.

System action: The server cannot authenticateadministrators and nodes defined with theAUTHENTICATION=LOCAL parameter.

User response: Recover the password file from abackup. Restart the server.

ANR2286E Command: The server master encryptionkey exists.

Explanation: A request was made to reset the servermaster encryption key, but a master encryption keyalready exists.



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 Resetting the master key will result inthe generation of a new masterencryption key; any data that wasencrypted using the previous masterencryption key will be lost.

Explanation: A request was made to reset the servermaster encryption key. The master encryption key isused to encrypt data in directory-container andcloud-container storage pools. In addition, it is used toencrypt sensitive information in the server databasesuch as administrator and node passwords. Resettingthe master encryption key will result in the loss of all



data encrypted using the old master encryption key.



ANR2291E Command: A error was encounteredwhile resetting the server masterencryption key. The error code is Errorcode.

Explanation: An error was encountered whileprocessing a request to reset the server masterencryption key.


User response: Inspect the activity log and thefirst-failure data capture log, dsmffdc.log, for errorsrelated to the command. Correct the condition leadingto the error and reissue the command.

ANR2292W The PROTECTKEYS parameter in SETDBRECOVERY is set to NO.

Explanation: The master encryption key that is usedto protect storage pool data, administrator passwords,and node passwords should be protected duringdatabase backups. The current value for thePROTECTKEYS parameter is NO, as set by the SETDBRECOVERY command.


User response: Issue the SET DBRECOVERYcommand, specifying the PROTECTKEYS=YES andPASSWORD= parameters to enable encryption keyprotection for automatic database backups.

ANR2293I Reissue the Command command andspecify the confirmation code"Confirmation Code" using the Parameterparameter.

Explanation: A request was made perform adestructive operation. Before performing the operation,the server requires that you confirm that youunderstand the risks and that you still wish to performthe operation.


User response: Confirm that you wish to perform thespecified action by reissuing the command with theprovided confirmation code.

ANR2294W Process process ID for MOVECONTAINER for container containername completed with warning ormore-severe messages issued (rc=returncode).

Explanation: The MOVE CONTAINER processcompleted with a state other than success.


User response: Review the messages in the activityand event logs that were issued by this process.Determine if the conditions that caused these messagesto be issued had an affect on the operation.

ANR2296E Command: The pool type pool type forstorage pool pool name is not compatiblewith the device class class name.

Explanation: The DEFINE STGPOOL command wasissued with conflicting pool type and device classparameters.


User response: Reissue the DEFINE STGPOOLcommand with a pool type and a device class namethat are compatible. For details about the compatibilityof storage pool types and device classes, see the helpfor the DEFINE STGPOOL command.

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.

ANR2301W No filespaces found for specifiednode(s).

Explanation: None of the node(s) specifed had afilespace.l


User response: Specify at least one node with afilespace.

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.

System action: The server does not process the HELPcommand.

User response: Issue the HELP command with nooperands and select from the numbered list (helpindex) displayed in response.

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.

System action: The server does not process the HELPcommand.


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 arenumbered 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.

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.


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 servercannot 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.


ANR2337W Header size is reset for object Object ID,verb type (Verb Type), from (Header Size)to (Verb Length).

Explanation: The header size for the specified objectwas recalculated while anditing a volume.

System action: If FIX=YES was specified, the headersize for the object will be updated. Processingcontinues.


ANR2338E Diagnostic(ID): Invalid header receivedfor object ObjectID, length Data Length.Size (Header Size), pushed (PushedLength), skipped (Skipped Length), status(New Retrieve). Found length (VerbLength), type (Verb Type), size (Verb Size).

Explanation: An invalid header was detected for thespecified object while auditing a volume. Diagnosticinformation is included in the message.

System action: If FIX=YES was specified, this objectwill be marked damaged. Processing continues.

User response: Restore the volume or storage poolthat includes this object.

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 valid

options for a volume in a primary 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 or backupset volumes.

Explanation: The DELETE DEVCLASS command hasattempted to delete a device class that has storagepools assigned to it, or is referenced by databasebackup, export volumes or backupset volumes.


User response: Issue Q DEVCLASS to view thestorage pool reference count, Q STGPOOL to determinewhich pool references the device class, and Q VOLHISTto locate database backup or export volume or



backupset 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.

ANR2359E Command: Volume name "volume name"must be specified with a DISK or FILESTGPOOL.

Explanation: The command indicated specifies thename of a volume that must be specified with a storagepool associated with a device class of type DISK orFILE.


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 a fullbackup.

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 (data type data type) has beendeleted.

Explanation: The backup set has been deleted.

System action: The server has deleted the backupset.


ANR2366I Backupset backup set name for node nodename (data type data type) would havebeen 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 (data typedata type) has been updated.

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 (data typedata type) would have been 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.


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.



ANR2380E Command: Storage pool storage pool nameis not defined.

Explanation: A nonexistent storage pool is specifiedfor the issued command.


User response: Reissue the command with a validstorage pool name. If you are using the MACROcommand to define and update the storage pool, youmust ensure that the DEFINE STGPOOL command is

committed before the UPDATE STGPOOL command isissued.

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 be



deleted, 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 or an active-data pool typepool.

Explanation: The command indicated specifies thename of a storage pool which is not a copy pool or anactive-data pool. The command syntax requires that acopy storage pool name or an active-data pool name bespecified.


User response: Reissue the command with a validcopy storage pool name or active-data pool name.

ANR2389E Command: The "option" parameter is notvalid for a primary storage pool.

Explanation: The command indicated specifies aparameter that is not valid for a primary storage pool.


User response: Reissue the command with parametersappropriate for a primary storage pool.

ANR2390E Command: The "option" parameter is notvalid for a pool type storage pool.

Explanation: The command indicated specifies aparameter that is not valid for either a copy,active-data, or copy container type storage pool.


User response: Reissue the command with parametersappropriate for the specified storage pool type.

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 youwould 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 fileautomatically, 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 volume nameto ensure it is correct. If the volume does not exist,preallocate it with the appropriate mechanism for theoperating 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.


User response: Verify that the volume is unavailableby issuing the QUERY VOLHISTORY command. If thevolume is listed in the command output, then it isbeing used and unavailable. Wait until the conflictingvolume activity has completed, and then retry thisoperation. If the volume is currently mounted, but idle,dismount it using the DISMOUNT VOLUMEcommand, and then retry the operation.

ANR2406E Command: Volume volume name stillcontains data.

Explanation: The indicated command tries to delete adata storage volume that contains data.



ANR2407W Error encountered for storage pooldirectory: STGPOOLDIRECTORY instorage pool: STGPOOL Error: Error.

Explanation: The server encountered an erroraccessing the specified directory.

System action: If appropriate, the operation isattempted in another directory.

User response: Evaluate the warning and takeappropriate corrective action.

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 specified a volume that iscurrently in use by an audit volume operation.

System action: If the command is a MOVENODEDATA command the server will skip the volumeand continues moving node data on other volumes.Other commands are not processed.

User response: Reissue the command after the auditvolume operation ends.

ANR2414E Command: Deletion operation already inprogress for volume volume name.

Explanation: The command specified a volume that iscurrently in use by a delete volume operation.


User response: Reissue the command after the deletevolume operation ends.

ANR2416E Command: Move Data operation alreadyin progress for volume volume name.

Explanation: The command specified a volume that iscurrently in use by a move data operation.


User response: Reissue the command after the movedata process ends.

ANR2418E Command: Migration operation alreadyin progress for volume volume name.

Explanation: The command specified a volume that iscurrently 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 specified a volume iscurrently in use by a reclamation operation.

System action: If the command is a MOVENODEDATA command the server will skip the volume

and continues moving node data on other volumes.Other commands are not processed.

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 (data type data type).

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 (data type data type) was notdeleted. Device class device class namewas 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 (data type data type) has not beendeleted due to error error code.

Explanation: The backup set has not been deleted.

System action: The server has not deleted thebackupset.

User response: Check related error messages.

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.

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.



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.

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.



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 the currentbackup 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 the currentrestore 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.



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.


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 server



console 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: Reissue the command and specify avalid type value.

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 the



server 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 command tofirst 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 may havebeen displayed prior to this message and correct anyproblems, if possible. For OUTFILE files, make surethat the server has proper authority to write to the fileindicated and that there is sufficient space in the filesystem for the file. On OS/390 and z/OS, make surethat the server has authority to write to the data set.

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 may havebeen displayed prior to this message and correct anyproblems, 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 VOLUMEcommand 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, issue theQUERY ACTLOG command to to view the activity logand search for the error messages. After the error hasbeen 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.

ANR2509E Command: Invalid Virtual file spacename - vfs name.

Explanation: The specified server command has beenentered with a virtual file space name that is longerthan allowed.


User response: Reissue the command with a validvirtual file space name.

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.





ANR2514E Command: Virtual file space name vfsname conflicts with file space on thenetwork attached storage (NAS) device.

Explanation: The specified server command has beenentered with a virtual file space that has the samename as a File space on the NAS device.


User response: Ensure that no virtual file spacemappings for this NAS device have the same name asan actual file space that exists on the NAS device.

ANR2515I Command: A virtual file space mappingnamed vfs name for node node name hasbeen defined.

Explanation: In response to the DEFINEVIRTUALFSMAPPING command, a virtual file spacemapping for the specified node has been defined in theserver database.



ANR2516E Command: The specified file space, fsname, does not exist on the NAS deviceassociated with the node node name.

Explanation: The specified server command has beenentered with a file space that does not exist on theassociate NAS device.


User response: Reissue the command with a valid filespace name from the NAS device.

ANR2517E Command: The virtual file space vfs nameis already defined for node node name.

Explanation: The specified command has been issuedwith a virtual file space name that has already beendefined for the indicated node.


User response: Issue the command using a virtual filespace name that has not already been defined for thisnode.

ANR2518E Command: A virtual file space mappingalready exists to the specified node, filespace and path.

Explanation: The specified command has been issuedwith a node, file space and path for which there isalready a virtual file space mapping defined.


User response: Issue the command using a file spaceand path that does not already have a mappingdefined.

ANR2519E Command: The file space, fs name, doesnot exist on the NAS device associatedwith the node node name.

Explanation: During a Backup of a virtual file spacemapping for a NAS device, the server detected that thefile space upon which the virtual file space resides doesnot exist on the associated NAS device.


User response: Use QUERY VIRTUALFSMAPPING toverify that the virtual file space mapping is definedcorrectly.

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 data classappropriate for the desired data format of the storagepool.

ANR2541E Command: The storage pool specifiedwith option "option" is not compatiblewith the option's intended use.

Explanation: The command specifies a storage poolwhose device class is a Centera device. Such storagepools are not available for use with data movementoperations such as reclaim or attributes such as copy,active-data, or reclaim storage pools.


User response: Issue the command again with astorage pool appropriate for the desired function.

ANR2542E Command: The storage pool is notcompatible with the operation'sintended use.

Explanation: The command specifies a storage poolwhose device class is a Centera device. Such storagepools are not available for use with data movementoperations, such as reclaim, or attributes, such as copyor reclaim storage pools.


User response: Issue the command again with astorage pool appropriate for the desired function.

ANR2543E Command: The volume name is notcompatible with the operation'sintended use.

Explanation: The command specifies a volume thatresides in a storage pool whose device class is aCentera device. Such volumes are not available for usewith data movement operations, such as reclaim, orattributes, such as copy or reclaim storage pools.


User response: Issue the command again with avolume appropriate for the desired function.



ANR2544E Unable to open the centera device at hlahla.

Explanation: The server cannot start communicationwith the device at the specified HLA.

System action: The transaction needing this devicefails.

User response: Verify that the hla specified in thedevice class is correct, verify that the centera device isoperational.

ANR2545E The version of the centera library,version, is not compatible with theserver.

Explanation: The centera library must be at leastversion 2 to be able to be compatible with the server.

System action: The transaction fails.


ANR2546E The centera device is not capable ofperforming the required operation,version.

Explanation: The centera device must be capable ofreading, writing and deleting objects. The device is notcapable of performing at least one of these operations.

System action: The transaction fails.


ANR2547E A Centera device (devclass) reported error"message,error" during command Centeracommand.

Explanation: The Centera device reported an errorwhile performing the specified command.


User response: Verify that the IP addresses specifiedin the device class associated with the storage pool arecorrect. Contact your service representative if theproblem persists.

ANR2548I NAS command: Renaming file spacefilespace name for node node name to filespace new filespace name.

Explanation: The NAS Backup process detected aname conflict between the Virtual file space filespacename and a file space on the NAS device associatedwith the node node name. The Virtual file space isrenamed to the new filespace name. During a NASbackup process, if the object to be backed up is aVirtual file space, IBM Spectrum Protect will verify thatthis name does not also exist as a file space on the NASdevice. If a name conflict exists, IBM Spectrum Protectwill rename the existing Virtual file space and the

associated file space definition, if one exists.

System action: NAS Backup processing for thecommand continues.

User response: None; however, users should makenote of the original Virtual file space filespace name andthe new new filespace name so that they know where thebackup data for this Virtual file space is located. Note,the RENAME FILESPACE command may be used torename the Virtual file space to a more appropriatename.

ANR2549E Command: Invalid virtual file spacename. A virtual file space mappingname must have a forward slash as thefirst character.

Explanation: The specified server command has beenentered with a virtual file space name that is does nothave a forward slash as the first character.


User response: Reissue the command with a validvirtual file space name.

ANR2550W Command: Modifying the virtual filespace mapping VFS Name for CelerraNAS device NAS device may preventdata from being recovered.If you modify this definition, save theexisting file space and path settings sothat the definition may be reverted to itsoriginal state.

Explanation: An UPDATE VIRTUALFSMAPPING hasbeen entered for a Celerra NAS device. Modifying aCelerra virtual file space defintion may prevent thedata from being recovered. If you are modifying thisdefinition in order to recover data, you should revertthe changes back to theiroriginal values after therecovery is performed.


User response: To process the UPDATEVIRTUALFSMAPPING command, enter 'Y' to continueor 'N' to stop the process.

ANR2551E Command: A virtual file space mappingfor a Celerra NAS device cannot bemodified.

Explanation: You cannot modify a virtual file spacedefintion for a Celerra NAS device. If the directory hasbeen relocated on the NAS device then create a newvirtual file space mapping to point to the new location.




User response: Define a new virtual file spacemapping for this NAS filespace and path.

ANR2552I Server now enabled for session typeaccess.

Explanation: The server has been made available foruse by the specified session types with the ENABLEcommand.



ANR2553I Server now disabled for session typeaccess.

Explanation: The server has been made unavailablefor use by the specified session types with theDISABLE command.



ANR2554I Format lfvolume process process id endedfor storage pool pool name, number ofvolumes requested volumes requested,number of volumes formatted volumesformatted.

Explanation: The FORMAT LFVOLUME process forthe storage pool shown has ended. The number ofvolumes requested to be formatted, and the number ofvolumes actually formatted are displayed.


User response: If the number of volumes formatted isless than the number of volumes requested to beformatted, check the activity log for messagesindicating the reason for the difference. Possiblereasons include the process was canceled, no morescratch volumes are allowed in the storage pool, or anerror occurred processing a scratch volume.

ANR2556W The managed server server name is notcapable of using enhanced style clientschedule schedule name in domain domainname. The domain will not bepropagated to this server.

Explanation: The managed server server name issubscribed to domain domain name that contains clientschedule schedule name that uses enhanced style syntax.The managed server is not capable of using anenhanced style schedule. Only IBM Spectrum Protectservers that are at least Version 5 Release 3 are capableof using enhanced style schedules.

System action: Server operation continues. Thedomain will not be propagated to the managed server.

User response: Consider upgrading the managed

server to at least IBM Spectrum Protect Version 5Release 3.

ANR2557W The managed server server name is notcapable of using the enhanced styleadministrative schedule schedule name.The administrative schedule will not bepropagated to this server.

Explanation: The managed server server name issubscribed to an administrative schedule that usesenhanced style syntax. The managed server is notcapable of using an enhanced style schedule. Only IBMSpectrum Protect servers that are at least Version 5Release 3 are capable of using enhanced styleschedules.

System action: Server operation continues. Theadministrative schedule will not be propagated to themanaged server.

User response: Consider upgrading the managedserver to at least IBM Spectrum Protect Version 5Release 3.

ANR2558W command: One or more managed serversthat subscribe to domain domain namewhich contains client schedule schedulename are not capable of using anenhanced style schedule.

Explanation: The client schedule schedule name usesenhanced style schedule syntax. The schedule is in adomain which is a managed object and one or more ofthe managed servers that subscribe to it are not capableof using an enhanced style schedule. Only IBMSpectrum Protect servers that are at least Version 5Release 3 are capable of using enhanced styleschedules. During configuration refresh processing, thedomain will not be propagated to managed servers thatare not capable of using it.


User response: Consider upgrading managed serversto at least IBM Spectrum Protect Version 5 Release 3.

ANR2559W command: One or more managed serversthat subscribe to administrativeschedule schedule name are not capable ofusing an enhanced style schedule.

Explanation: The administrative schedule schedulename uses enhanced style schedule syntax. Theschedule is a managed object and one or more of themanaged servers that subscribe to it are not capable ofusing an enhanced style schedule. Only IBM SpectrumProtect servers that are at least Version 5 Release 3 arecapable of using enhanced style schedules. Duringconfiguration refresh processing, The schedule will notbe propagated to managed servers that are not capableof using it.




User response: Consider upgrading managed serversto at least IBM Spectrum Protect Version 5 Release 3.

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.

ANR2568E Request for node node to start scheduleschedule at startTime is denied. Currenttime is now.

Explanation: The client scheduler attempted to startthe specified instance of a schedule for a node. Therequest was denied because that instance is still in thefuture.

System action: Server operation continues. The nodedoes not start the schedule.

User response: Check the client schedule and errorlogs for problems with the network or the preschedulecommand. Also, you may need to upgrade the client.

ANR2569E Request by node node to report results(result, code code) for schedule schedule atstartTime is denied. Current time is now.

Explanation: The client scheduler attempted to reportthe results of executing the specified schedule.However, the schedule occurs in the future. The resultswill not be saved.



System action: Server operation continues. The resultswill not be saved.

User response: Check the client schedule and errorlogs for problems with the network or the preschedulecommand. Also, you may need to upgrade the client.

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 have

been 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 theserver 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 The central scheduler has insufficientrecovery log space. The currenttransaction will be tried again in numberof seconds seconds.




ANR2575W The central scheduler has insufficientdatabase space. The current transactionwill be tried again in number of secondsseconds.

Explanation: The server suspends central schedulerprocessing because of insufficient database space.

System action: Server operation continues; thescheduler operation will be tried again after thespecified delay.




ANR2576W An attempt was made to update anevent record for a scheduled operationwhich has already been executed fornode node name.

Explanation: The server cannot update the eventrecord for the specified client node. The existing recordindicates that the scheduled operation has alreadycompleted. This can happen when two or more clientschedules are running for this node, or because theclient has retried the operation after an error hasoccurred.

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.

ANR2579E Schedule schedule name in domain domainname for node node name failed (returncode return code).

Explanation: The client reported a failure to completea scheduled action, or return code -99 was reported bythe server. One of the following return codes isdisplayed:

0 All operations were completed successfully.

4 The operation was completed, but some fileswere not processed.

8 The operation was completed with at least onewarning message.

12 The operation was completed with at least oneerror message. The count of error messagesdoes not include notifications about skippedfiles.

-99 The operation failed because the sessionbetween the client and the server ended for anunknown reason. It is unknown whether theclient can reconnect to the server to completethe scheduled event.


User response: Examine the node's schedule log todetermine the cause of the failure. To determine thefinal status of the scheduled event, issue the QUERYEVENT command.

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.

ANR2582E Command: Specified device class cannotbe used with storage pools withdifferent reclamation types.

Explanation: Storage pools can be defined withRECLAMATIONTYPE=THRESHOLD orRECLAMATIONTYPE=SNAPLOCK. A device class canonly be used with eitherRECLAMATIONTYPE=THRESHOLD orRECLAMATIONTYPE=SNAPLOCK storage pools. Anattempt was made to define a storage pool with onetype of reclamation type with a device class that isalready associated with another storage pool of theother reclamation type.


User response: Reissue the command and specifyanother device class that is referenced by storage poolswith the same reclamation type as your new storagepool. You may need to define another device class.

ANR2583E Command: Storage pool storage pool nameis not a LAN-free storage pool.

Explanation: The command indicated specifies thename of a storage pool which is not a LAN-free pool.



The command syntax requires that a LAN-free storagepoolname be specified.


User response: Reissue the command with a validLAN-free storage pool name.

ANR2584E Command: An email address exceedsmaximum characters characters.

Explanation: A REGISTER NODE or REGISTERADMIN command has been entered that specifies a listof email addresses, and one of those addresses is toolong. The maximum valid length for a single emailaddress is shown in the command.


User response: Reissue the command with a shorteremail address.

ANR2585E Command: An email address containsinvalid syntax.

Explanation: A server command has been entered thatspecifies an invalid email address. Email addressesmust be in the format "name@domain", where thename must be between 1 and 64 characters long, andthe domain must be between 1 and 255 characters long.


User response: Reissue the command with a correctemail address.

ANR2586W Setting the server name to serverNamecan adversely affect or stop operationsthat depend on communications such asfor the following purposes: OperationsCenter administration, backup-archiveclient operations, library sharing withthe library manager or library clients, orother server to server functions such asvirtual volumes, event logging, orenterprise configuration.

Explanation: The server name was changed using theSET SERVERNAME command. If the server is managed bythe Operations Center, server data might not be shown,or might be incorrect. In a virtual volumeconfiguration, renaming a source server can prevent itfrom accessing and managing data that is stored on thetarget server. Any Windows clients that are connectedto a server when its name is changed must reconnect tocontinue accessing the server.

System action: The server prompts the user tocontinue.

User response: Enter 'Y' to change the server name.

Enter 'N' to cancel the change. If you change the servername you must reconfigure all the affected componentssuch as backup-archive client operations, librarysharing with the library manager or library clients orother server to server operations. For example, if yourename an Operations Center spoke server, you mustremove it from the Operations Center and re-add it. Fora hub server, you must restart the initial configurationwizard to delete the existing server connection andcreate a new one.

ANR2587W IBM Spectrum Protect encountered azero verb on backupset volume Volumeand skipped to the next volume.

Explanation: IBM Spectrum Protect detected theproblem described in APAR PK12572 . The serveroptions file contains SKIPONZEROVERBBACKUPSETON. IBM Spectrum Protect verified there was nofurther data on the volume, and skipped to the nextvolume.


User response: If the backupset volume was writtenbefore IBM Spectrum Protect 5.2.7, or 5.3.3 was put onthe system and meets the PK12572 criteria, no action isrequired. If not, the volume has encountered a readerror, and should read again on a server without theSKIPONZEROVERBBACKUPSET ON option to get thecorrect error messages for problem determination.

ANR2588E Command: Storage pool "StgPool" cannothave CACHE set to YES with a non zeroSHRED attribute.

Explanation: Storage pools can be defined or updatedwith a non zero SHRED attribute only if the storagepool CACHE attribute is NO. Existing storage poolswith CACHE attribute of YES cannot be updated witha non zero SHRED attribute. Likewise, existing storagepools with a non zero SHRED attribute cannot beupdated with CACHE = YES. Existing storage poolswith CACHE set to YES cannot be updated with a nonzero SHRED attribute. New storage pools cannot bedefine nor can existing storage pools be modified withCACHE set to YES and a non zero SHRED value.


User response: Reissue the command and specifySHRED value of zero or CACHE = NO.

ANR2589E Backupset backup set name for node nodename (data type data type) is in use andcannot be deleted.

Explanation: The server attempted to delete thebackup set, but the operation could not be completed,because the backup set was in use by another process.





ANR2590E Command failed - SET DBRECOVERYcommand has not been issued.

Explanation: Backup DB command failed because aSET DBRECOVERY command has not been issued todefine the device class used for automatic DB backup.


User response: Issue the SET DBRECOVERYcommand to define the device class for automatic DBbackup operation.

ANR2591I Directory directory name is alreadydefined in the database space.

Explanation: This directory is already in the databasespace .


User response: Issue the command again, specifying adirectory that is not defined in the server databasespace.

ANR2592I Directory(ies) directory list has beendefined in the database space.

Explanation: Command 'EXTEND DBSPACE'successfully added new directory(ies) dir list into theserver database space.

System action:

User response:

ANR2593E Command: Storage pool storage pool nameexists but does not match thestorage-pool type that the server isattempting to process with thecommand.

Explanation: The storage pool specified does notmatch the type being processed with the command.


User response: Retry the command with a validstorage pool type specified.

ANR2594I LDAP user name set to LDAP user name.

Explanation: The LDAP user distinguished name thatthe server uses to authenticate with the LDAP serverhas been set to the value indicated with the SETLDAPUSER command.


User response: The SET LDAPPASSWORD commandis required to provide the password that correlates to

the LDAPUSER just set. This is required forcommunication with the LDAP server specified in theLDAPURL option.

ANR2595I Directory directory name is already in thelist to add to database space.

Explanation: While processing the commandargument list, a duplicate path name has beenencountered.


User response: Issue the command again, specifying adirectory that is not in the argument list.

ANR2596E There is insufficient authority to createthe database files.

Explanation: The database manager, running underthe user ID for the IBM Spectrum Protect instance, doesnot have the authority to create files in one or more ofthe database directories.


User response: Ensure that the user ID for the IBMSpectrum Protect instance has write permission to alldatabase directories. No matter which user ID isrunning the dsmserv process, the database files arewritten by the database manager. The permissions onthese database directories must allow write access fromthe database manager user ID. Change the ownershipof the database directories to the user ID for the IBMSpectrum Protect instance.

ANR2597W Node node name in domain domain namebegan schedule schedule name at actualstart and is schedule state. The periodexpired at expiration time.

Explanation: This message is displayed when a nodestarted a schedule, the period for the schedule expired,and the node has not reported results for the schedule.Possible causes are:

v processing for the action is taking longer than theschedule period

v a problem occurred while the node was performingthe scheduled action

v the node completed the scheduled action but did notreport the results to the server

System action: Server operation continues. The resultsof the scheduled operation are unknown.

User response: Administrators should consult theserver activity log and the client scheduler log, thentake corrective action if needed.



ANR2598W Administrative command scheduleschedule name started processing at actualstart and is schedule state. The periodexpired at expiration time.

Explanation: This message is displayed when anadministrative command schedule has started, theperiod for the schedule expired, and the results for theschedule have not been reported. Possible causes are:

v processing for the action is taking longer than thescheduled period

v a problem occurred while performing the scheduledaction

v a problem occurred reporting the schedule results

System action: Server operation continues. The resultsof the scheduled operation are unknown.

User response: Administrators should consult theserver activity log, then take corrective action if needed.

ANR2599W The central scheduler is unable toobtain a required lock and will retry innumber of seconds seconds.

Explanation: The server temporarily suspends centralscheduler processing because a required lock is notavailable.

System action: Server operation continues; thescheduler operation will be retried after the specifieddelay.

User response: The server workload is high. If thiscondition persists, you may need to consider adjustingthe server workload.

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 a validdescription.

ANR2602E Command: Invalid action - action.

Explanation: The specified command has been issuedwith an invalid action.


User response: Issue the command and specify a validaction.

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 a validpriority.

ANR2606E Command: Invalid start date - date.

Explanation: The specified command was issued withan invalid start date. For a schedule withACTION=DEPLOY, the specified date might be earlierthan the current system date.


User response: Reissue the command and specify avalid start date. When you define a schedule withACTION=DEPLOY, verify that the start date is notearlier than the current system date.



ANR2607E Command: Invalid start time - time.

Explanation: The specified command was issued withan invalid start time. For a schedule withACTION=DEPLOY, the specified time might be earlierthan the current system time.


User response: Reissue the command and specify avalid start time. When you define a schedule withACTION=DEPLOY, verify that the start time is notearlier than the current system time.

ANR2608E Command: Invalid duration - duration.

Explanation: The specified command has been issuedwith an invalid duration.


User response: Issue the command and specify a validduration.

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 a validvalue 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 a validperiod.

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 a validvalue 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 a validvalue 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 a validexpiration 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.



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 schedule



start 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.


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 valid valuefor 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 valid valuefor 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.

ANR2637E There is insufficient authority to createthe recovery log files.

Explanation: The database manager, running underthe user ID for the IBM Spectrum Protect instance, doesnot have the authority to create files in one or more ofthe log directories.


User response: Ensure that the user ID for the IBMSpectrum Protect instance has write permission to allactive, mirror, archive, and failover archive logdirectories. No matter which user ID is running thedsmserv process, the recovery log files are written bythe database manager. The permissions on these log



directories must allow write access from the databasemanager user ID. Change the ownership of therecovery log directories to the user ID for the IBMSpectrum Protect instance.

ANR2638W This command will delete all user dataand log files, as well as anybackup/restore history for the IBMSpectrum Protect server database. Areyou sure you want your database and allof its references removed (y or n)?

Explanation: A REMOVEDB command has beenentered.


User response: Enter 'y' to remove the database or 'n'to leave the server database.

ANR2639E Command failed - no files have beendefined for storing sequential volumehistory information.

Explanation: Sequential volume history information isrequired to restore the server data base. Because nofiles were configured for receiving this information, theoperation fails.


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.

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 valid value.

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, isdecommissioned or does not belong tothe specified domain.

Explanation: This command cannot be processed forthe indicated node. The specified node must beregistered to the server, and assigned to the requireddomain. The node cannot be decommissioned.

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.

ANR2656E Command: Invalid schedule styleschedStyle.

Explanation: The specified command has been issuedwith an invalid schedule style.




User response: Issue the command and specify a validschedule style.

ANR2657E Command: Invalid month month.

Explanation: The specified command has been issuedwith an invalid month.


User response: Issue the command and specify a validmonth.

ANR2658E Command: Invalid day of month month.

Explanation: The specified command has been issuedwith an invalid day of month.


User response: Issue the command and specify a validday of month.

ANR2659E Command: Invalid week of month month.

Explanation: The specified command has been issuedwith an invalid week of month.


User response: Issue the command and specify a validweek of month.

ANR2660E Command: Invalid combination ofenhanced schedule parameters or theirvalues: parm1 and parm2.

Explanation: The specified command has been issuedwith an invalid combination of the DAYOFMONTH,WEEKOFMONTH, and DAYOFWEEK parameters.WEEKOFMONTH and DAYOFWEEK cannot bespecified with DAYOFMONTH. WEEKEND orWEEKDAY must be specified with the FIRST or LASTweek of month.



ANR2661E Command: Invalid combination ofenhanced schedule parameters or theirvalues, parm1 and parm2, found forschedule name.

Explanation: The specified update command has beenissued with either an invalid combination ofparameters or their values, or a specified parameter or

value is not compatible with an option that is not beingupdated for the existing schedule. WEEKOFMONTHand DAYOFWEEK must not be specified withDAYOFMONTH. WEEKEND or WEEKDAY must bespecified with the FIRST or LAST week of month.


User response: To see the options for the existingschedule, issue: QUERY SCHEDULEFORMAT=DETAILED for the client or administrativeschedule. Determine if the error was caused by one ofthe following:

v a conflict between parameters to the updatecommand.

v a conflict between a parameter specified with theupdate command and a value that already exists forthe schedule.

For the latter problem, also update the existing optionthat is causing the problem. Correct the updatecommand and issue it again.

ANR2662I (*) "Query schedule format=standard"displays an asterisk in the day of weekcolumn for enhanced schedules. Theperiod column is blank. Issue "queryschedule format=detailed" to displaycomplete information about anenhanced schedule.

Explanation: This message explains the standarddisplay for an enhanced schedule.


User response: Issue "query schedule format=detailed"to display information about an enhanced schedule.

ANR2663I Command: resetting existing optionsoptions for schedule name to defaultvalues. .

Explanation: The update schedule command has resetexisting options for the schedule to default values. Thechange is required by the parameters specified with theupdate or audit commands.



ANR2664E Command: Invalid parameter parm forschedule style schedule style.

Explanation: A specified parameter is not valid for theschedule style.


User response: Issue the command and withparameters valid for the schedule style.



ANR2665W Command: Invalid month and day, monthday, detected.

Explanation: The specified command has been issuedwith an invalid combination of MONTH andDAYOFMONTH. If one month and one day werespecified in the command, the command will fail. Ifthere is at least one valid month and day combination,the schedule will be defined and run on the validdates. The schedule will skip the invalid month andday combinations.


User response: Determine the correct day and monthcombinations. If the command failed, issue the definecommand again. If the schedule was defined, use theupdate command to change the month and day values.

ANR2666W Command: Invalid month and day, monthday, detected for schedule name.

Explanation: The specified update command has beenissued with either an invalid combination of MONTHand DAYOFMONTH, or a specified MONTH orDAYOFMONTH value is incompatible with a MONTHor DAYOFMONTH value that is not being updated forthe existing schedule. If there is just one month andone day combination and that combination is invalid,the command will fail. If there is at least one validmonth and day combination, the schedule will beupdated and run on the valid dates. The schedule willskip the invalid month and day combinations.


User response: To see the options for the existingschedule, issue "q sched f=d" for the client oradministrative schedule. Determine the correct day andmonth combinations. If the the command failed, issuethe update command again.

ANR2667W Audit volume process has skippedvolume volume name due to an error.

Explanation: During processing of an AUDITVOLUME command for the volume shown, anunrecoverable error occurred on the volume.

System action: The AUDIT VOLUME command hasskipped the volume shown.

User response: Examine messages that werepreviously issued that explain the cause of the failureand correct the error if possible. Once the error hasbeen corrected, reissue the command.

ANR2668I The deduplication-verification level isset to percent.

Explanation: This message is displayed when theserver command SET DEDUPVERIFICATIONLEVEL isissued. Setting the deduplication-verification level helps

ensure that the client is not making a security attackagainst the server.



ANR2669E The specified deduplication-verificationlevel is invalid.


User response: Specify a value 0 - 100 for thiscommand.

ANR2670E Export command: Invalid value forSCHEDSTYLE 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 theSCHEDSTYLE parameter for schedule schedule name indomain domain name.

System action: Export processing continues, but theexported data contains an unknown SCHEDSTYLEvalue for this schedule. If this data is imported, thedefault or existing SCHEDSTYLE value is used.

User response: Update the SCHEDSTYLE value forthis schedule and restart the export command.Alternatively, use the export data with the unknownvalue, and check and update the SCHEDSTYLE valueafter import processing has been performed.

ANR2671E Export command: Invalid value forSCHEDSTYLE 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 theSCHEDSTYLE parameter for administrative scheduleschedule name.

System action: Export processing continues, but theexported data contains an unknown SCHEDSTYLEvalue for this schedule. If this data is imported, theserver uses the default or existing SCHEDSTYLE value.

User response: Update the SCHEDSTYLE value forthis schedule and restart the export command.Alternatively, the export data with the unknown valuecan be used, and the SCHEDSTYLE value can bechecked and updated after import processing has beenperformed.



ANR2672E Import command: Invalid value forSCHEDSTYLE parameter in exporteddata for schedule schedule name indomain domain name.

Explanation: During preview processing of commandimport command, an invalid value is encountered for theSCHEDSTYLE 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 SCHEDSTYLE value is used.

User response: If the data is imported with a latercommand, verify that the correct SCHEDSTYLE valueis used for this schedule.

ANR2673E Import command: Invalid value forSCHEDSTYLE parameter in exporteddata - schedule schedule name in domaindomain name defined with defaultSCHEDSTYLE value.

Explanation: During processing of command importcommand, an invalid value is encountered for theSCHEDSTYLE parameter for schedule schedule name inpolicy domain domain name.

System action: Processing of the command continues,by using the default SCHEDSTYLE value for thisschedule.

User response: Verify that the correct SCHEDSTYLEvalue has been used for this schedule. Update thisvalue, if necessary.

ANR2674E Import command: Invalid value forSCHEDSTYLE parameter in exporteddata - existing SCHEDSTYLE value forschedule schedule name in domain domainname was not updated.

Explanation: During processing of command importcommand, an invalid value is encountered for theSCHEDSTYLE parameter for schedule schedule name inpolicy domain domain name.

System action: Processing of the command continues,by using the existing SCHEDSTYLE value for thisschedule.


ANR2675E Import command: Invalid value forSCHEDSTYLE parameter in exporteddata for administrative schedule schedulename.

Explanation: During preview processing of commandimport command, an invalid value is encountered for the

SCHEDSTYLE 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 SCHEDSTYLE value isused.

User response: If the data is imported with a latercommand, verify that the correct SCHEDSTYLE valueis used for this schedule.

ANR2676E Import command: Invalid value forSCHEDSTYLE parameter in exporteddata - administrative schedule schedulename defined with defaultSCHEDSTYLE value.

Explanation: During processing of command importcommand, an invalid value is encountered for theSCHEDSTYLE parameter for administrative scheduleschedule name.

System action: Processing of the command continues,by using the default SCHEDSTYLE value for thisschedule.


ANR2677E Import command: Invalid value forSCHEDSTYLE parameter in exporteddata - existing SCHEDSTYLE value foradministrative schedule schedule namewas not updated.

Explanation: During processing of command importcommand, an invalid value is encountered for theSCHEDSTYLE parameter for administrative scheduleschedule name.

System action: Processing of the command continues,by using the existing SCHEDSTYLE value for thisschedule.


ANR2678E Server database format failed.

Explanation: A failure occurred during the format ofthe IBM Spectrum Protect server database. Thisoccurred during the processing of a 'DSMSERVFORMAT' command.

System action: Server format processing terminates.

User response: Review error messages to determinethe cause of the failure and retry the 'DSMSERVFORMAT' once the issue has been resolved.



ANR2679E Command: All of the nodes provided areinvalid.

Explanation: While verifying the parameters of thespecified command, no valid node was found.


User response: Verify that the nodes specified arecorrect and all are registered. Then, reissue thecommand.

ANR2680E Command: You cannot specify TOC=YESwhen TYPE is SNAPMIRROR.

Explanation: A SnapMirror backup was attemptedwhile specifying TOC=YES. Network ApplianceSnapMirror backups do not support TOC creation.


User response: Reissue the command withoutspecifying TOC=YES.

ANR2681E Command: The file server movername doesnot support SnapMirror-to-Tapeoperations or is not running NDMPVersion 4.

Explanation: A SnapMirror backup was specified witha NAS device that does not Network ApplianceSnapMirror backup operations.


User response: Reissue the command by specifying astandard NDMP full or differential backup. .

ANR2682E Command: You cannot specifyMODE=DIFF when TYPE isSNAPMIRROR.

Explanation: A SnapMirror backup was attemptedwhile specifying MODE=DIFF. Network ApplianceSnapMirror backups may only be full image backups.


User response: Reissue the command and do notspecifiy MODE=DIFF with TYPE=SNAPMIRROR.

ANR2683I Command: A Table of Contents will notbe created for a SnapMirror backup.

Explanation: A Netapp SnapMirror backup wasrequested and the TOC parameter is set toPREFERRED. The backup will continue, however noTable of Contents will be created.



ANR2684E Command: SnapMirror operations are notsupported on NAS virtual filespacedefinitions.

Explanation: A SnapMirror backup or restore wasattempted on a NAS virtual filespace. NetworkAppliance SnapMirror backups do not supportdirectory level backup, therefore a virtual filespace maynot used with TYPE=SNAPMIRROR.


User response: Reissue the command by specifyingTYPE=DUMPIMAGE.

ANR2685I SnapMirror backup of NAS nodenodename, file system file system, startedas process process ID by administratoradministrator.

Explanation: A SnapMirror backup is started for theindicated file system of a NAS node. The operation isinitiated by the administrator shown.



ANR2686I SnapMirror Restore of NAS nodenodename, file system filesystem, started asprocess process ID by administratoradministrator. A full image for this filesystem will be restored to destinationdestination.

Explanation: A SnapMirror restore is started for theindicated file system of a NAS node. The operation isinitiated by the administrator shown. The restore willbe performed using a full image of this file system. Thefile system will be restored to the indicated destination.



ANR2687E Command: You cannot specify aFILELIST when TYPE isSNAPMIRROR.

Explanation: A file level restore was attempted from aSnapMirror backup. Network Appliance SnapMirrorbackups do not support file level restore.


User response: Reissue the command without theFILELIST parameter.

ANR2688E Command: The SnapMirror Restore ofNAS node nodename, file system filesystem, cannot be started. Thedestination file system destination is notset to "Restricted" on the NAS device.



Explanation: While verifying the parameters of thespecified command, no valid node was found.


User response: Verify that the nodes specified arecorrect and all are registered. Then, reissue thecommand.

ANR2689W Command: The dataformat of thedatamover data mover is incompatiblewith the NAS device with hostidentifier hostId.

Explanation: The dataformat provided in thecommand is not compatible with the NAS devicewhich is associated with the high level address. wasfound.

System action: The server completes the command.

User response: Determine the proper dataformat foryour NAS device and reissue the command.

ANR2690E Command: The file system file system is inrestricted state and cannot be used in anNDMP backup or restore operation.

Explanation: A NAS file system that is in therestricted state was specified for an NDMP backup orrestore operation. You cannot perform an NDMPbackup or restore of a file system in the restricted state.


User response: Refer to your NAS device'sdocumentation on how to unrestrict the file system.Then, reissue the command.

ANR2691E Command: The file server file server name ,does not support the NDMP ClusterAware Backup extension and thedatamover type requires it.

Explanation: A datamover of type NASCLUSTER orNASVSERVER was defined however, the file serverdoes not support the NDMP Cluster Aware Backupextension.

System action: The IBM Spectrum Protect serverdefine operation on the file server fails.

User response: Verify that the file server is runningclustered Data OnTap from Netapp.

ANR2692E Command: Invalid subaction - action.

Explanation: The specified command has been issuedwith an invalid subaction.


User response: Issue the command and specify a validsubaction.

ANR2693E Command: Invalid action and subactioncombination.

Explanation: The specified command has been issuedwith an invalid combination of action and subactionvalues.



ANR2694E Command: Action must be specifed withsubaction.

Explanation: The specified command has been issuedwith a subaction and no action value.



ANR2695E The deduplication mode for node nodename was set to SERVERONLY.

Explanation: The server detected a potential securityattack and disabled client-side deduplication.

System action: Server and client operations continue.

User response: Verify that the client workstation doesnot have any applications that are attempting a securityattack on the server. If the client is secure, re-enableclient-side deduplication on the node by issuing theserver command UPDATE NODE with theDEDUPLICATION=CLIENTORSERVER parameter.

ANR2696E Export command: Invalid value forSUBACTION 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 SUBACTIONvalue for this schedule. If this data is imported, thedefault or existing SUBACTION value is used.

User response: Update the SUBACTION value for thisschedule and restart the export command. Alternatively,use the export data with the unknown value, and checkand update the SUBACTION value after importprocessing has been performed.



ANR2697E Import command: Invalid value forSUBACTION parameter in exporteddata - schedule schedule name in domaindomain name defined with defaultSUBACTION value.

Explanation: During processing of command importcommand, an invalid value is encountered for theSUBACTION parameter for schedule schedule name inpolicy domain domain name.

System action: Processing of the command continues,by using the default SUBACTION value for thisschedule.

User response: Verify that the correct SUBACTIONvalue has been used for this schedule. Update thisvalue, if necessary.

ANR2698E Import command: Invalid value forSUBACTION parameter in exporteddata - existing SUBACTION value forschedule schedule name in domain domainname was not updated.

Explanation: During processing of command importcommand, an invalid value is encountered for theSUBACTION parameter for schedule schedule name inpolicy domain domain name.

System action: Processing of the command continues,by using the existing SUBACTION value for thisschedule.

User response: Verify that the correct SUBACTIONvalue has been used for this schedule. Update thisvalue, if necessary.

ANR2699E Import command: Invalid value forSUBACTION parameter in exporteddata for schedule schedule name indomain domain name.

Explanation: During preview processing of commandimport command, an invalid value is encountered for theSUBACTION 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 SUBACTION value is used.

User response: If the data is imported with a latercommand, verify that the correct SUBACTION value isused for this schedule.

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 centralscheduler 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: To increase the amount of log spacethat is available to the server, evaluate the directoriesand file systems that are assigned to the



ACTIVELOGDIRECTORY, ARCHIVELOGDIRECTORY,and ARCHFAILOVERLOGDIRECTORY options in thedsmserv.opt file. An out of log space condition mightoccur because the ACTIVELOGDIRECTORY location isfull.


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.



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 that theclient scheduler is not using an invalid address,obtained at the time the client scheduler was started,from either the client's options file or from thecommand line. Verify that the client scheduler for nodenode name is running and that the necessarycommunication links to that scheduler are operational.Firewalls must allow traffic from the server to the clientand from the client to the server without the sessiontiming out. Ensure that the DNS configuration iscorrect.

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.

ANR2719E Command: Invalid parameter parm forACTION=DEPLOY.

Explanation: A parameter that is specified is not validfor ACTION=DEPLOY.

System action: Server operations will continue, butthe command is not processed.

User response: Reissue the command with validACTION=DEPLOY parameters.

ANR2720E Command: Node node name is currentlybeing replicated.

Explanation: The command shown specifies a nodethat is currently being replicated to another server.


User response: Reissue the command at a later time,or if necessary, cancel the current replication andreissue the command.

ANR2721E A non-replication SSL session toaddress address is requested.

Explanation: A non-replication SSL session to theindicated address was attempted. Server-to-server SSLsessions are supported for replication only.

System action: The server does not start the session.

User response: If you want to configure the sametarget server for both SSL and non-SSLcommunications, you can configure multiple serverdefinitions when you issue the DEFINE SERVERcommand. You can have multiple server definitionswith the same target address if the server names arenot the same.

ANR2722I The server now accepts sessions thatoriginate from server server name

Explanation: The server can now accept sessions fromthe named server.



ANR2723I The server is enabled to have outboundsessions to server server name

Explanation: The server now allows sessions targetedto the named server.





ANR2724I The server does not accept sessions fromserver server name

Explanation: The server rejects sessions from thenamed server.



ANR2725I The server is disabled for sessions withserver server name

Explanation: The server cannot initiate sessions to thenamed server.



ANR2726E Command: None of the specified nodesare configured for replication or they arepart of an active replication process.

Explanation: The replication command did not startbecause data belonging to the specified nodes wasbeing replicated, or because the nodes are notconfigured for replication.


User response: Verify that the specified nodes arecorrect and that they are configured for replication.Verify that the nodes are not part of an activereplication process. A node is configured for replicationif the replication state is ENABLED or DISABLED. Todetermine the replication state of a node, issue theQUERY NODE FORMAT=DETAILED command. Toconfigure nodes for replication, issue the UPDATENODE command. After the situation has beencorrected, reissue the REPLICATE NODE command.

ANR2727E Command: Node node name is currentlyaccessing server server name.

Explanation: The command shown specifies a nodethat has an active session with the specified server.

System action: The local server does not process thecommand.


ANR2728E Command: Node node name cannot bereplicated because it is not in the SENDor SYNCSEND mode.

Explanation: The replication mode of a specified nodeis RECEIVE or SYNCRECEIVE. To replicate, thereplication mode must be SEND or SYNCSEND.

System action: The server processes the command.

However the specified node is is skipped for thisoperation.

User response: Verify that all of the nodes to bereplicated are in SEND or SYNCSEND mode. Reissuethe command, or, if necessary, cancel the replicationprocess and reissue the command.

ANR2729W This command will register the node tonew domain domainname.Changing the domain will cause thenode to be disassociated from theschedule of original domain.

Explanation: The schedule belongs to the domain. Thenode will be disassociated from the schedule if thenode is registered to new domain.

System action: IBM Spectrum Protect prompts theuser to continue.

User response: Enter 'Y' to change the domain. Enter'N' if you do not want to change the domain.

ANR2730I Default authentication set to defaultAuth.

Explanation: This message is displayed in response tothe Set DEFAULTAUTHentication command. Itindicates the current default AUTHENTICATION valuefor the REGISTER NODE and REGISTER ADMINcommands.



ANR2731E An invalid command was issued: issuedcommand. The command prerequisitecommand must be issued first.

Explanation: The specified server command wasissued prior to another required command.


User response: Issue the required command and thenreissue the command that caused the error.

ANR2732E Unable to communicate with theexternal LDAP directory server.

Explanation: The server tried to communicate withthe external LDAP directory server but was unable todo so.


User response: Validate that the external LDAPdirectory server is actively running. Also, validate thatthe LDAPURL option is set appropriately and refers toa valid LDAP directory server.



ANR2733W Unable to authenticate with the externalLDAP directory server to process theSET LDAPUSER command.

Explanation: The LDAPUSER value or theLDAPPASSWORD value or both are invalid.

System action: The server command continues.

User response: During the SET LDAPUSER command,the IBM Spectrum Protect server tried to authenticate tothe external LDAP directory server. If theLDAPPASSWORD is not set or is invalid, theauthentication fails, but the SET LDAPUSER commandsucceeds. The LDAPUSER value and theLDAPPASSWORD value both must be set correctlybefore the server can communicate with the externalLDAP directory server. The SET LDAPPASSWORDcommand fails if authentication with the externalLDAP directory server fails with the currentLDAPUSER and new LDAPPASSWORD.

You can validate the current LDAPUSER by issuing theQUERY STATUS command. The LDAPUSER andLDAPPASSWORD commands can be corrected with theappropriate SET commands. If there is still anauthentication error, validate that the user andpassword are set correctly in the external LDAPdirectory server.

ANR2734E Unable to authenticate with the externalLDAP directory server to process theSET LDAPPASSWORD command.

Explanation: The LDAPUSER value or theLDAPPASSWORD value or both are invalid.

System action: The server command fails.

User response: You can validate the currentLDAPUSER by issuing the QUERY STATUS command.The LDAPUSER and LDAPPASSWORD commands canbe corrected with the appropriate SET commands. Ifthere is still an authentication error, validate that theuser and password are set correctly in the externalLDAP directory server.

ANR2735W Renamed node node name must beupdated with the current password.

Explanation: In response to a RENAME NODEcommand to a node that uses LDAP authentication, thenode was renamed in the IBM Spectrum Protectdatabase, but an LDAP entry does not exist for the newname in the LDAP directory server. This can happenbecause the SYNCLDAPDELETE=NO parameter wasused or an LDAP entry did not exist for the originalname.


User response: Issue the UPDATE NODE command tothe renamed node using the current password, beforeattempting any sessions with the node.

ANR2736W Renamed administrator admin name mustbe updated with the current password.

Explanation: In response to a RENAME ADMINcommand with an admin that uses LDAPauthentication, the admin was renamed in the IBMSpectrum Protect database, but an LDAP entry does notexist for the new name in the LDAP directory server.This can happen because the SYNCLDAPDELETE=NOparameter was used or an LDAP entry did not exist forthe original name.


User response: Issue the UPDATE ADMIN commandto the renamed admin using the current password,before attempting any sessions with the admin.

ANR2737E Command: All of the admins providedare invalid.

Explanation: While verifying the parameters of thespecified command, no valid admin was found.


User response: Verify that the admins specified arecorrect and all are registered. Then, reissue thecommand.

ANR2738W Command: parameter conflicts withparameter - conflicting parameter.

Explanation: Conflicting parameters were specified inthe command.

System action: The server bypasses the conflictingparameter and processing continues.

User response: Verify which parameter you want touse and reissue the command, if necessary. If thecommand needs to be reversed, undo the command,correct the syntax, and then reissue the command.

ANR2739I Audit LDAP directory started as processprocess ID.

Explanation: A background process was started toaudit the LDAP directory entries. The audit wasassigned the process ID shown.

System action: The audit process starts and serveroperation continues.

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



ANR2740E Alert monitor could not start or hasfailed and stopped.

Explanation: The server alert monitor is not able tostart or continue processing.

System action: The alert monitor is not able to run.

User response: Evaluate other messages in the activitylog to determine why the alert monitor is unable torun. This is typically caused by insufficient resourcessuch as a lack of memory or other system resources.

ANR2741I Alert monitor has started.

Explanation: The server alert monitor has startedsuccessfully and will evaluate messages to determineand raise alerts for administrative notification wherenecessary.



ANR2742W Command: Has been submitted forapproval consideration.

Explanation: The command has not been executed.The command has been recorded for approvalconsideration. Contact the primary or alternateapproval administrators for consideration anddisposition of this request. If the command is notapproved prior to the approval duration period, it willbe deleted and the command itself will not beexecuted.

System action: The server does not process thecommand. The command is recorded for pendingapproval. Issue QUERY PENDINGCOMMAND to seethe request.

User response: Contact the primary or alternateapproval administrators to disposition this request. Ifapproval is granted, the approval administrator willre-issue the command as part of the approvalprocessing. And if the command is rejected, it will bedeleted and no further action taken.

ANR2743I Approval processing for request requestIdto process Command issued byadministrator administrator is successful;command completed.

Explanation: The command was submitted for thedesignated administrator and has successfully run tocompletion.


User response: Review the activity log for thecommand processed.

ANR2744W Approval processing for request requestIdto process Command issued byadministrator administrator failed;command execution was not successful.

Explanation: The command was submitted for thedesignated administrator but failed to run successfully.

System action: The pending command entry isremoved and the command needs to be re-issued bythe originating administrator.

User response: Review the activity log for thecommand processed.

ANR2745I AUDIT LDAPDIRECTORY commandfinished: admin only LDAP administratorentries are only in the LDAP directoryserver (not in the IBM Spectrum Protectserver), number administrator entries areonly in the IBM Spectrum Protect server(not in the LDAP directory server), nodeonly LDAP node entries are only in theLDAP directory server (not in the IBMSpectrum Protect server), number nodeentries are only in the IBM SpectrumProtect server (not in the LDAPdirectory server), and total deleted entriesentries were deleted from the LDAPserver in total.

Explanation: The inconsistencies between the LDAPdirectory server and the IBM Spectrum Protect serverare displayed as a result of the AUDITLDAPDIRECTORY command.



ANR2746W Node node name was located in thedatabase but not in the LDAP directoryserver.

Explanation: An inconsistency between the LDAPdirectory server and the IBM Spectrum Protect databasewas discovered. A node in the IBM Spectrum Protectdatabase a does not have a corresponding entry in theLDAP directory server. Without an entry in the LDAPdirectory server, the node is inaccessible until action istaken. See the user response for recommended action.


User response: To make the node accessible, you needto add the node to the LDAP directory server. Issue theUPDATE NODE command with a password to createan LDAP node entry in the LDAP directory server.



ANR2747W Administrator admin name was located inthe database but not in the LDAPdirectory server.

Explanation: An inconsistency between the LDAPdirectory server and the IBM Spectrum Protect databasewas discovered. An administrator in the IBM SpectrumProtect database a does not have a corresponding entryin the LDAP directory server. Without an entry in theLDAP directory server, the administrator is inaccessibleuntil action is taken. See the user response forrecommended action.


User response: To make the administrator accessible,you need to add the administrator to the LDAPdirectory server. Issue the UPDATE ADMIN commandwith a password to create an LDAP administrator entryin the LDAP directory server.

ANR2748W Node node name was located in theLDAP directory server but not in thedatabase.

Explanation: An inconsistency between the LDAPdirectory server and the IBM Spectrum Protect databasewas discovered. An unexpected node entry was foundin the LDAP directory server. An extra entry in theLDAP directory server does not affect IBM SpectrumProtect server operations. If the LDAP directory serveris shared by multiple IBM Spectrum Protect servers, theextra entry might be needed for one or more of theother IBM Spectrum Protect servers.

System action: If the AUDIT LDAPDIRECTORYcommand is issued with FIX=YES, the server deletesthe node entry from the LDAP directory server. If thecommand is issued with FIX=NO, the server does notdelete the entry.


ANR2749W Administrator admin name was located inthe LDAP directory server but not in thedatabase.

Explanation: An inconsistency between the LDAPdirectory server and the IBM Spectrum Protect databasewas discovered. An unexpected administrator entrywas found in the LDAP directory server. An extra entryin the LDAP directory server does not affect IBMSpectrum Protect server operations. If the LDAPdirectory server is shared by multiple IBM SpectrumProtect servers, the extra entry might be needed for oneor more of the other IBM Spectrum Protect servers.

System action: If the AUDIT LDAPDIRECTORYcommand is issued with FIX=YES, the server deletesthe administrator entry from the LDAP directory server.If the command is issued with FIX=NO, the server doesnot delete the entry.


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

ANR2759I Command: The virtual file spacedefinition vfs name for node node namehas been deleted.

Explanation: In response to the DELETEVIRTUALFSMAPPING command, the virtual file spacemapping vfs name for the node node name has beendeleted in the server database.



ANR2760E Command: Unable to delete the virtualfile space definition vfs name for nodenode name. A file space definition existswith the same name.

Explanation: The DELETE VIRTUALFSMAPPINGcommand has been entered, but the specified virtualfile space mapping vfs name for the node node name hasan associated file space definition in server database.


User response: To delete the virtual file spacedefinition, first delete the filespace definition with thesame name.

ANR2761E Command: The deployment repositorydirectory cannot be updated at this time:Deploy Manager is active.

Explanation: The SET DEPLOYREPOSITORYcommand was issued while the deploy manager isactive.


User response: Reissue the command at a later time.Alternatively, issue the SET DEPLOYPKGMR OFFcommand, and then reissue the SETDEPLOYREPOSITORY command.

ANR2762I Command: A virtual file space mappingnamed vfs name for node node name hasbeen updated.

Explanation: In response to the UPDATEVIRTUALFSMAPPING command, a virtual file spacemapping for the specified node has been updated inthe server database.



ANR2763E Command: The hexadecimal stringentered for the path parameter is notvalid.

Explanation: The command indicated specifies aninvalid Hexadecimal value for the path parameter.


User response: Check that the string representing thepath contains only valid hexadecimal characters andcontains an even number of characters. Reissue thecommand with a valid Hex string for the pathparameter.



ANR2764E command: Filespace filespace name cannotbe renamed to new filespace name; avirtual file space with this name alreadyexists for node node name.

Explanation: The file space name specified as a targetname for the command was found to already exist as avirtual file space for the node specified. The commandfails.

System action: Server operation continues, thecommand fails.

User response: Reissue the command with a differenttarget filespace name

ANR2765E command: The node node name has aninvalid node type for virtual file spacedefinitions; the node type must be NAS.

Explanation: A Define VirtualFSMapping commandwas entered with an invalid node type.


User response: You might want to run this commandagain, specifying a node of TYPE=NAS.

ANR2766W Command: Virtual file space name vfsname conflicts with file space on thenetwork attached storage (NAS) device.

Explanation: The specified server command has beenentered with a virtual file space that has the samename as a file space on the NAS device.


User response: Ensure that no virtual file spacemappings for this NAS device have the same name asan actual file space that exists on the NAS device.

ANR2767E Command: The data format of storagepool Storage Pool Name does not matchthe data format of storage pool StoragePool Name.

Explanation: The data format of the indicated storagepools does not match. The requested operation failed.


User response: Use QUERY STGPOOL F=D to displaythe data format for various pools and determine whichmay be eligible for the operation. Choose a storagepool that has the matching data format and re-issue thecommand.

ANR2768I Process process ID will use data moverdatamover name for the operation.

Explanation: The indicated data mover is being usedby the indicated process.

System action: The indicated data mover is beingused by the indicated process.


ANR2769E Command: Process process ID terminated -data mover inaccessible.

Explanation: The indicated process terminated for theindicated command because none of the data movers isaccessible.

System action: The indicated process terminates.

User response: Examine the previous error messagesfor possible reasons a remote session could not bestarted.

ANR2770E Command: Process process ID skippedrestoring data from volume volume namein storage pool name storage pool - drivepath unavailable.

Explanation: The indicated process skipped restoringdata from the indicated volume because none of theNAS type datamovers is available.

System action: The data in the indicated volume isnot restored.

User response: Use QUERY STGPOOL to obtain thedevice class to which the indicated source storage poolbelongs. Use QUERY DEVCLASS to obtain the librarycontaining the source storage pool. Then, use theQUERY DATAMOVER and QUERY PATH commandsto verify that at least one NAS datamover has paths tothe drives in the library.

ANR2771E Move data process terminated forvolume volume name - data moverinaccessible.

Explanation: Move data processing terminated for theindicated volume because none of the data movers isaccessible.

System action: Move data ends for the indicatedvolume.

User response: Examine the previous error messagesfor possible reasons a remote session could not bestarted.



ANR2772E Command: Process process ID terminated -drive path or data mover unavailable.

Explanation: The indicated process terminated for theindicated command for one of the following reasons:

v None of the data movers with paths to the drives inthe library containing the source storage pool isavailable.

v None of the data movers with paths to the drives inthe library containing the target storage pool isavailable.


User response: Use QUERY STGPOOL to obtain thedevice class to which the source or target storage poolbelongs. Use QUERY DEVCLASS to obtain the libraryname that contains the source or target storage pool.Then, use the QUERY DATAMOVER and QUERYPATH commands to verify that at least one data moverhas paths to the drives in the library.

ANR2773E Move data process terminated forvolume volume name - drive path or datamover unavailable.

Explanation: MOVE DATA processing terminated forthe indicated volume for one of the following reasons:

v None of the data movers with paths to the drives inthe library containing the source storage pool isavailable.

v None of the data movers with paths to the drives inthe library containing the target storage pool isavailable.


User response: Use QUERY STGPOOL to obtain thedevice class to which the source or target storage poolbelong. Use QUERY DEVCLASS to obtain the libraryname that contains the source or target storage pool.Then, use the QUERY DATAMOVER and QUERYPATH commands to verify that at least one data moverhas paths to the drives in the library.

ANR2774E Command: Process process ID terminated -data format mismatch.

Explanation: During restore processing, a data formatmismatch occurred between the storage pool beingrestored and the copy storage pool.

System action: The indicated restore processterminates.

User response: Examine the previous error message todetermine the name of the copy storage pool used forthe restore. If possible, specify a copy storage pool thathas the same data format as the storage pool beingrestored on the restore command.

ANR2775W Command: Process Process id encounteredan output error. File on volume volumename skipped - Node node name, type filetype, file space filespace name, file namefile name, fsId filespace id.

Explanation: During copy or move operation, anoutput error was encountered. The indicated file wasskipped.

System action: The file will not be processed.

User response: If possible, correct the error and re-runthe command.

ANR2776W Transaction failed for session sessionnumber for node node name (clientplatform) - A storage pool for the targetdestination is associated with acontainer or cloud storage pool.

Explanation: The specified session fails because aninvalid storage pool is used to store the virtual volume.


User response: Ensure that container and cloudstorage pools are not used with virtual volumes. TheUPDATE COPYGROUP command can be used toupdate the copy group destination to point to a validstorage pool.

ANR2777I REPLICATE NODE: Node node name isdecommissioned and disabled.

Explanation: The requested node is decommissioned,disabled for replication, and has been skipped.

System action: The replication proceeds, but this nodeis skipped.


ANR2778I Command: Inventory information ismissing for object bfid.

Explanation: During a read operation, a damagedrecord for a file was identified. The file is skipped.

System action: The file is not displayed.

User response: Correct the error in the file and reissuethe QUERY CLEANUP command.

ANR2779I Command: Inventory information for allitems cannot be displayed. A total ofnum files files are missing inventoryinformation. The missing files are notdisplayed.

Explanation: During a read operation, a damagedrecord for a file was identified. The file is skipped.

System action: The files are not displayed.



User response: Correct the error in the file and reissuethe QUERY CLEANUP command.

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.

ANR2781E command name: keyword value longer thanmax length characters.

Explanation: The directory specified for the indicatedkeyword is too long. Specify a directory less than orequal to the number of characters indicated. This is alimitation of the underlying database.

System action: Server database format processingterminates.

User response: Specify a valid value for the indicatedkeyword.

ANR2782I SET DBRECOVERY completedsuccessfully and device class forautomatic DB backup is set to value.

Explanation: The device class requirement forautomatic database backup is set with the SETDBRECOVERY command.



ANR2783E FORMAT: Required keyword keywordnot specified.

Explanation: A required keyword was not specifiedfor database format processing.

System action: Server database format processingterminates.

User response: Reissue the format command with therequired parameters.

ANR2784W Specifying PROTECTKEYS=NOrequires the server's encryption keys tobe backed up manually.

Explanation: The server uses one or more encyptionkeys that are not stored in the server's database. Duringa database backup, if PROTECTKEYS=YES is specified,the server will back up these keys with the database so

they can be restored during a database restoreoperation. Specifying PROTECTKEYS=NO will preventthe server from backing up these keys, which areessential for normal server operation. In this case youmust manually save the dsmkeydb.kdb anddsmkeydb.sth files to a secure location, and make surethey are available when the restore database operationcompletes.

Failure to protect these keys will make anyserver-encrypted data inaccessible, as well as all locally-stored passwords for nodes and administrators.

System action: The command will be processed, butthe server will disable the automatic protection of theencryption key(s).


ANR2785E An error occurred when trying to accesspath name.

Explanation: An access denied error occurred whileattempting to access a directory.

System action: The command stops.

User response: Verify permission for that directory isset correctly then reissue the command.

ANR2786E The server was unable to find path name.

Explanation: The server could not find the directoryspecified.


User response: Verify the existence of that directoryand reissue the command.

ANR2787E The server failed with error code lasterror when attempt to access path name.

Explanation: The server failed to access the directoryspecified.


User response: Verify the existence of that directoryand reissue the command.

ANR2788E Database log path path name is notempty.

Explanation: When specifying a new active, archive,or mirror log directory in the server options file orwhen formatting a server, the indicated directory mustbe empty to prevent and accidental overwrite ofexisting data.

System action: If a FORMAT operation was beingperformed, the operation stops. If this was a change tothe server options file to specify a new log directory,the new directory is ignored, and the existing directoryis used.



User response: Verify the directory that was specified.Delete any data in that directory if the data is notneeded, or create a new directory. Reissue the formatcommand.

ANR2789E Command: The directory path deploydirectory path is already used in a serverdevice class or storage pool directory.

Explanation: The directory that was specified by theSET DEPLOYREPOSITORY command is already usedin a device class or stgpool directory definition.


User response: Reissue the command by specifying adifferent directory path.

ANR2790E Too many symbolic links were foundwhile traversing file path path name.

System action: The server stops processing thecommand.

User response: Refer to your operating system'smanual for the maximum number of symbolic linksallowed on a path name. Reduce the number ofsymbolic links that lead to the file path, and thenreissue the command.

ANR2791E The file or volume name path name istoo long.


User response: Check your operating system's limitson files and pathss length.Reissue the command with ashorter file or volume name.

ANR2792E A component of the path path name isnot a directory.

Explanation:


User response: Verify all directories in the path of thefile or volume name. Reissue the command with avalid file or volume path. command.

ANR2793W An invalid value for MAXTXNBYTE isfound in the database value in bytes.

Explanation: The server detects an invalid value forMAXTXNBYTE in the database. The server will use thedefault value for MAXTXNBYTE and processing willcontinue.

System action: Th server initialization continues.

User response: No action is required

ANR2794I LDAP password set.

Explanation: The password that the server uses toauthenticate with the LDAP server has been set,changed or removed with the SET LDAPPASSWORDcommand.



ANR2795I command: Repair failed processingbackup sets for node node name. backupset count backup sets belonging to nodecount nodes were successfully repairedbefore the failure.

Explanation: The REPAIR BACKUPSET commandencountered an error processing backup sets for thespecified node. Some backup sets might have beensuccessfully repaired.

System action: The command failed. Some backupsets might have been repaired.

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. Correct theproblem and rerun the command.

ANR2796I command: Repair completed for backup setcount backup sets belonging to nodecount nodes.

Explanation: The REPAIR BACKUPSET commandcompleted after successfully repairing the retentioninitiation date for the indicated number of backup sets.

System action: The command completed.


ANR2797E The license value was skipped becauseof a bad date range.

Explanation: One or more license values were skippeddue to the current system date not being valid for thelicense. This message occurs when reading thenodelock file. This can occur during server start-up,license audit, or REGISTER LICENSE.

System action: Server operation fails.

User response: Verify the correct system date setting.After you correct the system date, the licenses that areregistered with a quantity value will need to beregistered again.



ANR2798E Server operation is denied - server is notlicensed for License required.

Explanation: The server refuses a server operationbecause the server is not licensed with the appropriatesupport.


User response: Obtain and register the appropriatelicense.

ANR2799W Server operation is in violation of serverlicense terms - server is not licensed forLicense required.

Explanation: The server warns about a serveroperation because the server is not licensed with theappropriate support.


User response: Obtain and register the appropriatelicense.

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.




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.



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: To increase the amount of log spacethat is available to the server, evaluate the directoriesand file systems that are assigned to theACTIVELOGDIRECTORY, ARCHIVELOGDIRECTORY,and ARCHFAILOVERLOGDIRECTORY options in thedsmserv.opt file. An out of log space condition might



occur because the ACTIVELOGDIRECTORY location isfull.


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.



ANR2811W Command: The file system on which thedirectory path deploy directory pathresides has less than 40 gigabytes of freespace.

Explanation: The directory that was specified by theSET DEPLOYREPOSITORY command resides on a filesystem that might not have enough free storage forclient deployment packages.


User response: If possible, reissue the SETDEPLOYREPOSITORY command and specify adirectory path that resides on a file system with at least40 gigabytes of free space.

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.


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.

ANR2818E A consistency check failed on containerContainer Name with error Error Code.

Explanation: A data integrity problem was found inthe storage pool.

System action: The server checks the data as part ofnormal operation and encountered a data integrityproblem.

User response: Issue the REPAIR STGPOOL commandto repair the data or recover the data from a recoveryserver.

ANR2819E Command: There is insufficient authorityto write data to directory path deploydirectory path.

Explanation: The server does not have the authorityto create files in the directory that is specified in theSET DEPLOYREPOSITORY command.




User response: Ensure that the user ID for the IBMSpectrum Protect instance has write permission on thedirectory that is specified in the SETDEPLOYREPOSITORY command.

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.



ANR2827I Server is licensed to support feature namefor a quantity of licensed quantity.

Explanation: This message is issued during serverstartup.



ANR2828I Server is licensed to support featurename.






ANR2829E Command: parameter - parameter is notallowed.

Explanation: The UPDATE NODE command has beenentered with a parameter that is not allowed.


User response: When updating the REPLMODE andREPLSTATE parameters on a node definition, there arerestrictions that prohibit changing certain values.Several conditions are enforced during commandprocessing that prevents unintended updates. Thesyntax processing is strictly enforced and in manycases, it might be necessary to issue other commandsprior to using UPDATE NODE.

For information about the UPDATE NODE command,search for "UPDATE NODE" in the product information(http://www.ibm.com/support/knowledgecenter/SSEQVQ/).

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: The directory path deploydirectory path is already specified as thecurrent deployment repository directory.

Explanation: The directory that was specified by theSET DEPLOYREPOSITORY command is the same asthe current deployment repository directory.

System action: Server operation continues; thecommand is not processed.

User response: Verify that the specified deploymentrepository directory path is correct.

ANR2834E Command: The file system on which thedirectory path deploy directory pathresides has no free space.

Explanation: The directory that was specified by theSET DEPLOYREPOSITORY command resides on a filesystem that has no free space available for clientdeployment packages.


User response: Reissue the SETDEPLOYREPOSITORY command and specify adirectory path that resides on a file system with at least40 gigabytes of free space.

ANR2835I Server is licensed for number of clientsclients.

Explanation: This message is issued during serverstartup and in one hour increments there after.



ANR2839I Automatic license audit started asprocess process ID.


System action: The server checks registered nodes andcompares them against the value for which the serveris 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 command todisplay the current server configuration with respect tolicensed terms to discover which factors of theconfiguration do not conform to your license. Contactyour service representative to obtain more licenses, ifrequired.

ANR2842I Server is licensed to support number ofgigabytes gigabytes of storage.




ANR2843I Server is licensed to support UNIXclients.



User response: None. UNIX is a registered trademarkin the United States and other countries, licensed



exclusively through X/Open Company Limited.

ANR2844I Server is licensed to support desktopclients.

Explanation: This message is issued during serverstartup and in one hour increments there after.



ANR2847W The addition of client client node name isbeyond the client capacity that theserver is licensed to support.

Explanation: This message is issued when a newclient node is added to the server with the REGISTERNODE command, or through open registration, and theactual number of nodes registered on the serverexceeds the server's licensed capacity.


User response: This message is issued as a reminderto the administrator that the server is not operatingwithin compliance of its license. Contact your servicerepresentative if more licenses are required for yourserver.

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.

ANR2854I Server is licensed for device supportmodule module number.

Explanation: This message may be issued duringserver startup.



ANR2855W The UPDATE STGPOOLDIRECTORYcommand marks as destroyed all of thedata that is stored in the containerstorage pool pool name in the storagepool directory directory name.

Explanation: An update stgpooldir command hasbeen entered that will change the access of thestgpooldir to destroyed. This will mark all of theassociated storage as needing recovery.



ANR2856W The SHOW ORPHANOBJECTcommand with the clean option destroysall of the data that is orphaned andassociated with node node name.

Explanation: A show orphanobject command has beenentered that will destroy the objects associated with thespecified node. This is a non-revertable action.



ANR2859I Server is licensed for Secondary ServerAttachment.

Explanation: This message may be issued duringserver startup.



ANR2860I Server is licensed to support disasterrecovery manager.






ANR2861I Server is licensed to supportNETWORK connections.




ANR2863I Server is licensed to support EnterpriseAdministration functions.




ANR2864I Server is licensed to supportServer-to-Server Virtual Volumes.




ANR2865W The server is NOT licensed to supportEnterprise Administration functions. Byperforming this action you are no longerin compliance with license terms.

Explanation: This message is issued when enterpriseadministration functions are used, but the server isNOT licensed to support the functions.


User response: To bring your installation back intoconformance with license terms, obtain a license forenterprise administration functions or remove centrallogging definitions. Contact your service representativeif you have any questions or concerns with thismessage.

ANR2868E The server is NOT licensed to supportEnterprise Administration functions.

Explanation: This message is issued when EnterpriseAdministration functions are used, but the server isNOT licensed to support the functions.


User response: Contact your service representative ifyou want to obtain a license for enterpriseadministration.

ANR2879I The stgrule_name storage rule completedits processing, reclaiming reclaimed_cntrsof reclaimable containers by reading andwriting moved_bytes to save saved_bytes.

ANR2880W The reclamation process process IDended for storage pool storage pool name.

Explanation: The process stopped because it exceededthe time and duration that were set when the storagerule was defined.

System action: The reclamation process stops.

User response: To update the storage rule, issue theUPDATE STGRULE command and specify theDURATION and STARTTIME parameters.

ANR2899E Command: Operation is not valid forstorage pool type storage pool storage poolname.

Explanation: The command indicated specifies avolume in a storage pool which is not valid for thecommand.


User response: Reissue the command with a volumein a valid storage pool.

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 ofCHAR 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 data

type 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' contains anunknown SQL table name.

Explanation: A table name in the SQL command is notone of the base tables defined by the server's database.The rows of the table SYSCAT.TABLES can be selectedto obtain a list of all of the valid base tables.


User response: Retry the command using a table thatis defined by the IBM Spectrum Protect serverdatabase.

ANR2940E The command 'reference' contains anunknown SQL column name.

Explanation: A column name in the SQL command isnot one of the base table columns defined by theserver's database. The rows of the tableSYSCAT.COLUMNS can be selected to obtain a list ofall of the valid base table columns. If a two-part(compound) column reference such as X.Y is specified,then the correlation name X must be one of the activecorrelation names for the 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 wasspecified. 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, thereby

making 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 theserver 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 than

one 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 created



during the execution of the named command orprocess.

System action: The named command or process isterminated.

User response: Extend the server database (afteradding database volumes if necessary) and rerun thecommmand or process.

ANR2968E Database backup terminated. DB2sqlcode: sqlcode. DB2 sqlerrmc: sqlerrmc.

Explanation: DB2 detected a problem during thebackup operation. Sources of the problem mightinclude:

1. IBM Spectrum Protect API configuration errors forthe DB2 instance in which the IBM SpectrumProtect server database resides.

2. An error related to the DB2 backup operation.

3. Errors related to the target backup device.

System action: The database backup is terminated.

User response: If the message indicates DB2 sqlcode2033, then the problem is probably the IBM SpectrumProtect API configuration. The DB2 instance uses theIBM Spectrum Protect API to copy the IBM SpectrumProtect database-backup image to the IBM SpectrumProtect server-attached storage devices. Commonsqlerrmc codes include:

1. 50 - To determine whether an error created the APItimeout condition, look for any IBM SpectrumProtect server messages that occurred during thedatabase-backup process and that were issuedbefore ANR2968E. Ensure that the IBM SpectrumProtect API options file has the correctTCPSERVERADDR and TCPPORT options specifiedfor the IBM Spectrum Protect server being backedup. If the option settings are wrong, correct themfor the DB2 instance.

2. 53 - Ensure that the NODENAME option in theIBM Spectrum Protect API options files is set to$$_TSMDBMGR_$$. Also verify theTCPSERVERADDRESS setting. If the keyword"localhost" is being used verify that this is beingresolved correctly by issuing the command "pinglocalhost" from a system command window. If theping of localhost fails, consider changing theTCPSERVERADDRESS to the explicit loopbackaddress of 127.0.0.1. As an alternative to setting theexplicit loopback address of 127.0.0.1, verify theTCP/IP configuration and whether or not"localhost" is configured correctly. For example, forUnix or Linux systems, verify that /etc/hosts hasan appropriate entry for "localhost".

3. 106 - Ensure that the DB2 Instance DSMI_DIRenvironment variable is pointing to the location ofthe IBM Spectrum Protect API executables and the

dsm.sys configuration file. If the DSMI_DIR settingis wrong, correct it for the DB2 instance, and thenrestart the DB2 instance.

4. 137 - Ensure that the DB2-instance DSMAPIPWcommand was run and that it specified nodename$$_TSMDBMGR_$$ and the password TSMDBMGR.

5. 400 - Ensure that the options specified in the IBMSpectrum Protect API options file are valid.

6. 406 - Ensure that the DB2 instance owner has atleast read access to the IBM Spectrum Protect APIoptions file. Ensure that the DB2-instanceDSMI_CONFIG environment variable is pointing toa valid options file for the IBM Spectrum ProtectAPI. If the DSMI_CONFIG setting is wrong, correctit for the DB2 instance, and then restart the DB2instance.

7. 450,451 - Ensure that the server options file and theIBM Spectrum Protect API options file both containthe COMMMETHOD SHAREDMEM option. Ensurethat the values for the SHMPORT option in eachoptions file correspond. Restart the server if youchange any values in the server options file.

8. For descriptions of other sqlerrmc values, look inthe dsmrc.h file that is installed with the IBMSpectrum Protect API.

If this message is issued with a DB2 sqlcode that is not2033, then look for more information about the error byopening a DB2 command-line processor window andtyping: ? SQLsqlcode. For example, db2 => ? sql2428

ANR2969E Database restore terminated. DB2sqlcode: sqlcode. DB2 sqlerrmc: sqlerrmc.

Explanation: DB2 detected a problem during therestore operation. Sources of the problem mightinclude:

1. IBM Spectrum Protect API configuration errors forthe DB2 instance in which the IBM SpectrumProtect server database resides.

2. Errors related to the DB2 restore operation.

3. Errors related to the target backup device.

4. The IBM Spectrum Protect API client configurationused by the current instance is not able to access thebackup image.

System action: The database restore operation isterminated.

User response: If the message indicates DB2 sqlcode2033, then the problem is most likely the IBM SpectrumProtect API configuration. The DB2 instance uses theIBM Spectrum Protect API to copy the IBM SpectrumProtect database restore image from the IBM SpectrumProtect server-attached storage devices to DB2.Common sqlerrmc codes include:

1. 50 - To determine whether an error created the APItimeout condition, look for any IBM SpectrumProtect server messages that occurred during the



backup DB process and that were issued beforeANR2969E. Ensure that the IBM Spectrum ProtectAPI options file has the correct TCPSERVERADDRand TCPPORT options specified for the IBMSpectrum Protect server being backed up. If theoption settings are wrong, correct them for the DB2instance.

2. 53 - Ensure that the NODENAME option in theIBM Spectrum Protect API options files is set to$$_TSMDBMGR_$$.

3. 106 - Ensure that the DB2-instance DSMI_DIRenvironment variable is pointing to the location ofthe IBM Spectrum Protect API executables and thedsm.sys configuration file. Ensure that you have thecorrect permissions to access these locations. If theDSMI_DIR setting is wrong, correct it for the DB2instance, and then restart the DB2 instance.

4. 137 - Ensure that the DB2-instance DSMAPIPWcommand was run and that it specified thenodename $$_TSMDBMGR_$$ and the passwordTSMDBMGR.

5. 400 - Ensure that the options specified in the IBMSpectrum Protect API options file are valid.

6. 406 - Ensure that the DB2 instance owner has atleast read access to the IBM Spectrum Protect APIoptions file. Ensure that the DB2 InstanceDSMI_CONFIG environment variable is pointing toa valid options file for the IBM Spectrum ProtectAPI. If the DSMI_CONFIG setting is wrong, correctit for the DB2 instance, and then restart the DB2instance.

7. 450,451 - Ensure that the server options file and theIBM Spectrum Protect API options file both containthe COMMMETHOD SHAREDMEM option. Ensurethat the values for the SHMPORT option in eachoptions file correspond. Restart the server if youchange any values in the server options file.

8. For descriptions of other sqlerrmc values, look inthe dsmrc.h file that is installed with the IBMSpectrum Protect API.

If the message indicates DB2 sqlcode 2542, then theproblem is probably because IBM Spectrum Protect APIversion for database restore is not the same API versionfor database backup. Check IBM Spectrum Protect APIversion:

1. AIX - /bin/sh -c "lslpp -lcqtivoli.tsm.client.api.64bit"

2. Solaris - /bin/sh -c "cat /var/sadm/pkg/TIVsmCapi/pkginfo | grep VERSION

3. HP- /bin/sh -c "cat /var/adm/sw/products/TIVsm64/CLIENT_API64/INDEX| grep ^revision

4. Linux - rpm -q TIVsm-API64-* --qf%{VERSION}.%{RELEASE}\\n

5. Windows - reg query "HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\CurrentVersion\Api"

If this message is issued with a DB2 sqlcode that is not2033 or 2542, then look for more information about theerror by opening a DB2 command-line processorwindow and typing: ? SQLsqlcode. For example, db2=> ? sql2428

ANR2970E Database rollforward terminated - DB2sqlcode sqlcode sqlerrmc sqlerrmc

Explanation: There is a problem detected by DB2.

System action: The database rollforward isterminated.

User response: More information about the error isavailable by opening a DB2 command-line processorwindow and typing: ? SQLsqlcode. For example, db2=> ? sql2428

ANR2971E Database backup/restore/rollforwardterminated - DB2 sqlcode sqlcode error.

Explanation: There is a problem detected by DB2.

System action: The database backup/restore/rollforward is terminated.

User response: More information about the error isavailable by opening a DB2 command-line processorwindow and typing: ? SQLsqlcode. For example, db2=> ? sql2428

ANR2972E Restore DB Command: Databaserestore/rollforward terminated - Notable to clean up log directory directoryname.

Explanation: IBM Spectrum Protect tried to clean upthis log directory before PIT restore DB and not able to.

System action: The database restore/rollforward isterminated.

User response: Please clean up this directorymanually before performing DB PIT restore.

ANR2973E Restore DB Command: Databaserestore/rollforward terminated - Logdirectory is required and does not existdirectory name.

Explanation: The log direcotry is required and it doesnot exist. PIT restore DB is terminated.

System action: The database restore/rollforward isterminated.

User response: Create the specified directory andretry.



ANR2974I Offline DB backup for database DBAlias completed successfully.

Explanation: Offline DB backup completedsuccessfully.



ANR2975E Offline DB backup for database DBAlias failed with sqlcode sqlcode andsqlerrmc sqlerrmc.

Explanation: The Offline Database backup failed.

System action:

User response:

ANR2976I Offline DB backup for database DBAlias started.

Explanation: Offline DB backup started.



ANR2977E Command: The command failed becauseof an issue in the device configurationfile.

Explanation: The device configuration file includesone or more invalid values.

System action: The server ends the current operation.

User response: Correct the issue in the deviceconfiguration file and run the command again.

ANR2978E Command: Invalid directory name -directory name.

Explanation: Restore DB failed due to invalid targetdirectory name in device target directory file.


User response: Correct the problem in target directoryfile and retry.

ANR2979E Internal error - Control descriptor isNULL.

Explanation: Something is wrong the controldescriptor is NULL.



ANR2980E Database backup terminated TCPIPfailure - DB2 sqlcode sqlcode sqlerrmcsqlerrmc.

Explanation: There is a TCPIP failure detected byDB2.


User response: Correct the TCPIP setup problembetween IBM Spectrum Protect and DB2 and retry.

ANR2981E Database backup terminated due toenvironment or setup issue related tofile access - DB2 sqlcode sqlcodesqlerrmc sqlerrmc.

Explanation: There is a problem related toenvironment or setup detected by DB2.


User response: Ensure that you specified the correctfile or directory name, correct the permissions, orspecify a new location and retry.

ANR2982E Database backup terminated due toenvironment or setup issue related topassword - DB2 sqlcode sqlcode sqlerrmcsqlerrmc.



User response: If the IBM Spectrum Protect parameterPASSWORDACCESS is set to GENERATE, ensure thatthe system administrator has used the dsmapipw utilityto set the password. If PASSWORDACCESS is set toPROMPT, ensure that the TSM_NODENAME andTSM_PASSWORD database configuration parametershave been set correctly.

ANR2983E Database backup terminated due toenvironment or setup issue related toDSMI_DIR - DB2 sqlcode sqlcodesqlerrmc sqlerrmc.



User response: Ensure that DSMI_DIR points to adirectory containing the correct version of db2tca,restart the instance, and execute the command again.

ANR2984E Database backup terminated due toenvironment or setup issue related toDSMI_CONFIG - DB2 sqlcode sqlcodesqlerrmc sqlerrmc.

Explanation: There is a problem related to



environment or setup detected by DB2.


User response: Ensure that the DSMI_CONFIGenvironment variable points to a valid IBM SpectrumProtect options file. Ensure that the instance owner hasread access to the dsm.opt file. Ensure that theDSMI_CONFIG environment variable is set in thedb2profile.

ANR2985E Database backup terminated due to I/Oerror related to TCPIP - DB2 sqlcodesqlcode sqlerrmc sqlerrmc.

Explanation: There is a TCPIP problem detected byDB2 and caused the database backup to fail.


User response: The possible TCPIP problem areconnection time out, connection refused, bad host nameor network unreachable. Correct the TCPIP problembetween IBM Spectrum Protect and DB2 and retry.

ANR2986E Database backup terminated due to I/Oerror - DB2 sqlcode sqlcode sqlerrmcsqlerrmc.

Explanation: There is a I/O problem detected by DB2and caused the database backup to fail.


User response: Correct the I/O problem between IBMSpectrum Protect and DB2 and retry.

ANR2987W Session ended because of machineGUID or local host IP addressmismatch.

Explanation: Backup or Restore DB commands areonly allowed when the IBM Spectrum Protect databasebeing backed up or restored and the IBM SpectrumProtect api and the IBM Spectrum Protect server are onthe same machine. Either the GUID of the IBMSpectrum Protect api client in use by the databasemanager does not match the GUID of the IBMSpectrum Protect server or the local host IP addressindicated by the IBM Spectrum Protect client is notaccepted.

System action: The database backup or restoreoperation is terminated.

User response: Default acceptable local host addressesare "127.0.0.1" for IPV4 and "::1" for IPV6. If you cannot configure one of these local host addresses on yoursystem then use the IBM Spectrum Protect serveroption "DBMTRUSTEDIPADDR ipaddr" to set a localhost address that can be accepted.

ANR2988W Attempt to add the last backup dbvolume used entry back in to thevolume history was unsuccessful.

Explanation: Restore db operation was successfulhowever the attempt to add the last backup db volumeused back in to the volume history failed.

System action: The database restore operation issuccessful. Entry for last backup db volume used in theoperation might be missing from volume history.

User response: Keep a copy of the volume history filethat was used to do the restore operation. After youhave verified the restore db operation do a backup dbtype=full. Manually track the volume that was notadded back in to the volume history.

ANR2989E Database Database Name backup failed -Missing volume history file.

Explanation: Backup DB failed due to volume historyfile is not defined in the dsmserv.opt.


User response: Correct the problem in dsmserv.opt fileand retry.

ANR2990E Database restore is terminated due to aninvalid database path sqlerrmc and DB2sqlcode sqlcode

Explanation: DB2 detected invalid database path.

System action: The database restore is terminated.

User response: Ensure the path exists and permissionsare correct and issue restore DB command again orissue restore DB command again with ON parameter tospecify a new valid database storage path.

ANR2991E The Incremental Database backup wasterminated because a full databasebackup is required - DB2 sqlcode sqlcodesqlerrmc sqlerrmc.

Explanation: The Incremental Database backup wasterminated. A FULL database backup is required beforean Incremental Database backup can be completed.

System action: The incremental database backup isterminated.

User response: Complete a FULL database backupfirst, then retry the incremental database backup.

ANR2992W The database uses database space usedmegabytes of file-system space. Theamount of available file-system space isdatabase space available megabytes. Theratio is database file system used ratio.



Explanation: The ratio exceeds the threshold fordatabase space utilization.

System action: System operations might be restrictedbecause of limited database space.

User response: To increase the space for the database,use the EXTEND DBSPACE command.

ANR2993E The database backup terminated with alog problem. DB2 sqlcode: sqlcode. DB2sqlerrmc: sqlerrmc.

Explanation: The database backup was terminated byDB2 because one or more of the log files needed couldnot be retrieved.


User response: If the message did not indicate whichlog directory path caused the problem, look in thedb2diag.log for additional information. Commonproblems are a missing directory or permission denied.

ANR2994E The automatic database backup wasterminated.

Explanation: The operation was terminated becausethe device class that is used for the automatic databasebackup is not defined.

System action: The automatic database backup isterminated.

User response: Issue the SET DBRECOVERYcommand to define the device class for the automaticdatabase backup.

ANR2995E Command: Device class device class nameis used for the automatic databasebackup.

Explanation: The DELETE DEVCLASS command wasissued to delete a device class that is in use for theautomatic database backup.


User response: Issue the SET DBRECOVERYcommand to define a new device class for automaticdatabase backup before deleting this device class.

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 activity

and 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.

ANR2998I When storage rule stgrule_name isprocessed, it reclaims reclaimable_cntrscontainers, reading and writingmoved_bytes saving saved_bytes.

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 a validrefresh 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.

ANR3008I Database backup was written usingclient API: API information.

Explanation: The database backup was written usingthe indicated IBM Spectrum Protect Backup/ArchiveAPI.

System action: Database restore processing continues.

User response: This information will be used duringthe database restore operation. If the API used duringthe restore is not compatible, additional messages willbe issued and the operation will fail.

ANR3009E Database restore not possible, client APIis not compatible: API information.

Explanation: The IBM Spectrum Protect client APIversion being used for this database restore operation isnot compatible with the version used to write thedatabase backup.

System action: Database restore processing terminates.

User response: Install a newer version of the IBMSpectrum Protect client API and retry this databaserestore operation. The client API version currentlyavailable and used for this database restore operation isnot compatible with what was used to originally writethe database backup.

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 command todetermine which profiles still exist on the configurationmanager then use the DELETE PROFILE command.After all the profiles have been deleted, reissue thecommand.

ANR3016I command: Configuration refresh intervalset to interval.

Explanation: The command has successfully set theconfiguration refresh interval to the specified value.Automatic configuration refresh processing willimmediately 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 a validlock timeout interval value.

ANR3023I command: Profile profile name locked.

Explanation: The command has successfully lockedthe profile. No configuration information can bepropagated 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 specified.

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 bepropagated 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 specified command cannot beperformed on a locked profile.


User response: Unlock the profile using the UNLOCKPROFILE command and then reissue the command.

ANR3029I Reorganization for table table namecanceled.

Explanation: Based on the DISABLEREORGTABLEserver option, table reorganization is disabled for tablethat is referenced and a paused reorganization iscanceled.

System action: The reorganization is canceled.

User response: If the intention is to disable tablereorganization for table that is referenced, then nofurther action is required, otherwise consider updatingthe DISABLEREORGTABLE server option.

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 specified 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 configuration manager.

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 correct 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 thesubscription 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 name wasspecified correctly. Issue the QUERY SUBSCRIPTIONcommand to check to see which profiles havesubscriptions. Reissue the command with the correctprofile 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 propagated to managed servers whichsubscribe to the profile. If an administrator is added tothe configuration manager in the future, its definitionwill also be automatically propagated 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 automaticallypropagated 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 automaticallypropagated to managed servers which subscribe to theprofile. If a domain is added to the configurationmanager in the future, its definition will also beautomatically propagated 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 propagated 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 propagated to managed servers whichsubscribe to the profile. If an admin schedule is addedto the configuration manager in the future, itsdefinition will also be automatically propagated 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 propagated to managed servers whichsubscribe to the profile.



ANR3050W command: No additional adminschedules 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 propagated tomanaged servers which subscribe to the profile. If ascript is added to the configuration manager in thefuture, its definition will also be automaticallypropagated 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 propagated 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 propagated 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 propagated 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 propagated 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 propagated tomanaged servers which subscribe to the profile. If aserver is added to the configuration manager in thefuture, its definition will also be automaticallypropagated 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 propagated 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 propagated to managed servers whichsubscribe to the profile. If a server group is added tothe configuration manager in the future, its definitionwill also be automatically propagated 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 automaticallypropagated 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 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 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 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 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 client option set definitionsare associated with the 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 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 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 occur during the next configurationrefresh 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.

ANR3091I Command: One or more storage rulesexist for storage pool storage pool name.

Explanation: One or more storage rules exist for thestorage pool.


User response: Issue the QUERY STGRULE commandto identify the storage rule and the associated storagepool. Then, issue the UPDATE STGRULE command orthe DELETE STGRULE command to remove thestorage rule for the storage pool.



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 and QUERYSUBSCRIBER command to determine which profilesexist and which profiles have subscribers. Reissue thecommand specifying the correct profile name(s).

ANR3094E The distinguished name "DN" that isspecified in the LDAPURL option doesnot exist on the LDAP directory server.

Explanation: The distinguished name (DN) that isspecified in the LDAPURL server option is not foundon the LDAP directory server.


User response: Create the directory entry that isassociated with the DN, specify a DN in the LDAPURLthat already exists, or specify another directory serverthat contains the DN that is defined in the LDAPURLserver option. Choose one of these options and restartthe IBM Spectrum Protect server.

ANR3095W Failure updating the database volumehistory information with the volumesused to perform this restore operation.

Explanation: At the end of database restore processingfor a point in time operation, the server database willbe updated to show the volumes that were used torestore the database. This is done so that a futurerestore has knowledge of this database backup and willbe able to use this if it is the best possible candidate fora future operation. Because the server failed to updatethis information, a future restore database operationmay not select the best possible database backup to usefor the operation.

System action: Database restore processing completes.

User response: Once the server is restarted after thedatabase restore is completed, a BACKUP DB

TYPE=FULL should be performed as soon as possibleand the volume history information backed up afterthis backup is completed. This will set a new bestpossible restore point if a future restore operation isneeded. If you use the Disaster Recovery Managerfeature to track database backup volume physicallocation you will have to manually track the location ofthe database backup volumes which were not updated.

ANR3096I The volumes used to perform thisrestore operation were successfullyrecorded in the server volume history.

Explanation: At the end of database restore processingfor a point in time operation, the server database willbe updated to show the volumes that were used torestore the database. This is done so that a futurerestore has knowledge of this database backup and willbe able to use this if it is the best possible candidate fora future operation.

System action: Database restore processing completes.


ANR3097W LDAPUSER must be set before you canuse LDAP password authentication.

Explanation: The LDAPURL server option is set,however LDAP password authentication cannotcomplete until LDAPUSER and LDAPPASSWORD areset.

System action: Server operations continue withoutLDAP authentication.

User response: Issue the SET LDAPUSER and SETLDAPPASSWORD commands, in that order.

ANR3098W LDAPPASSWORD must be set beforeyou can use LDAP passwordauthentication.

Explanation: The LDAPURL server option is set,however LDAP password authentication cannotcomplete until the LDAPUSER and LDAPPASSWORDare set.

System action: Server operations continue withoutLDAP authentication.

User response: Issue the SET LDAPPASSWORDcommand.

ANR3099E The distinguished name "DN" specifiedin the LDAPURL option does not havethe proper syntax.

Explanation: The distinguished name (DN) in theLDAPURL server option does not have the propersyntax. The LDAP URL must use the RFC 2255 formatwith the restriction that the LDAPURL server optioncan only contain ASCII characters. The DN must



conform to the requirements of the directory server.Directory servers typically support RFC 2253 or 4514for the DN format.


User response: Correct the LDAPURL server optionand restart the IBM Spectrum Protect server.

ANR3100I Initializing LDAP directory services.

Explanation: The server started the initializationprocess with the LDAP directory server.



ANR3101I Successfully initialized LDAP directoryservices.

Explanation: The server was successfully configuredto use LDAP directory services.

System action: Server operations continue and LDAPdirectory services are available.


ANR3102E An authentication failure occurredduring LDAP directory servicesinitialization as user LDAP user.

Explanation: The LDAPUSER value or theLDAPPASSWORD value, or both, are incorrect.

System action: Server operations continue. LDAPdirectory services are not available.

User response: Correct the values for the LDAP userand LDAP password by issuing the SET LDAPUSERand SET LDAPPASSWORD commands. After you issuethese commands, LDAP directory services initializationis attempted.

ANR3103E Failure occurred while initializingLDAP directory services.

Explanation: An error occurred while the serverinitialized LDAP directory services.

System action: Server operations fail. If the server isalready started, LDAP directory services are no longeravailable. The server cannot start if it was in the middleof trying to start.

User response: Examine the server messages that wereissued prior to this message to determine the source ofthe error. Issue the QUERY ACTLOG command to viewthe activity log file and search for messages. Check fornetwork problems. Check for problems with thecertificate used by the directory server or the keydatabase containing the certificates. Check the accessrights of the LDAPUSER. Check the status of thedirectory server and examine the log files provided by

the directory server. Use LDAP utilities such asldapsearch or ldp to isolate the problem.

If the server does not start, remove the LDAPURLserver option to allow the server to start temporarilywithout directory services. If the server is running,issue the SET LDAPUSER or SET LDAPPASSWORDcommands to try initializing LDAP directory servicesagain.

ANR3104E The LDAP directory service is notsuccessfully configured.

Explanation: The IBM Spectrum Protect server mustbe configured correctly in order to use LDAP directoryservices, before accounts can be placed in the LDAPdirectory server to authenticate access requests.

System action: Server operations fail.

User response: To configure LDAP directory services,set the LDAPURL server option, add the appropriatecertificate to the IBM Spectrum Protect server keydatabase, and issue the SET LDAPUSER and SETLDAPPASSWORD commands. The LDAP password(LDAPPASSWORD) must match the password for theuser (LDAPUSER) that can conduct IBM SpectrumProtect administrative operations when accessing theLDAP directory server.

If the IBM Spectrum Protect server is alreadyconfigured to use LDAP directory services, anauthentication failure might have occurred or anothererror might have occurred during configuration.Examine the server messages that were issued prior tothis message to determine the source of the error. Issuethe QUERY ACTLOG command to view the activity logand search for messages.

ANR3105E The LDAP directory service was notfound by using Domain Name System(DNS).

Explanation: An LDAP directory server could not belocated using the system's current DNS serverconfiguration and DNS suffix search list.


User response: Check the system's DNS configuration,the status of the DNS servers, the DNS server log files,and the DNS server configuration. Verify that the DNSserver configuration complies with RFCs 2052, 2219, or2782.

ANR3106E Failed to parse the LDAPURL optionvalue LDAP URL.

Explanation: The LDAPURL server option valuecannot be parsed. The LDAP URL must use the RFC2255 format with the restriction that the LDAPURLserver option contain only ASCII characters.




User response: Correct the LDAPURL server optionvalue and restart the server.

ANR3107E LDAPS is not allowed for theLDAPURL option value LDAP URL.

Explanation: LDAPS represents using a Secure SocketsLayer (SSL) connection and sending LDAP data over anexisting SSL connection. The server only supportsLDAP connections secured by using the standardLDAPv3 "StartTLS" operation to establish a secure TLSexchange on an existing LDAP connection.


User response: Use the standard ldap:// scheme forthe LDAPURL server option and restart the IBMSpectrum Protect server.

ANR3108E The distinguished name is missing fromthe LDAPURL server option value LDAPURL.

Explanation: The distinguished name (DN) is requiredas part of the LDAPURL server option. When updatingthe LDAP URL information, use the RFC 2255 format.


User response: Correct the LDAPURL server optionvalue and restart the IBM Spectrum Protect server.

ANR3109E The LDAPURL server option valueLDAP URL does not contain a hostaddress and cannot be used becauseanother LDAPURL option valuespecifies a host address.

Explanation: You cannot have multiple LDAPURLserver option values if one of the values does notspecify a host address.



ANR3110E The distinguished names "DN" and"DN" specified with the LDAPURLserver option do not match.

Explanation: The distinguished names (DN) specifiedon each LDAPURL server option value must be thesame.



ANR3111E The LDAPURL server option valueLDAP URL is missing the ldap:// prefix.

Explanation: When updating the LDAP URLinformation, use the RFC 2255 format.


User response: Use the standard ldap:// schemeprefix for the LDAPURL server option and restart theIBM Spectrum Protect server.

ANR3112E The password cannot be reset, theLDAP directory server requires you toprovide the current password.

Explanation: The LDAP directory server requires thatthe user who is specified in the SET LDAPUSERcommand provide the current password whenchanging another user's password. The LDAPUSERneeds to be able to reset passwords to allow IBMSpectrum Protect administrators to reset passwords forIBM Spectrum Protect nodes and administrators.


User response: Change the password policy orpermission settings on the LDAP directory server toallow the user who is specified in the SET LDAPUSERcommand to change passwords for LDAP users whoare managed by the IBM Spectrum Protect server.

ANR3113E The password cannot be added orchanged, the LDAP user does not havesufficient access rights to add or changethe password.

Explanation: If the current password was notprovided for the operation, a password reset isperformed on the LDAP directory server by the userspecified in the SET LDAPUSER command. If thecurrent password was provided for the operation, forexample, in the SET PASSWORD client command, theuser's password is changed on the LDAP directoryserver by the user. However, if the user's passwordexpired, preventing access to the directory server, thepassword is changed by the user specified in the SETLDAPUSER command.


User response: Change the password policy andaccess rights on the LDAP directory server to allowusers to change their own passwords, and to allow theuser specified in the SET LDAPUSER command to addor reset passwords for the users that are beingmanaged by the IBM Spectrum Protect server.

ANR3114E LDAP error LDAP error code (errordescription) occurred during operation.

Explanation: The LDAP operation failed with anunexpected error.




User response: Examine the server messages issuedaround the same time as this message to determine thecause and impact of the error. Issue the QUERYACTLOG command to view the activity log and searchfor messages. Check the status of the LDAP directoryserver and examine its log files. Use LDAP utilitiessuch as ldapsearch or ldp to isolate the problem.

ANR3115E The LDAP directory server returned thefollowing error message (LDAP servermessage) with the LDAP error.

Explanation: The LDAP directory server returned anerror message associated with an LDAP error thatoccurred, providing addition information to assist indetermining the cause of the problem.


User response: Examine the server messages issuedaround the same time as this message to determine thecause and impact of the error. Issue the QUERYACTLOG command to view the activity log and searchfor messages. Check the status of the LDAP directoryserver and examine its log files. Use LDAP utilitiessuch as ldapsearch or ldp to isolate the problem.

ANR3116E LDAP SSL/TLS error GSKIT error code(error description) occurred duringoperation.

Explanation: An SSL/TLS error code was reported bythe GSKit component along with the LDAP error thatoccurred.


User response: Examine the server messages issuedaround the same time as this message to determine thecause and impact of the error. Issue the QUERYACTLOG command to view the activity log and searchfor messages. Check for network problems. Check forproblems with the certificate used by the LDAPdirectory server or the key database containing thecertificates. Check the status of the LDAP directoryserver and examine its log files. Use LDAP utilitiessuch as ldapsearch or ldp to isolate the problem usinga TLS connection to the LDAP server.

ANR3117E Session session number for node oradministrator node/admin name (clientplatform) refused - the level of the clientdoes not meet the minimum requiredlevel for LDAP authentication.

Explanation: The server refuses the client sessionbecause the client program version level is not 6.4 orlater. Only version 6.4 and later clients can use LDAPauthentication.

System action: The session is refused and serveroperations continue.

User response: Upgrade the client program to at leastversion 6.4 or do not use LDAP authentication to makeit compatible with the newer server program.

ANR3118I The LDAP entry for node node name wasdeleted.

Explanation: An inconsistency between the databaseof the IBM Spectrum Protect server database and theLDAP directory server was found during AUDITLDAPDIRECTORY command processing. Because youspecified FIX=YES, the LDAP entry for the node wasdeleted to correct this inconsistency.



ANR3119I The LDAP entry for administrator adminname was deleted.

Explanation: An inconsistency between the databaseof the IBM Spectrum Protect server database and theLDAP directory server was found during AUDITLDAPDIRECTORY command processing. Because youspecified FIX=YES, the LDAP entry for theadministrator was deleted to correct this inconsistency.



ANR3120I The administrator admin name wasupdated because the parameter parameterfor a node with the same name waschanged.

Explanation: Values for the AUTHENTICATION andSSLREQUIRED parameters must be the same for nodesand administrators that share the same name. If valuesfor either the node or the administrator changed, theadministrator or node sharing the same name will beupdated to keep these parameters the same.

If the AUTHENTICATION parameter changed fromLDAP to LOCAL, the password was also updated.When this happens, the password is updated to thesame password that is used for the node.

System action: The server updated theAUTHENTICATION or SSLREQUIRED parameter ofthe specified administrator.


ANR3121I The node node name was updatedbecause the parameter parameter for anadministrator with the same name waschanged.

Explanation: Values for the AUTHENTICATION andSSLREQUIRED parameters must be the same for nodesand administrators that share the same name. If valuesfor either the node or the administrator changed, the



node or administrator sharing the same name will beupdated to keep these parameters the same.

If the AUTHENTICATION parameter changed fromLDAP to LOCAL, the password was also updated.When this happens, the password is updated to thesame password that is used for the administrator.

System action: The server updated theAUTHENTICATION or SSLREQUIRED parameter ofthe specified node.


ANR3122E command: System level authority isrequired because the server needs toupdate a node or administrator thatshares the same name.

Explanation: Values for the AUTHENTICATION andSSLREQUIRED parameters must be the same for nodesand administrators that share the same name. If valuesfor either the node or the administrator changed, thenode or administrator sharing the same name will beupdated to keep these parameters the same.


User response: Reissue the command using anadministrator that has system level authority.Alternatively, rename either the node or theadministrator associated with the command such thatthey do not share the same name.

ANR3123W An LDAP entry for node node name wasnot found in the LDAP directory server.

Explanation: The REGISTER NODE command wasissued with AUTHENTICATION=LDAP but withoutproviding a password. This combination is valid.However, this combination will not create an LDAPentry, which is required to access the node.


User response: An LDAP entry must be created beforethis node can be accessed. To create a new LDAP entryfor this node issue the UPDATE NODE command andprovide a password. If the LDAP directory server isshared with another IBM Spectrum Protect server, theLDAP entry can be created by the other IBM SpectrumProtect server instead.

ANR3124W An LDAP entry for administrator adminname was not found in the LDAPdirectory server.

Explanation: The REGISTER ADMIN command wasissued with AUTHENTICATION=LDAP but withoutproviding a password. This combination is valid.However, this combination will not create an LDAPentry, which is required to access the administrator.


User response: An LDAP entry must be created beforethis administrator can be accessed. To create a newLDAP entry for this administrator issue the UPDATEADMIN command and provide a password. If theLDAP directory server is shared with another IBMSpectrum Protect server, the LDAP entry can be createdby the other IBM Spectrum Protect server instead.

ANR3125I command: Successfully updated successfulupdates nodes out of total update attemptsnodes that were targeted for updating.

Explanation: The command updated a node or nodesand produced summary statistics stating how manynodes were updated successfully and how manyattempts were made.



ANR3126I command: Successfully updated successfulupdates administrators out of total updateattempts administrators that weretargeted for updating.

Explanation: The command updated an administratoror administrators and produced summary statisticsstating how many administrators were updatedsuccessfully and how many attempts were made.



ANR3127W You must change the password for"LDAP user" within number day(s).

Explanation: The password is due to expire, and itmust be changed to prevent failures.


User response: Change the password on the LDAPdirectory server and issue the SET LDAPPASSWORDcommand with the new password.

ANR3128E Command: The number of failoverservers exceeds the maximum numberallowed.

Explanation: The number failover servers that can bedefined for a node is limited to one.


User response: Reissue the command specifying onlyone registered server name.



ANR3129I Server Fail Over high level address setto address.

Explanation: The high level address that clients use tocommunicate with this server during fail over has beenset to the value indicated with the SETFAILOVERHLADDRESS command.



ANR3132W Replication process with process Idprocess number from server server name, iscancelled. Replication process sourceprocess number on source server may stillbe active.

Explanation: A replication process on a targetreplication server which was initiated on a sourcereplication server has been cancelled.


User response: Check the status of the replicationprocess on the source server. Issue the CANCELPROCESS command on the source server to cancel thisreplication operation.

ANR3133E command: Server server name not defined

Explanation: The server server name is not defined tothe system.

System action: The command proceeds howver theserver name is not used.

User response: Use QUERY SERVER to identify avalid failover server.

ANR3134E Command: The number of specifiedoutput volumes (volume count) is lessthan the number of streams specified inthe MAXSTREAM parameter (streamcount).

Explanation: The number of specified output volumesis less than the number of streams specified in theMAXSTREAM parameter, and scratch volumes are notallowed.

System action: The command is not run.

User response: Rerun the commmand, specifyingmore output volumes or fewer streams, or specifySCRATCH=YES to allow scratch volumes to be used.

ANR3135E Command: The value specified for theMAXSTREAM parameter (stream count)is greater than the mount limitassociated with device class device class(mount limit).

Explanation: The value specified for the

MAXSTREAM parameter is greater than the mountlimit of the specified device class.

System action: The command is not run.

User response: Rerun the commmand, specifyingfewer streams.

ANR3136E Extractdb command: Failed to start orfailed to complete successfully.

Explanation: The database extract process was notable to start due to an error with the commandspecification or other validation performed prior toperforming the extract. Alternatively, the extract processhad started but failed to complete successfully due toan error during processing.

System action: Database extract processing did notprocess successfully.

User response: Review the other messages issued todetermine the cause of the failure.

ANR3137E Unable to reclaim database storage fortable space tbspace name. The error codereturn code is returned.

Explanation: An error occurred when the databasemanager was trying to reclaim space in the referencedtable space.

System action: The EXTEND DBSPACE operationfails. Server operation continues.

User response: Review messages on the server consoleand in the db2diag log to try and determine the reasonfor the failure. To complete the process, you will haveto manually execute the steps for redistributing dataand reclaiming space.

ANR3138I Reclaiming database storage for tablespace tbspace name is being started.

Explanation: The database manager is reclaimingstorage space for the referenced table space.



ANR3139I Reclaiming database storage for all tablespaces is completed .

Explanation: The database manager has reclaimedspace and reduced the size of all table spaces.





ANR3140I Redistribution of data for databasedatabase name on table space tbspace nameis complete.

Explanation: The database manager has createddirectories on recently added paths and hasredistributed data across those paths for the referencedtablespace.



ANR3141E Redistribution of data for databasedatabase name on table space tbspace namefailed with error code error code.

Explanation: A failure occurred during the creation ofdirectories on recently added paths or during theredistribution of data across new directories for thereferenced tablespace.

System action: The EXTEND DBSPACE operationfails. Server operation continues.

User response: Review messages on the server consoleand in the db2diag log to try and determine the reasonfor the failure. To complete the process, you will haveto manually execute the steps for redistributing dataand reclaiming space.

ANR3142I Redistribution of data for databasedatabase name on table space tblspace nameis starting.

Explanation: The database manager is creatingdirectories on newly added paths and redistributingdata across all directories for the referenced table space.



ANR3143I The following directory or directorieshave been defined in the databasespace: directory list. However, thedatabase manager might not use newstorage paths immediately.

Explanation: The EXTEND DBSPACE operationsuccessfully added new directories to the serverdatabase storage space. Because RECLAIM=NO wasspecified on the command, data is not redistributedacross all directories. New storage paths might not beused until existing storage is full.


User response: If you decide that you want toredistribute data and reclaim space in the database, youcan manually complete the step for these tasks.

ANR3144I Space is being added to the database asprocess process ID.

Explanation: An operation to add space to thedatabase, redistribute data across all directories, andreturn space to the operating system is in progress.

System action: The EXTEND DBSPACE command isprocessed and server operation continues.

User response: Do not stop the server while thisprocess is running and do not try to halt the processonce it has started. If you want to cancel the process,use the CANCEL PROCESS command. To query thestatus of this process, issue QUERY PROCESS

ANR3145E Command: Administrator admin name iscurrently accessing server server name.

Explanation: The command shown specifies anadmininistrator that has an active session with thespecified server.

System action: The local server does not process thecommand.

User response: Reissue the command at a later time,or if necessary, cancel the current administrator sessionand reissue the command.

ANR3146E command name: The list of directoriesspecified for database storage exceedslength limit characters.

Explanation: The list of directories is too long. Specifya list less than or equal to the number of charactersindicated.


User response: Consider breaking up the operationinto multiple EXTEND DBSPACE commands to reducethe number of directories specified on the command.

ANR3147I Directory(ies) directory list has beendefined in the database space. Databasedata was distributed and balancedacross existing directories.

Explanation: Command 'EXTEND DBSPACE'successfully added new directory(ies) into the serverdatabase space and balanced data across existingdirectories.

System action:

User response:

ANR3148W Process process number, replicating withprocess source process number on serverserver name, has been inactive for minutesof inactivity minutes.

Explanation: A replication process on a target server



has been inactive for a significant amount of time. It ispossible that there is a connection problem with thesource replication server, or the source replicationprocess is no longer running, or the source replicationserver is down.


User response: Verify that the source replicationserver is still running. If the server is running, checkthat the source replication process is still active. If thesource replication process is no longer active you cancancel this process.

ANR3149I Server Fail Over high level addressremoved.

Explanation: The high level address that clients use tocommunicate with this server during fail over has beenremoved.



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 identify the object, andtake 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 communicationserror was 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.

ANR3178E A communication error occurred duringsession session number with replicationserver server name.

Explanation: The communication error occurred whilethe system was receiving information from or sending



information to the specified replication server. Thiserror can occur on a target replication server if aCANCEL REPLICATION command is issued on thesource replication server.

System action: The server is running, but theoperation that was in progress failed.

User response: If this error occurs frequently, consultyour network administrator. Also review the activitylog on the target and source replication servers formessages that are related to replication.

ANR3179E Server server name does not supportreplication or is not initialized forreplication.

Explanation: In response to a REPLICATE command,the server attempted to establish a connection to thereplication target. But the target server does notsupport replication, or has not been properly initializedfor replication.

System action: Server operation continues. Thereplication fails.

User response: Make sure the replication target is atthe correct maintenance level and verify that theglobally unique ID (GUID) of the target server isproperly set. Use the tivguid utility to set the GUID ifnot properly set.

ANR3180E Replication cannot occur for node nodename, file-space filespace name and copytype copytype name because the targetreplication server is not set.

Explanation: In response to a REPLICATE NODEcommand, the server was unable to establish aconnection to a target replication server because atarget server was not defined.

System action: Replication for the node and file spaceis skipped. However, replication continues for othernodes and file spaces.

User response: To replicate data, the target replicationserver must be defined. Issue the SET REPLSERVERcommand to set the target replication server name. Thename specified in the SET REPLSERVER commandmust be associated with a valid server definition.

ANR3181E Replication server server name has thesame replication key as this server.

Explanation: During replication initialization, theserver detected that the replication key of the targetserver is the same as this server. Each server must havea unique replication key.

System action: Replication to the specified server isstopped.

User response: Issue the SET REPLSERVER command

to specify a different server for the target of thereplication.

ANR3182W The password authentication method fornode node name did not change.

Explanation: During replication or import processing,a node that uses an LDAP directory server toauthenticate passwords at the target was detected, butthe source node authenticates passwords with the IBMSpectrum Protect server (LOCAL). The Replication andImport process does not change the node passwordauthentication method from LDAP to LOCAL.

System action: Replication or Import processingcontinues. The node password authentication methoddid not change from LDAP to LOCAL.

User response: Change the node passwordauthentication method from LDAP to LOCAL byissuing the UPDATE NODE command with theAUTHENTICATION=LOCAL parameter.

ANR3183W The password authentication method foradministrator admin name did notchange.

Explanation: During import processing, anadministrator ID was detected that authenticatespasswords with an LDAP directory server at the target,but with the IBM Spectrum Protect server (LOCAL) atthe source. Import processing does not change anadministrator's password authentication method fromLDAP to LOCAL.

System action: Import processing continues. Thepassword authentication method did not change fromLDAP to LOCAL.

User response: You can change the passwordauthentication method for the target administrator fromLDAP to LOCAL by issuing the UPDATE ADMINcommand with the AUTHENTICATION=LOCALparameter.

ANR3184E Server server name cannot replicate withthis server.

Explanation: In response to a REPLICATE command,the server tried to establish a connection with thereplication target. The target server is at a level thatcannot support replication with this server.

System action: Server operations continue. Thereplication fails.

User response: Make sure that the replication targetserver is at a maintenance level that supportsreplication with this server.



ANR3185I Replicating node associated replicationnode as a proxy agent for replicated nodereference node

Explanation: During a REPLICATE NODE operation,the server has identified an associated proxy agentnode referenced by a replicated node. The proxy agentnode defintion will be replicated.



ANR3186I Replicating node associated replicationnode which is referenced in a file spaceauthorization rule for replicated nodereference node

Explanation: During a REPLICATE NODE operation,the server has identified an associated replication nodethat is referenced in a file space authorization rule of areplicated node. The associated replication nodedefintion will be replicated.



ANR3187E Replication of associated replicationnode associated replication node name failed- the node is not configured forreplication

Explanation: During a REPLICATE NODE operation,the server attempted to replicate a node that is either aproxy agent or referenced in a file space authorizationrule of a replicating node. The associated replicationnode could not be replicated because it is not currentlyconfigured for replication. Associated replication nodesmust have a replication mode set to SEND and areplication state of ENABLED in order to be replicatedto a target server.

System action: The replication operation continues.The replication of the associated node fails.

User response: To use an associated replication nodewith a client during a failover operation configure andenable the associated replication node for replication.

ANR3188E Replication of associated replicationnode associated replication node name failed- the node is not enabled for replication

Explanation: During a REPLICATE NODE operation,the server attempted to replicate a node that is either aproxy agent or referenced in a file space authorizationrule of a replicating node. The associated replicationnode could not be replicated because it is not currentlyenabled for replication. Associated replication nodesmust have a replication mode set to SEND and areplication state of ENABLED in order to be replicatedto a target server.


User response: To use an associated replication nodewith a client during a failover operation enable theassociated replication node for replication.

ANR3189E Replication of associated replicationnode associated replication node name failed- the target node is not enabled forreplication

Explanation: During a REPLICATE NODE operation,the server attempted to replicate a node that is either aproxy agent or referenced in a file space authorizationrule of a replicating node. The associated replicationnode could not be replicated because the nodedefinition on the target server is not currently enabledfor replication. Associated replication nodes on thetarget server must have a replication mode set to RECVand a replication state of ENABLED in order to bereplicated from a source server.


User response: To replicate an associated replicationnode set the replication state of the node on the targetserver to enabled.

ANR3190E Node node name on server server nameuses a different primary server forreplication.

Explanation: When you issued the REPLICATE NODEcommand, the server attempted to replicate a node toanother server. However, the other server already has areplica of the node from a different primary server.

System action: The replication of the node fails. Serveroperation continues.

User response: Issue the RENAME NODE commandto rename the node, or issue the REMOVE REPLNODEcommand to remove the node from replication with thecurrent primary server.

ANR3191E Command: The CONTAINER storagetype can only be used with aPOOLTYPE of PRIMARY.

Explanation: An attempt is made to define aPOOLTYPE using a storage type of CONTAINER.Storage pools with a POOLTYPE other than PRIMARYcan only be assigned to storage pools with aDEVCLASS storage type.


User response: Reissue the command specifying asequential device class or ommiting the POOLTYPE.



ANR3192I Replicate Node: Proxy agent nodesreplicated: proxy nodes replicated of proxynodes found identified. Associatedauthorized nodes replicated: authorizednodes replicated of authorized nodes foundidentified. Client option sets replicated:option sets replicated of option sets foundidentified.

Explanation: The replication process has completed.The meanings of the numbers are:

v Proxy agent nodes are the number of nodes whichare identified as proxy agents for any of the nodesspecified in the REPLICATE NODE command.

v Associated authorized nodes are the number ofnodes referenced in file space authorization rules ofany of the nodes specified in the REPLICATE NODEcommand.

v Client option sets are the number of option setswhich are referenced by any of the nodes specified inthe REPLICATE NODE command.



ANR3193I Replication Preview: Proxy agent nodesidentified: proxy nodes found. Associatedauthorized nodes identified: authorizednodes found. Client option sets identified:option sets found.

Explanation: The preview replication process hascompleted. The meanings of the numbers are:

v Proxy agent nodes are the number of nodes whichare identified as proxy agents for any of the nodesspecified in the REPLICATE NODE command.

v Associated authorized nodes are the number ofnodes referenced in file space authorization rules ofany of the nodes specified in the REPLICATE NODEcommand.

v Client option sets are the number of option setswhich are referenced by any of the nodes specified inthe REPLICATE NODE command.



ANR3194I Identified node associated replication nodeas a proxy agent for replicated nodereference node

Explanation: The preview replication process hascompleted. The server has identified an associatedproxy agent node referenced by a replicated node. Theproxy agent node defintion will be replicated if thereferencing node is replicated.



ANR3195I Identified node associated replication nodewhich is referenced in a file spaceauthorization rule for replicated nodereference node

Explanation: The preview replication process hascompleted. The server has identified an associatedreplication node that is referenced in a file spaceauthorization rule of a replicated node. The associatednode defintion will be replicated if the referencing nodeis replicated.



ANR3196E Communication error occurred onSession session number during importfrom (communication methodcommunication address).

Explanation: A communication error occurred duringimport from another server.

System action: The import process is ended.

User response: Determine the cause of thecommunication error and retry the import.

ANR3197W command: Replication of authorizationrule failed for node node name, filespaceId filespace id on target server target server- a duplicate rule exists on the targetserver.

Explanation: A file space authorization rule on thisserver could not be replicated to the target serverbecause an identical rule already exists on the targetserver.


User response: A file space which is being replicatedcontains an authorization rule that exists on both thesource and target servers. Determine whichauthorization rule should be used on the target serverusing the QUERY ACCESS command of the IBMSpectrum Protect client. Once you have decided whichauthorization rule to use, delete the unneededauthorization rule using the DELETE ACCESScommand of the IBM Spectrum Protect client.

ANR3198E command: The server server namedefinition could not be retrieved.Thedatabase is in an inconsistent state.

Explanation: An error occurred while accessing theserver information.


User response: For details and instructions to resolvethe issue, see Technote 1598476 at http://



www.ibm.com/support/entry/portal/. Type 1598476 inthe Search field.

ANR3199I Server halt for stage stage initiated attime.

Explanation: The server HALT processing is beingperformed and each stage is reported with the timewhen that stage was initiated.


User response: This message may not be logged to theactivity log. It is provided for informational purposesonly. The stages reported are for informationalpurposes and only to denote progress. The sequenceand actual stages to be performed during halt mayvary and as such will cause this not to always report inthe same fashion. The primary consideration is that theINIT stage and the COMPLETE stage can be used tocalculate the time used to halt the server. Thesemessages are only displayed if the halt command isissued with the verbose parameter such as: "HALTVERBOSE".

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 theindicated 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 delete

the 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.


User response: To update this object, you can deletethe subscription to the configuration profiles withwhich domain domain name is associated.

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 schedule canbe 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 profiles

with 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 is notdeleted.

User response: Before this administrator can be



deleted, 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 is notdeleted.

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 delete thesubscription to the configuration profiles with whichthe 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.

ANR3239E Error rc while creating device class deviceclass.

Explanation: This message is issued when a deviceclass could not be created, because there was an errorwhile processing the device configuration file.




User response: Look in the device configuration filefor errors, and look at the activity log for any previouserror messages that might help determine the locationof these errors in the device configuration file.

ANR3240W The device class device class only hasnumber of drives drives while the numberof streams requested is number of streams.

Explanation: This message is issued when a theNUMSTREAM parameter is being specified with avalue higher than the number of drives available to thedevice class.


User response: The value will be updated asrequested. If the number of drives available at the timethe database backup is attempted is less than thenumber of streams, the database backup will beperformed using the number of online drives as thenumber of streams. For example, if the number ofavailable drives is 2 but the NUMSTREAM value hadbeen set to 4, than the database backup will be doneusing only 2 streams.

ANR3241W The value specified for server optionoption 1 is ignored due to the setting ofoption option 2.

Explanation: The value specified for the first option isignored because the second option takes precedence.

System action: The default value of the option isused. Server operation continues.

User response: Modify the values for one or both ofthe server options so that they no longer conflict.Restart the server.

ANR3242E command: Replication server server Nameis currently being deleted by aREMOVE REPLSERVER command.

Explanation: When you issue the REMOVEREPLSERVER command, the replication server that youspecify to remove is already in the process of beingdeleted as a result of a previous REMOVEREPLSERVER command.


User response: Issue the QUERY REPLSERVERcommand to verify the current status of the replicationserver. Verify that the replication GUID specified iscorrect for the server you are deleting.

ANR3243E command: Replication server server Nameis currently being deleted by a previousREMOVE REPLSERVER command.

Explanation: When you issue the REPLICATE NODE

command, the default replication server is already inthe process of being deleted as a result of a previousREMOVE REPLSERVER command.


User response: Issue the QUERY REPLSERVERcommand to verify the current status of the replicationserver. Update the default replication server with theSET REPLSERVER command.

ANR3244E Session session number for server servername error - replication server iscurrently being deleted by a previousREMOVE REPLSERVER command.

Explanation: At the start of a REPLICATE NODEprocess on a target server, the replication server isalready in the process of being deleted on the targetserver as a result of a previous REMOVE REPLSERVERcommand.


User response: Issue the QUERY REPLSERVERcommand to verify the current status of the replicationserver. Update the default replication server with theSET REPLSERVER command.

ANR3245W Session session number for node nodename (client platform) - no failoverconnection information found for serverserver name.

Explanation: During client sign-on, there was nofailover server connection information stored. This iscaused when you issue the REMOVE REPLSERVERcommand on the failover server that is defined in theassociated node definition. No change is made to thestored failover server connection information in theclient option file. The client will fail over to the lastknown failover server.


User response: No action is needed if the failoverserver in the client option file is still valid. Replicate thenode to the default target replication server in order toupdate the node's failover server.

ANR3246W Process process ID skipped Num Filesfiles on volume Volume name because thefiles have been deleted.

Explanation: Some of the files that were encounteredduring the move operation were skipped because theyhave already been deleted.

System action: The operation skips the files withoutmaking copies and continues.




ANR3247W Process process ID skipped Num Filesfiles on volume Volume name because ofpending fragments.

Explanation: Some of the files that were encounteredduring the move operation were skipped because theycontained pending fragments.

Large files that are stored in deduplication-enabledstorage pools are split into smaller pieces or fragmentsfor performance reasons. When fragments are copied ormoved to another storage pool, they are markedpending until all fragments that comprise the file arriveat the target storage pool. The pending state is removedfrom the fragments once all fragments have beensuccessfully moved.


User response: Server processes such as BACKUPSTGPOOL, MOVE DATA, MOVE NODEDATA andstorage pool migration can result in fragments beingmarked as pending. You can issue the QUERYPROCESS command to see whether any of theprocesses are running. If so, retry the operation at alater time when the fragments are not pending.

ANR3248W Process process ID skipped Num Filesfiles on volume Volume name because itwas unable to lock all segments.

Explanation: The files were skipped because theprocess was unable to lock all segments of the files.


User response: Retry the operation.

ANR3249W The process desc process with process IDprocess id is canceled by the processmonitor.

Explanation: The process is canceled because themount wait time for the input or output volume hasexceeded the mount wait limit that is set through theMOUNTWAITRESOURCELIMIT server option. Eitherthere is a problem with a mount point, or the mountwait limit is set too low.


User response: Check the setting for theMOUNTWAITRESOURCELIMIT server option andincrease the value. If the problem persists with a highervalue, contact your service representative.

ANR3250E Command: Directory directory is notdefined in storage pool storage pool.

Explanation: A nonexistent storage pool directory isspecified for the issued command.


User response: Reissue the command with a validstorage pool directory. If you are using the MACROcommand to define and update the storage pooldirectory, you must ensure that the DEFINESTGPOOLDIRECTORY command is committed beforethe UPDATE STGPOOLDIRECTORY command isissued.

ANR3251E Command: Storage pool stgpool name isnot a container storage pool.

Explanation: The storage pool specified is invalid forthe command.


User response: Reissue the command with a validstorage pool. Only container storage pools may be usedwith STGPOOLDIRECTORY commands.

ANR3252E Command: Directory directory is alreadydefined in storage pool storage pool.

Explanation: An already existing storage pooldirectory is specified for the issued command.


User response: Reissue the command with a valid,unique storage pool directory.

ANR3253W A client operation that was started byschedule schedule name is running longerthan the maximum run time expectedfor client node name.

Explanation: When you defined or updated theschedule, you set a maximum run time for clientoperations that are associated with the schedule.Alternatively, in the Operations Center, you set an endtime for the client operations. A client operation startedas scheduled, but the operation is running after the endtime or for longer than the maximum run time.

System action: The server issues this warningmessage, and the client operation continues.


ANR3254I Storage pool directory storage pooldirectory name was defined in storagepool stgpool name.

Explanation: A DEFINE STGPOOLDIRECTORYcommand has created the storage pool directoryindicated of the storage pool shown.





ANR3255I Storage pool directory storage pooldirectory name deleted.

Explanation: A DELETE STGPOOLDIRECTORYcommand has deleted the storage pool directoryindicated.



ANR3256I Storage pool directory storage pooldirectory name updated.

Explanation: An UPDATE STGPOOLDIRECTORYcommand has updated the storage pool directoryindicated.



ANR3257W command: Filespace identifier fsId is notdefined for node node name.

Explanation: A filespace identifier specified in theREPLICATE NODE command is not defined for theindicated node.

System action: The replication operation continues forany other valid filespace identifiers specified.

User response: Use the QUERY FILESPACE commandto verify the list of filespace identifiers provided in theREPLICATE NODE command.

ANR3258E Command: Device class device class namehas a device type of SERVER and thesource server name is the same as thetarget.

Explanation: The specified device class has a devicetype of SERVER and the source and target servernames are the same. IBM Spectrum Protect serverdatabase backups cannot be restored from virtualvolumes that are on the same IBM Spectrum Protectserver that was used to complete the backups.


User response: Ensure that the virtual volumes arenot on the IBM Spectrum Protect server that is beingbacked up and that the names of the source and targetservers are unique.

ANR3259W Session session number for node nodename (client platform) refused -$$_TSMDBMGR_$$ node from anuntrusted system is not allowed.

Explanation: The server refuses the specified clientsession because node $$_TSMDBMGR_$$ is allowedonly from the trusted system for IBM Spectrum Protectdatabase backup or restore.


User response: Use $$_TSMDBMGR_$$ node from thetrusted system for IBM Spectrum Protect databasebackup or restore.

ANR3260E Database backup terminated due to apage validation failure that occurredduring a backup - DB2 sqlcode sqlcodesqlerrmc sqlerrmc. This might indicatecorruption in the database, requiring adatabase restore or other repair action tocorrect.

Explanation: A page validation error was detected byDB2 and the error caused the database backup to fail.

System action: If a full database backup was inprogress to free space in the archive log directory, takeone of the following actions:

v Increase the amount of space in the archive logdirectory.

v Use the ARCHFAILOVERLOGDIRECTORY option tospecify a failover archive log directory in which theserver can store log files that cannot be stored in thearchive log directory.

For assistance in diagnosing and repairing any databasecorruption, contact IBM Software Support.

ANR3261W An automatic full or incrementaldatabase backup will be started. Theactive log space used is log space used ismegabytes, and the active log spaceavailable is log space available megabytes.The ratio, active log used ratio, exceeds thethreshold log utilization threshold.

Explanation: When the active log space used exceedsthe log utilization threshold, a database backup isstarted. If there has been at least one full databasebackup, the backup is an incremental database backup.Otherwise, a full database backup is started.



ANR3262W A full database backup might berequired. The last log number used islast log used and the first log numberused is first log used. The log file size islog file size megabytes. The maximum logfile size is maximum log file sizemegabytes.

Explanation: When the log space used since the lastdatabase backup exceeds the maximum log file size,either a full database backup is required, or themaximum log file size must be increased.





ANR3263E Command: The CLOUD storage type canonly be used with a POOLTYPE ofPRIMARY.

Explanation: An attempt is made to define aPOOLTYPE using a storage type of CLOUD. Storagepools with a POOLTYPE other than PRIMARY can onlybe assigned to storage pools with a DEVCLASS storagetype.


User response: Reissue the command specifying asequential device class or ommiting the POOLTYPE.

ANR3264W A full database backup is needed. Theactive log space used is log space used ismegabytes, and the active log spaceavailable is log space available megabytes.The ratio, active log used ratio, exceeds thethreshold log utilization threshold.

Explanation: When the active log space used exceedsthe log utilization threshold, a database backup isneeded.



ANR3265W A full database backup will be started.The archive log space used is archivelog% and the archive log space usedthreshold is arch log threshold%.

Explanation: When the archive log space used exceedsthe threshold, a full database backup will be started.



ANR3266E Replication of node node name to targetreplication server target server failed. Thereason is that a required policy domainis not defined on the target server.

Explanation: If you plan to replicate a node, but thenode does not exist on the target server, you mustensure that an appropriate policy domain is defined forthe node on the target server.

System action: The data that belongs to the node wasnot replicated, but server operations continue.

User response: To replicate the node, take one of thefollowing actions:

v Define the policy domain that is used for the nodeon the source server to the target server.

v Define the STANDARD policy domain on the targetserver.

Then, restart the node replication process.

ANR3267E The storage pool stgpool name cannot bedefined as a container storage pool withthis operating system.



User response: Use an operating system that iscompatible with IBM Spectrum Protect to issue thecommand. For information about operating systemsthat are supported by IBM Spectrum Protect, seetechnote 1243309 "Overview - IBM Spectrum ProtectSupported Operating Systems" (http://www-01.ibm.com/support/docview.wss?uid=swg21243309).

ANR3268W Storage pool directory storage pooldirectory name access failed.

Explanation: The server was unable to access thespecified storage pool directory. Either the file system isnot available or permissions to the storage pooldirectory prevent access.


User response: Verify that the underlying file systemis mounted correctly and is available. Verify that theserver has full access permissions to the storage pooldirectory.

ANR3269E Command: Storage pool access mode forpool pool name cannot be changed fromUNAVAILABLE because the masterencryption key is not available.

Explanation: The storage pool access mode cannot bechanged because the pool is encrypted or containsencrypted data, and the server master encryption key isnot available.


User response: Review the activity log for errorsrelated to either the server master encryption key or theserver password file. Correct any problems that preventthe master encryption key being read from the serverpassword file. If necessary, rename the server keydatabase, dsmkeydb.kdb, and its password stash file,dsmkeydb.sth, and recover an earlier version of the keydatabase from a backup. Restart the server. Reissue theUPDATE STGPOOL command to change the storagepool ACCESS setting.



ANR3270E Command: Unsupported option - option

Explanation: The command shown specifies a clientoption for a client option set, which is no longersupported.


User response: Reissue the command with a validclient option.

ANR3271W Command: Deprecated option - option

Explanation: The command shown specifies adeprecated client option for a client option set. Whilethe specified option will be processed, it will be madeobsolete at a future date.

System action: The server processes the command.

User response: Be prepared to remove the clientoption from the client option set in the future.

ANR3272E Server server name does not supportreplication using fasp as the transfermethod.

Explanation: In response to a REPLICATE command,the server attempted to establish a connection to thereplication target. But the target server does notsupport fasp as the transfer method.

System action: Server operation continues. Thereplication fails.

User response: Make sure the replication target is atthe correct maintenance level and verify that theglobally unique ID (GUID) of the target server isproperly set. Use the tivguid utility to set the GUID ifnot properly set.

ANR3273I Using Active Directory Domain LDAPDN for LDAP Authentication.

Explanation: The Active Directory Domain wasdetermined from the LDAP server base context.



ANR3274I Running in LDAP Legacy Mode.

Explanation: The Server is running in LDAP LegacyMode which requires an LDAP Administrator ID andan Organizational Unit which is specific to the server.



ANR3275I Running in LDAP Integrated Mode.

Explanation: The Server is running in LDAPIntegrated Mode which allows existing LDAP users tobe registered to the server while managed through theLDAP server.



ANR3276I The server starts one or morebackground processes to update thedatabase entries for data that is storedin the storage pool directory storage pooldirectory name.

Explanation: Processes have been started in thebackground to update a stgpooldir.



ANR3277E Command: Storage rule rule is alreadydefined.

Explanation: An existing storage rule is specified forthe command.


User response: Reissue the command with a valid,unique storage rule name.

ANR3278I Storage rule storage rule was defined.

Explanation: A DEFINE STGRULE command hascreated the storage rule indicated.



ANR3279E Command: Storage pool pool is already inuse for another storage rule.

Explanation: A storage rule exists for the specifiedstorage pool.


User response: Reissue the command with a valid,unique source storage pool.

ANR3280I Storage rule rule name deleted.

Explanation: A DELETE STGRULE command hasdeleted the storage rule indicated.





ANR3281E Command: Storage rule rule name is notdefined.

Explanation: The storage rule name that is specifiedfor the command does not exist.


User response: Reissue the command with a validstorage rule name.

ANR3282I Storage Rule rule name updated.

Explanation: The storage rule was updated by theUPDATE STGRULE command.



ANR3283E Storage Rule rule name deletion failedbecause process is currently active.

Explanation: The storage rule deletion failed becausethere is currently an active process.

System action: The storage rule deletion fails.

User response: Try again when the storage rule is notrunning.

ANR3284W Tiering process process ID terminated forstorage pool storage pool name - durationexceeded.

Explanation: During a storage pool tiering action forthe indicated storage pool, a process performing thetiering has been terminated because the tieringduration has exceeded.

System action: The tiering process is terminated.


ANR3285W GSKit version GSKit version is below theminimum supported version of minimumGSKit version.

Explanation: The version of the IBM Global SecurityKit (GSKit) libraries that is in use by the server isbelow the minimum supported version. Unexpectederrors might occur as a result of using down-levelGSKit libraries.


User response: Review the instructions in IBMKnowledge Center for creating a server instance. Verifythat the library path was modified to use the version ofGSKit that is installed with the server.

ANR3286E Command: Update Storage Rule failedfor rule rule name because the specifiedparameters are not valid for Action Typerule action type.

Explanation: The Storage Rule update failed becauseone or more parameters are not valid for the ActionType of the specified Storage Rule.

System action: The Storage Rule update fails.

User response: Verify the command syntax andreissue the command.

ANR3287E Command: The DEFINE STGRULEcommand failed for rule rule namebecause the specified parameter optionname is not valid for action type ruleaction type.

Explanation: The operation failed because one or moreparameters are not valid for the action type of thespecified storage rule.

System action: System operation continues, but theDEFINE STGRULE command fails.

User response: Verify the command syntax andreissue the DEFINE STGRULE command.

ANR3288E The DEFINE STGRULE command failedfor rule rule name because a rule alreadyexists for storage pool pool name andaction type rule action type.

Explanation: The operation failed because a storagerule already exists for the action type and specifiedstorage pool.

System action: System operation continues, but theDEFINE STGRULE command fails.

User response: Verify the command storage pool andreissue the DEFINE STGRULE command.

ANR3289E Command: Protect in progress preventsmoving container for storage pool storagepool.

Explanation: A storage pool directory can not bemoved while it is undergoing protect.


User response: Reissue the command once protect hascompleted.

ANR3297I Objects were deleted from volumevolume name , node node name , and filespace filespace .

Explanation: The server deleted the indicated number



of objects for the reported node and file space from thereported volume.


User response: This message is for informationalpurposes only.

ANR3300W The FILELIST file named list file namedoes not contain any valid directories.

Explanation: The server detected that the FILELISTfile does not contain any valid directories.

System action: The RESTORE DB operation fails.

User response: Update the FILELIST file to include atleast one valid directory.

ANR3301E The EXTEND DBSPACE failed becausedatabase backup processing is active.

Explanation: The database backup and EXTENDDBSPACE processing are in conflict and cannot beactive simultaneously.

System action: The EXTEND DBSPACE operationfailed and is terminated.

User response: Rerun the EXTEND DBSPACE afterthe database backup completes.

ANR3302E The database backup failed becauseEXTEND DBSPACE processing is active.

Explanation: The database backup and EXTENDDBSPACE processing are in conflict and cannot beactive simultaneously.

System action: The database backup operation failedand is terminated.

User response: Rerun the database backup afterEXTEND DBSPACE processing completes.

ANR3335W Unable to distribute certificate to Id forsession session number.

Explanation: An SSL certificate could not bedistributed to the requesting server, node oradministrator because the value of the associatedSESSIONSECURITY parameter is set to STRICT.

For server-to-server sessions, each server must have thecertificate of the partner server in the server keydatabase. Nodes and administrators must have thecertificates for each server to which they connect.Certificates are distributed automatically, but aresubject to restrictions that are specified by theSESSIONSECURITY parameter.

System action: The requested certificate is notdelivered. Operations that require the certificate mightfail.

User response: Manually add the certificate to the key

database of the requesting server. For informationabout configuring SSL connections, see the instructionsin IBM Knowledge Center. To verify security settings,issue one of the following commands: QUERY ADMINadminname F=D QUERY NODE nodename F=DQUERY SERVER servername F=D

ANR3336W Default certificate labeled Label in keydata base is down level.

Explanation: The default label in the key data base isdown level.

System action: Consider updating default certificate toa more secure certificate.


ANR3337I Option option value added to serveroptions file.

Explanation: The indicated option and value werewritten to the server options file as part of the set ofoptions needed to secure communication at TLS level1.2 or higher. When the server key data base is created,this set of options is written to the server options file;These options are in effect immediately, as part of thestartup process.


User response: All clients contacting the server afterthe server comes up and which use SSL/TLScommunications should be configured to use TLS 1.2.Clients using the server self-signed certificate shouldhave the server exported certificate file, cert256.armadded to their key data base. If TLS 1.2 is not suitablefor SSL communications, the following options in theserver options file should be modified: SSLTLS12 (ifpresent), SSLDISABLELEGACYTLS, andSSLHIDELEGACYTLS should be changed to NO. Youmay also have to change the default label in theserver's key data base, if using self-signed certificates,to "TSM Server SelfSigned Key".

ANR3338E Session with node or system at addresshladdress failed due to use of TLS atlevel SSL Level instead of TLS 1.2 orhigher.

Explanation: When the server or storage agent optionSSLDISABLELEGACYTLS is set to YES, the serverenforces a TLS level of 1.2 or higher. If TLS is at a levellower than 1.2 or if any level of SSL is used, the sessionfails. Likewise, if the SESSIONSECURITY setting for theentity (node, administrator, or server definition) is setto STRICT, then TLS 1.2 or higher is also required. Ifthe SESSIONSECURITY parameter is set toTRANSITIONAL and the entity successfullyauthenticates by using TLS 1.2, that connection isremembered and the entity can no longer authenticateat a lower level.



System action: The session fails. Server or storageagent operation continues.

User response: Reconfigure the client or server to useTLS 1.2. Until the client or server that is receiving thismessage is using TLS 1.2, the server or storage agentwill continue to reject the session.

ANR3339I Default Label in key data base is Label.

Explanation: The default SSL label in the key database is displayed.

System action: Server or storage agent operationcontinues.


ANR3340W The CLEANUP REPLGROUPScommand failed or some records wereskipped. Issue the command again toclean up orphan records.

Explanation: The cleanup replgroups process mayskip orphan records from being deleted. Some commonreasons for this error are:

1. The node is currently replicating.

2. The cleanup replgroups process is cancelled.

3. Unexpected internal errors, which can be displayedthe activity log.


User response: Review the activity log for errors.Correct the error and issue the command again.

ANR3341I Process process ID was started todecommission node name.

Explanation: When you run the DECOMMISSIONNODE command, a process is started to prepare thenode for decommissioning and deactivating backupfiles for the node.

System action: The Decommission process can becanceled. Server operation continues.

User response: No action is required. However, youcan query the process by using the QUERY PROCESScommand: query process process_number You cancancel the process by using the CANCEL PROCESScommand: cancel process process_number

ANR3342I The process of decommissioning a nodewas canceled.

Explanation: The CANCEL PROCESS command wasissued to end the process of decommissioning a node.The process will end shortly.

System action: The decommission process will end,but server operation continues.


ANR3344E Command: An error occurred whiledeactivating data for node name.

Explanation: An error occurred while deactivatingbackup files for the specified node.

System action: The DEACTIVATE DATA command isended, but server operation continues.


ANR3345I Process process ID was started todeactivate data for node name.

Explanation: When you run the DEACTIVATE DATAcommand, a process begins to prepare the node fordeactivation of its active backup files.

System action: The deactivation process can becanceled. Server operation continues.


ANR3346I A process to deactivate backup files fora node was canceled.

Explanation: Cancellation is in progress. The processwill end shortly.

System action: The process for deactivating backupfiles is ending, but server operation continues.


ANR3348E Command: The process of deactivatingdata for node name failed.

Explanation: An error occurred while deactivatingbackup files for the specified node.

System action: The DEACTIVATE DATA command isended, but server operation continues.


ANR3349W Command: This command will deactivatedata. Active backup files that werecreated for the specified node on thedeactivation date or earlier will bedeactivated.

Explanation: The DEACTIVATE DATA commanddeactivates backup files for a specified node.

System action: You will be prompted to continue, orto cancel the command.

User response: Enter 'Y' to continue or 'N' to end thecommand.



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 thisdomain 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 youwant 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 notbe 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 SCHEDULE commandOR 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 onthe 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, themanaged 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.

ANR3378I Administrator administrator name addedduring configuration refresh processing.

Explanation: During configuration refresh processing,the indicated administrator definition was createdbased on information from the configuration manager.



ANR3379E Command: Unable to access pool poolname - access mode is set to "read only".

Explanation: The command shown specifies the poolwhose name is displayed, but the pool cannot beaccessed because its status is read only.


User response: Either reset the access state of the poolor choose another pool and reissue the command.

ANR3380E Command: Unable to access pool poolname - access mode is set to"unavailable".

Explanation: The command shown specifies the poolwhose name is displayed, but the pool cannot beaccessed because its status is unavailable.



ANR3381W This command will removeadministrator user ID. This administratoris defined to alert triggers or assigned toalerts. The command will remove theadministrator from those alert triggersand alerts.

Explanation: A REMOVE ADMINISTRATORcommand was issued for the specifie d administrator. Ifyou confirm the command, the administrator will beremoved from the alert triggers and alerts.

System action: The system will run or cancel thecommand, depending on your response.

User response: To run the REMOVEADMINISTRATOR command, enter 'Y'. To cancel thecommand, enter 'N'. To find the alert triggers to whichthe administrator is defined, use the QUERYALERTTRIGGER command or an SQL SELECTstatement on the TSM_MON_ALERTTRIG table. Tofind the alerts that are assigned to the administrator,use the QUERY ALERTSTATUS command or an SQLSELECT statement on the TSM_MON_ALERT table. Toupdate the alert triggers and modify the list ofadministrators who receive an email for the alerts, usethe UPDATE ALERTTRIGGER command. To assign thealert to another administrator, use the UPDATEALERTSTATUS command.

ANR3382W This command will renameadministrator user ID. This administratoris defined to alert triggers or assigned toalerts. If this administrator is renamed,the administrator of the alert triggersand alerts will also be renamed.

Explanation: A RENAME ADMINISTRATORcommand was issued for an administrator who isdefined to alert triggers or assigned to alerts. If youconfirm this command, the administrator for those alerttriggers and alerts will be renamed.

System action: The system will run or cancel thecommand, depending on your response.

User response: To run the RENAMEADMINISTRATOR command, enter 'Y'. To cancel thecommand, enter 'N'. To review alerts that are assignedto the administrator, use the QUERY ALERTSTATUScommand. To manage alerts that are assigned to theadministrator, use the UPDATE ALERTSTATUScommand. To review alert triggers, use the QUERYALERTTRIGGER command. To update alert triggers,use the UPDATE ALERTTRIGGER command.

ANR3383E command: Administrator user ID is themonitoring administrator and cannot beremoved or renamed.

Explanation: Because the specified administrator isused for communications between hub and spoke



servers, the administrator cannot be removed orrenamed.


User response: To remove or rename theadministrator, complete the following steps: 1. Issue theSET MONITORINGADMIN command to change themonitoring administrator for your hub server and forcorresponding spoke servers. 2. Remove or rename theadministrator.

ANR3384E command: Server group group name, is themonitored server group and cannot bedeleted or renamed.

Explanation: The specified server group is in use asthe monitored server group and cannot be deleted orrenamed.


User response: Use the SETMONITOREDSERVERGROUP command to remove itas the monitored server group. Then you can delete orrename the server group.

ANR3385E command: The operation is not allowedfor container storage pools.

Explanation: The specified storage pool is a containerstorage pool. You cannot issue the following commandswith container storage pools:

v BACKUP STGPOOL

v RESTORE STGPOOL

v MIGRATE STGPOOL

v IDENTIFY DUPLICATES

v RECLAIM STGPOOL

v AUDIT VOLUME

v MOVE NODEDATA

v MOVE DATA

v RESTORE VOLUME

v PREPARE

You must use a primary random, primary sequential,copy, or active-data storage pool to complete thesefunctions.

System action: The command fails and the serveroperation continues.

User response: Issue the PROTECT STGPOOLcommand to protect the contents of directory-containerstorage pools.

ANR3386E Insufficient authority to create filesystem object object name.

Explanation: An attempt to create a file or directoryfailed with insufficient authority.

System action: The operation fails and serveroperations continue.

User response: Check the permissions of the directoryleading up to the object being created. Ensure theuserid under which the server is executing has thenecessary permission to create objects in this directory.Retry the operation.

ANR3387W Command: This command will add,update, or delete alert triggers.

Explanation: A command has been issued that willadd, update, or delete alert triggers on your server.



ANR3388W Command: This commanddecommissions the client node anddeletes data. Active files are deactivated,and data is deleted as it expires.

Explanation: A command has been issued that willdecommission the node.



ANR3389E Command: Node name is alreadydecommissioned.

Explanation: You cannot decommission the nodebecause it is already decommissioned withdecommission state YES.


User response: You can use QUERY NODEFORMAT=DETAIL command to see the decommissionstate of the node and the date it was decommissioned.You can reissue the command on a node that does nothave decommissioned state of Yes.

ANR3390W Alert trigger message number is no longervalid and will be deleted.

Explanation: The alert trigger is obsolete because it isassociated with a server message that no longer exists.

System action: The alert trigger will be automaticallydeleted by the server. Server operation continues.




ANR3391E command: The operation is not allowedfor cloud storage pools.

Explanation: The specified storage pool has a cloudstorage type. You cannot issue the following commandswith cloud storage pools:

v BACKUP STGPOOL

v RESTORE STGPOOL

v MIGRATE STGPOOL

v IDENTIFY DUPLICATES

v RECLAIM STGPOOL

v PREPARE

You must use a primary random, primary sequential,copy, or active-data storage pool to complete thesefunctions.


User response: To back up a storage pool that uses aDEDUP device class, issue the PROTECT STGPOOLcommand to protect the contents of the storage pool.

ANR3392W Command: This command willdecommission the specified virtualmachine. The active files that belong tothe virtual machine will be inactivated,and the file space of the virtual machinewill be automatically deleted after its allthe files are expired.

Explanation: A command was issued to remove thespecified virtual machine from the productionenvironment.


User response: Enter 'Y' to continue or 'N' to cancelthe command.

ANR3393E Command: Virtual machine virtual machinename in node name is alreadydecommissioned.

Explanation: The specified virtual machine cannot bedecommissioned because it already has a decommissionstate of Yes.

System action: The virtual machine remainsdecommissioned and server operation continues.

User response: To view the date when the virtualmachine was decommissioned, issue the followingcommand: query filespace format=detailed Todecommission a different virtual machine, reissue theDECOMMISSION VM command for that virtualmachine.

ANR3394I Process process ID was started todecommission virtual machine virtualmachine name on node name.

Explanation: When you run the DECOMMISSION VMcommand, a process is started to prepare the virtualmachine for the decommission operation and todeactivate backup files for the virtual machine.

System action: The decommission process is inprogress.


ANR3395I The process of decommissioning avirtual machine was canceled.

Explanation: The CANCEL PROCESS command wasissued to end the decommission operation. Theoperation will end shortly.

System action: The decommission operation will end,but server operation continues.


ANR3397E Command: An error occurred whiledeactivating data for virtual machinevirtual machine name.

Explanation: An error occurred while deactivatingbackup files for the specified virtual machine.

System action: The DECOMMISSION VM commandhalts, but server operation continues.

User response: No action is required. However, toresolve the issue, review the dsmffdc.log anddsmserv.err files and correct any reported errors.

ANR3398E Command: File space FSID could not befound.

Explanation: The file space ID is not valid.

System action: The server does not process thecommand, but server operation continues.

User response: To resolve the issue, complete thefollowing steps: 1. To obtain the file space ID of thevirtual machine, issue the following command: queryfilespace 2. Reissue the command on the virtualmachine.

ANR3399E Command: Virtual machine virtual machinename could not be found.

Explanation: The command failed because the virtualmachine name is invalid.

System action: The server does not process the



command, but server operation continues.

User response: To resolve the issue, complete thefollowing steps: 1. Issue the following command: select* from filespaceview 2. To determine the name of thevirtual machine, review the output: - If theENTITYNAME field is not blank, the name in the fieldis the virtual machine name. - If the ENTITYNAMEfield is blank, go to the FILESPACE_NAME field todetermine the name of the virtual machine. 3. Reissuethe command on the virtual machine.

ANR3400I Command: Output stream stream usedvolume volume name.

Explanation: The specified output stream used thespecified volume.



ANR3401I Command: Output stream stream did notwrite to any output volumes.

Explanation: The specified output stream did notwrite to any output volumes.



ANR3402I Extractdb command: Process processnumber, database extract, has completed.

Explanation: The database extract process processnumber has completed.

System action: Database extract processing ends.


ANR3403I Extractdb command: Found number ofdatabase objects database objects.

Explanation: This message indicates the total numberof database objects that were found during databaseextract processing.



ANR3404I Extractdb command: Processed number ofdatabase objects database objects.

Explanation: This message indicates the total numberof database objects that were successfully processedduring database extract processing.



ANR3405I Extractdb command: Skipped number ofdatabase objects empty database objects.

Explanation: This message indicates the total numberof database objects that were skipped during databaseextract processing because they contained no records.



ANR3406I Extractdb command: Failed to processnumber of database objects databaseobjects.

Explanation: This message indicates the total numberof database objects that were not successfully processedduring database extract processing.



ANR3407I Extractdb command: Processed number ofdatabase records database records.

Explanation: This message indicates the total numberof database records that were successfully extractedduring database extract processing.



ANR3408I Extractdb command: Wrote number of bytesbytes.

Explanation: This message indicates the total numberof bytes that were successfully written during databaseextract processing.



ANR3409I Extractdb command: Elapsed time waselapsed time.

Explanation: This message indicates the total amountof time that elapsed during database extract processing.



ANR3410I Extractdb command: Throughput wasmegabytes per hour megabytes per hour.

Explanation: This message indicates the totalthroughput (megabytes/hour) during database extractprocessing.





ANR3411I Extractdb command: Extracted number ofdatabase records database entries andwrote number of bytes bytes in elapsed time(megabytes per hour megabytes per hour).

Explanation: The command read the indicatednumber of data base records, and wrote the indicatednumber of bytes.



ANR3412I Extractdb command: Terminating outputstream stream number due to error onserver server name.

Explanation: An error was encountered on the targetserver during a server-to-server upgrade process,resuting in the termination of the output stream beingused to send database information to the target server.


User response: Refer to the target server's messagesfor a description of the error. Correct the error andrerun the command.

ANR3413W Extractdb command: Encountered anunexpected table, table name. The tablewill be skipped.

Explanation: The database extract process encountereda table that it did not expect. In most cases, anunexpected table is one that was used in an earlierrelease, but which is no longer used in the currentrelease. Such tables can be safely ignored by thedatabase extract process. However, in rare cases, thismay indicate a programming error. As such, youshould contact your service representative to confirmwhether the table may be ignored without affecting thesuccess of the upgrade process.

System action: Database extract processing continues.Data from the specified table is not extracted.

User response: Contact your service representative toconfirm whether the specified table can be safelyignored.

ANR3414E Extractdb command: Process processnumber, database extract, has completedwith errors.

Explanation: The database extract process processnumber has completed, but errors were encountered bythe process.

System action: Database extract processing ends.

User response: Review any messages that were issuedby the process, and take corrective action asappropriate.

ANR3415I The server is in maintenance mode.

Explanation: The server is in maintenance mode. Thefollowing services are disabled:

v Client sessions

v The scheduler

v Automatic inventory expiration

v Automatic volume reclamation

v Automatic storage pool migration

System action: Server operation continues; howeverrestricted services are disabled.

User response: If you want to exit maintenance mode,use the HALT command to stop the server, and restartit.

ANR3416I The server is in maintenance mode.Client sessions cannot be enabled.

Explanation: The server is in maintenance mode.Client sessions are disabled and cannot be reenableduntil normal operation resumes.

System action: Client sessions are not enabled.

User response: If you want to exit maintenance mode,use the HALT command to stop the server, and restartit.

ANR3417W Database backup page verification isdisabled.

Explanation: Pages that are backed up from the DB2database are not being verified. A possible cause is thatIBM Software Support requested or enabled thischange.

System action: The database backup continues, butinvalid or corrupted database pages might not bedetected.

User response: If IBM Software Support directed youto disable database backup page verification, no actionis required.

If IBM Software Support did not direct you to disabledatabase backup page verification, reenable the featureto gain the additional protection that it provides.

ANR3418W Invalid storage pool directory specified:stgpooldir Error: Error.

Explanation: The storage pool directory specified inthe DEFINE STGPOOLDIRECTORY command does notexist or has invalid permissions.

System action: The command is processed, but thestorage pool directory is marked as UNAVAILABLE.

User response: To store data in the storage pooldirectory, verify that the directory exists and has validpermissions. Then, update the access state of thestorage pool directory to READWRITE.



ANR3419E Directory name directory name wasduplicated when the parameter commandwas issued.

Explanation: When you define or update multipledirectories for a container storage pool, you can specifya directory name only once in the command.

System action: The command fails. Server operationcontinues.

User response: Ensure that the directory name isspecified only once in the command.

ANR3420E Command: Node name is not a validapplication type node.

Explanation: You cannot deactivate a node which isnot valid application type node.



ANR3421E Invalid access state for storage pooldirectory stgpooldir.

Explanation: There is an invalid access state tocomplete the operation for the storage pool directory.The required access state is READWRITE.


User response: Verify that the directory has the correctwrite-access. Then, issue the UPDATESTGPOOLDIRECTORY command for the storage pooldirectory and specify the ACCESS=READWRITEparameter.

ANR3422W Invalid access state for storage pooldirectory stgpooldir.

Explanation: The access state for the storage pooldirectory is invalid. The access state must beREADONLY or READWRITE to complete thisoperation.


User response: Verify that the directory has at leastread access. Then, issue the UPDATESTGPOOLDIRECTORY command for the storage pooldirectory and specify the ACCESS=READWRITE orACCESS=READONLY parameter.

ANR3423E Proxy Session session number was notinitiated by an authorized user.

Explanation: A Proxy Session must be run as anauthorized user. An authorized user is any non-rootuser who has read and write access to the client stored

password (TSM.PWD file), or anyone who knows theclient password and enters it interactively. Authorizedusers can use the client passworddir option to definethe directory where their copy of the TSM.PWD file issaved.

System action: The session is ended. Systemprocessing continues

User response: Re-configure your client session as anauthorized user or connect to the server or storageagent as an authorized user.

ANR3424E Command: You must specify adirectory-container storage pool. Storagepool stgpool name is not adirectory-container storage pool.

Explanation: The command is valid only for adirectory-container storage pool.


User response: Specify the name of adirectory-container storage pool with the command.

ANR3425W Data in container-copy storage poolvolume volume name cannot be retrieved- access mode is not READWRITE orREADONLY.

Explanation: During processing of a REPAIRSTGPOOL command, data in a container-copy storagepool volume cannot be restored because the volume'saccess mode is not READWRITE or READONLY.

System action: The server repairs damaged extentsusing copies in the container-copy storage pools that itcan access, but it skips over damaged extents that existonly on offsite volumes.

User response: If the volume is stored at an offsitelocation, bring the volume onsite. Use the MOVEDRMEDIA command to change the access mode for thevolume to READWRITE or READONLY, and reissuethe REPAIR command.

ANR3426I Container-copy storage pool volumevolume name is required for repairprocessing.

Explanation: During processing of a REPAIRSTGPOOL command, the server determines that aremovable volume is required.





ANR3427E Command: Storage pool storage pool namedoes not have data protected to its localcontainer-copy storage pools.

Explanation: The command indicated references astorage pool that has not been protected by the LOCALPROTECT.


User response: Reissue the command after protectingdata from the storage pool specified to its containercopy storage pools.

ANR3428E Command: Unable to encrypt storagepool storage pool name - encryption isunavailable for the storage pool.

Explanation: The storage pool cannot be encryptedbecause the encryption is unavailable for this storagepool.


User response: Enable encryption for this storage poolby issuing the UPDATE STGPOOL command andspecifying the ENCRYPT=YES parameter.

ANR3429E Command: You must specify acloud-container storage pool. Storagepool stgpool name is not acloud-container storage pool.

Explanation: The command is valid only for acloud-container storage pool.


User response: Specify the name of a cloud-containerstorage pool with the command.

ANR3430E Command: You must specify acloud-container storage pool that isenabled for action type action_type.Storage pool stgpool name is a cloud typecloud-container storage pool and is notenabled.

Explanation: You can issue this command forcloud-container storage pools that use Microsoft Azureor Simple Storage Service (S3) protocol only.


User response: Specify the name of a cloud-containerstorage pool with a cloud type of either AZURE or S3.

ANR3431E Command: Unable to access pool poolname - access mode is set to "destroyed".

Explanation: The command shown specifies the poolwhose name is displayed, but the pool cannot beaccessed because its status is destroyed.



ANR3485W The hub server is running an earlierversion than the spoke server.

Explanation: The version of IBM Spectrum Protectserver that is installed on the hub server must be atleast the same version that is installed on a spokeserver.

System action: The hub server continues to receivealerts and status information from the spoke server, butunexpected behavior might occur.

User response: Upgrade the version of IBM SpectrumProtect server that is running on the hub server. It mustbe at least the same version as the spoke server.

ANR3486I CANCEL SESSION ALL commandprocessing ended sooner than expected.

Explanation: It is possible that the server was unableto cancel all sessions because a session wasencountered that could not be cancelled. Some sessionsmay still remain active after the command completes.

System action: Server operation completes.

User response: Specify a session_number with theCANCEL SESSION command to cancel a specificCLIENT session. If a SERVER session is active, thepartner server must be quiesced for the session to end.The SERVER session may be active with a StorageAgent, Library Client, Library Server or Virtual Volumeserver. To prevent new sessions from starting, see theDISABLE SESSIONS command.

ANR3487E Command: The number of administratorsexceed the maximum number allowed.

Explanation: The number of administrators that canreceive alert summary by email is limited to three.


User response: Reissue the command specifying amaximum of three registered administrator names.



ANR3488W Command: The administrator administratorname does not have an email address.

Explanation: The administrator does not have anemail address defined. The specified administratorcannot receive email from the server until a valid emailaddress is defined.

System action: The command processing continues.

User response: Issue UPDATE ADMIN command todefine the email address and reissue the command.

ANR3489I Command completed successfully.

Explanation: The specified SET command completedsuccessfully.



ANR3490E Command completed with failure.

Explanation: The specified SET command did notcomplete successfully.


User response: Verify that values are valid and reissuethe command.

ANR3491E No sender email address found - unableto send email for alert, message num.

Explanation: The server is unable to send an email tothe administrators for the specified alert because anemail address of the sender could not be found.


User response: Use the QUERY MONITORSETTINGScommand to display the current sender's email address.Use the SET ALERTEMAILFROMADDR command tospecify a valid sender email address.

ANR3492W Command: Administrator administratorname is not configured to receive alertsby email.

Explanation: The specified administrator name is notset up to receive alerts by email. Alerts cannot be sentto the administrator until it is configured to receivealerts by email.


User response: Use QUERY ADMINFORMAT=DETAIL to display the current settings forthe administrator. Verify that the administrator hasALERT=YES and has a valid email address. Use theUPDATE ADMIN command to update the settings.

ANR3493E Error sending an email for alert msgnumber to the administrator with emailaddress email address using the SMTPserver name SMTP host server and SMTPport port number.

Explanation: An email about an alert was not sentsuccessfully to the administrator with the specifiedemail address.


User response: Use QUERY MONITORSETTINGcommand to see the current settings for emailing analert. Check that the administrator's email address andSMTP host server name are correct. Check that theSMTP port is correct. Fix any incorrect settings. Thenext alert that is triggered will use the newconfiguration settings. You can also check the server'sffdc log for any additional information about the error.

ANR3494E Command: No administrators added ordeleted for the alert trigger.

Explanation: The specified command has been issuedbut no administrators are added or deleted for the alerttrigger.


User response: If you are adding an administratorreissue the command specifying an administrator namethat is registered on the server. If you are deleting anadministrator reissue the command specify one of theadministrator names defined to the alert trigger.

ANR3495I Command: Administrator admin name isnot defined to alert trigger.

Explanation: The administrator name cannot bedeleted because it is not defined to the specified alerttrigger.

System action: The administrator name is skippedand the server operation continues.

User response: Reissue the command specifying anadministrator name that is defined to the alert trigger.

ANR3496W An invalid value, option value, isspecified for option option name, Thereason code is reason code.

Explanation: Reason code 1 means that this tablename is not allowed for the option. Reason code 2means that this table does not exist in the database.


User response: Verify that the correct value is used.Update the value, if necessary.



ANR3497W Reorganization is required on excludedtable table name. The reason code isreason code.

Explanation: The server has determined thatreorganization is required on a table or index that hasbeen excluded from online reorganization by the serveror a server option. Reason code 1 means that tablereorganization is required on the listed table. And thistable is currently excluded from online reorganizationprocessing because it is either specified in theDISABLEREORGTable server option or is one of thefollowing tables: STAGED_EXPIRING_OBJECTS,STAGED_OBJECT_IDS (which are permanentlyexcluded by the server from online tablereorganization. Reason code 2 means that indexreorganization is required for the listed table. Andindex reorganization is excluded because it is eitherspecified in the DISABLEREORGIndex server option oris against one of the following tables:STAGED_EXPIRING_OBJECTS, STAGED_OBJECT_IDS,REPLICATED_OBJECTS (which are permanentlyexcluded by the server from online indexreorganization. Reason code 3 means that indexreorganization with the CLEANUP PAGES ALL optionis required. This reason is only valid for theBF_BITFILE_EXTENTS table when it is specified in theDISABLEREORGCleanupindex server option.


User response: Tables and indices not reorganizedwhen needed can lead to database growth and serverperformance degradation over time. If you experienceeither of these symptoms, and receive this messageconsideration should be given to running an offlinereorganization of the given table or index. Details andinstructions on running an offline reorganization can befound in technote 1452146 under the section "Runningan offline table or index reorg": http://www.ibm.com/support/docview.wss?uid=swg21452146

ANR3498W One-time setting of the serverreorganization options is performed.

Explanation: The following server options are set afterthe server starts for the first time: 1) TheDISABLEREORGTABLE option is set with no tablesspecified. As a result, no tables are excluded from thetable-reorganization processing. 2) TheDISABLEREORGINDEX option is set toARCHIVE_OBJECTS,BACKUP_OBJECTS,BF_AGGREGATED_BITFILES, andBF_BITFILE_EXTENTS. As a result, indexreorganization will not be run on these tables. 3) TheDISABLEREORGCLEANUPINDEX is set with no tablesspecified. As a result, INDEX REORG with theCLEANUP PAGES ALL option will be run on theBF_BITFILE_EXTENTS table. This process of updatingthe server options file runs only one time, which isafter the server starts for the first time.


User response: If you do not want the one-timereorganization processing to occur, issue the followingcommands from a DB2 command window: db2 connectto tsmdb1 db2 "insert into tsmdb1.global_attributes(owner,name,type,length,int32)values('RDB','REORG_ONETIME_AUTO_INIT',3,0,2)"The commands can be issued on any Version 6 serveror at the fixing level for APAR IC95301, before youstart the server.

ANR3499E command: Scratchpad entry alreadyexists.

Explanation: A scratchpad entry with the specifiedkeys already exists.


User response: Either define a new scratchpad entrywith unique keys or update the existing scratchpadentry.

ANR3500I Backup set for node node name as setname (data type data type) beinggenerated.

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 name(data type data type) completedsuccessfully - processed files files.

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 name(data type data type) completed with fileprocessing errors - processed files fileswith error files files skipped.

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 were 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 generate



the backup set without skipping files, please contactyour local service representative for assistance.

ANR3503E Generation of backup set for node nameas set name (data type data type) 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 were used to generate thisbackup set. The volumes can be inserted into the servervolume 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 (data type data type) failed -no filespaces to process.

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 find messagespreceding this one to determine the cause of the error.After the problem is corrected, the command can beretried.

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.

ANR3515E 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 server

volume 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 command toexamine messages prior to this error to determine thecause of the data storage failure. If the failure can befound 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 - error detected.

Explanation: The server ends an backup set operationbecause an error has been encountered on the server.Some common reasons for the error are:






System action: The server ends the backup setoperation and continues operation.

User response: Examine any prior error messages todetermine the source of the error. Use the QUERYACTLOG command to view the activity log and searchfor messages if needed. Correct the problem and try therestore or retrieve again. If retry of the operationcontinues to fail contact your service representative.

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 find messagespreceding this one that specify the device that is failing.Storage pool volumes can be varied offline (by usingthe VARY OFFLINE command), or the server may needto be shut down with the HALT command to correctthe 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 ended andserver 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.


ANR3527E Backup set command operation terminated- it is acting on an empty volume orvolume content is not as expected.

Explanation: The volume content this command isacting upon is not as expected, the volume is empty, orthe volume cannot be found.

System action: The command operation is ended.

User response: Issue the command again and makesure the expected content is in the volumes or thevolume is not empty and exists.

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.

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 for file storage.

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: The backup set generation processencountered a file that was previously found to bedamaged. The process encountered the file during asequential scan of all files on the storage pool volume;the indicated file may or may not have been acandidate for inclusion in the backup set.

If this file is part of an aggregate, it may have beenpreviously marked as damaged because an integrityerror was detected in some other file within the sameaggregate. AUDIT VOLUME can determine if this is thecase, and if so, will reset the damaged state for the file.

System action: The damaged file is not added to thebackupset.

User response: Audit the indicated volume withFIX=NO to determine if the file is actually damaged.The audit will reset the file's damaged state if the file isnot damaged. (If the file is part of an aggregate, andnone of the files within the aggregate are damaged, theaudit will also reset the entire aggregate's damagedstate.)

If the file remains in the damaged state after the auditcompletes, attempt to restore the damaged file by usingthe RESTORE STGPOOL command. Note, however,that this is only an option if the damaged file is in aprimary storage pool that had been previously backedup to a copy storage pool.

If the audit resets the file's damaged state, or thedamaged file was successfully restored using RESTORESTGPOOL, and it is important for this file be includedin the backup set, then rerun the GENERATEBACKUPSET command to generate a new backup setcontaining the file.

ANR3540E Object set set node:set name:data type wasnot found 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:data type for sessionsession number, 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:data type for sessionsession number, 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:setname:data type for 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.

ANR3544E Generation of backup set for node nameas set name (data type data type) skippedshreddable data object in file spacefilespace name (fsId filespace id), file namefile name, type file type.

Explanation: The named data object for the specifiednode was skipped while generating a backupset.

The data object resides in a shreddable storage pooland will not be included in the backupset because theALLOWSHREDDABLE=YES parameter was notspecified.

System action: Backupset generation continues.

User response: Check with your StorageAdministrator to ensure data residing in a shreddablestorage pool is a allowed to be stored on a backupset.Data stored on backupsets cannot be shredded. Onlydata that resides in a shreddable storage pool can beshredded. If your Storage Administrator allowsshreddable data to be stored on backupsets, then restartthe operation and specify theALLOWSHREDDABLE=YES parameter.

ANR3547I Backup set set name used volume volumename.

Explanation: The named object used the specifiedvolume.





ANR3548E Command: Retrieve or restore failed - filewas moved or deleted from data storageduring retrieval.

Explanation: The server ends a file retrieval operationfor the specified command because the file has beenmoved or deleted from data storage by another processbefore retrieval is complete.


User response: Contact your administrator to find outif space reclamation, migration, DELETE FILESPACE,DELETE VOLUME, MOVE DATA, or inventoryexpiration processes are running; these processes canmove or delete data storage files during retrieval.Reissue the command after these processes have beencompleted or canceled.

ANR3549W Reorganization was canceled because ofa conflicting lock on table table name.

Explanation: The server online reorganization for thereferenced table could not be completed because of alock conflict. The reorganization was canceled.



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.

ANR3551I The server delete batch size has been setto new batch size. Deletion operationsthat start after this point will use thenew value.

Explanation: A SETOPT command was used to set thevalue for the delete batch size value. This settingdetermines the maximum number of files that aredeleted from the server in one database transaction.The setting influences inventory expiration operations.

System action: The server uses this new setting fordeletion operations that are started after this message isissued.


ANR3552E Command: Node node name is a nodename not supported on the target serverand is skipped.

Explanation: The node name has one or morecharacters that is not supported on server versionsearlier than 7.1.1. The character is the '@' sign.

System action: The server skips the node name andoperation continues.

User response: Check if the node name has the '@' (atsign) character. Node names with the '@' character aresupported on server versions 7.1.1 and newer. Reissuethe command specifying a different node name, or,rename the node name and reissue the command.

ANR3555E The server cannot connect to the cloudservice provider with the specifiedcloud URL of url when using the givenpassword as a Shared Access Signaturetoken.

Explanation: The connection to the cloud serviceprovider failed because the cloud URL, and cloudpassword specified in the command could not beresolved.


User response: Verify that the cloud URL, password,and cloud type for the cloud storage pool are correctand have been entered correctly. Also, verify that thecloud provider is active.

ANR3556E The server cannot connect to the cloudservice provider with the specifiedcloud URL of url when using the cloudID of id and its password.

Explanation: The connection to the cloud serviceprovider failed because the cloud URL, cloud ID, andcloud password specified in the command could not beresolved.


User response: Verify that the cloud URL, user ID,password, and cloud type for the cloud storage poolare correct and have been entered correctly. Also, verifythat the cloud provider is active.

ANR3557I The cloud service provider URL andcredentials were verified.

Explanation: The verification of the credentials andURL for the cloud service provider succeeded.





ANR3560E command: One or more of the followingparameters are missing: parameters.

Explanation: The command cannot be processed asspecified.



ANR3561E command: Keyword parameter parameteris not recognized. The followingkeyword parameters are valid: validlist.




ANR3562E command: The parameter parameter valuevalue is not numeric. The minimumvalue is min value and the maximumvalue is max value.

Explanation: The command cannot be processedbecause the specified parameter requires a numericvalue.



ANR3563E command: The parameter parameter valuevalue is out of range. The minimumvalue is min value and the maximumvalue is max value.




ANR3564E command: The parameter parameter valuevalue is not recognized. The followingparameter values are valid: validlist.




ANR3565E command: The parameter parameter valuevalue is out of range. The minimumvalue is min value and the maximumvalue is max value. The followingparameter values are also valid: validlist.




ANR3566E command: The parameter parameter valuevalue is not recognized. The minimumvalue is min value and the maximumvalue is max value. The followingparameter values are also valid: validlist.




ANR3567E command: The scale scale for the parameterparameter is not recognized. Thefollowing scales are valid: validlist.




ANR3568E command: The parameter parameter valuevalue is out of range. The minimumvalue is min value and the maximumvalue is max value.




ANR3569E command: The parameter parameter valuevalue is too long. The maximum lengthis max length characters.






ANR3570E command: The parameter parameter valueis too short. The minimum length is minlength characters.




ANR3571E command: The parameter parameter valuevalue contains an invalid character"character". The following characters arevalid: "validlist" (excluding the quotationmarks).




ANR3572E command: The parameter parameter valuevalue is a reserved value and cannot bespecified.




ANR3573E command: The parameter parameter valuevalue is not a valid date.




ANR3574E command: The parameter parameter valuevalue month month is out of range. Theminimum value is minimum and themaximum value is maximum.




ANR3575E command: The parameter parameter valuevalue day day is out of range. Theminimum value is minimum and themaximum value is maximum.




ANR3576E command: The parameter parameter valuevalue year year is out of range. Theminimum value is minimum and themaximum value is maximum.




ANR3577E command: The parameter parameterrelative days value value is not numeric.




ANR3578E command: The parameter parameterrelative days value value is out of range.The minimum value is 0 and themaximum value is max value.




ANR3579E command: The parameter parameter valuevalue is not a valid time.






ANR3580E command: The parameter parameter valuevalue hours hours is out of range. Theminimum value is minimum and themaximum value is maximum.




ANR3581E command: The parameter parameter valuevalue minutes minutes is out of range.The minimum value is minimum and themaximum value is maximum.




ANR3582E command: The parameter parameter valuevalue seconds seconds is out of range. Theminimum value is minimum and themaximum value is maximum.




ANR3583E command: The parameter parameterrelative hours value value is notnumeric.




ANR3584E command: The parameter parameterrelative minutes value value is notnumeric.




ANR3585E command: The parameter parameterrelative hours value value is out ofrange. The minimum value is 0 and themaximum value is max value.




ANR3586E command: The parameter parameterrelative minutes value value is out ofrange. The minimum value is 0 and themaximum value is max value.




ANR3587E command: The parameter parameter isspecified more than once.

Explanation: The command cannot be processedbecause the specified parameter can only be enteredonce.



ANR3588E command: The parameter parameterrequires the prerequisite parameterparameter.




ANR3589I command: For more information, issuethe HELP command command.

Explanation: One or more syntax errors were found inthe specified server command (see the previousmessages). The command cannot be processed asspecified.





ANR3590E command: Command is above therequested skill level.

Explanation: The specified server command has a skilllevel above what was requested.



ANR3591E command: The parameter parameter valuevalue is out of range. The minimumvalue is min value and the maximumvalue is max value. The followingparameter values are also valid: validlist.




ANR3592E command: The parameter parameter valuevalue is not recognized. The minimumvalue is min value and the maximumvalue is max value. The followingparameter values are also valid: validlist.




ANR3593E command: The parameter parameter valuevalue is not valid. One of the followingscales is required: validlist.




ANR3594E command: The integer portion of theparameter parameter value value is out ofrange. The minimum integer value ismin value and the maximum integervalue is max value.




ANR3595E command: The integer portion of theparameter parameter value value is out ofrange. The minimum integer value ismin value and the maximum integervalue is max value. The followingparameter values are also valid: validlist.




ANR3596E command: The parameter parameterconflicts with the conflicting parameterparameter.




ANR3597E command: The parameter parameter valuevalue is specified more than once.




ANR3598E command: At least one of the followingparameters is required: parameters.




ANR3599E command: One and only one of thefollowing parameters is required:parameters.






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 IBM Software Support.

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 IBMSoftware Support.

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. While



communicating, the indicated verb ( an internal requestmechanism between the storage agent and databaseserver ), was unexpected. The verb number is providedfor IBM Software Support.

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 IBM Software Support.

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 the messageis the result of starting a storage agent. The storageagent requests that the server purge cached informationthat it was using previously. It is possible thatinformation tracking policy caching has become stale.In this case, no response is required. If the messageoccurs without a storage agent connecting to the 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 the messageis the result of stopping a server. Ensure that the server

with which the storage agent communicates is runningand that there is connectivity between the systems. Theserver must be restarted before you can start a newadministrator session with the storage agent.

ANR3612E This command is not supported in theExpress 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.

ANR3613W Process process ID skipped Num Filesfiles on volume Volume name because ofa lock conflict with another process.

Explanation: A lock conflict was encountered whilemoving files and the retries were exceeded.


User response: Retry the operation.

ANR3614E The server failed to connect to thedatabase.

Explanation: The server was unable to establish orvalidate a connection to the database.

System action: The server will shutdown.

User response: Examine the messages that wereissued before this message to determine the cause ofthe failure. Start the server after the issue has beenresolved.

ANR3615E The value of the DATAFORMATparameter for the datamover is notcompatible with the NAS file server.

Explanation: The datamover was defined with theNDMPDump DATAFORMAT. This data format is notcompatible with an EMC NAS file server.

System action: The NDMP operation fails.

User response: Update the datamover to use theCELERRADump dataformat.

ANR3616E An error occurred. More informationmight be available in the dsmserv.errand dsmffdc.log files.

Explanation: None.


User response: Review the dsmserv.err anddsmffdc.log files for messages that occurred at the same



time as the error. The dsmserv.err and dsmffdc.log filesis located in the server working directory. Correct anyproblems that are identified.

ANR3617E The server failed to start with returncode rc because of an issue with thedatabase environment handle.

Explanation: The server was unable to allocate ahandle to the database environment.


User response: The following are possible causes andsolutions:

v The most common cause is that the DSMSERV utilityis not being run as the instance owner, or the userprofile (db2profile) has not been sourced for thecurrent login shell. To resolve the issue, log in as theinstance user and source the DB2 profile, db2profile:. /home/tsminst1/sqllib/db2profile Note: Ensurethat you insert a space after the initial dot.

v A mismatch between the /etc/hosts file and the~/sqllib/db2nodes.cfg file. If the host name wasrecently updated, ensure that the systems host namein the /etc/hosts file matches the host name in the~/sqllib/db2nodes.cfg file. If the files contain thesame host name, see the db2diag.log files for moreinformation. For information about the db2nodes.cfgfile, see the DB2 documentation.

v The database manager cannot be started due toinsufficient system resources. Review the currentoperating system kernel settings and ulimit settingsfor parameters like nofiles for the user who isstarting the DSMSERV program. Increase the valuesif needed. For information about changing kerneland ulimit values, see the documentation for youroperating system. For guidelines concerning ulimitsettings on IBM Spectrum Protect servers search for"user limits" in the product information(http://www.ibm.com/support/knowledgecenter/SSEQVQ/). For guidelines concerning operatingsystem kernel parameters, search for "tuning kernelparameter" in the product information.

v Instance entries are missing from the /etc/servicesfile. If the entries do not exist in the /etc/servicesfile, re-create the entries as in this example:DB2_tsminst1 60000/tcp DB2_tsminst1_1 60001/tcpDB2_tsminst1_2 60002/tcp DB2_tsminst1_END60003/tcp As a general rule, these entries are placednear the end of the /etc/services file. Replacetsminst1 with the name of the IBM Spectrum Protectinstance that is being used on the server.

v A copy of the DB2APP64.dll file is in the serverinstance directory. In some cases, users mistakenlycopy the DB2APP64.dll file to the server instancedirectory from the installation directory. By default,the installation directory is C:\ProgramFiles\Tivoli\TSM\db2\BIN. The DB2APP64.dll fileshould be in this directory only. Any additionalcopies of this DLL file should be removed.

ANR3618W bad adapter number of total adapter numberhost bus adapters cannot be opened.

Explanation: The SAN discovery function is not ableto open all of the host bus adapters (HBAs) on thesystem.


User response: IBM Spectrum Protect SAN discoverymay only be getting partial device information from theSAN. Verify that all HBAs are configured and workingproperly.

ANR3619W The user limit for limit is below therecommended minimum value of value.

Explanation: A user limit that is below therecommended minimum value might cause unexpectedbehavior.


User response: Set the user limit so that it is equal toor greater than the recommended minimum value.

ANR3620I Status threshold status threshold updated.

Explanation: An UPDATE STATUSTHRESHOLDcommand has updated the status threshold indicated.



ANR3621I Status threshold status threshold deleted.

Explanation: A DELETE STATUSTHRESHOLDcommand has deleted the status threshold indicated.



ANR3622I Status threshold status threshold defined.

Explanation: A DEFINE STATUSTHRESHOLDcommand has created the status threshold indicated.



ANR3623E Command: Status threshold statusthreshold is already defined.

Explanation: The command indicated has attemptedto define a status threshold that already exists.





ANR3624E Command: Status threshold threshold nameis not defined.

Explanation: The command shown specifies a statusthreshold that is not defined with the server.



ANR3625I Host bus adapter (HBA) API functionsare not supported by adapter adaptername.

Explanation: The HBAAPI function failed to retrievethe attributes of the adapter. The reason is that thisadapter is not a Fibre Channel SCSI adapter. Thisadapter might be a Serial Attached SCSI adapter.Therefore, SAN discovery does not work.

System action: The system is unable to retrieve theattributes of the adapter.

User response: Validate whether this adapter is aFibre Channel SCSI adapter or not, and if it is, contacthardware support for the adapter.

ANR3626W A check condition occurred during asmall computer system interface (SCSI)inquiry at Fibre Channel port WWN=fcport wwn, KEY=sense key, ASC=asc,ASCQ=ascq.

Explanation: The host bus adapter (HBA) APIfunction failed to query the SCSI information of adevice located at this port. A hardware error or SCSIbus reset might have occurred during the operation.

System action: The HBAAPI inquiry function wasunable to retrieve the SCSI device information from thisport.

User response: Verify that the adapter, device, andFibre Channel are connected. For more informationabout the values of the KEY, ASC, and ASCQ fields, seethe SCSI specification.

ANR3627I Alerts cannot be sent by email.

Explanation: You must enable the alert monitor andemail option to receive alerts by email.


User response: Configure the server alert settings withthe following commands:

SET ALERTMONITOR ON

SET ALERTEMAIL ON

ANR3628E The monitor status process hasencountered an unexpected error settingthe status of element element. Theprocess returned error code rc.

Explanation: The process that monitors server activityhas detected an error setting the element status.



ANR3629W All administrators with system levelauthority use LDAP authentication.Administrator admin was the most recentadministrator with system levelauthority that used LOCALauthentication.

Explanation: All administrator with system levelauthority use LDAP authentication. This situation hasrisks, based on the availability of the LDAP server. Ifrequired, make sure that the LDAP server has highavailability configurations implemented. For example:clustering, mirroring, or replication. Having onesystem-level administrator with LOCAL authenticationgives that administrator the ability to update otheradministrators and nodes to LOCAL authentication ifthe LDAP server is down unusable for an extendedperiod of time.

System action: The only administrator with systemlevel authority uses LDAP authentication.

User response: Consider having one administratorwith system authority and LOCAL authentication. Ifthis is not possible, validate that the high availabilityconfigurations for the LDAP server are sufficient.

ANR3630E Command: The condition condition willconflict with existing status thresholdthreshold with condition condition.

Explanation: The command indicated has attemptedto define or update a status threshold that will conflictwith an existing threshold.

System action: The status threshold is not defined orupdated.

User response: Either delete the existing threshold oruse a different condition.

ANR3631E The database is not intact.

Explanation: The server failed to start because thedatabase was not intact.


User response: If this is a new installation orconfiguration, confirm that the DSMSERV FORMATstep was completed successfully. If this is an existing



configuration that was previously working, a databaserestore might be required.

ANR3632E command: The administrator administratorID is locked.

Explanation: The administrator ID is locked andcannot be used in this command.


User response: Unlock the administrator ID andreissue the command.

ANR3633I Process process ID skipped volumeVolume Name because the volumecontains files that have not been backedup.

Explanation: The DEDUPREQUIRESBACKUP serveroption is set to the default value of YES. If the value ofthis option is YES, files within a deduplicated storagepool must be backed up to a non-deduplicated copystorage pool before the files can be reclaimed.

System action: The operation skips the volume andcontinues.

User response: Ensure that all files on the volume arebacked up to a non-deduplicated copy storage pool.You can change the value of theDEDUPREQUIRESBACKUP server option to NO.However, changing the option value to NO can resultin unrecoverable data loss if a data-integrity erroroccurs.

ANR3634W The HBA API cannot provide tapedevice information from the SAN.

System action: No action is required.

User response: Check the connections between theFibre Channel cables and the tape device settings toensure that the tape devices can be presented to thesystem first. Contact the HBA vendor to reportproblems if the QUERY SAN command cannot retrievetape device information when tape devices arepresented to the system.

ANR3635I The status monitor has updated theevent record retention period to 14 days.

Explanation: To provide full functionality for theOperations Center, the server must retain event recordsfor a minimum of 14 days.

System action: Event records will be retained for 14days.

User response: Use the SET EVENTRETENTIONcommand if a different value is desired.

ANR3636W Transaction failed for session sessionnumber for node node name (clientplatform) - the key is already defined.

Explanation: The server ends the transaction becausethe key is already defined in the database.


User response: Make sure the key is unique.

ANR3637W Transaction failed for session sessionnumber for node node name (clientplatform) - the key is not defined.

Explanation: The server ends the transaction becausethe key is already defined in the database.


User response: Make sure the key is defined.

ANR3638W Space reclamation skipped volumevolume name because the spannedvolume volume name in storage poolstorage pool name is inaccessible.

Explanation: The specified volume is eligible for spacereclamation, but the spanned volume is eitherunavailable or destroyed. The specified volume isskipped. Space reclamation continues for othervolumes.

System action: The space reclamation processcontinues.


ANR3639I command: A deduplicated NAS backupimage for node node name, file spacefilespace name was skipped.

Explanation: The server command has determinedthat a NAS backup image is not eligible for processingbecause the image or one of its dependent files isstored or had been stored in a deduplicated storagepool.

System action: The processing continues.


ANR3640E command command failed because thetarget replication servertarget_server_name is invalid.

Explanation: The specified target replication server isnot a target replication server.


User response: To set the name of a target replicationserver and to run the replication validation process forthat target replication server, complete the followingsteps:



1. Obtain a list of possible target replication servers byissuing the QUERY SERVER command.

2. Verify the policies by issuing the VALIDATEREPLPOLICY command.

ANR3641E SET DISSIMILARPOLICIES commandfailed because the policies on the targetreplication server were not verified.

Explanation: The policies on the target replicationserver were not verified before issuing the SETDISSIMILARPOLICIES command.


User response: Verify the policies by issuing theVALIDATE REPLPOLICY command.

ANR3642E Damaged files are not recovered becausethe system-wideREPLRECOVERDAMAGED setting isturned off.

Explanation: To recover damaged files by using theREPLICATE NODE command, theREPLRECOVERDAMAGED setting must be turned on.

System action: The REPLICATE NODE commandfails.

User response: To resolve the issue, complete thefollowing steps: 1. Use the SETREPLRECOVERDAMAGED command to turn thesetting for file recovery on. Issue the followingcommand: set replrecoverdamaged on 2. Run theREPLICATE NODE command again. Ensure that theRECOVERDAMAGED parameter is set to YES orONLY.

ANR3643W Process number for description exceededthe maximum allowed running time.

Explanation: The process was started by aadministrative schedule and is running longer than themaximum allowed time defined in the schedule.

System action: The process is cancelled and serveroperation continues.


ANR3644E The target replication server name doesnot support dissimilar policies.

Explanation: Dissimilar policies are supported only onIBM Spectrum Protect Version 7.1.1 or later.

System action: Policy validation is skipped for thespecified server.

User response: To resolve this issue, complete thefollowing steps: 1. Upgrade the target server to IBMSpectrum Protect V7.1.1 or later. 2. Run the VALIDATEREPLPOLICY command again.

ANR3645E Command: Storage pool storage pool namestill contains at least one directory.

Explanation: A DELETE STGPOOL command specifiesa storage pool that has directories assigned to it.


User response: Delete the directory belonging to thestorage pool and reissue the command.

ANR3646E Command: Storage pool directory storagepool directory name has an access mode ofaccess mode and has active data.

Explanation: A DELETE STGPOOLDIR commandspecifies a storage pool directory that has in usedirectories assigned to it.


User response: Ensure that there are no containers inthe directory before you delete it. Issue the UPDATESTGPOOL command and set the REUSEDELAYparameter to specify the number of days that mustelapse after all deduplicated extents are removed froma container storage pool. To force removal of thedirectory, issue the UPDATE STGPOOLDIRECTORYcommand and set the access mode to DESTROYED.Issue the AUDIT CONTAINER command and specifythe ACTION=REMOVEDAMAGED parameter to deletethe container.

ANR3647E The Command command failed becausethe default replication server is not set.

Explanation: The command requires a default targetreplicatoin server. If the default target replication serveris not set, the command fails.


User response: Issue the SET REPLSERVER commandto set the default target replication server as the targetreplication server.

ANR3648E Command: Storage pool NEXTSTGPOOL:storage pool name is a directory-containerstorage pool.

Explanation: The command indicated specifies thename of a storage pool which is a directory-containerstorage pool. The command syntax requires that adirectory-container storage pool name not be specified.





ANR3649I A scan to identify damaged files wasinitiated at time.

Explanation: If the REPLRECOVERDAMAGEDsystem parameter is set to ON, the system conducts abrief check of server database tables every 30 minutesto determine whether the number of damaged bitfileshas changed. If the number has changed, the systeminitiates a scan of server database tables to identify thedamaged files for recovery purposes.

System action: A scan was started to collectinformation about damaged files.


ANR3650I A scan to identify damaged files wascompleted at time.

Explanation: If the REPLRECOVERDAMAGEDsystem parameter is set to ON, the system conducts abrief check of server database tables every 30 minutesto determine whether the number of damaged bitfileshas changed. If the number has changed, the systeminitiates a scan of server database tables to identify thedamaged files for recovery purposes.

System action: A scan that collected information aboutdamaged files is completed. If the recovery of damagedfiles is enabled for a node, the next replication processwill replace the damaged files on that node withundamaged files from the target replication server.Recovery of damaged files can take place only if thefiles were replicated before the damage occurred.


ANR3651W The replication process is skipping adamaged file on volume volume name:Node node name, Type file type, File spacefilespace name, File name file name.

Explanation: During the replication process, 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 is not replicated.

User response: Perform the following actions:

v Audit the volume with FIX=NO to verify that the fileis damaged. If the file is undamaged, the auditprocess resets the file status. If the file is part of anaggregate and the entire aggregate is found to beundamaged, the audit process resets the aggregatestatus.

v If the volume is in a primary storage pool and has acopy in the copy storage pool, attempt to restore thedamaged file by issuing the RESTORE STGPOOLcommand.

ANR3652I The VALIDATE REPLPOLICY commanddid not find any nodes to validate onthe target replication server target servername.

Explanation: The nodes on the target replicationserver are not the same as the nodes on the sourcereplication server. When you issue this command, itdoes not find any nodes that are common to bothreplication servers to compare.



ANR3653I A scan to identify damaged files wasstopped at time.

Explanation: The scan was stopped because theREPLRECOVERDAMAGED system parameter was setto OFF.

System action: Information that was collected duringthe scan was saved.

User response: No action is required. However, if youwant to restart the scan, issue the following command:SET REPLRECOVERDAMAGED ON

ANR3654W Inventory file expiration processing didnot run in the previous 24 hours.

Explanation: When you are using the policies on thetarget replication server to manage replicatedclient-node data, you must run expiration processingevery 24 hours to allow the target replication serverreuse storage pool space that is occupied by expiredreplicated data.


User response: Run expiration processing at least oncein a 24 hour period.

ANR3655I Replication ended for process node name,but the deduplication catalog is beingupdated for the following storage pools:pool list.

Explanation: As files were being recovered from thetarget replication server, a separate thread was startedto update the entries for the affected files in thededuplication catalog. The thread was still in theprocess of updating the entries when the replicationrecovery process ended.

System action: The thread continues to update theattributes of the recovered files in the deduplicationcatalog. When the updates are complete, all affectedfiles will be accessible to client sessions and serverprocesses.




ANR3656I Replication recovery of damaged files isdisabled.

Explanation: During a database upgrade, damagedfiles were detected. The REPLRECOVERDAMAGEDsystem parameter, which is used to enable the recoveryof damaged files, was automatically set to OFF. TheOFF setting prevents the server from scanning databasetables for damaged objects that can be recovered.Prevention of the scan is necessary in case manydamaged files are detected. In that case, the scan mightrequire considerable time and a large amount of serverresources.

System action: The server upgrade continues, and theREPLRECOVERDAMAGED system parameter remainsset to OFF.

User response: The process for scanning databasetables should be scheduled when the use of serverresources is at a minimum. To start the scan, issue thefollowing command: set replrecoverdamaged on Fordetailed instructions, see the documentation for the SETREPLRECOVERDAMAGED command.

ANR3657E REPAIR STGPOOL: One or morerequired stgpool directories is currentlyunavailable on the target server.

Explanation: The REPAIR STGPOOL process is unableto repair one or more files because the replicated datais located in a stgpool directory that is currentlyunavailable on the target server.

System action: The REPAIR STGPOOL process fails.

User response: If the stgpool directory has beenmarked unavailable on the target server, it can beupdated using the UPDATE STGPOOLDIR command.

ANR3658E Command: Storage pool storage pool nameis currently in use by replication, repair,protect, encrypt or move operations.

Explanation: The command indicated references astorage pool that is in use.



ANR3659E Command: Storage pool storage pool namedoes not have a protection stgpooldefined.

Explanation: The stgpool must have a protectionstgpool defined.


User response: Update the PROTECT STGpoolparameter for the pool you are trying to protect.

ANR3660E An unexpected error occured whileopening or writing to the container.Container container name in stgpoolstorage pool name has been marked ascontainer state and should be audited tovalidate accessibility and content.

Explanation: An I/O error occured on the containerand it cannot be used.

System action: The server does not use the container.

User response: Run an AUDIT CONTAINERcommand on the container.

ANR3661I Marked container container name and the# of data extents data extents that itcontains as damaged.

Explanation: Displays results of data extents markeddamaged due to an AUDIT CONTAINER command.



ANR3662E Command: Storage pool storage pool namestill contains data.

Explanation: A DELETE STGPOOL commandencountered a storage pool that still contains data.


User response: Delete the data that belongs to thestorage pool and reissue the command.

ANR3663W Source file(line number): Storage poolstorage pool name failed to delete thecloud container.

Explanation: A DELETE STGPOOL command couldnot delete the cloud container.


User response: Ensure the connection to the cloudserver has valid credentials and can communicateproperly.

ANR3664W Command: A network-attached storage(NAS) table of contents (TOC) for nodenode name, file space filespace name wasskipped.

Explanation: The TOC was skipped because a table ofcontents storage pool is not defined on the targetreplication server.

System action: Node replication processing continues,but the TOC is not replicated.

User response: No action is required. However, to



ensure that the backup image is replicated, you can usethe UPDATE COPYGROUP command to specify a table ofcontents destination, and then activate the updatedpolicy set by issuing the ACTIVATE POLICYSET command.These two commands must be issued on the targetreplication server. Then, initiate node replication on thesource replication server.For example, to change the STANDARD copy group tostore table of contents data in the TOCPOOL storagepool where the domain name is STANDARD and thepolicy name is STANDARD, complete the followingsteps:

1. Issue the following command:

update copygroup standard standard standardtocdestination=tocpool

2. Issue the following command:

activate policyset standard standard

3. Start the node replication process. For example, ifthe node is named NODE1, issue the followingcommand on the source replication server:

replicate node node1

ANR3665E Command: Source storage pool storagepool is not eligible to be converted.

Explanation: Only primary sequential-access storagepools that are enabled for data deduplication areeligible for conversion to a directory-container storagepool.


User response: Issue the command again and specifya primary sequential-access storage pool as the sourcestorage pool.

ANR3666E Command: Destination storage poolstorage pool is not eligible for theconversion.

Explanation: The command specifies a target storagepool that is not valid for conversion. You must specifya directory-container storage pool as the target storagepool for a conversion process. When restarting astopped conversion process, you must specify the targetstorage pool which was originally used for theconversion process.


User response: Issue the command again and specifya directory-container storage pool as the target storagepool. If restarting, specify the same target storage poolwhich was originally used for the conversion process,or issue the command without the target storage poolparameter.

ANR3667W Unable to connect by FASP with serverserver name on port port name.

Explanation: An attempt to estblish connectivity witha target server using specified port failed. Theoperation will use the existing TCP/IP session tocommunicate with the target server.


User response: Examine the source and target serveractivity logs for information related to FASPByte-Stream activity.

ANR3668E Command: Invalid attempt to change theaccess state for storage pool storage pool.

Explanation: The access state for a storage pool cannotbe changed once it has been converted. In addition, astorage pool cannot be manually changed to aconversion state.



ANR3669W There is at least one reference to storagepool storage pool as a policy or nextpooldestination. When the storage poolconversion starts the storage pool can nolonger ingest or store new data.

Explanation: There is limited write access to thestorage pool during conversion. The storage poolcannot store new files from either client sessions orserver processes. Server operations for the convertedstorage pool might be limited or unavailable. Storagepool conversion cannot be reversed after it is started.


User response: Enter 'Y' to convert the storage pool or'N' to stop the process.

ANR3670W Storage pool storage pool is eitherconverted or is being converted andcannot accept any new data.

Explanation: Conversion is in progress for the storagepool.

System action: The storage pool cannot store new filesfrom either client sessions or server processes.

User response: Update all policies to ensure that thedestination specifies a storage pool that does not have aconverting state. Ensure that a storage pool that doesnot have a converting state is named as the nextstorage pool by issuing the UPDATE STGPOOLcommand and specifying the NEXTstgpool parameter.



ANR3671E Storage pool storage pool is eitherconverted or is being converted andcannot perform migration or reclamationbetween storage pools.

Explanation: The storage pool is in a conversion stateand cannot migrate or reclaim data to another storagepool.

System action: The request will be denied for thestorage pool in conversion state.

User response: Use the MOVE DATA, or MOVENODEDATA, commands to move specific groups ofdata out of the storage pool. Data can only be moved ifthere are no conversion processes active for the storagepool.

ANR3672E The license file that is required toenable Aspera Fast Adaptive SecureProtocol (FASP) technology was notfound on the server_loc server.

Explanation: An attempt to use the Aspera FASP datatransfer method failed because the license file(aspera-license) was not found on the source or targetserver.

System action: System operations continue. However,data cannot be transferred by using Aspera FASPtechnology unless a valid license file is installed.


1. Obtain and install a valid license file. Follow theinstructions in technote 7047418(http://www.ibm.com/support/docview.wss?uid=swg27047418).

2. Retry the node replication or data protectionoperation.

ANR3673E One of the FASP related files is invalidor corrupt.

Explanation: Server replication attempted to use faspas the communication method and either the source ortarget server lacked a valid aspera file.

System action: Server replication will not proceeduntil the communication method is changed or a validset of files are obtained and installed.

User response: Obtain an Aspera license file and placeit in the server bin directory as aspera-license, anAspera Configuration file place in the server bindirectory as aspera.config, and the faspstreamcomponent of the Aspera SDK place as faspstream inthe server bin directory.

ANR3674E Unable to find aspera.conf file onserver_loc server.

Explanation: Server replication attempted to use faspas the communication method and either the source ortarget server lacked the appropriate aspera.conf file.

System action: Server replication will not proceeduntil the communication method is changed or a validAspera configuration file is obtained and installed.

User response: Obtain an Aspera configuration fileand place it in the server bin directory as aspera.conf.

ANR3675E Unable to find faspstream executable onserver_loc server.

Explanation: Server replication attempted to use faspas the communication method and either the source ortarget server lacked the appropriate faspstreamexecutable.

System action: Server replication will not proceeduntil the communication method is changed or a validAspera faspstream executable is obtained and installed.

User response: Obtain an Aspera faspstreamexecutable and place it in the server bin directory asfaspstream.

ANR3676E Storage pool storage pool is actively beingconverted and cannot perform any datamovement or deletion.

Explanation: Conversion is in progress for the storagepool.

System action: The storage pool cannot perform thecommand.

User response: Cancel all CONVERT STPGOOLprocesses for this stgpool, or wait until they havecompleted.

ANR3677E Storage pool storage pool is eitherconverted or is being converted andcannot be the target of a migration orreclamation operation.

Explanation: The storage pool is in a conversion stateand cannot be the target of migration or reclamation.

System action: The request will be denied for thestorage pool.

User response: Update the stgpool that is attemptingto migrate or reclaim into the converted stgpool topoint to a valid target.



ANR3678E Unable to initialize FASP driver - threadcreation failed.

Explanation: The server is unable to initialize theFASP driver due to an error creating a server thread.

System action: Server operation continues, but FASPsupport is inoperative.

User response: This error often results from a lack ofmemory. Ensure that your system has sufficient pagingspace to support the current activities.

ANR3679W You cannot convert data that is stored incopy storage pools or active-data storagepools. When you issue the CONVERTSTGPOOL command, copies of files thatare stored in primary storage poolstorage pool are deleted. You must updatecopy storage pools and active-datastorage pools that are used by DisasterRecovery Management.

Explanation: When the storage pool is successfullyconverted, all data and copies of data in existingstorage pools are removed. Use the PROTECT STGPOOLcommand to protect data in container storage pools oruse the REPLICATE NODE command to replicate data inother types of storage pools. Use the SETDRMCOPYSTGPOOL and the SET DRMACTIVEDATASTGPOOLcommands to specify the names of the copy storagepools and active-data storage pools to recover datafrom after a disaster.



ANR3680W The storage pool conversion is cancelledfor storage pool pool name.

Explanation: During conversion processing, for thestorage pool that is specified, the conversion processwas cancelled. The server might display this messagemore several times during the conversion cancellation.

System action: The storage pool conversion is endedand server operation continues.

User response: To convert the storage pool again,reissue the CONVERT STGPOOL command.

ANR3681E The license file that is required toenable Aspera Fast Adaptive SecureProtocol (FASP) technology has expiredon the server_loc server.

Explanation: An attempt to use the Aspera FASP datatransfer method failed because the license file hasexpired on the source or target server.

System action: System operations continue. However,

data cannot be transferred by using Aspera FASPtechnology unless a valid license file is installed.




ANR3682W Container container name is empty andcannot be moved.

Explanation: You cannot move an empty container.

System action: The container is skipped. Serveroperation continues.

User response: Reissue the MOVE CONTAINERcommand for a container that contains data.

ANR3683E Source storage pool storage pool isconverting to a directory-containerstorage pool and cannot be renamed.

Explanation: Conversion is in progress for the sourcestorage pool.

System action: The source storage pool cannot berenamed during conversion processing.

User response: When conversion completes, reissuethe RENAME STGPOOL command again.

ANR3684I The evaluation license id that isrequired to enable Aspera Fast AdaptiveSecure Protocol (FASP) technology willexpire in days days.

Explanation: The Aspera FASP data transfer licensefile will expire on the source or target server.

System action: System operations continue. However,unless a long term license is acquired, data willeventually stop being transferred using Aspera FASPtechnology.



ANR3685W The license file that is required toenable Aspera Fast Adaptive SecureProtocol (FASP) technology expirestoday.

Explanation: The Aspera FASP data transfer licensefile will expire on the source or target server.



System action: System operations continue. However,unless a long term license is acquired, data willeventually stop being transferred using Aspera FASPtechnology.



ANR3686W Source storage pool source_pool isreferenced by Disaster RecoveryManagement. After conversion, youcannot restore data to the source storagepool and disaster recovery might fail.

Explanation: When conversion starts, the sourcestorage pool cannot ingest or store new data. Use theQUERY DRMSTATUS command and the SETDRMPRIMSTGPOOL command to view and update primarystorage pools that are used by Disaster RecoveryManagement.



ANR3687E Transaction failed for session sessionnumber for node node name (clientplatform) - container transaction timeoutencountered.

Explanation: The server ends a database updatetransaction for the specified client because the clientdid not commit the transaction before the timeoutperiod. The timeout period is controlled by theCONTAINERRESOURCETIMEOUT option


User response: Determine why the operation did notcommit the transaction within the timeframe specifiedby the option. The option might need to be increased toallow for the ingest operation to commit the transactionover a longer period of time.

ANR3688E A file was skipped while moving datato storage pool storage pool name. Filename file name for Node node name, Filespace filespace name is excluded becauseof its size.

Explanation: The server skips the specified file for themove operation. The size of the file is larger than thatallowed in the storage pool based on the MAXSIZEparameter setting.

System action: The file is skipped by the datamovement process.

User response: Increase the maximum file size for thetarget storage pool. An authorized administrator canincrease the MAXSIZE parameter by issuing theUPDATE STGPOOL command. The file can also bemoved to another storage pool that allows for storageof larger objects.

ANR3689E Invalid container header found forcontainer container name and cannot bemoved.

Explanation: A container file selected for a moveoperation contains an invalid header and will not bemoved.

System action: The container is skipped. Serveroperation continues.

User response: Run the AUDIT CONTAINERcommand for the container.

ANR3690W Invalid header found during replicationof objects in pool pool name. Theseobjects have been marked damaged.

Explanation: A file selected for a replication operationcontains an invalid header and will not be moved.

System action: The object is marked damaged. Serveroperation continues.

User response: Run the AUDIT CONTAINERcommand for the container.

ANR3691E The transaction failed for process processname, process number process number,because of a transaction timeout.

Explanation: The server ended the database updatetransaction for the specified process because thetransaction was not committed within the timeoutperiod. The timeout period is controlled by theCONTAINERRESOURCETIMEOUT option.

System action: The specified process ended, butserver operation continues.

User response: To resolve the issue, complete thefollowing steps: 1. Determine why the operation didnot commit the transaction within the specified time. 2.If necessary, increase the timeout period. For example,to set a timeout period of 4 hours, specify the followingoption: containerresourcetimeout 240

ANR3692W A client backup anomaly was detectedfor node node name, session numbernumber. The average number of backedup bytes is bytes, the actual number ofbacked up bytes was bytes, the averagedata deduplication is percent number



percent, and the actual datadeduplication was percent numberpercent.

Explanation: The server detected a workload anomalyfrom a backup-archive client. Either the number ofbacked-up bytes exceeds the normal average, or thedata deduplication percent is much less than theaverage data deduplication percent.


User response: Review the data to determine whetherthe appropriate data was backed up and to identifypossible issues.

ANR3701E Cannot connect to the cloud serviceprovider for the operation_name operationon the pool_name storage pool.

Explanation: A request to the cloud service providerfailed because the client system is not connected to thecloud server.


User response: Ensure that you specify validcredentials for the connection to the cloud server andthat the client system can communicate with the cloudserver.

ANR3702E Cannot connect to the cloud serviceprovider for the operation_name operationon the pool_name storage pool.

Explanation: The connection to the cloud providerfailed because the cloud service provider that isspecified in the DEFINE STGPOOL command is notvalid.


User response: Ensure that you specify validcredentials for the connection to the cloud server andthat the client system can communicate with the cloudserver.

ANR3703E Source file(line number): Unable to connectto the cloud provider.

Explanation: An error occurred while attempting toconnect to the cloud provider.


User response:

ANR3704E Source file(line number): Unable to loadthe jvm for the cloud storage pool.

Explanation: An error occurred while attempting toload the jvm for the cloud storage pool.


User response:

ANR3705E Source file(line number): A required Javaarchive (JAR) file cannot be located, orthe required resources within the JARfile are unavailable.

Explanation: Some IBM Spectrum Protect operationsrequire the use of a Java virtual machine (JVM) andJava code running in that virtual machine. This code iscontained in JAR files. JAR files might be missing,incorrectly located, or lacking the necessary resources.Another possibility is that the JAR files and the IBMSpectrum Protect version are mismatched.

System action: Any capabilities that require the JVMwill not work.


1. Verify that the IBM Spectrum Protect server iscorrectly installed by ensuring that the JAR files arein the installation directory.

2. If the issue persists, retrieve the first-failure datacapture (FFDC) log files from the server. Forinstructions about retrieving the FFDC log files, seethe Problem Determination Guide.

3. Contact IBM Software Support for assistance.

ANR3706W Reorganization is required on table tablename, which is excluded from onlinereorganization.

Explanation: The specified table was excluded fromonline reorganization by the DISABLEREORGTABLEserver option.


User response: A failure to reorganize tables whennecessary can lead to database growth and serverperformance degradation over time. If you experienceeither of these symptoms, consider running an offlinereorganization of the specified table. For instructions,see the section about offline table reorganization inTechnote 1683633: http://www.ibm.com/support/docview.wss?uid=swg21683633#offline_table_reorg

ANR3707E An unexpected error occurred whilewhen the storage pool directory wasopened or when data was written to thestorage pool directory. The access modefor storage pool directory Directory Name



in storage pool Pool Name was changedto Access Mode.

Explanation: The access mode is changed for thespecified storage pool directory.

System action: Client nodes cannot access the storagepool and server processes cannot be completed.

User response: Ensure that the storage pool directoryis accessible on the file system. To change the accessmode, issue the UPDATE STGPOOLDIR command andspecify the ACCESS parameter.

ANR3708E The storage pool stgpool name cannot bedefined as a cloud storage pool withthis operating system.



User response: Use an operating system that iscompatible with IBM Spectrum Protect to issue thecommand. For information about operating systemsthat are supported by IBM Spectrum Protect, seetechnote 1243309 "Overview - IBM Spectrum ProtectSupported Operating Systems" (http://www-01.ibm.com/support/docview.wss?uid=swg21243309).

ANR3709W Container container name waspermanently deleted from the filesystem.

Explanation: The specified container could not befound in the database. For this reason, the containerwas deleted from the file system.

System action: The container is no longer available,but system operation continues.


ANR3710I This command will delete containercontainer name from the file system.

Explanation: Because the specified container could notbe found in the database, it will be deleted from the filesystem.

System action: You are prompted to confirm theaction.

User response: Enter 'Y' to delete the container fromthe file system or 'N' to cancel the command.

ANR3711E Container container name will not beremoved from the file system.

Explanation: The container will not be removedbecause its header could not be validated.


User response: To manually remove the containerfrom the file system, delete the file. If the server isinstalled on an AIX, Linux, or Solaris system, issue thefollowing command: rm container_name If the server isinstalled on a Windows system, issue the followingcommand: del container_name

ANR3712E Command: Storage pool NEXTSTGPOOL:storage pool name is a cloud pool.

Explanation: The command indicated specifies thename of a storage pool which is a cloud pool. Thecommand syntax requires that a cloud storage poolname not be specified for non-container storage pools.



ANR3713W Container Container Name was markedfor deletion but stgpool directory StgpoolDirectory is unavailable.

Explanation: The container had no chunks on it andwas marked for deletion. Deletion failed because thecontainer's stgpool directory access was not available.

System action: The system will not remove thiscontainer until the stgpool directory's access isavailable.

User response: Update the stgpool directory's accessto read/write and wait for container deletion to occuragain.

ANR3714E Cannot connect to the cloud serviceprovider with the cloud URL, url, for theoperation_name operation on thepool_name storage pool.

Explanation: The connection to the cloud serviceprovider failed because the cloud URL that is specifiedin the DEFINE STGPOOL command cannot beresolved.


User response: Verify that the cloud url, user ID andpassword for the cloud storage pool are correct andhave been entered correctly, and verify that the cloudprovider is active.

To remove damaged data from a cloud storage poolwithout communicating with the cloud provider, issuethe AUDIT CONTAINER ACTION=MARKDAMAGEDcommand to mark all data on the container asdamaged.



ANR3715E A request to the cloud service providerfor the operation_name operation on thepool_name storage pool failed with thefollowing HTTP status:UNAUTHORIZED.

Explanation: A request to the cloud service providerfailed. The credentials for the cloud service provider donot have the correct permissions to perform the activitythat generated this error.


User response: Ensure that the permissions are correctfor the credentials that are specified for the connectionto the cloud server.

ANR3716E A request to the cloud service providerfor the operation_name operation on thepool_name storage pool failed with thefollowing HTTP status code:http_status_code.

Explanation: A request to the cloud service providerfailed. The cloud service provider responded with anon-successful HTTP status code.


User response: Review the following list of HTTPstatus codes you might encounter in this situation:

v 401 Unauthorized: The request was valid, butauthentication was required and failed, orauthentication was not provided.

v 403 Forbidden: The request was valid, but the serverrefused to respond to it.

v 404 Not Found: The requested resource could not befound, but it might be available again in the future.

v 409 Conflict: The request could not be processedbecause of a conflict in the request.

For more information about HTTP status codes, consultyour object storage provider.

ANR3717E A request to the cloud service providerfor the operation_name operation on thepool_name storage pool failed with thefollowing HTTP status:CREDENTIAL_ERROR.

Explanation: A request to the cloud service providerfailed. The cloud service provider credentials do notexist.


User response: Ensure that the credentials that areprovided to the cloud server exist on the cloud serviceprovider.

ANR3718E A request to the cloud service providerfor the operation_name operation on thepool_name storage pool failed becausethe cloud connection was lost.

Explanation: A request to the cloud service providerfailed. The connection to the cloud service providerwas lost.


User response: Ensure that the cloud server is stillturned on.

ANR3719E The operation_name operation on thepool_name storage pool failed becausethe container_name cloud container doesnot exist.

Explanation: A request to the cloud provider failed.The cloud container that was requested does not exist.


User response: Verify that the container has not beenremoved from the cloud server.

If you want to remove data from a cloud storage poolwithout communicating with the cloud provider, issuethe AUDIT CONTAINER ACTION=MARKDAMAGEDcommand to mark all data on the container asdamaged, and then issue the AUDIT CONTAINERcommand with ACTION=REMOVEDAMAGEDFORCEORPHANDBDEL=YES to remove the data.

ANR3720E A request to the cloud service providerfor the operation_name operation on thepool_name storage pool failed with aHTTP protocol error.

Explanation: A request to the cloud service providerfailed from a HTTP error.



ANR3721E A request to the cloud service providerfor the operation_name operation on thepool_name storage pool failed with aninternal error.

Explanation: A request to the cloud provider failedbecause of an internal error.





ANR3722E A request to the cloud service providerfor the operation_name operation on thepool_name storage pool failed with acreation error.

Explanation: A request to the cloud service providerfailed because output cannot be written to an XML file.



ANR3723E A request to retrieve cloud metrics forthe operation_name operation on thepool_name storage pool failed with aninternal error.

Explanation: A request to retrieve cloud metrics failedbecause of an internal error.



ANR3724E Command: Data in storage pool storagepool name is not protected on servertarget server name.

Explanation: The specified storage pool has not beenprotected by the replication target server, or apreviously issued REPAIR STGPOOL commandinvalidated the protect setting for the replicated targetstorage pool. As a result, you cannot use the REPAIRSTGPOOL command to repair from the replicatedtarget storage pool until the PROTECT STGPOOLcommand is issued for the replicated target storagepool. Any REPAIR STGPOOL commands to the localtarget storage pool are unaffected.


User response: If you have not already set the targetreplication server, issue the SET REPLSERVERcommand to specify the target replication server thatwill be used to protect the storage pool. The namespecified in the SET REPLSERVER command must beassociated with a valid server definition. Issue thePROTECT STGPOOL command with a value ofTYPE=REPLSERVER for the specified storage pool. Forexample, if the source storage pool is named POOL1,issue the following command: protect stgpool pool1type=replserver By issuing the command, you restorethe protect setting on the specified storage pool.

ANR3725E Objects on the cloud provider for thefollowing storage pool storage pool nameare not deleted.

Explanation: The cloud provider is not available todelete a cloud object.

System action: The server deletes the objects from thedatabase.

User response: Ensure that the cloud server is on andthat the credentials are correct. To remove the cloudobjects that remain on the cloud server, issue theAUDIT CONTAINER command.

ANR3726I The AUDIT DATABASE command isprocessing for all container storagepools. Do no complete storage pooloperations during this process.

Explanation: The AUDIT DATABASE command scansmultiple tables in the database. Storage pool operationsthat are processing when you issue the AUDITDATABASE command might affect the audit result.

System action: Confirm whether to proceed with theAUDIT DATABASE command.


ANR3727E AUDIT CONTAINER: TheSTGPOOLDIRECTORY parametercannot be used on this cloud-containerstorage pool because local storage is notavailable for this storage pool.



User response: Verify that local storage is available forthe cloud-container storage pool, and reissue thecommand.

ANR3728E MOVE CONTAINER: You cannot movethe following container: container name.

Explanation: The container that you specified is acloud container. The MOVE CONTAINER commanddoes not apply to cloud containers.


User response: Select a different type of container tomove.

ANR3729I The AUDIT CONTAINER commandprocess process id completed: delete objectcount damaged objects are deleted. skipobject count damaged objects areskipped. delete cloud orphan object countorphan objects are deleted incloud-container storage pools. skip cloudorphan object count orphan objects areskipped in cloud-container storagepools.

Explanation: When you issue the AUDIT



CONTAINER command and specify theACTION=REMOVEDAMAGED parameter,

the following information is displayed:

v The number of damaged objects that are deleted.

v The number of damaged objects that are skipped.

v The number of cloud orphan objects that are deleted.

v The number of cloud orphan objects that areskipped.

The objects being processed are inventory files, dataextents or both.



ANR3730E The audit container operation process_idfailed because it cannot communicatewith the cloud provider for containercontainer_name.

Explanation: The AUDIT CONTAINER commandfailed either because the correct credentials were notprovided to the cloud provider or because the cloudprovider is inactive.

System action: The AUDIT CONTAINER commandfailed.

User response: Verify that the user ID and passwordfor the cloud storage pool are correct and have beenentered correctly, and verify that the cloud provider isactive.

To remove damaged data from a cloud storage poolwithout communicating with the cloud provider, issuethe AUDIT CONTAINER ACTION=MARKDAMAGEDcommand to mark all data on the container asdamaged.

ANR3731E A request to the cloud service providerfor the operation_name operation on thepool_name storage pool failed with the503 HTTP status code.

Explanation: The status code indicates that theoperation cannot proceed. The cloud provider cannotprocess further incoming requests. There might be ahardware limitation or an issue with the configurationsettings.

System action: The server is running, however, thecloud service provider cannot respond to the request.

User response: Verify with your system administratorthat the cloud service provider has the correctconfiguration settings and enough dedicated hardwareto accept additional requests.

v Proxy-server.conf; [default] node_timeout = 120,[app:proxy-server] conn_timeout = 120.

v Object-server.conf; [default] node_timeout = 60,[app:object-server] set node_timeout = 60.

In each .conf file, either set 'workers = auto' or set thatconfiguration equal to a value no greater than thenumber of cores on the system.

ANR3732E Storage pool poolname cannot be updatedbecause of an encryption key mismatch.

Explanation: The master encryption key changed sincethis pool was enabled for encryption. The storage poolcannot be updated without the original masterencryption key.


User response: If you used the BACKUP DBcommand to protect the server master encryption key,use the RESTORE DB command to restore the originalmaster encryption key.

ANR3733W The master encryption key cannot begenerated because the server passwordis not set.

Explanation: Without a master encryption key, storagepool encryption is disabled.

System action: The master encryption key is notgenerated.

User response: Use the SET SERVERPASSWORDcommand to set a server password. After you set thepassword, the master key is automatically generated.

ANR3734E Storage pool encryption could not beenabled because the server has not beenconfigured to protect the encryptionkeys using database backup.

Explanation: Database backup must be configured toprotect the master encryption key to enable stgpoolencryption.


User response: To protect the server masterencryption key during database backup, specify thePROTECTKeys=Yes and PASSword parameters on theSET DBRECOVERY command.

ANR3735W The protect storage pool process forstgpool name on this server to stgpool nameon other server is complete. Some extentsmight not have been protected. Extentsprotected: extents protected of extents toprotect. Extents failed to protect: extentsfailed to protect. Extents deleted: extentsdeleted of extents to delete. Amountprotected: amount protected of amount toprotect. Amount failed: amount transferred.Amount transferred: amount transferred.Elapsed time: elapsed time.

Explanation: The protect storage pool process



completed but some extents might have been skippeddue to conflicting operations. The following listdescribes the information in the message:

v Extents protected: Extents that were successfullyprotected by being linked to matching extents on thetarget server.

v Extents failed to protect: Extents that were notsuccessfully protected during the process ofprotecting to the target server.

v Extents deleted: Extents that were successfullydeleted from the target server because the extent didnot exist on the source server or because it wasdamaged on the target server and needed to beresent.

v Amount protected: Bytes that were successfullyprotected by being linked to matching extents on thetarget server.

v Amount failed: Bytes that were not protected. Seeprevious messages for further details.

v Amount transferred: Bytes that were sent to thetarget server during this process. The amount thatwas transferred can be less than the amount that isprotected when the target server already has some ofthe extents or when compression is enabled.

v Elapsed time: How long the process ran.

User response: Issue the PROTECT STGPOOLcommand again to ensure that all data extents arescanned and protected.

ANR3736E The requested data with the key key forthe operation_name operation on thepool_name storage pool was not found inthe container_name cloud container. Thecontainer should be audited to validateits contents.

Explanation: The requested data was not found on thecloud service provider.


User response: Run the AUDIT CONTAINERcommand on the container or the storage pool.

ANR3737E One or more orphaned extents in thecontainer_name container in thestgpool_name storage pool were skippedbecause the extents could not be deletedfrom the cloud.

Explanation: One or more orphaned extents could notbe deleted from the cloud, so they were not removedfrom the database. This might be a result of lack ofconnectivity to the cloud service provider.

System action: The orphaned extents that were notdeleted from the cloud are skipped. They remainorphaned in the database.

User response: Verify that the cloud URL, user ID,

and password for the cloud-container storage pool arecorrect and were entered correctly. Also, verify that thecloud provider is active. Reissue the AUDITCONTAINER command with theACTION=REMOVEDAMAGED parameter specified toremove the orphaned extents.

If the cloud provider is inactive or inaccessible, and thereferences to the orphaned extents should be removedfrom the database anyway, reissue the AUDITCONTAINER command and specify theACTION=REMOVEDAMAGED andFORCEORPHANDBDEL=YES parameters.

ANR3738I Command: Storage pool storage pool namestill has one or more containers.

Explanation: A DELETE STGPOOL commandencountered a storage pool that still contains one ormore containers.


User response: Empty containers are automaticallydeleted every few minutes. Wait for the automaticdeletion of the empty containers, then reissue thecommand.

ANR3740E One or more orphaned extents in thestgpool_name storage pool were skippedbecause the extents could not be deletedfrom the cloud.

Explanation: One or more orphaned extents could notbe deleted from the cloud, so they were not removedfrom the database. This might be a result of lack ofconnectivity to the cloud service provider.

System action: The orphaned extents that were notdeleted from the cloud are skipped. They remainorphaned in the database.

User response: Verify that the cloud URL, user ID,and password for the cloud-container storage pool arecorrect and were entered correctly. Also, verify that thecloud provider is active. Reissue the AUDITCONTAINER command with theACTION=REMOVEDAMAGED parameter specified toremove the orphaned extents.

If the cloud provider is inactive or inaccessible, and thereferences to the orphaned extents should be removedfrom the database anyway, reissue the AUDITCONTAINER command and specify theACTION=REMOVEDAMAGED andFORCEORPHANDBDEL=YES parameters.

ANR3741E Failed to update the stgpool_name storagepool: cannot change from thecurrent_cloud_type cloud type to thenew_cloud_type cloud type.

Explanation: An UPDATE STGPOOL command



resulted in error because of an incompatible change incloud type. To minimize accidental errors, you cannotchange from the current cloud type to the cloud typeyou specified.


User response: If you still need to update the storagepool, reissue the UPDATE STGPOOL command andmake sure that the CLOUDTYPE parameter is set to avalue that is compatible with the current cloud type ofthe storage pool. Another option is to not specify avalue for the CLOUDTYPE parameter.

ANR3742W This command attempts to update thestgpool_name storage pool. One or moreof the attributes being updated by thiscommand might affect your ability toaccess existing data in this storage pool.

Explanation: The execution of an UPDATE STGPOOLcommand with the parameters that have been specifiedby this command might prevent you from accessingexisting data.

System action: The system asks the administratorwhether to continue with the command.


ANR3743E A request to the cloud service providerfor the operation_name operation on thepool_name storage pool failed with anexception.

Explanation: The cloud client encounters anexceptions in processing the operation_name cloudoperation.

System action: The operation_name cloud operation isended and server operation continues.

User response: Use the QUERY ACTLOG command toexamine messages prior to this error and examineFFDC (First Failure Data Capture) file to determine thecause of the operation failure. If the cause of the failurecan be found and resolved, reissue the command. If thecause of failure cannot be found, contact your servicerepresentative for assistance in resolving the problem.

ANR3744I Session session number started for AsperaFASP high speed data transfer and ispaired with replication session sessionnumber.

Explanation: A new server session has been initiatedby the specified server for Aspera FASP High SpeedData Transfer. The parent session number is included inthe message.

System action: The server begins a FASPcommunications session to service the process.


ANR3745I Session session number ended for AsperaFASP high speed data transfer.

Explanation: An Aspera FASP High Speed DataTransfer session has completed normally.



ANR3746E The operation_name operation on thepool_name storage pool failed becausethe container_name bucket or vault doesnot exist in this region or access pool.

Explanation: A request to the cloud provider failed.The bucket or vault that was requested does not existin the region or access pool pointed to by the storagepool.


User response: Ensure that the CLOUDURL value forthis storage pool is directed to a location that canaccess the bucket or vault.

ANR3747E command: The parameter parameter is notsupported on this platform or with thisconfiguration.

Explanation: The command cannot be processed asspecified because the platform does not support thefeature required by the given parameter, or theconfiguration of the server has not enabled the feature.


User response: Verify the command syntax, platform,and configuration then reissue the command.

ANR3748E The license file that is required toenable Aspera Fast Adaptive SecureProtocol (FASP) technology has expiredon the server_loc server.

Explanation: An attempt to use the Aspera FASP datatransfer method failed because the license file hasexpired on the source or target server.

System action: System operations continue. However,data cannot be transferred by using Aspera FASPtechnology unless a valid license file is installed.






ANR3749I Aspera evaluation license currently inuse to allow FASP transfer method. .

Explanation: An Aspera FASP high speed datatransfer session was established using a 30 day Aspseraevaluation license.

System action: Server operation continue.

User response: The 30 day evaluation license expires30 days from the day it was generated.

ANR3751E The specified credentials failedverification because the container_namebucket or vault does not exist in thisregion or access pool.

Explanation: To use this bucket or vault, theCLOUDURL parameter must match the region oraccess pool in which this bucket or vault exists.


User response: Ensure that the CLOUDURL value forthis storage pool is directed to a location that canaccess the bucket or vault.

ANR3752E The container cannot be moved. Storagepool encryption is in progress for theassociated storage pool storage pool name.

Explanation: The container cannot be moved becausethe associated storage pool is specified by theENCRYPT STGPOOL command. Storage poolencryption is in progress.

System action: The server does not move thecontaienr that is specified.

User response: Wait for storage pool encryption tocomplete and rerun the action again.

ANR3753I The client update package manager isstarted.

Explanation: The update package manager startsautomatically when the server is initialized or whenstatus monitoring is turned on.



ANR3754I The client update package manager isstopped.

Explanation: The update package manager stopswhen status monitoring is turned off.



ANR3755E No directory is specified fordownloading client update packages.

Explanation: Because the directory is not specified, noclient update packages were downloaded. The clientupdate package manager will retry the downloadprocess at the next refresh time.


User response: Specify the directory for downloadingclient update packages by using the SETDEPLOYREPOSITORY command. For example, if thedirectory is client/packages, issue the followingcommand: set deployrepository /client/packages/

ANR3756I A refresh of client update packages wasstarted.

Explanation: The client update package manager isproviding the latest client fix packs to the server.



ANR3757I The refresh of client update packages iscomplete. The next refresh will bestarted on date at time.

Explanation: The client update package managerprovided the latest client fix packs to the server The fixpacks are available for client updates.



ANR3758W Client update package package namecould not be found. The package isskipped.

Explanation: The specified package was not imported.The client update package manager will try to importthe package during the next client update cycle.



ANR3759E An error occurred during the replicationof client update packages from nodeupdate node name to the monitored server,server name. The return code is number.

Explanation: The refresh of client update packages isstopped. The client update manager will retry theprocess at the next specified refresh time.


User response: To determine why the replication filed,review previous server messages and take action toresolve the issues.



ANR3760I All client update package informationwas removed successfully.

Explanation: The client update packages wereremoved in the database. These packages are retriedthe next time the client update package manager runs.



ANR3761E Command: An error was encounteredwhile removing the client updatepackage information from the databaseThe error code is Error code.

Explanation: An error was encountered whileprocessing a request to remove the client updatepackages from the database.


User response: Inspect the activity log and thefirst-failure data capture log, dsmffdc.log, for errorsrelated to the command. Correct the condition thatcaused the error and reissue the command.

ANR3762E Cannot connect to the download site atUrl to download the files that arerequired for client updates.

Explanation: A request to connect to the specifiedURL failed because the client system cannot connect.One or more client update packages cannot bedownloaded, or the update packages might bedown-level.

System action: The connection to the download sitefails.

User response: Verify that you have a workingnetwork connection. Ensure that the URL that isspecified in the CLIENTDEPLOYCATALOGURL serveroption is valid by issuing the QUERY OPTIONCLIENTDEPLOYCATALOGURL command.

ANR3763E An error occurred while the catalog fileused for client updates wasdownloading from Url.

Explanation: The catalog file failed to download fromthe specified URL. One or more update packagescannot be downloaded or the update packages mightbe down-level.

System action: The client update package or catalogfile is not downloaded.

User response: Verify that you have a workingnetwork connection to the specified URL and that youhave enough space to store the catalog file. Issue theQUERY MONITORSETTINGS command to verify thatyou specified a valid client update repository.

ANR3764E An error occurred while processing thecatalog file for client updates from Path.

Explanation: The catalog file cannot be processed.Client update package information might beunavailable or out-of-date. One or more updatepackages might be down-level or unavailable fordeployment.

System action: The catalog file is not processed.

User response: Ensure that you have enough space tostore the catalog file. Issue the QUERYMONITORSETTINGS command to verify that youspecified a valid client update repository. If you areusing a local copy of the catalog file, ensure that thefile exists and that it is not corrupted. If the local copyis invalid, use the catalog file at the default URL that isspecified in the CLIENTDEPLOYCATALOGURL serveroption. If the catalog file on that site is invalid,contactyour service representative.

ANR3765E An error occurred while a client updatepackage was downloading from Url.

Explanation: A client update package failed todownload from the specified URL. The failed packageis not available for deployment until it is successfullydownloaded.

System action: The failed package is not downloaded.

User response: Verify that you have a workingnetwork connection to the specified URL and that youhave enough space to store the package file. Issue theQUERY MONITORSETTINGS command to verify thatyou specified a valid client update repository.

ANR3766W An error occurred while client updatepackages were downloading.

Explanation: One or more packages failed todownload from the specified URL. The failed packagesare not available for deployment until they aresuccessfully downloaded.

System action: The failed packages are notdownloaded.

User response: Issue the QUERY ACTLOG commandto examine the messages that occurred prior toreceiving this error. Examine the first failure datacapture (FFDC) log to determine the cause of theoperation failure. If the cause of failure cannot befound, contact your service representative for assistancein resolving the problem.

ANR3767I All packages were successfullydownloaded for client updates.

Explanation: All of the packages that are required forclient updates were successfully downloaded to the filesystem.





ANR3768E The catalog file at Url does not exist orit cannot be read.

Explanation: The catalog file that is used for clientupdates is not available at the specified location or theserver does not have permission to read the file.

System action: The catalog file is not processed.

User response: Verify that the catalog file exists at thespecified path and that the server has read access forthe file.

ANR3769W Replication of client packages for clientupdates to monitored server, server name,was skipped.

Explanation: The specified server is unavailable, notat the required minimum server level for automaticclient updates, or temporarily unavailable because thisserver's client deploy information is currently beingupdated. The client update manager will retryreplication to the specified server at the next clientupdate refresh time.


User response: Start the specified server, or, upgradethe server to Version 8.1.3 or later.

ANR3770E Command: The directory path, path name,does not exist on the system.

Explanation: The specified directory path does notexist.



ANR3771E Command: Server is not configured forclient updates.

Explanation: The server is not configured for clientupdates. The server must be configured as a Hubserver.


User response: Issue this command on a Hub serveror use the Operation Center to configure your server asa Hub server.

ANR3772E The upgrade repository directory at Urldoes not exist or it cannot be read orwritten to.

Explanation: The repository directory that is used forclient updates is not available at the specified locationor the server does not have permission to read andwrite to the directory.

System action: Client update packages are notdownloaded.

User response: Verify that the repository directoryexists at the specified path and that the server has readand write access for the directory.

ANR3773I Client updates scheduled: numbercompleted of total number schedules werecreated for server name.

Explanation: The request to create deploy schedulesfor one or more client nodes is completed successfully.



ANR3774E Client updates scheduled with failures:number completed of total numberschedules were created for server name.

Explanation: The request to create deploy typeschedules for one or more clients is completed. Thespecified number of schedules were not created due toerrors.


User response: Check messages in the activity log onthe server to determine the reason for the error.

ANR3775I Client updates canceled: numbercompleted of total number schedules werecanceled for server name.

Explanation: The request to cancel deploy typeschedules for one or more client nodes is completedsuccessfully for the specified server.



ANR3776E Client updates canceled with failures:number completed of total numberschedules were canceled for server name.

Explanation: The request to cancel deploy typeschedules for one or more client nodes completed withfailures. The specified number of schedules for theserver were not cancelled due to errors.


User response: Check messages in the activity log on



the specified server to determine the reason for theerror.

ANR3777I Import of client update packagesstarted.

Explanation: The deployment package manager hasstarted importing the client update packages to theserver.



ANR3778I Client update packages imported:number completed of total number packageswere imported.

Explanation: The deployment package manager hasfinished importing client update packages to the server.



ANR3779E Client update packages imported withfailures: number of successes of totalnumber packages imported.

Explanation: The deployment package manager hasfinished importing client update packages to the server.There were some client update packages that did notget imported due to failures.


User response: Check messages in the activity log onthe specified server to determine the reason for theerror. Correct the errors. The deployment packagemanager will retry importing them at the nextdeployment package refresh time.

ANR3780I Replication of client update packagesstarted to server server name.

Explanation: The deployment package manager hasstarted replicating the client update packages to thespecified server.



ANR3781I Client update packages weresuccessfully replicated to server servername.

Explanation: The deployment package manager hasfinished replicating client update packages to thespecified server successfully.



ANR3782E Replication of client update packagesended with failures to server server name.

Explanation: The deployment package manager hasfinished replicating update client packages to theserver. There were some client update packages thatdid not get replicated due to errors.


User response: Check messages in the activity log onthe specified server to determine the reason for theerror. Correct the errors. The deployment packagemanager will retry the replication at the nextdeployment package refresh time.

ANR3783E A client update was not scheduled fornode node name on server server name.

Explanation: The client update schedule was notcreated due to an error.

System action: The schedule is not created. Serveroperation continues.

User response: Review the related activity logmessages on the specified server to determine the causeof the error.

ANR3784E Node node name was not associated withthe client update schedule schedule nameon server server name.

Explanation: The client was not associated with theupdate schedule due to an error.

System action: The client is not associated with theschedule. Server operation continues.

User response: Review the related activity logmessages on the specified server to determine the causeof the error. You can use the Operations Center tocancel the schedule or issue the DEFINEASSOCIATION command to manually associate theclient with the schedule.

ANR3785E The client update schedule schedule namewas not canceled for node node name onserver name.

Explanation: The update schedule was not canceleddue to an error.

System action: The schedule is not canceled. Serveroperation continues.

User response: Review the related activity logmessages on the specified server to determine the causeof the error. You can use the Operations Center to trycanceling the schedule again or issue the DELETESCHEDULE command on the server to manually deletethe schedule.



ANR3786E Server server name cannot create orcancel client updates because the serveris unavailable or has an unsupportedsoftware version installed.

Explanation: Update schedules cannot be created orcanceled on the specified server.

System action: Client update operations are skippedfor the specified server. Server operation continues.

User response: Ensure that the server is running andthat there are no network issues. If the server isrunning an earlier software version, upgrade to Version8.1.3 or later.

ANR3787I The client update catalog wasdownloaded successfully from URL URL

Explanation: The deployment manager has finisheddownloading the client update catalog file.

System action: Catalog processing continues.


ANR3788I Started downloading num packages stringclient update packages.

Explanation: The deployment manager starteddownloading the client update packages to the server.



ANR3789I The client update package wassuccessfully downloaded from: URLpath.

Explanation: The deployment manager finisheddownloading the client update package to the server.



ANR3790E The client update schedule could not becreated for node node name on serverserver name. The client update packagecould not be found for platform, platformname(architecture name), and versionversion.

Explanation: The client update package needed bydeploy schedule could not be found. The deployschedule could not be created.

System action: The schedule is not created. Serveroperation continues.

User response: Retry client update for the node afterthe next deploy package refresh is finished.

ANR3791E Command: Orphan Type discovery iscurrently running.

Explanation: The orphan discovery operation isalready running.


User response: Re-issue the command when orphandiscovery is not running.

ANR3792E Command: Orphan Type discovery orcleaning is not currently running.

Explanation: The orphan discovery or cleaningoperation is not running.


User response: Re-issue the command when orphandiscovery or cleaning is running.

ANR3793E Command: Orphan Type clean is currentlyrunning.

Explanation: The orphan cleaning operation is alreadyrunning.


User response: Re-issue the command when orphancleaning is not running.

ANR3794E Data from cloud containercontainer_name in storage pool pool_namecould not be uploaded.

Explanation: The operation to upload data to theobject storage system failed. This issue might be causedby a faulty network connection to the object storagesystem.

System action: The command fails, but systemoperation continues.

User response: To resolve the issue, complete thefollowing steps: 1. Check the network connection to theobject storage system. 2. Correct any detected issues. 3.Retry the upload operation.

ANR3824W Replication skipped one or more filesfor node node name file space file spacename because they were updated afterthe replication process was started.

Explanation: During replication processing, a clientupdated one or more files for the specified node andfile space.

System action: Replication skips the updated files.

User response: To replicate the updated files, reissue



the REPLICATE NODE command.

ANR3825E Command: Transfer Method transfermethod is not valid.

Explanation: The transfer method must be one of tcpor fasp on a platform that supports fasp.


User response: Update the PROTECT STGpoolparameter for the pool you are trying to protect.

ANR3826E Command: Transfer Method transfermethod is not valid.

Explanation: The transfer method must be one of tcp,or fasp on a platform that supports fasp.


User response: Update the Replicate Node parameterfor the node you are trying to replicate.

ANR3827E A request to create a container on thepool_name storage pool failed the accesspool does not have a vault template.

Explanation: A request to create a container failedbecause a default vault template was not specified, orthe default vault template was not deployed to thespecified accesser.


User response: Ensure that the IBM Cloud ObjectStorage dsNet has a default vault template specified,and ensure that the default vault template is deployedto the access pool which contains the accesser to whichthis storage pool points. Then run the command again.

ANR3828E The command specified multiple Amazonendpoints in the CLOUDURL parameter.

Explanation: The command specified a CLOUDURLparameter that listed multiple endpoints for anAmazon object storage system.


User response: Reissue the command with only oneAmazon endpoint specified in the CLOUDURLparameter.

ANR3829I The AUDIT CONTAINER processprocess_id ended for the stgpool_namestorage pool: inspected_extents cloudobjects inspected and orphaned_extentsdata extents marked as orphaned.

Explanation: The orphaned extent identificationgenerated the following information:

v The number of cloud objects inspected

v The number of orphaned data extents


User response: To remove orphaned extents fromcloud containers, issue the AUDIT CONTAINERcommand and specify theACTION=REMOVEDAMAGED parameter.

ANR3830E The command command specified thesame endpoint multiple times in theCLOUDURL parameter.

Explanation: The command contained a CLOUDURLparameter that specified one or more endpointsmultiple times.


User response: Reissue the command with aCLOUDURL parameter that specifies each endpointonly once.

ANR3831E FASP session Session identifier aborteddue to outstanding FASP read or writetimeout threshold exceeding timeoutvalue seconds.

Explanation: The FASP session between the serverand the partner system experienced an IO timeoutcondition while transferring data.

System action: The session with the remote system isended.

User response: Ensure that the specified remotesystem is operational and is properly configured to runAspera FASP. Adjust the server option FaspSessTimeoutaccordingly.

ANR3832I Local to Cloud Transfer process processidentifier for storage pool storage poolname started.

Explanation: A process begins to transfer data fromlocal storage to the cloud.



ANR3833I Local to Cloud Transfer process processidentifier for storage pool storage poolname has completed.

Explanation: The process of transferring data fromlocal storage to the cloud has completed.





ANR3834I Container container name is empty andwill not be transferred during processprocess identifier.

Explanation: The local-storage-to-cloud transferprocess will not move empty containers to the cloud.

System action: The local storage container wasskipped during this transfer process.


ANR3835E Command: The process of validatingaspera connection to targetservernamefailed.

Explanation: An error occurred while initializingvalidate aspera.

System action: The validate aspera command isended, but server operation continues.


ANR3836I Validation of the Aspera FASPconnection from srcserver to targetserver.Amount transferred using FASP: faspmbsMB per second. Amount transferredusing TCP/IP: tcpipmbs MB per second.Latency: latency microseconds. Status:status. Days until license expires: expires.

ANR3837I Storage pool Tier process process identifierfor storage pool storage pool name hascompleted.

Explanation: The process of tiering data from localstorage to a tier storage pool has completed.



ANR3838I The Tier Storage pool process numberprocess identifier from storage poolsource_stgpool to tgt_stgpool_type storagepool target_stgpool has completed. TieredFiles: tiered_files, Tiered Bytes:tiered_bytes, Skipped Files: skipped_files,Skipped Bytes: skipped_bytes, Total BytesTransferred: transferred_bytes, Elapsedtime: elapsed_time.

ANR3998W CONVERT STGPOOL is skipping aninconvertible file on volume volume:Node node_name, Type type, File spacefile_space, File name file_name.

Explanation: During the convert process, a file isencountered with a type that is not supported bydirectory-container storage pools.

System action: The file is not converted.

User response: After the storage pool enters theConverted state, issue the MOVE DATA command onthe volume to move the inconvertible files to anotherstorage pool.

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 encountered an errorresulting 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 The protect storage pool process forstgpool name on server this server tostgpool name on server other server iscomplete. Extents protected: extentsprotected of extents to protect. Extentsfailed to protect: extents failed to protect.Amount protected: amount protected ofamount to protect. Amount failed toprotect: amount not protected. Extentsdeleted: extents deleted of extents to delete.Extents failed to delete: extents failed todelete. Extents moved: extents moved forvolume reclamation of extents to move.Extents failed to move: extents not movedfor volume reclamation. Amount moved:amount moved for volume reclamation ofamount to move. Amount failed to move:amount not moved for volume reclamation.Elapsed time: elapsed time.

Explanation: The protect storage pool process iscomplete. The following list describes the informationin the message:

v Extents protected: Extents that were successfullycopied to the target container-copy storage pool.

v Amount protected: Bytes that were successfullyprotected by being copied to the targetcontainer-copy storage pool.




v Extents deleted: Extents that were deleted from thedirectory-container storage pool and have beenremoved from the copy-container storage pool.

v Extents moved: Extents that were successfullyrecopied to the target container-copy storage poolbecause a volume was eligible for reclamation.

v Amount moved: Bytes that were successfullyrecopied to the target container-copy storage pool.

v Amount failed to move: Bytes that were notrecopied. See previous messages for further details.


ANR4001I The preview of protect storage poolstgpool name on server this server tostgpool name on server other server iscomplete. Extents to be protected: extentsto be protected. Amount to be protected:amount to be protected. Extents to bedeleted: extents to be deleted. Extents to bemoved: extents to be moved for volumereclamation. Amount to be moved: amountto be moved for volume reclamation.

Explanation: The storage pool protection preview iscomplete. The following list describes the informationin the message:

v Extents to be protected: Extents that need to beprotected by being copied to the targetcontainer-copy storage pool.

v Amount to be protected: Bytes that need to beprotected by being linked to matching extents on thetarget server.

v Extents to be deleted: Extents that were deleted fromthe directory-container storage pool that need to beremoved from the copy-container storage pool.

v Extents to be moved: Extents that need to berecopied to the target container-copy storage poolbecause a volume was eligible for reclamation.

v Amount to be moved: Bytes that need to be recopiedto the target container-copy storage pool because avolume was eligible for reclamation.

ANR4002W The protect storage pool process forstgpool name on this server to stgpool nameon other server is complete. Some extentsmight not have been protected. Extentsprotected: extents protected of extents toprotect. Extents failed to protect: extentsfailed to protect. Amount protected:amount protected of amount to protect.Amount failed to protect: amount notprotected. Extents deleted: extents deletedof extents to delete. Extents failed todelete: extents failed to delete. Extentsmoved: extents moved for volumereclamation of extents to move. Extentsfailed to move: extents not moved forvolume reclamation. Amount moved:

amount moved for volume reclamation ofamount to move. Amount failed to move:amount not moved for volume reclamation.Elapsed time: elapsed time.

Explanation: The protect storage pool processcompleted but some extents might have been skippeddue to conflicting operations. The following listdescribes the information in the message:

v Extents protected: Extents that were successfullycopied to the target container-copy storage pool.

v Amount protected: Bytes that were successfullyprotected by being copied to the targetcontainer-copy storage pool.


v Extents deleted: Extents that were deleted from thedirectory-container storage pool and have beenremoved from the copy-container storage pool.

v Extents moved: Extents that were successfullyrecopied to the target container-copy storage poolbecause a volume was eligible for reclamation.

v Amount moved: Bytes that were successfullyrecopied to the target container-copy storage pool.

v Amount failed to move: Bytes that were notrecopied. See previous messages for further details.


User response: Issue the PROTECT STGPOOLcommand again to ensure that all data extents arescanned and protected.

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 a



syntax 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.

ANR4012W Dump command: Database page pagenumber is damaged.

Explanation: The specified database page is damaged;it will not be dumped.



ANR4013I Audit command process process idcompleted audit of total numbercontainers; successful number successfullyaudited containers, failed number failedaudited containers.

Explanation: The AUDIT CONTAINER command hascompleted processing.

The following information is displayed:

v The total number of containers that were audited.

v The number of successfully audited containers.

v The number of containers that failed to audit.



ANR4014W Audit container process process id iscanceled.

Explanation: During processing of an AUDITCONTAINER command, the process performing theaudit was canceled.

System action: The AUDIT CONTAINER command iscanceled.




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.




ANR4025W The AUDIT DATABASE commandprocess id ended. Command processing iscanceled.

Explanation: The AUDIT DATABSE command wascanceled during processing.

System action: The AUDIT DATABASE commandended.

User response: Reissue the AUDIT DATABASEcommand.

ANR4026I The AUDIT DATABASE commandprocess started (process ID process ID).

Explanation: The AUDIT DATABASE commandprocess started for the process whose ID that isdisplayed.

System action: The AUDIT DATABASE commandprocess is in progress.

User response: This process may be monitored usingthe QUERY PROCESS command. If this process needsto be cancelled, issue the CANCEL PROCESScommand.

ANR4027I The AUDIT DATABASE commandprocess process id completed processingtotal number orphaned data extents.

Explanation: The AUDIT DATABASE commandcompleted.


v The total number of orphaned data extents that areprocessed



ANR4028I A scan for damaged files is in progress.Processed count damaged file(s).

Explanation: If the REPLRECOVERDAMAGEDsystem parameter is set to ON, the system monitorsserver database tables every 30 minutes to determinewhether the number of damaged bitfiles has changed.If the number has changed, the system initiates a scanof server database tables to identify the damaged filesfor recovery purposes. Depending on the systemenvironment, the scan might take hours or days.

System action: System operation continues during thescan.

User response: No action is required. However, youcan cancel the scan by issuing the following commandfrom the server console or the administrative client:

set replrecoverdamaged off

ANR4029I A scan to identify damaged files is inprogress. If damaged files are detected,a recovery process will begin after thescan is completed.

Explanation: A REPLICATE NODE command initiateda process to identify and recover damaged files. Theserver scans database tables to identify which damagedfiles are eligible for recovery. Depending on the systemenvironment, the scan might take hours or days. Theserver issues periodic ANR4024I messages to indicatethat the scan is ongoing. When the scan is completed,message ANR3650I will appear on the server console.

System action: Server operation continues during thescan. If the scan identifies files that are eligible forrecovery, the recovery process begins.


ANR4030E The replication process failed because ofan inconsistency between extents on thesource server and extents on the targetserver that were written by a PROTECTSTGPOOL process.

Explanation: The REPLICATE NODE or PROTECTSTGPOOL process detected that extents that werewritten to the target server by a PROTECT STGPOOLprocess are inconsistent and out of sync with the sourceserver. The REPLICATE NODE process will end asFAILURE.


User response: Issue the PROTECT STGPOOLcommand with the FORCERECONCILE=YESparameter, and verify that the process has completed.Then, issue the command again without theFORCERECONCILE=YES parameter.

ANR4031I PROTECT STGPOOL: Reclamationprocessing started for container-copystorage pool target pool.

Explanation: The PROTECT STGPOOL commandstarted reclamation processing for the specifiedcontainer-copy storage pool. The reclamation process isintended to move data from underutilized volumes andthus release space.



ANR4032W PROTECT STGPOOL: All data indirectory-container storage pool sourcepool was protected to container-copystorage pool target pool. However,reclamation processing for thecontainer-copy storage pool isincomplete.

Explanation: The PROTECT STGPOOL command



protected all data in the specified directory-containerstorage pool to the specified container-copy storagepool. This ensures that the directory-container storagepool can be repaired if needed. However, reclamationprocessing for the container-copy storage pool isincomplete because the reclamation process wascanceled. The reclamation process is intended to movedata from underutilized volumes and thus releasespace.

System action: The storage pool protection processends.

User response: If the container-copy storage pool isrunning out of space or if this message is issuedfrequently, consider increasing the maximum run timefor the schedule that runs the storage pool protectionprocess. If the container-copy storage pool has sufficientspace and this message is issued infrequently, no actionis required.

ANR4033I Update stgpooldir command process processid completed update of stgpooldir name;successful number successfully updatedcontainers, failed number failed updatedcontainers.

Explanation: The UPDATE STGPOOLDIR commandhas completed processing.


v The stgpool directory updated.

v The number of successfully updated containers.

v The number of containers that failed to update.



ANR4034W Update Stgpooldir process process id iscanceled.

Explanation: During processing of an UPDATESTGPOOLDIR command, the process performing theaudit was canceled.

System action: The UPDATE STGPOOLDIR process iscanceled.


ANR4038W The automatic audit process for storagepool STGPOOL NAME cannot be startedbecause the resource manager for datadeduplication is not enabled.

Explanation: A data deduplication resource managercan be enabled on the server. The resource managerdynamically adjusts the automatic audit process tominimize its performance impact on other processes.The resource manager must be enabled before theautomatic audit process can be started.

System action: System operation continues, but the

automatic audit process for the specified storage pool isnot started.

User response: To enable the resource manager, ensurethat the SDRESMANEVENTENABLE server option isset to YES. To display current option settings, issue thequery option command. To update the server option,issue the SETOPT command: setoptsdresmaneventenable yes

ANR4039I Audit command process process idcompleted audit of total numbercontainers with the following results:successful number containers passed theaudit; failed number containers failed theaudit; processed_extents data extents wereprocessed; damaged_extents data extentswere found damaged; andundamaged_extents data extentspreviously marked as damaged were setto not damaged.

Explanation: The automatic audit process forcontainers is completed.


v The number of containers that were audited

v The number of containers that passed the audit

v The number of containers that failed the audit

v The number of data extents that were audited

v The number of damaged data extents

v The number of data extents that were previouslymarked as damaged and are now set to not damaged

System action: The process is completed.


ANR4040W The automatic audit process forcontainers, process process id, is canceled.

Explanation: The audit process was canceled.

System action: The process was canceled, but systemoperation continues.


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.

System action: Database dump or load processingends.




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.


User response: Reissue the audit command andspecify FIX=YES so that the error can be corrected.

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.





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 policy

set with a default management class specified that doesnot 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. Correct theACTIVE 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 incorrect



information 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 the



QUERY COPYGROUP command, and correct themwith 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 QUERYCOPYGROUP 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 notexist.

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.

ANR4121E Command: An operation that wasinitiated by the MOVE DRMEDIAcommand is in progress for volumevolume name.

Explanation: A subsequent command was issued, andit specifies the same volume. The newly issuedcommand cannot be completed for the specifiedvolume while the MOVE DRMEDIA command is inprogress.

System action: If the newly issued command is aMOVE NODEDATA command, the server skips thevolume and continues moving node data on othervolumes.

User response: Wait until the operation that wasinitiated by the MOVE DRMEDIA command iscompleted. Then, reissue the other command.

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 files previously marked asdamaged reset to undamaged, file countobjects updated.

Explanation: The AUDIT VOLUME commandspecifying FIX=YES for the volume shown has ended.


v The number of files audited

v The number of inconsistent files deleted

v The number of inconsistent files marked as damaged

v The number of files previously marked as damagedthat were reset to undamaged

v The number of updated objects

The number of files marked as damaged includes allfiles belonging to aggregates that were markeddamaged 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 been markedas 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 files previouslymarked as damaged reset to undamaged,file count objects need updating.

Explanation: The AUDIT VOLUME commandspecifying FIX=NO for the volume shown has ended.


v The number of files audited

v The number of inconsistent files marked as damaged

v The number of files previously marked as damagedthat were reset to undamaged

v The number of objects need updating

The number of files marked damaged includes all filesbelonging to aggregates that were marked damagedduring the audit. Inconsistent files are marked asdamaged in the database and can be recovered byusing the RESTORE STGPOOL or RESTORE VOLUMEcommand if copies of the files reside in a COPY storagepool. Another AUDIT VOLUME command may be ableto access the files and reset the damaged indicator inthe database if the audit volume process cannot accessthe files due to hardware problems (for example, dirtytape 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 andupdate the object information, issue the AUDITVOLUME command and specify FIX=YES.

ANR4134E Command: The "parameter" parameter isnot valid for cloud storage pools of thiscloud type.

Explanation: The command indicated specifies aparameter that is not valid for cloud storage pools ofthis cloud type.


User response: Reissue the command with parametersappropriate for this cloud type.

ANR4135E Command: Command could not becompleted because storage pool storagepool name has one or more cloudcontainers.

Explanation: The command could not be completedbecause the storage pool contains one or more cloudcontainers that use the existing bucket name.


User response: Before reissuing the command, ensurethat the command and all of the specified parametersare allowed when cloud containers already exist in thestorage pool.

ANR4136E A create container request to the cloudservice provider for the pool_namestorage pool failed because the bucketor vault this storage pool attempted touse is not accessible with the cloudprovider credentials provided.

Explanation: A create container request failed. Thecredentials for the cloud service provider did not havethe correct permissions for the bucket or vault that thisstorage pool attempted to use.

System action: The create container request fails.

User response: Ensure that the permissions are correctfor the credentials you specified for connecting to thecloud server. As needed, change the settings on thebucket or vault. If you do not have the ability tochange the bucket settings, use the UPDATE STGPOOLcommand with the BUCKETNAME parameter set to abucket or vault with a different name.

ANR4137E Container creation failed because thecurrent credentials do not havepermission for disallowed_operation_nameoperations on the bucket or vault.

Explanation: The credentials for the cloud serviceprovider do not have permission to do all of therequired operations in this storage pool's bucket orvault. As a result, the container was not created.

System action: Container creation was not allowed.

User response: Check the permissions for the bucketor vault and make sure that the credentials for thisstorage pool have permission to read, write, list, anddelete objects in this bucket or vault. If you do nothave the ability to change or view the permissions, andyou have not already written data to this storage pool,you can use the UPDATE STGPOOL command withthe BUCKETNAME parameter to try to use a differentbucket or vault.



ANR4138E A create container request to the cloudservice provider for the pool_namestorage pool failed because the name ofthe bucket or vault that this storage poolattempted to use is not valid for thiscloud service provider.

Explanation: A create container request failed. Thename of the bucket or vault that this storage poolattempted to use is not valid for this cloud serviceprovider.

System action: The create container request fails.

User response: Bucket and vault names must complywith S3 requirements, which can be found in theAmazon S3 documentation online. Also, check withyour cloud service provider for any specific restrictionson bucket or vault names. Use the UPDATE STGPOOLcommand with the BUCKETNAME parameter set to aname that complies with both the S3 requirements, andthe cloud provider restrictions.

ANR4139W The PROTECT STGPOOL settings forthe replicated target storage pool areinvalid. To resolve the issue, thePROTECT STGPOOL command needsto be manually issued for storage poolsource storage pool name.

Explanation: A previously issued REPAIR STGPOOLcommand invalidated the protect setting for thereplicated target storage pool. As a result, you cannotuse the REPAIR STGPOOL command to repair from thereplicated target storage pool until the PROTECTSTGPOOL command is issued for the replicated targetstorage pool. Any REPAIR STGPOOL commands to thelocal target storage pool are unaffected.


User response: Issue the PROTECT STGPOOLcommand with a value of TYPE=REPLSERVER for thespecified storage pool. By issuing the command, thiswill restore the protect setting on the source storagepool.

ANR4140E The specified credentials failedverification because they do not havepermission for disallowed_operation_nameoperations on the bucket or vault.

Explanation: The credentials for the cloud serviceprovider do not have permission to do all of therequired operations in this bucket or vault.


User response: Check the permissions for the bucketor vault and make sure that the credentials for thisstorage pool have permission to read, write, list, anddelete objects in this bucket or vault. If you do nothave the ability to change or view the permissions, trya bucket or vault with a different name.

ANR4141E The specified credentials failedverification because the name of thebucket or vault that was provided wasnot valid for this cloud service provider.

Explanation: Credential verification failed because thename of the bucket or vault that was specified is notvalid for this cloud service provider.


User response: Bucket and vault names must complywith S3 requirements, which can be found in theAmazon S3 documentation online. Also, check withyour cloud service provider for any specific restrictionson bucket or vault names. Use a bucket or vault namethat complies with both the S3 requirements, and thecloud provider restrictions.

ANR4142I The cloud service provider URL andcredentials were verified, and there isnot a bucket or vault on the specifiedcloud service provider with theprovided name.

Explanation: The verification of the credentials andURL for the cloud service provider succeeded.However, the specified bucket or vault does not yetexist.


User response: If these credentials also havepermission to create a bucket or vault, it is safe tocreate a storage pool with these parameters. If not, thenthis bucket or vault should be created by other means,and these credentials should have read, write, delete,and list access to the bucket or vault.

ANR4143E The credentials for the cloud storagepool could not be verified because thenecessary information was not available.

Explanation: The credentials could not be verifiedbecause the cloud type, the URL, the cloud ID, or thecloud password was not specified, and the storage poolprovided did not have values for the missingparameter or parameters.


User response: Either reissue the command whilespecifying all of the necessary parameters, or specifythe storage pool name of an existing cloud storagepool.

ANR4144E Command: Cloud-container storage poolstorage pool name was not found.

Explanation: The specified storage pool is eitherundefined or is not a cloud-container storage pool.




User response: Reissue the command with a validcloud-container storage pool name.

ANR4145E The specified credentials failedverification because they do not havepermission for disallowed_operation_nameoperations.

Explanation: The credentials for the cloud serviceprovider do not have permission to do all of therequired operations.


User response: Make sure that the credentialsprovided grant the permission to read, write, anddelete both objects and containers from the cloudprovider at the provided location.

ANR4146E The shared access signature (SAS) tokenvalue that you entered does not grantpermission for the following serveroperation: disallowed_operation_name.

Explanation: The SAS token might be invalid, expired,or lacking required permissions.

System action: The requested operation is not started.

User response: To resolve the issue, complete thefollowing steps: 1. Ensure that the SAS token is validand has not expired. 2. Verify that the SAS token grantsthe required permissions. Permissions are required toread, write to, and delete objects and containers thatare associated with the storage account at the specifiedlocation.

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.


User response: Reissue the audit command withFIX=YES so that the information can be created orcorrected.

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.



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 command: Internal extent repair processis currently running. Audit commandcan not begin.

Explanation: The internal extent repair process iscurrently running. The audit command will not be ableto begin until it is idle. This will prevent the auditcommand from reporting extents that are currentlybeing repaired.


User response: The internal extent repair proces willreport ANR1758I when it becomes idle. Re-run theaudit command at this time.



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 IBM Knowledge Center for valid values.

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.

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 DEVCLASS command



to determine which device classes are defined on theserver and reissue the RECONCILE VOLUMEScommand.

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.

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 memory



available 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 volumes

associated with the given device class. The number ofvolumes 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, the

device class may have been deleted from the sourceserver. If possible, issue the DEFINE DEVCLASScommand 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 that



server, 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.

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.

System action: The volume is deleted.


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.


ANR4369I Storage pool pool has insufficient diskspace and the operation will wait foradditional space to become available.

Explanation: Disk space for this cloud storage pool islow.

System action: A session is waiting either for datatransfer to the cloud or for additional space.

User response: To avoid waiting for additional spaceto become available, add more disk space.

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 newpassword on the target server. Retry the failingoperation.

ANR4373E Session rejected by target server servername, reason: rejection reason.

Explanation: The source server tried to open a sessionwith the target server. The session was rejected for theindicated 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. For all reasons, if none of theabove are applicable, ensure that that the target serverhas not disabled this server with the DISABLESESSIONS SERVER command. Retry the failingoperation.

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 session andcontinues 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: The target server must be correctlydefined before it can be accessed by the source server.Before you attempt the next operation, define the targetserver by using the DEFINE SERVER command.

If the target server is a replication server and its serverdefinition was incorrectly deleted, redefine the serverby using the DEFINE SERVER command before youattempt replication. However, if you intend to removethe target server from replication because it is no longerrequired, use the REMOVE REPLSERVER command toremove the target server from the list of replicationservers.

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 thefollowing 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 the



following 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 currenttransaction 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 else

change 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.



ANR4392I CONTAINER DEFRAGMENTATIONstarted processing stgpool stgpool name.Containers are only using util pct% ofcntr space due to fragmentation.

Explanation: CONTAINER DEFRAGMENTATION isattempting to free up fragmented space in the stgpool.



ANR4393I CONTAINER DEFRAGMENTATIONfinished reclaiming freed bytes bytes ofunused space on cntr count containers instgpool stgpool name.

Explanation: CONTAINER DEFRAGMENTATIONfreed up fragmented space in the stgpool.



ANR4394I The server database was previouslyrestored, and an audit of the affectedvolumes will now start or restart.Container-copy storage pool volumesthat were reused after the restore datewill be deleted.

Explanation: After a server database is restored from aprevious version, the server scans the volume historyfile to identify container-copy storage pool volumesthat were reused after the restore target date. Thereused storage pool volumes are deleted.

System action: All reused container-copy storage poolvolumes will be deleted. Local protect and repairprocesses are temporarily suspended during thisprocess.


ANR4395E command: The command is not allowedfor the node type of node node name.

Explanation: The command is incompatible with thenode type for the specified node.



ANR4396I The audit process is complete, andreused container-copy storage poolvolumes were deleted. number of volumesvolumes and number of chunks extentswere deleted from container-copy pools.

Explanation: After a server database was restoredfrom a previous version, the server scanned the volumehistory file to identify container-copy storage poolvolumes that were reused since the restore target date.Those reused volumes were deleted.

System action: All reused container-copy storage poolvolumes have been were deleted.

User response: Issue the PROTECT STGPOOLcommand with a value of TYPE=LOCAL to resumeprotection of the primary container storage pool to thecontainer-copy storage pool.

ANR4399E NAS file server NAS file server name isreporting NDMP error number NDMPerror number: NDMP error description.

System action: The process ends.

User response: To identify the cause of the networkdata management protocol (NDMP) error, see thedocumentation for the network-attached storage (NAS)file server. Review the NDMP logs for the NAS fileserver, resolve the error, and restart the operation.



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 CONTEXT messagingcommand.



ANR4446I No damaged data was identified by theAUDIT CONTAINER command (processID process ID).

Explanation: When you issued the AUDITCONTAINER command and specified theACTION=SCANDAMAGED parameter, no damageddata extents were identified.



ANR4483I Node node name issued command: SetAccess copy type file space namehigh-leveladdresslow-level address authorized nodename ,authorized owner name.

Explanation: The SET ACCESS command completed.



ANR4484I Node node name issued command: DeleteAccess copy type file space namehigh-leveladdresslow-level address authorized nodename ,authorized owner name.

Explanation: The DELETE ACCESS commandcompleted.



ANR4485I A storage pool space trigger has beendefined and enabled for storage poolstorage pool name.

Explanation: A storage pool space trigger has beendefined with a DEFINE SPACETRIGGER command forthe specified storage pool.



ANR4486I A default storage pool space trigger hasbeen defined and enabled.

Explanation: A default storage pool space trigger hasbeen defined and enabled. It will be effective for anystorage pools associated with a devtype=DISK deviceclass or a devtype=FILE device class.



ANR4487I The storage pool space trigger is definedfor storage pool storage pool name, but isdisabled.

Explanation: A storage pool space trigger has beendefined for the indicated storage pool, but because thespace expansion percentage is currently set to 0, thespace trigger is disabled.



ANR4488I The default storage pool space trigger isdefined, but it is disabled.

Explanation: A default storage pool space trigger hasbeen defined for storage pools associated with adevtype=DISK or devtype=FILE device class. But it hasbeen defined without a space trigger; because the spaceexpansion percentage is currently set to 0, the spacetrigger is disabled.



ANR4489I The storage pool space trigger has beendeleted for storage pool storage poolname.

Explanation: A DELETE SPACETRIGGER commandhas successfully completed for the indicated storagepool space trigger. Space expansions are no longertriggered automatically for the specified storage pool. Ifa default storage pool space trigger exists, it will apply



to the specified storage pool.



ANR4490I The default storage pool space triggerhas been deleted.

Explanation: A DELETE SPACETRIGGER commandhas successfully completed for the default storage poolspace trigger. Space expansions are no longer triggeredautomatically for storage pool without a specific spacetrigger.



ANR4491I The storage pool space trigger isupdated and enabled for storage poolstorage pool name.

Explanation: An UPDATE SPACETRIGGER commandhas successfully completed for the specified storagepool space trigger. The updated parameters specifiedon the command are used to automatically triggerspace expansion for the storage pool.



ANR4492I The default storage pool space trigger isupdated and enabled.

Explanation: An UPDATE SPACETRIGGER commandhas successfully completed for the default storage poolspace trigger. The updated parameters specified on thecommand are used to automatically trigger spaceexpansion for storage pools without a specific storagepool space trigger and which are associated with adevtype=FILE or devtype=DISK device class.



ANR4493I The storage pool space trigger isupdated, but disabled for storage poolstorage pool name.

Explanation: An UPDATE SPACETRIGGER commandhas successfully completed for the specified storagepool space trigger. However, the space expansionpercentage is currently set to 0, which disables thespace trigger.


User response: To activate the space trigger, use theUPDATE SPACETRIGGER command with theSPACEexpansion parameter to set a value greater thanzero.

ANR4494I The default storage pool space trigger isupdated, but disabled.

Explanation: An UPDATE SPACETRIGGER commandhas successfully completed for the default storage poolspace trigger. However, the space expansion percentageis currently 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.

ANR4495E Command: Storage pool space trigger isnot defined.

Explanation: The storage pool space trigger cannot beupdated or deleted because it is not currently defined.If a storage pool was not specified, an attempt wasmade to delete the default storage pool space trigger,but no default storage pool space trigger is defined.



ANR4496E Command: Storage pool space trigger isalready defined.

Explanation: The storage pool space trigger cannot bedefined because it is already defined for the storagepool. If a default storage pool trigger is being defined,a default storage pool trigger already exists.


User response: Use the UPDATE SPACETRIGGERcommand to modify the indicated space triggerparameters.

ANR4497E Command: EXPansionprefix not valid forstorage pool space trigger with storagepool Storage Pool.

Explanation: The storage pool space trigger cannot bedefined with an EXPansionprefix parameter because thespecified storage pool is not associated with aDISK-type device class. Sequential access storage poolsuse their associated directories for creating space whena space trigger is activated.


User response: Use the UPDATE SPACETRIGGERcommand to create a space trigger without using theEXPansionprefix parameter.



ANR4498E Command: STGPOOL Storage Pool is noteligible for a storage pool space trigger.

Explanation: The indicated storage pool cannot have aspace trigger defined, because it is not associated witha DISK-type or a FILE-type device class, or it is aRECLAMATIONTYPE=SNAPLOCK storage pool.


User response: Use the DEFINE SPACETRIGGERcommand to create a space trigger with a storage poolwhose device class is of type DISK or FILE, or is not aRECLAMATIONTYPE=SNAPLOCK storage pool.

ANR4499E Command: Base backup set name BackupSet Name could not be found.

Explanation: No full backup sets whose name beginswith the specified backup set name prefix could befound.


User response: Use the QUERY BACKUPSETcommand to list available full backup sets and reissuethe command with the backup set name prefix of anexisting full backup set. If no full backup set exists,then do not specify the BASE parameter until after afull backup set has been generated.

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.

ANR4503W The server current date current date isearlier than the date in a server recordserver date.

Explanation: The server has detected that the currentsystem date is an earlier date than the date in a serverrecord that is being processed. Possible causes for thisproblem are the current system date is invalid, theserver was previously run with a future date, or thereis an error in the server record. If the server was runwith a future date, this message will continue to appearuntil that date has passed, or all records with the futuredate have been deleted from the server.

System action: Processing continues. The processingfor the current object may not occur as expected.

User response: On the machine on which the server isrunning, verify that the system date is correct.

ANR4504E Command: The specified point in time isearlier than the point in time of the basebackup set.

Explanation: The point in time specified for thedifferential backup set is earlier than the point in timeof its base backup set.


User response: Reissue the command, specifying alater point in time.

ANR4505E Required table of contents could not becreated for backup set for node name asset name (data type data type).

Explanation: A table of contents could not be createdfor the named object set, but a table of contents wasrequired (TOC=YES was specified or implied).

System action: The backup set is deleted.



User response: Correct the problem that prevented thetable of contents from being created and generate thebackup set again.

ANR4506W Backup set for node name as set name(data type data type) requires a table ofcontents.

Explanation: The specified backup set requires a tableof contents, but TOC=YES was not specified.

System action: The server will attempt to create atable of contents for the backup set. If the table ofcontents creation fails, the backup set will be deleted.


ANR4508I Audit Container (Scan Damaged)process started for container containername (process ID process ID).

Explanation: As the result of an AUDIT CONTAINERcommand that specified scan action for the containershown, the process whose ID is displayed has begunauditing the previously marked damaged data extentson a given container.

System action: The previously marked damaged dataextents on a container are audited. If a data extent is nolonger damaged, it will be reset as not damaged.


ANR4510E The server could not write sequentialvolume history information to volumehistory file name. To restore the database,access to this file is required.

Explanation: While attempting to write sequentialvolume history information to defined history files, theserver could not write to the specified file. Thedatabase cannot be restored until this file can beaccessed.

System action: The server does not write volumehistory information to the file specified

User response: Examine any error messages that mayhave been displayed prior to this message and correctany problems. Ensure that the server has permission towrite to the file indicated and that there is sufficientspace in the file system for the file. On MVS, ensurethat the data set has been allocated and that the serverhas permission to write to the data set. After correctingthe problem, use the BACKUP VOLHISTORYcommand to write sequential volume historyinformation to the file.

ANR4511E Volume history file volume history filename could not be opened. To restore thedatabase, access to this file is required.

Explanation: While attempting to read or write

sequential volume history information from definedhistory files, the server was unable to open thespecified file name. The database cannot be restoreduntil this file can be accessed.

System action: The server does not read or writevolume history information from the specified file.

User response: Examine any error messages that mayhave been displayed prior to this message and correctany problems. Ensure that the server has permission towrite to the file indicated and that there is sufficientspace in the file system for the file. On MVS, ensurethat the data set has been allocated and that the serverhas permission to write to the data set.

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 may havebeen displayed prior to this message and correct anyproblems, 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 usually meansthat usage for a sequential volume was not properlyrecorded for later reference

User response: Examine error messages that may havebeen displayed prior to this message and correct anyproblems, 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 that is available to the server, issue the EXTEND



DBSPACE command to add one or more directories tothe database.

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.




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 may havebeen displayed prior to this message and correct anyproblems, 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 thisinformation the read operation fails.

System action: Server operation ends.

User response: You can restore the database specifyingthe volume names for each restore operation (in order)up to the desired point-in-time. If a volume history fileis available, specify its name in the server options fileand 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 to determineif the invalid record can be located and corrected. If thefile is corrupted or does not contain valid volumehistory entries, it cannot be used for the desiredoperation.

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.

ANR4520I Storage Pool storage pool name is beingskipped during a space allocation. Arequest for request amount megabyteswas made but only available amountmegabytes were available.

Explanation: A request for storage was made in theindicated storage pool. The storage pool has a capacityof the number of megabytes shown. The requestedamount can not be satisfied in the storage pool beingskipped. The next storage pool, if any, will be tried inan attempt to satisfy the request.

System action: The storage server skips the indicatedstorage pool and tries to allocate storage in a "next"pool.

User response: More space can be created in thestorage pool by increasing the number of scratchvolumes allowed (use the UPDATE STGPOOLpoolname MAXSCRATCH=xx command), by creatingprivate volumes in the storage pool (use the DEFINEVOLUME poolname volname command ), or bycreating a storage pool space trigger to monitor storagein the storage pool. The storage pool space trigger can



also automatically create new FILE volumes whenspace triggers are exceeded (use the DEFINESPACETRIGGER STG STGPOOL=poolname command).

ANR4521E The number of volumes specified in theBACKUP DB command is not sufficient.The backup failed.

Explanation: The backup volume provided in theinput parameter for BACKUP DB command is notsufficient.

System action: BACKUP DB terminates.

User response: Provide more input volumes.

ANR4522E RESTORE DB failed with LOG fileerror.

Explanation: The LOG file is not associated with thecurrent log sequence.

System action: RESTORE DB terminates.

User response: Issue REMOVE DB first and retry theRESTORE DB.

ANR4523I Storage Pool Space expansion triggered.Storage Pool storage pool name withcapacity of capacity megabytes requirespercentage percent expansion forexpansion amount bytes of additionalspace.

Explanation: A triggered space expansion has startedfor the indicated storage pool. The storage pool has acapacity of the number of megabytes shown. It is beingexpanded by the indicated percentage as directed bythe storage pool space trigger for this storage pool, orby the default storage space trigger if this storage poolhas no dedicated trigger of its own. The percentage isrepresented by the additional amount of spaceindicated.

System action: Space expansion begins.


ANR4524I Volume volume name defined in StoragePool storage pool name as a result ofstorage pool triggered space expansion.

Explanation: A triggered space expansion has causedthe indicated volume to be created in the storageshown in the message. The volume definition is theresult of a storage pool space trigger definition whichallocates new space when the space trigger spacethreshold is met.



ANR4525E Failure to define volume volume name inStorage Pool storage pool name. Returncodereturn code.

Explanation: A triggered space expansion has causedan attempt to create the indicated in the storage poolshown in the message. The volume creation failed withthe indicated return code. The volume was not addedto the storage pool. Additional messages with specificinformation on the failure are displayed from thevolume creation process.


User response: It might be necessary to take actionbased on the failure message from the volume creationprocess. Such actions might include changing thestorage space trigger definiton, ensuring that hardwareis function properly, or ensuring that the server is setup with sufficient permissions to access and create fileson the file system to which IBM Spectrum Protect iswriting.

ANR4526E Storage Pool Space trigger for storagepool name is ended; the thread resourcenot available.

Explanation: The server cannot start a thread tohandle storage pool expansion for the indicated storagepool.

System action: Server processing continues but thestorage pool is not expanded.


ANR4527W Storage Pool Space trigger for storagepool name is disabled after volumedefinition failures expansion failures.Insufficient space for pool expansion.

Explanation: The server failed to complete a storagepool expansion for the indicated storage pool. Thenumber of failures in pool expansion is also displayed.

System action: Server processing continues but thestorage pool is not expanded. The storage pool spacetrigger for the indicated storage pool is disabled.

User response: Allocate additional storage space tothe server. For storage pools of device type FILE,additional directories may be added to the list ofdirectories that the associated device class uses forstorage. If this action is taken, the correspondingstorage agent directories should be added via theUPDATE PATH command. The storage pool spacetrigger may be re-enabled with the UPDATESPACETRIGGER STG STPOOL=xx command, where xxis the storage pool for which expansion has failed ( nospace trigger parameters need be updated ).



ANR4528W Storage Pool Space Expansion for storagepool name is disabled due to previousexpansion failures. After addressingspace requirements, an UPDATESPACETRIGGER STG command mustbe issued to allow automatic stgpoolexpansion.

Explanation: The server failed to complete a storagepool expansion for the indicated storage pool. Thestorage pool space trigger is disabled due to previousexpansion failures. The storage pool space trigger maybe re-enabled with the UPDATE SPACETRIGGER STGSTPOOL=xx command, where xx is the storage pool forwhich expansion has failed ( no space triggerparameters need be updated ).

System action: Server processing continues but thestorage pool is not expanded. The storage pool spacetrigger for the indicated storage pool remains disabled.This message is re-issued periodically when expansionis required but the storage pool space trigger remainsdisabled.

User response: Allocate additional storage space tothe server. For storage pools of device type FILE,additional directories may be added to the list ofdirectories that the associated device class uses forstorage. If this action is taken, the correspondingstorage agent directories should be added via theUPDATE PATH command. The storage pool spacetrigger may be re-enabled with the UPDATESPACETRIGGER STG STPOOL=xx command, where xxis the storage pool for which expansion has failed ( nospace trigger parameters need be updated ).

ANR4531I An automatic full database backup willbe started. The last log number used islast log used and the first log numberused is first log used. The log file size islog file size megabytes. The maximum logfile size is maximum log file sizemegabytes.

Explanation: When the log space used since the lastdatabase backup exceeds the maximum log file size, afull database backup is started.

System action:

User response:

ANR4533E Database database name is invalid andcannot be created.

Explanation: Follow all of these rules when choosinga database name or alias:

v Character strings that represent names of a databasecan contain any of the following characters: a-z, A-Z,0-9, @, #, and $.

v A database name or alias must be unique in thedatabase instance.

v A database name or alias is one to eight characters inlength.

v The first character of the name must be an alphabeticcharacter, or a @, a #, or a $ character.

v The first three characters of the name cannot be anyof the following strings: SYS, DBM, or IBM.

System action: DSMSERV FORMAT processing stops.

User response: Choose a different database namewhich meets the criteria indicated above and issue theDSMSERV FORMAT command again.

ANR4534E The active log size of active log size MBexceeds the available space active logspace MB.

Explanation: There is not enough space for the activelog size specified in the DSMSERV FORMAT command.


User response: Ensure that the file systems you areusing for database and recovery log activities haveenough space. Reissue the DSMSERV FORMATcommand and specify a smaller value for the active logsize.

ANR4535E The active log directory active logdirectory is not valid.

Explanation: The active log directory that is specifiedin the DSMSERV FORMAT command does not exist.

System action: The database format operation failed.

User response: Verify that the file systems you havespecified for formatting the server database andrecovery log are valid. Reissue the DSMSERV FORMATcommand with a valid active log directory.

ANR4536E File Processor Value Unit table xml filecould not be found or opened for readaccess.

Explanation: The file could not be found or opened.

System action: Contents of the file are not parsed andloaded to the database.

User response: Verify that the file exists in either theserver instance directory or the server installationdirectory. If the file does exist verify permissions forread access. If the file does not exist obtain a copy fromthe IBM processor value unit website.

ANR4537I The active log space used is log spaceused is megabytes, and the active logspace available is log space availablemegabytes. The ratio, active log used ratio,exceeds the threshold log utilizationthreshold.

Explanation: When the active log space used exceeds



the log utilization threshold, the active log space mustbe increased.


User response: Increase the size of the active logspace. For information about increasing the size of theactive log space, search for "active log" in the productinformation: (http://www.ibm.com/support/knowledgecenter/SSEQVQ/).

ANR4538E The server could not write sequentialvolume history information to thevolume history file name temporary file.

Explanation: The server failed to write to the specifiedfile. The volume history file cannot be updated untilthis temporary file can be accessed.

System action: No volume history information waswritten to the temporary file specified.

User response: Examine any error messages thatmight have been displayed prior to this message andcorrect any problems. Ensure that the server haspermission to write to the specified file and that the filesystem has sufficient space for the file.

ANR4539E There is a mismatch in directory countbetween Device Class device class nameand Path Definition for Server servername. The device class has directory countdirectories while the path definition haspath directory count directories.

Explanation: The server was assigning a shared FILElibrary volume to a server or storage agent. Share FILElibraries require a matching number of directories inthe PATH definition for the server or storage agent'saccess to FILE drives and the server's device classdefinition. For example, if the server has the followingdevice class definition: DEFINE DEVCLASS SFILEDEVTYPE=FILE MOUNTL=10 SHARED=YESDIR=D:\DIR1,E:\DIR2,F:\DIR3 a FILE library nameSFILE will be created along with 10 drives namedSFILE1 to SFILE10 in shared library SFILE. Each ofthese drives might have scratch volumes created indirectories D:\DIR1, E:\DIR2 or F:\DIR3. (For UNIXPlatforms, substitute UNIX style names in theexample).

For library clients and storage agents, the appropriatedirectory paths from those systems must be definedusing the DEFINE PATH command. An example, inthis case, might be DEFINE PATH STA1 SFILE1SRCTYPE=SERVER DESTTYPE=DRIVEDIR=V:\DIR1,W:\DIR2,X:\DIR3 LIBRARY=SFILEwhich means that server (or storage agent) STA1accesses directory D:\DIR1 using V:\DIR1 from theSTA1 system, E:\DIR2 on the server is accessed usingW:\DIR2 on STA1, and that F:\DIR3 is accessed usingX:\DIR3 on STA1. If the number of directories betweenthe PATH and DEVCLASS do not match, there could

be problem in accessing the resulting file in the future.

System action: Processing continues. Anotherdirectory path is chosen. This might result in asubsequent access failure by the storage agent.

User response: Use the QUERY DEVCLASS classnameF=D and the QUERY PATH pathname F=D commandsto compare the directory lists for the device class andthe path and ensure that they are synchronized.

ANR4540I Container container name is now pending- Container will be deleted from storagepool storage pool name after the reusedelay period for this storage pool haselapsed.

Explanation: All files have been deleted from theindicated container. The container will not be removedfrom the storage pool until the reuse delay time periodfor the indicated storage pool has elapsed.



ANR4542E Audit command: Invalid server for deviceclass device class id in DevClass.Dirstable. The server name in the table isserver name.

Explanation: A database audit process finds adirectory entry with a server which is either notdefined or has an invalid length in the DevClass.Dirstable. This table relates directories to device classes andpaths. The class ID of the table entry is shown, alongwith the server name. However, if the server name hasan invalid length, only blanks are shown.


User response: If the FIX=YES parameter wasspecified, the data base record with the incorrect entrywill be deleted. Otherwise, reissue the audit commandwith FIX=YES, so that the incorrect record can bedeleted. After records with incorrect entries have beenremoved, review directories associated with deviceclasses and paths with the following commands:QUERY DEVCLASS F=D QUERY PATH F=D

ANR4546W A ping request to server 'server name'was not able to establish a connectionby using server credentials.

Explanation: The failure could indicate a problem onthe source or target server, or in the connectionbetween the servers.

System action: No connection was established.

User response: To identify and resolve the issue,complete the following steps: 1. Check the activity logand server console for messages that indicate a failureor problem on the source server. 2. Check the



communication connection between the servers. 3.Verify the server definition and password on bothservers. 4. Verify that the target server is running. 5.Correct any identified issues.

ANR4547W The clock on the remote serverserver_name differs from the clock on thelocal server by seconds seconds.

Explanation: The clocks on the local and remoteservers are not consistent. This can cause variousproblems such as inconsistent status reporting.


User response: Make sure that the clocks on allservers are set correctly. If possible, use an internet timeservice to automatically synchronize the clocks.

ANR4548W command: The specified at-risk intervalof interval hours exceeds the activitysummary retention of retention days.

Explanation: The activity summary is used todetermine if a client has been backed up within theat-risk interval. If the interval exceeds the activitysummary retention, the server may not be able to finda qualifying backup and would consider the client tobe unprotected.


User response: Either invoke the command again toreduce the interval or use the SETSUMMARYRETENTION command to increase theactivity summary retention.

ANR4550I Full database backup (process process ID)completed. Total bytes backed up: totalDB bytes.

Explanation: A full database backup process hascompleted. The output volumes used in this backupmay be used during a database restore operation.



ANR4551I Incremental database backup (processprocess ID) completed. Total bytesbacked up: total DB bytes.

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.



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.


ANR4558I Snapshot database backup (processprocess ID) completed. Total bytesbacked up: total DB bytes.

Explanation: A differential database backup processhas completed. The output volumes used in thisbackup may be used in conjunction with precedingvolumes in the full backup during a database restoreoperation.



ANR4559I Backup DB is in progress.

Explanation: The database backup in process.



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 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 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 becorrected, 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 VOLUME



command 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.

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 thesequential 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.

ANR4585W Volume History File does not exist -Backup/Restore DB operation requiresvolume history file.

Explanation: Volume history file is needed for thebackup/restore DB operation. .

System action: .

User response: Please specify volume history file inthe dsmserv.opt.

ANR4586E Not able to get a DB2 connection.Backup DB operation will beterminated.

Explanation: DB2 connection is needed for the backupDB operation. .

System action: Backup DB operation is terminated.

User response: Verify database manager resources.Submit command again.

ANR4587E Database backup or restoreconfiguration is incorrect; client nodenode name was attempted to be used forthis operation.

Explanation: A server database backup or restoreoperation was attempted and failed. The indicatedclient node was used for the operation which isincorrect. The server database backup and restoreoperations are a restricted protocol and require theexplicit use of client node name $$_TSMDBMGR_$$.



System action: Database backup or restore operationfailed and is terminated.

User response: Verify that the configuration of thedsm.sys file used by the IBM Spectrum Protect API forthe system where the server is installed. The serverstanza in the dsm.sys file for the database backup mustbe configured as follows:

v The NODENAME option must specify$$_TSMDBMGR_$$.

v If the server is configured for database backup andrestore using TCP/IP, the server TCP/IP addressmust be loopback (127.0.0.1).

v The server is configured to listen on the appropriateTCP/IP port or SHMPORT.

ANR4588E A database backup configuration mightbe incorrect.

Explanation: A server database backup operationfailed. The server database backup and restoreoperations are a restricted protocol and require theexplicit use of the client node name$$_TSMDBMGR_$$.

System action: The database backup operation failsand is ended.

User response: Verify that the configuration of thedsm.sys file used by the IBM Spectrum Protect API forthe system where the server is installed. The serverstanza in the dsm.sys file for the database backup mustbe configured as follows:

v The NODENAME option must specify$$_TSMDBMGR_$$.

v If the server is configured for database backup andrestore using TCP/IP, the server TCP/IP addressmust be loopback (127.0.0.1).

v The server is configured to listen on the appropriateTCP/IP port or SHMPORT.

ANR4589W The DB2 connection was lost followinga database restore operation.

Explanation: The server database was restored, butthe DB2 connection failed. For this reason, if the pathto the DB2 log directory was changed as part of a DBrestore operation, the database path to the log directorywas not updated automatically.

System action: The server database is restored.

User response: If the path to the DB2 log directorydid not change, no action is needed. If the path to theDB2 log directory changed, you must manually updatethe path when the server is started. To update the path,connect to the DB2 database and change theconfiguration, as described in the following example:

v Start DB2: db2start

v Connect to TSMDB1: db2 connect to TSMDB1

v Update the DB2 database configuration: db2 updatedb cfg using NEWLOGPATH (log path from serveroptions, e.g. /ALOG/tsminst1)

v Terminate the connection to TSMDB1: db2 terminate

v Recycle DB2: db2stop/db2start

v Verify that the new log path is in takes effect: db2connect to TSMDB1; db2 get db cfg | grep "Path tolog files ( on UNIX ) "

v Verify that the new log path is in takes effect: db2connect to TSMDB1; db2 get db cfg | find "Path tolog files ( on Windows ) "

ANR4591I Selected backup series seriesId from dateand time as best candidate available forrestore database processing.

Explanation: The DSMSERV RESTORE DB commandevaluates the volume history file using the criteriaspecified for the command to determine the bestcandidate database backup to use.


User response: Evaluate the backup series, date, andtime reported to determine if this meets the desiredrestore objectives. If these do not meet the objectives,re-issue the DSMSERV RESTORE DB with additional orchanged information in order to achieve the desiredrecovery objectives.

ANR4592I Restore database backup series seriesIdincludes eligible operation opId withvolume volume name having sequencesequence and using device class deviceclass.

Explanation: The DSMSERV RESTORE DB commandevaluates the volume history file using the criteriaspecified for the command to determine the bestcandidate database backup to use. The opId and volumename for the indicated device class are candidatevolumes that will be evaluated and used for the restoredatabase process.


User response: Evaluate the backup series, date, andtime reported to determine if this meets the desiredrestore objectives. If these do not meet the objectives,re-issue the DSMSERV RESTORE DB with additional orchanged information in order to achieve the desiredrecovery objectives.

ANR4593E Restore database unable to find eligiblecandidate to use for processing.

Explanation: The DSMSERV RESTORE DB commandevaluates the volume history file using the criteriaspecified for the command to determine the bestcandidate database backup to use. No eligiblecandidate backup series was found.




User response: Evaluate the volume history file andavailable volumes to use for restore of the database.Manually add entries to the volume history file for abackup series and corresponding volumes to considerfor restore database processing.

ANR4594E Restore database expects volumevolumeName for backup series seriesIDand operation operationID but it couldnot be found in the available volumehistory files.

Explanation: Once the DSMSERV RESTORE DBcommand selects a candidate database backup series, itwill validate the information from the backup datastream and compare it to the information availablefrom the volume history file. In this case, the databasebackup requires the specified volume for restoreprocessing of this backup series but this volume wasnot found in the available volume history fileinformation.


User response: Evaluate the volume history file andavailable volumes to use for restore of the database. Ifthe specified volume is available, than add an entry tothe volume history file for this volume and retry theoperation. If this volume is not available, than removeall entries from the volume history that are assigned tothis backup series ID. Once those entries are removed,retry the database restore operation and it will attemptto select the next best candidate for processing.

ANR4595E Restore database expects a streamsequence stream for backup seriesseriesID and operation operationID but itcould not be found in the availablevolume history files.

Explanation: Once the DSMSERV RESTORE DBcommand selects a candidate database backup series, itwill validate the information from the backup datastream and compare it to the information availablefrom the volume history file. In this case, the databasebackup has information for the indicated streamsequence but it has been unable to find anyinformation about volumes used for that stream withinthis backup series and operation.


User response: Evaluate the volume history file andavailable volumes to use for restore of the database. Ifadditional volumes are available for this series andoperation, than add entries to the volume history filefor these volume and retry the operation. If no othervolumes are available, than remove all entries from thevolume history that are assigned to this backup seriesID. Once those entries are removed, retry the databaserestore operation and it will attempt to select the next

best candidate for processing.

ANR4596E The restore database operation is unableto validate the selected database backupfor series seriesID and operationoperationID against the actual data fromthe database backup stream.

Explanation: When the DSMSERV RESTORE DBcommand selects a candidate database backup series, itwill validate the information from the backup datastream and compare it to the information availablefrom the volume history file. In this case, the databasebackup is missing information that is needed in orderto perform a restore of the server database.


User response: This error can be caused by one of thefollowing conditions: 1. All of the necessary volumesare not available and specified in the volume historyfile. 2. The release level of the server database backupis different from the release level of the server that isbeing restored. For example, error ANR4596E will occurwhen you restore a V6.2 database and you are using aV6.3 IBM Spectrum Protect server. 3. You have thewrong volume that is designated with sequence 10001.If a volume in the volume history file for this backupseries and operation is assigned 10001, try assigning adifferent volume as sequence 10001. The volumeassigned sequence 10001 is expected to have theself-describing validation information and signaturesthat are used by the restore process for the validationof an operation for a backup series. The restore will failif this information is not found or is incorrect.

ANR4597E Operation operationId for backup seriesseriesID does not reference volumevolumeName, the volume historyinformation is not correct.

Explanation: Once the DSMSERV RESTORE DBcommand selects a candidate database backup series, itwill validate the information from the backup datastream and compare it to the information availablefrom the volume history file. In this case, the volumehistory information reports a volume assigned to agiven series and operation but that backup does notreference that volume.


User response: This may be caused by one of twopossible cases. The first is that the transaction loginformation recorded for this backup to make thisdatabase referentially consistent required more than onevolume to store this information. This should bereferenced with a write sequence number greater than10001. If this was assigned a sequence value less thanthis value, it would be considered as a database backupvolume which would result in this error. Alternatively,if this volume simply does not belong to this databasebackup series or operation, that would result in this



failure as well. Removing this entry from the volumehistory file to eliminate it from consideration for thisbackup series and operation or correcting the operationid and series id to an approprite value would alsoresolve this. After considering the cases above andtaking action for one or the other of them, retry therestore database operation.

ANR4598I Validating database backup informationfor selected backup series seriesId andoperation operationId using volumevolumeName.

Explanation: The database backup information for theselected backup series selected from the volume historywill be validated against the information from thedatabase backup itself. The volume history informationwill be cross-checked to insure that the backup series,necessary volumes, and other attributes of the databasebackup are correct and complete for this operation.Note that if the database restore operation includesincremental database backups, the validation will bedone using the volumes assigned to sequence number10001 for operationId 0 and the operationIdrepresenting the best candidate for restore of theincremental database backup data.


User response: If the information is cross-checked andvalidated successfully, the database restore will beattempted using this database backup series andcorresponding volumes. If the information fails tovalidate, additional messages will be issued indicatingwhat is missing or why the selected database backupseries and volumes can not be used. In the case that thevalidation failed, review the other messages and takethe corrective action specified by those messages andthan retry the database restore operation.

ANR4599W Could not create the server database logdirectory Log directory.

Explanation: During a database restore operation,directories for active, archive, mirror, and archivefailover logs might be created. Errors can occur duringcreation of these directories due to permission, path, orfile system issues.

System action: The database restore was successful.However, the server might not be running with thespecified log directories.

User response: Review the server options file and theoutput of the QUERY LOG F=D command. Ensure thatthe configured log directories were created and havethe required access permissions. If you make changes,restart the server.

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.

ANR4603I The volume history file that existedbefore the upgrade to Version 6.3 orlater was saved under another name: filename.

Explanation: After an upgrade of IBM SpectrumProtect server to V6.3 or later, if you want to revert tothe previous release, you must have the originalvolume history file. The reason is that the V6.3 or latervolume history file has a different format than theearlier volume history file. The newer volume historyfile cannot be used to restore the IBM Spectrum Protectdatabase to the previous release.

System action: The system saves the previous volumehistory file under another name to ensure that it is notoverwritten.

User response: To restore the IBM Spectrum Protectdatabase, use the saved volume history file.

ANR4604E Restore database volume header magicnumber magic does not match theexpected volume header magic numberof expected magic. This volume cannot beused to restore the database.

Explanation: Each volume contains an IBM SpectrumProtect volume header that begins with a header magicnumber. A bad magic number indicates that thisvolume is either corrupted or not suitable for restoringthe database.

System action: The server does not process theDSMSERV RESTORE DB command.

User response: Check the volume history file to makesure that this volume is a valid database backupvolume. If the volume is corrupted, restore thedatabase to a different time using a different set ofbackup volumes.

ANR4605E Restore database volume header versionnumber version does not match theexpected volume version number ofexpected version. This volume cannot beused to restore the database.

Explanation: Each database backup volume containsan IBM Spectrum Protect version number in thevolume header. A mis-matched version number



indicates that this volume is either corrupted or notsuitable for restoring the database. This volume may bea pre Version 6.3.0 database backup volume. It cannotbe used to restore an IBM Spectrum Protect V6.3database.


User response: Check the volume history file to makesure that this volume is a valid database backupvolume. If this volume is corrupted, restore thedatabase to a different time using a different set ofbackup volumes.

ANR4606E Restore database volume header backupseries number series does not match theexpected backup series number ofexpected series. This volume cannot beused to restore the database.

Explanation: Each database backup volume containsan IBM Spectrum Protect backup series number in thevolume header. A mis-matched backup series numberindicates that this volume is either corrupted or notsuitable for restoring the database.


User response: Check the volume history file to makesure this volume is valid for a database backupoperation. If the volume is valid, the volume historyfile can be modified to match this series number andyou can reissue the DSMSERV RESTORE DB command.If the problem persists, this volume may be corrupted.Restore the database to a different time using adifferent set of backup volumes.

ANR4607E Restore database volume header backupoperation number operation does notmatch the expected backup operationnumber of expected operation. Thisvolume cannot be used to restore thedatabase.

Explanation: Each database backup volume containsan IBM Spectrum Protect backup operation number inthe volume header. A mis-matched backup operationnumber indicates that this volume is either corruptedor not suitable for restoring the database.


User response: Check the volume history file to makesure this volume is valid for a database backupoperation. If the volume is valid, the volume historyfile can be modified to match this operation numberand you can reissue the DSMSERV RESTORE DBcommand. If the problem persists, this volume may becorrupted. Restore the database to a different timeusing a different set of backup volumes.

ANR4608E Restore database volume header backuptype backup type is invalid. This volumecannot be used to restore the database.

Explanation: Each database backup volume containsan IBM Spectrum Protect backup type code in thevolume header. An invalid backup type code indicatesthat this volume is either corrupted or not suitable forrestoring the database.


User response: Check the volume history file to makesure this volume is valid for a database backupoperation. If this volume is corrupted, restore thedatabase to a different time using a different set ofbackup volumes.

ANR4609I Restore database process found backuptype database backup timestamp backuptimestamp from database backup media.

Explanation: This is the backup timestamp that isused for a database restore operation.

System action:

User response:

ANR4613E Meta data for restore database volumebackup volume is not valid. This volumecannot be used to restore the database.

Explanation: Backup volumes contain IBM SpectrumProtect meta data. Invalid meta data indicates that thisvolume is either corrupted or not suitable for restoringthe database.



ANR4614E The database backup timestamp ofbackup timestamp on media on databasebackup media with backup type backuptype does not match the backuptimestamp backup timestamp from volhistfrom the volume history file. Thisvolume cannot be used to restore thedatabase.

Explanation: Mis-matched timestamps indicates thatthis volume is either corrupted or not suitable forrestoring the database.





ANR4615E The server is unable to restore thedatabase due to inaccessible media.

Explanation: The database restore operation cannot becompleted. Possible reasons include:

v The device configuration file is not correctly definedto access the media.

v There is a problem with the media.

System action: The database is not restored.

User response: Review the information in the messageexplanation and take action to correct any problemswith the device configuration file or media. Reissue theRESTORE DB command.

ANR4616E Database restore terminated because themedia header cannot be found - DB2sqlcode sqlcode and DB2 error messagesqlerrmc.

Explanation: During a restore operation, the DB2database was unable to find the media header. Theremight be a problem with the media.

System action: The database restore is terminated.

User response: Check if the IBM Spectrum Protectserver reports an error for the media. Ensure that themedia that is used for the database backup is working.

ANR4617I A ping request to server 'server name'was able to establish a connection byusing server credentials.

Explanation: The server credentials are valid.

System action: The connection was established.


ANR4618I The server credentials can not beauthenticated for server server namebecause the server has no definedpassword.

Explanation: The server password is missing.


User response: If you want to use server-to-serverfunctions such as enterprise configuration or nodereplication, a server password is required. To specify apassword, issue the following command: UPDATESERVER server name SERVERPASSWORD=password Thepassword must match the password that is set by theSET SERVERPASSWORD command.

ANR4620I Database backup series Backup seriesoperation backup operation device classdevice class.

Explanation: The device class used 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.



ANR4624I Preview processing for a databaserestore operation has completed.

Explanation: The database restore command wasissued with PREVIEW=YES specified. The server willevaluate the volume history information and report thedetails about what it found. It will report the candidatedatabase backup that was selected based on the restorecommand that was specified. If the database restoreprocessing is unable to find a viable database backup touse for restore or other errors occur during thisevaluation, these will also be reported.


User response: Review the other messages issued todetermine the outcome of the database restore previewoperation.

ANR4625W Database backup failure whileattempting to use number of streamsstreams, backup will be retried usingone stream.

Explanation: The database backup process failedwhile attempting the operation with the specifiednumber of streams. The operation will be retried with asingle stream.

System action: The database backup will beautomatically retried using a single stream.

User response: Review the other messages issued todetermine the reason for the failure of the databasebackup while using multiple output streams. Alsoreview the process completion and other message todetermine if the retry using a single stream wassuccessful.



ANR4626I Database backup will use number ofstreams streams for processing with thenumber originally requested numberrequested.

Explanation: The database backup will be performedusing the specified number of streams. The originalnumber of streams requested, either through thecommand or the NUMSTREAM setting for SETDBRECOVERY, is also displayed.

System action: The database backup will beperformed with the indicated number of streams.

User response: Note that if the number of streamsused for the database backup differs from the numberrequested, this indicates either a configuration error orthat the device being used does not have as manydrives available as was previously considered andplanned for. Review the device class andNUMSTREAM settings used for the database backupcommand to determine if changes are needed or ifactions are needed to bring drives back online.

ANR4627W The object might be incomplete for nodename: type=type, file space=filespace name,object=object name.

Explanation: The IBM Spectrum Protect V7.1.0 serverexported the object of type type for node name,identified by file space and object name. The namedobject might be imcomplete.

System action: The IMPORT operation proceeds.

User response: Restore, retrieve, or recall the namedobject. Verify that all contents of the file are storedproperly.

ANR4628E Device device name failed to close witherror code errno.

Explanation: The IBM Spectrum Protect server cannotclose the device.

System action: The close operation fails.

User response: Check the error code value, get thedevice driver trace and contact the device vendor.

ANR4629E Attempting to restore a fragmented filethrough an earlier-level storage agent.The file will not be restored: Node nodename, Type file type, File space filespacename, File name file name.

Explanation: When the storage agent attempts torestore a fragmented file, the file is not restored. Thisbehavior occurs during a classic restore by using astorage agent earlier than version 7.1.

System action: The file is not restored.

User response: Complete one of the following actionsto resolve the problem:

v Restore the file from LAN explicitly.

v Restore the file through a no-query restore.

v Upgrade the storage agent to a level at version 7.1 orlater.

Refer to APAR IT02547 for more information about theproblem.

ANR4630W Container container name in storage poolstorage pool cannot be opened. Audit willmark the container as unavailable andall the data extents in it as damaged.

Explanation: The AUDIT CONTAINER processencountered an open error for the specified containerwhile attempting to read a data extent. The containerwill be marked unavailable, and all extents within thecontainer will be marked damaged.


User response: Identify and resolve the open error forthe container, if possible. Verify that the container'sphysical device is functioning properly and that thecontainer is usable.

ANR4631W Header of container container name incontainer storage pool storage pool iscorrupted. Audit will mark the containeras unavailable and will record allcontent as damaged.

Explanation: While attempting to access thecontainer's data, the container header was found to becorrupted. The container will be marked unavailable.


User response: Identify and resolve the invalid headerfor the container if possible. Verify that the container'sphysical device is functioning properly and that thecontainer is usable.

ANR4632E Session session number cannot store datain the container storage pool on thetarget replication server. There isinsufficient space in the containerstorage pool stgpool name.

Explanation: During replication processing, there wasinsufficient free space available in the container storagepool on the target replication server.

System action: The replication process fails.

User response: Issue the DEFINESTGPOOLDIRECTORY to define a new storage pooldirectory for the container storage pool on the targetreplication server.



ANR4633W Storage pool directory dir name instorage pool stgpool name can not beaccessed due to its access state access.

Explanation: The specified container's directory isrestricted to access.


User response: Identify and modify the access statefor the stgpool directory if possible.

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.



ANR4639W Container container name in storage poolstorage pool cannot be opened because ofincorrect privilege. The audit containerprocess marks the container asunavailable.

Explanation: The server reports an error for thespecified container during the audit container process.The server cannot read the data extent because theprivilege is incorrect for the server instance ID. Thecontainer is marked as unavailable.


User response: Identify and resolve the opencontainer error, if possible. Verify that the serverinstance ID has the correct privilege to access thecontainer.

ANR4640E Failed to retrieve space statistics fromdirectory directory name.

Explanation: The IBM Spectrum Protect server cannotgather space statistics for the directory.

System action: The directory space stats operationfails.

User response: Ensure that the directory has thecorrect permissions and can be accessed by the IBMSpectrum Protect server.

ANR4641W command: Replication is disabledbecause node name is not eligible forreplication.

Explanation: When you issue the REPLICATE NODEcommand, the specified node fails to replicate. Clientdeployment package nodes are processed forreplication by the server and are not eligible forprocessing by an administrator or schedule.

System action: Replication processing fails for thespecified node.

User response: Replication processing fails for thespecified node.



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.

ANR4652E No system message queues available forcommunications.

Explanation: While IBM Spectrum Protect was tryingto establish a communications session, an attempt toacquire a system message queue failed. This usuallymeans that the system-imposed limit on messagequeues has been reached.

System action: The communications session is notinitialized due to lack of system resources.

User response: Increase the maximum number ofmessage queues on the system and try the operationagain. This is normally accomplished by increasing thevalue in the kernel's msgmni file.

ANR4653E Incremental backup DB failed. Can notperform incremental DB backup withouta FULL DB backup performed first.

Explanation: A FULL DB backup has to be performedat least once before any Incremental DB backup can beperformed.

System action: The incremental DB backup isterminated.

User response: Reissue the backup db command withtype=FULL.

ANR4654I The restore db to most current time cannot be done since contents of the activeor archive log directories have beenchanged. The DB will be restored to thelast full or full plus incremental state.

Explanation: The restore DB can only restore to thelast FULL backup.

System action:

User response: Do not modify contents of active orarchive log directories before attempting a dsmserv rollforward restore command.

ANR4656E Invalid key-ring file password Key Ringpassword

Explanation: The specified key-ring file passwordexceeds the maximum password length of 64characters.

System action: None

User response: Specify a key-ring file password using1-64 characters. Ensure that the password is the samevalue that was specified with the key-ring filepassword utility.

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.

ANR4658I No key-ring file password was found.

Explanation: Either a QUERY command was issued todisplay the key-ring file password or a SET commandwas issued to inform the server of a change to thekey-ring file password. A password was not recordedby the server.

System action: None

User response: To create a key-ring file or to generatea password, the server must run with secure socketslayer (SSL) transmission control protocol (TCP) portoptions. If the server did not run with SSL TCP portoptions, start the server while the options file containsthe SSLTCPPORT or SSLTCPADMINPORT option. Thenissue the QUERY SSLKEYRINGPW command todisplay the generated password. If you use an externalutility to change the key-ring file password after theserver creates the key-ring file and its password, issuethe SET SSLKEYRINGPW command to inform theserver of the change.

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.


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 withthe 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.


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.


ANR4674E Error starting DPI thread - Return code:Return code received from called routine.

Explanation: The SNMP subagent could not start theDPI thread.

System action: Initialization of the subagent fails.


ANR4675W command: This command may take awhile to finish.

Explanation: A command has been invoked that couldpotentially run for a while.


User response: Enter 'Y' to continue with thecommand or 'N' to terminate the command.

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 andre-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.

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.

System action: The subagent will stop processingrequests from the server sending the invalid requests.




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.


ANR4694E SNMP Subagent Port Confirmation HasFailed.

Explanation: The server was communicatingconfiguration data to the SNMP subagent. An erroroccurred in the exchange. The server could not

communicate 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 has anan 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 sizethreshold. The setting influences file movement forserver migration, reclamation, 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.


ANR4704I key-ring filename and password havebeen set. Restart the server to use thenew settings

Explanation: The key-ring filename have been set to

the new value specified in the DEFINE KEYRINGcommand.


User response: Restart the server to use the newkey-ring information.

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.

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 waits foroperator 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.

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.



ANR4717E command: Replication or recovery ofdamaged files is not supported by targetserver due to unsupported transfermethod fasp.

Explanation: Replication recovery operationsoriginating from this server are not allowed because thetarget replication server does not support fasp as atransfer method.


User response: Upgrade the target replication serverto a level that supports replication recovery using fasp.

ANR4723E Session rejected for down level storageagent storage agent name.

Explanation: A down level storage agent attempted toconnect to this server. The server can not support allprevious versions of the storage agent.

System action: The server will not supportconnections by storage agents at a specific lowerversions of the product. Review the README for anexplanation of supported storage agent levels for thisserver. The storage agent will not startup and willreport ANR0454W indicating that it is down level.


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 can cause files to be deleted. The file spaceimage on the server will not be consistent with theclient until an incremental backup is completed for thenode.

System action: The server will continue processing.

User response: Perform an incremental backup for theclient 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 support module hasbeen 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.


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 An unsupported model of the filer server wasdetected

v If the message specifies address 127.0.0.1 or theaddress of the server system, theNDMPCONTROLPORT and/or NDMPPORTRANGEoptions may be set to port numbers or ranges whichare already in use.

System action: IBM Spectrum Protect serverbackup/restore of the file server 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 IBM Spectrum Protectserver. If the server's address is in the message ensurethat the ports specified or defaulted for optionsNDMPCONTROLPORT and/or NDMPPORTRANGEare available for use. Depending on the operatingsystem, the netstat operating system command may beused to determine in-use port numbers.

ANR4729E Server connection to file server Fileserver name failed. The level of the fileserver operating system is unsupportedby IBM Spectrum Protect server. Pleaseupgrade the file server to the level ofthe operating system supported by theserver.

Explanation: The IBM Spectrum Protect server was



trying to connect to a file server with an unsupportedlevel of the operating system. The server can establishNDMP connection only to a file server with supportedlevel of the operating system. Please check thefollowing site for supported levels of file serveroperating systems: http://www.tivoli.com/storage

System action: The IBM Spectrum Protect serverbackup/restore of the file server fails.

User response: Upgrade the file server to a supportedlevel of the operating system.

ANR4730E Command: The number of stgpool typestorage pool names specified with theparameter name parameter exceeds themaximum number allowed.

Explanation: The number of copy storage poolscombined with the number of active-data storage poolsfor a given primary storage pool is limited to amaximum of three.


User response: Reissue the command, specifying atotal of three or fewer storage pool names.

ANR4731E Command: The pool type storage poolstorage pool name is not defined.

Explanation: A DEFINE STGPOOL or UPDATESTGPOOL command contained a storage pool that isnot defined as either a copy storage pool or anactive-data storage pool.


User response: Verify that the copy or active-datastorage pool name stated in the error message iscorrect. If using the COPYSTGPOOLS parameter,correct the problem by using a copy storage pool thatalready exists or define the copy storage pool. If usingthe ACTIVEDATAPOOLS parameter, correct theproblem by using an active-data storage pool thatalready exists or define the active-data storage pool.Retry the command.

ANR4732E Command: The storage pool stgpool nameis not a copy, active-data, orcontainer-copy type storage pool.

Explanation: A DEFINE STGPOOL or UPDATESTGPOOL command contained a storage pool namethat is not a copy, active-data, or container-copy typestorage pool.


User response: Verify that the copy, active-data, orcontainer-copy storage pool name stated in the errormessage is correct or remove the storage pool namefrom the list. If using the COPYSTGPOOLS parameter,correct the problem by using a copy storage pool that

already exists or define the copy storage pool. If usingthe ACTIVEDATAPOOLS parameter, correct theproblem by using an active-data storage pool thatalready exists or define the active-data storage pool. Ifusing the PROTECTLOCALSTGPOOLS parameter,correct the problem by using a container-copy storagepool that already exists or define the container-copystorage pool. Retry the command.

ANR4733E Command: The pool type storage poolcontains a pool type storage pool namethat introduces a cycle into the storagepool chain.

Explanation: A DEFINE STGPOOL or UPDATESTGPOOL command contained a copy or active-datastorage pool that eventually points to the storage poolbeing processed.


User response: Remove the storage pool name fromthe copy or active-data storage pool list and retry thecommand.

ANR4734W The pool type storage pool pool name wasremoved from the storage pool listbecause of a failure for session SessionId.

Explanation: The named storage pool was removedfrom the storage pool list for the current sessionbackup/archive/space management operation becauseof 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 one ofmany failure. Look for the following items in the activelog or on the server console. 1. Is the named storagepool currently unavailable? 2. Have any I/O erroroccured on the destination devices (disk or tapedrives)? 3. Is the mount limit on the device classcorrectly set? 4. Is the node's MAXNUMMP valuesufficient to satisfy the request?

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 Command: The number of container-copytype storage pool names specified withthe parameter name parameter exceeds themaximum number allowed.

Explanation: The number of container-copy storagepools for a given primary storage pool is limited to amaximum of two.


User response: Reissue the command, specifying atotal of two or fewer storage pool names.

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 valuesufficient to satisfy the request? 3. Were there anyerrors reported during the transaction regarding I/O orrelated issues?

ANR4738E Command: One or more storage pools usepool name as a copy, active-data, orcontainer-copy type storage pool.

Explanation: The DELETE STGPOOL commandattempted to delete a storage pool that is defined as acopy storage pool, active-data storage pool, orcontainer-copy storage pool for another primarystorage pool.


User response: If necessary, issue the UPDATESTGPOOL command to update the other primarystorage pool. Use the COPYSTGPOOLS,ACTIVEDATAPOOLS, or PROTECTLOCAL parameterto remove the reference to the storage pool to bedeleted. Repeat for all primary storage pools thatreference the storage pool to be deleted. Reissue thecommand.

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 andlow-level address are required for an address to bevalid. For an update, both high-level address andlow-level address are required for the update tosucceed. For a new definition, both high-level addressand low-level address are required whenSESSIONINIT=SERVERONLY. Either the high-leveladdress or low-level address is missing from thiscommand. Issue the command again and supply themissing address represented 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 theLLADDRESS parameter for the node listen portinformation.

ANR4741W This command will renameadministrator adminName. Thisadministrator has defined or updatedschedules. Renaming this administratorwill cause these schedules to fail.

Explanation: A RENAME 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 RENAMEADMINISTRATOR command, enter 'Y' to continue or



'N' to stop the process. To deal with schedules ownedby the administrator, 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 contolled by an administrator that hasauthority to execute them, or use the DELETESCHEDULE command to remove the schedules.

ANR4742W This command has renamedadministrator adminName tonewAdminName. This administrator hasdefined or updated schedules. This willcause these schedules to fail in thefuture.

Explanation: A RENAME ADMINISTRATORcommand has been entered and the administratorrenamed owns the administrative schedules. Theschedules will fail when executed in the future becausethey do not belong to the administrator's new name.

System action: The system renames the administrator.

User response: Use the QUERY SCHEDULE commandor an SQL SELECT statement on theADMIN_SCHEDULES table to determine whichschedules were last updated by the administrator. Usethe UPDATE SCHEDULE command to update thoseschedules controlled by an administrator that hasauthority to execute them, or use the DELETESCHEDULE command to remove the schedules.

ANR4743W An insufficient number of mount pointsare available in device class device classname.

Explanation: During simultaneous write processing,the server cannot allocate sufficient mount points forthe specified device class. Possible reasons include:

v The mount limit specified for the device class doesnot provide a sufficient number of mount points tosupport the simultaneous write operation.

v The drives that service the device class areinaccessible.


User response: Ensure that:

v The mount limit specified for the device classprovides a sufficient number of mount points tosupport the simultaneous write operation.

v Enough drives are defined and on-line for the librarythat services the device class.

ANR4744W The server cannot acquire a sufficientnumber of mount points.

Explanation: During simultaneous write processing,the server cannot acquire a sufficient number of mountpoints to satisfy the request.


User response: Examine error messages that mighthave been displayed prior to, and after this message.Correct any problems, if possible.

ANR4746E Session rejected for up level storageagent storage agent name.

Explanation: An up level storage agent attempted toconnect to this server. The storage agent can not be athigher level than the server.

System action: The server will not supportconnections by storage agents at a higher version, atthe same version with a higher release, or at the sameversion and release with a higher modification level.The storage agent will not startup and will reportANR0454W indicating that no resources are available.


ANR4747W The web administrative interface is nolonger supported. Begin using theIntegrated Solutions Console instead.

Explanation: The web administrative interface is nolonger supported. It has been replaced by anadministrative interface based on the IntegratedSolutions Console.

System action: The web administrative interface's webpage is not displayed.

User response: Install the IBM Spectrum Protectsupport for the Integrated Solutions Console and beginusing it to manage your servers.

ANR4748E A NAS operation requiring NDMPVersion 4 was attempted for file serverFile server name , however the currentNDMP session uses NDMP Version 3.Please verfiy that file server supportsNDMP version 4.

Explanation: A NAS operation which requires NDMPVersion 4 was attempted for a file server that iscurrently configured to run NDMP Version 3.

System action: The IBM Spectrum Protect serverbackup/restore or other operation on the file serverfails.

User response: Verify that the file server supportsNDMP Version 4. Verify that the file server isconfigured to accept connections using NDMP Version4.

ANR4749I Key-ring filename and password havebeen deleted from the server database.

Explanation: The key-ring filename and passwordhave been deleted. Upon restart the server will attemptto generate a new password and new keyring file if



options SSLTCPPORT or SSLTCPADMINPORT are setand the keyring files cert.kdb,cert.crl,cert.rdb do notexist.


User response: Before restarting the server you shoulddelete the corresponding cert.kdb,cert.crl,cert.rdb andcert.arm files from the server execution directory if theyexist. Restart the server to generate and use the newkey-ring information.

ANR4752I REPAIR STGVOL process process numberstarted for number of volumes volumes.

Explanation: The REPAIR STGVOL process has beenstarted as the reported process number. This willevaluate and if needed repair the indicated number ofvolumes.


User response: This process may be monitored usingthe QUERY PROCESS command. If this process needsto be cancelled, issue the CANCEL PROCESScommand.

ANR4753E REPAIR STGVOL process process numberended, processed volumes processed oftotal volumes total volumes with repairedvolumes repaired and failed volumesfailures.

Explanation: The REPAIR STGVOL process has ended.It processed volumes processed out of total volumes totalvolumes to be processed. The repaired volumes indicatesthe number of volumes that needed database repairsand were repaired. The failed volumes are volumes thateither failed during evaluation or during databaserepair if it was needed.


User response: If there were failed volumes, review theactivity log for more information about the failure.

ANR4754I REPAIR STGVOL process process numberended, processed volumes processed oftotal volumes total volumes with repairedvolumes repaired.

Explanation: The REPAIR STGVOL process has ended.It processed volumes processed out of total volumes totalvolumes to be processed. The repaired volumes indicatesthe number of volumes that needed database repairsand were repaired.



ANR4755W REPAIR STGVOL process process numberended, processed volumes processed oftotal volumes total volumes with repairedvolumes repaired.

Explanation: The REPAIR STGVOL process has ended.It processed volumes processed out of total volumes totalvolumes to be processed. The repaired volumes indicatesthe number of volumes that needed database repairsand were repaired.


User response: If the volumes processed is less than thetotal volumes, this may be because the process wascancelled before it could process all the neededvolumes. Review the activity log to determine if this isthe case and re-issue the command to complete thisprocessing. Or if volumes were reclaimed or deletedwhile this process was running, there may have beenfewer actual volumes to process than what wascalculated when the process started. If this is the caseno further action is necessary.

ANR4757I REPAIR STGVOL finished evaluatingvolume volume name, no repair wasneeded.

Explanation: The REPAIR STGVOL finishedevaluating volume name volume. No repair actions weretaken for the database because there were no errorsdetected.



ANR4758W REPAIR STGVOL repaired volumevolume name, database reference errorswere found and corrected.

Explanation: The REPAIR STGVOL evaluated volumename volume and determined that repair actions wereneeded. The necessary repairs were done successfully.



ANR4759E REPAIR STGVOL failed to processvolume name.

Explanation: The REPAIR STGVOL failed for volumename volume. This process either failed whileevaluating this volume or it had determined that repairactions were needed and it failed performing thoseactions.


User response: Review the activity log for anindication of why processing for this volume failed. Tryissuing "REPAIR STGVOL VOLNAME=volume name" toprocess this volume again. If this volume was deleted



from the server, this message can be ignored.

ANR4760I REPAIR STGVOL reset processinghistory.

Explanation: The REPAIR STGVOL command wasissued with RESET=YES. This resets the processinghistory. Resetting the processing allows the commandto be rerun and causes previously evaluated volumes tobe re-evaluated.


User response: An administrator may want toperiodically reset the processing history and re-evaluateall volume in the server as a means of validating theserver database.

ANR4761E REPAIR STGVOL reset processinghistory failed.

Explanation: The REPAIR STGVOL command wasissued with RESET=YES. This resets the processinghistory. However, the reset of the processing historyfailed.


User response: The server is likely out of memory orresources. This command should be re-issued aftereither halting and restarting the server or after haltingthe server, rebooting the server machine, and thanrestarting the server. If the reset still fails after thesesteps, contact your IBM service representative.

ANR4762E Command: The SPACEMANAGED orARCHIVE type parameters are not validfor active data storage pool volumes.

Explanation: The QUERY CONTENT server commandhas been entered with an invalid type parameter. TheSPACEMANAGED or ARCHIVE parameters are notvalid when the volume specified belongs to anactive-data type storage pool.


User response: Reissue the command with correctTYPE parameter for active data storage pool.

ANR4763E Command: Invalid parameter - parameter.

Explanation: The specified server command has beenentered with an invalid parameter that is not applicablewhen using z/OS Media library for sequential FILEstorage.


User response: Reissue the command and enter theproper syntax. Neither NUMBEROFVOLUMES norFORMATSIZE parameter is valid when using z/OSMedia library for sequential FILE storage. The z/OS

Media server formats each FILE volume as it is beingfilled.

ANR4764E Command: Invalid length for parameterparameter - parameter value.

Explanation: The length for (parameter value) specifiedfor the (parameter) parameter in command commandexceeds the maximum allowed length.


User response: Reissue the command and specify avalid length for the parameter.

ANR4765I The key-ring file password was set.Restart the server to use the newpassword.

Explanation: The password that is used by the serverfor the key-ring file was set to a value that wasspecified in the SET SSLKEYRINGPW command. Thisis typically done after the key-ring file's password ischanged using an external utility.


User response: Restart the server to use the newkey-ring file password.

ANR4766E The server could not access the key-ringfile using the password specified in theSET SSLKEYRINGPW command.

Explanation: The password used by the server for thekey-ring file was checked for validity but was notvalid.

System action: None

User response: The QUERY SSLKEYRINGPWcommand will show you the key-ring file passwordthat the server is currently using. If the password waschanged with an external utility, ensure that thepassword is the same as that which was specified inthe SET SSLKEYRINGPW command. If the passwordwas lost, issue the DELETE KEYRING command todelete the current key-ring file. When you restart theserver it will generate a new key-ring file, password,and self-signed certificate. Issue the QUERYSSLKEYRINGPW command to obtain the newpassword. Then use an external utility to importadditional certificates again and designate one as thenew default. Restart the server to use the additionalcertificates.

ANR4767E The server was unable to change thekey-ring file password using the newpassword specified on the SETSSLKEYRINGPW command along withthe old password that the server hasstored.



Explanation: The previous key-ring file passwordremains in effect.

System action: None

User response: The QUERY SSLKEYRINGPWcommand will display the key-ring file password thatthe server is currently using. If the SETSSLKEYRINGPW password UPDATE=YES command isunable to update the key-ring file password, thekey-ring file and it's password can be deleted andre-created by: 1. Issuing the DELETE KEYRINGcommand to delete the server's record of the key-ringfile and password. 2. Stopping the server. 3. Deletingfiles cert.* in the server's instance directory. 4.Restarting the server so that the key-ring file and it'spassword are regenerated by the server.

ANR4768E Command: Invalid volume name - volumename.

Explanation: The command indicated contains aninvalid FILE volume name for a ZOSMEDIA libraryvolume.


User response: Reissue the command with a validvolume name that does not exceed 44 valid characters.

ANR4769W Command: Alert trigger is alreadydefined for message number.

Explanation: A DEFINE ALERTTRIGGER commandhas been entered that specifies a message number thatis already defined with the server.

System action: The server skips the message numberand continues processing the command.

User response: Use the UPDATE ALERTTRIGGERcommand to update the alert trigger if needed.

ANR4770W Command:Invalid message numbermessage number.

Explanation: The message number is invalid becausethe message number is in an incorrect format or doesnot exist on the server.

System action: The server skips the specified messagenumber and continues to process the rest of thecommand.

User response: Verify that the format of the messagenumber is correct and exists on the server. Reissue thecommand specifying the correct message number.

ANR4771W Command: Administrator admin namecannot be processed because it is notregistered or is locked.

Explanation: This command cannot be processed forthe indicated administrator name. The administratorname is not registered or is locked.

System action: The indicated administrator name isnot processed. The server continues to process the otheradministrator names specified with the command.

User response: If the administrator name wasspecified incorrectly, reissue the command with thecorrect name. If the administrator name is locked,determine if it can be unlocked. Use the UNLOCKADMIN command to unlock it, and reissue thecommand specifying the administrator name.

ANR4772I Alert trigger message number defined.

Explanation: The requested alert trigger has beenadded to the server in response to the command.



ANR4773I Alert trigger message number deleted.

Explanation: The requested alert trigger has beendeleted from the server.



ANR4774I Command command processed.

Explanation: The specified command was processed.


User response: Review previous messages. Correct theproblem and reissue the command.

ANR4775W Command: Alert trigger message number isnot defined.

Explanation: The specified message number does notrefer to a defined alert trigger in the server database.

System action: The server skips the specified messagenumber and continues to process the rest of thecommand.

User response: Reissue the command specifying amessage number that is defined as an alert trigger.Issue the QUERY ALERTTRIGGER command to displaya list of defined message numbers.



ANR4776I Command: Administrator admin name formessage number is action.

Explanation: The command has performed the actionand added or deleted the administrator namesuccessfully for the specified alert trigger.



ANR4777I Command: Administrator admin name isalready defined to alert message number.

Explanation: The command specifies an administratorname already defined to the alert.

System action: The server skips the administratorname and continues processing the command.


ANR4778E Command: Alert alert identifer could notbe found.

Explanation: The specified alert was not found in theserver database.

System action: The specified alert identifier isskipped. The server continues to process the next alertidentifier that is specified in the command.

User response: Reissue the command, specifying analert identifier for an alert that has not been closed ordeleted on the server. To display a list of existing alerts,issue the QUERY ALERTSTATUS command.

ANR4779E Command: The requested update for alertid, alert identifer, is invalid. The alert isnot changed.

Explanation: The specified update request is invalidor not correct for the alert. You can change the status ofan alert from active to inactive or closed, or, frominactive to closed. If you are specifying the ASSIGNEDor RESOLVEDBY parameters the value must be aregistered administrator name that is not locked.


User response: Reissue the command specifying avalid status for the alert. Issue the QUERYALERTSTATUS command to display a list of existingalerts and status.

ANR4780I Node group node group name defined.

Explanation: A DEFINE NODEGROUP command hascreated the node group indicated.



ANR4781E Command: Invalid node group name -node group name.

Explanation: Server processing for the commandcommand fails because the node group name node groupname specified does not contain valid characters orcontains too many characters.


User response: Issue the command again and specifya node group name that conforms to the namerequirements.

ANR4782E Command: Description exceeds maximumlength of length limit characters.

Explanation: Server processing for the commandcommand fails because the description specified islonger than the length limit number of charactersallowed.


User response: Issue the command again and specifya shorter description.

ANR4783E Command: Node group node group name isnot defined.

Explanation: Server processing for the commandcommand fails because the node group name node groupname specified does not refer to a defined node groupin the server database.


User response: Issue the command again, specifying anode group name that is defined in the server database.For a list of the names of defined node groups in theserver database, issue the QUERY NODEGROUPcommand.

ANR4784I Node group node group name updated.

Explanation: In response to the UPDATENODEGROUP command, the node group node groupname has been updated in the server database.





ANR4785I Node group node group name deleted.

Explanation: In response to the DELETENODEGROUP command, the node group node groupname has been deleted from the server database.



ANR4786E Command: Node group node group namestill contains at least one node.

Explanation: Server processing for the deletecommand command fails because the node group nodegroup name specified refers to a node group that stillcontains at least one node. A node group cannot bedeleted if one or more client nodes are still assigned tothe node group.


User response: To remove remaining nodes from thenode group, issue the DELETE NODEGROUPMEMBERcommand. After all nodes are removed, issue the deletecommand again.

ANR4787I Command: number of nodes membersdefined in the node group node groupname.

Explanation: A DEFINE NODEGROUPMEMBERcommand has created the specified number of membersin the indicated node group.



ANR4788I Command: number of nodes membersdeleted from node group node groupname.

Explanation: A DELETE NODEGROUPMEMBERcommand has deleted the specified number ofmembers from the indicated node group.



ANR4789I Node node name associated to nodegroup node group name.

Explanation: This message is displayed in response tothe DEFINE NODEGROUPMEMBER command. Nodenode name is associated with the node group name nodegroup name.



ANR4790I Node node name disassociated from nodegroup node group name.

Explanation: This message is displayed in response tothe DELETE NODEGROUPMEMBER command. Nodenode name is no longer associated with the node groupname node group name.



ANR4791E Command: Node group node group name isalready defined.

Explanation: Server processing for the commandcommand fails because the node group name node groupname specified refers to a node group that is alreadydefined in the server database.


User response: Issue the command again, specifying anode group name that is not defined in the serverdatabase. For a list of the names of defined nodegroups in the server database, issue the QUERYNODEGROUP command.

ANR4792E NDMP Tape server unable to initializedue to error in LISTENing on port Port

Explanation: The server failed in attempting to listenfor session requests on the server's internal tape server.

System action: Server operation continues, but NDMPoperations may fail.

User response: Ensure that theNDMPCONTROLPORT option defaults to or is set to aport number which is available in the system. TheQUERY OPTION command can be used to determinethe port number associated with theNDMPCONTROLPORT option. If this value requireschange, the server will have to be restarted after settingthe option in the server options file.

ANR4793E NDMP Tape server is terminating due toan error in accepting a new session onPort Port

Explanation: The server failed in attempting to accepta new session on the server's internal tape server.

System action: Server operation continues, but NDMPoperations may fail.

User response: Ensure that theNDMPCONTROLPORT option defaults to or is set to aport number which is available in the system. TheQUERY OPTION command can be used to determinethe port number associated with the



IBM Spectrum Protect: Server Messages and Error Codes...Messages, err or codes, and r eturn codes ar...

Documents

Transcript of IBM Spectrum Protect: Server Messages and Error Codes...Messages, err or codes, and r eturn codes ar...