TSM Guide

IBM Spectrum Protect
Version 8.1.0
Server Messages and Error Codes
IBM
IBM Spectrum Protect
Version 8.1.0
Server Messages and Error Codes
IBM
Note:
Before you use this information and the product it supports, read the information in “Notices” on page 725.
This edition applies to version 8, release 1, modification 0 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 new
editions.
© Copyright IBM Corporation 1993, 2016.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
About this publication . . . . . . . . v Device drivers completion codes: Common
Who should read this publication . . . . . . . v codes . . . . . . . . . . . . . . . 712
Publications . . . . . . . . . . . . . . v Device drivers completion codes: Media
changers . . . . . . . . . . . . . . 713
Chapter 1. Introduction to messages . . 1 Device drivers completion codes: Tape drives 715
Descriptions of standard ASC and ASCQ codes . . 716
IBM Spectrum Protect server and client messages
ASC and ASCQ codes in the Windows Event
format . . . . . . . . . . . . . . . . 1
Log. . . . . . . . . . . . . . . . 720
Interpreting return code messages . . . . . . . 2
Example one for QUERY EVENT command . . . 3
Example two for DEFINE VOLUME command . . 3 Chapter 5. Device error codes in the
AIX system error log . . . . . . . . 721
Chapter 2. ANE messages . . . . . . . 5
ANE messages list . . . . . . . . . . . . 5 Appendix. Accessibility features for
the IBM Spectrum Protect product
Chapter 3. ANR messages . . . . . . 49 family. . . . . . . . . . . . . . . 723
ANR messages list . . . . . . . . . . . . 49
Notices . . . . . . . . . . . . . . 725
Chapter 4. Descriptions of I/O codes
in server messages . . . . . . . . . 711 Glossary . . . . . . . . . . . . . 729
Completion code and operation code values
overview . . . . . . . . . . . . . . . 712
© Copyright IBM Corp. 1993, 2016 iii

iv IBM Spectrum Protect: Server Messages and Error Codes
About this publication
IBM Spectrum Protect™ is an enterprise-wide storage management application for
the network. It provides automated storage management services to multi-vendor
workstations, personal computers, and local area network (LAN) file servers.
This publication contains explanations and suggested actions for messages issued
by the IBM Spectrum Protect server.
Who should read this publication

The target audience for this publication is system administrators who service the
IBM Spectrum Protect components. In this publication, it is assumed that you have
a working knowledge of the IBM Spectrum Protect server and client components.
Publications
The IBM Spectrum Protect product family includes IBM Spectrum Protect
Snapshot, IBM Spectrum Protect for Space Management, IBM Spectrum Protect for
Databases, and several other storage management products from IBM®.
To view IBM product documentation, see IBM Knowledge Center.
© Copyright IBM Corp. 1993, 2016 v

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 Protect
server and clients.
Messages and codes can appear on the server console, the administrative client, an
operator terminal, the administrative graphical user interface, the backup-archive
client, or the hierarchical storage managment client (HSM client).
IBM Spectrum Protect provides an activity log to help the administrator track
server activity and monitor the system. The activity log contains messages
generated by the server, and is stored in the database. The server automatically
deletes messages from the activity log after they have passed the specified
retention period. Any messages sent to the server console are stored in the activity
log. Examples of the types of messages stored in the activity log include:
v When client sessions start or end
v When migration starts or ends
v When backed up files are expired from server storage
v Any output generated from background processes
Some messages have no explanations and are not published. The client can send
statistics to the server providing information about a backup or restore. These
statistics are informational messages that can be enabled or disabled to the various
event logging receivers. These messages are not published.
Related tasks:
Using the activity log (V7.1.1)
IBM Spectrum Protect server and client messages format

IBM 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, all
messages for a component have the same prefix. Sometimes a component issues
messages 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 Meaning

S 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, 2016 1

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 in
the command line help.
The following image presents a typical IBM Spectrum Protect server message.
The callouts identify each element of the message.

Message Prefix
Message Number
Message Type*
ANR 0992 I
Server installation complete. Message Text
Explanation: The server installation procedure

has completed successfully. The server is now Explanation
available for normal operation.
System Action: Server completes installation System Action

processing.
User Response: None. User Response
* I = Information
E = Error
S = Severe Error
W = Warning
K = Kernel message that originates from the
hierarchical storage management (HSM) client
Message variables in the message text appear in italics.
Interpreting return code messages

Many different commands can generate the same return code. The following
examples are illustrations of two different commands issued that result in the same
return code; therefore, you must read the descriptive message for the command.
In these examples, two different commands yield the same return code, but they
also return descriptive messages that are unique to each command. The two
commands are q event standard dddd and def vol cstg05 primary. Both yield a
generic 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 are
client events logged to the server.
ANE messages list

Messages are listed in ascending numerical order. All elements of the message are
documented.
For a list of new, changed, and deleted server messages, see the following files in
the server installation directory:
Release_msg_chgs
This file contains all new, changed, and deleted messages from the
previous server version to the current version.
Maint_msg_chgs
This file contains all new, changed, and deleted messages from the current
server version to the current release.
These files are in the installation_directory\doc directory for Windows

operating systems and the installation_directory/server/bin/ directory for all
other operating systems.
These files are also available in New, changed, and deleted server messages on the
IBM Spectrum Protect wiki.
System action: IBM Spectrum Protect processing

ANE4000E Error processing 'filespace-name': file
stops.
space does not exist.
User response: Try the operation again. If the problem
Explanation: The specified file space (domain) is
recurs, check the error log for any other messages that
incorrect or does not exist on the workstation. If the
might indicate a reason for the failure. Try to correct
message results from the BACKUP IMAGE command
any indicated problems, then try the operation again. If
with the -MODE=INCREMENTAL option, it means that
the problem persists, contact IBM technical support for
you have entered the name of a raw logical volume.
further assistance.
The MODE=INCREMENTAL option is not valid for
raw logical volumes.
ANE4002E Error processing 'filespace-name': volume
System action: Processing stops.
label does not exist
User response: Try the operation again, specifying an
Explanation: The selected drive does not have a label.
existing domain (drive letter or file system name). If
the message resulted from improper use of the System action: IBM Spectrum Protect is unable to do
MODE=INCREMENTAL option, try the command the requested operation without a drive or label
again, omitting that option. entered.
User response: If the drive is a floppy drive, place a
ANE4001E The file space for domain 'filespace-name' disk with a volume label in it and retry the operation.
could not be found on the IBM If the disk is a hard drive, ensure the drive has a
Spectrum Protect server. volume label, and retry the operation.
Explanation: The specified file space was expected to
be found on the server, but it no longer exists. It is ANE4003E Error processing 'filespace-name':
possible that a command was issued to delete the file duplicate volume label encountered
space from the server while the current operation was
in progress. Explanation: The selected drive has a duplicate
volume label. Because IBM Spectrum Protect uses the

ANE4004E • ANE4011E
volume label to keep track of backup/archive Exclude option to exclude the directory from the
information, it cannot back up or archive files from a operation.
drive with a duplicate volume label.
System action: IBM Spectrum Protect cannot select the ANE4007E Error processing 'filespace
drive. namepath-namefile-name': access to the
object is denied
User response: If the volume needs to be available to
the system, exit IBM Spectrum Protect, and assign a Explanation: Access to the specified file or directory is
volume label to the drive. Restart IBM Spectrum denied. You tried to read from or write to a file and
Protect and retry the operation. you do not have access permission for either the file or
the directory.
ANE4004E Error processing 'filespace System action: Processing stopped.
namepath-namefile-name': destination file
User response: Ensure that you specified the correct
or directory is write locked
file or directory name, correct the permissions, or
Explanation: The file or directory being restored or specify a new location.
retrieved from the server cannot be written to because
the destination is write locked. Another operation
ANE4008E Error processing 'filespace
might have the file open and will not allow it to be
namepath-namefile-name': file is
updated.
temporarily unavailable
System action: File skipped.
Explanation: File is temporarily unavailable.
User response: Either determine which operation has
the file write locked, or restore the file to another name
or location. User response: Check and see if file is locked by other
process. If not, retry the command.
namepath-namefile-name': file not found ANE4009E Error processing 'filespace
namepath-namefile-name': disk full
Explanation: The file being processed for backup,
condition
archive or migrate no longer exists on the client.
Another process deletes the file before it can be backed Explanation: No more files can be restored or
up, archived or migrated by IBM Spectrum Protect. retrieved because the destination disk is full.
System action: File skipped. System action: The client prompts you for action:
User response: None. v Retry this object
v Skip this object
ANE4006E Error processing 'filespace v Abort the action
namepath-namefile-name': directory path User response: Select the appropriate action for this
not found object. Create some free space on the destination disk
Explanation: The operating system returned a "path before you retry the operation. Another option is to
not found" status when IBM Spectrum Protect restore or retrieve the file to another disk.
attempted to access the directory. You either have
specified a directory that does not exist, as shown in ANE4010E Error processing 'filespace
the message (path-name), or the directory being namepath-namefile-name': stale NFS handle
processed no longer exists on the client because another
process deleted it before it could be backed up or Explanation: An NFS file system becomes stale.
archived by IBM Spectrum Protect.
System action: File system skipped.
System action: The directory is skipped, processing
User response: Check the NFS mounted filesystem.
continues
User response: Recheck all spelling and punctuation,
particularly the placement of directory delimiters (for
namepath-namefile-name': no file handles
example, "\"). Correct the syntax if it is incorrect, then
available
retry the operation. Ensure that the path is specified
correctly and that the directory actually exists. Retry Explanation: All file handles for your system are
the command with the corrected path and directory currently in use. No more are available.
name. If you cannot correct the directory name, use the
System action: Processing stopped.

User response: Either free some file handles by ending System action: processing stops.
other processes, or modify your system setup to allow
for more files to be open at the same time.
continues, look for other indications of system
problems to determine where the problem exists. Most
ANE4012E 'filespace namepath-namefile-name' already systems have error or event logs which may contain
exists. It will be skipped. additional information. See your system administrator
or IBM Spectrum Protect administrator for further help.
Explanation: The client tried to restore or retrieve the
specified file, but the file already existed in the target
restore location and the user chose not to replace the ANE4016E Error processing 'filespace
existing file. namepath-namefile-name': file is being
executed; write permission denied
System action: The file is skipped, a message is
logged in dsmerror.log, and restore or retrieve Explanation: The current file cannot be opened to
processing continues with the next object. write to because it is currently being run by another
operation.
User response: The file was skipped because either
REPLACE NO was in effect, causing all existing files System action: File skipped.
and directories to be skipped, or REPLACE PROMPT
User response: Stop the operation that is running the
was in effect, and when prompted, the user chose to
file and retry the operation, or restore or retrieve the
skip this file or all existing directories and files. No
file to a different name or directory.
additional action is necessary if the decision to skip the
file was deliberate. Otherwise the operation can be
retried using either REPLACE ALL REPLACE ANE4017E Error processing 'filespace
PROMPT. namepath-namefile-name': too many
symbolic links were detected while
resolving name
namepath-namefile-name': invalid file Explanation: While trying to resolve the file name, too
handle many symbolic links were found.
Explanation: An internal system error occurred. A file System action: File skipped.
operation failed because an invalid file handle was
passed. User response: Ensure that you do not have a looping
symbolic link for the file.
User response: Report the problem to your system ANE4018E Error processing 'filespace
administrator, and then retry the operation. namepath-namefile-name': file name too
long
ANE4014E Error processing 'filespace Explanation: The file name specified is too long to be
namepath-namefile-name': unknown system handled by IBM Spectrum Protect.
error (error-code) encountered. Program
ending. System action: File is skipped.
Explanation: An unrecognized and unexpected User response: See the appropriate Using the
error-code occurred within the client program. This is a Backup-Archive Client book for the particular operating
programming failure and the client program ends. system, for the file names that are handled by IBM
Spectrum Protect.
System action: processing stops.
User response: Try the operation again. If the problem ANE4019E Error processing 'filespace
continues, report the error to your IBM Spectrum namepath-namefile-name': file system is
Protect administrator. locked by system
Explanation: File system cannot be accessed because it
ANE4015E Error processing 'filespace is locked by the system.
namepath-namefile-name': unexpected IBM
Spectrum Protect error (error-code) System action: IBM Spectrum Protect cannot complete
encountered the operation.
Explanation: An unexpected error occurred. This User response: See your system administrator.
might be a low-level system or communication error
that IBM Spectrum Protect cannot handle or recover
from.
Chapter 2. ANE messages 7

ANE4020E • ANE4026W
ANE4020E The data format for object 'filespace ANE4024E Error processing 'filespace
namepath-namefile-name' is unknown. The namepath-namefile-name': file write error
unknown format usually occurs when
Explanation: An error was found while writing to the
the file was backed up or archived by a
file.
later version of IBM Spectrum Protect.
Explanation: When a file is backed up or archived,
IBM Spectrum Protect includes some additional User response: Check your system to ensure that it is
information about the file. This message is issued if operating properly.
IBM Spectrum Protect cannot recognize the information
during a restore or retrieve operation. The most likely
cause is that the file was backed up or archived with a ANE4025E Error processing 'filespace
newer version of IBM Spectrum Protect. If the file was namepath-namefile-name': file exceeds user
backed up from a case-preserving but not case-sensitive or system file limit
file system, the file name might be displayed with Explanation: A file being backed up/restored or
incorrect casing. The incorrect casing does not archived/retrieved exceeds system set limits for this
otherwise affect processing since the file is skipped. user. Shown below are the filesize limits corresponding
System action: The file is not restored or retrieved. to various platforms.
Processing continues with the next file. AIX 68,589,453,312 (64GB)
User response: Try the restore or retrieve operation HP-UX 1,099,511,627,775 (1TB-1)
again with a current version of the IBM Spectrum
Protect client software. If the problem persists, contact Linux 2,147,483,647 (2GB)
IBM technical support for further assistance. Mac pre-OS9
2,147,482,624 (2GB-1K)
ANE4021E Error processing 'filespace Mac OS9
namepath-namefile-name': file system not 18,446,744,073,709,551,616 (16EB)
ready
NetWare
Explanation: The file system/drive was not ready for 4,294,963,200 (4GB -4KB)
access.
NUMA-Q DYNIX/ptx
System action: Processing stopped. 4.5 1,095,216,660,480 (1TB-4GB)
User response: Ensure that the drive is available to OS/390 4,294,967,295 (4GB)
IBM Spectrum Protect, and then retry the operation.
SGI 18,446,744,073,709,551,615 (16EB-1)
ANE4022E Error processing 'filespace Solaris 2.6 or higher

namepath-namefile-name': file system is 1,099,511,627,775 (1TB-1)
invalid. Tru64 UNIX
Explanation: The drive was not available for access. 1,099,511,627,776 (1TB)
System action: processing stops. UnixWare

2,147,483,647 (2GB)
User response: Ensure that the drive is operational,
and then try the operation again. If this is unsuccessful, Windows ME (FAT32)
check the error log. 4,294,967,295 (4GB)
Windows NT/2000 (NTFS)
ANE4023E Error processing 'filespace 17,592,185,978,880 (16TB-64K)
namepath-namefile-name': file input/output System action: File skipped.
error
User response: Ensure that the system limits are set
Explanation: An error was found while reading from properly.
or writing to the file.
System action: File skipped. ANE4026W Error processing 'filespace
User response: Check your system to ensure that it is namepath-namefile-name': size of 'file-size'
operating properly. For OS/2, run CHKDSK /F for the exceeded the maximum file size limit on
failing drive which can be found in dsmerror.log. your system
Explanation: You tried to restore or retrieve a file that

ANE4027S • ANE4033E
has exceeded the maximum file size limitation on your

ANE4031E Error processing
system.
'file_space_namepath_namefile_name'. Name
System action: IBM Spectrum Protect cannot restore exceeds an internal IBM Spectrum
or retrieve the file. Protect limit.
User response: Restore or retrieve this file on a system Explanation: During a file operation, IBM Spectrum
that supports the file size. See your system Protect encountered a filename where at least one
administrator. component of the file name (file_space_name,
path_name or directory_name or file_name) exceeded
an internal IBM Spectrum Protect maximum. The
ANE4027S Error processing 'filespace internal IBM Spectrum Protect limits should not be
namepath-namefile-name': internal program confused with the operating system limits for
message 'value' encountered file_space_name, path_name or directory_name,
Explanation: An unexpected catastrophic program file_name.
failure occurred, indicated by value. Shown below are the IBM Spectrum Protect internal file
System action: Processing stopped. name limits for various platforms.
AIX HP-UX Solaris
User response: Retry the operation. If the problem
File_space_name 1024
continues, see your system administrator or service Path_name or directory_name 1023
representative. File_name 256
Linux
namepath-namefile-name': cannot create Path_name or directory_name 768
file/directory entry File_name 256
Explanation: The directory path for files being
Windows XP/2000/2003
restored or retrieved cannot be created.
System action: File skipped. Path_name or directory_name 248
File_name 248
User response: Ensure that you have the proper
authorization to create the directory for file being System action: The file is skipped.
restored or retrieved. User response: Reduce the size of the filename so that
it is smaller that theIBM Spectrum Protect internal
ANE4029E Error processing 'filespace limits.
namepath-namefile-name': unable to build
a directory path; a file exists with the ANE4032E Error processing 'filespace
same name as a directory namepath-namefile-name': file is not
Explanation: IBM Spectrum Protect tried to create a compressed.
directory path, but is unable to because a file exists that Explanation: A file that was flagged as compressed
has the same name as a directory. was not compressed, and the system failed.
System action: Processing stopped. System action: Processing stopped.
User response: Remove the file that has the same User response: See your system administrator to
name as the directory. Refer to the last restore/retrieve report this problem. This error is a system failure.
operation and check all directories along the path.

ANE4030E Error processing 'filespace namepath-namefile-name': file compressed
namepath-namefile-name': disk space limit on a different client machine that has
for this process reached more memory
Explanation: The disk space allocated for the client Explanation: You are trying to restore a file that was
owner is full. backed up and compressed on another client
System action: Processing stopped. workstation that had more memory than your client
workstation. You cannot restore this file. When the file
User response: Free up disk space and retry the is restored, it is expanded and your workstation does
restore or retrieve operation. not have enough memory.
System action: IBM Spectrum Protect canceled the
operation.

User response: Obtain a machine with more memory

ANE4038E An error occurred processing file system
and retry the operation.
'filespace name'.
Explanation: The file system is corrupted or contains
one or more corrupted directories and cannot be
namepath-namefile-name': unknown system
processed.
error
System action: File system is skipped.
Explanation: An unknown error occurred. This might
be a low-level system or communication error that IBM User response: Check your system to ensure that it is
Spectrum Protect cannot handle or recover from. operating properly. For the Windows environment, run
CHKDSK utility for the failing drive. More information
about corrupted directories can be found in
User response: Retry the operation. If the problem dsmerror.log.
continues, determine where the problem exists. See
your system administrator for further help.
namepath-namefile-name': compressed file
ANE4035W File 'filespace namepath-namefile-name' is corrupted and cannot be expanded.
currently unavailable on server.
Explanation: The compressed file cannot be expanded
Explanation: You tried to restore or retrieve a file that correctly due to one of the following reasons:
is currently not available from the IBM Spectrum There is a problem on the tape.
Protect server.
There is a communications problem.
System action: IBM Spectrum Protect Cannot restore The compressed file was corrupted on the TSM
or retrieve the file. Server.
User response: Try to restore or retrieve after the file System action: File skipped.
was made available on the server. See your system
administrator. User response: 1) The compressed file is corrupted
because there is a problem on the tape. To know if this
is the problem, please issue the following command on
ANE4036E An error occurred saving the registry the TSM Server: audit volume <volume_name> fix=no
key. If there is any problem reported, you could move the
Explanation: The active registry key cannot be copied data from that volume to a new one (see command
to the ADSM.SYS staging directory. MOVE DATA) and try again the restore. 2) There are
communications problems between the TSM Server and
System action: Registry backup operation terminates. the TSM Client and the results is that the file is
corrupted during the transmission. If you use a gigabit
User response: Check the space available on the
ethernet adapter on the Server please upgrade the card
Windows boot partition to ensure there enough space
driver (AIX platform) or add provided by SUN
to contain a copy of the Windows registry. This might
suggested changes to some system network options
require several megabytes of free space. Also check the
which have resolved this problem (SUN platform). 3)
Windows permissions on the ADSM.SYS staging
Please verify with your network support if during the
directory and ensure that the Windows user under
restore there are no any problems between the TSM
which you are running IBM Spectrum Protect has full
Client/Server that is originating the file corruption.
access to that directory and its contents.

ANE4037E Object 'file-namefile-namefile-name'
namepath-namefile-name': file system
changed during processing. Object
filespace name has exceeded its space
skipped.
management quota.
Explanation: The specified file-name was skipped
Explanation: IBM Spectrum Protect detects that the
during backup, archive, or migrate because it was
file system has exceeded its quota. No more data can
changing during the attempt to process it.
be migrated out of this file system.
System action: IBM Spectrum Protect skipped the
System action: IBM Spectrum Protect will not migrate
object.
files from this file system.
User response: If you want the file backed up,
User response: Recall some files, or ask the system
archived, or migrated, retry the operation. If it fails,
administrator to increase the quota for this file system.
determine why the object is being changed. For more
information on backing up, archiving, or migrating
changing objects, see your system administrator.

ANE4041W • ANE4048W
differ only in case on this platform and cannot

ANE4041W Error processing 'filespace
guarantee the integrity of the file, so the directory and
namepath-namefile-name': Out of free space
all of the objects contained within it are skipped.
or inodes in file system to migrate or
recall. System action: This object will be skipped.
Explanation: The file system is full. No more free User response: Rename the file in question to a
space or free inodes are available to be allocated for the unique name.
transaction file that is needed when a file is being
migrated or recalled.
ANE4046E There is an error processing
System action: IBM Spectrum Protect terminates the 'filespace-namepath-namefile-name': the
current operation for this file system. object is corrupted and unreadable.
User response: Remove some files in the file system, Explanation: You tried to read from or write to a file
and then run reconciliation. Retry the operation. or directory that is corrupted. The corrupted file is
skipped. If this is a directory, the objects contained in
the directory and its subdirectories are skipped.
ANE4042E Object name 'filespace
namepath-namefile-name' contains one or System action: This object will be skipped.
more unrecognized characters and is not
valid. User response: Check your system to ensure that the
filespace is not corrupted by using system tools like
Explanation: The file name, directory name, or chkdsk (Windows) or fsck (UNIX).
volume label syntax is incorrect.
System action: The file is skipped. ANE4047E There is a read error on
'file-namefile-namefile-name'. The file is
User response: Check the disk for errors.
skipped.
Explanation: The specified file-name was skipped
ANE4043I Total number of objects recalled: Number
during backup archive because the file could not be
of objects
read.
Explanation: This message reports statistics or
If you are performing a JFS2 snapshot based operation,
information for a client operation performed to this
it is possible that the snapshot was not large enough to
server. This is logged for informational purposes.
contain all the changes made to the filesystem after the
System action: Processing continues. snapshot was created. This could cause the snapshot to
become invalid thereby preventing IBM Spectrum
User response: None required.
Protect client from reading the snapshot.
System action: IBM Spectrum Protect skipped the file.
ANE4044E Error processing 'filespace-namepath-
namefile-name': Case-sensitive name User response: Check your system to ensure that it is
conflict exists. operating properly.
Explanation: While processing the specified file on the If you are performing a JFS2 snapshot based operation,
workstation, another file name was encountered with a please use the default snapshotcachesize of 100% and
similar name which only differed in case. The ensure that the volume group has sufficient disk space
Backup-Archive client does not allow names which to allocate snapshots at least as large as the file system
differ only in case on this platform and cannot and retry the operation.
guarantee the integrity of the file, so the file is skipped.
System action: This object will be skipped. ANE4048W LAN-Free connection failed.
User response: Rename the file in question to a Explanation: ENABLELANFREE option is set to YES
unique name. for this session, but an attempt to establish LAN-Free
connection failed.
ANE4045E Error processing 'filespace-namepath- System action: The IBM Spectrum Protect client will
namefile-name': Case-sensitive name failover to non LAN-Free support.
conflict exists. The directory tree will be
User response: Review the IBM Spectrum Protect
skipped.
error.log for LAN-Free failures. Check your LAN-Free
Explanation: While processing the specified file on the setup and verify that all components are working
workstation, another object name was encountered with properly.
a similar name which only differed in case. The
Backup-Archive client does not allow names which

ANE4049I • ANE4054E
ANE4049I Established LAN-Free connection. ANE4052E Error processing 'filespace

namepath-namefile-name':
Explanation: ENABLELANFREE option is set to YES
Encrypted-file-system (EFS) file cannot
for this session and the IBM Spectrum Protect client
be restored, because file system does
successfully established LAN-Free connection with
not support restore from the raw-EFS
server, after the LAN-Free connection was broken.
back-up data, or possibly because the
System action: The IBM Spectrum Protect client will restore function does not have write
communicate with the server via LAN-Free. access to the directory.
User response: Review the IBM Spectrum Protect Explanation: The file being processed is encrypted by
error.log for LAN-Free errors. Check your LAN-Free an encrypted file system (EFS). The file was backed up
setup and verify that all components are working in the raw encrypted format. Either the target
properly. filesystem does not support the encrypted format, or
restore does not have write access to the directory to
which the file is to be restored.
ANE4050W Scheduled action 'schedule-action' did not
execute for schedule 'schedule-name' as System action: The restore is terminated.
the IBM Spectrum Protect administrator
User response:
has been disabled from executing the
scheduled action on the client. v The file cannot be restored to this location if the file
system is not the AIX Enhanced Journaled File
Explanation: One or more of the client options - System (JFS2)
schedcmddisabled, srvprepostscheddisabled,
v If the file is JFS2 but EFS is not enabled, then EFS
srvprepostsnapdisabled, restretrscheddisabled, have
must be enabled before the file can be restored
been set to YES on the client thereby preventing the
IBM Spectrum Protect administrator from executing one v If the user ID under which restore is being run does
of the following scheduled actions on the client - not have write permission for the directory, the
preschedule, postschedule, presnapshot, postsnapshot permissions must be changed or the restore must be
or scheduled operating system commands, restore or run under a different user ID
retrieve operations.
System action: The scheduled operation will not be ANE4053E Error processing 'filespace path filename':
executed and a message will be logged to IBM The file cannot be restored because the
Spectrum Protect Server indicating this. file system or operating system does not
support the Encrypting File System
User response: None required. (EFS) data.
Explanation: The specified object was backed-up as
ANE4051E Error processing 'filespace raw Encrypting File System (EFS) data. The client is
namepath-namefile-name': The decryption trying to restore or retrieve the object to a destination
option is in effect, but the user ID that does not support the EFS data. The location might
under which back-up or archive is being not support the EFS data for one of the following
run is not authorized to decrypt this reasons:
encrypted-file-system (EFS) file.
v The operating system does not provide the support,
Explanation: The file being processed is encrypted by or is a release that does not include the support
an encrypted file system (EFS). The option is specified v EFS support has not been activated on the operating
to back-up or archive the file in decrypted form. The system
user ID under which the back-up or archive is being
v The target file system does not support the EFS data
run does not have decryption rights for this file.
System action: The object is not restored or retrieved.
System action: The file is skipped.
Processing continues with the next object.
User response: There are three possible ways to make
User response: If this file must be restored, restore it
decryption work:
to an AIX operating system environment supporting
v Re-encrypt the file under the encryption key of a EFS data.
group to which both the owner and the
back-up/archive user IDs belong
v Add the back-up/archive user ID to the list of users
namepath-namefile-name': The encryption
authorized to decrypt this file
key is not loaded.
v Run the back-up or archive under the owner's user
ID, if possible Explanation: The file being processed is encrypted by
an encrypted file system (EFS). The option is specified
to backup or archive the file in decrypted form. The

ANE4055E • ANE4059I
encryption key, required to decrypt the file, is not v IBM Spectrum Protect client version 6.2 or higher is
loaded in the kernel keyring. attempting to perform an operation that causes the
IBM Spectrum Protect server to return information
System action: The file is skipped.
about this object to the client. Note: During
User response: There are three situations in which this incremental backup, the server returns information to
problem can occur: the client about active backup versions which is used
v You just performed initial activation of EFS on the to determine which files have changed.
AIX system, and have not logged out. AIX does load
the keys for the session running at the time of initial Beginning with IBM Spectrum Protect server version
activation. Solution: Logout and login again. 6.1, the maximum high level name length was reduced
from 8192 characters to 6000 characters. Objects with
v The login password has been changed recently, and
high level names that exceed 6000 characters are not
you normally run with the EFS password the same
supported for backup or archive. Beginning with IBM
as the login password. AIX does not automatically
Spectrum Protect backup-archive client version 6.2, the
change the EFS password when you change the login
maximum high level name length was similarly
password. Solution: Issue 'efskeymgr -n' to set the
reduced.
EFS password to be the same as the login password.
v You need to run the decrypting backup when the System action: The file or directory specified in the
EFS password is different from the login password. message is skipped. Processing will continue with the
Solution: Issue 'efskeymgr -o ksh' to launch a new next object.
shell with the keys loaded. AIX will prompt you for User response: Contact your IBM Spectrum Protect
the EFS password as you launch the shell. Run the server administrator for further assistance.
backup from the new shell.
ANE4057I The secondary server is configured as

ANE4055E Cannot update file space 'filespace-name': read-only. The file-space-name; configured
the file space version on the IBM access is read only and the request
Spectrum Protect server is not requires read write access.
compatible with this client
Explanation: The file space on the IBM Spectrum information for a client operation performed to this
Protect server is not compatible with this client. This is server. This is logged for informational purposes.
caused by performing a backup or archive operation
with a client and then using a down-level client and System action: Processing continues.
attempting a backup or archive operation targeting the User response: None required.
same file space.
This problem occurs specifically after a Windows or
AIX client V6.1 or higher performs a backup or archive ANE4058I A write failure occurred while
operation and then a subsequent backup or archive attempting to save node replication
operation is attempted with a client V5.5 or lower. failover values to the options file.
System action: Processing stops. Explanation: A write failure is often a result of

insufficient access permissions to the options file, but
User response: Use the correct level of the client. could also be caused by the lack of available disk
space. The replication server connection information
ANE4056E Object 'object-name' returned by the IBM can not be saved and failover will not be possible.
Spectrum Protect server has a high-level System action: The operation failed.
name that exceeds the maximum length
of 6000 characters. The file or directory User response: Check the local disk for possible
cannot be processed. causes of the write error, and check to see that
sufficient access to the options file is configured.
Explanation: The IBM Spectrum Protect server
returned information about a backup or archive version
with a high level name that exceeds 6000 characters. ANE4059I The option USEREPLICATIONFailover
The high-level name is the directory path that contains is set. The node will not attempt a fail
the object (file or directory). over to the secondary server
This message is displayed when all of the following Explanation: This option will prevent the node from
conditions are true: connecting to the replication server in the event of a
v The object was backed up or archived by a version failure of the primary server.
6.1 or lower IBM Spectrum Protect client. System action: The configuration set by the IBM
v The object was backed up or archived to a version Spectrum Protect administrator will be saved to the
5.5 or lower IBM Spectrum Protect server. options file. The client will fail to connect to the

primary server and processing stops.

ANE4064I Restoring vCloud Director vApp 'vapp
User response: No response is required. name' from Organization VDC 'org vdc
name' from organization 'org name'
Target vApp name is 'restored vapp name'
ANE4060I Session established in failover mode to Restore VAPP command started. Total
secondary server number of vApps to process: vapps num
Explanation: This message reports statistics or to restore
information for a client operation performed to this Explanation: The restore vApp operation completed.
System action: This message is for informational
System action: Processing continues. purposes only.
User response: None required. User response: No action is required.
ANE4061I Connected to secondary server secondary ANE4065E Proxy rejected: data mover node 'dm
server; in fail over mode. Home server is: node' has not been granted proxy
home server; authority for target node 'target_node',
Explanation: The node is configured for replication associated with Organization vDC
and has successfully connected to the secondary server. 'OVDC name' of Organization 'Org Name'.
This message is to notify the server administrator that a Explanation: The operation requires that a proxy
node has connected to the secondary server in fail over access for the data center node is granted to the data
mode. mover node.
System action: Processing continues. System action: Operation is canceled for the specified
User response: None. vApp.
User response: Run configuration wizard or
ANE4062I The secondary server access is not configuration editor to configure proper nodes
configured. Unconfigured access for file relashionship.
space file-space-name;.
Explanation: This message reports statistics or ANE4076I Backing up hypervisor Virtual Machine
information for a client operation performed to this 'vmname' for the first time.
server. This is logged for informational purposes. target node name: 'target_node_name'
data mover node name:
System action: Processing continues. 'data_mover_node_name'
User response: None required. Explanation: This message reports statistics or
ANE4063W IBM Spectrum Protect application server. This is logged for informational purposes.
protection did not copy the System action: Processing continues.
SqlServerWriter.xml and/or
SQLDBINFO.XML files from VM 'VM'. User response: None required.
Individual SQL Database restore from
this backup is not supported. ANE4077E File 'filespace namepath-namefile-name' is
Explanation: The SqlServerWriter.xml and/or encrypted by Microsoft EFS and
sqldbinfo.xml files were not found on the guest contains at least one sparse data stream.
machine. The operating system does not support
restore for this file so it is not backed
System action: The operation completes. However, the up or restored.
SqlServerWriter.xml or sqldbinfo.xml files were not
copied. Explanation: An error in the Microsoft Windows API
prevents successful restore of files that meet the
User response: Make sure that the 'SQL Server VSS following conditions:
Writer' and the 'SQL Server' services are running on
v The file is encrypted by Microsoft Encrypting File
this guest machine. Then try the operation again.
System (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 Microsoft
Windows Server 2003 R2

Because the file cannot be restored, IBM Spectrum

ANE4085I Assigned 'number' objects from previous
Protect does not back it up. The problem is
systemstate backup to the new
documented by Microsoft at http://
systemstate backup.
support.microsoft.com/kb/2525290.
Explanation: Objects in the previous System State
System action: The file is not backed up or restored.
backup have not changed and were assigned to the
Processing continues with the next object or ends if
new System State backup.
there are no further objects.
System action: Processing continues.
User response: If this message is issued during a
backup operation, you can do the following: User response: None.
v Disable EFS encryption for the file so that it can be
backed up. ANE4086W Failed to assign unchanged objects from
v If a backup copy of the file is not necessary, you can previous systemstate backup to the new
exclude it from backup. systemstate backup. Objects will be
backed up.
ANE4081E Error processing 'filespace-name': file Explanation: Objects in the previous System State
space type is not supported. backup have not changed and should be assigned to
the new systemstate backup. Due to error assign
Explanation: The specified file space type is not
operation failed and objects will be backed up.
currently supported by IBM Spectrum Protect on this
platform. System action: Processing continues.
System action: The unsupported file system is User response: Retry the operation. If the problem
skipped. Processing continues with the next file system. persists, contact IBM Spectrum Protect technical
support.
User response: Refer to the documentation for
information on what file space types are supported.
ANE4087E An attempt to load data for the wizard
failed.
ANE4082I Node password has been reset to the
For more information, please see the log
administrative id password.
file.
Explanation: The client logged in using administrative
Explanation: An attempt to load data for the wizard
id rather than node name. The node password has been
failed as the remote agent is probably unavailable.
reset to be in sync with the administrative password.
User response: Check the log for reason for the
User response: None.
failure.
ANE4083I New node password has been

ANE4088I Error
generated.
Explanation: The client logged in using administrative
id rather than node name. New random node password
has been generated and recorded.
ANE4089W File server file-server-name has been

ANE4084E Error processing 'filespace-namepath-
upgraded to Data ONTAP version
namefile-name': cannot get file status.
'version.modifcation.submodification'.
Explanation: While processing the file, the lstat() call Perform a full incremental backup by
set EOVERFLOW error code. specifying option
createnewbase=migrate as soon as
System action: This file will be skipped. possible.
User response: The file is skipped. Processing Explanation: The file server has been upgraded to a
continues with the next file. version that supports unicode file names for
incremental backup using snapshot difference. Perform
a full incremental in order to backup any files with
unicode names that may have been skipped by the

ANE4090I • ANE4104I
previous version of the IBM Spectrum Protect client. then these files cannot be backed up. Therefore it is not
possible to back up the system state.
System action: Systemstate backup stops.
User response: Perform a full incremental by
specifying the command line option User response: Try the operation again. If the problem
createnewbase=migrate with the snapdiff option as persists, obtain a service trace that captures the
soon as possible. problem and contact IBM technical support for
additional assistance. Your IBM Spectrum Protect
administrator can help you configure the trace.
ANE4090I File server file-server-name has been
upgraded to Data ONTAP version
'version.modifcation.submodification'. ANE4100I Objects Scanned : Number of objects
Perform a full incremental backup by
specifying option
createnewbase=migrate as soon as
possible.
Explanation: The file server has been upgraded to a
version that supports unicode file names for User response: None required.
incremental backup using snapshot difference. Perform
a full incremental in order to backup any files with
unicode names that may have been skipped by the ANE4101I Files : Number of files New : Number of
previous version of the IBM Spectrum Protect client. new files
System action: Processing continues. Explanation: This message reports statistics or

User response: Perform a full incremental backup by server. This is logged for informational purposes.
specifying the command line option
createnewbase=migrate with the snapdiff option as System action: Processing continues.
soon as possible. User response: None required.
ANE4091I Starting Full VM Incremental backup of ANE4102I Directories : Number of directories New :
Virtual Machine 'vmname' Number of new directories
Explanation: This message reports statistics or Explanation: This message reports statistics or
information for a client operation performed to this information for a client operation performed to this
server. This is logged for informational purposes. server. This is logged for informational purposes.
System action: Processing continues. System action: Processing continues.
User response: None required. User response: None required.
ANE4092E Data mover platform is not supported ANE4103I Entries Entered : Number of entries
for instant access/restore operations.
Explanation: The instant access/restore operation information for a client operation performed to this
failed. server. This is logged for informational purposes.
System action: The instant access/restore operation System action: Processing continues.
failed. The reason for the failure is unsupported
platform. User response: None required.
User response: The instant access/restore operation

should be performed from a supported data mover ANE4104I Resident Objects : Number of objects New
platform. : Number of new objects
ANE4099E The system volume cannot be information for a client operation performed to this
identified. Therefore the system state server. This is logged for informational purposes.
cannot be backed up. System action: Processing continues.
Explanation: The system volume contains the User response: None required.
hardware-specific system state files that are needed to
start Windows, such as Ntldr, Boot.ini, Ntdetect.com or
Bootmgr. If the system volume cannot be identified,

ANE4105I Premigrated Objects : Number of objects ANE4111I Searching for largest or oldest
New : Number of new objects candidates (level2)
ANE4106I Migrated Objects : Number of objects New ANE4112I Searching for remaining candidates
: Number of new objects (level3)
ANE4107I Candidates : Number of migration ANE4113I Waiting for dsmautomig

candidates Migrated : Number of migrated
objects Premigrated : Number of
premigrated objects
server. This is logged for informational purposes. User response: None required.
ANE4114I Waiting for a new scan
ANE4108I Objects Removed : Number of objects
ANE4115I Creating pool file
ANE4109I Searching for premigrated candidates
ANE4116I Search finished
ANE4110I Searching for largest and oldest
candidates (level1)
information for a client operation performed to this User response: None required.

ANE4117I Current search state : ANE4123I Total candidates found : Number of objects
ANE4118I Objects scanned in hash : Number of ANE4124I NO INFORMATION AVAILABLE

objects
Explanation: This message reports statistics or information for a client operation performed to this
information for a client operation performed to this server. This is logged for informational purposes.
ANE4125I Search is currently running. Running
ANE4119I Premigrated candidates : Number of since Number of seconds seconds
objects
ANE4126I Scan is currently running. Running
ANE4120I Level 1 candidates : Number of objects since Number of seconds seconds
ANE4121I Level 2 candidates : Number of objects ANE4127I Currently scanning Number of objects
objects per second
information for a client operation performed to this Explanation: This message reports statistics or
server. This is logged for informational purposes. information for a client operation performed to this
ANE4122I Level 3 candidates : Number of objects
ANE4128I Scan complete

ANE4129I Scan time was Number of seconds seconds ANE4135I Querying all_local drives for VM
'vmname'
ANE4130I Scanned Number of objects objects per
second ANE4136I Searching for VM 'vmname' volumes for
backup at location:
volname
server. This is logged for informational purposes. Explanation: This message reports statistics or
ANE4131I ------------------------ Currently Searching:
-----------------------------
namepath-namefile-name': exceeded
maximum number of links allowed
Explanation: Link cannot be restored or retrieved
because the destination file system has exceeded
User response: None required. maximum number of links allowed.
System action: The client prompts you for action:
ANE4132I Backup of Virtual Machine 'vmname' v Skip this object
started
v Abort the action
User response: Select the appropriate action for this
object. Restore or retrieve the link to another file
system.
User response: None required. ANE4138I Filespace Query for Virtual Machine
'vmname'
ANE4133I Mount virtual machine disk on backup Explanation: This message reports statistics or
proxy for VM 'vmname' information for a client operation performed to this
information for a client operation performed to this System action: Processing continues.
User response: None required. ANE4139I Successful incremental backup of
Virtual Machine 'vmname'
ANE4134I Incremental backup of Virtual Machine Explanation: This message reports statistics or
'vmname' information for a client operation performed to this
information for a client operation performed to this System action: Processing continues.

ANE4140I Backup VM command complete ANE4146I Starting Full VM backup of Virtual

Machine 'vmname'
ANE4141I Total number of virtual machines
backed up successfully: num ANE4147I Successful Full VM backup of Virtual
Machine 'vmname'
ANE4142I virtual machine vmname backed up to
nodename nodename ANE4148E Full VM backup of Virtual Machine
'vmname' failed with RC rc
information for a client operation performed to this Explanation: The Full VM backup of virtual machine
server. This is logged for informational purposes. failed.
System action: Processing continues. System action: The full backup of the virtual machine
finished with failures. The next virtual machine in the
vmlist will be processed. The reason for the failure is
written to the local client error log.
ANE4143I Total number of virtual machines failed:
User response: Check the local client error log for
num
reason for the failure.
ANE4149I Total number of virtual machines
processed: num
User response: None required. information for a client operation performed to this
ANE4144I virtual machine vmname System action: Processing continues.
Explanation: This message reports statistics or User response: None required.

ANE4150E Incremental backup of Virtual Machine
System action: Processing continues. 'vmname' failed with RC rc
User response: None required. Explanation: The incremental backup of virtual
machine volumes failed.
ANE4145I Backup VM command started. Total System action: The backup of the virtual machine
number of virtual machines to process: finished with failures. The next virtual machine in the
num vmlist will be processed. The reason for the failure is
information for a client operation performed to this User response: Check the local client error log for
server. This is logged for informational purposes. reason for the failure.



ANE4151E Failure mounting Virtual Machine
'vmname'. RC=rc
Explanation: The VMware failed to mount virtual
ANE4156E File level VM backup of virtual machine
machine disk.
'vmname' not supported.
System action: The backup of the virtual machine can File level VM backup not support on
not continue. The next virtual machine in the vmlist non Windows platform guest OS.
will be processed. Refer to dsmerror.log for detailed Platform type: 'platform'.
error message for the reason for the failure.
Explanation: The backup of virtual machine failed.
User response: Refer to dsmerror.log for detailed error
System action: The backup of the virtual machine
message.
ANE4152E Failure initializing VMware virtual written to the local client error log.
machine environment. RC=rc. Refer to
User response: Back up the virtual machine using the
IBM Spectrum Protect error log for
VMBACKUPType=FULLvm option.
detailed error messages.
Explanation: Failure initializing VMware virtual
ANE4157I backuptype BACKUP VM of virtual
machine environment. Refer to IBM Spectrum Protect
machines specified in option option.
error log for detailed error messages.
System action: The backup can not continue.
User response: Refer to IBM Spectrum Protect error server. This is logged for informational purposes.
log for detailed messages.
ANE4153E Hostname could not be found for
ANE4158I backuptype BACKUP VM of virtual
machines 'option'.
reason for the failure. User response: None required.
ANE4154E Possible cause Virtual Machine is not ANE4159E Backup of Virtual Machine 'vmname'
running and does not have a static IP failed. rc=rc.
address.
System action: The backup of the virtual machine finished with failures. The next virtual machine in the
finished with failures. The next virtual machine in the vmlist will be processed. The reason for the failure is
vmlist will be processed. The reason for the failure is written to the local client error log.
User response: Check the local client error log for reason for the failure.
ANE4160E Proxy Rejected: Proxy authority has not
ANE4155E Virtual Machine 'vmname' could not be been granted to Agent Node: 'agent_node'
found on VMware server. for Target Node: 'target_node'.
Explanation: The backup of virtual machine failed. Explanation: The backup of virtual machine failed.
System action: The backup of the virtual machine System action: The backup of the virtual machine
finished with failures. The next virtual machine in the finished with failures. The next virtual machine in the
vmlist will be processed. The reason for the failure is vmlist will be processed. The reason for the failure is
written to the local client error log. the node has not been granted proxy authority to
access the node named by the backup proxy node. The

IBM Spectrum Protect administrator must first grant System action: Backup continues, and data is not
proxy authority. compressed.
User response: The IBM Spectrum Protect server User response: If you intend to compress virtual
administrator must grant proxy authority for this node. machine CTL and Data files, then update your Tivoli
See the administrator command "Grant Proxynode". Storage Manager configuration so that both types of
files are directed to storage pools that are enabled for
client-side deduplication. If you intend to compress
ANE4161E Duplicate virtual machine name
virtual machine Data files but not CTL files, then
'vmname' was detected in the same
update your Tivoli Storage Manager configuration so
backup operation. Backup of virtual
that the Data files are directed to a storage pool that is
machine 'vmfullname' can not continue
enabled for client-side deduplication. Set the
without a unique object name.
VMSKIPCTLCOMPRESSION to YES in your client
Explanation: The backup of virtual machine failed. options file. If you do not intend to use compression,
then set COMPRESSION NO in your client options file.
vmlist will be processed. The reason for the failure is ANE4165E Creating a Virtual Machine, but the
written to the local client error log. hostname 'virtual-machine-name' was not
found.
User response: Choose a unique name for the virtual
machine. Explanation: The Virtual Machine being creating must
have a valid hostname to be created.
ANE4162E The virtual machine System action: Check the virtual machine hostname
'virtual-machine-name' has not been specified for correctness.
previously backed up.
User response: Correct the virtual machine hostname
Explanation: The specified virtual machine has not specified and retry the restore.
been previously backed up, so can not be specified for
restore.
ANE4166E Creating a Virtual Machine, but the
System action: The specified virtual machine is datacenter 'virtual-machine-name' was not
skipped, and the next virtual machine in the restore list found. The name may be incorrect or
is processed. may be located in a VMware folder and
require the folder name such as
User response: Verify the virtual machine name to be vmfolder/dcname.
restored, and re-try the operation.
Explanation: The Virtual Machine being created must
have a valid datacenter to be created.
ANE4163I Encryption is currently enabled, but the
virtual machine backup for System action: Processing stops.
'virtual-machine-name' will not be
User response: Check the virtual machine datacenter
encrypted.
specified for correctness. If the datacenter is contained
Explanation: Virtual Machine files are not encrypted in a folder then the full datacenter name, complete with
when backed up to the TSM server. the folder path, must be specified, such as
vmfolder/dcname.
System action: The virtual machine files are not
encrypted during the backup processing.
ANE4167E Creating a Virtual Machine, but the
User response: No user action is necessary. datastore 'virtual-machine-name' was not
found.
ANE4164W Compression is currently enabled, but Explanation: The Virtual Machine being creating must
the virtual machine backup for have a valid datastore to be created.
'virtual-machine-name' is not compressed
because client-side deduplication is not System action: Check the virtual machine datastore
being used. specified for correctness.
Explanation: Compression can only be used with User response: Correct the virtual machine datastore
virtual machine CTL and Data files when the files are specified and retry the restore.
stored in a storage pool that is enabled for client-side
deduplication. This message is issued when the client is
configured for compression and virtual machine CTL or
Data files are directed to a storage pool that is not
enabled for client-side deduplication.

ANE4168E VMware has reported an error via their ANE4171E Backup of virtual machine 'vmname'
SOAP interface. On the Detailed Status failed. VM could not be contacted
Report panel, view the last error because of 'vmfullname' connection state.
message reported. Also check the error
log for more information about the
problem that occurred. System action: The backup of the virtual machine
finished with failures. The next virtual machine in list
Explanation: The command to VMware failed to
will be processed.
complete. The error returned is displayed on the
Restore or Backup summary panel under the Last Error User response: Correct the connection state from
Message section. VMware vCenter and assign VM to an ESX Server.
System action: An error occurred, and the operation
failed. ANE4172I Starting Full VM backup of VMware
User response: Check the reported error and correct
mode: 'full_or_incr'
the problem. Usually the reason for the error is a
target node name: 'target_node_name'
user-supplied value which is not valid for the
operation.
'data_mover_node_name'
application protection type:
ANE4169E A write failure occurred on the local 'application_protection_type'
disk proxy used to temporarily store the application(s) protected: 'application_list'
virtual machine virtual disk
information. The write failure can be
caused by the lack of available disk
space on the drive used to store this
information. The VMBACKDIR option System action: Processing continues.
can be used to assign a different disk
location for this purpose. Check the User response: None required.
drive being used and ensure that there
is enough space available for this ANE4173I Successful Full VM backup of VMware
operation. Virtual Machine 'vmname'
Explanation: There was a write error from the local mode: 'full_or_incr'
disk used to store the virtual machine virtual disk target node name: 'target_node_name'
information. Usually the write error is due to lack of data mover node name:
disk space, lack of write permissions, or some similar 'data_mover_node_name'
problem with the local disk. The VMBACKDIR option Explanation: This message reports statistics or
can be used to assign a different disk location if the information for a client operation performed to this
local drive does not have enough free space for the server. This is logged for informational purposes.
operation.
System action: A disk write error occurred, and the
operation failed. User response: None required.
User response: Check the local disk for possible

causes of the write error, and use the VMBACKDIR ANE4174E Full VM backup of VMware Virtual
option to assign another disk if needed. Machine 'vmname' failed with RC=rc
mode=full_or_incr, target node
name='target_node_name', data mover
ANE4170E Can not create a Virtual Machine on node name='data_mover_node_name'
VMware release 'release-version-target'
which was backed up from VMware Explanation: The Full VM backup of virtual machine
release 'release-version-source'. failed.
Explanation: The Virtual Machine being created was System action: The full backup of the virtual machine
backed up from a version of VMware which is not finished with failures. The next virtual machine in the
compatible with the target VMware release version vmlist will be processed. The reason for the failure is
being used for the restore. written to the local client error log.
System action: Processing stops. User response: Check the local client error log for
User response: Restore the Virtual Machine to a
VMware system which is compatible with the level
from which the Virtual Machine was backed up.

for client-side data deduplication: run "q stg <pool

ANE4175I Starting Full VM restore of VMware
name> f=d" and verify that the value of "Deduplicate
Virtual Machine 'vmname' target node
Data?" is "yes". Ensure that client-side data
deduplication is enabled on the server. To enable
node name='data_mover_node_name'
client-side data deduplication, use the
Explanation: This message reports statistics or DEDUPLICATION parameter on the REGISTER NODE
information for a client operation performed to this or UPDATE NODE server command. Set the value of
server. This is logged for informational purposes. the parameter to CLIENTORSERVER. The value of the
DEDUPLICATION option on the client must be set to
YES. You can set the DEDUPLICATION option in the
User response: None required. client options file, in the preference editor of the Tivoli
Storage Manager client GUI, or in the client option set
on the Tivoli Storage Manager server. Use the DEFINE
ANE4176I Successful Full VM restore of VMware CLIENTOPT command to set the DEDUPLICATION
Virtual Machine 'vmname' target node option in a client option set. To prevent the client from
name='target_node_name', data mover overriding the value in the client option set, specify
node name='data_mover_node_name' FORCE=YES. Ensure that the deduplication parameter
Explanation: This message reports statistics or for the node is "ClientOrServer": The value of the
information for a client operation performed to this DEDUPLICATION option on the client must be set to
server. This is logged for informational purposes. YES.

ANE4179I IBM Spectrum Protect application
User response: None required. protection did not truncate the Microsoft
SQL Server logs on VM 'VM'.
ANE4177E Full VM restore of VMware Virtual Explanation: The SQL server logs were not truncated
Machine 'vmname' failed with RC=rc because the following option was specified for this
target node name='target_node_name', virtual machine: INCLUDE.VMTSMVSS vname
data mover node OPTIONS=KEEPSQLLOG
name='data_mover_node_name'
System action: The operation completes.
Explanation: The Full VM restore of the virtual
machine failed. User response: Remove the OPTIONS=KEEPSQLLOG
option to enable truncation of the SQL logs when a
System action: The full restore of the the virtual backup completes.
machine finished with failures. The next virtual
machine in the vmlist will be processed. The reason for
the failure is written to the local client error log. ANE4180I BYTES='BYTES'
User response: Check the local client error log for Explanation: This message reports statistics or
reason for the failure. information for a client operation performed to this
ANE4178W Compression is currently enabled, but System action: Processing continues.

the virtual machine control files for User response: None required.
'virtual-machine-name' will not be
compressed because client-side
deduplication is not being used for the ANE4181I ACTIVITY_DETAILS='DETAILS'
management class default or specified
by the -vmctlmc option for
'vm-ctl-mgmt-class-name'.
Explanation: Virtual machine control files are not
compressed because data is stored in a storage pool
that is not enabled for client-side data deduplication. User response: None required.
The virtual machine control files are not compressed
during the backup processing unless data is stored in a
ANE4182I AS_ENTITY='AS_ENTITY'
storage pool that is enabled for client-data
deduplication. Explanation: This message reports statistics or
System action: Backup continues, and control file data
is not compressed.
User response: Ensure that the storage pool is enabled


ANE4188I EXAMINED='EXAMINED'
ANE4183I SUB_ENTITY='SUB_ENTITY'
Explanation: This message reports statistics or server. This is logged for informational purposes.
ANE4189I AFFECTED='AFFECTED'
ANE4184I ACTIVITY_TYPE='ACTIVITY_TYPE'
ANE4190I FAILED='FAILED'
ANE4185I RC='RC'
ANE4191E Restore VM operation failed using 'san'
transport mode. In some cases switching
ANE4186I ENTITY='ENTITY' from SAN to network-based VM
restores can be successful.
information for a client operation performed to this Explanation: Restore VM operations that fail using
server. This is logged for informational purposes. SAN transport mode can often be successful over a
LAN path. If a restore vm operation fails using the
System action: Processing continues. 'SAN' transport mode, set the client option
User response: None required. VMVSTORTRANSPORT to "nbd:nbdssl" and try the
restore vm operation again.
ANE4187W CPU and Memory Resource Allocation System action: Restore VM operation failed using 'san'
configuration settings cannot be restored transport mode. Restore may be successful using
when the IBM Spectrum Protect data 'nbd:nbdssl' transport modes.
mover node is connected directly to a User response: Restore VM operation failed using
Virtual Center managed ESX/ESXi host. 'san' transport mode. In some cases network-based VM
These settings have been skipped. restores can be successful when using 'nbd' or 'nbdssl'
Explanation: The VMware vStorage APIs do not transport modes. The VMVSTORTRANSPORT option
support the restore of CPU and Memory Resource can used to restrict the TSM client to use only the
Allocation configuration settings when connected specified transport modes.
directly to an ESX/ESXi host that is managed by a
Virtual Center. ANE4192I Years='Years' Months='Months'
System action: CPU and Memory Resource Allocation Days='Days' Hours='Hours'
configuration settings are skipped. Processing Minutes='Minutes' Seconds='Seconds'
continues. Explanation: This message reports statistics or
User response: Virtual machine CPU and Memory information for a client operation performed to this
Resource Allocation configuration settings will be server. This is logged for informational purposes.
restored when theIBM Spectrum Protect data mover System action: Processing continues.
node connects directly to a vCenter Server. Modify the
VMCHOST to connect the TSM data mover to a User response: None required.
vCenter Server.

ANE4193E vApp 'vApp name' cannot be processed ANE4196I Data encryption type: encryption type
because data mover 'dm node' cannot
connect to the target node 'target_node'.
Explanation: The operation requires that a proxy server. This is logged for informational purposes.
access for the data center node is granted to the data
mover node.
System action: Operation is canceled for the specified
vApp.
ANE4197I Total number of objects encrypted:
User response: Look for errors in error log and correct
Number of objects
any problems. Run configuration wizard or
configuration editor to ensure proper nodes Explanation: This message reports statistics or
configuration. information for a client operation performed to this
ANE4194E Encryption is currently enabled, but is System action: Processing continues.
not supported for incremental forever
backups of virtual machines User response: None required.
(-MODE=IFFULL or
-MODE=IFINCREMENTAL) . ANE4198I Total bytes after deduplication: bytes
Explanation: Client encryption of virtual machine Explanation: This message reports statistics or
incremental forever backups (-mode=IFFULL or information for a client operation performed to this
-mode=IFINCREMENTAL) is not supported. In order server. This is logged for informational purposes.
to avoid the unintentional storage of unencrypted data
on the server, the backup operation stops. System action: Processing continues.
System action: The virtual machine backup stops. User response: None required.
User response: Remove the encryption options for this

operation and run it again. You can use Secure Sockets ANE4199W File 'file name' is not backed up as part
Layer (SSL) encryption to encrypt the data over the of the system state because cluster disk
network. If the backup data must be encrypted in IBM 'volume name' is not accessible.
Spectrum Protect storage pools, use an alternative Explanation: The indicated file or directory was
backup method such as full and incremental backups returned by VSS as part of the backup file list of the
(-mode=FULL and -mode=INCREMENTAL), or writer. However, the cluster disk where the file is
in-guest backups. located is not accessible. The reasons for this problem
can be that the cluster disk is offline or belongs to
ANE4195E The target node for Organization VDC another node.
'OrgVDC name' in Organization 'Org System action: The file is not backed up. Processing
name' was not found. As a result, vApp continues.
'vApp name' cannot be backed up.
User response: This problem is documented in topic
Explanation: Either the IBM Spectrum Protect node 980794 in the Microsoft knowledge base, which is
for the specified organization VDC was not found on available by going to https://support.microsoft.com/
the IBM Spectrum Protect server, or information about and searching on 980794. The topic includes a hotfix.
the Organization VDC node was not found in the With the hotfix, you can specify a registry key that
Provider VDC node. contains a list of one or more files to be excluded from
System action: Back up of the specified vApp stops. VSS enumeration. IBM Spectrum Protect does not back
Processing continues to the next vApp. up files that are not enumerated by VSS. If the volume
is brought online to the node performing the system
User response: Go to the Configuration page and click state backup, then it cannot be backed up. You must
'Run the Configuration Wizard' to verify that all remove the volume from the registry key and restart
required IBM Spectrum Protect nodes are registered on the system before you can back up the volume.
the IBM Spectrum Protect server. If required, register a If you do not want to implement the hotfix for this
new data mover node. Make sure that the organization problem, IBM Spectrum Protect continues to issue this
VDC belongs to the provider VDC that this data mover message.
node protects.


ANE4200I architecture, schedule-name, domain-name:
The Deployment Manager process was User response: Check the release documentation for
started successfully. Deployment information on supported operating system levels.
Manager Version Information: version.
Explanation: The Deployment Manager process was ANE4205I The Deployment Manager succesfully
started as a post schedule command. This is the first extracted from installation image: image
message from the Deployment Manager. The name.
architecture of the client, schedule name, and domain
name are identified at the beginning of the message Explanation: This message reports statistics or
text. information for a client operation performed to this
System action: Deployment Manager continues to
process. System action: Processing continues.
User response: None User response: None required.
ANE4201I The Deployment Manager successfully ANE4206E The Deployment Manager received an
installed language pack: language pack error while extracting from installation
name. image: image name.
Explanation: This message reports statistics or Explanation: The installation image might be missing,
information for a client operation performed to this corrupted, or there might be insufficient disk space on
server. This is logged for informational purposes. the client computer.
System action: Processing continues. System action: Deployment Manager stops.
User response: None required. User response: Make sure that there is sufficient disk
space on the client computer.
ANE4202E The Deployment Manager failed to Make sure that all of the Windows self extracting client
install language pack: language pack images on the client computer are valid.
name. The Microsoft Installer error code
was error code. ANE4207I The Deployment Manager shut down
Explanation: The previous language pack has been service successfully: service name.
uninstalled, and the installation of the new language Explanation: This message reports statistics or
pack failed. information for a client operation performed to this
System action: Processing continues. server. This is logged for informational purposes.
User response: For more information about Windows System action: Processing continues.
installer error messages, go to the Microsoft Developer User response: None required.
Network (MSDN) technical library at
http://msdn.microsoft.com/library and search on
"Windows Installer Error Messages". ANE4208E The Deployment Manager could not
shut down IBM Spectrum Protect
Check the install log on the client computer. service: service name.
Explanation: None
ANE4203I The Deployment Manager successfully
retrieved system information. System action: Processing continues.
Explanation: This message reports statistics or User response: None

server. This is logged for informational purposes. ANE4209I The Deployment Manager successfully
System action: Processing continues. installed package: client package name.
User response: None required. Explanation: This message reports statistics or

ANE4204E The Operating System of the client
computer: os name is not supported by System action: Processing continues.
the target version: target version. User response: None required.
Explanation: The operating system level of the client
computer is no longer supported by the target level.

a client package with the appropriate operating system

ANE4210E The Deployment Manager failed to
platform.
install package: client package name. The
Microsoft Installer error code was error
code. ANE4215E The automatic deployment path from
the current client code version 'source
Explanation: The previous client package has been
version' to the client package version
uninstalled, and the installation of the new client
'target version' is not supported.
package failed.
Explanation: None
User response: For information about Microsoft
Installer error codes go to the Microsoft Developers User response: Reschedule the client deployment with
Network (http://msdn.microsoft.com/en-US/) and an appropriate target level.
search for "Windows Installer Error Messages".
For more information, search for "automatic client
Check the install log on the client computer. deployment" in the product information
(http://www.ibm.com/support/knowledgecenter/
SSEQVQ/).
ANE4211I The Deployment Manager successfully
restarted service: service name.
ANE4216E The IBM Spectrum Protect API library
version API version is at an earlier
version than the version of the client
package package version.
Explanation: The client package for automatic
User response: None required. deployment is invalid. In the client package, the API
version does not match the Deployment Manager
version.
restart service: service name. System action: Deployment Manager stops processing.
Explanation: After the automatic client deployment, User response: Please make sure that the installation
the IBM Spectrum Protect client services failed to start. package is valid.
ANE4217E The Deployment Manager received an
User response: Log on to the client machine and
error while setting up the client API.
check the backup-archive client error log.
The standard API function being
invoked is API setup function name.
ANE4213E Automatic restart of the client computer
Explanation: The Deployment Manager process failed
was required because reason
when setting up the client API.
Explanation: The Deployment Manager determined
that the deployment requires restarting the client.
User response: Check the error log on the client
Automatic restart is not enabled. The Deployment
computer.
Manager process cancels the deployment.
The current client is not uninstalled or updated.
ANE4218E The Deployment Manager received an
System action: Deployment Manager cancels the client error while initializing the client API.
deployment and stops The standard API function being
invoked was API init function name.
User response: Reschedule the client deployment.
Explanation: The Deployment Manager process failed
when initializing the client API.
ANE4214E The operating system platform of the
client package 'OS platform of package' is System action: Processing stops.
incompatible with the client computer
'OS platform of client computer'.
computer.
Explanation: None
User response: Reschedule the client deployment. Use

ANE4219E The Deployment Manager received an ANE4224I The Deployment Manager successfully
error while creating a pipe for the shuts down backup-archive client
standard output of the child process. processes with names starting with
"dsm" .
Explanation: The Deployment Manager failed to
create a pipe for the standard output of the child Explanation: This message reports statistics or
process. information for a client operation performed to this
computer. User response: None required.
ANE4220E The Deployment Manager is unable to ANE4225W The setup script is still waiting for the
determine if IBM Spectrum Protect result of querying system information.
processes are still running. Ensure that "PASSWORDACCESS
GENERATE" is set in the client options
Explanation: The Deployment Manager could not
file and that a connection to the server
determine whether all IBM Spectrum Protect processes
can be made without being prompted
were shut down successfully.
for a password.
System action: If automatic restart (autoreboot) is
Explanation: The results of querying the system
enabled, the Deployment Manager continues. If
information has taken longer than expected. This could
automatic restart is not enabled, Deployment Manager
be caused by either a slow system or becuase there is
stops.
no password saved for the node.
User response: Reschedule with automatic restart
System action: If the password is not generated,
(autoreboot) enabled.
processing stops and client deployment will not begin.
If the system is slow, processing continues.
ANE4221E The architecture of the package: package
User response: Ensure that "PASSWORDACCESS
architecture does not match the current
GENERATE" is set in the client options file and that a
client: system architecture.
connection to the server has been made without being
Explanation: The setup script was unable to retrieve prompted for a password. Ignore the warning if the
the matching package from the server. password has been generated.
ANE4226E There is at least one error in the post
User response: Ensure that the client packages for all schedule command of the client
architectures are available on the server. deployment schedule.
Explanation: The Deployment Manager encountered
ANE4222E The Deployment Manager is unable to at least one error while parsing the post schedule
read information in file: file name. command of the client deployment schedule.
Explanation: Deployment Manager failed to open a System action: Processing stops, and client
file containing required system information. deployment will not begin.
System action: Processing stops. User response: Check the release documentation for
User response: Check the error log on the client information on the format of the post schedule
computer. command of the client deployment schedule.
ANE4223E The Deployment Manager is missing ANE4227E The Deployment Manager failed to
required information in file: file_name. install package: client package name. The
client computer is out of disk space. The
Explanation: The Deployment Manager relies on the Microsoft Installer error code was error
information in this file to complete the client code.
deployment.
Explanation: The previous client package has been
System action: Processing stops. uninstalled, and the installation of the new client
User response: Check the error log on the client package failed because the client computer is out of
computer. disk space.


ANE4231E The deployment for language pack:
Installer error codes go to the Microsoft Developers
image name was cancelled.
Network (http://msdn.microsoft.com/en-US/) and
search for "Windows Installer Error Messages". Explanation: The Deployment Manager does not
uninstall or update the current language pack. It is
Check the install log on the client computer.
possible the other messages provide details of the
deployment.
System action: Processing stops. The client computer
install language pack: language pack
will be shut down and restarted immediately after all
name. The client computer is out of disk
language packs are deployed, or immediately if there
space. The Microsoft Installer error code
are no language pack to install.
was error code.
Explanation: The previous language pack has been
computer. Manually deploy the language pack.
uninstalled, and the installation of the new language
pack failed because the client computer is out of disk
space. ANE4232E Self-extracting installation image: image
name cannot be found.
Explanation: The Deployment Manager could not find
the required installation image.
Installer error codes go to the Microsoft Developers
Network (http://msdn.microsoft.com/en-US/) and System action: Processing stops. Client deployment
search for "Windows Installer Error Messages". will be cancelled.
Check the install log on the client computer. User response: Check the server's activity log or the
scheduler log on the client computer. Reshcedule the
client deployment.
ANE4229I The client computer is required to
restart to complete the new
Backup-Archive client installation. ANE4233I The Deployment Manager will install
the Backup-Archive client with the
Explanation: The deployment of the new
following feature set: feature set.
backup-archive client will not be complete until the
client computer is restarted. The restart is scheduled to Explanation: This message reports statistics or
happen immediately after all language packs are information for a client operation performed to this
deployed. server. This is logged for informational purposes.
System action: The Deployment Manager process System action: Processing continues.
continues. The client computer will be shut down and
restarted after all language packs are deployed, or
immediately if there are no language pack to install.
ANE4234E The deployment for language packs
User response: None
failed.
Explanation: The Deployment Manager failed to
ANE4230I The client computer will be shut down
install one or more language packs. It is possible the
and restarted immediately.
other messages provide details of the installation.
Explanation: The Deployment Manager needs to
System action: The Deployment Manager process
restart the client computer to complete the client
continues.
deployment. It is possible the other messages provide
details of the deployment. User response: Check the error log and installation on
the client computer. Identify the language packs that
failed to install and manually deploy them.
continues. The client computer will be shut down and
restarted immediately after all language packs are
deployed, or immediately if there are no language pack ANE4235I The deployment manager cannot log
to install. events to the server.
User response: None Explanation: The Deployment Manager is unable to
log events to the server. It is possible the other
messages provide details of the communications.
continues. Events will be logged locally on the client
machine only.

User response: Check network connection and the

ANE4240E Client version information is missing in
error log on the client computer.
the client package.
Explanation: It is possible the client deployment
ANE4236E The setup script was unable to query
package is missing or corrupted.
the registry for the IBM Spectrum
Protect client installation directory. System action: Processing stops. Client deployment
will not start.
Explanation: The setup script encountered an error
while querying the Windows registry for User response: Ensure that the client package is
[HKLM\SOFTWARE\IBM\ADSM\CurrentVersion\ available and imported to the server correctly.
BackupClient].
System action: Processing stops, and client ANE4241I Architecture of the package: package
deployment will not begin. architecture does not match the current
client: system architecture. The setup
User response: Check the release documentation for
script is attempting to retrieve the
information on supported Windows platforms and
matching package.
ensure the REG.EXE command is available on the client
computer. Explanation: The setup script is trying to retrieve the
matching client package from the server.
ANE4237W Query system information was System action: Processing continues.
completed with warnings or errors.
User response: Ensure that the client packages for all
ErrorLevel was error level
architectures are available on the server.
Explanation: The setup script encountered warnings
or errors while querying system information.
ANE4242E The setup script encountered a warning
System action: Processing continues. The Deployment or error while retrieving the client
Manager will check to see if required system package for architecture. The error level
information is available. Client deployment could be is error level.
cancelled if required information is missing.
Explanation: It is possible the client package is not
User response: Check the error log of the available on the server.
backup-archive client for warning and error messages.
User response: Ensure that client packages for all
ANE4238E Processor Architecture information is
architectures are available on the server. Check the
missing in the system information.
backup-archive client error log for more detailed error
Explanation: It is possible the setup script messages.
encountered a warning or error while querying system
information.
ANE4243I The setup script successfully retrieved
System action: Processing stops. Client deployment the client package for architecture.
will not start.
Explanation: The client package that was downloaded
User response: Check the error log of the matches the processor architecture of the current client.
backup-archive client for warning and error messages.
User response: None
ANE4239E Processor Architecture information is
missing in the client package.
ANE4244E The setup script failed to install the
Explanation: It is possible the client deployment
Microsoft Visual C++ redistributable
package is missing or corrupted.
package. Error Level is error level.
System action: Processing stops. Client deployment
Explanation: The Microsoft Visual C++ redistributable
will not start.
package is required by the new client.
User response: Ensure that the client package is
available and imported to the server correctly.
User response: Check the installation log file for
names with "vcredist*.log" file in system temp directory.

information on supported Windows platforms and

ANE4245I The setup script successfully installed
ensure the REG.EXE command is available on the client
the Microsoft Visual C++ redistributable
computer.
package.
Explanation: The Microsoft Visual C++ redistributable
ANE4250E There is already a deployment manager
package is required by the new client.
running on this computer.
Explanation: Only one instance of client deployment
User response: none manager can be active at a time. This client computer
might be configured with multiple node names, but the
new client code only needs to be deployed to one node
ANE4246E The setup script failed to start the
per computer. Each client deployment instance can take
Deployment Manager program. Error
a few minutes to complete.
Level is error level.
Explanation: The setup script could not start the client
deployment process. User response: Ensure only one client deployment
task is scheduled to run at a time.
User response: Check the log files on the client
ANE4251W writername file 'filename': not found.
computer for more details. Ensure the client package is
not corrupted. Explanation: The indicated VSS writer file or directory
was returned by VSS as part of the backup file list of
the writer. However, the object does not exist on the
ANE4247I The setup script successfully started the
disk.
Deployment Manager program.
.
Explanation: The setup script invokes the Deployment
System action: Processing stops if
Manager to manage the deployment process.
SKIPMISSINGSYSWFILES option is set to NO.
System action: Processing continues. Processing continues if SKIPMISSINGSYSWFILES
option is set to YES.
User response: None
User response: Verify that this file can be skipped
during system state backup.
ANE4248E The client is already at the target level:
'target version'.
ANE4252E The deployment manager failed to start
Explanation: Processing stopped because the as a scheduled task.
automatic client deployment feature does not support
the installation of a client to a workstation that is Explanation: The setup script failed to start the
already at its target level. deployment manager as a scheduled task with the
Windows "at" command.
System action: Your current backup-archive client is
not affected. System action: Processing stops.
User response: Reschedule the client deployment with User response: Ensure that the Windows Task
an appropriate target level. Scheduler service is running. It is possible that the
system event log contains more details about the
For more information, search for "automatic client failure. Reschedule the client deployment.
deployment" in the product information
SSEQVQ/). ANE4253E There was not enough disk space on the
client computer. Required space: package
space bytes; available space: system space
ANE4249E The setup script was unable to query bytes.
the registry for the client scheduler
service name. Explanation: The deployment manager determined
there was insufficient free disk space for the client
Explanation: The setup script encountered an error deployment.
while querying the Windows registry for
[HKLM\SOFTWARE\IBM\ADSM\CurrentVersion\ System action: Processing stops.
BackupClient\Scheduler Service].
User response: Free up required disk space and
System action: Processing stops, and client reschedule the client deployment.
deployment will not begin.
User response: Check the release documentation for

because the user who is initiating the task does not

ANE4254E The deployment manager detected an
have sufficient authority.
HSM client on the workstation that it
needs to deploy the Backup-Archive System action: Processing stops.
client to.
User response: Ensure that the user who starts the
Explanation: An attempt was made to deploy the client scheduler has administrative privileges.
Backup-Archive client to a workstation that already has
the HSM client installed. The Backup-Archive client
cannot be deployed to a workstation that has the HSM ANE4259E The client scheduler is not started as a
client. root user.
System action: Processing stops. Explanation: The client scheduler requires root user
privileges to upgrade the client code.
User response: Uninstall the HSM client and
reschedule the Backup-Archive client deployment. System action: Processing stops.
User response: Log in as root and start the client
ANE4255E There is not enough memory for the scheduler.
deployment manager to create the
system information object ANE4260E The installation file system is not
Explanation: The system information object could not writeable.
be created because there is not enough available RAM Explanation: The deployment manager cannot write
to temporarily write the data into. to the installation file system.
System action: Processing stops. System action: Processing stops.
User response: Close all unneeded applications on the User response: Check the installation file system
client workstation and reschedule the deployment. permissions. It is possible that the current client node
runs in a virtualized environment using the client code
ANE4256E The DSMI_DIR environment variable is installed in a shared storage of the physical
not defined. environment. Reschedule the client deployment with
the client node in the physical environment.
Explanation: The deployment manager cannot initiate
a connection to the server because the DSMI_DIR
environment variable is not set. This error can occur if ANE4261E The deployment manager cannot
the deployment manager is started without using the upgrade the Backup-Archive Client.
client scheduler. Explanation: The Backup-Archive Client cannot be
System action: Processing stops. upgraded because either the current location is not the
default installation location or the DSM_DIR,
User response: Read the available documentation to DSMI_DIR, DSM_CONFIG and DSMI_CONFIG
determine how to use the client scheduler to create a environment variables are defined with a relative path
client deployment task. and not an absolute path.
ANE4257E The deployment manager cannot parse
information in file: file name. User response: Check the installation directory of the
current Backup-Archive Client. If the Backup-Archive
Explanation: The deployment manager could not Client is not installed in the default location, manually
parse or extract the required information from the upgrade the Backup-Archive Client. If the DSM_DIR,
specified file. DSMI_DIR, DSM_CONFIG and DSMI_CONFIG
environment variables are defined with a relative path,
define them with an absolute path and try the client
User response: Check the error log file on the client deployment again.
workstation.
ANE4262E The preview of the client installation
ANE4258E The deployment manager received the failed.
Windows "OpenSCManager failed" error
Explanation: The deployment manager did not
message.
uninstall the current client. The client code is
Explanation: The deployment manager could not unchanged.
connect to the Windows service control manager to
start the client scheduler. In general, this error occurs
User response: Check the deployment manager log

and trace files on the client workstation for specific

ANE4267I The deployment manager failed to
issues identified during the preview. Reschedule a
install the hardware plugin package.
deployment after any issues are resolved.
Explanation: The previous package was uninstalled.
The installation of the new hardware plugin package
ANE4263E The deployment manager failed to
failed.
uninstall the backup-archive client.
Explanation: The deployment manager received an
error while uninstalling the current client. User response: Check the deployment trace file on the
client workstation.
ANE4268I The deployment manager failed to
and trace files on the client workstation for more
install the journal-based backup
details on the error. You might have to manually
package.
uninstall the client.
Explanation: The previous journal-based backup
package was uninstalled. The new journal based
ANE4264E The deployment manager failed to
backup package installation failed.
install the backup-archive client.
Explanation: The current client was uninstalled and
the deployment manager received an error while User response: Check the deployment trace file on the
installing the new client code. client workstation.
ANE4269W The deployment manager is stopping
the scheduler and/or CAD processes.
and trace files on the client workstation for more
details on the error. Manully install the new client after Explanation: Before deploying the new client, the
the issue is resolved. deployment manager must stop the scheduler and
CAD processes. After the deployment, the processes
must be restarted.
ANE4265I Client deployment options are not
specified in the scheduler command or System action: Processing continues.
from client services.
User response: The client scheduler is interrupted
Explanation: The default client options file will be during the deployment.
used. The deployment manager might not report the
correct server and node information when reporting
ANE4270I The deployment manager and the new
status.
client installation packages were
System action: Processing continues. downloaded to directory: file name.
User response: Avoid initiating the client deployment Explanation: The download directory contains
directly from the command-line, instead, always start everything required to complete the new client
the client scheduler as a Windows service. deployment. Deployment log and trace files can be
found in the log/ sub-directory.
ANE4266I The deployment manager failed to System action: Processing continues.
install non-English language pack(s).
User response: Obtain log and trace files from the
Explanation: The previous packages were uninstalled, download directory for problem determination. The
and the installation of one or more new language packs files are found within the log/ sub-directory.
were not successful.
System action: Processing continues. ANE4271E The deployment package is missing one
or more required installation image
User response: Check the deployment trace file on the
files.
client workstation for specific language pack
information. Explanation: The client deployment package might
not have been imported correctly to the server. It is
possible that the deployment package is not retrieved
completely to the client computer, due to a lack of disk
space.

User response: Ensure that client packages are workstation and check the error log file. If you have set
available on the server and there is sufficient disk space environment variables make sure they are not defined
on the client computer. Check the backup-archive client using relative path.
error log file for more detailed error messages.
ANE4276E The deployment manager cannot obtain
ANE4272E The processor type of the package: information about the scheduler or the
package processor type does not match the CAD processes.
current client: system processor type.
Explanation: The deployment manager needs process
.
information in order to stop and restart the
Explanation: The processor type supported by the Backup-Archive Client scheduler or CAD processes.
client package that you want to deploy does not match
the processor type of the workstation that you are
trying to deploy the client to. It is not always possible User response: Log on to the Backup-Archive Client
for the deployment manager to connect to the server workstation and check the error log file and the
and report the error. deployment manager error log file.
ANE4277E The target operating system version
User response: Verify that you are using the correct
target operating system does not meet the
client package for the processor architecture of the
minimum required version minimum
computer that you want to upgrade. Then restart the
required version
deployment.
Explanation: The operating system version is earlier
than the version required by the automatic deployment
ANE4273E The deployment manager detected a
package.
journal based backup (JBB) client on the
workstation where it needs to deploy System action: The deployment is canceled.
the Backup-Archive Client.
User response: Ensure that the IBM Spectrum Protect
Explanation: An attempt was made to deploy the version being deployed is supported by the target
Backup-Archive Client to a workstation that already operating system.
has the JBB client installed. On some platforms, the
Backup-Archive Client cannot be deployed to a
workstation that has the JBB client installed. ANE4278E The deployment manager cannot obtain
information about the Logical Volume
System action: Processing stops. Snapshot Agent (LVSA).
User response: Uninstall the JBB client and reschedule Explanation: The deployment manager needs to
the Backup-Archive Client deployment. determine whether an LVSA is installed on the client
workstation.
ANE4274E The deployment manager cannot stop System action: Processing stops.
the scheduler or the CAD processes.
User response: Log on to the Backup-Archive Client
Explanation: The deployment manager tried to shut workstation and check the error log file and the
down the Backup-Archive Client scheduler or CAD deployment manager error log file.
processes but the Backup-Archive Client might be busy
with other tasks.
ANE4279I Server information is not available in
System action: Processing stops. the deployment schedule.
User response: Reschedule the Backup-Archive Client Explanation: This message reports statistics or
deployment. information for a client operation performed to this
ANE4275E The deployment manager cannot restart System action: Processing continues.
the scheduler or the CAD processes.
Explanation: Before exiting, the deployment manager
could not restart the Backup-Archive Client scheduler
or CAD processes. The deployment manager stopped ANE4280E Automatic client deployment is not
the processes prior to the client upgrade. allowed on the client workstation.
System action: Processing continues. Explanation: One or more of the running client
services include AUTODEPLOY = NO in the option
User response: Log on to the Backup-Archive Client file.


ANE4284E The deployment is cancelled because an
User response: Change the AUTODEPLOY option on automatic client deployment task was
the client and reschedule the client deployment. scheduled for a sparse-root, non-global
zone that shares the /usr file system
with the global zone.
ANE4281E The update manager cannot remove the
TIVsmCapi package from non-global Explanation: The automatic client deployment task
zone(s): zone name. that was attempted is not supported and will be
cancelled.
Explanation: APAR IC57433 prevents the removal of
the TIVsmCapi package on Solaris on a sparse-root, System action: Processing stops.
non-global zone if uninstalling is done from the global
User response: Install the Backup-Archive Client from
zone.
the global zone or manually upgrade the
System action: Processing stops. Backup-Archive Client.
User response: Manually uninstall the Tivoli Storage

Manager client directly from the non-global zones and ANE4285E The update restore operation to an
reschedule the deployment. existing virtual machine 'VmName'
failed. The virtual machine is not in
power off state.
ANE4282E Sparse-root non-global zone(s) were
found with IBM Spectrum Protect Explanation: The update restore operation to an
Backup-Archive Client that was existing virtual machine is not supported for a running
installed from the non-global zone: zone machine and will be aborted.
names.
System action: Restore aborted.
Explanation: One or more non-global zones are
User response: Turn off the virtual machine and
sharing the /usr file system with the global zone. The
re-run the update restore command.
Tivoli Storage Manager Backup-Archive Client is
installed in the global zone with the -G parameter and
also installed manually in the non-global zone(s). You ANE4286I SCHEDULE_NAME=
cannot update the Tivoli Storage Manager 'SCHEDULE_NAME'
Backup-Archive Client in the global zone because it
will update the version of GSKit that is shared with the
sparse-root non-global zones that are not part of the
automatic deployment.
User response: Manually upgrade the Backup-Archive
Client or install it from the global zone without using
the -G parameter. This ensures that you have the same ANE4289I Backup of VMware vApp 'vApp name' in
version between the global zone and the sparse-root Organization VDC 'Org VDC name' of
non-global zones, and you can then deploy the client organization 'Org name' completed
automatically on all such zones. successfully
mode: 'Incremental Forever - full_or_incr'
target node name: 'target_node_name'
ANE4283E There is not enough disk space on path
to uncompress GSKit packages.
Required space: req_space bytes;
VMs backup status: number of VM backed
available space: avail_space bytes.
up out of number of VMs in vApp VMS
Explanation: The deployment manager determined backed up successfully
that there is not enough free disk space to uncompress
GSKit packages.
System action: Processing stops. server. This is logged for informational purposes.
User response: Free up the required amount of disk System action: Processing continues.
space and reschedule the automatic client deployment.

ANE4290E Only one virtual machine can be ANE4295W architecture, schedule-name, domain-name:
selected for restore. The client deployment was not
completed pending the restart of the
Explanation: Restoring multiple virtual machines is
client computer. The deployment
not allowed. Only one virtual machine can be selected
manager did not restart the client
for restore.
computer automatically because the
System action: No processing occurs. AUTODEPLOY option was set to
NOREBOOT.
User response: Select only one virtual machine for
restore. Explanation: The previous client has been uninstalled,
and the installation of the new client was not
completed pending the restart of the client computer.
ANE4291E Virtual Machine could not be found on The architecture of the client, schedule name, and
VMware server. domain name are identified at the beginning of the
Explanation: The backup of virtual machine failed. message text.
System action: The backup of the virtual machine System action: The Deployment Manager process
finished with failures. The next virtual machine in the completes.
vmlist will be processed. The reason for the failure is User response: Manually restart the client computer
written to the local client error log. as soon as possible.
reason for the failure. ANE4296I architecture, schedule-name, domain-name:
The client deployment was completed
ANE4292E No virtual machine found. successfully, and the client computer is
being restarted.
Explanation: No virtual machine found with name or
specified in domain option. Explanation: Restarting the computer is required to
complete the client deployment. The architecture of the
System action: Processing stopped. client, schedule name, and domain name are identified
User response: Specify a correct VM name or domain at the beginning of the message text.
option. System action: The Deployment Manager process
completes. The client computer will be shut down and
ANE4293E Backup of VMware vApp 'vApp name' in restarted.
Organization VDC 'Org VDC name' of User response: None
organization 'Org name' failed.
Explanation: The vApp backup operation failed. This ANE4297W architecture, schedule-name, domain-name:
error message is a summary message and does not Client deployment was completed with
contain detailed information. warnings: warnings.
System action: The configuration information and Explanation: This message is a generic warning
VMs for the specified vApps are not backed up. message. It is possible that other messages provide
Processing continues to the next vApp. details of the deployment. The architecture of the client,
User response: Check the previous messages in the schedule name, and domain name are identified at the
dsmerror.log file for more details about this vApp . beginning of the message text.
ANE4294I Total number of vApps processed: total completes.
number User response: Check the warning messages from the
Number of vApps backed up server administration center, the server activity log, or
successfully: total number error log on the client computer for more information.
Number of vApps failed: total number
Explanation: This message reports statistics or ANE4298E architecture, schedule-name, domain-name:
information for a client operation performed to this The client deployment was canceled.
server. This is logged for informational purposes. The previous event causing the
System action: Processing continues. cancellation is: event.
User response: None required. Explanation: This message is a generic message that
the client deployment was canceled. The Deployment
Manager does not uninstall or update the current client.
It is possible that the other messages provide details of

the deployment. The architecture of the client, schedule User response: Check IBM Spectrum Protect error log
name, and domain name are identified at the beginning for additional information.
of the message text.
System action: Processing stops. ANE4303E The vCloud Director vApp 'vapp-name'
has not been previously backed up.
User response: Check the warning messages from the
server administration center, the server activity log, or Explanation: The specified vCloud Director vApp has
error log on the client computer for more information. not been previously backed up, so can not be specified
for restore.
ANE4299E architecture, schedule-name, domain-name: System action: The specified vCloud Director vApp is
The client deployment failed. The skipped, and the next vApp in the restore list is
previous event causing the failure is: processed.
event.
User response: Verify the vCloud Director vApp name
Explanation: This message is a generic message that to be restored, and re-try the operation.
the client deployment failed. It is possible that other
messages provide details of the failure. The architecture
ANE4304I IBM Spectrum Protect could not detect
of the client, schedule name, and domain name are
the IBM Spectrum Protect for VE
identified at the beginning of the message text.
license. Active Directory Domain
System action: Processing stops. Controller will not be protected on VM
'VM'.
User response: Check the warning messages from the
server administration center, the server activity log, or Explanation: The virtual machine contains Microsoft
error log on the client computer for more information. Active Directory Domain Controller, but a TSM for VE
license is not detected. The Domain Controller will not
be protected.
ANE4300I architecture, schedule-name, domain-name:
Client deployment was completed System action: Install TSM for VE 7.1 or later to
successfully. protect Active Directory.
Explanation: This is a generic message that the client User response: None
deployment was successful. It is possible that other
messages provide details of the deployment. The
ANE4305W Backup of VMware vApp 'vApp name' in
architecture of the client, schedule name, and domain
Organization VDC 'Org VDC name' of
name are identified at the beginning of the message
organization 'Org name' completed. Some
text.
VMs were not backed up.
System action: The Deployment Manager process mode: 'Incremental Forever - full_or_incr'
completes. target node name: 'target_node_name'
User response: None
VMs backup status: number of VM backed
ANE4301I IBM Spectrum Protect detected up out of number of VMs in vApp VMs
Microsoft Active Directory Domain backed up successfully.
Controller on virtual machine 'VM'.
Explanation: The vApp backup operation completed
Explanation: The virtual machine contains Microsoft successfully. However, one or more VMs for the
Active Directory Domain Controller. specified vApp were not backed up. These VMs will
not be created during the restore operation.
System action: IBM Spectrum Protect saved additional
information about this virtual machine. System action: Processing continues to the next vApp.
User response: None User response: Check the dsmerror.log file for this
vApp for more information about this message. Resolve
the problem, then try the operation again.
ANE4302W IBM Spectrum Protect failed to detect if
Microsoft Active Directory Domain
Controller on virtual machine 'VM'. ANE4306I Starting Full VM backup of 'hypervisor'
Explanation: There was an error while checking if the mode: 'full_or_incr'
virtual machine contains Microsoft Active Directory target node name: 'target_node_name'
Domain Controller. data mover node name:
System action: IBM Spectrum Protect continues 'data_mover_node_name'
backing up this virtual machine. application protection type:

'application_protection_type' System action: Processing continues.

application(s) protected: 'application_list'
ANE4311E Full VM restore of 'hypervisor' Virtual
Machine 'vmname' failed with RC=rc
System action: Processing continues. target node name='target_node_name',
data mover node
name='data_mover_node_name'
Explanation: The Full VM restore of the virtual
ANE4307I Successful Full VM backup of
machine failed.
'hypervisor' Virtual Machine 'vmname'
mode: 'full_or_incr' System action: The full restore of the the virtual
target node name: 'target_node_name' machine finished with failures. The next virtual
data mover node name: machine in the vmlist will be processed. The reason for
'data_mover_node_name' the failure is written to the local client error log.
Explanation: This message reports statistics or User response: Check the local client error log for
information for a client operation performed to this reason for the failure.
System action: Processing continues. ANE4320I Agent Name session type (data mover
version version).
ANE4308E Full VM backup of 'hypervisor' Virtual
Machine 'vmname' failed with RC=rc
mode=full_or_incr, target node System action: Processing continues.
Explanation: The Full VM backup of virtual machine
ANE4324I Starting backup of VMWare vCloud
failed.
Director vApp 'vapp name' from
System action: The full backup of the virtual machine organization VDC 'org vdc name' of
finished with failures. The next virtual machine in the organization 'org name'.
vmlist will be processed. The reason for the failure is mode: 'full_or_incr'
written to the local client error log. target node name: 'target_node_name'
number of virtual machines: 'num vms'
ANE4309I Starting Full VM restore of 'hypervisor'
node name='data_mover_node_name' System action: Processing continues.
Explanation: This message reports statistics or User response: None required.
ANE4444I Starting a file-level restore of hypervisor
System action: Processing continues. type Virtual Machine 'vmname'. The data
center node name is'data center node
name', the mount proxy node name
is'mount proxy node name'
ANE4310I Successful Full VM restore of 'hypervisor'

ANE4445I • ANE4900W
ANE4445I Successful completion of a file-level ANE4449E A cleanup of the file-level restore of

restore for hypervisor type Virtual hypervisor type Virtual Machine 'vmname'
Machine 'vmname'. The data center node failed. The data center node name is
name is 'data center node name', the mount 'data center node name', the mount proxy
proxy node name is'mount proxy node node name is 'mount proxy node name'
name'
Explanation: The cleanup of file-level restore mount
Explanation: This message reports statistics or operation of the virtual machine failed.
System action: The cleanup of mount of the virtual
machine finished with failures. The reason for the
System action: Processing continues. failure is written to the local client error log.
User response: None required. User response: Check the local client error log for
ANE4446E A file-level restore mount operation for
hypervisor type Virtual Machine 'vmname' ANE4450E Mount proxy platform is not supported
failed. The data center node name is for file-level restore operations.
'data center node name', the mount proxy
Explanation: The file-level restore operation failed.
node name is 'mount proxy node name'
The reason for the failure is an unsupported platform
Explanation: The file-level restore mount operation of or that the IBM Spectrum Protect Recovery Agent is not
the virtual machine failed. correctly installed and configured.
System action: The mount of the virtual machine System action: The file-level restore operation failed.
finished with failures. The reason for the failure is
User response: The file-level restore mount operation
should be performed from a supported mount proxy
User response: Check the local client error log for platform with IBM Spectrum Protect Recovery Agent
reason for the failure. installed and configure correctly .
ANE4447I Starting a cleanup for the file-level ANE4451E The Windows iSCSI service is not
restore of hypervisor type Virtual Machine available.
'vmname'. The data center node name is
Explanation: The Windows iSCSI service is not
'data center node name', the mount proxy
available on the mount proxy machine. It is either not
node name is 'mount proxy node name'
started or not installed or configured correctly.
System action: Processing stops, the file-level restore
mount operation fails.
User response: Ensure that the iSCSI service is up and
running on the mount proxy machine.
ANE4900W Schedule 'schedule-name' has opened a
ANE4448I Successful completion of a cleanup for new session with the server.
the file-level restore of hypervisor type
Explanation: A scheduled event endsbecause of a
Virtual Machine 'vmname'. The data
connection failure. The scheduled event had to be
center node name is 'data center node
restarted outside its normal startup window to
name', the mount proxy node name is
continue the operation.
'mount proxy node name'
System action: The scheduled event is completed
using more than one session.
server. This is logged for informational purposes. User response: None required. If this is a recurrent
condition, you may want to check for network
problems.

ANE4901E The following object contains one or ANE4905I Starting instant restore of VMware
more unmatched quotation marks and Virtual Machine 'vmname' target node
cannot be processed: 'filespace path name='target_node_name', data mover
filename'. node name='data_mover_node_name'
Explanation: The file name in the file list contains Explanation: This message reports statistics or
unmatched quotes. If a line in the file list begins with a information for a client operation performed to this
single or double quotation mark this quotation mark is server. This is logged for informational purposes.
considered to be an opening quotation mark. The
corresponding closing quotation mark of the same type
must be at the end of the line. If there is no closing User response: None required.
quotation mark or the closing quotation mark has been
encountered in the middle of the line, it is an invalid
input. ANE4906I Successful instant restore of VMware
System action: The object is skipped. name='target_node_name', data mover
User response: Correct the specification of the object.
ANE4902I Starting instant access of VMware
name='target_node_name', data mover System action: Processing continues.
server. This is logged for informational purposes. ANE4907E Instant restore of VMware Virtual
Machine 'vmname' failed. target node
System action: Processing continues. name='target_node_name', data mover
Explanation: The instant restore of the virtual machine
failed.
ANE4903I Successful instant access of VMware
Virtual Machine 'vmname' target node System action: The instant restore of the the virtual
name='target_node_name', data mover machine finished with failures. The reason for the
node name='data_mover_node_name' failure is written to the local client error log.
Explanation: This message reports statistics or User response: Check the local client error log for
information for a client operation performed to this reason for the failure.
System action: Processing continues. ANE4908I Starting cleanup of VMware Virtual
Machine 'vmname' from snapshot of
'origvmname' target node
ANE4904E Instant access of VMware Virtual node name='data_mover_node_name'
Machine 'vmname' failed. target node
Explanation: The instant access of the virtual machine
failed.
System action: The instant access of the the virtual
machine finished with failures. The reason for the
failure is written to the local client error log. ANE4909I Successful cleanup of VMware Virtual
Machine 'vmname' from snapshot of
'origvmname' target node


ANE4915I Object increased in size during
User response: None required. compression: filespace pathfilename
Explanation: The file increased in size during
ANE4910E Cleanup of VMware Virtual Machine compression.
'vmname' failed. target node
System action: Processing contiues.
node name='data_mover_node_name' User response: None.
Explanation: The cleanup of the virtual machine
failed. ANE4916I Total number of retries: Number
System action: The cleanup of the the virtual machine Explanation: This message reports statistics or
finished with failures. The reason for the failure is information for a client operation performed to this
written to the local client error log. server. This is logged for informational purposes.
User response: Check the local client error log for System action: Processing continues.
ANE4911I VMware Virtual Machine 'vmname' is

ANE4939I Total snapshot difference objects:
ready for use
Number
ANE4912I Backup for 'Data Protection Product'

ANE4940I Backing up object 'writer-name'
started successfully.
component 'component-name' using
Explanation: This message reports statistics or shadow copy.
System action: Processing continues. server. This is logged for informational purposes.
User response: None required. System action: Processing continues.
ANE4913I Backup for 'Data Protection Product'
finished.
ANE4941I Backup of object 'writer-name'
Explanation: This message reports statistics or component 'component-name' finished
information for a client operation performed to this successfully.
System action: Processing continues. information for a client operation performed to this
ANE4914I Total number of objects grew: Number User response: None required.
information for a client operation performed to this ANE4942E The file specification 'string' is invalid.
Explanation: The operating system indicated that the
System action: Processing continues. file specification is invalid. One possible reason is that
the file specification contains unrecognized characters.
Another possible cause is incorrect use of quotation
marks in the file specification.
User response: Enter a correct file specification as

described in the Using the Backup-Archive Client book

ANE4947E Error: virtual machine: 'vm-name' disk:
for the particular operating system. Ensure that the file
'disk-name' included by user, was not
specification contains valid characters. Verify correct
found.
use of quotation marks for specifications that contain
blanks spaces. If multiple file specifications are used, Explanation: The specified virtual disk does not exist
make sure that any use of quotation marks does not on the virtual machine.
cause the file specifications to be treated as a single file
specification.
User response: Use the "dsmc backup vm ..."
command with the -preview option to display a listing
ANE4943I Existing filespace name 'filespace-name'
of the disk labels which exist on the virtual machine.
has been renamed to 'filespace-name'
Check the spelling of the disk label and correct the disk
Explanation: This message reports statistics or label and then retry the 'backup vm' operation.
ANE4948E A specified virtual disk was not found
System action: Processing continues. on the virtual machine.
User response: None required. Explanation: You must specify a virtual disk label
name which exists on the virtual machine.
ANE4944I Virtual machine: 'vm-name' disk: System action: Processing stops.
'disk-name' is excluded by user.
User response: For a backup operation, use the "dsmc
Explanation: This message reports statistics or backup vm ..." command with the -preview option to
information for a client operation performed to this display a listing of the disk labels which exist on the
server. This is logged for informational purposes. virtual machine. For a restore operation, use the "dsmc
query vm ..." command with the -detail option to
display a listing of the disk labels which exist on the
User response: None required. virtual machine backup. Check the spelling of the disk
label and correct the disk label and then retry the
operation.
ANE4945I Virtual machine: 'vm-name' disk:
'disk-name' is included by user.
Explanation: This message reports statistics or 'disk-name' was excluded when the
information for a client operation performed to this backup was performed.
System action: Processing continues. information for a client operation performed to this
User response: None required. server. This is logged for informational purposes.
ANE4946W Warning: virtual machine: 'vm-name' User response: None required.
disk: 'disk-name' excluded by user, was
not found.
Explanation: The specified virtual disk does not exist 'disk-name' is excluded from restore by
on the virtual machine. user.
System action: Processing continues. Explanation: This message reports statistics or
User response: Use the "dsmc backup vm ..." information for a client operation performed to this
command with the -preview option to display a listing server. This is logged for informational purposes.
of the disk labels which exist on the virtual machine. System action: Processing continues.
Since the disk was specified to be excluded from the
backup, the backup will continue. However it is User response: None required.
possible that a disk will included in the backup which
was not desired, check the spelling of the disk label,
ANE4951I Total number of objects assigned:
and correct the disk label if an undesired disk is now
Number of objects
included in the backup operation.

ANE4952I Total number of objects inspected: ANE4958I Total number of objects updated:
Number of objects Number of objects
ANE4953I Total number of objects archived: ANE4959I Total number of objects failed: Number
Number of objects of objects
ANE4954I Total number of objects backed up: ANE4960I Total number of objects rebound:
Number of objects Number of objects
ANE4955I Total number of objects restored: ANE4961I Total number of bytes transferred:
Number of objects Number of bytes
ANE4956I Total number of objects retrieved: ANE4962I Average file size: Size
Number of objects
ANE4963I Data transfer time: Transfer time sec
ANE4957I Total number of objects deleted: Number
of objects

ANE4964I Elapsed processing time: Elapsed time ANE4970I Total number of objects expired: Number
of objects
ANE4965I Total number of subfile objects: Number
of objects ANE4971I LanFree data bytes: Number of bytes
ANE4966I Network data transfer rate: Transfer rate ANE4972W File server file-server-name has been
KB/sec upgraded to Data ONTAP version
'version.modifcation.submodification'. This
version does not support unicode file
names for snapshot difference
incremental backup. Upgrade to a
System action: Processing continues. version that supports unicode file names
as soon as possible.
Explanation: The file server has been upgraded from a
version that supports unicode file names for
ANE4967I Aggregate data transfer rate: Transfer rate incremental backup using snapshot difference to a
KB/sec version that does not. If you have upgraded from Data
Explanation: This message reports statistics or ONTAP version 7.3.3 (or later) to 8.0, you lose the
information for a client operation performed to this ability to back up files with unicode file names when
server. This is logged for informational purposes. performing snapshot difference incremental backup.
System action: Processing continues. System action: Processing continues. However, files
with unicode names are not backed up.
User response: Upgrade to a version that supports
unicode file names as soon as possible. If you have
ANE4968I Objects compressed by: Number% upgraded from Data ONTAP version 7.3.3 (or later) to
Explanation: This message reports statistics or 8.0, upgrade to 8.1 (or later). If it is not possible to
information for a client operation performed to this upgrade at this time, you can suppress this warning
server. This is logged for informational purposes. message by renaming the file space on the IBM
Spectrum Protect server and performing a snapshot
System action: Processing continues. difference incremental backup.
ANE4973E An error occurred accessing NTFS
ANE4969I Subfile objects reduced by: Number% security information for file 'filespace
namepath-namefile-name'
information for a client operation performed to this Explanation: An access denied error occurred while
server. This is logged for informational purposes. attempting to access NTFS security info rmation.
System action: Processing continues. System action: The object is skipped.
User response: None required. User response: See your system administrator or
bypass the failing check by using SkipNTSecu rity
option.

ANE4974E Error processing 'filespace ANE4980I Total Bytes Inspected:

namepath-namefile-name': a required NT
privilege is not held.
Explanation: The user account running IBM Spectrum server. This is logged for informational purposes.
Protect does not possess a required NT user right/pr
ivilege for performing the current operation.
System action: The object is skipped.
User response: Your system administrator has the
ANE4981I Deduplication reduction: Number%
authority to grant the needed privilege.
ANE4975I Total number of bytes processed:
Number of bytes
System action: Processing continues. ANE4982I Total objects deduplicated: Number of
objects
ANE4976I Total data reduction ratio: Number%
ANE4983I Files Deduplicated:
ANE4977I Total number of bytes inspected: bytes
ANE4984I Total bytes before deduplication: number
of bytes
ANE4978I Deduplication Reduction:
ANE4985I Session
ANE4979I Total Data Reduction:

ANE4986I Node ANE4990I @1%s

ANE4987E Error processing 'filespace ANE4991I Application Type Application Message Id

namepath-namefile-name': the object is in Application Message
use by another process
Explanation: This is a message sent by the application
Explanation: The specified file is being used by you are currently running with IBM Spectrum Protect.
another process. You tried to read from or write to a
System action: IBM Spectrum Protect logs the
file that is currently being used by another process.
application message.
User response: Refer to the documentation for the
User response: Ensure that the file is not locked by application that you are using.
another process. If the file is not locked, retry the
command.
ANE4992W Application Type Application Message Id
Application Message
ANE4988W File 'filespace namepath-namefile-name' is
Explanation: This is a message sent by the application
currently unavailable on server and has
you are currently running with IBM Spectrum Protect.
been skipped.
Explanation: You tried to restore or retrieve a file that
is currently not available from the IBM Spectrum
Protect server. This is most likely a temporary User response: Refer to the documentation for the
condition. application that you are using.
System action: IBM Spectrum Protect cannot restore
or retrieve the file. ANE4993E Application Type Application Message Id
Application Message
User response: Try to restore or retrieve the file again
after the file becomes available on the server. If the Explanation: This is a message sent by the application
problem persists, see your IBM Spectrum Protect you are currently running with IBM Spectrum Protect.
administrator for assistance.
namepath-namefile-name': the directory is User response: Refer to the documentation for the
in use by another process. All objects in application that you are using.
the directory and any of its
subdirectories are skipped. ANE4994S Application Type Application Message Id
Explanation: The specified directory is being used by Application Message
another process. You tried to read from or write to a Explanation: This is a message sent by the application
directory that is currently being used by another you are currently running with IBM Spectrum Protect.
process. The objects contained in the directory and its
subdirectories are not backed up. System action: IBM Spectrum Protect logs the
System action: Processing stopped for that directory.
If other files and directories were also specified in this User response: Refer to the documentation for the
backup, they are processed application that you are using.
User response: Ensure that you specified the correct

directory name, correct the permissions, or specify a ANE4995I @1%s @2%s @3%s
new location.If the directory name is correct, retry the Explanation: This message reports statistics or
backup when no process has exclusive use of the information for a client operation performed to this
directory. server. This is logged for informational purposes.

ANE4996I @1%s @2%s @3%s


namepath-namefile-name': file system quota
reached condition - no space left.
Explanation: No more files can be restored or
retrieved because the quota of the destination file
system has been reached.
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 this
object. Create some free space or increase the quota on
the destination file system before you retry the
operation. Another option is to restore or retrieve the
file to another file system.
ANE4998E Link information for file 'filename' could

not be obtained: access to the object is
denied.
Explanation: Access to the specified file link is denied.
You tried to read information for file link and you do
not have access permission for this object.
System action: Processing of System State stops.
persists, contactIBM technical support for additional
assistance.
ANE4999I The following message was too long to

log to the server: 'shortened message with
message number'
Explanation: The message text and inserts are too
large to send to the server in the available internal
buffer.
System action: The message number message is written
to the local client error log, then shortened and sent to
the server as a part of this message. The message is
reduced in length by substituting '...' in the middle of
the original message.
User response: The message referred to has been
shortened, but describes the error that occurred. See the
documentation for that message for more information.

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

Messages are listed in ascending numerical order. All elements of the message are
documented.
For a list of new, changed, and deleted server messages, see the following files in
the server installation directory:
Release_msg_chgs
This file contains all new, changed, and deleted messages from the
previous server version to the current version.
Maint_msg_chgs
This file contains all new, changed, and deleted messages from the current
server version to the current release.
These files are in the installation_directory\doc directory for Microsoft Windows

operating systems and the installation_directory/server/bin/ directory for all
other operating systems.
These files are also available in New, changed, and deleted server messages on the
IBM Spectrum Protect wiki.
System action: The server continues to initialize using

ANR0010W Unable to open message catalog for
the second locale.
language language. The default language
message catalog will be used. User response: To resolve the issue, complete the
following steps:
Explanation: The message catalog for the specified
language could not be found. v If you specified a LANGUAGE option in the server
options file, ensure that you specified a supported
System action: The server continues to initialize with locale and that the locale is installed on your system.
the default English message catalog.
v If you specified environment variables for the
User response: To resolve the issue, complete the system locale, ensure that you specified a supported
following steps: locale and that the locale is installed on your system.
v If you specified a LANGUAGE option in the server v Restart the server.
options file, verify that you specified a supported
language.
ANR0098W This system does not meet the
v If you specified environment variables for the minimum memory requirements.
system locale, ensure that you specified a supported
locale and that the locale is installed on your system. Explanation: The minimum memory required is 12
GB. 16 GB is required if you are using data
v Ensure that the IBM Spectrum Protect language
deduplication. At least 32 GB is needed for heavily
package for the specified language is installed on
used servers. Using 32 GB or more of memory
your system.
enhances performance of the IBM Spectrum Protect
v Restart the server. server database inventory.
If you plan to run multiple instances, each instance
ANR0011W Unable to set locale to first locale. Using requires the memory listed for one server. Multiply the
locale second locale for message memory for one server by the number of instances
formatting. planned for the system.
Explanation: The first locale could not be set.

ANR0099W • ANR0104E
Node replication processing requires additional

ANR0102E Source file(line number): Error error code
memory. Use a minimum of 32 GB of memory for node
inserting row in table "table name".
replication without data deduplication. Node
replication with data deduplication requires a Explanation: An internal error occurred when data
minimum of 64 GB of memory. You will require an was added to a server database table. This error
active log at least 64 GB in size to run replication. If message always accompanies another error message
replication and deduplication are both being used, an which provides more details about the error.
active log at least 128 GB in size is required.
System action: The activity that generated this error
System action: Server operation continues. fails.
User response: Increase the amount of memory on the User response: An error occurred when a row was
system. inserted into a server database table. Typically, this
error causes an error code value of 1 to be displayed.
An error code value of 1 indicates that the record being
ANR0099W This operating system is not supported.
inserted already exists in the database. This type of
Explanation: The system has detected one of the error might be caused by a timing issue with the server
following items: or a synchronization issue involving server processes,
v a release of the operating system that is not client sessions, or other server actions. Review the
supported activity log file to determine what operations were in
progress and were affected by this error. Try the
v the required maintenance for the operating system is operation again and change the timing so that it does
not installed not run with the same processes or actions as when the
error occurred.
See the software requirements section in the
information center for more details.
System action: Server operation continues. updating row in table "table name".
User response: See the software requirements section Explanation: An internal error occurred when data
in the information center and upgrade to a supported was updated in a server database table. This error
operating system. message always accompanies another error message
which provides more details about the error.
ANR0100E Source file(line number): Error error code System action: The activity that generated this error
creating table "table name". fails.
Explanation: An internal error has occurred in an User response: An error occurred when a row was
attempt to create a server database table. This message inserted into a server database table. Typically, this
always accompanies another error message and error causes an error code value of 2 to be displayed.
provides more detail about that error. An error code value of 2 indicates that the record being
System action: The activity that generated this error updated does not exist in the database. This type of
fails. error might be caused by a timing issue with the server
or a synchronization issue involving server processes,
User response: Contact your service representative. client sessions, or other server actions. Review the
activity log file to determine what operations were in
ANR0101E Source file(line number): Error error code progress and were affected by this error. Try the
opening table "table name". operation again and change the timing so that it does
not run with the same processes or actions as when the
Explanation: An internal error occurred when a server error occurred.
database table was being accessed. This error message
always accompanies another error message which
provides more details about the error. ANR0104E Source file(line number): Error error code
deleting row from table "table name".
fails. Explanation: An internal error occurred when data
was being removed from a server database table. This
User response: If the server or storage agent stops in error message always accompanies another error
response to a HALT command, you can ignore this message which provides more details about the error.
error message.
fails.
User response: An error occurred when a row was
deleted from a server database table. Typically, this
error causes an error code value of 2 to be displayed.

ANR0105E • ANR0111E
An error code value of 2 indicates that the record being

ANR0108E Source file(line number): could not start a
deleted does not exist in the database. This type of
new transaction.
error might be caused by a timing issue with the server
or a synchronization issue involving server processes, Explanation: An error occurred while attempting to
client sessions, or other server actions. Review the start a new transaction. Possibly there is not enough
activity log file to determine what operations were in memory.
progress and were affected by this error. Try the
operation again and change the timing so that it does
fails.
not run with the same processes or actions as when the
error occurred. User response: See the documentation for the
operating system about how to increase memory for an
application.
ANR0105E Source file(line number): Error setting
search bounds for table "table name".
ANR0109E Attempt number att_num Unable to load
Explanation: An internal error occurred when data
cryptography module from 'icc location'.
was being accessed from a server database table. This
error message always accompanies another error Explanation: An error occurred while attempting to
message which provides more details about the error. load the cryptography module.
System action: The activity that generated this error System action: The application will not start.
fails.
User response: Verify that the ICC cryptography
User response: Review the activity log file to directory is located in either the application root
determine what operations were in progress and were directory or the directory specified in the platform
affected by this error. Try the operation again and specific environment variable (the DSMSERV_DIR for
change the timing so that it does not run with the same Unix platforms or the Windows registry).
processes or actions as when the error occurred.
ANR0110E An unexpected system date has been
ANR0106E Source file(line number): Unexpected error detected; the server is disabled. Verify
error code fetching row in table "table the system date and use the ACCEPT
name". DATE command to establish the current
date as valid.
Explanation: An internal error occurred when data
was being accessed from a server database table. This Explanation: The server has noted that the current
error message always accompanies another error system date is suspect. It is earlier than the server
message which provides more details about the error. install date or has suddenly moved into the future by
30 days or more.
fails. System action: The server is disabled for client, server
and administrative access. Most server processes will
User response: Review the activity log to determine
not execute.
what operations were in progress and were affected by
this error. Try the operation again and change the User response: If the current system date is not valid,
timing so that it does not run with the same processes reset the date. Use the ACCEPT DATE command to
or actions as when the error occurred. establish the current date as valid on the server. After
executing this command, you can use the ENABLE
SESSIONS ALL command to enable the server for
ANR0107W Source file(line number): Transaction
sessions. Accepting an invalid date can cause any of the
transaction ID was not committed due to
following problems:
an internal error.
Premature deletion of data
Explanation: An internal error was detected during Excessive retention of data
transaction commit. This message is typically preceded Scheduling problems
by another error message which provides more details Event record problems
about the error. Password expiration problems.
fails. ANR0111E Command: The BEGINNODEID and
ENDNODEID are both required to be
User response: Review the activity log to determine
specified.
what operations were in progress and were affected by
this error. Try the operation again and change the Explanation: The BEGINNODEID and ENDNODEID
timing so that it does not run with the same processes are both required to be specified or neither of them are
or actions as when the error occurred. required.
Chapter 3. ANR messages 51

ANR0112E • ANR0118W
System action: The server fails the command. parallel commands before allowing the script to
continue.
User response: Reissue the command, specifying both
BEGINNODEID and ENDNODEID, or neither of them. User response: If you need to start more parallel
commands than the script limit allows, modify the
script to invoke multiple scripts in parallel, each of
ANR0112E Command: The specified
which can start multiple parallel commands, up to the
BEGINNODEID node id is greater than
script limit.
the ENDNODEID node id.
Explanation: Either the BEGINNODEID or the
ANR0116W The server script script name attempted
ENDNODEID is invalid because the value of the
to start more parallel commands than
BEGINNODEID is greater than the ENDNODEID.
are allowed for the server. The server is
System action: The server fails the command. limited to parallel command limit parallel
commands.
User response: Reissue the command, specifying the
ENDNODEID to be greater than the BEGINNODEID, Explanation: The server waits for all previous parallel
or both to be equal. commands started by the script to complete. When all
previous parallel commands are complete, the server
allows the script to continue. The script can attempt to
ANR0113E Command: The storage pool list specified start more parallel commands. If the limit is exceeded,
with the parameter parameter name the command will run serially.
includes storage pool storage pool name
more than once. System action: The server waits for all previous
parallel commands before allowing the script to
Explanation: The storage pool name specified has continue.
been specified more than once. The name occurs more
than once in the COPYSTGPOOLS list, more than once User response: Reduce the number of parallel
in the ACTIVEDATAPOOLS list, more than once in the commands or scripts that are running on the server at
PROTECTLOCALSTGPOOLS list, or it has been any one time.
specified in multiple lists.
System action: The command fails. ANR0117E The server contains stored data. Archive
data retention protection cannot be
User response: Reissue the command specifying changed.
unique storage pool names.
Explanation: The archive data retention protection
state cannot be changed while the server contains any
ANR0114E Command: The NUMBER parameter is backup, archive, or space-managed data.
required on this command. The current
default value is 0. System action: Processing continues.
Explanation: The NUMBER parameter is required for User response: In order to change the archive data
the FORMAT LFVOLUME COMMAND when the retention protection state, the server must contain no
LFVOLUMEFORMATCOUNT option is set to 0. backup, archive, or space-managed data. Either
re-initialize the server database, or delete all stored
System action: The command is not executed. data and try the command again.
User response: Either reissue the command with the
NUMBER parameter or else use the the SETOPT ANR0118W The client option client option is not
command to change the LFVOLUMEFORMATCOUNT valid and will not be sent to the client.
value. Use the INCLEXCL option instead.
Explanation: The client options INCLUDE and
ANR0115W The server script script name attempted EXCLUDE are not valid and have been replaced by the
to start more parallel commands than combined INCLEXCL. If INCLUDE and EXCLUDE are
are allowed for a single script. A single used in client option sets, use the INCLEXCL option
script is limited to parallel command limit along with the specific include or exclude option that
parallel commands. you want the clients to use.
Explanation: The server waits for all previous parallel System action: The option is ignored and is not sent
commands started by the script to complete. When all to the client. The server continues processing.
previous parallel commands are complete, the server
allows the script to continue. The script can attempt to User response: Client options INCLUDE and
start more parallel commands. EXCLUDE are not valid; use the INCLEXCL option
along with the specific include or exclude option that
System action: The server waits for all previous you want the clients to use.

ANR0119W The client option client option is not ANR0124W Object object name (object id hi ) for node
valid and will not be sent to the client. node name (node id), filespace filespace
Delete it from client option sets. name (filespace id) is retention protected
and can not be deleted.
Explanation: The client option is not supported by
this server and should be deleted from the client option Explanation: The specified object can not be deleted
set. because:
System action: The option is ignored and is not sent v Archive retention protection is enabled and the
to the client. The server continues processing. object's retention period has not elapsed, or
v The object is part of a deletion hold.
User response: Delete the option from the option set.
Check the documentation for a possible replacement for System action: Server operation continues.
the option.
ANR0120I Archive data retention protection is set

ANR0125W DELETE FILESPACE filespace name for
to state of archive data retention protection.
node node name contains retention
Explanation: The archive data retention protection protected data and cannot be deleted.
state has been set.
Explanation: The specified file space cannot be deleted
System action: Processing continues. because it contains one or more objects that must be
retained for one of the following reasons:
v Archive retention protection is enabled and the
object's retention period has not elapsed.
ANR0121E command is not allowed when archive
data retention is enabled.
System action: The file space is not deleted.
Explanation: The specified command is not allowed
when archive data retention protection is enabled on User response: None.
the server.
System action: Processing continues. ANR0126W DELETE VOLUME: Volume volume name
contains retention protected data and
can not be deleted.
Explanation: The specified volume cannot be deleted
ANR0122E command: A node cannot be assigned to
because it contains one or more objects that must be
a new domain when archive data
retained because of one of the following:
retention is enabled.
v Archive retention protection is enabled and the
Explanation: A previously defined node cannot be object's retention period has not elapsed.
assigned to a new domain when archive data retention
protection is enabled on the server.
ANR0127E command to another server is not

ANR0123E command: A device type of SERVER is
allowed when data retention protection
not allowed when archive data retention
is enabled on the target server.
is enabled.
Explanation: The specified command is not allowed
Explanation: The specified device type is not allowed
when data retention protection is enabled on the target
when archive data retention protection is enabled on
server.
the server.
ANR0128E Command: The list of storage pools

specified with the parameter parameter
name includes storage pool storage pool
name, which is already in use by another
storage pool.

ANR0129I • ANR0138E
Explanation: The specified storage pool name is

ANR0132E Diagnostic(ID): Memory allocation failed:
already being used to protect another storage pool. You
object object name, size size.
cannot protect multiple storage pools using the same
container-copy storage pool. Explanation: The server cannot obtain enough
memory to create the object named.
System action: The command fails.
User response: Reissue the command specifying
fails.
unique storage pool names.
User response: See the documentation for the
ANR0129I Database upgrade completed
application.
successfully.
Explanation: The requested database upgrade
ANR0133E Error loading module modname: error
operation completed successfully.
string
Explanation: The error specified by error string
User response: None. occurred when the server attempted to load module
modname
ANR0130E Diagnostic(ID): Server LOG space System action: Server operation continues, but the
exhausted. function provided by the module is not available.
Explanation: There is no space to write data to the User response: Refer to the error string and correct
server recovery log. the condition causing the load to fail.
fails. ANR0136I Table updating statistics performed
successfully for processed tables of total
User response: To increase the amount of log space tables.
available to the server, evaluate the directories and
filesystem assigned to the ACTIVELOGDIR, Explanation: The server periodically performs
ARCHIVELOGDIR, and ARCHFAILOVERLOGDIR. An maintenance on the database tables. The maintenance
out of log space condition may occur because the processing allows the database to update statistics
ACTIVELOGDIR location is full. Alternatively, an out determine how to best access a given table. The
of log condition may occur if the log files in the maintenance processing will periodically process all
ACTIVELOGDIR which are no longer active can not be tables for the server.
archived to the ARCHIVELOGDIR and
System action: Server operation continues.
ARCHFAILOVERLOGDIR locations. If necessary, a
larger ARCHIVELOGDIR or ARCHFAILOVERLOGDIR User response: No user action required.
can be specified by updating this option in the
dsmserv.opt file and then restarting the server.
allocating num rows database rows.
ANR0131E Diagnostic(ID): Server DB space
Explanation: An internal error has occurred in an
exhausted.
attempt to allocate storage for the requested number of
Explanation: There is no space to write data to the database rows indicated.
server database.
System action: The activity that generated this error fails.
fails.
User response: Contact your service representative.
User response: To increase the amount of database
space available to the server, an authorized
ANR0138E Value primary logs for number of
administrator can add database volumes by using the
primary logs is invalid.
DEFINE DBSPACE command. Once additional space
has been added for the database, the server database Explanation: The command has been issued with an
manager will automatically extend into that space and invalid number of primary logs.
use it.
System action: Server installation stops.
User response: Reissue the command with a valid
number of primary logs.

ANR0140I Command: success. Node node_id_1 is ANR0145E Command: failed. Node node_id_1 already
granted proxy authority to node has been granted proxynode authority to
node_id_2. node node_id_2.
Explanation: The command was successful. Explanation: The command failed because a proxy
relationship between the two nodes already exists.
System action: The server performs the command.
System action: The server fails the command, but
does not change the existing association.
ANR0141E Command: failed. Node node_id_1 was not
granted proxynode authority to node
node_id_2. ANR0146E Command: failed. Node node_id_1 was not
granted proxynode authority to itself.
Explanation: The command fails if either of the nodes
do not exist, or if the administrator issuing the Explanation: The command failed because a node
command does not have sufficient authority. cannot have a proxy relationship defined to itself.
System action: The server fails the command. System action: The server fails the command.
User response: Verify that both nodes exist and that User response: None.
the administrator has sufficient authority, then issue the
command again.
ANR0147E Command: failed. Proxy node authority
for node node_id_1 to node node_id_2 was
ANR0142I Command: success. Proxynode authority not revoked because node
for node node_id_1 has been revoked node_id_missing has not been defined to
from node node_id_2. the server.
Explanation: The command was successful. Explanation: The command failed because one of the
nodes has not been defined to the server.
System action: The server performs the command.
System action: The server fails the command.
User response: Verify that both nodes have been
defined to the server, and then issue the command
ANR0143E Command: failed. Proxynode authority
again.
for node node_id_1 has not been revoked
to node node_id_2.
ANR0148I Command: No proxy relationships were
Explanation: The command fails if the administrator
found.
issuing the command does not have sufficient authority.
Explanation: No proxy relationships were found.
System action: None.
User response: Check the help for the command and
verify that the administrator has either system or User response: None.
unrestricted policy authority; then issue the command
again.
ANR0149E Filespace filespace for node node_name
was deleted concurrently with the
ANR0144E Command: failed. Node node_id_1 was not command.
granted proxynode authority to node
Explanation: The command failed. The requested
node_id_2 because node node_id_missing
filespace was deleted concurrently with the command.
has not been defined to the server.
System action: The server will fail the command.
Explanation: The command failed because one of the
nodes has not been defined to the server. User response: Retry the command.
ANR0150E Failed to open object object_name. There
User response: Verify that both nodes have been
was an error decrypting the
defined to the server and then issue the command
password_type password.
again.
Explanation: The server could not open the object
specified due to the error encountered while decrypting
the password.

ANR0151W • ANR0158W
System action: The server will fail the related User response: Reissue the command specifying
command or action. unique active-data pool names.
User response: Reset the password using the
appropriate UPDATE command and retry the failing ANR0155E Command: The number of active data
command or action. pool names specified with the
ACTIVEDESTINATION parameter
cannot exceed 10.
ANR0151W Database manager fails to start. For
more information about the failure, Explanation: The maximum number of active data
issue the db2start command. pool names that you can specify with the
ACTIVEDESTINATION parameter is 10. You may enter
Explanation: The server was unable to start the
up to 10 unique names, separated by commas.
database manager. The following are possible causes:
v The database manager license key is invalid or System action: The command fails.
missing. User response: Reissue the command specifying up to
v The server instance password was changed. 10 unique active-data pool names separated only by
commas.
System action: Server initialization stops.
User response: For more information about the failure,
ANR0156E Command: The pool active data pool name
try to start the database manager by issuing the
with pool ID pool ID is not an active
db2start command, as in this example:
pool.
C:\Users\admin>db2start. You might receive messages
similar to the following ones: SQL1397N The DB2 Explanation: The storage pool specified is not an
service failed to logon. SQL1032N No start database active-data pool. Only active-data pools are allowed to
manager command was issued. SQLSTATE=57019. To be specified in the ACTIVEDESTINATION parameter.
determine the cause of the failure, evaluate recent
changes to the server and review the system error logs.
Information can be found in the DB2 diagnostic log file. User response: Reissue the command specifying ten or
If you are starting a DB2 server on a Windows fewer active-data pool names.
platform, you can set the logon account for a DB2
service by using the Services dialog box from the
Control Panel. ANR0157W Database operation table operation for
table table name failed with result code
op code and tracking ID: id.
ANR0152I Database manager successfully started.
Explanation: An error occurred during the specified
Explanation: The server was successfully able to start table operation for the table indicated.
the database manager.
System action: The server operations continue. fails.
User response: None. User response: If there were no operational failures as
a result of issue, then this was anticipated and the
server was able to continue appropriately. If this
ANR0153I Database manager already running.
resulted in a failure for a client session or server
Explanation: The server database manager is already process, this information is needed to help diagnose the
running. issue. In the even of a failure, please contact your IBM
service representative for further assistance.
System action: The server continues startup.
ANR0158W Database operation table operation for
table table name failed with operation
ANR0154E Command: The active data pool list that code op code and tracking id tracking
you specified with the number. The data for column column
ACTIVEDESTINATION parameter number is: column data.
includes active data pool active data pool
Explanation: An error occurred during the specified
name that is a duplicate. All names must
table operation for the table indicated.
be unique.
Explanation: You may enter up to 10 unique active
fails.
data pool names specified with the
ACTIVEDESTINATION parameter. User response: If there were no operational failures as
a result of issue, then this was anticipated and the

ANR0159E • ANR0166I
server was able to continue appropriately. If this

ANR0162W Supplemental database diagnostic
resulted in a failure for a client session or server
information: dbReturnCode:dbState:dbCode
process, this information is needed to help diagnose the
(dbErrorMessage).
issue. In the even of a failure, please contact your IBM
service representative for further assistance. Explanation: The dbReturnCode, dbState, and dbCode are
displayed as supplemental information. This
information should be used in conjunction with any
ANR0159E Diagnostic(ID): Database deadlock
other database error or warning messages issues to
detected on DB2 Statement Handle.
assist with diagnosing a given issue.
Explanation: The database server detected a deadlock
situation and rolled back the outstanding work on this
fails.
statement handle. When server processes encounter a
database deadlock, they usually reattempt the work User response: None. This is supplemental
that was in progress when the deadlock was information corresponding to another database error or
encountered. Not all processes can explicitly try an warning message issued.
operation again. For example, migration and
reclamation will eventually be tried again. However,
ANR0163E Diagnostic(ID): Database insufficient
something such as a delete volume run in a macro will
memory detected on DB2 Statement
only be tried again if the delete command is reissued
Handle.
either in the macro or the command line.
Explanation: The database server detected an
System action: The work being done on the statement
insufficient memory condition and rolled back the
handle is rolled back. Some processes will attempt to
outstanding work on this statement handle.
retry the request. Others will just stop. Server operation
continues. System action: The work being done on the statement
handle is rolled back. Server operation continues.
User response: If a process can retry (like migration),
then monitor the re-try attempt to see if it succeeds or User response: See the documentation for the
not. If the process or command is not able to retry on operating system about how to increase memory for an
it's own, then reissue the command or macro that application.
caused the action to occur.
ANR0165I Inventory file expiration started
ANR0160I Displaying segment segment number of processing for node nodename, filespace
total segments for client object object filespace name, copygroup copygroup and
identifier with text: object name. object type type.
Explanation: Display a client object, such as a file or Explanation: Inventory file expiration processing
directory, that uses a long fully qualified name. The started processing for the node name and filespace name
name is displayed in smaller segments until the entire indicated. For this node name and filespace name the
name is shown. The segment numbers are incremented indicated copygroup and object types are currently
from 1 to N until all the segments for this object name being evaluated.
are displayed.
System action: Inventory file expiration continues.
System action: The fully qualified name for this object
is displayed. User response: This message is for informational
purposes only and is only displayed if the expiration
User response: None. processing is executed with QUIET=NO.
ANR0161I Displaying segment segment number for ANR0166I Inventory file expiration finished
message insert insert identifier with text processing for node nodename, filespace
segment text. filespace name, copygroup copygroup and
object type type with processing
Explanation: Display a segment of a message insert
statistics: examined examined, deleted
that was too long to be displayed within the specified
deleted, retrying retrying, failed failed and
message. There may be one or more segments
skipped skipped.
displayed for a given message insert.
Explanation: Inventory file expiration processing
System action: The entire message insert segment is
finished processing for the node name and filespace name
displayed.
indicated. For this node name and filespace name the
User response: None. indicated copygroup and object types were evaluated.
And the ending statistics show the number of objects
examined, deleted, retried, skipped and those that
failed to be processed.

ANR0167I • ANR0173I
System action: Inventory file expiration continues. halt. Follow the instructions indicated in any associated
messages, then start the server. If the server still cannot
User response: This message is for informational
be started, manually issue the DB2 RESTART DB
purposes only and is only displayed if the expiration
command, then attempt to start the IBM Spectrum
processing is executed with QUIET=NO.
Protect server again.
ANR0167I Inventory file expiration process process

ANR0171I Diagnostic(ID): Error detected on DB2
ID processed for minutes minutes.
Statement Handle, database in evaluation
Explanation: Server expiration processing ran for the mode.
indicated number of minutes.
System action: None. encountered an error on the database and will take
action to determine the type of error and whether or
User response: None. not it can recover from the error.
System action: Server processing continues.
ANR0168I Analyst authority for administrator
admin name will be ignored. Analyst User response: This is an information message. As the
authority is not supported on this IBM Spectrum Protect server attempts to resolve the
server. error, it might issue other messages. Follow the
instructions indicated in any associated messages.
Explanation: Analyst authority is not supported for
servers at V6.1 or later.
ANR0172I Diagnostic(ID): Error encountered
System action: The operation continues. performing action action.
User response: None. Explanation: The IBM Spectrum Protect server
encountered an error performing the specified database
ANR0169E An unexpected error has occurred and action. This error caused the action to fail and
the IBM Spectrum Protect server is prevented the server from being able to continue.
stopping. System action: Server processing terminates, the
Explanation: The IBM Spectrum Protect server requested action fails.
encountered an error from which it cannot recover, and User response: Review other messages issued to
the server is halting. Other messages will be issued determine the actual error and then take steps to
along with this message indicating the specific error remedy that failure before retrying the operation.
conditions which have occurred.
System action: The server halts. ANR0173I The database failed action action because
User response: Follow the instructions indicated in of insufficient system memory available.
any associated messages, then start the server. Explanation: The IBM Spectrum Protect server
encountered an error while performing the specified
ANR0170E Diagnostic(ID): Error detected on DB2 action. Specifically, the server database did not have
Statement Handle, database restart sufficient memory to communicate with the server
required. database or was unable to acquire the memory needed
for the server buffer pools.
encountered an error on the database and needs to System action: Server processing terminates, the
issue a DB2 RESTART DB to the database manager. All requested action fails.
connections to the database server are severed, and User response: In most cases, this indicates a lack of
uncompleted operations are aborted. The IBM available resources on the system. This may be a lack
Spectrum Protect server will then restart the database of physical resources or it may be an environment
and attempt to continue. If the database manager setting that prevents the server from having access to
cannot be restarted, the IBM Spectrum Protect server the needed resources. For instance, on Linux systems,
will halt. Other messages may be issued along with this this may be caused by the SHMMAX value (maximum
message indicating the specific error conditions which allowed shared memory) being set too low. On Linux,
have occurred. this can be viewed using the command "ipcs -l".
System action: The server continues, or if it cannot Similarly, for Linux, this value can be increased using
restart the database, it halts. the command "sysctl -w kernel.shmmax=nnn" where
nnn is the new maximum memory value to assign to
User response: If the server is able to recover, no be used for shared memory. As a general
action is needed, except to restart operations that were recommendation, this value should be set to
aborted. However, if the server cannot recover, it will approximately 1.25 GB or higher depending upon the

actual physical memory (RAM) available on that

ANR0186E There is insufficient authority to start
system.
Explanation: If the server is starting, then the user ID
ANR0174E Diagnostic(ID): Maximum DB2
under which the dsmserv process is running does not
connections reached on DB2 Handle.
have authority to start the database manager. If the
Explanation: There are no more available connections server is running, it does not have sufficient authority
to the server database. to perform the server operations.
System action: The activity that generated this error System action: The server process ends, and the
fails. server stops if it is running.
User response: To increase the number of database User response: Ensure that the user ID under which
connections available to the server, the DB2 the server is running is authorized to start the database
administrator can modify the IDBACK parameter in the manager. Take the following actions:
DSNzPARM settings. v Log in to the user ID for your IBM Spectrum Protect
instance and start the server.
ANR0175E Diagnostic(ID): Space exhausted for one – To run the server using the root user ID on a
or more of the following: DB, LOG, or UNIX system, add the root user ID to the primary
instance directory. group of the IBM Spectrum Protect instance user
ID.
Explanation: The space assigned to the server
database, the recovery log, or instance directory has – Or, to run the server using the instance user ID on
been exhausted. a UNIX system, when using the automatic start,
specify the -u option when you start the server.
System action: The server terminates.
User response: Review the filesystems or other space ANR0187E Database db name was not found.
assigned to the server for the database, recovery log or
instance directory. If the space assigned to the database Explanation: The server attempted to open the
is full, restart the server and add additional database database, but it was not found by the database
space using the EXTEND DBSPACE command or use manager. If this occurs immediately after formatting a
the DSMSERV EXTEND DBSPACE utility. If the server new database, it could mean the format operation
ACTIVELOGDIR is full, update this server option to a failed.
new location that has space available for the server to System action: The server process ends.
use for logging changes to the database. If the server
instance directory is full, remove unneeded files or else User response: Ensure that you format the database
extend this filesystem. before starting it the first time. Ensure that all database
and log directories are online and available.
Please note that the server should be configured with
the database, activelog, and archivelogs using different
directories and storage devices. For example, if the ANR0188E Fail to start the database manager.
database and activelog are configured to use the same Database manager license not found
directory and underlying storage device, this may Explanation: Could not find database manager license.
adversely impact performance. This may also
compromise the server's ability to manage the database System action: The server process ends.
and active log space effectively. Similarly, the server's User response: Contact your service representative.
instance directory should also be monitored and
managed with some amount of space available. The
server instance directory is used to record and log some ANR0189E Fail to start the database manager.
server and database actions. Database manager license has expired
Explanation: Database manager license has expired.
ANR0185E The data in primary storage pool name can
System action: The server process ends.
not be copied to active data pool name.
The active-data pool is not defined to a User response: Contact your service representative.
domain.
System action: The command fails. ANR0190I Inventory file expiration started
processing node node name for backup
User response: Define the active-data pool to a
sets.
domain using the ACTIVEDESTINATION parameter on
either the DEFINE DOMAIN or UPDATE DOMAIN Explanation: Expiration processing is currently
command. evaluating information for backup sets for the node
specified.

System action: Inventory file expiration continues.

ANR0197E Removal of extraneous database entries
User response: This message is for informational for volume volume name failed due to
purposes only and is only displayed if the expiration contention with other server processes
processing is invoked with QUIET=NO. or activities.
Explanation: The server was not able to remove
ANR0191I Inventory file expiration finished extraneous database entries for the specified volume.
processing node node name for backup This was due to contention with another server process
sets with processing statistics: examined or activity.
examined, deleted deleted, retrying
System action: System operation continues and this
retrying, and failed failed.
volume still has extraneous database entries.
Explanation: Expiration processing has finished
User response: It is possible that future server
processing backup sets for the node specified.The
activities or processes will select this volume and
ending statistics show the number of objects examined,
attempt to repair it. If this occurs and the future
deleted, and those that failed to be processed.
attempt is successful, no further action is needed. The
System action: Inventory file expiration continues. server administrator should review the activity log for
the time that the repair was attempted and try to
User response: This message is for informational determine what caused the contention. If you are
purposes only and is only displayed if the expiration unable to determine the cause of the contention of the
processing is invoked with QUIET=NO. problem persists, please contact your service
representative for additional assistance.
ANR0193E The REPAIR EXPIRATION TYPE=type
command cannot be issued from the ANR0198E Removal of extraneous database entries
server console. for volume volume name failed.
Explanation: The specified REPAIR EXPIRATION Explanation: The server was not able to remove
command was issued from the server console. This extraneous database entries for the specified volume.
command cannot be issued from the server console
because the administrator must be prompted to System action: System operation continues and this
continue processing the command. volume still has extraneous database entries.
System action: The server ignores the command and User response: The server administrator should
continues processing. review the activity log for the time that the repair was
attempted and try to determine the cause of the failure.
User response: Issue the command from an If you are unable to determine the cause of the
administrative client. contention of the problem persists, please contact your
service representative for additional assistance.
ANR0195W Attempting to remove extraneous
database entries for volume volume name. ANR0199W Not possible to repair volume volume
Explanation: The server is attempting to remove name due to other database references to
extraneous database entries for the specified volume. this volume.
System action: IBM Spectrum Protect will attempt to Explanation: The server was not able to remove
remove the extraneous database entries for this volume. extraneous database entries for the specified volume
because other database references to this volume exist.
User response: Review the completion messages for
this volume to determine if the removal of the System action: System operation continues.
extraneous database entries was successful or if an User response: The volume repair operation for this
error was encountered. volume is not able to take any action because other
unexpected database references to this volume exists.
ANR0196I Removal of extraneous database entries For additional assistance contact your IBM service
for volume volume name was successful. representative.
Explanation: The server successfully removed

extraneous database entries for the specified volume. ANR0200E PROTECT STGPOOL process process ID
failed due to insufficient space in
System action: System operation continues and future destination storage pool.
operations on the specified volume should work
normally. Explanation: The destination stgpool had insufficient
space.
User response: The server successfully repaired the
specified volume. System action: The indicated process ends.

ANR0201I • ANR0211W
User response: Make more space available in the

ANR0206E Command name process process ID failed
storage pool and restart the operation.
due to insufficient space in destination
storage pool.
ANR0201I The access mode for storage pool
Explanation: The indicated process failed because the
directory Directory Name in storage pool
destination storage pool has insufficient space.
Pool Name was changed to Access Mode.
System action: The indicated process ends.
Explanation: The access mode is changed for the
specified storage pool directory. User response: Make more space available in the
storage pool and reissue the command.
System action: Client nodes and server processes
cannot access the storage pool.
ANR0207W Command name skipped object ID Object
User response: To change the access mode, issue the
ID because one or more extents are
UPDATE STGPOOLDIR command.
marked damaged.
Explanation: During command processing, the server
ANR0202I The parameter name has been set but the
skipped an object because a data extent (chunk) was
changes will not be effective until the
marked damaged.
next start
Explanation: The Database configuration has been
updated but has not taken effect. This setting will take User response: None.
effect on next server start.
System action: This server parameter does not take ANR0211W The shredding process was unable to
effect until next start. The server continues processing. shred a deleted file.
User response: None. Explanation: The shredding process encountered an
error that prevents a file from being shredded. See
previous error messages for more details.
ANR0203E MOVE CONTAINER process process ID
terminated for container name - System action: The file is not shredded. The next time
insufficient space in directory directory the shredding process runs, it will attempt to shred the
name. file again.
Explanation: During MOVE CONTAINER processing, User response: If there are files that can not be
the server could not allocate sufficient space in the shredded due to integrity or corruption errors or
storage pool directory for the container. unrecoverable I/O errors, run the following commands:
System action: Server processing continues. 1. Set for manual shredding, if not already done:
SETOPT SHREDDING MANUAL
2. Run manual shredding with IOERROR parameter:
storage pool, and re-issue the MOVE CONTAINER
SHRED DATA IOERROR=SHREDSUCCESS
command.
3. Reset for automatic shredding, if desired: SETOPT
SHREDDING AUTOMATIC
ANR0204I The container state for container name is
updated from previous state to current If an entire disk volume has failed and all files on it are
state. no longer accessible, run the following commands:
Explanation: The server updates the container state. 1. Set the volume access to destroyed: UPDATE
VOLUME volname ACCESS=DESTROYED
2. Delete the volume and the data: DELETE VOLUME
User response: Review the other messages issued to volname DISCARDDATA=YES
determine if further action is required.
3. Set for manual shredding, if not already done:
SETOPT SHREDDING MANUAL
ANR0205W Command name skipped data extent ID 4. Run manual shredding with IOERROR parameter:
Chunk ID because it is marked damaged. SHRED DATA IOERROR=SHREDSUCCESS
Explanation: During command processing, the server 5. Reset for automatic shredding, if desired: SETOPT
skipped a chunk that was marked damaged. SHREDDING AUTOMATIC


that the environment is set up correctly. The instance

ANR0212E Unable to read disk definition file file
directory is generally the directory from which you
specification.
formatted the database, or, if on UNIX, have specified
Explanation: At startup, the server cannot read the with the -i command-line option.
indicated file in order to obtain a list of disk volumes
When the ID of the database that is opened does not
to mount.
match the ID that is stored in the database ID file
System action: Server initialization fails. (dsmserv.dbid), the server will not start. Use the -S
(skip DB ID check) parameter after deleting the
User response: Use a text editor to recreate the file; it
dsmserv.dbid file. After the initial use of the -S
should contain one line with the name of a single log
parameter in a restore scenario, the server creates a
or database volume. Then restart the server.
new dsmserv.dbid file in the instance directory.
ANR0222E Error action disk definition file file

ANR0228S Error errno opening the database ID file
specification.
for server startup.
Explanation: An error occurred creating or changing
Explanation: The server's database ID file
the disk definition file.
(dsmserv.dbid) could not be opened. The errno
System action: None. indicates the reason for the failure.
User response: Attempt to determine the cause of the System action: The server does not start.
write error and correct it.
User response: Ensure that you are starting the server
from the correct instance directory, and that the
ANR0225S Invalid use of the -S command-line dsmserv.dbid file has the correct ownership and
option. permission. If the file is empty, erase the file, and
restart the server with the -S command-line option to
Explanation: The -S option cannot be specified on the generate a new database ID file.
command line if the database ID file (dsmserv.dbid) is
intact. This option is to be used only if the ID file does
not exist. ANR0229W Server is unable to add entries to the
Activity Log. Console messages will not
System action: The server does not start. be logged until database access is
User response: Start the server without specifying the available.
-S command-line option. Explanation: The process that monitors the default
(console) output stream and maintains the activity log
ANR0226S The database ID file could not be found cannot update the activity log. The error is due to the
for server startup. inability of the server to access the server database.
Explanation: The server's database ID file System action: The server does not update the activity
(dsmserv.dbid) could not be found. This file is created log. The activity log will continue to run and attempt
when the database is formatted, is stored in the to recover from this situation.
directory from which the format is performed, and is User response: Access to the server database is
required for normal server operation. temporarily unavailable. The server database manager
System action: The server does not start. will attempt to recover from this situation and
reestablish access to the server database. When access
User response: Ensure that you are starting the server to the server database is reestablished, the activity log
from the correct instance directory, and that the processing will continue. If the server database access
dsmserv.dbid file exists and can be read. If no fails to be reestablished, additional messages will be
dsmserv.dbid file exists, restart the server with the -S issued providing more information.
option to create a new database ID file.
ANR0236E Fail to start the database manager due to

ANR0227S Incorrect database opened. Server an I/0 error. Check for filesystem full
cannot start. conditions, file permissions, and
Explanation: The ID of the database opened does not operating system errors.
match the ID stored in the database ID file Explanation: The IBM Spectrum Protect server
(dsmserv.dbid). encountered an I/O error while attempting to start the
System action: The server does not start. database manager.
User response: Ensure that you are in the proper System action: The server process ends.
instance directory for the database being opened, and User response: Review the filesystems assigned to the

server for the database and recovery log.

ANR0239E The DB2 instance name instance name
may not be valid or is not configured
ANR0237E Fail to start the database manager. An properly. The return code was sqlcode
unexpected system error occurred.
Explanation: IBM Spectrum Protect Server attempted
Explanation: An unexpected system error occurred. to connect using the database instance set by the
DB2INSTANCE environment variable, but the attempt
Some common reasons for this error are: failed.
v The system name where you ran the server has been
changed System action: The server is not started because the
database instance is not valid.
v The system date and time is set incorrectly
User response: Verify that the database instance exists
System action: The server process ends. and that it is configured properly. You can list DB2
User response: Contact your service representative. instances by issuing the db2ilist command from the
instance directory, under the DB2 installation directory.
Example: c:\Program Files\tivoli\tsm\db2\instance\
ANR0238E A database recovery task is prohibiting db2ilist
activation of db name with sqlcode
dbCode.
ANR0264E A database file IO error is prohibiting
Explanation: While attempting to activate the database activation of db name with sqlcode
an error occurred because the database was busy dbCode.
performing a BACKUP, RESTORE or was in
ROLLFORWARD pending state. Examine the sqlcode to Explanation: While attempting to activate the database
determine the condition that is preventing the database an IO error occurred when processing a database file.
from activating. The following sqlcodes are most likely The problem may have occurred in one of the
to occur during the activate database step and will following situations: The system cannot open, read
prevent the server from starting. SQLE_RC_BKP_PEND from, or write to a database file. The system cannot
( -1116 ) indicates a database BACKUP is pending and create the database because an error occurred while the
must complete prior to activating the database. Once system was creating a database file or a directory for
the database BACKUP is complete,the database can be the database. The system cannot drop the database
activated by starting the server. because an error occurred while the system was
SQLE_RC_ROLLFWD_PEND ( -1117 ) indicates a deleting a database file or a directory for the database.
database Roll Forward operation is pending and must The system cannot create the database because an
complete before activating the database. After the Roll interrupt was received while the system was creating
Forward recovery step is complete, the database can be or deleting a database file or a directory for the
activated by starting the server. database. The system cannot locate the database
SQLE_RC_BKP_INPROG ( -1118 ) occurs when an subdirectory or database configuration file during
attempt to activate the database fails because a connect. Problem causes are ordered in terms of their
database BACKUP was in progress. Prior to activating frequency of occurrence: A log file cannot be found in
the database, it is necessary to rerun database BACKUP. the active log path directory. There may be a problem
Once the database BACKUP completes successfully, the with the database directory the operation is being
database can be activated by starting the server. attempted on. There may be inadequate disk space to
SQLE_RC_RST_INPROG ( -1119 ) shows that a complete the operation. The database cannot be used.
database RESTORE was in progress when the database System action: The server is not started because the
failed to activate. The RESTORE database must be database cannot be activated.
restarted and allowed to complete successfully before
activating the database. Once the database RESTORE in User response: Appropriate responses for the problem
complete, the database can be activated by starting the causes described above are: To verify if a log file is
server. SQLE_RC_BR_INPROG ( -1120 ) means that missing, check the db2diag.log for the presence of a
either a database BACKUP or RESTORE must complete logging error (return code contains SQLO_FNEX). If
before activating the database. Ensure that either a present, this error will contain the name of the missing
BACKUP or RESTORE operation completes successfully log file. Ensure that the file is located in the active log
before activating the database. path directory. If the file cannot be located, restore and
roll-forward the database to an earlier point in time
System action: The server is not started because the referenced in a log file preceding the missing log file
database cannot be activated. (use a timestamp that is earlier than that of the missing
User response: See message explanation for more file). There may be a problem with the database
information. directory. Check the integrity of the directory. Examples
of potential problems include: permissions issues,
mount point problems, corruption. Increase filesystem
size.

ANR0273W • ANR0297I
ANR0273W Not initializing library library name ANR0278S The database manager cannot create the
because the library is set offline . database because of a virtual memory
shortage.
Explanation: The External Library is set offline. It will
not be used for new transactions until it is set online System action: Server operation stops.
again.
User response: Stop other applications running on the
System action: This server skips the initialization of system, especially those that use large amounts of
the library. The server continues processing. shared memory.
User response: Refer to the UPDATE PATH command
for details on changing the online option. ANR0279S Database manager failed to start due to
incorrect service logon credentials.
ANR0274E Attempt to access library library name Explanation: The server was unable to start the
failed, because the library is set offline. database manager because the database manager
service credentials (userid and/or password) are
Explanation: The Library is set offline. It will not be
incorrect.
used for new transactions until it is set online again.
System action: Server initialization stops.
System action: This mount fails.
User response: Correct the logon properties for the
User response: Refer to the UPDATE PATH command
database manager service by using the Services dialog
for details on changing the online option.
box from the Control Panel.
ANR0275I Detected schema change for table table,

ANR0293I Reorganization for table table name
attempting to reconcile.
started.
Explanation: The schema for the table referenced does
Explanation: The server is performing an online
not match the server definition for this table. The
reorganization for the table referenced.
schema difference for this table will be reconciled.
System action: The server will continue to operate.
System action: Server startup continues if the schema
difference was successfully reconciled. Server startup User response: Monitor the available log space in the
will fail if the schema reconciliation failed. active log and archive log storage paths. If the log
space available to the filesystem begins to fill up, then
User response: The schema for this table will attempt
perform a BACKUP DATABASE command with the
to be reconciled. Specifically, the server will try to
TYPE=FULL parameter in order to initiate pruning of
modify the table in the database to match the schema
the archive log space.
that was expected. A message will be issued indicating
the success or failure of the schema reconciliation.
ended.
ANR0276I Schema reconciliation for table table
succeeded. Explanation: The server online reorganization for the
table referenced has ended.
Explanation: The schema differences for this table
were successfully reconciled. System action: The server will continue to operate.
System action: Server operation continues. User response: Review the available log space in the
active log and archive log storage paths. If the log
User response: None
space available to the filesystem has to filled up or is
close to filling up, then perform a BACKUP
ANR0277E Schema reconciliation for table table DATABASE command with the TYPE=FULL parameter
failed. in order to initiate pruning of the archive log space.
Explanation: The server was unable to reconcile the

schema differences for the indicated table. ANR0297I A full database backup might be
required. The last log number used is
System action: Server operation terminates. last log used and the first log number
User response: Contact your IBM service used is first log used. The log file size is
representative. log file size megabytes. The maximum log
file size is maximum log file size
megabytes.
Explanation: When the log space used since the last
database backup exceeds the maximum log file size,

ANR0298S • ANR0319W
either a full database backup is required, or the

ANR0316W A full backup for database DB Name
maximum log file size must be increased.
cannot be started. This backup is
System action: None. required.
User response: None. Explanation: An automatic full backup was attempted

for this database. However, the device class for
database backups has not been specified.
ANR0298S Authority is insufficient to access the
database. System action: The database backup operation is not
started.
Explanation: If the server is starting, then the user ID
under which the dsmserv process is running does not User response: Issue the SET DBRECOVERY
have sufficient authority to access the database. If the command to specify the default device class for
server is running and a server operation failed, then the automatic database backups. Then, issue the BACKUP
user ID does not have sufficient authority to perform DB command and specify TYPE=FULL to back up the
the operation. database.
System action: If the server is starting, the dsmserv
process ends. If the server is running, the server stops. ANR0317I Reorganization of indices for table table
name started.
User response: Ensure that the user ID under which
the server is running is either the instance user ID, or is Explanation: The server is performing an online
authorized to access the database. reorganization for the indices of the referenced table.
ANR0299I A full database backup will be started.
User response: Monitor the available log space in the
The archive log space used is archive
active log and archive log storage paths. If the log
log% and the archive log space used
space available to the filesystem begins to fill up, then
threshold is arch log threshold%.
perform a BACKUP DATABASE command with the
Explanation: When the archive log space used exceeds TYPE=FULL parameter in order to initiate pruning of
the threshold, a full database backup will be started. the archive log space.
ANR0318I Reorganization of indices for table table
User response: None. name ended with sqlCode dbCode.
Explanation: The server online reorganization for the
ANR0314W Recovery log usage exceeds utilization indices for the table referenced has ended.
percentage % of its assigned capacity.
Explanation: This message is issued to notify the
administrator that the server recovery log utilization User response: Review the available log space in the
exceeds 90% or more of its assigned capacity. active log and archive log storage paths. If the log
space available to the filesystem has to filled up or is
System action: Server operation continues. close to filling up, then perform a BACKUP
User response: DATABASE command with the TYPE=FULL parameter
in order to initiate pruning of the archive log space.
v If the server is operating in NORMAL log mode,
depending upon the size of your recovery log, add
recovery log volumes, or extend the recovery log, or ANR0319W The file system for the database archive
both, before it fills completely. Refer to the DEFINE log has insufficient free space.
LOGVOL, and EXTEND LOG commands for more
information on these operations. Explanation: The usage of the file system for the
database archive log has exceeded the
v If the server is operating in ROLLFORWARD log ARCHLOGUSEDTHRESHOLD. Space is used by files
mode: that are not database archive log files, and the
– backup the database, or BACKUP DB command cannot free space in the
– define a database backup trigger if one is not filesystem..
already defined, or System action: The server will continue to operate.
– lower the database backup trigger if one is
defined User response: Create sufficient free space on the file
system so that usage does not exceed the
Refer to the DEFINE DBBACKUPTRIGGER or ARCHLOGUSEDTHRESHOLD.
UPDATE DBBACKUPTRIGGER commands.

to read data over the LAN, consider updating the

ANR0320W Storage agent storage agent is not able to
DATAREADPATH setting for this node by using the
use device class device class for storage
UPDATE NODE command.
pool storagepool for LAN-Free data
movement operations.
If this was an operation performed by an agent node
Explanation: The storage agent referenced is not able with proxy node authority to a target node, the session
to perform LAN-Free data movement operations using failed with a protocol error. The operation was
this storage pool and device class. The storage agent is attempted by a version 5.3 or higher client and server,
back-level and is not able to support LAN-Free but the storage agent is not able to support this
operations using this device class. operation. To allow an agent node to perform
operations for a target node, the storage agent must be
System action: LAN-Free data movement operations
upgraded to version 5.3.0 or later.
are not performed. The operations are either sent via
the LAN or else proxied by the storage agent directly
to the server. ANR0322E The NEWSTGPOOL parameter is not
valid for deduplicated volume volume
User response: In IBM Spectrum Protect version 5.3, a
name.
change was made to the way the FILE and device
classes are supported. This change prevents back-level Explanation: The volume contains one or more
storage agents from being able to use these device deduplicated objects and must be restored to the
classes. The storage agent should be upgraded to the original storage pool.
same version and release as the server. Until the
storage agent is upgraded, any LAN-Free data System action: The operation is not allowed.
movement operations that are attempted will be done User response: To restore the volume to the original
using the LAN. storage pool, reissue the RESTORE VOLUME command
without the NEWSTGPOOL parameter.
ANR0321W Storage agent storage agent name at
version storage agent VRMF does not ANR0323E The NEWSTGPOOL parameter is not
support operation operationName, valid for deduplicated storage pool pool
although the server server name at name.
version server VRMF can support it.
Explanation: The storage pool contains deduplicated
Explanation: The storage agent is at an earlier version objects and must be restored to the original storage
than the server and is not able to use advanced pool.
functions that were requested by a client.
System action: The operation is not allowed.
System action: The operation is not allowed.
User response: To restore the storage pool to the
User response: The storage agent must be upgraded original storage pool, reissue the RESTORE STGPOOL
to a version, release, and level that supports this command without the NEWSTGPOOL parameter.
operation. Typically, the problem is that the storage
agent and server are not at the same version and
release. For example, if the server is version 5.3.0.0 and ANR0324E command: Replication parameters cannot
the storage agent is version 5.2.3.0, the storage agent be used with the TYPE=SERVER
needs to be upgraded to version 5.3.0.0 to perform the parameter.
requested function. System action: The command failed.
If this was a restore or retrieve operation and the client User response: Reissue the command without
node DATAREADPATH setting was ANY or LANFREE, replication parameters. Replication parameters include
the server will override this to be LAN only. This will REPLSTATE, REPLMODE, BKREPLRULEDEFAULT,
cause the operation to fail on the storage agent and ARREPLRULEDEFAULT and SPREPLRULEDEFAULT.
message ANR0416W to be issued. Retry the operation
after performing one of the following actions:
ANR0325E command: Operation is not allowed
v Halt the storage agent, upgrade the storage agent
because node nodename is a replica.
program, and then restart the storage agent.
v Set the ENABLELANFREE client option to NO, and Explanation: The specified node is a replica of a node
then restart the client on another server, created using the REPLICATE NODE
command.
If this was a no-query restore operation, the data was You can restore or retrieve data from this node, but you
not restored by the storage agent using LAN-Free data cannot store new data or alter existing data in any way.
transfer. If the client node is allowed to read data over
the LAN, the data was restored over the LAN. If the System action: Client sessions that attempt to store
operation failed because the client node is not allowed new data or change existing data will be terminated

with a protocol error. IMPORT operations will skip the replicated: amount to replicate. Estimated
node. run time: estimated runtime.
User response: Perform the operation on the server on Explanation: The replication process has completed in
which the original node resides. preview mode. The meanings of the numbers are:
v Files current indicates the number of files that do not
ANR0326E command: The ROLEOVERRIDE need to be replicated.
parameter cannot be used with either v Files to be replicated indicates the number of files
the TYPE=SERVER or TYPE=NAS requiring replication.
parameter. v Files to be updated indicates the number of files
System action: The command failed. requiring a meta-data update.
v Files to be deleted indicates the number of files to be
User response: Reissue the command without the
deleted from the target server.
ROLEOVERRIDE parameter.
v Amount to be replicated indicates the size of the files
that require replication.
ANR0327I Replication of node node list completed.
v Estimated run time is an estimate of how long the
Files current: files current. Files
process will run.
replicated: files replicated of files to
replicate. Files updated: files updated of System action: None.
files to update. Files deleted: files deleted of
files to delete. Amount replicated: amount
replicated of amount to replicate. Amount
transferred: amount transferred. Elapsed ANR0329I Starting replication of data type data for
time: elapsed time. node node name, filespace ID filespace id.
Explanation: The replication process has completed. Explanation: The replication process has started
The meanings of the numbers are: processing data for the specified node and file space
v Files current indicates the number of files that do not ID.
need to be replicated. System action: None.
v Files replicated indicates the number of files
successfully replicated out of the number of files that User response: None.
we attempted to replicate.
v Files updated indicates the number of files which ANR0330W Session session number for node node
had meta-data updated on the target server out of name (client platform) refused - invalid
the number of files that needed an update. authentication protocol requested.
v Files deleted indicates the number of files deleted Explanation: The server refuses a request to start a
from the target server out of the number that needed session because an invalid authentication protocol was
to be deleted. requested during sign-on processing. This might be due
v Amount replicated indictaes the size of the files that to a down-level client, server, or storage agent that is
were replicated out of the size of the files that accessing a server or storage agent that is configured to
needed to be replicated disallow such attempts.
v Amount transferred indicates the number of bytes System action: Server operation continues.
transferred for the files that were replicated. For
compressed files, the number of bytes transferred is User response: Upgrade the accessing client, server, or
the compressed size in bytes. The total number of storage agent to version 6.3 or later, or re-configure the
bytes transferred can be less than the amount server to allow access from down-level clients, servers,
replicated if data deduplication or compression is or storage agents.
used to reduce the amount of data transferred.
v Elapsed time indicate how long the process ran ANR0331W Replication session for server server name
refused - server is down-level.
Explanation: The server specified for replication
cannot be used because it is not at the current level.
ANR0328I Replication preview of node(s) node list
completed. Files current: files current. User response: Upgrade the server to version 6.3 or
Files to be replicated: files to replicate. later, or specify a different server for replication.
Files to be updated: files to update. Files
to be deleted: files to delete. Amount to

ANR0332E Replication mode source repl mode of ANR0336I Runstats for table table name started.
node node name is incompatible with
Explanation: The server is performing an online
mode target repl mode on server server
runstats on the referenced table.
name.
Explanation: The replication mode of the indicated
node is incompatible. If the source mode is SEND, the User response: None.
target mode must be RECV. If the source mode is
SYNCSEND, the target mode must be SYNCRECV. The
source mode cannot be anything other than SEND or ANR0337I Runstats for table table name ended with
SYNCSEND. sqlCode dbCode.
System action: The replication of the node's data fails. Explanation: The server online runstats for the table
Server operation continues. referenced has completed.
User response: Use the UPDATE NODE command to System action: Server operation continues.
put the node in the proper state on both the source and User response: For a non-zero sqlCode, consult the
target servers. DB2 Information Center for details.
ANR0333E Server server name is disabled for ANR0338E Database create terminated.
outbound sessions. The session request
is rejected. Explanation: DB2 detected a problem during the
create database operation. The source of the problem
Explanation: The DISABLED SESSION SERVER might be a DB2 limitation. When "No File System
command disabled outbound sessions for the indicated Caching" is used to create a table space with Database
server. Sessions to this server are not permitted. Managed Storage containers, DB2 only supports storage
System action: The session request fails. Server devices with a sector size of 512 Bytes on AIX, Solaris,
operation continues. Linux, Windows, and a sector size of 1024 Bytes on
HP-UX.
User response: Issue the QUERY STATUS command
to view the servers that are disabled for inbound and System action: The create database operation is
outbound sessions. Issue the ENABLE SESSIONS terminated.
SERVER command to make the server available for User response: See the db2diag.log file for additional
outbound sessions. information to confirm the DB2 limitation. Change the
sector size to 512 Bytes on AIX, Solaris, Linux,
ANR0334E Server server name is disabled for Windows, and to 1024 Bytes on HP-UX.
inbound sessions. The session request is
rejected. ANR0339E command: Outbound replication is
Explanation: The DISABLED SESSION SERVER disabled.
command disabled inbound sessions for the indicated Explanation: Replication operations originating from
server. The indicated server is not permitted to initiate this server are disabled.
sessions to this server.
System action: Processing ends.
System action: The session request fails. Server
operation continues. User response: Use the ENABLE REPLICATION
command to re-enable the use of replication.
User response: Issue the QUERY STATUS command
to view the servers that are disabled for inbound and
outbound sessions. Issue the ENABLE SESSIONS ANR0340E command: Outbound replication
SERVER command to make the server available for operations are disabled because the
inbound sessions. database was restored.
Explanation: The database for this server was
ANR0335I Schema reconciliation for table table in restored. Data that was on this server but that is not
progress; pct% completed. referenced by the restored database is no longer
accessible. To prevent this server from deleting copies
Explanation: The schema for this table is reconciling. of data that might exist on the target replication
System action: Schema reconciliation will continue for servers, replication operations originating from this
this table. server are disabled.
User response: None System action: Processing ends.

User response: Disabling replication after a database

restore is a precautionary step to alert the user of the REPLSTATE=ENABLED

potential that a restored database might contain node REPLMODE=SYNCSEND.
inventory that could result in the loss of filespace data b. On DRSRV, issue the following command:
on a target replication server that is using node UPDATE NODE NODE1
replication. If replication was not used on this server REPLSTATE=ENABLED
before the database restore, issue the ENABLE REPLMODE=SYNCRECEIVE.
REPLICATION command to resume replication
8. On PRODSRV, enable replication by issuing the
operations.
following command: ENABLE REPLICATION.
To preserve the data that exists on target replication 9. On PRODSRV, replicate data belonging to NODE1
servers, determine whether copies of data that are on by issuing the following command: REPLICATE
the target replication server are needed. If they are, you NODE NODE1. Replication processing changes the
must replicate data that is on the target replication replication mode of NODE1 to SEND on PRODSRV
server to the source replication server. After the and to RECEIVE on DRSRV.
replication is complete, issue the ENABLE
REPLICATION command to resume replication The original replication configuration is restored.
operations. PRODSRV has all the data that was lost because of the
For example, suppose that PRODSRV is the source database restore.
replication server. The data belonging to client node
NODE1 was replicated from PRODSRV to DRSRV, the REMEMBER: To replicate data that was on DRSRV, you
target replication server. The database on PRODSRV set the target replication server to PRODSRV. In your
was restored. original configuration, if you were replicating data from
DRSRV to another server, for example, BKUPDRSRV,
To resume replication, complete the following steps: you must reset the target replication server. To reset the
1. On PRODSRV and DRSRV, remove NODE1 from target replication server, issue the following command
replication by issuing the following command: on DRSRV: SET REPLSERVER BKUPDRSRV.
REMOVE REPLNODE NODE1.
2. Update NODE1 definitions. When replication ANR0341E command with keyword keyword is not
occurs, DRSRV will send the data to PRODSRV that allowed when archive data retention
was lost because of the database restore. protection is enabled.
a. On DRSRV, issue the following command:
UPDATE NODE NODE1 Explanation: The specified command with the
REPLSTATE=ENABLED specified keyword is not allowed when archive data
REPLMODE=SYNCSEND. retention protection is enabled on the server.
b. On PRODSRV, issue the following command: System action: Processing continues.

UPDATE NODE NODE1
REPLSTATE=ENABLED
REPLMODE=SYNCRECEIVE.
3. On DRSRV, set the replication rules to match those ANR0343W File space filespace name could not be
on PRODSRV. For example, if only archive data was created by node $$_TSMDBMGR_$$.
being replicated from PRODSRV to DRSRV, set the $$_TSMDBMGR_$$ node name is
rules on DRSRV to replicate only archive data from reserved for IBM Spectrum Protect
DRSRV to PRODSRV. Backup and space-managed database backup and restore.
data will not be replicated to PRODSRV. System action: Server processing continues.
4. On DRSRV, set the target replication server by
User response: Node $$_TSMDBMGR_$$ is only used
issuing the following command: SET REPLSERVER
for IBM Spectrum Protect database backup or restore.
PRODSRV.
The server does not create a file space with this special
5. On DRSRV, replicate data belonging to NODE1 by node since there is no running database backup or
issuing the following command: REPLICATE NODE restore session.
NODE1. Replication processing changes the
replication mode of NODE1 to SEND on DRSRV User response: Use another node name to create this
and to RECEIVE on PRODSRV. filespace.
6. On PRODSRV and DRSRV, remove NODE1 from
replication by issuing the following command: ANR0344E The server failed to restore the database.
REMOVE REPLNODE NODE1. Missing ARCHIVELOGDIR value in the
7. Update NODE1 definitions: server option file.
a. On PRODSRV, issue the following command: Explanation: While attempting to restore the database,
UPDATE NODE NODE1 the IBM Spectrum Protect server detects a missing
value for ARCHIVELOGDIR in the server option file.

System action: Server database restore stops.

ANR0365E Database database name is currently in
User response: Before reissuing the command to use and can not be removed.
restore the database, check the following items:
v Ensure that ARCHIVELOGDIR option has a valid administrator that the server has detected that the
value. database is currently in use during a REMOVE DB
v Ensure that the command is using the correct options process.
file for the server. If you are using the -o option with
System action: Server REMOVE DB stops.
the command to specify a server options file, ensure
that the name and location of the file is correct. User response: Drop all database connections then
issue the command again.
ANR0345E The database manager cannot start
while file file name exists. ANR0366I Database database name was removed
successfully.
System action: The server stops.
User response: Remove or rename the specified file
administrator that the server has removed the server
and restart the server.
database successfully.
ANR0347E Database database name is reporting a
drive is invalid and the database can not User response: The server database was removed. In
be removed. order to run the IBM Spectrum Protect server, you need
to format a new database using the 'DSMSERV
FORMAT' command.
administrator that the server has detected that the API
is reporting an invalid drive condition during a
REMOVE DB process. ANR0367W The server failed to format the database
database name. This database name
System action: Server REMOVE DB stops.
already exists.
User response: Interrogate the database, correct the
Explanation: While attempting to format a database,
problem then issue the command again.
the IBM Spectrum Protect server has found that this
database name already exists.
ANR0358E Database initialization failed: sufficient
System action: Server format stops.
memory is not available.
User response: Before reissuing the command to
Explanation: During server initialization, the server
format a new database, check the following items:
database fails initialization because sufficient server
memory is not available. v Remove the old database using command 'DSMSERV
REMOVEDB DB_NAME'.
System action: Initialization fails.
v Ensure that the command is using the correct options
User response: Make more memory available to the file for the server. If you are using the -o option with
server. the command to specify a server options file, ensure
that the name and location of the file is correct.
ANR0361I Recovery is in progress following a

database failure. ANR0369I Stopping the database manager because
of a server shutdown.
Explanation: During server initialization, the database
manager indicated that the database requires failure System action: Stopping the server's database
recovery. A database failure can occur in the event of a manager.
power outage or other abnormal termination of the
database manager. Failure recovery can take extensive
time, depending on how many transactions in the log
require examination. ANR0370E Diagnostic(ID) During the format
operation, the server cannot create files
System action: The server initialization is delayed
in one or more directories that you
while the database is recovered.
specified for log type. Ensure that the file
User response: No action is required. system where the directory is located
has sufficient space.
Explanation: Space is not available for the server to
write data to the directory.

System action: The format operation stops.

ANR0374E Database database name is invalid and
User response: Before reissuing the command to can not be removed.
format a new database, check the following items:
v Check whether the format operation created a administrator that the server has detected that the API
database but did not remove the database after the is reporting an Invalid DB error during a REMOVE DB
failure. If the database that was created was not process.
removed, use the utility DSMSERV REMOVEDB
db_name to remove it. System action: Server REMOVE DB stops.
v Check that space is available to the directories that User response: Interrogate the database, correct the
you specified for problem then issue the command again.
ACTIVELOGDIR,ARCHIVELOGDIR, and
ARCHFAILOVERLOGDIR. Ensure that the amount
ANR0375E Database database name is reporting an
of space meets requirements. For example, the
authorization error and can not be
directory for ACTIVELOGDIR must have at least 8
removed.
GB space available.
v Remove any files that are in the directories that you Explanation: This message is issued to notify the
want to use for the recovery logs. administrator that the server has detected that the
database is reporting an authorization error during a
REMOVE DB process.
ANR0371E Error setting environment variable
environment variable name with value value System action: Server REMOVE DB stops.
- return code return code value. User response: Interrogate the database, correct the
Explanation: The server is unable to set the content of problem then issue the command again.
the environment variable on the operating system to
the value specified in the message. The return code in ANR0376E Database database name is not found and
the message is the last error code set in the operating can not be removed.
system. The return code, or, last error code is a system
error code as a result of the failed function call to set Explanation: This message is issued to notify the
the environment variable. administrator that the server has detected that the API
is reporting the DB cannot be found during a REMOVE
System action: The server operation stops. DB process.
User response: Refer to the list of system error codes System action: Server REMOVE DB stops.
provided by the operating system to determine the
cause of the problem. Resolve the problem and retry User response: Interrogate the database, correct the
the server operation. problem then issue the command again.
ANR0372E Database database name is currently ANR0377E Database database name is reporting a
damaged and can not be removed. drive is not found and can not be
removed.
administrator that the server has detected that the Explanation: This message is issued to notify the
database is damaged during a REMOVE DB process. administrator that the server has detected that the API
is reporting a database drive cannot be found during a
System action: Server REMOVE DB stops. REMOVE DB process.
User response: Interrogate the database, correct the System action: Server REMOVE DB stops.
User response: Interrogate the database, correct the
ANR0373E Database database name is reporting a
File error and can not be removed.
ANR0378W Database database name is reporting a
Explanation: This message is issued to notify the drive is not found and can not be
administrator that the server has detected that the removed.
database is reporting a File error during a REMOVE DB
process. Explanation: This message is issued to notify the
administrator that the server has detected that the API
System action: Server REMOVE DB stops. is reporting a warning during a REMOVE DB process.
User response: Interrogate the database, correct the System action: Server REMOVE DB completed
problem then issue the command again. successfully.

User response: The drop database command has

ANR0388I Node node name using storage agent
completed successfully, however, there are some nodes
storage agent has capable count storage
where the database alias or database name was not
pools capable of LAN-free data
found. It is possible that DROP DATABASE AT NODE
movement and not capable count storage
was already performed on these nodes.
pools not capable of LAN-free data
movement.
ANR0379W A server database deadlock situation has
Explanation: The server has completed evaluation of
been encountered; the lock request for
the LAN-free and non-LAN-free storage pool
the lock name lock, key name will be
destinations for this node using this storage agent. The
denied to resolve the deadlock.
server determined that there are capable count storage
Explanation: The server detected a deadlock situation pools that are capable of LAN-free data movement. It
between a number of processes attempting to access also determined that there are not capable count storage
database information. A lock request for one of the pools that cannot be used for LAN-free data
processes will be denied to resolve the database movement.
deadlock. When the server processes encounter a
database deadlock, they usually try to run the function
that was in progress when the deadlock was User response: Review the other messages issued to
encountered again. Not all process can explicitly try an determine which storage pools are capable of LAN-free
operation again. For example, migration and data movement and those which are not capable of
reclamation will eventually try again. However, LAN-free data movement for this node using this
something like a delete volume run in a macro will storage agent.
only be tried again if the delete command is reissued
either in the macro or the command line.
ANR0389W Node node name has data path
System action: A lock request fails for one of the restrictions.
deadlocked processes. Server operation continues.
Explanation: The node name has data path restrictions.
User response: If a process can be retried (like The registered node has data write path, data read
migration), monitor the retry effort to see if it succeeds. path, or both, configured to not allow LAN-free
If the process or command cannot be retried, reissue operations.
the command or macro that caused the action.
Consider what other processes are running at the time
User response: Issue the command QUERY NODE
the deadlock is reported. For example, if a process is
node name F=D and evaluate the data read path and
started manually, as opposed to running as part of your
data write path settings. To store data or read data
regularly scheduled server maintenance tasks, that
using LAN-free data movement, set the data write path
process may have caused the deadlock. You might have
to ANY or LANFREE.
to adjust the scheduling of your server maintenance
tasks to avoid the problem.
ANR0390W A server database deadlock situation has
been encountered; the lock request for
ANR0387I Evaluating node node name using storage
transaction transaction ID will be denied.
agent storage agent for LAN-free data
movement. Explanation: The server detected a deadlock situation
between a number of processes that were attempting to
Explanation: The server is evaluating whether the
access database information. A lock request for one of
node and storage agent can use storage pools capable
the processes is denied, to resolve the database
of LAN-free data movement.
deadlock. When server processes encounter a database
System action: The server evaluates the storage pool deadlock, they usually reattempt the function that was
destinations available to this node and reports which in progress when the deadlock was encountered. Not
storage pools can and cannot be used for LAN-free all process can explicitly try an operation again. For
data movement. example, migration and reclamation will eventually be
tried again. However, something such as a delete
User response: Review the results of this processing to
volume run in a macro will only be tried again if the
determine if the appropriate LAN-free environment is
delete command is reissued either in the macro or the
configured.
command line.
System action: A lock request fails for one of the
deadlocked processes. Server operation continues.
User response: If a process can try again (like
migration), then monitor the subsequent attempt to see
if it succeeds or not. If it fails, contact a service

representative. If the process or command is not able to

ANR0402I Session session number started for
automatically try again, then reissue the command or
administrator administrator ID
macro that caused the action to occur. If it fails again,
(administrator's platform) (communication
contact a service representative for further assistance to
method).
better isolate the deadlock condition.
Explanation: A new administrator client session has
been initiated by the specified administrator. The
ANR0397I Session session number for node
session number, administrator's platform type and
agent_node has begun a proxy session for
communication method used by this session are
node target_node.
included in the message.
Explanation: A client session has begun proxy
System action: The server begins a communications
operations.
session to service the administrator client.
System action: The server granted a proxy session to
a client node.
ANR0403I Session session number ended for node
node name (client platform).
ANR0398W Session session number for node
Explanation: A client session has completed normally.
agent_node has failed to begin a proxy
session for node target_node. System action: Server operation continues.
Explanation: A client session attempted to begin a User response: None.
proxy operation. The server failed the client request.
This can occur if the agent node does not have a proxy
ANR0405I Session session number ended for
association with the target node.
administrator administrator ID (client
System action: The server blocks the proxy platform).
authorization attempt.
Explanation: An administrative client session has
User response: None. completed normally.
ANR0399I Session session number for node
agent_node has ended a proxy session for
node target_node.
ANR0406I Session session number started for node
Explanation: A proxy session has been ended. The
node name (client platform) (communication
server terminates a session if there is an error in the
method communication address).
protocol. On the other hand, the client can also
terminate the session. Explanation: A new client session has been initiated
by the specified node. The session number, client
System action: The server, or the client, has ended a
platform type, communication method and address
proxy session for a client node.
used by this session are included in the message.
session to service the client node.
ANR0400I Session session number started for node
node name (client platform) (communication
method).
ANR0407I Session session number started for
Explanation: A new client session has been initiated
administrator administrator ID
by the specified node. The session number, client
(administrator's platform) (communication
platform type and communication method used by this
method communication address).
session are included in the message.
Explanation: A new administrator client session has
been initiated by the specified administrator. The
session to service the client node.
session number, administrator's platform type,
User response: None. communication method and address used by this
session are included in the message.
session to service the administrator client.


ANR0408I Session session number started for server
server name (server's platform) User response: None.
(communication method) for purpose.
Explanation: A new server session has been initiated ANR0413I Session session number for administrator
by the specified server for the specified purpose. The administrator name logged in as node node
session number, server's platform type and name is restoring backup set: node node
communication method used by this session are name, set filespace name.
included in the message.
Explanation: This message logs information about a
System action: The server begins a communications backup set restored by an administrator logged in for a
session to service the administrator client. node.
User response: None. System action: Server operation continues.
ANR0409I Session session number ended for server
server name (client platform).
ANR0414I Session session number for node node
Explanation: A server has completed normally. name is restoring backup set: node node
name, set filespace name.
Explanation: This message logs information about a
backup set restored by a node.
ANR0410E EXPORT operation to server server name
rejected - administrator administrator is User response: None.
not authorized to perform the import
operation on the target server.
ANR0415I Session session number proxied by storage
Explanation: An export operation to the named server agent name started for node node name.
was rejected, because the administrator issuing the
export command is not defined on the target server or Explanation: This session is started for the indicated
does not have sufficient authority to perform the node and the storage agent acts as the proxy for the
import operation on the target server. node. Client node sessions are used to perform
LAN-free operations between the client and server.
ANR0411I Session session number for administrator

administrator name logged in as node node ANR0416W Session session number for node node
name restored or retrieved object type name not allowed to operation using path
object: node node name, filespace filespace data transfer path.
name, object object name. Explanation: This session attempted this operation
Explanation: This message logs information about an using the specified data transfer path. This operation is
object that was restored or retrieved by an not permitted for this client.
administrator logged in for a node. System action: Server operation continues.
System action: Server operation continues. User response: Issue QUERY NODE
User response: None. FORMAT=DETAILED for this node to see the current
DATA WRITE PATH or DATA READ PATH settings.
These settings determine if a given operation is
ANR0412I Session session number for node node permitted using a specific data transfer path. If this
name(Userid=user id), restored or client node should be permitted to perform this
retrieved object type object: node node operation using this data transfer path, the UPDATE
name, filespace filespace name, object object NODE command should be used to correct this.
name.
Explanation: This message logs information to the ANR0417W Session session number for node node
activity log about an object that was restored or name terminated - data transfer path not
retrieved by a user logged in for a node. A user ID allowed.
with no value indicates that an administrative or root
user on the platform initiated the restore. Explanation: This session attempted an operation that

needed a data transfer path that this node is not System action: Server operation continues.
allowed to use.
User response: This error is usually the result of a
System action: This client session terminates. client programming error in which the sign-on verb has
been incorrectly formatted and delivered to the server.
User response: Refer to the ANR0416W message that
This error can also result when the server is contacted
was issued for this client session to determine which
by an application that is not a part of this product.
operation and data transfer path was attempted.
ANR0422W Session session number for node node

ANR0418W Session session number for administrator
name (client platform) refused - node
administrator name (client platform) is
name not registered.
refused because an incorrect password
was submitted. Explanation: The server refuses a request to start a
client session because the client node name is not
Explanation: The server refuses a request to start a
registered in the server database.
client session because an invalid password has been
submitted by the client during sign-on processing. System action: Server operation continues.
System action: The server will continue to deny access User response: Register the node name with the
attempts by this client until a valid password is server before establishing a session. If the server is
submitted. running with OPEN registration, no action is required;
the client prompts the user for a password and
User response: Enter the proper password. If you
registers the client with the server. If CLOSED
have forgotten the password, contact an authorized
registration is in effect on the server, an authorized
administrator, who can assign a new password using
administrator must use the REGISTER NODE
the UPDATE ADMIN command.
command to register the client node name with the
server.
ANR0419W Administrative client userid
administrative ID cannot be used when
authentication is on.
administrator ID (client platform) refused -
Explanation: The server refuses a request for a client administrator name not registered.
(administrative) session because the user ID specified
Explanation: The server refuses a request to start an
cannot be used when authentication of IDs is in effect.
administrative session because the administrator name
SERVER_CONSOLE is an administrative ID that has
is not registered in the server database.
this restriction.
User response: Register the administrator name with
User response: Use an administrative ID that was
the server before establishing a session. An authorized
registered for this server and that has a password.
administrator must use the REGISTER ADMIN
command to register the administrator with the server.
name (client platform) refused - server
disabled for user access.
name (client platform) refused - invalid
Explanation: The server refuses a request for a client password submitted.
(backup-archive) session because the server is currently
disabled for client access.
client session because an invalid password has been
System action: Server operation continues. submitted by the client during sign-on processing. The
Administrative clients are permitted access to the server will continue to deny access attempts by this
server. client until a valid password is submitted.
User response: An authorized administrator must System action: Server operation continues.
issue the ENABLE SESSION command before client
User response: Enter the proper password. If the
nodes are permitted access to the server.
password has been forgotten by the user, an authorized
administrator can assign a new password by using the
ANR0421W Session session number for node node UPDATE NODE command.
name (client platform) refused - sign-on
protocol violation.
Explanation: The server refuses a request for a client
session because sign-on protocol has been violated.

ANR0425W Session session number for node node ANR0429W Session session number for node node
name (client platform) refused - node name (client platform) refused - maximum
password has expired. server sessions (max sessions allowed)
exceeded.
Explanation: The server refuses the specified session
because the client node's password has expired. Explanation: The server refuses the specified client or
administrative session because the maximum number
of concurrent client sessions has been exceeded.
User response: Upon receipt of this error condition,
the client program immediately reconnects to the server
specifying a password update session and prompts the User response: If necessary, increase the maximum
user for a new password. After the user enters a new number of permitted sessions. To do this, update the
password, the client reconnects to the server for normal value for the MAXSESSIONS parameter in the server
operations. Alternatively, an authorized administrator options file and restart the server with the updated
can update the client password using the UPDATE options file. Note that increasing the MAXSESSIONS
NODE command. value requires additional memory resource by the
server. You may want to retry the connection at a later
time.
name (client platform) refused - open
registration not permitted. ANR0430W Session session number for node node
name (client platform) refused - node
Explanation: The server refuses a client session
name is locked.
because an open registration action has been attempted
and the server is running with CLOSED registration. Explanation: The server refuses the specified client
session because the node is locked from server access
(with the LOCK NODE command or by the LDAP
User response: Ask an authorized administrator to directory server).
submit the request using the REGISTER NODE or
System action: Server operations continue.
REGISTER ADMIN command.
User response: Before the client node is permitted to
access the server, a properly authorized administrator
must unlock the node. Nodes using LOCAL
authentication can be unlocked with the UNLOCK
version is down-level with this client.
NODE command. Nodes using LDAP authentication
Explanation: The server refuses a client session can be unlocked from within the LDAP directory
because the client program version level is newer than server.
that supported by the server program.
System action: Server operation continues. ANR0431W Session session number refused -
administrator administrator ID (client
User response: Apply service to the server program to platform) is locked.
make it compatible with the newer client program, or
use an older client program to contact the server. Explanation: The server refuses the specified
administrative session because the administrator is
locked from server access (with the LOCK ADMIN
ANR0428W Session session number for node node command or by the LDAP directory server).
name (client platform) refused - client is
down-level with this server version. System action: Server operations continue.
Explanation: The server refuses the client session User response: Before the administrator is permitted
because the client program version level is older than to access the server, a properly authorized
that supported by the server program. For certain administrator must unlock the administrator.
problems (such as the compression fix), once a node Administrators using LOCAL authentication can be
connects to the server using the newer client, the server unlocked with the UNLOCK ADMIN command.
records this fact and will not let this node back off this Administrators using LDAP authentication can be
client version to a version that does not include the fix. unlocked from within the LDAP directory server.

User response: Apply service to the client program to name (client platform) refused -
make it compatible with the newer server program. insufficient memory.
Explanation: The server ends the specified session

because sufficient memory (virtual memory) is not messages. If the error cannot be isolated and resolved,
available. contact your service representative.
System action: The server ends the session and
continues operation. ANR0437W Session session number for node client
node name (client platform) encountered an
internal server error while checking
license compliance.
application.
Explanation: The server encountered an internal error
in determining if the server is in compliance with
ANR0433W Session session number for node or
license terms.
administrator ID (client platform) was
refused because of insufficient recovery System action: The client session is ended.
log space.
User response: Use the QUERY LICENSE and QUERY
Explanation: If a log runs out of space, the current STATUS commands to determine if the server is in
transaction is rolled back. The server issues an error compliance with license terms. Start an AUDIT
message and halts. You cannot restart the server until LICENSES process to readjust server license
the recovery log size is increased. information. When this process completes you may
restart the session. If the problem persists, contact your
System action: The server halts.
service representative.
User response: Monitor archive logs and active logs. If
the recovery log space is insufficient, monitor the
ANR0438W Session session number archive operation
archive log space first. If the archive log space is full or
for client client node name (client platform)
nearly full, run a full database backup to remove
has been denied - Server is not in
archive logs and consider adding more disk space to
compliance with license terms.
the archive log directory. If the archive log space is not
full and the active log space is full or nearly full, Explanation: The server refuses a client archive
update the value of the ACTIVELOGSIZE option in the operation because the current server configuration is
dsmserv.opt file. Set the value of the ACTIVELOGSIZE not in compliance with license terms.
option to the new maximum size of the active log.
System action: Server operation continues. Clients
may perform any action except backup or archive.
ANR0434W Session session number for node or
User response: Use the QUERY LICENSE command to
administrator ID (client platform) was
determine the license terms that are no longer in
refused because of insufficient database
compliance.
space.
Explanation: The server ends the specified client or
ANR0439W Session session number backup operation
administrative session because of insufficient database
for client client node name (client platform)
space.
has been denied - Server is not in
System action: The server ends the session, but compliance with license terms.
continues operation.
Explanation: The server refuses a client backup
User response: To increase the amount of database operation because the current server configuration is
space that is available to the server, issue the EXTEND not in compliance with license terms.
DBSPACE command. Add one or more directories to
System action: Server operation continues. Clients
the database.
may perform any action except backup or archive.
name (client platform) refused - internal
compliance.
error detected.
ANR0440W Protocol error on session session number
because an internal logic error is detected.
for node client node name (client platform) -
System action: The server ends the session and invalid verb header received.
Explanation: The server detects a protocol error on the
User response: To determine the source of the error, specified session because an invalid verb header has
the administrator can examine server messages issued been received from the client. Verb headers always
prior to this message. The QUERY ACTLOG command precede communication sent to the server from the
can be used to view the activity log and search for client or from the server to the client.

System action: The server ends the client session. an API client, contact your service representative. If the
client generating the error is an API client, contact the
User response: Correct the programming error in the
owner of the API client. If the client generating the
client program if it has been written by your
error is a client that you have created using WDSF
installation using WDSF verbs. Otherwise, contact your
verbs, correct the programming error in your client
program.

invalid data length received.
maximum group transaction size
Explanation: The server detects a protocol error on the exceeded.
specified session because an invalid verb length has
been received from the client.
specified session because the client has attempted to
System action: The server ends the client session. group more than the maximum database update
operations in a single database transaction.
client program if it has been written by your System action: The server ends the client session.
ANR0442W Protocol error on session session number service representative.
invalid stream mode switch.
ANR0446W Session session number client client node
Explanation: The server detects a protocol error on the name compression method unsupported -
specified session because the client has attempted an Compression forced OFF. Please obtain
illegal stream operation. the latest level of the client code.
System action: The server ends the client session. Explanation: The client is using a compression
method that is no longer supported by the Server.
client program if it has been written by your System action: Server operation continues. The client's
installation. Otherwise, contact your service backup operation continues, without compressing the
representative. data.
User response: The compression method used by the
ANR0443W Protocol error on session session number client is no longer supported. In order to use
for node client node name (client platform) - compression, the client needs to be upgraded to a client
invalid "field name" field found in "verb service level that supports the newer compression
name" verb (offset offset position). method.

specified session because an invalid field has been ANR0447W Session session number space
found in a verb sent from the client node. management migration operation for
client client node name (client platform) has
System action: The server ends the client session. been denied - Server is not in
User response: Correct the programming error in the compliance with license terms.
client program if it has been written by your Explanation: The server refuses a client space
installation using WDSF verbs. Otherwise, contact your management migration operation because the current
service representative. server configuration is not in compliance with license
terms.
ANR0444W Protocol error on session session number System action: Server operation continues. Clients
for node client node name (client platform) - may perform any action except backup, archive, or
out-of-sequence verb (type verb name) space-managed file migration.
received.
Explanation: The server detects a protocol error on the determine the license terms that are no longer in
specified session because a verb has been received that compliance.
does not adhere to the client-server exchange sequence.
System action: The server ends the client session.
User response: If the client generating the error is not

ANR0448W Session session number space ANR0451W Session session number for server server
management migration operation for name (server platform) refused - invalid
client client node name (client platform) has password submitted.
been denied - server is not licensed for
space management support.
server session because an invalid password has been
Explanation: The server refuses a client space submitted during sign-on processing. The server will
management migration operation because the server is continue to deny access attempts by that server until
not licensed to support space-managed clients. valid passwords are submitted.
System action: Server operation continues. System action: Server operation continues.
User response: Licenses to support space-managed User response: Set the proper passwords. If the
clients can be obtained from your service provider or password has been changed on either server, an
re-seller. The REGISTER LICENSE command can be authorized administrator can set new passwords by
used with these licenses to enable space management using the UPDATE SERVER command with the
support. SERVERPASSWORD parameter.
ANR0449W Session session number space ANR0452W Session for server source server name
management migration operation for refused. Server source server name is not
client client node name (client platform) is defined for server-to-server
in violation of server license terms - communications on server target server
server is not licensed for space name.
management support.
Explanation: The server warns about a client space server-to-server session because a server name is not
management migration operation because the server is defined in the server database, or the server definition
not licensed to support space-managed clients. does not have a SERVERPASSWORD. Server-to-server
communications that use the SERVERPASSWORD
require that each server has a server definition for the
User response: Licenses to support space-managed other server.
clients can be obtained from your service provider or
re-seller. The REGISTER LICENSE command can be
used with these licenses to enable space management User response: Register the server names on both
support. servers before establishing a session, or update the
server's existing server definition and set a
SERVERPASSWORD. An authorized administrator
ANR0450W Session session number for server server
must use the DEFINE SERVER or UPDATE SERVER
command to register the servers and set the passwords.
name not defined for server to server
communications.
ANR0453W Server to server session refused - no
password defined.
server session because the requesting server name is
not defined in the server database, or the requesting Explanation: The server to server session cannot be
server definition does not have a SERVERPASSWORD, initiated because no server password has been defined
or a password or node name is not setup for virtual for this server.
volume use on the source server.
User response: Define a server password with the SET
User response: Register the requesting server name SERVERPASSWORD command and retry the
with the server before establishing a session, or update command.
the existing requesting server definition and set a
SERVERPASSWORD. An authorized administrator
ANR0454E Session rejected by server target server
must use the DEFINE SERVER or UPDATE SERVER
name, reason: rejection reason.
command to register the requesting server and set the
password. For a virtual volume environment, the Explanation: The server tried to open a session with
source server must have a definition for the target the named server. The session was rejected for the
server which includes a node name and password. indicated reason.
System action: The operation fails.
User response: Check both the servers for any

additional messages that might further describe the

ANR0455W Invalid Command command name for
reason the session was rejected. The rejection reason
SNMP session.
will be in the form of "diagnostic code - reason". The
diagnostic code is only intended for use by your Explanation: An SNMP administrative session
service representative. The following responses apply to attempted to run a command which is not an macro
the specified rejection reasons. invocation. SNMP administrative sessions are only
v No Resource: Ensure that the receiving server is allowed to issue macro commands.
enabled and has sufficient database, log, and System action: The server ends the client session.
memory resource to support the server session.
User response: Enter commands through the SNMP
v Verifier expired: Ensure that the administrator's
administrative interface which are macros defined on
password is current on both servers.
the server.
v Admin not registered: Ensure that the administrator
is registered on the target server.
ANR0456W Session rejected for server server name -
v Inbound sessions disabled: Ensure that the target
the server name at High level address, Low
server has not disabled this server with the DISABLE
level address does not match.
SESSIONS SERVER command.
v Down Level: Ensure that this server's level is current Explanation: The server name at the address specified
with respect to the target server's level. does not match the name in the server definition. The
connection is not established.
v Admin in use: Ensure that the administrator is not
being updated on the target server. System action: The server continues.
v Language not available: Ensure that required User response: Ensure the HLADDRESS and
languages are installed on the target server. LLADDRESS in the define server command are correct,
v Admin locked: Ensure that the administrator is not and that the servername on the server being contacted
locked on either server. matches the name used in the DEFINE SERVER
v License Failure: Ensure that appropriate licenses are command.
registered.
v Admin on client port: Use the UPDATE SERVER ANR0457W Session for server server name refused -
command to set the admin port for the target server. crossdefine is not allowed on this
v SSL Required: Ensure that SSL is properly server.
configured. Explanation: The server refuses a request to start a
v Authentication Failure: Ensure that all passwords server to server session for crossdefine because it is not
have been set correctly on both servers. The allowed on this server. The server will deny any
password for the server (set by SET sessions for crossdefine until crossdefine is allowed on
SERVERPASSWORD on server X) and the password this server.
in the server definition (set by DEFINE or UPDATE
SERVER X SERVERPASSWORD=) are the same System action: Server operation continues.
password. User response: An authorized administrator must use
v Verification Failure: Use the QUERY SERVER the SET CROSSDEFINE ON command to allow cross
command to determine that the HLADDRESS and registration of servers.
LLADDRESS of the target server are correct. If they
are not, correct them with the UPDATE SERVER
ANR0458S Server server name does not support
command. If they are correct, resynchronize with the
access by the Storage Agent.
target server by issuing the UPDATE SERVER
FORCESYNC=YES command. Explanation: The storage agent attempted to contact a
v Communication Failure: Ensure that the target server Database Server, but the server contacted was not at
is available and that TCPIP is available on both the correct level.
servers. Use the QUERY SERVER command to System action: The Storage Agent terminates.
determine that the HLADDRESS and LLADDRESS of
the target server are correct. If they are not, correct User response: Specify a correct Database Server in
them with the UPDATE SERVER command. the devconfig file for the Storage Agent.
v Node Type: Either the TYPE of the registered node
on the target server is not SERVER or the ANR0459W Authentication Protocol error on session
NODENAME parameter of the server definition on session number for node client node name
the source server is incorrect. (client platform) - out-of-sequence verb
v Internal error: Use the messages on the target server (type verb name) received.
to determine the problem. Explanation: The server detects a protocol error on the

specified session because a verb has been received that

ANR0463W Open registration failed for session
does not adhere to the client-server authentication
session number for node node name (client
exchange sequence.
platform) - invalid password.
Explanation: The server refuses a client session during
User response: If the client generating the error is not open registration because the password name specified
an API client, contact your service representative. If the by the user is not valid.
client generating the error is an API client, contact the
owner of the API client. If the client generating the
error is an IBM-provided client, please ensure that it is User response: Specify a password that uses valid
at the current software level. characters and is less than the maximum length in size.
ANR0460W Open registration failed for session ANR0464W Open registration failed for session
session number - node name node name session number for node node name (client
(client platform) already exists. platform) - exceeded number of nodes
available under license terms.
open registration because the client has specified a Explanation: The server detected an attempt to
node name that is already registered on the server. register more nodes than allowed by the terms of the
current license.
System action: Server operation continues, but the
User response: The client program user must specify a
REGISTER NODE command fails, and the node is not
different node name for the client in the client options
registered.
file.
compliance.
platform) - policy domain STANDARD
does not exist. ANR0465W Open registration failed for session
platform) - policy domain STANDARD
open registration because the STANDARD policy
does not have an ACTIVE policy set.
domain does not exist. All nodes added to the server
database under open registration are automatically Explanation: The server refuses a client session during
assigned to the STANDARD policy domain. This policy open registration because the STANDARD policy
domain must be defined and have an active policy set domain does not have an active policy set. All nodes
to support open registration. added to the server database under open registration
are automatically assigned to the STANDARD policy
domain. This policy domain must be defined and have
User response: If you want to support open an active policy set to support open registration.
registration, define a policy domain using the DEFINE
DOMAIN command with the name STANDARD and
activate a valid policy set in the domain. You can issue User response: If you want to support open
the UPDATE NODE command to move nodes to registration, define a policy domain using the DEFINE
different policy domains after the nodes have registered DOMAIN command with the name STANDARD and
themselves through open registration. activate a valid policy set in the domain. You can issue
the UPDATE NODE command to move nodes to
different policy domains after the nodes have registered
themselves through open registration.
platform) - invalid node name.
ANR0466E The SETSTORAGESERVER command
did not complete successfully.
open registration because the node name specified by
the client is not valid. Explanation: The SETSTORAGESERVER command
encountered an error and did not complete successfully.
System action: Storage agent operation terminates.
User response: Specify a node name in the options file
of the client program that contains valid characters and User response: Please review prior error messages and
does not exceed the maximum length in size. take the necessary corrective actions.

ANR0467I The SETSTORAGESERVER command ANR0472E The database manager did not start. A
completed successfully. tablespace container is inaccessible.
Explanation: The SETSTORAGESERVER command Explanation: The server was unable to start the
has completed successfully, and the appropriate device database manager.
configuration files have been updated.
System action: Storage agent operation terminates.
User response: Before restarting the server, check the
User response: None following items:
v Reboot the system.
ANR0468E Server-to-server export and import not v Check that the directories for dbdir, log, or devices
allowed with server server name. Export exists and that the file system is mounted (if it is on
server is at version export version; import a separate file system).
server is at version import version. v Make sure that the hardware and network
Explanation: An attempt was made to export to an connection are working properly.
outdated server. The server on which the import is v Fix any errors in the system log or db2diag.log.
performed must be at the same or later level than the
server from which the data was exported.
System action: The export operation ends and server administrator ID (client platform) refused -
operation continues. administrator name does not have the
correct level of authority over client
User response: Export to a server that is at the same
node.
or later level.
Explanation: The server refuses a request to start an
administrative session because the administrator name
does not have appropriate authority over the node.
name (client platform) refused - client is
not configured for archive retention System action: Server operation continues.
protection.
User response: Use command GRANT AUTHORITY
Explanation: The server refuses a client session to grant appropriate authority to the current
because the client is not configured for archive administrator ID.
retention protection.
System action: Server operation continues. ANR0474W Session session number for administrator
administrator ID (administrator platform)
User response: Either disable archive retention
was refused because administrators are
protection on the server or configure the client for
not allowed to initiate sessions on the
archive retention protection.
client port.
Explanation: The server did not start the specified
administrative session because the administrator
administrator name refused -
connected to the server on the server port that is used
administrator password has expired.
for client sessions, and the option
Explanation: The server refuses the specified session ADMINONCLIENTPORT is set to NO. When different
because the administrator's password has expired. port numbers are used for administrative and client
sessions (controlled by the TCPPORT and
System action: Server operation continues. TCPADMINPORT options), and option
User response: Upon receipt of this error condition, ADMINONCLIENTPORT is set to NO, administrative
the client program immediately reconnects to the server sessions can be started only on the port used for
specifying a password update session and prompts the administrative sessions (as specified by the
user for a new password. After the user enters a new TCPADMINPORT option).
password, the client reconnects to the server for normal System action: Server operation continues.
operations. Alternatively, an authorized administrator
can update the client password using the UPDATE User response: Update the client options file to
ADMIN command. specify the port to be used for administrative sessions.
This is typically specified by the TCPADMINPORT
option in both client and server option files.

ANR0475W Session session number for node node ANR0478W Session request refused. Server is
name (client platform) refused - node is running in standalone mode.
not allowed to initiate sessions on
Explanation: A client has requested a session with the
administrative port.
server. The server is running in a mode in which it
Explanation: The server had refused to start a session cannot start client sessions.
with the specified client node because the node
System action: The session request is refused. The
connected to the server on the server's administrative
server operation continues.
port. When different port numbers are used for
administrative and client sessions, client sessions may User response: No response is required. To reduce or
be started only on the port used for client sessions. disable the display of this message, you can update the
server options before running in standalone mode with
the COMMMETHOD NONE option. This will allow the
User response: The client option file should be server to run without enabling client connections.
updated to specify the port to be used for client
sessions. This is typically specified by TCPPORT option
ANR0479W Session session number for server server
in both client and server option files. The MVS server
name (server platform) terminated -
also uses the ICSPORT option.
connection with server severed.
Explanation: If server A has opened a connection with
server B, server B's session is ended because the
name (client platform) refused - node is
communications link has been closed by a network
not allowed to initiate sessions.
error or by server A's program.
Explanation: The server had refused to start a session
System action: Server A continues operation.
with the specified client node because the node is not
allowed to initiate session. Only server initiated User response: If server B halts operation or in some
sessions are allowed with this client. The SESSIONINIT way stops communicating with server A, this message
parameter of the REGISTER NODE and UPDATE will be displayed on server A indicating that the
NODE commands control the ability of a client to connection was closed suddenly by server B. A network
initiate sessions. failure can also cause this message to be displayed. If a
large number of these messages occur simultaneously,
check the network for failure and correct any problems.
User response: An administrator can use the UPDATE
NODE command with the SESSIONINIT parameter to
specify that the client may initiate sessions.
name (client platform) terminated -
Alternatively, sessions can be scheduled with the client
connection with client severed.
that are stared by the server through server-prompted
scheduling commands ( DEFINE SCHEDULE, DEFINE Explanation: The specified client session is ended
ASSOCIATION ). because the communications link has been closed by a
network error or by the client program.
ANR0477W Session session number refused - The System action: Server operation continues.
client client node name cannot access the
server with a platform type of client User response: If a user breaks out of a client
platform. program, this message will be displayed on the server
as the connection is suddenly closed by the client. A
Explanation: A client with a invalid combination of network failure can also cause this message to be
node type and platform type has requested a session displayed. If a large number of these messages occur
with the server. For example, a node id of type NAS simultaneously, check the network for failure and
can only sign on with a platform type of "TSMNAS", correct any problems.
all other node types cannot use this platform type.
System action: The session request is refused. The ANR0481W Session session number for node node
server operation continues. name (client platform) was terminated. The
client did not respond within
User response: Verify that the Id used by a client to
commtimeout seconds seconds.
sign on has the proper platform type.
Explanation: The server ends a client session because
the client was holding database locks during a
transaction. The client did not respond within the
number of seconds specified by the COMMTIMEOUT
server option.

System action: The server rolls back the transaction determine the problem. Correct the programming error
that was in progress and the session is ended. Server in the client program. If the error cannot be isolated
operation continues. and resolved, contact your service representative.
User response: If this message appears frequently, If this session is a proxied LAN-Free session for a
consider incrementing the value specified for the storage agent, this error may be the result of a mount
COMMTIMEOUT option. Use the SETOPT command to point or volume preemption on the storage agent.
change the value of the COMMTIMEOUT option Review the messages logged by the storage agent to
without stopping or restarting the server. This update determine if a storage agent action caused this to occur.
changes the amount of time that the server waits for an
expected client message during an operation that
causes a database update.
sufficient memory is not available.
name (client platform) terminated - idle for
because sufficient memory (virtual memory) is not
more than idletimeout minutes minutes.
available.
Explanation: The server ends a client session because
System action: The server ends the session and
it has been idle for more minutes than specified in the
IDLETIMEOUT parameter in the server options file.
The client program will automatically attempt to User response: See the documentation for the
reconnect to the server when necessary. operating system about how to increase memory for an
application.
User response: If the problems persists, increase the
value specified for the IDLETIMEOUT parameter in the
server options file and restart the server. Many times,
internal error detected.
the client program is idle while waiting for the user to
choose an action to perform (for example, backup, Explanation: The specified client session is ended by
archive, restore, or retrieve files). If a user starts the the server because an internal processing error has been
client program and does not choose an action to detected on the server. A programming error may have
perform, the session will eventually time out. The client occurred in the server program.
program automatically reconnects to the server when
the user chooses an action that requires server System action: The session is ended and server
participation. Note that a large number of idle sessions operation continues.
can inadvertently prevent other users from connecting User response: If this session is a proxied LAN-Free
to the server, so care should be used when increasing session for a storage agent, this error may be the result
the IDLETIMEOUT parameter. of a mount point or volume preemption on the storage
agent. Review the messages logged by the storage
ANR0483W Session session number for node node agent to determine if a storage agent action caused this
name (client platform) terminated - forced to occur.
by administrator. If the cause of the error can not be determined after
Explanation: The server ends a client session in reviewing the activity log, contact your service
response to a CANCEL SESSION command issued by representative.
an authorized administrator.
System action: The server rolls back any transactions ANR0487W Session session number for node node
in progress for the terminated client session. name (client platform) terminated -
preempted by another operation.
Explanation: The server ends a client session in
response to a cancel request issued by a higher priority
ANR0484W Session session number for node node operation that needed the mount point that the client
name (client platform) terminated - was using.
protocol violation detected.
System action: The server rolls back any transactions
Explanation: The server ends the specified session in progress for the terminated client session.
because a communications protocol error by the client
has been detected. User response: Reissue the operation. If this message
appears frequently, consider increasing the mountlimit
System action: The server ends the client session. value for the affected device class.
User response: Examine the client message to

ANR0488W Session session number for node node ANR0490I Canceling session session number for
name (client platform) terminated - node node name (client platform) .
transfer rate is less than (transfer rate)
Explanation: The server is canceling client session
and more than (elapsed time since first data
number session number. This message is displayed in
transfer) minutes have elapsed since first
response to the CANCEL SESSION command.
data transfer.
Depending on the state of the session, it may take a
Explanation: The server is canceling client session while for the session to be canceled.
number session number. Depending on the state of the
System action: The session is canceled and server
session, it may take a while for the session to be
operation continues.
canceled. The server ends a client session because it has
been active for more minutes than specified in the User response: None.
THROUGHPUTTIMETHRESHOLD parameter in the
server options file and the data transfer rate is less than
the amount specified with the ANR0491I No matching session(s) found to cancel.
THROUGHPUTDATATHRESHOLD parameter in the Explanation: The server cannot find any sessions to
server options file. The client is transferring data to the cancel matching the specifications entered in the
server at an abnormally slow rate and may have CANCEL SESSION command.
become a bottleneck for handling data from other
clients. If the client has caused log records to be System action: Server operation continues.
written, it is possible that this client will prevent log User response: Use the QUERY SESSION command to
space reclamation. ensure that the session you wish to cancel is connected.
System action: The session is canceled and server Reissue the command using the appropriate session
operation continues. number to cancel the client session.
User response: If a low data transfer rate is not a

problem, the THROUGHPUTTIMETHRESHOLD or ANR0492I All drives in use. Session session number
THROUGHPUTDATATHRESHOLD parameters in the for node node name (client platform) being
server options file can be set to zero - this will disable preempted by higher priority operation.
the throughput check. The change can be made without Explanation: When a high priority operation
taking down the server and restarting it by using the attempted to find an available drive, all the drives were
SETOPT THROUGHPUTTIMETHRESHOLD or the being used. To free up a drive for this operation, the
SETOPT THROUGHPUTDATATHRESHOLD client session identified is being cancelled by the
commands. If a low data transfer rate is not expected, system.
external causes should be investigated. This would
include network problems and problems in accessing System action: The lower priority client session is
data on the client node. The client program may cancelled to free up a mount point (drive).
automatically reconnect to the server, so this message User response: When a drive again becomes available,
may appear on subsequent sessions until the data restart the session that was cancelled. This session was
transfer problem is resolved. The default server most likely a backup/archive session and you may just
operation is not to perform a throughput check. want to let it restart automatically during its next
scheduled backup window. If this message appears
ANR0489W Session session number refused for client frequently, you may want to increase the number of
node name - NAS type nodes are not drives available. See the MOUNTLIMIT parameter on
supported by a storage agent. the UPDATE DEVCLASS command.
Explanation: The specified client tried to connect to a

storage agent. The storage agent does not support a ANR0493I Restore session session number canceled.
node that is defined as TYPE=NAS. Explanation: The specified session was canceled with
System action: The session request is refused. The the CANCEL RESTORE command.
server operation continues. System action: The restore session is canceled and
User response: The client should be re-configured to server operation continues.
not try LAN-free operations. This may be done by User response: None.
setting UPDATE NODE ENABLELANFREE=NO for the
client.

ANR0494I Volume volume name in use. Session ANR0498W Session session number refused for client
session number for node node name (client node name because restore DB is in
platform) being preempted by higher progress.
priority operation.
Explanation: Restore DB is in progress, only
Explanation: When a high priority operation connection from Client related to restore DB are
attempted to acquire a specific volume, it was being allowed.
used. To free the volume for this operation, the client
session identified is being cancelled by the system.
server Restore DB operation continues.
System action: The lower priority client session is
cancelled to free up the volume.
User response: Restart the session that was cancelled,
ANR0500W Transaction failed for session session
it will wait until the higher priority operation if
number for node node name (client
finished with the volume. This cancelled session was
platform) - invalid password submitted.
most likely a backup/archive session and you may just
want to let it restart automatically during its next Explanation: The server ends a password update
scheduled backup window. transaction because the user has not correctly specified
the current password.
ANR0495I Cannot cancel the specified System action: Server operation continues.
EXPORT/IMPORT session.
User response: Update your password by correctly
Explanation: The server cannot cancel the session specifying the current password. If the current
specified in the CANCEL SESSION command. password has been misplaced, the administrator can
reassign a password for the client by using the
UPDATE NODE or UPDATE ADMIN command.
User response: Export/Import sessions cannot be
canceled using CANCEL SESSION. The user should
use the CANCEL PROCESS command to terminate the
EXPORT/IMPORT operation.
platform) - invalid policy binding
specified.
ANR0496E Session session number operation for
Explanation: The server ends a database update
client client node name (client platform) has
transaction for the specified session because an invalid
been denied because verb (type verb
management class has been specified for a file or
name) is not allowed when archive
directory object.
retention is active.
System action: The specified session is ended and
Explanation: The server refuses the specified client
operation because archive retention protection is active.
User response: Do not send the specified operation to installation using WDSF verbs. Otherwise, contact your
the server when archive retention protection is active. service representative.
ANR0497W Session request refused from ANR0502E Transaction failed for session session
non-Express client. number for node node name (client
platform) - A storage pool for the target
Explanation: A non-Express client has requested a
destination is associated with a device
session with the Express server. Only connections from
class that has a Centera device type.
an Express client will be accepted by an Express server.
transaction for the specified session because an invalid
management class has been specified. Centera device
User response: None. types may be used only for archive objects.
User response: Ensure that Centera device types are
associated with device classes that are used only for
archive operations. The UPDATE COPYGRP command

can be used to update copy groups associated with created prior to this level of the server cannot be used
space management and/or backup storage pools so to restore the database. A new database backup image
that they point to valid destinations. is needed to ensure that the database is protected.
System action: A full database backup is started.
ANR0503I Session session number for administrator
administrator name logged in as node node
name restored or retrieved object type
object: node node name, filespace filespace ANR0507E Protocol error on session session number
name, object object name, version version for node client node name (client platform)
of total version. because an owner was not properly
provided for the indicated node.
Explanation: This message logs information about an
object that was restored or retrieved by an Explanation: The session does not adhere to the
administrator logged in for a node. client-server exchange sequence, therefore the server
detected a protocol error on the specified session.
User response: If the client runs in a non-standard
environment, the server detects that the owner field is
not being sent properly. It is not recommended to run
name(Userid=user id), restored or
the client in a non-standard environment.
retrieved object type object: node node
name filespace filespace name, object object
name, version version of total version. ANR0508E An automatic full database backup for
database DB Alias has failed.
Explanation: This message logs information to the
activity log about an object that was restored or Explanation: A full database backup failed. This
retrieved by a user logged in for a node. A user ID message always accompanies one or more other
with no value indicates that an administrative or root message that provides more details about the error.
user on the platform initiated the restore.
System action: The server operation continues.
User response: Examine the server messages that were
User response: None. issued prior to this message to determine the source of
the error. Issue the QUERY ACTLOG command to view
the activity log and search for messages.
ANR0505E The database manager encountered a
null value for column name during the
data fetching. ANR0509E The database restore failed on DB Alias
due to the log format differences
Explanation: The server received an unexpected data
between database manager versions.
value.
Explanation: The database restore failed because the
System action: The server cannot process the
backup image was produced by a previous version of
command.
User response: Before reissuing the command, try the
System action: The database restore terminates.
following actions:
v Reboot the system. User response: If you need to restore the database
immediately, uninstall the upgraded server, re-install
v Check that the directories for dbdir, log, or devices
the previous version of the server, then run the restore
exists and that the file system is mounted (if it is on
command. Otherwise, start the upgraded server. The
a separate file system).
upgraded server creates a new backup image
v Make sure that the hardware and network automatically. After the database backup completes, run
connection are working properly. the server restore utility again.
v Fix any errors in the system log or db2diag.log.
ANR0510I Session session number opened input
ANR0506I A full backup has been started for volume volume name.
database DB Alias. This backup is
Explanation: The indicated session has opened the
required.
specified volume for input processing.
Explanation: This level of the IBM Spectrum Protect
server uses a new version of the database manager that
has a new format for log files. Database backups User response: None.

User response: Review the server activity log for

ANR0511I Session session number opened output
message ANR0162W for an explanation of the error
volume volume name.
that caused this statement to fail.
Explanation: The indicated session has opened the
specified volume for output processing.
ANR0517E command: The DEDUPLICATION
System action: Processing continues. parameter cannot be used with either
the TYPE=SERVER or TYPE=NAS
parameter.
System action: The command failed.
ANR0512I Process process number opened input
volume volume name. User response: Reissue the command without the
DEDUPLICATION parameter.
Explanation: The indicated process has opened the
specified volume for input processing. You may or may
not see an associated ANR0515I message for this ANR0518W NDMP restore failed for session session
process/volume combination, since some volumes are number for node node name (client
shared between multiple processes. platform), file space filespace.
System action: Processing continues. Explanation: The server ends a restore operation for
the specified NAS node because an error has been
encountered on the server. Some common reasons for
the error are:
ANR0513I Process process number opened output v The input volume is unavailable
volume volume name.
v The storage pool is unavailable
Explanation: The indicated process has opened the v Data is corrupted on the input volume
specified volume for output processing. You may not
v Hardware or media failure has occurred
see an associated ANR0515I message for this
process/volume combination, since some volumes are v The server database is corrupted
shared between multiple processes. System action: The server ends the restore operation.
System action: Processing continues. User response: Examine any prior error messages to
User response: None. determine the source of the error. Use the QUERY
ACTLOG command to view the activity log and search
for messages if needed. Correct any problem and try
ANR0514I Session session number closed volume the restore again. If the data is also backed up in a
volume name. copy storage pool, the retry operation will attempt to
Explanation: The indicated session has finished using read the file from the alternate location. If retry of the
the specified volume. restore operation continues to fail contact your service
representative.
User response: None. ANR0519E A retrieve or restore operation failed for
session session number for node node name
(client platform). An invalid partial object
ANR0515I Process process number closed volume
request was received.
volume name.
Explanation: The server ended a file retrieve or restore
Explanation: The indicated process has finished using
operation for the specified session because an invalid
the specified volume. It is possible that the process
value for the offset, length, or both was received from
indicated was not the process that opened the volume.
the client application for the object being retrieved or
System action: Processing continues. restored.
User response: None. System action: The server ends the specified operation
and server operation continues.
ANR0516E SQL processing for statement statement User response: Specify an offset, length, or both
failed. within the bounds of the object to be retrieved or
restored, and rerun the application.
Explanation: The indicated select statement failed. The
failure was caused by a syntax error with the statement
itself.
System action: The select statement failed.

hierarchy. Ensure that you size the file system based on

the amount of data that you manage. Add storage
space by using operating system tools. On the UPDATE
platform) - storage pool pool name is not
STGPOOL command, specify the ACCESS parameter as
defined.
READWRITE to ensure that client nodes and server
Explanation: The server rolls back a database update processes can read and write to the storage pool.
transaction for the specified session because the
destination specified for a management class copy
group specifies the named storage pool, but that
storage pool does not exist.
platform) - error on output storage
System action: Server operation continues. device.
User response: An administrator with policy authority Explanation: The server ends a database update
over the client policy domain must correct management transaction for the specified client because an I/O error
class definitions so that copy group destinations refer has been encountered by the server in writing to a
to defined storage pools, or the specified storage pool device.
must be created by an authorized administrator.
User response: Query the activity log to find messages
preceding this one that specify the failing device.
platform) - object excluded by size in
Storage pool volumes can be varied offline (by using
storage pool pool name and all successor
the VARY command), or the server may need to be
pools.
halted to correct the hardware problem. After the
Explanation: The server ends a database update problem is corrected, the client should retry the
transaction for the specified session because the size of operation.
a file sent from the client node is larger than that
allowed in the storage pool specified in the client's
management class copy group. No successor storage
pools to the one specified on the copy group can accept
platform) - data transfer interrupted.
the large file.
Explanation: The database transaction associated with
session session number was aborted because data
transfer to or from data storage was interrupted by an
User response: If the client is not using compression external event.
to send files to the host, turn compression on for the
System action: The session is canceled and server
client (using the UPDATE NODE command) to try and
resolve the problem. Otherwise, the maximum file size
for one or more of the storage pools in the storage User response: Examine the messages issued prior to
hierarchy can be increased to accommodate the file. An this message to determine why the data transfer was
authorized administrator can increase the MAXSIZE interrupted. Attempt the client operation again if the
parameter by issuing the UPDATE STGPOOL problem can be resolved.
command.
ANR0522W Transaction failed for session session number for node node name (client
number for node node name (client platform) - storage media inaccessible.
platform) - no space available in storage
pool pool name and all successor pools. Explanation: The server ends a transaction for the
specified session because storage volumes are not
Explanation: The server ends a database update available in the storage pools in which the client's files
transaction for the specified session because the storage are to be stored.
pool specified in the client's management class copy
group does not contain enough free space to hold the System action: The server ends the specified session
files sent from the client. Successor storage pools to the and server operation continues.
one specified on the copy group do not contain enough User response: An authorized administrator can issue
free space. the DEFINE VOLUME command to add storage to one
System action: The specified session is ended and or more storage pools in the storage hierarchy. The
server operation continues. VARY ONLINE command can be used to vary offline
storage volumes online in the storage hierarchy to
User response: An authorized administrator can add make them available to client nodes for file storage.
storage to one or more storage pools in the storage

System action: The server ends the specified session

ANR0526W A transaction failed for session session
platform) because of insufficient recovery User response: See the documentation for the
log space. operating system about how to increase memory for an
application.
Explanation: If a log runs out of space, the current
transaction is rolled back. The server issues an error
message and halts. You cannot restart the server until ANR0530W Transaction failed for session session
the recovery log size is increased. number for node node name (client
platform) - internal server error detected.
transaction for the specified session because an internal
logic error is detected.
nearly full, run a full database backup to remove System action: The server ends the specified session
archive logs and consider adding more disk space to and server operation continues.
full and the active log space is full or nearly full, User response: Examine the server messages that were
update the value of the ACTIVELOGSIZE option in the issued prior to this message to determine the source of
dsmserv.opt file. Set the value of the ACTIVELOGSIZE the error. Issue the QUERY ACTLOG command to view
option to the new maximum size of the active log. the activity log and search for messages that indicate
the source of the error.
ANR0527W A transaction failed for session session

number for node node name (client ANR0531W Transaction failed for session session
platform) because of insufficient database number for node node name (client
space. platform) - invalid file space identifier
specified by client.
transaction for the specified session because the server Explanation: The server ends a database update
has insufficient database space. transaction for the specified session because the file
space identified by the client for the transaction does
System action: The server ends the specified session, not exist.
but server operation continues.
System action: This action usually occurs when a
User response: To increase the amount of database client is operating on a file space that is currently being
space that is available to the server, issue the EXTEND deleted as a result of an administrative command or
DBSPACE command. Add one or more directories to client action. The server ends the specified session and
the database. server operation continues.
User response: Use the QUERY PROCESS command
ANR0528W Transaction failed for session session to monitor and wait for any file space deletion
number for node node name (client processes to complete, or cancel the process if you do
platform) - thread resource not available. not want to delete the file space. Try the client action
again after this action has been taken.
transaction for the specified session because sufficient
memory is not available for starting additional ANR0532W Diagnostic(ID): Transaction transaction ID
processes on the server. was aborted for session session number
for node node name (client platform).
and server operation continues. Explanation: An error has been detected during a
transaction commit for the specified session. This
message should be preceded by other messages that
give additional information about the failed transaction.
application.
fails.
number for node node name (client User response: Check for additional messages and
platform) - insufficient memory. eliminate the condition that caused the failed
transaction. If the error cannot be isolated and resolved,
contact your service representative.
transaction for the specified session because sufficient
memory is not available on the server.

If the suspected cause of the failure is that a file grew

in size during compression on the client, another
number - compression method used by
possible circumvention is to set the
client not supported. Please obtain the
COMPRESSALWAYS option in the client options file to
latest level of the client code.
NO and retry the operation. This may allow the client
Explanation: The server ends the transaction for the to accurately report the file size and possibly avoid the
specified session because the compression method that out of space condition in the storage pool.
is used by the client is no longer supported by the
server.
System action: The server ends the specified session number for node node name (client
and server operation continues. platform) - insufficient mount points
available to satisfy the request.
User response: The client must either backup the data
with compression turned off, or upgrade to a client that Explanation: The server was unable to allocate
supports the newer compression method. If the client is sufficient mount points to process the transaction.
a WDSF client, upgrade to a non-WDSF client in order
System action: The operation is ended and server
to use the compression performed by the client.
User response: If necessary, make more mount points
available or validate your device class and library
configuration.
platform) - size estimate exceeded and
server is unable to obtain additional
space in storage pool pool name. Size ANR0536W Transaction failed for session session
estimate was size estimate. number for node node name (client
platform) - down-level client does not
support format of stored files.
transaction for the specified session because the size
estimate provided by the client is too small. The server Explanation: A client attempts to perform an
has attempted to obtain additional space in the operation involving files that are stored in a format that
indicated storage pool, but was unable to do so. is not supported by that client level.
System action: The specified session is ended and System action: The operation is ended and server
server operation continues. operation continues.
If pool name is a random access storage pool with User response: Upgrade the client to a later level.
caching enabled, it is also possible that additional space
can be made available in this storage pool by
eliminating cached files. When the server allocates ANR0537E Transaction failed for session session
space based on the size estimate provided by the client, number for node node name (client
it frees space occupied by cached files if this space is platform) - filespace name cannot be
needed to obtain the estimated space. However, if the renamed from or to a Unicode name.
server later determines that the file size estimate was Explanation: The server ends a database update
too low, it attempts to obtain additional space that is transaction for the specified session because a file space
not utilized, but does not delete cached files to do so. was attempted to be renamed to or from unicode.
If the client sending the data has the option System action: The server ends the specified
COMPRESSALWAYS YES set, it is possible that a file transaction and server operation continues.
grew during the compression operation and when the
client sent it to the server it exceeded the space User response: Do not attempt to rename a unicode
available in storage pool pool name. file space to a non-unicode name or a non-unicode file
space to a unicode name.
User response: This message may indicate that there
is no additional space in pool name. The following are
possible circumventions: ANR0538I A resource waiter has been aborted.
An authorized administrator can issue the DEFINE Explanation: The server aborts a resource wait
VOLUME command to add storage to this pool. because of waiting too long for a resource to become
available. This could cause a process or session to fail.
If the suspected cause of the failure is that pool name is If this causes a process or a session to fail then there
a DISK storage pool and that space in use by cached will be other messages at this time indicating which
files was not freed, turn off caching for the storage pool process or session has failed. Resources are internal
and issue the MOVE DATA command for the volumes server resources such as locks and synchronization
in pool pool name. objects.

System action: The server terminates the resource System action: The server ends the specified session
with request and server operation continues. and server operation continues.
User response: Either a server deadlock situation has User response: Query the activity log to find messages
occurred or the resource timeout value is set too low. preceding this one that specify the device that is failing.
Check the setting for the RESOURCETimeout server Storage pool volumes can be varied offline (by using
option and increase the value. If the problem persists the VARY OFFLINE command), or the server may need
with a higher timeout then contact your service to be shut down by using the HALT command to
representative. correct the hardware problem. After the problem is
corrected, the client may try the operation again.
number for node node name. This node ANR0542W Retrieve or restore failed for session
has exceeded its maximum number of session number for node node name (client
mount points. platform) - storage media inaccessible.
Explanation: The server ends the transaction because Explanation: The server ends a client retrieval or
the node requires mount points to store data, and restore operation for the specified session because a
either the node is not allowed to acquire any mount needed storage pool volume has been varied offline or
points, or the node is already using the maximum the storage pool is unavailable.
number of mount points allowed for the node. The
maximum number of mount points a node is allowed
to use on the server is controlled by the setting of the
MAXNUMMP parameter on the REGISTER NODE or User response: Use the VARY ONLINE command to
UPDATE NODE command. vary offline storage volumes online in the storage
hierarchy and make them available to client nodes for
file storage. If all volumes are online, check the
ACCESS parameter of the storage pool. If the access
User response: If the number of mount points that the mode is UNAVAILABLE, use the UPDATE STGPOOL
node is allowed to use on the server are already command to update it to READONLY or READWRITE.
acquired, reduce the number of client sessions for the
specified node that are running concurrently. For
ANR0543W Retrieve or restore failed for session
example, decrease the value of the client option
RESOURCEUTILIZATION. If sufficient mount points
platform) - data transfer interrupted.
(for example, drives) are available to satisfy the data
store operations, issue the UPDATE NODE command Explanation: The database transaction associated with
to increase the value of the MAXNUMMP parameter. session session number was aborted because data
If the node is not allowed to acquire any mount points
external event.
(the node's MAXNUMMP option is set to zero), issue
the UPDATE NODE command to change the value of System action: The session is canceled and server
the MAXNUMMP parameter. operation continues.
User response: Examine the messages issued prior to
ANR0540W Retrieve or restore failed for session this message to determine why the data transfer was
session number for node node name (client interrupted. Attempt the client operation again, if the
platform) - data integrity error detected. problem can be resolved.
Explanation: The server ends a file retrieval operation
for the specified session because an internal database ANR0544W Retrieve or restore failed for session
integrity error has been encountered on the server. session number for node node name (client
platform) - thread resource not available.
and continues operation. Explanation: The server ends a file retrieval or restore
operation for the specified session because sufficient
memory is not available for starting additional
processes on the server.
platform) - error on input storage device.
Explanation: The server ends a client retrieval or
restore operation for the specified session because an
application.
I/O error has been encountered by the server in
reading from a device.

v The input volume is unavailable

session number for node node name (client v The storage pool is unavailable
platform) - insufficient memory. v Data is corrupted on the input volume
Explanation: The server ends a file retrieval or restore v Hardware or media failure has occurred
operation for the specified session because sufficient v Database corruption
System action: The server ends the specified session and continues operation.
User response: Try the restore or retrieve operation
User response: See the documentation for the again, and if the file is also backed up in a copy storage
operating system about how to increase memory for an pool, the operation will attempt to read the file from
application. the alternate location. If retry of the restore or retrieve
operation continues to fail examine any prior error
messages to determine the source of the error. Use the
QUERY ACTLOG command to view the activity log
and search for messages if needed. Correct the problem
platform) - internal server error detected.
and try the restore or retrieve again.
Explanation: The server ends a file retrieval or restore
operation for the specified session because an internal
logic error is detected in the server program.
System action: The server ends the specified session platform) - no existing restore session
and continues operation. found.
User response: Examine the server messages issued Explanation: A client attempted to start an additional
prior to this message to determine the source of the no query restore session to increase restore throughput,
error. Use the QUERY ACTLOG command to view the but the original restore session was not found.
activity log and search for messages. If the error cannot
be isolated and resolved, contact your service
representative.
User response: Check the status of the original restore.
It may have already completed or been cancelled. The
ANR0547E Invalid data was encountered in the
QUERY SESSION command and the QUERY RESTORE
command processor output stream:
commands can provide information about existing
output formatting terminated for the last
sessions and restore sessions which are restartable.
command entered.
Explanation: The server console session encounters an
ANR0550E The client operation failed for session
error in formatting output from a command.
System action: The command output is discarded and platform) - see previous error messages.
Explanation: The indicated operation has failed. This
User response: Use the server QUERY command to message is always preceded by one or more other error
determine if the command you entered had the desired messages which provide more detail about why the
affect in the server. Use the QUERY ACTLOG command failed.
command to see if a server error condition (like out of
memory) occurred prior to the command. Resolve the
error if it is found. Contact your service representative
if you cannot resolve the error, or if an error is not User response: Examine the previous error messages
found. to determine the source of the error. Use the QUERY
for messages if needed. Correct the problem and try the
command again.
platform) processing file space filespace
(fsId filespace id) for file file name stored ANR0551E The client operation failed for session
as storage repository - error detected. session number for node node name (client
platform) - lock conflict.
for the specified session because an error has been Explanation: An operation that requires the server to
encountered on the server. Some common reasons for lock a system resource has been initiated. The operation
the error are: cannot be executed because the resource is already in

use by another command or process.

ANR0555E command name: The parameter name
System action: The server does not process the parameter cannot be specified when the
command. TOSERVER parameter is specified.
User response: Try the command again at a later time. Explanation: The command failed because the
TOSERVER parameter was not specified.
ANR0552E Client operation failed for session System action: The command fails and server
session number for node node name (client operation continues.
platform) - destination storage pool
User response: Reissue the command and omit the
storage pool was skipped.
TOSERVER parameter.
Explanation: The indicated client operation failed
because the destination storage pool was skipped. A
ANR0556E command name: DATES=RELATIVE
storage pool may be skipped because it does not have
parameter value cannot be specified
enough available space, or because it has a MAXSIZE
when merging imported files using the
value that is less than the size of the object to be
MERGE=YES parameter value.
inserted.
Explanation: When importing files and merging them
into existing file spaces, the DATES=RELATIVE
User response: Ensure that the destination storage parameter value cannot be specified.
pool is available, has an adequate MAXSIZE setting,
System action: The command fails and server
and has adequate space. The MAXSIZE setting may be
changed using the UPDATE STGPOOL command.
Space may be added to the storage pool by checking in User response: Reissue the command and omit the
scratch volumes or defining new volumes in the DATES=RELATIVE parameter.
storage pool. If volumes in the destination storage pool
are offline, use the VARY ONLINE command to vary
ANR0557I Import command: An invalid export
them online and make them available for use. Correct
record (version version, copy type copy
the problem and try the command again.
type, object type object type) was found.
Explanation: An invalid import record was found for
ANR0553E Client operation failed for session
the specified version, copy type and object type. The
session number - administrator
object will be skipped, and import processing will
administrator name does not have
continue.
adequate authority over node node name.
Explanation: The specified administrator does not
have the proper authority necessary to perform this User response: Issue QUERY ACTLOG to determine
operation on the specified node. the source of the error.
System action: The server does not perform the query.
ANR0558W Import processing did not create a
User response: Issue the command from a properly
proxynode association for nodes
authorized administrator ID, or contact the system
node_id_target and node_id_agent.
administrator to have additional authority granted to
the current administrator ID. Explanation: Import processing did not create a
proxynode association between the two nodes. The
association fails if either of the nodes does not exist on
ANR0554E command name: The parameter name
the server, or if import processing was not allowed to
parameter is only valid if the
complete.
TOSERVER parameter is specified.
System action: The server does not create the
Explanation: The command failed because the
specified proxynode association.
TOSERVER parameter was not specified.
User response: Verify that both nodes were imported
properly and issue the import command again. Or, use
the GRANT PROXYNODE command to manually
User response: Reissue the command and specify the create the proxynode association.
TOSERVER parameter.

ANR0559E Too many domains are specified on the ANR0563W NDMP restore failed for node node name,
EXPORT NODE command. file space filespace.
Explanation: The maximum length of the domain list Explanation: The server ends a restore operation for
cannot exceed approximately 1400 characters. the specified NAS node because an error has been
encountered on the server. Some common reasons for
System action: The EXPORT command is ended.
the error are:
User response: If you specified DOMAIN=* on the v The input volume is unavailable
command, issue the command again without specifying
the domain to let it default to all domains. If you
specified a domain list, then split up the EXPORT into v Data is corrupted on the input volume
multiple export commands to reduce the number of v Hardware or media failure has occurred
domains specified on the command. v The server database is corrupted
System action: The server ends the restore operation.
ANR0560E Import command: Unable to decrypt
encrypted password or key. User response: Examine any prior error messages to
determine the source of the error. Use the QUERY
Explanation: The server is not able to decrypt the ACTLOG command to view the activity log and search
password associated with a node or administrator, or for messages if needed. Correct any problem and try
the client encryption key associated with an object the restore again. If the data is also backed up in a
being imported. The password or key was encrypted copy storage pool, the retry operation will attempt to
with the AES encryption standard, but the server does read the file from the alternate location. If retry of the
not support AES. restore operation continues to fail contact your service
System action: The object is not imported. representative.
User response: Rerun the export command, specifying

the ENCryptionstrength=DES option. Or, rerun the ANR0564E Restartable restore request failed for
import on a server that supports AES. session session number, restartable restore
session restore session number - sessions
are active from the original restore.
ANR0561E Export command: Process aborted - sign
on to server, target server name, failed. Explanation: A client attempted to restart a restartable
no query restore session; However, sessions from the
Explanation: The server export process encountered original no query restore invocation are still active.
an error in establishing a communication session with Both the current and restartable restore session
the target server. numbers are shown.
System action: The export process ends and server System action: The restartable restore request is ended
operation continues. and server operation continues. The restore's
User response: Check the activity log and server restartability status does not change.
console for messages that indicate a failure or problem User response: Check the status of the original restore.
on the server issuing this command and on the target The QUERY RESTORE command can be used to show
server. Next, check the server definition, administrator the status of restartable restores. The restartable restore
name, and password on both the server issuing the session number is the one for which sessions were
command and the server specified. Also, check the found to be running. Sessions may be active on either
communication connection between the two servers. the server or a storage agent. Restartable restores may
And finally, verify that the target server specified is be cancelled by issuing the CANCEL RESTORE
running. If the problem is not resolved, contact your command, after which the restore may be retried. Once
service representative. CANCEL RESTORE is issued for a restore session, it is
not eligible to be restarted.
ANR0562I Export command: Data transfer complete,
deleting temporary data. ANR0565W Retrieve or restore failed for session
Explanation: The server export process has completed session number for node node name (client
writing data to the target media or server. Temporary platform). The storage volume volume
data used during the operation is now being deleted name is inaccessible.
from the database. Explanation: The server ends a client retrieval or
System action: The export process continues until all restore operation for the specified session because a
temporary data is removed. needed storage pool volume has been varied offline.
User response: None. System action: The server ends the specified session

User response: Use the VARY ONLINE command to name, identified by type, file space and object name was
vary offline storage volumes online, and make them not processed.
available to client nodes for file storage.
System action: Server action is defined by the error
that occurred.
User response: Issue QUERY ACTLOG to determine
the source of the error.
platform) - file was deleted from data
storage during retrieval.
ANR0570E Export command: Invalid value for
DURUNITS parameter detected while
for the specified session because the file has been
exporting administrative schedule
deleted from data storage by another process before
schedule name - default or existing value
retrieval is complete.
is used during import.
Explanation: During processing of command export
and continues operation.
command, an invalid value is encountered for the
User response: Contact your administrator to find out DURUNITS parameter for administrative schedule
if DELETE FILESPACE, DELETE VOLUME, or schedule name.
inventory expiration processes are running; these
System action: Export processing continues, but the
processes can delete data storage files during retrieval.
exported data contains an unknown DURUNITS value
Reissue the restore or retrieve operation and specify a
for this schedule. If this data is imported, the server
different file version.
uses the default or existing DURUNITS value.
User response: Update the DURUNITS value for this
ANR0567W Retrieve or restored failed for session
schedule and restart the export command. Alternatively,
the export data with the unknown value can be used,
platform) - insufficient mount points
and the DURUNITS value can be checked and updated
available to satisfy the request.
after import processing has been performed.
Explanation: The server was unable to allocate
sufficient mount points to process the retrieve or
restore operation.
PERUNITS parameter detected while
System action: The operation is ended and server exporting administrative schedule
operation continues. schedule name - default or existing value
available. Explanation: During processing of command export
PERUNITS parameter for administrative schedule
ANR0568W Session session number for admin admin
schedule name.
connection with client severed. System action: Export processing continues, but the
exported data will contain an unknown PERUNITS
Explanation: The specified admin session is ended
value for this schedule. If this data is imported, the
because the communications link has been closed by a
server uses the default or existing PERUNITS value.
network error or by the client program.
User response: Update the PERUNITS value for this
User response: If a user breaks out of a client use the export data with the unknown value, and check
program, this message will be displayed on the server and update the PERUNITS value after import
as the connection is suddenly closed by the client. A processing has been performed.
network failure can also cause this message to be
displayed. If a large number of these messages occur
simultaneously, check the network for failure and
DAYOFWEEK parameter detected while
correct any problems.
exporting administrative schedule
schedule name - default or existing value
ANR0569I Object not processed for node name: is used during import.
type=type, file space=filespace name,
object=object name.
Explanation: An error occurred. The object for node DAYOFWEEK parameter for administrative schedule
schedule name.


ANR0576E Import command: Invalid value for
exported data contains an unknown DAYOFWEEK
DURUNITS or PERUNITS parameter in
exported data - administrative schedule
server uses the default or existing DAYOFWEEK value.
schedule name defined with default
User response: Update the DAYOFWEEK value for values for DURATION, DURUNITS,
this schedule and restart the export command. PERIOD, and PERUNITS.
Alternatively, use the export data with the unknown
Explanation: During processing of command import
value, and check and update the DAYOFWEEK value
DURUNITS or PERUNITS parameter for administrative
schedule schedule name.
ANR0573I Export/import command: Processing
System action: Processing of the command continues,
administrative schedule schedule name.
by using the default values for DURATION,
Explanation: The background export or import DURUNITS, PERIOD, and PERUNITS.
process to service the command export/import command
User response: Verify that the correct values have
is currently processing the schedule definition
been used for DURATION, DURUNITS, PERIOD, and
information for administrative schedule schedule name.
PERUNITS. Update these values, if necessary.
System action: Export or import processing for the
command continues.
User response: None. DAYOFWEEK parameter in exported
data - administrative schedule schedule
name defined with default DAYOFWEEK
ANR0574E Import command: Invalid value for value.
exported data for administrative Explanation: During processing of command import
schedule schedule name. command, an invalid value is encountered for the
DAYOFWEEK parameter for administrative schedule
Explanation: During preview processing of command schedule name.
import command, an invalid value is encountered for the
DURUNITS or PERUNITS parameter for administrative System action: Processing of the command continues,
schedule schedule name. by using the default DAYOFWEEK value for this
schedule.
System action: Processing of the command continues.
If a later command is issued that causes the data to be User response: Verify that the correct DAYOFWEEK
imported, the default or existing values are used for value has been used for this schedule. Update this
DURATION, DURUNITS, PERIOD, and PERUNITS. value, if necessary.
User response: If the data is imported with a later

command, verify that the correct values for ANR0578E Import command: Invalid value for
DURATION, DURUNITS, PERIOD, and PERUNITS are DURUNITS or PERUNITS parameter in
used for this schedule. exported data - existing values for
DURATION, DURUNITS PERIOD, and
PERUNITS for administrative schedule
ANR0575E Import command: Invalid value for schedule name were not updated.
DAYOFWEEK parameter in exported
data for administrative schedule schedule Explanation: During processing of command import
name. command, an invalid value is encountered for the
DURUNITS or PERUNITS parameter for administrative
Explanation: During preview processing of command schedule schedule name.
DAYOFWEEK parameter for administrative schedule System action: Processing of the command continues,
schedule name. by using the existing values for DURATION,
DURUNITS, PERIOD, and PERUNITS.
If a later command is issued that causes the data to be User response: Verify that the correct values have
imported, the default or existing DAYOFWEEK value is been used for DURATION, DURUNITS, PERIOD, and
used. PERUNITS. Update these values, if necessary.
command, verify that the correct DAYOFWEEK value is
used for this schedule.

value for this copy group and restart the export.

value, and check and update the MIGREQUIRESBKUP
data - existing DAYOFWEEK value for
value after import processing has been performed.
administrative schedule schedule name
was not updated.
SPACEMGTECHNIQUE parameter in
exported data for management class
DAYOFWEEK parameter for administrative schedule
management class name in domain domain
schedule name.
name, set policy set name.
Explanation: During preview processing of command
by using the existing DAYOFWEEK value for this
schedule.
SPACEMGTECHNIQUE parameter for management
User response: Verify that the correct DAYOFWEEK class management class name, in policy domain domain
value has been used for this schedule. Update this name, policy set policy set name.
value, if necessary.
If a later command is issued that causes the data to be
ANR0580E Export command: Invalid value for imported, the default or existing
SPACEMGTECHNIQUE parameter SPACEMGTECHNIQUE value is used.
detected while exporting management
User response: None. If the data is imported with a
class management class name in domain
later command, verify that the correct
domain name, set policy set name - default
SPACEMGTECHNIQUE value is used for this
or existing value is used during import.
management class.
SPACEMGTECHNIQUE parameter in
class management class name in domain domain name,
exported data - management class
policy set policy set name.
management class name in domain domain
System action: Export processing continues, but the name, set policy set name defined with
exported data contains an unknown default SPACEMGTECHNIQUE value.
SPACEMGTECHNIQUE value for this management
class. If this data is imported, the default or existing
SPACEMGTECHNIQUE value is used.
User response: Update the SPACEMGTECHNIQUE class management class name, in policy domain domain
value for this copy group and restart the export. name, policy set policy set name.
value, and check and update the
by using the default SPACEMGTECHNIQUE value for
SPACEMGTECHNIQUE value after import processing
this management class.
has been performed.
User response: Verify that the correct
SPACEMGTECHNIQUE value has been used for this
management class. Update this value, if necessary.
MIGREQUIRESBKUP parameter
detected while exporting management
class management class name in domain ANR0584E Import command: Invalid value for
domain name, set policy set name - default SPACEMGTECHNIQUE parameter in
or existing value is used during import. exported data - SPACEMGTECHNIQUE
value for management class management
class name in domain domain name, set
policy set name was not updated.
MIGREQUIRESBKUP parameter for management class
management class name in domain domain name, policy Explanation: During processing of command import
set policy set name. command, an invalid value is encountered for the
class management class name, in policy domain domain
exported data contains an unknown value for this
name, policy set policy set name.
management class. If this data is imported, the default
or existing MIGREQUIRESBKUP value is used. System action: Processing of the command continues,
User response: Update the MIGREQUIRESBKUP

by using the existing SPACEMGTECHNIQUE value for User response: Verify that the correct
this management class. MIGREQUIRESBKUP parameter has been used for this
management class. Update this value, if necessary.
SPACEMGTECHNIQUE value has been used for this
management class. Update this value, if necessary. ANR0588E Import command: Server is down-level
compared to export data version version
number.
MIGREQUIRESBKUP parameter in Explanation: An attempt is made to import data to a
exported data for management class down-level server. The server on which the import is
management class name in domain domain performed must be at the same or later level than the
name, set policy set name. server from which the data was exported.
Explanation: During preview processing of command System action: The import process ends and server
import command, an invalid value is encountered for the operation continues.
MIGREQUIRESBKUP parameter for management class
User response: Import to a server that is at the same
management class name, in policy domain domain name,
or later level than the server from which the export
policy set policy set name.
was performed.
If a later command causes the data to be imported, the
ANR0589E Import command: Preview processing
default or existing MIGREQUIRESBKUP value is used.
terminated abnormally - server is
User response: None. If the data is imported with a down-level.
later command, verify that the correct
Explanation: Processing for the command import
MIGREQUIRESBKUP value is used for this
command in preview mode ends when it is determined
management class.
that the server is down-level compared to the export
data.
System action: Import processing ends and server
MIGREQUIRESBKUP parameter in
exported data - management class
management class name in domain domain User response: Import to a server that is at the same
name, set policy set name defined with or later level than the server from which the export
default MIGREQUIRESBKUP value. was performed.
command, an invalid value is encountered for the ANR0590E Import command: Processing terminated
MIGREQUIRESBKUP parameter for management class abnormally - server is down-level.
management class name, in policy domain domain name,
policy set policy set name. Explanation: Processing for the command import
command ends when it is determined that the server is
System action: Processing of the command continues, down-level compared to the export data.
by using the default MIGREQUIRESBKUP value for
this management class. System action: Import processing ends and server
MIGREQUIRESBKUP value has been used for this User response: Import to a server that is at the same
management class. Update this value, if necessary. or later level than the server from which the export
was performed.

MIGREQUIRESBKUP parameter in ANR0592E Export/import command: Invalid value for
exported data - MIGREQUIRESBKUP table of contents parameter - parameter
value for management class management value.
class name in domain domain name, set Explanation: The value (parameter value) specified for
policy set name was not updated. the table of contents (TOC) parameter in command
Explanation: During processing of command import export/import command is not a valid value for this
command, an invalid value is encountered for the parameter.
MIGREQUIRESBKUP parameter. System action: The command fails and server
System action: Processing of the command continues, operation continues.
by using the existing MIGREQUIRESBKUP value for User response: Reissue the command and specify a
this management class. valid TOC parameter.

space-managed file being imported does not exist in

ANR0593E Export/import command: Invalid value for
the active policy set for the domain to which the node
NOSPAN parameter - parameter value.
is assigned.
Explanation: The value (parameter value) specified for
System action: The default management class for the
the NOSPAN parameter in command export/import
node's policy domain is bound to the space-managed
command is not a valid value for this parameter.
file and import processing continues.
User response: If you want to define the missing
management class, an authorized administrator may
User response: Reissue the command and specify a cancel the import operation, define the missing space
valid NOSPAN parameter. management attributes or management class for the
domain, and process the import operation again.
ANR0594E device class: NOSPAN parameter can only
be used with a 3590 device class. ANR0598W IMPORT: Space management attributes
not found for default management class
Explanation: The device class specified must be a 3590
in domain domain name - space managed
device class when NOSPAN is set to True.
files bound to management class
System action: The command fails and server management class name in this domain
operation continues. cannot be imported.
User response: Reissue the command and specify a Explanation: During import processing, the server
valid NOSPAN/Device Class parameter. finds that a management class bound to a
space-managed file being imported does not exist in
the active policy set for the domain to which the node
ANR0595W The server deleted object count objects is assigned. When trying to rebind the space-managed
that were part of incomplete groups. file to the default management class for the domain,
Explanation: After importing data that was exported the server finds that the space-managed attributes are
from another server, the server deletes any objects that not defined for the default management class.
are part of incomplete groups. Incomplete groups may System action: The file is not imported; import
be a result of importing from media written by an processing continues.
export operation that failed. Incomplete groups may
also be a result of a failed import operation. User response: If you want to define the missing copy
group, an authorized administrator may cancel the
System action: Server operation continues. import operation, define the missing space
User response: Ensure that the export and import management attributes or management class for the
operations run to completion. If any errors are domain, and process the import operation again.
observed, correct them and run again the export or
import or both, as needed. ANR0599E Export/import command: Invalid volume
name volume name specified for device
ANR0596W Space-managed object object name for class device class name.
client node node name, filespace filespace Explanation: One of the volume names specified in
name already exists on the server - it will the VOLUMENAMES parameter for an import or
be skipped. export command is not a valid volume name for the
Explanation: While attempting to import a device class specified in the DEVCLASS parameter.
spaced-managed object, the server discovers that the System action: The export or import command fails.
object already exists. The space-managed object is
skipped. User response: Specify volume names in the
VOLUMENAMES parameter that are valid for the
System action: Server operation continues. device class specified in the DEVCLASS parameter.
ANR0600I Export command: No matching policy
ANR0597W IMPORT: Space management attributes domains found for exporting.
in management class management class Explanation: The background export process does not
name for domain domain name is not find any policy domains that match the specification
defined - default management class will entered in the export command.
be used.
System action: The export process continues and no
Explanation: During import processing, the server policy domains are exported from the server.
finds that the space management attributes for a

User response: None. User response: None.
ANR0601I Export command: No policy sets found in ANR0606I Export command: No node definitions
policy domain domain name for were found for exporting.
exporting.
Explanation: The background export process does not
Explanation: The background export process does not find any node definitions to export as specified in the
find any policy sets defined in domains matching command export command.
domain name.
System action: The export process continues.
policy sets are exported from the domain.
ANR0607I Export command: No administrator
definitions were found for exporting.
ANR0602I Export command: No management classes
were found in policy domain domain
find any administrator definitions to export as specified
name for exporting.
in the command export command.
System action: The export process continues.
find any management classes defined in policy
domains matching domain name. User response: None.
management classes are exported from the domain. ANR0608E Command: Command failed - see
previous error messages or view the
activity log.
Explanation: The indicated import command has
ANR0603I Export command: No copy groups were
failed. This message is always preceded by one or more
found in policy domain domain name for
other error messages which provide more detail about
exporting.
why the command failed.
find any copy groups defined in policy domains
matching domain name. User response: Examine the previous error messages
to determine the source of the error. Use the QUERY
copy groups are exported from the domain.
User response: None. command again.
ANR0604I Export command: No schedules were ANR0609I Command started as process process ID.
found in policy domain domain name for
Explanation: A background process has been started
exporting.
to service the command command. The background
Explanation: The background export process does not process is defined as process process ID.
find any schedules defined for policy domains
matching domain name.
User response: To query the progress of the
background process, use the QUERY PROCESS
schedules are exported for the domain.
command. To cancel the background process, use the
User response: None. CANCEL PROCESS command. Use the process ID
number to specify this specific process.
ANR0605I Export command: No schedule
associations were found in policy ANR0610I Command started by administrator name as
domain domain name for exporting. process process ID.
Explanation: The background export process does not Explanation: A background process has started to
find any schedule node associations defined for policy service the command command entered by administrator
domains matching domain name. administrator name. The background process is defined
as process process ID.
schedule associations are exported for the domain. System action: Server operation continues.


ANR0615I Import command: Reading EXPORT
NODE data from server server name
exported export date export time.
CANCEL PROCESS command. Use the process ID
number to specify this specific process. Explanation: The background import process to
service the command import command is importing
information exported from server server name with the
ANR0611I Command started by administrator name as
EXPORT NODE command on export date at export time.
process process ID has ended.
System action: Import processing continues.
Explanation: The background process to service the
command command by administrator administrator name User response: None.
has completed processing.
System action: The specified process ends, and server ANR0616I Export/import command: Preview
operation continues. processing completed successfully.
User response: None. Explanation: The background export or import
in preview (Preview=Yes) mode has completed
successfully.
SERVER data from server server name
exported export date export time. System action: Export or import processing for the
command completes. Statistics on the projected number
Explanation: The background import process to
and type of objects moved, together with the projected
total number of bytes copied, are displayed on the
server console following this message.
EXPORT SERVER command on export date at export
time. User response: None.
System action: Import processing continues.
completed with status status.
Explanation: The background export or import
POLICY data from server server name
has completed with status status. If the status is
exported export date export time.
INCOMPLETE, some files have been skipped due to
Explanation: The background import process to errors reading or writing the file.
command completes. Statistics on the number and type
EXPORT POLICY command on export date at export
of objects moved, together with the total number of
time.
bytes copied, are displayed on the server console
System action: Import processing continues. following this message. A summary of the number of
files that were skipped is also displayed.
ADMIN data from server server name ANR0618I Export/import command: Preview
exported export date export time. processing canceled before completion.
Explanation: The background import process to Explanation: The background export or import
service the command import command is importing process to service the command export/import command
information exported from server server name with the in preview (Preview=Yes) mode has been canceled with
EXPORT ADMIN command on export date at export the CANCEL PROCESS command.
time.
System action: Import processing continues. command ends. Statistics on the projected number and
type of objects moved, together with the projected total
User response: None. number of bytes copied, are displayed on the server
console following this message.

ANR0619I Command: Processing canceled before ANR0623I Export/import command: Copied number
completion. copy groups.
Explanation: The background process to service the Explanation: The background export or import
command command has been canceled with the process to service the command export/import command
CANCEL PROCESS command. copies number copy group definitions from either the
server database to export media or from export media
System action: Processing for the command command
into the server database. Data is not moved if
ends. Statistics on the number and type of objects
Preview=Yes is specified in the command export/import
moved, together with the total number of bytes copied,
command.
are displayed on the server console following this
message. System action: Export or import processing for the
command completes. Server operation continues.
ANR0620I Export/import command: Copied number
domain(s). ANR0624I Export/import command: Copied number
schedules.
process to service the command export/import command Explanation: The background export or import
copies number policy domain definitions from the process to service the command export/import command
server database to export media or from export media copies number schedule definitions from either the
into the server database. Data is not actually moved if server database to export media or from export media
Preview=Yes is specified in the command export/import into the server database. Data is not moved if
command. Preview=Yes is specified in the command export/import
command.
command completes. Server operation continues. System action: Export or import processing for the
policy sets. ANR0625I Export/import command: Copied number
administrators.
copies number policy set definitions from the server process to service the command export/import command
database to export media or from export media into the copies number administrator definitions from either the
server database. Data is not actually moved if server database to export media or from export media
Preview=Yes is specified in the command export/import into the server database. Data is not moved if
command. Preview=Yes is specified in the command export/import
command.
command completes. Server operation continues. System action: Export or import processing for the
management classes. ANR0626I Export/import command: Copied number
node definitions.
copies number management class definitions from the process to service the command export/import command
server database to export media or from export media copies number client node definitions from the server
into the server database. Data is not moved if database to export media or from export media into the
Preview=Yes is specified in the command export/import server database. Data is not moved if Preview=Yes is
command. specified in the command export/import command.
System action: Export or import processing for the System action: Export or import processing for the
command completes. Server operation continues. command completes. Server operation continues.

the export media to the server database and data

ANR0627I Export/import command: Copied filespace
storage. This figure can be used during export preview
number file spaces archive number archive
processing to estimate the number of removable media
files, backup number backup files, and
volumes needed to hold the exported information from
spacemg number space managed files.
the server.
copies filespace number client file space definitions,
archive number archive file copies, backup number backup User response: None.
file copies, and spacemg number space-managed files
from either the server database to export media or from
import media into the server database. Data is not ANR0632I Export/import command: Copied number
actually moved if Preview=Yes is specified in the gigabytes of data.
command export/import command. Explanation: The background export or import
System action: Export or import processing for the process to service the command export/import command
command completes. Server operation continues. copies number gigabytes of data from the server
database and data storage to the export media or from
User response: None. the export media to the server database and data
bytes of data.
the server.
copies number bytes of data from the server database
and data storage to the export media or from the User response: None.
export media to the server database and data storage.
Data is not moved if Preview=Yes is specified in the
command export/import command. This figure can be ANR0633I Export/import command: Copied number
used during export preview processing to estimate the terabytes of data.
number of removable media volumes needed to hold Explanation: The background export or import
the exported information from the server. process to service the command export/import command
System action: Export or import processing for the copies number terabytes of data from the server
command completes. Server operation continues. database and data storage to the export media or from
User response: None. storage. This figure can be used during export preview
the server.
kilobytes of data.
copies number kilobytes of data from the server User response: None.
storage. This figure can be used during export preview ANR0634I Export/import command: Detected number
processing to estimate the number of removable media errors.
volumes needed to hold the exported information from Explanation: The background export or import
the server. process to service the command export/import command
System action: Export or import processing for the detects number errors while copying information from
command completes. Server operation continues. the server database and data storage to the export
media or from the export media to the server database
User response: None. and data storage.
ANR0631I Export/import command: Copied number command completes. Server operation continues.
megabytes of data.
User response: Examine the server messages issued
Explanation: The background export or import prior to this message to view the error. Use the QUERY
process to service the command export/import command ACTLOG command to view the activity log and search
copies number megabytes of data from the server for messages.


ANR0635I Export/import command: Processing node
command continues.
node name in domain domain name.
is currently processing the client node definition ANR0639I Export/import command: Processing
information for node node name. The node will be domain domain name.
imported to domain domain name.
System action: Export or import processing for the process to service the command export/import command
command continues. is currently processing the policy domain definition
information for domain domain name.
command continues.
ANR0636I Import command: Processing file space
filespace name for node node name as file User response: None.
space new filespace name.
Explanation: The background import process to ANR0640I Export/import command: Processing policy
service the command import command is currently set set name in policy domain domain
processing the client file space definition information name.
for file space filespace name belonging to client node
node name. The file space is imported under the name Explanation: The background export or import
new filespace name. During import processing, file spaces process to service the command export/import command
defined for clients are not replaced, and file copy is currently processing the policy set definition
information in the file spaces are imported to new file information for policy set set name belonging to policy
space names so that client file copies are not mixed domain domain name.
with existing definitions. Import processing can then System action: Export or import processing for the
create file spaces with names generated by the import command continues.
processor for client nodes that existed prior to the
import operation. User response: None.
System action: Import processing for the command

continues. ANR0641I Export/import command: Processing
management class class name in domain
User response: None; however, clients may want to domain name, set set name.
examine the contents of the file space with the name
new filespace name so that they know where certain file Explanation: The background export or import
copies are kept. process to service the command export/import command
is currently processing the management class definition
information for management class class name belonging
ANR0637I Export/import command: Processing file to policy set set name in policy domain domain name.
space filespace name for node node name
fsId filespace id. System action: Export or import processing for the
command continues.
process to service the command export/import command User response: None.
is currently processing client node file space
information for file space filespace name belonging to ANR0642I Export/import command: Processing
client node node name. backup copy group in domain domain
System action: Export or import processing for the name, set set name, management class
command continues. class name.

is currently processing the backup copy group
ANR0638I Export/import command: Processing definition information for management class class name
administrator administrator name. belonging to policy set set name in policy domain
Explanation: The background export or import domain name.
process to service the command export/import command System action: Export or import processing for the
is currently processing the administrator definition command continues.
information for administrator administrator name.

command continues, but errors may have been

encountered.
archive copy group in domain domain
name, set set name, management class User response: Examine the documentation for the
class name. message message and resolve the problem reported.
Explanation: The background export process to
service the command export/import command is currently ANR0647I Cancel in progress
processing the archive copy group definition
information for management class class name belonging Explanation: The export or import operation has been
to policy set set name in policy domain domain name. canceled and will end when resources have been freed
for the background process. This message may be
System action: Export processing for the command displayed in response to a QUERY PROCESS command
continues. for an export or import operation.
User response: None. System action: Server operation continues.
ANR0644I Export command: Processing copy group
of unknown type in domain domain
name, set set name, management class ANR0648I Have copied the following:
class name. Explanation: The export or import operation has
Explanation: The background export or import copied the number and types of objects displayed. This
process to service the command export command is message may be displayed in response to a QUERY
currently processing copy group definition information PROCESS command for an export or import operation.
for management class class name belonging to policy set System action: Server operation continues.
set name in policy domain domain name. The type of
copy group being processed is unknown. User response: None.

command continues. The import or export process ANR0649I Import command: Domain domain name
assumes that the copy group is a backup copy group. does not exist - the system will attempt
to import node node name to domain
User response: After policy definitions are imported, STANDARD.
use the QUERY MGMTCLASS and QUERY
COPYGROUP commands to query the server Explanation: The background import process to
definitions for management class class name to ensure service the command import command is currently
that the copy groups defined have the desired processing client node node name. This node was
attributes and types. Alternatively, the copy group can assigned to domain domain name at the time of export.
be deleted and defined with the correct type, and then However, domain domain name does not exist on the
the export command can be issued again. server to which the import is being performed.
System action: Import processing continues, but node
ANR0645I Export/import command: Processing node name will be assigned to domain STANDARD
schedule schedule name in domain domain during import unless one of the following conditions
name. exist:
v Preview=Yes
process to service the command export/import command v Node node name is already registered and
is currently processing the schedule definition Replacedefs=No
information for schedule schedule name belonging to v Domain STANDARD does not exist
policy domain domain name.
User response: If Preview=Yes, consider defining
System action: Export or import processing for the domain domain name before nodes are actually
command continues. imported. Otherwise, domain domain name can be
created after the node is imported and the UPDATE
NODE command can be used to assign the node to
domain domain name.
ANR0646I Export/import command: message
Explanation: The background export or import ANR0650W IMPORT: Archive copygroup copy group
process to service the command export/import command name in management class management
has received the message message from the server. class name for domain domain name is not
defined, default management class will
System action: Export or import processing for the be used.

Explanation: During import processing, the server

ANR0653W IMPORT: Backup copygroup not found
finds that a management class or copy group bound to
for default management class in domain
an archive file being imported does not exist in the
domain name - backup files bound to
active policy set for the domain to which the node is
management class management class name
assigned.
in this domain cannot be imported.
node's policy domain is bound to the archive file and
import processing continues.
a backup file being imported does not exist in the
User response: If you want to define the missing active policy set for the domain to which the node is
management class, an authorized administrator may assigned. When trying to rebind the backup file to the
cancel the import operation, define the missing default management class for the domain, the server
management class or copy group for the domain, and finds that a backup copy group is not defined for the
process the import operation again. default management class.
System action: The file is not imported; import
ANR0651W IMPORT: Backup copygroup copy group processing continues.
name in management class management
User response: If you want to define the missing copy
class name for domain domain name is not
group, an authorized administrator may cancel the
defined, default management class will
import operation, define the missing management class
be used.
or copy group for the domain, and process the import
Explanation: During import processing, the server operation again.
a backup file being imported does not exist in the
ANR0654I Restartable export command with export
active policy set for the domain to which the node is
identifier exportID started as process
assigned.
process ID.
Explanation: A background process was started to
node's policy domain is bound to the backup file copy
service the command command. The background
and import processing continues.
process is defined as process process ID.
User response: If you want to define the missing
management class, an authorized administrator may
cancel the import operation, define the missing User response: To query the progress of the
management class or copy group for the domain, and background server-to-server export process, issue the
process the import operation again. QUERY PROCESS or QUERY EXPORT command. To
suspend the process, issue the SUSPEND EXPORT
command. To cancel the background process, issue the
ANR0652W IMPORT: Archive copygroup not found
for default management class in domain
number to specify this specific process.
domain name - archive files bound to
in this domain cannot be imported. ANR0655W Command: Retrieve or restore failed - file
was deleted from data storage during
retrieval.
an archive file being imported does not exist in the Explanation: The server ends a file retrieval operation
active policy set for the domain to which the node is for the specified command because the file has been
assigned. When trying to rebind the archive file to the deleted from data storage by another process before
default management class for the domain, the server retrieval is complete.
finds that an archive copy group is not defined for the
System action: The server ends the command and
default management class.
System action: The file is not imported; import
User response: Contact your administrator to find out
processing continues.
if DELETE FILESPACE, DELETE VOLUME, or
User response: If you want to define the missing copy inventory expiration processes are running; these
group, an authorized administrator may cancel the processes can delete data storage files during retrieval.
import operation, define the missing management class Reissue the command after these processes have been
or copy group for the domain, and process the import completed or canceled.
operation again.

ANR0656W Export/import command: Skipped archive ANR0659W Export command: The password for node
number archive files, backup number node name could not be obtained. The
backup files, and spacemg number space value 'password value' will be assumed:
managed files. The system administrator may wish to
change this password after importing
node node name.
skipped archive number archive file copies, backup Explanation: During processing of command export
number backup file copies, and spacemg number command, the export processor cannot obtain the
space-managed files from either the server database to password for client node node name. The value password
export media or from import media into the server value is assigned as the password for the client node on
database. Data is not actually moved if Preview=Yes is the export media.
specified in the command export/import command.
User response: After the client node definition has
been imported to another server, an authorized
User response: Check previous messages for the administrator should use the UPDATE NODE
names of the files that were not exported or imported, command to set a password for the node node name.
and problem determination information.
ANR0660E Command: Insufficient memory available
ANR0657W Export command: Invalid authorization in accessing data storage.
rule type rule type encountered for file
Explanation: The server encounters a memory
space filespace name fsId filespace id in
shortage in accessing data storage during command
node node name - both backup and
command operation.
archive will be assumed during import.
System action: The command command operation ends
encounters an invalid file space authorization rule type
for the indicated file space and node. User response: See the documentation for the
application.
User response: After import processing is completed,
ask the user of node node name to query the access rules
ANR0661E Command: Internal error encountered in
and ensure that they are specified as desired. The user
accessing data storage.
should correct any rules that grant access to objects that
the user does not want others to access. Explanation: The server encounters an internal error
in accessing data storage while processing command
command operation.
ANR0658W Export command: The password for
administrator administrator name could System action: The command command operation is
not be obtained. The value 'password ended and server operation continues.
value' will be assumed: The system
administrator may wish to change this User response: Use the QUERY ACTLOG command to
password after importing administrator examine messages prior to this error to determine the
administrator name. cause of the data storage failure. If the failure can be
found and resolved, reissue the command command
Explanation: During processing of command export operation. If the failure cannot be found, contact your
command, the export processor cannot obtain the service representative for assistance in resolving the
password for administrator administrator name. The problem.
value password value is assigned as the password for the
administrator on the export media.
ANR0662E Command: Output error encountered in
System action: Processing of the command continues. accessing data storage.
User response: After the administrative definition has Explanation: The command command operation ends
been imported to another server, an authorized because an error has been encountered by the server in
administrator should use the UPDATE ADMIN writing to a device. Possible reasons include:
command to set a password for the administrator v I/O error writing to a device
administrator name.
v No storage space.
v Incompatible storage pool data format.
System action: The command command operation ends


ANR0666W Import command: Transaction failed -
User response: Query the activity log to find messages object excluded by size in storage pool
preceding this one to determine the cause of the error. pool name and all successor pools.
After the problem is corrected, the command can be
retried.
transaction for an import operation because the size of
an imported file is larger than that allowed in the
ANR0663E Command: Data transfer was interrupted storage pool specified in the bound management class
in accessing data storage. copy group for the file. No successor storage pools to
the one specified on the copy group can accept the
Explanation: The database transaction associated with large file.
command command operation failed because data
transfer to or from data storage was interrupted by an System action: The import operation is ended and
external event. server operation continues.
System action: The command command operation is User response: The maximum file size for one or more
ended and server operation continues. of the storage pools in the storage hierarchy can be
increased to accommodate the file. An authorized
User response: Examine the messages issued prior to administrator can increase the MAXSIZE parameter by
this message to determine why the data transfer was issuing the UPDATE STGPOOL command.
interrupted. Reissue the command command after the Alternatively, the appropriate copygroup definition can
problem is resolved. be updated so that a different destination storage pool
is specified.
ANR0664E Export/import command: Media not
accessible in accessing data storage. ANR0667W Import command: Transaction failed - no
Explanation: The server ends a transaction for an space available in storage pool pool name
export or import operation because storage volumes are and all successor pools.
not available in the storage pools in which the client Explanation: The server ends an import operation
files are to be stored. because the storage pool specified in a management
System action: The server ends the export or import class copy group does not contain enough free space to
operation and server operation continues. hold the files being imported. Successor storage pools
to the one specified on the copy group do not contain
User response: An authorized administrator can issue enough free space.
the DEFINE VOLUME command to add storage to one
or more storage pools in the storage hierarchy. The System action: The import operation is ended and
VARY ONLINE command can be used to vary offline server operation continues.
storage volumes online in the storage hierarchy to User response: An authorized administrator can issue
make them available for file storage. the DEFINE VOLUME command to add storage to one
or more storage pools in the storage hierarchy.
ANR0665W Import command: Transaction failed -
storage pool pool name is not defined. ANR0668W Export/import command: Transaction failed
Explanation: The server rolls back a database update - error on output storage device.
transaction for an import operation because the Explanation: The server ends an export or import
destination specified for a management class copy operation for the specified session because an I/O error
group specifies the named storage pool, but that has been encountered by the server in writing to a
storage pool does not exist. device.
System action: The import operation is ended and System action: The server ends the export or import
server operation continues. operation and server operation continues.
User response: An administrator with policy authority User response: Query the activity log to find messages
over the client policy domain must correct management preceding this one that specify the device that is failing.
class definitions so that copy group destinations refer Storage pool volumes can be varied offline (by using
to defined storage pools, or the specified storage pool the VARY OFFLINE command), or the server may need
must be created by an authorized administrator. to be shut down by using the HALT command to
correct the hardware problem. After the problem is
corrected, the client may be able to try the operation
again.

ANR0669W Export/import command: Transaction failed ANR0672W Export/import command: Transaction failed
- data transfer interrupted. - sufficient database space is not
available.
Explanation: The database transaction associated with
an export or import operation failed because data Explanation: The server ends a database update
transfer to or from data storage was interrupted by an transaction for an export or import operation because
external event. sufficient database space is not available on the server.
System action: The export or import operation is System action: The server ends the export or import
ended and server operation continues. operation and server operation continues.
User response: Examine the messages issued prior to User response: To increase the amount of database
this message to determine why the data transfer was space that is available to the server, issue the EXTEND
interrupted. Attempt the export/import operation again DBSPACE command to add one or more directories to
after problem is resolved. the database.
ANR0670W Export/import command: Transaction failed ANR0673W Export/import command: Data storage
- storage media inaccessible. retrieve or restore failed - error detected.
Explanation: The server ends a transaction for an Explanation: The server ends an export or import
export or import operation because storage volumes are operation because an error has been encountered on the
not available in the storage pools in which the client server. Some common reasons for the error are:
files are to be stored. v The input volume is unavailable
System action: The server ends the export or import v The storage pool is unavailable
operation and server operation continues. v Data is corrupted on the input volume
User response: An authorized administrator can issue v Hardware or media failure has occurred
the DEFINE VOLUME command to add storage to one v Database corruption
or more storage pools in the storage hierarchy. The
VARY ONLINE command can be used to vary offline System action: The server ends the export or import
storage volumes online in the storage hierarchy to operation and continues operation.
make them available for file storage. User response: Examine any prior error messages to
determine the source of the error. Use the QUERY
ANR0671W Export/import command: Transaction failed ACTLOG command to view the activity log and search
- sufficient recovery log space is not for messages if needed. Correct the problem and try the
available. restore or retrieve again.

transaction for an export or import operation because ANR0674W Export command: Retrieve failed - error
sufficient log space is not available on the server. on input storage device.
System action: The server ends the export or import Explanation: The server ends an export operation for
operation and server operation continues. the specified session because an I/O error has been
encountered by the server in reading from a device.
User response: To increase the amount of log space The object for which the I/O was issued is reported in
that is available to the server, evaluate the directories a later message.
and file systems that are assigned to the
ACTIVELOGDIRECTORY, ARCHIVELOGDIRECTORY, System action: Export processing skips this file, and
and ARCHFAILOVERLOGDIRECTORY options in the continues operation.
dsmserv.opt file. An out of log space condition might User response: Query the activity log to find messages
occur because the ACTIVELOGDIRECTORY location is preceding this one that specify the device that is failing.
full. Storage pool volumes can be varied offline (by using
Alternatively, an out of log space condition might occur the VARY OFFLINE command), or the server may need
if there are log files in the ACTIVELOGDIRECTORY to be shut down with the HALT command to correct
location that are no longer active and cannot be the hardware problem.
archived to the ARCHIVELOGDIRECTORY and
ARCHFAILOVERLOGDIRECTORY locations. If ANR0675E EXPORT/IMPORT: Error starting the
necessary, specify a larger directory for the Export/Import Session.
ARCHIVELOGDIRECTORY or
ARCHFAILOVERLOGDIRECTORY options in the Explanation: The server export/import process is not
dsmserv.opt file and then restart the server. able to start the session to export information from the
server or import information into the server.

System action: The export or import process ends and User response: Contact your service representative.
User response: See the documentation for the ANR0684E EXPORT/IMPORT: Communications
operating system about how to increase memory for an failure: bad verb received (verb type).
application.
Explanation: The server encounters an invalid
communications verb during export or import
ANR0678E EXPORT/IMPORT: Communications processing and is not able to continue processing.
Failure in Sending "verb type" verb.
System action: The export or import process ends and
Explanation: The server export/import process server operation continues.
encounters a communications error in using the verb
type verb to transfer information to or from the server.
ANR0685E EXPORT/IMPORT: Internal error:
Invalid table output handle detected.
Explanation: The server export/import process
encounters an internal error in transferring information
ANR0679E EXPORT/IMPORT: Communications to or from the server.
Failure in Receiving "verb type" verb.
Explanation: The server export/import process server operation continues.
type verb to transfer information to or from the server.
ANR0686E Export/import command: Transaction
failure - could not start database
User response: Contact your service representative. transaction.
Explanation: During processing of command
ANR0681E EXPORT/IMPORT: Authentication export/import command, a database transaction cannot be
Failure. started in the server database.
Explanation: The server export/import process System action: Processing of the command terminates.
encounters an authentication error in transferring
information to or from the server.
prior to this message to determine the source of the
System action: The export or import process ends and error. Use the QUERY ACTLOG command to view the
server operation continues. activity log and search for messages. If the error cannot
representative.
ANR0682E EXPORT/IMPORT: Communications

Failure in Sending "verb type" verb
failure - could not commit database
(command).
transaction.
export/import command, a database transaction cannot be
type verb to issue command command.
committed to the server database.
System action: Processing of the command ends.
error. Use the QUERY ACTLOG command to view the
ANR0683E EXPORT/IMPORT: Receive Buffer activity log and search for messages. If the error cannot
overflow. be isolated and resolved, contact your service
representative.
encounters an overflow error in transferring
information to or from the server.


failure - commit called when no
transaction started.
Explanation: During processing of command representative.
started in the server database.
ANR0695E Export command: Unexpected error error
System action: Processing of the command ends. code encountered in receiving table
output data.
prior to this message to determine the source of the Explanation: During processing of command export
error. Use the QUERY ACTLOG command to view the command, an unexpected error is detected.
representative. User response: Examine the server messages issued
failure - server aborted the transaction
(abort code).
representative.
ANR0696E Export command: Output table error
committed in the server database. The reason code abort
encountered - 0 columns reported in the
code is returned.
table.
User response: Examine the server messages issued command, an unexpected error is detected.
activity log and search for messages. If the error cannot User response: Examine the server messages issued
be isolated and resolved, contact your service prior to this message to determine the source of the
representative. error. Use the QUERY ACTLOG command to view the
ANR0692E Command: Out of space on sequential
representative.
media, scratch media could not be
mounted.
ANR0697E Export command: Output table error
Explanation: During command command processing,
encountered - not positioned to the first
the process encounters an out-of-space condition
column in the table.
writing to the sequential media. Command command
ends when there is no more space on the sequential Explanation: During processing of command export
media for storing data and SCRATCH=NO has been command, an unexpected error is detected.
specified on command command.
System action: Command command processing ends.
Server processing continues. User response: Examine the server messages issued
User response: Reissue the command and specify error. Use the QUERY ACTLOG command to view the
SCRATCH=YES or specify additional volume names on activity log and search for messages. If the error cannot
the command. be isolated and resolved, contact your service
representative.
ANR0694E Import command: Invalid record format
(format code) detected on import. ANR0698E Export/import command: Invalid value for
FILEDATA parameter - parameter value.
command, an invalid record type is detected when Explanation: The value (parameter value) specified for
reading the exported information from the export the FILEDATA parameter in command export/import
media. command is not a valid value for this parameter.
System action: Processing of the command ends. System action: The command fails and server

User response: Reissue the command and specify a

ANR0706E Export command: A device class must be
valid FILEDATA parameter.
specified unless PREVIEW=YES is
specified.
ANR0699E Export/import command: Device class
Explanation: The DEVCLASS parameter is not
DISK cannot be specified for this
specified in the command export command. Unless
command.
PREVIEW=YES is specified, a DEVCLASS value must
Explanation: The DEVCLASS value DISK cannot be be specified.
specified for the command export/import command.
System action: The command fails and server operation continues.
User response: Reissue the command and specify a valid device class. Issue the QUERY DEVCLASS
valid device class. Issue the QUERY DEVCLASS command for a list of valid device classes for the
command for a list of valid device classes for the server.
server.
ANR0707E Export command: The FILESPACE
ANR0700E Export/import command: Invalid value for parameter cannot be specified.
PREVIEW parameter - parameter value.
Explanation: The FILESPACE parameter is specified
Explanation: The value (parameter value) specified for for the command export command, but the FILEDATA
the PREVIEW parameter in command export/import parameter is specified as NONE, or is not specified and
command is not a valid value for this parameter. defaults to NONE. File spaces are only copied if the
FILEDATA parameter is specified with a value other
System action: The command fails and server than NONE.
User response: Reissue the command and specify a operation continues.
valid PREVIEW parameter.
valid FILEDATA parameter.
ANR0701E Export/import command: Invalid value for
SCRATCH parameter - parameter value.
ANR0708E Import command: The FILESPACE
Explanation: The value (parameter value) specified for parameter cannot be specified unless the
the SCRATCH parameter in command export/import FILEDATA parameter specifies that files
command is not a valid value for this parameter. should be imported.
System action: The command fails and server Explanation: The FILESPACE parameter is specified
operation continues. for the command import command, but the FILEDATA
User response: Reissue the command and specify a parameter is specified as NONE, or is not specified and
valid SCRATCH parameter. defaults to NONE. File spaces are only copied if the
FILEDATA parameter is specified with a value other
than NONE.
ANR0705E Export command: The VOLUMENAMES
parameter must be specified when System action: The command fails and server
SCRATCH=NO is specified. operation continues.
Explanation: The SCRATCH parameter is specified as User response: Reissue the command and specify a
NO for the command export command but the valid FILEDATA parameter.
VOLUMENAMES parameter is not specified. When
scratch volumes are not allowed, the VOLUMENAMES ANR0709E Command: No matching nodes registered
parameter must be specified to indicate the volumes in the specified domains.
that can be used for the command.
Explanation: The DOMAIN parameter has been
System action: The command fails and server specified for this command, but no nodes matching the
operation continues. node name specification are found in the domains
User response: Reissue the command and specify a specified.
valid VOLUMENAMES parameter. System action: The command fails and server
valid combination of node and domain names. Use the

QUERY NODE command to view the names of nodes

ANR0716E Import command: Invalid export data
in the domains that you are interested in exporting.
detected.
Explanation: The command import command
ANR0710E Command: Unable to start background
encounters invalid data on the export media while
process.
trying to import server information.
Explanation: The server command processor is not
able to start a background process to perform the
command command.
User response: Ensure that the mounted export tapes
System action: The command process ends and server
are in the correct order (mounted in the same order as
they were mounted during export). Reissue the
User response: See the documentation for the command, and mount the tapes in the correct order. If
operating system about how to increase memory for an the VOLUMENAMES parameter has been specified,
application. make sure that the volume names in the command are
specified in the correct order.
DATES parameter - parameter value. ANR0717E Export/import command: Preview
processing terminated abnormally -
Explanation: The value (parameter value) specified for communications send or receive failed.
the DATES parameter in command import command is
not a valid value for this parameter. Explanation: Processing for the command export/import
command in preview mode has been terminated when
System action: The command fails and server an internal communications error is encountered in the
operation continues. server.
User response: Reissue the command and specify a System action: Export/import processing is ended
valid DATES parameter. and server operation continues.
ANR0713E Import command: Invalid value for prior to this message to determine the source of the
REPLACEDEFS parameter - parameter error. Use the QUERY ACTLOG command to view the
value. activity log and search for messages. If the error cannot
Explanation: The value (parameter value) specified for be isolated and resolved, contact your service
the REPLACEDEFS parameter in command import representative.
command is not a valid value for this parameter.
System action: The command fails and server ANR0718E Export/import command: Processing
operation continues. terminated abnormally -
communications send or receive failed.
valid REPLACEDEFS parameter. Explanation: Processing for the command export/import
command ends when an internal communications error
is encountered in the server.
ANR0715E Import command: A device class must be
specified. System action: Export/import processing is ended
Explanation: The command import command has been
specified, but does not include specification of the User response: Examine the server messages issued
DEVCLASS parameter. The DEVCLASS parameter prior to this message to determine the source of the
must be specified for this command. error. Use the QUERY ACTLOG command to view the
System action: The command fails and server be isolated and resolved, contact your service
operation continues. representative.
valid device class. For a list of valid device classes for ANR0719E Export/import command: Preview
the server, issue the QUERY DEVCLASS command. processing terminated abnormally -
insufficient memory.
Explanation: Processing for the command export/import
command in preview mode is ended because sufficient
System action: Export/import processing is ended

and server operation continues. System action: Export/import processing ends and
operating system about how to increase memory for an User response: Examine the server messages issued
application. prior to this message to determine the source of the
ANR0720E command: Processing terminated
abnormally - insufficient memory.
representative.
Explanation: Processing for the command ends
because sufficient memory is not available on the
ANR0724E Export/import command: Processing
server.
terminated abnormally - transaction
System action: Command processing is ended and failure.
User response: See the documentation for the command ends when a database transaction error is
operating system about how to increase memory for an encountered in the server.
application.
System action: Export/import processing ends and
ANR0721E Export/import command: Preview
User response: Examine the source and target server
messages issued prior to this message to determine the
unexpected verb received from server.
source of the error. Use the QUERY ACTLOG
Explanation: Processing for the command export/import command to view the activity log and search for
command in preview mode ends when an internal messages. If the error cannot be isolated and resolved,
communications error is encountered in the server. contact your service representative.
server operation continues. ANR0725E Export/import command: Preview
User response: Examine the server messages issued authentication failure.
error. Use the QUERY ACTLOG command to view the Explanation: Processing for the command export/import
activity log and search for messages. If the error cannot command in preview mode ends when an authentication
be isolated and resolved, contact your service error is encountered in the server.
representative.
terminated abnormally - unexpected
verb received from server.
Explanation: Processing for the command export/import activity log and search for messages. If the error cannot
command ends when an internal communications error be isolated and resolved, contact your service
is encountered in the server. representative.

server operation continues. ANR0726E Export/import command: Processing
terminated abnormally - authentication
User response: Examine the server messages issued failure.
error. Use the QUERY ACTLOG command to view the Explanation: Processing for the command export/import
activity log and search for messages. If the error cannot command ends when an authentication error is
be isolated and resolved, contact your service encountered in the server.
representative.
transaction failure.
Explanation: Processing for the command export/import activity log and search for messages. If the error cannot
command in preview mode ends when a database be isolated and resolved, contact your service
transaction error is encountered in the server. representative.


internal error.
Explanation: Processing for the command export/import representative.
command in preview mode ends when an internal error
is encountered in the server.
System action: Export/import processing ends and COMPRESSION parameter in exported
server operation continues. data for node node name.
User response: Examine the server messages issued Explanation: During preview processing of command
prior to this message to determine the source of the import command, an invalid value is encountered for the
error. Use the QUERY ACTLOG command to view the COMPRESSION parameter for node node name.
representative.
default or existing COMPRESSION value is used.
later command, verify that the correct COMPRESSION
terminated abnormally - internal error.
value is used for this node.
command ends when an internal error is encountered in
the server.
ARCHDELETE parameter in exported
System action: Export/import processing ends and data for node node name.
User response: Examine the server messages issued import command, an invalid value is encountered for the
prior to this message to determine the source of the ARCHDELETE parameter for node node name.
default or existing ARCHDELETE value is used.
representative.
later command, verify that the correct ARCHDELETE
ANR0729E Import command: Syntax error from
command 'server command'.
Explanation: During processing of the command
import command, an internal syntax error is encountered
BACKDELETE parameter in exported
in the server.
data for node node name.
System action: Import processing continues, but the
indicated command will have no effect.
User response: Examine the server messages issued BACKDELETE parameter for node node name.
activity log and search for messages. After import
default or existing BACKDELETE value is used.
processing is complete, it may be necessary to issue
additional commands manually to obtain the necessary User response: None. If the data is imported with a
definitions. later command, verify that the correct BACKDELETE
ANR0730E Import command: Internal error from
command 'server command'. ANR0734E Import command: Invalid value for
COMPRESSION parameter in exported
Explanation: Processing for the command import
data - node node name registered with
command ends when an internal command error is
default COMPRESSION value.
encountered in the server.
System action: Import processing ends and server
COMPRESSION parameter for node node name.

by using the default COMPRESSION value for this System action: Processing of the command continues,
node. by using the existing ARCHDELETE value for this
node.
User response: Verify that the correct COMPRESSION
value has been used for this node. Update this value, if User response: Verify that the correct ARCHDELETE
necessary. value has been used for this node. Update this value, if
necessary.
ARCHDELETE parameter in exported ANR0739E Import command: Invalid value for
data - node node name registered with BACKDELETE parameter in exported
default ARCHDELETE value. data - existing BACKDELETE value for
node node name was not updated.
command, an invalid value is encountered for the Explanation: During processing of command import
ARCHDELETE parameter for node node name. command, an invalid value is encountered for the
BACKDELETE parameter for node node name.
by using the default ARCHDELETE value for this node. System action: Processing of the command continues,
by using the existing BACKDELETE value for this
User response: Verify that the correct ARCHDELETE
node.
value has been used for this node. Update this value, if
necessary. User response: Verify that the correct BACKDELETE
value has been used for this node. Update this value, if
necessary.
BACKDELETE parameter in exported
data - node node name registered with ANR0740E Import command: Invalid value for TYPE
default BACKDELETE value. parameter in exported data for copy
group copy group name in domain domain
name, set policy set name, management
class management class name - backup is
assumed.
by using the default BACKDELETE value for this node.
command, an invalid value is encountered for the TYPE
User response: Verify that the correct BACKDELETE parameter for copy group copy group, in policy domain
value has been used for this node. Update this value, if domain name, policy set policy set name, management
necessary. class management class name.
ANR0737E Import command: Invalid value for Based upon other copy group parameters, a copy group
COMPRESSION parameter in exported type of backup is assigned.
data - existing COMPRESSION value
User response: Verify that the assigned TYPE value of
for node node name was not updated.
backup for this copy group is correct.
ANR0741E Import command: Invalid value for TYPE
COMPRESSION parameter for node node name.
parameter in exported data for copy
System action: Processing of the command continues, group copy group name in domain domain
by using the existing COMPRESSION value for this name, set policy set name, management
node. class management class name - archive is
assumed.
User response: Verify that the correct COMPRESSION
value has been used for this node. Update this value, if Explanation: During processing of command import
necessary. command, an invalid value is encountered for the TYPE
parameter for copy group copy group, in policy domain
domain name, policy set policy set name, management
ANR0738E Import command: Invalid value for class management class name.
ARCHDELETE parameter in exported
data - existing ARCHDELETE value for System action: Processing of the command continues.
node node name was not updated. Based upon other copy group parameters, a copy group
type of archive is assigned.
command, an invalid value is encountered for the User response: Verify that the assigned TYPE value of
ARCHDELETE parameter for node node name. archive for this copy group is correct.

ANR0742E Import command: Invalid value for TYPE ANR0745E Import command: Invalid value for
parameter in exported data for copy SERIALIZATION parameter in exported
group copy group name in domain domain data for archive copy group copy group
name, set policy set name, management name in domain domain name, set policy
class management class name - this copy set name, management class management
group will not be imported. class name.
Explanation: During processing of command import Explanation: During preview processing of command
command, an invalid value is encountered for the TYPE import command, an invalid value is encountered for the
parameter for copy group copy group, in policy domain SERIALIZATION parameter for archive copy group
domain name, policy set policy set name, management copy group name, in policy domain domain name, policy
class management class name. set policy set name, management class management class
name.
However, this copy group is not imported because a System action: Processing of the command continues.
TYPE value cannot be assigned. If a later command causes the data to be imported, the
default or existing SERIALIZATION value is used.
User response: Manually define this copy group, if
necessary. User response: None. If the data is imported with a
later command, verify that the correct SERIALIZATION
value is used for this archive copy group.
MODE parameter in exported data for
archive copy group copy group name in ANR0746E Import command: Invalid value for
domain domain name, set policy set name, SERIALIZATION parameter in exported
management class management class name. data for backup copy group copy group
name in domain domain name, set policy
set name, management class management
class name.
MODE parameter for archive copy group copy group
name, in policy domain domain name, policy set policy set Explanation: During preview processing of command
name, management class management class name. import command, an invalid value is encountered for the
SERIALIZATION parameter for backup copy group
copy group name, in policy domain domain name, policy
set policy set name, management class management class
default or existing MODE value is used.
name.
later command, verify that the correct MODE value is
used for this archive copy group.
default or existing SERIALIZATION value is used.
later command, verify that the correct SERIALIZATION
MODE parameter in exported data for
value is used for this backup copy group.
backup copy group copy group name in
domain domain name, set policy set name,
management class management class name. ANR0747E Import command: Invalid value for
MODE parameter in exported data -
archive copy group copy group name in
MODE parameter for backup copy group copy group
name, in policy domain domain name, policy set policy set
defined with default MODE value.
name, management class management class name.
default or existing MODE value is used.
User response: None. If the data is imported with a name, management class management class name.
later command, verify that the correct MODE value is
used for this backup copy group.
by using the default MODE value for this archive copy
group.
User response: Verify that the correct MODE value
has been used for this copy group. Update this value, if
necessary.

SERIALIZATION value has been used for this copy

group. Update this value, if necessary.
MODE parameter in exported data -
backup copy group copy group name in
domain domain name, set policy set name, ANR0751E Import command: Invalid value for
management class management class name MODE parameter in exported data -
defined with default MODE value. existing MODE value for archive copy
class management class name was not
updated.
name, management class management class name. Explanation: During processing of command import
by using the default MODE value for this backup copy
group.
by using the existing MODE value for this archive copy
necessary.
group.
SERIALIZATION parameter in exported
necessary.
data - archive copy group copy group
set name, management class management ANR0752E Import command: Invalid value for
class name defined with default MODE parameter in exported data -
SERIALIZATION value. existing MODE value for backup copy
class management class name was not
SERIALIZATION parameter for archive copy group
updated.
set policy set name, management class management class Explanation: During processing of command import
name. command, an invalid value is encountered for the
by using the default SERIALIZATION value for this
archive copy group.
by using the existing MODE value for this backup copy
group.
necessary.
data - backup copy group copy group
name in domain domain name, set policy ANR0753E Import command: Invalid value for
set name, management class management SERIALIZATION parameter in exported
class name defined with default data - existing SERIALIZATION value
SERIALIZATION value. for archive copy group copy group name
in domain domain name, set policy set
name, management class management class
name was not updated.
copy group name, in policy domain domain name, policy Explanation: During processing of command import
set policy set name, management class management class command, an invalid value is encountered for the
name. SERIALIZATION parameter for archive copy group
by using the default SERIALIZATION value for this
name.
backup copy group.

by using the existing SERIALIZATION value for this command, verify that the correct values for
archive copy group. DURATION, DURUNITS, PERIOD, and PERUNITS are
group. Update this value, if necessary. ANR0757E Import command: Invalid value for
data for schedule schedule name in
domain domain name.
data - existing SERIALIZATION value Explanation: During preview processing of command
for backup copy group copy group name import command, an invalid value is encountered for the
in domain domain name, set policy set DAYOFWEEK parameter for schedule schedule name in
name, management class management class policy domain domain name.
Explanation: During processing of command import If a later command causes the data to be imported, the
command, an invalid value is encountered for the default or existing DAYOFWEEK value is used.
command, verify that the correct DAYOFWEEK value is
name.
by using the existing SERIALIZATION value for this
ACTION parameter in exported data -
backup copy group.
schedule schedule name in domain domain
User response: Verify that the correct name defined with default ACTION
SERIALIZATION value has been used for this copy value.
ANR0755E Import command: Invalid value for ACTION parameter for schedule schedule name in policy
ACTION parameter in exported data for domain domain name.
name.
by using the default ACTION value for this schedule.
User response: Verify that the correct ACTION value
has been used for this schedule. Update this value, if
ACTION parameter for schedule schedule name in policy
necessary.
domain domain name.
default or existing ACTION value is used.
exported data - schedule schedule name in
User response: If the data is imported with a later domain domain name defined with
command, verify that the correct ACTION value is default values for DURATION,
used for this schedule. DURUNITS, PERIOD, and PERUNITS.
ANR0756E Import command: Invalid value for command, an invalid value is encountered for the
DURUNITS or PERUNITS parameter in DURUNITS or PERUNITS parameter for schedule
exported data for schedule schedule name schedule name in policy domain domain name.
in domain domain name.
Explanation: During preview processing of command by using the default values for DURATION,
import command, an invalid value is encountered for the DURUNITS, PERIOD, and PERUNITS.
DURUNITS or PERUNITS parameter for schedule
User response: Verify that the correct values have
schedule name in policy domain domain name.
been used for DURATION, DURUNITS, PERIOD, and
System action: Processing of the command continues. PERUNITS. Update these values, if necessary.
default or existing values are used for DURATION,
DURUNITS, PERIOD, and PERUNITS.


DAYOFWEEK parameter for schedule schedule name in
data - schedule schedule name in domain
domain name defined with default System action: Processing of the command continues,
DAYOFWEEK value. by using the existing DAYOFWEEK value for this
schedule.
command, an invalid value is encountered for the User response: Verify that the correct DAYOFWEEK
DAYOFWEEK parameter for schedule schedule name in value has been used for this schedule. Update this
policy domain domain name. value, if necessary.
by using the default DAYOFWEEK value for this ANR0764E Import command: Invalid lock status
schedule. detected while importing node node
name - this node will not be locked.
User response: Verify that the correct DAYOFWEEK
value has been used for this schedule. Update this Explanation: During processing of command import
value, if necessary. command, an invalid value is encountered for the lock
status for node node name.
ANR0761E Import command: Invalid value for System action: Processing of the command continues,
ACTION parameter in exported data - but the node is not locked.
existing ACTION value for schedule
schedule name in domain domain name was User response: An administrator with the proper
not updated. authorization must issue the LOCK NODE command, if
necessary.
ACTION parameter for schedule schedule name in policy ANR0765E Import command: Invalid lock status
domain domain name. detected while importing administrator
administrator name - this administrator
System action: Processing of the command continues, will not be locked.
by using the existing ACTION value for this schedule.
User response: Verify that the correct ACTION value command, an invalid value is encountered for the lock
has been used for this schedule. Update this value, if status for administrator administrator name.
necessary.
but the administrator is not locked.
DURUNITS or PERUNITS parameter in User response: An administrator with the proper
exported data - existing values for authorization must issue the LOCK ADMIN command,
DURATION, DURUNITS PERIOD, and if necessary.
PERUNITS for schedule schedule name in
domain domain name were not updated. ANR0766E Export command: Invalid value for TYPE
Explanation: During processing of command import parameter detected while exporting copy
command, an invalid value is encountered for the group copy group name in domain domain
DURUNITS or PERUNITS parameter for schedule name, set policy set name, management
schedule name in policy domain domain name. class management class name - system will
attempt to assign value during import.
by using the existing values for DURATION, Explanation: During processing of command export
DURUNITS, PERIOD, and PERUNITS. command, an invalid value is encountered for the TYPE
parameter for copy group copy group name, in domain
User response: Verify that the correct values have domain name, policy set policy set name, management
been used for DURATION, DURUNITS, PERIOD, and class management class name.
PERUNITS. Update these values, if necessary.
exported data contains an unknown TYPE value for
ANR0763E Import command: Invalid value for this copy group. If this data is imported, the system
DAYOFWEEK parameter in exported attempts to assign a TYPE value based upon values for
data - existing DAYOFWEEK value for other copy group parameters.
name was not updated. User response: Delete and define this copy group to
eliminate the invalid data, and then restart the export

command. Alternatively, use the export data with the ACTION parameter for schedule schedule name in
unknown value, and the system will attempt to assign domain domain name.
a TYPE during import processing.
exported data will contain an unknown ACTION value
ANR0767E Export command: Invalid value for for this schedule. If this data is imported, the default or
MODE parameter detected while existing ACTION value is used.
exporting copy group copy group name in
User response: Update the ACTION value for this
use the export data with the unknown value, and check
- default or existing value is used
and update the ACTION value after import processing
during import.
has been performed.
MODE parameter for copy group copy group name in
DURUNITS parameter detected while
domain domain name, policy set policy set name,
exporting schedule schedule name in
management class management class name.
domain domain name - default or existing
System action: Export processing continues, but the value is used during import.
exported data contains an unknown MODE value for
this copy group. If this data is imported, the default or
existing MODE value is used.
DURUNITS parameter for schedule schedule name in
User response: Update the MODE value for this copy domain domain name.
group and restart the export command. Alternatively,
exported data contains an unknown DURUNITS value
and update the MODE value after import processing
for this schedule. If this data is imported, the default or
has been performed.
existing DURUNITS value is used.
User response: Update the DURUNITS value for this
SERIALIZATION parameter detected
while exporting copy group copy group
and update the DURUNITS value after import
processing has been performed.
set name, management class management
class name - default or existing value is
used during import. ANR0771E Export command: Invalid value for
PERUNITS parameter detected while
SERIALIZATION parameter for copy group copy group
value is used during import.
name, in domain domain name, policy set policy set name,
management class management class name. Explanation: During processing of command export
PERUNITS parameter for schedule schedule name in
exported data contains an unknown SERIALIZATION
domain domain name.
value for this copy group. If this data is imported, the
default or existing SERIALIZATION value is used. System action: Export processing continues, but the
exported data will contain an unknown PERUNITS
User response: Update the SERIALIZATION value for
this copy group and restart the export command.
default or existing PERUNITS value is used.
value, and check and update the SERIALIZATION User response: Update the PERUNITS value for this
value after import processing has been performed. schedule and restart the export command. Alternatively,
and update the PERUNITS value after import
processing has been performed.
ACTION parameter detected while
domain domain name - default or existing ANR0772E Export command: Invalid value for
value is used during import. DAYOFWEEK parameter detected while


ANR0775E Export command: Invalid lock status
detected while exporting node node name
DAYOFWEEK parameter for schedule schedule name in
- this node will not be locked during
domain domain name.
import.
exported data contains an unknown DAYOFWEEK
command, an invalid value is encountered for the lock
status for node node name.
default or existing DAYOFWEEK value is used.
User response: Update the DAYOFWEEK value for
exported data contains an unknown lock status for this
this schedule and restart the export command.
node. If this data is imported, the node will not be
locked.
value, and check and update the DAYOFWEEK value
after import processing has been performed. User response: Lock or unlock the node to achieve the
desired lock status, and then restart the export
command. Alternatively, use the export data with the
ANR0773E Export command: Invalid lock status
unknown status, and lock or unlock the node after
detected while exporting administrator
import processing has been performed.
administrator name - this administrator
will not be locked during import.
ARCHDELETE parameter detected
command, an invalid value is encountered for the lock
while exporting node node name - default
status for administrator administrator name.
or existing value is used during import.
exported data contains an unknown lock status for this
administrator. If this data is imported, the
ARCHDELETE parameter for node node name.
administrator will not be locked.
User response: An administrator with the proper
exported data contains an unknown ARCHDELETE
authorization must issue the LOCK NODE or
value for this node. If this data is imported, the default
UNLOCK NODE command to achieve the desired lock
or existing ARCHDELETE value is used.
status, and then restart the export command.
Alternatively, use the export data with the unknown User response: Update the ARCHDELETE parameter
status, and issue a LOCK ADMIN or UNLOCK for this node and restart the export command.
ADMIN command after import processing has been Alternatively, use the export data with the unknown
performed. value, and check and update the ARCHDELETE value
COMPRESSION parameter detected ANR0777E Export command: Invalid value for
while exporting node node name - default BACKDELETE parameter detected while
or existing value is used during import. exporting node node - default or existing
command, an invalid value is encountered for the Explanation: During processing of command export
COMPRESSION parameter for node node name. command, an invalid value is encountered for the
exported data contains an unknown COMPRESSION System action: Export processing continues, but the
value for this node. If this data is imported, the default exported data contains an unknown BACKDELETE
or existing COMPRESSION value is used. value for this node. If this data is imported, the default
or existing BACKDELETE value is used.
User response: Update the COMPRESSION parameter
for this node and restart the export command. User response: Update the BACKDELETE parameter
Alternatively, use the export data with the unknown for this node and restart the export command.
value, and check and update the COMPRESSION value Alternatively, use the export data with the unknown
after import processing has been performed. value, and check and update the BACKDELETE value

export/import level (SERVER, NODE, ADMIN,

ANR0778E Command: Error encountered in accessing
POLICY).
data storage - device class device class
name is not defined. System action: The export or import process ends and
an error occurred because the specified device class is User response: Examine the server messages issued
not defined. prior to this message to determine the source of the
System action: The command command is ended and
User response: Make sure the specified device class is representative.
defined.
ANR0785E Import command: Invalid record type
ANR0779E Command: Error encountered in accessing xrecord type read from export data.
data storage - disk volume specified.
Explanation: During command command processing, encounters an internal error in reading data from the
an error occurred because a specified volume is a disk export media. An invalid record type of record type is
volume rather than a tape volume. encountered during the read operation.
System action: The command command is ended and System action: The export or import process ends and
server operation continues. server operation continues.
User response: Make sure that all volumes specified User response: Examine the server messages issued
for the command command are tape volumes. prior to this message to determine the source of the
ANR0780E Export/import command: Process aborted -
a server communications session could
representative.
not be established.
ANR0786E Import command: Invalid export version
encounters an internal error in establishing an
version number in exported data.
intermemory communications session with other server
components. Explanation: The server import process encounters an
internal error in reading data from the export media.
An invalid export version number (version number) is
encountered during the read operation.
application.
If the error is not resolved, contact your service
representative.
ANR0781E Export/import command: Process aborted - be isolated and resolved, contact your service
server sign on failed. representative.
encounters an internal error in establishing an ANR0787E Import command: Import of file space
intermemory communications session with other server filespace name in node node name aborted
components. by server (abort reason).
System action: The export or import process ends and Explanation: The server import process encounters an
server operation continues. internal error in importing file space filespace name for
client node node name. The reason code abort reason is
User response: Contact your service representative. encountered.
ANR0784E Export/import command: Process aborted - server operation continues.
internal error detected with the
Export/Import level: level number. User response: Examine the server messages issued
Explanation: The server export/import process error. Use the QUERY ACTLOG command to view the
encounters an internal error in evaluating the


representative.
error accessing data storage.
ANR0789E Import command: Failure in normalizing
in accessing data storage while executing an import or
transaction identifier for sending to the
export preview operation.
server.
System action: The export or import operation is
Explanation: The server import process encounters an
ended and server operation continues.
internal database transaction error in importing
information into the server database. User response: Use the QUERY ACTLOG command to
examine messages prior to this error to determine the
cause of the data storage failure. If you find and
resolve the error, retry the export or import operation.
User response: Examine the server messages issued If you cannot find the error, contact your service
prior to this message to determine the source of the representative for assistance in resolving the problem.
terminated abnormally - error accessing
representative.
data storage.
ANR0790E Import command: Error in absorbing data
in accessing data storage while executing an import or
records.
export operation.
Explanation: The server import process encounters an
internal error in importing information into the server
database.
User response: Use the QUERY ACTLOG command to
cause of the data storage failure. If the import or export
User response: Examine the server messages issued operation involves a session with another server, run
prior to this message to determine the source of the the QUERY ACTLOG command to examine messages
error. Use the QUERY ACTLOG command to view the on the other server as well. Messages on the other
activity log and search for messages. If the error cannot server can help you troubleshoot the error on the local
be isolated and resolved, contact your service server. If you find and resolve the error, retry the
representative. export or import operation. If you cannot find the error,
contact your service representative for assistance in
resolving the problem.
ANR0792E Import command: Invalid copy type
encountered in an imported file space
authorization rule for node node name, ANR0795E Command: Error encountered in accessing
file space filespace name - a type of data storage - invalid volume name
BACKUP will be assumed. specified.
Explanation: During import processing for command Explanation: The server encounters an error in
import command, an invalid copy type is encountered accessing data storage while processing command
for an authorization rule that grants access for file command. The error occurred because an attempt has
space filespace name on node node name. Authorization been made to access a volume with an invalid name.
rules typically specify copy types of backup or archive,
System action: The command command operation is
depending on whether backup file access or archive file
access is granted by the file space owner to other users.
Because the imported information for the rule is User response: Issue the command with a valid
ambiguous, the server assumes that the rule is for volume name.
backup data.
System action: The import process continues. ANR0796E Command: Error encountered in accessing
data storage - insufficient number of
User response: The user for node node name should
mount points available for removable
query the access rules for the specified node name after
media.
the import process has completed, and correct or delete
any access rules that are in error or not needed. Explanation: During command command processing,
the server cannot allocate sufficient mount points.

System action: The command command operation is System action: The server starts a background process
ended and server operation continues. to perform the operation in response to the DELETE
FILESPACE command entered by an administrator.
available. User response: To obtain status on the file space
deletion process, issue the QUERY PROCESS command.
The process may be canceled with the CANCEL
PROCESS command.
data storage - required volume was not
mounted.
ANR0801I DELETE FILESPACE filespace name for
Explanation: During command command processing, a
node node name started as process process
required volume cannot be mounted. The mount
ID.
request may have been canceled.
Explanation: The specified client node has started a
file space deletion process (on the server) to delete one
or more file spaces. The process has been assigned the
User response: Issue the command again and make ID specified in the message.
sure the necessary volumes are accessible.
System action: The server starts a background process
to perform the operation in response to a request from
ANR0798E Import command: Error encountered in the client node.
accessing data storage - volume cannot
User response: To obtain status on the file space
be used.
Explanation: During import processing, a volume has The process may be canceled by an authorized
been mounted but cannot be used. administrator using the CANCEL PROCESS command.
System action: The import operation is ended and

server operation continues. ANR0802I DELETE FILESPACE filespace name
(backup/archive data) for node node name
User response: Query the activity log for messages started.
preceding this one that give additional information.
Make sure a usable volume is specified and mounted. Explanation: A background server process has started
(on the server) to delete the specified file space
belonging to the node indicated. If a file space name is
ANR0799E Command: Error encountered in accessing not included in the message, all file spaces belonging to
data storage - volume already in use. the node are deleted.
Explanation: During command command processing, a System action: The background process deletes
volume cannot be used because it is already defined in backup and archive objects for the specified file space
a storage pool, or has been previously used by an while server operation continues.
export, database dump, or database backup operation
(as recorded in the volume history) or is in use by User response: To obtain status on the file space
another process. deletion process, issue the QUERY PROCESS command.
The process may be canceled by an authorized
System action: The command command operation is administrator using the CANCEL PROCESS command.
User response: Specify a volume that is not in use or ANR0803I DELETE FILESPACE filespace name
defined in a storage pool, and that has not been (backup data) for node node name
previously used for an export, database dump, or started.
database backup operation as recorded in the server
volume history information. Use the QUERY VOLUME Explanation: A background server process has started
command to display the names of volumes that are (on the server) to delete backup objects in the specified
defined to server storage pools. Use the QUERY file space belonging to the node indicated. If a file
VOLHISTORY command to display the names of space name is not included in the message, then the
volumes that have been used for export, database backup objects for all file spaces that belong to the
dump, or database backup operations. node are deleted.
System action: The background process deletes
ANR0800I Command command for node node name backup objects for the specified file space while server
started as process process ID. operation continues.
Explanation: A file space deletion process has started User response: To obtain status on the file space
to delete one or more file spaces for the specified node. deletion process, issue the QUERY PROCESS command.
The process is assigned the ID specified in the message. The process may be canceled by an authorized

administrator using the CANCEL PROCESS command. with the QUERY PROCESS or CANCEL PROCESS
commands, respectively.
ANR0804I DELETE FILESPACE filespace name System action: The expiration process is now
(archive data) for node node name started. cancellable. Server operation continues.
Explanation: A background server process has started User response: None.
(on the server) to delete archive objects in the specified
file space belonging to the node indicated. If a file
ANR0812I Inventory file expiration process process
space name is not included in the message, then the
ID completed: processed number of nodes
archive objects for all file spaces that belong to the
nodes, examined number of objects
node are deleted.
objects, deleting number of backup objects
System action: The background process deletes backup objects, number of archive objects
archive objects for the specified file space while server archive objects, number of DB backup
operation continues. volumes DB backup volumes, and number
of recovery plan files recovery plan files.
User response: To obtain status on the file space
retry count objects were retried error
count errors were encountered and
The process may be canceled by an authorized
skipped count objects were skipped.
administrator using the CANCEL PROCESS command.
Explanation: Server expiration processing has
completed. The number of client objects examined and
ANR0805I DELETE FILESPACE filespace name
deleted, based on management class policy, are
canceled for node node name: number of
displayed in the message. A total error count is also
objects objects deleted.
displayed. A count of objects skipped due to replication
Explanation: A background server process that has being required is also included. The number of DB
been deleting file space data for the indicated node is backup volumes deleted is based on the value specified
canceled by the CANCEL PROCESS command. The on the SET DRMDBBACKUPEXPIREDAYS. The
number of objects deleted before the cancel ended the number of recovery plan files deleted is based on the
operation are reported in the message. value specified on the SET DRMRPFEXPIREDAYS.
Server expiration processing deletes the DB backup
System action: The server process is ended and server volumes and recovery plan files only if DRM is
operation continues. licensed on the server and the volumes or plan files are
User response: No action is required. An authorized created on the server to server virtual volumes.
administrator can issue the DELETE FILESPACE System action: The roll-off process is ended and
command to delete remaining objects in the file space. server operation continues.
User response: If the error count is not equal to 0,
ANR0806I The filespace name file space was deleted examine messages that may have been issued in the
for node node name: number of objects activity log to determine the cause for the errors.
objects were deleted.
Explanation: A server process deleted file space data ANR0813I Inventory file expiration process process
for the specified node. The total number of deleted ID canceled prior to completion:
objects is reported in the message. processed number of nodes nodes,
System action: The deletion process is complete, but examined number of objects objects,
server operations continue. deleting number of backup objects backup
objects, number of archive objects archive
User response: None. objects, number of DB backup volumes DB
backup volumes, and number of recovery
ANR0811I Inventory client file expiration started as plan files recovery plan files. retry count
process process ID. objects were retried error count errors
were encountered and skipped count
Explanation: The server has started roll-off processing objects were skipped.
to remove expired client backup and archive file copies,
based on the management class policy that is bound to Explanation: The inventory file expiration process was
the files. The copy group retention and version canceled by an administrator. The number of objects
parameters for each file's copy group are used by the examined and deleted prior to the cancelation are
server to determine if copies are to be deleted from the reported. A total error count and a skipped is also
server. The expiration process was started as process displayed.
number process ID, and may be queried or canceled System action: The server ends the file expiration
process.

User response: None. User response: Reissue the command with a different
target filespace name
ANR0819I Cancel in progress
ANR0824I Delete Filespace filespace name
Explanation: This message is displayed in response to
(space-managed data) for node node name
a QUERY PROCESS command, and indicates that an
started.
inventory expiration process has been canceled. The
process will end shortly. Explanation: A background server process has started
(on the server) to delete space-managed objects in the
System action: The expiration process terminates and
specified file space belonging to the node indicated. If a
file space name is not included in the message, then the
User response: None. space-managed objects for all file spaces that belong to
the node are deleted.
ANR0820I Sorting information for number objects System action: The background process deletes
has been deleted. space-managed objects for the specified file space while
Explanation: A background server process has deleted
sorting information for number files from the server User response: To obtain status on the file space
database. This process is started during initialization to deletion process, issue the QUERY PROCESS command.
remove any sorting information which is left over from The process may be canceled by an authorized
previous export operations. administrator using the CANCEL PROCESS command.
System action: The actual backup or archive objects

were not deleted, but only information used to sort ANR0826I DELETE FILESPACE filespace name for
these objects during the previous export operation. node node name encountered a
transaction failure.
Explanation: A background server process that has
been deleting file space data for the indicated node
ANR0821E Filespace identifier fsId is not valid. encountered a transaction failure.
Explanation: The identifier assigned for a filespace is System action: The server process is retried if the
out of range. maximum number of retry attempts have not been
System action: The file space is not added. exceeded.
User response: Contact your service representative. User response: Transaction failure usually indicates
that a database deadlock was detected during file space
deletion. These deadlock conditions are sometimes
ANR0822I command: Filespace filespace name encountered when multiple file space deletion
(fsId=filespace id) successfully renamed processes are running at the same time. No action is
to new filespace name for node node name. required unless the DELETE FILESPACE terminates
Explanation: The file space specified was renamed to without completing the deletion process (see message
the new name specified for the node. This message is ANR0828).
displayed in response to successful completion of the
RENAME FILESPACE command. ANR0827I DELETE FILESPACE filespace name will
System action: The system renames the file space for be retried for node node name.
the node as indicated Explanation: A file space deletion process for the node
User response: None. indicated is being retried because an error was
encountered.
ANR0823E command: Filespace filespace name cannot System action: The server process is retried.
be renamed to new filespace name, a User response: None.
filespace with this name already exists
for node node name.
ANR0828W DELETE FILESPACE filespace name for
Explanation: The file space name specified as a target node node name terminated before
name for the command was found to already exist for completion due to transaction failure:
the node specified. The command fails. number of objects objects deleted.
System action: Server operation continues, the Explanation: A background server process that has
command fails. been deleting file space data for the indicated node is
terminated prematurely because of transaction failure.

The number of objects deleted before the operation uses the GRACE PERIOD retention value defined for
ended are reported in the message. the specified policy domain to determine if client file
copies need to be expired and removed from the server
System action: The server process is ended and server
database.
System action: The server obtains the GRACE
User response: Termination of this process because of
PERIOD retention values for the specified domain and
transaction failure usually indicates that a database
then determines if backup file copies need to be
deadlock was detected during file space deletion. These
expired.
deadlock conditions are sometimes encountered when
multiple file space deletion processes are running at the User response: No action is required. A policy
same time. The command should be started again administrator with authority over the specified domain
when fewer file space deletion processes are active. An may use the DEFINE COPYGROUP, DEFINE
authorized administrator can issue the DELETE MGMTCLASS, and ACTIVATE POLICY commands to
FILESPACE command to delete remaining files in the define and activate a policy set that contains definitions
file space(s). for the missing management class or backup copy
group.
ANR0829E Command: Invalid combination of TYPE
and DATA parameters. ANR0832W Management class class name in domain
domain name used by node node name in
Explanation: The specified command has been issued
filespace filespace name is no longer
with an invalid combination of the TYPE and DATA
active, or no longer has an ARCHIVE
parameters. DATA=IMAGES can only be specified if
copy group: DEFAULT management
TYPE=ANY or TYPE=BACKUP.
class attributes will be used for
System action: Server operation continues, but the expiration.
command is not processed.
Explanation: During policy roll-off processing, the
User response: Issue the command and specify a valid server found a client file copy whose management class
combination of parameters. or archive copy group no longer exists.
System action: The server obtains the DEFAULT
ANR0830W Management class class name in domain management class for the specified domain and uses its
domain name used by node node name in archive copy group retention parameter to determine if
file space filespace name is no longer file copies need to be expired.
active, or no longer has a BACKUP copy
User response: No action is required. A policy
group: DEFAULT management class
administrator with authority over the specified domain
attributes will be used for expiration.
may use the DEFINE COPYGROUP, DEFINE
Explanation: During policy roll-off processing, the MGMTCLASS, and ACTIVATE POLICY commands to
server has found a client file copy whose management define and activate a policy set that contains definitions
class or backup copy group no longer exists. for the missing management class or copy group.
management class for the specified domain and uses its ANR0833W The DEFAULT management class class
backup copy group version and retention parameters to name in domain domain name does not
determine if file copies need to be expired. have an ARCHIVE copy group: GRACE
PERIOD will be used for expiration.
User response: No action is required. A policy
administrator with authority over the specified domain Explanation: During policy roll-off processing, the
may use the DEFINE COPYGROUP, DEFINE server found a client file copy whose management class
MGMTCLASS, and ACTIVATE POLICY commands to or archive copy group no longer exists. The DEFAULT
define and activate a policy set that contains definitions management class for the indicated policy domain does
for the missing management class or copy group. not contain an archive copy group; therefore, the server
uses the GRACE PERIOD retention value defined for
the specified policy domain to determine if client file
ANR0831W The DEFAULT management class class copies need to be expired and removed from the server
name in domain domain name does not database.
have a BACKUP copy group: GRACE
PERIOD will be used for expiration. System action: The server obtains the GRACE
PERIOD retention values for the specified domain and
Explanation: During policy roll-off processing, the then determines if archive file copies need to be
server found a client file copy whose management class expired.
or backup copy group no longer exists. The DEFAULT
management class for the indicated policy domain does User response: No action is required. A policy
not contain a backup copy group; therefore, the server administrator with authority over the specified domain

may use the DEFINE COPYGROUP, DEFINE DEFINE MGMTCLASS, and ACTIVATE POLICY
MGMTCLASS, and ACTIVATE POLICYSET commands commands to define and activate a policy set that
to define and activate a policy set that contains contains definitions for the missing management class
definitions for the missing management class or backup or copy group.
copy group.
ANR0836W No query restore processing session
ANR0834W Inventory client file expiration cannot session id for node node name and filespace
start because of insufficient memory - name failed to retrieve file high-level file
will retry in number of seconds seconds. namelow-level file name - file being
skipped.
Explanation: The server inventory expiration process
is pausing to retry an operation that failed because Explanation: The no query restore processing for the
sufficient memory is not available on the server. session listed relating to the specified node name and
filespace failed to retrieve the specified file. An error
System action: Server operation continues; the
occurred while retrieving this file so it will be skipped.
expiration process will be retried after the stated delay.
System action: The no query restore operation
continues.
application. User response: Determine the cause of the file retrieve
failure and correct it. After this situation is correct, the
client can do a restore of the specific file that was
ANR0835W Management class class name in domain
skipped.
domain name is no longer active, or no
longer has a BACKUP copy group, or no
longer has an ARCHIVE copy group. ANR0837I Inventory file expiration process process
DEFAULT management class used to ID was terminated after exceeding the
delete number of backup files backup files duration limit of duration minutes:
and number of archive files archive files. processed number of nodes nodes,
Retention grace period used to delete examined number of objects objects,
number of backup files backup files and deleting number of backup objects backup
number of archive files archive files. objects, number of archive objects archive
objects, number of DB backup volumes DB
backup volumes, and number of recovery
server found a management class or backup copy
plan files recovery plan files. retry count
group or archive copy group that no longer exists.
objects were retried error count errors
When a management class or backup copy group no
were encountered and skipped count
longer exists, the number of backup client file copies
objects were skipped.
that have been deleted using the default management
class or the retention grace period is displayed in the Explanation: An administrator or schedule issued the
message. When a management class or archive copy command EXPIRE INVENTORY ... DURATION=xxx,
group no longer exists, the number of archive client where xxx is the number of minutes for the expire
files that have been deleted using the default inventory process to run. That xxx number of minutes
management class or the retention grace period is has been reached, so the expire inventory process ends.
displayed in the message.
System action: The expire inventory process ends.
management class for the specified domain and uses its
backup copy group or archive copy group version and
retention parameters to determine if file copies need to ANR0844E Command: node name is not a
be expired. If, however, the needed backup copy group backup-archive node.
or archive copy group does not exist in the DEFAULT
management class, the server will use the retention Explanation: The specified node name is not a
grace period for the domain. backup-archive node.
User response: No action is required. This message is System action: Processing fails for the command.
only issued when expiration processing has been Server operation continues.
started with the QUIET option to suppress detailed User response: Reissue the command with a valid
messages. Expiration processing can be started without node name.
the QUIET option to see the detailed messages which
will indicate specific node and filespaces and will
further distinguish between backup and archive copy
groups. A policy administrator with authority over the
specified domain may use the DEFINE COPYGROUP,

ANR0848W Expiration failed to delete file type file ANR0852E Command: No matching file spaces
file name for node node name and found for node node name.
filespace filespace name - file will be
Explanation: The server did not find any file spaces
skipped.
for the node indicated matching the names specified in
Explanation: The expiration process was unable to the command.
delete the indicated file. The file will be skipped by
System action: The server ends the command.
expiration.
User response: Enter the command with file space
System action: The expiration process continues.
names that refer to defined file spaces for the specified
User response: Try expiration again to determine if node. Note that file space names are case sensitive.
the cause of the deletion failure was an intermittent Enter them by using exactly the same uppercase and
problem or if it is a permanent problem. If after a lowercase characters that match the file space name
subsequent expiration attempt the file still is not defined on the server. Use the QUERY FILESPACE
deleted, contact your service representative. command to determine which file spaces are defined
for a node on the server.
ANR0849E Command: Not permitted for node Node
Name - node of type SERVER. ANR0853E Transaction failed in file space deletion,
DELETE FILESPACE process aborted.
Explanation: The indicated DELETE FILESPACE
process is not started because the node specified is of Explanation: A database transaction fails while the
NODETYPE=SERVER. A DELETE FILESPACE may server is deleting file space data.
only be processed for nodes of this type with the
System action: The server ends the file space deletion
TYPE=SERVER parameter specified.
process.
System action: The DELETE FILESPACE command is
ended and server processing continues.
User response: If this filespace must be deleted, error. Issue the QUERY ACTLOG command to view the
Reissue the command with the TYPE parameter set to activity log and search for messages. If the error cannot
TYPE=SERVER. Please use caution when using the be isolated and resolved, contact your service
TYPE=SERVER parameter as this can impact the representative.
availability of data for the server that owns these files.
ANR0854E Inventory file space query failure,
ANR0850E Command: Cannot Start process name DELETE FILESPACE process aborted.
Process.
Explanation: The server encounters an error in
Explanation: The indicated DELETE FILESPACE querying the inventory database during a file space
process cannot be started on the server. deletion process.
System action: The DELETE FILESPACE command is System action: The server ends the file space deletion
ended and server processing continues. process.
User response: This usually indicates that sufficient User response: Examine the server messages issued
server memory is not available on the server. prior to this message to determine the source of the
error. Issue the QUERY ACTLOG command to view the
See the documentation for the operating system about
how to increase memory for an application.
representative.
ANR0851E Cannot start delete file space thread for
node node name.
ANR0855E Server LOG space exhausted, DELETE
Explanation: The indicated DELETE FILESPACE FILESPACE process aborted.
process cannot be started on the server. Sufficient
Explanation: Insufficient server log space has been
memory on the server may not be available.
encountered during file space deletion processing.
System action: The DELETE FILESPACE command is
ended and server processing continues.
process.
User response: To increase the amount of log space
that is available to the server, evaluate the directories
application.
ACTIVELOGDIRECTORY, ARCHIVELOGDIRECTORY,

and ARCHFAILOVERLOGDIRECTORY options in the prior to this message to determine the source of the
dsmserv.opt file. An out of log space condition might error. Issue the QUERY ACTLOG command to view the
occur because the ACTIVELOGDIRECTORY location is activity log and search for messages. If the error cannot
full. be isolated and resolved, contact your service
representative.
Alternatively, an out of log space condition might occur
if there are log files in the ACTIVELOGDIRECTORY
location that are no longer active and cannot be ANR0861E Transaction failed in expiration,
archived to the ARCHIVELOGDIRECTORY and inventory expiration aborted.
ARCHFAILOVERLOGDIRECTORY locations. If
Explanation: The server encounters a database
necessary, specify a larger directory for the
transaction failure during policy roll-off processing.
ARCHFAILOVERLOGDIRECTORY options in the System action: The server ends roll-off processing.
dsmserv.opt file and then restart the server.
ANR0856E Server database space exhausted, error. Issue the QUERY ACTLOG command to view the
DELETE FILESPACE process aborted. activity log and search for messages. If the error cannot
Explanation: Insufficient server database space has
representative.
been encountered during file space deletion processing.
ANR0865E Expiration processing failed - internal
process.
server error.
Explanation: Server retry processing during policy
space that is available to the server, issue the EXTEND
roll-off fails.
DBSPACE command to add one or more directories to
the database. System action: The server ends policy roll-off
processing.
ANR0859E Data storage object erasure failure, User response: Issue the QUERY ACTLOG command
DELETE FILESPACE process aborted. to view the activity log and search for messages.
Examine the server messages issued prior to this
message to determine the source of the error.
removing file copies from data storage during file space
deletion processing. The following issues can cause this message to occur:
System action: The server ends the file space deletion v The server is out of database space. To increase the
process. amount of database space that is available to the
server, issue the EXTEND DBSPACE command to
User response: Examine the server messages issued add one or more directories to the database.
v The server is out of log space. To increase the
amount of log space that is available to the server,
evaluate the directories and file systems that are
assigned to the ACTIVELOGDIRECTORY,
representative.
ARCHIVELOGDIRECTORY, and
ARCHFAILOVERLOGDIRECTORY options in the
ANR0860E Expiration process process ID terminated dsmserv.opt file. An out of log space condition might
due to internal error: examined number of occur because the ACTIVELOGDIRECTORY location
objects objects, deleting number of backup is full. Alternatively, an out of log space condition
objects backup objects, number of archive might occur if there are log files in the
objects archive objects, number of DB ACTIVELOGDIRECTORY location that are no longer
backup volumes DB backup volumes, and active and cannot be archived to the
number of recovery plan files recovery plan ARCHIVELOGDIRECTORY and
files. retry count objects were retried and ARCHFAILOVERLOGDIRECTORY locations. If
error count errors were encountered. necessary, specify a larger directory for the
Explanation: The server encounters an internal error
during file expiration processing. The number of files
examined and deleted prior to the error are reported. A
total error count is also displayed. v The server is low on memory. To increase the
amount of memory that is available to the server, see
System action: The server ends the expiration process. the operating system documentation that describes
User response: Examine the server messages issued how to increase memory for an application.

If the error cannot be isolated and resolved, contact activity log and search for messages. If the error cannot
your service representative. be isolated and resolved, contact your service
representative.
ANR0866E Expiration processing retries failed - no
success after maximum retries retries. ANR0868E Cannot find management class name for
ID management class ID.
Explanation: Server policy roll-off processing ends
because retry processing has not been successful in Explanation: Policy roll-off processing on the server
expiring client file copies from the server database. encounters an error while obtaining policy information.
System action: The server ends policy roll-off System action: The server ends roll-off processing and
processing and server operation continues. server operation continues.
User response: Issue the QUERY ACTLOG command User response: Examine the server messages issued
to view the activity log and search for messages. prior to this message to determine the source of the
Examine the server messages issued prior to this error. Issue the QUERY ACTLOG command to view the
message to determine the source of the error. activity log and search for messages. If the error cannot
The following issues can cause this message to occur:
representative.
v The server is out of database space. To increase the
amount of database space that is available to the
server, issue the EXTEND DBSPACE command to ANR0869E Cannot find policy domain for node
add one or more directories to the database. node ID.
v The server is out of log space. To increase the Explanation: Policy roll-off processing on the server
amount of log space that is available to the server, encounters an error while obtaining policy information
evaluate the directories and file systems that are related to the specified node.
assigned to the ACTIVELOGDIRECTORY,
System action: The server ends roll-off processing and
ARCHIVELOGDIRECTORY, and
dsmserv.opt file. An out of log space condition might User response: Examine the server messages issued
occur because the ACTIVELOGDIRECTORY location prior to this message to determine the source of the
is full. Alternatively, an out of log space condition error. Issue the QUERY ACTLOG command to view the
might occur if there are log files in the activity log and search for messages. If the error cannot
ACTIVELOGDIRECTORY location that are no longer be isolated and resolved, contact your service
active and cannot be archived to the representative.
ARCHIVELOGDIRECTORY and
necessary, specify a larger directory for the ANR0870E Cannot find node name for node node
ARCHIVELOGDIRECTORY or ID.
ARCHFAILOVERLOGDIRECTORY options in the Explanation: Policy roll-off processing on the server
dsmserv.opt file and then restart the server. encounters a database error in obtaining information
v The server is low on memory. To increase the for a client node.
amount of memory that is available to the server, see
the operating system documentation that describes
how to increase memory for an application.
If the error cannot be isolated and resolved, contact prior to this message to determine the source of the
your service representative. error. Issue the QUERY ACTLOG command to view the
ANR0867E Unable to open policy domain for node representative.
node name during server operation.
Explanation: Policy roll-off processing on the server ANR0871E Cannot find file space name for node
encounters an error while obtaining policy information node ID, file space file space ID.
related to the specified node.
Explanation: Policy roll-off processing on the server
System action: The server ends roll-off processing and encounters a database error in obtaining information
server operation continues. for a client node.
User response: Examine the server messages issued System action: The server ends roll-off processing and
prior to this message to determine the source of the server operation continues.

User response: Examine the server messages issued encounters a database error in obtaining archive
prior to this message to determine the source of the information in data storage.
ANR0872E Grace Period retention for domain
domain name could not be obtained.
Explanation: Policy roll-off processing on the server representative.
encounters a database error in obtaining GRACE
PERIOD values for the specified policy domain.
ANR0879E Error opening inventory file space
System action: The server ends roll-off processing and query.
Explanation: Policy roll-off processing on the server
User response: Examine the server messages issued encounters a database error in accessing inventory
prior to this message to determine the source of the information.
ANR0873E Invalid copy type encountered in
expiring files: copytype ID
Explanation: Policy roll-off processing on the server representative.
encounters a database error in obtaining copy group
information.
ANR0880E Filespace command: No matching file
System action: The server ends roll-off processing and spaces.
Explanation: The server did not find any file space
User response: Examine the server messages issued names matching the specifications entered in the
prior to this message to determine the source of the filespace command.
be isolated and resolved, contact your service User response: Use the QUERY FILESPACE command
representative. to determine which file spaces are defined on the
server. Note, that file space names are case sensitive.
Reissue the file space command and specify the proper
ANR0874E Backup object object not found during
file space name (in proper case).
inventory processing.
Explanation: Inventory processing on the server
ANR0881E Policy Error : the GRACE PERIOD
encounters a database error in obtaining backup
archive retention value could not be
information in data storage.
obtained for domain domain ID during
System action: The server ends roll-off processing, or client inventory processing.
client session(s) and server operation continues.
User response: Examine the server messages issued in accessing policy information.
be isolated and resolved, contact your service User response: Contact your service representative.
representative.
ANR0882E Policy Error: Unable to open policy

ANR0875E Archive object object.ID not found domain for node node name during client
during expiration processing. inventory query processing.
Explanation: Policy roll-off processing on the server Explanation: The server encounters an internal error
in accessing policy information.

System action: The client operation is ended and want to examine the policy definitions for new
server operation continues. management class name so they are aware of the
management classes that may be used if the policy set
containing this management class is activated.
ANR0883E Cannot obtain node name for node node

ANR0886E Management class class name in domain
ID.
Explanation: The server encounters an internal error file space filespace name has no BACKUP
in accessing client node information. copy group with id copy group id;
Expiration will not be performed for
System action: The operation is ended and server files from this node and filespace that
operation continues. are bound to this management class and
User response: Contact your service representative. copy group id.
ANR0884E Error code during deletion of sorting server finds a client file copy with a management class
information for number objects. or a backup copy group that no longer exists.
Explanation: A background server process System action: The server skips the files in error.
encountered an internal error after deleting sorting User response: For programming support, contact
information for number files from the server database. your service representative.
This process is started during initialization to remove
any sorting information which is left over from
previous export operations. ANR0887E Management class class name in domain
System action: The backup or archive objects were not file space filespace name has no archive
deleted. Only the information used to sort these objects copy group with id copy group id. Server
during the previous export operation was deleted. The operation will not be performed for files
background process was terminated before all sorting from this node and filespace that are
information had been deleted. The system will not bound to this management class and
perform further export processing of file data until this copy group id.
problem has been resolved.
User response: Examine the server messages issued server finds a client file copy with a management class
prior to this message to determine the source of the or an archive copy group that no longer exists.
activity log and search for messages. Then restart the System action: The server skips the specified files.
server. If the error cannot be isolated and resolved,
User response: For programming support, contact
your service representative.
ANR0885I Import command: Processing management

ANR0888E SQL commands cannot be issued from
class management class name for domain
the server console.
domain name and policy set policy set
name as management class new Explanation: An SQL command was issued from the
management class name. server console. SQL commands cannot be issued from
the server console because they may require a long
Explanation: The background import process to
time complete and the server console should be
service the command import command is currently
available to control other server functions.
processing the policy information for management class
management class name in domain domain name and System action: The server ignores the command and
policy set policy set name. The management class is continues processing.
imported under the name new management class name.
User response: Issue the SQL command from an
During import processing, management classes defined
administrative client.
as either DEFAULT or GRACE_PERIOD must be
renamed so that the management class does not conflict
with existing server policy conventions. Import ANR0889I Deleted count statistics reports about
processing is then able to import file data by using the data deduplication for node node name.
renamed management class.
Explanation: The server processed DELETE
System action: Import processing for the command DEDUPSTATS for the specified node, with the total
continues. number of deleted statistics reports about data
deduplication specified in this message.
User response: None. However, an administrator may

System action: The deletion of data deduplication

ANR0894I Current system has been accepted as
statistics is complete for the node, and server
valid.
operations continue.
Explanation: This message is displayed when the
ACCEPT DATE command has been issued and the date
has been accepted as valid by the server.
System action: The current system date is accepted as
optionset optionset name.
valid by the server. The server will begin processing
Explanation: The background export or import using the current system date.
User response: Issue the ENABLE SESSIONS ALL
is currently processing optionset definition information.
command to allow client, server and administrative
System action: Export or import processing for the sessions to start.
command continues.
User response: None. ANR0895E Command: Cannot Start process name
Process.
ANR0891I Export/import command: Copied number Explanation: The indicated process cannot be started
optionset definitions. on the server.
Explanation: The background export or import System action: The specified command is ended and
process to service the command export/import command server processing continues.
copies number client optionset definitions from the
User response: This usually indicates that sufficient
server database to export media or from export media
server memory is not available on the server.
into the server database. Data is not moved if
Preview=Yes is specified in the command export/import See the documentation for the operating system about
command. how to increase memory for an application.
command completes. Server operation continues. ANR0896I Generated count statistics reports about
data deduplication for node node name in
pool pool name.
Explanation: The server processed GENERATE
ANR0892I Export command: No matching optionsets
DEDUPSTATS for the specified node and pool, with the
found for exporting.
total number of generated statistics reports about data
Explanation: The background export process does not deduplication specified in this message.
find any client optionsets for export command.
System action: The generation of data deduplication
System action: The export process continues and no statistics is complete for the node and pool specified in
option sets from the server. the command, and server operations continue.
ANR0893I Are you sure that you want to accept the ANR0900I Processing options file filespec.
current system date as valid ?
Explanation: At server initialization, the server is
Explanation: This message is displayed when the reading the server options file whose name is shown in
ACCEPT DATE command has been issued to confirm the message.
that you want to accept the date on the system as
System action: The server reads and processes the
valid. Accepting an invalid date can cause any of the
options in this file.
following problems:
Premature deletion of data User response: None.
Excessive retention of data
Scheduling problems
ANR0901W Invalid option statement found in file
Event record problems
filespec.
Password expiration problems.
Explanation: While processing the server options file
System action: The command waits for you to
named, the server has encountered an invalid
confirm the action.
statement. The invalid statement type is shown in the
User response: Specify Yes if you want to accept the message. The lines following this message provide
system date as valid, or No if you do not want to more information.
execute the command.

System action: The server ignores the statement in restart the server to activate changes.
error. Server initialization continues. The default value
is used for any missing or ignored options.
ANR0916I Product Name distributed by Company is
User response: Ignore the error, or use a text editor to now ready for use.
correct the error and restart the server.
Explanation: The server has completed startup
processing and is now ready for use.
ANR0902W Unsupported keyword or invalid value
found in file filespec.
Explanation: While processing the server options file
named, the server has encountered an invalid keyword
or an invalid value on an option statement. The lines ANR0917W Session session number for node node
following this message provide more information. name (client platform) - in domain domain
name failed because of policy length.
System action: The server ignores the option
statement in error. Server initialization continues. The Explanation: The client cannot handle very long
default value is used for any missing or ignored policies.
options.
System action: The client operation is ended and
User response: Ignore the error, or use a text editor to server operation continues.
correct the error and restart the server.
User response: Upgrade the client to the latest level,
or activate a policy set with fewer management classes.
ANR0905W Options file filespec not found.
Explanation: At server initialization, the server is ANR0918E Inventory operation for node node name
unable to locate the server options file named. terminated - lock conflict.
System action: The server uses the default values for Explanation: During the indicated operation, the
all options. Server initialization continues. server needs to obtain a lock that is not available.
User response: If the default values are acceptable, System action: The indicated operation ends.
ignore the error. Otherwise, move a valid server
options file to the proper location, rename a valid User response: Restart the operation.
options file to the proper name, or use a text editor to
build the proper server options file, and then restart the ANR0919E Filespace name fsName with length
server. length was encountered for nodes node
list.
ANR0914E Diagnostic(ID): a request failed because Explanation: The specified filespace name was found
object (object name), size (size), exceeds for the nodes in the list. The name is not allowed. The
the maximum size of maximum size. error may occur while processing an administrative
Explanation: The size of the specified object exceeds command or client request.
the maximum size defined for that object. The server System action: Server processing continues.
cannot handle the new object.
User response: If the error occurs during processing
System action: The activity that generated this error for an administrative command such as EXPORT
fails. NODE or RENAME FILESPACE, rename the filespace
User response: Determine why the new object's length for the nodes in the list using a valid name. If found
exceeds the maximum specified for the object. Reduce while processing a client request, contact your service
the length of the object. representative.
ANR0915E Unable to open language language name ANR0920I Tracing is now active to standard
for message formatting. output.
Explanation: The server is unable to open the Explanation: In response to a TRACE START
specified message repository. command, server trace records are being written to the
standard output destination (usually the server
System action: Server initialization continues with the console).
default message repository.
User response: Ensure that a valid language is
specified in the LANGUAGE option of the server User response: None.
options file. If a change is made to the options file,

ANR0921I Tracing is now active to file file spec. ANR0928E Unable to open trace file file spec for
appending.
Explanation: In response to a TRACE START
command, server trace records are being written to the Explanation: A TRACE BEGIN command specifies an
file named. output file, but the server cannot write to that file.
System action: None. System action: The command is ignored.
User response: None. User response: Check the file for proper access
permissions, or reissue the TRACE command
specifying a different output file.
ANR0922I Trace ended.
Explanation: In response to a TRACE END command,
ANR0929E Insufficient memory to activate tracing.
server trace records are no longer being written.
Explanation: A TRACE BEGIN command has been
entered, but the server has insufficient memory
User response: None. available to activate tracing.
System action: The command is ignored.
ANR0923E Tracing is inactive.
User response: If tracing is required, make more
Explanation: A TRACE END command has been memory available to the server then restart the server.
entered, but tracing is not active.
System action: The command is ignored. ANR0936E Session session ID for session name failed
sending verb verb name because client
User response: If tracing is desired, use the TRACE not able to handle extended qualifier
ENABLE and TRACE START commands to activate attribute.
server tracing.
Explanation: A server was going to send the reported
verb for the indicated session but was not able to send
ANR0924E Tracing is already active to file file spec. it. The verb could not be sent to the client because it
Explanation: A TRACE BEGIN command has been contains extended information about the low-level
entered, but tracing is already active to the file named. qualifier. The extended low-level qualifier is used to
store names up to 512 bytes in length. The client that
System action: The command is ignored. this verb was supposed to be sent to does not support
User response: If the current trace output file is the extented low-level qualifier information.
acceptable, no action is required. Otherwise use the System action: The send of the verb to the reported
TRACE END command to stop tracing and then reissue session fails and this server operation will fail and
the TRACE BEGIN command as desired. report a communication error.
User response: The client session reported needs to
ANR0925E Tracing is already active to standard have the installed client upgraded to IBM Spectrum
output. Protect version 5.1.5 or higher in order to support the
Explanation: A TRACE BEGIN command has been extended low-level qualifier.
entered, but tracing is already active to the standard
output destination (usually the server console). ANR0937I Expiration process process ID is ending.
System action: The command is ignored. Explanation: The expiration process referenced is
User response: If the current trace output destination ending either because it has been cancelled or because
is acceptable, no action is required. Otherwise use the it has completed the necessary actions. This message is
TRACE END command to stop tracing and then reissue only issued in the case where expiration was processing
the TRACE BEGIN command as desired. a long-running operation, such as deleting a group of
related files (for example, a backup group). This
message indicates the time when the long-running
ANR0927E Unknown trace class keyword - class. operation ended.
Explanation: A TRACE ENABLE command has been System action: None.
entered which specifies an unknown trace class.
User response: Reissue the TRACE command with the
correct class.

canceled if the process is in progress and the source

ANR0939E Error error code occurred while locating
server is available. The target server monitors
base object (baseId) for subfile (subfileId):
communications with the source server. If 5 minutes
Node node name, File space filespace name,
have expired since the last communications, the target
Type file type, File name file name.
server assumes that the source server is no longer
Explanation: Export processing did not find the base available, and the process is canceled. To view the
object for the specified subfile. Export processing does length of time during which the process has been idle,
not continue. issue the QUERY PROCESS command and specify the
process ID for the replication process.
System action: Export processing stops. Server
ANR0944E Command: No active processes found.
User response: Audit the database to correct the
entries. Explanation: A QUERY PROCESS command has been
entered, and no processes are active.
ANR0940I Cancel request accepted for process System action: The server ignores the command.
process ID.
Explanation: A CANCEL PROCESS command has
been entered for the specified process. Some processes
ANR0946E Archive processing fails: Object objId not
will experience a delay before they terminate. This
found.
delay may be lengthy for processes that involve remote
data movement. Explanation: Archive processing fails because the
specified object was not found. An archive request is
completed in stages. The object may have been deleted
User response: None. by an archive delete request, delete filespace or
expiration that began and completed between these
stages.
ANR0941I Command: Cancel for process process ID
is already pending. System action: System processing continues.
Explanation: A CANCEL PROCESS command has User response: Check the client log for error and retry
been entered for the specified process, but a cancel is messages. Reissue the archive request if the retry failed.
already pending for that process.
System action: The server ignores the command. ANR0947E Error writing to trace file file spec.
User response: None. Explanation: An error occurred while writing to the
specified trace file.
ANR0942E Command: Process process ID cannot be System action: Trace is disabled.
found.
User response: Check the file for proper access
Explanation: A CANCEL PROCESS command has permissions, or for the out of space issue for the trace
been entered for the specified process, but the process file. Once this is corrected, reissue the TRACE BEGIN
is not active. Either the process has already ended or command, specifying either the same or a different
the wrong process number has been entered. output file.
System action: The server ignores the command.
ANR0950I Session Session number for node Node
User response: If the wrong process number has been
name is using inline server data
entered, reissue the command with the correct process
deduplication or inline compression.
number.
Explanation: Inline data deduplication or inline
compression was used for the specified node and
ANR0943E Command: Process process ID could not be
session.
canceled.
System action: Data was deduplicated by the server
Explanation: A CANCEL PROCESS command has
as it was written to the container storage pool.
been entered for the specified process, but the process
specified is an automatic process, such as migration or User response: None.
reclamation, that cannot be canceled.
User response: If the process is a REPLICATE NODE
process and is on the target server, it cannot be


ANR0951I Session Session number for node Node
name processed files processed files by User response: None.
using inline data deduplication or
compression, or both. The number of
original bytes was bytes processed. Inline ANR0960I Process process ID waiting for mount
data deduplication reduced the data by point in device class device class name.
bytes reduced by dedup bytes and inline Explanation: The process whose ID is shown has
compression reduced the data by bytes begun to wait for a mount point that can be used for a
reduced by compression bytes. volume in the device class shown.
Explanation: Data deduplication or compression System action: The process waits for the mount point.
processing, or both, is complete for the specified node.
User response: Respond to any mount requests.
System action: Statistics are displayed for the
specified node.
ANR0961I Process process ID waiting for multiple
User response: None. mount points in device class device class
name.
ANR0952W The filespace Filespace name cannot be Explanation: The process whose ID is shown has
included in the backup set because it begun to wait for multiple mount points that can be
contains encrypted data. used for a volume in the device class shown.
Explanation: Data from the filespace cannot be System action: The process waits for the mount
included in the backup set because the filespace points.
contains encrypted data.
System action: The filespace is skipped.
User response: None. ANR0962I Process process ID waiting for mount
points in device classes device class name
ANR0955I DELETE FILESPACE filespace name for and device class name.
node node name failed deletion because Explanation: The process whose ID is shown has
of a restartable restore session. begun to wait for mount points that can be used for a
Explanation: The reported node and filespace have a volume in the two device classes shown.
restartable restore session active or restartable. A System action: The process waits for the mount
filespace cannot be deleted while the restartable restore points.
session exists.
System action: The server process is retried if the
maximum number of retry attempts have not been
exceeded. ANR0963I Process process ID waiting for mount of
input volume volume name.
User response: Use the QUERY RESTORE command
to view active and restartable restores sessions for this Explanation: The process whose ID is shown has
filespace. Either wait for the sessions to complete or begun to wait for the mount of the input volume
cancel the sessions with the CANCEL RESTORE shown.
command, and reissue the DELETE FILESPACE System action: The process waits for the mount.
command. To view restartable restore sessions issue the
command QUERY RESTORE. Either: User response: Respond to any mount requests.
v wait to reissue the DELETE FILESPACE command
after this restartable restore has completed ANR0964I Process process ID waiting for mount of
v cancel the restartable restore session with the output volume volume name.
CANCEL RESTORE command Explanation: The process whose ID is shown has
begun to wait for the mount of the output volume
ANR0958I CLEANUP BACKUPGROUPS evaluated shown.
objectcount group objects, found System action: The process waits for the mount.
errorcount errors, and deleted deleted
group objects with completion state User response: Respond to any mount requests.
state.
Explanation: The CLEANUP BACKUPGROUPS utility
ended with the presented state.

ANR0965I Process process ID waiting for mount of ANR0982I Session Session number for node Node
scratch volume. name is using server-side encryption.
Explanation: The process whose ID is shown has Explanation: Server-side encryption was used for the
begun to wait for the mount of a scratch volume. specified node and session.
System action: The process waits for the mount. System action: Data was encrypted by the server as it
was written to the container storage pool.
ANR0966I Process process ID waiting for access to
input volume volume name. ANR0983W The server database was recorded by a
down-level version of the server
Explanation: The process whose ID is shown has
program. The UPGRADEDB parameter
begun to wait for availability of the input volume
is required to start the server and
shown.
automatically upgrade the database
System action: The process waits for the volume to contents to the current server version.
become available. Please refer to installation instructions
for precautionary backup procedures
User response: None. prior to doing this.
Explanation: At server startup, the server has
ANR0967I Process process ID waiting for access to discovered that the database information was written
output volume volume name. by an earlier version of the server program and is not
Explanation: The process whose ID is shown has compatible with this version. To automatically upgrade
begun to wait for availability of the output volume the server database to this version of the server
shown. program, the UPGRADEDB parameter must be
specified when starting the server.
System action: The process waits for the volume to
become available. System action: The server ends.
User response: None. User response: Refer to installation instructions for

specific information on precautionary measures that
you may want to take to back up the database prior to
ANR0981E The server database must be restored upgrading it to the current server level. After you have
before the server can be started. taken these measures, start the server and specify the
Explanation: This message is issued in one of two UPGRADEDB parameter. This parameter only needs to
cases: 1) The server has been restarted after an be specified once to start the server, and should NOT
incomplete RESTORE DB. In order to start the server, be included in any automated programs that start the
you must restore the database to a consistent state server.
using the DSMSERV RESTORE DB command; 2)
During server operation, an error condition occurred ANR0984I Process process ID for process name started
such that the IBM Spectrum Protect server cannot in the process state at process start time.
continue. This message is issued, and the server halts.
Before you can start the server again, you need to use Explanation: The process whose ID is shown has been
the DSMSERV RESTORE DB command to restore the started for the process indicated by the process name
database. running in the indicated state.
System action: Server initialization stops, or the server System action: None.
stops. User response: None.
User response: If there are other messages issued with
this error message which have instructions associated ANR0985I Process process ID for process name
with them, follow the instructions in those messages. running in the process state completed
Then issue the DSMSERV RESTORE DB command. with completion state completion state at
After the DSMSERV RESTORE DB command completes process start time.
successfully, restart the IBM Spectrum Protect server.
Explanation: A completion state of FAILURE indicates
that the operation encountered an error condition or
terminated before completion. A completion state of
SUCCESS indicates that the operation ran to
completion, but in some situations may have
encountered and reported conditions that would affect
the outcome of the operation.


ANR0988I Process process ID for process name
User response: If the completion state is FAILURE, running in the process state processed
then review the activity log and the event log to try to bytes processed bytes with a completion
determine the cause of the failure. If the completion state of completion state at process start
state is SUCCESS, the activity log and the event log can time.
still be checked for warning messages regarding
conditions that could have affected the operation.
ANR0986I Process process ID for process name SUCCESS indicates that the operation ran to
running in the process state processed completion, but in some situations may have
items processed items for a total of bytes encountered and reported conditions that would affect
processed bytes with a completion state the outcome of the operation.
of completion state at process start time.
User response: If the completion state is FAILURE,
then review the activity log and the event log to try to
determine the cause of the failure. If the completion
state is SUCCESS, the activity log and the event log can
still be checked for warning messages regarding
the outcome of the operation. The total bytes that is
reported is the number of bytes of source data that was
processed in the transaction. It does not include any ANR0989E The server database must be inserted or
meta data that might be in the output. restored before the server can be started.
System action: None. Explanation: The server is restarted after the
LOADFORMAT command is run. To start the server,
you must upgrade the database by issuing DSMSERV
INSERTDB or else the database needs to be restored
determine the cause of the failure. If the completion
using the DSMSERV RESTORE DB command.
still be checked for warning messages regarding System action: Server initialization stops.
User response: Issue the DSMSERV INSERTDB or
DSMSERV RESTORE DB command. Alternatively, the
ANR0987I Process process ID for process name server can be installed using the DSMSERV FORMAT
running in the process state processed command in order to prepare it for regular use without
items processed items with a completion needing to upgrade an earlier version server with the
state of completion state at process start DSMSERV INSERTDB command or restoring the
time. database with the DSMSERV RESTORE DB command.
that the operation encountered an error condition or ANR0990I Server restart-recovery in progress.
Explanation: The server has been restarted after a halt
or system failure. If necessary, the server performs
recovery processing in order to bring the system back
to a consistent state.
the outcome of the operation.
System action: Server initialization continues.
determine the cause of the failure. If the completion ANR0991I server shutdown complete.
still be checked for warning messages regarding Explanation: In response to a HALT command, the
conditions that could have affected the operation. server or storage agent has completed its termination
processing.
System action: The server or storage agent ends.

is not specified and hence the migration runs without

ANR0992I Server's database formatting complete.
duration.
Explanation: The server formatting procedure has
System action: Data is moved from this storage pool
completed successfully. The server is now available for
to the next (target) pool.
normal operation.
System action: Server completes formatting
processing.
ANR1001I Migration process process ID ended for
storage pool storage pool name.
Explanation: A migration process for the named
ANR0993I Server initialization complete.
storage pool ends. This action can occur because the
Explanation: The server has been restarted after a halt low migration threshold for the storage pool has been
or system failure. It is now ready to resume normal reached, there are no more nodes with files to be
operation. migrated, there are no more volumes to be migrated, or
the duration specified has been reached.
System action: Server completes initialization.
ANR0995W This version of the server program is
down-level with respect to the ANR1002I Migration for storage pool storage pool
information recorded on disk; a newer name will be retried in number of seconds
version of the program should be used. seconds.
Explanation: At server startup, the server has Explanation: Because of a problem encountered
discovered that the disk information was written by a attempting migration for the named storage pool,
later version of the server program. This version of the migration is delayed but will be retried after the time
server program should not be used. period shown.
System action: The server ends. System action: The server waits for the specified
period and then retries migration for the storage pool.
User response: Start a version of the server program
This delay applies to a single migration process. After a
that is at the same level as the prior server program
number of unsuccessful retries, the server will
used.
automatically cancel the process. If other migration
processes are executing for the named storage pool,
ANR0996W The information on disk was recorded these processes will continue migration.
by a down-level version of the server
User response: If possible, correct the condition that
program; reinstallation is required to
has caused delayed migration.
use this version.
Explanation: At server startup, the server has
ANR1003I Migration retry delay ended; checking
discovered that the disk information was written by an
migration status for storage pool storage
earlier version of the server program and is not
pool name.
compatible with this version.
Explanation: Because migration for the indicated
System action: The server ends.
storage pool had been delayed due to a problem, the
User response: Install this version of the server to system waited before retrying. The retry wait period
bring the information up to the level of the program has ended, and the system will now retry migration.
being used.
System action: Migration processing for the storage
pool resumes.
ANR1000I Migration process process ID started for
storage pool storage pool name
automatically or manually,
highMig=highMig value, lowMig=lowMig ANR1004I Server formatting complete, database
value, duration=duration. ready for loading.
Explanation: Because the high migration threshold for Explanation: The server formatting procedure has
the storage pool shown has been exceeded, a process completed successfully. The server is ready to be
has been started to migrate files from the storage pool. loaded by issuing the DSMSERV LOADDB or the
Note: a duration value of No means that the duration DSMSERV RESTORE DB command.

System action: Server completes formatting v There is not enough space available in the specified
processing. storage pool.
User response: The DSMSERV LOADDB or the System action: The result of the simultaneous write
DSMSERV RESTORE DB command is required to load operation depends on the setting of the
the database before the server will be ready for use. COPYCONTINUE attribute of the original destination
primary pool destination:
ANR1013I During a store operation, the server is v If the value of the COPYCONTINUE attribute of the
switching to a next pool in the storage destination primary pool is YES, the server will stop
hierarchy. The next storage pool will writing to the failing copy pool for the remainder of
inherit the simultaneous write the session, but continue storing files into a primary
configuration from the destination pool in the storage hierarchy and any other
primary storage pool. remaining copy pools.
v If the value of the COPYCONTINUE attribute of the
Explanation: If during a backup, archive, client
destination primary pool is NO, the server will fail
migration, or server import operation, the server must
the transaction and discontinue the operation.
write data to a next pool in a storage pool hierarchy,
the following rules will apply: User response: Ensure the copy storage pool is set for
1. If the destination storage pool specified in the READWRITE access. If needed, make more space
management class copy group has one or more available in the copy storage pool. After the problem is
copy storage pools associated with it for corrected, take one of the following actions:
simultaneous write operations: v If the value of the COPYCONTINUE attribute of the
a. The server will write the data to the next storage destination primary pool is YES, issue the BACKUP
pool and to the copy pools that are associated STGPOOL commands to back up any files in
with the original destination primary storage primary storage pools in the storage pool hierarchy
pool. that have not been copied to the copy pool that
failed.
b. The setting of the COPYCONTINUE attribute of
the original destination primary pool will be v If the value of the COPYCONTINUE attribute of the
inherited by the next pool. destination primary pool is NO, run the
simultaneous write operation again.
c. If the next pool is configured for simultaneous
write operations, the copy storage pools
associated with the next pool will be ignored as ANR1015I Storage pool pool name has pending bytes
well as the value of its COPYCONTINUE duplicate bytes pending removal.
attribute.
Explanation: The number of bytes indicated have been
2. If the primary storage pool specified in the identified as duplicate bytes in the storage pool, but the
management class copy group does not have copy volumes on which the data resides have not yet been
pools associated with it for simultaneous write reclaimed.
operations:
System action: None
a. The server will write the data to the next storage
pool. User response: None
b. If the next pool is configured for simultaneous
write operations, the copy pools associated with ANR1016W Fibre Channel adapters on the system
the next pool will be ignored. cannot be opened.
System action: The server operation continues. Explanation: Due to problems with the HBAAPI or
User response: None. Refer to IBM Knowledge Center Fibre Channel HBA driver, the HBAAPI function
for details about simultaneous write configurations. cannot open any Fibre Channel host bus adapters
(HBAs) on the system.
ANR1014W The pool type storage pool pool name is System action: None.
either not available, or does not have User response: The IBM Spectrum Protect SAN
enough space for a simultaneous write discovery function is not working. Check your Fibre
operation. Channel host bus adapter (HBA) vendor and upgrade
Explanation: During a backup, archive, client your HBAAPI or Fibre Channel HBA driver version.
migration, or import operation that is using For a list of supported HBAs and required driver levels
simultaneous write, the server cannot write data to the by operating system, see techdoc 1193154 at
specified storage pool. Possible reasons include: http://www.ibm.com/support/
docview.wss?uid=swg21193154.
v The storage pool is unavailable.

ANR1018I Volume deduplication process process ID ANR1022W Migration process process ID terminated
started for storage pool storage pool name, for storage pool storage pool name -
identify processes=number of identify excessive read errors encountered.
processes.
Explanation: During migration for the indicated
Explanation: A volume deduplication process was storage pool, read errors occur that prevented the
started for the storage pool shown. migration from continuing.
System action: None. System action: The indicated migration process ends.
The server waits for the retry period to expire and then
tries the migration again. If other migration processes
are executing for the named storage pool, these
ANR1019W Unable to get the node attributes for processes will continue migration.
node name.
User response: If possible, correct the cause of the
Explanation: The HBAAPI function cannot obtain the read errors.
node's attributes. Removing devices from the SAN
without reconfiguring the system can cause this
ANR1023W Migration process process ID terminated
problem.
for storage pool storage pool name -
System action: None. excessive write errors encountered.
User response: SAN discovery is not working for this Explanation: During migration for the indicated
device. Check the device configuration on the system. storage pool, write errors occur that prevent the
migration from continuing.
ANR1020W Migration process process ID terminated System action: The indicated migration process ends.
for storage pool storage pool name - The server waits for the retry period to expire and then
process canceled. tries the migration again. If other migration processes
Explanation: During migration for the indicated processes will continue migration.
storage pool, a process performing the migration has
been canceled. User response: If possible, correct the cause of the
write errors.
System action: The migration process is terminated. If
other migration processes are executing for the named
storage pool, these processes will continue migration. ANR1024W Migration process process ID terminated
for storage pool storage pool name - data
User response: None. transfer interrupted.
ANR1021W Migration process process ID terminated storage pool, a data transfer operation was interrupted
for storage pool storage pool name - and could not be continued.
storage media inaccessible.
System action: The indicated migration process ends.
Explanation: During migration for the indicated The server waits for the retry period to expire and then
storage pool, a required volume could not be mounted. tries the migration again. If other migration processes
System action: The indicated migration process ends. are executing for the named storage pool, these
The server waits for the retry period to expire and then processes will continue migration.
tries the migration again. If other migration processes User response: If possible, correct the cause of the
are executing for the named storage pool, these interruption.
processes will continue migration.
User response: One possible cause for this failure is ANR1025W Migration process process ID terminated
that the access state for the target volume or storage for storage pool storage pool name -
pool for this operation is not set to READWRITE. insufficient space in subordinate storage
Check the access state for the requested output volume pool.
and storage pool and ensure they are set to
ACCESS=READWRITE. Explanation: During migration for the indicated
storage pool, the server cannot move the data from the
storage pool, because there is not enough space on the
next storage pool to hold it.
tries the migration again.

User response: Make more space available in the next tries the migration again. If other migration processes
storage pool, or use the UPDATE STGPOOL command are executing for the named storage pool, these
to change the next storage pool to one with more space. processes will continue migration.
User response: Wait for the server to retry the
ANR1026W Migration process process ID terminated migration.
unable to move file to subordinate
storage pool due to exclusion by size.
for storage pool storage pool name - thread
Explanation: During migration for the indicated resource not available.
storage pool, the server cannot move the data from the
storage pool, because a file is larger than what is
storage pool, the server cannot start a thread for the
allowed on the next storage pool.
migration process.
User response: Use the UPDATE STGPOOL command
User response: Wait for the server to retry the
to change the next storage pool maximum file size or to
migration. If the error persists, it may indicate a
change the next storage pool target.
shortage of server memory.

sufficient recovery log space is not
available.
storage pool, there is not enough server memory
storage pool, the server runs out of recovery log space.
available.
User response: If necessary, make more server
User response: If necessary, make more memory
recovery log space available.
available to the server.

sufficient database space is not
internal server error detected.
available.
storage pool, the server encounters an internal error.
storage pool, the server runs out of database space.
User response: If necessary, make more server processes will continue migration.
database space available.

for storage pool storage pool name - lock
conflict.
transaction aborted.
storage pool, the server needs to obtain a lock that is
storage pool, the server detected an error while
not available.
attempting to commit a transaction. This message
System action: The indicated migration process ends. should be preceded by other messages that give
The server waits for the retry period to expire and then additional information about the failed transaction.

System action: The indicated migration process ends. period and then retries space reclamation for the
The server waits for the retry period to expire and then storage pool.
User response: If possible, correct the condition that
has stopped reclamation.
User response: Check for additional messages and
ANR1043I Space reclamation retry delay ended;
eliminate the condition that caused the failed
checking volume reclamation status for
transaction.
Explanation: Because space reclamation for the
ANR1034W Files stored on volume volume name
indicated storage pool had been stopped due to a
cannot be migrated - volume is offline
problem, the system waited before retrying. The retry
or access mode is "unavailable" or
wait period has ended, and the system can now retry
"destroyed".
space reclamation.
Explanation: During migration, files on the indicated
System action: Reclamation for the pool begins.
volume cannot be migrated either because the volume
has been varied offline or because of the volume's User response: None.
access mode.
System action: The server continues migration ANR1044I Removable volume volume name is
processing, but skips files stored on the indicated required for space reclamation.
volume.
Explanation: During space reclamation processing, the
User response: If necessary, use the VARY ON or server determines that a removable volume is required
UPDATE VOLUME command for this volume. in order to complete processing.
System action: The server attempts to mount the
ANR1040I Space reclamation started for volume removable volume.
volume name, storage pool storage pool
name (process number process ID). User response: Respond to any mount request for the
indicated volume.
Explanation: The percentage of reclaimable space on
the volume shown has reached the reclaim percentage
specified for the storage group; as a result, data from ANR1045E Reclamation has ended for volume
the volume is moved to another volume so that the volume name. The files on the volume are
volume can be reclaimed. too large for the target storage pool,
storage pool name.
System action: The server starts volume space
reclamation. Explanation: During reclamation for the indicated
volume, the server cannot move the data from the
User response: None. volume because a file is larger than allowed for the
indicated storage pool.
ANR1041I Space reclamation ended for volume System action: Reclamation of the volume stops. If
volume name. other reclamation processes are running, these
processes will continue the reclamation.
Explanation: Space reclamation for the volume named
is complete. User response: Use the UPDATE STGPOOL command
to change the value of the MAXSIZE parameter for the
storage pool. Specify the value as NOLIMIT, or specify
User response: None. a value larger than the largest file to be reclaimed.
ANR1042I Space reclamation for storage pool ANR1046E command: Database upgrade not
storage pool name will be retried in currently supported for this server
number of seconds seconds. because it uses backup sets.
Explanation: Because of a problem encountered Explanation: The current version of the IBM Spectrum
attempting space reclamation for the named storage Protect 6.1 server does not support backup sets.
pool, reclamation stops but will be retried after the However, the server being upgraded uses backup sets,
time period shown. After a number of unsuccessful and so cannot be upgraded at this time. Note that this
retries, the process will be automatically cancelled. is a temporary limitation that will be lifted in a future
IBM Spectrum Protect 6.1 Server Fix Pack.
System action: The system waits for the specified

System action: The command ends without inserting server initialization that might indicatea problem
any data into the database. initializing the locale . Check whether the server is
running in a locale supported by the server. If it is not,
User response: Rerun the command using a version of
restart the server in a supported locale.
the IBM Spectrum Protect 6.1 server that supports
backup sets.
ANR1053E Command: Invalid process number -
processIdvalue
ANR1047E command: Database upgrade not
currently supported for this server Explanation: A QUERY EXPORT command was
because it uses NAS backups with issued that specifies an invalid process number.
TOCs.
System action: The server does not process the
Explanation: The current version of the IBM Spectrum command.
Protect 6.1 server does not support NAS backups that
use a table of contents (TOC). However, the server
process number.
being upgraded uses TOCs, and so cannot be upgraded
at this time. Note that this is a temporary limitation
that will be lifted in a future IBM Spectrum Protect 6.1 ANR1054E Command: Invalid export operation state
Server Fix Pack. - export state
System action: The command ends without inserting Explanation: A QUERY EXPORT command was
any data into the database. issued that specifies an invalid export state.
User response: Rerun the command using a version of System action: The server does not process the
the IBM Spectrum Protect 6.1 server that supports NAS command.
backups with TOCs.
export operation state.
ANR1048E command: Protocol error -
out-of-sequence verb (type verb name)
received. ANR1055E Command: Invalid export session
identifier name - export sess name.
Explanation: The server detects a protocol error while
upgrading the database because a verb has been Explanation: The issued command specifies an invalid
received that does not adhere to the defined verb export session identifier.
sequence. This error may be the result of using a System action: The server does not process the
version of the DSMUPGRD utility that is not command.
compatible with the IBM Spectrum Protect 6.1 version
to which you are upgrading. User response: Reissue the command with a valid
export session identifier.
System action: The command ends without inserting
any data into the database.
ANR1056E command name: The PROCESS parameter
User response: Rerun the command using a version of is not valid if an export identifier is
the server compatible with the version of DSMUPGRD specified.
used to extract the data. Or reextract the data using an
older version of DSMUPGRD that is compatible with Explanation: The command failed because of an
the version of the server. invalid combination of arguments.
ANR1049W The server is unable to obtain operations continue.
number-formatting information from the User response: Reissue the command with a valid set
system-locale attributes. The server of parameters.
substitutes alternate number format
nmbrFmt.
ANR1057E command name: The PROCESS parameter
Explanation: The server is unable to format some is not valid when the STATE parameter
numbers because it is unable to obtain a valid thousand is specified with a value of
and decimal separator value from the system locale. INITIALIZING or SUSPENDED
System action: The server continues. An alternate Explanation: The command failed because of an
number format is used. Numbers are displayed using a invalid combination of arguments.
comma character as the thousand separator and a
period character as the decimal separator. System action: The command fails and server
User response: Check whether errors occurred during

User response: Reissue the command with a valid set

ANR1062W Error initiating space reclamation for
of parameters.
storage pool storage pool name - internal
server error detected.
ANR1058E command name: TODATE must be
Explanation: During an attempt to initiate space
specified when TOTIME is specified.
reclamation for the indicated storage pool, an internal
Explanation: A command supporting the TODATE server error is encountered.
and TOTIME parameters was issued with the TOTIME
System action: Space reclamation stops. The server
parameter specified but without the TODATE
will wait for the retry period to expire and then tries
parameter. When the TOTIME parameter is used, the
the reclamation again.
TODATE parameter must be specified.
System action: The server ignores the command and
continues processing.
ANR1063I Full backup of NAS node nodename, file
User response: Reissue the command and specify both
system file system, started as process
the TODATE and TOTIME parameters.
process ID by administrator administrator.
Explanation: A full backup is started for the indicated
ANR1059I Selective restore of NAS node nodename,
file system of a NAS node. The operation is initiated by
file system file system, started as process
the administrator shown.
process ID by administrator administrator.
Specified files and/or directory trees System action: The indicated process is started.
will be restored to destination
destination.
Explanation: A restore is started for the indicated file
ANR1064I Differential backup of NAS node
system of a NAS node. The operation is initiated by the
nodename, file system file system, started
administrator shown. Selected files and/or directory
as process process ID by administrator
trees specified by the administrator will be restored to
administrator.
the indicated destination.
Explanation: A differential backup is started for the
System action: The indicated process is started.
indicated file system of a NAS node. Only files that
User response: None. have changed since the last full backup will be
processed. The operation is initiated by the
administrator shown.
storage pool storage pool name - lock System action: The indicated process is started.
conflict.
Explanation: While attempting to initiate space
reclamation for the indicated storage pool, the server
ANR1065I Restore of NAS node nodename, file
needs to obtain a lock that is not available.
system file system, started as process
System action: Space reclamation stops. The server process ID by administrator administrator.
waits for the retry period to expire and then tries the A full image for this file system will be
reclamation again. restored to destination destination.
User response: Wait for the server to retry the Explanation: A restore is started for the indicated file
reclamation. system of a NAS node. The operation is initiated by the
administrator shown. The restore will be performed
using a full image of this file system. The file system
will be restored to the indicated destination.
storage pool storage pool name - sufficient
memory is not available. System action: The indicated process is started.
Explanation: During an attempt to initiate space User response: None.
reclamation for the indicated storage pool, there is not
enough server memory available.
ANR1066I Restore of NAS node nodename, file
System action: Space reclamation stops. The server system file system, started as process
waits for the retry period to expire and then tries the process ID by administrator administrator.
reclamation again. A full image plus a differential image
for this file system will be restored to
destination destination.

Explanation: A restore is started for the indicated file

ANR1073E Operation process process ID terminated -
system of a NAS node. The operation is initiated by the
administrator shown. The restore will be performed
available.
using a full image plus a differential image of this file
system. The file system will be restored to the indicated Explanation: During the indicated operation, the
destination. server runs out of recovery log space.
System action: The indicated process is started. System action: The indicated process ends.
User response: None. User response: If necessary, make more server
ANR1067I Operation process process ID completed.
Explanation: The indicated operation completed.
System action: The indicated process ends. available.
User response: None. Explanation: During the indicated operation, the
server runs out of database space.
ANR1068W Operation process process ID terminated - System action: The indicated process ends.
process cancelled.
Explanation: During the indicated operation, a database space available.
background process was cancelled.
System action: The indicated process ends. ANR1075E Operation process process ID terminated -
lock conflict.
Explanation: During the indicated operation, the
server needs to obtain a lock that is not available.
insufficient number of mount points System action: The indicated process ends.
available for removable media.
User response: Restart the operation.
server could not allocate sufficient mount points for the
volumes required.
Explanation: During the indicated operation, not
User response: If necessary, make more mount points enough server memory is available.
available.
available to the server, and then restart the operation.
read errors encountered.
Explanation: During the indicated operation, read
errors prevent the operation from continuing.
User response: If possible, correct the cause of the server detected an error while attempting to commit a
errors and restart the operation. transaction. This message should be preceded by other
messages that give additional information about the
failed transaction.
insufficient space in destination storage System action: The indicated process ends.
pool.
Explanation: During the indicated operation, there is eliminate the condition that caused the failed
not enough space available in the destination storage transaction.
pool.
storage pool and restart the operation.

User response: If possible, determine and correct the

cause of the read errors.
ANR1084E Space reclamation is ended for volume
server encounters an internal error.
volume name. Excessive write errors were
System action: The indicated process ends. encountered.
User response: Contact your service representative. Explanation: During space reclamation for the
indicated volume, write errors occur that prevent
reclamation from continuing.
ANR1080W Space reclamation is ended for volume
volume name. The process is canceled. System action: Space reclamation of the volume stops.
If other reclamation processes are running, these
Explanation: During space reclamation for the
indicated volume, the process performing the
reclamation has been canceled. User response: If possible, determine and correct the
cause of the write errors.
System action: Space reclamation of the volume stops.
processes will continue the reclamation. ANR1085E Space reclamation is ended for volume
volume name. Data transfer was
interrupted.
indicated volume, a data transfer operation has been
volume name. Storage media is
interrupted and cannot be continued.
inaccessible.
indicated volume, a required volume cannot be
mounted.
cause of the interruption.
If other reclamation processes are executing, these
ANR1086E Space reclamation is complete for
volume volume name. The storage pool
has insufficient space.
volume name. There is an insufficient
indicated volume, data could not be moved from the
number of mount points available for
volume due to insufficient space on other volumes in
removable media.
the storage pool.
indicated volume, the server could not allocate
sufficient mount points for the volumes required.
processes continue the reclamation.
User response: Make more space available on other
volumes in the storage pool. If necessary, define the
next storage pool.
available.
volume name. Sufficient recovery log
ANR1083E Space reclamation is ended for volume space is not available.
volume name. Excessive read errors were
encountered.
indicated volume, the server runs out of recovery log
Explanation: During space reclamation for the space.
indicated volume, read errors occur that prevent
System action: Space reclamation stops.
reclamation from continuing.

indicated volume, the server encounters an internal

error.
volume name. Sufficient database space is
not available. System action: Space reclamation of the volume stops.
indicated volume, the server runs out of database
space. User response: Examine the server messages that were
issued prior to this message to determine the source of
System action: Space reclamation stops.
the error. Issue the QUERY ACTLOG command to view
User response: If necessary, make more server the activity log and to look for messages that indicate
database space available. the source of the error. Correct any errors that might
have caused the space reclamation to fail and try the
operation again.
volume name. There is a lock conflict.
volume name. The transaction is ended.
indicated volume, the server needed to obtain a lock
that is not available. Explanation: During space reclamation for the
indicated volume, the server detected an error while
attempting to commit a transaction.
processes will continue the reclamation. System action: Space reclamation of the volume stops.
User response: Wait for the server to try the
reclamation again.
transaction.
volume name. Thread resource is not
available.
ANR1094E Invalid destination storage pool storage
pool name specified for storage of an
indicated volume, the server cannot start a thread for
object using data mover data mover.
the reclamation process.
Explanation: While attempting to store an object using
the indicated data mover, the server determined that
the indicated storage pool was invalid for this
operation. The indicated storage pool is used because it
User response: Wait for the server to try the is specified as the copy group destination of the
reclamation again. If the error persists, it might indicate assigned management class.
a shortage of server memory.
This storage pool could be invalid for any of the
following reasons:
ANR1091E Space reclamation is ended for volume v The storage pool is not defined
volume name. Sufficient memory is not
v The storage pool is a random-access storage pool and
available.
this operation requires a sequential-access storage
Explanation: During space reclamation for the pool
indicated volume, there was not enough server v The storage pool is not a primary storage pool
memory available.
v The storage pool has a NATIVE or NONBLOCK data
System action: Space reclamation of the volume stops. format, which is not supported for this operation
If other reclamation processes are running, these v The storage pool is not a NONBLOCK data format,
processes will continue the reclamation. which is required for server-free operations
User response: If necessary, make more memory v The data format of the storage pool does not match
available to the server. the data format of the data mover
User response: This message usually indicates a
volume name. An internal server error
configuration problem with either the storage pool or
was detected.
the policy. Ensure that the destination storage pool has
Explanation: During space reclamation for the appropriate attributes, including data format, for this
operation. Check the copy group of the assigned

management class. If the destination is incorrect, either

assign a new management class, or change the
thread resource not available.
destination in the copy group and activate the changed
policy. Also, consider whether you must define a new Explanation: During the indicated operation, the
storage pool or data mover. server cannot start a thread.
ANR1095E Data mover operation for node node
User response: The problem may indicate a shortage
name and file space filespace name cannot
of memory. If necessary, make more memory available
be started - an operation involving this
to the server, and then restart the operation.
node and file space is already in
progress.
ANR1100I Migration started for volume volume
Explanation: A request has been made to use a data
name, storage pool storage pool name
mover to perform an operation involving the indicated
(process number process ID).
node and file space. The indicated file space was either
specified as the source for a backup operation or the Explanation: Because the high migration threshold for
destination location for a restore operation. However, a the indicated storage pool has been exceeded,
data mover operation involving that node and file migration of files from the volume shown begins.
space is already in progress; the indicated file space is
either the source for a currently running backup System action: The system moves the data from this
operation or is the destination for a currently running volume to the next (target) pool.
restore operation. To avoid possible conflicts, the new User response: None.
operation is not performed.
System action: The operation fails. ANR1101I Migration ended for volume volume
User response: Allow the current operation to name.
complete before starting a new operation for this node Explanation: Because the low migration threshold for
and file space. the indicated storage pool has been reached, migration
of files from the indicated volume ends.
ANR1096E Operation process process ID terminated - System action: None.
Explanation: During the indicated operation, a
required volume cannot be mounted.
ANR1102I Removable volume volume name is
System action: The indicated process ends. required for migration.
User response: If possible, correct the problem and Explanation: During migration processing, the server
restart the operation. determines that a removable volume is required in
order to complete processing.
ANR1097E Operation process process ID terminated - System action: The server attempts to mount the
data transfer interrupted. removable volume.
Explanation: During the indicated operation, a data User response: Respond to any mount request for the
transfer operation is interrupted and cannot be indicated volume.
continued.
System action: The indicated process ends. ANR1104E Operation process process ID terminated -
User response: If possible, correct the problem and NAS datamover NAS datamover name
restart the operation. reported NDMP session errors.
ANR1098E Operation process process ID terminated - NDMP session with the NAS file server reported errors
file deleted from data storage during which prevent the operation from continuing.
retrieval. System action: The indicated process ends.
Explanation: During the indicated operation, a file User response: For details about how to identify the
was deleted from data storage during retrieval. cause of the terminated NDMP operations, see the NAS
System action: The indicated process ends. file-server documentation. Check the NDMP logs for
the NAS file server and, if possible, correct the cause of
User response: None. the errors and restart the operation.

in the copy group and activate the changed policy.

ANR1106W An incorrect destination storage pool
storage pool name was specified for
storing a table of contents for an image. ANR1108W The server is unable to create a table of
A table of contents will not be created contents for node node name, file space
for the image. file space in storage pool storage pool name.
Explanation: While attempting to store an image Explanation: While attempting to create a table of
object, the server determined that the indicated table of contents (TOC) for the specified node and file space in
contents (TOC) destination storage pool was invalid. the indicated TOC destination pool, a failure occurred.
The indicated storage pool is used because it is
specified as the copy group TOC destination of the System action: The operation continues because TOC
assigned management class. creation is preferred, but not required. A TOC will not
be created for the stored image object.
This storage pool could be invalid for any of the
following reasons: User response: Look for previous messages giving a
specific reason for the failure. Take corrective action as
v The storage pool is not defined appropriate.
v The storage pool is not a primary storage pool
v The storage pool has a data format other than ANR1109W Command: A table of contents was
NATIVE or NONBLOCK requested, but there is no table of
System action: The operation continues because TOC contents destination storage pool
creation is preferred, but not required. A TOC will not specified. The table of contents will not
be created for the stored image object. be created, but the operation continues.
User response: This message usually indicates a Explanation: While preparing to create a table of
configuration problem with either the storage pool or contents (TOC), the server determined that the TOC
the policy. Ensure that the TOC destination storage destination storage pool is not specified in the backup
pool has appropriate attributes, including data format. copy group for the assigned management class.
Check the copy group of the assigned management System action: The operation continues because TOC
class. If the TOC destination is incorrect, either assign a creation is preferred, but not required. A TOC will not
new management class, or change the TOC destination be created.
in the copy group and activate the changed policy.
User response: This message indicates a configuration
problem with the policy. Either assign a new
ANR1107E An incorrect destination storage pool management class with appropriate attributes, or
storage pool name was specified for correct the assigned management class by setting the
storage of a table of contents for an TOC destination in the backup copy group and
image object. The backup operation activating the changed policy.
fails.
Explanation: While attempting to store an image ANR1110E Command: A table of contents was
object, the server determined that the indicated table of requested, but there is no table of
contents (TOC) destination storage pool was invalid. contents destination storage pool
The indicated storage pool is used because it is specified. The table of contents can not
specified as the copy group TOC destination of the be created and the operation fails.
assigned management class.
Explanation: While preparing to create a table of
This storage pool could be invalid for any of the contents (TOC), the server determined that the TOC
following reasons: destination storage pool is not specified in the backup
v The storage pool is not defined copy group for the assigned management class.
v The storage pool is not a primary storage pool System action: The operation fails.
v The storage pool has a data format other than
NATIVE or NONBLOCK User response: This message indicates a configuration
problem with the policy. Either assign a new
System action: The operation fails. management class with appropriate attributes, or
correct the assigned management class by setting the
User response: This message usually indicates a
TOC destination in the backup copy group and
configuration problem with either the storage pool or
activating the changed policy. If a TOC is not required,
the policy. Ensure that the TOC destination storage
change the value of the TOC parameter on the
pool has appropriate attributes, including data format.
command.
Check the copy group of the assigned management
class. If the TOC destination is incorrect, either assign a
new management class, or change the TOC destination

ANR1111E Command: An incorrect message number, ANR1114E Command: No nodes or data types are
message number, was specified. eligible for a backup set operation.
Explanation: A MSGSTACKTRACE ENABLE or Explanation: None of the specified nodes or data
MSGSTACKTRACE DISABLE command has been types are eligible to be included in the backup set for
entered that specifies an invalid message number. the GENERATE BACKUPSET or DEFINE BACKUPSET
Messages must be between 3 and 8 digits. No letters command.
are allowed on message numbers.
User response: Check previous messages for problem
command.
determination information.
message number.
ANR1115W Error initiating migration for storage
pool storage pool name - lock conflict.
ANR1112W Command: No table of contents
Explanation: While trying to start migration for the
destination storage pool available for
indicated storage pool, the server needs to obtain a lock
backup set for node Node name (data
that is not available.
type data type). The table of contents
will not be created. System action: Migration stops. The server waits for
the retry period to expire and then tries the migration
Explanation: While preparing to create a table of
again.
contents (TOC), the server determined that the TOC
destination storage pool is not specified in the backup User response: Wait for the server to retry the
copy group for the assigned management class. migration.
System action: The operation continues because TOC
creation is preferred, but not required. A TOC will not ANR1116W Error initiating migration for storage
be created. pool storage pool name - sufficient
User response: This message indicates a configuration
problem with the policy. Either assign a new Explanation: While trying to start migration for the
management class with appropriate attributes, or indicated storage pool, there is not enough server
correct the assigned management class by setting the memory available.
activating the changed policy. System action: Migration stops. The server waits for
again.
ANR1113E Command: No table of contents
destination storage pool available for User response: If necessary, make more memory
backup set for node Node name (data available to the server.
type data type). The backup set will not
be generated. ANR1117W Error initiating migration for storage
Explanation: While preparing to create a table of pool storage pool name - internal server
contents (TOC), the server determined that the TOC error detected.
destination storage pool is not specified in the backup Explanation: While trying to start migration for the
copy group for the assigned management class. indicated storage pool, the server encounters an
System action: The operation fails. internal error.
User response: This message indicates a configuration System action: Migration stops. The server waits for
problem with the policy. Either assign a new the retry period to expire and then tries the migration
management class with appropriate attributes, or again.
correct the assigned management class by setting the User response: Contact your service representative.
activating the changed policy. If a TOC is not required,
change the value of the TOC parameter on the ANR1118I Command: Table of contents successfully
command. generated for node Node name, backup
set backup set name.
Explanation: You requested a table of contents to be
generated for the specified backup set and data type.
The table of contents was successfully generated.


ANR1123E Migration is ended for volume volume
name. Excessive read errors were
ANR1119W Command: Table of contents already encountered.
exists for node Node name, backup set
backup set name (data type data type). The
volume, read errors occurred that prevent the migration
table of contents will not be created.
from continuing.
Explanation: You requested a table of contents to be
System action: Migration of the volume stops. If other
generated for the specified backup set and data type,
migration processes are running, these processes will
but the table of contents already exists.
continue migration.
System action: The server will not generate a table of
contents for this backup set and data type.
read errors.
User response: If the specified backup set name and
data type are not correct, re-issue the command with
the correct parameters.
name. Excessive write errors were
encountered.
ANR1120W Migration is ended for volume volume
name. The process is canceled.
volume, write errors occurred that prevent the
Explanation: During migration for the indicated migration from continuing.
volume, the process performing the migration has been
canceled.
System action: The migration process stops. If other continue migration.
continue migration.
write errors.
ANR1121E Migration is ended for volume volume name. Data transfer is interrupted.
name - storage. Media is inaccessible.
Explanation: During migration for the indicated volume a data transfer operation was interrupted and
volume a required volume cannot be mounted. could not be continued.
System action: Migration of the volume stops. If other System action: Migration of the volume stops. If other
migration processes are running, these processes will migration processes are running, these processes will
continue migration. continue migration.
User response: One possible cause for this failure is User response: If possible, determine and correct the
that the access state for the target volume or storage cause of the interruption.
pool for this operation is not set to READWRITE.
Check the access state for the requested output volume
and storage pool and ensure they are set to
name. There is insufficient space in
ACCESS=READWRITE.
subordinate storage pools.
name. An insufficient number of mount
volume because there is not enough space on the next
points are available for removable
storage pool, or the next storage pool is not defined.
media.
volume the server could not allocate sufficient mount
continue migration.
points for the volumes required.
User response: Ensure that the next storage pool is
defined, and make more space available in the next
storage pool. Use the UPDATE STGPOOL command to
continue migration.
change the next storage pool to one with more space.
available.


continue migration.
name. - The server is unable to move
files to subordinate storage pools User response: Wait for the server to try the migration
because the files are too large. again. If the error persists, it might indicate a shortage
of server memory.
volume because a file size is larger than allowed on the ANR1132E Migration is ended for volume volume
next storage pool. name. Sufficient memory is not
available.
migration processes are running, these processes will Explanation: During migration for the indicated
continue migration. volume, there is not enough server memory available.
User response: Use the UPDATE STGPOOL command System action: Migration stops.
change the next storage pool target. User response: If necessary, make more memory

name. Sufficient recovery log space is ANR1133E Migration is ended for volume volume
not available. name. An internal server error is
detected.
volume, the server runs out of recovery log space. Explanation: During migration for the indicated
volume, the server encounters an internal error.
System action: Migration stops.
User response: If necessary, make more server migration processes are running, these processes will
recovery log space available. continue migration.
name. Sufficient database space is not
available. ANR1134E Migration is ended for storage pool
storage pool name. There is an insufficient
Explanation: During migration for the indicated number of mount points available for
volume pool, the server runs out of database space. removable media.
System action: Migration stops. Explanation: During migration for the indicated
storage pool the server could not allocate sufficient
mount points in the next storage pool.
System action: Migration stops. The server waits for
again.
name. There is a lock conflict.
available.
volume, the server needs to obtain a lock that is not
available.
name. The transaction is ended.
continue migration. Explanation: During migration for the indicated
volume, the server detected an error while attempting
User response: Wait for the server to try the migration
to commit a transaction.
again.
continue migration.
name. A thread resource is not available.
volume, the server cannot start a thread for the
transaction.
migration process.

ANR1136W Operation process process ID completed - ANR1140I Move data process started for volume
There is no data to process for the volume name (process ID process ID).
differential backup of NAS node node
Explanation: As a result of a MOVE DATA command,
name, file space file space.
a process begins to move data from the volume shown.
Explanation: The NAS file server reported zero bytes
System action: The server moves all data from the
stored at the conclusion of an NDMP backup of the
volume.
specified file space. The command ends without
updating the server's database. User response: None.
ANR1141I Move data process ended for volume
volume name.
Explanation: The MOVE DATA command for the
volume shown completes.
object excluded by size in destination
storage pool and all successor pools. System action: None.
Explanation: During the indicated operation, the size User response: None.
of a file sent from the client node is larger than that
allowed in the destination storage pool. No successor
storage pools can accept the large file. ANR1142I Moving data for collocation cluster
cluster number of total clusters on volume
System action: The indicated process ends. volume name.
User response: Increase the maximum file size for one Explanation: As a result of a MOVE DATA command,
or more of the storage pools in the storage hierarchy to data moves from the volume indicated to new volumes;
accommodate the file. An authorized administrator can the message shows the total number of clusters (data
increase the MAXSIZE parameter by issuing the objects) on the volume and the current cluster being
UPDATE STGPOOL command. processed.
ANR1139E The command name command failed
because some data was missing. User response: None.
Explanation: An attempt to gather database statistics

from the database manager failed. This failure can ANR1143W Move data process terminated for
occur if either of these conditions is met: volume volume name - process canceled.
v The buffer pool monitor switch Explanation: During move data processing for the
(DFT_MON_BUFPOOL) has been set to 'OFF.' The indicated volume, the process performing the move
buffer pool monitor switch controls the collection of data was canceled. It is possible that the server may
database statistics. issue this message more than once while the server is
v The file systems or drives are in a remote network. ending this process.
There might be a network problem causing the System action: The server ends the MOVE DATA
server fail to collect the statistics of those volumes. command.
System action: The command fails, and the server User response: None.
User response: Take one of the following actions, and ANR1144W Move data process terminated for
then try running the QUERY DBSPACE command volume volume name - storage media
again: inaccessible.
v Stop and restart the server.
Explanation: During move data processing for the
v Set the buffer pool monitor switch to 'ON' using this indicated volume, a required volume cannot be
DB2 command: 'db2 update dbm cfg using mounted.
DFT_MON_BUFPOOL ON'.
System action: The server ends the MOVE DATA
v If you cannot obtain drive or file system statistics by
command.
running operating system commands, fix the
problem, then try running the command again. User response: None.

ANR1145W Move data process terminated for ANR1149W Move data process terminated for
volume volume name - insufficient volume volume name - insufficient space
number of mount points available for in target storage pool.
removable media.
Explanation: During move data processing for the indicated volume, the server cannot move the data
indicated volume, the server could not allocate from the volume, because there is not enough space on
sufficient mount points for the volumes required. the destination storage pool to hold it or the access for
the storage pool is either unavailable or readonly.
command. System action: The server ends the MOVE DATA
command.
available. User response: Make more space available in the next
storage pool, or specify a storage pool with more space,
and reissue the MOVE DATA command.
ANR1146W Move data process terminated for
volume volume name - excessive read
errors encountered. ANR1150W Move data process terminated for
volume volume name - unable to move
file to target storage pool due to
indicated volume, read errors occurred that prevented
exclusion by size.
the move from continuing.
indicated volume, the server cannot move the data
command.
from the volume because a file size is larger than
User response: If possible, correct the cause of the allowed on the next storage pool.
read errors and then reissue the MOVE DATA
System action: The server ends the MOVE DATA or
command.
MOVE NODEDATA command.
User response: Use the UPDATE STGPOOL command
volume volume name - excessive write
change the next storage pool target, and then reissue
errors encountered.
the MOVE DATA or MOVE NODEDATA command.
indicated volume, write errors occurred that prevented
the move from continuing.
volume volume name - sufficient recovery
System action: The server ends the MOVE DATA log space is not available.
command.
User response: If possible, correct the cause of the indicated volume, the server runs out of recovery log
write errors and then reissue the MOVE DATA space.
command.
command.
volume volume name - data transfer
interrupted.
indicated volume a data transfer operation was
volume volume name - sufficient database
interrupted and could not be continued.
space is not available.
command.
indicated volume, the server runs out of database
User response: If possible, determine and correct the space.
cause of the interruption.
command.

ANR1153W Move data process terminated for ANR1157I Removable volume volume name is
volume volume name - lock conflict. required for move process.
Explanation: During move data processing, the server Explanation: During move data or move node data
was unable to obtain the volume specified because a processing, the server determines that the indicated
lock was not available or a restartable restore is active removable volume is required in order to complete
for data on the volume and has it locked. . processing.
System action: The server ends the MOVE DATA System action: The server attempts to mount the
command. removable volume.
User response: Check for restartable restores by User response: Respond to any mount request for the
issuing the QUERY RESTORE command. If the volume indicated volume.
specified contains any data from the node and filespace
identifed by the QUERY RESTORE command, the
ANR1160W Transaction was aborted for volume
MOVE DATA command will fail. The restartable
volume name.
restores must complete or be cancelled before the
MOVE DATA command can succeed. Explanation: An error was detected during transaction
commit. This message should be preceded by other
If the volume does not contain data from the node and
filespace identified by the QUERY RESTORE command,
failed transaction.
the reissue the MOVE DATA command.
fails.
volume volume name - thread resource User response: Check for additional messages and
not available. eliminate the condition that caused the failed
indicated volume, the server cannot start a thread for
the migration process.
ANR1161W The move process is skipping a
damaged file on volume volume name:
command.
Node node name, Type file type, File space
User response: Reissue the MOVE DATA command. If filespace name, File name file name.
the error persists, it may indicate a shortage of server
Explanation: During the move process, a file is
memory.
encountered that was previously found to be damaged.
If this file is part of an aggregate, the entire aggregate
ANR1155W Move data process terminated for was previously marked damaged, possibly because an
volume volume name - sufficient memory error was detected for some other file within the
is not available. aggregate.
Explanation: During move data processing for the System action: The damaged file is not moved.
indicated volume, there is not enough server memory
User response: Perform the following actions:
available.
v Audit the indicated volume with FIX=NO to verify
System action: The server ends the MOVE DATA that the file is damaged. The audit will reset the file
command. status if the file is found to be undamaged during
User response: If necessary, make more memory the audit. If the file is part of an aggregate, the audit
available to the server, and then reissue the MOVE will reset the aggregate status if the entire aggregate
DATA command. is found to be undamaged.
v If this volume is in a primary storage pool that has
previously been backed up to a copy storage pool,
attempt to restore damaged files by using the
volume volume name - internal server
RESTORE STGPOOL command.
error detected.
ANR1162W Space reclamation skipping damaged
indicated volume, the server encounters an internal
file on volume volume name: Node node
error.
name, Type file type, File space filespace
System action: The server ends the MOVE DATA name, File name file name.
command.
Explanation: During reclamation, a file is encountered
User response: Contact your service representative. that was previously found to be damaged. If this file is

part of an aggregate, the entire aggregate was output volumes until the volume being moved or
previously marked damaged, possibly because an reclaimed is empty. It might take more than one
integrity error was detected for some other file within attempt to totally empty the volume.
the aggregate.
System action: The damaged file is not moved. ANR1165E Error detected for file in storage pool
storage pool name: Node node name, Type
User response: Audit the indicated volume with
file type, File space filespace name, fsId
FIX=NO to verify that the file is damaged. The audit
filespace id, File name file name.
will reset the file status if the file is found to be
undamaged during the audit. If the file is part of an Explanation: The server has detected an error for the
aggregate, the audit will reset the aggregate status if indicated file.
the entire aggregate is found to be undamaged. If this
System action: The file will be marked damaged in
volume is in a primary storage pool that has previously
the server database, and will not be accessed for future
been backed up to a copy storage pool, attempt to
operations. If this file is part of an aggregate, the entire
restore damaged files by using the RESTORE
aggregate will be marked damaged. If a usable copy of
STGPOOL command.
the file exists in another storage pool, that copy may be
accessed for future operations involving the file.
ANR1163W Offsite volume volume name still
User response: If the indicated storage pool is a
contains files which could not be
primary pool, and a usable copy of the file exists in a
moved.
copy storage pool, you can recreate the file in the
Explanation: During processing of a MOVE DATA primary pool using the RESTORE STGPOOL command.
command or reclamation, the server determined that If the indicated storage pool is a copy storage pool, it is
the indicated offsite volume contained one or more files possible that the primary copy of the file is usable, but
that could not be moved. One or more files could not was not accessed because the access mode for the
be copied from the other available volumes. primary storage pool or volume is unavailable. If this is
the case, the primary copy of the file may be made
The server might not move some files if the storage
accessible by changing the access mode of the primary
pool is collocated and the volume being moved or
pool or volume.
reclaimed contains files that require different output
volumes. The server will skip these files and no
messages are issued identifying the skipped files. The ANR1166E Move Data for offsite volume cannot
files are skipped to honor the collocation attribute of copy damaged file in storage pool
the storage pool. storage pool name: Node node name, Type
file type, File space filespace name, fsId
If the files in the storage pool are deduplicated, they
filespace id, File name file name.
could be skipped due to the unavailability of an on-site
copy. This can occur if the file has been logically Explanation: A move data process for an offsite
deleted from all other storage pools due to either policy volume cannot locate an undamaged copy of the
retention settings, or explicit deletion, but must remain specified file in any storage pool accessible by the
in the offsite storage pool due to deduplication server. If this file is part of an aggregate, the process
dependencies. could not locate an undamaged copy of the aggregate
to which the file belongs.
System action: The file will skipped and will not be
User response: Check for messages that indicate why
moved from the offsite volume.
files could not be moved. To complete the move
operation, you have several options: User response: The indicated storage pool is a
v Bring the volume back on-site and reissue a MOVE primary pool that contains a damaged copy of the file.
DATA command to reclaim the volume. If the The only usable copy of the file may now only reside
storage pool is deduplicated and all primary storage on the offsite volume that was involved in the move
pool volumes are available, this is the recommended data process. If you bring this volume back onsite, you
solution. can recreate the file in the primary pool by using the
RESTORE STGPOOL command. After the restore, you
v Make the primary volumes available and reissue a
can reissue the MOVE DATA command.
MOVE DATA command to reclaim the volume.
v Delete the files by using the DELETE VOLUME
command. ANR1167E Space reclamation for offsite volume
volume name cannot copy damaged file in
If the server is skipping files to honor the collocation storage pool storage pool name: Node node
attribute of the storage pool, run the MOVE DATA name, Type file type, File space filespace
command, or wait until reclamation runs again. In name,fsId filespace id , File name file name.
either case, the server will move files to the appropriate Explanation: A reclamation process of offsite volumes

cannot locate an undamaged copy of the specified file

ANR1170E Out of Space in target copy storage
in any storage pool accessible by the server. If this file
pool: copy storage pool name.
is part of an aggregate, the process could not locate an
undamaged copy of the aggregate to which the file Explanation: During reclamation, or move data
belongs. processing of a volume that is offsite, there was no
volume available in the specified target copy storage
System action: The file is skipped and will not be
pool.
moved from the offsite volume.
System action: The operation is terminated.
User response: The indicated storage pool is a
primary pool that contains a damaged copy of the file. User response: Define volumes to the copy storage
The only usable copy of the file may now only reside pool or raise the MAXSCRATCH value.
on an offsite volume that was involved in the
reclamation process, but was not totally reclaimed. If
ANR1171W Unable to move files associated with
you bring this volume back onsite, you can recreate the
node node name, filespace filespace name
file in the primary pool by using the RESTORE
fsId filespace id on volume volume name
STGPOOL command.
due to restore in progress.
Explanation: During movement of data (migration,
ANR1168W Migration skipping damaged file on
reclamation, move data) from a sequential volume, one
volume volume name: Node node name,
or more files were encountered that were locked by a
Type file type, File space filespace name,
restore operation.
fsId filespace id, File name file name.
System action: The files are not moved, but are
Explanation: During migration, a file is encountered
skipped.
that was previously found to be damaged. If this file is
part of an aggregate, the entire aggregate was User response: Use the QUERY RESTORE
previously marked damaged, possibly because an FORMAT=DETAILED command to determine if the
integrity error was detected for some other file within restore operation is active or is in restartable state. A
the aggregate. restartable restore operation will keep the files locked
from movement until the RESTOREINTERVAL is
System action: The damaged file will not be moved.
reached. QUERY OPTION will display this interval.
User response: Audit the indicated volume with You may wish to lower the RESTOREINTERVAL to
FIX=NO to verify that the file is damaged. The audit cause a restartable restore operation to be removed and
will reset the file status if the file is found to be free up the locked files. The RESTOREINTERVAL is a
undamaged during the audit. If the file is part of an server option. If you received this message due to a
aggregate, the audit will reset the aggregate status if MOVE DATA operation, reissue the MOVE DATA
the entire aggregate is found to be undamaged. If this command after the restore operation has completed in
volume is in a primary storage pool that has previously order to move any remaining files.
been backed up to a copy storage pool, you can also
attempt to restore damaged files by using the
ANR1172E Move Data for offsite volume cannot
RESTORE STGPOOL command.
copy file in storage pool storage pool
name: Node node name, Type file type, File
ANR1169W Lock conflict on movement of offsite space filespace name, fsId filespace id, File
file - file is skipped. name file name.
Explanation: During migration, reclamation, or move Explanation: A move data process for an offsite
data processing of a volume that is offsite, a copy of volume cannot locate a copy of the specified file in any
the file that resides in a primary disk storage pool is storage pool accessible by the server. If this file is part
locked by another process. of an aggregate, the process could not locate copy of
the aggregate to which the file belongs on an accessible
System action: The file is skipped and the process will
volume.
try to find another copy of the file in a copy storage
pool. If another copy cannot be used, the move System action: The file will skipped and will not be
operation on the volume may be incomplete. moved from the offsite volume.
User response: If a move operation was incomplete, User response: The indicated storage pool is a
try repeating the operation. primary pool that should contain a primary copy of the
file. Perhaps the volume on which that file resides is on
a destroyed volume. The only usable copy of the file
may now only reside on the offsite volume that was
involved in the move data process. If you bring this
volume back onsite, you can recreate the file in the
primary pool by using the RESTORE STGPOOL

command. After the restore, you can reissue the MOVE v Try using the MOVE DATA command again.
DATA command. v Use the RESTORE VOLUME command to restore
files marked damaged.
ANR1173E Space reclamation for offsite volume(s)
cannot copy file in storage pool storage ANR1176I Moving data for collocation set set
pool name: Node node name, Type file type, number of total sets on volume volume
File space filespace name, fsId filespace id, name.
File name file name.
Explanation: As a result of a move operations, such as
Explanation: A reclamation process of offsite volumes MOVE DATA, MOVE NODEDATA, migration, or
cannot locate a copy of the specified file in any storage reclamation, the server is moving data from the volume
pool accessible by the server. If this file is part of an indicated to new volumes. This message shows the
aggregate, the process could not locate a copy of the total sets of data on the volume to be processed.
aggregate to which the file belongs on an accessible Depending upon the collocation setting of the
volume. destination storage pool, a set can be file spaces that
System action: The file is skipped and will not be belong to the same collocation group, file spaces for a
moved from the offsite volume. node, or a single filespace.
User response: The indicated storage pool is a System action: None.

primary pool that should contain a copy of the file. User response: None.
Perhaps the volume on which that file resides is on a
destroyed volume. The only usable copy of the file may
now only reside on an offsite volume that was involved ANR1178I Copying active files from primary
in the reclamation process, but was not totally storage pool primary pool name to active
reclaimed. If you bring this volume back onsite, you data pool active data pool name started as
can recreate the file in the primary pool by using the process process ID.
RESTORE STGPOOL command. Explanation: A process has been started to copy active
data from a primary storage pool to the indicated
ANR1174W One or more cached files were not active data.
deleted on volume volume name. System action: For every noncached, active file in the
Explanation: The MOVE DATA command could not primary pool, a copy is made in the active data pool, if
delete one or more cached files on the disk volume a copy of that file does not already exist.
shown. Migration was probably running at the same User response: None.
time, creating cached files while the MOVE DATA
command was trying to delete them.
ANR1179I Preview of copying active files from
System action: The MOVE DATA command ran to primary storage pool primary pool name to
completion. active data pool active data pool name
User response: If you want the remaining cached files started as process process ID.
removed from the disk volume, reissue the MOVE Explanation: A preview process has been started to
DATA command. copy active data from a primary storage pool to the
indicated active data pool.
ANR1175W Volume volume name contains files which System action: Preview information about the COPY
could not be reclaimed. ACTIVEDATA operation is collected and displayed, but
Explanation: After reclamation of the indicated files are not copied.
volume, it still contains one or more files that could not User response: None.
be reclaimed. These files were skipped because of read
errors, or because the files are marked damaged.
ANR1181E Diagnostic(ID): Data storage transaction
System action: The volume is marked unavailable so transaction ID was aborted.
it will not be chosen again for reclamation.
Explanation: A database transaction failed because of
User response: an error that was detected during data storage
v Use the UPDATE VOLUME command to set the processing. This message should be preceded by other
volume access to readonly. messages that give additional information about the
v Try using the MOVE DATA command to manually failed transaction.
reclaim the volume. System action: The server operation that encountered
v If files still exist on the volume, audit the volume this error during data storage processing fails.
using AUDIT VOLUME FIX=YES.


ANR1185I Copy active data process process ID
terminated for storage pool storage pool
transaction.
name - process canceled.
Explanation: While copying active data from the
indicated primary storage pool, a process performing
required for a restore request from
the operation has been canceled.
session session id.
System action: If other copy active data processes are
Explanation: A restore request will need a removable
executing for the named storage pool, these processes
volume. This message is issued as soon as the server
continue.
determines that the volume will be needed. A mount
request will be made when the volume is actually User response: None.
needed for processing. When the first pass
determination of needed volumes is complete, message
ANR1186I Restore of node nodename, file system file
ANR1183I will be issued. However, it is possible that
system, started as process process ID by
additional volumes will be needed later, as indicated in
administrator administrator. A full image
the explanation for message ANR1183I. This message is
for this file system will be restored to
not issued for DISK device class volumes nor is it
destination destination.
issued for FILE device class volumes.
Explanation: The administrator initiates a restore of
System action: The server continues processing.
the node's file system. The restore will be performed
User response: Respond to any mount request for the using a full image of this file system. The file system
indicated volume. will be restored to the indicated destination.
ANR1183I Initial determination of removable
volumes required for a restore request
from session session id is complete.
Additional volumes may still be ANR1189I Removable volume volume name is
required. required for copying active data.
Explanation: The first pass determination of needed Explanation: During processing of a COPY
volumes is complete for the indicated restore session. It ACTIVEDATA command, the server determines that a
is possible that additional volumes will be needed as removable volume is required.
individual objects are restored. This can happen for a
variety of reasons. Examples of such reasons include: 1. System action: Unless this is a preview process, the
An object spanning from one volume to another, where server attempts to mount the removable volume.
the second volume is not needed for any other objects User response: Respond to any mount request for the
during this restore session. 2. An object is found to be indicated volume.
damaged and a copy storage pool volume is needed to
complete the restore. 3. A volume is unavailable and a
copy storage pool volume is needed to complete the ANR1199I Removable volume volume name is
restore. required for audit process.
System action: The server continues processing. Explanation: During audit volume processing for the
indicated volume, the server determines that a
User response: Respond to any mount request for any removable volume is required in order to complete
additional volumes. processing.
System action: The server attempts to mount the
ANR1184I Copy active data process process ID removable volume.
ended for storage pool storage pool name.
User response: Respond to any mount request for the
Explanation: A COPY ACTIVEDATA process for the indicated volume.
named primary storage pool has ended.
System action: None. ANR1210I Backup of primary storage pool primary
User response: None. pool name to copy storage pool copy pool
name started as process process ID.
Explanation: A process has been started to back up a
primary storage pool to the indicated copy storage
pool.
System action: For every noncached file in the

primary pool, a backup copy is made in the copy pool,

ANR1215I The backup preview of the primary pool
if a copy of that file does not already exist.
name primary storage pool to the copy
User response: None. pool name copy storage pool is complete.
Number of files backed up: number of
backed up files. Number of bytes backed
ANR1211I Backup preview of primary storage pool up: number of backed up bytes. Number of
primary pool name to copy storage pool deduplicated bytes backed up: number of
copy pool name started as process process backed up dedup bytes.
ID.
Explanation: Backup preview processing for the
Explanation: A preview process has been started to specified storage pool ended with the displayed results.
back up a primary storage pool to the indicated copy
storage pool. System action: None.
System action: Preview information about the backup User response: No action is required.
operation is collected and displayed, but files are not
backed up.
ANR1216E Command: Process process ID terminated -
User response: None. storage media inaccessible.
Explanation: During backup processing, a required
ANR1212I Backup process process ID ended for volume could not be mounted.
System action: The indicated backup process ends.
Explanation: A backup process for the named primary
storage pool has ended.
ANR1217E Command: Process process ID stopped -
User response: None. insufficient number of mount points
available for removable media.
ANR1213I Backup process process ID terminated for Explanation: During backup processing, the server
storage pool storage pool name - process could not allocate sufficient mount points for the
canceled. volumes required.
Explanation: During backup of the indicated primary System action: The indicated backup process ends.
storage pool, a process performing the backup has been
canceled.
available. To prevent sessions or processes from having
System action: If other backup processes are executing to wait for a mount point, increase the value of the
for the named storage pool, these processes continue. MOUNTLIMIT parameter in the device-class definition.
Set the value of the MOUNTLIMIT parameter high
User response: None. enough to allow all server processes using deduplicated
storage pools to open the number of volumes specified
ANR1214I The backup of the primary pool name by the NUMOPENVOLSALLOWED option.
primary storage pool to the copy pool
name copy storage pool is complete. ANR1218E Command: Process process ID terminated -
Number of files backed up: number of excessive read errors encountered.
backed up files. Number of bytes backed
up: number of backed up bytes. Explanation: During backup processing, read errors
Deduplicated bytes backed up: number of occur that prevent the backup from continuing.
backed up dedup bytes. Unreadable files:
number of unreadable files. Unreadable
bytes: number of unreadable bytes. User response: If possible, correct the cause of the
read errors and reissue the backup command.
Explanation: Backup processing for the specified
storage pool ended with the displayed results.
excessive write errors encountered.
User response: Examine previous messages to
Explanation: During backup processing, write errors
determine whether all backup processes ended
occur that prevent the backup from continuing.
successfully.

write errors and reissue the backup command. User response: To increase the amount of database
the database.
data transfer interrupted.
Explanation: During backup processing, a data
transfer operation was interrupted and could not be
lock conflict.
continued.
Explanation: During backup processing, the server
interruption and reissue the backup command.
User response: Reissue the backup command.
insufficient space in target storage pool ANR1225E Command: Process process ID terminated -
pool name. thread resource not available.
Explanation: During backup processing, the server Explanation: During backup processing, the server
cannot copy data to the specified copy or active-data cannot start a thread.
storage pool because not enough space is available in
the specified copy or active-data storage pool, or, the
access for the copy or active-data storage pool is either User response: Reissue the backup command. If the
unavailable or readonly. error persists, it may indicate a shortage of server
memory.
User response: Make more space available in the copy
or active-data storage pool and reissue the backup
command, or reissue the backup command and specify
another copy or active-data storage pool with more Explanation: During backup processing, not enough
space. server memory is available.
ANR1222E Command: Process process ID was
terminated because of insufficient User response: If necessary, make more memory
recovery log space. available to the server, and then reissue the backup
command.
message and halts. You cannot restart the server until ANR1227E Command: Process process ID terminated -
the recovery log size is increased. internal server error detected.
System action: The server halts. Explanation: During backup processing, the server
encounters an internal error.
the recovery log space is insufficient, monitor the System action: The indicated backup process ends.
archive log space first. If the archive log space is full or User response: Examine the server messages that were
nearly full, run a full database backup to remove issued prior to this message to determine the source of
archive logs and consider adding more disk space to the error. Issue the QUERY ACTLOG command to view
the archive log directory. If the archive log space is not the activity log and search for messages that indicate
full and the active log space is full or nearly full, the source of the error.
update the value of the ACTIVELOGSIZE option in the
dsmserv.opt file. Set the value of the ACTIVELOGSIZE
option to the new maximum size of the active log. ANR1228I Removable volume volume name is
required for storage pool backup.
ANR1223E Command: Process process ID was Explanation: During processing of a BACKUP

terminated because of insufficient STGPOOL command, the server determines that a
database space. removable volume is required.
Explanation: During backup processing, the server System action: Unless this is a preview process, the
runs out of database space. server attempts to mount the removable volume.
System action: The specified backup process ends. User response: Respond to any mount request for the
indicated volume.

System action: Preview information about the restore

ANR1229W Volume volume name is inaccessible
operation is collected and displayed, but files are not
therefore it cannot be backed up to a
restored. The restore preview includes noncached files
copy storage pool or copied to an
that reside in the specified primary storage pool and
active-data storage pool.
that meet either of the following conditions:
Explanation: During storage pool backup or the v The file is stored on a volume whose access mode is
copying of active data, the contents of a volume cannot destroyed
be backed up or copied if one of the following
v The primary file has been identified as having
conditions exists:
data-integrity errors during a previous operation
v The volume is offline.
v The volume is in use by another process.
v The volume cannot be mounted.
ANR1232I Restore of volumes in primary storage
v The access mode of the volume does not allow the
pool primary pool name started as process
operation.
process ID.
System action: The server continues backup
Explanation: A process has been started to restore one
processing, but skips the indicated volume.
or more volumes in the indicated primary storage pool.
User response: Take one of the following actions:
System action: Noncached files that reside on selected
v If the volume is offline, issue the VARY ONLINE volumes in the primary storage pool are restored.
command for the indicated volume.
v If the access mode of the volume is unavailable, issue
the UPDATE VOLUME command to change the
access mode to readwrite or readonly. If the access ANR1233I Restore preview of volumes in primary
mode of the volume is destroyed, verify with an storage pool primary pool name started as
administrator whether the access mode should be process process ID.
updated. If it should, issue the UPDATE VOLUME
command to change the access mode to readwrite or Explanation: A preview process has been started to
readonly. restore one or more volumes in the indicated primary
storage pool.
v If the volume is in use by another process, wait for
that process to complete, and then retry the BACKUP System action: Preview information about the restore
STGPOOL command or the COPY ACTIVEDATA operation is collected and displayed, but files are not
command. restored. The restore preview includes noncached files
v If the volume is not currently mountable, verify that that reside on selected volumes in the primary storage
the drive can mount the volume, and then retry the pool.
BACKUP STGPOOL command or the COPY User response: None.
ACTIVEDATA command.
ANR1234I Restore process process ID ended for

ANR1230I Restore of primary storage pool primary storage pool storage pool name.
pool name started as process process ID.
Explanation: A restore process for the named primary
Explanation: A process has been started to restore the storage pool has ended.
indicated primary storage pool.
System action: Non-cached files that reside in the
named primary storage pool are restored if either of the User response: None.
following criteria are met:
v The file is stored on a volume whose access mode is ANR1235I Restore process process ID ended for
destroyed volumes in storage pool storage pool
v The primary file has been identified as having name.
data-integrity errors during a previous operation Explanation: A restore process for volumes in the
User response: None. named primary storage pool has ended.
ANR1231I Restore preview of primary storage pool User response: None.
primary pool name started as process
process ID.
Explanation: A preview process has been started to
restore a primary storage pool.

ANR1236I Restore process process ID terminated for ANR1240I The restore of volumes in the primary
storage pool storage pool name - process pool name primary storage pool is
canceled. complete. Number of files restored:
number of restored files. Number of bytes
Explanation: During restore of the indicated primary
restored: number of restored bytes. Number
storage pool, a process performing the restore has been
of deduplicated bytes restored: number of
canceled.
restored dedup bytes. Number of
System action: If other restore processes are executing unreadable files: number of unreadable
for the named storage pool, these processes continue. files. Number of unreadable bytes:
number of unreadable bytes.
Explanation: Restore processing for volumes in the
specified storage pool ended with the displayed results.
ANR1237I Restore process process ID terminated for
volumes in storage pool storage pool name System action: None.
- process canceled.
Explanation: During restore of volumes in the determine whether all restore processes ended
indicated primary storage pool, a process performing successfully.
the restore has been canceled.
System action: If other restore processes are executing ANR1241I The restore preview of volumes in the
for the volumes, these processes continue. primary pool name primary storage pool is
complete. Number of files restored:
User response: None. number of restored files. Number of bytes
restored: number of restored bytes. Number
ANR1238I The restore of the primary pool name of deduplicated bytes restored: number of
primary storage pool is complete. restored dedup bytes.
Number of files restored: number of Explanation: Restore preview processing for volumes
restored files. Number of bytes restored: in the specified storage pool ended with the displayed
number of restored bytes. Number of results.
deduplicated bytes restored: number of
restored dedup bytes. Number of System action: None.
unreadable files: number of unreadable
User response: No action is required.
files. Number of unreadable bytes:
number of unreadable bytes.
Explanation: Restore processing for the specified
storage pool ended with the displayed results.
Explanation: During restore processing, a required
volume could not be mounted.
System action: The indicated restore process ends.
determine whether all restore processes ended
successfully. User response: Verify that the copy and primary
storage pools and volumes being accessed are available.
Check the ACCESS parameter for both of the storage
ANR1239I The restore preview of the primary pool
pools and all related volumes to ensure the ACCESS
name primary storage pool is complete.
state is not preventing access.
Number of files restored: number of
restored files. Number of bytes restored:
number of restored bytes. Number of ANR1243E Command: Process process ID terminated -
deduplicated bytes restored: number of insufficient number of mount points
restored dedup bytes. available for removable media.
Explanation: Restore preview processing for the Explanation: During restore processing, the server
specified storage pool ended with the displayed results. could not allocate sufficient mount points for the
volumes required.
available.

ANR1244E Command: Process process ID terminated - ANR1249E Command: Process process ID terminated -
excessive read errors encountered. sufficient database space is not
available.
Explanation: During restore processing, read errors
occur that prevent the restore from continuing. Explanation: During restore processing, the server
runs out of database space.
read errors and reissue the restore command. User response: If necessary, make more server
excessive write errors encountered. ANR1250E Command: Process process ID terminated -
lock conflict.
Explanation: During restore processing, write errors
occur that prevent the restore from continuing. Explanation: During restore processing, the server
write errors and reissue the restore command. User response: Reissue the restore command.
ANR1246E Command: Process process ID terminated - ANR1251E Command: Process process ID terminated -
data transfer interrupted. thread resource not available.
Explanation: During restore processing, a data transfer Explanation: During restore processing, the server
operation was interrupted and could not be continued. cannot start a thread.
System action: The indicated restore process ends. System action: The indicated restore process ends.
User response: If possible, correct the cause of the User response: Reissue the restore command. If the
interruption and reissue the restore command. error persists, it may indicate a shortage of server
memory.
insufficient space in target primary ANR1252E Command: Process process ID terminated -
storage pool. sufficient memory is not available.
Explanation: During restore processing, the server Explanation: During restore processing, there is not
cannot copy data to the target primary storage pool, enough server memory available.
because not enough space is available in the target
pool.
available to the server; and then reissue the restore
User response: Make more space available in the command.
target primary storage pool, and then reissue the
restore command.
Explanation: During restore processing, the server
encounters an internal error.
available.
Explanation: During restore processing, the server
runs out of recovery log space. User response: Contact your service representative.
required for restore processing.
Explanation: During processing of a RESTORE
STGPOOL or RESTORE VOLUME command, the server
determines that a removable volume is required.
System action: Unless this is a preview process, the
server attempts to mount the removable volume.


ANR1257W Storage pool backup skipping damaged
indicated volume.
file on volume volume name: Node node
name, Type file type, File space filespace
ANR1255W Files on volume volume name cannot be name, fsId filespace id, File name file name.
restored - access mode is "unavailable"
Explanation: During storage pool backup, a file is
or "offsite".
encountered that was previously found to be damaged.
Explanation: During processing of a RESTORE If this file is part of an aggregate, the entire aggregate
STGPOOL or RESTORE VOLUME command, files on a was previously marked damaged, possibly because an
copy storage pool volume cannot be restored because integrity error was detected for some other file within
of the volume's access mode. the aggregate.
System action: The server continues restore System action: The damaged file will not be backed
processing, but skips the indicated volume. up.
User response: If the volume is stored at an offsite User response: Audit the indicated volume with
location, bring the volume onsite. Use the UPDATE FIX=YES. The audit will verify whether or not the file
VOLUME command to change the access mode for the is damaged and perform one of the following actions:
volume and restart the restore command. v If the the file is found to be undamaged, the audit
will reset the file status. If the file is part of an
ANR1256W Volume volume name contains files that aggregate, the audit will reset the aggregate status if
could not be restored. the entire aggregate is found to be undamaged.
v If the file is found to be damaged and the file had
Explanation: During processing of a RESTORE not previously been backed up to a copy storage
STGPOOL or RESTORE VOLUME command, the server pool, the audit will delete the file.
determines that the indicated volume contains one or
more files that could not be restored. If this is a v If the file is found to be damaged and the file has
preview operation, this message indicates that a previously been backed up to a copy storage pool,
restorable backup copy cannot be found for one or the audit will report the file as damaged and you
more files on the indicated volume. If this is an actual must use the RESTORE STGPOOL command to
restore operation, this message could result if any of recover the file.
the following conditions exist for a file on the indicated
volume: ANR1258W Files on volume volume name needed for
v A restorable backup copy cannot be found for the move data cannot be accessed - access
file. mode is "unavailable", "offsite", or
v A restorable backup copy of the file exists, but is "destroyed".
located on a copy storage pool volume whose access Explanation: During a move data operation, files on a
mode is unavailable or offsite. storage pool volume cannot be copied because of the
v During restore processing, a backup copy was volume's access mode. The server cannot move data on
selected for restore processing, but was deleted or a volume that has an access mode of "unavailable",
moved before the file was actually restored. This "offsite", or "destroyed".
action could occur as a result of MOVE DATA,
System action: The server continues move data
DELETE VOLUME, AUDIT VOLUME FIX=YES, or
processing, but one or more files were not moved from
reclamation processing of a copy storage pool
the volume.
volume while the restore was in progress.
v A restorable backup copy of the file exists, but is on User response: If the specified volume can be made
a copy storage pool volume that cannot be accessed available, use the UPDATE VOLUME command to
since no drive path exists. change the access mode for the volume and reissue the
MOVE DATA or MOVE NODEDATA command.
User response: If this was an actual restore operation, ANR1259W Files on volume volume name needed for
check for messages indicating that files could not be offsite reclamation cannot be accessed -
restored because a copy storage pool volume was access mode is "unavailable" or "offsite".
unavailable or offsite. Check to see if a move data,
delete volume, audit volume, or reclamation process Explanation: During reclamation processing of an
occurred for a copy storage pool while the restore was offsite volume, files on a storage pool volume cannot
in progress. If either of these conditions existed, correct be copied because of the volume's access mode.
the situation and reissue the restore command. System action: The server continues reclamation, but
one or more files were not moved from an offsite
volume, which prevents it from being reclaimed.

User response: If the specified volume can be made

ANR1265E Salvage volume command: Processing
available, use the UPDATE VOLUME command to
terminated abnormally - error accessing
change the access mode for the volume and initiate
data storage.
reclamation again by updating the reclamation
threshold for the copy storage pool. Explanation: The server encountered an internal error
in accessing data storage while executing a salvage
volume operation.
ANR1260W Volume volume name contains one or
more damaged, primary files. System action: The operation is ended and server
Explanation: This message is issued during RESTORE
STGPOOL processing. The indicated volume contains User response: Use the QUERY ACTLOG command to
one or more primary, noncached files that have examine messages prior to this error to determine the
previously been found to be damaged. cause of the data storage failure. If you find and
resolve the error, retry the operation. If you cannot find
System action: If this is not a preview operation, the
the error, contact your service representative for
restore processing attempts to restore the damaged files
assistance in resolving the problem.
from copies located in a copy storage pool. If this is a
preview operation, no system action is taken.
ANR1266E Salvage volume command: Processing
User response: You can take the following actions:
terminated abnormally - volume not a
v Issue the QUERY CONTENT command with storage pool volume.
DAMAGED=YES to obtain a list of damaged files on
the indicated volume. Explanation: The server encountered an internal error
in accessing data storage while executing a salvage
v Audit the indicated volume with FIX=NO to verify
volume operation.The error occurred because an
that the files are damaged; the audit will reset the
attempt has been made to access a volume that was not
status of any files that are found to be undamaged
a storage pool volume.
during the audit.
v If this message was issued during a restore preview System action: The command command operation is
operation, attempt to restore the damaged files using ended and server operation continues.
the RESTORE STGPOOL command. User response: Issue the command with a valid
v Audit the indicated volume with FIX=YES to delete volume name.
the damaged files from the database.
ANR1267I Salvage volume command: Processed
ANR1263I command: Processing completed number volume(s).
successfully.
Explanation: The background process to service the command Salvage volume command inspected number
command command has completed successfully. input volumes.
System action: Processing for the command System action: Salvage processing for the command
completes. Statistics on the number and type of objects completes. Server operation continues.
message.
ANR1268I Salvage volume command: Recovered
number byte(s).
ANR1264I Command: Processing canceled before
command Salvage volume command recovered number
completion.
bytes worth of data.
System action: Salvage processing for the command
command command has been canceled with the
completes. Server operation continues.
CANCEL PROCESS command.
moved, together with the total number of bytes copied, ANR1269I Salvage volume command: Recovered
are displayed on the server console following this number file(s).
message.
User response: None. command Salvage volume command recovered number
files.


ANR1274I Salvage volume command: * File is
incomplete - it ended on volume volume
User response: None. but did not begin there.
ANR1270I Salvage volume command: File (internal file command Salvage volume command recovered a file from
identifierinternal file identifier) recovered. the volume volume. The file was not completely
contained on volume. Although the file ended on this
Explanation: The background process to service the volume, it spanned in from a different volume.
command Salvage volume command recovered a file. The
new file was given a new, system generated name System action: Salvage processing for the command
based on the internal file identifier and the name of the completes. Server operation continues.
volume from which the file was recovered. The internal
file identifier is the identifier by which the file was
known to the server before the file was deleted.
ANR1275I Salvage volume command: * File is
incomplete - it did not began or end on
volume volume.
command Salvage volume command recovered a file from
ANR1271I Salvage volume command: * number bytes the volume volume. The file was not completely
recovered from volume volume. contained on volume. It spanned in from one volume
and spanned out to a another.
command Salvage volume command recovered a file from System action: Salvage processing for the command
the volume volume. The number of bytes recovered from completes. Server operation continues.
the volume is listed.
ANR1276E Command: Process terminated - sufficient
User response: None. memory is not available.
Explanation: During salvage processing, not enough
ANR1272I Salvage volume command: * File is server memory is available.
complete - it began and ended on
System action: The salvage process ends.
volume volume.
available to the server, and then reissue the salvage
command.
the volume volume. The file was completely contained
on volume.
ANR1277E Command: Process terminated - the
default management class in the active
policy set in policy domain domain name
User response: None. does not contain an archive copy group.
Unable to continue with salvage.
ANR1273I Salvage volume command: * File is Explanation: The background process to service the
incomplete - it began on volume volume command Salvage volume command was unable to
but did not end. recover any files because the default management class
in the active policy set in policy domain does not contain
Explanation: The background process to service the an archive copy group.
the volume volume. The file was not completely System action: The salvage process ends.
contained on volume. Although the file began on this
User response: Add an archive copy group to the
volume, it spanned out to a different volume.
default management class in the active policy set of the
System action: Salvage processing for the command specified domain, and then reissue the salvage
completes. Server operation continues. command.

ANR1278I Occupancy is incorrect for storage pool ANR1283I File count is incorrect for storage pool
storage pool name. Occupancy is being storage pool name - file count is being
reset. reset.
Explanation: The server has detected incorrect Explanation: The server has detected an incorrect
occupancy information. count of the number of files within this storage pool.
System action: The server recalculates the occupancy System action: The server will correct this
value based on current storage pool information. information.
ANR1279I Occupancy is incorrect for volume name ANR1284I Move node data started as process
volume name. Occupancy is being reset. process ID.
Explanation: The server has detected incorrect Explanation: A process has been started to move data
occupancy information. by node.
System action: The server recalculates the occupancy System action: The indicated process has started.
value based on current sequential volume information.
User response: To query the progress of the process,
User response: None. use the QUERY PROCESS command. To cancel the
background process, use the CANCEL PROCESS
command. Use the process ID number to specify this
process.
Explanation: During backup processing, the server
ANR1288I Move node data process process ID
detected an error while attempting to commit a
ended for storage pool storage pool name.
transaction. This message should be preceded by other
messages that give additional information about the Explanation: A move node data process for the named
failed transaction. storage pool has ended.
System action: The indicated backup process ends. System action: None.
User response: Check for additional messages and User response: None.
transaction.
ANR1289I Move node data process process ID
terminated for the storage pool storage
ANR1281E Command: Process process ID terminated - pool name - process canceled.
Explanation: During move node data processing in
Explanation: During restore processing, the server the indicated storage pool, the process performing the
detected an error while attempting to commit a move node data has been canceled.
transaction. This message should be preceded by other
System action: If other move node data processes are
executing for the storage pool, these processes continue.
failed transaction.
ANR1290I The process of moving node data from
the storage pool name storage pool to the
transaction.
storage pool name storage pool is
complete. Number of files moved:
ANR1282I Logical occupancy is incorrect for number of moved files. Number of bytes
storage pool storage pool name. Logical moved: number of moved bytes. Number of
occupancy is being reset. deduplicated bytes moved: number of
moved dedup bytes. Number of unreadable
Explanation: The server has detected incorrect logical
files: number of unreadable files. Number
occupancy information.
of unreadable bytes: number of unreadable
System action: The server recalculates the logical bytes.
occupancy value based on current storage pool
Explanation: The process of moving node data for the
information.
specified storage pool ended with the displayed results.

User response: Examine previous messages to recommended to use a FILE storage pool as the target.
determine whether all of the move node data processes
ended successfully.
ANR1295W An attempt to set end reclamation date
for WORM volume volume name to end
ANR1293E Space-reclamation process process reclamation date failed. end reclamation
number: Fifty files in offsite storage-pool date set to SnapLock retention date.
volumes do not have copies in
Explanation: IBM Spectrum Protect computes and
accessible storage pools.
attempts to set the end reclamation date for a volume
Explanation: More files in offsite storage-pool volumes based on the RETMIN and RETVER COPYGROUP
might exist for which copies cannot be located. If this is attributes. When setting the end reclamation date for
the case, message ANR1173E is not displayed. the named volume, the Network Appliance SnapLock
file system was unable to fulfil the request. It was,
System action: The IBM Spectrum Protect server skips
however, able to set the date to the Snaplock retention
files that do not have copies. The server does not move
date, which is farther in the future than the requested
the files from offsite storage-pool volumes.
date. This is probably due to how the SnapLock NAS
User response: To view detailed information about all file server's retention date is configured.
the files that are skipped during the space-reclamation
This warning message is only issued once per volume,
process, enable trace AFUNAVAILABLE and look in the
when this condition is detected when data is first
trace log.
placed on the volume.
System action: The operation continues.
ANR1294I Process process ID skipped skipped files
files on volume volume name because of User response: Verify that the IBM Spectrum Protect
deduplicated files. COPYGROUP attributes and the retention settings of
the Network Appliance file system are consistent with
Explanation: While moving or copying files from the
your requirements for WORM volume storage.
sequential FILE volume shown to a DISK storage pool,
files that had deduplicated extents were encountered.
As a result, the files were skipped. ANR1296W Storage pool storage pool name does not
contain WORM FILE volumes.
The sequential FILE volume shown is assigned to a
storage pool that has deduplication enabled or at one Explanation: This message might be issued during the
time had deduplication enabled. Some of the files on definition or updating of a storage pool, or during
the volume have deduplicated extents and can not be BACKUP or RESTORE STGPOOL commands, or in
moved or copied to the DISK storage pool. other such situations when it is determined that data
on WORM volumes might be moved to other media. It
System action: The server moves or copies all files
names a storage pool that does not contain WORM
from the volume that do not have deduplicated extents.
FILE volumes.
Those files that do have deduplicated extents are
skipped. When it is issued during the DEFINE and UPDATE
STGPOOL commands, it indicates that the storage pool
User response: If attempting a MOVE
being defined or updated is being configured with
DATA/NODEDATA to move the files with
WORM FILE volumes (Reclamationtype is SnapLock),
deduplicated extents to the DISK storage pool, one
but other storage pools being specified on the storage
must first perform a MOVE DATA/NODEDATA to
pool definition (for example, the Next or Reclaim or
another sequential storage pool that does not have
Copy storage pool parameters) do not contain WORM
deduplication enabled. This move will restore the
FILE volumes (Reclamationtype is Threshold). Such
deduplicated files to their complete state in the target
configurations might cause data on those WORM FILE
storage pool. Once all deduplicated data has been
volumes to be moved to a storage pool that does not
moved, perform a MOVE DATA or MOVE
support WORM FILE volumes.
NODEDATA to the DISK storage pool from the target
storage pool. It is recommended to use a FILE storage For other situations, this message might be issued
pool as the target. when there will be a movement of data from a storage
pool with WORM FILE volumes (Reclamationtype is
If attempting a RESTORE STGPOOL/VOLUME to copy
SnapLock) to a storage pool that does not have WORM
the files with deduplicated extents, one must first
FILE volumes (Reclamationtype is Threshold).
perform a RESTORE STGPOOL/VOLUME to another
sequential storage pool that does not have The server allows this type of movement, but the
deduplication enabled. This will restore the customer needs to be aware that if data is moved from
deduplicated files to their complete state in the target a WORM FILE volume to another type of media, the
storage pool. Once all deduplicated data has been data may no longer be protected from inadvertent or
restored, perform a MOVE DATA/NODEDATA to the malicious deletion. In addition, if this data is on
DISK storage pool from the target storage pool. It is WORM volumes to meet data retention and protection

requirements for certain legal purposes and is moved User response: Try the retrieve again, using a regular
to other media, the data might no longer meet those or full retrieve instead of a partial object retrieve.
requirements.
System action: The command continues. ANR1305I Disk volume volume name varied online.
User response: Verify that the storage pools being Explanation: The specified volume has been varied
used meet your requirements for data protection and online as the result of a VARY ONLINE command.
retention.
ANR1297E Storage pools with
RECLAMATIONTYPE=SNAPLOCK can
only be defined on servers with archive ANR1306I Disk volume volume name varied online
data retention protection enabled. (read-only).
Explanation: Defining storage pools with Explanation: The specified volume has been varied
RECLAMATION=SNAPLOCK is only supported on a online in read-only mode as the result of a VARY
server with archive data protection enabled. ONLINE command.
System action: The define storage pool command System action: None.
fails.
User response: Define the storage pool with
RECLAMATIONTYPE=THRESHOLD on this server. Or
else enable archive data retention protection on this ANR1307I Disk volume volume name varied offline.
server, and try the command again. Explanation: The specified volume has been varied
offline as the result of a VARY OFFLINE command.
ANR1298W The server encountered an error in System action: None.
attempting to delete an object in a
Centera storage device. The Centera User response: None.
representation of the name is Centera
object string. The server was keeping ANR1308W Incorrect bytes read bytes read for offset
track of the object in volume id volume offset.
id. The return code received was return
code. Explanation: The read operation fails. Check previous
messages in the activity log for a message that shows
Explanation: The server failed to delete an object in a an I/O error or warnings.
Centera storage device after server records concerning
the object were deleted. The object is no longer System action: None.
accessible through the server. The object continues to User response: None.
occupy space in the Centera storage device. The return
code that is returned is either from the server interface
to Centera services, or it can be directly from the ANR1309W Shred value zero for storage pool storage
Centera device. pool name may render deleted data non
shreddable.
System action: The server continues operation, and
the object is logically deleted within the server, but Explanation: This message is issued during the define
continues to occupy space in the Centera device. or update of a storage pool when a SHRED value of
zero has been found with a storage pool in the storage
User response: The server can continue to operate in pool hierachy.
spite of this error. Centera service can be required if the
volume of unpurged objects becomes a problem. The server allows this type of operation, but the
administrator needs to be aware that if data is stored or
moved to the affected storage pool, the data cannot be
ANR1299E The server encountered an invalid shredded after deletion.
storage format while attempting a
partial object retrieve for object seg_id. When it is issued during the DEFINE command, it
indicates that the storage pool definition is being
Explanation: A partial object retrieve was attempted configured with a non zero SHRED value, however
on a file that was stored in a format that does not other storage pools being specified on the definition
support partial object retrieves. (for example, the Next or Reclaim or Copy storage pool
System action: The transaction ends and the retrieve parameters) have a SHRED value of zero.
request fails. When issued during the UPDATE command, it
indicates the specified storage pool may be altering the

SHRED value from non zero to zero or that the

ANR1314E Vary-on failed for disk volume volume
specified Copy, Next or Reclaim storage pool has a
name - reduced capacity (was count
SHRED value zero. Such configurations may result in
blocks, now count blocks.
data to become non shreddable if data from the
primary random access storage pool is moved to one of Explanation: A VARY ONLINE command has been
the storage pools with a zero SHRED value. issued for the disk volume specified, but the size of the
volume does not match the size expected.
System action: The command continues.
System action: The volume is not varied online.
User response: Verify that the storage pools being
used meet your requirements for data protection. User response: Restore the volume or otherwise
correct the disk volume size, and reissue the command.
name - insufficient memory. ANR1315E Vary-on failed for disk volume volume
name - invalid label block.
Explanation: A VARY ONLINE command has been
issued for the disk volume specified, but sufficient Explanation: A VARY ONLINE command has been
memory is not available to process the command. issued for the disk volume specified, but the label block
of the volume is invalid or cannot be read.
User response: Reissue the command at a later time,
or make more memory available to the server. User response: Restore or reformat the disk volume.
ANR1311E Vary-on failed for disk volume volume ANR1316E Vary-on failed for disk volume volume
name - unable to access disk device. name - internal error detected.
Explanation: A VARY ONLINE command has been Explanation: A VARY ONLINE command has been
issued for the disk volume specified, but the server is issued for the disk volume specified, but fails due to an
unable to access the disk. internal server error.
System action: The volume is not varied online. System action: The volume is not varied online.
User response: Attempt to determine the cause of the User response: Contact your service representative.
inability to access the volume and correct the problem.
ANR1317E Command: Storage pool storage pool name
ANR1312E Vary-on failed for disk volume volume is not a shreddable pool.
name - error reading disk.
Explanation: The command indicated specifies the
Explanation: A VARY ONLINE command has been name of a storage pool which is not a shreddable pool.
issued for the disk volume specified but the server The command syntax requires that
encounters an error reading the disk. SHREDTONOSHRED=YES be specified when data is
moved from a shreddable storage pool to a non
shreddable storage pool.
User response: Attempt to determine the cause of the
read error and correct the problem.
command.
User response: Reissue the command with
SHREDTONOSHRED=YES.
name - unsupported block size (block
size).
ANR1318I The process of copying active data from
the primary pool name primary storage
issued for the disk volume specified, but the volume is
pool to the active data pool name active
formatted with a block size that cannot be used.
data pool is complete. Number of
System action: The volume is not varied online. copied files: number of copied files.
Number of copied bytes: number of copied
User response: Reformat the disk with a block size bytes. Number of copied deduplicated
that is an evenly divisible by 4096. bytes: number of copied dedup bytes.
Number of unreadable files: number of
unreadable files. Number of unreadable
bytes: number of unreadable bytes.
Explanation: The process of copying active data for

the specified storage pool ended with the displayed

ANR1323E Command SHRED DATA is invalid for
results.
automatic shredding mode.
Explanation: A SHRED DATA command was issued
User response: Examine previous messages to while shredding mode is set to Automatic.
determine whether all copy active data processes ended
successfully.
User response: Set the shredding mode to Manual or
wait for automatic shredding to shred the data.
ANR1319I The preview of copying active data from
the primary pool name primary storage
pool to the active data pool name active ANR1324E Process process number is already running
data pool is complete. Number of files a SHRED DATA.
copied: number of copied files. Number of
Explanation: A SHRED DATA command was issued
copied bytes: number of copied bytes.
while another SHRED DATA process is still executing.
Number of copied deduplicated bytes:
Only a single SHRED DATA process is allowed at any
number of copied dedup bytes.
time.
Explanation: The preview of copy active data
processing for the specified storage pool ended with
the displayed results. User response: Wait for the current SHRED DATA
process to finish, and issue the command again.
ANR1325W Shreddable object for node name:
type=type, file space=filespace name,
ANR1320W Vary-on not possible for disk volume object=object name skipped.
volume name - access state is
Explanation: The object for node name, identified by
"unavailable".
type, file space and object name was found in a
Explanation: A VARY ONLINE command has been shreddable storage pool and is skipped, however the
issued for the disk volume specified, but the status of EXPORT continues.
the volume is unavailable.
System action: The server process continues exporting
System action: The volume is not varied online. and will skip all shreddable objects.
User response: If necessary, use the UPDATE User response: Specify the
VOLUME command to change the status of the ALLOWSHREDDABLE=YES parameter when exporting
volume, and reissue the command. objects from a shreddable storage pool. Using this
option forces EXPORT to process all objects, including
objects found in shreddable storage pools.
ANR1321W Vary-on not possible for disk volume
volume name - access state is "destroyed".
ANR1326I Shredding process complete after
shredding shredded bytes bytes and
issued for the disk volume specified, but the status of
skipping skipped bytes bytes.
the volume is destroyed.
Explanation: The shredding process has completed.
The amount of data successfully shredded and the
User response: If necessary, use the UPDATE amount of data that was skipped are reported.
VOLUME command to change the status of the
System action: Server operation continues. If any data
volume, and reissue the command.
was skipped, the server will attempt to shred it the
next time shredding runs.
ANR1322W The shredding mode is already shredding
mode.
Explanation: A SETOPT SHREDDING command was
ANR1327I Automatic shredding stopped. Total
issued to change the shredding mode, but the new
bytes shredded was shredded bytes and
mode is the same as the existing mode.
total bytes skipped was skipped bytes
System action: The shredding mode is unchanged. bytes.
User response: None. Explanation: The automatic shredding process has

ended. The amount of data successfully shredded and
skipped during automatic shredding is reported.

System action: Server operation continues. If any data

ANR1332W Shredding cancelled prior to
was skipped, the server will attempt to shred it the
completion. Total bytes shredded was
next time shredding runs.
shredded bytes and total bytes skipped
User response: None. was skipped bytes bytes.
Explanation: The shredding process was cancelled
ANR1328E The server has detected an attempt to either because the specified duration has elapsed, or
restore or retrieve a shredded object. because the CANCEL PROCESS command was used to
cancel it. The amount of data successfully shredded
Explanation: An attempt was made to retrieve or and skipped is reported.
restore an object which has already been shredded. This
can happen if your datasbase was recently restored, System action: Server operation continues. If any data
and data which existed at the time of the database was skipped or not processed, the server will attempt
backup has since been erased and shredded. to shred it the next time shredding runs.
System action: Server operation continues. User response: None.
User response: Perform an AUDIT VOLUME
operation on the volume containing the shredded data. ANR1335E command: Database database name cannot
be the target of an upgrade because it is
not empty.
ANR1329I Automatic shredding started.
Explanation: The DSMSERV INSERTDB operation
Explanation: The automatic shredding of deleted cannot insert data into the specified database because
objects is starting. the database already contains data from another server.
System action: Server operation continues. Possible causes for this error include:
User response: None. v The wrong database was specified in the
DATABASEALIAS option in the server's options file.
ANR1330E The server has detected possible v The database was formatted using the DSMSERV
corruption in an object that is being FORMAT command instead of the DSMSERV
restored or moved. The actual values for LOADFORMAT command.
the incorrect frame are: magic magic hdr System action: The DSMSERV INSERTDB command
version ver hdr length hdrLen sequence terminates.
number seqNum data length length server
ID srvId segment ID segId crc crc. User response: Verify that the correct database name
is specified in the server's options file. If the correct
Explanation: An invalid frame was detected. This database is specified, and the database is not in use by
might indicate corruption within the object that is being a different IBM Spectrum Protect server, then drop the
restored or moved. database and recreate it using the DSMSERV
System action: The object is not restored or moved. LOADFORMAT command before rerunning the
DSMSERV INSERTDB command.
User response: Retry the failing operation. If the
operation fails again, review additional information
that is available for this message: Search for ANR1336I command: Ready for connections from
"ANR1330E" in the product information the source server. Remaining time:
(http://www.ibm.com/support/knowledgecenter/ remaining time
SSEQVQ/). Explanation: The command has completed its
initialization, and is ready to begin receiving database
ANR1331E Invalid frame detected. Expected magic information from the source server.
magic sequence number seqNum server id System action: The command will continue to wait
servId segment id segId. until the source server establishes a server-to-server
Explanation: This message indicates the expected connection and begins sending database information, or
values when an invalid frame is detected. until the specified amount of time has passed.
System action: None. User response: Initiate a session from the source
server.
User response: If contacting support, please provide
the information from this message.

Spectrum Protect API that is not an IBM product,

ANR1337I A trigger type trigger has been removed.
contact the vendor for the application to have this
Explanation: The DSMSERV INSERTDB command corrected.
encountered a database backup trigger, a database
space trigger, or recovery log space trigger, and
ANR1340I Scratch volume volume name is now
removed it as part of the database upgrade process.
defined in storage pool storage pool name.
System action: The trigger is deleted from the
Explanation: The scratch volume specified has been
upgraded database.
added to the storage pool shown.
ANR1338E One or more constraint violations were
detected. Examine log file log file name
for details. ANR1341I Scratch volume volume name has been
deleted from storage pool storage pool
Explanation: The DSMSERV INSERTDB command
name.
encountered one or more instances where data being
inserted into the database violated a constraint or was Explanation: The scratch volume specified is no
otherwise invalid. Information about the error, along longer in use and has been removed from the indicated
with the data that caused the error, was logged in the storage pool.
specified log file.
System action: The offending row was not inserted
into the database. Instead, the contents of the row were User response: None.
written to the specified log file along with additional
information about the specific error. ANR1342I Scratch volume volume name is now
User response: Because some data was not inserted pending - volume will be deleted from
into the database, the database is in an inconsistent storage pool storage pool name after the
state. The server should not be started until the reuse delay period for this storage pool
problem is corrected. has elapsed.
Contact your service representative for assistance in Explanation: All files have been deleted from the
correcting the problem. You may be directed to indicated scratch volume. The volume will not be
examine the log file, and in some cases, correct the removed from the storage pool until the reuse delay
erroneous data and insert it into the database. time period for the indicated storage pool has elapsed.
However, due to the sensitive nature of the database, If the storage pool does not have a reuse tdelay
you should never attempt to do this unless directed to specified, the indicated volume was emptied after it
do so by your service representative. had been requested by another process. It will be in the
full or filling state if the process places more data on
the tape, or it will be removed from the storage pool
ANR1339W Session session id underestimated a size after it is no longer required.
allocation request - additional spaceMB
more space was allocated to allow the System action: None.
operation to continue. User response: None.
Explanation: This session required additional space
megabytes of space in order for the operation to ANR1343I Unable to delete scratch volume volume
continue. The client is responsible for accurately name.
reporting the size of a file to be stored to the server.
The size reported by the client is used to reserve space Explanation: A scratch volume cannot be deleted from
in the DISK storage pool to store this file. If this size is the server and returned to scratch at this time because
underestimated, the server may not be able to allocate all the locks have not be released. A number of retries
the additional space needed for this file to continue have been attempted.
with this operation. System action: None
System action: None, the operation was able to User response: The scratch volume will be
continue. automatically deleted when the server is restarted. Or,
User response: The installed version of the client for you may manually delete this volume later, using the
this node should be evaluated. In most cases, if a client DELETE VOLUME command.
has underestimated the sizes of files reported to the
server, this may have been corrected in a newer version
of the client. If this is an application using the IBM

ANR1344I Volume volume name cannot be reused. ANR1347E Export/import command: Processing
Remove the volume from server storage. terminated abnormally - error accessing
data storage.
Explanation: A volume that was full and is now
empty cannot be reused by the server because the Explanation: The server encountered an internal error
volume is on WORM media. in accessing data storage while executing an import or
export operation.
System action: The volume is in a state where the
access mode is READONLY, the status is FULL, and the System action: The export or import operation is
percent utilized is 0. The server considers the volume ended and server operation continues.
to be empty when calculating the occupancy and
utilization fields for the volume.
User response: The volume remains in the library and cause of the data storage failure. If you find and
in the storage pool, with the attributes described in the resolve the error, retry the export or import operation.
System Action section. If this is not a volume in a If you cannot find the error, contact your service
RECLAMATIONTYPE=SNAPLOCK storage pool, you representative for assistance in resolving the problem.
may remove the volume by performing these steps:
1. Remove the volume from the storage pool by ANR1348I Export Operation information for number
issuing the DELETE VOLUME command. objects has been deleted.
2. Remove the volume from the library by issuing the
Explanation: A background server process deleted
CHECKOUT LIBVOLUME command.
export operation information for number files from the
If this is a volume in a server database. This process started during
RECLAMATIONTYPE=SNAPLOCK storage pool, you initialization to remove any unneeded export
cannot remove the volume. Rather, allow IBM information.
Spectrum Protect reclamation processing to delete the
System action: The actual backup or archive objects
volume.
were not deleted. Only information used to sort these
objects during the previous export operation was
ANR1345I Volume volume name cannot be reused deleted.
by other applications and will remain in
the storage pool.
Explanation: A WORM (write-once-read-many)
ANR1349E Error code during deletion of export
volume that has been written by the server cannot be
operation information for number
used by other applications. This volume was not full
objects.
and has been emptied due to expiration, delete
commands, or transaction failure. Explanation: A background server process
encountered an internal error after deleting export
System action: The volume remains in the storage
operation information for number files from the server
pool to be reused by IBM Spectrum Protect, unless it is
database. This process started during initialization to
manually deleted. The remaining space on the volume
remove any sorting information which is left over from
will be used in the normal course of server operation.
previous export operations.
User response: If the volume is no longer to be used,
System action: The backup or archive objects were not
manually delete it from the storage pool.
deleted. Only the information used to sort these objects
during the previous export operation was deleted. The
ANR1346E Export/import command: Preview background process was terminated before all sorting
processing terminated abnormally - information was deleted. The system will not perform
error accessing data storage. further export processing of file data until this problem
is resolved.
in accessing data storage while executing an import or User response: Examine the server messages issued
export preview operation. prior to this message to determine the source of the
activity log and search for messages, then restart the
server. If the error cannot be isolated and resolved,
User response: Use the QUERY ACTLOG command to contact your service representative.
cause of the data storage failure. If you find and
resolve the error, retry the export or import operation.
If you cannot find the error, contact your service
representative for assistance in resolving the problem.

System action: The command runs and server

ANR1350E Command: Invalid time range specified.
FROM: fromdate fromtime TO: todate
totime. User response: None.
Explanation: A command was issued that specifies an
invalid FROM and TO date or time range. This error ANR1355I command name: An export operation
can occur when the FROM date or time is not before already exists with the
the TO date or time. EXPORTIDentifier export ID.
System action: The server does not process the Explanation: The export command fails.
command.
User response: Reissue the command with a valid operations continue.
date or time range.
User response: Reenter the export command with an
unused export identifier.
suspended with status status.
ANR1356I Command: Cannot restart the EXPORT
Explanation: The background process to service the operation with export identifier exportId.
command command was suspended with a SUSPEND The operation is currently active.
command.
Explanation: The server cannot restart the export
System action: Processing for the command command operation specified in the RESTART EXPORT command
stops. Statistics on the number and type of objects because the export operation is currently running as an
moved, together with the total number of bytes copied, active process.
message. System action: Server operations continue.
User response: None. User response: Only suspended Export operations

may be restarted using RESTART EXPORT command.
Issue the QUERY EXPORT command to identify the
ANR1352I Command started by administrator name as current state the EXPORT operation.
process process ID has been suspended.
Explanation: The background process to service the ANR1357I command name: The EXPORTIDentifier
command command by administrator administrator name parameter is not supported when the
suspended processing. PREVIEWIMPORT parameter is
specified. Running as non-restartable
System action: The specified process suspends, and
export.
server operations continue.
Explanation: The EXPORTIDentifier parameter is
ignored while the command continues.
System action: The command runs and server
ANR1353I Command: Cannot cancel the EXPORT
operation with export identifier exportId.
The operation is currently active. User response: None.
Explanation: The server cannot cancel the export
operation specified in the CANCEL EXPORT command ANR1358I Export Identifier: Export Id
because it is currently running as an active process.
Explanation: This is a restartable export operation that
System action: Server operations continue. can be referenced by the displayed EXPORTIDentifier
parameter.
User response: Only suspended EXPORT operations
may be cancelled by issuing the CANCEL EXPORT System action: Server operations continue
command. Issue the QUERY EXPORT command to
identify the current state of the EXPORT operation. User response: None.
ANR1354I command name: The EXPORTIDentifier ANR1359I Suspend in progress

parameter is not supported when the Explanation: The server-to-server export operation has
FILEDATA parameter is set to NONE. been suspended and will stop when resources have
Running as non-restartable export. been freed for the background process. This message
Explanation: The EXPORTIDentifier parameter is may be displayed in response to a QUERY PROCESS
ignored while the command continues. command for an export operation.


ANR1366W Input volume volume name contains an
invalid identifier.
ANR1360I Output volume volume name opened
(sequence number sequence number). Explanation: During a sequential data operation, the
volume specified has been mounted but contains an
Explanation: During a sequential data operation, the
invalid identifier.
volume specified has been opened for output as the
volume number shown. System action: The volume is not used.
System action: None. User response: Make sure you specified the correct
volume for the operation. If a LOADDB operation was
being performed on MVS, the command syntax may be
specified by using a ddname or by specifying a device
ANR1361I Output volume volume name closed. class name. You must use the same method that was
used when the database was originally dumped. If you
Explanation: During a sequential data operation, the did not, this error message will be displayed. Try
volume specified has been closed because the export or loading the data base by using the other method of
dump is complete. syntax (ddname).
User response: None. ANR1367W Import volume volume name was written
by a different export process.
ANR1362I Output volume volume name closed Explanation: During an IMPORT operation, the
(full). volume specified has been mounted but contains an
export identifier that does not match the import
Explanation: During a sequential data operation, the process.
volume specified has been closed because the volume is
full. System action: The volume is not used.
System action: None. User response: Supply a volume created by the proper
export process.
ANR1368W Input volume volume name contains

ANR1363I Input volume volume name opened sequence number sequence number;
(sequence number sequence number). volume sequence number sequence
Explanation: Because of a sequential data operation, number is required.
the volume specified has been opened for input as the Explanation: During a sequential data operation, the
volume number shown. volume specified has been mounted but contains the
System action: None. wrong volume sequence number.
User response: None. System action: The volume is not used.

User response: Supply the volume with the proper
ANR1364I Input volume volume name closed. sequence number. The volume history file can help you
choose the correct volume.
volume specified has been closed because the operation
is complete. ANR1369E Input volume volume name contains
Version 1 dump.
User response: None. volume specified has been mounted but appears to
contain a version 1 database dump.
ANR1365I Volume volume name closed (end System action: The volume is not used. The operation
reached). is terminated.
Explanation: During a sequential data operation, the User response: Make sure you specified the correct
volume specified has been closed because processing of volume for the operation. A Version 1 database dump
the volume is complete. may not be loaded into a Version 2 server. The Version
System action: None. 1 database dump must only be loaded into a Version 1
server.

ANR1370E Insufficient number of mount points ANR1375I Command: Cannot suspend the export
available in device class device class name. operation export Id because the current
state is not valid.
Explanation: During IMPORT or EXPORT processing,
the server cannot allocate sufficient mount points for Explanation: This message is returned in response to a
the device class specified. The device class associated SUSPEND EXPORT command which specified an
with the EXPORT or IMPORT drive only has a mount export operation that is not currently suspendible. The
limit of one. The operation needs to read or write file export operation may not be running, or it may be in
data from or to the same device class because file data the process of being suspended.
is being imported or exported.
System action: The specified command fails, and
System action: The IMPORT or EXPORT command is server operation continues.
User response: Make more mount points available.
ANR1376I Analyst authority has been revoked for
ANR1371I Command: The export operation with administrator administrator name.
export identifier Export Id has been
deleted.
encountered an administrator with analyst authority,
Explanation: The suspended server-to-server export and revoked the authority as part of the database
operation has been deleted. This operation may no upgrade process.
longer be restarted. This message is be displayed in
System action: The analyst authority is revoked.
response to a CANCEL EXPORT command.
ANR1377I Analyst authority has been revoked for
administrator id administrator id.
ANR1372I Suspend export request accepted for
export process with export Identifier
encountered an administrator with analyst authority,
Export Id ( process process ID).
and revoked the authority as part of the database
Explanation: A SUSPEND EXPORT command has upgrade process.
been entered for the specified server-to-server export
System action: The analyst authority is revoked.
process. Some processes will experience a delay before
they suspend. This delay may be lengthy for processes User response: None.
that involve remote data movement.
System action: None. ANR1378I command: No connection was received
after session wait time minutes.
Explanation: The command waited the specified
amunt of time for the source server to connect, but no
ANR1373I Process process Id for Command has been
connection was established.
suspended on source server.
System action: The command terminates.
Explanation: The background import process has been
suspended on the source server. User response: Rerun the command. Either specify a
larger value for the SESSWAIT parameter, or establish a
System action: The specified process ends, and server
connection from the source server more quickly.
ANR1379I command: Read bytes bytes and inserted
database entries database entries in elapsed
ANR1374I Process process Id for Command has been time (read rate megabytes per hour).
canceled on source server.
Explanation: The command read the indicated
Explanation: The background import process has been number of bytes, and wrote the indicated number of
canceled on the source server. database entries.
System action: The specified process ends, and server System action: None.

ANR1380I The buffer pool monitor switch is ANR1385E The database name is either invalid or
enabled. missing in the server option file.
Explanation: The server has turned the buffer pool Explanation: While attempting to format a database,
monitor switch to 'ON'. the IBM Spectrum Protect server has found that the
database name is either invalid or missing.
System action: Server continues processing.
System action: Server format stops.
User response: Before reissuing the command to
format the database, check the following items:
ANR1381W The buffer pool monitor switch is
disabled 'OFF'. A manual update might v Ensure that the server options file has a valid name
be needed. for for IBM Spectrum Protect server database. The
database name is specified with the
Explanation: The server failed to turn the buffer pool DATABASEALIAS option. The database name is a
monitor switch to 'ON'. unique character string containing from one to eight
System action: Server continues processing. letters, numbers, or keyboard characters. The name
can contain any of the following characters: a-z, A-Z,
User response: No action is required at this time. But 0-9, @, #, and $.
a manual update might be needed before executing v Ensure that the command is using the correct options
command 'Q DBS' or 'Q DB F=D'. Refer to message file for the server. If you are using the -o option with
1139I. the command to specify a server options file, ensure
that the name and location of the file is correct.
ANR1382E The server failed with error code return
code when attempting to update a ANR1386I Beginning schema verification for the
database parameter. database insert process.
Explanation: Cannot update a database parameter Explanation: The database insert process is verifying
with the value specified in the server options file. that the database schema is correct.
System action: The server initialization fails. System action: The server will verify the correctness
User response: Examine the server messages issued of the database schema before inserting any database
prior to this message to determine the source of the records.
error. Contact your service representative for further User response: None.
ANR1383I Memory usage by the database manager ANR1387I Schema verification for the database
is limited to instance memory in MBMB. insert process has completed.
Explanation: The memory dedicated to the database Explanation: The database insert process has
manager was set successfully. successfully verified that the database schema is
System action: Server continues processing. correct.
User response: None. System action: If CHECKSCHEMA=YES was specified

then the database insert process will begin inserting
records into the database.
ANR1384E The update to set memory used by IBM
Spectrum Protect server database to User response: None.
instance memory in MBMB failed.
Explanation: Attempt to set memory dedicated to IBM ANR1388E Schema verification for the database
Spectrum Protect server database failed. insert process detected inconsistencies.
System action: Server operation continues. Explanation: Inconsistencies were detected during
database schema verification.
User response: Collect all messages prior to this one
and contact your service representative for further System action: The database insert process terminates.
assistance. User response: Contact your service representative.

ANR1389I The database insert process is ANR1393I Memory usage by the database manager
terminating because is set to AUTOMATIC.
CHECKSCHEMA=ONLY was specified.
Explanation: The memory dedicated to IBM Spectrum
Explanation: The database insert process is Protect server database was set to automatic
terminating after verifying the database schema successfully.
because the CHECKSCHEMA=ONLY parameter was
System action: Server continues processing.
specified.
System action: The database insert process terminates.
User response: Rerun the command without
ANR1394E The update to set memory used by IBM
specifying the CHECKSCHEMA=ONLY parameter.
Spectrum Protect server database to
AUTOMATIC failed.
ANR1390E Column source column name (source
Explanation: Attempt to set memory dedicated to IBM
column number) in legacy table source
Spectrum Protect server database to automatic failed.
table name is mapped to an invalid
column (target column number) in target System action: Server operation continues.
table target table name (maximum column
is table size). User response: Collect all messages prior to this one
and contact your service representative for further
Explanation: The database insert process has detected assistance.
a discrepency while verifying the data base schema. A
column in the source database table was mapped to an
invalid column in the target table. The target column ANR1395I Insertdb command: Process process number,
number is higher than the number of columns in the database insert, has completed.
target table. Explanation: The database insert process process
System action: The database insert process terminates. number has completed.
User response: Contact your service representative. System action: Database insert processing ends.
ANR1391E Column source column name (source
column number) in legacy table source ANR1396E Insertdb command: Process process number,
table name is mapped to the wrong database insert, has completed with
column target column name (target column errors.
number) in target table target table name.
Explanation: The database insert process process
Explanation: The database insert process has detected number has completed, but errors were encountered by
a discrepency while verifying the data base schema. A the process.
column in the source database table was mapped to the
wrong column in the target table. System action: Database insert processing ends.
System action: The database insert process terminates. User response: Review any messages that were issued
by the process, and take corrective action as
User response: Contact your service representative. appropriate.
ANR1392E Column target column name (target column ANR1397I Insertdb command: Found number of
number) in target table target table name is database objects database objects.
not set by upgrade, but does not allow
NULLs and has no default value. Explanation: This message indicates the total number
of database objects that were found during database
Explanation: The database insert process has detected insert processing.
a discrepency while verifying the data base schema. A
column in the target database table is not set, does not System action: Server processing continues.
have a default value and does not allow NULLs. User response: None.
System action: The database insert process terminates.
User response: Contact your service representative. ANR1398I Insertdb command: Processed number of
database objects database objects.
Explanation: This message indicates the total number
of database objects that were successfully processed
during database insert processing.


ANR1404W Scratch volume mount request denied -
User response: None. mount failed.
Explanation: A scratch volume cannot be mounted
ANR1399I Insertdb command: Failed to process because the mount request cannot be completed
number of database objects database successfully. Possible reasons include, an error in device
objects. specifications to the server or the mount request timed
out.
of database objects that were not successfully processed System action: The scratch volume is not mounted.
during database insert processing.
User response: If the device specifications (for
System action: Server processing continues. example, DEFINE DEVCLASS) are in error, correct
them and reissue the command that requested the
User response: None. volume to be mounted.
ANR1400W Mount request denied for volume ANR1405W Scratch volume mount request denied -
volume name - mount canceled. no scratch volume available.
Explanation: The volume shown cannot be mounted Explanation: A scratch volume cannot be mounted
because the mount request has been canceled. because no scratch volume is available.
System action: The volume is not mounted. System action: The scratch volume is not mounted.
ANR1401W Mount request denied for volume ANR1406E Simultaneous write operation could not
volume name - mount failed. release all the acquired mount points.
Explanation: The volume shown cannot be mounted Explanation: A simultaneous write to a primary and
because the mount request cannot be completed copy storage pools failed to release all the acquired
successfully. Possible reasons include, an error in device mount points. When a simultaneous write operation
specifications to the server or the mount request timed begins it will attempt to acquire all of the necessary
out. mount points. If a mount point cannot be acquired or
System action: The volume is not mounted. the simultaneous write operation has to wait for a
mount point, then the operation will release any mount
User response: If the device specifications (DEFINE points it has already acquired. This prevents the
DEVCLASS and so forth) are in error, correct them and simultaneous write operation from holding mount
reissue the command that requested the volume to be points and other mount requests from completing. This
mounted. message is issued if one of the previously acquired
mount points cannot be released.
ANR1402W Mount request denied for volume System action: At least one mount point acquired by
volume name - volume unavailable. simultaneous write operation is not released.
Explanation: The volume shown cannot be mounted User response: None.
because it is not available.
System action: The volume is not mounted. ANR1407W Scratch volume mount request denied -
User response: If the attempted mount occurs in a storage pool pool name has reached
library sharing environment and the library manager maxscratch limit.
was recently recycled, try again in five minutes. In this Explanation: A scratch volume cannot be mounted
case the library manager and library client need a few because the storage pool has reached the maximum
minutes to reestablish communication and synchronize scratch volume limit allowed by the MAXSCRATCH
the mounting information between the two servers. parameter.
System action: A scratch volume is not mounted.
ANR1403W Scratch volume mount request denied -
mount canceled. User response: Use the UPDATE STGPOOL poolname
MAXSCRATCH=xx command command to increase the
Explanation: A scratch volume cannot be mounted number of scratch volumes allowed in the storage pool.
because the mount request has been canceled.
System action: The scratch volume is not mounted.


ANR1408I Insertdb command: PREVIEW=YES was
specified. No data will be inserted into
the database. ANR1413W Volume volume name access mode is
"read-only".
Explanation: PREVIEW=YES was specified on the
INSERTDB command. Database data will be read and Explanation: At server startup, the status of the
checked for errors, but no data will be written into the indicated volume is read-only.
database.
ANR1414W Volume volume name access mode is
ANR1409W Volume volume name already in use - "read-only" due to previous write error.
skipped.
Explanation: At server startup, the status of the
Explanation: During an export or database backup, a indicated volume is read-only due to an unrecoverable
volume cannot be used because it is already defined in write error, or because an administrator used the
a storage pool, or has already been used by the current UPDATE VOLUME command to set the volume access
operation, or has been previously used by an export or mode to read-only.
database backup operation (as recorded in the volume
history) or is in use by another process. System action: None.
System action: The operation continues and the User response: None.
volume is skipped.
User response: Use the QUERY VOLUME command ANR1415W Volume volume name access mode is
to display the names of volumes that are defined to DESTROYED.
server storage pools. Use the QUERY VOLHISTORY Explanation: At server startup, the status of the
command to display the names of volumes that have indicated volume is DESTROYED. This status can
been used for export or database backup operations. If result because the access mode was set to DESTROYED
no volume names are displayed using the query by a storage administrator. This status can also result
commands described above, ensure that the volume because the server determined that the database
identified in this message has not been specified or records associated with this volume are damaged and
used more than once in the operation being performed. set the status of the volume to DESTROYED. If this is
the case, the server also issues an ANR1316E message.
ANR1410W Access mode for volume volume name System action: None.
now set to "unavailable".
User response: You can issue the RESTORE VOLUME
Explanation: The status of the volume shown has server command to restore the volume if a storage pool
been set to unavailable. backup is available.
User response: None. ANR1416I command: Read bytes bytes and inserted
database entries database entries in elapsed
time (read rate megabytes per hour).
ANR1411W Access mode for volume volume name Checked database objects of database objects
now set to "read-only" due to write database objects.
error.
Explanation: Because of an unrecoverable write error number of bytes, and wrote the indicated number of
on the volume shown, the status of the volume has database entries. The command has checked the
been set to read-only. integrity of the indicated number of database tables.
System action: None. System action: None.
ANR1412W Volume volume name access mode is ANR1417W Access mode for volume volume name
"unavailable". now set to "read-only" due to excessive
read error.
Explanation: At server startup, the status of the
indicated volume is unavailable. Explanation: Because of an numerous read errors on

the volume shown, the status of the volume has been

ANR1421W Read access denied for volume volume
set to read-only.
name - volume is offline.
Explanation: An attempt to access the named volume
User response: Use QUERY VOLUME for reading failed because the volume is offline.
FORMAT=DETAILED for the volume to view the
System action: The volume is not used.
access mode and number of read errors. You may want
to use the MOVE DATA command to move the User response: None.
retrievable data from this volume to another volume.
For the damaged files, use the RESTORE VOLUME
ANR1422W Read access denied for volume volume
command to restore a readable copy of the file to the
name - volume access mode="offsite".
storage pool.
Explanation: An attempt to access the named volume
for reading failed because the volume status is offsite.
ANR1418E command name: Export commands that
target another server cannot be issued System action: The volume is not used for read
from the server console. access.
Explanation: An EXPORT command that targets User response: None.
another server was issued from the server console. This
command cannot be issued from the server console
because it requires authentication of the issuing ANR1423W Scratch volume volume name is empty
administrator on the target server. but will not be deleted - volume access
mode is "offsite".
continues processing. Explanation: The named scratch volume is empty but
will not be deleted at this time because the access mode
User response: Issue the command from an is offsite.
System action: The volume is not deleted.
ANR1419E command name : FROMDATE must be User response: After bringing the volume onsite,
specified when FROMTIME is change the access mode to read-only so the volume will
specified. be deleted.
Explanation: A command that supports the

FROMDATE and FROMTIME parameters was issued ANR1424W Read access denied for volume volume
with the FROMTIME parameter specified, but without name - volume access mode="destroyed".
the FROMDATE parameter. When the FROMTIME Explanation: An attempt to access the named volume
parameter is used, the FROMDATE parameter must be for reading failed because the volume status is
specified. destroyed.
System action: The server ignores the command and System action: The volume is not used for read
continues processing. access.
User response: Reissue the command with both the User response: None.
FROMDATE and FROMTIME parameters specified.
ANR1425W Scratch volume volume name is empty

ANR1420W Read access denied for volume volume but will not be deleted - volume state is
name - volume access mode = "mountablenotinlib".
"unavailable".
Explanation: The named scratch volume is empty but
Explanation: An attempt to access the named volume will not be deleted at this time because the state of the
for reading fails because the volume status is volume is MOUNTABLENOTINLIB. Possible reasons
unavailable. include, a MOVE MEDIA command was used to check
System action: The volume is not used for read the volume out of the library and the volume was
access. subsequently checked into the library using CHECKIN
LIBVOL without first running a MOVE MEDIA
User response: None. command to update the volume state back to
MOUNTABLEINLIB state. If this should happen, the
QUERY MEDIA will display the volume to be in
MOUNTABLEINLIB state since QUERY MEDIA does
verify if the volume is actually in the library before
displaying the state of the volume.

System action: The volume is not deleted.

ANR1429E Transaction failed for Import process -
User response: The following steps may be used if the invalid file space filespace name for node
volume is to be deleted: node name was detected.
1. Run CHECKOUT LIBVOL to check the affected Explanation: During import processing, the server
volume out of the library, the REMOVE=NO option encounters an invalid file space name.
may be used to prevent actual volume movement
System action: This action usually occurs when the
2. Run MOVE MEDIA * STG=*
import is operating on a file space that is currently
WHERESTATE=MOUNTABLENOTINLIB
being deleted as a result of an administrative command
WHERESTATUS=EMPTY. When the volume is
or client action. The server ends import operation.
moved by MOVE MEDIA
WHERESTATE=MOUNTABLENOTINLIB, the User response: Use the QUERY PROCESS command
scratch empty volume is deleted to monitor and wait for any file space deletion
3. Check the volume back into the library using processes to complete, or cancel the process if you do
CHECKIN LIBVOL command not want to delete the file space. Try the import
operation again after this action has been taken.
ANR1426I All legacy FILE volumes have been

marked FULL. ANR1430W Retrieval request denied for storage
pool storage pool name - access
Explanation: As part of the conversion of the database mode="unavailable".
to IBM Spectrum Protect version 5.3, all existing
non-full volumes of devtype FILE have been marked Explanation: An attempt was made to retrieve a file
FULL to keep them from being extended. from the storage pool shown, but the access mode of
the storage pool is unavailable.
System action: All FILE volumes that were not
already FULL have been marked FULL and cannot be System action: The file is not retrieved from this
appended to. storage pool. If possible, the file is retrieved from
another storage pool.
User response: Consider changing the access mode for
the storage pool.
ANR1427E No legacy FILE volumes were marked
FULL.
ANR1431E An error occurred while writing to side
Explanation: As part of the conversion of the database A of volume volume name. An attempt
to IBM Spectrum Protect Version 5.3, all existing will be made to write to side B of this
non-full volumes of devtype FILE were attempted to be volume.
made FULL. However, a database error prevented the
conversion, and the status of these volumes remains Explanation: An error occurred while writing to side
unchanged. A of a two-sided volume.
System action: The volumes are not marked FULL. System action: No additional data will be written to
side A of this volume. Any remaining space on side A
User response: Examine the server messages issued will not be used. An attempt will be made to use the
prior to this message to determine the source of the reverse side (side B) of the volume.
activity log and search for messages. Contact your User response: None required if the side B can be
service representative for further assistance. used successfully. However, the administrator should
investigate the cause of the error and may want to
move data from this volume.
ANR1428W Shredding access denied for volume
volume name - volume is offline.
ANR1432I Updating device configuration
Explanation: An object on the indicated volume information to defined files.
cannot be shredded because the volume is offline.
Explanation: The server is updating device
System action: The object is not shredded at this time. configuration information for the files or data sets
When the volume is put back online, another attempt specified with the DEVCONFIG option in the server
will be made to shred the object. options file.
User response: Determine why the volume is offline, System action: Server operation continues.
and, if possible, place the volume back online.

proper authority to write to the file indicated and that

ANR1433I Device configuration information
there is sufficient space in the file system for the file.
successfully written to file name.
On MVS, make sure that the data set has been allocated
Explanation: Device configuration information was and that the server has authority to write to the data
successfully written to the file specified. set. After the problem has been corrected, use the
BACKUP DEVCONFIG command to write device
configuration information to the file.
ANR1437E No device configuration files could be
ANR1434W No files have been identified for used.
automatically storing device
Explanation: The server attempts to read device
configuration information.
configuration information from defined files and cannot
Explanation: The server is unable to automatically open any of the files.
update device configuration file. No files were
System action: The operation is ended.
identified using the DEVCONFIG option in the server
options file. User response: Examine error messages that may have
been displayed prior to this message and correct any
problems, if possible. Ensure that the defined device
User response: If you would like to have the server configuration files have been created. If you can start
automatically record device configuration information the server, you can create the files by using the
to assist in server recovery, use the DEVCONFIG BACKUP DEVCONFIG command. If you cannot start
option in the server options file to specify where device the server, you will need to create a device
configuration information should be written. If you configuration file by editing the file and adding the
update the options file, halt and then restart the server appropriate DEFINE commands for the device class,
so the changes can take effect. drive, and library definitions. Make sure that the server
has proper authority to read from the defined device
configuration files.
ANR1435E Server could not write device
configuration information to devconfig
file name. ANR1438W Skipping device configuration file:
devconfig file name.
Explanation: While attempting to write device
configuration information to defined files, the server Explanation: While attempting to read device
cannot write to the file name specified. configuration information from a defined device
configuration file, the server encounters problems in
System action: The server cannot write device processing the definitions included in the file.
configuration information to the specified file.
System action: The specified file is skipped, and the
User response: Examine error messages that may have next one specified in the server options file will be
been displayed prior to this message and correct any used.
problems, if possible. Make sure that the server has
proper authority to write to the file indicated and that User response: Examine error messages that may have
there is sufficient space in the file system for the file. been displayed prior to this message to understand
On MVS, make sure that the data set has been allocated why the file could not be used. When you can start the
and that the server has authority to write to the data server again, you can refresh this file by using the
set. After the problem has been corrected, use the BACKUP DEVCONFIG command.
BACKUP DEVCONFIG command to write device
configuration information to the file.
ANR1439E Allocate prohibited - transaction failed.
Explanation: While attempting to preallocate storage
ANR1436E Device configuration file devconfig file
on a storage pool, the server detected that the
name cannot be opened.
transaction for this operation has previously failed. This
Explanation: While attempting to write device error may occur when a large file is selected for backup
configuration information to device configuration files, and the client did not properly estimate the file size.
the server cannot open the file name specified. There may not be enough space in the storage pool for
the file.
System action: The server does not write device
configuration information to the file specified. System action: An internal error is reported by the
server and the operation being performed is ended.
User response: Examine error messages that may have
been displayed prior to this message and correct any User response: Examine error messages that may have
problems, if possible. Make sure that the server has been displayed prior to this message for more
information.

ANR1440I All drives in use. Process process number ANR1444E No device configuration file is defined.
being preempted by higher priority
Explanation: No device configuration file is defined.
operation.
Check DEVCONFIG option in server options file.
Explanation: When a high priority operation
System action: The specified configuration parameter
attempted to find an available drive, all the drives were
is skipped.
in use. To make a drive available for this operation, the
indicated process is being cancelled by the system. User response: Add the DEVCONFIG option to the
server options file, specifying a valid file or data set
System action: The lower priority process is cancelled
name to use for the device configuration file.
to make a mount point (drive) available.
User response: When a drive again becomes available,
ANR1445I Insertdb command: Throughput was
restart the process that was cancelled. If the process
megabytes per hour megabytes per hour.
was a migration or reclamation process, it will be
automatically restarted when needed. If this message Explanation: This message indicates the total
appears frequently, you may want to increase the throughput (megabytes/hour) during database insert
number of drives available. See the MOUNTLIMIT processing.
parameter on the UPDATE DEVCLASS command.
ANR1441I Volume volume name is in use. Process User response: None.

process number being preempted by
higher priority operation. ANR1446I RUNSTATS: Table updating statistics
Explanation: When a high priority operation started.
attempted to use a volume, it was in use. To make a Explanation: This message indicates the update
volume available for this operation, the indicated statistics for all tables started.
process is being cancelled by the system.
System action: The lower priority process is cancelled
to the volume available. User response: None.
User response: Restart the process that was cancelled.

It will wait until the higher priority process is finished ANR1447W command name: The server is not able to
with the volume. If the cancelled process was a begin a new thread to execute the
migration or reclamation process, it will be command on line line number in parallel.
automatically restarted when needed. The command will run serially.
Explanation: This message is issued during a RUN
ANR1442E Invalid storage pool for store operation: command to indicate that thread resources are not
storage pool. available to run the command in parallel. The
command will be executed serially.
Explanation: The storage pool selected for a store
operation (for example, backup or archive) was not a System action: The SCRIPT continues.
NATIVE or NONBLOCK data format storage pool. This User response: Increase the resources available to the
may be caused by an incorrect management class being server or reduce the number of parallel commands or
assigned to an object. scripts that are running on the server at any one time.
User response: Ensure that the copy group destination ANR1448I command name: Beginning serial SCRIPT
storage pool of the assigned management class has the command execution on line line number.
appropriate NATIVE or NONBLOCK data format. Explanation: This message is issued during a RUN
command (VERBOSE=YES) to indicate that a SERIAL
ANR1443W Process process ID terminated from command was encountered and following SCRIPT
session session id. A potential commands will be executed serially.
drive-contention deadlock was detected. System action: The SCRIPT command continues.
Explanation: See message. User response: See the output of the commands
User response: No action is required. following the SERIAL command to determine their
results.

User response: Reenter the command specifying a

ANR1449I command name: Beginning parallel
different command name.
SCRIPT command execution on line line
number.
ANR1456I command name: Command script command
script name updated.
command (VERBOSE=YES) to indicate that a
PARALLEL command was encountered and following Explanation: The script name specified in an UPDATE
SCRIPT commands will be executed in parallel. SCRIPT command was successfully updated.
System action: The SCRIPT command continues. System action: None
User response: See the output of the commands User response: None
following the PARALLEL command to determine their
results.
script name deleted.
ANR1450E command name: Invalid command script
name: command script name. Explanation: The script name specified in a DELETE
COMMAND command was successfully deleted.
Explanation: An invalid script name was specified for
a DEFINE, UPDATE, or DELETE SCRIPT command. System action: None
System action: The operation fails. User response: None

valid command name. ANR1458I command name: Line line number was
deleted from command script command
script name.
ANR1452E command name: Invalid line number: line
number. Explanation: The specified line number was deleted
from the command script as a result of a DELETE
Explanation: An invalid line number was specified for SCRIPT command.
a DEFINE, UPDATE, or DELETE SCRIPT command.
System action: None
User response: None
valid line number.
ANR1459E command name: Command script command
script name, line line number does not
ANR1453E command name: Command script command exist.
script name already exists.
Explanation: The line in command script name
Explanation: The script name specified in a DEFINE specified in a UPDATE, or DELETE SCRIPT command
SCRIPT command already exists. does not exist.
System action: The operation fails. System action: The operation fails.
User response: Reenter the command specifying a User response: Reenter the command specifying a
different command name. different line number.
ANR1454I command name: Command script command ANR1460I command name: Command script command
script name defined. script name copied to new command script
name.
Explanation: The script name specified in a DEFINE
SCRIPT command was successfully defined. Explanation: The specified command script was
copied to a new script with the COPY SCRIPT
System action: None
command.
User response: None
System action: None
User response: None
script name does not exist.
Explanation: The script name specified in a DEFINE,
UPDATE, or DELETE SCRIPT command does not exist.

ANR1461I command name: Executing command ANR1466I command name: Command script command
script command script name. script name, Line line number : command
line.
Explanation: The specified command script is being
executed as a result of a RUN command. Explanation: The specified line for the command
script is being executed. The contects of the line being
System action: None
executed are displayed.
User response: None
System action: None
User response: None
script name completed successfully.
Explanation: The specified command script, started
script name, continued line is too long
with a RUN command, has successfully completed.
Explanation: The specified command script with
System action: None
continuation lines is too long to be executed.
User response: None
User response: Correct the specified command script
so that it is shorter.
script name completed in error.
Explanation: The specified command script, started
with a RUN command, encountered errors.
script name, Line line number is an
System action: Part or all of the command lines in the INVALID command : command line.
script ended in error. Command processing is
Explanation: The specified line for the command
terminated.
script is not a valid server command. This message is
User response: Examine the messages preceeding this displayed when a RUN command is executed with the
message to determine the cause of the error. Correct the PREVIEW=YES parameter specified.
command script and reissue the command.
System action: Command Preview processing fails
User response: Correct the script and reenter the RUN
command.
script name, line line number, parameter
parameter number was not specified:
command line. ANR1470I command name: Command script command
script name completed successfully
Explanation: All parameters required to execute a
(PREVIEW mode).
command script were not specified in the RUN
command. Explanation: The specified command script, started
with a RUN command, has successfully completed.
User response: Reenter the RUN command specifying
all required parameters. User response: None.
ANR1465E command name: Command script command ANR1471E command name: Command script command
script name, line line number, parameter is script name completed in error
invalid: command line. (PREVIEW mode).
Explanation: An invalid parameter was encountered Explanation: The specified command script, started
in a command script. with a RUN command, encountered errors.
System action: The command fails. System action: Part or all of the command lines in the
command script ended in error. Command processing
User response: Correct the script definition and
is terminated.
reexecute the RUN command.
User response: Examine the messages preceeding this
message to determine the cause of the error. Correct the
script and reissue the command.


script name renamed to new command User response: Add script command lines to the file
script name. or specify another file and reenter the command.
Explanation: The specified command script was
renamed with the RENAME SCRIPT command. ANR1477E command name: The OUTPUTFILE
parameter may only be specified when
FORMAT=RAW is specified.
Explanation: The OUTPUTFILE parameter was
specified in a QUERY SCRIPT command but the
ANR1473E command name: A command line cannot FORMAT parameter did not specify RAW output.
be specified when the FILE= parameter When outputting the QUERY to a file, you MUST
is used. specify RAW output format.
Explanation: The FILE= parameter was specified in System action: The command fails.
the DEFINE SCRIPT command AND a command line
User response: Reenter the command specifyingthe
was also specified for the SCRIPT. When the FILE=
proper value for the FORMAT parameter or do not
parameter is specified, a command line cannot be
specify the OUTPUTFILE parameter.
specified.
ANR1478E command name: Error writing to file file
User response: Reenter the command without the name.
command line OR the FILE= parameter.
Explanation: An error was encountered while writing
to the file specified.
ANR1474E command name: A line number cannot be
specified when the FILE= parameter is
used. User response: Examine any messages that might
appear prior to this one in the activity log to determine
Explanation: The FILE= parameter was specified in
if the error can be found. Ensure that the filesystem has
the DEFINE SCRIPT command AND a line number
sufficient space and that the server has authority to
was also specified for the SCRIPT. When the FILE=
create the file in the location specified.
parameter is specified, a line number cannot be
specified.
ANR1479I command name: Query output was
written to file file name.
User response: Reenter the command without the line
Explanation: The output from the specified query was
number OR the FILE= parameter.
successfully written to the specified file.
System action: The command completes successfully.
ANR1475E command name: File file name could not be
opened. User response: None.
Explanation: A filename was specified in a command
but the specified file could not be opened by the server. ANR1480E command name: Description text is too
long.
Explanation: The specified description text is too long
User response: Examine any messages that might
for a command that allows description text to be
specified.
if the error can be found. If the file was to exist for use
by the command, ensure that the file does exists and System action: The command fails.
that the server has proper authority to access the file. If
the file was to be created by the command, ensure that User response: Reenter the command specifying a
the filesystem has sufficient space and that the server shorter description.
has authority to create the file in the location specified.
ANR1481E command name: A command line or
ANR1476E command name: File file name contains no description must be specified.
data. Explanation: An UPDATE SCRIPT command was
Explanation: The FILE= parameter was specified in a specified with out a command line (script line) or
command but the specified file did not contain script description text.
command lines. System action: The command fails.


ANR1487I command name: Command return code is
command line or description text.
symbolic return code (return code severity).
ANR1482I command name: Found label statement label
command (VERBOSE=YES) to indicate the return code
on line line number and continuing.
that was returned from the latest command.
System action: SCRIPT processing continues.
command (VERBOSE=YES) to indicate that the target
label for a GOTO statement was found. User response: None.
System action: Command processing continues.
ANR1488E command name: Line line number
condition IF(condition) is not a valid
condition.
ANR1483I command name: Line line number
Explanation: This message is issued if an IF()
condition IF(condition) is NOT true -
statement in a SCRIPT does not specify proper
statement is skipped.
condition values.
System action: Command processing fails.
command (VERBOSE=YES) to indicate that the a return
code condition check failed and the IF(..) statement is User response: Reenter the command using valid
skipped. conditions for the IF() statement.
ANR1489E command name: Line line number is a
GOTO to a label (label name) that does
not exist or is associated with a line
ANR1484I command name: Line line number prior to line line number.
condition IF(condition) is TRUE -
Explanation: This message is issued if a GOTO
statement will be executed.
statement in a SCRIPT does not specify a label that
Explanation: This message is issued during a RUN exists in the SCRIPT, or that does exist but is associated
command (VERBOSE=YES) to indicate that the a return with a line prior to the line that contains the GOTO
code condition check succeeded and the IF(..) statement statement.
is executed.
User response: Correct the SCRIPT definition and
User response: None. reenter the RUN command.
ANR1485I command name: Ending SCRIPT with ANR1490W command name: Command script command
EXIT statement on line line number. script name does not contain any
commands.
command (VERBOSE=YES) to indicate that an EXIT Explanation: The script name specified in a RUN
statement was encountered and SCRIPT termination command does not contain any commands.
will end.
System action: The RUN operation fails (has nothing
System action: The SCRIPT command ends. to do).
User response: None. User response: Server command Scripts that contain
no commands will not execute. Add command lines to
the Script and reenter the RUN command.
ANR1486I command name: Executing line line number
GOTO label name.
ANR1491E Server command scripts cannot be
Explanation: This message is issued during a RUN started from the server console.
command (VERBOSE=YES) to indicate that a GOTO
statement was encountered and processing will skip to Explanation: A server command script RUN
the named label. command was issued from the server console. Server
command scripts cannot be started from the server
System action: SCRIPT processing continues. console because they may require a long time to
User response: None. complete and the server console should be available to
control other server functions.

System action: The server ignores the command and System action: The operation fails.
User response: Reenter the command when the script
User response: Start the server command script from is not running.
an administrative client or schedule it for execution
using the administrative command scheduler.
ANR1496I
Explanation: The ISSUE MESSAGE command with a
ANR1492E command name: A loop has been detected
severity indicator of INFORMATION was issued.
in server command script RUN
commands - command failed. System action: Server operation continues.
Explanation: A server command script DEFINE or User response: None.
UPDATE command has created a situation where one
or more scripts invoke each other in a loop that can
cause the scripts to run idefinitely. ANR1497W
System action: The command fails to update the Explanation: The ISSUE MESSAGE command with a
server command script. severity indicator of WARNING was issued.
User response: Server command scripts can invoke System action: Server operation continues.
each other, but not in a fashion that causes a potential User response: None.
loop in their execution. Specify the scripts in a manner
that does not cause them to invoke each other in a
loop. ANR1498E
Explanation: The ISSUE MESSAGE command with a
ANR1493E Command: Administrator administrator severity indicator of ERROR was issued.
name is not authorized to update or System action: Server operation continues.
delete command script command script
name. User response: None.
Explanation: The specified administrator has entered

the indicated command, but this administrator does not ANR1499S
have the proper authority necessary to update or delete Explanation: The ISSUE MESSAGE command with a
this command script. If an administrator does not have severity indicator of SEVERE was issued.
system authority, they must have previously created or
updated the script. System action: Server operation continues.
System action: The server does not process the User response: None.
command.
User response: Issue the command from a properly ANR1500I Policy domain domain name defined.
authorized administrator ID, or contact the
Explanation: In response to the DEFINE DOMAIN
administrator that created the script.
command, the policy domain domain name has been
defined in the server database.
ANR1494I command name: Command return code is
numeric return code.
command (VERBOSE=YES) to indicate the numeric
return code that was returned from the latest ANR1501I Policy domain domain name deleted.
command.
Explanation: In response to the DELETE DOMAIN
System action: SCRIPT processing continues. command, the policy domain domain name has been
deleted from the server database. All policy sets,
management classes, copy groups, and schedules
related to the domain have also been removed.
ANR1495E command name: command script name is
currently running. Define, update or
delete can not be performed. User response: None.
Explanation: An DEFINE, UPDATE or DELETE
SCRIPT was attempted on a script that is currently
running.

destination to refer to an existing storage pool, issue

ANR1502I Policy domain domain name updated.
the UPDATE COPYGROUP command. To define the
Explanation: In response to the UPDATE DOMAIN storage pool, an authorized administrator can issue the
command, the policy domain domain name has been DEFINE STGPOOL command.
updated in the server database.
System action: Server operation continues. ANR1506E Command: An incorrect storage pool
name - storage pool name was specified
for the TOC destination.
Explanation: Server processing for the command
ANR1503I Policy domain domain name copied to
command fails because the storage pool name pool name
domain target domain.
specified for the table of contents (TOC) is an invalid
Explanation: In response to the COPY DOMAIN destination storage pool type. A copy storage pool or
command, the policy domain domain name has been an active-data storage pool is not a valid copy group
copied to a new policy domain named target domain. TOC destination.
All policy sets, management classes, and copy groups
are also copied to the target domain policy domain.
User response: Reissue the command using a storage
User response: None. pool name that is not a copy pool or active-data pool.
For a list of names of defined storage pools, issue the
QUERY STGPOOL command.
ANR1504I Command: No matching domains.
Explanation: The server cannot find any policy ANR1507I Table of contents load retention is set to
domains with names that match the specification number of minutes minutes.
entered in the command command.
Explanation: The number of minutes that the
System action: Server operation continues. unreferenced table of contents (TOC) data will remain
User response: Reissue the command with a loaded in the server database has been set to the value
specification that matches an existing policy domain indicated with the SET TOCLOADRETENTION
name. Use the QUERY DOMAIN command to obtain a command.
list of the names of existing policy domains. System action: None.
ANR1505W The BACKUP copy group in
specifies a table of contents destination ANR1508E Command: An incorrect table of contents
storage pool : storage pool name that does load retention retention value was
not exist. If this pool does not exist specified.
when policy set policy set name is
Explanation: A SET TOCLOADRETENTION
activated, the creation of the table of
command has been entered that specifies an invalid
contents may fail for an image backup
table of contents (TOC) retention period.
when this management class is used for
the backup. System action: The server does not process the
command.
Explanation: This message may be returned from the
DEFINE COPYGROUP, UPDATE COPYGROUP, User response: Reissue the command with a valid
VALIDATE POLICYSET or ACTIVATE POLICYSET retention period.
command. During the indicated command processing,
the server has found a backup copy group that has a
ANR1509E Error writing option option name to file
table of contents (TOC) destination referring to an
file name.
undefined storage pool named storage pool name. If this
storage pool is undefined when the policy set is Explanation: An error was encountered while writing
activated, the creation of the TOC for an image backup an option entry to server option file.
will fail if its TOC creation binds to the management
class whose copy groups reference this pool. System action: The format command fails.
System action: Server operation continues. User response: Examine any messages that might
User response: To locate the copy groups that refer to if the error can be found. Ensure that the filesystem has
the undefined storage pool, issue the QUERY sufficient space and that the server has authority to
COPYGROUP command. To change the TOC

update the server option file then reissue the format policy domain with the definitions found in the
command. specified policy set. These values are returned to client
nodes that start a session with the server after this
command is committed to the server database.
ANR1510I Policy set set name defined in policy
domain domain name. User response: None.
Explanation: In response to the DEFINE POLICYSET
command, the policy set named set name has been ANR1515I Policy set set name validated in domain
defined in the policy domain named domain name in the domain name (ready for activation).
server database.
Explanation: This message may be displayed in
System action: Server operation continues. response to a VALIDATE POLICYSET command. The
policy set set name has been checked in the domain
domain name to see if the management class and copy
group definitions are adequate for activating the policy
ANR1511I Policy set set name deleted from policy set. This message indicates that the policy set may be
domain domain name. activated. Warning messages may be issued prior to
this message if there are discrepancies in the policy set
Explanation: In response to the DELETE POLICYSET with respect to the set that is currently active in the
command, the policy set set name has been deleted from policy domain.
the policy domain domain name in the server database.
System action: The server checks its definitions to
System action: Server operation continues. determine the policy set's qualifications for activation.
User response: None. The server does not activate the policy set.
User response: If you are satisfied with any warning
ANR1512I Policy set set name updated in policy messages that may have been issued prior to this
domain domain name. message concerning any possible discrepancies in the
policy set, issue the ACTIVATE POLICYSET command
Explanation: In response to the UPDATE POLICYSET to activate the policy set in the policy domain.
command, the policy set set name has been updated in Otherwise, correct the discrepancies prior to activating
the policy domain domain name in the server database. the policy set. Before the ACTIVATE POLICYSET
System action: Server operation continues. command is used to activate the policy set, use the
validate command to check policy set contents.

ANR1513I Policy set set name copied to set new set is not enabled for deduplication.
name in policy domain domain name.
Explanation: In response to the COPY POLICYSET name of a storage pool which does not have
command, the policy set set name has been copied to deduplication enabled. The command requires that
the policy set new set name in the policy domain named deduplication be enabled on the storage pool before the
domain name. All management classes and copy groups command can execute.
are also copied to the policy set new set name.
System action: Server operation continues. command.
User response: None. User response: Update the storage pool to allow data
deduplication by specifying the parameter
ANR1514I Policy set set name activated in policy DEDUPLICATE=YES. But only do so if you wish to
domain domain name. have duplicates of data in the storage pool removed.
Explanation: In response to the ACTIVATE

POLICYSET command, the policy set set name has been ANR1517I Insertdb command: Processed number of
activated in the policy domain domain name. All database records database records.
management class and copy group definitions in the Explanation: This message indicates the total number
policy set will be used by clients that start sessions of database records that were successfully inserted
after this command is committed. Clients that currently during database insert processing.
have sessions established with the server will use the
policy definitions in the previously active policy set for System action: Server processing continues.
the domain. User response: None.
System action: The server replaces the active
management class and copy group definitions for the

been copied to a new management class named new

ANR1518I Insertdb command: Read number of bytes
class name in policy set set name belonging to policy
bytes.
domain domain name. All copy groups defined for
Explanation: This message indicates the total number management class class name are also copied to
of bytes that were successfully read during database management class new class name.
insert processing.
ANR1524I Insertdb command: Beginning database
ANR1519I Insertdb command: Elapsed time was update phase.
elapsed time.
Explanation: The database insert process has
Explanation: This message indicates the total amount completed inserting database records, and has begun
of time that elapsed during database insert processing. making updates to the inserted records.
System action: Server processing continues. System action: Server processing continues.
ANR1520I Management class class name defined in ANR1525I command: Updated database entries of
policy domain domain name, set set name. database entries database entries in elapsed
time.
Explanation: In response to the DEFINE
MGMTCLASS command, the management class named Explanation: The command has updated the indicated
class name has been defined in the policy set set name number of database entries.
belonging to the policy domain named domain name.
ANR1526I Insertdb command: Building indices and
ANR1521I Management class class name deleted checking table integrity.
from policy domain domain name, set set
Explanation: The database insert process has begun to
name.
create indices and check the integrity of the database
Explanation: In response to a DELETE MGMTCLASS tables.
command, the management class named class name has
been deleted from the policy set set name belonging to
the policy domain domain name. All copy groups User response: None.
defined for the management class are also removed.
System action: Server operation continues. ANR1527I command: Checked database objects of
database objects database objects in elapsed
time.
Explanation: The command has checked the integrity
ANR1522I Management class class name updated in
of the indicated number of database tables.
policy domain domain name, set set name.
Explanation: In response to the UPDATE
MGMTCLASS command, the management class named User response: None.
class name has been updated in the policy domain
domain name, policy set set name.
ANR1528I RUNSTATS: Table updating statistics
System action: Server operation continues. completed in elapsed time.
User response: None. Explanation: This message indicates the update
statistics for all tables completed.
ANR1523I Management class class name copied to System action: Server processing continues.
class new class name in policy domain
domain name, set set name. User response: None.
Explanation: In response to the COPY MGMTCLASS

command, the management class named class name has

ANR1529I Process process ID skipped File state ANR1533E command: The target client version that
deduplicated extent Extent id on volume was specified is not valid. The value
Volume name. name value: value in the form V.R.M.F. (
Version, Release, Modification, and Fix
Explanation: While moving or copying deduplicated
Level ) is incorrect.
extents from a sequential FILE volume, extents were
encountered that were marked deleted or damaged. As Explanation: During pre-processing of command
a result, the extents were skipped. command, an invalid value was encountered for the
client target level. The correct client target level should
System action: The server moves or copies all extents
be formatted like 6.2.0.0
from the volume that are not marked damaged or
deleted. The damaged or deleted extents are skipped. System action: The register/update node fails.
User response: If the deduplicated extent was marked User response: Specify the correct client target level,
damaged, audit the indicated volume with FIX=NO to then reissue the command.
verify whether the file is damaged. The audit will reset
the file status if the deduplicated extent is not
ANR1534I Process process ID skipped Num Files
damaged.
deduplicated files on volume Volume
If the deduplicated extent has been marked deleted, it name because copies of the files were
is not copied to another storage pool. not found.
Explanation: The DEDUPREQUIRESBACKUP server
ANR1530I Backup copy group group name defined option is set to YES. If the value of this option is YES
in policy domain domain name, set set (the default), files within a deduplicated storage pool
name, management class class name. must be backed up to a non-deduplicated copy storage
pool before the files can be moved.
COPYGROUP command, a backup copy group named System action: The operation skips the files without
group name has been defined for the management class copies and continues the operation.
named class name in the policy set set name belonging to
User response: Ensure that all files in the primary
storage pool are backed up to a non-deduplicated copy
System action: Server operation continues. storage pool. You can also change the value of the
DEDUPREQUIRESBACKUP server option to NO.
However, doing so can result in unrecoverable data loss
if a data-integrity error occurs. As a best practice, do
ANR1531I Backup copy group group name deleted not change the default.
from policy domain domain name, set set
name, management class class name.
ANR1535I Archive copy group group name defined
Explanation: In response to the DELETE in policy domain domain name, set set
COPYGROUP command, the backup copy group name, management class class name.
named group name has been deleted from the
management class named class name in the policy set set
COPYGROUP command, an archive copy group named
name belonging to policy domain domain name.
group name has been defined for the management class
System action: Server operation continues. named class name in the policy set set name belonging to
ANR1532I Backup copy group group name updated User response: None.
in policy domain domain name, set set
ANR1536I Archive copy group group name deleted
Explanation: In response to the UPDATE from policy domain domain name, set set
COPYGROUP command, the backup copy group name, management class class name.
named group name has been updated in the
Explanation: In response to the DELETE
management class named class name in the policy set set
COPYGROUP command, the archive copy group
named group name has been deleted from the
System action: Server operation continues. management class named class name in the policy set set


ANR1541E Export command: The processing stopped.
The connection with the target server is
ANR1537I Archive copy group group name updated broken.
in policy domain domain name, set set
Explanation: The communications link with the target
server broke because of a network error or because the
Explanation: In response to the UPDATE target-server import process stopped.
COPYGROUP command, the archive copy group
System action: The export process ends.
named group name has been updated in the
management class named class name in the policy set set User response: Examine the activity log of the target
name belonging to policy domain domain name. server to determine if the import process stopped. A
network failure can also cause this message to be
displayed. If many communication error messages
User response: None. occur simultaneously, check the network for failure and
correct any problems.
ANR1538I Default management class set to class
name for policy domain domain name, set ANR1542E Import command: Preview processing
set name. stopped. The connection with the source
server is broken.
Explanation: The default management class for the
policy set set name in policy domain domain name has Explanation: The communications link with the source
been set to the management class named class name. server broke because of a network error or because the
source-server export process stopped.
System action: If this policy set is activated, clients
use this management class for backup-archive System action: The import process ends.
processing by default, or if other management classes
User response: Examine the activity log of the source
specified for binding do not exist in the policy set.
server to determine if the export process stopped. A
User response: None. network failure can also cause this message to be
displayed. If many communication error messages
occur simultaneously, check the network for failure and
ANR1539S A previous database upgrade did not correct any problems.
succeed. The server cannot start.
Explanation: A DSMSERV INSERTDB command used ANR1543E Export command: Preview processing
to upgrade from IBM Spectrum Protect V5 failed or stopped. The connection with the target
was cancelled. The result is a database that does not server is broken.
contain all of the data from the original database. The
server cannot be run with an incomplete database. Explanation: The communications link with the target
System action: The server will not start. target-server import process stopped.
User response: Rerun the DSMSERV INSERTDB System action: The export process ends.
command.
User response: Examine the activity log of the target
server to determine if the import process stopped. A
ANR1540E Import command: The processing stopped. network failure can also cause this message to be
The connection with the source server is displayed. If many communication error messages
broken. occur simultaneously, check the network for failure and
Explanation: The communications link with the source correct any problems.
source-server export process stopped. ANR1544I The DEDUPTIER3FILESIZE option
System action: The import process ends. value is temporarily updated from old
value to new value.
User response: Examine the activity log of the source
server to determine if the export process stopped. A Explanation: The value for the DEDUPTIER3FILESIZE
network failure can also cause this message to be option must be greater than or equal to the value for
displayed. If many communication error messages the DEDUPTIER2FILESIZE option. The value for the
occur simultaneously, check the network for failure and DEDUPTIER3FILESIZE option is increased to match the
correct any problems. value for the DEDUPTIER2FILESIZE option until the
server is restarted or until the value for the
DEDUPTIER3FILESIZE option is updated with the
SETOPT command.

System action: Server operations continue. required disk space and update the DBDIAGLOGSIZE
option.
User response: Use the SETOPT command to update
the value for either the DEDUPTIER2FILESIZE option
or the DEDUPTIER3FILESIZE option. Ensure that the ANR1548E The server failed to format or initialize
value for the DEDUPTIER3FILESIZE option is greater because the available space (free
than or equal to the value for the spacebytes) in the diagnostic data
DEDUPTIER2FILESIZE option when you are specifying directory path path is less than 2MB to
the values. allocate db2diag.log files;
Explanation: There was not enough free space in the
ANR1545W The diagpath ( path ) file system or disk diagnostic directory to allocate 2MB db2diag.log files.
is becoming full. Space available: space
available MB of total space MB. Percent
full: file system used ratio percent. User response: Free the required disk space in the
diagnostic directory to at least 2MB and then run the
Explanation: The file system or disk containing the
command again.
db2diag.log file is becoming full. This could cause
problems with the server if other DB2 or server
databases are in this space. ANR1549W Transaction failed for session session
platform). The next storage pool pool name
User response: Add space to the file system or free up for the primary storage pool pool name
space on the file system or disk. cannot be a target for LAN-free backup.
Explanation: The server rolled back a database update
ANR1546W Available space for the directory (path) is transaction for the specified session because the
less than 1 GB. If there is no space specified next storage pool of the specified primary
available the server can no longer storage pool cannot be a target for LAN-free backup.
function correctly.
Explanation: There is less than 1 GB of available space server operation continues.
in the file system or disk where the server database
User response: An authorized administrator can issue
files are located. When a server is initially created, with
the UPDATE STGPOOL command for the specified
the DSMSERV FORMAT utility or with the
primary storage pool to remove the specified next
configuration wizard, a server database and recovery
storage pool from the parameter NEXTSTGPOOLS.
log are created. In addition, files are created to hold
Alternatively, an authorized administrator can enable
database information used by the database manager.
LAN-free backup to the specified next storage pool.
The specified path is the location of the database
information used by the database manager. If there is
no space available, the server can no longer function ANR1550W Management class class name is NOT
correctly. defined in policy set set name but IS
defined in the ACTIVE policy set for
domain domain name: files bound to this
User response: Add space to the file system or free up management class will be REBOUND to
space on the file system or disk. the default management class if/when
this set is activated.
ANR1547W The server failed to update the Explanation: This message may be returned from the
DBDIAGLOGSIZE server option due to VALIDATE POLICYSET or ACTIVATE POLICYSET
insufficient available space. Required command. During policy set validation processing, the
space: new value megabytes; available server has found a management class named class name
space: system free space megabytes. The in the currently active policy set, but not defined in the
current value:current value megabytes. policy set being validated or activated (set name). If
policy set set name is activated, files bound to this
Explanation: There was not enough free space in the
management class in domain domain name are
filesystem or drive to create db2diag.log files.
automatically rebound to the default management class
System action: The update fails but the server in policy set set name.
continues.
User response: Because the value in the server option
User response: If you do not want files to be rebound
and logattr.chk have been updated, you must change
to the default management class, define a management
them to the current value so that they are consistent
class with the name specified in the message for the
with the value stored in the database manager. Free the
policy set. To define the proper copy group attributes,

reference the management class definition in the management class class name by using the DEFINE
ACTIVE policy set or copy the management class class COPYGROUP command.
name from the ACTIVE policy set to policy set set name
using the COPY MGMTCLAS command.
ANR1553W DEFAULT Management class class name
in policy set domain name set name does
ANR1551W BACKUP copygroup group name in not have a BACKUP copygroup: files
management class class name is NOT will not be backed up by default if this
defined in policy set set name but is set is activated.
domain domain name: files bound to this
VALIDATE POLICYSET or ACTIVATE POLICYSET
management class will no longer be
command. During policy set validation for policy set
backed up if/when set name is activated.
set name in policy domain domain name, the server has
Explanation: This message may be returned from the found that the default management class named class
VALIDATE POLICYSET or ACTIVATE POLICYSET name does not have a backup copy group. This message
command. During policy set validation processing, the warns the administrator that activation of this policy
server has found a backup copy group named group set results in client files not being backed up, unless
name for management class class name in the currently they are bound to a management class (which has a
active policy set, but the copy group is not defined for copy group) other than the default.
the management class in the policy set being validated
or activated (set name). If policy set set name is
activated, files bound to management class class name in User response: To define a backup copy group for the
domain domain name will no longer be eligible for management class, issue the DEFINE COPYGROUP
backup processing. command. To assign a different default management
class for the domain, issue the ASSIGN
DEFMGMTCLASS command. Take either action if you
User response: If you want files bound to this want files to be backed up by default.
management class to be eligible for backup processing,
define an archive copy group for management class
ANR1554W DEFAULT Management class class name
class name by using the DEFINE COPYGROUP
in policy set domain name set name does
command.
not have an ARCHIVE copygroup: files
will not be archived by default if this
ANR1552W ARCHIVE copygroup group name in set is activated.
management class class name is NOT
defined in policy set set name but is
command. During policy set validation for policy set
domain domain name: attempting to
set name in policy domain domain name, the server has
archive files specifiying this
found that the default management class named class
management class will fail if set name is
name does not have an archive copy group. This
activated.
message warns the administrator that activation of this
Explanation: This message may be returned from the policy set will result in client files not being allowed
VALIDATE POLICYSET or ACTIVATE POLICYSET archive processing unless they are bound to a
command. During policy set validation processing, the management class (which has an archive copy group)
server has found an archive copy group named group other than the default.
name for management class class name in the currently
active policy set, but the copy group is not defined for
the management class in the policy set being validated User response: To define a backup copy group for the
or activated (set name). If policy set set name is management class, issue the DEFINE COPYGROUP
activated, attempting to archive files specifiying this command. To assign a different default management
management class will fail. Existing archives bound to class for the domain, issue the ASSIGN
this management class on the IBM Spectrum Protect DEFMGMTCLASS command. Take either action if you
server will be expired based on the defmgmtclass want files to be eligible for archive processing by
values, or the archive retention grace period for the default.
policy domain, if the default management class does
not contain an archive copygroup.
ANR1555W The BACKUP copy group in
System action: Server operation continues. management class management class name
specifies a destination that does not
User response: To archive files specifying this
refer to a defined storage pool: storage
management class, define an archive copy group for
pool name. If this pool does not exist

when policy set policy set name is to migrate space-managed files to the
activated, clients will fail when using server.
this management class to backup files to
the server.
Explanation: This message may be returned from the command. During policy set validation for set name, the
VALIDATE POLICYSET or ACTIVATE POLICYSET server has found a space management migration
command. During policy set validation for set name, the destination that references an undefined storage pool
server has found a backup copy group destination that named pool name. If this storage pool is undefined
references an undefined storage pool named pool name. when the policy set is activated, space management
If this storage pool is undefined when the policy set is migration operations will fail for clients with files
activated, backup or archive operations will fail for bound to the management class that references this
clients with files bound to the management class whose pool.
copy groups reference this pool.
User response: To locate the management class that
User response: To locate the copy groups that refer to refers to the undefined storage pool, issue the QUERY
the undefined storage pool, issue the QUERY MGMTCLASS command. To change the destination to
COPYGROUP command. To change the destination to refer to an existing storage pool, issue the UPDATE
refer to an existing storage pool, issue the UPDATE MGMTCLASS command. To define the storage pool, an
COPYGROUP command. To define the storage pool, an authorized administrator can issue the DEFINE
authorized administrator can issue the DEFINE STGPOOL command.
STGPOOL command.
ANR1558E The space management migration
ANR1556W The ARCHIVE copy group in destination in management class
management class management class name management class name in policy set policy
specifies a destination that does not set name refers to copy storage pool:
refer to a defined storage pool: storage storage pool name. Copy storage pools are
pool name. If this pool does not exist not a valid migration destination.
when policy set policy set name is
activated, clients will fail when using
this management class to archive files to
command. During policy set validation for set name, the
the server.
server has found a space management migration
Explanation: This message may be returned from the destination that references a copy storage pool named
VALIDATE POLICYSET or ACTIVATE POLICYSET pool name.
System action: Server operation continues. The policy
server has found a archive copy group destination that
set is not activated.
references an undefined storage pool named pool name.
If this storage pool is undefined when the policy set is User response: To locate the management class that
activated, backup or archive operations will fail for refers to the copy storage pool, issue the QUERY
clients with files bound to the management class whose MGMTCLASS command. To change the destination to
copy groups reference this pool. refer to a non-copy storage pool, issue the UPDATE
MGMTCLASS command.
User response: To locate the copy groups that refer to
ANR1559E The copy group destination for type
the undefined storage pool, issue the QUERY
copy group type in management class
COPYGROUP command. To change the destination to
management class name in policy set policy
refer to an existing storage pool, issue the UPDATE
set name refers to copy storage pool:
COPYGROUP command. To define the storage pool, an
storage pool name. Copy storage pools are
authorized administrator can issue the DEFINE
not a valid copy group destination.
STGPOOL command.
ANR1557W The space management migration
destination in management class
server has found a copy group destination that
management class name does not refer to a
references a copy storage pool named pool name.
defined storage pool: storage pool name. If
this pool does not exist when policy set System action: Server operation continues. The policy
policy set name is activated, clients will set is not activated.
fail when using this management class
User response: To locate the management class that

refers to the copy storage pool, issue the QUERY command is not successful in changing the server
MGMTCLASS command. To change the destination to database.
refer to a non-copy storage pool, issue the UPDATE
MGMTCLASS command.
valid ARCHRETN value.
ANR1560E Command: Invalid policy domain name -

ANR1565E Command: Invalid policy set name - set
domain name.
name.
command fails because the policy domain name domain
command fails because the policy set name set name
name specified does not contain valid characters or
specified does not contain valid characters or contains
contains too many characters.
too many characters.
System action: Database changes for the command are
rolled back and server operation continues. The
command is not successful in changing the server
database.
database.
policy domain name that conforms to these name
policy set name that conforms to valid name
requirements.
requirements.
ANR1562E Command: Policy domain description

ANR1566E Command: Policy set description exceeds
exceeds length limit characters.
length limit characters.
command fails because the policy domain description
command fails because the policy set description
specified is longer than the length limit number of
specified is longer than the length limit number of
characters allowed.
characters allowed.
database.
database.
shorter policy domain description.
shorter policy set description.
ANR1563E Command: Invalid retention period for

ANR1567E Command: Invalid management class
BACKRETN parameter - retention value.
name - class name.
Explanation: Server processing for the copy group
command command fails because the value (retention
command fails because the management class name class
value) specified for the BACKRETN parameter is not
valid.
database.
database.
valid BACKRETN value.
management class name that conforms to valid name
requirements.
ANR1564E Command: Invalid retention period for
ARCHRETN parameter - retention value.
ANR1568E Command: Management class description
Explanation: Server processing for the copy group exceeds length limit characters.
value) specified for the ARCHRETN parameter is not
command fails because the management class
valid.
description specified is longer than the length limit
System action: Database changes for the command are number of characters allowed.


ANR1572E Command: Missing copy destination.
command is not successful in changing the server Explanation: Server processing for the copy group
database. command command fails because the required copy
group destination is not specified.
shorter management class description. System action: Database changes for the command are
ANR1569E Command: Invalid copy group name -
database.
group name.
User response: Reissue the command and specify the
required copy group destination (DEST).
command fails because the copy group name group name
specified does not contain valid characters or contains
too many characters. ANR1573E Command: Invalid copy type - type value.
System action: Database changes for the command are Explanation: Server processing for the copy group
rolled back and server operation continues. The command command fails because the value (type value)
command is not successful in changing the server specified for the TYPE parameter is not valid.
database.
User response: Reissue the command and specify a rolled back and server operation continues. The
copy group name that conforms to valid name command is not successful in changing the server
requirements. database.
ANR1570E Command: Invalid copy frequency - valid TYPE value.
frequency value.
Explanation: Server processing for the copy group ANR1574E Command: Invalid version count for
command command fails because the value (frequency VEREXISTS parameter - version value.
value) specified for the FREQUENCY parameter is not
valid.
command command fails because the value (version
System action: Database changes for the command are value) specified for the VEREXISTS parameter is not
rolled back and server operation continues. The valid.
database.
User response: Reissue the command and specify a command is not successful in changing the server
valid FREQUENCY value. database.
ANR1571E Command: Invalid copy destination - pool valid VEREXISTS value.
name.
Explanation: Server processing for the command ANR1575E Command: Invalid version count for
command fails because the storage pool name pool name VERDELETED parameter - version value.
specified for the copy group destination or for the table
of contents (TOC) destination does not contain valid
command command fails because the value (version
characters or contains too many characters.
value) specified for the VERDELETED parameter is not
System action: Database changes for the command are valid.
database.
User response: Reissue the command and specify a database.
storage pool name that conforms to valid name
requirements.
valid VERDELETED value.

ANR1576E Command: Invalid retention period for ANR1580E Command: Invalid copy serialization
RETEXTRA parameter - retention value. mode - serialization value.
Explanation: Server processing for the copy group Explanation: Server processing for the copy group
command command fails because the value (retention command command fails because the value (serialization
value) specified for the RETEXTRA parameter is not value) specified for the SERIALIZATION parameter is
valid. not valid.
System action: Database changes for the command are System action: Database changes for the command are
rolled back and server operation continues. The rolled back and server operation continues. The
command is not successful in changing the server command is not successful in changing the server
database. database.
User response: Reissue the command and specify a User response: Reissue the command and specify a
valid RETEXTRA value. valid SERIALIZATION value.
ANR1577E Command: Invalid retention period for ANR1581E Command: The option option is valid only
RETONLY parameter - retention value. for backup copy groups.
Explanation: Server processing for the copy group Explanation: Server processing for the archive copy
command command fails because the value (retention group command command fails because the option
value) specified for the RETONLY parameter is not specified is only valid for backup copy group
valid. definitions.
System action: Database changes for the command are System action: Database changes for the command are
rolled back and server operation continues. The rolled back and server operation continues. The
command is not successful in changing the server command is not successful in changing the server
database. database.
User response: Reissue the command and specify a User response: Reissue the command specifying valid
valid RETONLY value. archive copy group options, or specify TYPE=BACKUP
if the intent is to operate on a backup copy group.
ANR1578E Command: Invalid version count for
RETVER parameter - retention value. ANR1582E Command: The option option is valid only
for archive copy groups.
command command fails because the value (retention Explanation: Server processing for the backup copy
value) specified for the RETVER parameter is not valid. group command command fails because the option
specified is only valid for archive copy group
definitions.
command is not successful in changing the server System action: Database changes for the command are
database. rolled back and server operation continues. The
database.
valid RETVER value.
User response: Reissue the command specifying valid
backup copy group options, or specifying
ANR1579E Command: Invalid copy mode - mode
TYPE=ARCHIVE if the intent is to operate on an
value.
archive copy group.
command command fails because the value (mode value)
ANR1583E Command: Copy frequency for archive
specified for the MODE parameter is not valid.
copy groups must be CMD - frequency
System action: Database changes for the command are value is not valid.
Explanation: Server processing for the archive copy
group command command fails because a value other
database.
than CMD has been specified for the FREQUENCY
User response: Reissue the command and specify a parameter. The only value that may be specified for the
valid MODE value. archive copy group FREQUENCY parameter is CMD.

command is not successful in changing the server of defined storage pools, issue the QUERY STGPOOL
database. command.
User response: Reissue the command specifying CMD
for the FREQUENCY parameter, or omitting the ANR1587E Command: Invalid copy group
FREQUENCY parameter because the default value for destination - pool name.
FREQUENCY is CMD for archive copy groups.
command fails because the storage pool name pool name
ANR1584E Command: Copy mode for archive copy specified for the copy group destination is a copy pool,
groups must be ABSOLUTE - mode value active-data pool, or container-copy pool. A copy pool,
is not valid. active-data pool, or container-copy pool is not a valid
copy group destination.
Explanation: Server processing for the archive copy
group command command fails because a value other System action: Database changes for the command are
than ABSOLUTE has been specified for the MODE rolled back and server operation continues. The
parameter. The only value that may be specified for the command is not successful in changing the server
archive copy group MODE parameter is ABSOLUTE. database.
System action: Database changes for the command are User response: Reissue the command and specify the
rolled back and server operation continues. The name of a primary storage pool. The storage pool that
command is not successful in changing the server you specify for the copy group destination cannot be a
database. copy pool, active-data pool, or container-copy pool. For
a list of the storage pool names that are defined, issue
the QUERY STGPOOL command.
ABSOLUTE for the MODE parameter, or omitting the
MODE parameter because the default value for MODE
is ABSOLUTE for archive copy groups. ANR1588W The value of the
ACTIVEDESTINATION parameter
received from the configuration manager
ANR1585E Command: Policy set ACTIVE cannot be
specifies a storage pool storage pool name
modified.
for domain domain name that is not
Explanation: Server processing for the command defined on the managed server.
command fails because the policy set name ACTIVE is
Explanation: If the storage pool on the managed
specified. Objects in the ACTIVE policy set for a
server is undefined, the value of the
domain may only be changed through activation of
ACTIVEDESTINATION parameter for domain domain
another policy set.
name is not updated.
command is not successful in changing the server User response: Define an active-data storage pool on
database. the managed server with the same name as that on the
configuration manager.
User response: Reissue the command specifying a
policy set other than ACTIVE. To copy the ACTIVE
policy set for a policy domain to another name so that ANR1589E Error reason code updating database
commands may be used to change its contents, issue manager security plugin file name.
the COPY POLICYSET command. Then to activate the
Explanation: The server was unable to update the
changes, issue the ACTIVATE POLICYSET command.
database manager security plugin. This plugin controls
access to the database manager from the IBM Spectrum
ANR1586E Command: Invalid migration destination Protect server. The reason code is the errno from the
- pool name. fopen subroutine for the file. Some common reason
codes are:
command fails because the storage pool name pool name v 26 - The file is in use.
specified for the migration destination is a copy pool. A v 13 - Permission to write to the file is denied. On
copy pool is not a valid migration destination. Windows, this reason code can also indicate that the
file is in use.
rolled back and server operation continues. The For other reason codes, refer to your operating system
command is not successful in changing the server reference guide for errno values.
database.
User response: Reissue the command using a storage
User response: Manually copy the file from the
pool name that is not a copy pool. For a list of names

installation directory to the location identified in the

ANR1593E Command: Policy domain domain name
message, and restart the server. On AIX, you might also
still contains at least one node.
need to run the /usr/sbin/slibclean command as root
after halting the server but before copying the file. This Explanation: Server processing for the delete
procedure will unload the plugin from the kernel command command fails because the policy domain
memory. name domain name specified refers to a policy domain
that still contains at least one node. A policy domain
cannot be deleted if one or more client nodes are still
ANR1590E Command: Policy domain domain name is
assigned to the domain.
not defined.
name does not refer to a defined policy domain in the
database.
server database. If you used the REPLICATE NODE
command, this message applies to the target server. User response: To remove remaining nodes from the
policy domain, issue the REMOVE NODE command.
After all nodes are removed, issue the delete command
again.
database.
has no active policy set.
policy domain name that is defined in the server
database. For a list of the names of defined policy Explanation: Server processing for the update or
domains in the server database, issue the QUERY register node command command fails because the
DOMAIN command. policy domain name domain name specified refers to a
policy domain that does not have an active policy set
defined. Nodes cannot be assigned to policy domains
ANR1591E Command: Policy domain domain name is
that do not have an active policy set.
already defined.
name specified refers to a policy domain that is already
database.
User response: To activate a policy set for the
specified policy domain, issue the ACTIVATE
POLICYSET command. After a policy set has been
activated, client nodes may be assigned to the policy
database.
domain.
policy domain name that is not defined in the server
ANR1595E Command: Policy set set name is not
database. For a list of the names of defined policy
defined in policy domain domain name.
domains in the server database, issue the QUERY
DOMAIN command. Explanation: Server processing for the command
specified does not refer to a defined set in policy
domain domain name in the server database.
still contains at least one policy set.
Explanation: Server processing for the delete
command command fails because the policy domain
name domain name specified refers to a policy domain
database.
that still contains at least one policy set.
policy set name that is defined in the policy domain.
For a list of the names of defined policy sets in the
policy domain, issue the QUERY POLICYSET
database.
command.
User response: To delete the policy set from the policy
domain, issue the DELETE POLICYSET command.


ANR1596E Command: Policy set set name is already
database.
policy set name that is defined in the policy domain.
For a list of the names of defined policy sets in the
specified refers to a policy set that is already defined in
policy domain, issue the QUERY POLICYSET
command.
ANR1600E Command: Management class class name
is already defined in policy domain
database.
domain name, set set name.
policy set name that is not defined in the policy
command fails because the specified management class
domain. For a list of the names of defined policy sets in
name class name refers to a management class that is
the policy domain, issue the QUERY POLICYSET
already defined in policy set set name belonging to
command.
ANR1597E policy set command: Policy set set name in
domain domain name still contains at
least one management class.
database.
Explanation: The policy set command failed because the
set still contains at least one management class
management class name that is not defined in the
definition.
policy set. For a list of the names of defined
System action: The command fails and server management classes in the policy domain and policy
operation continues. set, issue the QUERY MGMTCLASS command.
User response: Remove the remaining management
classes from the policy set and reissue the command. ANR1602E Command: Backup copy group group name
is not defined in policy domain domain
name, set set name, management class
ANR1598E Command: No default management class
class name.
has been assigned for policy set set name
in domain domain name. Explanation: Server processing for the command
command fails because the backup copy group named
group name specified for management class class name
command fails because the policy set set name in policy
does not refer to a defined backup copy group in
domain domain name does not have a default
policy set set name belonging to policy domain domain
management class assigned.
name.
database.
database.
User response: To assign a default management class
in the policy set, issue the ASSIGN DEFMGMTCLASS
copy group name that is defined. For a list of the
command.
names of defined copy groups and management classes
in the policy domain or policy set, issue the QUERY
ANR1599E Command: Management class class name COPYGROUP command.
is not defined in policy domain domain
name, set set name.
ANR1603E Command: Backup copy group group name
Explanation: Server processing for the command is already defined in policy domain
command fails because the management class name class domain name, set set name, management
name specified does not refer to a defined management class class name.
class in policy set set name belonging to policy domain
domain name.
command fails because the specified backup copy group
System action: Database changes for the command are named group name refers to a copy group that is
rolled back and server operation continues. The already defined for management class (class name) in

policy set set name belonging to policy domain domain

ANR1606E Out of server LOG space in accessing
name.
policy tables.
transaction for policy information because sufficient log
space is not available on the server.
database.
System action: The policy operation is ended and
copy group that is not defined in the policy set. For a
list of the names of defined copy groups for User response: To increase the amount of log space
management classes in the policy domain and policy that is available to the server, evaluate the directories
set, issue the QUERY COPYGROUP command. and file systems that are assigned to the
and ARCHFAILOVERLOGDIRECTORY options in the
ANR1604E Command: Archive copy group group
dsmserv.opt file. An out of log space condition might
name is not defined in policy domain
occur because the ACTIVELOGDIRECTORY location is
domain name, set set name, management
full.
class class name.
command fails because the archive copy group named
location that are no longer active and cannot be
group name specified for management class class name
does not refer to a defined archive copy group in policy
set set name belonging to policy domain domain name.
System action: Database changes for the command are ARCHIVELOGDIRECTORY or
rolled back and server operation continues. The ARCHFAILOVERLOGDIRECTORY options in the
command is not successful in changing the server dsmserv.opt file and then restart the server.
database.
User response: Reissue the command specifying a ANR1607E Out of server DB space in accessing
copy group name that is defined. For a list of the policy tables.
names of defined copy groups and management classes
in the policy domain or policy set, issue the QUERY
transaction for policy information because sufficient
COPYGROUP command.
database space is not available on the server.
ANR1605E Command: Archive copy group group
name is already defined in policy
domain domain name, set set name, User response: To increase the amount of database
management class class name. space that is available to the server, issue the EXTEND
the database.
command fails because the specified archive copy group
named group name refers to a copy group that is
already defined for management class class name in ANR1608E Error fetching entry for domain domain
policy set set name belonging to policy domain domain name, set set name.
name.
Explanation: An internal server database error occurs
System action: Database changes for the command are while retrieving policy information for policy set set
rolled back and server operation continues. The name in domain domain name.
database.
copy group that is not defined in the policy set. For a
list of the names of defined copy groups for
management classes in the policy domain and policy
set, issue the QUERY COPYGROUP command.
representative.

parameter but does not contain a backup copy group.

ANR1609E Policy error: unable to find management
Policy set validation or activation fails in this case
class ID for class class name in policy set
because it would not be possible to ensure that
set name belonging to domain domain
space-managed client files are backed up prior to being
name.
migrated to the server.
Explanation: An internal server database error has
been encountered while retrieving policy information
for management class class name in policy set set name
belonging to policy domain domain name.
database.
User response: To define a backup copy group within
the management class, issue the DEFINE COPYGROUP
User response: Examine the server messages issued command. To change the MIGREQUIRESBKUP
prior to this message to determine the source of the parameter, issue the UPDATE MGMTCLASS command.
ANR1613E Command: Invalid retention initiation -
retention initiation value.
representative.
ANR1610E Internal Server error: invalid copy type
initiation value) specified for the RETINIT parameter is
copy type integer encountered in policy
not valid.
set validation.
Explanation: An internal server database error has
been encountered while validating a policy set in User response: Issue the command again and specify
response to the VALIDATE POLICYSET or ACTIVATE a valid RETINIT value.
POLICYSET command.
System action: The policy operation is ended and ANR1614E Command: Invalid number of days for
server operation continues. RETMIN parameter - days value.
User response: Examine the server messages issued Explanation: The command fails.
error. Use the QUERY ACTLOG command to view the System action: Database changes for the command are
activity log and search for messages. If the error cannot rolled back and server operation continues. The
be isolated and resolved, contact your service command is not successful in changing the server
representative. database.
User response: Issue the command again and specify
ANR1611E Command: Invalid management class a valid RETMIN value.
name - management class name.
Explanation: Server processing for the command ANR1615E Command: RETVER of NOLIMIT cannot
command fails because the specified management class be specified with RETINIT value of
name may not be used as a management class name. EVENT.
System action: Database changes for the command are Explanation: Server processing for the copy group
rolled back and server operation continues. The command command fails because the retain versions
command is not successful in changing the server value of NOLIMIT is not allowed with the retention
database. initiation value of EVENT. If this is the UPDATE copy
group command, at least one of the values might have
User response: Reissue the command and specify been defined already.
another management class name.
ANR1612E Command: Management class management command is not successful in changing the server
class name in policy set set name, domain database.
domain name specifies
MIGREQUIRESBKUP=YES, but User response: Issue the command again and specify
contains no backup copy group. a valid RETVER or RETMIN value.
Explanation: During policy set validation or activation

for policy set set name in policy domain domain name,
the server has found that the management class named
class name specifies the MIGREQUIRESBKUP=YES

ANR1616W Command: the specified RETMIN value ANR1619E The RETVER of NOLIMIT is not
(new days) will be ignored because the allowed with the RETINIT value of
RETINIT value is CREATION for EVENT for domain policy set management
domain policy set management class. class.
Explanation: Processing for the copy group command Explanation: This message can be returned from the
command detected that a retain minimum number of VALIDATE POLICYSET or ACTIVATE POLICYSET
days value was specified either with the retention command. During policy set validation processing, the
initiation value of CREATION, or the current retention server has found the the copy group in the policy has
initiation value stored for the copy group is specified an invalid combination of options. Retain
CREATION. The retain minimum number of days versions of NOLIMIT and retention initiation of
value is not used when the retention initiation value is EVENT are not allowed. The policy will not be
CREATION. The copy group will be defined or validated or activated.
updated, but the RETMIN value will not be stored.
System action: The copy group is defined or updated
User response: Update the RETVER or REINIT values
and system operation continues.
in the copy group.
User response: The copy group will be defined or
updated, but the retain minimum number of days
ANR1620E The new RETVER value (new days) is
value will not be stored. If you want to specify a
less than the value in the ACTIVE
retention initiation value of EVENT, issue the update
policy (old days) for domain policy set
command again.
management class.
Explanation: This message can be returned from the
ANR1617W Command: the new RETVER value (new
days) is less than the value previously
command. During policy set validation processing, the
stored (old days) for domain policy set
server has found that archive retention protection is
management class.
active and the copy group has a retain versions value
Explanation: Processing for the copy group command less than the value in the ACTIVE policy set. The
command detected that the new number of days to policy will not be validated or activated.
retain versions is less than the number of days
currently stored for the copy group. If archive retention
protection is active, the policy set might not activate User response: Update the RETVER value in the copy
because the retain versions value is not allowed to group.
decrease.
System action: The copy group is updated and system ANR1621E The new RETMIN value (new days) is
operation continues. less than the value in the ACTIVE
policy (old days) for domain policy set
User response: The copy group will be updated, but
management class.
the copy group might fail validation when the policy
set is validated or activated. Explanation: This message can be returned from the
ANR1618W Command: the new RETMIN value (new
server has found that archive retention protection is
days) is less than the value previously
active and the the copy group has a retain minimum
stored (old days) for domain policy set
days value that is less than the value in the ACTIVE
management class.
policy set. The policy will not be validated or activated.
Explanation: Processing for the copy group command
command detected that the new retain minimum
number of days is less than the number of days User response: Update the RETMIN value in the copy
currently stored for the copy group. The policy set group.
might not activate when archive retention protection is
active, because the retain minimum days value is not
allowed to decrease. ANR1622E Management class class name is not
defined in policy set set name, but is
System action: The copy group is updated and system defined in the active policy set for
operation continues. domain domain name. Archive retention
protection is active, so validation fails.
User response: The copy group will be updated, but
the copy group might fail validation when the policy Explanation: This message can be returned from the
set is validated or activated. VALIDATE POLICYSET or ACTIVATE POLICYSET

server found a management class named class name in System action: The duplicate messages were
the currently active policy set, but not defined in the suppressed.
policy set being validated or activated (set name). When
archive retention protection is active, all management
classses in the active policy set must be included in the
policy set being validated. Policy validation will fail. ANR1627I The previous message was repeated
repeat count times.
Explanation: The message issued prior to this message
User response: Define a management class with the
was issued repeatedly.
name specified in the message for the policy set. To
define the proper copy group attributes, reference the System action: The duplicate messages were
management class definition in the active policy set or suppressed.
copy the management class class name from the active
policy set to the policy set set name, using the COPY User response: No action is required.
MGMTCLAS command.
ANR1628I The database manager is using port port
ANR1623E Management class class name in policy number for server connections.
set set name for domain domain name does Explanation: The server configures the database
not have an archive copy group. Archive manager environment to use the indicated port for
retention protection is active, so connections from the server. Initially, connections from
validation fails. the server do not use TCP/IP. After the number of
Explanation: This message can be returned from the connections exceeds a pre-determined threshold,
VALIDATE POLICYSET or ACTIVATE POLICYSET connections are made through TCP/IP to the specified
command. During policy set validation processing, the port. If the port is being used by another application,
server found a management class named class name in the database manager cannot receive connections from
the policy set being validated or activated (set name). the server after the change to TCP/IP connections is
The management class does not have an archive copy necessary. After this situation occurs, future connections
group. When archive retention protection is active, all to the database manager might fail.
management classses in the policy set being validated System action: Server operation continues.
must have an archive copy group. Policy validation
will fail. User response: No action is required.

ANR1629W command: This command will result in
User response: Define an archive copy group in ending the replication relationship for
specified management class, then try the validation all nodes that match the pattern node
again. pattern. Replication will no longer be
performed for the specified node(s).
ANR1625E command: Server is down-level compared Explanation: A REMOVE REPLMODE command with
to the version of data being inserted prevent the specified nodes from being replicated. The
into the database: data version. replication relationship is removed for each node. No
Explanation: The DSMSERV INSERTDB command node data is removed from this or any of the other
encountered data written by a version of the replication servers.
DSMUPGRD EXTRACTDB command that is newer System action: The system asks whether you wish to
than what is supported by the server version. continue with the REMOVE REPLNODE command.
System action: The command ends without inserting User response: To process the REMOVE REPLNODE
any data into the database. command, enter 'Y' to continue or 'N' to stop the
User response: Rerun the command using a version of process.
the server compatible with the version of DSMUPGRD
used to extract the data. Or reextract the data using an ANR1630W command: node name is not configured for
older version of DSMUPGRD that is compatible with replication.
the version of the server.
Explanation: The node specified in the command is
not configured for replication. A node is configured for
ANR1626I The previous message (message number replication if the replication state of the node is
message number) was repeated repeat count ENABLED or DISABLED. To determine the replication
times. state, issue the QUERY NODE FORMAT=DETAILED
Explanation: The message issued prior to this message command.
was issued repeatedly.

System action: The operation continues but the node

ANR1635I The server machine GUID, machine
is skipped for this operation.
GUID, has initialized.
User response: Verify that the nodes specified in the
Explanation: The specified globally unique identifier
command are configured for replication and try the
(GUID) has initialized for the server machine.
command again. Nodes may be configured for
replication with the UPDATE NODE command. System action: Server operation continues.
ANR1631I command: Replication state information
for the specified nodes have been
ANR1636W The server machine GUID changed: old
removed.
value (old value), new value (new value).
Explanation: All replication state information for the
Explanation: The globally unique identifier (GUID)
specified node has been removed from the database
has changed for the server machine. The old and new
and the node is no longer configured for replication. If
values are displayed.
the node was a target of a replication operation it may
now be used to accept client data. System action: Server operation continues.
ANR1637W Error (error) occurred initializing the
server machine GUID.
ANR1632E command: Command failed. Replication
state information for the specified nodes Explanation: An error occurred while initializing the
could not be removed. server machine globally unique identifier (GUID).
Explanation: A REMVOVE REPLNODE command System action: Server operation continues.
failed to complete. The replication state for the
specified node is not changed. User response: Handle problems appropriately. A
write error may occur because the server needs root
System action: Server operation continues. authority to write the GUID. A read error may occur if
the server does not have authority to read the GUID.
User response: The server reported a problem running
Other error codes are received from the GUID utility.
the REMOVE REPLNODE command. See
accompanying messages for further information.
ANR1638W Error (error) occurred initializing the
server machine GUID. Old value was
ANR1633E Command: Node node name is set up for
old GUID.
replication and cannot be renamed or
removed. Explanation: An error occurred while initializing the
server machine globally unique identifier (GUID). The
Explanation: You cannot rename or remove a node
old value is displayed.
that is configured for replication from a source server
or that is created on a target server as a result of System action: Server operation continues.
replication.
User response: Handle problems appropriately. A
System action: The requested operation fails. write error may occur because the server needs root
authority to write the GUID. A read error may occur if
User response: To rename or remove the node, you
the server does not have authority to read the GUID.
must first remove the node from replication by issuing
Other error codes are received from the GUID utility.
the REMOVE REPLNODE command on the server
from which the node is to be removed.
ANR1639I Attributes changed for node nodeName:
changed attribute list.
ANR1634I Default replication server name set to
server name. Explanation: The TCP/IP name or address, or the
globally unique identifier (GUID) has changed for the
Explanation: The name of the default
specified node. The old and new values are displayed
target-replication server was set to the value that was
for entries that have changed.
specified with the SET REPLSERVER command. If you
did not specify a value with the command, the existing System action: Server operation continues.
target replication server was removed, and client node
data will not be replicated. User response: None.


or, reissue the command after the move node data

ANR1640E There is no data mover defined for node
process ends.
node name.
Explanation: To perform the requested operation, the
ANR1645I Command: Data for node node name,
specified node must have an associated data mover
filespace filespace name, FSID filespace ID
defined.
will be moved.
System action: The requested operation fails.
Explanation: The server will move data for the
User response: Define a data mover for the node and specified filespace name and node name based on the
retry the operation. criteria entered in the MOVE NODEDATA command.
System action: The server moves data for the
ANR1641E command: The node node name has a type specified node and filespaces.
that is not allowed for this command.
Explanation: The node is not the correct type to be
used with this command.
ANR1646E Command: The datamover type data mover
System action: The command fails. type can only be used with a data format
of NETAPPDUMP.
User response: Re-run the command with a node of
the correct type. Explanation: The data format specified is not valid for
a datamover of type data mover type.
ANR1642E command: The node node name is locked. System action: The command fails and server
Explanation: The node is locked and cannot be used
in this command. User response: Reissue the command and specify a
valid parameter value.
User response: Unlock the node and re-run the
ANR1647E Cannot find file space name for node
command.
node ID, file space file space ID.
Explanation: The server could not obtain filespace
ANR1643I Command: All file spaces for node node
information for that node.
name, will be moved.
Explanation: The server will attempt to move data for
all the file spaces for the specified node name based on User response: Examine the server messages issued
the criteria entered in the MOVE NODEDATA prior to this message to determine the source of the
command. error. Issue the QUERY ACTLOG command to view the
System action: Server moves data for the indicated
node.
representative.
ANR1648W Command:This command will move data
ANR1644E Command: Move node data operation for nodes stored in volumes in storage
already in progress for storage pool pool source storage pool to other volumes
storage pool. within the same storage pool; the data
will be inaccessible to users until the
Explanation: A command has been issued to move operation completes.
node data for the specified storage pool but there is
already a move node data operation in progress for one Explanation: A MOVE NODEDATA command has
or more nodes that have been specifed for that same been entered that will move data to other volumes in
storage pool. the same storage pool. While the data is being moved,
it will not be available to users.
command. System action: The administrator is asked whether to
continue.
User response: Check the activity log for a previous
MOVE NODEDATA command to determine what User response: Enter 'Y' to continue or 'N' to end the
processes for moving node data are in progress for the process.
storage pool. Reissue the command for the node(s) and
storage pool you desire that are not already in progress,

System action: The BACKUP DEVCONFIG action

ANR1649W Command:This command will move data
fails.
for nodes stored in storage pool source
storage pool to storage pool destination User response: Check that the device configuration
storage pool; the data will be inaccessible file exists and that the file system the file resides on is
to users until the operation completes. not out of space.
Explanation: A MOVE NODEDATA command has
been entered that will move data from the source ANR1657E Command: Invalid server or group name
storage pool to the destination storage pool shown. - server or group name.
While the data is being moved it, will not be available
to users. Explanation: The command shown specifies an invalid
server or server group name.
System action: The administrator is asked whether to
continue. System action: The server does not process the
command.
User response: Enter 'Y' to continue or 'N' to end the
process. User response: Reissue the command with a valid
name.
ANR1651E Server information for server name is not

available. ANR1659E Command: Server or server group server
or group name is already defined.
Explanation: The information for server name was not
available. Explanation: A DEFINE SERVER or DEFINE
SERVERGROUP command has been entered that
System action: The current server action fails. specifies a server or server group name that already
exists. The name specified must be a unique name. It
User response: Please review any other messages
must not duplicate a node name used by a registered
prior to this message to determine the cause of the
node, a server name used by a defined server, or a
failure.
server group name used by a defined server group.
ANR1653E Resource lock acquisition for server
command.
server name failed.
User response: To define the server or server group,
Explanation: The acquisition of the resource lock for
reissue the command and specify a different name.
server server name failed.
System action: The current action for the device class
ANR1660I Server server name defined successfully.
referring to this server fails.
Explanation: The requested server has been defined to
User response: Retry the action referring to the device
the system in response to a DEFINE SERVER
class that refers to this server name. If the lock failure
command.
persists, please contact your service representative.
ANR1654E Server server name will not be written to User response: None.
a device configuration file.
Explanation: An error occurred accessing the ANR1661I Server server name deleted.
information for server name while trying to write this
information to a device configuration file. Explanation: In response to a DELETE SERVER
command, the requested server has been removed from
System action: This DEFINE SERVER entry is not the system.
processing.
User response: Verify that the necessary DEFINE
SERVER entries were written to a device configuration User response: None.
file. If this error persists, please contact your service
representative. ANR1662I Server server name updated.
Explanation: One or more attributes of a server have
ANR1656E Failure writing server definitions to a been updated by an UPDATE SERVER command.
device configuration file.
Explanation: An error occurred writing the server
information to a device configuration file. User response: None.

User response: If the specified server is the event

ANR1663E command: Server server name not defined
server, and you want to delete it, issue the DELETE
Explanation: The server server name is not defined to EVENTSERVER command and then reissue the
the system. DELETE SERVER command. To remove a node entry,
issue the REMOVE NODE command for the specified
name.
ANR1669I Server event server name is defined as the
ANR1664W Command: Server server name is currently event server.
in use.
Explanation: The specified server is defined.
Explanation: The command shown specifies a server
that is currently in use for one or more of the following
purposes: User response: None.
v The server is referenced by a device class of
DEVTYPE=SERVER that specifies this server for the ANR1670E Server event server name is already
'SERVERNAME=' parameter. defined as the event server. You must
v The server is defined as the target replication server. issue the DELETE EVENTSERVER
v A connection with this server is currently open. command before defining a new event
server.
command. Explanation: An event server is already defined.
User response: Reissue the command at a later time. System action: The command fails.
In order to delete the server specified, it must not be User response: Delete the existing Event Server and
currently connected, it must not be referenced in a try the command again.
device class, and it must not be defined as the target
replication server.
ANR1671I The event server definition has been
deleted.
ANR1666E command: FILEAGGR not allowed with
TYPE=SERVER. Explanation: The event server definition has been
deleted.
Explanation: The FILEAGGR= parameter may not be
specified with the TYPE=SERVER parameter also being System action: None.
specified. User response: If an event server definition is desired,
System action: The command fails. use the DEFINE EVENTSERVER command.
User response: Reissue the command command

without the FILEAGGR= parameter if this node is of ANR1672I No event server is currently defined.
type SERVER. Explanation: A query was issued to get the name of
the event server; however, no event server is currently
ANR1667E command: Action not permitted against defined.
node node name. System action: None.
Explanation: The command is not permitted against User response: If an event server definition is desired,
the entry for node node name. This node entry has a use the DEFINE EVENTSERVER command.
type of SERVER.
System action: The command fails. ANR1673I Server group group name defined
User response: None. successfully.
Explanation: The requested server group is defined to
ANR1668E command: Not allowed for server server the system in response to a DEFINE SERVERGROUP
name. command.
Explanation: The DELETE SERVER command is not System action: None.

permitted for server server name. The specified server is User response: None.
either the event server or else it is a node entry rather
than a server definition.

ANR1674I Member member name defined ANR1680E Command: Member member name not
successfully in server group group name. defined in server group server group
name.
Explanation: The requested member is defined in the
server group in response to a DEFINE GRPMEMBER Explanation: The member member name is not defined
command. in server group server group name.
System action: None. System action: The command fails.
User response: None. User response: Retry the command specifying an
existing member of the group.
ANR1675I Server group server group name deleted.
ANR1681E Command: Member member name is
Explanation: The requested server is removed from
already in server group server group
the system in response to a DELETE SERVERGROUP
name.
command.
Explanation: The member member name is defined in
server group server group name.
User response: Retry the command and specify a new
ANR1676I Member member name deleted from
member name.
server group server group name.
Explanation: The requested member is removed from
ANR1682E A group cannot be a member of itself.
the server group in response to a DELETE
GRPMEMBER command, Explanation: The member and group name are the
same. A group may not be a member of itself.
User response: Retry the command and specify
another member name.
ANR1677I Server group server group name updated.
Explanation: One or more attributes of a server group
ANR1683E Command: Member member name not
is updated by an UPDATE SERVERGROUP command.
defined.
Explanation: The member member name is not defined
User response: None. to the system. Server group members must be a
defined server or server group.
ANR1678I Server group original server group name System action: The command fails.
renamed new server group name.
User response: Retry the command specifying existing
Explanation: A server group is renamed by a server or group.
RENAME SERVERGROUP command. The original
name is not valid.
ANR1684E Route:command: Routed commands
System action: None. cannot be routed.
User response: None. Explanation: The command part of a routed command

may not contain route information itself. The allowable
syntax for routed commands is "route : command". The
ANR1679E Command: Server group server group name command may not contain route information. Only one
not defined. level of routing is allowed.
Explanation: The server server group name is not System action: The command is not processed.
defined to the system.
User response: Reissue the command without
System action: The command fails. specifying route information in the command portion
User response: Retry the command specifying an of this routed command.
existing group.

ANR1685I Server group server group copied to ANR1690E Error sending command 'command' to
server group new server group. server server name.
Explanation: This message is displayed in response to Explanation: An error was encountered sending the
the COPY SERVERGROUP command. The server group specified command to the server indicated.
named server group is copied to the server group named
new server group.
User response: Retry the command against the
requested server once the error condition has been
User response: None. resolved. If the cause of the error can not be
determined, please contact your local service
representative.
ANR1686I Member member name moved from
server group group name to server group
new group name. ANR1691E Error receiving response from server
server name for command 'command'.
Explanation: The requested member member name is
moved from server group group name to the server Explanation: An error was encountered receiving the
group new server group in response to a MOVE response from the server indicated for the command
GRPMEMBER command. that was issued against it.
User response: None. User response: Retry the command against the
requested server once the error condition has been
resolved. If the cause of the error can not be
ANR1687I Output for command 'command' issued
determined, please contact your local service
against server server name follows:
representative.
Explanation: The output for the command issued
against the indicated server follows this message.
ANR1692E Response for command 'command' from
System action: None. server server name contains invalid data.
User response: None. Explanation: The output returned from the specified
server for the command that was issued, contains
invalid output. The command response can not be
ANR1688I Output for command 'command' issued processed.
against server server name completed.
System action: Output processing for this command
Explanation: This message marks the end of the response terminates.
output for the command specified that was issued
against the indicated server. User response: Please contact your local service
representative.
User response: None. ANR1693E Unable to issue command 'command'
against server server name - failure
ANR1689E Output for command 'command' issued starting thread.
against server server name terminated. Explanation: A thread could not be started to issue
Explanation: An error condition occurred causing the the specified command against the server indicated.
output for the command issued against the specified System action: This command is not issued against
server to be terminated. the server specified. The process will attempt to issue
System action: None. the command against any other servers that were
specified for the command routing information.
User response: Retry the command against the
requested server once the error condition has been User response: Examine the server messages issued
resolved. If the cause of the error can not be prior to this message to determine the source of the
determined, please contact your local service error. Retry routing this command to the indicated
representative. server after the cause of the error has been determined
and resolved. If the error cannot be isolated and
resolved, contact your service representative.


ANR1694I Server server name processed command
'command' and completed successfully. User response: Check to see that valid route
information was provided for the command or else
Explanation: The server indicated processed the
check the activity log for error messages that indicate
command successfully.
why the command was not issued to the other servers.
User response: None. ANR1699I Resolved route information to number of
servers server(s) - issuing command
command against server(s).
ANR1695W Server server name processed command
'command' but completed with warnings. Explanation: The route information was resolved to
the number of servers indicated. The specified
command will be issued against those servers.
command but encountered warnings. However, the
warnings did not prevent the execution of the System action: None.
command.
User response: None. ANR1700E Unable to resolve 'route information' to
any server(s).
ANR1696E Server server name attempted to process Explanation: The route information provided for this
command ' command' but encountered command did not resolve to any server names or group
errors. names. Because of this, the command will not be
issued.
command but encountered errors. These errors System action: None.
prevented the successful completion of the command.
User response: Examine the route information
System action: None. provided. Reissue the command providing correct route
information.
User response: Examine any error messages issued on
either the server sending the command or else the
server executing the command to determine the cause ANR1701E Command: No matching servers defined.
of the failure. Reissue the command once these errors
Explanation: No matching servers are found for the
are corrected.
specified command.
ANR1697I Command 'command' processed by total
number for servers server(s): number of
successful servers successful, number of User response: Issue the command and specify
servers with warnings with warnings, and different servers.
number of servers with errors with errors.
Explanation: The indicated command was processed ANR1702W Skipping 'server name' - unable to resolve
by the number of servers specified. For the total to a valid server name.
number of servers, the number indicated were
successful, the number indicated encountered a Explanation: The server name specified is being
warning condition but processed anyway, and finally, skipped because it could not be resolved to a valid
the number indicated encountered errors and could not server name.
process. System action: None.
System action: None. User response: Reissue the command providing the
User response: None. correct server name.
ANR1698I Command 'command' was not issued ANR1703E Failure resolving server names.
against any other servers. Explanation: An error occurred while resolving the
Explanation: The indicated command was not issued server names. Specifically, the resolution of the server
against any other server. Either the routing information names has terminated because of a significant failure.
did not resolve to any valid servers or else failures System action: None.
occurred issuing the command against the required
servers. User response: Check the activity log and server
console for other messages about the cause of the

failure. Once the cause has been resolved, reissue the administrator must issue the SET
command. SERVERHLADDRESS, SET and SERVERLLADDRESS
or SET SERVERPASSWORD command to set the
missing values.
ANR1704E Failure obtaining or using credentials
for administrator admin name.
ANR1708I Define server for Server name failed
Explanation: An error occurred obtaining or using the
because the crossdefine failed.
credentials for the administrator referenced.
Explanation: The define server command failed
because the crossdefine parameter was included, and
User response: If the administrator the crossdefine was not successful.
SERVER_CONSOLE was being used for a PING or
VALIDATE LANFREE command, the command may
fail. The administrator SERVER_CONSOLE is not able User response: Check this server, and the server being
to perform these commands where the source server, defined for other messages indicating the reason for the
the target server, or both servers have authentication failure.
enabled. The command should be retried using an
administrator other than SERVER_CONSOLE.
ANR1709E Command.: Failure determining current
Check the activity log and server console for other usage for server or group name Server
messages about the cause of the failure. Once the cause name.
has been resolved, reissue the command.
Explanation: The specified command failed to
determine the current use of the server name or server
ANR1705W A ping request to server 'server name' group specified.
was not able to establish a connection
by using administrator credentials.
User response: Retry the command. If it continues to
Explanation: The failure could indicate a problem on
fail and the cause of the failure can not be determined,
the source or target server, or in the connection
please contact your local service representative.
between the servers.
System action: No connection was established.
ANR1710E Command.: Name Name not valid for this
User response: To identify and resolve the issue, command.
complete the following steps: 1. Check the activity log
Explanation: The name specified for this command is
and server console for messages that indicate a failure
not valid for this operation. The first case is that a
or problem on the source server. 2. Check the
server name was specified for a command requiring a
communication connection between the servers. 3.
server group name. The other case is where a server
Verify the administrator definition and password on
group name was specified for a command requiring a
both servers. 4. Verify that the target server is running.
server name.
5. Correct any identified issues.
ANR1706I A ping request to server 'server name' User response: Retry the command specifying the
was able to establish a connection by proper name.
using administrator credentials.
Explanation: The administrator credentials are valid. ANR1711E Error accessing the server or server
group name Name.
System action: The connection was established.
Explanation: A server operation attempted to access
the server name or server group name specified. An
error occurred while trying to access the information
ANR1707E Server information not complete, for this server name or server group name.
crossdefine not allowed.
System action: The server operation fails.
Explanation: The SERVERHLADDRESS,
User response: Review the activity log to try to
SERVERLLADDRESS or SERVERPASSWORD has not
determine the cause of the failure. If a cause can not be
been set for this server. These are required for the
determines, please contact your local service
CROSSDEFINE option on the define server command.
representative.
User response: Use the QUERY STATUS command to
find what values need to be set. An authorized

ANR1712W Command routing not allowed from ANR1717E Command: Command failed -
server console. Non-Compatible Filespace name types
have been specified.
Explanation: Command routing is not allowed from
the server console. Explanation: A server command has been entered but
cannot be processed because Non-Compatible Filespace
System action: The command is not executed.
name types have been specified.
User response: Reissue the command from an
Administrative client.
command.
User response: Specify compatible filespace names.
ANR1713I Command 'command' issued against
Unicode to Unicode or Non-Unicode to Non-Unicode.
server server name.
Explanation: The specified command has been sent to
ANR1718E Command: Reconstruction of file
the indicated server. The command is to terminate the
aggregates is supported only for
specified server, no confirmation will be recieved.
movement in which the source and
System action: None. target storage pools are
sequential-access.
Explanation: The indicated command specifies that
file aggregates be reconstructed during a move
ANR1714W The password for administrator operation for which reconstruction is not supported.
administartor name has expired. The Aggregates are reconstructed only when both the
password for this administrator must be source storage pool and the target storage pool are
updated on the configuration manager sequential-access.
server server name.
Explanation: The password for the named command.
administrator has expired, but the administrator is a
managed object on this server. The password must be User response: Reissue the command without
updated on the named configuration manager server. specifying that aggregates should be reconstructed.
Alternatively, specify a move operation involving
System action: The administrator is allow access to transfer of data within a sequential-access storage pool
the server. or between two sequential-access storage pools.
User response: Change the administrator's password
on the named configuration manager server. ANR1719E Storage pool storage pool name specified
on the MOVE NODEDATA command is
ANR1715E Event server cannot be deleted - it is not a valid pool name or pool type.
currently active. Explanation: If the source storage pool specified in the
Explanation: The event server cannot be deleted since command is a primary storage pool, then the
it is currently active for event logging. destination storage pool specified must also be a
primary storage pool. If the source storage pool is a
System action: The server does not delete the event copy storage pool, then the specified destination
server entry. storage pool must be the same storage pool as the
User response: In order to delete the event server, it source storage pool.
must not be currently active for event logging. To stop System action: The MOVE NODEDATA process fails.
event logging to the event server issue END
EVENTLOGGING EVENTSERVER. Then reissue the User response: Provide a valid primary storage pool
DELETE EVENTSERVER command. name as the destination storage pool if the source pool
is a primary storage pool. If the source pool is a copy
storage pool do not specify a destination pool, or,
ANR1716I Server cannot be crossdefined to itself, specify the same copy storage pool as the destination
crossdefine not allowed. pool.
Explanation: An attempt was made to crossdefine the
server to itself. ANR1720I A path from source name to destination
System action: The command fails. name has been defined.
User response: None. Explanation: In response to the DEFINE PATH

command, the path from the source name to the
destination name has been defined in the server
database.


ANR1725E The source or destination name name is
User response: None. invalid and the command command
failed.
ANR1721I A path from source name to destination Explanation: The source or destination name is invalid
name has been deleted. in the DEFINE PATH, DELETE PATH, or PERFORM
LIBACTION command.
Explanation: In response to the DELETE PATH
command or to an UPDATE DEVCLASS command System action: Server operations continue.
with the MOUNTLIMIT parameter, the path from the
User response: Issue the command again with a valid
source name to the destination name has been deleted
source or destination name.
in the server database.
ANR1726E A operation using the path from
User response: None. sourcename to destname is currently being
used.
ANR1722I A path from source name to destination Explanation: This path was in use when the command
name has been updated. was entered. The attributes of a path may not be
changed while it is being used.
Explanation: In response to the UPDATE PATH
command, the path from the source name to the System action: The server ignores the command.
destination name has been updated in the server
User response: Wait until the operation using this
database.
path is complete, or cancel the operation using this
System action: Server operation continues. path, and then reissue the command.

ANR1727E A path from sourcename to destname does
not exist.
ANR1723E A path is already defined using source
name and destination name. Explanation: The path being updated or deleted does
not exist.
Explanation: In response to the DEFINE PATH
command, the server determines that a path with the System action: The server ignores the command.
same source name and the same destination name
User response: Reissue the command with a different
already exists in the server database.
source or destination name or define a new path.
User response: Correct the source name or destination ANR1728E The library libname is not a SCSI or VTL
name and re-enter this command. library.
Explanation: A drive that is to be used by a NAS data
ANR1724W Command: Server server name is currently mover must be attached to a SCSI or VTL library.
in use.
Explanation: The command shown specifies a server
that is currently in use. The server is referenced in a
drive name.
PATH used for LANFree access to a FILE device type
drive in a shared library.
ANR1729E A path using the data mover source name
still exists.
command.
Explanation: In the DELETE DATAMOVER command,
User response: Reissue the command at a later time.
the data mover name supplied is either the source or
In order to delete the server specified, it must not be
the destination in a path that still exists in the server
currently connected to the server, it may not be
database.
referenced in a device class, it can not be defined to be
the event server, and it cannot be referenced within a System action: Server operation continues.
PATH definition as a FILE device type drive.
User response: Delete the existing path and reissue
this command.

this data mover, and then reissue the command.

ANR1730I Data mover mover name has been
defined.
ANR1736E Command: Parameter parameter length is
Explanation: The data mover has been defined in the
invalid.
server database.
Explanation: The specified server command has been
entered with a parameter that is longer or smaller in
User response: None. length than the allowed length.
User response: Reissue the command and enter the
deleted.
proper syntax.
Explanation: The data mover has been deleted in the
server database.
ANR1737E Command: Device name device specified
System action: Server operation continues. is invalid.
User response: None. Explanation: The specified command has been entered
with an invalid device name.
ANR1732I Data mover mover name has been System action: The command failed.
updated.
Explanation: The data mover has been updated in the device name.
server database.
System action: Server operation continues. ANR1738W The database backup does not contain a
copy of the server master encryption
key. The server master encryption key
will not be restored.
ANR1733E Data mover mover name is already
Explanation: This databackup backup was completed
defined.
in a server level that does not support encryption.
Explanation: A DEFINE DATAMOVER command was
entered for a data mover that already exists in the
server database. User response: None
ANR1739E The database backup contains a copy of
User response: Use the UPDATE DATAMOVER to
the server master encryption key but no
change the attributes in this data mover. Otherwise use
password was provided.
a different data mover name.
Explanation: To restore the server master encryption
key, a password must be specified on the DSMSERV
ANR1734E Data mover mover name is not defined.
RESTORE DB command.
Explanation: An UPDATE DATAMOVER command
was entered for a data mover that does not exist in the
server database. User response: ToRestore the server master encryption
key, specify a password on the DSMSERV RESTORE
DB command. If you do not want to restore the master
User response: Correct the data mover name or use encryption key, you must specify the
the DEFINE DATAMOVER command to define a new RESTOREKeys=No value.
data mover.
ANR1740W The database backup does not contain a
ANR1735E Data mover data mover is currently being copy of the server master encryption
used. key. The server master encryption key
will not be restored.
Explanation: A data mover was in use when the
command was entered. The attributes of a data mover Explanation: The server master encryption key was
may not be changed while it is being used. not stored when the database was backed up.
System action: The server ignores the command. System action: The command continues.
User response: Wait until the operation using this User response: To store a copy of the server master
data mover is complete, or cancel the operation using encryption key during database backup, you must

specify the PROTECTKEYS and PASSWORD User response: Update the destination's definition
parameters on the SET DBRECOVERY or BACKUP DB with the correct world wide name.
command.
ANR1745I The HBA is busy and SAN devices
ANR1741E The server master encryption key in the cannot be discovered.
database backup cannot be read. The
Explanation: The SAN device discovery function is
password might be incorrect, or the
busy. The requested HBA API query cannot be
encryption key might be invalid.
completed at this time. This type of timeout is
Explanation: The server master encryption key stored generally caused by a bad HBA adapter in a system
in the database backup cannot be read. To access the with multiple HBAs.
master encryption key, a password is required. If the
password is incorrect, the master encryption key cannot
be accessed. If the password is correct, the master User response: Check all HBA adapters on the system
encryption key is not being read properly. and ensure that all of them are functioning correctly.
Reissue the QUERY SAN command.
User response: Verify that the password is correct and
ANR1746E The path from data mover datamover
retry the command. If the password is correct, you can
name to drive library name drive name is
skip restoring the master encryption key. To skip
not online.
restoring the master encryption key, you must specify
the RESTOREKeys=No value on the DSMSERV Explanation: A server-free operation requested the
RESTORE DB command. Warning: If you skip restoring specified device. The device cannot be used because the
the master encryption key, you will be unable to path from the datamover to the device is not online.
retrieve data stored in any encrypted storage pool, and
no new data will be allowed to be stored in any System action: Server operation continues.
encrypted storage pool. User response: Determine the reason for the path
being offline; if possible, update the path status to
ANR1742I The server master encryption key was online.
restored successfully.
Explanation: The server master encryption key was ANR1747E The library libname is not a ZOSMEDIA
restored to the server password file. enabled library.
System action: N/A Explanation: Defining a PATH to a library using the

ZOSMEDIASERVER parameter requires the library be a
User response: None ZOSMEDIA library ( e.g., DEFINE LIB libname
LIBTYPE=ZOSMEDIA ).
ANR1743E The parm parameter is required to be System action: The server ignores the command.
enabled when PASSWORD is specified.
User response: Reissue the command with the correct
Explanation: The PASSWORD parameter is only used library name.
when the specified parameter has an enabled value.
System action: The command fails. ANR1748E The PASSWORD parameter is required
when parm is enabled.
User response: Remove the PASSWORD parameter or
enable the keys parameter. To enable the keys Explanation: The PASSWORD parameter is required
parameter for the SET DB RECOVERY or BACKUP DB when the specified parameter has an enabled value.
commands, set the PROTECTKEYS parameter to YES.
To enable the keys parameter for the DSMSERV System action: The command fails.
RESTORE DB utility, set the RESTOREKEYS parameter User response: Add the PASSWORD parameter or
to YES or ONLY. disable the keys parameter. To disable the keys
parameter for the SET DB RECOVERY or BACKUP DB
ANR1744E The world wide name is invalid for the commands, set the PROTECTKEYS parameter to NO.
destination of the path being defined. To disable the keys parameter for the DSMSERV
RESTORE DB utility, set the RESTOREKEYS parameter
Explanation: A path was being defined from a to NO.
datamover to a destination and that destination has an
incorrect world wide name specified.

that is less than the size of the object to be inserted.

ANR1749W The drive library name drive name was not
found on the SAN. The path definition System action: The operation fails.
for this drive has been marked offline.
User response: Ensure that the destination storage
Explanation: During device discovery on a storage pool is available, has an adequate MAXSIZE setting,
area network a device was not found that has the same and has adequate space. The MAXSIZE setting may be
serial number as the drive defined to IBM Spectrum changed using the UPDATE STGPOOL command.
Protect. Space may be added to the storage pool by checking in
scratch volumes or defining new volumes in the
storage pool. If volumes in the destination storage pool
User response: Verify that the serial number of the are offline, use the VARY ONLINE command to vary
drive definition is correct and that the drive is them online and make them available for use. Correct
operational. the problem and reissue the command.
ANR1750E The server detected an internal error, ANR1761E Command: Command failed for node
return code = return code. node name, filespace filespace name -
storage media is inaccessible.
Explanation: An unexpected error occured during
server operation. Explanation: The indicated command failed because
required storage media is unavailable.
examine messages prior to this error to determine the User response: Ensure that there are sufficient
cause of the data storage failure. If the failure can be volumes available for storing backups and that any
found and resolved, retry the operation. If the failure volumes required for restore are checked in and
cannot be found, contact your service representative for available. Correct the problem and try the command
assistance in resolving the problem. again.
ANR1758I Repaired extents damaged extents in ANR1762E Command: Command failed for node
directory container pools. node name, filespace filespace name -
mount point unavailable.
Explanation: The server repaired the specified number
of extents. Explanation: The indicated command failed because
sufficient mount points are not available.
User response: Ensure that sufficient mount points are
available and working correctly. Correct the problem
ANR1759E Command: A device with SCSI
and try the command again.
datamover capabilities was not found in
the system configuration for datamover
datamover name. ANR1763E Command: Command failed - see
previous error messages or view the
Explanation: The scsi address could not be
activity log.
determined for a device that is capable of performing
datamover operations. Explanation: The indicated server command has
failed. This message is always preceded by one or more
other error messages which provide more detail about
User response: Verify that the hardware that can why the command failed.
perform SCSI datamover operations is installed and
powered on.
User response: Examine the previous error messages
to determine the source of the error. Use the QUERY
ANR1760E Command: Command failed for node
node name, filespace filespace name -
destination storage pool storage pool was
command again.
skipped.
Explanation: The indicated command failed because
the destination storage pool was skipped. A storage
pool may be skipped because it does not have enough
available space, or because it has a MAXSIZE value

System action: The command is not processed.

ANR1764E Command: Command failed - loadable
module module name is not available. User response: Specify a valid DEVICE parameter that
is not used by any other drive or library.
Explanation: The indicated server command has failed
because it requires the availability of the specified
loadable module, but the module is not loaded. ANR1769E Command: Command failed - multiple
actions between commit actions not
allowed.
User response: Make sure the necessary loadable
Explanation: A server script that performs multiple
module is available for your platform. Not all modules
actions between commit actions is not allowed. For
are available on all platforms. If the module is available
example, deletion of multiple paths before each of the
for your platform and is installed, contact your service
deletions is committed is not allowed.
representative for assistance.
command.
ANR1765E Command:The number of copy threads
entered, copythreads, exceed the User response: Rewrite the script or macro so that no
capabilities of the datamover. new command is issued until the previous command is
committed.
Explanation: A datamover has an upper limit of the
number of copy threads that it is capable of executing.
The copythreads parameter provided is greater than ANR1770E Processing for session session id found
this limit. destination new destination. Expected
current destination.
Explanation: While processing a remote image
User response: Make sure the value entered for the
operation, the specified session was working with the
copythreads parameter is less than the maximum for
current destination. But the server received a client
this datamover. Using the default for the number of
request with a new destination name.
copythreads sets the number of copythreads to the
datamover's maximum value. System action: Server operation continues.
User response: From the client, quit the current
ANR1766E Command: NAS device datamover reports remote image request. Reissue the request, if desired.
a drive affinity for drive tape drive that
does not match this data mover.
ANR1771E The path from remote server remote
Explanation: A NAS device returned an affinity server name to destination destination name
identifier for a tape drive that does not match the with the destination device type is not
recorded affinity identifier for the data mover. valid.
System action: The command fails. Explanation: The library manager receives a command
to update the path for the remote server. The device
User response: Check the High Level Address for the
type field of the destination device is not valid. The
data mover and verify that it is a node management
destination for update path from remote server must be
network interface on the NAS cluster. Verify that the
either drive or library.
interface is located on the appropriate node cluster.
ANR1767I Process process number for NAS node User response: Determine why the device type field of
node name will use NAS data mover the destination device is not valid.
datamover
Explanation: An alternate NAS data mover was ANR1772E The path from source source name to
selected for the current NAS operation. destination drive name is taken offline.
System action: The NAS operation continues. Explanation: The path is now marked offline.
User response: None. System action: The path is inaccessible.
User response: Determine the reason the path is
ANR1768E Command: The device name provided inaccessible, such as a hardware problem. Make any
conflicts with a device name that is needed corrections. Then, issue the the UPDATE PATH
already in use. command with the ONLINE=YES option to make the
path online.
Explanation: The device name provided in the
command is already used by an existing path.

v One of the parameters specified during datamover

ANR1773W Unable to update the path in the
update was incorrect: TCP/IP address of the file
database path source name and drive drive
server, user id, password, TCP/IP port
name .
v File server is not accessible
Explanation: The system is unable to update the path
v NDMP server limits the number of opened NDMP
information in the database table.
sessions
System action: .
System action: The data mover definition is updated.
User response: Check that the file server associated
with the data mover is accessible through the network;
ANR1774E The Query Status command failed, and check each of the attributes specified in the datamover
server initialization has not completed. update command; check the number of open NDMP
Allow server initialization to complete, sessions with the file server.
and then try the command again.
Explanation: The command Query Status failed ANR1777W Command: New cluster node cluster node
because server initialization has not completed. on NAS cluster nas cluster is assigned
same cluster affinity as cluster node
existing cluster node
User response: Allow server initialization to complete,
Explanation: A NAS cluster device reported a cluster
and then try the command again.
node with a cluster affinity identifier that is the same
as an existing data mover.
defined, however a connection to the
data mover failed. Please check the User response: Check the data movers reported in the
attributes of the file server specified in message and updata any existing device paths defined
the definition of the data mover. for these data movers based upon the current
configuration of the NAS cluster.
Explanation: The data mover has been defined in the
server database, however the server cannot connect to
the file server associated with the data mover. The ANR1778E Command: Invalid or missing parameter.
connection failed because of one of the following
possible reasons:
entered with an invalid parameter, or, is missing a
v One of the parameters specified during datamover required parameter.
definition was incorrect: TCP/IP address of the file
server, user id, password, TCP/IP port System action: The server ignores the command.
v File server is not accessible User response: Reissue the command and enter the
v NDMP server limits the number of opened NDMP proper syntax.
sessions
System action: The data mover is defined to the ANR1779I backupset process name process completed:
server. successful count backupset(s) were
generated or defined out of total count
User response: Check that the file server associated backupset(s) requested by the
with the data mover is accessible through the network; command's specifications.
check each of the attributes specified during datamover
definition; check the number of open NDMP sessions Explanation: A GENERATE or DEFINE BACKUPSET
with the file server. command has finished successfully, and the backupsets
described in previous messages have been created.
ANR1776I Data mover mover name has been System action: The backupsets described have been
updated, however a connection to the created.
data mover failed. Please check the User response: None.
attributes of the file server specified in
the update command.
ANR1780I Command: The network-attached storage
Explanation: The data mover has been updated in the (NAS) cluster cluster name has tape
server database, however the server cannot connect to devices attached to cluster node cluster
the file server associated with the data mover. The node
connection failed because of one of the following
possible reasons: Explanation: The server has discovered tape drives
attached to a node in a NAS cluster during a DEFINE

DATAMOVER or UPDATE DATAMOVER command. System action: None.

System action: Server processing continues. User response: SAN discovery does not work for this
adapter. For the list of supported HBAs and required
driver levels by operating system, see techdoc 1193154
at http://www.ibm.com/support/
ANR1781I Command: The network-attached storage docview.wss?uid=swg21193154
(NAS) cluster cluster name requires new
data mover, cluster node, for tape drive
ANR1789W Get HBA target mapping failed.
access.
Explanation: The HBAAPI function to get the target
Explanation: The server has discovered a node within
mapping failed.
in a NAS cluster with attached tape drives. A new data
mover will be defined to provide access to the attached System action: None.
tape drives.
User response: SAN discovery will not work for this
System action: Server processing continues. adapter. For the list of supported HBAs and required
driver levels by operating system, see techdoc 1193154
User response: When a datamover is created by the
at http://www.ibm.com/support/
server for node within a cluster you should identify the
tape drives attached to the node. Define paths from the
new datamover to each drive you want to use for
backup of the NAS cluster. ANR1790W SAN discovery failed.
Explanation: SAN discovery failed.
ANR1786W HBAAPI not able to get adapter name.
Explanation: The HBAAPI function getAdapterName
User response: SAN discovery failed. This may be a
failed. The server will continue to access next adapter if
problem with the HBA firmware, HBA or the HBA
it exists.
verdor's HBAAPI driver. For the list of supported
System action: None. HBAs and required driver levels by operating system,
see techdoc 1193154 at http://www.ibm.com/support/
User response: The IBM Spectrum Protect SAN
discovery will not work with this Host Bus Adapter.
For the list of supported HBAs and required driver
levels by operating system, see techdoc 1193154 at ANR1791W HBAAPI wrapper library file name failed
http://www.ibm.com/support/ to load or is missing.
Explanation: This library is provided by IBM
Spectrum Protect. It is required for discovery of devices
ANR1787W Unable to open adapter adapter name. on a SAN.
Explanation: The HBAAPI function to open the host v For windows, the HBAAPI wrapper library is
bus adapter (HBA) failed. hbaapi.dll.
v For AIX, the HBAAPI wrapper library is
libHBAAPI.a.
User response: The IBM Spectrum Protect SAN v For Solaris, the HBAAPI wrapper library is
discovery will not work with this Host Bus Adapter. libhbaapi32.so for 32 bit application and
For the list of supported HBAs and required driver libhbaapi64.so for 64 bit application.
levels by operating system, see techdoc 1193154 at
v For Linux, the HBAAPI wrapper library is
http://www.ibm.com/support/
libhbaapi32.so for 32 bit application and
libhbaapi64.so for 64 bit application.
ANR1788W Unable to retrieve the adapter attributes
for adapter name. User response: Make sure the HBAAPI wrapper
library for this platform is in the same directory as the
Explanation: The HBAAPI function failed to retrieve
IBM Spectrum Protect server executable. AIX is the
the adapter' attributes. This problem is caused by a
only exception with HBAAPI wrapper library
nonfunctional Fibre Channel adapter on the system.
libHBAAPI.a in /usr/lib.
Check this adapter to ensure it works properly. This
problem also can be caused by other non Fibre Channel
types of adapters on the system, such as, a SAS or a
parallel SCSI adapter. This message can be ignored if
you are using a non Fibre Channel adapter.


ANR1792W HBAAPI vendor library failed to load or
is missing. User response: SAN discovery is currently disabled
either by default by the SANDISCOVERY OFF option
Explanation: The HBAAPI vendor library failed to
depending on the platform or by the SANDISCOVERY
load or is missing. This HBAAPI library is provided by
UNSCANNEDPATHOFF option. For the list of
the Host Bus Adapter (HBA) vendor. It is required for
supported HBAs and required driver levels by
IBM Spectrum Protect server to discover devices on the
operating system, see techdoc 1193154 at
SAN.
System action: None. docview.wss?uid=swg21193154.
User response: Ensure the HBAAPI file exists on the
system. If the driver level on your system is not ANR1795I The device driver has been updated
supported, go to the HBA vendor's website and successfully for device old device name.
download/install the HBA driver. For the list of The new device name is new device name.
supported HBAs and required driver levels by
operating system, see techdoc 1193154 at
the CHANGE DEVDRIVER command. The device
driver for device old device name has been updated
docview.wss?uid=swg21193154. The following is an
successfully.
example of some of the HBA vendor's HBAAPI file:
v For UNIX systems, This HBAAPI vendor library's System action: Server operation continues.
location is indicated in /etc/hba.conf. For example: User response: None.
qla2x00 /usr/lib/libqlsdm.so
com.emulex.emulexapilibrary
/usr/lib/libemulexhbaapi.so ANR1796E Invalid device name device name.
v For Windows systems, verify the location of the Explanation: The device name is not in the form of
HBAAPI vendor library by checking LibraryFile in: TAPEx or CHANGERx.
HKEY_LOCAL_MACHINE System action: The server fails the command.
SOFTWARE
SNIA User response: Change the device name to TAPEx or
HBA CHANGERx and retry the command.
<HBAAPI library>
ANR1797E Device device name is not supported by

ANR1793W IBM Spectrum Protect SAN discovery is the IBM Spectrum Protect device driver.
not supported on this platform or this
version of OS. Explanation: Device device name is not supported by
the IBM Spectrum Protect device driver. The hardware
Explanation: SAN discovery for this platform is ID was not found in the IBM Spectrum Protect device
currently not supported. driver INF file, i.e. tsmlb.inf and tsmmt.inf.
System action: None. System action: The server fails the command.
User response: SAN discovery will not work for this User response: Access the IBM Spectrum Protect Web
platform. site at www.ibm.com/software/sysmgmt/products/
v For AIX, we only support AIX5.2F and above support/IBMTivoliStorageManager.html and navigate
v For HP, we do not support this platform yet. to the device support information for the server's
operating system. Verify if the device is supported. If
v For Linux, we do not support Linux-zOS yet.
the device is supported by the IBM Spectrum Protect
v For Windows, we do not support Windows 2003 64 device driver, contact your service representative.
bit yet.
For the list of supported HBAs and required driver ANR1798E Device driver update failed for device
levels by operating system, see techdoc 1193154 at device name.
http://www.ibm.com/support/ Explanation: The CHANGE DEVDRIVER operation
docview.wss?uid=swg21193154. failed for device device name.
ANR1794W IBM Spectrum Protect SAN discovery is fails.
disabled by options.
Explanation: SAN discovery is disabled by option
SANDISCOVERY OFF or SANDISCOVERY
UNSCANNEDPATHOFF.

ANR1799E The IBM Spectrum Protect device driver ANR1804W Command: Process process number
is not installed, or one or more device skipping volume volume name in storage
driver files are missing. pool pool name because the volume is in
use by another process.
Explanation: The server command has failed because
the IBM Spectrum Protect device driver is not installed, Explanation: The command shown specifies the
or one or more device driver files are missing. volume to be processed, but that volume is currently
being used by another operation.
System action: The server skips the volume and
User response: Make sure the IBM Spectrum Protect
processes the next available volume.
device driver is installed. and the following files are not
missing. %WINDIR%\system32\drivers\tsmscsi.sys (or User response: Check the activity log to determine
tsmscsi64.sys for 64-bit Windows), %WINDIR%\inf\ which operation was using the volume. If the operation
tsmmt.inf, and %WINDIR%\inf\tsmlb.inf. using the volume is complete reissue the Command to
process the skipped volume.
ANR1801E Eventlog command: Invalid event or event
class - Event or event class name. ANR1805I This export command does not work
with either container or cloud storage
Explanation: An event logging command has been
pools. Object Object Name is skipped.
entered which specifies an unknown event or event
class. Explanation: Container storage pools cannot be used
for storage pool backup, reclamation, migration,
System action: The command is ignored for the
collocation, export, import, or simultaneous-write.
invalid event or event class. Any valid events or classes
specified are processed. System action: The server skips the object and
processes the next available object.
event or event class. User response: Use another method or storage pool
type to store the data.
ANR1802E Device device name was not found.
ANR1806I Some data is skipped because the
Explanation: The device was not found in the device
operation cannot be completed for
information set. The vendor ID and/or product ID, or
container or cloud storage pools.
device name may be invalid, or the device has been
removed from the system. Explanation: Container or cloud storage pools cannot
be used for storage pool backup, reclamation,
migration, collocation, export, import, NDMP, generate
fails.
backupset or simultaneous-write.
System action: The server skips the object and
vendor ID and product ID, or device name.
User response: Use another method or storage pool
ANR1803W SAN discovery module module name is
not installed correctly.
Explanation: The server attempted to load the SAN
ANR1807I Table updating statistics performed
discovery module, but the permissions or ownership of
successfully for processed table.
the file are incorrect.
Explanation: Runstat successfully run on that table.
System action: Server operation continues, but
without SAN discovery function. System action: Server operation continues.
User response: Ensure that the SAN discovery module User response: No user action required.
is executable, has the setuid bit turned on, and is
owned by root. The SAN discovery module is called
ANR1808I Object Object ID is skipped because the
'dsmqsan' and must reside in the server or storage
operation cannot be completed for cloud
agent executable directory.
storage pools.
Explanation: Cloud storage pools cannot be used for
storage pool backup, reclamation, migration,
collocation, or simultaneous-write.
System action: The server skips the object and

User response: Use another method or storage pool

ANR1813W Filespace filespace name for node node
name is a replication replication role.
Explanation: The reported filespace is either the
ANR1809E Insufficient memory to activate event
source or target of a replicated node. The DELETE
logging.
FILESPACE command will delete the data on this
Explanation: A BEGIN EVENTLOGGING command server, but will not delete the data on any other
has been entered, but the server has insufficient replication servers.
memory available to activate logging.
System action: The DELETE FILESPACE command
System action: The command is ignored. continues.
User response: If logging is required, make more User response: If this message indicates this filespace
memory available to the server then restart the server. is the source of replicated data, then login to all servers
containing replicated data from this filespace and issue
the DELETE FILESPACE command to remove the data
ANR1810E Eventlog command: Invalid receiver - from those servers. If this message indicates this
receiverName. filespace is the target of replicated data, ensure that the
Explanation: An event logging command has been filespace on the source server is either deleted, or
entered which specifies an unknown event log receiver updated to no longer replicate to this server.
(maybe unknown just to this platform).
System action: The command is ignored for the ANR1814W The database manager cannot load the
invalid receiver. Any valid receivers specified are security plugin file name.
processed. Explanation: The database manager cannot load the
User response: Reissue the command with the correct security plugin. This plugin controls access to the
receiver. database manager from the IBM Spectrum Protect
server.
ANR1811W The Host Bus Adapter API package System action: The server stops.
might not be installed. User response: Inspect the DB2 diagnostic log file to
System action: None. identify the reason the database manager cannot load
the security plugin. Correct the problem and restart the
User response: The HBA API does not provide the server.
number of Fibre Channel adapters from the host
system. The HBA API file version that is on your
operating system might not be supported or the HBA ANR1815W Check target server for storage problems
API package might not be installed. Go to the HBA during replication of node node list.
vendor website to obtain the latest version of the HBA Explanation: During the replication process for the
API. For a list of supported HBAs and required HBA specified nodes, there were problems storing data at
API levels by operating system, see techdoc 1193154 at the replication target server.
docview.wss?uid=swg21193154. System action: Processing ends.
User response: Check the activity log of the target
ANR1812E DELETE FILESPACE filespace name for server for specific error messages relating to data
node node name failed deletion because storage during the replication process.
of a replication in progress.
Explanation: The reported filespace belonging to the ANR1816W The names of one or more files were
reported node is currently being replicated as part of a truncated. Examine log file log file name
REPLICATE NODE command. A filespace cannot be for details.
deleted while the replication is in progress.
System action: The DELETE FILESPACE ends with a attempted to insert a database row describing a file
state of FAILURE. whose path name is longer than the maximum path
name supported by IBM Spectrum Protect V6. The IBM
User response: Use the QUERY PROCESS command Spectrum Protect V5 server supported path names of
to view active REPLICATE NODE processes. Either up to 8000 bytes, but the V6 server does not allow path
wait for the replication to complete or cancel the names to be longer than 6000 bytes.
replication process with the CANCEL PROCESS or
CANCEL REPLICATION commands, and reissue the System action: The name of the file was replaced by a
DELETE FILESPACE command. system-generated name. Information needed to restore

the file to its original name was written to the specified System action: None.
log file.
User response: Check for warning or error messages
The log file contains two sections. The first section lists during the import process on the server and handle as
files whose names were truncated. The second section needed.
identifies the node names and filespace names of the
truncated files.
ANR1819E Permission denial to device device name.
The first section is identified by the header "--
Explanation: A read-only attribute is assigned to
Truncated Files --". Each line of this section identifies
non-root users and their tape device files. If this
one file whose name was truncated. The line consists of
attribute is not changed, non-root users cannot store
four fields, separated by tabs:
data to tape devices. This only affects HP-UX, Linux,
v Node ID - a numeric identifier for the node that and Solaris operating systems.
owns the file.
System action: The open operation fails.
v Filespace ID - a numeric identifier for the file's
filespace. User response: Issue the CHMOD system command
v New Name - the system generated name that was to change the read-only attribution for specific tape
assigned to the file. device files and run the previously failed operation
again. See Technote 1321130 for details about resolving
v Original Name - the original name of the file.
this problem: https://www-304.ibm.com/support/
docview.wss?uid=swg21321130
The second section is identified by the header "-- Node
and Filespace Names --". Each line in this section maps
the node ID and filespace ID associated with one or ANR1820E The server could not connect to the
more of the files in the first section to a node name and database manager by using TCP/IP port
filespace name that can be specified on a restore port number.
command. The line consists of four fields, separated by
Explanation: The server attempted to connect to the
tabs:
database by using TCP/IP, but it was not able to do so.
v Node ID - a numeric identifier for the node that
owns the file. System action: The server stops.
v Node Name - the name of the node associated with User response: First, verify that the port number is
the node ID. not already in use. Possible methods include:
v Filespace ID - a numeric identifier for the file's v On Unix systems, inspect /etc/services for an
filespace. occurance of the port number.
v Filespace Name - the name of the filespace associated v Use the netstat command to determine if a service is
with the filespace ID. listening on the port number.
User response: Inspect the contents of the specified
log file. If necessary, use the information in the log file If a conflict is detected, specify a different port number
to restore the files to their original name. on the DBMTCPPORT option in the server options file
and restart the server.
ANR1817W command: No valid nodes were If no conflict is found, use the "db2 get database
identified for import on target server manager config" command to verify that the
tgtServerName. SVCENAME configuration parameter is set to the port
Explanation: During a server-to-server export, the number identified by the message. If not, then use the
import process on the target server reported that none "db2 update database manager config using
of the node definitions in the export data were valid for SVCENAME port number" command to manually
import. No node data was imported on the target update the configuration parameter. Ensure that the
server. value specified is also specified on the DBMTCPPORT
server option. Restart the server.
User response: Check for warning or error messages Finally, use the "db2set" command to verify that the
on the target server and handle as needed. DB2COMM environment variable is set to "TCPIP". If
not, then use the "db2set DB2COMM=TCPIP"
command to set the environment variable and restart
ANR1818W command: No valid nodes were the server.
identified for import.
Explanation: During a server import process none of
the node definitions in the import data were valid for
import. No node data was imported.

ANR1821W Event logging is not started for the ANR1825I Event logging active for the receiverName
receiverName receiver. receiver.
Explanation: In response to a BEGIN Explanation: In response to a BEGIN
EVENTLOGGING command, recording of event log EVENTLOGGING command, event log records are now
records to the specified receiver was attempted. The being output to the specified receiver.
event logging for the specified receiver is already
started because either the receiver is currently running
or the receiver was terminated previously and is still in User response: None.
the process of writing the messages that were queued
up for processing.
ANR1827E Eventlog command: No valid receiver
System action: None. specified.
User response: Check to see if the event log receiver is Explanation: An event logging command has been
already started by issuing the QUERY STATUS entered, and no valid receivers were specified.
command, and checking the Active Receivers field.
Some event log receivers such as FILETEXT, System action: The command is ignored.
FILETEXTEXIT, USEREXIT, and Tivoli receiver, can be User response: Reissue the command with the correct
started during server initialization if they are receiver.
configured in the server options file.
v If the event log receiver is already started you do not
ANR1829E Eventlog command: Server events may not
take any further action.
be disabled for the activity log receiver.
v If the event log receiver is not currently running then
wait and try to start it again after a short delay. Explanation: A DISABLE EVENT command has been
entered for the activity log receiver.
ANR1822I Event logging ended for the receiverName System action: The command is ignored for the
receiver. activity log receiver. Any valid receivers specified are
processed.
Explanation: In response to an END
EVENTLOGGING command or because an error User response: Reissue the command with the correct
occurred, event log records are no longer being output receiver.
to the specified receiver.
System action: None. ANR1830E receiverName receiver options not defined
in the server options file.
Explanation: A BEGIN EVENTLOGGING command
has been entered for a receiver, but the required
ANR1823I Event logging ended for all receivers. receiver options were not specified in the server
Explanation: In response to an END options file.
EVENTLOGGING command, event log records are no System action: Logging is not started for the specified
longer being output to any receiver. receiver.
System action: None. User response: Enter the receiver options in the server
User response: None. options file and restart the server.
ANR1824E Event logging is inactive for the ANR1831I Event logging of client events ended for
specified receiver. ACTLOG receiver.
Explanation: An END EVENTLOGGING command Explanation: An END EVENTLOGGING command

has been entered, but logging is not active for the has been entered for the activity log receiver.
specified receiver. System action: The server no longer records client
System action: The command is ignored. events in the activity log. Server events continue to be
recorded in the activity log.
User response: If logging is desired, use the ENABLE
EVENT and BEGIN EVENTLOGGING commands to User response: None.
activate event logging.

ANR1842E An error occurred on the receiverName ANR1851E The source trail for server to server
receiver. event logging has exceeded the
maximum length of Maximum sourcetrail
Explanation: An error occurred on the specified
length bytes.
receiver.
Explanation: While attempting to log an event to the
System action: The server no longer sends events to
event server, the server has found that the source trail
the receiver.
length is too long.
User response: Issue a BEGIN EVENTLOGGING
System action: The server continues to try to send the
command for the receiver to attempt to start logging
event to the event server, but the source trail may be
events to the receiver again.
truncated and appear something like:
ANR1843I Fasp monitor collector finished and name1>...>namex>namey

exiting. where,
name1 is the originator of the event.
Explanation: The Fasp monitor processing collector is
... is where intervening server name(s)
terminating processing because the Fasp monitoring
have been left off the source trail.
function has been set to off or the system is shutting
down.
User response: Most likely you are using very long
System action: None, the Fasp monitor collector
server names and/or have excessive hops from server
terminates.
to server. Either use shorter server names or change
User response: The Fasp status processing was turned your configuration to reduce the number of hops.
off using the SET MONITORFASP command.
ANR1852E Unable to send header to TEC at TEC
ANR1844I Eventlog command command processed. server rc return code
Explanation: The specified command was processed. Explanation: A network error has occurred in
attempting to send the event header to the Tivoli
System action: None. Enterprise Console.
User response: If any previous messages indicate that System action: None.
parts of the command failed, reissue the command for
those parts only. User response: Verify network connections and
contact your service representative if this error persists.
ANR1850E Circular event logging detected. The

event server has previously handled ANR1853E Unable to send data to TEC at TEC
event Event number from Source trail. To server rc return code
prevent looping, events which have
Explanation: A network error has occurred in
already been logged by the event server
attempting to send the event data to the Tivoli
are not sent again. Please correct the
Enterprise Console.
situation causing circular logging to
avoid wasting system resources. System action: None.
Explanation: The server is attempting to log an event User response: Verify network connections and
which has previously been handled by the event server contact your service representative if this error persists.
that is currently defined.
System action: The event is not sent to the event ANR1854E Unable to flush data to TEC at TEC
server. Other events will still be sent, and this message server rc return code
will be issued periodically if this situation is detected
Explanation: A network error has occurred in
again.
attempting to flush data to the Tivoli Enterprise
User response: Determine what is wrong with the Console.
server to server event logging setup, and fix the
problem.
User response: Verify network connections and

User response: Enter 'Y' to audit the volume or 'N' to

ANR1855E Failure validating protocol between
stop the process.
client and server for node node on
session session number
ANR1859W Node node on session session id received
Explanation: For a node having the "VALIDATE
CRC protocol validation information
PROTOCOL" option set to either "DATAONLY" or
when it is not configured to do so.
"ALL", a validation error occurred. The transaction is
aborted and an indication is sent to the client indicating Explanation: The server received protocol validation
the failure. information for the session and node specified. The
settings for this node are not configured to perform
protocol validation and any CRC information received
User response: Verify network connections and will be ignored.
User response: The server administrator should
ANR1856W Command: No volumes selected to
evaluate whether or not this node should perform
process.
protocol validation. If so, issue the UPDATE NODE
Explanation: No volumes were eligible for processing command and specify the VALIDATEPROTOCOL
by the AUDIT VOLUME command based upon the option with the appropriate setting to enable protocol
parameters specified. validation.
System action: The AUDIT VOLUME process ends If this is a TYPE=SERVER node for the target of a
without processing any volumes. virtual volume operation and protocol validation is not
desired, the server definition on the source server
User response: Review the parameters specified for
should be updated with VALIDATEPROTOCOL=NO
the command. If there was an error specifying a
set. Otherwise, if protocol validate is desired, the
parameter, re-issue the command with the parameter
SERVER type node on the target server should be
corrected.
updated using the UPDATE NODE command with
VALIDATEPROTOCOL=ALL.
ANR1857I AUDIT VOLUME will start count repair
processes.
ANR1860E Drive with serial serial element element
Explanation: The AUDIT VOLUME command will port port and target target lun lun does
process a range of volumes due to one or more of the not match with the library libraryPath .
following parameters having been specified:
Explanation:
FROMDATE, TODATE, or STGPOOL. The AUDIT
VOLUME processing will start a process for each System action:
volume that qualifies and process an AUDIT VOLUME
User response:
for each volume with FIX=YES specified.
System action: One or more volumes are audited and
ANR1861E Drive with element element port port and
inconsistent data is discarded.
target target lun lun does not match with
System action: The administrator is asked whether to the library libraryPath .
continue.
Explanation:
System action:
stop the process.
User response:
ANR1858I AUDIT VOLUME will start count
inspect processes. ANR1862W command: This command will remove all
replication information for the server
Explanation: The AUDIT VOLUME command will
with ID Unique ID.
process a range of volumes due to one or more of the
following parameters having been specified: Explanation: All replication information stored on this
FROMDATE, TODATE, or STGPOOL. The AUDIT server that references the indicated server will be
VOLUME processing will start a process for each deleted. Subsequent replications to the indicated server
volume that qualifies and process an AUDIT VOLUME may cause data to be re-sent.
for each volume with FIX=NO specified.
System action: The system asks whether you wish to
System action: The administrator is asked whether to continue with the REMOVE REPLSERVER command.
continue.
User response: To process the REMOVE REPLSERVER

command, enter 'Y' to continue or 'N' to stop the command completes. Statistics on the number and type
process. of objects moved, together with the total number of
bytes copied, are displayed on the server console
following this message. A summary of the number of
ANR1863E library libraryPath and serial serial does
files that were skipped is also displayed.
not support Read Element Status
command. It is very old and should be User response: None.
replaced with newer model.
Explanation: ANR1868I Export/import command: Copied filespace
number file spaces archive number archive
System action:
files, backup number backup files, and
User response: spacemg number space managed files.
ANR1864E library libraryPath does not support Read process to service the command export/import command
Element Status command and it does copies filespace number client file space definitions,
not have a serial number. It is very old archive number archive file copies, backup number backup
and should be replaced with newer file copies, and spacemg number space-managed files
model. from either the server database to export media or from
import media into the server database. Data is not
Explanation: actually moved if Preview=Yes is specified in the
System action: command export/import command.
User response: System action: Export or import processing for the

ANR1865I export command : Summary for User response: None.

Restartable Export operation export
identifier : ANR1869W Export/import command: Skipped archive
Explanation: A summary of the total number of number archive files, backup number
objects transmitted in the restartable export operation backup files, and spacemg number space
with export identifier is displayed following this managed files.
message. Explanation: The background export or import
System action: Export processing for the command process to service the command export/import command
ends. Server operation continues. skipped archive number archive file copies, backup
number backup file copies, and spacemg number
User response: None. space-managed files from either the server database to
export media or from import media into the server
ANR1866I Export/import command: Processing database. Data is not actually moved if Preview=Yes is
suspended with status status. specified in the command export/import command.
Explanation: The background process to service the System action: Export or import processing for the
command command was suspended with a SUSPEND command completes. Server operation continues.
command. User response: Check previous messages for the
System action: Processing for the command command names of the files that were not exported or imported,
stops. Statistics on the number and type of objects and problem determination information.
are displayed on the server console following this ANR1870I Export/import command: Copied number
message. bytes of data.
ANR1867I Export/import command: Processing copies number bytes of data from the server database
completed with status status. and data storage to the export media or from the
export media to the server database and data storage.
Explanation: The background export or import Data is not moved if Preview=Yes is specified in the
process to service the command export/import command command export/import command. This figure can be
has completed with status status. If the status is used during export preview processing to estimate the
INCOMPLETE, some files have been skipped due to number of removable media volumes needed to hold
errors reading or writing the file. the exported information from the server.
System action: Export or import processing for the System action: Export or import processing for the

command completes. Server operation continues. database and data storage to the export media or from
ANR1871I Export/import command: Copied number volumes needed to hold the exported information from
kilobytes of data. the server.
Explanation: The background export or import System action: Export or import processing for the
process to service the command export/import command command completes. Server operation continues.
copies number kilobytes of data from the server
storage. This figure can be used during export preview ANR1875I Export/import command: Detected number
processing to estimate the number of removable media errors.
the server.
System action: Export or import processing for the detects number errors while copying information from
command completes. Server operation continues. the server database and data storage to the export
media or from the export media to the server database
and data storage.
megabytes of data.
prior to this message to view the error. Use the QUERY
copies number megabytes of data from the server
for messages.
storage. This figure can be used during export preview ANR1876W Export/import command: Detected an
processing to estimate the number of removable media unexpected value, value, for the
volumes needed to hold the exported information from data-transfer path option setting for node
the server. node name. The default value of 'ANY' is
used for the node.
command completes. Server operation continues. Explanation: The export or import operation detected
an unexpected data-transfer path value for the node. As
a result, the default value of 'ANY' is used for the node
and indicated data-transfer path option.
gigabytes of data.
User response: If the data-transfer path setting of
'ANY' is acceptable for the node, do nothing further. If
copies number gigabytes of data from the server
you must change the setting, use the UPDATE NODE
command.
processing to estimate the number of removable media ANR1877E NAS backup process terminated - NAS
volumes needed to hold the exported information from file server NAS file server name reported
the server. illegal arguments.
System action: Export or import processing for the System action: The indicated process ends.
User response: Verify the that the filespace exists on
User response: None. the NAS file server. If backing up a NAS virtual
filespace verify that the path specified in the virtual
filespace exists.
terabytes of data. For details about how to identify the cause of the
terminated NDMP operations, see the NAS file-server
documentation. Check the NDMP logs for the NAS file
copies number terabytes of data from the server

server and correct the cause of the errors and restart User response: Issue the REMOVE REPLSERVER
the operation. command with a more specific replication server ID
value such that only one matching server ID is selected.
ANR1878E A database manager configuration
parameter cannot be updated. The value ANR1880W Server transaction was canceled because
of the DIAGSIZE parameter is greater of a conflicting lock on table table name.
than the amount of free space available
Explanation: The server online reorganization for the
in the database manager's diagnostic
referenced table could not be completed because of a
data directory.
lock conflict between the reorganization process and a
Explanation: The error occurred because the current server process. The server process was canceled to
value of the DIAGSIZE database manager configuration allow the reorganization process to be completed. In
parameter is greater than the amount of free space in some cases, the server might need to cancel multiple
the drive or the file system that contains the diagnostic server processes to resolve the lock conflict.
data directory. Consequently, this message might be displayed
multiple times as server processes are forced to stop. In
System action: The operation fails. Depending on the
addition, other server application error messages might
configuration parameter that is being updated, the
be displayed as the lock conflicts are resolved.
server might stop.
System action: The server will continue to operate;
User response: Complete one of the following options:
however, until the lock conflict is resolved, no new
v Specify a smaller value for DIAGSIZE. reorganizations will be started.
v Change the location of the diagnostic data directory
User response: Review the server activity log and
to a drive or file system that has more free space.
determine whether a critical server operation was
v Increase the amount of free space on the drive or file canceled that should be restarted. If so, restart the
system containing the diagnostic data directory. server operation.
To check the current setting of the DIAGSIZE

configuration parameter, issue the following database ANR1881E Command or operation: Failure because the
command: LDAPUSER password is expired.
Explanation: The password credentials for the user
db2 get dbm cfg account specified as the LDAPUSER are expired and
need to be updated.
and search for "DIAGSIZE".
To change the value of the DIAGSIZE configuration User response: The administrator for the LDAP
parameter, issue the following command: directory server must update the password for the
LDAPUSER account in the LDAP directory server.
db2 update dbm cfg using DIAGSIZE new_size Then, after the LDAP administrator updates the
password, issue the LDAPPASSWORD command to
new_size is the value, in megabytes, of the DIAGSIZE match the new password. Reissue the command that
configuration parameter. The value must be 2 or failed.
greater.
ANR1882E Command or operation: A password was
For more information, see "Locating DB2 diagnostic log reset and must change while accessing
files" in the product information (http:// the LDAP administrator or node entry
www.ibm.com/support/knowledgecenter/SSEQVQ/). admin or node name with administrator/node
name or LDAPUSER credentials.
ANR1879E command: Multiple replication server IDs Explanation: The password credentials used for this
match the specified ID pattern. operation were reset and you must update the
Explanation: During a REMOVE REPLSERVER password on the LDAP directory server.
command, a wildcard was used for the replication System action: The operation requires a password
server ID. This resulted in more than 1 matching server update.
ID. To avoid accidental erasure of replication
information, only a single replication server ID can be User response: If the operation used the LDAPUSER
removed at a time. credentials, update the password for the user account
specified as the LDAPUSER in the LDAP directory
System action: The command is terminated by the server. If the operation used node or administrator
server. credentials, a password expiration status is issued to
force a password update.


ANR1883E Command or operation: An access failure
occurred while accessing the LDAP User response: The IBM Spectrum Protect server tried
administrator or node entry admin or node an operation with the LDAP directory server and the
name with administrator/node name or operation failed because the entry could not be found.
LDAPUSER credentials. To insert a new entry for this node or administrator,
issue an UPDATE NODE or UPDATE ADMIN
Explanation: The command failed after the IBM
command and provide a password.
Spectrum Protect server accessed an entry in the LDAP
directory server and received a locked account error.
ANR1887E Command or operation: Failure when
working with the LDAP directory
User response: If the operation used the LDAPUSER server.
credentials, unlock the user account specified as the
Explanation: The command or operation failed
LDAPUSER in the LDAP directory server. If the
because of an error returned by the LDAP directory
operation used a node or administrator credentials,
sterver.
unlock the node or administrator by issuing the
UPDATE NODE or UPDATE ADMIN command with a System action: The operation fails.
password or directly unlock the node or administrator
account in the LDAP directory server. User response: The IBM Spectrum Protect server ran
an operation with the LDAP directory server and the
operation failed. Specific error details are contained in
ANR1884E Command or operation: An authentication previous messages. The common causes of LDAP
failure occurred with the LDAP failures are as follows:
directory server when the LDAPUSER v A communication error occurred with the LDAP
credentials were used. directory server
Explanation: The IBM Spectrum Protect server tried to v The LDAPURL is invalid or missing (wrong
authenticate and access was denied. hostname or base DN)
System action: The operation fails. v The LDAPUSER is invalid or missing (wrong value
or locked)
User response: Validate that the LDAPUSER, the
v The LDAPPASSWORD is invalid or missing (wrong
LDAPPASSWORD, and the LDAPURL are set to the
value or expired)
correct values. Correct any invalid setting and reissue
the command or operation.
Update the LDAP directory server settings or contact
your LDAP administrator to resolve this issue
ANR1885E Command or operation: Permission was
denied when the LDAP administrator or
node entry admin or node name was ANR1888W Session session number for node node
accessed as administrator/node name or name (client platform) refused - client
LDAPUSER. requires SSL connection with this
server.
Explanation: The command failed after the IBM
Spectrum Protect server authenticated with the LDAP Explanation: No SSL connection was established,
directory server as the LDAPUSER. Permission was therefore the server did not start a client session
denied when the server tried to add, modify or delete because the client node or admin requires an SSL
an entry in the LDAP directory server. connection.
System action: The operation fails. System action: Server operation continues.
User response: The user specified by the LDAPUSER User response: Configure the client to use SSL or
needs full access control over the distinguished name update the node or admin definition on the server such
(DN) specified in the LDAPURL server option. Correct that SSL is not required (update SSLREQUIRED
the access control rights of the LDAPUSER or provide a parameter). If the node is created with
different LDAPUSER who has full access control rights SSLREQUIRED=SERVERONLY, a corresponding admin
over the IBM Spectrum Protect server's DN. definition is created with SSLREQUIRED=YES. To use a
non-SSL session with a storage agent, rename the
admin with the identical name by issuing the RENAME
ANR1886E Entry entry name was not found in the ADMIN command.
LDAP directory server.
Explanation: The command failed because the IBM
Spectrum Protect server tried an operation on an LDAP
entry that was not found on the LDAP directory server.

ANR1889W Session session number was terminated ANR1892W Process process ID for process name
during backup for node node name (client completed with a completion state of
platform), with file space filespace id or SUCCESS but warning or more-severe
name because a restore operation is in messages were issued.
progress.
Explanation: The process completed with a
Explanation: During a file backup operation, the completion state of SUCCESS but warning messages or
server ends a node session because one or more files more-severe messages were issued by this process. This
are locked by a restore operation. process may not have completed all of the processing.
System action: The backup session is terminated by System action: None.
the server.
User response: Review the messages in the activity
User response: Issue the QUERY RESTORE command and event logs that were issued by this process.
with FORMAT=DETAILED to determine if the restore Determine if the conditions that caused these messages
operation is active or is in a restartable state. A to be issued had an affect on the operation.
restartable restore operation keeps files locked until the
amount of time that is specified for the
ANR1893E Process process ID for process name
RESTOREINTERVAL server option is reached. You can
completed with a completion state of
lower this value to free up locked files. Issue the
FAILURE.
QUERY OPTION command to display the current
setting for the RESTOREINTERVAL option. Explanation: The process completed with a state of
FAILURE.
If you received this message due to a client backup
operation, restart the operation after the restore System action: None.
operation has completed in order to move any
remaining files. You can also cancel the restartable User response: Review the messages in the activity
restore session with the CANCEL RESTORE command. and event logs that were issued by this process.
Determine the conditions that caused these messages to
be issued, resolve those issues and retry the operation.
ANR1890W Backup operation for session session
number node client node name failed due
to root-only restriction. ANR1894E command: Processing for node node name,
file space file space name failed because
Explanation: The backup operation failed because a of a lock conflict.
non-root user attempted the operation. A restriction is
in place to disallow backup operations by non-root Explanation: The server could not obtain a resource
users for the indicated node. that is required to process the indicated file space.
System action: The backup operation is terminated. A System action: The command continues, but
message is issued by the client. For clients that are processing of the indicated file space fails.
levels prior to 6.3, message ANS0350E may appear. User response: To increase the probability of acquiring
User response: Retry the backup operation as the root all of the necessary resources, issue the indicated
user. command when server activity is relatively low.
ANR1891E Command or operation: The operation ANR1895W Command or operation: The password for
cannot be completed when the the node node name now uses
Lightweight Directory Access Protocol case-sensitive passwords.
(LDAP) mode is set to Integrated. Explanation: The node is authenticating with an
Explanation: In Integrated mode, the LDAP directory LDAP directory server. The LDAP authentication
cannot be modified, except to delete users or change password policy is dictated by the LDAP directory
passwords. To delete users or change passwords, the server and this usually requires passwords to be
user ID that is specified with the SET LDAPUSER case-sensitive.
command must have sufficient authority. System action: None.
System action: The operation fails. User response: None.
User response: Run the operation by using LDAP
utilities instead of server commands.

Common incomplete configuration scenarios are as

ANR1896E Unable to allocate volume volume name
follows:
because it is still referenced in the
volume history. v LDAPURL values were not provided in the server
options file
Explanation: The volume cannot be allocated because
v The LDAPUSER is invalid (wrong value or locked)
the active volume history record shows the volume as
being in use. v The LDAPPASSWORD is invalid (wrong value or
expired)
System action: The active volume history record
shows the volume as being in use. Update the LDAP directory server information or
User response: The volume is being managed by the contact your LDAP administrator to resolve this issue.
server or it might be incorrectly referenced in the After completing the LDAP configuration, when you
volume history table due to out-of-date records. To add a node or admin with LDAP authentication, you
check the records and confirm the volume history are required to submit a new password when you log
status, issue the QUERY VOLHISTORY command. If on to the IBM Spectrum Protect server.
there is an invalid volume history record, use the
DELETE VOLHISTORY command to remove the ANR1900E Path between server server source and
record. If the DELETE VOLHISTORY command fails, library parm is not allowed.
contact IBM Software Support to remove the record.
Explanation: You must specify a path from the current
server to the library when you are defining the library.
ANR1897I LDAP password removed. You cannot specify a path from a different server.
Explanation: The password that the server uses to System action: The server ignores the command.
authenticate with the LDAP server was removed by the
SET LDAPPASSWORD command. User response: Reissue the command with a different
source or destination name or define a new path.
User response: None. ANR1901I The specified session is associated with
process name process process id and can
ANR1898I LDAP user name removed. not be cancelled.
Explanation: The LDAP user distinguished name Explanation: The server can not cancel the session
(DN) that the server uses to authenticate with the because it is associated with a running process.
LDAP server was removed by the SET LDAPUSER System action: Server operation continues.
command.
User response: The session can only be cancelled by
System action: None. cancelling the associated process. Use the CANCEL
User response: None. PROCESS command to cancel a process.
ANR1899W Command or operation: Unable to work ANR1902W Node node name on server server name is
with the LDAP directory server. not enabled for replication. It will not
be replicated.
Explanation: The command or operation finished, but
the IBM Spectrum Protect server did not work with the Explanation: The server is not able to replicate the
LDAP directory server because the LDAP directory specified node because the node on the specified target
server configuration is incomplete. If a node or server is not enabled for replication.
administrator was being created or updated on the System action: The node is not replicated to the
LDAP server, you cannot use it to logon until the specified server. Server operation continues.
server is able to use LDAP directory server
information. User response: Enable the node on the target server
for replication and rerun the replication command.
System action: The operation finished, but
information was not added to the LDAP directory
server. ANR1903E Export export name is not defined.
User response: An operation was run on the IBM Explanation: An NFS client attempted to mount the
Spectrum Protect server with the LDAP directory specified name as a mount point. The specified name is
server. The operation succeeded, but information was not currently being exported by the server.
not added to the LDAP directory server because the
System action: The server does not provide an export
LDAP directory server configuration is incomplete.
of the specified directory.

User response: Ensure that an NFS ADDEXPORT User response: Verify that the correct value have been
command was issued for the specified node. used. Update the value, if necessary.
ANR1904E Missing or invalid value for option. A ANR1909W Invalid value for option name option -
valid directory needs to be defined for option valuetype. The default value default
this. valuetype is used for this option.
Explanation: The server detects a missing or invalid Explanation: The value (option value) specified for the
value for a server option. A valid directory needs to be (option) option is not valid. The server uses the default
defined for this option. value for this parameter.
System action: Server initialization stops. System action: Server operation continues.
User response: Correct the error and restart the server. User response: Verify that the correct value have been
used. Update the value, if necessary.
ANR1905E Path dir name for parm does not exist or
is not empty. ANR1910E Directory directory name is already
defined for other path in the command.
Explanation: The directory specified does not exist or
is not empty. Explanation: While processing the command
argument list, a duplicate path name has been
encountered.
path name.
User response: Issue the command again, specifying a
directory that is not in the argument list.
ANR1906E Command: failed to extend the database
space.
ANR1911W Invalid value for option name option -
Explanation: A failure occurred during the extend
option valuetype . The default value
database space. This occurred during the processing of
default valuetype is used for this option.
a 'EXTEND DBSPACE' command.
Explanation: The value (option value) specified for the
(option) option is not valid. The server uses the default
User response: Review error messages to determine value for this parameter.
the cause of the failure and retry the 'EXTEND
DBSPACE' once the issue has been resolved. If unable
to determine the cause of the failure or to resolve it, User response: Verify that the correct value have been
please contact your IBM service representative for used. Update the value, if necessary.
further assistance.
ANR1912I Stopping the activity log because of a
ANR1907E The server can not resolve absolute path server shutdown.
of directory dir name. That path might
System action: Stopping the activity log because of a
not exist.
server shutdown.
Explanation: The directory specified does not exist or
is not accessible.
System action: The server operation stops.
ANR1913I command successfully started number of
User response: Reissue the command with a valid processes IDENTIFY processes.
path name.
System action: The server successfully started the
indicated number of IDENTIFY processes.
ANR1908W Invalid value for parameter parameter -
User response: Review the status of the identify
parameter valueMB. The default value
processes using the QUERY PROCESS or QUERY
default valueMB is used for this
ACTLOG commands.
parameter.
the (parameter) parameter is not a valid. The server uses
the default value for this parameter.
System action: Processing of the command continues
by using the default value.

ANR1914I command successfully ended number of ANR1919W Autocopy process process ID was
processes IDENTIFY processes. disabled for storage pool Storage pool
name . At least one storage pool in the
System action: The server successfully ended the
hierarchy is enabled for deduplication.
indicated number of IDENTIFY processes.
Explanation: All autocopy processes have been
User response: Review the status of the identify
disabled because at least one target storage pool is
processes using the QUERY ACTLOG command.
enabled for deduplication.
ANR1915I Autocopy process process ID started
transferring data to target storage pool User response: Either disable deduplication for all
storage pool name. storage pools in the storage-pool hierarchy or remove
the deduplicated storage pool from the autocopy
Explanation: An autocopy process to the named
storage-pool hierarchy.
active-data or copy storage pool has started.
ANR1920W A query for the number of HBA
User response: None. adapters has timed out with a current
value of timeout value.
ANR1916I Autocopy process process ID ended Explanation: The HBAAPI function to get the number
successfully for storage pool storage pool of HBA adapters failed with a time out.
name. Files Transferred: number of files,
Bytes Transferred: number of bytes.
User response: Check all of the HBA adapters on the
system and ensure that they are configured correctly.
active/copy storage pool has ended successfully.
Increase the SANDISCOVERYTIMEOUT value and try
System action: None. again. If the SANDISCOVERYTIMEOUT option is not
set, set it with a higher value.
ANR1921W A query for the name of an HBA

ANR1917E Autocopy process process ID failed for adapter has timed out with a current
storage pool storage pool name. Files value of timeout value.
Backed Up: number of files,Bytes
BackedUp: number of bytes. Result code: Explanation: The HBAAPI function to get a name
return code. from an FC adapter failed with a time out.
Explanation: An autocopy process to the named System action: None.

active/copy storage pool has ended in failure.
User response: Check all of the HBA adapters on the
System action: None. system and ensure that they are configured correctly. If
there is an FC adapter that is not functional, remove it
User response: Check the activity log for messages from the system and reconfigure the HBA driver. If
that were issued prior to completion. The messages there is no device on an FC port, increase the
may give more information about the failure. SANDISCOVERYTIMEOUT value and try again. If the
SANDISCOVERYTIMEOUT option is not set, set it with
ANR1918I Autocopy process process ID stopped for a higher value.
storage pool Storage pool name because of
a server error. ANR1922W A request to open an HBA adapter
Explanation: An autocopy process to the named timed out with a current value of timeout
active-data or copy storage pool has been disabled. value.
System action: None. Explanation: The HBAAPI function to open an FC

adapter failed with a time out.
User response: Check the activity log for messages
that were issued before the process stopped. The System action: None.
messages may give more information about the failure. User response: Check all of the HBA adapters on the
system and ensure that they are configured correctly. If
there is an FC adapter that is not functional, remove it
from the system and reconfigure the HBA driver. If
there is no device on an FC port, increase the
SANDISCOVERYTIMEOUT value and try again. If the


ANR1926W A SCSI inquiry has timed out after
a higher value.
timeout value seconds.
Explanation: A request to the HBAAPI library to
ANR1923W A query for fibre channel adapter
query SCSI devices has failed to respond within the
attributes has timed out after timeout
allotted time.
value seconds.
obtain attributes for a fibre channel (FC) adapter has User response: Ensure all devices connected to the
failed to respond within the allotted time. fibre channel (FC) adapters are operational. Remove
non-functional devices from the SAN and reconfigure
the devices on the system. If there is no device on an
User response: Ensure all fibre channel adapters on FC port, increase the SANDISCOVERYTIMEOUT value
the system are configured correctly. If there is an and try again. If the SANDISCOVERYTIMEOUT option
adapter that is non-functional, remove it from the is not set, set it with a value higher than the default
system. If there is no device on an adapter port, value.
increase the SANDISCOVERYTIMEOUT value to allow
the operating system sufficient time to respond. If the
ANR1927W Autocopy process process ID stopped for
storage pool Storage pool name . The data
a value higher than the default value.
format or device type was not
compatible with the data format or
ANR1924W A query for fibre channel (FC) port device type of the primary pool.
attributes has timed out after timeout
value seconds.
active-data or copy storage pool was disabled.
obtain port attributes for a fibre channel (FC) adapter
has failed to respond within the allotted time. User response: Use the QUERY STGPOOL command
to check the data format of the storage pools. Use the
QUERY DEVCLASS command to check the device
User response: Ensure all fibre channel adapters on types of the device classes associated with the storage
the system are configured correctly. If there is an pools.
adapter that is not functional, remove it from the
system. If there is no device attached to a particular
ANR1928W The file descriptor table for the SAN
adapter, increase the SANDISCOVERYTIMEOUT value
discovery process is full.
to allow the operating system sufficient time to
respond. If the SANDISCOVERYTIMEOUT option is Explanation: There might be too many paths that
not set, set it with a value higher than the default have been changed and updated by the SAN discovery
value. process.
ANR1925W A query for the fibre channel (FC) target
User response: Use one of the following methods to
mapping has timed out after timeout
resolve this problem:
value seconds.
v Use the SANREFRESHTIME option to increase the
Explanation: A request to the HBAAPI library to amount of time elapsed before the cached SAN
obtain target mappings for a fibre channel (FC) adapter discovery information is refreshed. For example:
has failed to respond within the allotted time. setopt sanrefreshtime 600.
System action: None. v Increase the nofiles (descriptors) in ulimit and
restart the IBM Spectrum Protect server.
User response: There might be too many devices to be
discovered, given the allotted time. If the
SANDISCOVERYTIMEOUT option is set, increase the ANR1929E Replication of node node name to target
value. If the SANDISCOVERYTIMEOUT option is not replication server target server failed. The
set, set the option to a value higher than the default replication mode of the source node is
value. SYNCSEND, and the node is not
defined on the target replication server.
Explanation: In order to replicate a node that is in
Sync Send mode the target node must exist on the
target replication server and be in Sync Receive mode.

System action: The replication of the node's data fails. determine if the restore operation is restartable on
Server operation continues. target replication server. A restartable restore operation
locks the files. The files cannot be moved until the
User response: Issue the REMOVE REPLNODE
value for the RESTOREINTERVAL server option is
command for the node on the source server, and then
reached. Use the QUERY OPTION command to display
issue the UPDATE NODE command and specify
the RESTOREINTERVAL value. You can lower the
ENABLED or DISABLED. The replication mode of the
RESTOREINTERVAL value to remove a restartable
node on the source replication server is automatically
restore operation earlier in the replication process and
set to SEND after the UPDATE NODE command is
to unlock the file space. Reissue the REPLICATE NODE
issued. After issuing the command, try the replication
command after the restore operation has completed to
operation again.
replicate any remaining files.
ANR1930E command: There are no eligible

ANR1934W REPLICATE NODE: Node node name is
filespaces for node node name.
disabled.
Explanation: The specified node has no applicable
Explanation: The requested node is disabled for
filespaces to be processed by the command.
replication, and has been skipped.
System action: The replication proceeds, but this node
User response: Check the command settings for the is skipped.
filespaces belonging to the node and retry the
User response: Enable the node for replication using
command.
the UPDATE NODE command and retry the
REPLICATE NODE command.
ANR1931E command: No replication-eligible data
was found for the specified nodes and
file spaces.
name (client platform) refused because the
System action: The operation ends. server initialization is not complete after
timeout value minutes.
User response: Verify that the specified nodes have
data and file spaces. Verify that replication is enabled Explanation: The specified session is refused because
for data types in file spaces that you want to replicate. the server initialization did not complete within the
To determine the replication status for a file space, use specified time.
the QUERY FILESPACE command .
System action: The session is ended and server
initialization continues.
ANR1932I command: A NAS backup image for node
User response: Allow some time for the server
node name, file space filespace name was
initialization to complete and retry the session. If this
skipped for replication.
message occurs regularly, consider increasing the value
Explanation: The replication process has determined of the SESSIONSERVERINITTIMEOUT option in the
that a NAS backup image is not eligible for replication server options file.
because the image, or one of its dependent files is
stored in a non-native storage pool.
ANR1936E Replication of data type data for file
System action: Replication processing continues. space filespace name (fsId filespace id) on
node node name failed with reason:
User response: No action is required. reason.
Explanation: The server could not replicate the
ANR1933W Replication of BACKUP data for file specified file space for the reason indicated in the
space filespace name on node node name message text.
skipped because of a restore operation
on target server target server. System action: The command continues, but
replication of the file space fails.
Explanation: During replication processing, the file
space on target replication server has a pending restore User response: Review the reason for the failure and
operation. Files can not be stored into the file space correct the problem, if possible. Then rerun the
while the pending restore is active. REPLICATE NODE command.
System action: The files are not replicated on the
target replication server.
User response: Use the QUERY RESTORE command
and specify the FORMAT=DETAILED parameter to

ANR1937I Failover Session session num for replica ANR1942W Option set option set name already exists.
node nodename (platform) is enabled for Skipping for replication from source
store operations. server source server name.
Explanation: The specified replica node is in failover Explanation: A new option set which is referenced by
mode and is now elgible for store operations. a replicating node is not replicated because an option
set with the same name already exists on this server.
System action: Any store operations request by the
The option set is not a replica of the option set for the
client on this session will be allowed to proceed.
source server.
User response: In order to repicate the required option
ANR1938W The next storage pool is no longer
set, consider copying the option set to an option set
defined for source pool storage pool name.
with a different name an update the replicating node to
Explanation: The storage pool that is being migrated reference the new option set.
no longer has a next storage pool to migrate data to.
System action: The migration fails because there is no ANR1943I Replicated option set option set name
target storage pool. being updated with option set from
source server source server name.
User response: Ensure that the storage pool being
migrated has a next storage pool before running any Explanation: An existing replicated option set on this
further migration operations. server is updated with an option set with the same
name from the source server.
ANR1939W Session session number for node node System action: Server operation continues.
name (client platform) No failover server
User response: None
information currently exists for this
node.
ANR1944I Replicating option set option set name
Explanation: No failover server is identified for the
with option count options needed by
node. The client removes any failover configuration
node referencing node to server target
that is stored in the client options file.
server.
Explanation: An option set on this server is replicated
User response: To ensure that failover can occur, to a target server because it is referenced by a node
replicate this node to a secondary server. which is being replicated.
ANR1940E Source file(line number): Unique ID
User response: None
generation failed with Return code.
Explanation: An internal error occurred when a
ANR1945I Option set option set name successfully
unique ID is created. This error message always
replicated to server target server.
accompanies another error message which provides
more details about the error. Explanation: An option set on this server has been
successfully replicated to the target server.
User response: Review the reason for the failure and
correct the problem, if possible. User response: None
ANR1941I Replicating option set option set name ANR1946W Option set option set name already exists
from source server source server name. on target server target server and is not
replicated.
Explanation: A new option set which is referenced by
a replicated node is is created by the replication process Explanation: An option set on this server could not be
from the definition on the source replication server. replicated to the target server because an option set
with the same name already exists on the target server.
User response: A node that is replicated references an
option set that exists on both the source and target
servers. Determine which option set is used on the

target server. When you decide which option to use,

ANR1950W Device type device type in device class
rename the definition on the other server by copying it
device class is not supported during a
to a new option set name and deleting the original
migration from z/OS to AIX, or from
option set.
z/OS to Linux on System z. The device
class will be skipped.
ANR1947E Replication of option set option set name
Explanation: During a migration from z/OS to AIX,
to target server target server failed. See
or from z/OS to Linux on System z, a device class was
activity log on target server for possible
encountered that had a device type that is not
errors.
supported on the target platform.
Explanation: An error occurred on the target server
System action: The device class will not be added to
while replicating the specified option set.
the target database.
User response: No action is required..
User response: Check the activity log of the target
server for possible errors.
ANR1951W Device class device class uses a recording
format format (format code) that is not
ANR1948W Volume mount request for volume name supported for device type device type.
denied - server operation cannot wait FORMAT=DRIVE will be used instead.
for the volume.
Explanation: If an operation acquired a volume and a or from z/OS to Linux on System z, a device class was
second operation waits for that same volume, the first encountered that uses a recording format that is not
operation does not wait to acquire any other volumes. supported by the device type on the target platform.
If the first operation was allowed to wait for another
System action: The recording format will be replaced
volume, a deadlock could occur.
with FORMAT=DRIVE.
System action: Server operations continue, volume
User response: Verify whether FORMAT=DRIVE
acquisition may be tried again, including attempts to
supports your media type. If not, update the device
mount scratch tapes, but the server operation does not
class, specifying a supported recording format.
wait to acquire the volume.
User response: If the server operation succeeds, no
ANR1952I Library library name was added to the
action is required. However, if the operation fails, you
definition of device class device class.
need to supply more scratch tapes to the storage pool.
or from z/OS to Linux on System z, a device class
definition was updated to include a library that will be
name (client platform) refused - the node
used for accessing media through the z/OS Media
has a unicode filespace but the client
Server.
does not use unicode.
System action: The device class will be modified to
Explanation: The server cannot accept the client
use the new library.
session because the client's platform does not use
unicode and the node already contains a unicode User response: No action is required.
filespace. The server records whether or not the client's
data is unicode, and does not let the node change this
ANR1953E command: target platform cannot be the
attribute.
target of a database upgrade from source
System action: Server operation continues, but the platform.
node session is refused.
Explanation: A cross-platform database upgrade is not
User response: Logon to the server from a client with supported between the indicated source and target
a platform that uses unicode data. For example, the platforms.
original platform that was used to create the existing
System action: The INSERTDB command stops.
filespaces for this node. Alternatively, if the client node
needs to change to the platform that is currently being User response: Rerun the INSERTDB command on a
attempted, remove the existing filespaces that contain supported platform.
unicode data and try the node connection again.


ANR1954W Library definition library was not sent to
downlevel storage agent stagent. User response: None.
Explanation: The storage agent has requested a
definition for a library type that is not supported and ANR1958I Command: Administrator administrator ID
the server has not sent the definition. is already registered and locked.
System action: The storage agent does not process the Explanation: An import process is trying to import an
library definition. administrator ID that is registered and locked on the
server.
User response: Upgrade the storage agent to a level
that supports the library type. System action: The process continues without
importing the ID.
ANR1955E The level of DB2 installed on the User response: Unlock admin ID ADMIN_CENTER or
system (current db2 level) is lower than log off the administrator. Try the operation again.
the required level (required db2 level).
Explanation: The DB2 level on the system does not ANR1959I Status monitor collecting current data at
meet the requirements for this server. The server time.
package includes the required DB2 level which is
installed along with the server. If the DB2 level is Explanation: The status monitor processing is
incorrect, it is possible that DB2 failed to upgrade collecting a current set of data for the server at the
during the server upgrade process. indicated time.
System action: The server stops. System action: The process collects the monitored
status data elements.
User response: To resolve the issue, complete the
following steps: : User response: The monitor status processing is
enabled using the SET MONITORSTATUS command.
v 1. Verify the level of DB2 installed on the system: The interval with which it collects data is controlled by
Run 'db2level' the SET STATUSREFRESHINTERVAL. If the status data
v 2. Review the installation log files to determine the is being collected too frequently, increase the collection
problem that caused the DB2 upgrade failure. interval. Note that the administrative graphical user
v 3. Fix the problem and install the server again. interface relies upon this data, do not turn off the status
monitor processing if this interface will be used for the
v Do not alter the DB2 software that is installed with
administration of IBM Spectrum Protect.
IBM Spectrum Protect installation packages and fix
packs. Do not install or upgrade to a different
version, release, or fix pack of DB2 software. If you ANR1960I Status monitor finished collecting data
are unable to fix the problem, contact IBM Software at time and will sleep for refreshinterval
Support. minutes.
Explanation: The status monitor processing finished a
ANR1956W The password for the administrator data collection cycle and will sleep for the indicated
administrator name is expired. number of minutes before waking up and attempting
to process again.
Explanation: The administrator is attempting to open
a session to a remote server. The password is expired System action: The status monitor data collection
on the local server. process is idle.
System action: Operation continues. The remote User response: The monitor status processing is
session may be refused. enabled using the SET MONITORSTATUS command.
The interval with which it collects data is controlled by
User response: Update the password at your earliest
the SET STATUSREFRESHINTERVAL. If the status data
convenience.
is being collected too frequently, increase the collection
interval. Note that the administrative graphical user
ANR1957W Command or operation: The password for interface relies upon this data, do not turn off the status
the administrator administrator name now monitor processing if this interface will be used for the
uses case-sensitive passwords. administration of IBM Spectrum Protect.
Explanation: The administrator is authenticating with
an LDAP directory server. The LDAP authentication
password policy is dictated by the LDAP directory
server and this usually requires passwords to be
case-sensitive.

ANR1961I Status monitor collector finished and ANR1965E Command: You requested to add or
exiting. remove filespace filespace name for the
node collocation group collocation group
Explanation: The status monitor processing collector is
name. Filespaces cannot be added to or
terminating processing because the status monitoring
removed from node collocation groups.
function has been set to off.
Explanation: The command was issued and the
System action: None, the status monitor collector
specified collocation group exists. However, the
terminates.
collocation group is a node collocation group and a
User response: The monitor status processing was filespace cannot be added to or removed from a node
turned off using the SET MONITORSTATUS command. collocation group.
As a result of this, the administrative graphical user
System action: Server operations continue, but the
interface will not be able to manage this server.
User response: Issue the command and specify a
ANR1962W command: This command is being routed
registered collocation group that can contain filespace
to one or more servers, so its potential
collocation group members.
effect cannot be determined. Depending
on the parameters that you specify, the
command can be destructive or can ANR1966E Command: Specify the filespace name for
produce a large amount of output. the collocation group collocation group
Destructive commands can halt the name.
server, delete data, or change data
Explanation: You did not provide the filespace name
placement or retention policies.
for the filespace collocation group. When you add or
Explanation: The command is destructive or produces remove a collocation group member in a filespace
a large amount of output. collocation group, you must provide the filespace name
for the collocation group.
System action: IBM Spectrum Protect prompts the
user to continue. System action: Server operations continue, but the
User response: Enter 'Y' to continue with the
command. Enter 'N' if you do not want to continue User response: Issue the command again and specify
with the command. the filespace name for the filespace collocation group.
ANR1963E command: This command cannot be ANR1967E Command: The filespace name cannot be
issued from the server console. a wildcard character when you specify
the NAMEType parameter for a
Explanation: This command cannot be issued from the
filespace collocation group.
server console because it may require a long time to
complete and the server console should be available to Explanation: The command was issued, but there is a
control other server functions. mismatch between the filespace name and the
NAMEType value. When you specify the NAMEType
value, the filespace name must be partially-qualified or
fully-qualified.
User response: Issue the command from an
ANR1964W command: This command may produce a
partially-qualified or fully-qualified filespace name in
large amount of output.
combination with the NAMEType parameter.
Explanation: A command has been invoked that could
potentially produce a large amount of output.
ANR1968E Command: The filespace name filespace
System action: The administrator is asked whether to name is not valid. The filespace name
continue. must be the wildcard character when
you specify the CODETType parameter
command or 'N' to terminate the command. Explanation: The command was issued, but there is a
mismatch between the filespace name and the
CODEType value. When you specify the CODEType
value, the filespace name must be a wildcard character.


ANR1972W Command: No new file space associations
were added to the collocation group.
Explanation: The specified command was issued but
wildcard character for the filespace name in
no new file space associations are defined for the
combination with the NAMEType parameter.
collocation group.
ANR1969E Command: filespace name is not a valid
command has no effect.
filespace ID. Filespace IDs must be
numeric values when the NAMEType User response: Issue the command and specify
parameter is FSID. different filespaces.
Explanation: The command was issued, but the list of
filespace IDs are not numeric. When you specify the ANR1973W Command: Nodes in the NODE
NAMEType=FSID parameter, the filespace names in the parameter list node list may not contain
filespace name list must contain only numbers. wildcard characters when dealing with
filespace groups. No filespace
associations were deleted from the
collocation group.
User response: Issue the command and specify a list
of filespace IDs that contain only numbers.
no file space associations are deleted.
ANR1970E Command: An invalid node name list
node name was specified. A single node
name must be specified when working User response: Issue the command and specify a valid
with filespace collocation group client node without wildcards.
members.
Explanation: The command was issued, but the list of ANR1974W Command: Filespaces in the FILESPACE
node names is invalid. When working with filespace parameter list filespace list are not
collocation group members, only one node name can be associated with the filespace collocation
specified. group collocgroup name. No filespace
associations were deleted from the
collocation group.
no file space associations are deleted.
single node name.
ANR1971W Command: No matching file space was
found for file space filespace name on User response: Issue the command and specify
node node name using the specified different filespaces.
NAMEType and CODEType parameters.
Explanation: The server did not find a matching file ANR1975W Node node name is already associated
space name or file space ID for the file space and node with node collocation group node
that are specified in the command. collocation group name. File spaces that
belong to same node name cannot be
added to the user specified collocation group
User response: Enter the command with file space collocation group.
names or file space IDs that refer to defined file spaces
for the specified node. Note that file space names are
the DEFINE COLLOCMEMBER command that is used
case sensitive. Enter the file space names by using
for creating file space collocation group members. Node
exactly the same upper- and lowercase characters that
node name is already associated with the node
match the file space name that is defined on the server.
collocation group name collocation group name and file
File space name searches are also sensitive to
spaces that belong to a node that is already in a node
NAMEType (SERVER, UNICode, FSID) and CODEType
collocation group cannot be added to a file space
(BOTH, UNICode, NONUNIcode) parameters. Issue the
collocation group. The indicated file spaces are not
QUERY FILESPACE command to determine which file
processed.
spaces and file space IDs are defined for a node on the
server. System action: Server operations continue.

User response: If the node name was entered

ANR1980I File space filespace name is disassociated
incorrectly, issue the command again with the correct
from filespace collocation group
node name.
collocation group name.
ANR1976I Command: number of filespace members are
the DELETE COLLOCMEMBER command. Filespace
defined in the collocation group
filespace name is no longer associated with the filespace
collocation group name collocation group name.
Explanation: A DEFINE COLLOCMEMBER command
created the specified number of filespace members in
the indicated collocation group. User response: None.
ANR1981I Command: number of filespace filespace
members were deleted from filespace
collocation group collocation group name.
ANR1977I File space filespace name on node node
Explanation: A DELETE COLLOCMEMBER command
name is associated with filespace
has deleted the specified number of filespace members
from the indicated collocation group.
the DEFINE COLLOCMEMBER command. File space
filespace name on node node name is associated with the User response: None.
filespace collocation group name collocation group name.
System action: Server operations continue. ANR1982W File space filespace name exists on node
node name but the filespace is not a
member of the specified collocation
group collocation group name.
ANR1978W File space filespace name on node node
name is already associated to filespace
the DELETE COLLOCMEMBER command. Filespace
filespace name is not associated with a filespace
Explanation: This message is displayed in response to collocation group with the name collocation group name.
the DEFINE COLLOCMEMBER command. Filespace The indicated filespace is not processed. The other
filespace name is already associated with a filespace filespaces can be processed if specified by the
collocation group with the name collocation group name. command.
The indicated filespace is not processed. The other
filespaces can be processed if specified by the
command. User response: If the filespace name was entered
filespace name.
User response: If the filespace name was entered
ANR1983W The collocation group collocgroup name
filespace name.
exists, but the node name in the
parameter list node name is not
ANR1979W Node node name is already associated to associated with the collocation group.
one or more filespace collocation groups No filespaces are associated with the
and cannot be associated to a node collocation group.
collocation group.
Explanation: This message is displayed in response to no file spaces are associated with the collocation group.
the DEFINE COLLOCMEMBER command. Node node
name is already associated with at least one filespace
collocation group name. The indicated node is not
processed. The other nodes can be processed if User response: Issue the command and specify
specified by the command. different nodes.
node name.

log on both servers for messages that are related to

ANR1984E command: Replication server server name
remote monitoring.
is in use by an active replication process
and cannot be removed.
ANR1988W The remote monitoring session for
Explanation: When you issue the REMOVE
server server name was refused - server is
REPLSERVER command, the replication server that you
down-level.
specify to remove is in use by an active replication
process. You cannot remove a replication server that is Explanation: The specified remote server cannot be
used in an active replication process. monitored because it must be V6.3.4 or later.
System action: The command is stopped by the System action: Server operation continues.
server.
User response: Upgrade the specified remote server or
User response: Issue the QUERY PROCESS command remove it from the remote monitoring server group
from the source replication server or the target using the DELETE GRPMEMBER command.
replication server to identify active replication
processes. Issue the CANCEL PROCESS command from
the source replication server to stop the replication ANR1989W Remote monitoring of server server name
process. If running this command on a target could not be started. Will retry in
replication server, log on to the source replication minutes minutes.
server and issue the CANCEL PROCESS command. Explanation: An error occurred while attempting to
When the replication process stops, reissue the monitor the specified remote server.
REMOVE REPLSERVER command.
System action: Server operation continues. The
specified remote server is not being monitored. The
ANR1985E The remote monitoring admin admin server will attempt to start monitoring again after the
name does not exist. specified number of minutes.
Explanation: The administrator used to monitor User response: Check previous messages in the
remote servers does not exist. activity log. Verify that the specified remote server is
System action: Remote monitoring sessions will be running and is available on the network. If you no
ended. longer want this remote server to be monitored, remove
it from the remote monitoring server group using the
User response: Use the SET MONITORINGADMIN DELETE GRPMEMBER command.
command to set a new administrator for monitoring
remote servers.
ANR1990I Remote monitoring started for server
server name.
ANR1986E The remote monitoring server group
group name does not exist. Explanation: The specified remote server is now being
monitored.
Explanation: The server group being remotely
monitored does not exist. System action: Server operation continues.
System action: Remote monitoring sessions will be User response: None.

ended.
User response: Use the SET ANR1991I Remote monitoring ended for server
MONITOREDSERVERGROUP command to set a new server name.
group for monitoring remote servers. Explanation: The specified remote server is no longer
being monitored.
ANR1987E A communication error occurred during System action: Server operation continues.
session session number with monitored
server server name. User response: None.
Explanation: The communication error occurred while

the system was receiving information from the ANR1992E Command: The parameter parameter is
specified monitored server. missing.
System action: The monitoring that was in progress Explanation: The specified server command has been
failed. The server will attempt to re-establish entered without all required parameters. At least the
communications with the monitored server. named parameter is missing.
User response: If this error occurs frequently, consult System action: The server ignores the command.
your network administrator. Also review the activity

User response: Reissue the command and enter the User response: Reissue the command with a prefix
proper syntax. short enough to allow for the suffix. Three extra
characters are needed for the suffix.
ANR1993I command has been removed.
ANR1997E Command: The Formatsize parameter
Explanation: The specified command was a valid
must be specified when more than 1
server command, but is no longer needed due to new
volume is created.
capabilities in the IBM Spectrum Protect server. The
command has been removed. Explanation: The command specified the createion of
more than one volume with the Numberofvolumes
parameter. When multiple volumes are created, the
User response: None. Formatsize parameter must also be specified to provide
the size of the volumes. Each volume will be created
with the same size.
ANR1994I Activity log pruning started: removing
delete megabytes M based on current size System action: The server does not process the
current size megabytes M and retention command.
setting retention size megabytes M.
User response: Reissue the command with the
Explanation: Server activity log exceeds the retention Formatsize parameter or define a single volume
size by the delete megabytes specified. The activity log without the Formatsize parameter.
pruning will delete as many records as necessary to
reduce the current activity log size by the delete
ANR1998E Command: Invalid value for parameter
megabytes size.
parameter - parameter value.
User response: None. the (parameter) parameter in command command is not a
valid value for this parameter.
ANR1995E Command: Invalid Formatsize value - System action: The command fails and server
formatsize value for device class Device operation continues.
Class
Explanation: A value was specified for the Formatsize valid parameter value.
parameter which is larger than the maximum capacity
value for the device class indicated in the message. The
ANR1999I Command completed successfully.
device class is associated with the storage pool
specified in the DEFINE VOLUME command and is a Explanation: Processing for the specified command
FILE device type. The maximum capacity value of the completed successfully.
device class is the limit of data that the server will
write to the volume.
command.
ANR2000E Unknown command - command.
User response: Reissue the command with a
Formatsize value which is less than the maximum Explanation: The specified command is not a valid
capacity value of the storage pool. The maximum server command.
capacity can be displayed with the QUERY DEVCLASS
classname F=D command. System action: The server ignores the command.
User response: Reissue the correct command.
ANR1996E Command: Invalid volume name prefix -
volume name. Room for additional ANR2001E Insufficient server memory to initiate
characters is required. command.
Explanation: The command is being used for multiple Explanation: A command has been entered, but the
volume names. The suffix for the names is being server cannot obtain enough internal memory to
generated in the indicated command. When the suffix process the command.
is taken into account, the specified name is too long by
the indicated number of characters. Three characters System action: The server ignores the command.
must be allowed for the suffix. User response: See the documentation for the
System action: The server does not process the operating system about how to increase memory for an
command. application.

System action: The server does not update the activity

ANR2002E Missing closing quote character.
log.
Explanation: A server command that contains a
quoted parameter has been entered, but a matching
closing quote is missing.
System action: The server ignores the command. activity log and search for messages. If the error cannot
User response: Reissue the command with properly
representative.
matched quotes.
ANR2008E Activity log process has stopped -

ANR2003E Illegal use of keyword parameter
database transaction could not be
character (=) - parameter.
started.
Explanation: A server command contains the
Explanation: The process that monitors the default
parameter shown followed by an equal sign (=), but the
parameter is not a keyword parameter.
cannot continue due to a server transaction failure. This
System action: The server ignores the command. may be a memory shortage error.
User response: Reissue the command and enter the System action: The server stops updating the activity
proper syntax. log.
ANR2004E Missing value for keyword parameter - operating system about how to increase memory for an
parameter. application.
Explanation: A server command containing a keyword
parameter has been entered, but the value for the ANR2009E Activity log process has stopped -
parameter is missing. database error.
System action: The server ignores the command. Explanation: The process that monitors the default
User response: Reissue the command and supply a cannot continue due to a server database error.
value for the keyword parameter.
System action: The server stops updating the activity
log.
ANR2005E Keyword parameter character (=) may
not be surrounded by blanks. User response: Contact your service representative.
Explanation: A server command contains a keyword

parameter followed by an equal sign (=), but the equal ANR2010W The active log space is full. Console
sign is preceded or followed by a blank, or both. messages cannot be logged until log
space becomes available.
User response: Reissue the command without blanks transaction is rolled back. The server issues an error
next to the equal sign. message and halts. You cannot restart the server until
the recovery log size is increased.
ANR2006E Activity log process was not started, the System action: The server halts.
default output stream cannot be opened.
Explanation: The process that monitors the default the recovery log space is insufficient, monitor the
(console) output stream and maintains the activity log archive log space first. If the archive log space is full or
cannot access that output stream. nearly full, run a full database backup to remove
System action: The server does not update the activity archive logs and consider adding more disk space to
log. the archive log directory. If the archive log space is not
full and the active log space is full or nearly full,
User response: Contact your service representative. update the value of the ACTIVELOGSIZE option in the
ANR2007E Activity log process was not started, due option to the new maximum size of the active log.
to an internal error.
Explanation: The process that monitors the default
cannot start due to a server internal error.


ANR2011W The server ran out of database space
representative.
while entries were being added to the
active log. Console messages will not be
logged until database space becomes ANR2015E Activity log failure - database
available. transaction could not be started.
Explanation: The process that monitors the console Explanation: The process that removes expired records
output stream and maintains the active log cannot from the server activity log has failed due to a database
update the active log because of insufficient database transaction failure, which may be a memory shortage
space. error.
System action: The server fails to update the active System action: The server ends activity log pruning.
log.
User response: To increase the amount of database operating system about how to increase memory for an
space that is available to the server, issue the EXTEND application.
the database.
ANR2016E Activity log failure - database error.
ANR2012W Error encountered for storage pool Explanation: The process that removes expired records
directory: STGPOOLDIRECTORY in from the server activity log has failed due to a server
storage pool: STGPOOL. database error.
Explanation: The server encountered an error System action: The server ends activity log pruning.
accessing the specified directory. User response: Contact your service representative.
System action: If appropriate, the operation is
attempted in another directory. ANR2017I Administrator Administrator Name issued
User response: Evaluate the warning and take command: Command
appropriate corrective action. Explanation: This message records the fact that the
named administrator issued the command specified.
ANR2013E The activity log process has encountered The messages is issued and logged to provide an audit
unexpected output data in the console trail for administrative commands.
output stream. The process will be System action: Server operation continues
restarted.
Explanation: The process that monitors console output
and maintains the activity log has detected invalid data
(unknown data type) in the console stream. ANR2018E Administrator Command: Unicode
conversion failed for argument Command
System action: The server restarts the activity log Argument
recording process. While the process is restarting, the
server may not be able to record some console Explanation: The specified command argument could
messages in the activity log. not be converted to a Unicode string. Conversion can
fail if the string includes characters that are not
User response: See the documentation for the available in the server code page, or if the server has a
operating system about how to increase memory for an problem accessing system conversion routines. If you
application. issued a RENAME FILESPACE command, the new
filespace name might be too long.
ANR2014E Activity log pruning process could not System action: The server command fails.
be started, due to an internal error.
User response: Ensure that the server locale is
Explanation: The process that removes expired records configured correctly. If you issued a RENAME
from the server activity log cannot begin execution due FILESPACE command, consider specifying a shorter
to a server internal error. name for the new filespace.
System action: The server does not prune the activity
log. ANR2019I Command: No nodes updated.
User response: Examine the server messages issued Explanation: An UPDATE NODE command has been
prior to this message to determine the source of the entered, but no objects were updated.
activity log and search for messages. If the error cannot System action: None.

User response: None. User response: Reissue the command. If the command
fails with the same error, wait for server activity to
decrease and try again.
ANR2020E Command: Invalid parameter - parameter.
ANR2026E Command: Command failed - sufficient
entered with an invalid parameter.
server memory is not available.
Explanation: A server command has been entered but
User response: Reissue the command and enter the cannot be processed because sufficient memory is not
proper syntax. available to the server.
ANR2021E Command: Missing subcommand command.
keyword.
Explanation: The specified server command has been operating system about how to increase memory for an
entered without a valid subcommand (second application.
parameter).
System action: The server ignores the command. ANR2027E Command: Command failed - sufficient
server recovery log space is not
User response: Reissue the command and enter the available.
proper syntax.
cannot be processed because sufficient recovery log
ANR2022E Command: One or more parameters are space is not available.
missing.
Explanation: The specified server command has been command.
entered without all required parameters.
System action: The server ignores the command. that is available to the server, evaluate the directories
User response: Reissue the command and enter the and file systems that are assigned to the
proper syntax. ACTIVELOGDIRECTORY, ARCHIVELOGDIRECTORY,
ANR2023E Command: Extraneous parameter - occur because the ACTIVELOGDIRECTORY location is
parameter. full.
Explanation: The specified server command contains Alternatively, an out of log space condition might occur
more positional parameters than is allowed. if there are log files in the ACTIVELOGDIRECTORY
System action: The server ignores the command. location that are no longer active and cannot be
User response: Reissue the command and enter the ARCHFAILOVERLOGDIRECTORY locations. If
proper syntax. necessary, specify a larger directory for the
ANR2024E Command: Too many parameters ARCHFAILOVERLOGDIRECTORY options in the
specified. dsmserv.opt file and then restart the server.
Explanation: The specified server command contains

more positional parameters than is allowed. ANR2028E Command: Command failed - sufficient
server database space is not available.
User response: Reissue the command and enter the cannot be processed because sufficient database space
proper syntax. is not available. For certain operations, like SQL
commands, this message can be issued when the
database has space, but it is unusable for the current
ANR2025E Command: Command failed - server
request due to the DB allocation history. In this case,
thread resource not available.
the database query will show a Maximum Reduction of
Explanation: A server command, which has a 0.
requirement to start a server thread, has been entered
but cannot be executed because no server thread is
command.
available.
System action: The command is not executed.


ANR2033E Command: Command failed - lock
conflict.
the database.
Explanation: A server command that requires the
server to lock a system resource has been entered. The
ANR2029E Command: Transaction failed; command
command cannot be executed because the resource is
not executed.
already in use by another command or process.
Explanation: A command that is part of the current
transaction has failed; therefore, any additional
command.
commands fail.
User response: Try the command again at a later time.
command.
ANR2034E Command: No match found using this
User response: Stop the administrative session, restart
criteria.
it, and try the command again. If this problem persists,
contact your service representative. Explanation: The specified command has been
entered, but no objects that match the criteria can be
found. In some cases when using the SELECT
ANR2030E Commit not accepted; transaction failed.
command, this message is issued when there is
Explanation: A command that is part of the current contention for a record.
transaction has failed; therefore, a COMMIT command
cannot be processed.
User response: Verify that all the specified parameter
values are correct. If a mistake is found, correct it and
COMMIT command.
reissue the command. If you issued a SELECT
User response: Stop the administrative session, restart command, in some cases issuing the command again
it, and try the command again. If this problem persists, will yield a match.
ANR2035E Command: Administrator administrator
ANR2031E Command: At least one attribute must be name is not authorized to issue this
specified for update. command.
Explanation: The specified UPDATE command has Explanation: The specified administrator has entered
been entered, but no attributes have been specified for the indicated command, but this administrator does not
updating. have the proper authority necessary to run the
command. Note: This message can be issued as a result
System action: The server ignores the command. of the server option REQSYSAUTHOUTFILE YES being
User response: Reissue the UPDATE command with in effect.
one or more attributes to be updated. System action: The server does not process the
command.
ANR2032E Command: Command failed - internal User response: Examine previous messages for any
server error detected. additional information. Issue the command from a
Explanation: An internal error has occurred during an properly authorized administrator ID, or contact the
attempt to process a server command. This message system administrator to have additional authority
always accompanies another error message and granted to the current administrator ID.
provides more detail about that error.
System action: The server does not process the ANR2036E Command: Process could not be started -
command. sufficient memory is not available.
User response: Examine the server messages issued Explanation: A background process cannot be started
prior to this message to determine the source of the for the indicated command because sufficient memory
error. Issue the QUERY ACTLOG command to view the is not available to the server.
activity log and search for messages. If the error cannot System action: A new process is not started to execute
be isolated and resolved, contact your service this command.
representative.
application.

with access mode destroyed becomes empty because all

ANR2037E Command: Process could not be started -
files on the volume have been restored to another
lock conflict.
location, the destroyed volume will be deleted from the
Explanation: A background process cannot be started database.
for the indicated command because a required system
resource is already locked by another command or
continue.
process.
User response: Enter 'Y' to restore the storage pool,
System action: A new process is not started to execute
'N' otherwise.
this command. If other processes have been started for
this command, these processes may execute
successfully. ANR2041W This command attempts to restore all
files in storage pool storage pool which
User response: If necessary, try the command again at
reside on one of the volumes specified
a later time.
in the command; existing references to
files on these volumes will be deleted
ANR2038E Command: Process could not be started - from the database after the files have
server thread resource not available. been restored.
Explanation: A background process cannot be started Explanation: Issuing the RESTORE VOLUME
for the indicated command because no server thread is command causes the access mode of the specified
available. volumes to be updated to destroyed. Existing files will
be deleted from the specified volumes after these files
have been restored from a copy storage pool. If a
volume with access mode destroyed becomes empty
because all files on the volume have been restored to
successfully.
another location, the destroyed volume will be deleted
User response: If necessary, reissue the command. If from the database.
the command fails with the same error, wait for server
activity to decrease and try again.
continue.
User response: Enter 'Y' to restore the volumes, 'N'
ANR2039E Command: Process could not be started -
otherwise.
Explanation: A background process cannot be started
ANR2042E Command: Copied parameter not valid
for the indicated command because an internal error
for pool type storage pool volume.
has occurred.
Explanation: The QUERY CONTENT server command
has been entered with an invalid parameter. COPIED is
not a valid parameter when the volume specified
belongs to a copy or active-data type storage pool.
successfully.
prior to this message to determine the source of the User response: Reissue the command without the
error. Issue the QUERY ACTLOG command to view the COPIED parameter.
ANR2043E Command: WAIT parameter not allowed
representative.
from server console.
Explanation: The WAIT parameter is not allowed for
ANR2040W This command attempts to restore all
commands issued from the server console.
files in storage pool storage pool which
have previously been found to be System action: The command is not executed.
damaged or which reside on a volume
with access mode "destroyed"; existing User response: Either reissue the command without
references to files in storage pool storage the WAIT parameter or else reissue the command from
pool will be deleted from the database an administrator using an Administrative Client.
after the files have been restored.
Explanation: Issuing the RESTORE STGPOOL
command will result in deletion of existing files in the
indicated primary storage pool after these files have
been restored from a copy storage pool. If a volume


ANR2044E Command: Invalid option's value -
Option's value.
ANR2050I Command: Option option name defined in
Explanation: The set option command has been
optionset option set name.
entered with an invalid value.
Explanation: The requested option has been added to
the specified optionset in response to a DEFINE
command.
OPTIONSET command.
value.
ANR2045E Command: An error (error code) occurred
during a write operation. ANR2051E Command: Option option name, sequence
number sequence number is already
Explanation: The server detects an error while
defined in optionset option set name.
attempting a write operation.
Explanation: The requested option already exists in
the optionset specified by the DEFINE CLIENTOPT
User response: Refer to the other displayed messages command.
to determine why the write operation has failed.
command.
ANR2046I optionset name: Optionset optionset name
defined.
Explanation: The requested option set has been added
ANR2052E Command: Option option name, sequence
to the system in response to a DEFINE OPTIONSET
number sequence number is not defined
command.
in optionset option set name.
Explanation: The requested option is not defined in
User response: None. the optionset specified by the DELETE CLIENTOPT
command.
ANR2047E Command: Optionset optionset name is System action: The server does not process the
already defined. command.
Explanation: A DEFINE OPTIONSET command has User response: None.
been entered that specifies an optionset name already
defined to the server.
ANR2053I Command: Option option name, sequence
System action: The server does not process the number sequence number, has been
command. deleted from optionset option set name.
User response: To define the optionset, reissue the Explanation: The requested option has been deleted
command and specify a different optionset name. from the specified optionset in response to a DELETE
CLIENTOPT command.
ANR2048I Command: Optionset optionset name System action: None.
deleted.
Explanation: The requested option set has been
deleted from the system in response to a DELETE
ANR2054I Command: Optionset optionset name
OPTIONSET command.
updated.
Explanation: The requested option set has been
User response: None. updated in the system in response to an UPDATE
OPTIONSET command.
ANR2049E Command: Optionset optionset name is not System action: None.
defined.
Explanation: The command shown specifies an
optionset that is not defined in the server.
command.

server restarts later. If the user does not update the file,
ANR2055I Command: Optionset source optionset name
the current value in the options file will be used when
copied to optionset target optionset name.
the server restarts.
the COPY OPTIONSET command. The optionset
ANR2060I Node node name registered in policy
named source optionset name has been copied to the
domain domain name.
optionset named target optionset name.
Explanation: The requested backup-archive node has
been added to the system in response to a REGISTER
User response: None. The requested option set has NODE command and has been assigned to the policy
been added to the system in response to a COPY domain indicated.
OPTIONSET command.
ANR2056E Command: Invalid option name - option
name. Retry using the full optionname.
ANR2061I Node node name removed from policy
Explanation: The command shown specifies an invalid
domain domain name.
option name.
Explanation: In response to a REMOVE NODE
command, the requested backup-archive node has been
command.
removed from the system.
option name.
ANR2057E Command: Invalid option value - option
value. ANR2062I Node node name renamed to new node
name.
option value. Explanation: In response to a RENAME NODE
renamed to the new name shown.
command.
option value. User response: None.
ANR2058W Command: Options file Filespec not found ANR2063I Node node name updated.
- user needs to update the file manually.
Explanation: One or more attributes of a
Explanation: The server options file cannot be opened backup-archive node have been updated by an
or found. UPDATE NODE command.
System action: The command is processed but the System action: None.
option is not updated in the options file.
User response: Use a text editor to update the server
options file if the user wants to use this value when the
server restarts later. If the user does not update the file, ANR2064I Node node name locked.
the current value in the options file will be used when Explanation: In response to a LOCK NODE command,
the server restarts. the indicated backup-archive node has been locked.
ANR2059W Command: Error occurs when writing to
Filespec - user needs to update the file User response: None.
manually.
Explanation: An error occurs when trying to write the ANR2065I Node node name is already locked.
new value to the server options file. Explanation: The indicated backup-archive node
System action: The command is processed but the referenced in the LOCK NODE command is already
option is not updated in the options file. locked.
User response: Use a text editor to update the server System action: None.
options file if the user wants to use this value when the User response: None.

ANR2066I Node node name unlocked. ANR2072I Administrator administrator ID locked.

Explanation: In response to an UNLOCK NODE Explanation: In response to a LOCK ADMIN
command, the indicated backup-archive node is command, the indicated administrator ID has been
unlocked. locked.
ANR2067I Node node name is already unlocked. ANR2073I Administrator administrator ID is already
locked.
Explanation: The indicated backup-archive node
referenced in the UNLOCK NODE command is not Explanation: The indicated administrator ID
locked. referenced in the LOCK ADMIN command is already
locked.
ANR2068I Administrator administrator ID registered.
ANR2074I Administrator administrator ID unlocked.
Explanation: In response to a REGISTER ADMIN
command, the requested administrator ID has been Explanation: In response to an UNLOCK ADMIN
added to the system. command, the indicated administrator ID is unlocked.
ANR2069I Administrator administrator ID removed. ANR2075I Administrator administrator ID is already

unlocked.
Explanation: In response to a REMOVE ADMIN
command, the requested administrator ID has been Explanation: The indicated administrator ID
removed from the system. referenced in the UNLOCK ADMIN command is not
locked.
ANR2070I Administrator administrator ID renamed
to new administrator ID. ANR2076I System privilege granted to
administrator administrator ID.
Explanation: In response to a RENAME ADMIN
command, the requested administrator ID has been Explanation: In response to a GRANT AUTHORITY
changed to the new name shown. command, system privilege class has been granted to
the indicated administrator.
ANR2071I Administrator administrator ID updated.
ANR2077I Unrestricted policy privilege granted to
Explanation: One or more attributes of an
administrative user have been updated by an UPDATE
ADMIN command. Explanation: In response to a GRANT AUTHORITY
command, unrestricted policy privilege has been
granted to the indicated administrator.

ANR2078I Restricted policy privilege granted to ANR2083I System privilege revoked for
administrator administrator ID - policy administrator administrator ID.
domain domain name.
Explanation: In response to a REVOKE AUTHORITY
Explanation: In response to a GRANT AUTHORITY command, system privilege class has been revoked
command, restricted policy privilege for the specified from the indicated administrator.
policy domain has been granted to the indicated
administrator.
ANR2084I Policy privilege revoked for
ANR2079I Unrestricted storage privilege granted to
command, policy privilege class for all policy domains
Explanation: In response to a GRANT AUTHORITY has been revoked from the indicated administrator.
command, unrestricted storage privilege has been
granted to the indicated administrator.
ANR2085I Restricted policy privilege revoked for
administrator administrator ID - policy
ANR2080I Restricted storage privilege granted to domain domain name.
administrator administrator ID - storage
pool storage pool name.
command, restricted policy privilege for the specified
Explanation: In response to a GRANT AUTHORITY policy domain has been revoked from the indicated
command, restricted storage privilege for the specified administrator.
storage pool has been granted to the indicated
administrator.
ANR2086I Storage privilege revoked for
ANR2081E The STGPOOLDIRECTORY
STGPOOLDIRECTORY in STGPOOL
command, storage privilege class for all storage pools
STGPOOL is full.
has been revoked from the indicated administrator.
Explanation: The operating system reported space
problem with a directory.
System action: The write will be attempted to another
directory.
ANR2087I Restricted storage privilege revoked for
User response: Ensure adaquate storage is assigned to
administrator administrator ID - storage
the storage pool directory or a next pool is defined.
pool storage pool name.
ANR2082I Operator privilege granted to
command, restricted storage privilege for the storage
pool indicated has been revoked from the indicated
Explanation: In response to a GRANT AUTHORITY administrator.
command, operator privilege class has been granted to
the indicated administrator.
ANR2088E An I/O error ocurred while reading
container container name in storage pool
storage pool name.
Explanation: One or more data extents cannot be
accessed in the container.

System action: The operation fails and server

ANR2093I Registration parameter set to registration
operation continues. Depending upon the operation
method.
being performed, the data extent being accessed is
marked damaged so it can be repaired. Explanation: Backup-archive node registration has
been set to the method indicated with the SET
User response: For more information about the I/O
REGISTRATION command.
error, see the server's First Failure Data Capture (FFDC)
log. Issue the AUDIT CONTAINER command to System action: None.
validate the contents of the container. If the AUDIT
CONTAINER command detects damaged extents,
repair the storage pool and retry the failing operation.
ANR2094I Server name set to server name.
ANR2089I Operator privilege revoked for Explanation: The name that the server displays and
administrator administrator ID. communicates to backup-archive nodes has been set to
the value indicated with the SET SERVERNAME
command.
command, operator privilege class has been revoked
from the indicated administrator. System action: None.
System action: None. User response: None.
ANR2095I Authentication parameter set to value.
ANR2090I Activity log retention set to value for Explanation: The requirement for a node or
management by management style. administrator to enter a password when establishing a
session with the server has been turned on or off as
Explanation: The server activity log has been set to
indicated with the SET AUTHENTICATION command.
the value indicated with the SET ACTLOGRETENTION
command for the indicated management style. If the System action: None.
management style is DATE, the value is the number of
days that messages will be kept in the activity log User response: None.
before being deleted. If the management style is SIZE,
the value is the size in megabytes that the activity log ANR2096I Server now enabled for backup/archive
will be allowed to occupy in the server database. client access.
System action: None. Explanation: The server has been made available for
User response: None. use by backup-archive clients with the ENABLE
command.
ANR2091I Accounting parameter set to value. System action: None.
Explanation: Accounting record generation has been User response: None.

turned on or off as indicated with the SET
ACCOUNTING command. ANR2097E Unable to retrieve the master encryption
System action: None. key from the server password file,
password file name.
Explanation: The master encryption key could not be
read from the password file in which it was stored. The
ANR2092I Password expiration period set to following list contains possible reasons:
number of days days. v The password file was created by a different server
Explanation: The number of days that a password can instance.
be used before it must be changed has been set to the v The password file was created before the database
value indicated with the SET PASSEXP command. was formatted.
System action: None. v The server password changed, and the password file
was restored from a point in time prior to the
User response: None. change.
System action: Server initialization continues. Data
stored in encrypted storage pools cannot be retrieved.
New data cannot be written to encrypted storage pools.
User response: Confirm that the correct password file

is present in the server's instance directory. User response: None.

v If the server is not configured to encrypt data in
storage pools either delete or rename the password ANR2103I Activity log pruning completed: number
file. Restart the server. of records records removed.
v If the server database was reformatted, either delete
Explanation: All expired (older than the log archive
or rename the password file. Restart the server.
retention value) server activity log records have been
v If the server password changed, either restore the removed; the number of records deleted is shown.
database to a point in time prior to the change, or
reset the password back to the previous value. System action: None.
ANR2098E Command: Invalid URL specification -
url. ANR2104I Activity log processing is now restarted.
Explanation: The specified URL is too long. Explanation: The process that records data in the
System action: The server ignores the command. server activity log had suspended logging messages
because of insufficient space in the server recovery log
User response: Reissue the command and enter a URL or database or because access to the database failed.
value that is 200 characters or less. The condition that caused the activity log processing to
fail has been resolved and the activity log processing is
ANR2099I Administrative userid admininstrator able to resume.
name defined for OWNER access to node System action: Activity log processing resumes.
node name.
Explanation: An administrator with the specified
name was created having OWNER access to the client
node. This administrator is created for accessing the ANR2105W Command: Node was registered in excess
client node from an interactive interface. of license terms - node registration will
fail after 120% of the licensed quantity
System action: None. of nodes have been registered.
User response: None. Explanation: The server has detected the addition of a
node in excess of the terms under which the server is
ANR2100I Activity log process has started. licensed. The REGISTER NODE command will fail after
120% of the licensed number of nodes have been
Explanation: The automatic server process that registered.
removes expired server activity log records has begun
processing. System action: Server operation continues.
System action: None. User response: Use the QUERY LICENSE command to
User response: None. compliance. You may remove nodes to reduce the
number of registered nodes or purchase additional
ANR2101I Activity log process stopped, activity log client node connections. If additional nodes have been
retention set to 0. purchased, issue the AUDIT LICENSES command to
resynchronize the server configuration with license
Explanation: A SET ACTLOGRETENTION command terms.
has set the retention period to zero days. As a result,
activity logging stops.
ANR2106I Server HALT command: Quiescing
System action: The activity log process stops database update activity.
recording console output in the server activity log.
Explanation: The server is quiescing transactions that
User response: None. update the database so that the database is in a
consistent state when the server is halted. This action
occurs when HALT QUIESCE is specified to halt the
ANR2102I Activity log pruning started: removing
server with the database in a consistent state.
entries prior to date time.
System action: When database update transaction
Explanation: Server activity log records older than the
activity has been stopped, the server program ends.
date and time indicated are being removed from the
activity log. User response: None.


ANR2107I Server HALT command: Database update
number to specify this process.
activity is now quiesced.
Explanation: The server has stopped all database
ANR2111W Command: There is no data to process for
update transaction activity. This action occurs when
storage pool.
HALT QUIESCE is specified to halt the server with the
database in a consistent state. Explanation: The indicated command does not have
any data to process. This can occur if the command
System action: The server program ends.
specifies a storage pool with no volumes, or with no
User response: None. volumes that contain data. This can also occur if there
are no volumes in the storage pool with an access state
of READWRITE or READONLY.
ANR2108I Server HALT command: Reattempting to
quiesce database update activity. System action: The command ends without starting a
background process.
Explanation: The server is quiescing transactions that
update the database so that the database is in a User response: Issue the QUERY VOLUME F=D
consistent state when the server is halted. The previous command to verify that there is at least one volume in
attempt at quiescing database activity failed because of the storage pool that contains data, and that the storage
the current transaction load on the server. The quiesce pool volumes have an access state of READWRITE or
operation is being reattempted. This action occurs when READONLY.
HALT QUIESCE is specified to halt the server with the
database in a consistent state.
ANR2112E Command: Volume volume name is not in
System action: When database update transaction a primary storage pool.
activity has been stopped, the server program ends.
User response: None. name of a volume that does not belong to a primary
storage pool. The command syntax requires that a
volume in a primary storage pool be specified.
ANR2109I Server HALT command: Database update
transaction activity could not be System action: The server does not process the
successfully quiesced. command.
Explanation: After repeated attempts, server database User response: Reissue the command with a volume
update transaction activity could not be quiesced. The in a primary pool.
server is not halted with the HALT QUIESCE
command. Attempts to quiesce database update
ANR2113E Command: Volume volume name does not
transaction activity can fail if heavy transaction load is
belong to the same storage pool (storage
on the server when a HALT QUIESCE command is
pool name) as previously listed volumes.
entered.
Explanation: The indicated command accepts a list of
one or more volumes which belong to the same storage
User response: You may disable the server, cancel all pool. The named volume does not belong to the same
client sessions accessing the server, cancel all processes, storage pool as the previously listed volumes.
and reenter the HALT QUIESCE command to stop
server processing. The HALT command may also be
command.
used to stop server processing without quiescing
database transaction update activity. Server recovery User response: Issue the command with a list of
logic will be used when the server is restarted to volumes that belong to the same storage pool.
reconcile database transaction activity.
ANR2114I Command: Access mode for volume
ANR2110I Command started as process process ID. volume name updated to "destroyed".
Explanation: A background process has been started Explanation: A RESTORE VOLUME command has
to service the command command. The background updated the access mode of the indicated volume to
process is defined as process process ID. destroyed.
System action: The server processes the indicated System action: Restore processing continues.
command.

ANR2115E Command: Access mode for volume ANR2119I The Option option has been changed in
volume name cannot be changed to the options file.
"destroyed" - volume is still online.
Explanation: The option is updated in the server
Explanation: A RESTORE VOLUME command cannot options file.
change the access mode of the indicated volume to
System action: Server continues.
destroyed because the volume is still online.
command.
ANR2120E Command: Invalid platform name -
User response: Issue the VARY OFFLINE command,
platform name.
and reissue the RESTORE VOLUME command.
platform name.
ANR2116E Command: Access mode for volume
volume name cannot be changed to System action: The server does not process the
"destroyed" - volume does not belong to command.
a primary storage pool.
Explanation: The access mode for the indicated platform name.
volume cannot be changed to destroyed because the
volume does not belong to a primary storage pool.
ANR2121W ATTENTION: More than amount changed
System action: The access mode for this volume is not unit megabytes, gigabytes or terabytes of the
changed. database has changed and the last
database backup was more than hours
name hours ago. Use the BACKUP DB
command to provide for database
ANR2117E Command: Access mode for volume recovery.
volume name cannot be changed to
Explanation: The server issues this warning when a
"offsite" - volume either does not belong
significant amount of database change activity has
to a copy storage pool or from a device
occurred and the server database has not been backed
class of DEVTYPE=SERVER.
up.
Explanation: The access mode for the indicated
volume cannot be changed to offsite because the
volume either does not belong to a copy storage pool User response: To provide for server database
or is of a device class with a DEVTYPE of SERVER. recovery should a hardware or software problem affect
your database, use the BACKUP DB command to back
System action: The access mode for this volume is not
up the database.
changed.
ANR2122E command name: The DOMAINS
parameter cannot be specified when the
ANR2118E Storage pool storage pool name specified NODES parameter is specified.
on the MOVE DATA command is not a
Explanation: Both the NODES and DOMAINS
valid poolname and or pooltype for
parameters were specified. The NODES parameter may
volume volume name.
be specified, or the DOMAINS parameter may be
Explanation: If the volume belongs to a primary specified, but both should not be specified at the same
storage pool, then the storage pool specified must also time.
be a primary storage pool. If the volume belongs to a
copy storage pool, then the specified storage pool must
be the same storage pool as that of the volume. User response: Reenter the command specifying either
the NODES parameter or the DOMAINS parameter, but
System action: The MOVE DATA process fails.
not both.
User response: Provide a valid primary storage pool
name if the volume belongs to a primary storage pool.
ANR2123E command name: The NODES parameter
If the volume belongs to a copy storage pool, remove
cannot be specified when the
the storage pool name from the command.
DOMAINS parameter is specified.
Explanation: Both the NODES and DOMAINS
parameters were specified. The NODES parameter may

be specified, or the DOMAINS parameter may be result of a REVOKE AUTHORITY command.

specfied, but both should not be specified at the same
time.
User response: Reenter the command specifying either
ANR2129I Administrative userid admininstrator
the NODES parameter or the DOMAINS parameter, but
name defined ONLY for authority over
not both.
node node name has been removed.
Explanation: The specified administrator has been
ANR2124E command name: Invalid Client authority
removed because the client node was removed and the
specified: authority.
administrator only had OWNER access to the specified
Explanation: An invalid client authority was specified node.
in a GRANT AUTHORITY or REVOKE AUTHORITY
command when the CLASS=NODE parameter was
specified. User response: None.
ANR2130S Early Product Version has Expired.
Server is HALTing.
valid client authority.
Explanation: This server is pre-release version of the
server. The pre-release version's expiration date has
ANR2125I command name: Administrator
been reached.
administrator name was granted OWNER
authority for client client name. System action: The server halts.
Explanation: The named administrator was granted User response: Install the product version of the
OWNER authority over the named client node as the server.
result of a GRANT AUTHORITY command.
System action: Processing continues. ANR2131I Server password set.
User response: None. Explanation: The password that the server uses to
allow other servers to communicate with it has been
set, changed or removed with the SET
ANR2126I command name: Administrator
SERVERPASSWORD command.
administrator name was granted ACCESS
authority for client client name. System action: None.
Explanation: The named administrator was granted User response: None.
ACCESS authority over the named client node as the
result of a GRANT AUTHORITY command.
ANR2132I Server hladdress set to hladdress.
Explanation: The high level address that other servers
User response: None. use to communicate with this server has been set to the
value indicated with the SET SERVERHLADDRESS
command.
ANR2127I command name: Owner authority for node
client node was revoked for administrator System action: None.
administrator.
Explanation: OWNER authority over the named client
node was revoked from the named administrator as a
result of a REVOKE AUTHORITY command. ANR2133I Server lladdress set to lladdress.
System action: Processing continues. Explanation: The low level address that other servers
use to communicate with this server has been set to the
User response: None. value indicated with the SET SERVERLLADDRESS
command.
ANR2128I command name: Access authority for node System action: None.
client node was revoked for administrator
administrator. User response: None.
Explanation: ACCESS authority over the named client

node was revoked from the named administrator as a


ANR2134I Server url set to url.
command.
Explanation: The url that other servers use to
communicate with this server has been set to the value
value.
indicated with the SET SERVERURL command.
ANR2140E Command: Invalid activity log retention
User response: None. period - retention value.
Explanation: A SET ACTLOGRETENTION command
ANR2135I Crossdefine set to state. has been entered that specifies an invalid log retention
period.
Explanation: The ability for another server to
automatically define itself to this server has been System action: The server does not process the
turned on or off as indicated with the SET command.
CROSSDEFINE command.
System action: None. retention period.
ANR2141E Command: Invalid password expiration
period - days value.
ANR2136I Administrator administrator name already
has POLICY access for domain policy Explanation: A SET PASSEXP command has been
domain name. entered that specifies an invalid days value.
Explanation: The named administrator already has System action: The server does not process the
POLICY authority over the named policy domain. An command.
attempt to grant client authority over this domain is
User response: Reissue the command with a password
ignored.
expiration period.
System action: The policy domain is skipped.
User response: None. ANR2142E Command: Invalid server name - server
name.
ANR2137I Administrator administrator name already Explanation: A SET SERVERNAME command has
has POLICY access for domain policy been entered that specifies an invalid server name.
domain name to which node node name
belongs.
command.
Explanation: The named administrator already has
POLICY authority over the named policy domain. An
server name.
attempt to grant client authority for a client in this
domain is ignored.
ANR2143E Command: Invalid node name - node
System action: The client is skipped.
name.
node name.
ANR2138I Minimum password length set to length.
Explanation: The minimum length of a password a command.
node or administrator may send to the server is
indicated with the SET MINPWLENGTH command.
node name.
User response: None. ANR2144E Command: Invalid password - password.
Explanation: The command specifies an invalid node
ANR2139E Command: The value supplied for the or administrator password.
minimum password length is not valid -
length.
command.
Explanation: A SET MINPWLENGTH command has
User response: Ensure that the password adheres to
been entered that specifies a value for the length is not
naming convention rules and meets the minimum
valid. Valid values are from 0 to 64, inclusive.
password length requirement as set by your

administrator. Ensure that the new password is User response: To register the administrator, reissue
different from the old password. If you are the command and specify a different administrator ID.
authenticating to an LDAP directory server ensure that
the new password meets all other password policy
ANR2150E Command: Node node name is currently
rules specified by the LDAP directory server. Reissue
accessing the server.
the command with a valid password.
Explanation: The command shown specifies a node
that has an active session with the server.
ANR2145E Command: Contact information exceeds
maximum characters characters. System action: The server does not process the
command.
Explanation: A REGISTER NODE or REGISTER
ADMIN command has been entered that specifies a User response: Reissue the command at a later time,
contact information value that is too long. The or if necessary, cancel the current session and reissue
maximum valid length is shown in the command. the command.
command. ANR2151E Command: Administrator administrator ID
is currently accessing the server.
User response: Reissue the command with less contact
information. Explanation: An UPDATE ADMIN or REMOVE
ADMIN command has been entered that specifies an
administrator ID that is having an active session with
ANR2146E Command: Node node name is not
the server.
registered.
command.
that is not registered with the server.
or if necessary, cancel the current session and reissue
command.
the command.
ANR2152E Command: Inventory references still exist
ANR2147E Command: Node node name is already for node node name.
registered.
Explanation: A REMOVE NODE command has been
Explanation: A REGISTER NODE command has been entered for a node for which the server is still storing
entered that specifies a node name already registered backup or archive data, or both.
with the server.
System action: The server does not process the command.
command.
User response: To remove the node, delete all of its
User response: To register the node, reissue the file spaces and any virtual file space mapping
command and specify a different node name. definitions from the server and reissue the command.
ANR2148E Command: Administrator administrator ID ANR2153E Command: Invalid file space name -
is not registered. filespace name.
Explanation: The command shown specifies an Explanation: The specified server command has been
administrator ID that is not registered with the server. entered with a file space name that is longer than
allowed. Note that the maximum length of a unicode
file space name is eight characters less than the
command.
maximum length of a non-unicode file space name.
command.
ANR2149E Command: Administrator administrator ID
User response: Reissue the command with a valid file
is already registered.
space name.
Explanation: A REGISTER ADMIN command has
been entered that specifies an administrator ID already
registered with the server.
command.

ANR2154E Command: Invalid administrator name - ANR2159E Command: Storage pools cannot be
administrator ID. specified for unrestricted storage
administrator ID. Explanation: A REVOKE AUTHORITY command has
been issued to revoke an administrator's storage
authority over a specific storage pool, but the
command.
administrator has unrestricted storage authority.
administrator ID.
command.
ANR2155E Command: Invalid privilege class -
privilege class.
ANR2160E Command: No new privileges granted to
Explanation: A command specifies an invalid
administrative privilege class.
Explanation: A GRANT AUTHORITY command has
been issued to grant authority to an administrator ID,
command.
but the administrator already has all privileges
User response: Reissue the command with a valid specified.
privilege class.
command.
ANR2156E Command: Administrator administrator ID
has already been granted system
privilege.
ANR2161E Command: Only system privilege can be
revoked for administrator administrator
been issued to grant system authority to an
ID.
administrator ID that already has system authority.
Explanation: A REVOKE AUTHORITY command has
been issued to revoke one or more of an administrator's
command.
privileges, but the administrator has system authority.
command.
ANR2157E Command: Other privileges cannot be
granted with system privilege.
ANR2162E Command: No privileges revoked for
been issued to grant system authority to an
administrator ID, and at the same time to grant other
privileges. Explanation: A REVOKE AUTHORITY command has
been issued to revoke authority from an administrator
ID, but the administrator does not have any of the
command.
privileges specified.
User response: Reissue the GRANT AUTHORITY
command specifying only system privilege class.
command.
ANR2158E Command: Policy domains cannot be
specified for unrestricted policy
administrator administrator ID. ANR2163E Command: Command is invalid for
administrator ID.
Explanation: A REVOKE AUTHORITY command has
been issued to revoke an administrator's policy Explanation: The command specified cannot be issued
authority over a specific policy domain, but the for the server console. For instance, the server console
administrator has unrestricted policy authority. administrator ID cannot be removed.
System action: The server does not process the System action: The server does not process the
command. command.

ANR2164E Command: Command rejected - ANR2169E Command: Invalid message number -

administrator ID is the only system message number.
administrator.
Explanation: A QUERY ACTLOG command has been
Explanation: A REMOVE ADMIN or REVOKE entered that specifies an invalid message number as a
AUTHORITY command has been issued to remove or search criteria.
revoke the authority of the last administrator who had
system authority.
command.
command.
message number.
User response: To remove or revoke this ID, grant
system authority to another administrator ID before
ANR2170E Command: Invalid message search string
reissuing the command.
argument - search string.
ANR2165E Command: Invalid begin date - date.
entered that specifies an invalid search string as a
Explanation: A QUERY ACTLOG command has been search criteria.
entered that specifies an invalid begin date as a search
criteria.
command.
command.
search string.
begin date.
ANR2171E Command: Invalid time range - Begin:
date time End: date time.
ANR2166E Command: Invalid begin time - time.
Explanation: A QUERY ACTLOG command has been entered that specifies an invalid beginning and ending
entered that specifies an invalid begin time as a search date/time range. This error can occur when the
criteria. beginning date/time is not before the ending
date/time.
command. System action: The server does not process the
command.
begin time. User response: Reissue the command with a valid
date/time range.
ANR2167E Command: Invalid end date - date.
ANR2172E Command: No matching administrators.
entered that specifies an invalid end date as a search Explanation: The command shown specified an
criteria. administrator ID that does not match any administrator
registered with the server.
command. System action: The command is not executed.
User response: Reissue the command with a valid end User response: If desired, reissue the command with a
date. different administrator ID.
ANR2168E Command: Invalid end time - time. ANR2173E Command: Location information exceeds
maximum characters characters.
entered that specifies an invalid end time as a search Explanation: A DEFINE or UPDATE VOLUME
criteria. command has been entered that specifies a location
information value that is too long. The maximum valid
length is shown in the command.
command.
User response: Reissue the command with a valid end
command.
time.
User response: Reissue the command with less
location information.

ANR2174E Administrator administrator ID is not ANR2178E node/admin name has been locked. Invalid
registered. Schedule schedule name is not sign-on attempt limit (limit) reached.
processed and is marked as failed.
Explanation: The specified node has been locked by
Explanation: The command shown specifies an the server. The limit for consecutive invalid passwords
administrator ID that is not registered with the server. has been reached.
The schedule and related command are not processed.
System action: The node or administrator session will
System action: The server does not process the be refused.
command.
User response: Before the client node is permitted to
User response: Update the command schedule with a access the server, a properly authorized administrator
valid administrator ID which has the proper authority must unlock the node or administrator with the
to execute the scheduled command. UNLOCK NODE or UNLOCK ADMIN command.
ANR2175I Invalid password limit set to password ANR2179E Administrator administrator should have
attempts limit attempts. been locked, but was not.
Explanation: The maximum number of consecutive Explanation: The indicated administrator reached the
invalid passwords a node or administrator may send to limit for consecutive invalid passwords and should
the server is indicated with the SET INVALIDPWLIMIT have been locked. If it were locked, there would be no
command. means to execute commands requiring system
authority.
System action: The administrator session will be
refused.
User response: Sign-on again using the correct
ANR2176E Command: The value supplied for the
password.
invalid password attempts limit is not
valid - password attempts limit.
ANR2180W Unable to update last access date for
Explanation: A SET INVALIDPWLIMIT command has
administrator administrator ID -
been entered that specifies a value for the consecutive
insufficient recovery log space.
invalid password attempts limit that is not valid. Valid
values are from 0 to 9999, inclusive. Explanation: While establishing an administrative
session for the indicated ID, the server is unable to
update the administrator's date of last access due to
command.
insufficient recovery log space.
System action: The server establishes the
value.
administrative session, but the last access date is not
updated.
ANR2177I node/admin name has count invalid
sign-on attempts. The limit is limit.
Explanation: The server detected an invalid password and file systems that are assigned to the
for the specified node during sign-on processing. The ACTIVELOGDIRECTORY, ARCHIVELOGDIRECTORY,
node currently has sent count consecutive invalid and ARCHFAILOVERLOGDIRECTORY options in the
passwords. The maximum allowed is limit. The server dsmserv.opt file. An out of log space condition might
will lock the node when limit is reached. occur because the ACTIVELOGDIRECTORY location is
full.
System action: The node or administrator session will
be refused. Alternatively, an out of log space condition might occur
User response: Before the client node is permitted to location that are no longer active and cannot be
access the server, a properly authorized administrator archived to the ARCHIVELOGDIRECTORY and
must unlock the node or administrator with the ARCHFAILOVERLOGDIRECTORY locations. If
UNLOCK NODE or UNLOCK ADMIN command. necessary, specify a larger directory for the

ANR2181W Unable to update last access date for ANR2184W Diagnostic(ID): Transaction transaction ID
administrator administrator ID - was aborted for command command.
insufficient database space.
Explanation: An error was detected during transaction
Explanation: While establishing an administrative commit for the specified server command. This
session for the indicated ID, the server cannot update message should be preceded by other messages that
the administrator's date of last access due to insufficient give additional information about the failed transaction.
database space.
System action: The server establishes the fails.
updated.
User response: To increase the amount of database transaction. If the error cannot be isolated and resolved,
space that is available to the server, issue the EXTEND contact your service representative.
the database.
ANR2185W Transaction was aborted for command
command.
ANR2182W Unable to update last access date for
administrator administrator ID - internal
server error.
Explanation: While establishing an administrative failed transaction.
session for the indicated ID, the server cannot update
the administrator's date of last access due to a server
fails.
internal error.
System action: The server establishes the
updated.
ANR2186W Transaction was aborted for session
platform).
representative. Explanation: An error was detected during transaction
ANR2183W Diagnostic(ID): Transaction transaction ID
failed transaction.
was aborted.
fails.
commit that caused this transaction to be aborted. This
message may have been preceded by other messages User response: Check for additional messages and
that give additional information about the failed eliminate the condition that caused the failed
transaction. transaction. If the error cannot be isolated and resolved,
fails.
ANR2187W Transaction was aborted for node/admin
name.
transaction. If this was encountered while the server Explanation: An error is detected during a transaction
was halting then this can be ignored. During server commit for the specified node or administrator name.
HALT processing, existing in-flight transactions may be This message should be preceded by other messages
aborted as a normal part of server shutdown that give additional information about the failed
processing. If the error cannot be isolated and resolved, transaction.
fails.


ANR2192E Command: Unable to start background
process.
ANR2188W A Transaction was aborted. The activity
Explanation: The server command processor is not
is terminating.
able to start a background process to perform the
Explanation: An error is detected during a transaction command command.
failed transaction.
ends.
application.
ANR2193E Command: Invalid option set name -
option set name.
option set name.
ANR2189W Diagnostic(ID): Transaction transaction ID
was aborted for node/admin name. System action: The server does not process the
command.
Explanation: An error is detected during a transaction
commit for the specified node or administrator name. User response: Reissue the command with a valid
This message should be preceded by other messages option set name.
that give additional information about the failed
transaction.
ANR2194E Command: Invalid option set description
System action: The activity that generated this error - too long.
fails.
User response: Check for additional messages and description. The description is too long.
command.
description.
ANR2190E command: Device class DISK cannot be
specified for this command.
ANR2195E Command: Invalid option sequence
Explanation: The DEVCLASS value DISK cannot be
number - option sequence number name.
specified for the command.
option sequence number.
command.
valid device class. Issue the QUERY DEVCLASS
command for a list of valid device classes for the User response: Reissue the command with a valid
server. option sequence number.
ANR2191E command: Volume list contains defined ANR2196W An existing server password file,
and undefined volumes. password file name, was found during a
database format operation. It was
Explanation: The list of volumes specified on the
renamed to new password file name.
SALVAGE VOLUME command must all be defined to
the server, or all not defined to the server. Explanation: A password file already exists. The file
cannot be used by the new instance of the server
database. You might need it later, however, if the
database is restored to an earlier point in time.
System action: The password file was renamed.
valid list of volumes.
User response: If the database will be restored to an
earlier point in time, save the renamed password file.
After the database is restored, rename the password file

to 'dsmserv.pwd' and place it in the server instance

ANR2202I Storage pool storage pool name updated.
directory.
Explanation: An UPDATE STGPOOL command has
updated the storage pool indicated.
ANR2197E Command: The value supplied for the
WEB authentication time out is not System action: None.
valid - time-out value.
Explanation: A SET WEBAUTHTIMEOUT command
has been entered that specifies a value that is not valid.
ANR2203I Device class device class name defined.
Valid values are from 0 to 9999, inclusive.
Explanation: A DEFINE DEVCLASS command has
created the device class indicated.
command.
value. User response: None.
ANR2198I Command: Web authentication time-out ANR2204I Device class device class name deleted.
set to time-out value minutes.
Explanation: A DELETE DEVCLASS command has
Explanation: The time-out value that determines how deleted the device class indicated.
often WEB browser administrative users need to
re-authenticate with the server has been set with the System action: None.
SET WEBAUTHTIMEOUT command to the value User response: None.
displayed.
System action: None. ANR2205I Device class device class name updated.
User response: None. Explanation: An UPDATE DEVCLASS command has
updated the device class indicated.
ANR2199I Password expiration period for node System action: None.
node name set to number of days days.
Explanation: The number of days that the node's
password can be used before it must be changed has
been set to the value indicated with the SET PASSEXP ANR2206I Volume volume name defined in storage
command. pool storage pool name (device class device
class name).
Explanation: A DEFINE VOLUME command has
User response: None. defined the volume indicated in the storage pool
shown that belongs to the device class shown.
ANR2200I Storage pool storage pool name defined System action: None.
(device class device class name).
Explanation: A DEFINE STGPOOL command has
created the storage pool indicated of the device class
shown. ANR2207I Volume volume name updated.
System action: None. Explanation: An UPDATE VOLUME command has

updated the volume indicated.
ANR2201I Storage pool storage pool name deleted. User response: None.
Explanation: A DELETE STGPOOL command has

deleted the storage pool indicated. ANR2208I Volume volume name deleted from
Explanation: The volume indicated has been deleted
User response: None. by one of the following:
v A DELETE VOLUME command was issued.
v The volume was empty and the volume's access
mode was updated to destroyed.

v The volume was empty, scratch, and offsite, and the

ANR2214E Command: Invalid backup set name -
access mode was changed to readwrite, readonly, or
backup set name.
unavailable.
v The volume was scratch, not offsite, and was Explanation: The command shown specifies an invalid
emptied by DELETE FILESPACE, RECLAMATION, backup set name.
or RESTORE VOLUME/STGPOOL. System action: The command fails.
v The volume was an empty scratch WORM FILE
volume and deleted by RECLAMATION since the
backup set name.
retention of the volume has expired.
ANR2215E Command: Description text is too long.
Explanation: The specified description text is too long
for a command that allows description text to be
ANR2209W Volume volume name contains no data. specified.
Explanation: The AUDIT VOLUME or MOVE DATA System action: The command fails
command entered specifies a volume that contains no
data.
shorter description
command.
ANR2216E Command: Device class must be a
User response: None. sequential device class.
Explanation: The device class specified on the
ANR2210I Vary online initiated for disk volume command is not a sequential device class.
volume name.
System action: The command fails
Explanation: A VARY ONLINE command for the
User response: Reissue the command specifying the
volume shown is being processed, and if no errors
name of a sequential device class
occur the volume will be varied online.
ANR2217E Command: Invalid backup set retention
User response: None. period - retention value.
Explanation: Server processing for the backup set
ANR2211I Vary offline initiated for disk volume command command fails because the value (retention
volume name. value) specified for the RETENTION parameter is not
valid.
Explanation: A VARY OFFLINE command for the
volume shown is being processed and, if no errors System action: The command fails
occur, the volume will be varied offline.
System action: None. valid RETENTION value.
ANR2218E Command: A device class must be
specified.
ANR2212I Command: No volumes updated.
Explanation: The DEVCLASS parameter is not
Explanation: An UPDATE VOLUME command has
specified in the command command name. A DEVCLASS
been entered, but no objects were updated.
value must be specified.
valid device class. Issue the QUERY DEVCLASS
ANR2213I Command: Storage pool storage pool name command for a list of valid device classes for the
renamed to storage pool name. server.
Explanation: A RENAME STGPOOL command has
been entered. The rename of the storage pool was
successful.

ANR2219E Command: Storage pool cloud url exceeds ANR2223I Discard Data process ended for volume
870 characters. volume name - volume deleted from
Explanation: The command indicated contains a
storage pool cloud url that exceeds the maximum Explanation: The process that deleted data for the
length allowed. volume shown has ended, and the volume has been
deleted.
command. System action: None.
User response: Reissue the command with a valid User response: None.
storage pool cloud url.
ANR2224W Discard Data process terminated for
ANR2220W This command will delete volume volume volume name - process canceled.
volume name from its storage pool after
Explanation: The process that was deleting data for
verifying that the volume contains no
the volume shown, in preparation for deleting the
data.
volume, has been canceled.
Explanation: A DELETE VOLUME command with the
System action: The server does not delete the volume.
Discarddata=No option has been entered.
continue with the command.
ANR2225W Discard Data process terminated for
User response: To process the DELETE VOLUME
volume volume name - volume still
command, enter 'Y' to continue or 'N' to stop the
contains data.
process.
ANR2221W This command will result in the
volume, has ended. However, the volume contains
deletion of all inventory references to
data.
the data on volume volume name, thereby
rendering the data unrecoverable. System action: The server does not delete the volume.
If the volume being deleted contains
deduplicated data, the server invalidates User response: Contact your service representative.
all files that reside in the storage pool
that are dependent upon the data stored ANR2226W Discard data process terminated for
on this volume. Files on other volumes volume volume name - sufficient recovery
might be marked as damaged and result log space is not available.
in warning messages when that data is
accessed. Explanation: The process that was deleting data for
Explanation: A DELETE VOLUME command with the volume, has ended due to a shortage of recovery log
Discarddata=Yes option has been entered. space.
System action: The system asks whether you wish to System action: The server does not delete the volume.
User response: To process the DELETE VOLUME that is available to the server, evaluate the directories
command, enter 'Y' to continue or 'N' to stop the and file systems that are assigned to the
process. ACTIVELOGDIRECTORY, ARCHIVELOGDIRECTORY,
ANR2222I Discard Data process started for volume dsmserv.opt file. An out of log space condition might
volume name (process ID process ID). occur because the ACTIVELOGDIRECTORY location is
full.
Explanation: As a result of a DELETE VOLUME
command with the Discarddata=Yes option, the process Alternatively, an out of log space condition might occur
whose ID is displayed has begun to delete the data on if there are log files in the ACTIVELOGDIRECTORY
the volume shown. location that are no longer active and cannot be
System action: The server deletes the data on the ARCHFAILOVERLOGDIRECTORY locations. If
volume. necessary, specify a larger directory for the

ANR2227W Discard data process terminated for ANR2233W This command will move all of the data
volume volume name - sufficient memory stored on volume volume name to other
is not available. volumes in storage pool storage pool
name; the data will be inaccessible to
users until the operation completes.
volume, has ended due to a shortage of memory. Explanation: A move data has been entered that will
move data from the indicated volume to volumes in
the storage pool shown. While the data is being moved
User response: See the documentation for the it will not be available to users.
application.
continue.
ANR2228W Discard data process terminated for
command or 'N' to end the process.
volume volume name - lock conflict
detected.
ANR2234W This command will halt the server; if
the command is issued from a remote
client, it may not be possible to restart
volume, has ended due to a locking conflict.
the server from the remote location.
Explanation: A HALT command has been entered.
User response: Reissue the command at a later time. If
this problem persists, contact your service
continue.
representative.
User response: Enter 'Y' to halt the server or 'N' to
leave the server activated.
ANR2229W Discard data process terminated for
volume volume name - internal server
error detected. ANR2235W This command will remove
administrator adminName. This
administrator has defined or updated
schedules. Removing this authority
volume, has ended due to a server internal error.
WILL cause these schedules to fail.
System action: The server does not delete the volume
Explanation: A REMOVE ADMINISTRATOR
User response: Examine the server messages that were command has been entered for an administrator that
issued prior to this message to determine the source of owns administrative schedules. If you confirm that you
the error. Issue the QUERY ACTLOG command to view want to proceed with this command, the schedules
the activity log and search for messages that indicate owned by this administrator will fail when executed in
the source of the error. the future.
ANR2232W This command will move all of the data continue with the command.
stored on volume volume name to other
User response: To process the REMOVE
volumes within the same storage pool;
ADMINISTRATOR command, enter 'Y' to continue or
the data will be inaccessible to users
'N' to stop the process. To deal with schedules owned
until the operation completes.
by the administrator, use the QUERY SCHEDULE
Explanation: A move data has been entered that will command OR an SQL SELECT statement on the
move data from the indicated volume to other volumes ADMIN_SCHEDULES table to determine which
in the same storage pool. While the data is being schedules were last updated by the administrator. Use
moved, it will not be available to users. the UPDATE SCHEDULE command to update those
schedules under an administrator that has authority to
System action: The administrator is asked whether to execute them, or use the DELETE SCHEDULE
continue. command to remove the schedules.
command or 'N' to end the process. ANR2236W This command has removed
schedules. This WILL cause these
schedules to fail in the future.

Explanation: A REMOVE ADMINISTRATOR

ANR2240E Command: Storage pool cloud identity
command has been entered and the administrator
exceeds 255 characters.
removed owns administrative schedules. The schedules
will fail when executed in the future because they do Explanation: The command indicated contains a
not belong to a valid administrator. storage pool cloud identity that exceeds the maximum
length allowed.
System action: The system removes the administrator.
User response: Use the QUERY SCHEDULE command
command.
OR an SQL SELECT statement on the
ADMIN_SCHEDULES table to determine which User response: Reissue the command with a valid
schedules were last updated by the administrator. Use storage pool cloud identity.
the UPDATE SCHEDULE command to update those
ANR2241E Command: Storage pool cloud password
execute them, or use the DELETE SCHEDULE
exceeds 255 characters.
command to remove the schedules.
Explanation: The command indicated contains a
storage pool cloud password that exceeds the
ANR2237W This command has revoked privileges
maximum length allowed.
for administrator adminName. This
administrator has defined or updated System action: The server does not process the
schedules. This may cause these command.
schedules to fail in the future.
Explanation: A REVOKE AUTHORITY command has storage pool cloud password.
been entered.
System action: The system removes the authority. ANR2242E Command: The cloud url for the cloud
storage pool contains no information.
Explanation: There is no valid cloud url in this
command.
deletion of all inventory references to System action: The IBM Spectrum Protect server does
the data on filespaces that match the not process the command.
pattern filespace name for node node name,
whereby rendering the data User response: Reissue the command with a valid
unrecoverable. cloud url.
Explanation: A DELETE FILESPACE command has

been entered. ANR2243E Command: Provide the cloud storage pool
identity.
continue with the command. Explanation: A cloud storage pool identity is
necessary for this command.
User response: To process the DELETE FILESPACE
command, enter 'Y'; otherwise, enter 'N'. System action: The IBM Spectrum Protect server does
not process the command.
ANR2239W This command will revoke privileges User response: Reissue the command with a valid
for administrator adminName. This cloud storage pool identity.
schedules. Revoking this authority may ANR2244I Activity Summary pruning started:
cause schedules to fail. removing entries prior to date time.
Explanation: A REVOKE AUTHORITY command has Explanation: Server activity summary records older
been entered. than the date and time indicated are being removed
System action: The system asks whether you wish to from the activity summary.
continue with the command. System action: None.
User response: To process the REVOKE AUTHORITY User response: None.
process.


ANR2245I Activity summary pruning completed:
number of records records removed.
ANR2251S The ACCESS setting for storage pool
Explanation: All expired (older than the summary
poolname was changed from access to
archive retention value) server activity summary
UNAVAILABLE. The pool is enabled for
records have been removed; the number of records
encryption, but the master encryption
deleted is shown.
key for the server is not available.
Explanation: The server either does not have a master
User response: None. encryption key or the master encryption key is not
available. Encrypted storage pool data cannot be read
from or written to the storage pool.
ANR2246I Vary online process initiated for
database volume volume name (process System action: The storage pool ACCESS setting was
ID process ID). changed to UNAVAILABLE.
Explanation: In response to a VARY ONLINE User response: Verify that the server password file,
command, the process with the process ID shown has dsmserv.pwd, exists and can be read by the server. If
been started to vary on the database volume indicated. necessary, recover the password file from a backup.
System action: None. If the server password recently changed, ensure that
the password file does not predate the change. If it
predates the change, issue the SET SERVERPASSWORD
command to reset the server password to the earlier
ANR2247I Database volume volume name varied value. Restart the server. If the encryption key can be
offline. read by the server, ensure that the server has read and
write access to the password file. Reissue the SET
Explanation: A VARY OFFLINE command has put the SERVERPASSWORD command to change the server
indicated database volume into an offline state. password again.
System action: None. After the server password file becomes available to the
User response: None. server, restart the server and issue the UPDATE
STGPOOL command to change the ACCESS setting to
its original value.
ANR2248E Command: The cloud storage pool
password is missing.
ANR2252S The ACCESS setting for storage pool
Explanation: A cloud storage pool password is poolname was changed from access to
necessary for this command. UNAVAILABLE. The pool is enabled for
System action: The IBM Spectrum Protect server does encryption, but the master encryption
not process the command. key for the server was reset.
User response: Reissue the command with a valid Explanation: The master encryption key used to
cloud storage pool password. protect data in encrypted storage pools changed,
possibly because the server password file,
dsmserv.pwd, was deleted. The server cannot read
ANR2249I Storage pool storage pool name is defined. existing data that was encrypted because it no longer
Explanation: A DEFINE STGPOOL command has has access to the encryption key used to protect the
created the storage pool. data.
System action: None. System action: The storage pool ACCESS setting was
changed to UNAVAILABLE.
User response: Rename the server password file,
dsmserv.pwd, and recover an earlier version of the
ANR2250E command: Operation is not allowed password file from a backup. Restart the server. Issue
because node nodename is the UPDATE STGPOOL command to change the
decommissioned. storage pool ACCESS setting back to its original value.
Explanation: You might be able to restore or retrieve
data from a decommissioned client node, but you ANR2253E Command: You cannot specify the
cannot store new data or alter existing data. ENCRYPT=YES parameter because the
server master encryption key is
System action: Client sessions that attempt to store
unavailable.
new data or change existing data will be terminated
with a protocol error. Explanation: Encryption cannot be enabled for a

storage pool because the server master encryption key System action: The server does not process the
is not available. command for the indicated node. If multiple nodes
were specified on the command, the server may
continue processing the command for the other nodes.
User response: Reissue the command and specify
User response: Examine previous messages for any
ENCRYPT=NO.
additional information. Issue the command from a
If encryption is required, review the activity log for properly authorized administrator ID, or contact the
errors related to either the server master encryption key system administrator to have additional authority
or the server password file. Correct any problems that granted to the current administrator ID.
prevent the master encryption key being read from the
server password file.
ANR2258E Command: Invalid summary retention
period - retention value.
ANR2254E Command: The VOLUMENAMES
Explanation: A SET SUMMARYRETENTION
parameter must be specified when
command has been entered that specifies an invalid
SCRATCH=NO is specified.
retention period.
Explanation: The SCRATCH parameter is specified as
NO for the command Command but the
command.
VOLUMENAMES parameter is not specified. When
scratch volumes are not allowed, the VOLUMENAMES User response: Reissue the command with a valid
parameter must be specified to indicate the volumes retention period.
that can be used for the command.
System action: The command fails. ANR2259I Summary retention period set to number
of days days.
valid VOLUMENAMES parameter. Explanation: The number of days that activity sumary
records are kept in the server database has been set to
the value indicated with the SET
ANR2255E Command: The VOLUMENAMES
SUMMARYRETENTION command.
parameter must be specified.
Explanation: The VOLUMENAMES parameter must
be specified to indicate the volumes that can be used User response: None.
for the command.
System action: The command fails. ANR2260W The version of IBM Spectrum Protect is
not compatible with this operating
system.
valid VOLUMENAMES parameter.
Explanation: The command cannot be processed on
this operating system.
ANR2256E Command: The RETENTION parameter
must be specified. System action: The operation fails.
Explanation: The RETENTION parameter must be User response: Use an operating system that is
specified to indicate the retention period to be used for compatible with IBM Spectrum Protect to issue this
the command. command. For information about operating systems
that are supported by IBM Spectrum Protect, see
technote 1243309 "Overview - IBM Spectrum Protect
User response: Reissue the command and specify a Supported Operating Systems" (http://www-
valid RETENTION parameter. 01.ibm.com/support/docview.wss?uid=swg21243309).
ANR2257E Command: Administrator administrator ANR2261W The server password file, password file
name is not authorized to issue this name, was not found. A new master
command for node node name. encryption key will be created and
stored in a new password file.
the indicated command, but this administrator does not Explanation: The master encryption key cannot be
have the proper authority necessary to run the read from the password file because the file does not
command for the indicated node. Note: This message exist.
can be issued as a result of the server option
System action: A new master encryption key will be
REQSYSAUTHOUTFILE YES being in effect.
created and stored in the server password file.

User response: If storage pool encryption is not in System action: None.

use, no action is required.
If existing storage pools contain encrypted data, restore
the server password file. Restore it to a version that
ANR2267I Recovery log volume volume name varied
contains the master encryption key that was used to
offline.
protect the encrypted storage pool data. Restart the
server. Explanation: A VARY OFFLINE command has put the
recovery log volume indicated into an offline state.
ANR2262E Unable to read from the server System action: None.
password file, password file name; reason:
error reason. User response: None.
Explanation: The server could not read the master

encryption key from the server password file. ANR2268W ENCRYPTED value encryption value was
not changed when the
System action: None. CLOUDLOCATION parameter was
updated to cloudlocation value.
User response: Correct the problem identified in the
error reason and restart the server. Explanation: The ENCRYPTION value does not
automatically change when you change the
CLOUDLOCATION value in the UPDATE STGPOOL
ANR2263E Unable to write to the server password
command.
file, password file name; reason: error
reason. System action: None.
Explanation: The server could not write the master User response: If you want to turn encryption off,
encryption key to the server password file. change the ENCRYPTION value to OFF.
ANR2269E The PROTECTKEYS=NO parameter
User response: Correct the problem identified in the
cannot be specified on the SET
error reason and restart the server.
DBRECOVERY command because one
or more storage pools are enabled for
ANR2264E Corruption detected reading from the encryption.
server password file, password file name.
Explanation: The SET DBRECOVERY command failed
The master encryption key cannot be
because PROTECTKEYS=NO was specified and one or
read.
more storage pools are enabled for encryption.
Explanation: The server detected corruption in the
server password file while attempting to read the
command.
master encryption key. The master encryption key
could not be read. User response: Issue the SET DBRECOVERY
command without the PROTECTKEYS=NO parameter.
User response: Recover the password file from a
ANR2270E The PROTECTKEYS parameter is not
backup. Restart the server.
enabled.
Explanation: The master encryption key must be set
ANR2265E The SERVERPASSWORD cannot be
before you enable the PROTECTKEYS parameter.
blank.
Explanation: Encryption does not work if the
command.
password is not set.
User response: Issue the SET SERVERPASSWORD
command to set and protect the master encryption key.
User response: Set the server password.
ANR2266I Vary online process initiated for deletion of all inventory references to
recovery log volume volume name damaged data in stgpool stgpool.
(process ID process ID).
Explanation: A REMOVE DAMAGE command has
Explanation: In response to a VARY ONLINE been entered.
command, the process with process ID shown has been
started to vary on the recovery log volume indicated.

continue with the command. this situation, automatic password changes might
update the same password twice. As a result, the
User response: To process the REMOVE DAMAGE
password might become unknown to the
administrative user ID. Alternatively, password update
process.
operations might fail.
System action: System operations continue.
ANR2273E A protection or replication operation
failed because a container is not User response: To avoid password management
available. issues, complete the following steps: 1. Remove the
specified administrative user ID by using the REMOVE
Explanation: The server cannot complete the operation
ADMIN command. For example, if the administrator is
because it cannot access data in a container.
ADMIN6, issue the following command: remove admin
System action: The operation fails and server admin6 2. Register a different administrative user ID
operation continues. for client owner operations by using the REGISTER
ADMIN command. For example, if the administrator is
User response: For details about the problem, see the ADMIN6 and you want to authenticate with an LDAP
first-failure data capture (FFDC) log for the server. By server, issue the following command: register admin
default, the log is named dsmffdc.log and is in the admin6 authentication=ldap 3. Grant client owner
server instance directory. Validate the data in the privileges to the new administrative user ID by using
container that caused the problem by issuing the the GRANT AUTHORITY command. For example, if
AUDIT CONTAINER command. If the command the administrator is ADMIN6 and the node name is
results show that the container is damaged, repair the NODE2, issue the following command: grant authority
storage pool by using the REPAIR STGPOOL admin6 classes=node authority=owner node=node2
command. Then, retry the operation that failed.
ANR2280I Full database backup started as process

ANR2274W Operation is not allowed because the process ID.
VM backed up to filespace filespacename
is decommissioned. Explanation: A background process was started to
backup the contents of the database. The full database
Explanation: The filespace is a decommissioned VM backup process was assigned the process ID shown.
and will not be processed by this command.
System action: The database backup process starts
System action: Processing will continue with the next and server operation continues.
filesystem in the list.
User response: The administrator may query the
User response: None. status of the database backup process by using the
QUERY PROCESS command, or cancel the process with
ANR2275I Data Base Space trigger defined, but is the CANCEL PROCESS command.
disabled.
Explanation: A database space trigger has been ANR2281I Incremental database backup started as
defined, but because the space expansion percentage is process process ID.
currently set to 0, the space trigger is disabled. Explanation: A background process was started to
System action: None. backup the contents of the database. The incremental
database backup process was assigned the process ID
User response: To activate the space trigger, use the shown.
UPDATE SPACETRIGGER command to set the space
expansion percentage to a value greater than 0. System action: The database backup process starts
ANR2276W The administrative user ID administrator User response: The administrator may query the
name matches a node name. The status of the database backup process by using the
matching names can cause password QUERY PROCESS command, or cancel the process with
management issues if you are the CANCEL PROCESS command.
authenticating users with a Lightweight
Directory Access Protocol (LDAP) server ANR2282E Command name has already been started
in integrated mode. for storage pool Stgpool.
Explanation: Integrated mode means that users Explanation: An audit container process has already
authenticate with an LDAP server by using IDs that are been started for the storage pool.
defined on that server. If you are using integrated
mode, and have a matching administrative user ID and System action:
node name, they resolve to a single LDAP user ID. In

User response: Wait for the current audit container System action: The server does not process the
process to complete. command.
User response: Reissue the DEFINE STGPOOL
ANR2283E Command: Storage pool bucket name command with a pool type and a device class name
exceeds 63 characters. that are compatible. For details about the compatibility
of storage pool types and device classes, see the help
Explanation: The command contains a storage pool
for the DEFINE STGPOOL command.
bucket name that exceeds the maximum length
allowed.
ANR2297I Command: Optionset optionset name,
option option name, sequence number old
command.
sequence number, has been changed to
User response: Reissue the command with a valid new sequence number.
storage pool bucket name.
Explanation: The requested option sequence number
has been updated in response to an UPDATE
ANR2287I Snapshot database backup started as CLIENTOPT command.
process process ID.
backup the contents of the database. The snapshot
database backup process was assigned the process id
shown. ANR2298I Command: Optionset optionset name,
option option name, sequence number old
System action: The database backup process starts
sequence number, is not updated.
Explanation: The requested option sequence number
is not updated in response to an UPDATE CLIENTOPT
started process by using the QUERY PROCESS
command.
command, or may cancel the process using the
CANCEL PROCESS command. System action: None.
User response: Reissue the UPDATE CLIENTOPT
ANR2288I Subfile set to state. command with a valid old sequence number.
Explanation: The SET SUBFILE command has been
used to specify whether this server will allow clients to ANR2299I Password expiration period for
back up subfiles. If a value of CLIENT is specified, administrator administrator name set to
clients are given the option of backing up subfiles. If a number of days days.
value of NO is specified, clients are not allowed to back
Explanation: The number of days that the
up subfiles.
administrator's password can be used before it must be
System action: None. changed has been set to the value indicated with the
SET PASSEXP command.
ANR2289I Administrative userid admininstrator User response: None.
name defined for authority over node
node name has not been removed.
ANR2300E Could not open "file spec" the server help
Explanation: The specified administrator was not file.
removed.
Explanation: The named help file could not be
System action: None. accessed.
User response: None. System action: The requested help text is not
displayed.
ANR2296E Command: The pool type pool type for User response: Contact the system administrator.
storage pool pool name is not compatible
with the device class class name.
ANR2301W No filespaces found for specified
Explanation: The DEFINE STGPOOL command was node(s).
issued with conflicting pool type and device class
Explanation: None of the node(s) specifed had a
parameters.
filespace.l

System action: None. User response: To recover the damaged file use the
RESTORE STGPOOL or RESTORE VOLUME command.
User response: Specify at least one node with a
filespace.
ANR2310W This command will compare all
inventory references to volume volume
ANR2303E There is no help section numbered
name with the actual data stored on the
section number.
volume and will report any
Explanation: The numeric operand supplied on the discrepancies; the data will be
HELP command is either less than 1 or greater than the inaccessible to users until the operation
highest-numbered entry in the help index. completes.
System action: The server does not process the HELP Explanation: During the execution of an AUDIT
command. VOLUME command, any data the volume named
would be unavailable to users.
User response: Issue the HELP command with no
operands and select from the numbered list (help System action: The administrator is asked whether to
index) displayed in response. continue.
ANR2306E No help text could be found for this stop the process.
command/subcommand: command.
Explanation: The operands you entered for the HELP ANR2311W This command will discard any
command, although valid command/subcommand inventory references to volume volume
names, do not match any named entry into the file of name associated with missing or
help text. inconsistent stored data, thereby
rendering the data unrecoverable; the
System action: The server does not process the HELP valid data on the volume will be
command. inaccessible to users until the operation
User response: Contact the system administrator. completes.
Explanation: During the execution of an AUDIT
ANR2307E No help text could be found for this VOLUME command, any data the volume named
message: message ID. would be unavailable to users. After the command has
ended, any inconsistent data found will be discarded.
Explanation: The message ID you entered for the help
command does not match any message entry in the file System action: The administrator is asked whether to
of help text. continue.
System action: The help command is not processed. User response: Enter 'Y' to audit the volume or 'N' to
stop the process.
User response: Contact the system administrator.
ANR2312I Audit Volume (Repair) process started

ANR2308W Audit Volume marking damaged file as for volume volume name (process ID
damaged on volume volume name: Node process ID).
node name, Type file type, File space
filespace name, fsId filespace id, File Name Explanation: As the result of an AUDIT VOLUME
file name is number version of total command that specified FIX=YES for the volume
versions versions. shown, the process whose ID is displayed has begun
auditing the volume.
Explanation: As the result of an AUDIT VOLUME
command that specified FIX=YES for the volume System action: The volume is audited and
shown, the file whose information is displayed is inconsistent data is discarded.
marked as damaged in the server. The file is marked as User response: None.
damaged because it can be recovered from a copy
known to exist in a COPY storage pool. If this file
belongs to an aggregate, the entire aggregate is marked ANR2313I Audit Volume (Inspect Only) process
damaged, and this message will be issued for every file started for volume volume name (process
in the aggregate. The version numbers for the file are ID process ID).
numbered from most recent (1) to least recent (n, where
n is the total number of versions.
command that specified FIX=NO for the volume
System action: The file is marked as damaged in the shown, the process whose ID is displayed has begun
server database. auditing the volume.

System action: The volume is audited and User response: Attempt to correct the cause of the
inconsistent data is displayed. read error, and reissue the command.
ANR2320W Audit volume process terminated for
volume volume name - data transfer
ANR2316W Audit Volume deleting damaged file on
interrupted.
volume volume name: Node node name,
Type file type, File space filespace name, Explanation: During processing of an AUDIT
fsId filespace id, File Name file name is VOLUME command for the volume shown, a data
number version of total versions versions. transfer operation has been interrupted and cannot be
continued.
command that specified FIX=YES for the volume System action: The AUDIT VOLUME command is
shown, the file whose information is displayed is ended.
deleted from the server. The version numbers for the
file are numbered from most recent (1) to least recent
cause of the interruption, and reissue the command.
(n, where n is the total number of versions.
System action: The file is deleted.
User response: None. volume volume name - storage media
inaccessible.
ANR2317W Audit Volume found damaged file on Explanation: During processing of an AUDIT
volume volume name: Node node name, VOLUME command for the volume shown, a required
Type file type, File space filespace name, volume cannot be mounted.
fsId filespace id, File name file name is
System action: The AUDIT VOLUME command is
number version of total versions versions.
ended.
command that specified FIX=NO for the volume
shown, the file whose information is displayed is found
to be in error and not accessible. If this file belongs to ANR2322W Audit volume process terminated for
an aggregate, the entire aggregate is marked damaged, volume volume name - sufficient recovery
and this message will be issued for every file in the log space is not available.
aggregate. The version numbers for the file are
numbered from most recent (1) to least recent (n, where Explanation: During processing of an AUDIT
n is the total number of versions. VOLUME command for the volume shown, the server
does not have sufficient recovery log space to continue.
User response: None. ended.
User response: If necessary, make more recovery log
ANR2318W Audit volume process terminated for space available to the server.
volume volume name - process canceled.
Explanation: During processing of an AUDIT ANR2323W Audit volume process terminated for
VOLUME command for the volume shown, the process volume volume name - sufficient database
performing the audit was canceled. space is not available.
System action: The AUDIT VOLUME command is Explanation: During processing of an AUDIT
ended. VOLUME command for the volume shown, the server
does not have sufficient database space to continue.
ended.
volume volume name - error reading User response: If necessary, make more database
device. space available to the server.
Explanation: During processing of an AUDIT
VOLUME command for the volume shown, an
unrecoverable read error occurred on the volume.
ended.

VOLUME process was unable to locate this object on

the specified volume. Normally, this action is not
volume volume name - thread resource
considered an error condition, because the object was
not available.
probably deleted by a process such as a DELETE
Explanation: During processing of an AUDIT FILESPACE command.
VOLUME command for the volume shown, the server
System action: Processing of the AUDIT VOLUME
cannot start a thread for the audit process.
command continues.
User response: Check the activity log to verify that
ended.
some process (such as a DELETE FILESPACE
User response: Reissue the AUDIT VOLUME command) was in progress during the AUDIT
command. If the error persists, it may indicate a VOLUME command that would account for the deleted
shortage of server memory. object. If no such process can be identified, contact your
volume volume name - sufficient memory ANR2333W Missing or incorrect information
is not available. detected by AUDIT VOLUME for
volume volume name.
VOLUME command for the volume shown, the server Explanation: An AUDIT VOLUME command detects
does not have enough memory available to complete missing or incorrect information for the specified
the command. volume.
System action: The AUDIT VOLUME command is System action: Audit processing continues.
ended.
User response: Reissue the audit command with
User response: If necessary make more memory FIX=YES so that the information can be created or
available to the server. corrected.
ANR2326W Audit volume process terminated for ANR2334W Missing or incorrect information
volume volume name - lock conflict detected by AUDIT VOLUME for
detected. volume volume name - information will
be created or corrected.
VOLUME command for the volume shown, the server Explanation: An AUDIT VOLUME process detects
cannot obtain a required lock. missing or incorrect information for the specified
volume. Because FIX=YES has been specified for the
audit command, the information is created or corrected.
ended.
System action: Audit processing continues.
User response: Reissue the command.
volume volume name - internal server ANR2335W Audit Volume has encountered an I/O
error detected. error for volume volume name while
attempting to read: Node node name,
Type file type, Filespace filespace name,
VOLUME command for the volume shown, an internal
fsId filespace id, File Name file name.
server error occurs.
Explanation: The AUDIT VOLUME process
encountered an I/O error for the specified volume
ended.
while attempting to read the specified file. If this file
User response: Contact your service representative. belongs to an aggregate, the entire aggregate is marked
damaged, and this message will be issued for every file
in the aggregate.
ANR2332W Object object.ID deleted by another
process during execution of an AUDIT System action: None.
VOLUME command for volume volume
User response: Identify and resolve the I/O error for
name.
the volume if possible. Verify that the volume's device
Explanation: During processing of an AUDIT is functioning properly and that the volume is usable.
VOLUME command, a data storage object was deleted For example, if the volume is a tape volume, make sure
from the volume that was being audited. The AUDIT the drive is clean or that the tape volume is usable by

testing it by using a different drive.

ANR2340E Command: Invalid storage pool name -
storage pool name.
ANR2336W Audit Volume terminated for volume
Explanation: The command indicated contains an
volume name - insufficient number of
invalid storage pool name.
media. System action: The server does not process the
command.
Explanation: During Audit Volume for the indicated
volume, the server could not allocate sufficient mount User response: Reissue the command with a valid
points for the volume required. storage pool name.
System action: Audit Volume stops.
ANR2341E Command: Missing next storage pool
name.
available.
Explanation: The command indicated requires a
storage pool name, but none has been entered.
ANR2337W Header size is reset for object Object ID,
verb type (Verb Type), from (Header Size) System action: The server does not process the
to (Verb Length). command.
Explanation: The header size for the specified object User response: Reissue the command with a storage
was recalculated while anditing a volume. pool name.
System action: If FIX=YES was specified, the header
size for the object will be updated. Processing ANR2342E Command: Storage pool description
continues. exceeds maximum characters characters.
User response: None. Explanation: The command indicated contains a
storage pool description that exceeds the maximum
length allowed.
ANR2338E Diagnostic(ID): Invalid header received
for object ObjectID, length Data Length. System action: The server does not process the
Size (Header Size), pushed (Pushed command.
Length), skipped (Skipped Length), status
(New Retrieve). Found length (Verb
storage pool description.
Length), type (Verb Type), size (Verb Size).
Explanation: An invalid header was detected for the
ANR2343E Command: Invalid device class name -
specified object while auditing a volume. Diagnostic
device class name.
information is included in the message.
System action: If FIX=YES was specified, this object
invalid device class name.
will be marked damaged. Processing continues.
User response: Restore the volume or storage pool
command.
that includes this object.
device class name.
ANR2339E Command: Object sets still exist for node
node name.
ANR2344E Command: The "option" option is not
Explanation: A REMOVE NODE command has been
valid for device class device class name.
entered for a node for which the server is still storing
backup sets. To remove a node, the node must not have Explanation: The command indicated specifies an
any files or backup sets stored on the server. option shown that is not valid for a storage pool that
belongs to the device class shown.
command.
User response: To remove the node, delete all backup
sets from the server and reissue the command. User response: Reissue the command with options
appropriate to the device class.

ANR2345E Command: Invalid volume name - volume ANR2351E Command: Device class device class name
name. is not defined.
Explanation: The command indicated contains an Explanation: The command indicated references a
invalid volume name. device class that does not exist.
command. command.
volume name.
ANR2352E Command: Device class device class name
ANR2346E Command: Volume name "volume name" is may not be deleted.
not valid for device class device class
Explanation: A DELETE DEVCLASS command
name.
specifies the class name DISK, which is a
Explanation: The command indicated specifies the system-defined device class and may not be deleted.
name of a volume that cannot be used with the device
class shown.
command.
command.
volume name.
may not be updated.
Explanation: An UPDATE DEVCLASS command
ANR2347E Command: Volume name "volume name" is
specifies the class name DISK, which is a
ambiguous; resolves to multiple defined
system-defined device class and may not be changed.
volume names.
Explanation: The command shown was entered with a
command.
volume name pattern that matches more than one
volume. The command can only process a single User response: None.
volume.
System action: The command is not executed. ANR2354E Command: Device class device class name
is still referenced by one or more
User response: Reissue the command with a more
storage pools, or database backup, or
specific volume name.
export volumes or backupset volumes.
Explanation: The DELETE DEVCLASS command has
attempted to delete a device class that has storage
valid for a volume assigned to a primary
pools assigned to it, or is referenced by database
storage pool.
backup, export volumes or backupset volumes.
Explanation: The command indicated specifies an
option that is not valid for a volume in a primary
command.
storage pool.
User response: Issue Q DEVCLASS to view the
storage pool reference count, Q STGPOOL to determine
command.
which pool references the device class, and Q VOLHIST
User response: Reissue the command with valid to locate database backup or export volume or
options for a volume in a primary storage pool. backupset volume references.
ANR2350E Command: Device class device class name ANR2355E Command: Required parameter is
is already defined. missing - missing parameter.
Explanation: The command indicated has attempted Explanation: The specified server command has been
to define a device class that already exists. entered without the required parameter. The required
parameter is shown.
command. System action: The server ignores the command.
User response: None. User response: Reissue the command and enter the
proper syntax.

ANR2356E Command: Incompatible parameters ANR2364E Command: Missing reclaim-storage pool

specified - first parameter, second name.
parameter.
Explanation: The command indicated requires a
Explanation: The specified server command has been storage pool name, but none has been entered.
entered with mutually exclusive parameters. The two
parameters are listed.
command.
User response: Reissue the command with a storage
User response: Reissue the command and enter the pool name.
proper syntax.
ANR2365I Backupset backup set name for node node
ANR2357E Command: The DISK device class is not name (data type data type) has been
supported for copy storage pools. deleted.
Explanation: An attempt is made to define a copy Explanation: The backup set has been deleted.
storage pool using a device of DISK. Copy storage
System action: The server has deleted the backupset.
pools can only be assigned to a sequential device class.
command.
ANR2366I Backupset backup set name for node node
name (data type data type) would have
sequential device class.
been deleted.
Explanation: The backup set would have been deleted
ANR2359E Command: Volume name "volume name"
as the result of a DELETE BACKUPSET command, but
must be specified with a DISK or FILE
the PREVIEW=YES parameter was specified.
STGPOOL.
name of a volume that must be specified with a storage User response: If the backup set is to be deleted,
pool associated with a device class of type DISK or reissue the command without specifying
FILE. PREVIEW=YES.
command. ANR2367I Retention period for backupset backup
set name for node node name (data type
data type) has been updated.
volume name and storage pool.
Explanation: The backup set's retention period has
been updated.
may not be used for database backup. System action: The server has updated the
backupset's retention period.
Explanation: The command specifies the DISK device
class, which cannot be used for database backup, User response: None.
backup trigger, or restore operations.
System action: The server does not process the ANR2368I Retention period for backupset backup
command. set name for node node name (data type
data type) would have been updated.
device class. Explanation: The backup set's retention period would
have been updated as the result of an UPDATE
BACKUPSET command, but the PREVIEW=YES
ANR2361E Command: A full database backup is
parameter was specified.
required.
Explanation: A BACKUP DB command specified an
incremental backup, but a full backup is required. User response: If the backup set is to be updated,
reissue the command without specifying
PREVIEW=YES.
command.
User response: Reissue the command specifying a full
backup.

ANR2369I Database backup volume and recovery ANR2382E Command: Storage pool storage pool name
plan file expiration starting under still contains at least one volume.
process process ID.
Explanation: A DELETE STGPOOL command specifies
Explanation: The server has started expiration a storage pool that has volumes assigned to it.
processing to remove expired database backup volumes
and recovery plan files created on a remote server. This
command.
message is issued only if DRM is licensed on the
server. The DB backup volumes expired is based on the User response: Delete the volume belonging to the
value specified on the SET storage pool and reissue the command.
DRMDBBACKUPEXPIREDAYS. The recovery plan files
expired is based on the value specified on the SET
DRMRPFEXPIREDAYS. Server inventory expiration ANR2383E Command: Storage pool storage pool name
processing deletes the DB backup volumes and is currently in use by clients and/or data
recovery plan files only if the volumes or plan files are management operations.
created on the server to server virtual volumes. Explanation: The command indicated references a
System action: Server operation continues. The storage pool that is in use.
expiration process is cancellable. System action: The server does not process the
User response: None. command.
User response: Reissue the command at a later time.
ANR2376I Recovery Log Space trigger defined, but
is disabled. ANR2384E Command: Next or Reclaim storage pool
Explanation: A recovery log space trigger has been storage pool name introduces a cycle into
defined, but because the space expansion percentage is the storage pool chain.
currently set to 0, the space trigger is disabled. Explanation: A DEFINE STGPOOL or UPDATE
System action: None. STGPOOL command specifies a next storage pool that
eventually points to the pool being processed.
User response: To activate the space trigger, use the
UPDATE SPACETRIGGER command to set the space System action: The server does not process the
expansion percentage to a value greater than 0. command.
ANR2380E Command: Storage pool storage pool name next pool value.
is not defined.
Explanation: A nonexistent storage pool is specified ANR2385E Command: Storage pool storage pool name
for the issued command. is in use as the next or reclaim pool for
one or more other storage pools.
command. Explanation: A DELETE STGPOOL command specifies
a pool that is the next pool or the reclaim pool for
User response: Reissue the command with a valid other storage pools.
storage pool name. If you are using the MACRO
command to define and update the storage pool, you System action: The server does not process the
must ensure that the DEFINE STGPOOL command is command.
committed before the UPDATE STGPOOL command is User response: If necessary, update other storage
issued. pools so that they do not reference the pool to be
deleted, and reissue the command.
is already defined. ANR2386E Command: High migration threshold
Explanation: A DEFINE STGPOOL command specifies must be set greater than or equal to the
the name of a storage pool that already exists. low migration threshold.
System action: The server does not process the Explanation: A DEFINE or UPDATE STGPOOL
command. command has attempted to set the storage pool low
migration threshold (LOWMIG) parameter greater than
User response: None. the high migration threshold (HIGHMIG).
command.

User response: Reissue the command with a low

ANR2391E Command: Server could not write device
migration threshold less than or equal to the high
configuration information to file name.
migration threshold.
Explanation: The BACKUP DEVCONFIG command
does not successfully complete because the server
cannot write to the file name specified.
is not a primary pool.
command.
name of a storage pool which is not a primary pool.
The command syntax requires that a primary storage User response: Make sure that the server has proper
pool name be specified. authority to write to the file indicated and that
sufficient space is available in the file system for the
file. On MVS, make sure that the data set has been
command.
allocated and that the server has authority to write to
User response: Reissue the command with a valid the data set.
primary storage pool name.
ANR2392E Command: An internal error was
ANR2388E Command: Storage pool storage pool name encountered in writing device
is not a copy or an active-data pool type configuration information to file name.
pool.
Explanation: The BACKUP DEVCONFIG command
Explanation: The command indicated specifies the does not successfully complete because the server
name of a storage pool which is not a copy pool or an cannot write to the file name specified.
active-data pool. The command syntax requires that a
copy storage pool name or an active-data pool name be
command.
specified.
User response: Examine error messages on the server
console that may have been displayed prior to this
command.
message and correct any problems, if possible. Make
User response: Reissue the command with a valid sure that the server has proper authority to write to the
copy storage pool name or active-data pool name. file indicated and that sufficient space is available in
the file system for the file. On MVS, make sure that the
data set has been allocated and that the server has
ANR2389E Command: The "option" option is not authority to write to the data set.
valid for a primary storage pool.
Explanation: The command indicated specifies an ANR2393I Command: Server device configuration
option that is not valid for a primary storage pool. information was written to file name.
System action: The server does not process the Explanation: This message is displayed in response to
command. the BACKUP DEVCONFIG command and indicates
User response: Reissue the command with options that device configuration information was successfully
appropriate for a primary storage pool. written to the file name indicated.
System action: The server records device
ANR2390E Command: The "option" option is not configuration information to the file name specified
valid for a pool type storage pool. User response: None.
option that is not valid for either a copy, active-data, or ANR2394I Command: Server device configuration
copy container type storage pool. information was written to all device
System action: The server does not process the configuration files.
command. Explanation: This message is displayed in response to
User response: Reissue the command with options the BACKUP DEVCONFIG command and indicates
appropriate for the specified storage pool type. that device configuration information was successfully
written to all files that were specified in the server
options file.
System action: The server records device
configuration information to the device configuration
files.


ANR2398E Command: The device configuration file
contains a statement with invalid
ANR2395I Command: Device configuration files syntax.
have NOT been defined for automatic
Explanation: While processing the device
recording - specify a file name for
configuration information, an invalid statement has
device configuration information.
been encountered.
System action: The server ends the operation being
the BACKUP DEVCONFIG command and indicates
performed.
that device configuration information cannot be written
because no files were specified in the options file. User response: Examine error messages on the server
System action: The device configuration information
message and correct any problems if you have
is not written. Server operation continues.
constructed the device configuration file manually.
User response: Reissue the BACKUP DEVCONFIG Make sure the statements are in the proper order. If
command and specify the name of a file to which you you let the server construct the device configuration file
would like to have device configuration information automatically, restart the server, refresh the device
recorded. If desired, you may configure files that configuration file by issuing the BACKUP DEVCONFIG
should be automatically updated with the command, and reissue the operation. If the problem
DEVCONFIG option and restart the server. persists, contact your service representative.
ANR2396E Command: An I/O error was encountered ANR2399E Command: Storage pool storage pool name
in writing device configuration is not a sequential pool.
information to one or more of the
defined device configuration files.
name of a storage pool which is not a sequential pool.
Explanation: The BACKUP DEVCONFIG command All storage pools are either fixed disk or sequential
does not complete successfully because the server archival. All tape devices, as well as optical and file
cannot write to one or more of the defined device device classes, are sequential.
configuration files.
command.
User response: Examine error messages on the server sequential storage pool name.
message and correct any problems, if possible. Make
ANR2400E Command: Volume volume name is already
sure that the server has proper authority to write to the
defined in a storage pool or has been
file indicated and that sufficient space is available in
used previously to store export, database
dump, or database backup information.
authority to write to the data set. Explanation: The command indicated specifies the
name of a storage pool volume that already exists or
has been used to store server export, database dump,
ANR2397E Command: An internal server error was
or database backup information as recorded in the
encountered in writing device
server volume history file.
configuration information to one or
more of the defined device System action: The server does not process the
configuration files. command.
Explanation: The BACKUP DEVCONFIG command User response: Specify a volume that is not in use, is
does not complete successfully because the server not defined in a storage pool, and which has not been
cannot write to one or more of the defined device previously used for an export, a database dump, or
configuration files. database backup operation as recorded in the server
volume history information. Use the QUERY VOLUME
command to display the names of volumes that are
command.
defined to server storage pools. Use the QUERY
User response: Examine error messages on the server VOLHISTORY command to display the names of
console that may have been displayed prior to this volumes that have been used for export, a database
message and correct any problems, if possible. Contact dump, or database backup operations.
your service representative if you are unable to resolve
the problem.

ANR2401E Command: Volume volume name is not ANR2406E Command: Volume volume name still
defined in a storage pool. contains data.
Explanation: The command indicated specifies the Explanation: The indicated command tries to delete a
name of a storage pool volume that does not exist. data storage volume that contains data.
command. command.
ANR2402E Command: Volume volume name is already ANR2407W Error encountered for storage pool
online. directory: STGPOOLDIRECTORY in
storage pool: STGPOOL Error: Error.
Explanation: A VARY ONLINE command specifies the
name of a volume that is already online. Explanation: The server encountered an error
accessing the specified directory.
command. System action: If appropriate, the operation is
attempted in another directory.
User response: Evaluate the warning and take
appropriate corrective action.
ANR2403E Command: Volume volume name is not
online.
ANR2410E Command: Unable to access volume
volume name - access mode is set to
name of a volume that is not online.
"unavailable".
Explanation: The command shown specifies the
command.
volume whose name is displayed, but the volume
User response: None. cannot be accessed because its status is unavailable.
ANR2404E Command: Volume volume name is not command.
available.
User response: If necessary, reset the status of the
Explanation: The command indicated has attempted volume and reissue the command.
to access a volume that cannot be found.
System action: The server does not process the ANR2411E Command: Unable to access associated
command. volume volume name - access mode is set
to "unavailable".
User response: Check the spelling of the volume name
to ensure it is correct. If the volume does not exist, Explanation: The command shown would require
preallocate it with the appropriate mechanism for the access to the volume whose name is displayed (because
operating system on which the server is running. data from the volume specified in the command spans
into this volume); the volume shown cannot be
accessed because its status is unavailable.
ANR2405E Command: Volume volume name is
currently in use by clients and/or data System action: The server does not process the
management operations. command.
Explanation: The command indicated specifies the User response: If necessary, reset the status of the
name of a data storage volume that is currently in use. volume and reissue the command.

command. ANR2412E Command: Audit operation already in
progress for volume volume name.
User response: Verify that the volume is unavailable
by issuing the QUERY VOLHISTORY command. If the Explanation: The command specified a volume that is
volume is listed in the command output, then it is currently in use by an audit volume operation.
being used and unavailable. Wait until the conflicting
System action: If the command is a MOVE
volume activity has completed, and then retry this
NODEDATA command the server will skip the volume
operation. If the volume is currently mounted, but idle,
and continues moving node data on other volumes.
dismount it using the DISMOUNT VOLUME
Other commands are not processed.
command, and then retry the operation.

User response: Reissue the command after the audit

ANR2422E Command: Volume volume name is not a
volume operation ends.
defined disk volume.
Explanation: The command shown specifies a volume
ANR2414E Command: Deletion operation already in
name that does not match any known disk volume.
progress for volume volume name.
Explanation: The command specified a volume that is
command.
currently in use by a delete volume operation.
volume name.
and continues moving node data on other volumes.
Other commands are not processed. ANR2423E Command: Volume volume name is still
online.
User response: Reissue the command after the delete
volume operation ends. Explanation: An UPDATE VOLUME command
specifies access=unavailable for a disk volume that is
still online.
ANR2416E Command: Move Data operation already
in progress for volume volume name. System action: The server does not process the
command.
currently in use by a move data operation. User response: Issue the VARY OFFLINE command,
and reissue the UPDATE VOLUME command.
and continues moving node data on other volumes. ANR2424E Command: Unable to access volume
Other commands are not processed. volume name - access mode is set to
"destroyed".
User response: Reissue the command after the move
data process ends. Explanation: The command shown specifies the
cannot be accessed because its status is destroyed.
ANR2418E Command: Migration operation already
in progress for volume volume name. System action: The server does not process the
command.
currently in use by a migration operation. User response: If necessary, reset the status of the
volume and reissue the command.
and continues moving node data on other volumes. ANR2425E Command: Unable to access volume
Other commands are not processed. volume name - access mode is set to
"offsite".
User response: Reissue the command after the
migration ends. Explanation: The command shown specifies the
cannot be accessed because its status is offsite.
ANR2420E Command: Space reclamation operation
already in progress for volume volume System action: The server does not process the
name. command.
Explanation: The command specified a volume is User response: If necessary, reset the status of the
currently in use by a reclamation operation. volume and reissue the command.
NODEDATA command the server will skip the volume ANR2426I Backupset backup set name defined for
and continues moving node data on other volumes. node node name (data type data type).
Other commands are not processed.
Explanation: The backup set has been defined for the
User response: Reissue the command after the indicated node.
reclamation ends.
System action: The server has defined the backupset.

ANR2427E Backupset backup set name for node node ANR2444E Command: A recovery log define, delete,
name (data type data type) was not extend, or reduce operation is already in
deleted. Device class device class name progress.
was not found.
Explanation: The specified command has been entered
Explanation: The specified backup set was not deleted while a command that is modifying the recovery log is
because the device class used to generate it was not already active.
found.
System action: The backup set is not deleted. command.
User response: If the device class was inadvertently User response: Wait for other activity to end, and
deleted, redefine it, then delete the backup set again. reissue the command.
ANR2428E Backupset backup set name for node node ANR2451E Command: Unable to vary recovery log
name (data type data type) has not been volume volume name offline - only copy.
deleted due to error error code.
Explanation: A VARY OFFLINE command has been
Explanation: The backup set has not been deleted. entered, but the recovery log volume has no mirrors
and contains the only copy of the data on that volume.
System action: The server has not deleted the
backupset. System action: The server does not process the
command.
User response: Check related error messages.
ANR2433E Command: A database define, delete,
extend, reduce, or backup operation is ANR2455E Command: Unable to access associated
already in progress. volume volume name - access mode is set
to "destroyed".
Explanation: The specified command has been entered
while a command that is modifying or backing up the Explanation: The specified command would require
database is already active. access to the volume whose name is displayed (because
data from the volume specified in the command spans
into this volume); the volume shown cannot be
command.
accessed because its status is destroyed.
User response: Wait for other activity to end, and
reissue the command.
command.
ANR2439E Command: Unable to vary database
volume and reissue the command.
volume volume name offline - mirrored
copies not synchronized.
ANR2456E Command: Unable to access associated
Explanation: A VARY OFFLINE command has been
volume volume name - access mode is set
entered, but mirrors of the volume to be varied are not
to "offsite".
up to date.
Explanation: The command shown would require
access to the volume whose name is displayed (because
command.
data from the volume specified in the command spans
User response: Try the command at a later time (after into this volume); the volume shown cannot be
database volumes have been synchronized). accessed because its status is offsite.
ANR2440E Command: Unable to vary database command.
volume volume name offline - only copy.
Explanation: A VARY OFFLINE command has been volume and reissue the command.
entered, but the database volume has no mirrors and
therefore contains the only copy of the data on that
ANR2457E Command: Backup of primary storage
volume.
pool primary pool name to copy storage
System action: The server does not process the pool copy pool name already in progress.
command.
Explanation: The command shown specifies a backup
User response: None. operation that is already in progress.

System action: The server does not process the cannot write to the file name specified.
command.
User response: Reissue the command after the current command.
backup operation ends.
ANR2458E Command: Restore of primary storage message and correct any problems, if possible. Make
pool primary pool name (or volumes in sure that the server has proper authority to write to the
that storage pool) already in progress. file indicated and that sufficient space is available in
Explanation: The command shown cannot be
processed because a restore operation involving the
authority to write to the data set.
indicated storage pool is already in progress. Either a
RESTORE STGPOOL command is in progress for the
indicated storage pool or a RESTORE VOLUME ANR2462I Command: Server sequential volume
command is in progress for volumes that belong to the history information was written to file
indicated storage pool. name.
System action: The server does not process the Explanation: This message is displayed in response to
command. the BACKUP VOLHISTORY command and indicates
that sequential volume history information was
User response: Reissue the command after the current
successfully written to the file name indicated.
restore operation ends.
System action: The server records sequential volume
history information to the file name specified.
ANR2459E Command: Volume volume name cannot be
updated - a restore operation involving User response: None.
that volume is in progress.
Explanation: The indicated volume has an access ANR2463I Command: Server sequential volume
mode of destroyed. Either a RESTORE STGPOOL history information was written to all
command or a RESTORE VOLUME command is in configured history files.
progress to restore the contents of the indicated
volume.
the BACKUP VOLHISTORY command and indicates
System action: The server does not process the that sequential volume history information was
command. successfully written to all files that were specified in
the server options file.
User response: If necessary, cancel the restore
processing and update the volume. System action: The server records sequential volume
history information to the configured files.
ANR2460E Command: Server could not write User response: None.
sequential volume history information
to File name.
Explanation: The BACKUP VOLHISTORY command encountered in writing sequential
does not complete successfully because the server volume history information to one or
cannot write to the file name specified. more of the defined volume history
files.
command. Explanation: The BACKUP VOLHISTORY command
does not complete successfully because the server
User response: Make sure that the server has proper
cannot write to one or more of the defined volume
authority to write to the file indicated and that
history files.
sufficient space is available in the file system for the
file. On MVS, make sure that the data set has been System action: The server does not process the
allocated and that the server has authority to write to command.
the data set.
ANR2461E Command: An internal error was message and correct any problems, if possible. Contact
encountered in writing sequential your service representative if you are unable to resolve
volume history information to file name. the problem.
Explanation: The BACKUP VOLHISTORY command
does not complete successfully because the server

ANR2467I Command: number of entries deleted ANR2474E Command: Input volume names must be
sequential volume history entries were specified with the VOLumenames=
successfully deleted. parameter.
Explanation: The DELETE VOLHISTORY command Explanation: The command failed because input
successfully deleted the number of entries specified. volume names were not specified with the
VOLumenames parameter.
User response: On some platforms, or with certain
device classes, the server cannot prompt to mount
input removable media volumes, so the names of the
encountered while deleting server
required volumes must be specified in the command.
sequential volume history information.
Reissue the command specifying the name(s) of
Explanation: The DELETE VOLHISTORY command volumes that should be mounted for input.
fails because an internal server error has been
encountered.
ANR2475E Command: File file name could not be
System action: The DELETE VOLHISTORY command opened.
fails, and server operation continues.
Explanation: The DSMSERV command could not be
User response: Examine the messages in the activity completed successfully because the file specified (to
log or server console that were displayed prior to the contain the list of volumes to be used) cannot be
error to see if the error can be resolved. Contact your opened.
service representative if this error cannot be resolved.
System action: The DSMSERV command fails.
User response: Examine the file name that was
ANR2469E Command: Invalid volume history type:
specified in the DSMSERV command. Correct the
history type.
specification, if necessary, so that it specifies the name
Explanation: The command failed because an invalid of a file that exists and is accessible by the server
sequential volume history type was specified for the program. Reissue the DSMSERV command if this can
TYPE= parameter. be corrected. Contact your service representative if this
error cannot be resolved.
System action: The command fails, and server
ANR2476I License storage auditing is disabled, no
User response: Reissue the command and specify a output available.
valid type value.
Explanation: The license storage occupancy function is
currently disabled.
ANR2472E Command: Invalid volume specified:
volume name. System action: None.
Explanation: The command failed because the User response: To obtain storage occupancy results,
sequential history volume specified is not a DB DUMP, remove the NOAUDITSTORAGE or AUDITSTORAGE
DB BACKUP, or EXPORT volume. NO option from the server options file, then restart the
server and issue the AUDIT LICENSES command.
System action: The command fails, and server
ANR2477I License storage auditing is disabled,
User response: Reissue the command and specify a storage values may be outdated and
valid volume name. should be ignored.
Explanation: The license storage occupancy function is
ANR2473I Command for volume volume name currently disabled.
completed.
Explanation: The command completed and the
volume history file has been updated. User response: To obtain storage occupancy results,
remove the NOAUDITSTORAGE or AUDITSTORAGE
System action: The server records sequential volume NO option from the server options file, then restart the
history information. server and issue the AUDIT LICENSES command.

ANR2478E Command: Command cannot be executed ANR2483E Command: No SQL cursor is currently
in this session. open.
Explanation: The command indicated is not supported Explanation: The command indicated failed because
by the session in which it was invoked. For example, a no SQL cursor is currently open.
DEFINE CURSOR command can not be invoked from
the server's primary console.
command.
User response: Use the OPEN CURSOR command to
command.
first open a cursor.
User response: The command must be issued from a
standard administrator session.
ANR2484E Command: Invalid SQL date-time display
format - SQL date-time display format
ANR2479E Command: Invalid SQL cursor name - name.
SQL cursor name.
Explanation: The command indicated contains an invalid SQL date-time display format name.
invalid SQL cursor name.
command.
User response: Reissue the command with a valid SQL date-time format name.
SQL cursor name.
ANR2485E Command: Invalid SQL display format -
ANR2480E Command: SQL cursor name SQL cursor SQL display format name.
name is already defined.
Explanation: The command indicated specifies an SQL invalid SQL display format name.
cursor name that has already been defined.
command.
User response: Reissue the command and specify a SQL display format name.
different cursor name.
ANR2486E Command: Invalid SQL character
ANR2481E Command: SQL cursor name SQL cursor arithmetic mode - SQL arithmetic mode.
name is not defined.
Explanation: The command indicated specifies an SQL invalid SQL arithmetic mode name.
cursor name that has not been defined.
command.
User response: Use the DEFINE CURSOR command SQL arithmetic mode name.
to first define the cursor.
ANR2487E Command: An SQL expression is
ANR2482E Command: SQL cursor SQL cursor name is required.
already open.
Explanation: The command indicated requires that an
Explanation: The command indicated failed because SQL expression be provided through the SQL keyword
an SQL cursor is already open. parameter.
command. command.
User response: Use the CLOSE CURSOR command to User response: Reissue the command specifying an
first close the current cursor. SQL expression.

ANR2488W List file list file name could not be ANR2500I Schedule schedule name defined in policy
opened. domain domain name.
Explanation: While attempting to read or write a Explanation: This message is displayed in response to
sequential file list, the server was unable to open the the DEFINE SCHEDULE command. The schedule
file name specified. named schedule name has been defined in the policy
domain named domain name in the server database.
System action: The server does not use the list file.
been displayed prior to this message and correct any User response: None.
problems, if possible. For OUTFILE files, make sure
that the server has proper authority to write to the file
ANR2501I Schedule schedule name deleted from
indicated and that there is sufficient space in the file
system for the file. On OS/390 and z/OS, make sure
that the server has authority to write to the data set. Explanation: This message is displayed in response to
the DELETE SCHEDULE command. The schedule
named schedule name has been deleted from the policy
ANR2489W An error was encountered writing to
domain named domain name in the server database.
volume list file volume list file name.
Explanation: While attempting to write to the
sequential file for a volume list an error occurs on the User response: None.
file name specified. The volume list is not be complete
and should not be used for input.
ANR2502I Schedule schedule name updated in
System action: The server stops writing to the file. policy domain domain name.
User response: Examine error messages that may have Explanation: This message is displayed in response to
been displayed prior to this message and correct any the UPDATE SCHEDULE command. The schedule
problems, if possible. Make sure that the server has named schedule name has been updated in the policy
proper authority to write to the file indicated and that domain named domain name in the server database.
On MVS, make sure that the server has authority to System action: Server operation continues.
write to the data set. Obtain the volume list from User response: None.
console messages, the QUERY VOLHISTORY command
or the volume history file, if it is used.
ANR2503I Schedule schedule name in domain domain
name copied to schedule new schedule
ANR2490E Command: NODENAMES and name in domain new domain name.
SERVERNAMES parameters cannot
both be specified in the same command. Explanation: This message is displayed in response to
the COPY SCHEDULE command. The schedule named
Explanation: The command indicated failed because schedule name in policy domain domain name has been
both the nodenames parameter and the servernames copied to the schedule named new schedule name in the
parameter were specified. policy domain named new domain name. Node
System action: None. associations have not been copied.
User response: Determine whether you want the System action: Server operation continues.
action taken for one or more nodes or for one or more User response: None.
servers and reenter the command with only the correct
parameter specified.
ANR2504I Schedule schedule name deleted.
ANR2491I Volume creation process starting for Explanation: This message is displayed in response to
volume name, Process ID process ID. the DELETE SCHEDULE command. The schedule
named schedule name has been deleted from the server
Explanation: As a result of a DEFINE VOLUME database.
command with the SIZE=xxx parameter, a new volume
is being created. The process whose ID is displayed has System action: Server operation continues.
begun to create the volume shown. User response: None.
System action: The server creates the volume and
adds it to the server.

ANR2505I number of schedules schedules were ANR2509E Command: Invalid Virtual file space
defined for command. name - vfs name.
Explanation: number of schedules were generated and Explanation: The specified server command has been
nodes successfully associated for the command issued. entered with a virtual file space name that is longer
than allowed.
User response: If the number is less than expected,
command.
check the nodeList and domainList combination specified
to the DEFINE CLIENTACTION command. Schedules User response: Reissue the command with a valid
are generated when at least one node in the nodeList virtual file space name.
exists in a domain in the domainList.
ANR2510I Node node name associated with
ANR2506I Node node name associated with schedule schedule name in policy domain
schedule schedule name in policy domain domain name.
domain name processed. rc=return code.
Explanation: This message is displayed in response to the DEFINE ASSOCIATION command. Node node name
the DEFINE CLIENTACTION WAIT=YES command. is associated with the schedule named schedule name in
Node node name is associated with the schedule named policy domain domain name. Schedule schedule name is
schedule name in policy domain domain name has been now applied to node node name.
processed. name The result is indicated in the return
code return code.
User response: If the return code is non-zero, issue the
ANR2511I Node node name disassociated from
QUERY ACTLOG command to to view the activity log
schedule schedule name in policy domain
and search for the error messages. After the error has
domain name.
been resolved, restart the scheduled operations.
the DELETE ASSOCIATION command. Node node name
ANR2507I Schedule schedule name for domain
is no longer associated with the schedule named
domain name started at start timestamp for
schedule name in policy domain domain name.
node node name completed successfully
at timestamp. System action: Server operation continues.
Explanation: The scheduled operation for the domain User response: None.
name and schedule name specified was processed. It was
processed for node node name and completed
successfully at the indicated time. ANR2512I Event records deleted: record count.
System action: Server operation continues. Explanation: This message is displayed in response to
the DELETE EVENT command. A total of record count
User response: This message is intended to report the event records have been deleted from the database.
completion state of a scheduled client action. This
message indicates that the scheduled action completed System action: Server operation continues.
successfully. User response: None.
ANR2508E Trace Tsmtrcfm failed: A tracefile name ANR2513I Schedule schedule name copied to
is required. schedule new schedule name.
Explanation: Trace Tsmtrcfm doesn't output to console Explanation: This message is displayed in response to
System action: Trace won't start without a tracefile the COPY SCHEDULE command. The schedule named
name for Trace Tsmtrcfm schedule name has been copied to the schedule named
new schedule name.
User response: Issue the command with a tracefile
name. System action: Server operation continues.

User response: Issue the command using a file space

ANR2514E Command: Virtual file space name vfs
and path that does not already have a mapping
name conflicts with file space on the
defined.
network attached storage (NAS) device.
ANR2519E Command: The file space, fs name, does
entered with a virtual file space that has the same
not exist on the NAS device associated
name as a File space on the NAS device.
with the node node name.
Explanation: During a Backup of a virtual file space
command.
mapping for a NAS device, the server detected that the
User response: Ensure that no virtual file space file space upon which the virtual file space resides does
mappings for this NAS device have the same name as not exist on the associated NAS device.
an actual file space that exists on the NAS device.
User response: Use QUERY VIRTUALFSMAPPING to
ANR2515I Command: A virtual file space mapping
verify that the virtual file space mapping is defined
named vfs name for node node name has
correctly.
been defined.
ANR2520I Scheduled sessions set to percent
VIRTUALFSMAPPING command, a virtual file space
percent.
mapping for the specified node has been defined in the
server database. Explanation: This message is displayed in response to
the SET MAXSCHEDSESSIONS command. It indicates
the percentage of total server sessions that can be used
User response: None. for the processing of scheduled work.
ANR2516E Command: The specified file space, fs
name, does not exist on the NAS device
associated with the node node name.
ANR2521I Event record retention period set to days
days.
entered with a file space that does not exist on the
associate NAS device. Explanation: This message is displayed in response to
the SET EVENTRETENTION command. It indicates the
number of days for which event records are retained in
User response: Reissue the command with a valid file the database.
space name from the NAS device.
ANR2517E Command: The virtual file space vfs name
is already defined for node node name.
ANR2522I Randomization set to percent percent.
with a virtual file space name that has already been Explanation: This message is displayed in response to
defined for the indicated node. the SET RANDOMIZE command. It indicates the
percentage of the startup window over which the start
times for individual clients are distributed.
User response: Issue the command using a virtual file
space name that has not already been defined for this User response: None.
node.
ANR2523I Schedule query period set to hours
ANR2518E Command: A virtual file space mapping hour(s).
already exists to the specified node, file
space and path. Explanation: This message is displayed in response to
the SET QUERYSCHEDPERIOD command. It indicates
Explanation: The specified command has been issued the number of hours between attempts by the client to
with a node, file space and path for which there is contact the server for scheduled commands.
already a virtual file space mapping defined.
command is not processed. User response: None.


ANR2524I Schedule query period reset to value
determined by each client.
ANR2530I Scheduling mode set to PROMPTED.
the SET QUERYSCHEDPERIOD command. Explanation: This message is displayed in response to
the SET SCHEDMODES command. With
server-prompted scheduling, the server contacts the
User response: None. client when scheduled work needs to be performed and
a session is available.
ANR2525I Maximum number of command retries System action: Server operation continues.
set to retries.
the SET MAXCMDRETRIES command. It indicates the
ANR2531I Scheduling mode set to ANY.
maximum number of times the client scheduler retries
a command after a failed attempt to process a Explanation: This message is displayed in response to
scheduled command. the SET SCHEDMODES command. The server now
allows clients to run in either the client-polling or the
server-prompted scheduling mode.
ANR2526I Maximum number of command retries
reset to value determined by each client.
ANR2532I Schedule schedule name updated.
the SET MAXCMDRETRIES command. Explanation: This message is displayed in response to
the UPDATE SCHEDULE command. The schedule
named schedule name has been updated in the server
User response: None. database.
ANR2527I Retry period set to minutes minutes.
the SET RETRYPERIOD command. It indicates the
ANR2533I Client action schedule duration set to
number of minutes between attempts by the client
days days.
scheduler to retry, after a failed attempt, to contact the
server or to process a scheduled command. Explanation: This message is displayed in response to
the Set CLIENTACTDuration command. It indicates the
number of days for which schedules and associations
User response: None. generated by the DEFine CLIENTAction are retained in
the database.
ANR2528I Retry period reset to value determined System action: Server operation continues.
by each client.
the SET RETRYPERIOD command.
ANR2534I Client action schedule schedule name was
System action: Server operation continues. not executed by node name in domain
name.
Explanation: Immediate client action schedule name
was not executed by node node name, which is in
ANR2529I Scheduling mode set to POLLING.
domain domain name. The schedule is being deleted.
the SET SCHEDMODES command. With client-polling
scheduling, a client queries the server at prescribed User response: None.
time intervals to obtain scheduled work or to ensure
that the schedules the client is waiting to process have
not changed.

ANR2535E Command: The node node name cannot be ANR2540E Command: The "option" device class is not
removed or renamed because it has an valid with the storage pool's data
associated data mover. format.
Explanation: You attempted to remove or rename a Explanation: The command indicated specifies a
node that has an associated data mover. device class that is not valid with the specified (or
defaulted) data format for the storage pool.
System action: The server does not remove or rename
the node. System action: The server does not process the
command.
User response: To remove or rename the node, delete
the associated data mover and reissue the command. User response: Reissue the command with a data class
appropriate for the desired data format of the storage
pool.
valid with the storage pool's data
format. ANR2541E Command: The storage pool specified
with option "option" is not compatible
Explanation: The command indicated includes an
with the option's intended use.
option that is not valid with the specified (or defaulted)
data format for the storage pool. Explanation: The command specifies a storage pool
whose device class is a Centera device. Such storage
pools are not available for use with data movement
command.
operations such as reclaim or attributes such as copy,
User response: Reissue the command with options active-data, or reclaim storage pools.
appropriate for the desired data format of the storage
pool.
command.
User response: Issue the command again with a
storage pool appropriate for the desired function.
has a device type that is not allowed for
this operation.
ANR2542E Command: The storage pool is not
Explanation: The device class in the indicated
compatible with the operation's
command has a device type that is not allowed for this
intended use.
operation.
Explanation: The command specifies a storage pool
whose device class is a Centera device. Such storage
command.
pools are not available for use with data movement
User response: Choose a different device class and operations, such as reclaim, or attributes, such as copy
reissue the command. or reclaim storage pools.
ANR2538E Command: Backup set cannot be command.
generated for NAS node node name.
Explanation: Backup sets cannot be generated for storage pool appropriate for the desired function.
NAS nodes.
System action: The command fails. ANR2543E Command: The volume name is not
compatible with the operation's
User response: None. intended use.
Explanation: The command specifies a volume that
ANR2539E Command: Storage pool Storage Pool Name resides in a storage pool whose device class is a
does not have a valid data format. Centera device. Such volumes are not available for use
Explanation: The data format of the indicated storage with data movement operations, such as reclaim, or
pool is not valid for the requested operation. The attributes, such as copy or reclaim storage pools.
storage pool must have NATIVE or NONBLOCK data System action: The server does not process the
format. The server is unable to perform the requested command.
operation.
System action: The command fails. volume appropriate for the desired function.
User response: Choose a different storage pool with
the appropriate data format and reissue the command.

associated file space definition, if one exists.

ANR2544E Unable to open the centera device at hla
hla. System action: NAS Backup processing for the
command continues.
Explanation: The server cannot start communication
with the device at the specified HLA. User response: None; however, users should make
note of the original Virtual file space filespace name and
System action: The transaction needing this device
the new new filespace name so that they know where the
fails.
backup data for this Virtual file space is located. Note,
User response: Verify that the hla specified in the the RENAME FILESPACE command may be used to
device class is correct, verify that the centera device is rename the Virtual file space to a more appropriate
operational. name.
ANR2545E The version of the centera library, ANR2549E Command: Invalid virtual file space
version, is not compatible with the name. A virtual file space mapping
server. name must have a forward slash as the
first character.
Explanation: The centera library must be at least
version 2 to be able to be compatible with the server. Explanation: The specified server command has been
entered with a virtual file space name that is does not
System action: The transaction fails.
have a forward slash as the first character.
command.
ANR2546E The centera device is not capable of
performing the required operation,
virtual file space name.
version.
Explanation: The centera device must be capable of
ANR2550W Command: Modifying the virtual file
reading, writing and deleting objects. The device is not
space mapping VFS Name for Celerra
capable of performing at least one of these operations.
NAS device NAS device may prevent
System action: The transaction fails. data from being recovered.
If you modify this definition, save the
User response: Contact your service representative. existing file space and path settings so
that the definition may be reverted to its
ANR2547E A Centera device (devclass) reported error original state.
"message,error" during command Centera Explanation: An UPDATE VIRTUALFSMAPPING has
command. been entered for a Celerra NAS device. Modifying a
Explanation: The Centera device reported an error Celerra virtual file space defintion may prevent the
while performing the specified command. data from being recovered. If you are modifying this
definition in order to recover data, you should revert
System action: The operation fails. the changes back to theiroriginal values after the
User response: Verify that the IP addresses specified recovery is performed.
in the device class associated with the storage pool are System action: The system asks whether you wish to
correct. Contact your service representative if the continue with the command.
problem persists.
User response: To process the UPDATE
VIRTUALFSMAPPING command, enter 'Y' to continue
ANR2548I NAS command: Renaming file space or 'N' to stop the process.
filespace name for node node name to file
space new filespace name.
ANR2551E Command: A virtual file space mapping
Explanation: The NAS Backup process detected a for a Celerra NAS device cannot be
name conflict between the Virtual file space filespace modified.
name and a file space on the NAS device associated
with the node node name. The Virtual file space is Explanation: You cannot modify a virtual file space
renamed to the new filespace name. During a NAS defintion for a Celerra NAS device. If the directory has
backup process, if the object to be backed up is a been relocated on the NAS device then create a new
Virtual file space, IBM Spectrum Protect will verify that virtual file space mapping to point to the new location.
this name does not also exist as a file space on the NAS System action: The server does not process the
device. If a name conflict exists, IBM Spectrum Protect command.
will rename the existing Virtual file space and the

User response: Define a new virtual file space server to at least IBM Spectrum Protect Version 5
mapping for this NAS filespace and path. Release 3.
ANR2552I Server now enabled for session type ANR2557W The managed server server name is not
access. capable of using the enhanced style
administrative schedule schedule name.
Explanation: The server has been made available for
The administrative schedule will not be
use by the specified session types with the ENABLE
propagated to this server.
command.
Explanation: The managed server server name is
subscribed to an administrative schedule that uses
User response: None. enhanced style syntax. The managed server is not
capable of using an enhanced style schedule. Only IBM
Spectrum Protect servers that are at least Version 5
ANR2553I Server now disabled for session type Release 3 are capable of using enhanced style
access. schedules.
Explanation: The server has been made unavailable System action: Server operation continues. The
for use by the specified session types with the administrative schedule will not be propagated to the
DISABLE command. managed server.
System action: None. User response: Consider upgrading the managed
User response: None. server to at least IBM Spectrum Protect Version 5
Release 3.
ANR2554I Format lfvolume process process id ended

for storage pool pool name, number of ANR2558W command: One or more managed servers
volumes requested volumes requested, that subscribe to domain domain name
number of volumes formatted volumes which contains client schedule schedule
formatted. name are not capable of using an
enhanced style schedule.
Explanation: The FORMAT LFVOLUME process for
the storage pool shown has ended. The number of Explanation: The client schedule schedule name uses
volumes requested to be formatted, and the number of enhanced style schedule syntax. The schedule is in a
volumes actually formatted are displayed. domain which is a managed object and one or more of
the managed servers that subscribe to it are not capable
System action: None. of using an enhanced style schedule. Only IBM
User response: If the number of volumes formatted is Spectrum Protect servers that are at least Version 5
less than the number of volumes requested to be Release 3 are capable of using enhanced style
formatted, check the activity log for messages schedules. During configuration refresh processing, the
indicating the reason for the difference. Possible domain will not be propagated to managed servers that
reasons include the process was canceled, no more are not capable of using it.
scratch volumes are allowed in the storage pool, or an System action: Server operation continues.
error occurred processing a scratch volume.
User response: Consider upgrading managed servers
to at least IBM Spectrum Protect Version 5 Release 3.
ANR2556W The managed server server name is not
capable of using enhanced style client
schedule schedule name in domain domain ANR2559W command: One or more managed servers
name. The domain will not be that subscribe to administrative
propagated to this server. schedule schedule name are not capable of
using an enhanced style schedule.
Explanation: The managed server server name is
subscribed to domain domain name that contains client Explanation: The administrative schedule schedule
schedule schedule name that uses enhanced style syntax. name uses enhanced style schedule syntax. The
The managed server is not capable of using an schedule is a managed object and one or more of the
enhanced style schedule. Only IBM Spectrum Protect managed servers that subscribe to it are not capable of
servers that are at least Version 5 Release 3 are capable using an enhanced style schedule. Only IBM Spectrum
of using enhanced style schedules. Protect servers that are at least Version 5 Release 3 are
capable of using enhanced style schedules. During
System action: Server operation continues. The configuration refresh processing, The schedule will not
domain will not be propagated to the managed server. be propagated to managed servers that are not capable
User response: Consider upgrading the managed of using it.

User response: Consider upgrading managed servers User response: None.
to at least IBM Spectrum Protect Version 5 Release 3.
ANR2566E An error occurred while deleting
ANR2560I Schedule manager started. immediate client action schedules.
Explanation: The schedule manager is started when Explanation: Processing did not complete for deleting
the server is initialized. The schedule manager schedules that were generated by the DEFINE
maintains entries of scheduled operations. CLIENTACTION command.
User response: None. User response: Check the activity log for other
messages that might relate to this failure. Correct any
memory or space problems.
ANR2561I Schedule prompter contacting node name
(session session number) to start a
scheduled operation. ANR2567W Schedule prompter skipped contact
attempt with node name to start a
Explanation: The schedule prompter contacts the
scheduled operation.
client scheduler for node node name because a
scheduled operation should be started for that node. Explanation: The schedule prompter skipped the
contact attempt with the client scheduler for node node
name because the start-up window has passed for that
User response: None. node, or the node was locked.
ANR2562I Automatic event record deletion started.
User response: Check the length of the schedule
Explanation: A process has been started to delete start-up window to see if it needs to be increased.
event records for which the retention period has Check the activity log for ANR2716E messages. These
elapsed. messages are associated with failures to contact a client
scheduler. If there are an excessive number of these
System action: Server operation continues. messages the schedule window could have elapsed
User response: None. waiting for TCP/IP timeouts from these failed
attempts. Also, check to see if the client node is locked.
The contact attempt would be skipped for a locked
ANR2563I Removing event records dated prior to node.
date time.
Explanation: Events that were scheduled to start prior ANR2568E Request for node node to start schedule
to date time are automatically deleted unless their schedule at startTime is denied. Current
startup window has not yet elapsed. time is now.
System action: Server operation continues. Explanation: The client scheduler attempted to start
User response: None. the specified instance of a schedule for a node. The
request was denied because that instance is still in the
future.
ANR2564I Automatic event record deletion ended -
record count records deleted. System action: Server operation continues. The node
does not start the schedule.
Explanation: The event deletion process has ended. A
total of record count event records have been deleted User response: Check the client schedule and error
from the database. logs for problems with the network or the preschedule
command. Also, you may need to upgrade the client.
User response: None. ANR2569E Request by node node to report results
(result, code code) for schedule schedule at
ANR2565I schedules schedules for immediate client startTime is denied. Current time is now.
actions have been deleted. Explanation: The client scheduler attempted to report
Explanation: A total of schedules that were generated the results of executing the specified schedule.
by the DEFINE CLIENTACTION command have However, the schedule occurs in the future. The results
expired and been deleted from the database. will not be saved.

System action: Server operation continues. The results been allocated for scheduled operations are already in
will not be saved. use.
User response: Check the client schedule and error System action: The server continues to attempt
logs for problems with the network or the preschedule contact with the client scheduler until the startup
command. Also, you may need to upgrade the client. window for the scheduled event has elapsed.
User response: To change the total number of
ANR2570W A scheduled session has been denied. sessions, alter the MAXSESSIONS parameter in the
The schedule manager is not active. server options file and then restart the server. The
percentage of sessions that are available for scheduled
Explanation: The client scheduler attempts to connect
operations can be increased by using the SET
with the server, but it is denied a session because the
MAXSCHEDSESSIONS command.
schedule manager is not active.
System action: Server operation continues, but central
ANR2573W Sufficient memory is not available for
scheduling is not operational.
the central scheduler - will retry in
User response: Issue the QUERY OPTION command number of seconds seconds.
to determine if the option DISABLESCHEDS YES has
Explanation: The server suspends central scheduler
been specified in the server options file. If so,
processing because sufficient server memory is not
scheduling can be enabled by updating the server
available.
options file with DISABLESCHEDS NO and restarting
the server. If DISABLESCHEDS YES was not specfied System action: Server operation continues; the
in the server options file, determine the source of the scheduler operation will be retried after the specified
error by examining the QUERY ACTLOG command to delay.
view the activity log and search for messages. After the
error has been resolved, restart the server to restore
central scheduler operations. If the error cannot be
application.
isolated and resolved, contact your service
representative.
ANR2574W The central scheduler has insufficient
recovery log space. The current
ANR2571W Scheduled session from node node name
transaction will be tried again in number
(platform name) has been denied,
of seconds seconds.
scheduled sessions are not currently
available. Explanation: If a log runs out of space, the current
Explanation: The client scheduler for node node name
message and halts. You cannot restart the server until
attempts to connect with the server, but is denied a
the recovery log size is increased.
session. All sessions that have been allocated for
scheduled operations are already in use. System action: The server halts.
System action: Server operation continues. User response: Monitor archive logs and active logs. If
User response: Issue the QUERY OPTION command
to determine if the option DISABLESCHEDS YES has
nearly full, run a full database backup to remove
been specified in the server options file. If so,
archive logs and consider adding more disk space to
scheduling can be enabled by updating the server
options file with DISABLESCHEDS NO and restarting
full and the active log space is full or nearly full,
the server. If DISABLESCHEDS YES was not specfied
update the value of the ACTIVELOGSIZE option in the
in the server options file, change the total number of
sessions by altering the MAXSESSIONS parameter in
option to the new maximum size of the active log.
the server options file and then restarting the server.
The percentage of sessions that are available for
scheduled operations can be increased by using the SET ANR2575W The central scheduler has insufficient
MAXSCHEDSESSIONS command. database space. The current transaction
will be tried again in number of seconds
seconds.
ANR2572W Schedule prompter session to node node
name has been denied, scheduled Explanation: The server suspends central scheduler
sessions are not currently available. processing because of insufficient database space.
Explanation: The server attempts to prompt the client System action: Server operation continues; the
scheduler for node node name, but all sessions that have scheduler operation will be tried again after the
specified delay.

User response: To increase the amount of database 8 The operation was completed with at least one
space that is available to the server, issue the EXTEND warning message.
12 The operation was completed with at least one
the database.
error message. The count of error messages
does not include notifications about skipped
ANR2576W An attempt was made to update an files.
event record for a scheduled operation
-99 The operation failed because the session
which has already been executed for
between the client and the server ended for an
node node name.
unknown reason. It is unknown whether the
Explanation: The server cannot update the event client can reconnect to the server to complete
record for the specified client node. The existing record the scheduled event.
indicates that the scheduled operation has already
completed. This can happen when two or more client
schedules are running for this node, or because the User response: Examine the node's schedule log to
client has retried the operation after an error has determine the cause of the failure. To determine the
occurred. final status of the scheduled event, issue the QUERY
EVENT command.
existing event record is not modified. No further
processing is performed for this scheduled operation. ANR2581W Schedule schedule name of an
administrative command has missed its
User response: Contact the user for this client node,
scheduled start up window.
and make sure that only one client scheduler is
running. Explanation: This message is displayed when the
scheduled startup window for this schedule has passed
and the schedule has not begun.
ANR2577I Schedule schedule name defined.
scheduled operation is not processed by the server.
the DEFINE SCHEDULE command. The schedule
named schedule name in the server database. User response: Ensure that the duration and period
specified in the schedule are long enough to allow the
schedule to start.
ANR2582E Command: Specified device class cannot
ANR2578W Schedule schedule name in domain domain be used with storage pools with
name for node node name has missed its different reclamation types.
scheduled start up window.
Explanation: Storage pools can be defined with
Explanation: This message is displayed when the RECLAMATIONTYPE=THRESHOLD or
scheduled startup window for this schedule has passed RECLAMATIONTYPE=SNAPLOCK. A device class can
and the schedule has not begun. only be used with either
RECLAMATIONTYPE=THRESHOLD or
RECLAMATIONTYPE=SNAPLOCK storage pools. An
scheduled operation is not processed by the server.
attempt was made to define a storage pool with one
User response: Ensure that a scheduled session for type of reclamation type with a device class that is
node node name has been initiated from the client to the already associated with another storage pool of the
server. other reclamation type.
ANR2579E Schedule schedule name in domain domain
name for node node name failed (return
another device class that is referenced by storage pools
code return code).
with the same reclamation type as your new storage
Explanation: The client reported a failure to complete pool. You may need to define another device class.
a scheduled action, or return code -99 was reported by
the server. One of the following return codes is
displayed:
is not a LAN-free storage pool.
0 All operations were completed successfully.
4 The operation was completed, but some files name of a storage pool which is not a LAN-free pool.
were not processed.

The command syntax requires that a LAN-free storage Enter 'N' to cancel the change. If you change the server
poolname be specified. name you must reconfigure all the affected components
such as backup-archive client operations, library
sharing with the library manager or library clients or
command.
other server to server operations. For example, if you
User response: Reissue the command with a valid rename an Operations Center spoke server, you must
LAN-free storage pool name. remove it from the Operations Center and re-add it. For
a hub server, you must restart the initial configuration
wizard to delete the existing server connection and
ANR2584E Command: An email address exceeds create a new one.
Explanation: A REGISTER NODE or REGISTER ANR2587W IBM Spectrum Protect encountered a
ADMIN command has been entered that specifies a list zero verb on backupset volume Volume
of email addresses, and one of those addresses is too and skipped to the next volume.
long. The maximum valid length for a single email
address is shown in the command. Explanation: IBM Spectrum Protect detected the
problem described in APAR PK12572 . The server
System action: The server does not process the options file contains SKIPONZEROVERBBACKUPSET
command. ON. IBM Spectrum Protect verified there was no
User response: Reissue the command with a shorter further data on the volume, and skipped to the next
email address. volume.
ANR2585E Command: An email address contains User response: If the backupset volume was written
invalid syntax. before IBM Spectrum Protect 5.2.7, or 5.3.3 was put on
Explanation: A server command has been entered that the system and meets the PK12572 criteria, no action is
specifies an invalid email address. Email addresses required. If not, the volume has encountered a read
must be in the format "name@domain", where the error, and should read again on a server without the
name must be between 1 and 64 characters long, and SKIPONZEROVERBBACKUPSET ON option to get the
the domain must be between 1 and 255 characters long. correct error messages for problem determination.

command. ANR2588E Command: Storage pool "StgPool" cannot
have CACHE set to YES with a non zero
User response: Reissue the command with a correct SHRED attribute.
email address.
Explanation: Storage pools can be defined or updated
with a non zero SHRED attribute only if the storage
ANR2586W Setting the server name to serverName pool CACHE attribute is NO. Existing storage pools
can adversely affect or stop operations with CACHE attribute of YES cannot be updated with
that depend on communications such as a non zero SHRED attribute. Likewise, existing storage
for the following purposes: Operations pools with a non zero SHRED attribute cannot be
Center administration, backup-archive updated with CACHE = YES. Existing storage pools
client operations, library sharing with with CACHE set to YES cannot be updated with a non
the library manager or library clients, or zero SHRED attribute. New storage pools cannot be
other server to server functions such as define nor can existing storage pools be modified with
virtual volumes, event logging, or CACHE set to YES and a non zero SHRED value.
enterprise configuration.
Explanation: The server name was changed using the
SET SERVERNAME command. If the server is managed by User response: Reissue the command and specify
the Operations Center, server data might not be shown, SHRED value of zero or CACHE = NO.
or might be incorrect. In a virtual volume
configuration, renaming a source server can prevent it ANR2589E Backupset backup set name for node node
from accessing and managing data that is stored on the name (data type data type) is in use and
target server. Any Windows clients that are connected cannot be deleted.
to a server when its name is changed must reconnect to
continue accessing the server. Explanation: The server attempted to delete the
backup set, but the operation could not be completed,
System action: The server prompts the user to because the backup set was in use by another process.
continue.
User response: Enter 'Y' to change the server name. command.

User response: Reissue the command at a later time. the LDAPUSER just set. This is required for
communication with the LDAP server specified in the
LDAPURL option.
ANR2590E Command failed - SET DBRECOVERY
command has not been issued.
ANR2595I Directory directory name is already in the
Explanation: Backup DB command failed because a
list to add to database space.
SET DBRECOVERY command has not been issued to
define the device class used for automatic DB backup. Explanation: While processing the command
argument list, a duplicate path name has been
encountered.
command.
User response: Issue the SET DBRECOVERY
command to define the device class for automatic DB User response: Issue the command again, specifying a
backup operation. directory that is not in the argument list.
ANR2591I Directory directory name is already ANR2596E There is insufficient authority to create
defined in the database space. the database files.
Explanation: This directory is already in the database Explanation: The database manager, running under
space . the user ID for the IBM Spectrum Protect instance, does
not have the authority to create files in one or more of
the database directories.
System action: The server process ends.
directory that is not defined in the server database
space. User response: Ensure that the user ID for the IBM
Spectrum Protect instance has write permission to all
database directories. No matter which user ID is
ANR2592I Directory(ies) directory list has been
running the dsmserv process, the database files are
defined in the database space.
written by the database manager. The permissions on
Explanation: Command 'EXTEND DBSPACE' these database directories must allow write access from
successfully added new directory(ies) dir list into the the database manager user ID. Change the ownership
server database space. of the database directories to the user ID for the IBM
Spectrum Protect instance.
System action:
User response: ANR2597W Node node name in domain domain name
began schedule schedule name at actual
ANR2593E Command: Storage pool storage pool name start and is schedule state. The period
exists but does not match the expired at expiration time.
storage-pool type that the server is Explanation: This message is displayed when a node
attempting to process with the started a schedule, the period for the schedule expired,
command. and the node has not reported results for the schedule.
Explanation: The storage pool specified does not Possible causes are:
match the type being processed with the command. v processing for the action is taking longer than the
schedule period
command. v a problem occurred while the node was performing
the scheduled action
User response: Retry the command with a valid
v the node completed the scheduled action but did not
storage pool type specified.
report the results to the server
System action: Server operation continues. The results
ANR2594I LDAP user name set to LDAP user name.
of the scheduled operation are unknown.
Explanation: The LDAP user distinguished name that
User response: Administrators should consult the
the server uses to authenticate with the LDAP server
server activity log and the client scheduler log, then
has been set to the value indicated with the SET
take corrective action if needed.
LDAPUSER command.
User response: The SET LDAPPASSWORD command
is required to provide the password that correlates to

ANR2598W Administrative command schedule ANR2602E Command: Invalid action - action.

schedule name started processing at actual
start and is schedule state. The period
with an invalid action.
expired at expiration time.
Explanation: This message is displayed when an
administrative command schedule has started, the
period for the schedule expired, and the results for the User response: Issue the command and specify a valid
schedule have not been reported. Possible causes are: action.
v processing for the action is taking longer than the
scheduled period ANR2603E Command: Options string exceeds
v a problem occurred while performing the scheduled maximum length characters.
action
v a problem occurred reporting the schedule results with an options string that exceeds the maximum
System action: Server operation continues. The results length.
of the scheduled operation are unknown. System action: Server operation continues, but the
User response: Administrators should consult the command is not processed.
server activity log, then take corrective action if needed. User response: Issue the command with a valid
options string.
ANR2599W The central scheduler is unable to
obtain a required lock and will retry in ANR2604E Command: Objects string exceeds
number of seconds seconds. maximum length characters.
Explanation: The server temporarily suspends central Explanation: The specified command has been issued
scheduler processing because a required lock is not with an objects string that exceeds the maximum
available. length.
System action: Server operation continues; the System action: Server operation continues, but the
scheduler operation will be retried after the specified command is not processed.
delay.
User response: Issue the command with a valid
User response: The server workload is high. If this objects string.
condition persists, you may need to consider adjusting
the server workload.
ANR2605E Command: Invalid priority - priority.
ANR2600E Command: Invalid schedule name - Explanation: The specified command has been issued
schedule name. with an invalid priority.
Explanation: The specified command has been issued System action: Server operation continues, but the
with an invalid schedule name. command is not processed.
System action: Server operation continues, but the User response: Issue the command and specify a valid
command is not processed. priority.
User response: Issue the command with a valid
schedule name. ANR2606E Command: Invalid start date - date.
ANR2601E Command: Schedule description exceeds with an invalid start date.
maximum length characters.
Explanation: The specified command has been issued command is not processed.
with a description that exceeds the maximum length.
User response: Issue the command and specify a valid
System action: Server operation continues, but the start date.
User response: Issue the command and specify a valid ANR2607E Command: Invalid start time - time.
description.
with an invalid start time.


ANR2613E Command: Invalid expiration - date.
start time.
with an invalid expiration date.
ANR2608E Command: Invalid duration - duration.
with an invalid duration.
expiration date.
ANR2614E Command: Invalid combination of the
duration.
following parameters: duration, duration
units, period, period units.
ANR2609E Command: Invalid duration units -
duration units.
with an invalid combination of the DURATION,
Explanation: The specified command has been issued DURUNITS, PERIOD, and PERUNITS parameters. This
with an invalid value for duration units. message may be displayed if the duration of the
startup window for the schedule is not shorter than the
System action: Server operation continues, but the period between windows. This message may also be
command is not processed. displayed if DURUNITS=INDefinite is specified, but
User response: Issue the command and specify a valid PERUNITS=Onetime is not specified.
value for duration units. System action: Server operation continues, but the
ANR2610E Command: Invalid period - period. User response: Issue the command and specify a valid
Explanation: The specified command has been issued combination of parameters.
with an invalid period.
System action: Server operation continues, but the ANR2615E Command: Expiration date date has
command is not processed. elapsed.
User response: Issue the command and specify a valid Explanation: The specified command has been issued
period. with an elapsed expiration date date.
ANR2611E Command: Invalid period units - period command is not processed.
units. User response: Issue the command and specify an
Explanation: The specified command has been issued expiration date that has not already elapsed.
with an invalid value for period units.
System action: Server operation continues, but the ANR2616E Command: Start date start date must be
command is not processed. earlier than expiration date expiration.
User response: Issue the command and specify a valid Explanation: The specified command has been issued
value for period units. with a start date that is not earlier than the expiration
date.
ANR2612E Command: Invalid day of week - day of System action: Server operation continues, but the
week. command is not processed.
Explanation: The specified command has been issued User response: Issue the command using a schedule
with an invalid value for day of the week. start date that is earlier than the expiration date.

command is not processed. ANR2617E Command: Schedule schedule name is not
value for day of the week. Explanation: The specified command has been issued
with a schedule name that has not been defined in the
indicated policy domain.

User response: Issue the command using a schedule User response: Issue the command and specify
that has already been defined for this domain. different nodes.
ANR2618E Command: Schedule schedule name is ANR2623E Command: No node associations deleted.
already defined in policy domain domain
name.
but no node associations are deleted.
with a schedule name that has already been defined for
the indicated policy domain.
User response: Issue the command and specify
different nodes.
User response: Issue the command using a schedule
ANR2624E Command: No matching nodes registered.
that has not already been defined for this domain.
Explanation: No matching nodes are found for the
specified command.
ANR2619E Command: Currently defined period
period is invalid with updated period System action: Server operation continues, but the
units. command is not processed.
Explanation: The specified command has been issued User response: Issue the command and specify
with a value for period units that is not allowed with different nodes.
the existing period.
System action: Server operation continues, but the ANR2625E Command: No matching nodes registered
command is not processed. in policy domain domain name.
User response: Issue the command and specify a new Explanation: The specified command has been issued,
period. but no matching nodes are registered in the indicated
policy domain.
ANR2620E Command: Currently defined duration System action: Server operation continues, but the
duration is invalid with updated command is not processed.
duration units.
User response: Issue the command and specify
Explanation: The specified command has been issued different nodes.
with a value for duration units that is not allowed with
the existing duration.
ANR2626E Command: Invalid value for replace -
System action: Server operation continues, but the replace.
User response: Issue the command and specify a new with an invalid value for replace.
duration.
ANR2621E Command: No matching schedules.
User response: Issue the command using a valid value
Explanation: The specified command has been issued for replace.
but no matching schedules have been found.
System action: Server operation continues, but the ANR2627E Command: Invalid value for format -
command is not processed. format.
User response: Issue the command and specify Explanation: The specified command has been issued
different schedules. with an invalid value for format.
ANR2622E Command: No new node associations command is not processed.
added.
User response: Issue the command using a valid value
Explanation: The specified command has been issued for format.
but no new node associations are defined.

ANR2628E Command: Invalid date - date. ANR2634E Command: Invalid end time - time.
Explanation: The specified command has been issued Explanation: The specified command has been issued
with an invalid date. with an invalid end time.
System action: Server operation continues, but the System action: Server operation continues, but the
command is not processed. command is not processed.
User response: Issue the command with a valid date. User response: Issue the command with a valid end
time.
ANR2629E Command: Invalid time - time.
ANR2635E Command: Invalid time range - Begin:
begin End: end.
with an invalid time.
with an invalid time range. This occurs if the date and
time for the beginning of the time range (begin) do not
User response: Issue the command with a valid time. precede the date and time for the end of the time range
(end).
ANR2630E Command: Event deletion is already in System action: Server operation continues, but the
process. command is not processed.
Explanation: The specified command has been issued User response: Issue the command with a valid time
while event deletion is already in progress. range.
command is not processed. ANR2636E Command: Invalid value for exceptions
only - exceptions only.
User response: Wait for event deletion to complete
before issuing the command. Explanation: The specified command has been issued
with an invalid value for exceptions only.
ANR2631E Command: Invalid begin date - date. System action: Server operation continues, but the
with an invalid begin date. User response: Issue the command with a valid value
for exceptions only.
ANR2637E There is insufficient authority to create
User response: Issue the command with a valid begin the recovery log files.
date.
Explanation: The database manager, running under
the user ID for the IBM Spectrum Protect instance, does
ANR2632E Command: Invalid begin time - date. not have the authority to create files in one or more of
Explanation: The specified command has been issued the log directories.
with an invalid begin time. System action: The server process ends.
System action: Server operation continues, but the User response: Ensure that the user ID for the IBM
command is not processed. Spectrum Protect instance has write permission to all
User response: Issue the command with a valid begin active, mirror, archive, and failover archive log
time. directories. No matter which user ID is running the
dsmserv process, the recovery log files are written by
the database manager. The permissions on these log
ANR2633E Command: Invalid end date - date. directories must allow write access from the database
Explanation: The specified command has been issued manager user ID. Change the ownership of the
with an invalid end date. recovery log directories to the user ID for the IBM
Spectrum Protect instance.
User response: Issue the command with a valid end
date.

User response: Issue the command with a valid value.

ANR2638W This command will delete all user data
and log files, as well as any
backup/restore history for the IBM ANR2643E Command: Invalid schedule query period
Spectrum Protect server database. Are - value.
you sure you want your database and all
of its references removed (y or n)? Explanation: The specified command has been issued
with an invalid value.
Explanation: A REMOVEDB command has been
entered. System action: Server operation continues, but the
continue. User response: Issue the command with a valid value.
User response: Enter 'y' to remove the database or 'n'

to leave the server database. ANR2644E Command: Invalid maximum number of
command retries - value.
ANR2639E Command failed - no files have been Explanation: The specified command has been issued
defined for storing sequential volume with an invalid value.
history information. System action: Server operation continues, but the
Explanation: Sequential volume history information is command is not processed.
required to restore the server data base. Because no User response: Issue the command with a valid value.
files were configured for receiving this information, the
operation fails.
ANR2645E Command: Invalid retry period - value.
User response: To have the server automatically with an invalid value.
record sequential volume history information to assist
in server recovery, use the VOLUMEHISTORY option System action: Server operation continues, but the
in the server options file to specify where history command is not processed.
information should be written. If you update the User response: Issue the command with a valid value.
options file, restart the server.
ANR2646E Command: Invalid scheduling mode -

ANR2640E Command: Invalid percentage of sessions value.
for scheduled processing - value.
Explanation: The specified command has been issued with an invalid value.
System action: Server operation continues, but the command is not processed.
ANR2647E Command: Invalid type - type.

ANR2641E Command: Invalid event record retention
period - value. Explanation: The specified command has been issued
with an invalid type.
with an invalid value. System action: Server operation continues, but the
command is not processed. User response: Issue the command with a valid type.

ANR2648E Command: Type string exceeds maximum
length characters.
ANR2642E Command: Invalid percentage for
randomization - value. Explanation: The specified command has been issued
with a type string that exceeds the maximum length.
with an invalid value. System action: Server operation continues, but the
command is not processed. User response: Issue the command with a valid type
string.

ANR2649E Command: Schedule schedule name is not ANR2653W Command: Node node name cannot be
defined. processed because it is not registered, is
decommissioned or does not belong to
the specified domain.
with a schedule name that has not been defined.
Explanation: This command cannot be processed for
the indicated node. The specified node must be
registered to the server, and assigned to the required
User response: Issue the command with a schedule domain. The node cannot be decommissioned.
that has already been defined.
System action: The indicated node is not processed,
but other nodes may be processed if specified by this
ANR2650E Command: Schedule schedule name is command.
already defined.
Explanation: The specified command has been issued incorrectly, reissue the command with the correct node
with a schedule name that has already been defined. name.
command is not processed. ANR2654E Command: The NODES parameter cannot
be used when querying administrative
User response: Issue the command with a schedule schedules.
name that has not already been defined.
Explanation: A QUERY SCHEDULE command has
been issued with TYPE=ADMINISTRATIVE and the
ANR2651E Command: Invalid combination of one or NODES parameter both specified. The NODES
more of the following parameters: cmd, parameter cannot be specified when querying
type, action, objects, options. administrative schedules.
Explanation: The specified command has been issued System action: Server operation continues, but the
with an invalid combination of the CMD, ACTION, command is not processed.
OBJECTS, and OPTIONS parameters. This message is
displayed when the CMD parameter is specified and User response: Issue the command without the
TYPE=CLIENT is not specified, or when NODES parameter.
TYPE=ADMIN is specified, and one or more of the
following is specified: ACTION, OBJECTS, or
ANR2655E Command: Invalid client action schedule
OPTIONS.
duration - days.
with an invalid number of days. Valid values are 1 to
User response: Issue the command with a valid 9999 inclusive. days specifies the length of time during
combination of parameters. which a schedule defined by the DEFine CLIENTAction
command must be executed by an associated node.
After that, the schedule will be deleted from the
ANR2652E Command: Invalid combination of one or database.
more of the following parameters:
active, cmd, type. System action: Server operation continues, but the
with an invalid combination of the TYPE, CMD, or User response: Reissue the command with a valid
ACTIVE parameters. This message is displayed when number of days.
TYPE=CLIENT is specified and one or more of the
following is specified: ACTIVE, CMD.
ANR2656E Command: Invalid schedule style
System action: Server operation continues, but the schedStyle.
User response: Issue the command with a valid with an invalid schedule style.
combination of parameters.
schedule style.


ANR2657E Command: Invalid month month.
User response: To see the options for the existing
with an invalid month.
schedule, issue: QUERY SCHEDULE
System action: Server operation continues, but the FORMAT=DETAILED for the client or administrative
command is not processed. schedule. Determine if the error was caused by one of
the following:
month. v a conflict between parameters to the update
command.
v a conflict between a parameter specified with the
ANR2658E Command: Invalid day of month month.
update command and a value that already exists for
Explanation: The specified command has been issued the schedule.
with an invalid day of month.
For the latter problem, also update the existing option
System action: Server operation continues, but the that is causing the problem. Correct the update
command is not processed. command and issue it again.
day of month. ANR2662I (*) "Query schedule format=standard"
displays an asterisk in the day of week
column for enhanced schedules. The
ANR2659E Command: Invalid week of month month. period column is blank. Issue "query
Explanation: The specified command has been issued schedule format=detailed" to display
with an invalid week of month. complete information about an
enhanced schedule.
command is not processed. Explanation: This message explains the standard
display for an enhanced schedule.
week of month. System action: Server operation continues.
User response: Issue "query schedule format=detailed"
ANR2660E Command: Invalid combination of to display information about an enhanced schedule.
enhanced schedule parameters or their
values: parm1 and parm2. ANR2663I Command: resetting existing options
Explanation: The specified command has been issued options for schedule name to default
with an invalid combination of the DAYOFMONTH, values. .
WEEKOFMONTH, and DAYOFWEEK parameters. Explanation: The update schedule command has reset
WEEKOFMONTH and DAYOFWEEK cannot be existing options for the schedule to default values. The
specified with DAYOFMONTH. WEEKEND or change is required by the parameters specified with the
WEEKDAY must be specified with the FIRST or LAST update or audit commands.
week of month.
command is not processed. User response: None.
combination of parameters. ANR2664E Command: Invalid parameter parm for
schedule style schedule style.
ANR2661E Command: Invalid combination of Explanation: A specified parameter is not valid for the
enhanced schedule parameters or their schedule style.
values, parm1 and parm2, found for
schedule name.
Explanation: The specified update command has been
User response: Issue the command and with
issued with either an invalid combination of
parameters valid for the schedule style.
parameters or their values, or a specified parameter or
value is not compatible with an option that is not being
updated for the existing schedule. WEEKOFMONTH
and DAYOFWEEK must not be specified with
DAYOFMONTH. WEEKEND or WEEKDAY must be
specified with the FIRST or LAST week of month.

ensure that the client is not making a security attack

ANR2665W Command: Invalid month and day, month
against the server.
day, detected.
with an invalid combination of MONTH and User response: None.
DAYOFMONTH. If one month and one day were
specified in the command, the command will fail. If
there is at least one valid month and day combination, ANR2669E The specified deduplication-verification
the schedule will be defined and run on the valid level is invalid.
dates. The schedule will skip the invalid month and System action: Server operation continues.
day combinations.
User response: Specify a value 0 - 100 for this
System action: Server operation continues. command.
User response: Determine the correct day and month
combinations. If the command failed, issue the define ANR2670E Export command: Invalid value for
command again. If the schedule was defined, use the SCHEDSTYLE parameter detected while
update command to change the month and day values. exporting schedule schedule name in
ANR2666W Command: Invalid month and day, month value is used during import.
day, detected for schedule name. Explanation: During processing of command export
Explanation: The specified update command has been command, an invalid value is encountered for the
issued with either an invalid combination of MONTH SCHEDSTYLE parameter for schedule schedule name in
and DAYOFMONTH, or a specified MONTH or domain domain name.
DAYOFMONTH value is incompatible with a MONTH System action: Export processing continues, but the
or DAYOFMONTH value that is not being updated for exported data contains an unknown SCHEDSTYLE
the existing schedule. If there is just one month and value for this schedule. If this data is imported, the
one day combination and that combination is invalid, default or existing SCHEDSTYLE value is used.
the command will fail. If there is at least one valid
month and day combination, the schedule will be User response: Update the SCHEDSTYLE value for
updated and run on the valid dates. The schedule will this schedule and restart the export command.
skip the invalid month and day combinations. Alternatively, use the export data with the unknown
value, and check and update the SCHEDSTYLE value
System action: Server operation continues. after import processing has been performed.
User response: To see the options for the existing
schedule, issue "q sched f=d" for the client or ANR2671E Export command: Invalid value for
administrative schedule. Determine the correct day and SCHEDSTYLE parameter detected while
month combinations. If the the command failed, issue exporting administrative schedule
the update command again. schedule name - default or existing value
ANR2667W Audit volume process has skipped Explanation: During processing of command export
volume volume name due to an error. command, an invalid value is encountered for the
Explanation: During processing of an AUDIT SCHEDSTYLE parameter for administrative schedule
VOLUME command for the volume shown, an schedule name.
unrecoverable error occurred on the volume. System action: Export processing continues, but the
System action: The AUDIT VOLUME command has exported data contains an unknown SCHEDSTYLE
skipped the volume shown. value for this schedule. If this data is imported, the
server uses the default or existing SCHEDSTYLE value.
User response: Examine messages that were
previously issued that explain the cause of the failure User response: Update the SCHEDSTYLE value for
and correct the error if possible. Once the error has this schedule and restart the export command.
been corrected, reissue the command. Alternatively, the export data with the unknown value
can be used, and the SCHEDSTYLE value can be
checked and updated after import processing has been
ANR2668I The deduplication-verification level is performed.
set to percent.
server command SET DEDUPVERIFICATIONLEVEL is
issued. Setting the deduplication-verification level helps

SCHEDSTYLE parameter for administrative schedule

schedule name.
SCHEDSTYLE parameter in exported
data for schedule schedule name in System action: Processing of the command continues.
domain domain name. If a later command is issued that causes the data to be
imported, the default or existing SCHEDSTYLE value is
used.
SCHEDSTYLE parameter for schedule schedule name in User response: If the data is imported with a later
policy domain domain name. command, verify that the correct SCHEDSTYLE value
is used for this schedule.
default or existing SCHEDSTYLE value is used. ANR2676E Import command: Invalid value for
data - administrative schedule schedule
command, verify that the correct SCHEDSTYLE value
name defined with default
is used for this schedule.
SCHEDSTYLE value.
schedule name.
domain name defined with default
SCHEDSTYLE value. System action: Processing of the command continues,
by using the default SCHEDSTYLE value for this
schedule.
SCHEDSTYLE parameter for schedule schedule name in User response: Verify that the correct SCHEDSTYLE
policy domain domain name. value has been used for this schedule. Update this
by using the default SCHEDSTYLE value for this
schedule. ANR2677E Import command: Invalid value for
User response: Verify that the correct SCHEDSTYLE
data - existing SCHEDSTYLE value for
value has been used for this schedule. Update this
administrative schedule schedule name
was not updated.
data - existing SCHEDSTYLE value for
schedule name.
name was not updated. System action: Processing of the command continues,
by using the existing SCHEDSTYLE value for this
schedule.
SCHEDSTYLE parameter for schedule schedule name in User response: Verify that the correct SCHEDSTYLE
policy domain domain name. value has been used for this schedule. Update this
by using the existing SCHEDSTYLE value for this
schedule. ANR2678E Server database format failed.
User response: Verify that the correct SCHEDSTYLE Explanation: A failure occurred during the format of
value has been used for this schedule. Update this the IBM Spectrum Protect server database. This
value, if necessary. occurred during the processing of a 'DSMSERV
FORMAT' command.
ANR2675E Import command: Invalid value for System action: Server format processing terminates.
data for administrative schedule schedule User response: Review error messages to determine
name. the cause of the failure and retry the 'DSMSERV
FORMAT' once the issue has been resolved.

ANR2679E Command: All of the nodes provided are ANR2684E Command: SnapMirror operations are not
invalid. supported on NAS virtual filespace
definitions.
Explanation: While verifying the parameters of the
specified command, no valid node was found. Explanation: A SnapMirror backup or restore was
attempted on a NAS virtual filespace. Network
Appliance SnapMirror backups do not support
User response: Verify that the nodes specified are directory level backup, therefore a virtual filespace may
correct and all are registered. Then, reissue the not used with TYPE=SNAPMIRROR.
command.
User response: Reissue the command by specifying
ANR2680E Command: You cannot specify TOC=YES
TYPE=DUMPIMAGE.
when TYPE is SNAPMIRROR.
Explanation: A SnapMirror backup was attempted
ANR2685I SnapMirror backup of NAS node
while specifying TOC=YES. Network Appliance
nodename, file system file system, started
SnapMirror backups do not support TOC creation.
as process process ID by administrator
System action: The server ends the command. administrator.
User response: Reissue the command without Explanation: A SnapMirror backup is started for the
specifying TOC=YES. indicated file system of a NAS node. The operation is
initiated by the administrator shown.
ANR2681E Command: The file server movername does System action: The indicated process is started.
not support SnapMirror-to-Tape
operations or is not running NDMP
Version 4.
ANR2686I SnapMirror Restore of NAS node
Explanation: A SnapMirror backup was specified with
nodename, file system filesystem, started as
a NAS device that does not Network Appliance
process process ID by administrator
SnapMirror backup operations.
administrator. A full image for this file
System action: The server ends the command. system will be restored to destination
destination.
User response: Reissue the command by specifying a
standard NDMP full or differential backup. . Explanation: A SnapMirror restore is started for the
indicated file system of a NAS node. The operation is
initiated by the administrator shown. The restore will
ANR2682E Command: You cannot specify be performed using a full image of this file system. The
MODE=DIFF when TYPE is file system will be restored to the indicated destination.
SNAPMIRROR.
Explanation: A SnapMirror backup was attempted
while specifying MODE=DIFF. Network Appliance User response: None.
SnapMirror backups may only be full image backups.
System action: The server ends the command. ANR2687E Command: You cannot specify a
FILELIST when TYPE is
User response: Reissue the command and do not SNAPMIRROR.
specifiy MODE=DIFF with TYPE=SNAPMIRROR.
Explanation: A file level restore was attempted from a
SnapMirror backup. Network Appliance SnapMirror
ANR2683I Command: A Table of Contents will not backups do not support file level restore.
be created for a SnapMirror backup.
Explanation: A Netapp SnapMirror backup was
requested and the TOC parameter is set to User response: Reissue the command without the
PREFERRED. The backup will continue, however no FILELIST parameter.
Table of Contents will be created.
System action: The server operation continues. ANR2688E Command: The SnapMirror Restore of
NAS node nodename, file system file
User response: None. system, cannot be started. The
destination file system destination is not
set to "Restricted" on the NAS device.


ANR2693E Command: Invalid action and subaction
specified command, no valid node was found.
combination.
User response: Verify that the nodes specified are with an invalid combination of action and subaction
correct and all are registered. Then, reissue the values.
command.
ANR2689W Command: The dataformat of the
datamover data mover is incompatible
subaction.
with the NAS device with host
identifier hostId.
ANR2694E Command: Action must be specifed with
Explanation: The dataformat provided in the
subaction.
command is not compatible with the NAS device
which is associated with the high level address. was Explanation: The specified command has been issued
found. with a subaction and no action value.
System action: The server completes the command. System action: Server operation continues, but the
User response: Determine the proper dataformat for
your NAS device and reissue the command. User response: Issue the command and specify a valid
subaction.
ANR2690E Command: The file system file system is in
restricted state and cannot be used in an ANR2695E The deduplication mode for node node
NDMP backup or restore operation. name was set to SERVERONLY.
Explanation: A NAS file system that is in the Explanation: The server detected a potential security
restricted state was specified for an NDMP backup or attack and disabled client-side deduplication.
restore operation. You cannot perform an NDMP
System action: Server and client operations continue.
backup or restore of a file system in the restricted state.
User response: Verify that the client workstation does
not have any applications that are attempting a security
User response: Refer to your NAS device's attack on the server. If the client is secure, re-enable
documentation on how to unrestrict the file system. client-side deduplication on the node by issuing the
Then, reissue the command. server command UPDATE NODE with the
DEDUPLICATION=CLIENTORSERVER parameter.
ANR2691E Command: The file server file server name ,
does not support the NDMP Cluster ANR2696E Export command: Invalid value for
Aware Backup extension and the SUBACTION parameter detected while
datamover type requires it. exporting schedule schedule name in
Explanation: A datamover of type NASCLUSTER or
NASVSERVER was defined however, the file server
does not support the NDMP Cluster Aware Backup Explanation: During processing of command export
extension. command, an invalid value is encountered for the
ACTION parameter for schedule schedule name in
System action: The IBM Spectrum Protect server
domain domain name.
define operation on the file server fails.
User response: Verify that the file server is running
exported data will contain an unknown SUBACTION
clustered Data OnTap from Netapp.
default or existing SUBACTION value is used.
ANR2692E Command: Invalid subaction - action.
User response: Update the SUBACTION value for this
Explanation: The specified command has been issued schedule and restart the export command. Alternatively,
with an invalid subaction. use the export data with the unknown value, and check
and update the SUBACTION value after import
System action: Server operation continues, but the processing has been performed.
subaction.

User response: To determine the source of the error,

examine server messages issued prior to this message.
SUBACTION parameter in exported
Issue the QUERY ACTLOG command to view the
activity log and search for messages. After the error has
domain name defined with default
been resolved, restart the server to restore central
SUBACTION value.
scheduler operations. If the error cannot be isolated and
Explanation: During processing of command import resolved, contact your service representative.
SUBACTION parameter for schedule schedule name in
ANR2701E The schedule manager could not be
started: diagcode.
Explanation: The schedule manager cannot be started
by using the default SUBACTION value for this
during initialization because sufficient memory is not
schedule.
available. Diagnostic code diagcode is issued.
User response: Verify that the correct SUBACTION
value has been used for this schedule. Update this
value, if necessary. User response: See the documentation for the
application.
SUBACTION parameter in exported
data - existing SUBACTION value for ANR2702E The schedule prompter could not be
schedule schedule name in domain domain started: diagcode.
Explanation: The schedule prompter cannot be started
Explanation: During processing of command import during initialization because sufficient memory is not
command, an invalid value is encountered for the available. Diagnostic code diagcode is issued.
SUBACTION parameter for schedule schedule name in
policy domain domain name. System action: Initialization fails.
System action: Processing of the command continues, User response: See the documentation for the
by using the existing SUBACTION value for this operating system about how to increase memory for an
schedule. application.
User response: Verify that the correct SUBACTION

value has been used for this schedule. Update this ANR2703E Schedule prompter aborted.
value, if necessary. Explanation: The schedule prompter ends because of a
processing error.
ANR2699E Import command: Invalid value for System action: Server operation continues, but
SUBACTION parameter in exported prompted scheduling is not operational.
data for schedule schedule name in
domain domain name. User response: To determine the source of the error,
examine server messages issued prior to this message.
Explanation: During preview processing of command Issue the QUERY ACTLOG command to view the
import command, an invalid value is encountered for the activity log and search for messages. After the error has
SUBACTION parameter for schedule schedule name in been resolved, restart the server to restore central
policy domain domain name. scheduler prompting operations. If the error cannot be
System action: Processing of the command continues. isolated and resolved, contact your service
If a later command causes the data to be imported, the representative.
default or existing SUBACTION value is used.
User response: If the data is imported with a later ANR2707E Out of server log space in central
command, verify that the correct SUBACTION value is scheduler.
used for this schedule. Explanation: The server ends a database update
transaction for the central scheduler because sufficient
ANR2700E Schedule manager aborted. log space is not available on the server.
Explanation: The schedule manager has ended System action: Server operation continues, but the
because of an error condition and is not able to database update fails.
maintain entries for scheduled operations. User response: To increase the amount of log space
System action: Server operation continues, but the that is available to the server, evaluate the directories
central scheduler is not operational. and file systems that are assigned to the

ANR2713E Node node1 trying to start scheduled
operation for node node2 - session
rejected.
full. Explanation: The client scheduler for node node1 has
attempted to execute a scheduled operation for another
node, node2.
location that are no longer active and cannot be System action: Server operation continues, but the
archived to the ARCHIVELOGDIRECTORY and scheduled operation is not processed.
User response: Try restarting the client scheduler for
node node1. If the problem persists, contact your service
representative to resolve client program error.
ANR2714E Node node1 trying to report scheduled
operation results for node node2 -
ANR2708E Out of server database space in central
session rejected.
scheduler.
Explanation: The client scheduler for node node1 has
attempted to report the results of a scheduled operation
transaction for the central scheduler because sufficient
using another node name, node2.
results that were sent from node node1 are not be stored
database update fails.
in the server's database.
representative to resolve the client program error.
the database.
ANR2715E Client node node id unable to register

ANR2709E Schedule manager : Unable to start
valid address for server prompting: type
event record deletion.
address type (high address low address).
Explanation: Event record deletion cannot be started
Explanation: The client scheduler for node node id has
because sufficient memory is not available.
attempted to register an invalid address for
System action: Server operation continues, but event server-prompted central scheduling. The address was
records are not automatically deleted after their type address type with high-level field high address and
retention period has elapsed. low-level field low address. The only valid address type
is 1.
operating system about how to increase memory for an System action: Server operation continues, but the
application. node node id will not be prompted to perform
scheduled operations.
ANR2712E Node node1 requested scheduling User response: Verify that the address type and
information for node node2 - session address are correct for this client. The only valid
rejected. address type is 1 (for TCP/IP). Make sure the client
scheduler is not using an invalid address obtained from
Explanation: A request for pending scheduled
the client's options file or from the command line when
operations has been sent from the client scheduler for
the client scheduler was started.
node node1. However, the request is for scheduling
information concerning another node node2.
ANR2716E Schedule prompter was not able to
contact client node name using type
client scheduler for node node1 will not be able to
address type (high address low address).
process pending operations.
Explanation: The server has attempted to prompt the
client scheduler for node node name because a
scheduled operation should be started. The server is
representative to resolve the client program error.
unable to contact the client by using address type
address type, with high-level field high address and
low-level field low address.

System action: Server operation continues, but node

ANR2719E Command: Invalid parameter parm for
node name is not prompted to start the scheduled
ACTION=DEPLOY.
operation. If operations should be started for other
nodes, the server will attempt to prompt the client Explanation: A parameter that is specified is not valid
schedulers for these nodes. This error is usually caused for ACTION=DEPLOY.
by network outages or the client scheduler program not
System action: Server operations will continue, but
being run on the client node.
the command is not processed.
User response: Verify that the address type and
User response: Reissue the command with valid
address are correct for this client. The only valid
ACTION=DEPLOY parameters.
address type is 1 (for TCP/IP). Make sure that the
client scheduler is not using an invalid address,
obtained at the time the client scheduler was started, ANR2720E Command: Node node name is currently
from either the client's options file or from the being replicated.
command line. Verify that the client scheduler for node
node name is running and that the necessary Explanation: The command shown specifies a node
communication links to that scheduler are operational. that is currently being replicated to another server.
Firewalls must allow traffic from the server to the client System action: The server does not process the
and from the client to the server without the session command.
timing out. Ensure that the DNS configuration is
correct. User response: Reissue the command at a later time,
or if necessary, cancel the current replication and
ANR2717E Schedule prompter cannot contact client
node name using address type (address
type). ANR2721E A non-replication SSL session to
address address is requested.
Explanation: The server attempts to prompt the client
scheduler for node node name because scheduled work Explanation: A non-replication SSL session to the
should be started. However, either the server does not indicated address was attempted. Server-to-server SSL
support address type address type needed for sessions are supported for replication only.
server-prompted scheduling, or the communication System action: The server does not start the session.
method is not currently available. The only valid
address type is 1 (for TCP/IP). User response: If you want to configure the same
target server for both SSL and non-SSL
System action: Server operation continues, but the communications, you can configure multiple server
server does not prompt node node name. definitions when you issue the DEFINE SERVER
User response: If the server does not support the command. You can have multiple server definitions
address type specified, clients may only use the polling with the same target address if the server names are
mode of scheduling. If the communication method is not the same.
temporarily not available, prompted mode scheduling
will resume after the communication problem is fixed ANR2722I The server now accepts sessions that
and service restored. If the problem persists, contact originate from server server name
Explanation: The server can now accept sessions from
the named server.
ANR2718W Schedule manager disabled.
Explanation: The schedule manager has been disabled
because the DISABLESCHEDS YES option was User response: None.
specified in the server options file.
System action: Server operation continues, but the ANR2723I The server is enabled to have outbound
central scheduler is not operational. sessions to server server name
User response: To enable the schedule manager, Explanation: The server now allows sessions targeted
specify DISABLESCHEDS NO in the server options file to the named server.
and restart the server. System action: None.

However the specified node is is skipped for this

ANR2724I The server does not accept sessions from
operation.
server server name
User response: Verify that all of the nodes to be
Explanation: The server rejects sessions from the
replicated are in SEND or SYNCSEND mode. Reissue
named server.
the command, or, if necessary, cancel the replication
System action: None. process and reissue the command.
ANR2729W This command will register the node to
new domain domainname.
ANR2725I The server is disabled for sessions with
Changing the domain will cause the
server server name
node to be disassociated from the
Explanation: The server cannot initiate sessions to the schedule of original domain.
named server.
Explanation: The schedule belongs to the domain. The
System action: None. node will be disassociated from the schedule if the
node is registered to new domain.
System action: IBM Spectrum Protect prompts the
user to continue.
ANR2726E Command: None of the specified nodes
are configured for replication or they are User response: Enter 'Y' to change the domain. Enter
part of an active replication process. 'N' if you do not want to change the domain.
Explanation: The replication command did not start
because data belonging to the specified nodes was ANR2730I Default authentication set to defaultAuth.
being replicated, or because the nodes are not
configured for replication.
the Set DEFAULTAUTHentication command. It
System action: The server ends the command. indicates the current default AUTHENTICATION value
for the REGISTER NODE and REGISTER ADMIN
User response: Verify that the specified nodes are commands.
correct and that they are configured for replication.
Verify that the nodes are not part of an active System action: None.
replication process. A node is configured for replication
if the replication state is ENABLED or DISABLED. To
determine the replication state of a node, issue the
QUERY NODE FORMAT=DETAILED command. To ANR2731E An invalid command was issued: issued
configure nodes for replication, issue the UPDATE command. The command prerequisite
NODE command. After the situation has been command must be issued first.
corrected, reissue the REPLICATE NODE command.
Explanation: The specified server command was
issued prior to another required command.
ANR2727E Command: Node node name is currently
accessing server server name.
User response: Issue the required command and then
reissue the command that caused the error.
that has an active session with the specified server.
System action: The local server does not process the
ANR2732E Unable to communicate with the
command.
external LDAP directory server.
Explanation: The server tried to communicate with
or if necessary, cancel the current session and reissue
the external LDAP directory server but was unable to
the command.
do so.
ANR2728E Command: Node node name cannot be
replicated because it is not in the SEND User response: Validate that the external LDAP
or SYNCSEND mode. directory server is actively running. Also, validate that
the LDAPURL option is set appropriately and refers to
Explanation: The replication mode of a specified node
a valid LDAP directory server.
is RECEIVE or SYNCRECEIVE. To replicate, the
replication mode must be SEND or SYNCSEND.
System action: The server processes the command.

ANR2733W Unable to authenticate with the external ANR2736W Renamed administrator admin name must
LDAP directory server to process the be updated with the current password.
SET LDAPUSER command.
Explanation: In response to a RENAME ADMIN
Explanation: The LDAPUSER value or the command with an admin that uses LDAP
LDAPPASSWORD value or both are invalid. authentication, the admin was renamed in the IBM
Spectrum Protect database, but an LDAP entry does not
System action: The server command continues.
exist for the new name in the LDAP directory server.
User response: During the SET LDAPUSER command, This can happen because the SYNCLDAPDELETE=NO
the IBM Spectrum Protect server tried to authenticate to parameter was used or an LDAP entry did not exist for
the external LDAP directory server. If the the original name.
LDAPPASSWORD is not set or is invalid, the
authentication fails, but the SET LDAPUSER command
succeeds. The LDAPUSER value and the User response: Issue the UPDATE ADMIN command
LDAPPASSWORD value both must be set correctly to the renamed admin using the current password,
before the server can communicate with the external before attempting any sessions with the admin.
LDAP directory server. The SET LDAPPASSWORD
command fails if authentication with the external
ANR2737E Command: All of the admins provided
LDAP directory server fails with the current
are invalid.
LDAPUSER and new LDAPPASSWORD.
You can validate the current LDAPUSER by issuing the
specified command, no valid admin was found.
QUERY STATUS command. The LDAPUSER and
LDAPPASSWORD commands can be corrected with the System action: The server ends the command.
appropriate SET commands. If there is still an
authentication error, validate that the user and User response: Verify that the admins specified are
password are set correctly in the external LDAP correct and all are registered. Then, reissue the
directory server. command.
ANR2734E Unable to authenticate with the external ANR2738W Command: parameter conflicts with
LDAP directory server to process the parameter - conflicting parameter.
SET LDAPPASSWORD command. Explanation: Conflicting parameters were specified in
Explanation: The LDAPUSER value or the the command.
LDAPPASSWORD value or both are invalid. System action: The server bypasses the conflicting
System action: The server command fails. parameter and processing continues.
User response: You can validate the current User response: Verify which parameter you want to
LDAPUSER by issuing the QUERY STATUS command. use and reissue the command, if necessary. If the
The LDAPUSER and LDAPPASSWORD commands can command needs to be reversed, undo the command,
be corrected with the appropriate SET commands. If correct the syntax, and then reissue the command.
there is still an authentication error, validate that the
user and password are set correctly in the external ANR2739I Audit LDAP directory started as process
LDAP directory server. process ID.
ANR2735W Renamed node node name must be audit the LDAP directory entries. The audit was
updated with the current password. assigned the process ID shown.
Explanation: In response to a RENAME NODE System action: The audit process starts and server
command to a node that uses LDAP authentication, the operation continues.
node was renamed in the IBM Spectrum Protect
database, but an LDAP entry does not exist for the new User response: The administrator may query the
name in the LDAP directory server. This can happen status of the audit process by using the QUERY
because the SYNCLDAPDELETE=NO parameter was PROCESS command, or cancel the process with the
used or an LDAP entry did not exist for the original CANCEL PROCESS command.
name.
User response: Issue the UPDATE NODE command to
the renamed node using the current password, before
attempting any sessions with the node.

ANR2740E Alert monitor could not start or has ANR2744W Approval processing for request requestId
failed and stopped. to process Command issued by
administrator administrator failed;
Explanation: The server alert monitor is not able to
command execution was not successful.
start or continue processing.
Explanation: The command was submitted for the
System action: The alert monitor is not able to run.
designated administrator but failed to run successfully.
User response: Evaluate other messages in the activity
System action: The pending command entry is
log to determine why the alert monitor is unable to
removed and the command needs to be re-issued by
run. This is typically caused by insufficient resources
the originating administrator.
such as a lack of memory or other system resources.
User response: Review the activity log for the
command processed.
ANR2741I Alert monitor has started.
Explanation: The server alert monitor has started
ANR2745I AUDIT LDAPDIRECTORY command
successfully and will evaluate messages to determine
finished: admin only LDAP administrator
and raise alerts for administrative notification where
entries are only in the LDAP directory
necessary.
server (not in the IBM Spectrum Protect
System action: None. server), number administrator entries are
only in the IBM Spectrum Protect server
User response: None. (not in the LDAP directory server), node
only LDAP node entries are only in the
ANR2742W Command: Has been submitted for LDAP directory server (not in the IBM
approval consideration. Spectrum Protect server), number node
entries are only in the IBM Spectrum
Explanation: The command has not been executed. Protect server (not in the LDAP
The command has been recorded for approval directory server), and total deleted entries
consideration. Contact the primary or alternate entries were deleted from the LDAP
approval administrators for consideration and server in total.
disposition of this request. If the command is not
approved prior to the approval duration period, it will Explanation: The inconsistencies between the LDAP
be deleted and the command itself will not be directory server and the IBM Spectrum Protect server
executed. are displayed as a result of the AUDIT
LDAPDIRECTORY command.
command. The command is recorded for pending System action: None.
approval. Issue QUERY PENDINGCOMMAND to see User response: None.
the request.
User response: Contact the primary or alternate ANR2746W Node node name was located in the
approval administrators to disposition this request. If database but not in the LDAP directory
approval is granted, the approval administrator will server.
re-issue the command as part of the approval
processing. And if the command is rejected, it will be Explanation: An inconsistency between the LDAP
deleted and no further action taken. directory server and the IBM Spectrum Protect database
was discovered. A node in the IBM Spectrum Protect
database a does not have a corresponding entry in the
ANR2743I Approval processing for request requestId LDAP directory server. Without an entry in the LDAP
to process Command issued by directory server, the node is inaccessible until action is
administrator administrator is successful; taken. See the user response for recommended action.
command completed.
Explanation: The command was submitted for the
designated administrator and has successfully run to User response: To make the node accessible, you need
completion. to add the node to the LDAP directory server. Issue the
UPDATE NODE command with a password to create
System action: None. an LDAP node entry in the LDAP directory server.
User response: Review the activity log for the
command processed.

ANR2747W Administrator admin name was located in ANR2750I Starting scheduled command schedule
the database but not in the LDAP name ( scheduled command ).
directory server.
Explanation: An inconsistency between the LDAP server starts the execution of a scheduled command.
directory server and the IBM Spectrum Protect database The name of the schedule and the actual command
was discovered. An administrator in the IBM Spectrum scheduled is displayed.
Protect database a does not have a corresponding entry
System action: Server operation continues, the
in the LDAP directory server. Without an entry in the
scheduled command is processed.
LDAP directory server, the administrator is inaccessible
until action is taken. See the user response for User response: None.
recommended action.
System action: None. ANR2751I Scheduled command schedule name
completed successfully.
User response: To make the administrator accessible,
you need to add the administrator to the LDAP Explanation: This message is displayed when the
directory server. Issue the UPDATE ADMIN command server successfully completes processing of a scheduled
with a password to create an LDAP administrator entry command.
in the LDAP directory server.
ANR2748W Node node name was located in the User response: None.
LDAP directory server but not in the
database. ANR2752E Scheduled command schedule name
Explanation: An inconsistency between the LDAP failed.
directory server and the IBM Spectrum Protect database Explanation: This message is displayed when the
was discovered. An unexpected node entry was found server encounters a failure in processing a scheduled
in the LDAP directory server. An extra entry in the command.
LDAP directory server does not affect IBM Spectrum
Protect server operations. If the LDAP directory server System action: Server operation continues. The
is shared by multiple IBM Spectrum Protect servers, the scheduled command is ended.
extra entry might be needed for one or more of the User response: Examine messages issued prior to this
other IBM Spectrum Protect servers. message and use the UPDATE SCHEDULE command
System action: If the AUDIT LDAPDIRECTORY to correct the scheduled command. The QUERY EVENT
command is issued with FIX=YES, the server deletes command may also be used to determine the cause of
the node entry from the LDAP directory server. If the the failure for this scheduled command.
command is issued with FIX=NO, the server does not
delete the entry. ANR2753I (Schedule name):command response
User response: None. Explanation: This message is used to display the
server response to a scheduled command. The name of
ANR2749W Administrator admin name was located in the command schedule is included at the beginning of
the LDAP directory server but not in the the message in parentheses.
database. System action: Server operation continues. The
Explanation: An inconsistency between the LDAP scheduled command is ended.
directory server and the IBM Spectrum Protect database User response: None.
was discovered. An unexpected administrator entry
was found in the LDAP directory server. An extra entry
in the LDAP directory server does not affect IBM ANR2754E DEFINE SCHEDULE or UPDATE
Spectrum Protect server operations. If the LDAP SCHEDULE parameter CMD='command'
directory server is shared by multiple IBM Spectrum - Unknown command.
Protect servers, the extra entry might be needed for one Explanation: The specified command is not a valid
or more of the other IBM Spectrum Protect servers. server command.
System action: If the AUDIT LDAPDIRECTORY System action: The DEFINE SCHEDULE or UPDATE
command is issued with FIX=YES, the server deletes SCHEDULE command is not processed.
the administrator entry from the LDAP directory server.
If the command is issued with FIX=NO, the server does User response: Reissue the correct command.
not delete the entry.

ANR2755E DEFINE SCHEDULE or UPDATE ANR2760E Command: Unable to delete the virtual
SCHEDULE parameter CMD='command' file space definition vfs name for node
- not eligible for scheduling. node name. A file space definition exists
with the same name.
Explanation: The specified command is not eligible for
scheduling. Explanation: The DELETE VIRTUALFSMAPPING
command has been entered, but the specified virtual
System action: The DEFINE SCHEDULE or UPDATE
file space mapping vfs name for the node node name has
SCHEDULE command is not processed.
an associated file space definition in server database.
command.
ANR2756I Scheduled command schedule name
User response: To delete the virtual file space
started successfully.
definition, first delete the filespace definition with the
Explanation: This message is displayed when the same name.
server successfully starts processing of a background
process for a scheduled command.
ANR2762I Command: A virtual file space mapping
System action: Server operation continues. named vfs name for node node name has
been updated.
VIRTUALFSMAPPING command, a virtual file space
ANR2757E Command: The NODES parameter cannot mapping for the specified node has been updated in
be used when querying events for the server database.
administrative schedules.
Explanation: A QUERY EVENT command has been
issued with TYPE=ADMINISTRATIVE and the NODES User response: None.
parameter both specified. The NODES parameter
cannot be specified when querying events for
ANR2763E Command: The hexadecimal string
administrative schedules.
entered for the path parameter is not
System action: Server operation continues, but the valid.
User response: Issue the command without the invalid Hexadecimal value for the path parameter.
NODES parameter.
command.
ANR2758E Please specifiy a tracefile name with
User response: Check that the string representing the
less than 37 characters if it is fully
path contains only valid hexadecimal characters and
qualified or 26 characters if it is not
contains an even number of characters. Reissue the
fully qualified.
command with a valid Hex string for the path
Explanation: The .template file adds 9 more characters parameter.
to the end of the filename.
System action: Server operation continues. ANR2764E command: Filespace filespace name cannot
be renamed to new filespace name; a
User response: Reduce the filename length to a virtual file space with this name already
working range for s390 system exists for node node name.
Explanation: The file space name specified as a target
ANR2759I Command: The virtual file space name for the command was found to already exist as a
definition vfs name for node node name virtual file space for the node specified. The command
has been deleted. fails.
Explanation: In response to the DELETE System action: Server operation continues, the
VIRTUALFSMAPPING command, the virtual file space command fails.
mapping vfs name for the node node name has been
deleted in the server database. User response: Reissue the command with a different
target filespace name

for possible reasons a remote session could not be

ANR2765E command: The node node name has an
started.
invalid node type for virtual file space
definitions; the node type must be NAS.
ANR2770E Command: Process process ID skipped
Explanation: A Define VirtualFSMapping command
restoring data from volume volume name
was entered with an invalid node type.
in storage pool name storage pool - drive
System action: The server does not process the path unavailable.
command.
Explanation: The indicated process skipped restoring
User response: You might want to run this command data from the indicated volume because none of the
again, specifying a node of TYPE=NAS. NAS type datamovers is available.
System action: The data in the indicated volume is
ANR2766W Command: Virtual file space name vfs not restored.
name conflicts with file space on the
User response: Use QUERY STGPOOL to obtain the
network attached storage (NAS) device.
device class to which the indicated source storage pool
Explanation: The specified server command has been belongs. Use QUERY DEVCLASS to obtain the library
entered with a virtual file space that has the same containing the source storage pool. Then, use the
name as a file space on the NAS device. QUERY DATAMOVER and QUERY PATH commands
to verify that at least one NAS datamover has paths to
the drives in the library.
User response: Ensure that no virtual file space
mappings for this NAS device have the same name as
ANR2771E Move data process terminated for
an actual file space that exists on the NAS device.
volume volume name - data mover
inaccessible.
ANR2767E Command: The data format of storage
Explanation: Move data processing terminated for the
pool Storage Pool Name does not match
indicated volume because none of the data movers is
the data format of storage pool Storage
accessible.
Pool Name.
System action: Move data ends for the indicated
Explanation: The data format of the indicated storage
volume.
pools does not match. The requested operation failed.
for possible reasons a remote session could not be
User response: Use QUERY STGPOOL F=D to display started.
the data format for various pools and determine which
may be eligible for the operation. Choose a storage
pool that has the matching data format and re-issue the
drive path or data mover unavailable.
command.
Explanation: The indicated process terminated for the
indicated command for one of the following reasons:
ANR2768I Process process ID will use data mover
datamover name for the operation. v None of the data movers with paths to the drives in
the library containing the source storage pool is
Explanation: The indicated data mover is being used available.
by the indicated process.
v None of the data movers with paths to the drives in
System action: The indicated data mover is being the library containing the target storage pool is
used by the indicated process. available.
User response: None. System action: The indicated process ends.
ANR2769E Command: Process process ID terminated - device class to which the source or target storage pool
data mover inaccessible. belongs. Use QUERY DEVCLASS to obtain the library
name that contains the source or target storage pool.
Explanation: The indicated process terminated for the Then, use the QUERY DATAMOVER and QUERY
indicated command because none of the data movers is PATH commands to verify that at least one data mover
accessible. has paths to the drives in the library.
System action: The indicated process terminates.


ANR2773E Move data process terminated for
volume volume name - drive path or data
mover unavailable. User response: Ensure that container and cloud
storage pools are not used with virtual volumes. The
Explanation: MOVE DATA processing terminated for
UPDATE COPYGROUP command can be used to
the indicated volume for one of the following reasons:
update the copy group destination to point to a valid
v None of the data movers with paths to the drives in storage pool.
the library containing the source storage pool is
available.
ANR2777I REPLICATE NODE: Node node name is
v None of the data movers with paths to the drives in
decommissioned and disabled.
the library containing the target storage pool is
available. Explanation: The requested node is decommissioned,
disabled for replication, and has been skipped.
System action: The replication proceeds, but this node
is skipped.
device class to which the source or target storage pool
belong. Use QUERY DEVCLASS to obtain the library User response: None.
name that contains the source or target storage pool.
Then, use the QUERY DATAMOVER and QUERY
PATH commands to verify that at least one data mover ANR2778I Command: Inventory information is
has paths to the drives in the library. missing for object bfid.
Explanation: During a read operation, a damaged
ANR2774E Command: Process process ID terminated - record for a file was identified. The file is skipped.
data format mismatch. System action: The file is not displayed.
Explanation: During restore processing, a data format User response: Correct the error in the file and reissue
mismatch occurred between the storage pool being the QUERY CLEANUP command.
restored and the copy storage pool.
System action: The indicated restore process ANR2779I Command: Inventory information for all
terminates. items cannot be displayed. A total of
User response: Examine the previous error message to num files files are missing inventory
determine the name of the copy storage pool used for information. The missing files are not
the restore. If possible, specify a copy storage pool that displayed.
has the same data format as the storage pool being Explanation: During a read operation, a damaged
restored on the restore command. record for a file was identified. The file is skipped.
System action: The files are not displayed.
ANR2775W Command: Process Process id encountered
an output error. File on volume volume User response: Correct the error in the file and reissue
name skipped - Node node name, type file the QUERY CLEANUP command.
type, file space filespace name, file name
file name, fsId filespace id. ANR2780W Command: Updates for nodes previously
Explanation: During copy or move operation, an processed during this command will be
output error was encountered. The indicated file was rolled back.
skipped. Explanation: An error has occurred during an
System action: The file will not be processed. UPDATE NODE operation. If the UPDATE NODE
command was processing more than one node, updates
User response: If possible, correct the error and re-run for nodes which were previously processed will be
the command. rolled back.
number for node node name (client User response: Correct the error and reissue the
platform) - A storage pool for the target command.
destination is associated with a
container or cloud storage pool.
Explanation: The specified session fails because an
invalid storage pool is used to store the virtual volume.

User response: Verify the existence of that directory

ANR2781E command name: keyword value longer than
and reissue the command.
max length characters.
Explanation: The directory specified for the indicated
ANR2788E Database log path path name is not
keyword is too long. Specify a directory less than or
empty.
equal to the number of characters indicated. This is a
limitation of the underlying database. Explanation: When specifying a new active, archive,
or mirror log directory in the server options file or
System action: Server database format processing
when formatting a server, the indicated directory must
terminates.
be empty to prevent and accidental overwrite of
User response: Specify a valid value for the indicated existing data.
keyword.
System action: If a FORMAT operation was being
performed, the operation stops. If this was a change to
ANR2782I SET DBRECOVERY completed the server options file to specify a new log directory,
successfully and device class for the new directory is ignored, and the existing directory
automatic DB backup is set to value. is used.
Explanation: The device class requirement for User response: Verify the directory that was specified.
automatic database backup is set with the SET Delete any data in that directory if the data is not
DBRECOVERY command. needed, or create a new directory. Reissue the format
command.
ANR2790E Too many symbolic links were found
while traversing file path path name.
ANR2783E FORMAT: Required keyword keyword
System action: The server stops processing the
not specified.
command.
Explanation: A required keyword was not specified
User response: Refer to your operating system's
for database format processing.
manual for the maximum number of symbolic links
System action: Server database format processing allowed on a path name. Reduce the number of
terminates. symbolic links that lead to the file path, and then
User response: Reissue the format command with the
required parameters.
ANR2791E The file or volume name path name is
too long.
ANR2785E An error occurred when trying to access
path name. System action: The server stops processing the
command.
Explanation: An access denied error occurred while
attempting to access a directory. User response: Check your operating system's limits
on files and pathss length.Reissue the command with a
System action: The command stops. shorter file or volume name.
User response: Verify permission for that directory is
set correctly then reissue the command. ANR2792E A component of the path path name is
not a directory.
ANR2786E The server was unable to find path name. Explanation:
Explanation: The server could not find the directory System action: The server stops processing the
specified. command.
System action: The command stops. User response: Verify all directories in the path of the
User response: Verify the existence of that directory file or volume name. Reissue the command with a
and reissue the command. valid file or volume path. command.
ANR2787E The server failed with error code last ANR2793W An invalid value for MAXTXNBYTE is
error when attempt to access path name. found in the database value in bytes.
Explanation: The server failed to access the directory Explanation: The server detects an invalid value for
specified. MAXTXNBYTE in the database. The server will use the
System action: The command stops.

default value for MAXTXNBYTE and processing will

ANR2798E Server operation is denied - server is not
continue.
licensed for License required.
System action: Th server initialization continues.
Explanation: The server refuses a server operation
User response: No action is required because the server is not licensed with the appropriate
support.
ANR2794I LDAP password set. System action: Server operation fails.
Explanation: The password that the server uses to User response: Obtain and register the appropriate
authenticate with the LDAP server has been set, license.
changed or removed with the SET LDAPPASSWORD
command.
ANR2799W Server operation is in violation of server
System action: None. license terms - server is not licensed for
License required.
Explanation: The server warns about a server
operation because the server is not licensed with the
ANR2795I command: Repair failed processing appropriate support.
backup sets for node node name. backup
set count backup sets belonging to node System action: Server operation continues.
count nodes were successfully repaired
User response: Obtain and register the appropriate
before the failure.
license.
Explanation: The REPAIR BACKUPSET command
encountered an error processing backup sets for the
ANR2800E The license manager cannot be started:
specified node. Some backup sets might have been
diagcode.
successfully repaired.
Explanation: The license manager cannot be started
System action: The command failed. Some backup
during initialization because sufficient memory is not
sets might have been repaired.
available. Diagnostic code diagcode is issued.
error. Issue the QUERY ACTLOG command to view the User response: See the documentation for the
activity log and search for messages. Correct the operating system about how to increase memory for an
problem and rerun the command. application.
ANR2796I command: Repair completed for backup set ANR2803I License manager started.
count backup sets belonging to node
Explanation: The license manager is started when the
count nodes.
server is initialized. The license manager monitors
Explanation: The REPAIR BACKUPSET command license compliance.
completed after successfully repairing the retention
initiation date for the indicated number of backup sets.
System action: The command completed.
ANR2804W Insufficient memory is available for the
license manager - will retry in number of
ANR2797E The license value was skipped because seconds seconds.
of a bad date range.
Explanation: The server suspends license manager
Explanation: One or more license values were skipped processing because sufficient server memory is not
due to the current system date not being valid for the available.
license. This message occurs when reading the
System action: Server operation continues; the license
nodelock file. This can occur during server start-up,
manager operation will be retried after the specified
license audit, or REGISTER LICENSE.
delay.
System action: Server operation fails.
User response: Verify the correct system date setting. operating system about how to increase memory for an
After you correct the system date, the licenses that are application.
registered with a quantity value will need to be
registered again.


ANR2805W Insufficient recovery log space available
full.
for the license manager - will retry in
number of seconds seconds. Alternatively, an out of log space condition might occur
processing because sufficient recovery log space is not
available.
System action: Server operation continues; the license necessary, specify a larger directory for the
manager operation will be retried after the specified ARCHIVELOGDIRECTORY or
delay. ARCHFAILOVERLOGDIRECTORY options in the
and file systems that are assigned to the ANR2808E Out of server database space in license
ACTIVELOGDIRECTORY, ARCHIVELOGDIRECTORY, manager.
transaction for the license manager because sufficient
full.
database update fails.
location that are no longer active and cannot be User response: To increase the amount of database
archived to the ARCHIVELOGDIRECTORY and space that is available to the server, issue the EXTEND
ARCHFAILOVERLOGDIRECTORY locations. If DBSPACE command to add one or more directories to
necessary, specify a larger directory for the the database.
dsmserv.opt file and then restart the server. ANR2812W License Audit completed - ATTENTION:
Server is NOT in compliance with
license terms.
ANR2806W Insufficient database space available for
the license manager - will retry in Explanation: The results from the AUDIT LICENSES
number of seconds seconds. command indicate the server is not in compliance with
the terms of the current license.
processing because sufficient database space is not System action: Server operation continues, but the
available. REGISTER NODE command or backup-archive
requests, or both, will fail.
System action: Server operation continues; the license
manager operation will be retried after the specified User response: Use the QUERY LICENSE command to
delay. determine the license terms that are no longer in
compliance.
DBSPACE command to add one or more directories to ANR2815E Command: Invalid value specified for
the database. interval between license audits - value.
ANR2807E Out of server log space in license with an invalid value.
manager. System action: Server operation continues, but the
Explanation: The server ends a database update command is not processed.
transaction for the license manager because sufficient User response: Issue the command with a valid value.
recovery log space is not available on the server.
System action: Server operation continues, but the ANR2816E Command: License audit or register
database update fails. operation already in progress.
User response: To increase the amount of log space Explanation: The server is currently performing a
that is available to the server, evaluate the directories register license or license audit.
ACTIVELOGDIRECTORY, ARCHIVELOGDIRECTORY, System action: The server does not process the
and ARCHFAILOVERLOGDIRECTORY options in the specified command.
dsmserv.opt file. An out of log space condition might User response: Reissue the command after the license

audit process or the register license command ends.

Only one REGISTER LICENSE command or AUDIT
LICENSE process can be running at a time. The Explanation: The license audit operation has been
REGISTER LICENSE command and the AUDIT cancelled and will end when resources have been freed
LICENSE process may not run at the same time. for the background process. This message may be
displayed in response to a QUERY PROCESS command
for an AUDIT LICENSES operation.
ANR2817I Command: License audit started as
process process ID. System action: Server operation continues.
Explanation: A background process has been started User response: None.
to audit the server for license compliance.
System action: The server checks the existing ANR2823I Have audited number of nodes nodes
configuration for the server and compares it against the
Explanation: An AUDIT LICENSES operation is in
values for which the server is licensed.
progress. The process has audited the specified number
User response: The administrator may query the of nodes. This message may be displayed in response
status of the background process by using the QUERY to a QUERY PROCESS command for an AUDIT
PROCESS command, or cancel the process with the LICENSES operation.
ANR2818E A consistency check failed on container
Container Name with error Error Code.
ANR2824I License audit process process number
Explanation: A data integrity problem was found in
canceled - number of nodes nodes audited.
the storage pool.
Explanation: A background server process to audit
System action: The server checks the data as part of
server licenses has been canceled by using the
normal operation and encountered a data integrity
CANCEL PROCESS command. The number of nodes
problem.
that have been audited before the operation ended are
User response: Issue the REPAIR STGPOOL command reported in the message.
to repair the data or recover the data from a recovery
server.
ANR2820I Automatic license audit started as
process process ID.
ANR2825I License audit process process number
Explanation: A background process has been started
completed successfully - number of nodes
to audit the server for license compliance.
nodes audited.
System action: The server checks storage utilization
Explanation: A background server process to audit
and registered nodes for the server and licensed factors,
server licenses has completed successfully after
comparing these against the values for which the server
auditing the specified number of nodes.
is licensed.
status of the background process using the QUERY
PROCESS command. User response: None.
ANR2821E Automatic license audit could not be ANR2826I License audit process process number
started: diagcode. terminated in error - number of nodes
nodes audited.
Explanation: The license manager cannot start an
automatic process to audit server licenses because Explanation: A background server process to audit
sufficient memory is not available. Diagnostic code server licenses encounters an error and is ended. The
diagcode is issued. number of nodes that have been audited before the
operation ended is reported in the message.
application. User response: None.

ANR2827I Server is licensed to support feature name ANR2835I Server is licensed for number of clients
for a quantity of licensed quantity. clients.
Explanation: This message is issued during server Explanation: This message is issued during server
startup. startup and in one hour increments there after.
ANR2828I Server is licensed to support feature ANR2839I Automatic license audit started as
name. process process ID.
Explanation: This message is issued during server Explanation: A background process has been started
startup. to audit the server for license compliance.
System action: Server operation continues. System action: The server checks registered nodes and
compares them against the value for which the server
is licensed.
ANR2829E Command: parameter - parameter is not
status of the background process by using the QUERY
allowed.
PROCESS command.
Explanation: The UPDATE NODE command has been
entered with a parameter that is not allowed.
ANR2841W Server is NOT IN COMPLIANCE with
System action: The server ignores the command. license terms.
User response: When updating the REPLMODE and Explanation: This message is issued periodically when
REPLSTATE parameters on a node definition, there are the server configuration does not comply with the
restrictions that prohibit changing certain values. terms for which it is licensed.
Several conditions are enforced during command
processing that prevents unintended updates. The
syntax processing is strictly enforced and in many User response: Use the QUERY LICENSE command to
cases, it might be necessary to issue other commands display the current server configuration with respect to
prior to using UPDATE NODE. licensed terms to discover which factors of the
configuration do not conform to your license. Contact
For information about the UPDATE NODE command,
your service representative to obtain more licenses, if
search for "UPDATE NODE" in the product information
required.
SSEQVQ/).
ANR2842I Server is licensed to support number of
gigabytes gigabytes of storage.
ANR2832I Command: The License Manager has not
yet completed initialization - please Explanation: This message is issued during server
retry this command later. startup.
Explanation: While attempting to process the specified System action: Server operation continues.
license command, the server detects that the licensing
component of the server had not completed
initialization. The licensing facility used on some
platforms may require some time to initialize because ANR2843I Server is licensed to support UNIX
network calls are involved, and waits may occur. clients.
System action: Server operation continues; the Explanation: This message is issued during server
command is not processed. startup.
User response: Reissue the command after waiting 10 System action: Server operation continues.
minutes. If this message is displayed after a number of
retry attempts, contact your service representative. User response: None. UNIX is a registered trademark
in the United States and other countries, licensed
exclusively through X/Open Company Limited.

ANR2844I Server is licensed to support desktop ANR2854I Server is licensed for device support
clients. module module number.
Explanation: This message is issued during server Explanation: This message may be issued during
startup and in one hour increments there after. server startup.
ANR2847W The addition of client client node name is ANR2855W The UPDATE STGPOOLDIRECTORY
beyond the client capacity that the command marks as destroyed all of the
server is licensed to support. data that is stored in the container
storage pool pool name in the storage
Explanation: This message is issued when a new
pool directory directory name.
client node is added to the server with the REGISTER
NODE command, or through open registration, and the Explanation: An update stgpooldir command has
actual number of nodes registered on the server been entered that will change the access of the
exceeds the server's licensed capacity. stgpooldir to destroyed. This will mark all of the
associated storage as needing recovery.
User response: This message is issued as a reminder
continue.
to the administrator that the server is not operating
within compliance of its license. Contact your service User response: Enter 'Y' to continue with the
representative if more licenses are required for your command or 'N' to end the process.
server.
ANR2859I Server is licensed for Secondary Server
ANR2852I Current license information: Attachment.
Explanation: This message is issued during a Explanation: This message may be issued during
REGISTER LICENSE command to display the current server startup.
licensing information for the server before the new
license has been interpreted by the command. Messages
appearing after this message display the factors under User response: None.
which the server is currently licensed.
System action: Server operation continues. ANR2860I Server is licensed to support disaster
recovery manager.
Explanation: This message is issued during server
startup.
ANR2853I New license information:
Explanation: This message is issued during a
REGISTER LICENSE command to display the updated User response: None.
licensing information for the server after the new
license has been interpreted by the command. Messages
appearing after this message display the updated ANR2861I Server is licensed to support
factors under which the server is licensed. NETWORK connections.
System action: Server operation continues. Explanation: This message is issued during server
startup.
User response: Check to make sure that the new
license information includes the updates that you System action: Server operation continues.
intended for the REGISTER LICENSE command. If the User response: None.
license terms do not change, check the parameters and
reissue the command, if you find that it was not
entered correctly. If the REGISTER LICENSE command ANR2863I Server is licensed to support Enterprise
does not produce the desired updates in terms of Administration functions.
licensing, contact your service representative. Explanation: This message is issued during server
startup.

SQL query processing, but does not terminate query

ANR2864I Server is licensed to support
processing.
Server-to-Server Virtual Volumes.
Explanation: This message is issued during server
startup.
ANR2901W The result of character string
concatenation was truncated.
Explanation: Truncation occurred when the
concatenation of character strings resulted in a length
ANR2865W The server is NOT licensed to support that exceeds the maximum character string length (250
Enterprise Administration functions. By for data type CHAR, and 2000 for data type
performing this action you are no longer VARCHAR).
in compliance with license terms.
System action: This warning can occur before or after
Explanation: This message is issued when enterprise SQL query processing, but does not terminate query
administration functions are used, but the server is processing.
NOT licensed to support the functions.
User response: To bring your installation back into ANR2902E Insufficient memory was available to
conformance with license terms, obtain a license for process the SQL statement.
enterprise administration functions or remove central
Explanation: Sufficient memory was not available to
logging definitions. Contact your service representative
complete the processing of an SQL query.
if you have any questions or concerns with this
message. System action: The SQL query is terminated.
ANR2868E The server is NOT licensed to support
Enterprise Administration functions.
ANR2903E An SQL parser stack overflow occurred
Explanation: This message is issued when Enterprise while processing token 'token'.
Administration functions are used, but the server is
NOT licensed to support the functions. Explanation: The internal stack used by the SQL
query parser has overflowed. This typically occurs
System action: The command fails. when too many column names or expressions have
been specified in the SELECT clause.
User response: Contact your service representative if
you want to obtain a license for enterprise System action: The SQL query is terminated.
administration.
ANR2899E Command: Operation is not valid for

storage pool type storage pool storage pool ANR2904E Unexpected SQL key word token -
name. 'token'.
Explanation: The command indicated specifies a Explanation: A syntax error occurred because an SQL
volume in a storage pool which is not valid for the key word was found that can not legally be used at the
command. specified position within the SQL statement. Examples
of SQL key words are SELECT, FROM, and WHERE.
command. System action: The SQL query is terminated.
User response: Reissue the command with a volume User response: None.
in a valid storage pool.
ANR2905E Unexpected SQL identifier token -
ANR2900W The character string 'string' was 'token'.
truncated during assignment. Explanation: A syntax error occurred because an SQL
Explanation: Truncation occurred during assignment identifier was found that can not legally be used at the
of an SQL character string. For example, the expression specified position within the SQL statement. Examples
CAST( 'Hello' AS CHAR(2) ) will result in truncation of SQL identifiers are table names and column names.
because the string 'Hello' (length 5) can not fit in the System action: The SQL query is terminated.
target type CHAR(2) without loss of trailing characters.
System action: This warning can occur before or after

System action: The SQL query is terminated.

ANR2906E Unexpected SQL literal token - 'token'.
Explanation: A syntax error occurred because an SQL
literal token was found that can not legally be used at
the specified position within the SQL statement. ANR2912E Invalid character string literal token -
Examples of SQL literal tokens are 'abc', 1.567, and 'token'.
DATE '1/1/96'.
Explanation: An invalid SQL character string literal
System action: The SQL query is terminated. token was found. For example, the hexadecimal literal
X'78FG' is not valid because it contains the character
'G'.
ANR2907E Unexpected SQL operator token - 'token'.
operator token was found that can not legally be used
at the specified position within the SQL statement. ANR2913E Invalid SQL identifier token - 'token'.
Examples of SQL operator tokens are +, *, <, and =.
Explanation: An invalid SQL identifier token was
System action: The SQL query is terminated. found. For example, the character sequence "ABC.123"
is not a valid identifier because the second part of the
identifier, "123", does not begin with a letter.
ANR2908E Unexpected SQL punctuation token -
'token'. User response: None.
punctuation token was found that can not legally be ANR2914E SQL identifier token 'token' is too long;
used at the specified position within the SQL statement. name or component exceeds 18
Examples of SQL punctuation tokens are the period, characters.
the comma, and the parenthesis.
Explanation: An SQL identifier token was found that
System action: The SQL query is terminated. exceeds the maximum length of 18 characters per
component.
ANR2909E The SQL statement is incomplete; User response: None.
additional tokens are required.
Explanation: A syntax error occurred because, ANR2915E The SQL token beginning with 'token' is
although the syntax of the SQL query expression was missing an ending delimiter.
correct up to the end of the string, the parser expected
additional tokens in order to form a Explanation: An SQL token was found that is missing
syntactically-correct SQL statement. its ending delimiter. For example, each of the tokens
'abc, "abc, and X'abc is missing its ending delimiter.
ANR2910E Invalid SQL token - 'token'.

ANR2916E The SQL data types data type and data
Explanation: An invalid SQL token was found. For type are incompatible for operator
example, the token formed by the character sequence 'operator'.
"::!" is not a valid SQL token.
Explanation: The data types of the operands are not
System action: The SQL query is terminated. compatible when used with the specified operator. For
example, the expression 3 + 'abc' is not valid because
the operand data types INTEGER and CHAR(3) are not
compatible for the addition operator "+".
ANR2911E Invalid SQL numeric literal token -
'token'.
Explanation: An invalid SQL numeric literal token
was found. For example, the floating point literal
"1.456E" is not valid.

Explanation: An SQL expression was expected of one

ANR2917E The SQL data type of expression
of the types DATE, TIMESTAMP, CHAR, VARCHAR,
'expression' is data type; expecting an
or INTERVAL as the operand to the EXTRACT
integer expression.
function. In the case of CHAR or VARCHAR, the
Explanation: An SQL expression of data type expression must be a valid character string
SMALLINT, INTEGER, or DECIMAL with scale zero is representation of a date or a timestamp.
expected.
ANR2918E The SQL data type of expression 'expression' is data type; expecting a time,
'expression' is data type; expecting a timestamp, character string time,
Boolean expression. character string timestamp, or interval
expression.
Explanation: An SQL expression of data type
BOOLEAN is expected. Explanation: An SQL expression was expected of one
of the types TIME, TIMESTAMP, CHAR, VARCHAR, or
INTERVAL as the operand to the EXTRACT function.
User response: None. In the case of CHAR or VARCHAR, the expression
must be a valid character string representation of a
time or a timestamp.
'expression' is data type; expecting a System action: The SQL query is terminated.
numeric expression.
Explanation: An SQL expression of numeric data type
SMALLINT, INTEGER, DECIMAL, NUMERIC, REAL,
FLOAT, or DOUBLE_PRECISION is expected.
'expression' is data type; expecting a date
System action: The SQL query is terminated. or character string date expression.
User response: None. Explanation: An SQL expression was expected of one
of the types DATE, CHAR, or VARCHAR. In the case
of CHAR or VARCHAR, the expression must be a valid
ANR2920E The SQL data type of expression character string representation of a date.
'expression' is data type; expecting a
numeric or interval expression. System action: The SQL query is terminated.
Explanation: An SQL expression of numeric data type User response: None.
(SMALLINT, INTEGER, DECIMAL, NUMERIC, REAL,
FLOAT, DOUBLE) or of interval data type (INTERVAL)
is expected.
'expression' is data type; expecting a time
System action: The SQL query is terminated. or character string time expression.
User response: None. Explanation: An SQL expression was expected of one

of the types TIME, CHAR, or VARCHAR. In the case of
CHAR or VARCHAR, the expression must be a valid
ANR2921E The SQL data type of expression character string representation of a time.
'expression' is data type; expecting a
character string expression. System action: The SQL query is terminated.
Explanation: An SQL expression of character string User response: None.
type CHAR or VARCHAR is expected.
System action: The SQL query is terminated. ANR2926E The SQL data type of expression
'expression' is data type; expecting a date,
User response: None. timestamp, character string date, or
character string timestamp expression.
ANR2922E The SQL data type of expression Explanation: An SQL expression was expected of one
'expression' is data type; expecting a date, of the types DATE, TIMESTAMP, CHAR, or
timestamp, character string date, VARCHAR. In the case of CHAR or VARCHAR, the
character string timestamp, or interval expression must be a valid character string
expression. representation of a date or a timestamp.


ANR2931E A subquery expression may not contain
User response: None. a reference to a column name that is
contained in an outer query expression.
ANR2927E The SQL data type of expression Explanation: A subquery contains a reference to a
'expression' is data type; expecting an column name in an outer query expression.
interval containing a single date-time
field.
Explanation: An SQL expression was expected of data
type INTERVAL YEAR, INTERVAL MONTH,
INTERVAL DAY, INTERVAL HOUR, INTERVAL ANR2932E The maximum nesting depth for
MINUTE, or INTERVAL SECOND, all of which contain subquery expressions has been
a single date-time field. Multi-field interval types (for exceeded.
example, INTERVAL DAY TO SECOND) are not
Explanation: Too many nested subqueries were
allowed.
specified.
ANR2928E A number can not be converted to SQL

ANR2933E The WHERE clause must not contain an
data type INTERVAL if the interval
aggregate function.
contains multiple date-time fields.
Explanation: The use of the aggregate functions
Explanation: An attempt was made to convert a
COUNT, MAX, MIN, SUM, AVG, VARIANCE, or
number to the data type INTERVAL, but the target
STDDEV in the WHERE clause is not allowed.
interval contains multiple date-time fields (for example,
INTERVAL DAY TO SECOND). Only the single-field System action: The SQL query is terminated.
interval types INTERVAL YEAR, INTERVAL MONTH,
INTERVAL DAY, INTERVAL HOUR, INTERVAL User response: None.
MINUTE, or INTERVAL SECOND can be specified.
System action: The SQL query is terminated. ANR2934E The result data type of a CASE
expression can not be determined; at
User response: None. least one non-null THEN or ELSE
expression must be specified.
ANR2929E The expression 'expression' is not an Explanation: The result data type of a CASE
integer constant. expression can not be determined because all of the
THEN expressions and the ELSE expression (if present)
Explanation: An integer constant such as 1 or -9 is
specifies the NULL key word.
expected. For example, the DECIMAL function requires
that the precision and scale operands be integer System action: The SQL query is terminated.
constants. A decimal constant such as 1.67 is not valid.
User response: None. ANR2935E The date-time field field is not present in
the expression 'expression' (data type data
type).
ANR2930E A subquery used in an SQL expression
must specify a single result column. Explanation: The specified date-time field (YEAR,
MONTH, DAY, HOUR, MINUTE, or SECOND) is not
Explanation: A subquery used in an expression can
contained in the data type of the expression.
not specify multiple result columns. For example, the
expression X > (select A,B from T) is invalid because it System action: The SQL query is terminated.
specifies two result columns (A and B).
User response: None. ANR2936E The SQL aggregate function function can
not be nested within another aggregate
function.
Explanation: One of the aggregate functions COUNT,
MAX, MIN, SUM, AVG, VARIANCE, or STDDEV was

found nested within another aggregate expression.

ANR2941E The column reference 'column reference'
System action: The SQL query is terminated. matches more than one SQL column
name.
Explanation: The specified column reference is
ambiguous because it matches the columns associated
ANR2937E An SQL subquery expression can not be with multiple tables.
nested within an aggregate function.
Explanation: An expression containing a subquery
was found nested within one of the aggregate functions User response: None.
STDDEV.
ANR2942E The column reference 'column reference' is
System action: The SQL query is terminated. not allowed in this context because it is
part of an outer SQL query expression.
Explanation: The specified column reference is not
allowed because it names a columns of some outer
ANR2938E The column 'column' is not allowed in query expression. Such references are not allowed when
this context; it must either be named in contained within the expressions of the HAVING and
the GROUP BY clause or be nested SELECT clauses.
within an aggregate function.
Explanation: A column reference was specified that is
neither a column specified in a GROUP BY clause nor User response: None.
is a column nested in one of the aggregate functions
ANR2943E The column reference 'column reference' is
STDDEV. The use of the column reference is prohibited
a duplicate of another SQL column
because either 1) the GROUP BY clause has been
name in the same list.
specified, 2) the HAVING clause has been specified, or
3) at least one aggregate function is present. Explanation: A duplicate column reference was
specified within the same GROUP BY or ORDER BY
list of columns.
ANR2939E The reference 'reference' contains an
unknown SQL table name.
ANR2944E The reference 'reference' is an unknown
Explanation: A table name in the SQL command is not
SQL scalar function name.
one of the base tables defined by the server's database.
The rows of the table SYSCAT.TABLES can be selected Explanation: The specified function reference is not
to obtain a list of all of the valid base tables. the name of a valid scalar function.
System action: The SQL query is terminated. System action: The SQL query is terminated.
User response: Retry the command using a table that User response: None.
is defined by the IBM Spectrum Protect server
database.
ANR2945E Too few arguments are specified for
SQL scalar function function.
ANR2940E The command 'reference' contains an
Explanation: Too few function arguments were
unknown SQL column name.
specified. For example, the expression LEFT(x) is
Explanation: A column name in the SQL command is invalid because the LEFT function requires at least two
not one of the base table columns defined by the arguments.
server's database. The rows of the table
SYSCAT.COLUMNS can be selected to obtain a list of
all of the valid base table columns. If a two-part User response: None.
(compound) column reference such as X.Y is specified,
then the correlation name X must be one of the active
correlation names for the query.


ANR2946E Too many arguments are specified for
SQL scalar function function.
ANR2950E Arithmetic or date-time overflow
Explanation: Too many function arguments were
occurred for SQL operator 'operator' for
specified. For example, the expression UPPER(x,y) is
values 'value' (data type data type) and
invalid because the UPPER function requires exactly
'value' (data type data type).
one argument.
Explanation: An arithmetic or date-time overflow
occurred for the specified operator. The values that
User response: None. caused the overflow (and their SQL data types) are
displayed.
ANR2947E Division by zero was detected for System action: The SQL query is terminated.
operator 'operator'.
Explanation: An attempt to divide by the number zero
was detected for the specified SQL operator. The most
ANR2951E The value 'value' (data type data type) is
likely cause of the problem is that one of the values of
not a valid argument for operator
a column is zero, and that column is used in the
'operator'.
denominator of a division operation. To protect against
this case the NULLIF function can be used. For Explanation: An invalid value was specified as an
example, instead of the expression 1/X, specify argument to an SQL operator. For example, the
1/NULLIF(X,0), which will set the expression to null expression SQRT(-1) is not valid because the argument
whenever the value if X is zero. to the SQRT function is negative.
ANR2948E The value 'value' can not be assigned or ANR2952E The value 'value' (data type data type) is
converted to SQL data type data type. not a valid character string
representation of an SQL date or a
Explanation: A value could not assigned or converted
timestamp for operator 'operator'.
to a value in the specified SQL data type because either
1) the data type of the value can not be legally cast to Explanation: An invalid character string
the target data type (for example, data type TIME can representation of a DATE or TIMESTAMP was
not be converted to data type INTEGER); 2) the specified. For example, the string 'abc' is neither a valid
assignment of the value results in overflow in the date nor a timestamp.
target data type (for example, the decimal value
12345678.34 can not be assigned to data type System action: The SQL query is terminated.
DECIMAL(3,2) because the precision of the target type User response: None.
is exceeded); or 3) the syntax of a character string value
is not appropriate for the target data type (for example,
the string 'abc' can not be converted to data type ANR2953E The value 'value' (data type data type) is
DATE). not a valid character string
representation of an SQL time or a
System action: The SQL query is terminated. timestamp for operator 'operator'.
User response: None. Explanation: An invalid character string
representation of a TIME or TIMESTAMP was
ANR2949E Arithmetic overflow occurred for SQL specified. For example, the string 'g pm' is neither a
operator 'operator'. valid time nor a timestamp.
Explanation: An arithmetic overflow occurred for the System action: The SQL query is terminated.
specified operator. Examples of this include: 1) the User response: None.
application of the unary negation operator to the
smallest INTEGER value (-2147483648) causes overflow
because the result can not be represented in 2's ANR2954E An SQL subquery used in a scalar
complement; 2) the sum of the set of INTEGER column expression must yield a table that
values applied to the SUM aggregate function can not contains at most one row.
be represented within the precision of INTEGER type. Explanation: This error results when a subquery used
System action: The SQL query is terminated. in a scalar expression returns multiple rows, thereby

making it ambiguous as to which value should be and the DISTINCT operator can cause additional
returned. temporary table space to be required.
User response: Respecify the subquery (for example, User response: If your database is full, increase the
using the WHERE clause) so that the subquery returns size of the database. If your database is fragmented
at most one row. (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 add
ANR2955E The SQL character string expression
avolume.
'expression' must return a single
character.
ANR2959E SQL temporary table row is too wide.
Explanation: A single-character character string was
expected for the ESCAPE clause of the LIKE operator, Explanation: A row could not be inserted into an SQL
for the trim character of the TRIM operator, or for the temporary table because the row is too wide. This can
pad character of the LEFT or RIGHT function. For occur if 1) there are too many columns in the row being
example, the string 'Hello' is invalid because it contains inserted, or 2) the sum of the lengths of the columns in
multiple characters. the row is too wide. Temporary tables are used when 1)
the ORDER BY clause is specified; 2) the GROUP BY
clause is specified; or 3) the DISTINCT operator is
User response: None. specified.
ANR2956E Unable to access SQL base table 'table'.
User response: Reduce the number of columns
Explanation: An error occurred when attempting to specified in the ORDER BY and/or GROUP BY clauses.
read rows from one of the SQL base tables. This
message is typically preceded by another error
ANR2960E Unexpected SQL enumerated type name
describing the condition.
token - 'token'.
User response: None. enumerated type name was found that can not legally
be used at the specified position within the SQL
statement. A list of all of the enumerated types declared
ANR2957E An error occurred inserting a row in an by the server can be found in the SQL catalog table
SQL temporary table. The server SYSCAT.ENUMTYPES.
database size may need to be increased
Explanation: An error occurred when attempting to
insert a row into a temporary table being used for an User response: None.
SQL query. This message is typically preceded by
another error describing the condition. In many cases
ANR2961E Invalid SQL enumerated type name -
this error can be resolved by increasing the size of the
'name'.
server database. Free space in the database is used to
store temporary tables created during the execution of Explanation: A syntax error occurred because an SQL
an SQL SELECT query. enumerated type name was expected, but the specified
name is not one of the declared enumerated types. For
example, the literal expression XXX::YYYY is illegal
User response: None. because XXX is not a valid enumerated type name. A
list of all of the enumerated types declared by the
server can be found in the SQL catalog table
ANR2958E SQL temporary table storage has been SYSCAT.ENUMTYPES.
exhausted.
Explanation: The result of an SQL query could not be
computed because temporary table storage space was User response: None.
unavailable. By issuing the QUERY DB command and
viewing the Maximum Reduction parameter, you can
ANR2962E Unable to resolve SQL enumerated type
determine the amount of space that is available for
for value 'value'.
temporary table storage space. If the parameter is less
than 4, the storage space becomes exhausted and the Explanation: A syntax error occurred because an
SQL query can no longer run. Complex SQL queries unqualified SQL enumerated value name was specified,
such as the ORDER BY clause, the GROUP BY clause, but, because that value name is a member of more than

one enumerated type, its type could not be resolved. during the execution of the named command or
For example, the enumerated value name YES belongs process.
to more than one enumerated type, and so the result
System action: The named command or process is
type of the expression YES = YES can not be resolved.
terminated.
A list of all of the enumerated types declared by the
server can be found in the SQL catalog table User response: Extend the server database (after
SYSCAT.ENUMTYPES. adding database volumes if necessary) and rerun the
commmand or process.
ANR2968E Database backup terminated. DB2
sqlcode: sqlcode. DB2 sqlerrmc: sqlerrmc.
ANR2963W This SQL query may produce a very
Explanation: DB2 detected a problem during the
large result table, or may require a
backup operation. Sources of the problem might
significant amount of time to compute.
include:
Explanation: An SQL query has been posed that could 1. IBM Spectrum Protect API configuration errors for
potentially cause a very large number of rows to be the DB2 instance in which the IBM Spectrum
returned and displayed, or may involve a large amount Protect server database resides.
of processing time before the first result table row can
2. An error related to the DB2 backup operation.
be generated.
3. Errors related to the target backup device.
continue. System action: The database backup is terminated.
User response: Enter 'Y' to continue with SQL query User response: If the message indicates DB2 sqlcode
processing or 'N' to terminate the query. 2033, then the problem is probably the IBM Spectrum
Protect API configuration. The DB2 instance uses the
IBM Spectrum Protect API to copy the IBM Spectrum
ANR2964E The reference 'reference' is not a column Protect database-backup image to the IBM Spectrum
of the SQL result table. Protect server-attached storage devices. Common
Explanation: The ORDER BY clause specified a sqlerrmc codes include:
column that is not part of the result table for the SQL 1. 50 - To determine whether an error created the API
query. Only those columns named in the select list are timeout condition, look for any IBM Spectrum
part of the result table. Protect server messages that occurred during the
database-backup process and that were issued
before ANR2968E. Ensure that the IBM Spectrum
User response: None. Protect API options file has the correct
TCPSERVERADDR and TCPPORT options specified
for the IBM Spectrum Protect server being backed
ANR2965E An SQL temporary table cannot be up. If the option settings are wrong, correct them
built. required columns columns are for the DB2 instance.
needed. maximum columns is the
maximum. 2. 53 - Ensure that the NODENAME option in the
IBM Spectrum Protect API options files is set to
Explanation: A temporary table required columns wide $$_TSMDBMGR_$$. Also verify the
is needed to complete processing for an SQL query. The TCPSERVERADDRESS setting. If the keyword
maximum degree of an SQL table is maximum columns. "localhost" is being used verify that this is being
The table will not be created. resolved correctly by issuing the command "ping
localhost" from a system command window. If the
ping of localhost fails, consider changing the
User response: If the ORDER BY and/or GROUP BY TCPSERVERADDRESS to the explicit loopback
clauses were specified, reduce the number of columns address of 127.0.0.1. As an alternative to setting the
needed for the result table. explicit loopback address of 127.0.0.1, verify the
TCP/IP configuration and whether or not
"localhost" is configured correctly. For example, for
ANR2966E Command/process: Database temporary
Unix or Linux systems, verify that /etc/hosts has
table storage has been exhausted.
an appropriate entry for "localhost".
Explanation: The named command or operation could 3. 106 - Ensure that the DB2 Instance DSMI_DIR
not be completed because insufficient temporary table environment variable is pointing to the location of
storage space was available. Free space in the server the IBM Spectrum Protect API executables and the
database is used to store temporary tables created

ANR2969E
dsm.sys configuration file. If the DSMI_DIR setting backup DB process and that were issued before
is wrong, correct it for the DB2 instance, and then ANR2969E. Ensure that the IBM Spectrum Protect
restart the DB2 instance. API options file has the correct TCPSERVERADDR
4. 137 - Ensure that the DB2-instance DSMAPIPW and TCPPORT options specified for the IBM
command was run and that it specified nodename Spectrum Protect server being backed up. If the
$$_TSMDBMGR_$$ and the password TSMDBMGR. option settings are wrong, correct them for the DB2
instance.
5. 400 - Ensure that the options specified in the IBM
Spectrum Protect API options file are valid. 2. 53 - Ensure that the NODENAME option in the
IBM Spectrum Protect API options files is set to
6. 406 - Ensure that the DB2 instance owner has at
$$_TSMDBMGR_$$.
least read access to the IBM Spectrum Protect API
options file. Ensure that the DB2-instance 3. 106 - Ensure that the DB2-instance DSMI_DIR
DSMI_CONFIG environment variable is pointing to environment variable is pointing to the location of
a valid options file for the IBM Spectrum Protect the IBM Spectrum Protect API executables and the
API. If the DSMI_CONFIG setting is wrong, correct dsm.sys configuration file. Ensure that you have the
it for the DB2 instance, and then restart the DB2 correct permissions to access these locations. If the
instance. DSMI_DIR setting is wrong, correct it for the DB2
instance, and then restart the DB2 instance.
7. 450,451 - Ensure that the server options file and the
IBM Spectrum Protect API options file both contain 4. 137 - Ensure that the DB2-instance DSMAPIPW
the COMMMETHOD SHAREDMEM option. Ensure command was run and that it specified the
that the values for the SHMPORT option in each nodename $$_TSMDBMGR_$$ and the password
options file correspond. Restart the server if you TSMDBMGR.
change any values in the server options file. 5. 400 - Ensure that the options specified in the IBM
8. For descriptions of other sqlerrmc values, look in Spectrum Protect API options file are valid.
the dsmrc.h file that is installed with the IBM 6. 406 - Ensure that the DB2 instance owner has at
Spectrum Protect API. least read access to the IBM Spectrum Protect API
options file. Ensure that the DB2 Instance
If this message is issued with a DB2 sqlcode that is not DSMI_CONFIG environment variable is pointing to
2033, then look for more information about the error by a valid options file for the IBM Spectrum Protect
opening a DB2 command-line processor window and API. If the DSMI_CONFIG setting is wrong, correct
typing: ? SQLsqlcode. For example, db2 => ? sql2428 it for the DB2 instance, and then restart the DB2
instance.
ANR2969E Database restore terminated. DB2 7. 450,451 - Ensure that the server options file and the
sqlcode: sqlcode. DB2 sqlerrmc: sqlerrmc. IBM Spectrum Protect API options file both contain
the COMMMETHOD SHAREDMEM option. Ensure
Explanation: DB2 detected a problem during the that the values for the SHMPORT option in each
restore operation. Sources of the problem might options file correspond. Restart the server if you
include: change any values in the server options file.
1. IBM Spectrum Protect API configuration errors for 8. For descriptions of other sqlerrmc values, look in
the DB2 instance in which the IBM Spectrum the dsmrc.h file that is installed with the IBM
Protect server database resides. Spectrum Protect API.
2. Errors related to the DB2 restore operation.
3. Errors related to the target backup device. If the message indicates DB2 sqlcode 2542, then the
problem is probably because IBM Spectrum Protect API
4. The IBM Spectrum Protect API client configuration version for database restore is not the same API version
used by the current instance is not able to access the for database backup. Check IBM Spectrum Protect API
backup image. version:
System action: The database restore operation is 1. AIX - /bin/sh -c "lslpp -lcq
terminated. tivoli.tsm.client.api.64bit"
User response: If the message indicates DB2 sqlcode 2. Solaris - /bin/sh -c "cat /var/sadm/pkg/
2033, then the problem is most likely the IBM Spectrum TIVsmCapi/pkginfo | grep VERSION
Protect API configuration. The DB2 instance uses the 3. HP- /bin/sh -c "cat /var/adm/sw/products/
IBM Spectrum Protect API to copy the IBM Spectrum TIVsm64/CLIENT_API64/INDEX| grep ^revision
Protect database restore image from the IBM Spectrum 4. Linux - rpm -q TIVsm-API64-* --qf
Protect server-attached storage devices to DB2. %{VERSION}.%{RELEASE}\\n
Common sqlerrmc codes include:
5. Windows - reg query "HKEY_LOCAL_MACHINE\
1. 50 - To determine whether an error created the API SOFTWARE\IBM\ADSM\CurrentVersion\Api"
timeout condition, look for any IBM Spectrum
Protect server messages that occurred during the

If this message is issued with a DB2 sqlcode that is not

ANR2974I Offline DB backup for database DB
2033 or 2542, then look for more information about the
Alias completed successfully.
error by opening a DB2 command-line processor
window and typing: ? SQLsqlcode. For example, db2 Explanation: Offline DB backup completed
=> ? sql2428 successfully.
ANR2970E Database rollforward terminated - DB2
sqlcode sqlcode sqlerrmc sqlerrmc
Explanation: There is a problem detected by DB2.
ANR2975E Offline DB backup for database DB
System action: The database rollforward is Alias failed with sqlcode sqlcode and
terminated. sqlerrmc sqlerrmc.
User response: More information about the error is Explanation: The Offline Database backup failed.
available by opening a DB2 command-line processor
System action:
window and typing: ? SQLsqlcode. For example, db2
=> ? sql2428 User response:
ANR2971E Database backup/restore/rollforward ANR2976I Offline DB backup for database DB

terminated - DB2 sqlcode sqlcode error. Alias started.
Explanation: There is a problem detected by DB2. Explanation: Offline DB backup started.
System action: The database backup/restore/ System action: None.
rollforward is terminated.
User response: More information about the error is
available by opening a DB2 command-line processor
window and typing: ? SQLsqlcode. For example, db2 ANR2977E Command: The command failed because
=> ? sql2428 of an issue in the device configuration
file.
ANR2972E Restore DB Command: Database Explanation: The device configuration file includes
restore/rollforward terminated - Not one or more invalid values.
able to clean up log directory directory System action: The server ends the current operation.
name.
User response: Correct the issue in the device
Explanation: IBM Spectrum Protect tried to clean up configuration file and run the command again.
this log directory before PIT restore DB and not able to.
System action: The database restore/rollforward is ANR2978E Command: Invalid directory name -
terminated. directory name.
User response: Please clean up this directory Explanation: Restore DB failed due to invalid target
manually before performing DB PIT restore. directory name in device target directory file.
ANR2973E Restore DB Command: Database
restore/rollforward terminated - Log User response: Correct the problem in target directory
directory is required and does not exist file and retry.
directory name.
Explanation: The log direcotry is required and it does ANR2979E Internal error - Control descriptor is
not exist. PIT restore DB is terminated. NULL.
System action: The database restore/rollforward is Explanation: Something is wrong the control
terminated. descriptor is NULL.
User response: Create the specified directory and System action: None.
retry. User response: None.

environment or setup detected by DB2.

ANR2980E Database backup terminated TCPIP
failure - DB2 sqlcode sqlcode sqlerrmc System action: The database backup is terminated.
sqlerrmc.
User response: Ensure that the DSMI_CONFIG
Explanation: There is a TCPIP failure detected by environment variable points to a valid IBM Spectrum
DB2. Protect options file. Ensure that the instance owner has
read access to the dsm.opt file. Ensure that the
System action: The database backup is terminated.
DSMI_CONFIG environment variable is set in the
User response: Correct the TCPIP setup problem db2profile.
between IBM Spectrum Protect and DB2 and retry.
ANR2985E Database backup terminated due to I/O
ANR2981E Database backup terminated due to error related to TCPIP - DB2 sqlcode
environment or setup issue related to sqlcode sqlerrmc sqlerrmc.
file access - DB2 sqlcode sqlcode
Explanation: There is a TCPIP problem detected by
sqlerrmc sqlerrmc.
DB2 and caused the database backup to fail.
Explanation: There is a problem related to
User response: The possible TCPIP problem are
connection time out, connection refused, bad host name
User response: Ensure that you specified the correct or network unreachable. Correct the TCPIP problem
file or directory name, correct the permissions, or between IBM Spectrum Protect and DB2 and retry.
specify a new location and retry.
ANR2986E Database backup terminated due to I/O
ANR2982E Database backup terminated due to error - DB2 sqlcode sqlcode sqlerrmc
environment or setup issue related to sqlerrmc.
password - DB2 sqlcode sqlcode sqlerrmc
Explanation: There is a I/O problem detected by DB2
sqlerrmc.
and caused the database backup to fail.
User response: Correct the I/O problem between IBM
Spectrum Protect and DB2 and retry.
User response: If the IBM Spectrum Protect parameter
PASSWORDACCESS is set to GENERATE, ensure that
ANR2987W Session ended because of machine
the system administrator has used the dsmapipw utility
GUID or local host IP address
to set the password. If PASSWORDACCESS is set to
mismatch.
PROMPT, ensure that the TSM_NODENAME and
TSM_PASSWORD database configuration parameters Explanation: Backup or Restore DB commands are
have been set correctly. only allowed when the IBM Spectrum Protect database
being backed up or restored and the IBM Spectrum
Protect api and the IBM Spectrum Protect server are on
ANR2983E Database backup terminated due to
the same machine. Either the GUID of the IBM
environment or setup issue related to
Spectrum Protect api client in use by the database
DSMI_DIR - DB2 sqlcode sqlcode
manager does not match the GUID of the IBM
sqlerrmc sqlerrmc.
Spectrum Protect server or the local host IP address
Explanation: There is a problem related to indicated by the IBM Spectrum Protect client is not
environment or setup detected by DB2. accepted.
System action: The database backup is terminated. System action: The database backup or restore
operation is terminated.
User response: Ensure that DSMI_DIR points to a
directory containing the correct version of db2tca, User response: Default acceptable local host addresses
restart the instance, and execute the command again. are "127.0.0.1" for IPV4 and "::1" for IPV6. If you can
not configure one of these local host addresses on your
system then use the IBM Spectrum Protect server
ANR2984E Database backup terminated due to
option "DBMTRUSTEDIPADDR ipaddr" to set a local
environment or setup issue related to
host address that can be accepted.
DSMI_CONFIG - DB2 sqlcode sqlcode
sqlerrmc sqlerrmc.

Explanation: The ratio exceeds the threshold for

ANR2988W Attempt to add the last backup db
database space utilization.
volume used entry back in to the
volume history was unsuccessful. System action: System operations might be restricted
because of limited database space.
Explanation: Restore db operation was successful
however the attempt to add the last backup db volume User response: To increase the space for the database,
used back in to the volume history failed. use the EXTEND DBSPACE command.
System action: The database restore operation is
successful. Entry for last backup db volume used in the ANR2993E The database backup terminated with a
operation might be missing from volume history. log problem. DB2 sqlcode: sqlcode. DB2
sqlerrmc: sqlerrmc.
User response: Keep a copy of the volume history file
that was used to do the restore operation. After you Explanation: The database backup was terminated by
have verified the restore db operation do a backup db DB2 because one or more of the log files needed could
type=full. Manually track the volume that was not not be retrieved.
added back in to the volume history.
ANR2989E Database Database Name backup failed - User response: If the message did not indicate which
Missing volume history file. log directory path caused the problem, look in the
db2diag.log for additional information. Common
Explanation: Backup DB failed due to volume history problems are a missing directory or permission denied.
file is not defined in the dsmserv.opt.
System action: None. ANR2994E The automatic database backup was
terminated.
User response: Correct the problem in dsmserv.opt file
and retry. Explanation: The operation was terminated because
the device class that is used for the automatic database
backup is not defined.
ANR2990E Database restore is terminated due to an
invalid database path sqlerrmc and DB2 System action: The automatic database backup is
sqlcode sqlcode terminated.
Explanation: DB2 detected invalid database path. User response: Issue the SET DBRECOVERY
command to define the device class for the automatic
System action: The database restore is terminated.
database backup.
User response: Ensure the path exists and permissions
are correct and issue restore DB command again or
issue restore DB command again with ON parameter to
is used for the automatic database
specify a new valid database storage path.
backup.
Explanation: The DELETE DEVCLASS command was
ANR2991E The Incremental Database backup was
issued to delete a device class that is in use for the
terminated because a full database
automatic database backup.
backup is required - DB2 sqlcode sqlcode
sqlerrmc sqlerrmc. System action: The server does not process the
command.
Explanation: The Incremental Database backup was
terminated. A FULL database backup is required before User response: Issue the SET DBRECOVERY
an Incremental Database backup can be completed. command to define a new device class for automatic
database backup before deleting this device class.
System action: The incremental database backup is
terminated.
ANR2996I The server log is log full percentage
User response: Complete a FULL database backup
percent full. The server is no longer
first, then retry the incremental database backup.
delaying transactions.
Explanation: The server log utilization was
ANR2992W The database uses database space used
dangerously high and the server was delaying
megabytes of file-system space. The
transactions. The log utilization is now at a lower level
amount of available file-system space is
and the server is no longer delaying transactions.
database space available megabytes. The
ratio is database file system used ratio. System action: Server processing continues.
User response: Continue to monitor server activity

and log usage. If log usage is low enough, you may

ANR3004E Command: The configuration manager
consider reducing the amount of space allocated to the
name exceeds maximum length characters.
log.
Explanation: The configuration manager name
specified in the command is longer than the maximum
ANR2997W The server log is log full percentage
length allowed.
percent full. The server will delay
transactions by delay time milliseconds. System action: Server operation continues. The
Explanation: The server log utilization is very high. In
order to prevent the server log from becoming full, the User response: Select a configuration manager name
server will begin delaying transactions by the specified that does not exceed the maximum length.
amount of time.
System action: Server processing continues. ANR3005E Command: The server name exceeds
User response: Monitor server activity and log usage.
If possible, delay adding new work to the server load. Explanation: The configuration manager name
specified in the command is longer than the maximum
length allowed.
ANR3000E Command: Command can only be issued
on a configuration manager. System action: Server operation continues. The
Explanation: The command can only be issued on a
server that is a configuration manager. User response: Select a configuration manager name
that does not exceed the maximum length.
ANR3006E Command: The configuration refresh
User response: Issue this command from a
interval value must be between minimum
value and maximum value.
ANR3001E Command: Command can only be issued
with an invalid refresh interval.
on a managed server.
Explanation: The command can only be issued on a
managed server.
refresh interval value.
User response: Issue this command from a managed
ANR3007E Command: The option option must be
server.
specified.
Explanation: When the command is issued on a a
ANR3002E Command: Profile name exceeds maximum
server that is neither a configuration manager nor a
length characters.
managed server, the specified option must be supplied.
Explanation: The profile name specified in the
command is longer than the maximum length allowed.
specified option.
User response: Select a profile name that does not
exceed the maximum length.
ANR3008I Database backup was written using
client API: API information.
ANR3003E Command: Profile description exceeds
Explanation: The database backup was written using
the indicated IBM Spectrum Protect Backup/Archive
Explanation: The profile description specified in the API.
command is longer than the maximum length allowed.
System action: Database restore processing continues.
User response: This information will be used during
the database restore operation. If the API used during
User response: Select a description that does not the restore is not compatible, additional messages will
exceed the maximum length. be issued and the operation will fail.


ANR3009E Database restore not possible, client API
is not compatible: API information.
ANR3013W command: Configuration manager state
Explanation: The IBM Spectrum Protect client API
already set to state.
version being used for this database restore operation is
not compatible with the version used to write the Explanation: The specified state is already in force on
database backup. the server.
System action: Database restore processing terminates. System action: Server operation continues. The
User response: Install a newer version of the IBM
Spectrum Protect client API and retry this database User response: This server is already set to the
restore operation. The client API version currently specified state. If the state should be set differently,
available and used for this database restore operation is reissue the command specifying the new state value.
not compatible with what was used to originally write
the database backup.
ANR3014E command: One or more subscriptions still
exist.
ANR3010W This command will delete an object that
is associated with one or more profiles Explanation: A configuration manager state cannot be
on a configuration manager. Subsequent set to OFF is one or more subscription still exist. The
configuration refresh processing will server still has a record of one or more subscriptions to
delete the object on managed servers its profiles.
that subscribe to a profile with which System action: Server operation continues. The
the object is associated. command is not processed.
Explanation: A command has been entered that will User response: Use the QUERY SUBSCRIBERS
delete an object from a configuration manager. Since command to determine which subscriptions still exist.
this object is associated with one or more profiles on a The DELETE SUBSCRIBER command can be used to
configuration manager, configuration refresh processing remove the record of these subscriptions. You may
will delete this object on subscribing managed servers. instead want to delete the actual subscription(s) on the
System action: The system asks whether you wish to managed server(s). When there are no more
continue with the command. subscriptions recorded on the configuration manager,
you must then delete all the profiles. Once the profiles
User response: To process the command, enter 'Y' to have been deleted, you can reissue the command.
continue or 'N' to stop the process.
ANR3015E command: One or more profiles still
ANR3011E command: Subscription for profile profile exist.
name was not deleted because one or
more objects could not be discarded. Explanation: A configuration manager state cannot be
set to OFF is one or more profiles still exist.
Explanation: This message was issued because one or
more objects could not be discarded by the indicated System action: Server operation continues. The
command. A previous message gives an explanation for command is not processed.
each object that could not be discarded. User response: Use the QUERY PROFILE command to
System action: The system may discard some of the determine which profiles still exist on the configuration
managed objects that are associated with profile profile manager then use the DELETE PROFILE command.
name The subscription itself is not deleted. After all the profiles have been deleted, reissue the
command.
determine the action that must be taken before
remaining objects can be discarded. Alternatively, you ANR3016I command: Configuration refresh interval
can delete the subscription without using the set to interval.
DISCARDOBJECTS=YES option. Explanation: The command has successfully set the
configuration refresh interval to the specified value.
ANR3012I command: Configuration manager state Automatic configuration refresh processing will
set to state. immediately be attempted and then will again be
performed after the specified number of minutes of
Explanation: The command has successfully set the elapsed.
configuration manager state.
System action: The command succeeded.

ANR3017I command: Profile profile name defined. ANR3023I command: Profile profile name locked.
Explanation: The command has successfully define a Explanation: The command has successfully locked
profile. the profile. No configuration information can be
propagated to the subscribers of the profile until it is
unlocked.
ANR3018E command: Profile profile name already
exists.
ANR3024W command: Profile profile already locked
Explanation: The profile specified already exists on
with timeout interval greater than
the configuration manager.
interval.
Explanation: An attempt was made to lock the
specified profile. The profile is already locked with a
User response: Decide on another profile name and timeout interval greater than the value specified.
System action: The profile remains locked with the
original timeout interval.
ANR3019I command: Profile profile name updated.
User response: If you want to lower the timeout
Explanation: The command has successfully updated interval, unlock the profile and then lock the profile
a profile. again specifying the lower value.
ANR3025I command: Profile profile name unlocked.
Explanation: The command has successfully unlocked
the profile. Configuration information can now be
ANR3020E command: Profile profile name not found. propagated to the subscribers of the profile.
Explanation: The profile specified could not be found. System action: The command succeeded.
System action: Server operation continues. The User response: None.
User response: Check to see if the profile name was ANR3026I command: Profile profile name deleted.
specified correctly on the command. Use the QUERY
PROFILE command to check to see if the profile exists Explanation: The command has successfully deleted
on the configuration manager. Reissue the command the profile from the configuration manager.
with the correct profile name.
ANR3021I command: Profile profile name copied to
profile profile name.
ANR3027E command: One or more subscriptions still
Explanation: The command has successfully copied
exist to profile profile name.
the first profile to the newly created second profile. All
the profile associations were also copied. Explanation: An attempt was made to delete a profile
that still has subscriptions defined on one or more
managed servers. The configuration manager still has a
User response: None. record of one or more subscriptions to the profiles.
ANR3022E command: The profile lock timeout command is not processed.
interval value must be between minimum
User response: Use the QUERY SUBSCRIBERS
value and maximum value.
command to determine which subscriptions still exist.
Explanation: The specified command has been issued Use the DELETE SUBSCRIPTION command on the
with an invalid lock timeout interval. managed server(s) to delete the subscriptions, and then
reissue the DELETE PROFILE command on the
System action: Server operation continues. The configuration manager. Alternatively, the FORCE=YES
command is not processed. option can be used on the DELETE PROFILE command
User response: Issue the command and specify a valid to delete the profile even if there are subscriptions to
lock timeout interval value. the profile. In this case, messages will be issued when

the managed server requests updates for that profile,

ANR3033E command: Server server is not the
informing the managed server that the profile has been
managed server's configuration manager.
deleted.
Explanation: A server name was specified on the
command which does not match the current
ANR3028E command: Profile profile name is locked.
configuration manager. A managed server may only
Explanation: The specified command cannot be have one configuration manager.
performed on a locked profile.
System action: Server operation continues. The command is not processed.
User response: Reissue the command and leave off
User response: Unlock the profile using the UNLOCK the server parameter. It will default to use the current
PROFILE command and then reissue the command. configuration manager. A QUERY SUBSCRIPTION will
display the configuration manager currently in use.

canceled. ANR3034E command: Server server cannot be used as
this server's configuration manager.
Explanation: Based on the DISABLEREORGTABLE
server option, table reorganization is disabled for table Explanation: A server name was specified on the
that is referenced and a paused reorganization is command which cannot be used as a configuration
canceled. manager.
System action: The reorganization is canceled. System action: Server operation continues. The
User response: If the intention is to disable table
reorganization for table that is referenced, then no User response: Find out the correct name for the
further action is required, otherwise consider updating configuration manager and then reissue the command.
the DISABLEREORGTABLE server option.
ANR3035I command: Subscriber subscriber name
ANR3030I command: Subscription defined for deleted.
Explanation: The command has successfully deleted a
Explanation: The command has successfully defined a subscriber from the record kept in the configuration
subscription to the specified profile. A refresh of the manager. If the subscriber (managed server) still has a
configuration information has been initiated. subscription to a valid profile, the record of the
subscription will reappear when it performs its next
System action: The command succeeded. configuration refresh.
User response: None. System action: The command succeeded.
ANR3031W command: Subscription for profile profile
name already exists.
ANR3036E command: Subscriber subscriber name not
Explanation: A subscription already exists for the found.
specified profile.
Explanation: The specified subscriber name was not
System action: Server operation continues. The found in the configuration manager's records as being a
command is not processed. valid subscriber of any profiles.
User response: Check to make sure you specified the System action: Server operation continues. The
correction profile name, and reissue the command if command is not processed.
needed.
User response: Check to see that the subscriber
(managed server) name is correction. If you think the
ANR3032E command: Server name not specified. name is correct, perhaps the managed server has not
Explanation: A server name must be specified on this yet successfully contacted the configuration manager to
command using the SERVER= parameter. This inform it that the subscription exists.
identifies the configuration manager.
server name.

propagated to managed servers which subscribe to the

ANR3037I command: Subscription deleted for
profile.
subscription for the specified profile. A refresh of the User response: None.
configuration information has been initiated.
System action: The command succeeded. ANR3042W command: No additional administrators
associated with profile profilename.
Explanation: No additional administrator were
associated with the profile. The administrator(s)
ANR3038E command: Subscription for profile profile
specified are already associated with the profile.
name not found.
Explanation: A subscription was not found for the
specified profile.
User response: Use the QUERY ADMIN command to
check which administrators are defined on the server
and then reissue to DEFINE PROFASSOCIATION
User response: Check to see that the profile name was command. The QUERY PROFASSOCIATION
specified correctly. Issue the QUERY SUBSCRIPTION FORMAT=DETAILED can be used to see which
command to check to see which profiles have administrators are already associated with the profile.
subscriptions. Reissue the command with the correct
profile name.
ANR3043E command: No matching domains found
in configuration.
ANR3039E command: No matching administrators
Explanation: No domain definitions were found on
found in configuration.
the configuration manager that match the domain(s)
Explanation: No administrator definitions were found specified on the DEFINE PROFASSOCIATION
on the configuration manager that match the admin(s) command.
specified on the DEFINE PROFASSOCIATION
command.
User response: Use the QUERY DOMAIN command
to check which domains that are defined on the server
User response: Use the QUERY ADMIN command to and then reissue to DEFINE PROFASSOCIATION
check which administrators that are defined on the command.
server and then reissue to DEFINE
PROFASSOCIATION command.
ANR3044I command: All domains associated with
profile profilename.
ANR3040I command: All administrators associated
Explanation: The command has successfully
with profile profilename.
associated all the domains with the specified profile.
Explanation: The command has successfully All domain definitions will be automatically
associated all the administrators with the specified propagated to managed servers which subscribe to the
profile. All administrator definitions will be profile. If a domain is added to the configuration
automatically propagated to managed servers which manager in the future, its definition will also be
subscribe to the profile. If an administrator is added to automatically propagated to the managed servers.
the configuration manager in the future, its definition
will also be automatically propagated to the managed
servers. User response: None.
ANR3045I command: Domain domain associated with
ANR3041I command: Administrator admin associated
associated the domain with the specified profile. The
domain definition will be automatically propagated to
Explanation: The command has successfully managed servers which subscribe to the profile.
associated the administrator with the specified profile.
The administrator definition will be automatically


ANR3050W command: No additional admin
schedules associated with profile
ANR3046W command: No additional domains profilename.
Explanation: No additional admin schedules were
Explanation: No additional domains were associated associated with the profile. The admin schedule(s)
with the profile. The domain(s) specified are already specified are already associated with the profile.
associated with the profile.
User response: Use the QUERY SCHEDULE
User response: Use the QUERY DOMAIN command TYPE=ADMIN command to check which admin
to check which domains are defined on the server and schedules are defined on the server and then reissue to
then reissue to DEFINE PROFASSOCIATION DEFINE PROFASSOCIATION command. The QUERY
command. The QUERY PROFASSOCIATION PROFASSOCIATION FORMAT=DETAILED can be
FORMAT=DETAILED can be used to see which used to see which admin schedules are already
domains are already associated with the profile. associated with the profile.
ANR3047E command: No matching admin schedules ANR3051E command: No matching scripts found in
found in configuration. configuration.
Explanation: No admin schedule definitions were Explanation: No script definitions were found on the
found on the configuration manager that match the configuration manager that match the script(s) specified
admin schedule(s) specified on the DEFINE on the DEFINE PROFASSOCIATION command.
User response: Use the QUERY SCRIPT command to
User response: Use the QUERY SCHEDULE check which scripts that are defined on the server and
TYPE=ADMIN command to check which admin then reissue to DEFINE PROFASSOCIATION
schedules are defined on the server and then reissue to command.
DEFINE PROFASSOCIATION command.
ANR3052I command: All scripts associated with
ANR3048I command: All admin schedules profile profilename.
Explanation: The command has successfully associated all the scripts with the specified profile. All
associated all the admin schedules with the specified script definitions will be automatically propagated to
profile. All admin schedule definitions will be managed servers which subscribe to the profile. If a
automatically propagated to managed servers which script is added to the configuration manager in the
subscribe to the profile. If an admin schedule is added future, its definition will also be automatically
to the configuration manager in the future, its propagated to the managed servers.
definition will also be automatically propagated to the
managed servers.
ANR3053I command: Script script associated with
ANR3049I command: Admin Schedule admin schedule
associated the script with the specified profile. The
Explanation: The command has successfully script definition will be automatically propagated to
associated the admin schedule with the specified managed servers which subscribe to the profile.
profile. The admin schedule definition will be
automatically propagated to managed servers which
subscribe to the profile. User response: None.

ANR3054W command: No additional scripts ANR3058W command: No additional client option

associated with profile profilename. sets associated with profile profilename.
Explanation: No additional scripts were associated Explanation: No additional client option sets were
with the profile. The script(s) specified are already associated with the profile. The client option set(s)
associated with the profile. specified are already associated with the profile.
System action: Server operation continues. The System action: Server operation continues. The
User response: Use the QUERY SCRIPT command to User response: Use the QUERY CLOPTSET command
check which scripts are defined on the server and then to check which client option sets are defined on the
reissue to DEFINE PROFASSOCIATION command. The server and then reissue to DEFINE
QUERY PROFASSOCIATION FORMAT=DETAILED PROFASSOCIATION command. The QUERY
can be used to see which scripts are already associated PROFASSOCIATION FORMAT=DETAILED can be
with the profile. used to see which client option sets are already
associated with the profile.
ANR3055E command: No matching client option sets
found in configuration. ANR3059E command: No matching servers found in
configuration.
Explanation: No client option set definitions were
found on the configuration manager that match the Explanation: No server definitions were found on the
client option set(s) specified on the DEFINE configuration manager that match the server(s)
PROFASSOCIATION command. specified on the DEFINE PROFASSOCIATION
command.
command is not processed. System action: Server operation continues. The
User response: Use the QUERY CLOPTSET command
to check which client option sets that are defined on User response: Use the QUERY SERVER command to
the server and then reissue to DEFINE check which servers that are defined on the server and
PROFASSOCIATION command. then reissue to DEFINE PROFASSOCIATION
command.
ANR3056I command: All client option sets
associated with profile profilename. ANR3060I command: All servers associated with
associated all the client option sets with the specified Explanation: The command has successfully
profile. All client option set definitions will be associated all the servers with the specified profile. All
automatically propagated to managed servers which server definitions will be automatically propagated to
subscribe to the profile. If a client option set is added managed servers which subscribe to the profile. If a
to the configuration manager in the future, its server is added to the configuration manager in the
definition will also be automatically propagated to the future, its definition will also be automatically
managed servers. propagated to the managed servers.
System action: The command succeeded. System action: The command succeeded.
ANR3057I command: Client option set client option ANR3061I command: Server server associated with
set associated with profile profilename. profile profilename.
Explanation: The command has successfully Explanation: The command has successfully
associated the client option set with the specified associated the server with the specified profile. The
profile. The client option set definition will be server definition will be automatically propagated to
automatically propagated to managed servers which managed servers which subscribe to the profile.
subscribe to the profile.

ANR3062W command: No additional servers ANR3066W command: No additional server groups

associated with profile profilename. associated with profile profilename.
Explanation: No additional servers were associated Explanation: No additional server groups were
with the profile. The server(s) specified are already associated with the profile. The server group(s)
associated with the profile. specified are already associated with the profile.
System action: Server operation continues. The System action: Server operation continues. The
User response: Use the QUERY SERVER command to User response: Use the QUERY SERVERGROUP
check which servers are defined on the server and then command to check which server groups are defined on
reissue to DEFINE PROFASSOCIATION command. The the server and then reissue to DEFINE
QUERY PROFASSOCIATION FORMAT=DETAILED PROFASSOCIATION command. The QUERY
can be used to see which servers are already associated PROFASSOCIATION FORMAT=DETAILED can be
with the profile. used to see which server groups are already associated
with the profile.
ANR3063E command: No matching server groups
found in configuration. ANR3067E command: No matching administrators
associated with profile profile.
Explanation: No server group definitions were found
on the configuration manager that match the server Explanation: No matching administrator definitions
group(s) specified on the DEFINE PROFASSOCIATION are associated with the specified profile.
command.
User response: Use the QUERY PROFASSOCIATION
User response: Use the QUERY SERVERGROUP command to check which administrators are associated
command to check which server groups that are with the profile and then reissue to DELETE
defined on the server and then reissue to DEFINE PROFASSOCIATION command.
ANR3068I command: All administrator associations
ANR3064I command: All server groups associated deleted from profile profilename.
Explanation: The command has successfully deleted
Explanation: The command has successfully all administrators associations from the specified
associated all the server groups with the specified profile. This will automatically delete these
profile. All server group definitions will be administrators from the managed servers that are
automatically propagated to managed servers which subscribed to this profile.
subscribe to the profile. If a server group is added to
the configuration manager in the future, its definition
will also be automatically propagated to the managed User response: None.
servers.
System action: The command succeeded. ANR3069I command: Administrator association
admin deleted from profile profilename.
an administrator association from the specified profile.
ANR3065I command: Server group server group
This will automatically delete this administrator from
the managed servers that are subscribed to this profile.
associated the server group with the specified profile.
The server group definition will be automatically User response: None.
propagated to managed servers which subscribe to the
profile.
ANR3070E command: No matching domains
System action: The command succeeded. associated with profile profile.
User response: None. Explanation: No matching domain definitions are
associated with the specified profile.

User response: Use the QUERY PROFASSOCIATION schedule from the managed servers that are subscribed
command to check which domains are associated with to this profile.
the profile and then reissue to DELETE
ANR3071I command: All domain associations
deleted from profile profilename. ANR3076E command: No matching scripts associated
with profile profile.
all domains associations from the specified profile. This Explanation: No matching script definitions are
will automatically delete these domains from the associated with the specified profile.
managed servers that are subscribed to this profile.
System action: The command succeeded. command is not processed.
User response: None. User response: Use the QUERY PROFASSOCIATION
command to check which scripts are associated with
ANR3072I command: Domain association domain
deleted from profile profilename.
ANR3077I command: All script associations deleted
domain association from the specified profile. This will
from profile profilename.
automatically delete this domain from the managed
servers that are subscribed to this profile. Explanation: The command has successfully deleted
all scripts associations from the specified profile. This
will automatically delete these scripts from the
User response: None. managed servers that are subscribed to this profile.
ANR3073E command: No matching admin schedules
Explanation: No matching admin schedule definitions
ANR3078I command: Script association script deleted
are associated with the specified profile.
from profile profilename.
script association from the specified profile. This will
User response: Use the QUERY PROFASSOCIATION automatically delete this script from the managed
command to check which admin schedules are servers that are subscribed to this profile.
associated with the profile and then reissue to DELETE
ANR3074I command: All admin schedule
associations deleted from profile ANR3079E command: No matching client option sets
profilename. associated with profile profile.
Explanation: The command has successfully deleted Explanation: No matching client option set definitions
all admin schedules associations from the specified are associated with the specified profile.
profile. This will automatically delete these admin
schedules from the managed servers that are subscribed System action: Server operation continues. The
to this profile. command is not processed.
System action: The command succeeded. User response: Use the QUERY PROFASSOCIATION
command to check which client option sets are
User response: None. associated with the profile and then reissue to DELETE
ANR3075I command: Admin schedule association
admin schedule deleted from profile ANR3080I command: All client option set
profilename. associations deleted from profile
profilename.
an admin schedule association from the specified Explanation: The command has successfully deleted
profile. This will automatically delete this admin all client option sets associations from the specified

profile. This will automatically delete these client System action: Server operation continues. The
option sets from the managed servers that are command is not processed.
subscribed to this profile.
System action: The command succeeded. command to check which server groups are associated
with the profile and then reissue to DELETE
ANR3081I command: Client option set association

ANR3086I command: All server group associations
client option set deleted from profile
deleted from profile profilename.
profilename.
all server groups associations from the specified profile.
client option set association from the specified profile.
This will automatically delete these server groups from
This will automatically delete this client option set from
ANR3087I command: Server group association server

ANR3082E command: No matching servers
group deleted from profile profilename.
Explanation: No matching server definitions are
server group association from the specified profile. This
associated with the specified profile.
will automatically delete this server group from the
System action: Server operation continues. The managed servers that are subscribed to this profile.
command to check which servers are associated with
PROFASSOCIATION command. ANR3088W This command will cause the deletion
of objects on any managed server
subscribed to profile profile name.
ANR3083I command: All server associations deleted
from profile profilename. Explanation: A DELETE PROFASSOCIATION
command option has been entered. This action will not
only delete the association from the profile, but it will
all servers associations from the specified profile. This
also result in the deletion of managed object(s) on any
will automatically delete these servers from the
managed server subscribing to this profile. The deletion
managed servers that are subscribed to this profile.
of these objects will occur during the next configuration
System action: The command succeeded. refresh for that managed server.
User response: None. System action: The system asks whether you wish to
ANR3084I command: Server association server User response: To process the DELETE
deleted from profile profilename. PROFASSOCATION command, enter 'Y' to continue or
'N' to stop the command.
server association from the specified profile. This will
automatically delete this server definition from the ANR3089E command: Command failed -
managed servers that are subscribed to this profile. Server-to-server communication error
with server server name.
Explanation: The specified command failed while
User response: None. attempting to communicate with the indicated server.
ANR3085E command: No matching server groups command is not processed.
User response: Verify that the indicated server name
Explanation: No matching server group definitions are is correctly defined. Try reissuing the command. Use
associated with the specified profile. the server PING command to see if the other server is

up. If the problem persists, consult with your network

ANR3095W Failure updating the database volume
administrator.
history information with the volumes
used to perform this restore operation.
ANR3090E command: Server server name is not a
Explanation: At the end of database restore processing
for a point in time operation, the server database will
Explanation: The specified command failed because it be updated to show the volumes that were used to
tried to contact the specified server, and discovered that restore the database. This is done so that a future
the server is not a configuration manager. restore has knowledge of this database backup and will
be able to use this if it is the best possible candidate for
System action: Server operation continues. The a future operation. Because the server failed to update
command is not processed. this information, a future restore database operation
User response: Reissue the command and specify a may not select the best possible database backup to use
correct configuration manager name. for the operation.
System action: Database restore processing completes.
ANR3092I command: Subscriber notification User response: Once the server is restarted after the
processing has begun. database restore is completed, a BACKUP DB
Explanation: A NOTIFY SUBSCRIBER process has TYPE=FULL should be performed as soon as possible
begun. The managed server(s) are being contacted, and the volume history information backed up after
asking them to immediately perform a configuration this backup is completed. This will set a new best
refresh. possible restore point if a future restore operation is
needed. If you use the Disaster Recovery Manager
System action: Server operation continues. The feature to track database backup volume physical
command succeeded. location you will have to manually track the location of
User response: None. the database backup volumes which were not updated.
ANR3093I command: No matching profiles or ANR3096I The volumes used to perform this
subscriptions were found. restore operation were successfully
recorded in the server volume history.
Explanation: No subscriptions were found for the
profiles specified. Either the profiles do not exist, or Explanation: At the end of database restore processing
there are no subscriptions to the profiles. for a point in time operation, the server database will
be updated to show the volumes that were used to
System action: Server operation continues. The restore the database. This is done so that a future
command is not processed. restore has knowledge of this database backup and will
User response: Use the QUERY PROFILE and QUERY be able to use this if it is the best possible candidate for
SUBSCRIBER command to determine which profiles a future operation.
exist and which profiles have subscribers. Reissue the System action: Database restore processing completes.
command specifying the correct profile name(s).
ANR3094E The distinguished name "DN" that is

specified in the LDAPURL option does ANR3097W LDAPUSER must be set before you can
not exist on the LDAP directory server. use LDAP password authentication.
Explanation: The distinguished name (DN) that is Explanation: The LDAPURL server option is set,
specified in the LDAPURL server option is not found however LDAP password authentication cannot
on the LDAP directory server. complete until LDAPUSER and LDAPPASSWORD are
set.
System action: Server initialization fails.
System action: Server operations continue without
User response: Create the directory entry that is LDAP authentication.
associated with the DN, specify a DN in the LDAPURL
that already exists, or specify another directory server User response: Issue the SET LDAPUSER and SET
that contains the DN that is defined in the LDAPURL LDAPPASSWORD commands, in that order.
server option. Choose one of these options and restart
the IBM Spectrum Protect server. ANR3098W LDAPPASSWORD must be set before
you can use LDAP password
authentication.
Explanation: The LDAPURL server option is set,
however LDAP password authentication cannot

complete until the LDAPUSER and LDAPPASSWORD

ANR3103E Failure occurred while initializing
are set.
LDAP directory services.
System action: Server operations continue without
Explanation: An error occurred while the server
LDAP authentication.
initialized LDAP directory services.
User response: Issue the SET LDAPPASSWORD
System action: Server operations fail. If the server is
command.
already started, LDAP directory services are no longer
available. The server cannot start if it was in the middle
ANR3099E The distinguished name "DN" specified of trying to start.
in the LDAPURL option does not have
User response: Examine the server messages that were
the proper syntax.
issued prior to this message to determine the source of
Explanation: The distinguished name (DN) in the the error. Issue the QUERY ACTLOG command to view
LDAPURL server option does not have the proper the activity log file and search for messages. Check for
syntax. The LDAP URL must use the RFC 2255 format network problems. Check for problems with the
with the restriction that the LDAPURL server option certificate used by the directory server or the key
can only contain ASCII characters. The DN must database containing the certificates. Check the access
conform to the requirements of the directory server. rights of the LDAPUSER. Check the status of the
Directory servers typically support RFC 2253 or 4514 directory server and examine the log files provided by
for the DN format. the directory server. Use LDAP utilities such as
ldapsearch or ldp to isolate the problem.
If the server does not start, remove the LDAPURL
User response: Correct the LDAPURL server option server option to allow the server to start temporarily
and restart the IBM Spectrum Protect server. without directory services. If the server is running,
issue the SET LDAPUSER or SET LDAPPASSWORD
ANR3100I Initializing LDAP directory services. commands to try initializing LDAP directory services
again.
Explanation: The server started the initialization
process with the LDAP directory server.
ANR3104E The LDAP directory service is not
System action: Server operations continue. successfully configured.
User response: None. Explanation: The IBM Spectrum Protect server must
be configured correctly in order to use LDAP directory
ANR3101I Successfully initialized LDAP directory services, before accounts can be placed in the LDAP
services. directory server to authenticate access requests.
Explanation: The server was successfully configured System action: Server operations fail.
to use LDAP directory services. User response: To configure LDAP directory services,
System action: Server operations continue and LDAP set the LDAPURL server option, add the appropriate
directory services are available. certificate to the IBM Spectrum Protect server key
database, and issue the SET LDAPUSER and SET
User response: None. LDAPPASSWORD commands. The LDAP password
(LDAPPASSWORD) must match the password for the
ANR3102E An authentication failure occurred user (LDAPUSER) that can conduct IBM Spectrum
during LDAP directory services Protect administrative operations when accessing the
initialization as user LDAP user. LDAP directory server.
Explanation: The LDAPUSER value or the If the IBM Spectrum Protect server is already
LDAPPASSWORD value, or both, are incorrect. configured to use LDAP directory services, an
authentication failure might have occurred or another
System action: Server operations continue. LDAP error might have occurred during configuration.
directory services are not available. Examine the server messages that were issued prior to
this message to determine the source of the error. Issue
User response: Correct the values for the LDAP user
the QUERY ACTLOG command to view the activity log
and LDAP password by issuing the SET LDAPUSER
and search for messages.
and SET LDAPPASSWORD commands. After you issue
these commands, LDAP directory services initialization
is attempted.

Explanation: You cannot have multiple LDAPURL

ANR3105E The LDAP directory service was not
server option values if one of the values does not
found by using Domain Name System
specify a host address.
(DNS).
Explanation: An LDAP directory server could not be
located using the system's current DNS server User response: Correct the LDAPURL server option
configuration and DNS suffix search list. value and restart the IBM Spectrum Protect server.
System action: Server operations fail.
ANR3110E The distinguished names "DN" and
User response: Check the system's DNS configuration,
"DN" specified with the LDAPURL
the status of the DNS servers, the DNS server log files,
server option do not match.
and the DNS server configuration. Verify that the DNS
server configuration complies with RFCs 2052, 2219, or Explanation: The distinguished names (DN) specified
2782. on each LDAPURL server option value must be the
same.
ANR3106E Failed to parse the LDAPURL option System action: Server initialization fails.
value LDAP URL.
User response: Correct the LDAPURL server option
Explanation: The LDAPURL server option value value and restart the IBM Spectrum Protect server.
cannot be parsed. The LDAP URL must use the RFC
2255 format with the restriction that the LDAPURL
server option contain only ASCII characters. ANR3111E The LDAPURL server option value
LDAP URL is missing the ldap:// prefix.
Explanation: When updating the LDAP URL
User response: Correct the LDAPURL server option information, use the RFC 2255 format.
value and restart the server.
System action: Server operations fail.
ANR3107E LDAPS is not allowed for the User response: Use the standard ldap:// scheme
LDAPURL option value LDAP URL. prefix for the LDAPURL server option and restart the
IBM Spectrum Protect server.
Explanation: LDAPS represents using a Secure Sockets
Layer (SSL) connection and sending LDAP data over an
existing SSL connection. The server only supports ANR3112E The password cannot be reset, the
LDAP connections secured by using the standard LDAP directory server requires you to
LDAPv3 "StartTLS" operation to establish a secure TLS provide the current password.
exchange on an existing LDAP connection. Explanation: The LDAP directory server requires that
System action: Server initialization fails. the user who is specified in the SET LDAPUSER
command provide the current password when
User response: Use the standard ldap:// scheme for changing another user's password. The LDAPUSER
the LDAPURL server option and restart the IBM needs to be able to reset passwords to allow IBM
Spectrum Protect server. Spectrum Protect administrators to reset passwords for
IBM Spectrum Protect nodes and administrators.
ANR3108E The distinguished name is missing from System action: Server operation fails.
the LDAPURL server option value LDAP
URL. User response: Change the password policy or
permission settings on the LDAP directory server to
Explanation: The distinguished name (DN) is required allow the user who is specified in the SET LDAPUSER
as part of the LDAPURL server option. When updating command to change passwords for LDAP users who
the LDAP URL information, use the RFC 2255 format. are managed by the IBM Spectrum Protect server.
ANR3113E The password cannot be added or
User response: Correct the LDAPURL server option
changed, the LDAP user does not have
value and restart the IBM Spectrum Protect server.
sufficient access rights to add or change
the password.
ANR3109E The LDAPURL server option value
Explanation: If the current password was not
LDAP URL does not contain a host
provided for the operation, a password reset is
address and cannot be used because
performed on the LDAP directory server by the user
another LDAPURL option value
specified in the SET LDAPUSER command. If the
specifies a host address.
current password was provided for the operation, for

example, in the SET PASSWORD client command, the ACTLOG command to view the activity log and search
user's password is changed on the LDAP directory for messages. Check for network problems. Check for
server by the user. However, if the user's password problems with the certificate used by the LDAP
expired, preventing access to the directory server, the directory server or the key database containing the
password is changed by the user specified in the SET certificates. Check the status of the LDAP directory
LDAPUSER command. server and examine its log files. Use LDAP utilities
such as ldapsearch or ldp to isolate the problem using
System action: Server operation fails.
a TLS connection to the LDAP server.
User response: Change the password policy and
access rights on the LDAP directory server to allow
ANR3117E Session session number for node or
users to change their own passwords, and to allow the
administrator node/admin name (client
user specified in the SET LDAPUSER command to add
platform) refused - the level of the client
or reset passwords for the users that are being
does not meet the minimum required
managed by the IBM Spectrum Protect server.
level for LDAP authentication.
Explanation: The server refuses the client session
ANR3114E LDAP error LDAP error code (error
because the client program version level is not 6.4 or
description) occurred during operation.
later. Only version 6.4 and later clients can use LDAP
Explanation: The LDAP operation failed with an authentication.
unexpected error.
System action: The session is refused and server
System action: The server operation fails. operations continue.
User response: Examine the server messages issued User response: Upgrade the client program to at least
around the same time as this message to determine the version 6.4 or do not use LDAP authentication to make
cause and impact of the error. Issue the QUERY it compatible with the newer server program.
for messages. Check the status of the LDAP directory
ANR3118I The LDAP entry for node node name was
server and examine its log files. Use LDAP utilities
deleted.
such as ldapsearch or ldp to isolate the problem.
Explanation: An inconsistency between the database
of the IBM Spectrum Protect server database and the
ANR3115E The LDAP directory server returned the
LDAP directory server was found during AUDIT
following error message (LDAP server
LDAPDIRECTORY command processing. Because you
message) with the LDAP error.
specified FIX=YES, the LDAP entry for the node was
Explanation: The LDAP directory server returned an deleted to correct this inconsistency.
error message associated with an LDAP error that
occurred, providing addition information to assist in
determining the cause of the problem. User response: None.
System action: The server operation fails.
ANR3119I The LDAP entry for administrator admin
name was deleted.
around the same time as this message to determine the
cause and impact of the error. Issue the QUERY Explanation: An inconsistency between the database
ACTLOG command to view the activity log and search of the IBM Spectrum Protect server database and the
for messages. Check the status of the LDAP directory LDAP directory server was found during AUDIT
server and examine its log files. Use LDAP utilities LDAPDIRECTORY command processing. Because you
such as ldapsearch or ldp to isolate the problem. specified FIX=YES, the LDAP entry for the
administrator was deleted to correct this inconsistency.
ANR3116E LDAP SSL/TLS error GSKIT error code System action: Server operations continue.
(error description) occurred during
operation.
Explanation: An SSL/TLS error code was reported by
ANR3120I The administrator admin name was
the GSKit component along with the LDAP error that
updated because the parameter parameter
occurred.
for a node with the same name was
System action: The server operation fails. changed.
User response: Examine the server messages issued Explanation: Values for the AUTHENTICATION and
around the same time as this message to determine the SSLREQUIRED parameters must be the same for nodes
cause and impact of the error. Issue the QUERY and administrators that share the same name. If values

for either the node or the administrator changed, the However, this combination will not create an LDAP
administrator or node sharing the same name will be entry, which is required to access the node.
updated to keep these parameters the same.
If the AUTHENTICATION parameter changed from
User response: An LDAP entry must be created before
LDAP to LOCAL, the password was also updated.
this node can be accessed. To create a new LDAP entry
When this happens, the password is updated to the
for this node issue the UPDATE NODE command and
same password that is used for the node.
provide a password. If the LDAP directory server is
System action: The server updated the shared with another IBM Spectrum Protect server, the
AUTHENTICATION or SSLREQUIRED parameter of LDAP entry can be created by the other IBM Spectrum
the specified administrator. Protect server instead.
ANR3124W An LDAP entry for administrator admin
name was not found in the LDAP
ANR3121I The node node name was updated
directory server.
because the parameter parameter for an
administrator with the same name was Explanation: The REGISTER ADMIN command was
changed. issued with AUTHENTICATION=LDAP but without
providing a password. This combination is valid.
Explanation: Values for the AUTHENTICATION and
However, this combination will not create an LDAP
SSLREQUIRED parameters must be the same for nodes
entry, which is required to access the administrator.
and administrators that share the same name. If values
for either the node or the administrator changed, the System action: The command succeeded.
node or administrator sharing the same name will be
User response: An LDAP entry must be created before
this administrator can be accessed. To create a new
If the AUTHENTICATION parameter changed from LDAP entry for this administrator issue the UPDATE
LDAP to LOCAL, the password was also updated. ADMIN command and provide a password. If the
When this happens, the password is updated to the LDAP directory server is shared with another IBM
same password that is used for the administrator. Spectrum Protect server, the LDAP entry can be created
by the other IBM Spectrum Protect server instead.
System action: The server updated the
AUTHENTICATION or SSLREQUIRED parameter of
the specified node. ANR3125I command: Successfully updated successful
updates nodes out of total update attempts
nodes that were targeted for updating.
Explanation: The command updated a node or nodes
ANR3122E command: System level authority is
and produced summary statistics stating how many
required because the server needs to
nodes were updated successfully and how many
update a node or administrator that
attempts were made.
shares the same name.
Explanation: Values for the AUTHENTICATION and
SSLREQUIRED parameters must be the same for nodes User response: None.
and administrators that share the same name. If values
for either the node or the administrator changed, the
ANR3126I command: Successfully updated successful
node or administrator sharing the same name will be
updates administrators out of total update
attempts administrators that were
System action: The server fails the command. targeted for updating.
User response: Reissue the command using an Explanation: The command updated an administrator
administrator that has system level authority. or administrators and produced summary statistics
Alternatively, rename either the node or the stating how many administrators were updated
administrator associated with the command such that successfully and how many attempts were made.
they do not share the same name.
ANR3123W An LDAP entry for node node name was
not found in the LDAP directory server.
Explanation: The REGISTER NODE command was
issued with AUTHENTICATION=LDAP but without
providing a password. This combination is valid.

ANR3127W You must change the password for ANR3134E Command: The number of specified
"LDAP user" within number day(s). output volumes (volume count) is less
than the number of streams specified in
Explanation: The password is due to expire, and it
the MAXSTREAM parameter (stream
must be changed to prevent failures.
count).
Explanation: The number of specified output volumes
User response: Change the password on the LDAP is less than the number of streams specified in the
directory server and issue the SET LDAPPASSWORD MAXSTREAM parameter, and scratch volumes are not
command with the new password. allowed.
System action: The command is not run.
ANR3128E Command: The number of failover
User response: Rerun the commmand, specifying
servers exceeds the maximum number
more output volumes or fewer streams, or specify
allowed.
SCRATCH=YES to allow scratch volumes to be used.
Explanation: The number failover servers that can be
defined for a node is limited to one.
ANR3135E Command: The value specified for the
System action: The command fails. MAXSTREAM parameter (stream count)
is greater than the mount limit
User response: Reissue the command specifying only associated with device class device class
one registered server name. (mount limit).
Explanation: The value specified for the
ANR3129I Server Fail Over high level address set MAXSTREAM parameter is greater than the mount
to address. limit of the specified device class.
Explanation: The high level address that clients use to System action: The command is not run.
communicate with this server during fail over has been
set to the value indicated with the SET User response: Rerun the commmand, specifying
FAILOVERHLADDRESS command. fewer streams.
ANR3136E Extractdb command: Failed to start or
User response: None. failed to complete successfully.
Explanation: The database extract process was not
ANR3132W Replication process with process Id able to start due to an error with the command
process number from server server name, is specification or other validation performed prior to
cancelled. Replication process source performing the extract. Alternatively, the extract process
process number on source server may still had started but failed to complete successfully due to
be active. an error during processing.
Explanation: A replication process on a target System action: Database extract processing did not
replication server which was initiated on a source process successfully.
replication server has been cancelled.
User response: Review the other messages issued to
System action: Server operation continues. determine the cause of the failure.
User response: Check the status of the replication
process on the source server. Issue the CANCEL ANR3137E Unable to reclaim database storage for
PROCESS command on the source server to cancel this table space tbspace name. The error code
replication operation. return code is returned.
Explanation: An error occurred when the database
ANR3133E command: Server server name not defined manager was trying to reclaim space in the referenced
Explanation: The server server name is not defined to table space.
the system. System action: The EXTEND DBSPACE operation
System action: The command proceeds howver the fails. Server operation continues.
server name is not used. User response: Review messages on the server console
User response: Use QUERY SERVER to identify a and in the db2diag log to try and determine the reason
valid failover server. for the failure. To complete the process, you will have
to manually execute the steps for redistributing data
and reclaiming space.

ANR3138I Reclaiming database storage for table ANR3143I The following directory or directories
space tbspace name is being started. have been defined in the database
space: directory list. However, the
Explanation: The database manager is reclaiming
database manager might not use new
storage space for the referenced table space.
storage paths immediately.
Explanation: The EXTEND DBSPACE operation
User response: None. successfully added new directories to the server
database storage space. Because RECLAIM=NO was
specified on the command, data is not redistributed
ANR3139I Reclaiming database storage for all table across all directories. New storage paths might not be
spaces is completed . used until existing storage is full.
Explanation: The database manager has reclaimed System action: Server operation continues.
space and reduced the size of all table spaces.
User response: If you decide that you want to
System action: Server operation continues. redistribute data and reclaim space in the database, you
User response: None. can manually complete the step for these tasks.
ANR3140I Redistribution of data for database ANR3144I Space is being added to the database as
database name on table space tbspace name process process ID.
is complete. Explanation: An operation to add space to the
Explanation: The database manager has created database, redistribute data across all directories, and
directories on recently added paths and has return space to the operating system is in progress.
redistributed data across those paths for the referenced System action: The EXTEND DBSPACE command is
tablespace. processed and server operation continues.
System action: Server operation continues. User response: Do not stop the server while this
User response: None. process is running and do not try to halt the process
once it has started. If you want to cancel the process,
use the CANCEL PROCESS command. To query the
ANR3141E Redistribution of data for database status of this process, issue QUERY PROCESS
database name on table space tbspace name
failed with error code error code.
ANR3145E Command: Administrator admin name is
Explanation: A failure occurred during the creation of currently accessing server server name.
directories on recently added paths or during the
redistribution of data across new directories for the Explanation: The command shown specifies an
referenced tablespace. admininistrator that has an active session with the
specified server.
System action: The EXTEND DBSPACE operation
fails. Server operation continues. System action: The local server does not process the
command.
User response: Review messages on the server console
and in the db2diag log to try and determine the reason User response: Reissue the command at a later time,
for the failure. To complete the process, you will have or if necessary, cancel the current administrator session
to manually execute the steps for redistributing data and reissue the command.
and reclaiming space.
ANR3146E command name: The list of directories
ANR3142I Redistribution of data for database specified for database storage exceeds
database name on table space tblspace name length limit characters.
is starting. Explanation: The list of directories is too long. Specify
Explanation: The database manager is creating a list less than or equal to the number of characters
directories on newly added paths and redistributing indicated.
data across all directories for the referenced table space. System action: The command stops.
System action: Server operation continues. User response: Consider breaking up the operation
User response: None. into multiple EXTEND DBSPACE commands to reduce
the number of directories specified on the command.

ANR3147I Directory(ies) directory list has been ANR3151E Configuration refresh failed with
defined in the database space. Database configuration manager server name.
data was distributed and balanced
Explanation: While receiving configuration
across existing directories.
information from the specified configuration manager,
Explanation: Command 'EXTEND DBSPACE' processing failed.
successfully added new directory(ies) into the server
database space and balanced data across existing
configuration refresh process was stopped.
directories.
User response: Examine the activity log for other
System action:
messages that may explain why the configuration
User response: refresh failed. The refresh will attempted again when
the configuration refresh interval is reached.
ANR3148W Process process number, replicating with
process source process number on server ANR3152I Configuration refresh started with
server name, has been inactive for minutes configuration manager server name.
of inactivity minutes.
Explanation: Configuration refresh processing has
Explanation: A replication process on a target server started. A server-to-server session was opened to
has been inactive for a significant amount of time. It is receive configuration information from the
possible that there is a connection problem with the configuration manager. Updates will be sent for objects
source replication server, or the source replication associated with any subscribed-to profiles.
process is no longer running, or the source replication
System action: Refresh processing continues.
server is down.
User response: Verify that the source replication
ANR3153I Configuration refresh ended
server is still running. If the server is running, check
successfully with configuration manager
that the source replication process is still active. If the
server name.
source replication process is no longer active you can
cancel this process. Explanation: Configuration refresh processing ended
successfully. All updates have been made to managed
objects associated with any subscribed-to profiles.
ANR3149I Server Fail Over high level address
removed. System action: Server processing continues. The next
automatic refresh will start when the configuration
Explanation: The high level address that clients use to
refresh interval is reached.
communicate with this server during fail over has been
removed. User response: None.
ANR3154E Communication error on notify to
managed server server name. Will retry in
minutes minutes.
ANR3150E Configuration refresh failed with
Explanation: While attempting a notify subscriber
configuration manager server name. Will
request to the specified managed server, a
retry in minutes minutes.
communications error was detected.
System action: Server operation continues. The notify
subscriber request was stopped and will be
processing failed because of a communications error.
automatically retried.
User response: Perhaps the managed server is not
configuration refresh process was stopped and will be
active. If the problem continues, contact the
automatically retried.
administrator for the managed server, or contact a
User response: Perhaps the configuration manager is network administrator. The notify subscriber request
not active. If the problem continues, contact the will automatically retry several times and then give up.
administrator for the configuration manager, or contact
a network administrator. The refresh will automatically
retry several times and then give up until the
configuration refresh interval is reached again.

configuration manager and a new profile by the same

ANR3155E Error attempting notify subscribers
name was created.
request to managed server server.
System action: Server operation continues. No
System action: Server operation continues. The notify
configuration information for this profile will be sent to
subscriber request failed.
the managed server until this condition is corrected.
User response: Examine the activity log for other
User response: Before correcting the situation, you
messages that may explain why the notify subscriber
may want to use QUERY PROFILE to examine the
request failed.
profile associations defined on both the configuration
manager and the managed server. To correct the
ANR3156E Configuration refresh failed for situation, on the managed server delete the
managed server server name. subscription to the profile and define the subscription
again. This will cause the managed server to be
Explanation: While sending configuration information
refreshed at the configuration manager's current level.
to the specified managed server, processing failed.
ANR3160E Unable to receive confirmation of
configuration refresh process ended.
refresh from managed server server name.
User response: Examine the activity log of both the
managed server and the configuration manager for
to the specified managed server, a communication error
other messages that may explain why the configuration
occurred when trying to receive confirmation from the
refresh failed. The refresh will attempted again by the
managed server that information was processed
managed server when its configuration refresh interval
successfully.
is reached.
Configuration refresh processing ended.
ANR3157I Configuration refresh started for
managed server server name. User response: Determine if communication can be
established with the managed server by using the
Explanation: Configuration refresh processing has
server PING command. Use the NOTIFY
started. A server to server session was opened by the
SUBSCRIBERS command to force the configuration
managed server to receive configuration information
refresh to retry.
from the configuration manager. Updates will be sent
for objects associated with any subscribed-to profiles.
ANR3161E Premature end of configuration refresh
System action: Refresh processing continues.
for managed server server server name.
to the specified managed server, processing ended
ANR3158I Configuration refresh ended prematurely because of on error.
successfully for managed server server
name.
Explanation: Configuration refresh processing ended
User response: Examine the activity log on the
successfully. All updates have been made to managed
managed server for any error messages that might
objects associated with any subscribed-to profiles on
explain why the refresh failed. Use the NOTIFY
the managed server.
SUBSCRIBERS command on the configuration manager
System action: Server processing continues. to force the configuration refresh to retry.

ANR3162E Managed server server name aborted
configuration refresh processing due to
ANR3159E Managed server server name has newer a low memory condition.
version for profile profile name.
Explanation: While sending configuration information to the specified managed server, processing ended
to the specified managed server, it has been detected prematurely because of a low memory condition on the
that the managed server has a newer version of managed server.
configuration information for the specified profile than
does the configuration manager. This condition can System action: Server operation continues.
happen if the configuration manager's database has Configuration refresh processing ended.
been restored to an earlier point in time. Another
User response: Make more memory available to the
possibility is that the profile was deleted on the
managed server.

ANR3163E Managed server server name aborted ANR3167E Configuration manager server name
configuration refresh processing due to aborted configuration refresh processing
an internal error. due to a low memory condition.
Explanation: While sending configuration information Explanation: While receiving configuration
to the specified managed server, processing ended information from the specified configuration manager,
prematurely because of an internal error on the processing ended prematurely because of a low
managed server. memory condition on the configuration manager.
Configuration refresh processing ended. Configuration refresh processing ended.
User response: Examine the activity log of the User response: Notify the administrator of the
managed server for messages that explain the cause of configuration manager.
the internal error.
ANR3168E Configuration manager server name
ANR3164E Managed server server name aborted aborted configuration refresh processing
configuration refresh processing due to due to an internal error.
a lock conflict.
Explanation: While sending configuration information information from the specified configuration manager,
to the specified managed server, processing ended processing ended prematurely because of an internal
prematurely because of a lock conflict on the managed error on the configuration manager.
server.
System action: Server operation continues. Configuration refresh processing ended.
User response: Examine the activity log of the
User response: Use the NOTIFY SUBSCRIBERS configuration manager for messages that explain the
command to retry the configuration refresh. If this cause of the internal error.
problem persists, contact your service representative.
ANR3169E Configuration manager server name
ANR3165E Managed server server name aborted aborted configuration refresh processing
configuration refresh processing due to due to a lock conflict.
a protocol error.
Explanation: While sending configuration information information from the specified managed server,
to the specified managed server, processing ended processing ended prematurely because of a lock conflict
prematurely because of a protocol error detected on the on the configuration manager.
managed server.
System action: Server operation continues. Configuration refresh processing ended.
User response: Retry the configuration refresh by
User response: Use the NOTIFY SUBSCRIBERS issuing the SET CONFIGREFRESH command (using
command to retry the configuration refresh. If this the current refresh interval value). If this problem
problem persists, contact your service representative. persists, contact your service representative.
ANR3166E Unable to receive configuration refresh ANR3170E Configuration manager server name
information from server server name. aborted configuration refresh processing
due to a protocol error.
information from the specified configuration manager, Explanation: While receiving configuration
processing ended prematurely because of a information from the specified configuration manager,
communications error. processing ended prematurely because of a protocol
error detected on the configuration manager.
Configuration refresh processing ended. System action: Server operation continues.
User response: Use the server PING command to see
if the configuration manager can be reached. If the User response: Retry the configuration refresh by
problem persists, contact your network administrator. issuing the SET CONFIGREFRESH command (using
the current refresh interval value). If this problem
persists, contact your service representative.

manager and the managed server. To correct the

ANR3171E Configuration refresh with
situation, on the managed server delete the
configuration manager server name had
subscription to the profile and define the subscription
to skip processing for one or more
again. This will cause the managed server to be
objects.
refreshed at the configuration manager's current level.
ANR3174E Communication error with managed
it became necessary to skip the creation or deletion of
server server name.
one or more objects.
Explanation: While receiving or sending information
to the specified managed server, a communications
error was experienced.
User response: Examine the managed server's activity
log for earlier messages that identify the object, and
operation in progress fails.
take the actions identified in those messages.
Configuration refresh processing will not complete User response: If this error happens often, consult
successfully until the problem is clear up. with your network administrator. Also check to see that
the managed server is up.
ANR3172W Subscription exists for deleted profile
profile name. ANR3175W Profile profile name is locked and could
not be refreshed from configuration
manager server name.
information from the configuration manager, it has
been detected that the managed server has a Explanation: While receiving configuration refresh
subscription to an profile that no longer exists on the information from the specified managed server, it was
configuration manager. This condition can exist because detected that a subscribed-to profile is locked.
the profile was deleted with FORCE=YES on the
configuration manager. This out-of-synch condition can System action: Server operation continues. Refresh
also occur because one of the server's database was processings skips over this profile.
regressed because of a restore db. User response: Normally, the profile will later be
System action: Server operation continues. unlocked automatically, or by an administrator. If you
think that it should not be locked, have ask the
User response: The DELETE SUBSCRIPTION configuration manager admin to unlock it using the
command is used to correct this situation. You need to UNLOCK PROFILE command.
decide if you want the managed objects to remain on
the server. If you want them to be deleted, specify
DISCARD=YES. If you want the objects to remain on ANR3176W Profile profile name is locked and could
the managed server as local objects, specify not be refreshed for managed server
DISCARD=NO. server name.
Explanation: While sending configuration refresh
ANR3173E Server has newer version for profile information to the specified managed server, it was
profile name than the configuration detected that a subscribed-to profile is locked.
manager server name. System action: Server operation continues. Refresh
Explanation: While receiving configuration processings skips over this profile.
information from the configuration manager, it has User response: If the profile should no longer be
been detected that the managed server has a newer locked, use the UNLOCK PROFILE command to
version of configuration information for the specified unlock it.
profile than does the configuration manager. This
condition can happen if the configuration manager's
database has been restored to an earlier point in time. ANR3177W Server level does not support object in
Another possibility is that the profile was deleted on profile profile name.
the configuration manager with FORCE=YES and a Explanation: While receiving configuration refresh
new profile by the same name was created. information from the configuration manager, an object
System action: Server operation continues. No was received that is not supported on this managed
configuration information for this profile will be sent to server.
the managed server until this condition is corrected. System action: Server operation continues. Refresh
User response: Before correcting the situation, you processings skips over this object. The refresh for the
may want to use QUERY PROFILE to examine the profile fails.
profile associations defined on both the configuration

User response: The configuration manager is at a

ANR3181E Replication server server name has the
higher release level than the managed server. The
same replication key as this server.
managed server subscribed to a profile that contains an
unsupported object. Delete the subscription to this Explanation: During replication initialization, the
profile until service can be applied to the server to server detected that the replication key of the target
bring it to a higher release level. server is the same as this server. Each server must have
a unique replication key.
ANR3178E A communication error occurred during System action: Replication to the specified server is
session session number with replication stopped.
server server name.
User response: Issue the SET REPLSERVER command
Explanation: The communication error occurred while to specify a different server for the target of the
the system was receiving information from or sending replication.
information to the specified replication server. This
error can occur on a target replication server if a
ANR3182W The password authentication method for
CANCEL REPLICATION command is issued on the
node node name did not change.
source replication server.
Explanation: During replication or import processing,
System action: The server is running, but the
a node that uses an LDAP directory server to
operation that was in progress failed.
authenticate passwords at the target was detected, but
User response: If this error occurs frequently, consult the source node authenticates passwords with the IBM
your network administrator. Also review the activity Spectrum Protect server (LOCAL). The Replication and
log on the target and source replication servers for Import process does not change the node password
messages that are related to replication. authentication method from LDAP to LOCAL.
System action: Replication or Import processing
ANR3179E Server server name does not support continues. The node password authentication method
replication or is not initialized for did not change from LDAP to LOCAL.
replication.
User response: Change the node password
Explanation: In response to a REPLICATE command, authentication method from LDAP to LOCAL by
the server attempted to establish a connection to the issuing the UPDATE NODE command with the
replication target. But the target server does not AUTHENTICATION=LOCAL parameter.
support replication, or has not been properly initialized
for replication.
ANR3183W The password authentication method for
System action: Server operation continues. The administrator admin name did not
replication fails. change.
User response: Make sure the replication target is at Explanation: During import processing, an
the correct maintenance level and verify that the administrator ID was detected that authenticates
globally unique ID (GUID) of the target server is passwords with an LDAP directory server at the target,
properly set. Use the tivguid utility to set the GUID if but with the IBM Spectrum Protect server (LOCAL) at
not properly set. the source. Import processing does not change an
administrator's password authentication method from
LDAP to LOCAL.
ANR3180E Replication cannot occur for node node
name, file-space filespace name and copy System action: Import processing continues. The
type copytype name because the target password authentication method did not change from
replication server is not set. LDAP to LOCAL.
Explanation: In response to a REPLICATE NODE User response: You can change the password
command, the server was unable to establish a authentication method for the target administrator from
connection to a target replication server because a LDAP to LOCAL by issuing the UPDATE ADMIN
target server was not defined. command with the AUTHENTICATION=LOCAL
parameter.
System action: Replication for the node and file space
is skipped. However, replication continues for other
nodes and file spaces. ANR3184E Server server name cannot replicate with
this server.
User response: To replicate data, the target replication
server must be defined. Issue the SET REPLSERVER Explanation: In response to a REPLICATE command,
command to set the target replication server name. The the server tried to establish a connection with the
name specified in the SET REPLSERVER command replication target. The target server is at a level that
must be associated with a valid server definition. cannot support replication with this server.

System action: Server operations continue. The rule of a replicating node. The associated replication
replication fails. node could not be replicated because it is not currently
enabled for replication. Associated replication nodes
User response: Make sure that the replication target
must have a replication mode set to SEND and a
server is at a maintenance level that supports
replication state of ENABLED in order to be replicated
replication with this server.
to a target server.
System action: The replication operation continues.
ANR3185I Replicating node associated replication
The replication of the associated node fails.
node as a proxy agent for replicated node
reference node User response: To use an associated replication node
with a client during a failover operation enable the
Explanation: During a REPLICATE NODE operation,
associated replication node for replication.
the server has identified an associated proxy agent
node referenced by a replicated node. The proxy agent
node defintion will be replicated. ANR3189E Replication of associated replication
node associated replication node name failed
- the target node is not enabled for
User response: None. replication
Explanation: During a REPLICATE NODE operation,
ANR3186I Replicating node associated replication the server attempted to replicate a node that is either a
node which is referenced in a file space proxy agent or referenced in a file space authorization
authorization rule for replicated node rule of a replicating node. The associated replication
reference node node could not be replicated because the node
definition on the target server is not currently enabled
Explanation: During a REPLICATE NODE operation, for replication. Associated replication nodes on the
the server has identified an associated replication node target server must have a replication mode set to RECV
that is referenced in a file space authorization rule of a and a replication state of ENABLED in order to be
replicated node. The associated replication node replicated from a source server.
defintion will be replicated.
System action: The replication operation continues.
System action: Server operations continue. The replication of the associated node fails.
User response: None. User response: To replicate an associated replication
node set the replication state of the node on the target
ANR3187E Replication of associated replication server to enabled.
node associated replication node name failed
- the node is not configured for ANR3190E Node node name on server server name
replication uses a different primary server for
Explanation: During a REPLICATE NODE operation, replication.
the server attempted to replicate a node that is either a Explanation: When you issued the REPLICATE NODE
proxy agent or referenced in a file space authorization command, the server attempted to replicate a node to
rule of a replicating node. The associated replication another server. However, the other server already has a
node could not be replicated because it is not currently replica of the node from a different primary server.
configured for replication. Associated replication nodes
must have a replication mode set to SEND and a System action: The replication of the node fails. Server
replication state of ENABLED in order to be replicated operation continues.
to a target server.
User response: Issue the RENAME NODE command
System action: The replication operation continues. to rename the node, or issue the REMOVE REPLNODE
The replication of the associated node fails. command to remove the node from replication with the
current primary server.
User response: To use an associated replication node
with a client during a failover operation configure and
enable the associated replication node for replication. ANR3191E Command: The CONTAINER storage
type can only be used with a
POOLTYPE of PRIMARY.
ANR3188E Replication of associated replication
node associated replication node name failed Explanation: An attempt is made to define a
- the node is not enabled for replication POOLTYPE using a storage type of CONTAINER.
Storage pools with a POOLTYPE other than PRIMARY
Explanation: During a REPLICATE NODE operation, can only be assigned to storage pools with a
the server attempted to replicate a node that is either a DEVCLASS storage type.
proxy agent or referenced in a file space authorization

System action: The server does not process the proxy agent node referenced by a replicated node. The
command. proxy agent node defintion will be replicated if the
referencing node is replicated.
sequential device class or ommiting the POOLTYPE. System action: Server operations continue.
ANR3192I Replicate Node: Proxy agent nodes
replicated: proxy nodes replicated of proxy
ANR3195I Identified node associated replication node
nodes found identified. Associated
which is referenced in a file space
authorized nodes replicated: authorized
authorization rule for replicated node
nodes replicated of authorized nodes found
reference node
identified. Client option sets replicated:
option sets replicated of option sets found Explanation: The preview replication process has
identified. completed. The server has identified an associated
replication node that is referenced in a file space
Explanation: The replication process has completed.
authorization rule of a replicated node. The associated
The meanings of the numbers are:
node defintion will be replicated if the referencing node
v Proxy agent nodes are the number of nodes which is replicated.
are identified as proxy agents for any of the nodes
specified in the REPLICATE NODE command. System action: Server operations continue.
v Associated authorized nodes are the number of User response: None.
nodes referenced in file space authorization rules of
any of the nodes specified in the REPLICATE NODE
command. ANR3196E Communication error occurred on
Session session number during import
v Client option sets are the number of option sets from (communication method
which are referenced by any of the nodes specified in communication address).
the REPLICATE NODE command.
Explanation: A communication error occurred during
System action: None. import from another server.
User response: None. System action: The import process is ended.
User response: Determine the cause of the
ANR3193I Replication Preview: Proxy agent nodes communication error and retry the import.
identified: proxy nodes found. Associated
authorized nodes identified: authorized
nodes found. Client option sets identified: ANR3197W command: Replication of authorization
option sets found. rule failed for node node name, filespace
Id filespace id on target server target server
Explanation: The preview replication process has - a duplicate rule exists on the target
completed. The meanings of the numbers are: server.
v Proxy agent nodes are the number of nodes which
are identified as proxy agents for any of the nodes Explanation: A file space authorization rule on this
specified in the REPLICATE NODE command. server could not be replicated to the target server
because an identical rule already exists on the target
v Associated authorized nodes are the number of server.
nodes referenced in file space authorization rules of
any of the nodes specified in the REPLICATE NODE System action: Server operation continues.
command.
User response: A file space which is being replicated
v Client option sets are the number of option sets contains an authorization rule that exists on both the
which are referenced by any of the nodes specified in source and target servers. Determine which
the REPLICATE NODE command. authorization rule should be used on the target server
System action: None. using the QUERY ACCESS command of the IBM
Spectrum Protect client. Once you have decided which
User response: None. authorization rule to use, delete the unneeded
authorization rule using the DELETE ACCESS
command of the IBM Spectrum Protect client.
ANR3194I Identified node associated replication node
as a proxy agent for replicated node
reference node
Explanation: The preview replication process has
completed. The server has identified an associated

ANR3198E command: The server server name ANR3202E command: Domain domain name is a
definition could not be retrieved.The managed object and cannot be updated.
database is in an inconsistent state.
Explanation: The indicated domain is a managed
Explanation: An error occurred while accessing the object and cannot be updated on the managed server.
server information.
System action: The command fails. operation continues.
User response: For details and instructions to resolve User response: To update this object, you can delete
the issue, see Technote 1598476 at http:// the subscription to the configuration profiles with
www.ibm.com/support/entry/portal/. Type 1598476 in which domain domain name is associated.
the Search field.
ANR3203E command: Policy set set name in domain
ANR3199I Server halt for stage stage initiated at domain name is a managed object and
time. cannot be deleted.
Explanation: The server HALT processing is being Explanation: The indicated policy set is a managed
performed and each stage is reported with the time object and cannot be deleted on the managed server.
when that stage was initiated.
System action: None. operation continues.
User response: This message may not be logged to the User response: To delete this object, you can delete
activity log. It is provided for informational purposes the subscription to the configuration profiles with
only. The stages reported are for informational which domain domain name is associated.
purposes and only to denote progress. The sequence
and actual stages to be performed during halt may
ANR3204E command: Policy set set name in domain
vary and as such will cause this not to always report in
domain name is a managed object and
the same fashion. The primary consideration is that the
cannot be updated.
INIT stage and the COMPLETE stage can be used to
calculate the time used to halt the server. These Explanation: The indicated policy set is a managed
messages are only displayed if the halt command is object and cannot be updated on the managed server.
issued with the verbose parameter such as: "HALT
VERBOSE". System action: The command fails and server
ANR3200E command: Command cannot be executed User response: To update this object, you can delete
- domain domain name is a managed the subscription to the configuration profiles with
object. which domain domain name is associated.
Explanation: The specified command cannot be

executed because it would alter the contents of the ANR3205E command: Management class class name in
indicated managed domain. With the exception of domain domain name, policy set set name
policy set activation, a managed domain can only be is a managed object and cannot be
modified using configuration information propagated deleted.
from the configuration manager. Explanation: The indicated management class is a
System action: The command fails and server managed object and cannot be deleted on the managed
operation continues. server.
User response: None. System action: The command fails and server
ANR3201E command: Domain domain name is a User response: To delete this object, you can delete
managed object and cannot be deleted. the subscription to the configuration profiles with
which domain domain name is associated.
Explanation: The indicated domain is a managed
object and cannot be deleted on the managed server.
ANR3206E command: Management class class name in
System action: The command fails and server domain domain name, policy set set name
operation continues. is a managed object and cannot be
updated.
User response: To delete this object, you can delete
the subscription to the configuration profiles with Explanation: The indicated management class is a

managed object and cannot be updated on the managed object and cannot be updated on the
managed server. managed server.
System action: The command fails and server System action: The command fails and server
operation continues. operation continues.
User response: To update this object, you can delete User response: To update this object, you can delete
the subscription to the configuration profiles with the subscription to the configuration profiles with
which domain domain name is associated. which domain domain name is associated.
ANR3207E command: Backup copy group group name ANR3211E command: Client schedule schedule name
in domain domain name, policy set set in domain domain name is a managed
name, management class class name is a object and cannot be deleted.
managed object and cannot be deleted.
Explanation: The indicated client schedule is a
Explanation: The indicated backup copy group is a managed object and cannot be deleted on the managed
managed object and cannot be deleted on the managed server.
server.
System action: The command fails and server operation continues.
User response: To delete this object, you can delete the subscription to the configuration profiles with
the subscription to the configuration profiles with which domain domain name is associated.
ANR3212E command: Client schedule schedule name
ANR3208E command: Archive copy group group name in domain domain name is a managed
in domain domain name, policy set set object and cannot be updated.
name, management class class name is a
Explanation: The indicated client schedule is a
managed object and cannot be updated on the
Explanation: The indicated archive copy group is a managed server.
managed object and cannot be deleted on the managed
server.
User response: To update this object, you can delete
the subscription to the configuration profiles with
User response: To delete this object, you can delete which domain domain name is associated.
ANR3213E command: Administrative schedule
schedule name is a managed object and
ANR3209E command: Backup copy group group name cannot be deleted.
in domain domain name, policy set set
Explanation: The indicated administrative schedule is
a managed object and cannot be deleted on the
managed object and cannot be updated.
managed server.
Explanation: The indicated backup copy group is a
managed object and cannot be updated on the
managed server.
which the object is associated.
User response: To update this object, you can delete
ANR3214E command: Administrative schedule
schedule name is a managed object and
cannot be updated, except to activate or
ANR3210E command: Archive copy group group name deactivate the schedule.
in domain domain name, policy set set
Explanation: The indicated administrative schedule is
a managed object and cannot be updated on the
managed server, except to change the active state of the
Explanation: The indicated archive copy group is a schedule.

System action: The command fails and server managed object and cannot be updated on the
operation continues. managed server.
User response: To update this object, you can delete System action: The command fails and server
the subscription to the configuration profiles with operation continues.
User response: To update this administrator, you can
delete the subscription to the configuration profiles
ANR3215W Managed domain domain name contains with which the object is associated.
at least one node and cannot be
discarded.
ANR3219E command: Administrator administrator
Explanation: This message is issued while processing name is a managed object and cannot be
a DELETE SUBSCRIPTION command with renamed.
DISCARDOBJECTS=YES. The indicated domain cannot
Explanation: The indicated administrator is a
be discarded on the managed server because it still
managed object and cannot be renamed on the
contains one or more nodes.
managed server.
System action: Domain domain name is not deleted.
Policy sets, management classes, copy groups, and
client schedules belonging to this domain are also not
deleted. User response: To rename this administrator, you can
User response: Before this domain can be deleted,
with which the object is associated.
nodes in the domain must be removed or assigned
another domain.
name is a managed object - authority
ANR3216W Managed administrative schedule
cannot be granted.
schedule name is active and cannot be
discarded. Explanation: The indicated administrator is a
managed object. Authority cannot be granted to this
Explanation: This message is issued while processing
administrator on the managed server.
a DELETE SUBSCRIPTION command with
DISCARDOBJECTS=YES. The indicated administrative System action: The command fails and server
schedule cannot be discarded on the managed server operation continues.
because it is in the active state.
User response: To grant authority to this
System action: Administrative schedule schedule name administrator, you can delete the subscription to the
is not deleted. configuration profiles with which the object is
associated.
User response: Before this administrative schedule can
be deleted, it must be deactivated using the Update
Schedule command. ANR3221E command: Administrator administrator
name is a managed object - authority
cannot be revoked.
name is a managed object and cannot be Explanation: The indicated administrator is a
removed. managed object. Authority of this administrator cannot
be revoked on the managed server.
managed object and cannot be removed on the System action: The command fails and server
managed server. operation continues.
System action: The command fails and server User response: To revoke authority of this
operation continues. administrator, you can delete the subscription to the
configuration profiles with which the object is
User response: To remove this administrator, you can
associated.
ANR3222W Managed administrator administrator
name is the only system administrator
and cannot be discarded.
name is a managed object and cannot be
updated. Explanation: This message is issued while processing
DISCARDOBJECTS=YES. The indicated administrator

cannot be discarded on the managed server because it System action: The command fails and server
is the only system administrator. operation continues.
System action: Administrator administrator name is not User response: To rename this script, you can delete
deleted. the subscription to the configuration profiles with
User response: Before this administrator can be
deleted, another administrator must be given system
authority. ANR3227E command: Option set optionset name is a
ANR3223W Managed administrator administrator Explanation: The indicated option set is a managed
name is currently accessing the server object and cannot be deleted on the managed server.
Explanation: This message is issued while processing operation continues.
User response: To delete this option set, you can
DISCARDOBJECTS=YES. The indicated administrator
cannot be discarded on the managed server because it
has an active session with the server.
System action: Administrator administrator name is not
ANR3228E command: Option set optionset name is a
deleted.
User response: Quit or cancel all sessions for this
Explanation: The indicated option set is a managed
administrator before discarding the administrator
object and cannot be updated on the managed server.
definition.
ANR3224E command: Command script command
script name is a managed object and User response: To update this option set, you can
cannot be deleted. delete the subscription to the configuration profiles
Explanation: The indicated command script is a
managed object and cannot be deleted on the managed
server. ANR3229E command: Command cannot be executed
- option set optionset name is a managed
object.
User response: To delete this script, you can delete the
executed because it would alter the contents of the
subscription to the configuration profiles with which
indicated managed option set.
the object is associated.
script name is a managed object and User response: None.
cannot be updated.
Explanation: The indicated command script is a ANR3230E command: Server group group name is a
managed object and cannot be updated on the managed object and cannot be deleted.
managed server.
Explanation: The indicated server group is a managed
System action: The command fails and server object and cannot be deleted on the managed server.
User response: To update this script, you can delete operation continues.
which the object is associated. User response: To delete this server group, you can
script name is a managed object and
cannot be renamed. ANR3231E command: Server group group name is a
Explanation: The indicated command script is a
managed object and cannot be renamed on the Explanation: The indicated server group is a managed
managed server. object and cannot be updated on the managed server.

System action: The command fails and server Alternatively, you can delete the subscription to the
operation continues. configuration profiles with which the object is
associated, so that the server is no longer a managed
User response: To update this server group, you can
object.
ANR3236W Server server name is currently in use
ANR3232E command: Server group group name is a
managed object and cannot be renamed. Explanation: This message is issued while processing
Explanation: The indicated server group is a managed
DISCARDOBJECTS=YES. The indicated server cannot
object and cannot be renamed on the managed server.
be discarded on the managed server because server
System action: The command fails and server name is in use. This could occur if the managed server
operation continues. has an active connection to server name or if the
managed server has a device class with
User response: To rename this server group, you can DEVTYPE=SERVER that refers to server name.
with which the object is associated. System action: Server server name is not deleted.
User response: Before server name can be deleted, the
ANR3233E command: Command cannot be executed managed server must not have a connection to that
- server group group name is a managed server and the managed server cannot have any
object. device-class references to that server.
executed because it would alter the membership of the ANR3237W Server server name is the event server
indicated managed server group. and cannot be discarded.
System action: The command fails and server Explanation: This message is issued while processing
operation continues. a DELETE SUBSCRIPTION command with
DISCARDOBJECTS=YES. The indicated server cannot
User response: None. be discarded because it is the event server for the
managed server.
ANR3234E command: Server server name is a System action: Server server name is not deleted.
Explanation: The indicated server is a managed object DELETE EVENTSERVER command must be used to
and cannot be deleted on the managed server. remove the event server reference to server name.
operation continues. ANR3238E command: This object cannot be renamed
User response: To delete this object, you can delete because it is associated with one or
the subscription to the configuration profiles with more configuration profiles.
which the object is associated. Explanation: This message is issued on a
configuration manager when an attempt is made to
ANR3235E command: Server server name is a rename an object that is associated with one or more
managed object - one or more specified configuration profiles. Associated objects cannot be
attributes cannot be updated. renamed because the enterprise configuration facility
does not support renaming of objects.
Explanation: Because the indicated server is a
managed object, certain attributes cannot be updated System action: The command fails and server
on the managed server. These attributes are: operation continues.
SERVERPASSWORD, HLADDRESS, LLADDRESS, User response: If you must change the object name
COMMMETHOD, DESCRIPTION, URL, and you can delete the object, define it with a new name,
ALLOWREPLACE. and then define a profile association to the new object
System action: The command fails and server (unless a wildcard profile association already exists).
operation continues. This will cause the object to be deleted and re-defined
on managed servers with subscriptions to the profiles
User response: You can restrict the update to with which this object is associated.
attributes that can be updated on the managed server.
For example, the PASSWORD, NODENAME,
FORCESYNC, and DELGRACEPERIOD attributes can
be updated, even if the server is a managed object.

server. Verify that the replication GUID specified is

ANR3239E Error rc while creating device class device
correct for the server you are deleting.
class.
Explanation: This message is issued when a device
ANR3243E command: Replication server server Name
class could not be created, because there was an error
is currently being deleted by a previous
while processing the device configuration file.
Explanation: When you issue the REPLICATE NODE
User response: Look in the device configuration file command, the default replication server is already in
for errors, and look at the activity log for any previous the process of being deleted as a result of a previous
error messages that might help determine the location REMOVE REPLSERVER command.
of these errors in the device configuration file.
System action: The command is stopped by the
server.
ANR3240W The device class device class only has
User response: Issue the QUERY REPLSERVER
number of drives drives while the number
command to verify the current status of the replication
of streams requested is number of streams.
server. Update the default replication server with the
Explanation: This message is issued when a the SET REPLSERVER command.
NUMSTREAM parameter is being specified with a
value higher than the number of drives available to the
ANR3244E Session session number for server server
device class.
name error - replication server is
System action: The command continues. currently being deleted by a previous
User response: The value will be updated as
requested. If the number of drives available at the time Explanation: At the start of a REPLICATE NODE
the database backup is attempted is less than the process on a target server, the replication server is
number of streams, the database backup will be already in the process of being deleted on the target
performed using the number of online drives as the server as a result of a previous REMOVE REPLSERVER
number of streams. For example, if the number of command.
available drives is 2 but the NUMSTREAM value had
been set to 4, than the database backup will be done
server.
using only 2 streams.
ANR3241W The value specified for server option
server. Update the default replication server with the
option 1 is ignored due to the setting of
SET REPLSERVER command.
option option 2.
Explanation: The value specified for the first option is
ignored because the second option takes precedence.
name (client platform) - no failover
System action: The default value of the option is connection information found for server
used. Server operation continues. server name.
User response: Modify the values for one or both of Explanation: During client sign-on, there was no
the server options so that they no longer conflict. failover server connection information stored. This is
Restart the server. caused when you issue the REMOVE REPLSERVER
command on the failover server that is defined in the
associated node definition. No change is made to the
ANR3242E command: Replication server server Name
stored failover server connection information in the
is currently being deleted by a
client option file. The client will fail over to the last
known failover server.
Explanation: When you issue the REMOVE
REPLSERVER command, the replication server that you
specify to remove is already in the process of being User response: No action is needed if the failover
deleted as a result of a previous REMOVE server in the client option file is still valid. Replicate the
REPLSERVER command. node to the default target replication server in order to
update the node's failover server.
server.


ANR3246W Process process ID skipped Num Files
files on volume Volume name because the User response: Check the setting for the
files have been deleted. MOUNTWAITRESOURCELIMIT server option and
increase the value. If the problem persists with a higher
Explanation: Some of the files that were encountered
value, contact your service representative.
during the move operation were skipped because they
have already been deleted.
ANR3250E Command: Directory directory is not
System action: The operation skips the files without
defined in storage pool storage pool.
making copies and continues.
Explanation: A nonexistent storage pool directory is
specified for the issued command.
command.
files on volume Volume name because of
pending fragments. User response: Reissue the command with a valid
storage pool directory. If you are using the MACRO
Explanation: Some of the files that were encountered
command to define and update the storage pool
during the move operation were skipped because they
directory, you must ensure that the DEFINE
contained pending fragments.
STGPOOLDIRECTORY command is committed before
Large files that are stored in deduplication-enabled the UPDATE STGPOOLDIRECTORY command is
storage pools are split into smaller pieces or fragments issued.
for performance reasons. When fragments are copied or
moved to another storage pool, they are marked
ANR3251E Command: Storage pool stgpool name is
pending until all fragments that comprise the file arrive
not a container storage pool.
at the target storage pool. The pending state is removed
from the fragments once all fragments have been Explanation: The storage pool specified is invalid for
successfully moved. the command.
System action: The operation skips the files without System action: The server does not process the
making copies and continues. command.
User response: Server processes such as BACKUP User response: Reissue the command with a valid
STGPOOL, MOVE DATA, MOVE NODEDATA and storage pool. Only container storage pools may be used
storage pool migration can result in fragments being with STGPOOLDIRECTORY commands.
marked as pending. You can issue the QUERY
PROCESS command to see whether any of the
processes are running. If so, retry the operation at a ANR3252E Command: Directory directory is already
later time when the fragments are not pending. defined in storage pool storage pool.
Explanation: An already existing storage pool
ANR3248W Process process ID skipped Num Files directory is specified for the issued command.
files on volume Volume name because it System action: The server does not process the
was unable to lock all segments. command.
Explanation: The files were skipped because the User response: Reissue the command with a valid,
process was unable to lock all segments of the files. unique storage pool directory.
System action: The operation skips the files without
making copies and continues. ANR3253W A client operation that was started by
User response: Retry the operation. schedule schedule name is running longer
than the maximum run time expected
for client node name.
ANR3249W The process desc process with process ID
process id is canceled by the process Explanation: When you defined or updated the
monitor. schedule, you set a maximum run time for client
operations that are associated with the schedule.
Explanation: The process is canceled because the Alternatively, in the Operations Center, you set an end
mount wait time for the input or output volume has time for the client operations. A client operation started
exceeded the mount wait limit that is set through the as scheduled, but the operation is running after the end
MOUNTWAITRESOURCELIMIT server option. Either time or for longer than the maximum run time.
there is a problem with a mount point, or the mount
wait limit is set too low. System action: The server issues this warning
message, and the client operation continues.

User response: None. not on the IBM Spectrum Protect server that is being
backed up and that the names of the source and target
servers are unique.
ANR3254I Storage pool directory storage pool
directory name was defined in storage
pool stgpool name. ANR3259W Session session number for node node
name (client platform) refused -
Explanation: A DEFINE STGPOOLDIRECTORY
$$_TSMDBMGR_$$ node from an
command has created the storage pool directory
untrusted system is not allowed.
indicated of the storage pool shown.
Explanation: The server refuses the specified client
session because node $$_TSMDBMGR_$$ is allowed
User response: None. only from the trusted system for IBM Spectrum Protect
database backup or restore.
ANR3255I Storage pool directory storage pool System action: Server processing continues.
directory name deleted.
User response: Use $$_TSMDBMGR_$$ node from the
Explanation: A DELETE STGPOOLDIRECTORY trusted system for IBM Spectrum Protect database
command has deleted the storage pool directory backup or restore.
indicated.
System action: None. ANR3260E Database backup terminated due to a
page validation failure that occurred
User response: None. during a backup - DB2 sqlcode sqlcode
sqlerrmc sqlerrmc. This might indicate
ANR3256I Storage pool directory storage pool corruption in the database, requiring a
directory name updated. database restore or other repair action to
correct.
Explanation: An UPDATE STGPOOLDIRECTORY
command has updated the storage pool directory Explanation: A page validation error was detected by
indicated. DB2 and the error caused the database backup to fail.
System action: None. System action: If a full database backup was in

progress to free space in the archive log directory, take
User response: None. one of the following actions:
v Increase the amount of space in the archive log
ANR3257W command: Filespace identifier fsId is not directory.
defined for node node name. v Use the ARCHFAILOVERLOGDIRECTORY option to
Explanation: A filespace identifier specified in the specify a failover archive log directory in which the
REPLICATE NODE command is not defined for the server can store log files that cannot be stored in the
indicated node. archive log directory.
System action: The replication operation continues for For assistance in diagnosing and repairing any database
any other valid filespace identifiers specified. corruption, contact IBM Software Support.
User response: Use the QUERY FILESPACE command
to verify the list of filespace identifiers provided in the ANR3261W An automatic full or incremental
REPLICATE NODE command. database backup will be started. The
active log space used is log space used is
ANR3258E Command: Device class device class name megabytes, and the active log space
has a device type of SERVER and the available is log space available megabytes.
source server name is the same as the The ratio, active log used ratio, exceeds the
target. threshold log utilization threshold.
Explanation: The specified device class has a device Explanation: When the active log space used exceeds
type of SERVER and the source and target server the log utilization threshold, a database backup is
names are the same. IBM Spectrum Protect server started. If there has been at least one full database
database backups cannot be restored from virtual backup, the backup is an incremental database backup.
volumes that are on the same IBM Spectrum Protect Otherwise, a full database backup is started.
server that was used to complete the backups. System action: None.
System action: Processing stops. User response: None.
User response: Ensure that the virtual volumes are

ANR3262W A full database backup might be ANR3266E Replication of node node name to target
required. The last log number used is replication server target server failed. The
last log used and the first log number reason is that a required policy domain
used is first log used. The log file size is is not defined on the target server.
log file size megabytes. The maximum log
Explanation: If you plan to replicate a node, but the
file size is maximum log file size
node does not exist on the target server, you must
megabytes.
ensure that an appropriate policy domain is defined for
Explanation: When the log space used since the last the node on the target server.
database backup exceeds the maximum log file size,
System action: The data that belongs to the node was
either a full database backup is required, or the
not replicated, but server operations continue.
maximum log file size must be increased.
User response: To replicate the node, take one of the
following actions:
User response: None. v Define the policy domain that is used for the node
on the source server to the target server.
ANR3263E Command: The CLOUD storage type can v Define the STANDARD policy domain on the target
only be used with a POOLTYPE of server.
PRIMARY.
Then, restart the node replication process.
Explanation: An attempt is made to define a
POOLTYPE using a storage type of CLOUD. Storage
pools with a POOLTYPE other than PRIMARY can only ANR3267E The storage pool stgpool name cannot be
be assigned to storage pools with a DEVCLASS storage defined as a container storage pool with
type. this operating system.
System action: The server does not process the Explanation: The command cannot be processed on
command. this operating system.
User response: Reissue the command specifying a System action: The server does not process the
sequential device class or ommiting the POOLTYPE. command.
User response: Use an operating system that is
ANR3264W A full database backup is needed. The compatible with IBM Spectrum Protect to issue the
active log space used is log space used is command. For information about operating systems
megabytes, and the active log space that are supported by IBM Spectrum Protect, see
available is log space available megabytes. technote 1243309 "Overview - IBM Spectrum Protect
The ratio, active log used ratio, exceeds the Supported Operating Systems" (http://www-
threshold log utilization threshold. 01.ibm.com/support/docview.wss?uid=swg21243309).
Explanation: When the active log space used exceeds
the log utilization threshold, a database backup is ANR3268W Storage pool directory storage pool
needed. directory name access failed.
System action: None. Explanation: The server was unable to access the
specified storage pool directory. Either the file system is
not available or permissions to the storage pool
directory prevent access.
ANR3265W A full database backup will be started.
The archive log space used is archive
command.
log% and the archive log space used
threshold is arch log threshold%. User response: Verify that the underlying file system
is mounted correctly and is available. Verify that the
Explanation: When the archive log space used exceeds
server has full access permissions to the storage pool
the threshold, a full database backup will be started.
directory.
User response: None. ANR3269E Command: Storage pool access mode for
pool pool name cannot be changed from
UNAVAILABLE because the master
encryption key is not available.
Explanation: The storage pool access mode cannot be
changed because the pool is encrypted or contains

encrypted data, and the server master encryption key is User response: None.
not available.
System action: The server does not process the ANR3274I Running in LDAP Legacy Mode.
command.
Explanation: The Server is running in LDAP Legacy
User response: Review the activity log for errors Mode which requires an LDAP Administrator ID and
related to either the server master encryption key or the an Organizational Unit which is specific to the server.
server password file. Correct any problems that prevent
the master encryption key being read from the server
password file. If necessary, ename the server password User response: None.
file, dsmserv.pwd, and recover an earlier version of the
password file from a backup. Restart the server. Reissue
the UPDATE STGPOOL command to change the ANR3275I Running in LDAP Integrated Mode.
storage pool ACCESS setting. Explanation: The Server is running in LDAP
Integrated Mode which allows existing LDAP users to
ANR3270E Command: Unsupported option - option be registered to the server while managed through the
LDAP server.
Explanation: The command shown specifies a client
option for a client option set, which is no longer System action: Server operation continues.
supported. User response: None.
command. ANR3300W The FILELIST file named list file name
User response: Reissue the command with a valid does not contain any valid directories.
client option. Explanation: The server detected that the FILELIST
file does not contain any valid directories.
ANR3271W Command: Deprecated option - option System action: The RESTORE DB operation fails.
Explanation: The command shown specifies a User response: Update the FILELIST file to include at
deprecated client option for a client option set. While least one valid directory.
the specified option will be processed, it will be made
obsolete at a future date.
ANR3301E The EXTEND DBSPACE failed because
System action: The server processes the command. database backup processing is active.
User response: Be prepared to remove the client Explanation: The database backup and EXTEND
option from the client option set in the future. DBSPACE processing are in conflict and cannot be
active simultaneously.
ANR3272E Server server name does not support System action: The EXTEND DBSPACE operation
replication using fasp as the transfer failed and is terminated.
method.
User response: Rerun the EXTEND DBSPACE after
Explanation: In response to a REPLICATE command, the database backup completes.
the server attempted to establish a connection to the
replication target. But the target server does not
support fasp as the transfer method. ANR3302E The database backup failed because
EXTEND DBSPACE processing is active.
replication fails. Explanation: The database backup and EXTEND
DBSPACE processing are in conflict and cannot be
User response: Make sure the replication target is at active simultaneously.
the correct maintenance level and verify that the
globally unique ID (GUID) of the target server is System action: The database backup operation failed
properly set. Use the tivguid utility to set the GUID if and is terminated.
not properly set. User response: Rerun the database backup after
EXTEND DBSPACE processing completes.
ANR3273I Using Active Directory Domain LDAP
DN for LDAP Authentication.
Explanation: The Active Directory Domain was
determined from the LDAP server base context.

1. The node is currently replicating.

ANR3337I Option option value added to server
options file. 2. The cleanup replgroups process is cancelled.
3. Unexpected internal errors, which can be displayed
Explanation: The indicated option and value were
the activity log.
written to the server options file as part of the set of
options needed to secure communication at TLS level System action: The command terminates.
1.2 or higher. When the server key data base is created,
this set of options is written to the server options file; User response: Review the activity log for errors.
These options are in effect immediately, as part of the Correct the error and issue the command again.
startup process.
System action: Server operation continues. ANR3341I Process process ID was started to
decommission node name.
User response: All clients contacting the server after
the server comes up and which use SSL/TLS Explanation: When you run the DECOMMISSION
communications should be configured to use TLS 1.2. NODE command, a process is started to prepare the
Clients using the server self-signed certificate should node for decommissioning and deactivating backup
have the server exported certificate file, cert256.arm files for the node.
added to their key data base. If TLS 1.2 is not suitable System action: The Decommission process can be
for SSL communications, the following options in the canceled. Server operation continues.
server options file should be modified: SSLTLS12 (if
present), SSLDISABLELEGACYTLS, and User response: No action is required. However, you
SSLHIDELEGACYTLS should be changed to NO. You can query the process by using the QUERY PROCESS
may also have to change the default label in the command: query process process_number You can
server's key data base, if using self-signed certificates, cancel the process by using the CANCEL PROCESS
to "TSM Server SelfSigned Key". command: cancel process process_number
ANR3338E Session with node or system at address ANR3342I The process of decommissioning a node
hladdress failed due to use of TLS at was canceled.
level SSL Level instead of TLS 1.2 or Explanation: The CANCEL PROCESS command was
higher. issued to end the process of decommissioning a node.
Explanation: When server or storage agent option The process will end shortly.
SSLDISABLELEGACYTLS is set to yes, the server System action: The decommission process will end,
enforces a TLS level of 1.2 or higher. If TLS is at a level but server operation continues.
lower than 1.2 or any level of SSL is used, the session
fails. User response: No action is required.
System action: The session fails. Server or storage

agent operation continues. ANR3344E Command: An error occurred while
deactivating data for node name.
User response: All clients contacting the server or
storage agent that is rejecting sessions with this Explanation: An error occurred while deactivating
message should be re-configured to use TLS 1.2. backup files for the specified node.
System action: The DEACTIVATE DATA command is
ANR3339I Default Label in key data base is Label. ended, but server operation continues.
Explanation: The default SSL label in the key data User response: No action is required.
base is displayed.
System action: Server or storage agent operation ANR3345I Process process ID was started to
continues. deactivate data for node name.
User response: None. Explanation: When you run the DEACTIVATE DATA
command, a process begins to prepare the node for
deactivation of its active backup files.
ANR3340W The CLEANUP REPLGROUPS
command failed or some records were System action: The deactivation process can be
skipped. Issue the command again to canceled. Server operation continues.
clean up orphan records. User response: No action is required. However, you
Explanation: The cleanup replgroups process may can query the process by using the QUERY PROCESS
skip orphan records from being deleted. Some common command: query process process_number You can
reasons for this error are: cancel the process by using the CANCEL PROCESS
command: cancel process process_number

ANR3346I A process to deactivate backup files for ANR3351W Managed domain domain name contains
a node was canceled. at least one node and cannot be deleted
during configuration refresh processing.
Explanation: Cancellation is in progress. The process
will end shortly. Explanation: During configuration refresh processing,
the enterprise configuration facility attempted to
System action: The process for deactivating backup
remove the indicated domain because it has been
files is ending, but server operation continues.
deleted from the configuration manager or because the
User response: No action is required. profile association no longer exists. The domain could
not be deleted on the managed server because it still
contains one or more nodes.
ANR3348E Command: The process of deactivating
data for node name failed. System action: Refresh processing continues, but this
domain is not deleted. The system will attempt to
Explanation: An error occurred while deactivating delete the domain during later configuration refresh
backup files for the specified node. operations.
System action: The DEACTIVATE DATA command is User response: Assign nodes in this domain to
ended, but server operation continues. another domain. Alternatively, you can delete the
User response: No action is required. subscription to the profiles with which domain domain
name is associated.
ANR3349W Command: This command will deactivate

data. Active backup files that were ANR3352I Locally defined domain domain name
created for the specified node on the replaced during configuration refresh
deactivation date or earlier will be processing.
deactivated. Explanation: During configuration refresh processing,
Explanation: The DEACTIVATE DATA command a local domain definition was replaced with a
deactivates backup files for a specified node. definition from the configuration manager. The system
also deleted all policy sets, management classes, copy
System action: You will be prompted to continue, or groups, and client schedules belonging to the locally
to cancel the command. defined domain and added definitions from the
User response: Enter 'Y' to continue or 'N' to end the configuration manager.
ANR3350W Locally defined domain domain name
contains at least one node and cannot be
replaced with a definition from the ANR3353I Managed domain domain name deleted
configuration manager. during configuration refresh processing.
Explanation: During configuration refresh processing Explanation: During configuration refresh processing,
the indicated locally defined domain could not be the indicated managed domain was removed from the
replaced with a definition from the configuration managed server. This occurred either because the
manager. The domain definition was not replaced domain has been deleted from the configuration
because the domain still contains one or more assigned manager or because the profile association no longer
nodes. exists. The system also deleted all policy sets,
management classes, copy groups, and client schedules
System action: Refresh processing continues, but this belonging to the managed domain.
domain is not replaced. The system will attempt to
replace the local domain during later configuration System action: None.
refresh operations. User response: None.
User response: If you want existing nodes to be
assigned to the domain from the configuration ANR3354W Locally defined administrative schedule
manager, you can temporarily assign them to another schedule name is active and cannot be
domain. After the domain definition has successfully replaced with a definition from the
been propagated from the configuration manager, configuration manager.
reassign the nodes to the new domain. Alternatively, if
you want to prevent further attempts to replace the Explanation: During configuration refresh processing
local domain definition during configuration refresh the indicated locally defined administrative schedule
processing, delete the subscription to the profiles with could not be replaced with a definition from the
which domain domain name is associated. configuration manager. The schedule definition was not
replaced because the schedule is in the active state.

System action: Refresh processing continues, but this removed from the managed server. This occurred either
administrative schedule is not replaced. The system because the schedule has been deleted from the
will attempt to replace the local administrative configuration manager or because the profile
schedule during later configuration refresh operations. association no longer exists.
User response: If you want this administrative System action: None.
schedule to be replaced with the schedule definition
from the configuration manager, deactivate the local
schedule using the Update Schedule command. After
the administrative schedule definition has successfully ANR3358W Locally defined administrator
been propagated from the configuration manager, you administrator name is the only system
can activate the new schedule. Alternatively, if you administrator and cannot be replaced
want to prevent further attempts to replace the local with a definition from the configuration
schedule definition during configuration refresh manager.
processing, delete the subscription to the profiles with
which the schedule name is associated. Explanation: During configuration refresh processing
the indicated locally defined administrator could not be
replaced with a definition from the configuration
ANR3355W Managed administrative schedule manager. The administrator definition was not replaced
schedule name is active and cannot be because it is the only system administrator and the
deleted during configuration refresh definition from the configuration manager does not
processing. include system authority.
Explanation: During configuration refresh processing, System action: Refresh processing continues, but this
the enterprise configuration facility attempted to administrator definition is not replaced. The system
remove the indicated administrative schedule because it will attempt to replace the local administrator
has been deleted from the configuration manager or definition during later configuration refresh operations.
because the profile association no longer exists. The
schedule could not be deleted on the managed server User response: If you want this administrator
because the schedule is in the active state. definition to be replaced with a definition from the
configuration manager, you can grant system authority
System action: Refresh processing continues, but this to another administrator. Alternatively, if you want to
schedule is not deleted. The system will attempt to prevent further attempts to replace the local
delete the administrative schedule during later administrator definition during configuration refresh
configuration refresh operations. processing, delete the subscription to the profiles with
which administrator administrator name is associated.
User response: If you want this administrative
schedule to be deleted in accordance with changes that
have been made on the configuration manager, ANR3359W Managed system administrator
deactivate the managed schedule using the Update administrator name is the only system
Schedule command. Alternatively, if you want to administrator and cannot be deleted
prevent further attempts to delete the managed during configuration refresh processing.
schedule definition during configuration refresh
processing, delete the subscription to the profiles with Explanation: During configuration refresh processing,
which the schedule name is associated. the enterprise configuration facility attempted to
remove the indicated administrator because it has been
ANR3356I Locally defined administrative schedule profile association no longer exists. The administrator
schedule name replaced during could not be deleted on the managed server because it
configuration refresh processing. is the only system administrator.
Explanation: During configuration refresh processing, System action: Refresh processing continues, but this
a local administrative schedule definition was replaced administrator is not deleted. The system will attempt to
with a definition from the configuration manager. delete the administrator during later configuration
refresh operations.
User response: Grant system authority to another
administrator. Alternatively, you can delete the
subscription to the profiles with which administrator
ANR3357I Managed administrative schedule administrator name is associated.
schedule name deleted during
configuration refresh processing.
Explanation: During configuration refresh processing,
the indicated managed administrative schedule was

System action: Refresh processing continues, but this

ANR3360W Managed system administrator
administrator is not deleted. The system will attempt to
administrator name is the only system
delete the administrator during later configuration
administrator - authority cannot be
refresh operations.
revoked during configuration refresh
processing. User response: Quit or cancel all sessions for the
indicated administrator. Alternatively, you can delete
the subscription to the profiles with which
the enterprise configuration facility attempted to revoke
administrator administrator name is associated.
authority for the indicated administrator because
authority has been revoked on the configuration
manager. The authority of the administrator could not ANR3364W Administrator administrator name has
be revoked on the managed server because this is the been removed. This administrator has
only system administrator. defined or updated administrative
schedules that will fail when executed.
System action: Refresh processing continues, but
authority is not revoked for this administrator. The Explanation: This message is issued during
system will attempt to revoke administrator during configuration refresh processing or as a result of a
later configuration refresh operations. DELETE SUBSCRIPTION command with the
DISCARDOBJECTS=YES option. The indicated
User response: Grant system authority to another
managed administrator was removed from the server,
administrator. Alternatively, you can delete the
but this administrator owns one or more administrative
subscription to the profiles with which administrator
schedules. These schedules will fail when executed in
administrator name is associated.
the future because they do not belong to a valid
administrator.
ANR3361I Locally defined administrator
System action: The indicated administrator was
administrator name replaced during
removed.
configuration refresh processing.
User response: Use the QUERY SCHEDULE command
OR an SQL SELECT statement on the
a local administrator definition was replaced with a
ADMIN_SCHEDULES table to determine which
definition from the configuration manager.
schedules were last updated by the administrator. Use
System action: None. the UPDATE SCHEDULE command to update those
execute them, or use the DELETE SCHEDULE
command to remove the schedules.
ANR3362I Managed administrator administrator
name deleted during configuration
ANR3365I Locally defined command script
refresh processing.
command script name replaced during
Explanation: During configuration refresh processing, configuration refresh processing.
the indicated managed administrator was removed
from the managed server. This occurred either because
a local command script definition was replaced with a
the administrator has been deleted from the
configuration manager or because the profile
association no longer exists. System action: None.
System action: None. User response: None.
ANR3366I Managed command script command script
name deleted during configuration
ANR3363W Managed administrator administrator
refresh processing.
name is currently accessing the server
and cannot be deleted during Explanation: During configuration refresh processing,
configuration refresh processing. the indicated managed command script was removed
from the managed server. This occurred either because
the script has been deleted from the configuration
the enterprise configuration facility attempted to
manager or because the profile association no longer
remove the indicated administrator because it has been
exists.
profile association no longer exists. The administrator System action: None.
could not be deleted on the managed server because it
currently has an active session with the server.

definition with the same name already exists on the

ANR3367I Locally defined option set option set name
managed server.
replaced during configuration refresh
processing. System action: Refresh processing continues, but this
server group is not defined. The system will attempt to
define the server group during later configuration
a local option set definition was replaced with a
refresh operations.
User response: You can delete the subscription to the
profile with which the indicated server group is
User response: None. associated or delete the conflicting server definition on
the managed server. Alternatively, you can rename the
server group on the configuration manager, after first
ANR3368I Managed option set option set name
deleting the profile association for that server group.
deleted during configuration refresh
processing.
ANR3372I Locally defined server server name
replaced during configuration refresh
the indicated managed option set was removed from
processing.
the managed server. This occurred either because the
option set has been deleted from the configuration Explanation: During configuration refresh processing,
manager or because the profile association no longer a local server definition was replaced with a definition
exists. from the configuration manager.
ANR3369I Locally defined server group group name ANR3373I Server server name deleted during
replaced during configuration refresh configuration refresh processing.
processing.
Explanation: During configuration refresh processing, the definition for managed object server name was
a local server group definition was replaced with a removed from the managed server. This occurred either
definition from the configuration manager. because server name has been deleted from the
configuration manager or because the profile
association no longer exists.
ANR3370I Managed server group group name
deleted during configuration refresh
processing. ANR3374I Server group group name replaced with
server server name during configuration
refresh processing.
the indicated managed server group was removed from
the managed server. This occurred either because the Explanation: During configuration refresh processing,
server group has been deleted from the configuration a server group definition was replaced with a server
manager or because the profile association no longer definition from the configuration manager. The server
exists. has the same name as the deleted server group.
ANR3371W Server group group name cannot be ANR3375W Server server name is currently in use
defined during configuration refresh cannot be deleted during configuration
processing because a server already refresh processing.
exists with this name.
Explanation: During configuration refresh processing, the enterprise configuration facility attempted to
the enterprise configuration facility attempted to define remove the indicated server definition because it has
the indicated server group on a managed server. The been deleted from the configuration manager or
server group could not be defined because a server because the profile association no longer exists. The
indicated server could not be deleted on the managed

server because server name is in use. This could occur if

ANR3378I Administrator administrator name added
the managed server has an active connection to server
during configuration refresh processing.
name or if the managed server has a device class with
DEVTYPE=SERVER that refers to server name. Explanation: During configuration refresh processing,
the indicated administrator definition was created
System action: Refresh processing continues, but this
based on information from the configuration manager.
server definition is not deleted. The system will attempt
to delete the server during later configuration refresh System action: None.
operations.
managed server must not have a connection to that
ANR3379E Command: Unable to access pool pool
server and the managed server cannot have any
name - access mode is set to "read only".
device-class references to that server.
Explanation: The command shown specifies the pool
whose name is displayed, but the pool cannot be
ANR3376W Server server name is the event server
accessed because its status is read only.
and cannot be deleted during
configuration refresh processing. System action: The server does not process the
command.
the enterprise configuration facility attempted to User response: Either reset the access state of the pool
remove the indicated server definition because it has or choose another pool and reissue the command.
been deleted from the configuration manager or
because the profile association no longer exists. The
indicated server could not be deleted on the managed ANR3380E Command: Unable to access pool pool
server because it is the event server for the managed name - access mode is set to
server. "unavailable".
System action: Refresh processing continues, but this Explanation: The command shown specifies the pool
server definition is not deleted. The system will attempt whose name is displayed, but the pool cannot be
to delete the server during later configuration refresh accessed because its status is unavailable.
operations. System action: The server does not process the
User response: Before server name can be deleted, the command.
DELETE EVENTSERVER command must be used to User response: Either reset the access state of the pool
remove the event server reference to server name. or choose another pool and reissue the command.
ANR3377W Replacement of local server server name ANR3381W This command will remove
with a definition from the configuration administrator user ID. This administrator
manager is not allowed. is defined to alert triggers or assigned to
Explanation: During configuration refresh processing, alerts. The command will remove the
the enterprise configuration facility attempted to administrator from those alert triggers
replace the indicated server definition with a definition and alerts.
from the configuration manager. This operation could Explanation: A REMOVE ADMINISTRATOR
not be performed because ALLOWREPLACE=NO for command was issued for the specifie d administrator. If
the indicated server. you confirm the command, the administrator will be
System action: Refresh processing continues, but this removed from the alert triggers and alerts.
server definition is not replaced. The system will System action: The system will run or cancel the
attempt to replace the server definition during later command, depending on your response.
configuration refresh operations.
User response: To run the REMOVE
User response: Before the local server definition for ADMINISTRATOR command, enter 'Y'. To cancel the
server name can be replaced with a definition from the command, enter 'N'. To find the alert triggers to which
configuration manager, the UPDATE SERVER the administrator is defined, use the QUERY
command must be used to set the ALLOWREPLACE ALERTTRIGGER command or an SQL SELECT
attribute to ON. statement on the TSM_MON_ALERTTRIG table. To
find the alerts that are assigned to the administrator,
use the QUERY ALERTSTATUS command or an SQL
SELECT statement on the TSM_MON_ALERT table. To
update the alert triggers and modify the list of
administrators who receive an email for the alerts, use

the UPDATE ALERTTRIGGER command. To assign the

ANR3385E command: The operation is not allowed
alert to another administrator, use the UPDATE
for container storage pools.
ALERTSTATUS command.
Explanation: The specified storage pool is a container
storage pool. You cannot issue the following commands
ANR3382W This command will rename
with container storage pools:
administrator user ID. This administrator
is defined to alert triggers or assigned to v BACKUP STGPOOL
alerts. If this administrator is renamed, v RESTORE STGPOOL
the administrator of the alert triggers v MIGRATE STGPOOL
and alerts will also be renamed.
v IDENTIFY DUPLICATES
Explanation: A RENAME ADMINISTRATOR v RECLAIM STGPOOL
command was issued for an administrator who is
v AUDIT VOLUME
defined to alert triggers or assigned to alerts. If you
confirm this command, the administrator for those alert v MOVE NODEDATA
triggers and alerts will be renamed. v MOVE DATA
System action: The system will run or cancel the v RESTORE VOLUME
command, depending on your response. v PREPARE
User response: To run the RENAME You must use a primary random, primary sequential,
ADMINISTRATOR command, enter 'Y'. To cancel the copy, or active-data storage pool to complete these
command, enter 'N'. To review alerts that are assigned functions.
to the administrator, use the QUERY ALERTSTATUS
command. To manage alerts that are assigned to the System action: The command fails and the server
administrator, use the UPDATE ALERTSTATUS operation continues.
command. To review alert triggers, use the QUERY User response: Issue the PROTECT STGPOOL
ALERTTRIGGER command. To update alert triggers, command to protect the contents of directory-container
use the UPDATE ALERTTRIGGER command. storage pools.
ANR3383E command: Administrator user ID is the ANR3386E Insufficient authority to create file
monitoring administrator and cannot be system object object name.
removed or renamed.
Explanation: An attempt to create a file or directory
Explanation: Because the specified administrator is failed with insufficient authority.
used for communications between hub and spoke
servers, the administrator cannot be removed or System action: The operation fails and server
renamed. operations continue.
System action: The command fails, and server User response: Check the permissions of the directory
operation continues. leading up to the object being created. Ensure the
userid under which the server is executing has the
User response: To remove or rename the necessary permission to create objects in this directory.
administrator, complete the following steps: 1. Issue the Retry the operation.
SET ALERTMONITORINGADMIN command to change
the monitoring administrator for your hub server and
for corresponding spoke servers. 2. Remove or rename ANR3387W Command: This command will add,
the administrator. update, or delete alert triggers.
Explanation: A command has been issued that will
ANR3384E command: Server group group name, is the add, update, or delete alert triggers on your server.
monitored server group and cannot be System action: You will be prompted to continue, or
deleted or renamed. to cancel the command.
Explanation: The specified server group is in use as User response: Enter 'Y' to continue or 'N' to end the
the monitored server group and cannot be deleted or command.
renamed.
System action: The command fails and server ANR3388W Command: This command
operation continues. decommissions the client node and
User response: Use the SET deletes data. Active files are deactivated,
MONITOREDSERVERGROUP command to remove it and data is deleted as it expires.
as the monitored server group. Then you can delete or
rename the server group.

Explanation: A command has been issued that will

ANR3392W Command: This command will
decommission the node.
decommission the specified virtual
System action: You will be prompted to continue, or machine. The active files that belong to
to cancel the command. the virtual machine will be inactivated,
and the file space of the virtual machine
User response: Enter 'Y' to continue or 'N' to end the will be automatically deleted after its all
command. the files are expired.
Explanation: A command was issued to remove the
ANR3389E Command: Node name is already specified virtual machine from the production
decommissioned. environment.
Explanation: You cannot decommission the node System action: You will be prompted to continue, or
because it is already decommissioned with to cancel the command.
decommission state YES.
User response: Enter 'Y' to continue or 'N' to cancel
System action: The server does not process the the command.
command.
User response: You can use QUERY NODE ANR3393E Command: Virtual machine virtual machine
FORMAT=DETAIL command to see the decommission name in node name is already
state of the node and the date it was decommissioned. decommissioned.
You can reissue the command on a node that does not
have decommissioned state of Yes. Explanation: The specified virtual machine cannot be
decommissioned because it already has a decommission
state of Yes.
ANR3390W Alert trigger message number is no longer
valid and will be deleted. System action: The virtual machine remains
decommissioned and server operation continues.
Explanation: The alert trigger is obsolete because it is
associated with a server message that no longer exists. User response: To view the date when the virtual
machine was decommissioned, issue the following
System action: The alert trigger will be automatically command: query filespace format=detailed To
deleted by the server. Server operation continues. decommission a different virtual machine, reissue the
User response: No action is required. DECOMMISSION VM command for that virtual
machine.
ANR3391E command: The operation is not allowed

for cloud storage pools. ANR3394I Process process ID was started to
decommission virtual machine virtual
Explanation: The specified storage pool has a cloud machine name on node name.
storage type. You cannot issue the following commands
with cloud storage pools: Explanation: When you run the DECOMMISSION VM
command, a process is started to prepare the virtual
v BACKUP STGPOOL
machine for the decommission operation and to
v RESTORE STGPOOL deactivate backup files for the virtual machine.
v MIGRATE STGPOOL
System action: The decommission process is in
v IDENTIFY DUPLICATES progress.
v RECLAIM STGPOOL
User response: No action is required. However, you
v PREPARE can query the process by using the QUERY PROCESS
You must use a primary random, primary sequential, command: query process process_number You can
copy, or active-data storage pool to complete these cancel the process by using the CANCEL PROCESS
functions. command: cancel process process_number
System action: The command fails and the server

operation continues. ANR3395I The process of decommissioning a
virtual machine was canceled.
User response: To back up a storage pool that uses a
DEDUP device class, issue the PROTECT STGPOOL Explanation: The CANCEL PROCESS command was
command to protect the contents of the storage pool. issued to end the decommission operation. The
operation will end shortly.
System action: The decommission operation will end,
but server operation continues.


ANR3401I Command: Output stream stream did not
write to any output volumes.
ANR3397E Command: An error occurred while
Explanation: The specified output stream did not
deactivating data for virtual machine
write to any output volumes.
virtual machine name.
Explanation: An error occurred while deactivating
backup files for the specified virtual machine. User response: None.
System action: The DECOMMISSION VM command
halts, but server operation continues. ANR3402I Extractdb command: Process process
number, database extract, has completed.
User response: No action is required. However, to
resolve the issue, review the dsmffdc.log and Explanation: The database extract process process
dsmserv.err files and correct any reported errors. number has completed.
System action: Database extract processing ends.
ANR3398E Command: File space FSID could not be
found.
Explanation: The file space ID is not valid.
ANR3403I Extractdb command: Found number of
System action: The server does not process the database objects database objects.
command, but server operation continues.
User response: To resolve the issue, complete the of database objects that were found during database
following steps: 1. To obtain the file space ID of the extract processing.
virtual machine, issue the following command: query
filespace 2. Reissue the command on the virtual
machine. User response: None.
ANR3399E Command: Virtual machine virtual machine ANR3404I Extractdb command: Processed number of
name could not be found. database objects database objects.
Explanation: The command failed because the virtual Explanation: This message indicates the total number
machine name is invalid. of database objects that were successfully processed
during database extract processing.
command, but server operation continues. System action: Server processing continues.
User response: To resolve the issue, complete the User response: None.
following steps: 1. Issue the following command: select
* from filespaceview 2. To determine the name of the
virtual machine, review the output: - If the ANR3405I Extractdb command: Skipped number of
ENTITYNAME field is not blank, the name in the field database objects empty database objects.
is the virtual machine name. - If the ENTITYNAME Explanation: This message indicates the total number
field is blank, go to the FILESPACE_NAME field to of database objects that were skipped during database
determine the name of the virtual machine. 3. Reissue extract processing because they contained no records.
the command on the virtual machine.
ANR3400I Command: Output stream stream used User response: None.

volume volume name.
Explanation: The specified output stream used the ANR3406I Extractdb command: Failed to process
specified volume. number of database objects database
objects.
User response: None. of database objects that were not successfully processed

User response: Refer to the target server's messages

ANR3407I Extractdb command: Processed number of
for a description of the error. Correct the error and
database records database records.
rerun the command.
of database records that were successfully extracted
ANR3413W Extractdb command: Encountered an
unexpected table, table name. The table
System action: Server processing continues. will be skipped.
User response: None. Explanation: The database extract process encountered
a table that it did not expect. In most cases, an
unexpected table is one that was used in an earlier
ANR3408I Extractdb command: Wrote number of bytes
release, but which is no longer used in the current
bytes.
release. Such tables can be safely ignored by the
Explanation: This message indicates the total number database extract process. However, in rare cases, this
of bytes that were successfully written during database may indicate a programming error. As such, you
extract processing. should contact your service representative to confirm
whether the table may be ignored without affecting the
System action: Server processing continues. success of the upgrade process.
User response: None. System action: Database extract processing continues.
Data from the specified table is not extracted.
ANR3409I Extractdb command: Elapsed time was User response: Contact your service representative to
elapsed time. confirm whether the specified table can be safely
Explanation: This message indicates the total amount ignored.
of time that elapsed during database extract processing.
System action: Server processing continues. ANR3414E Extractdb command: Process process
number, database extract, has completed
User response: None. with errors.
Explanation: The database extract process process
ANR3410I Extractdb command: Throughput was number has completed, but errors were encountered by
megabytes per hour megabytes per hour. the process.
Explanation: This message indicates the total System action: Database extract processing ends.
throughput (megabytes/hour) during database extract
processing. User response: Review any messages that were issued
by the process, and take corrective action as
System action: Server processing continues. appropriate.
ANR3415I The server is in maintenance mode.
ANR3411I Extractdb command: Extracted number of Explanation: The server is in maintenance mode. The
database records database entries and following services are disabled:
wrote number of bytes bytes in elapsed time
v Client sessions
(megabytes per hour megabytes per hour).
v The scheduler
v Automatic inventory expiration
number of data base records, and wrote the indicated
number of bytes. v Automatic volume reclamation
v Automatic storage pool migration
System action: Server operation continues; however
restricted services are disabled.
User response: If you want to exit maintenance mode,
ANR3412I Extractdb command: Terminating output
use the HALT command to stop the server, and restart
stream stream number due to error on
it.
server server name.
Explanation: An error was encountered on the target
server during a server-to-server upgrade process,
resuting in the termination of the output stream being
used to send database information to the target server.

ANR3416I The server is in maintenance mode. ANR3420E Command: Node name is not a valid
Client sessions cannot be enabled. application type node.
Explanation: The server is in maintenance mode. Explanation: You cannot deactivate a node which is
Client sessions are disabled and cannot be reenabled not valid application type node.
until normal operation resumes.
System action: Client sessions are not enabled. command.
User response: If you want to exit maintenance mode, User response: None.
use the HALT command to stop the server, and restart
it.
ANR3421E Invalid access state for storage pool
directory stgpooldir.
ANR3417W Database backup page verification is
Explanation: There is an invalid access state to
disabled.
complete the operation for the storage pool directory.
Explanation: Pages that are backed up from the DB2 The required access state is READWRITE.
database are not being verified. A possible cause is that
IBM Software Support requested or enabled this
change.
User response: Verify that the directory has the correct
System action: The database backup continues, but
write-access. Then, issue the UPDATE
invalid or corrupted database pages might not be
STGPOOLDIRECTORY command for the storage pool
detected.
directory and specify the ACCESS=READWRITE
User response: If IBM Software Support directed you parameter.
to disable database backup page verification, no action
is required.
ANR3422W Invalid access state for storage pool
If IBM Software Support did not direct you to disable directory stgpooldir.
database backup page verification, reenable the feature
Explanation: The access state for the storage pool
to gain the additional protection that it provides.
directory is invalid. The access state must be
READONLY or READWRITE to complete this
ANR3418W Invalid storage pool directory specified: operation.
stgpooldir Error: Error.
Explanation: The storage pool directory specified in operations continue.
the DEFINE STGPOOLDIRECTORY command does not
User response: Verify that the directory has at least
exist or has invalid permissions.
read access. Then, issue the UPDATE
System action: The command is processed, but the STGPOOLDIRECTORY command for the storage pool
storage pool directory is marked as UNAVAILABLE. directory and specify the ACCESS=READWRITE or
ACCESS=READONLY parameter.
User response: To store data in the storage pool
directory, verify that the directory exists and has valid
permissions. Then, update the access state of the ANR3423E Proxy Session session number was not
storage pool directory to READWRITE. initiated by an authorized user.
Explanation: A Proxy Session must be run as an
ANR3419E Directory name directory name was authorized user. An authorized user is any non-root
duplicated when the parameter command user who has read and write access to the client stored
was issued. password (TSM.PWD file), or anyone who knows the
client password and enters it interactively. Authorized
Explanation: When you define or update multiple
users can use the client passworddir option to define
directories for a container storage pool, you can specify
the directory where their copy of the TSM.PWD file is
a directory name only once in the command.
saved.
System action: The command fails. Server operation
System action: The session is ended. System
continues.
processing continues
User response: Ensure that the directory name is
User response: Re-configure your client session as an
specified only once in the command.
authorized user or connect to the server or storage
agent as an authorized user.

ANR3424E Command: You must specify a ANR3485W The hub server is running an earlier
directory-container storage pool. Storage version than the spoke server.
pool stgpool name is not a
Explanation: The version of IBM Spectrum Protect
directory-container storage pool.
server that is installed on the hub server must be at
Explanation: The command is valid only for a least the same version that is installed on a spoke
directory-container storage pool. server.
System action: The server does not process the System action: The hub server continues to receive
command. alerts and status information from the spoke server, but
unexpected behavior might occur.
User response: Specify the name of a
directory-container storage pool with the command. User response: Upgrade the version of IBM Spectrum
Protect server that is running on the hub server. It must
be at least the same version as the spoke server.
ANR3425W Data in container-copy storage pool
volume volume name cannot be retrieved
- access mode is not READWRITE or ANR3486I CANCEL SESSION ALL command
READONLY. processing ended sooner than expected.
Explanation: During processing of a REPAIR Explanation: It is possible that the server was unable
STGPOOL command, data in a container-copy storage to cancel all sessions because a session was
pool volume cannot be restored because the volume's encountered that could not be cancelled. Some sessions
access mode is not READWRITE or READONLY. may still remain active after the command completes.
System action: The server repairs damaged extents System action: Server operation completes.
using copies in the container-copy storage pools that it
User response: Specify a session_number with the
can access, but it skips over damaged extents that exist
CANCEL SESSION command to cancel a specific
only on offsite volumes.
CLIENT session. If a SERVER session is active, the
User response: If the volume is stored at an offsite partner server must be quiesced for the session to end.
location, bring the volume onsite. Use the MOVE The SERVER session may be active with a Storage
DRMEDIA command to change the access mode for the Agent, Library Client, Library Server or Virtual Volume
volume to READWRITE or READONLY, and reissue server. To prevent new sessions from starting, see the
the REPAIR command. DISABLE SESSIONS command.
ANR3426I Container-copy storage pool volume ANR3487E Command: The number of administrators
volume name is required for repair exceed the maximum number allowed.
processing.
Explanation: The number of administrators that can
Explanation: During processing of a REPAIR receive alert summary by email is limited to three.
STGPOOL command, the server determines that a
removable volume is required.
System action: Unless this is a preview process, the
maximum of three registered administrator names.
server attempts to mount the removable volume.
ANR3488W Command: The administrator administrator
indicated volume.
name does not have an email address.
Explanation: The administrator does not have an
email address defined. The specified administrator
does not have data protected to its local
cannot receive email from the server until a valid email
container-copy storage pools.
address is defined.
Explanation: The command indicated references a
System action: The command processing continues.
storage pool that has not been protected by the LOCAL
PROTECT. User response: Issue UPDATE ADMIN command to
define the email address and reissue the command.
command.
User response: Reissue the command after protecting
data from the storage pool specified to its container
copy storage pools.

SMTP host server name are correct. Check that the

ANR3489I Command completed successfully.
SMTP port is correct. Fix any incorrect settings. The
Explanation: The specified SET command completed next alert that is triggered will use the new
successfully. configuration settings. You can also check the server's
ffdc log for any additional information about the error.
ANR3494E Command: No administrators added or
deleted for the alert trigger.
ANR3490E Command completed with failure.
Explanation: The specified SET command did not but no administrators are added or deleted for the alert
complete successfully. trigger.
System action: The server ignores the command. System action: Server operation continues, but the
User response: Verify that values are valid and reissue
the command. User response: If you are adding an administrator
reissue the command specifying an administrator name
that is registered on the server. If you are deleting an
ANR3491E No sender email address found - unable administrator reissue the command specify one of the
to send email for alert, message num. administrator names defined to the alert trigger.
Explanation: The server is unable to send an email to
the administrators for the specified alert because an ANR3495I Command: Administrator admin name is
email address of the sender could not be found. not defined to alert trigger.
System action: Server operation continues. Explanation: The administrator name cannot be
User response: Use the QUERY MONITORSETTINGS deleted because it is not defined to the specified alert
command to display the current sender's email address. trigger.
Use the SET ALERTEMAILFROMADDR command to System action: The administrator name is skipped
specify a valid sender email address. and the server operation continues.
User response: Reissue the command specifying an
ANR3492W Command: Administrator administrator administrator name that is defined to the alert trigger.
name is not configured to receive alerts
by email.
ANR3496W An invalid value, option value, is
Explanation: The specified administrator name is not specified for option option name, The
set up to receive alerts by email. Alerts cannot be sent reason code is reason code.
to the administrator until it is configured to receive
alerts by email. Explanation: Reason code 1 means that this table
name is not allowed for the option. Reason code 2
System action: Server operation continues. means that this table does not exist in the database.
User response: Use QUERY ADMIN System action: Server operation continues.
FORMAT=DETAIL to display the current settings for
the administrator. Verify that the administrator has User response: Verify that the correct value is used.
ALERT=YES and has a valid email address. Use the Update the value, if necessary.
UPDATE ADMIN command to update the settings.
ANR3497W Reorganization is required on excluded
ANR3493E Error sending an email for alert msg table table name. The reason code is
number to the administrator with email reason code.
address email address using the SMTP
Explanation: The server has determined that
server name SMTP host server and SMTP
reorganization is required on a table or index that has
port port number.
been excluded from online reorganization by the server
Explanation: An email about an alert was not sent or a server option. Reason code 1 means that table
successfully to the administrator with the specified reorganization is required on the listed table. And this
email address. table is currently excluded from online reorganization
processing because it is either specified in the
System action: Server operation continues. DISABLEREORGTable server option or is one of the
User response: Use QUERY MONITORSETTING following tables: STAGED_EXPIRING_OBJECTS,
command to see the current settings for emailing an STAGED_OBJECT_IDS (which are permanently
alert. Check that the administrator's email address and excluded by the server from online table

reorganization. Reason code 2 means that index

ANR3499E command: Scratchpad entry already
reorganization is required for the listed table. And
exists.
index reorganization is excluded because it is either
specified in the DISABLEREORGIndex server option or Explanation: A scratchpad entry with the specified
is against one of the following tables: keys already exists.
STAGED_EXPIRING_OBJECTS, STAGED_OBJECT_IDS,
REPLICATED_OBJECTS (which are permanently
excluded by the server from online index User response: Either define a new scratchpad entry
reorganization. Reason code 3 means that index with unique keys or update the existing scratchpad
reorganization with the CLEANUP PAGES ALL option entry.
is required. This reason is only valid for the
BF_BITFILE_EXTENTS table when it is specified in the
DISABLEREORGCleanupindex server option. ANR3500I Backup set for node node name as set
name (data type data type) being
System action: Server operation continues. generated.
User response: Tables and indices not reorganized Explanation: The named object set is being created for
when needed can lead to database growth and server the specified node.
performance degradation over time. If you experience
either of these symptoms, and receive this message System action: The server generates a backup set.
consideration should be given to running an offline User response: None.
reorganization of the given table or index. Details and
instructions on running an offline reorganization can be
found in technote 1452146 under the section "Running ANR3501I Backup set for node name as set name
an offline table or index reorg": http://www.ibm.com/ (data type data type) completed
support/docview.wss?uid=swg21452146 successfully - processed files files.
Explanation: The named object set was successfully
ANR3498W One-time setting of the server created for the specified node. The number of files
reorganization options is performed. processed is specified.
Explanation: The following server options are set after System action: None.
the server starts for the first time: 1) The User response: None.
DISABLEREORGTABLE option is set with no tables
specified. As a result, no tables are excluded from the
table-reorganization processing. 2) The ANR3502W Backup set for node name as set name
DISABLEREORGINDEX option is set to (data type data type) completed with file
ARCHIVE_OBJECTS,BACKUP_OBJECTS, processing errors - processed files files
BF_AGGREGATED_BITFILES, and with error files files skipped.
BF_BITFILE_EXTENTS. As a result, index Explanation: The named object set was successfully
reorganization will not be run on these tables. 3) The created for the specified node. However, during
DISABLEREORGCLEANUPINDEX is set with no tables processing errors were encountered accessing some files
specified. As a result, INDEX REORG with the - these files were skipped.
CLEANUP PAGES ALL option will be run on the
BF_BITFILE_EXTENTS table. This process of updating System action: None.
the server options file runs only one time, which is
User response: Evaluate other server messages for an
after the server starts for the first time.
indication of why the files were skipped. Files can be
System action: Server operation continues. skipped because of failures locking those files, having
no files to process, or for other more serious problems.
User response: If you do not want the one-time First, retry the command and see if it completes
reorganization processing to occur, issue the following without any skipped files. If you are unable to generate
commands from a DB2 command window: db2 connect the backup set without skipping files, please contact
to tsmdb1 db2 "insert into tsmdb1.global_attributes your local service representative for assistance.
(owner,name,type,length,int32)
values('RDB','REORG_ONETIME_AUTO_INIT',3,0,2)"
The commands can be issued on any Version 6 server ANR3503E Generation of backup set for node name
or at the fixing level for APAR IC95301, before you as set name (data type data type) failed.
start the server.
Explanation: The named object for the specified node
was not created. An error was encountered causing the
creation of this object set not to complete successfully.

User response: Evaluate other messages that were System action: Server operation continues.
issued and try to determine the cause of the failure.
User response: Reissue the command against a node
After determining the cause of the failure, retry the
that has filespaces associated with it. If no filespaces
command. If the cause can not be determined, please
exist for a given node, than there is no file data to
contact your local service representative.
write to the backupset.
If ANR3504W was received, than an error occurred
while logging the volumes used to the server volume
history. It is possible to issue a DEFINE BACKUPSET
data storage - device class device class
listing these volumes. That would cause the server to
name is not defined.
create the necessary entries for this backup set on this
server. Explanation: During command command processing,
an error occurred because the specified device class is
not defined.
ANR3504W Backup set for node name as set name was
not able to log the volumes used for this System action: The command command is ended and
operation to the server volume history. server operation continues.
Explanation: The named object for the specified node User response: Make sure the specified device class is
was created. However, when the process attempted to defined.
add the volumes, used for this operation to the volume
history for the server, an error occurred and this could
not be completed. ANR3510E Command: Error encountered in accessing
data storage - disk volume specified.
User response: Review other messages issued to an error occurred because a specified volume is a disk
determine which volumes were used to generate this volume rather than a tape volume.
backup set. The volumes can be inserted into the server
volume history for use by issuing a DEFINE System action: The command command is ended and
BACKUPSET and listing these volumes. This will also server operation continues.
allow this backup set to be queried from a client as User response: Make sure that all volumes specified
well since there is not a server entry for this backup for the command command are tape volumes.
set. Only issue the DEFINE BACKUPSET if this
generate backup set operation completed successfully.
data storage - invalid volume name
ANR3505I Backup set for node name as set name specified.
used volume volume name.
Explanation: The named object for the specified node accessing data storage while processing command
used the specified volume. command. The error occurred because an attempt has
System action: Server operation continues. been made to access a volume with an invalid name.
User response: None. System action: The command command operation is

ANR3507I Cancel in progress User response: Issue the command with a valid
volume name.
a QUERY PROCESS command, and indicates that a
generate backupset process has been canceled. The ANR3512E Command: Error encountered in accessing
process will end shortly. data storage - insufficient number of
System action: The process terminates and server media.
User response: None. the server cannot allocate sufficient mount points.
ANR3508W Generation of backup set for node name ended and server operation continues.
as set name (data type data type) failed -
no filespaces to process. User response: If necessary, make more mount points
available.
was not created. No filespaces were available to
process.

writing to the sequential media. Command command

ANR3513E Command: Output error encountered in
ends when there is no more space on the sequential
accessing data storage.
media for storing data and SCRATCH=NO has been
Explanation: The command command operation ends specified on command command.
because an error has been encountered by the server in
System action: Command command processing ends.
writing to a device. Possible reasons include:
Server processing continues.
v I/O error writing to a device
v No storage space.
SCRATCH=YES or specify additional volume names on
System action: The command command operation ends the command.
User response: Query the activity log to find messages ANR3517E Command: Error encountered in accessing
preceding this one to determine the cause of the error. data storage - required volume was not
After the problem is corrected, the command can be mounted.
retried.
Explanation: During command command processing, a
required volume cannot be mounted. The mount
ANR3514E Command: Data transfer was interrupted request may have been canceled.
in accessing data storage.
Explanation: The database transaction associated with ended and server operation continues.
command command operation failed because data
User response: Issue the command again and make
sure the necessary volumes are accessible.
external event.
ANR3518I Command: Processing canceled before
completion.
this message to determine why the data transfer was
command command has been canceled with the
interrupted. Reissue the command command after the
problem is resolved.
data storage - volume already in use.
Explanation: During command command processing, a message.
volume cannot be used because it is already defined in
a storage pool, or has been previously used by an
export, database dump, or database backup operation
(as recorded in the volume history) or is in use by ANR3519E Command: Insufficient memory available
another process. in accessing data storage.
System action: The command command operation is Explanation: The server encounters a memory
ended and server operation continues. shortage in accessing data storage during command
command operation.
User response: Specify a volume that is not in use or
defined in a storage pool, and that has not been System action: The command command operation ends
previously used for an export, database dump, or and server operation continues.
database backup operation as recorded in the server
volume history information. Use the QUERY VOLUME User response: See the documentation for the
command to display the names of volumes that are operating system about how to increase memory for an
defined to server storage pools. Use the QUERY application.
VOLHISTORY command to display the names of
volumes that have been used for export, database ANR3520E Command: Internal error encountered in
dump, or database backup operations. accessing data storage.
ANR3516E Command: Out of space on sequential in accessing data storage while processing command
media, scratch media could not be command operation.
mounted.
Explanation: During command command processing, ended and server operation continues.

User response: Use the QUERY ACTLOG command to interrupted. Attempt the backup set operation again
examine messages prior to this error to determine the after problem is resolved.
cause of the data storage failure. If the failure can be
found and resolved, reissue the command command
ANR3525W Backup set command: Transaction failed -
operation. If the failure cannot be found, contact your
service representative for assistance in resolving the
problem. Explanation: The server ends a transaction for an
backup set operation because storage volumes are not
available in the storage pools in which the client files
ANR3521W BackupSet command: Data storage retrieve
are to be stored.
or restore failed - error detected.
System action: The server ends the backup set
Explanation: The server ends an backup set operation
operation and server operation continues.
because an error has been encountered on the server.
Some common reasons for the error are: User response: An authorized administrator can issue
v The input volume is unavailable the DEFINE VOLUME command to add storage to one
or more storage pools in the storage hierarchy. The
VARY ONLINE command can be used to vary offline
v Data is corrupted on the input volume storage volumes online in the storage hierarchy to
v Hardware or media failure has occurred make them available for file storage.
v Database corruption
System action: The server ends the backup set ANR3527E Backup set command operation terminated
operation and continues operation. - it is acting on an empty volume or
volume content is not as expected.
User response: Examine any prior error messages to
determine the source of the error. Use the QUERY Explanation: The volume content this command is
ACTLOG command to view the activity log and search acting upon is not as expected, the volume is empty, or
for messages if needed. Correct the problem and try the the volume cannot be found.
restore or retrieve again. If retry of the operation System action: The command operation is ended.
continues to fail contact your service representative.
sure the expected content is in the volumes or the
ANR3523W Backup set command: Retrieve failed - volume is not empty and exists.
error on input storage device.
Explanation: The server ends a backup set operation ANR3528E Backup set command: Media not accessible
for the specified session because an I/O error has been in accessing data storage.
encountered by the server in reading from a device.
The object for which the I/O was issued is reported in Explanation: The server ends a transaction for a
a later message. backup set operation because storage volumes are not
available in the storage pools in which the client files
System action: Backup set processing skips this file, are to be stored.
and continues operation.
System action: The server ends the backup set
User response: Query the activity log to find messages operation and server operation continues.
preceding this one that specify the device that is failing.
Storage pool volumes can be varied offline (by using User response: An authorized administrator can issue
the VARY OFFLINE command), or the server may need the DEFINE VOLUME command to add storage to one
to be shut down with the HALT command to correct or more storage pools in the storage hierarchy. The
the hardware problem. VARY ONLINE command can be used to vary offline
make them available for file storage.
ANR3524W Backup set command: Transaction failed -
data transfer interrupted.
ANR3529W Generate backupset skipping damaged
Explanation: The database transaction associated with file on volume volume name: Node node
a backup set operation failed because data transfer to name, Type file type, File space filespace
or from data storage was interrupted by an external name, fsId filespace id, File name file name.
event.
Explanation: The backup set generation process
System action: The backup set operation is ended and encountered a file that was previously found to be
server operation continues. damaged. The process encountered the file during a
User response: Examine the messages issued prior to sequential scan of all files on the storage pool volume;
this message to determine why the data transfer was the indicated file may or may not have been a

candidate for inclusion in the backup set. User response: Correct the problem reported by
previous messages, if possible.
If this file is part of an aggregate, it may have been
previously marked as damaged because an integrity
error was detected in some other file within the same ANR3543E Error error code occurred while sending
aggregate. AUDIT VOLUME can determine if this is the entries from object set set node:set
case, and if so, will reset the damaged state for the file. name:data type for session session number,
node.
System action: The damaged file is not added to the
backupset. Explanation: An error occurred while sending entries
for the indicated object set.
User response: Audit the indicated volume with
FIX=NO to determine if the file is actually damaged. System action: An error is returned to the client.
The audit will reset the file's damaged state if the file is
User response: Correct the problem reported by other
not damaged. (If the file is part of an aggregate, and
prior or subsequent messages related to this session,
none of the files within the aggregate are damaged, the
and try the operation again.
audit will also reset the entire aggregate's damaged
state.)
ANR3544E Generation of backup set for node name
If the file remains in the damaged state after the audit
as set name (data type data type) skipped
completes, attempt to restore the damaged file by using
shreddable data object in file space
the RESTORE STGPOOL command. Note, however,
filespace name (fsId filespace id), file name
that this is only an option if the damaged file is in a
file name, type file type.
primary storage pool that had been previously backed
up to a copy storage pool. Explanation: The named data object for the specified
node was skipped while generating a backupset.
If the audit resets the file's damaged state, or the
damaged file was successfully restored using RESTORE The data object resides in a shreddable storage pool
STGPOOL, and it is important for this file be included and will not be included in the backupset because the
in the backup set, then rerun the GENERATE ALLOWSHREDDABLE=YES parameter was not
BACKUPSET command to generate a new backup set specified.
containing the file.
System action: Backupset generation continues.
ANR3540E Object set set node:set name:data type was User response: Check with your Storage
not found for session session number, Administrator to ensure data residing in a shreddable
node. storage pool is a allowed to be stored on a backupset.
Data stored on backupsets cannot be shredded. Only
Explanation: The indicated session id requested to data that resides in a shreddable storage pool can be
restore the object set. The object set was not found on shredded. If your Storage Administrator allows
the server. shreddable data to be stored on backupsets, then restart
the operation and specify the
System action: The error is returned to the client.
ALLOWSHREDDABLE=YES parameter.
ANR3547I Backup set set name used volume volume
ANR3541E Error error code occurred opening object name.
set set node:set name:data type for session
Explanation: The named object used the specified
session number, node.
volume.
Explanation: An error occurred while opening the
indicated object set.
System action: An error is returned to the client.
User response: Correct the problem reported by
ANR3548E Command: Retrieve or restore failed - file
previous messages, if possible.
was moved or deleted from data storage
during retrieval.
ANR3542E Error error code occurred reading object
set set node:set name:data type for session
for the specified command because the file has been
session number, node.
moved or deleted from data storage by another process
Explanation: An error occurred while reading the before retrieval is complete.
indicated object set.
System action: An error is returned to the client.

if space reclamation, migration, DELETE FILESPACE, supported on server versions 7.1.1 and newer. Reissue
DELETE VOLUME, MOVE DATA, or inventory the command specifying a different node name, or,
expiration processes are running; these processes can rename the node name and reissue the command.
move or delete data storage files during retrieval.
Reissue the command after these processes have been
ANR3556E The server cannot connect to the cloud
completed or canceled.
service provider with the specified
cloud URL of url when using the cloud
ANR3549W Reorganization was canceled because of ID of id and its password.
a conflicting lock on table table name.
Explanation: The connection to the cloud service
Explanation: The server online reorganization for the provider failed because the cloud URL, cloud ID, and
referenced table could not be completed because of a cloud password specified in the command could not be
lock conflict. The reorganization was canceled. resolved.
System action: The server will continue to operate. System action: The command fails.
User response: None. User response: Verify that the cloud URL, user ID,
password, and cloud type for the cloud storage pool
are correct and have been entered correctly. Also, verify
ANR3550E Definition of backup set set name for
that the cloud provider is active.
node name failed because it has an
unknown format.
ANR3557I The cloud service provider URL and
credentials were verified.
was not defined. It was generated on a server that is at
a higher level than this server and contains data that Explanation: The verification of the credentials and
cannot be properly interpreted by this server. URL for the cloud service provider succeeded.
User response: Define the object on a server that is User response: None.
compatible with the server that generated the object, or
upgrade this server to be compatible with the server
ANR3560E command: One or more of the following
that generated the object.
parameters are missing: parameters.
Explanation: The command cannot be processed as
ANR3551I The server delete batch size has been set
specified.
to new batch size. Deletion operations
that start after this point will use the System action: The server ignores the command.
new value.
User response: Verify the command syntax and
Explanation: A SETOPT command was used to set the reissue the command.
value for the delete batch size value. This setting
determines the maximum number of files that are
deleted from the server in one database transaction. ANR3561E command: Keyword parameter parameter
The setting influences inventory expiration operations. is not recognized. The following
keyword parameters are valid: validlist.
System action: The server uses this new setting for
deletion operations that are started after this message is Explanation: The command cannot be processed as
issued. specified.
User response: None. System action: The server ignores the command.
ANR3552E Command: Node node name is a node reissue the command.
name not supported on the target server
and is skipped. ANR3562E command: The parameter parameter value
Explanation: The node name has one or more value is not numeric. The minimum
characters that is not supported on server versions value is min value and the maximum
earlier than 7.1.1. The character is the '@' sign. value is max value.
System action: The server skips the node name and Explanation: The command cannot be processed
operation continues. because the specified parameter requires a numeric
value.
User response: Check if the node name has the '@' (at
sign) character. Node names with the '@' character are System action: The server ignores the command.

User response: Verify the command syntax and User response: Verify the command syntax and
reissue the command. reissue the command.
ANR3563E command: The parameter parameter value ANR3568E command: The parameter parameter value
value is out of range. The minimum value is out of range. The minimum
value is min value and the maximum value is min value and the maximum
value is max value. value is max value.
Explanation: The command cannot be processed as Explanation: The command cannot be processed as
specified. specified.
System action: The server ignores the command. System action: The server ignores the command.
value is not recognized. The following value is too long. The maximum length
parameter values are valid: validlist. is max length characters.
value is out of range. The minimum is too short. The minimum length is min
value is min value and the maximum length characters.
value is max value. The following
parameter values are also valid: validlist.
specified.
specified.
ANR3571E command: The parameter parameter value
value contains an invalid character
ANR3566E command: The parameter parameter value "character". The following characters are
value is not recognized. The minimum valid: "validlist" (excluding the quotation
value is min value and the maximum marks).
specified.
specified.
value is a reserved value and cannot be
ANR3567E command: The scale scale for the parameter specified.
parameter is not recognized. The
following scales are valid: validlist.
specified.
specified.

ANR3573E command: The parameter parameter value ANR3578E command: The parameter parameter
value is not a valid date. relative days value value is out of range.
The minimum value is 0 and the
maximum value is max value.
specified.
specified.
value month month is out of range. The
minimum value is minimum and the ANR3579E command: The parameter parameter value
maximum value is maximum. value is not a valid time.
value day day is out of range. The value hours hours is out of range. The
minimum value is minimum and the minimum value is minimum and the
maximum value is maximum. maximum value is maximum.
value year year is out of range. The value minutes minutes is out of range.
minimum value is minimum and the The minimum value is minimum and the
maximum value is maximum. maximum value is maximum.
ANR3577E command: The parameter parameter ANR3582E command: The parameter parameter value
relative days value value is not numeric. value seconds seconds is out of range. The
minimum value is minimum and the
Explanation: The command cannot be processed
maximum value is maximum.
because the specified parameter requires a numeric
value. Explanation: The command cannot be processed as
specified.
reissue the command. User response: Verify the command syntax and

ANR3583E command: The parameter parameter ANR3588E command: The parameter parameter
relative hours value value is not requires the prerequisite parameter
numeric. parameter.
Explanation: The command cannot be processed Explanation: The command cannot be processed as
because the specified parameter requires a numeric specified.
value.
User response: Verify the command syntax and reissue the command.
ANR3589I command: For more information, issue
ANR3584E command: The parameter parameter the HELP command command.
relative minutes value value is not
Explanation: One or more syntax errors were found in
numeric.
the specified server command (see the previous
Explanation: The command cannot be processed messages). The command cannot be processed as
because the specified parameter requires a numeric specified.
value.
ANR3590E command: Command is above the
ANR3585E command: The parameter parameter requested skill level.
relative hours value value is out of
Explanation: The specified server command has a skill
range. The minimum value is 0 and the
level above what was requested.
specified. User response: Reissue the command and enter the
proper syntax.
value is out of range. The minimum
value is min value and the maximum
ANR3586E command: The parameter parameter value is max value. The following
relative minutes value value is out of parameter values are also valid: validlist.
range. The minimum value is 0 and the
specified.
specified.
value is not recognized. The minimum
ANR3587E command: The parameter parameter is value is min value and the maximum
specified more than once. value is max value. The following
because the specified parameter can only be entered Explanation: The command cannot be processed as
once. specified.

ANR3593E command: The parameter parameter value ANR3598E command: At least one of the following
value is not valid. One of the following parameters is required: parameters.
scales is required: validlist.
Explanation: The command cannot be processed as specified.
specified.
ANR3599E command: One and only one of the
ANR3594E command: The integer portion of the following parameters is required:
parameter parameter value value is out of parameters.
range. The minimum integer value is
min value and the maximum integer
specified.
value is max value.
specified. User response: Verify the command syntax and
ANR3601W Policy Domain release failed for domain
domain id due to communications failure.
Explanation: The storage agent was attempting to
ANR3595E command: The integer portion of the
inform the database server that it was finished with the
parameter parameter value value is out of
domain indicated by the domain id, but was unable to
range. The minimum integer value is
communicate with the database server. The cached
min value and the maximum integer
policy information will be cleaned up when the storage
server terminates or re-starts or when the database
server re-starts.
System action: The storage agent continues operation.
specified.
The policy information is deleted from the storage
System action: The server ignores the command. agent policy cache.
User response: Verify the command syntax and User response: Policy caches are cleaned up on the
reissue the command. storage agent or server re-start. Network
communication between the storage agent and database
server should be checked.
ANR3596E command: The parameter parameter
conflicts with the conflicting parameter
parameter. ANR3602E Unable to communicate with database
server.
specified. Explanation: The storage agent was attempting to
communicate with the database server but was unable
to do so.
System action: The storage agent operation fails.
User response: Check the configuration of the storage
agent and server to ensure that communication
parameters are correct. Ensure that the database server
value is specified more than once.
is running and is accepting messages.
specified.
ANR3603E Storage AgentStorage Agent name was
System action: The server ignores the command. unable to load policy information due to
a protocol error.
reissue the command. Explanation: While receiving policy information from
a database server, processing ended prematurely
because of a protocol error.

System action: Server operation continues. Policy is verb name and return code are provided for IBM
loaded from the database server database. Software Support.
User response: If this problem persists, contact your System action: Database server and storage agent
service representative. continue. The restore request fails, but may be retried
by the client.
ANR3604E This command is not supported in the User response: Check the configuration of the storage
current operating environment. agent and client to ensure that communication
parameters are correct. If this problem persists, contact
Explanation: A command was issued that is valid
under most circumstances, but not in the current server
environment.
ANR3608E The storage agent was communicating
with the database server on a restore
User response: Issue commands which are allowed in request. An unexpected request (id verb )
the current environment. was received from the database server.
Explanation: The storage agent and database server
ANR3605E Unable to communicate with storage were coordinating a restore request. While
agent. communicating, the indicated verb ( an internal request
mechanism between the storage agent and database
Explanation: The database server was attempting to server ), was unexpected. The verb number is provided
communicate with the storage agent but was unable to for IBM Software Support.
do so.
System action: Database server and storage agent
System action: The database server operation fails. continue. The restore request may fail, but may be
User response: Check the configuration of the storage retried by the client.
agent and server to ensure that communication User response: If this problem persists, contact your
parameters are correct. service representative.
ANR3606E The storage agent was communicating ANR3609E The storage agent was handling a
with the database server on a restore restore request. A failure occurred in
request with verb verb name and starting a new thread. The return code
received return code return code. return code from the failing routine may
Explanation: The storage agent and database server be useful to IBM Software Support.
were coordinating a restore request. While Explanation: The storage agent was handling a restore
communicating using the indicated verb ( an internal request. A new thread could not be started. Without the
request mechanism between the storage agent and new thread the request could not be handled.
database server ), an unexpected return code was
received. The verb name and return code are provided System action: Database server and storage agent
for IBM Software Support. continue. The restore request has failed.
System action: Database server and storage agent User response: Ensure that there is sufficient system
continue. The restore request fails, but may be retried memory for the storage agent to operate properly.
by the client. Insufficient memory or paging/swap space can cause
problems in starting threads. If this problem persists,
User response: Check the configuration of the storage contact your service representative.
agent and server to ensure that communication
parameters are correct. If this problem persists, contact
your service representative. ANR3610I Domain Identifier domain identifier was
not found.
ANR3607E The storage agent was communicating Explanation: The server was cleaning up cached
with the client on a restore request with policy information after a restore request. A domain
verb verb name and received return code with the indicated identifier was not found in an
return code. internal list.
Explanation: The storage agent was communicating System action: Database server and storage agent
with a client for a restore request. While continue.
communicating using the indicated verb ( an internal
User response: No response is required if the message
request mechanism between the storage agent and
is the result of starting a storage agent. The storage
client ), an unexpected return code was received. The
agent requests that the server purge cached information

that it was using previously. It is possible that

ANR3615E The value of the DATAFORMAT
information tracking policy caching has become stale.
parameter for the datamover is not
In this case, no response is required. If the message
compatible with the NAS file server.
occurs without a storage agent connecting to the server,
contact your service representative. Explanation: The datamover was defined with the
NDMPDump DATAFORMAT. This data format is not
compatible with an EMC NAS file server.
ANR3611E Storage Agent unable to contact server.
System action: The NDMP operation fails.
Explanation: The storage agent was attempting to
contact the server to start a session or run a command. User response: Update the datamover to use the
The storage agent was unable to contact the server to CELERRADump dataformat.
start a transaction.
System action: The storage agent continues ANR3616E An error occurred. More information
processing. The server may be down or there may be a might be available in the dsmserv.err
communications problem. and dsmffdc.log files.
User response: No response is required if the message Explanation: None.
is the result of stopping a server. Ensure that the server
with which the storage agent communicates is running
and that there is connectivity between the systems. The User response: Review the dsmserv.err and
server must be restarted before you can start a new dsmffdc.log files for messages that occurred at the same
administrator session with the storage agent. time as the error. The dsmserv.err and dsmffdc.log files
is located in the server working directory. Correct any
problems that are identified.
ANR3612E This command is not supported in the
Express environment.
ANR3617E The server failed to start with return
Explanation: A command was issued that is valid
code rc because of an issue with the
under most circumstances, but not in the current server
database environment handle.
environment.
Explanation: The server was unable to allocate a
handle to the database environment.
User response: Issue commands which are allowed in
the current environment.
User response: The following are possible causes and
solutions:
files on volume Volume name because of v The most common cause is that the DSMSERV utility
a lock conflict with another process. is not being run as the instance owner, or the user
profile (db2profile) has not been sourced for the
Explanation: A lock conflict was encountered while current login shell. To resolve the issue, log in as the
moving files and the retries were exceeded. instance user and source the DB2 profile, db2profile:
System action: The operation skips the files without . /home/tsminst1/sqllib/db2profile Note: Ensure
making copies and continues. that you insert a space after the initial dot.
v A mismatch between the /etc/hosts file and the
User response: Retry the operation.
~/sqllib/db2nodes.cfg file. If the host name was
recently updated, ensure that the systems host name
ANR3614E The server failed to connect to the in the /etc/hosts file matches the host name in the
database. ~/sqllib/db2nodes.cfg file. If the files contain the
same host name, see the db2diag.log files for more
Explanation: The server was unable to establish or information. For information about the db2nodes.cfg
validate a connection to the database. file, see the DB2 documentation.
System action: The server will shutdown. v The database manager cannot be started due to
insufficient system resources. Review the current
User response: Examine the messages that were
operating system kernel settings and ulimit settings
issued before this message to determine the cause of
for parameters like nofiles for the user who is
the failure. Start the server after the issue has been
starting the DSMSERV program. Increase the values
resolved.
if needed. For information about changing kernel
and ulimit values, see the documentation for your
operating system. For guidelines concerning ulimit
settings on IBM Spectrum Protect servers search for
"user limits" in the product information

(http://www.ibm.com/support/knowledgecenter/ User response: None.

SSEQVQ/). For guidelines concerning operating
system kernel parameters, search for "tuning kernel
ANR3622I Status threshold status threshold defined.
parameter" in the product information.
v Instance entries are missing from the /etc/services Explanation: A DEFINE STATUSTHRESHOLD
file. If the entries do not exist in the /etc/services command has created the status threshold indicated.
file, re-create the entries as in this example: System action: None.
DB2_tsminst1 60000/tcp DB2_tsminst1_1 60001/tcp
DB2_tsminst1_2 60002/tcp DB2_tsminst1_END User response: None.
60003/tcp As a general rule, these entries are placed
near the end of the /etc/services file. Replace
ANR3623E Command: Status threshold status
tsminst1 with the name of the IBM Spectrum Protect
threshold is already defined.
instance that is being used on the server.
v A copy of the DB2APP64.dll file is in the server Explanation: The command indicated has attempted
instance directory. In some cases, users mistakenly to define a status threshold that already exists.
copy the DB2APP64.dll file to the server instance System action: None.
directory from the installation directory. By default,
the installation directory is C:\Program User response: None.
Files\Tivoli\TSM\db2\BIN. The DB2APP64.dll file
should be in this directory only. Any additional ANR3624E Command: Status threshold threshold name
copies of this DLL file should be removed. is not defined.
Explanation: The command shown specifies a status
ANR3618W bad adapter number of total adapter number threshold that is not defined with the server.
host bus adapters cannot be opened.
Explanation: The SAN discovery function is not able
to open all of the host bus adapters (HBAs) on the User response: None.
system.
System action: None. ANR3625I Host bus adapter (HBA) API functions
are not supported by adapter adapter
User response: IBM Spectrum Protect SAN discovery name.
may only be getting partial device information from the
SAN. Verify that all HBAs are configured and working Explanation: The HBAAPI function failed to retrieve
properly. the attributes of the adapter. The reason is that this
adapter is not a Fibre Channel SCSI adapter. This
adapter might be a Serial Attached SCSI adapter.
ANR3619W The user limit for limit is below the Therefore, SAN discovery does not work.
recommended minimum value of value.
System action: The system is unable to retrieve the
Explanation: A user limit that is below the attributes of the adapter.
recommended minimum value might cause unexpected
behavior. User response: Validate whether this adapter is a
Fibre Channel SCSI adapter or not, and if it is, contact
System action: None. hardware support for the adapter.
User response: Set the user limit so that it is equal to
or greater than the recommended minimum value. ANR3626W A check condition occurred during a
small computer system interface (SCSI)
ANR3620I Status threshold status threshold updated. inquiry at Fibre Channel port WWN=fc
port wwn, KEY=sense key, ASC=asc,
Explanation: An UPDATE STATUSTHRESHOLD ASCQ=ascq.
command has updated the status threshold indicated.
Explanation: The host bus adapter (HBA) API
System action: None. function failed to query the SCSI information of a
User response: None. device located at this port. A hardware error or SCSI
bus reset might have occurred during the operation.
ANR3621I Status threshold status threshold deleted. System action: The HBAAPI inquiry function was
unable to retrieve the SCSI device information from this
Explanation: A DELETE STATUSTHRESHOLD port.
command has deleted the status threshold indicated.
User response: Verify that the adapter, device, and
System action: None. Fibre Channel are connected. For more information

about the values of the KEY, ASC, and ASCQ fields, see System action: The status threshold is not defined or
the SCSI specification. updated.
User response: Either delete the existing threshold or
ANR3627I Alerts cannot be sent by email. use a different condition.
Explanation: You must enable the alert monitor and
email option to receive alerts by email. ANR3631E The database is not intact.
System action: Server processing continues. Explanation: The server failed to start because the
database was not intact.
User response: Configure the server alert settings with
the following commands: System action: Server initialization fails.
SET ALERTMONITOR ON User response: If this is a new installation or
configuration, confirm that the DSMSERV FORMAT
SET ALERTEMAIL ON
step was completed successfully. If this is an existing
configuration that was previously working, a database
ANR3628E The monitor status process has restore might be required.
encountered an unexpected error setting
the status of element element. The
ANR3632E command: The administrator administrator
process returned error code rc.
ID is locked.
Explanation: The process that monitors server activity
Explanation: The administrator ID is locked and
has detected an error setting the element status.
cannot be used in this command.
User response: Unlock the administrator ID and
ANR3629W All administrators with system level
authority use LDAP authentication.
ANR3633I Process process ID skipped volume
Administrator admin was the most recent
Volume Name because the volume
administrator with system level
contains files that have not been backed
authority that used LOCAL
up.
authentication.
Explanation: The DEDUPREQUIRESBACKUP server
Explanation: All administrator with system level
option is set to the default value of YES. If the value of
authority use LDAP authentication. This situation has
this option is YES, files within a deduplicated storage
risks, based on the availability of the LDAP server. If
pool must be backed up to a non-deduplicated copy
required, make sure that the LDAP server has high
storage pool before the files can be reclaimed.
availability configurations implemented. For example:
clustering, mirroring, or replication. Having one System action: The operation skips the volume and
system-level administrator with LOCAL authentication continues.
gives that administrator the ability to update other
User response: Ensure that all files on the volume are
administrators and nodes to LOCAL authentication if
backed up to a non-deduplicated copy storage pool.
the LDAP server is down unusable for an extended
You can change the value of the
period of time.
DEDUPREQUIRESBACKUP server option to NO.
System action: The only administrator with system However, changing the option value to NO can result
level authority uses LDAP authentication. in unrecoverable data loss if a data-integrity error
occurs.
User response: Consider having one administrator
with system authority and LOCAL authentication. If
this is not possible, validate that the high availability ANR3634W The HBA API cannot provide tape
configurations for the LDAP server are sufficient. device information from the SAN.
System action: No action is required.
ANR3630E Command: The condition condition will
User response: Check the connections between the
conflict with existing status threshold
Fibre Channel cables and the tape device settings to
threshold with condition condition.
ensure that the tape devices can be presented to the
Explanation: The command indicated has attempted system first. Contact the HBA vendor to report
to define or update a status threshold that will conflict problems if the QUERY SAN command cannot retrieve
with an existing threshold. tape device information when tape devices are
presented to the system.

ANR3635I The status monitor has updated the ANR3640E command command failed because the
event record retention period to 14 days. target replication server
target_server_name is invalid.
Explanation: To provide full functionality for the
Operations Center, the server must retain event records Explanation: The specified target replication server is
for a minimum of 14 days. not a target replication server.
System action: Event records will be retained for 14 System action: The command fails.
days.
User response: To set the name of a target replication
User response: Use the SET EVENTRETENTION server and to run the replication validation process for
command if a different value is desired. that target replication server, complete the following
steps:
ANR3636W Transaction failed for session session 1. Obtain a list of possible target replication servers by
number for node node name (client issuing the QUERY SERVER command.
platform) - the key is already defined.
2. Verify the policies by issuing the VALIDATE
Explanation: The server ends the transaction because REPLPOLICY command.
the key is already defined in the database.
System action: Server operation continues. ANR3641E SET DISSIMILARPOLICIES command
failed because the policies on the target
User response: Make sure the key is unique.
replication server were not verified.
Explanation: The policies on the target replication
server were not verified before issuing the SET
DISSIMILARPOLICIES command.
platform) - the key is not defined.
Explanation: The server ends the transaction because
the key is already defined in the database. User response: Verify the policies by issuing the
VALIDATE REPLPOLICY command.
User response: Make sure the key is defined.
ANR3642E Damaged files are not recovered because
the system-wide
ANR3638W Space reclamation skipped volume REPLRECOVERDAMAGED setting is
volume name because the spanned turned off.
volume volume name in storage pool
Explanation: To recover damaged files by using the
storage pool name is inaccessible.
REPLICATE NODE command, the
Explanation: The specified volume is eligible for space REPLRECOVERDAMAGED setting must be turned on.
reclamation, but the spanned volume is either
System action: The REPLICATE NODE command
unavailable or destroyed. The specified volume is
fails.
skipped. Space reclamation continues for other
volumes. User response: To resolve the issue, complete the
following steps: 1. Use the SET
System action: The space reclamation process
REPLRECOVERDAMAGED command to turn the
continues.
setting for file recovery on. Issue the following
User response: No action is required. command: set replrecoverdamaged on 2. Run the
REPLICATE NODE command again. Ensure that the
RECOVERDAMAGED parameter is set to YES or
ANR3639I command: A deduplicated NAS backup ONLY.
image for node node name, file space
filespace name was skipped.
ANR3643W Process number for description exceeded
Explanation: The server command has determined the maximum allowed running time.
that a NAS backup image is not eligible for processing
because the image or one of its dependent files is Explanation: The process was started by a
stored or had been stored in a deduplicated storage administrative schedule and is running longer than the
pool. maximum allowed time defined in the schedule.
System action: The processing continues. System action: The process is cancelled and server

ANR3644E The target replication server name does ANR3648E Command: Storage pool NEXTSTGPOOL:
not support dissimilar policies. storage pool name is a directory-container
storage pool.
Explanation: Dissimilar policies are supported only on
IBM Spectrum Protect Version 7.1.1 or later. Explanation: The command indicated specifies the
name of a storage pool which is a directory-container
System action: Policy validation is skipped for the
storage pool. The command syntax requires that a
specified server.
directory-container storage pool name not be specified.
User response: To resolve this issue, complete the
following steps: 1. Upgrade the target server to IBM
command.
Spectrum Protect V7.1.1 or later. 2. Run the VALIDATE
REPLPOLICY command again. User response: Reissue the command with a valid
storage pool name.
still contains at least one directory. ANR3649I A scan to identify damaged files was
initiated at time.
Explanation: A DELETE STGPOOL command specifies
a storage pool that has directories assigned to it. Explanation: If the REPLRECOVERDAMAGED
system parameter is set to ON, the system conducts a
brief check of server database tables every 30 minutes
command.
to determine whether the number of damaged bitfiles
User response: Delete the directory belonging to the has changed. If the number has changed, the system
storage pool and reissue the command. initiates a scan of server database tables to identify the
damaged files for recovery purposes.
ANR3646E Command: Storage pool directory storage System action: A scan was started to collect
pool directory name has an access mode of information about damaged files.
access mode and has active data.
Explanation: A DELETE STGPOOLDIR command
specifies a storage pool directory that has in use
ANR3650I A scan to identify damaged files was
directories assigned to it.
completed at time.
Explanation: If the REPLRECOVERDAMAGED
command.
system parameter is set to ON, the system conducts a
User response: Ensure that there are no containers in brief check of server database tables every 30 minutes
the directory before you delete it. Issue the UPDATE to determine whether the number of damaged bitfiles
STGPOOL command and set the REUSEDELAY has changed. If the number has changed, the system
parameter to specify the number of days that must initiates a scan of server database tables to identify the
elapse after all deduplicated extents are removed from damaged files for recovery purposes.
a container storage pool. To force removal of the
System action: A scan that collected information about
directory, issue the UPDATE STGPOOLDIRECTORY
damaged files is completed. If the recovery of damaged
command and set the access mode to DESTROYED.
files is enabled for a node, the next replication process
Issue the AUDIT CONTAINER command and specify
will replace the damaged files on that node with
the ACTION=REMOVEDAMAGED parameter to delete
undamaged files from the target replication server.
the container.
Recovery of damaged files can take place only if the
files were replicated before the damage occurred.
ANR3647E The Command command failed because
the default replication server is not set.
Explanation: The command requires a default target
ANR3651W The replication process is skipping a
replicatoin server. If the default target replication server
damaged file on volume volume name:
is not set, the command fails.
Node node name, Type file type, File space
System action: The command fails. filespace name, File name file name.
User response: Issue the SET REPLSERVER command Explanation: During the replication process, a file is
to set the default target replication server as the target encountered that was previously found to be damaged.
replication server. If this file is part of an aggregate, the entire aggregate
was previously marked damaged, possibly because an
integrity error was detected for some other file within
the aggregate.

System action: The damaged file is not replicated.

ANR3655I Replication ended for process node name,
User response: Perform the following actions: but the deduplication catalog is being
v Audit the volume with FIX=NO to verify that the file updated for the following storage pools:
is damaged. If the file is undamaged, the audit pool list.
process resets the file status. If the file is part of an Explanation: As files were being recovered from the
aggregate and the entire aggregate is found to be target replication server, a separate thread was started
undamaged, the audit process resets the aggregate to update the entries for the affected files in the
status. deduplication catalog. The thread was still in the
v If the volume is in a primary storage pool and has a process of updating the entries when the replication
copy in the copy storage pool, attempt to restore the recovery process ended.
damaged file by issuing the RESTORE STGPOOL
System action: The thread continues to update the
command.
attributes of the recovered files in the deduplication
catalog. When the updates are complete, all affected
ANR3652I The VALIDATE REPLPOLICY command files will be accessible to client sessions and server
did not find any nodes to validate on processes.
the target replication server target server
name.
Explanation: The nodes on the target replication
ANR3656I Replication recovery of damaged files is
server are not the same as the nodes on the source
disabled.
replication server. When you issue this command, it
does not find any nodes that are common to both Explanation: During a database upgrade, damaged
replication servers to compare. files were detected. The REPLRECOVERDAMAGED
system parameter, which is used to enable the recovery
of damaged files, was automatically set to OFF. The
User response: No action is required. OFF setting prevents the server from scanning database
tables for damaged objects that can be recovered.
Prevention of the scan is necessary in case many
ANR3653I A scan to identify damaged files was damaged files are detected. In that case, the scan might
stopped at time. require considerable time and a large amount of server
Explanation: The scan was stopped because the resources.
REPLRECOVERDAMAGED system parameter was set System action: The server upgrade continues, and the
to OFF. REPLRECOVERDAMAGED system parameter remains
System action: Information that was collected during set to OFF.
the scan was saved. User response: The process for scanning database
User response: No action is required. However, if you tables should be scheduled when the use of server
want to restart the scan, issue the following command: resources is at a minimum. To start the scan, issue the
SET REPLRECOVERDAMAGED ON following command: set replrecoverdamaged on For
detailed instructions, see the documentation for the SET
REPLRECOVERDAMAGED command.
ANR3654W Inventory file expiration processing did
not run in the previous 24 hours.
ANR3657E REPAIR STGPOOL: One or more
Explanation: When you are using the policies on the required stgpool directories is currently
target replication server to manage replicated unavailable on the target server.
client-node data, you must run expiration processing
every 24 hours to allow the target replication server Explanation: The REPAIR STGPOOL process is unable
reuse storage pool space that is occupied by expired to repair one or more files because the replicated data
replicated data. is located in a stgpool directory that is currently
unavailable on the target server.
System action: The REPAIR STGPOOL process fails.
User response: Run expiration processing at least once
in a 24 hour period. User response: If the stgpool directory has been
marked unavailable on the target server, it can be
updated using the UPDATE STGPOOLDIR command.

ANR3658E Command: Storage pool storage pool name ANR3663W Source file(line number): Storage pool
is currently in use by replication, repair, storage pool name failed to delete the
or protect operations. cloud container.
Explanation: The command indicated references a Explanation: A DELETE STGPOOL command could
storage pool that is in use. not delete the cloud container.
command. command.
User response: Reissue the command at a later time. User response: Ensure the connection to the cloud
server has valid credentials and can communicate
properly.
does not have a protection stgpool
defined. ANR3664W Command: A network-attached storage
(NAS) table of contents (TOC) for node
Explanation: The stgpool must have a protection
node name, file space filespace name was
stgpool defined.
skipped.
Explanation: The TOC was skipped because a table of
command.
contents storage pool is not defined on the target
User response: Update the PROTECT STGpool replication server.
parameter for the pool you are trying to protect.
System action: Node replication processing continues,
but the TOC is not replicated.
ANR3660E An unexpected error occured while
User response: No action is required. However, to
opening or writing to the container.
ensure that the backup image is replicated, you can use
Container container name in stgpool
the UPDATE COPYGROUP command to specify a table of
storage pool name has been marked as
contents destination, and then activate the updated
container state and should be audited to
policy set by issuing the ACTIVATE POLICYSET command.
validate accessibility and content.
These two commands must be issued on the target
Explanation: An I/O error occured on the container replication server. Then, initiate node replication on the
and it cannot be used. source replication server.
For example, to change the STANDARD copy group to
System action: The server does not use the container. store table of contents data in the TOCPOOL storage
User response: Run an AUDIT CONTAINER pool where the domain name is STANDARD and the
command on the container. policy name is STANDARD, complete the following
steps:
1. Issue the following command:
ANR3661I Marked container container name and the
# of data extents data extents that it update copygroup standard standard standard
contains as damaged. tocdestination=tocpool
2. Issue the following command:
Explanation: Displays results of data extents marked
damaged due to an AUDIT CONTAINER command. activate policyset standard standard
3. Start the node replication process. For example, if
the node is named NODE1, issue the following
User response: None. command on the source replication server:
replicate node node1
still contains data. ANR3665E Command: Source storage pool storage
Explanation: A DELETE STGPOOL command pool is not eligible to be converted.
encountered a storage pool that still contains data. Explanation: Only primary sequential-access storage
System action: The server does not process the pools that are enabled for data deduplication are
command. eligible for conversion to a directory-container storage
pool.
User response: Delete the data that belongs to the
storage pool and reissue the command. System action: The server does not process the
command.

a primary sequential-access storage pool as the source pool conversion cannot be reversed after it is started.
storage pool.
continue.
ANR3666E Command: Destination storage pool
User response: Enter 'Y' to convert the storage pool or
storage pool is not eligible for the
'N' to stop the process.
conversion.
Explanation: The command specifies a target storage
ANR3670W Storage pool storage pool is either
pool that is not valid for conversion. You must specify
converted or is being converted and
a directory-container storage pool as the target storage
cannot accept any new data.
pool for a conversion process. When restarting a
stopped conversion process, you must specify the target Explanation: Conversion is in progress for the storage
storage pool which was originally used for the pool.
conversion process.
System action: The storage pool cannot store new files
System action: The server does not process the from either client sessions or server processes.
command.
User response: Update all policies to ensure that the
User response: Issue the command again and specify destination specifies a storage pool that does not have a
a directory-container storage pool as the target storage converting state. Ensure that a storage pool that does
pool. If restarting, specify the same target storage pool not have a converting state is named as the next
which was originally used for the conversion process, storage pool by issuing the UPDATE STGPOOL
or issue the command without the target storage pool command and specifying the NEXTstgpool parameter.
parameter.
ANR3671E Storage pool storage pool is either
ANR3667W Unable to connect by FASP with server converted or is being converted and
server name on port port name. cannot perform migration or reclamation
between storage pools.
Explanation: An attempt to estblish connectivity with
a target server using specified port failed. The Explanation: The storage pool is in a conversion state
operation will use the existing TCP/IP session to and cannot migrate or reclaim data to another storage
communicate with the target server. pool.
System action: The server operation continues. System action: The request will be denied for the
storage pool in conversion state.
User response: Examine the source and target server
activity logs for information related to FASP User response: Use the MOVE DATA, or MOVE
Byte-Stream activity. NODEDATA, commands to move specific groups of
data out of the storage pool. Data can only be moved if
there are no conversion processes active for the storage
ANR3668E Command: Invalid attempt to change the
pool.
access state for storage pool storage pool.
Explanation: The access state for a storage pool cannot
ANR3672E The license file that is required to
be changed once it has been converted. In addition, a
enable Aspera Fast Adaptive Secure
storage pool cannot be manually changed to a
Protocol (FASP) technology was not
conversion state.
found on the server_loc server.
Explanation: An attempt to use the Aspera FASP data
command.
transfer method failed because the license file
User response: No action is required. (aspera-license) was not found on the source or target
server.
ANR3669W There is at least one reference to storage System action: System operations continue. However,
pool storage pool as a policy or nextpool data cannot be transferred by using Aspera FASP
destination. When the storage pool technology unless a valid license file is installed.
conversion starts the storage pool can no
longer ingest or store new data.
following steps:
Explanation: There is limited write access to the 1. Obtain and install a valid license file. Follow the
storage pool during conversion. The storage pool instructions in technote 7047418
cannot store new files from either client sessions or (http://www.ibm.com/support/
server processes. Server operations for the converted docview.wss?uid=swg27047418).
storage pool might be limited or unavailable. Storage

2. Retry the node replication or data protection

ANR3677E Storage pool storage pool is either
operation.
converted or is being converted and
cannot be the target of a migration or
ANR3673E One of the FASP related files is invalid reclamation operation.
or corrupt.
Explanation: The storage pool is in a conversion state
Explanation: Server replication attempted to use fasp and cannot be the target of migration or reclamation.
as the communication method and either the source or
System action: The request will be denied for the
target server lacked a valid aspera file.
storage pool.
System action: Server replication will not proceed
User response: Update the stgpool that is attempting
until the communication method is changed or a valid
to migrate or reclaim into the converted stgpool to
set of files are obtained and installed.
point to a valid target.
User response: Obtain an Aspera license file and place
it in the server bin directory as aspera-license, an
ANR3678E Unable to initialize FASP driver - thread
Aspera Configuration file place in the server bin
creation failed.
directory as aspera.config, and the faspstream
component of the Aspera SDK place as faspstream in Explanation: The server is unable to initialize the
the server bin directory. FASP driver due to an error creating a server thread.
System action: Server operation continues, but FASP
ANR3674E Unable to find aspera.conf file on support is inoperative.
server_loc server.
User response: This error often results from a lack of
Explanation: Server replication attempted to use fasp memory. Ensure that your system has sufficient paging
as the communication method and either the source or space to support the current activities.
target server lacked the appropriate aspera.conf file.
System action: Server replication will not proceed ANR3679W You cannot convert data that is stored in
until the communication method is changed or a valid copy storage pools or active-data storage
Aspera configuration file is obtained and installed. pools. When you issue the CONVERT
STGPOOL command, copies of files that
User response: Obtain an Aspera configuration file
are stored in primary storage pool
and place it in the server bin directory as aspera.conf.
storage pool are deleted. You must update
copy storage pools and active-data
ANR3675E Unable to find faspstream executable on storage pools that are used by Disaster
server_loc server. Recovery Management.
Explanation: Server replication attempted to use fasp Explanation: When the storage pool is successfully
as the communication method and either the source or converted, all data and copies of data in existing
target server lacked the appropriate faspstream storage pools are removed. Use the PROTECT STGPOOL
executable. command to protect data in container storage pools or
use the REPLICATE NODE command to replicate data in
System action: Server replication will not proceed other types of storage pools. Use the SET
until the communication method is changed or a valid DRMCOPYSTGPOOL and the SET DRMACTIVEDATASTGPOOL
Aspera faspstream executable is obtained and installed. commands to specify the names of the copy storage
User response: Obtain an Aspera faspstream pools and active-data storage pools to recover data
executable and place it in the server bin directory as from after a disaster.
faspstream. System action: The administrator is asked whether to
continue.
ANR3676E Storage pool storage pool is actively being User response: Enter 'Y' to convert the storage pool or
converted and cannot perform any data 'N' to stop the process.
movement or deletion.
Explanation: Conversion is in progress for the storage ANR3680W The storage pool conversion is cancelled
pool. for storage pool pool name.
System action: The storage pool cannot perform the Explanation: During conversion processing, for the
command. storage pool that is specified, the conversion process
User response: Cancel all CONVERT STPGOOL was cancelled. The server might display this message
processes for this stgpool, or wait until they have more several times during the conversion cancellation.
completed. System action: The storage pool conversion is ended

and server operation continues. User response: To resolve the issue, complete the
following steps:
User response: To convert the storage pool again,
reissue the CONVERT STGPOOL command. 1. Obtain and install a valid license file. Follow the
instructions in technote 7047418
(http://www.ibm.com/support/
ANR3681E The license file that is required to docview.wss?uid=swg27047418).
Protocol (FASP) technology has expired
on the server_loc server. ANR3685W The license file that is required to
Explanation: An attempt to use the Aspera FASP data Protocol (FASP) technology expires
transfer method failed because the license file has today.
expired on the source or target server.
Explanation: The Aspera FASP data transfer license
System action: System operations continue. However, file will expire on the source or target server.
data cannot be transferred by using Aspera FASP
technology unless a valid license file is installed. System action: System operations continue. However,
unless a long term license is acquired, data will
User response: To resolve the issue, complete the eventually stop being transferred using Aspera FASP
following steps: technology.
1. Obtain and install a valid license file. Follow the
following steps:
docview.wss?uid=swg27047418). 1. Obtain and install a valid license file. Follow the
2. Retry the node replication or data protection
operation.
docview.wss?uid=swg27047418).
ANR3682W Container container name is empty and

ANR3686W Source storage pool source_pool is
cannot be moved.
referenced by Disaster Recovery
Explanation: You cannot move an empty container. Management. After conversion, you
cannot restore data to the source storage
System action: The container is skipped. Server pool and disaster recovery might fail.
Explanation: When conversion starts, the source
User response: Reissue the MOVE CONTAINER storage pool cannot ingest or store new data. Use the
command for a container that contains data. QUERY DRMSTATUS command and the SET
DRMPRIMSTGPOOL command to view and update primary
ANR3683E Source storage pool storage pool is storage pools that are used by Disaster Recovery
converting to a directory-container Management.
storage pool and cannot be renamed. System action: The administrator is asked whether to
Explanation: Conversion is in progress for the source continue.
storage pool. User response: Enter 'Y' to convert the storage pool or
System action: The source storage pool cannot be 'N' to stop the process.
renamed during conversion processing.
User response: When conversion completes, reissue ANR3687E Transaction failed for session session
the RENAME STGPOOL command again. number for node node name (client
platform) - container transaction timeout
encountered.
ANR3684I The evaluation license id that is
required to enable Aspera Fast Adaptive Explanation: The server ends a database update
Secure Protocol (FASP) technology will transaction for the specified client because the client
expire in days days. did not commit the transaction before the timeout
period. The timeout period is controlled by the
Explanation: The Aspera FASP data transfer license CONTAINERRESOURCETIMEOUT option
file will expire on the source or target server.
System action: System operations continue. However, server operation continues.
unless a long term license is acquired, data will
eventually stop being transferred using Aspera FASP User response: Determine why the operation did not
technology. commit the transaction within the timeframe specified
by the option. The option might need to be increased to

allow for the ingest operation to commit the transaction System action: The activity that generated this error
over a longer period of time. fails.
User response:
ANR3688E A file was skipped while converting
data to storage pool storage pool name.
ANR3704E Source file(line number): Unable to load
File name file name for Node node name,
the jvm for the cloud storage pool.
File space filespace name is excluded
because of its size. Explanation: An error occurred while attempting to
load the jvm for the cloud storage pool.
Explanation: The server skips the conversion for the
specified file. The size of the file is larger than that System action: The activity that generated this error
allowed in the storage pool based on the MAXSIZE fails.
parameter setting.
User response:
System action: The file is skipped by the conversion
process.
ANR3705E Source file(line number): Error locating the
User response: Increase the maximum file size for the dsmcloud.jar file.
target storage pool specified by the CONVERT
STGPOOL command. An authorized administrator can Explanation: An error occurred while attempting to
increase the MAXSIZE parameter by issuing the load the dsmcloud.jar file for the cloud storage pool.
UPDATE STGPOOL command. The file can also be System action: The activity that generated this error
moved to another storage pool that allows for storage fails.
of larger objects.
User response:
ANR3701E Cannot connect to the cloud service

provider for the operation_name operation ANR3706W Reorganization is required on table table
on the pool_name storage pool. name, which is excluded from online
reorganization.
Explanation: A request to the cloud service provider
failed because the client system is not connected to the Explanation: The specified table was excluded from
cloud server. online reorganization by the DISABLEREORGTABLE
server option.
fails. System action: Server operation continues.
User response: Ensure that you specify valid User response: A failure to reorganize tables when
credentials for the connection to the cloud server and necessary can lead to database growth and server
that the client system can communicate with the cloud performance degradation over time. If you experience
server. either of these symptoms, consider running an offline
reorganization of the specified table. For instructions,
see the section about offline table reorganization in
ANR3702E Cannot connect to the cloud service Technote 1683633: http://www.ibm.com/support/
provider for the operation_name operation docview.wss?uid=swg21683633#offline_table_reorg
on the pool_name storage pool.
Explanation: The connection to the cloud provider ANR3707E An unexpected error occurred while
failed because the cloud service provider that is when the storage pool directory was
specified in the DEFINE STGPOOL command is not opened or when data was written to the
valid. storage pool directory. The access mode
System action: The activity that generated this error for storage pool directory Directory Name
fails. in storage pool Pool Name was changed
to Access Mode.
User response: Ensure that you specify valid
credentials for the connection to the cloud server and Explanation: The access mode is changed for the
that the client system can communicate with the cloud specified storage pool directory.
server. System action: Client nodes cannot access the storage
pool and server processes cannot be completed.
ANR3703E Source file(line number): Unable to connect User response: Ensure that the storage pool directory
to the cloud provider. is accessible on the file system. To change the access
Explanation: An error occurred while attempting to mode, issue the UPDATE STGPOOLDIR command and
connect to the cloud provider. specify the ACCESS parameter.

ANR3708E The storage pool stgpool name cannot be ANR3712E Command: Storage pool NEXTSTGPOOL:
defined as a cloud storage pool with storage pool name is a cloud pool.
this operating system.
Explanation: The command cannot be processed on name of a storage pool which is a cloud pool. The
this operating system. command syntax requires that a cloud storage pool
name not be specified for non-container storage pools.
command.
User response: Use an operating system that is
compatible with IBM Spectrum Protect to issue the User response: Reissue the command with a valid
command. For information about operating systems storage pool name.
that are supported by IBM Spectrum Protect, see
technote 1243309 "Overview - IBM Spectrum Protect
ANR3713W Container Container Name was marked
Supported Operating Systems" (http://www-
for deletion but stgpool directory Stgpool
01.ibm.com/support/docview.wss?uid=swg21243309).
Directory is unavailable.
Explanation: The container had no chunks on it and
ANR3709W Container container name was
was marked for deletion. Deletion failed because the
permanently deleted from the file
container's stgpool directory access was not available.
system.
System action: The system will not remove this
Explanation: The specified container could not be
container until the stgpool directory's access is
found in the database. For this reason, the container
available.
was deleted from the file system.
User response: Update the stgpool directory's access
System action: The container is no longer available,
to read/write and wait for container deletion to occur
but system operation continues.
again.
ANR3714E Cannot connect to the cloud service
ANR3710I This command will delete container provider with the cloud URL, url, for the
container name from the file system. operation_name operation on the
pool_name storage pool.
Explanation: Because the specified container could not
be found in the database, it will be deleted from the file Explanation: The connection to the cloud service
system. provider failed because the cloud URL that is specified
in the DEFINE STGPOOL command cannot be
System action: You are prompted to confirm the
resolved.
action.
User response: Enter 'Y' to delete the container from
fails.
the file system or 'N' to cancel the command.
User response: Verify that the cloud url, user ID and
password for the cloud storage pool are correct and
ANR3711E Container container name will not be
have been entered correctly, and verify that the cloud
removed from the file system.
provider is active.
Explanation: The container will not be removed
To remove damaged data from a cloud storage pool
because its header could not be validated.
without communicating with the cloud provider, issue
System action: System operation continues. the AUDIT CONTAINER ACTION=MARKDAMAGED
command to mark all data on the container as
User response: To manually remove the container damaged.
from the file system, delete the file. If the server is
installed on an AIX, Linux, or Solaris system, issue the
following command: rm container_name If the server is ANR3715E A request to the cloud service provider
installed on a Windows system, issue the following for the operation_name operation on the
command: del container_name pool_name storage pool failed with the
following HTTP status:
UNAUTHORIZED.
failed. The credentials for the cloud service provider do
not have the correct permissions to perform the activity
that generated this error.

System action: The activity that generated this error User response: Ensure that the cloud server is still
fails. turned on.
User response: Ensure that the permissions are correct
for the credentials that are specified for the connection ANR3719E The operation_name operation on the
to the cloud server. pool_name storage pool failed because
the container_name cloud container does
not exist.
ANR3716E A request to the cloud service provider
for the operation_name operation on the Explanation: A request to the cloud provider failed.
pool_name storage pool failed with the The cloud container that was requested does not exist.
following HTTP status code:
http_status_code.
fails.
User response: Verify that the container has not been
failed. The cloud service provider responded with a
removed from the cloud server.
non-successful HTTP status code.
If you want to remove data from a cloud storage pool
fails.
the AUDIT CONTAINER ACTION=MARKDAMAGED
User response: Review the following list of HTTP command to mark all data on the container as
status codes you might encounter in this situation: damaged, and then issue the AUDIT CONTAINER
v 401 Unauthorized: The request was valid, but command with ACTION=REMOVEDAMAGED
authentication was required and failed, or FORCEORPHANDBDEL=YES to remove the data.
authentication was not provided.
v 403 Forbidden: The request was valid, but the server ANR3720E A request to the cloud service provider
refused to respond to it. for the operation_name operation on the
v 404 Not Found: The requested resource could not be pool_name storage pool failed with a
found, but it might be available again in the future. HTTP protocol error.
v 409 Conflict: The request could not be processed Explanation: A request to the cloud service provider
because of a conflict in the request. failed from a HTTP error.
For more information about HTTP status codes, consult System action: The activity that generated this error
your object storage provider. fails.
for the operation_name operation on the
pool_name storage pool failed with the
following HTTP status:
pool_name storage pool failed with an
CREDENTIAL_ERROR.
internal error.
Explanation: A request to the cloud provider failed
failed. The cloud service provider credentials do not
because of an internal error.
exist.
fails.
fails.
User response: Ensure that the credentials that are
provided to the cloud server exist on the cloud service
provider. ANR3722E A request to the cloud service provider
pool_name storage pool failed with a
creation error.
pool_name storage pool failed because Explanation: A request to the cloud service provider
the cloud connection was lost. failed because output cannot be written to an XML file.
Explanation: A request to the cloud service provider System action: The activity that generated this error
failed. The connection to the cloud service provider fails.
was lost.
fails.

ANR3723E A request to retrieve cloud metrics for ANR3726I The AUDIT DATABASE command is
the operation_name operation on the processing for all container storage
pool_name storage pool failed with an pools. Do no complete storage pool
internal error. operations during this process.
Explanation: A request to retrieve cloud metrics failed Explanation: The AUDIT DATABASE command scans
because of an internal error. multiple tables in the database. Storage pool operations
that are processing when you issue the AUDIT
DATABASE command might affect the audit result.
fails.
System action: Confirm whether to proceed with the
AUDIT DATABASE command.
ANR3724E Command: Data in storage pool storage
the command.
pool name is not protected on server
target server name.
ANR3727E AUDIT CONTAINER: The
Explanation: The specified storage pool has not been
STGPOOLDIRECTORY parameter
protected by the replication target server, or a
cannot be used on this cloud-container
previously issued REPAIR STGPOOL command
storage pool because local storage is not
invalidated the protect setting for the replicated target
available for this storage pool.
storage pool. As a result, you cannot use the REPAIR
STGPOOL command to repair from the replicated Explanation: The command cannot be processed as
target storage pool until the PROTECT STGPOOL specified.
command is issued for the replicated target storage
pool. Any REPAIR STGPOOL commands to the local
target storage pool are unaffected. User response: Verify that local storage is available for
the cloud-container storage pool, and reissue the
command.
command.
User response: If you have not already set the target
ANR3728E MOVE CONTAINER: You cannot move
replication server, issue the SET REPLSERVER
the following container: container name.
command to specify the target replication server that
will be used to protect the storage pool. The name Explanation: The container that you specified is a
specified in the SET REPLSERVER command must be cloud container. The MOVE CONTAINER command
associated with a valid server definition. Issue the does not apply to cloud containers.
PROTECT STGPOOL command with a value of
TYPE=REPLSERVER for the specified storage pool. For System action: The command fails and the server
example, if the source storage pool is named POOL1, operation continues.
issue the following command: protect stgpool pool1 User response: Select a different type of container to
type=replserver By issuing the command, you restore move.
the protect setting on the specified storage pool.
ANR3729I The AUDIT CONTAINER command

ANR3725E Objects on the cloud provider for the process process id completed: delete object
following storage pool storage pool name count damaged objects are deleted. skip
are not deleted. object count damaged objects are
Explanation: The cloud provider is not available to skipped. delete cloud orphan object count
delete a cloud object. orphan objects are deleted in
cloud-container storage pools. skip cloud
System action: The server deletes the objects from the orphan object count orphan objects are
database. skipped in cloud-container storage
pools.
User response: Ensure that the cloud server is on and
that the credentials are correct. To remove the cloud Explanation: When you issue the AUDIT
objects that remain on the cloud server, issue the CONTAINER command and specify the
AUDIT CONTAINER command. ACTION=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 are

ANR3732E Storage pool poolname cannot be updated
skipped.
because of an encryption key mismatch.
The objects being processed are inventory files, data
Explanation: The master encryption key changed since
extents or both.
this pool was enabled for encryption. The storage pool
System action: None. cannot be updated without the original master
encryption key.
ANR3730E The audit container operation process_id User response: If you used the BACKUP DB
failed because it cannot communicate command to protect the server master key, use the
with the cloud provider for container RESTORE DB command to restore the original server
container_name. password file (dsmserv.pwd).
Explanation: The AUDIT CONTAINER command
failed either because the correct credentials were not ANR3733W The master encryption key cannot be
provided to the cloud provider or because the cloud generated because the server password
provider is inactive. is not set.
System action: The AUDIT CONTAINER command Explanation: Without a master encryption key, storage
failed. pool encryption is disabled.
User response: Verify that the user ID and password System action: The master encryption key is not
for the cloud storage pool are correct and have been generated.
entered correctly, and verify that the cloud provider is
User response: Use the SET SERVERPASSWORD
active.
command to set a server password. After you set the
To remove damaged data from a cloud storage pool password, the master key is automatically generated.
the AUDIT CONTAINER ACTION=MARKDAMAGED
ANR3734E Storage pool encryption could not be
command to mark all data on the container as
enabled because the server has not been
damaged.
configured to protect the encryption
keys using database backup.
Explanation: Database backup must be configured to
protect the master encryption key to enable stgpool
pool_name storage pool failed with the
encryption.
503 HTTP status code.
Explanation: The status code indicates that the
operation cannot proceed. The cloud provider cannot User response: To protect the server master
process further incoming requests. There might be a encryption key during database backup, specify the
hardware limitation or an issue with the configuration PROTECTKeys=Yes and PASSword parameters on the
settings. SET DBRECOVERY command.
System action: The server is running, however, the
cloud service provider cannot respond to the request. ANR3735W The protect storage pool process for
stgpool name on this server to stgpool name
User response: Verify with your system administrator
on other server is complete. Some extents
that the cloud service provider has the correct
might not have been protected. Extents
configuration settings and enough dedicated hardware
protected: extents protected of extents to
to accept additional requests.
protect. Extents failed to protect: extents
v Proxy-server.conf; [default] node_timeout = 120, failed to protect. Extents deleted: extents
[app:proxy-server] conn_timeout = 120. deleted of extents to delete. Amount
v Object-server.conf; [default] node_timeout = 60, protected: amount protected of amount to
[app:object-server] set node_timeout = 60. protect. Amount failed: amount transferred.
Amount transferred: amount transferred.
In each .conf file, either set 'workers = auto' or set that Elapsed time: elapsed time.
configuration equal to a value no greater than the
number of cores on the system. Explanation: The protect storage pool process
completed but some extents might have been skipped
due to conflicting operations. The following list
describes the information in the message:

v Extents protected: Extents that were successfully ACTION=REMOVEDAMAGED parameter specified to

protected by being linked to matching extents on the remove the orphaned extents.
target server.
If the cloud provider is inactive or inaccessible, and the
v Extents failed to protect: Extents that were not references to the orphaned extents should be removed
successfully protected during the process of from the database anyway, reissue the AUDIT
protecting to the target server. CONTAINER command and specify the
v Extents deleted: Extents that were successfully ACTION=REMOVEDAMAGED and
deleted from the target server because the extent did FORCEORPHANDBDEL=YES parameters.
not exist on the source server or because it was
damaged on the target server and needed to be
ANR3738I Command: Storage pool storage pool name
resent.
still has one or more containers.
v Amount protected: Bytes that were successfully
protected by being linked to matching extents on the Explanation: A DELETE STGPOOL command
target server. encountered a storage pool that still contains one or
more containers.
v Amount failed: Bytes that were not protected. See
previous messages for further details. System action: The server does not process the
v Amount transferred: Bytes that were sent to the command.
target server during this process. The amount that User response: Empty containers are automatically
was transferred can be less than the amount that is deleted every few minutes. Wait for the automatic
protected when the target server already has some of deletion of the empty containers, then reissue the
the extents or when compression is enabled. command.
v Elapsed time: How long the process ran.
User response: Issue the PROTECT STGPOOL ANR3740E One or more orphaned extents in the
command again to ensure that all data extents are stgpool_name storage pool were skipped
scanned and protected. because the extents could not be deleted
from the cloud.
ANR3736E The requested data with the key key for Explanation: One or more orphaned extents could not
the operation_name operation on the be deleted from the cloud, so they were not removed
pool_name storage pool was not found in from the database. This might be a result of lack of
the container_name cloud container. The connectivity to the cloud service provider.
container should be audited to validate
its contents. System action: The orphaned extents that were not
deleted from the cloud are skipped. They remain
Explanation: The requested data was not found on the orphaned in the database.
cloud service provider.
User response: Verify that the cloud URL, user ID,
System action: The command fails. and password for the cloud-container storage pool are
correct and were entered correctly. Also, verify that the
User response: Run the AUDIT CONTAINER
cloud provider is active. Reissue the AUDIT
command on the container or the storage pool.
CONTAINER command with the
ACTION=REMOVEDAMAGED parameter specified to
ANR3737E One or more orphaned extents in the remove the orphaned extents.
container_name container in the
If the cloud provider is inactive or inaccessible, and the
stgpool_name storage pool were skipped
references to the orphaned extents should be removed
because the extents could not be deleted
from the database anyway, reissue the AUDIT
from the cloud.
CONTAINER command and specify the
Explanation: One or more orphaned extents could not ACTION=REMOVEDAMAGED and
be deleted from the cloud, so they were not removed FORCEORPHANDBDEL=YES parameters.
from the database. This might be a result of lack of
connectivity to the cloud service provider.
ANR3741E Failed to update the stgpool_name storage
System action: The orphaned extents that were not pool: cannot change from the
deleted from the cloud are skipped. They remain current_cloud_type cloud type to the
orphaned in the database. new_cloud_type cloud type.
User response: Verify that the cloud URL, user ID, Explanation: An UPDATE STGPOOL command
and password for the cloud-container storage pool are resulted in error because of an incompatible change in
correct and were entered correctly. Also, verify that the cloud type. To minimize accidental errors, you cannot
cloud provider is active. Reissue the AUDIT change from the current cloud type to the cloud type
CONTAINER command with the you specified.


ANR3745I Session session number ended for Aspera
FASP high speed data transfer.
User response: If you still need to update the storage
Explanation: An Aspera FASP High Speed Data
pool, reissue the UPDATE STGPOOL command and
Transfer session has completed normally.
make sure that the CLOUDTYPE parameter is set to a
value that is compatible with the current cloud type of System action: Server operation continues.
the storage pool. Another option is to not specify a
value for the CLOUDTYPE parameter.
ANR3746E The operation_name operation on the

ANR3742W This command attempts to update the
pool_name storage pool failed because
stgpool_name storage pool. One or more
the container_name bucket or vault does
of the attributes being updated by this
not exist in this region or access pool.
command might affect your ability to
access existing data in this storage pool. Explanation: A request to the cloud provider failed.
The bucket or vault that was requested does not exist
Explanation: The execution of an UPDATE STGPOOL
in the region or access pool pointed to by the storage
command with the parameters that have been specified
pool.
by this command might prevent you from accessing
existing data. System action: The activity that generated this error
fails.
System action: The system asks the administrator
whether to continue with the command. User response: Ensure that the CLOUDURL value for
this storage pool is directed to a location that can
access the bucket or vault.
the command.
ANR3747E command: The parameter parameter is not

supported on this platform or with this
configuration.
pool_name storage pool failed with an
exception. Explanation: The command cannot be processed as
specified because the platform does not support the
Explanation: The cloud client encounters an
feature required by the given parameter, or the
exceptions in processing the operation_name cloud
configuration of the server has not enabled the feature.
operation.
System action: The operation_name cloud operation is
ended and server operation continues. User response: Verify the command syntax, platform,
and configuration then reissue the command.
examine messages prior to this error and examine
FFDC (First Failure Data Capture) file to determine the ANR3748E The license file that is required to
cause of the operation failure. If the cause of the failure enable Aspera Fast Adaptive Secure
can be found and resolved, reissue the command. If the Protocol (FASP) technology has expired
cause of failure cannot be found, contact your service on the server_loc server.
representative for assistance in resolving the problem.
Explanation: An attempt to use the Aspera FASP data
transfer method failed because the license file has
ANR3744I Session session number started for Aspera expired on the source or target server.
FASP high speed data transfer and is
paired with replication session session System action: System operations continue. However,
number. data cannot be transferred by using Aspera FASP
technology unless a valid license file is installed.
Explanation: A new server session has been initiated
by the specified server for Aspera FASP High Speed User response: To resolve the issue, complete the
Data Transfer. The parent session number is included in following steps:
the message. 1. Obtain and install a valid license file. Follow the
System action: The server begins a FASP (http://www.ibm.com/support/
communications session to service the process. docview.wss?uid=swg27047418).
User response: None. 2. Retry the node replication or data protection
operation.

and ensure that the default vault template is deployed

ANR3749I Aspera evaluation license currently in
to the access pool which contains the accesser to which
use to allow FASP transfer method. .
this storage pool points. Then run the command again.
Explanation: An Aspera FASP high speed data
transfer session was established using a 30 day Aspsera
ANR3828E The command specified multiple Amazon
evaluation license.
endpoints in the CLOUDURL parameter.
System action: Server operation continue.
Explanation: The command specified a CLOUDURL
User response: The 30 day evaluation license expires parameter that listed multiple endpoints for an
30 days from the day it was generated. Amazon object storage system.
ANR3751E The specified credentials failed command.
verification because the container_name
User response: Reissue the command with only one
bucket or vault does not exist in this
Amazon endpoint specified in the CLOUDURL
region or access pool.
parameter.
Explanation: To use this bucket or vault, the
CLOUDURL parameter must match the region or
ANR3829I The AUDIT CONTAINER process
access pool in which this bucket or vault exists.
process_id ended for the stgpool_name
System action: None. storage pool: inspected_extents cloud
objects inspected and orphaned_extents
User response: Ensure that the CLOUDURL value for
data extents marked as orphaned.
this storage pool is directed to a location that can
access the bucket or vault. Explanation: The orphaned extent identification
generated the following information:
ANR3825E Command: Transfer Method transfer v The number of cloud objects inspected
method is not valid. v The number of orphaned data extents
Explanation: The transfer method must be one of tcp System action: None.
or fasp on a platform that supports fasp.
User response: To remove orphaned extents from
System action: The server does not process the cloud containers, issue the AUDIT CONTAINER
command. command and specify the
ACTION=REMOVEDAMAGED parameter.
User response: Update the PROTECT STGpool
parameter for the pool you are trying to protect.
ANR3830E The command command specified the
same endpoint multiple times in the
ANR3826E Command: Transfer Method transfer
CLOUDURL parameter.
method is not valid.
Explanation: The command contained a CLOUDURL
Explanation: The transfer method must be one of tcp,
parameter that specified one or more endpoints
or fasp on a platform that supports fasp.
multiple times.
command.
command.
User response: Update the Replicate Node parameter
User response: Reissue the command with a
for the node you are trying to replicate.
CLOUDURL parameter that specifies each endpoint
only once.
ANR3827E A request to create a container on the
pool_name storage pool failed the access
ANR3831E FASP session Session identifier aborted
pool does not have a vault template.
due to outstanding FASP read or write
Explanation: A request to create a container failed timeout threshold exceeding timeout
because a default vault template was not specified, or value seconds.
the default vault template was not deployed to the
Explanation: The FASP session between the server
specified accesser.
and the partner system experienced an IO timeout
System action: The activity that generated this error condition while transferring data.
fails.
System action: The session with the remote system is
User response: Ensure that the IBM Cloud Object ended.
Storage dsNet has a default vault template specified,
User response: Ensure that the specified remote

system is operational and is properly configured to run encountered with a type that is not supported by
Aspera FASP. Adjust the server option FaspSessTimeout directory-container storage pools.
accordingly.
System action: The file is not converted.
User response: After the storage pool enters the
ANR3832I Local to Cloud Transfer process process
Converted state, issue the MOVE DATA command on
identifier for storage pool storage pool
the volume to move the inconvertible files to another
name started.
storage pool.
Explanation: A process begins to transfer data from
local storage to the cloud.
ANR3999E Failure validating database load:
System action: The indicated process is started. expected numRecs records and numBV bit
vectors - loaded actNumRecs records and
actNumBV bit vectors.
Explanation: The database load process has ended
ANR3833I Local to Cloud Transfer process process
and the number of records, the number of bit vectors,
identifier for storage pool storage pool
or both the number of records or number of bit vectors
name has completed.
loaded, failed to validate.
Explanation: The process of transferring data from
System action: The LOAD DB process completes with
local storage to the cloud has completed.
a failure. The server database is not in a usable state.
User response: A number of possible causes exist. To
User response: None. recover from this situation, first retry the database load
process. If the error reoccurs, check the activity log or
other system logs to determine if there is a hardware or
ANR3834I Container container name is empty and media error. If a hardware or media error exists, correct
will not be transferred during process the error and retry the load process. If a hardware or
process identifier. media error does not exist, it is likely the dump or
Explanation: The local-storage-to-cloud transfer unload of the server database has encountered an error
process will not move empty containers to the cloud. resulting in the dump/unload server database image as
being unusable or that there is an error in the logic for
System action: The local storage container was load db processing. Contact your service representative
skipped during this transfer process. for assistance.
ANR4000I The protect storage pool process for
ANR3835E Command: The process of validating stgpool name on server this server to
aspera connection to targetservername stgpool name on server other server is
failed. complete. Extents protected: extents
protected of extents to protect. Extents
Explanation: An error occurred while initializing failed to protect: extents failed to protect.
validate aspera. Amount protected: amount protected of
System action: The validate aspera command is amount to protect. Amount failed to
ended, but server operation continues. protect: amount not protected. Extents
deleted: extents deleted of extents to delete.
User response: No action is required. Extents failed to delete: extents failed to
delete. Extents moved: extents moved for
volume reclamation of extents to move.
ANR3836I Validation of the Aspera FASP
Extents failed to move: extents not moved
connection from srcserver to targetserver.
for volume reclamation. Amount moved:
Amount transferred using FASP: faspmbs
amount moved for volume reclamation of
MB per second. Amount transferred
amount to move. Amount failed to move:
using TCP/IP: tcpipmbs MB per second.
amount not moved for volume reclamation.
Latency: latency microseconds. Status:
Elapsed time: elapsed time.
status. Days until license expires: expires.
Explanation: The protect storage pool process is
complete. The following list describes the information
ANR3998W CONVERT STGPOOL is skipping an
in the message:
inconvertible file on volume volume:
Node node_name, Type type, File space v Extents protected: Extents that were successfully
file_space, File name file_name. copied to the target container-copy storage pool.
Explanation: During the convert process, a file is

v Amount protected: Bytes that were successfully of extents to delete. Extents failed to
protected by being copied to the target delete: extents failed to delete. Extents
container-copy storage pool. moved: extents moved for volume
v Amount failed: Bytes that were not protected. See reclamation of extents to move. Extents
previous messages for further details. failed to move: extents not moved for
volume reclamation. Amount moved:
v Extents deleted: Extents that were deleted from the
amount moved for volume reclamation of
directory-container storage pool and have been
amount to move. Amount failed to move:
removed from the copy-container storage pool.
amount not moved for volume reclamation.
v Extents moved: Extents that were successfully Elapsed time: elapsed time.
recopied to the target container-copy storage pool
because a volume was eligible for reclamation. Explanation: The protect storage pool process
completed but some extents might have been skipped
v Amount moved: Bytes that were successfully
due to conflicting operations. The following list
recopied to the target container-copy storage pool.
describes the information in the message:
v Amount failed to move: Bytes that were not
v Extents protected: Extents that were successfully
recopied. See previous messages for further details.
copied to the target container-copy storage pool.
v Elapsed time: How long the process ran.
protected by being copied to the target
ANR4001I The preview of protect storage pool container-copy storage pool.
stgpool name on server this server to v Amount failed: Bytes that were not protected. See
stgpool name on server other server is previous messages for further details.
complete. Extents to be protected: extents
v Extents deleted: Extents that were deleted from the
to be protected. Amount to be protected:
directory-container storage pool and have been
amount to be protected. Extents to be
deleted: extents to be deleted. Extents to be
moved: extents to be moved for volume v Extents moved: Extents that were successfully
reclamation. Amount to be moved: amount recopied to the target container-copy storage pool
to be moved for volume reclamation. because a volume was eligible for reclamation.
v Amount moved: Bytes that were successfully
Explanation: The storage pool protection preview is
recopied to the target container-copy storage pool.
in the message: v Amount failed to move: Bytes that were not
recopied. See previous messages for further details.
v Extents to be protected: Extents that need to be
protected by being copied to the target v Elapsed time: How long the process ran.
container-copy storage pool. User response: Issue the PROTECT STGPOOL
v Amount to be protected: Bytes that need to be command again to ensure that all data extents are
protected by being linked to matching extents on the scanned and protected.
target server.
v Extents to be deleted: Extents that were deleted from ANR4003I Load command: Database load process
the directory-container storage pool that need to be started.
Explanation: The database load process has started.
v Extents to be moved: Extents that need to be
recopied to the target container-copy storage pool System action: The server loads the contents of the
because a volume was eligible for reclamation. database from a file or removable media.
v Amount to be moved: Bytes that need to be recopied User response: None.
to the target container-copy storage pool because a
volume was eligible for reclamation.
ANR4004I Load command: Database load process
completed.
ANR4002W The protect storage pool process for
stgpool name on this server to stgpool name Explanation: The database load process has ended.
on other server is complete. Some extents
System action: The server completes processing.
might not have been protected. Extents
protected: extents protected of extents to User response: None.
protect. Extents failed to protect: extents
failed to protect. Amount protected:
amount protected of amount to protect.
Amount failed to protect: amount not
protected. Extents deleted: extents deleted


ANR4005E Load command: Database load process
terminated due to error (error indicator).
ANR4010E Dump/load command: Database dump/load
Explanation: The database load process has ended
processing failed - insufficient memory.
prematurely due to an error.
Explanation: The database dump/load process fails
System action: The server ends load processing.
due to insufficient memory.
User response: Examine previously issued messages
System action: Database processing ends.
to determine if an error can be corrected, such as a
syntax error. If you cannot resolve the error, contact User response: Allocate additional storage to the
your service representative. server. There are two ways to do this:
v Increase the size of the server's virtual machine (for
ANR4006I Command: Volume volume number written VM), or region size (for MVS). For AIX, ensure that
by process is volume name. there is sufficient paging space. You may also use
SMIT to determine if the number of applications is
Explanation: A sequential data process wrote to the causing a memory shortage. For OS/2, ensure that
volume named in the series of one or more volumes there is sufficient space for the OS/2 SWAPPER.DAT
that were used to store output. The volume's position file. Check your CONFIG.SYS for the SWAPPATH
in the series in indicated by the volume number statement to determine where your SWAPPER.DAT
reported. file is located and then determine how much space is
System action: The server ends processing. left on the drive.
v Decrease the amount of space allocated to the
server's database or log buffer pool. To do this,
update the value of the BUFPOOLSIZE or
ANR4007E Command: A transaction error was LOGPOOLSIZE parameters in the server options file
encountered in recording volume usage and restart the server. Note that each page causes an
history. additional 4K page to be allocated for the specified
buffer pool. Reducing the pool sizes requires more
Explanation: The command process encounters a I/O to service the same amount of data; some
database transaction error in recording the names of the performance degradation may result.
volumes used for the process in the server database.
System action: The server ends processing. ANR4012W Dump command: Database page page
User response: Examine previously issued messages number is damaged.
to determine if there is an error that can be corrected, Explanation: The specified database page is damaged;
such as a syntax error. If you cannot resolve the error, it will not be dumped.
contact your service representative. The volumes used
by the process are valid for the corresponding input System action: Processing continues.
process, but are not recorded in sequential volume
history lists generated by the server.
ANR4013I Audit command process process id

ANR4008W Load command: Database object object
completed audit of total number
name does not exist.
containers; successful number successfully
Explanation: The database load process attempts to audited containers, failed number failed
delete a database object, but the object does not exist. audited containers.
System action: Database processing continues. Explanation: The AUDIT CONTAINER command has
completed processing.
The following information is displayed:
ANR4009E Load command: Database object object v The total number of containers that were audited.
name cannot be deleted because it is in v The number of successfully audited containers.
use by another process. v The number of containers that failed to audit.
Explanation: The database load process attempts to System action: None.
delete a database object, but the object is currently
being used by another process. User response: None.
System action: Database processing ends.

User response: Reissue the command. If it fails,

ANR4014W Audit container process process id is ANR4018E Load command: Load processing failed -
canceled. insufficient recovery log space.
Explanation: During processing of an AUDIT Explanation: The load process fails due to insufficient
CONTAINER command, the process performing the recovery log space.
audit was canceled.
System action: Database load processing ends.
System action: The AUDIT CONTAINER command is
User response: Reinstall the server and specify a
canceled.
larger recovery log and reissue the database load
ANR4015E Load command: Invalid record format ANR4019E Load command: Load processing failed -
(format code) detected. insufficient database space.
Explanation: During processing of command load Explanation: The load process fails due to insufficient
command, an invalid record type is detected when database space.
reading the dumped information from the dump
System action: Load processing ends.
media.
User response: Reinstall the server and specify a
larger database and reissue the database load
User response: Examine the server messages issued command.
error. On MVS or VM, the LOADDB command syntax
ANR4020E Load command: Batch database insert
may be specified by using a ddname or by specifying a
failed.
device class name. You must use the same method that
was used when the database was originally dumped. If Explanation: The database load process fails when it
you did not, this error message will be displayed. Try attempts to insert a batch of rows into the database.
loading the database by using the other method of
syntax (devclass). If the error cannot be isolated and System action: Database load processing ends.
resolved, contact your service representative. User response: Examine the messages issued prior to
this one to determine if an error can be corrected. You
ANR4016E Load command: Invalid header sequence may wish to reinstall the server with a new recovery
number detected in database dump. log and database and reissue the load command. If the
Expected expected sequence number; Actual problem persists, contact your service representative.
actual sequence number.
Explanation: During processing of command load ANR4021E Dump/load command: Error (error code)
command, an invalid sequence number is detected when occurred during an open operation.
reading the dumped information from the dump Explanation: An error occurs while attempting an
media. open operation on the dump media for a database
System action: Processing of the command ends. dump/load operation.
User response: Examine previously issued server System action: Server processing continues.
messages to determine the source of the error. If the User response: Refer to the other displayed messages
error cannot be isolated and resolved, contact your to determine why the operation failed; correct the
service representative. problem and restart the process.
ANR4017E Load command: Invalid record type record ANR4022E Dump command: Error (error code)
type read from database dump data. occurred during a write operation.
Explanation: The server database load process Explanation: The server database dump process
encounters an invalid record in reading data from the encounters an error while writing to the dump media.
dump media.
System action: Server processing continues, the dump
System action: The database load process ends. processing ends.
User response: Examine previously issued server User response: Refer to the other displayed messages
messages to determine the source of the error. If the to determine why the operation failed; correct the
error cannot be isolated and resolved, contact your problem and restart the process.

for recovery purposes. Depending on the system

ANR4023E Load command: Error (error code) occurred
environment, the scan might take hours or days.
during a read operation.
System action: System operation continues during the
Explanation: The server database load process
scan.
encounters an error reading from the dump media.
User response: No action is required. However, you
System action: The database load operation ends.
can cancel the scan by issuing the following command
User response: Refer to the other displayed messages from the server console or the administrative client:
to determine why the operation failed; correct the set replrecoverdamaged off
problem and restart the process.
ANR4029I A scan to identify damaged files is in

ANR4025W The AUDIT DATABASE command progress. If damaged files are detected,
process id ended. Command processing is a recovery process will begin after the
canceled. scan is completed.
Explanation: The AUDIT DATABSE command was Explanation: A REPLICATE NODE command initiated
canceled during processing. a process to identify and recover damaged files. The
System action: The AUDIT DATABASE command server scans database tables to identify which damaged
ended. files are eligible for recovery. Depending on the system
environment, the scan might take hours or days. The
User response: Reissue the AUDIT DATABASE server issues periodic ANR4024I messages to indicate
command. that the scan is ongoing. When the scan is completed,
message ANR3650I will appear on the server console.
ANR4026I The AUDIT DATABASE command System action: Server operation continues during the
process started (process ID process ID). scan. If the scan identifies files that are eligible for
Explanation: The AUDIT DATABASE command recovery, the recovery process begins.
process started for the process whose ID that is User response: No action is required.
displayed.
System action: The AUDIT DATABASE command ANR4030E The replication process failed because of
process is in progress. an inconsistency between extents on the
User response: This process may be monitored using source server and extents on the target
the QUERY PROCESS command. If this process needs server that were written by a PROTECT
to be cancelled, issue the CANCEL PROCESS STGPOOL process.
command. Explanation: The REPLICATE NODE process detected
that extents that were written to the target server by a
ANR4027I The AUDIT DATABASE command PROTECT STGPOOL process are inconsistent and out
process process id completed processing of sync with the source server. The REPLICATE NODE
total number orphaned data extents. process will end as FAILURE.
Explanation: The AUDIT DATABASE command System action: None.

completed. User response: Issue the PROTECT STGPOOL
The following information is displayed: command, and verify that the process has completed.
Then, issue the REPLICATE NODE command again.
v The total number of orphaned data extents that are
processed
ANR4031I PROTECT STGPOOL: Reclamation
System action: None. processing started for container-copy
User response: For programming support, contact storage pool target pool.
your service representative. Explanation: The PROTECT STGPOOL command
started reclamation processing for the specified
ANR4028I A scan for damaged files is in progress. container-copy storage pool. The reclamation process is
Processed count damaged file(s). intended to move data from underutilized volumes and
thus release space.
Explanation: If the REPLRECOVERDAMAGED
system parameter is set to ON, the system monitors System action: Processing continues.
server database tables every 30 minutes to determine User response: None.
whether the number of damaged bitfiles has changed.
If the number has changed, the system initiates a scan
of server database tables to identify the damaged files

ANR4032W PROTECT STGPOOL: All data in ANR4074I Dump/load command: Encountered number
directory-container storage pool source of entries bad database entries.
pool was protected to container-copy
Explanation: This message is displayed at the end of a
storage pool target pool. However,
server database dump or load command to indicate the
reclamation processing for the
number of invalid database entries that have been
container-copy storage pool is
encountered.
incomplete.
System action: Database dump or load processing
Explanation: The PROTECT STGPOOL command
ends.
protected all data in the specified directory-container
storage pool to the specified container-copy storage User response: None.
pool. This ensures that the directory-container storage
pool can be repaired if needed. However, reclamation
processing for the container-copy storage pool is ANR4075I Audit command: Auditing policy
incomplete because the reclamation process was definitions.
canceled. The reclamation process is intended to move Explanation: This message is displayed during a
data from underutilized volumes and thus release database audit and indicates that the server policy
space. information (domain, policy set, management classes,
System action: The storage pool protection process and copy groups) are being examined by the database
ends. audit process.
User response: If the container-copy storage pool is System action: Audit processing continues.
running out of space or if this message is issued User response: None.
frequently, consider increasing the maximum run time
for the schedule that runs the storage pool protection
process. If the container-copy storage pool has sufficient ANR4076E Audit command: Invalid client node count
space and this message is issued infrequently, no action detected for policy domain domain name.
is required. Explanation: A database audit process finds that the
count of nodes recorded for the specified policy
ANR4033I Update stgpooldir command process process domain do not match the actual number of nodes
id completed update of stgpooldir name; assigned to the domain.
successful number successfully updated System action: Audit processing continues.
containers, failed number failed updated
containers. User response: Reissue the audit command and
specify FIX=YES so that the error can be corrected.
Explanation: The UPDATE STGPOOLDIR command
has completed processing.
ANR4077I Audit command: Invalid client node count
The following information is displayed: detected for policy domain domain name
v The stgpool directory updated. count will be corrected.
v The number of successfully updated containers. Explanation: A database audit process finds that the
v The number of containers that failed to update. count of nodes recorded for the specified policy
domain do not match the actual number of nodes
assigned to the domain. Because FIX=YES has been
User response: None. specified for the command, the node count will
automatically be corrected.
ANR4034W Update Stgpooldir process process id is System action: Audit processing continues.
canceled.
Explanation: During processing of an UPDATE
STGPOOLDIR command, the process performing the
ANR4078E Audit command: Invalid activation
audit was canceled.
indicators encountered for policy
System action: The UPDATE STGPOOLDIR process is domain domain name.
canceled.
Explanation: A database audit process finds incorrect
User response: None. policy set activation entries for the specified policy
domain.
User response: Reissue the audit command and

specify FIX=YES so that the error can be corrected. the audit command, the default value will be set.
ANR4079I Audit command: Invalid activation
indicators encountered for policy
domain domain name - entry will be
corrected. ANR4084E Audit command: Invalid administrator
update information encountered for
policy set activation entries for the specified policy
domain. Because FIX=YES has been specified for the Explanation: A database audit process finds incorrect
audit command, the entry will be corrected. last updated information for the specified policy
domain.
ANR4080E Audit command: Invalid grace period
backup retention value encountered for
policy domain domain name. ANR4085I Audit command: Invalid administrator
Explanation: A database audit process finds an
policy domain domain name - information
incorrect grace period retention value for the specified
will be corrected.
policy domain.
last updated information for the specified policy
User response: Reissue the audit command and domain. Because FIX=YES has been specified for the
specify FIX=YES so that the error can be corrected. command, the information is corrected.
ANR4081I Audit command: Invalid grace period
backup retention value encountered for
policy domain domain name - default
value will be set. ANR4086E Audit command: Invalid node node number
found assigned to domain domain name.
incorrect grace period retention value for the specified Explanation: A database audit process finds a node
policy domain. Because FIX=YES has been specified for number assigned to a policy domain that does not
the audit command, the default value will be set. reference a valid client node definition.
System action: Audit processing continues. System action: Audit processing continues.
User response: None. User response: Reissue the audit command and
ANR4082E Audit command: Invalid grace period
archive retention value encountered for ANR4087I Audit command: Invalid node node number
policy domain domain name. found assigned to domain domain name
reference will be deleted.
incorrect grace period retention value for the specified Explanation: A database audit process finds a node
policy domain. number assigned to a policy domain that does not
reference a valid client node definition. Because
FIX=YES has been specified for the audit command, the
User response: Reissue the audit command and reference will be deleted.
ANR4083I Audit command: Invalid grace period
archive retention value encountered for
policy domain domain name - default ANR4088E Audit command: Default management
value will be set. class management class name specified for
policy set policy set name in domain
domain name does not exist.
incorrect grace period retention value for the specified
policy domain. Because FIX=YES has been specified for Explanation: A database audit process finds a policy

set with a default management class specified that does last updated information for the specified policy set.
not exist. Because FIX=YES has been specified for the command,
the information is corrected.
specify FIX=YES so that the error can be corrected. User response: None.
ANR4089I Audit command: Default management ANR4093E Audit command: A management class
class management class name specified for identifier is not defined for
policy set policy set name in domain management class management class name
domain name does not exist - the in policy set set name, domain domain
reference will be removed. name.
Explanation: A database audit process finds a policy Explanation: A database audit process finds incorrect
set with a default management class specified that does information for the specified management class.
not exist. Because FIX=YES has been specified for the
audit command, the reference will be removed from the
policy set. User response: Reissue the audit command and
User response: When the audit command completes,
ANR4094E Audit command: A management class
examine the policy set specified, and set a new default
identifier is not defined for
management class for the set. If the policy set is the
ACTIVE policy set, you must activate a new policy set
in policy set set name, domain domain
for the domain with a valid default management class.
name - an identifier will be generated
for this management class.
ANR4090E Audit command: Active Policy set for
domain domain name does not contain a
information for the specified management class. The
valid default management class - policy
audit process generates an identifier, because FIX=YES
will fail for this domain. Correct the
has been specified for the audit command.
ACTIVE policy set.
Explanation: A database audit process finds an active
policy set for the specified policy domain that does not User response: None.
have a valid active management class specified.
System action: Audit processing continues. ANR4095E Audit command: An invalid management
class identifier (actual identifier) was
User response: When the audit command completes,
encountered for management class
you must activate a new policy set for the domain with
management class name in policy set set
a valid default management class.
name, domain domain name (expected
expected identifier).
ANR4091E Audit command: Invalid administrator
information for the specified management class.
policy set set name in policy domain
domain name. System action: Audit processing continues.
Explanation: A database audit process finds incorrect User response: Reissue the audit command and
last updated information for the specified policy set. specify FIX=YES so that the error can be corrected.
ANR4096E Audit command: An invalid management
class identifier (actual identifier) was
encountered for management class
management class name in policy set set
ANR4092I Audit command: Invalid administrator name, domain domain name (expected
update information encountered for expected identifier) - the correct identifier
policy set set name in policy domain will be stored.
domain name - information will be
corrected.
information for the specified management class. The
Explanation: A database audit process finds incorrect audit process corrects the identifier, because FIX=YES

has been specified for the audit command.

ANR4101I Audit command: A backup copy group
System action: Audit processing continues. already exists - the invalid copy group
will be deleted.
Explanation: A database audit process encounters a
copy group that has an invalid name or copy group
ANR4097E Audit command: Invalid administrator type. While attempting to reinsert the copy group as a
update information encountered for backup copy group, the process discovers that a
management class management class name backup copy group already exists for the management
in policy set set name in policy domain class. The copy group is deleted.
domain name.
last updated information for the specified management User response: After the audit command completes,
class. you may examine the server copy groups using the
QUERY COPYGROUP command, and correct them
System action: Audit processing continues. with the DEFINE COPYGROUP and UPDATE
User response: Reissue the audit command and COPYGROUP commands if desired.
ANR4102I Audit command: Attempting to reinsert
ANR4098I Audit command: Invalid administrator the copy group as an ARCHIVE copy
update information encountered for group.
management class management class name Explanation: A database audit process encounters a
in policy set set name in policy domain copy group that has an invalid name or copy group
domain name - information will be type. The process attempts to reinsert the definition as
corrected. an archive copy group.
Explanation: A database audit process finds incorrect System action: Audit processing continues.
last updated information for the specified management
class. Because FIX=YES has been specified for the User response: None.
command, the information is corrected.
System action: Audit processing continues. ANR4103I Audit command: An archive copy group
already exists - the invalid copy group
User response: None. will be deleted.
Explanation: A database audit process encounters a
ANR4099E Audit command: Copy group copy group copy group that has an invalid name or copy group
name in management class management type. While attempting to reinsert the copy group as an
class name, policy set set name, domain archive copy group, the process discovers that a backup
domain name has an invalid name or copy group already exists for the management class.
type. The copy group is deleted.
Explanation: A database audit process encounters a System action: Audit processing continues.
type. User response: After the audit command completes,
you may examine the server copy groups using the
System action: Audit processing continues. QUERY COPYGROUP command, and correct them
User response: If FIX=YES has not been specified for with the DEFINE COPYGROUP and UPDATE
the audit command, reissue the command specifying COPYGROUP commands, if desired.
FIX=YES so that the error can be corrected.
ANR4104E Audit command: An invalid management
ANR4100I Audit command: Attempting to reinsert class identifier (actual identifier) was
the copy group as a BACKUP copy encountered for a copy group in
group. management class management class name,
policy set set name, domain domain name
Explanation: A database audit process encounters a (expected expected identifier).
type. The process attempts to reinsert the definition as Explanation: A database audit process finds incorrect
a backup copy group. information for the specified copy group.
User response: None. User response: Reissue the audit command and


ANR4109I Audit command: Invalid backup copy
group attributes encountered for copy
ANR4105E Audit command: An invalid management group copy group name in management
class identifier (actual identifier) was class management class name, policy set set
encountered for a copy group in name, domain domain name - the copy
management class management class name, group will be corrected using default
policy set set name, domain domain name attributes.
(expected expected identifier) - the correct
Explanation: A database audit process encounters
identifier will be stored.
invalid backup copy group attributes for the specified
Explanation: A database audit process finds incorrect copy group. Because FIX=YES has been specified for
information for the specified copy group. The audit the command, the copy group will be corrected using
process corrects the identifier, since FIX=YES has been default values for the attributes found in error.
specified for the audit command.
User response: After the audit command completes,
User response: None. examine the copy group by using the QUERY
COPYGROUP command, and correct attributes with
the UPDATE COPYGROUP command, if desired.
ANR4106E Audit command: An invalid copy group
identifier (actual identifier) was
encountered for a copy group in ANR4110E Audit command: Invalid archive copy
management class management class name, group attributes encountered for copy
policy set set name, domain domain name group copy group name in management
(expected expected identifier). class management class name, policy set set
name, domain domain name.
information for the specified copy group. Explanation: A database audit process encounters
invalid archive copy group attributes for the specified
System action: Audit processing continues. copy group.
User response: For programming support, contact System action: Audit processing continues.
User response: If FIX=YES has not been specified for
the audit command, reissue the command and specify
ANR4107E Audit command: An invalid copy group FIX=YES so that the inconsistency can be corrected.
identifier (actual identifier) was
encountered for copy group name copy
group name (expected expected identifier). ANR4111I Audit command: Invalid archive copy
group attributes encountered for copy
Explanation: A database audit process finds incorrect group copy group name in management
information for the specified copy group name. class management class name, policy set set
System action: Audit processing continues. name, domain domain name - the copy
group will be corrected using default
User response: For programming support, contact attributes.
invalid archive copy group attributes for the specified
ANR4108E Audit command: Invalid backup copy copy group. Because FIX=YES has been specified for
group attributes encountered for copy the command, the copy group will be corrected using
group copy group name in management default values for the attributes found in error.
class management class name, policy set set
name, domain domain name. System action: Audit processing continues.
Explanation: A database audit process encounters User response: After the audit command completes,
invalid backup copy group attributes for the specified examine the copy group by using the QUERY
copy group. COPYGROUP command, and correct the attributes
with the UPDATE COPYGROUP command, if desired.
User response: If FIX=YES has not been specified for ANR4112W Audit command: Storage pool storage pool
the audit command, reissue the command specifying name, specified as a destination for copy
FIX=YES so that the inconsistency can be corrected. group copy group name in management
class management class name, policy set set

name, domain domain name, does not

ANR4116I Audit command: Policy domain domain
exist.
name is referenced, but not formally
Explanation: A database audit process encounters a defined - a policy domain with default
storage pool specified for the destination of the attributes will be defined with this
specified copy group that is not defined in the server name.
database. If this copy group is used in an active policy
Explanation: A database audit process finds a
set, then backup or archive operations will fail when
reference to the specified policy domain, but the
attempting to put client data in the destination.
domain is not formally defined in the server database.
System action: Audit processing continues. Because FIX=YES has been specified, a new policy
domain with this name will be defined by the audit
User response: After the audit command completes, processor.
use the DEFINE STGPOOL command to define the
missing storage pool or the UPDATE COPYGROUP System action: Audit processing continues.
command to update the copy group to refer to an
User response: After the audit command has
existing storage pool.
completed, you can view the attributes for this policy
domain using the QUERY DOMAIN command, and
ANR4113E Audit command: Invalid administrator update attributes with the UPDATE DOMAIN
update information encountered for command, if desired.
copy group copy group name in
management class management class name,
ANR4117E Audit command: Policy set set name in
policy set set name, policy domain domain
domain domain name is referenced, but
name.
not formally defined.
last updated information for the specified copy group.
reference to the specified policy set, but the set is not
System action: Audit processing continues. formally defined in the server database.
User response: Reissue the audit command and System action: Audit processing continues.
ANR4114I Audit command: Invalid administrator
ANR4118I Audit command: Policy set set name in
copy group copy group name in
domain domain name is referenced, but
management class management class name,
not formally defined - a policy set with
policy set set name, policy domain domain
this name will be created.
name - information will be corrected.
reference to the specified policy set, but the set is not
last updated information for the specified copy group.
formally defined in the server database. Because
Because FIX=YES has been specified for the command,
FIX=YES has been specified, the audit process will
the information is corrected.
create a new policy set with this name.
completed, you can view the attributes for this policy
ANR4115E Audit command: Policy domain domain set by using the QUERY POLICYSET command, and
name is referenced, but not formally update attributes with the UPDATE POLICYSET
defined. command, if desired.
reference to the specified policy domain, but the ANR4119E Audit command: Management class class
domain is not formally defined in the server database. name in policy set set name, domain
domain name is referenced, but not
System action: Audit processing continues. formally defined.
User response: Reissue the audit command and Explanation: A database audit process finds a
specify FIX=YES so that the error can be corrected. reference to the specified management class, but the
class is not formally defined in the server database.


ANR4123I Audit command: The instance count for
management class class name does not
agree with the actual management class
ANR4120I Audit command: Management class class data (number of instances instances) - the
name in policy set set name, domain number will be corrected.
domain name is referenced, but not
formally defined - the management class
reference count for the specified management class that
will be created.
does not match the actual number of instances for this
Explanation: A database audit process finds a class. The audit process corrects the count because
reference to the specified management class, but the FIX=YES has been specified for the audit command.
class is not formally defined in the server database.
Because FIX=YES has been specified for the audit
command, the audit process defines a management User response: None.
class in the server with this name.
System action: Audit processing continues. ANR4124E Audit command: The instance count for
copy group copy group name does not
agree with the actual copy group data
completed, you can view the attributes for this
(number of instances instances).
management class by using the QUERY MGMTCLASS
command, and update attributes with the UPDATE Explanation: A database audit process finds a
MGMTCLASS command, if desired. reference count for the specified copy group that does
not match the actual number of instances for this copy
group.
ANR4121E Command: An operation that was
initiated by the MOVE DRMEDIA System action: Audit processing continues.
command is in progress for volume
volume name.
Explanation: A subsequent command was issued, and
it specifies the same volume. The newly issued
ANR4125I Audit command: The instance count for
command cannot be completed for the specified
copy group copy group name does not
volume while the MOVE DRMEDIA command is in
agree with the actual copy group data
progress.
(number of instances instances) - the
System action: If the newly issued command is a number will be corrected.
MOVE NODEDATA command, the server skips the
volume and continues moving node data on other
reference count for the specified copy group that does
volumes.
not match the actual number of instances for this copy
User response: Wait until the operation that was group. The audit process corrects the count because
initiated by the MOVE DRMEDIA command is FIX=YES has been specified for the audit command.
completed. Then, reissue the other command.
ANR4122E Audit command: The instance count for
management class class name does not
agree with the actual management class ANR4126E Audit command: Policy global attributes
data (number of instances instances). cannot be found.
Explanation: A database audit process finds a Explanation: A database audit process is not able to
reference count for the specified management class that locate the global attributes for policy information in the
did not match the actual number of instances for this server database.
class.
User response: Reissue the audit command and specify FIX=YES so that the error can be corrected.


ANR4127I Audit command: Policy global attributes
cannot be found - attributes will User response: None.
recreated.
Explanation: A database audit process is not able to ANR4132I Audit volume process ended for volume
locate the global attributes for policy information in the volume name; file count files inspected, file
server database. Because FIX=YES has been specified count damaged files deleted, file count
for the audit command, the attributes will be damaged files marked as damaged, file
regenerated. count files previously marked as
damaged reset to undamaged, file count
objects updated.
Explanation: The AUDIT VOLUME command
specifying FIX=YES for the volume shown has ended.
ANR4128E Audit command: Policy global high-water
The following information is displayed:
marks do not match the identifiers in
use. v The number of files audited
v The number of inconsistent files deleted
Explanation: A database audit process finds the
attributes used to track policy identifiers are incorrect. v The number of inconsistent files marked as damaged
v The number of files previously marked as damaged
that were reset to undamaged
User response: Reissue the audit command and v The number of updated objects
The number of files marked as damaged includes all
ANR4129E Audit command: Policy global high-water files belonging to aggregates that were marked
marks do not match the identifiers in damaged during the audit. Files are marked as
use - they will be corrected. damaged in primary storage pools and not deleted
when backup copies for the files are known to exist in
Explanation: A database audit process finds the COPY storage pools.
attributes used to track policy identifiers are incorrect.
Because FIX=YES has been specified for the audit System action: None.
command, the attributes will be corrected. User response: To recover files that have been marked
System action: Audit processing continues. as damaged on the volume, use the RESTORE
STGPOOL or RESTORE volume command.
ANR4133I Audit volume process ended for volume

ANR4130W Audit Volume updating object volume name; file count files inspected, file
information for volume volume name: count damaged files found and marked
Node node name, Type file type, File space as damaged, file count files previously
filespace name, fsId filespace id , File Name marked as damaged reset to undamaged,
file name. file count objects need updating.
Explanation: As the result of an AUDIT VOLUME Explanation: The AUDIT VOLUME command
command that specified FIX=YES for the volume specifying FIX=NO for the volume shown has ended.
shown, object information for the specified file will be
updated. The following information is displayed:
v The number of files audited
System action: The object information is updated.
v The number of inconsistent files marked as damaged
v The number of files previously marked as damaged
that were reset to undamaged
ANR4131W Audit Volume found incorrect object v The number of objects need updating
information for volume volume name:
Node node name, Type file type, File space The number of files marked damaged includes all files
filespace name, fsId filespace id, File name belonging to aggregates that were marked damaged
file name. during the audit. Inconsistent files are marked as
Explanation: As the result of an AUDIT VOLUME damaged in the database and can be recovered by
command that specified FIX=NO for the volume using the RESTORE STGPOOL or RESTORE VOLUME
shown, object information for the specified file is found command if copies of the files reside in a COPY storage
to be in error. pool. Another AUDIT VOLUME command may be able
to access the files and reset the damaged indicator in

the database if the audit volume process cannot access command with the BUCKETNAME parameter set to a
the files due to hardware problems (for example, dirty bucket or vault with a different name.
tape heads).
System action: None. ANR4137E Container creation failed because the
current credentials do not have
User response: If you suspect that files were
permission for disallowed_operation_name
inaccessible because of hardware problems such as
operations on the bucket or vault.
dirty tape heads, correct the hardware problem and
reissue the AUDIT VOLUME FIX=NO command for Explanation: The credentials for the cloud service
this volume. To remove damaged file references and provider do not have permission to do all of the
update the object information, issue the AUDIT required operations in this storage pool's bucket or
VOLUME command and specify FIX=YES. vault. As a result, the container was not created.
System action: Container creation was not allowed.
ANR4134E Command: The "parameter" parameter is
User response: Check the permissions for the bucket
not valid for cloud storage pools of this
or vault and make sure that the credentials for this
cloud type.
storage pool have permission to read, write, list, and
Explanation: The command indicated specifies a delete objects in this bucket or vault. If you do not
parameter that is not valid for cloud storage pools of have the ability to change or view the permissions, and
this cloud type. you have not already written data to this storage pool,
you can use the UPDATE STGPOOL command with
the BUCKETNAME parameter to try to use a different
command.
bucket or vault.
User response: Reissue the command with parameters
appropriate for this cloud type.
ANR4138E A create container request to the cloud
service provider for the pool_name
ANR4135E Command: Command could not be storage pool failed because the name of
completed because storage pool storage the bucket or vault that this storage pool
pool name has one or more cloud attempted to use is not valid for this
containers. cloud service provider.
Explanation: The command could not be completed Explanation: A create container request failed. The
because the storage pool contains one or more cloud name of the bucket or vault that this storage pool
containers that use the existing bucket name. attempted to use is not valid for this cloud service
provider.
command. System action: The create container request fails.
User response: Before reissuing the command, ensure User response: Bucket and vault names must comply
that the command and all of the specified parameters with S3 requirements, which can be found in the
are allowed when cloud containers already exist in the Amazon S3 documentation online. Also, check with
storage pool. your cloud service provider for any specific restrictions
on bucket or vault names. Use the UPDATE STGPOOL
command with the BUCKETNAME parameter set to a
ANR4136E A create container request to the cloud name that complies with both the S3 requirements, and
service provider for the pool_name the cloud provider restrictions.
storage pool failed because the bucket
or vault this storage pool attempted to
use is not accessible with the cloud ANR4139W The PROTECT STGPOOL settings for
provider credentials provided. the replicated target storage pool are
invalid. To resolve the issue, the
Explanation: A create container request failed. The PROTECT STGPOOL command needs
credentials for the cloud service provider did not have to be manually issued for storage pool
the correct permissions for the bucket or vault that this source storage pool name.
storage pool attempted to use.
Explanation: A previously issued REPAIR STGPOOL
System action: The create container request fails. command invalidated the protect setting for the
User response: Ensure that the permissions are correct replicated target storage pool. As a result, you cannot
for the credentials you specified for connecting to the use the REPAIR STGPOOL command to repair from the
cloud server. As needed, change the settings on the replicated target storage pool until the PROTECT
bucket or vault. If you do not have the ability to STGPOOL command is issued for the replicated target
change the bucket settings, use the UPDATE STGPOOL storage pool. Any REPAIR STGPOOL commands to the
local target storage pool are unaffected.


ANR4143E The credentials for the cloud storage
User response: Issue the PROTECT STGPOOL pool could not be verified because the
command with a value of TYPE=REPLSERVER for the necessary information was not available.
specified storage pool. By issuing the command, this
Explanation: The credentials could not be verified
will restore the protect setting on the source storage
because the cloud type, the URL, the cloud ID, or the
pool.
cloud password was not specified, and the storage pool
provided did not have values for the missing
ANR4140E The specified credentials failed parameter or parameters.
verification because they do not have
permission for disallowed_operation_name
operations on the bucket or vault. User response: Either reissue the command while
specifying all of the necessary parameters, or specify
Explanation: The credentials for the cloud service
the storage pool name of an existing cloud storage
provider do not have permission to do all of the
pool.
required operations in this bucket or vault.
ANR4144E Command: Cloud-container storage pool
User response: Check the permissions for the bucket storage pool name was not found.
or vault and make sure that the credentials for this
Explanation: The specified storage pool is either
storage pool have permission to read, write, list, and
undefined or is not a cloud-container storage pool.
delete objects in this bucket or vault. If you do not
have the ability to change or view the permissions, try System action: The server does not process the
a bucket or vault with a different name. command.
ANR4141E The specified credentials failed cloud-container storage pool name.
verification because the name of the
bucket or vault that was provided was
ANR4248E Audit command: Missing or incorrect
not valid for this cloud service provider.
information for storage volume volume
Explanation: Credential verification failed because the name.
name of the bucket or vault that was specified is not
Explanation: A database audit process finds a data
valid for this cloud service provider.
storage volume for which information is missing or
System action: None. incorrect.
User response: Bucket and vault names must comply System action: Audit processing continues.
with S3 requirements, which can be found in the
Amazon S3 documentation online. Also, check with
FIX=YES so that the information can be created or
your cloud service provider for any specific restrictions
corrected.
on bucket or vault names. Use a bucket or vault name
that complies with both the S3 requirements, and the
cloud provider restrictions. ANR4249E Audit command: Missing or incorrect
information for storage volume volume
name - information will be created or
ANR4142I The cloud service provider URL and
corrected.
credentials were verified, and there is
not a bucket or vault on the specified Explanation: A database audit process finds a data
cloud service provider with the storage volume for which information is missing or
provided name. incorrect. Since FIX=YES has been specified for the
audit command, the information will be created or
Explanation: The verification of the credentials and
corrected.
URL for the cloud service provider succeeded.
However, the specified bucket or vault does not yet System action: Audit processing continues.
exist.
User response: If these credentials also have ANR4250E Audit command: Extraneous reference
permission to create a bucket or vault, it is safe to found.
create a storage pool with these parameters. If not, then
this bucket or vault should be created by other means, Explanation: A database audit process finds a
and these credentials should have read, write, delete, reference to a nonexistent entity such as a storage pool
and list access to the bucket or vault. or volume.

User response: Reissue the audit command with User response: Reissue the audit command and
FIX=YES so that the non-existant entity is recreated, if specify FIX=YES so that the error can be corrected.
possible. If recreation is not possible, the extraneous
reference is deleted.
ANR4323E Audit command: Management class class
name in policy set set name, domain
ANR4251E Audit command: Extraneous reference domain name does not have a valid space
found - information will be recreated or management technique defined - the
deleted. default value will be set.
Explanation: A database audit process finds a Explanation: A database audit process finds a
reference to a nonexistent entity such as a storage pool management class that does not have a valid value
or volume. Since FIX=YES has been specified for the specified. Because FIX=YES was specified for the
audit command, the nonexistant entity will be AUDITDB operation, the default space management
recreated, if possible. If recreation is not possible, the technique value will be set for the management class
extraneous information will be deleted. specified.
User response: None. User response: Refer to the DEFINE MGMTCLASS
command in IBM Knowledge Center for valid values.
ANR4298I Expiration thread already processing -
unable to begin another expiration ANR4324E Audit command: Management class class
process. name in policy set set name, domain
domain name does not have a valid
Explanation: The expiration thread is already
AUTOMIGNONUSE value specified.
processing. The processing expiration thread is either
an EXPIRE INVENTORY command or is the automatic Explanation: A database audit process finds a
background expiration process. In either case, another management class that does not have a valid value
expiration process cannot be started until the current specified.
expiration process completes or is canceled.
System action: Current expiration process continues.
User response: Use the QUERY PROCESS command specify FIX=YES so that the error can be corrected.
to determine the status of the current expiration
process.
ANR4299I command: Internal extent repair process domain name does not have a valid
is currently running. Audit command AUTOMIGNONUSE value defined - the
can not begin. default value will be set.
Explanation: The internal extent repair process is Explanation: A database audit process finds a
currently running. The audit command will not be able management class that does not have a valid value
to begin until it is idle. This will prevent the audit specified. Because FIX=YES was specified for the
command from reporting extents that are currently AUDITDB operation, the default AUTOMIGNONUSE
being repaired. value will be set for the management class specified.
System action: Server operation continues. System action: Audit processing continues.
User response: The internal extent repair proces will User response: Refer to the DEFINE MGMTCLASS
report ANR1758I when it becomes idle. Re-run the command in IBM Knowledge Center for valid values.
audit command at this time.
ANR4322E Audit command: Management class class name in policy set set name, domain
name in policy set set name, domain domain name does not have a valid
domain name does not have a valid space MIGREQUIRESBKUP value specified.
management technique defined.
Explanation: A database audit process finds a management class that does not have a valid value
management class that does not have a valid value specified.
specified.

User response: Reissue the audit command and operation completes.

Explanation: During the execution of a RECONCILE
VOLUMES command, any data a volume named
ANR4327E Audit command: Management class class would be unavailable to users.
domain name does not have a valid
continue.
MIGREQUIRESBKUP value defined -
the default value will be set. User response: Enter 'Y' to reconcile the volumes or
management class that does not have a valid value
specified. Because FIX=YES was specified for the ANR4333W This command will discard any
AUDITDB operation, the default MIGREQUIRESBKUP references to volumes used by the
value will be set for the management class specified. specified device class(es) that are
missing from the associated server,
thereby rendering the data
User response: Refer to the DEFINE MGMTCLASS unrecoverable; the valid volumes will
command in IBM Knowledge Center for valid values. be inaccessible to users until the
operation completes.
ANR4328W Audit command: Storage pool storage pool Explanation: During the execution of a RECONCILE
name, specified as a space management VOLUMES command, any data on a volume being
destination for management class reconciled would be unavailable to users. After the
management class name, policy set set command has ended, any inconsistent volumes found
name, domain domain name, does not will be discarded.
exist.
Explanation: A database audit process encounters a continue.
storage pool specified for the space management
User response: Enter 'Y' to reconcile the volumes or
destination of the specified management class that is
not defined in the server database. If this management
class is used in an active policy set, then migration
operations will fail when attempting to put client data ANR4334I command (Repair) process started,
in the destination. process ID process ID.
System action: Audit processing continues. Explanation: As the result of a RECONCILE
VOLUMES command that specified FIX=YES, the
User response: After the audit command completes,
process whose ID is displayed has begun reconciling
use the DEFINE STGPOOL command to define the
the volumes associated with the given device class.
missing storage pool or the UPDATE MGMTCLASS
command to update the management class to refer to System action: The volumes are reconciled and
an existing storage pool. invalid volumes are displayed.
ANR4331E command process terminated, no
matching device classes.
ANR4335I command (Inspect Only) process started,
Explanation: The server did not find any device class process ID process ID.
names matching the specifications entered in the
RECONCILE VOLUMES command. Explanation: As the result of a RECONCILE
VOLUMES command that specified FIX=NO, the
System action: Server operation continues. process whose ID is displayed has begun reconciling
the volumes associated with the given device class.
User response: Use the QUERY DEVCLASS command
to determine which device classes are defined on the System action: The volumes are reconciled and
server and reissue the RECONCILE VOLUMES inconsistent volumes are displayed.
command.
ANR4332W This command will compare all volumes

used by the specified device class(es) ANR4336W command process ended, process ID
with the actual data stored on the process ID.
associated server for those volumes and Explanation: The RECONCILE VOLUMES command
will report any discrepancies; the data for the specified device class has ended.
will be inaccessible to users until the

System action: None. System action: The RECONCILE VOLUMES

command is ended.
User response: For complete details on the results of
the RECONCILE VOLUMES command, examine the User response: Reissue the RECONCILE VOLUMES
previous messages. command.
ANR4337W command process terminated - process ANR4343W command process terminated - internal
canceled. server error detected.
Explanation: During processing of a RECONCILE Explanation: During processing of a RECONCILE
VOLUMES command, the process performing the VOLUMES command, an internal server error occurs
reconcile was canceled. on the source server.
System action: The RECONCILE VOLUMES System action: The RECONCILE VOLUMES
command is ended. command is ended.
User response: None. User response: Contact your service representative.
ANR4338W command process terminated - sufficient ANR4344I command started for device class device
recovery log space is not available. class (process ID process ID).
Explanation: During processing of a RECONCILE Explanation: The RECONCILE VOLUMES process
VOLUMES command, the source server does not have whose ID is displayed has started reconciling volumes
sufficient recovery log space to continue. associated with the given device class.
System action: The RECONCILE VOLUMES System action: The volumes are reconciled and
command is ended. inconsistent volumes are displayed.
User response: If necessary, make more recovery log User response: None.
space available to the source server.
ANR4345I command completed for device class
ANR4339W command process terminated - sufficient device class; (process ID process ID);
database space is not available. volume count volumes inspected, volume
count invalid volumes found, volume
Explanation: During processing of a RECONCILE
count volumes deleted.
VOLUMES command, the source server does not have
sufficient database space to continue. Explanation: The RECONCILE VOLUMES process
whose ID is displayed has finished reconciling volumes
System action: The RECONCILE VOLUMES
associated with the given device class. The number of
command is ended.
volumes reconciled and the number of invalid volumes
User response: If necessary, make more database found or deleted are displayed.
space available to the source server.
User response: For complete details on the results of
ANR4341W command process terminated - sufficient
the RECONCILE VOLUMES command for the shown
device class, examine the previous messages.
VOLUMES command, the source server does not have
ANR4346I command completed for device class
enough memory available to complete the command.
device class; (process ID process ID);
System action: The RECONCILE VOLUMES volume count volumes inspected, volume
command is ended. count invalid volumes found.
User response: If necessary make more memory Explanation: The RECONCILE VOLUMES process
available to the source server. whose ID is displayed has finished reconciling volumes
associated with the given device class. The number of
volumes reconciled and the number of invalid volumes
ANR4342W command process terminated - lock found are displayed.
conflict detected.
VOLUMES command, the source server cannot obtain a User response: For complete details on the results of
required lock. the RECONCILE VOLUMES command for the shown
device class, examine the previous messages. If you
suspect that volumes were inaccessible because of

communications problems, correct the problems and time. If the condition of the database on each server is
retry the RECONCILE VOLUMES command. If the acceptable and the RECONCILE VOLUMES command
errors are valid, reissue the reconcile volumes was issued with FIX=NO, reissue the RECONCILE
command with FIX=YES so that the source server can VOLUMES command with FIX=Yes to have the volume
attempt to correct the information. deleted from the target server.
ANR4352I Contacting Server server name ANR4356W command: Volume volume name not valid,
target server missing corresponding
entry for source server.
a QUERY PROCESS command, and indicates that a
reconciliation process is attempting to obtain volume Explanation: As the result of a RECONCILE
information from the shown server. VOLUMES command, the volume shown was found on
the source server and it has no matching volume on the
System action: The reconciliation process continues.
target server.
User response: The database on either the source or
target server has been regressed by either an RESTORE
Explanation: This message is displayed in response to DATABASE operation or some system facility external
a QUERY PROCESS command, and indicates that a to the server. Investigate the action that caused one or
reconciliation process has been canceled. The process both of the databases to be regressed to there current
will end shortly. condition. If a newer database images exist for that
server, consider restoring the server to that point in
System action: The reconciliation process terminates time. If the RECONCILE VOLUMES command was
and server operation continues. issued with FIX=Yes and the volume is defined in a
User response: None. storage pool, the access mode of the volume will
changed to unavailable to prevent attempted mounts
on the source server. If the condition of the database on
ANR4354W command: Source server not authorized each server is acceptable, issue the DELETE VOLUME
to reconcile target server server name. or DELETE VOLHISTORY command on the source
Explanation: During processing of a RECONCILE server to remove the volume from the database.
VOLUMES command, the source server was not
permitted to reconcile volume on the shown target ANR4357W command: Volume volume name not valid,
server. target server volume refers to device
System action: The reconciliation process continues. class device class that does not exist on
the source server.
User response: If the source server should have
permission to reconcile volumes on the shown target Explanation: As the result of a RECONCILE
server, issue the UPDATE SERVER command with VOLUMES command, the volume shown was found on
FORCESYNC=YES to cause the target server to accept the target server and it is associated with the device
reconcile operations for the source server. Reissue the class shown. The source server has NO corresponding
RECONCILE VOLUMES command. device class.
ANR4355W command: Volume volume name not valid, User response: The database on either the source or
source server missing corresponding target server has been regressed by either an RESTORE
entry for target server. DATABASE operation or some system facility external
Explanation: As the result of a RECONCILE to the server. Investigate the action that caused one or
VOLUMES command, the volume shown was reported both of the databases to be regressed to their current
by the target server and it has no matching volume on condition. If a newer database image exist for that
the source server. server, consider restoring the server to that point in
time. In the case of a volume in the VOLHISTORY, the
System action: The reconciliation process continues. device class may have been deleted from the source
User response: The database on either the source or server. If possible, issue the DEFINE DEVCLASS
target server has been regressed by either a RESTORE command to correct the situation. If the condition of
DATABASE operation or some system facility external the database on each server is acceptable and the
to the server. Investigate the action that caused one or RECONCILE VOLUMES command was issued with
both of the databases to be regressed to there current FIX=NO, reissue the RECONCILE VOLUMES
condition. If a newer database images exist for that command with FIX=Yes to have the volume deleted
server, consider restoring the server to that point in from the target server.

both the source and target servers. In the case of a

ANR4358W command: Volume volume name not valid,
volume in a storage pool, an AUDIT VOLUME
the attributes of the volume on target
FIX=NO will determine the integrity of the volume. If
server do not match the attributes on the
errors are found, an AUDIT VOLUME FIX=YES may
source server.
make some data on the volume accessible. Otherwise,
Explanation: As the result of a RECONCILE issue the DELETE VOLUME command on the source
VOLUMES command, the volume shown was found on server to remove the volume from both the source and
both the source and target server, but the attributes target servers.
describing the volume does not match.
System action: The reconciliation process continues. ANR4360W command: Volume volume name not valid,
the type of the volume on target server
does not match the type on the source
target server has been regressed by either a RESTORE
server.
DATABASE operation or some system facility external
to the server. Investigate the action that caused one or Explanation: As the result of a RECONCILE
both of the databases to be regressed to there current VOLUMES command, the volume shown was found on
condition. If a newer database image exist for that both the source and target server, but the type of the
server, consider restoring the server to that point in volume does not match. For example, the volume on
time. If the condition of the database on each server is the target server is defined in a storage pool, but the
acceptable, additional actions will have to be taken target server indicates that volume was used for a
because RECONCILE VOLUMES FIX=YES is unable to DATABASE BACKUP.
correct this situation. In the case of a volume in the
VOLHISTORY, an IMPORT PREVIEW=YES or a
RESTORE DATABASE PREVIEW=YES will determine User response: The database on either the source or
the integrity of the volume. If the volume is in error, a target server has been regressed by either an RESTORE
DELETE VOLHISTORY will remove the volume from DATABASE operation or some system facility external
both the source and target servers. In the case of a to the server. Investigate the action that caused one or
volume in a storage pool, an AUDIT VOLUME both of the databases to be regressed to there current
FIX=NO will determine the integrity of the volume. If condition. If a newer database image exists for that
errors are found, an AUDIT VOLUME FIX=YES may server, consider restoring the server to that point in
make some data on the volume accessible. Otherwise, time. If the condition of the database on each server is
issue the DELETE VOLUME command on the source acceptable, additional actions will have to be taken
server to remove the volume from both the source and because RECONCILE VOLUMES FIX=YES is unable to
target servers. correct this situation. These actions may have to be
performed on one or both servers. Use the QUERY
VOLHISTORY and QUERY VOLUME commands on
ANR4359W command: Volume volume name not valid,
both servers to determine the volume type on each
the size of the volume on target server
server. In the case of a volume in the VOLHISTORY, a
does not match the size on the source
DELETE VOLHISTORY on the appropriate server that
server.
will remove the volume on that server. In the case of a
Explanation: As the result of a RECONCILE volume in a storage pool, the DELETE VOLUME
VOLUMES command, the volume shown was found on command on the appropriate server will remove the
both the source and target server, but the size of the volume on that server.
volume does not match.
System action: The reconciliation process continues. ANR4361W command: Volume volume name not valid,
the target server has reported damage to
all or part of the volume.
target server has been regressed by either an RESTORE
DATABASE operation or some system facility external Explanation: As the result of a RECONCILE
to the server. Investigate the action that caused one or VOLUMES command, the volume shown was found on
both of the databases to be regressed to there current both the source and target server, but the target server
condition. If a newer database image exist for that has reported damage to all or part of the volume.
server, consider restoring the server to that point in
time. If the condition of the database on each server is
acceptable, additional actions will have to be taken User response: On the target server, an audit with
because RECONCILE VOLUMES FIX=YES is unable to FIX=NO of the volumes in the storage pool used by the
correct this situation. In the case of a volume in the source server will indicate what which volume on the
VOLHISTORY, an IMPORT PREVIEW=YES or a target server is damaged. This AUDIT VOLUME
RESTORE DATABASE PREVIEW=YES will determine command may be able to reset the damaged indicator
the integrity of the volume. If the volume is in error, a in the database if the damage was temporary due to
DELETE VOLHISTORY will remove the volume from hardware problems (for example, dirty tape heads). If

the volume on the target server is in a primary storage on the target server does not match the prefix in the
pool that has previously been backed up to a copy device class on the source server.
storage pool, attempt to correct the damage by using
the RESTORE STGPOOL command. If attempts to
correct the damage on the target server fail, an AUDIT User response: Verify that the prefix in the device
VOLUME command FIX=YES from the source server class on the source server is correct and update it if
will mark as damaged in the source server database necessary. Use the RECONCILE VOLUMES FIX=YES
each file that is inaccessible and those files will not be command on the source server to rename the target
accessed for future operations. If the files are part of an archive objects to match the device class on the source
aggregate, the entire aggregate will be marked server.
damaged. If a usable copy of the file exists in another
storage pool, that copy may be accessed for future
operations involving the file. ANR4366I command: Prefix for volume volume name
was changed to match the device class
prefix.
ANR4362W command: Invalid volume volume name
deleted from server server name for Explanation: As the result of a RECONCILE
device class device class. VOLUMES FIX=YES command, the beginning portion
of the high-level archive file name (the prefix) on the
Explanation: As the result of a RECONCILE target server was changed to match the prefix in the
VOLUMES command that specified FIX=YES, the device class on the source server.
volume shown whose information is displayed is
deleted from the target server. System action: The prefix is corrected.
System action: The volume is deleted. User response: None.

ANR4370E The source server is not authorized to
create volumes on target server server
ANR4363W command: Volume volume name access name.
changed to access mode.
Explanation: The source server has attempted to
Explanation: As the result of a RECONCILE create a volume on the shown target server, but the
VOLUMES command that specified FIX=YES, the operation failed because the source server does not
access mode of the source volume has been changed to have the authority to create volumes.
the value shown.
System action: The volume's access mode is changed.
User response: If the source server should have
User response: Review any additional messages permission to create volumes on the shown target
issued by the RECONCILE VOLUMES command and server, issue the UPDATE SERVER command with
correct the errors that set the volume to unavailable, or FORCESYNC=YES to cause the target server to accept
use the DELETE VOLUME command to remove it from volume create operations for the source server. Retry
the system. the failing operation.
ANR4364W command: Unable to connect to target ANR4371E Information on the source server does
server server name. not match information on target server
server name.
Explanation: During processing of indicated
command, the source server was unable to maintain Explanation: The source server has determined that
communications with the shown target server. information contained on the shown target server no
longer matches information contained on the source
System action: The command process continues.
server.
User response: Check both the source server and the
target server for any additional messages that might
further describe the communications problem. User response: Issue the RECONCILE VOLUMES
command to determine the problem. If possible, correct
the problem and retry the failing operation.
ANR4365W command: Prefix for volume volume name
does not match the device class prefix.
Explanation: As the result of a RECONCILE
VOLUMES command, the volume shown was found on
both the source and target server, but the beginning
portion of the high-level archive file name (the prefix)

ANR4372E The password on the source server does ANR4374E Session failure, source server detected
not match the password on target server an internal error.
server name.
Explanation: The source server ends the session
Explanation: The source server has attempted to because an internal logic error is detected.
update both the source password and the target
System action: The source server ends the session and
password. An error occurred that prevented the source
server from updating the target server. The passwords
no longer match. User response: To determine the source of the error,
the administrator can examine server messages issued
prior to this message. The QUERY ACTLOG command
User response: On the target server, issue the can be used to view the activity log and search for
UPDATE NODE command to change the password. On messages. If the error cannot be isolated and resolved,
the source server, issue the UPDATE SERVER contact your service representative.
command to change the password to match the new
password on the target server. Retry the failing
ANR4375E Session failure, source server has
operation.
insufficient memory.
Explanation: The source server ends the session
ANR4373E Session rejected by target server server
because sufficient memory (virtual memory) is not
name, reason: rejection reason.
available.
Explanation: The source server tried to open a session
with the target server. The session was rejected for the
indicated reason.
User response: Check both the source server and the application.
target server for any additional messages that might
further describe the reason the session was rejected. For
ANR4376E Session failure, target server server name
a reason of AUTHENTICATION FAILURE, ensure that
is locked on the source server.
both the source and target servers are using the same
password. For a reason of NO RESOURCE, ensure that Explanation: The source server ends the session
the target server is enabled, has sufficient DB, LOG, because shown target server is locked from source
and memory resource to support the source server server access.
session, and that the node name of the source server is
not locked or in use. If this is a routed command, check System action: The source server ends the session and
to make sure that the administator id being used to continues operation.
route the command is not locked or in use. For a User response: Before the source server is permitted
reason of LICENSE FAILURE, ensure that the target to access the target server, a properly authorized
server is properly licensed to support the source server administrator must unlock the target server.
session. For a reason of DOWN LEVEL, ensure that the
target server program is a level new enough to support
the source server session. For a reason of NODE TYPE, ANR4377E Session failure, target server server name
the source server is not allowed to establish a session is not defined on the source server.
with the given target server. The NODETYPE on the Explanation: The source server ends the session
target server is CLIENT. The NODENAME parameter because shown target server is not defined on the
of the server definition on the source server is incorrect. source server.
The NODETYPE parameter of the registered node on
the target server is incorrect and should be System action: The source server ends the session and
NODETYPE=SERVER. For a reason of INTERNAL continues operation.
ERROR, use the messages on the target server to User response: The target server must be correctly
determine the problem. For all reasons, if none of the defined before it can be accessed by the source server.
above are applicable, ensure that that the target server Before you attempt the next operation, define the target
has not disabled this server with the DISABLE server by using the DEFINE SERVER command.
SESSIONS SERVER command. Retry the failing
operation. If the target server is a replication server and its server
definition was incorrectly deleted, redefine the server
by using the DEFINE SERVER command before you
attempt replication. However, if you intend to remove
the target server from replication because it is no longer
required, use the REMOVE REPLSERVER command to

remove the target server from the list of replication that prevented the source server from registering with
servers. the target server.
ANR4378E For device class device class, the retry of a
User response: Ask an authorized administrator to
session with target server server name has
submit the request on the use of the target server using
timed out.
REGISTER NODE command. Retry the failing
Explanation: The source server has attempted to operation.
re-establish a session with the shown target server, but
the RETRYPERIOD from the given device class has
ANR4382E Session failure, policy information from
been exceeded.
target server server name is incomplete,
System action: The source server ends the operation. missing policy object.
User response: Determine it the target server is Explanation: The source server ends the session
having a problem or considering increasing the because the shown target server has provided policy
RETRYPERIOD value. information which is incomplete. The missing policy
object is shown.
ANR4379E The source server was unable to update System action: The source server ends the session and
the password on target server server continues operation.
name.
User response: Use the appropriate commands on the
Explanation: The source server has attempted to target server to complete the policy definitions being
update the target password. An error occurred that used by the source server. Retry the failing operation.
prevented the source server from updating the target
server.
ANR4383E Session failure, target server server name
System action: The operation fails. has aborted current transaction; reason:
abort reason.
User response: On the target server, determine the
cause of the problem and correct it. It may be necessary Explanation: The source server ends the session
for an administrator to correct the passwords with the because the shown target server has aborted the current
following actions. On the target server, issue the transaction for the given reason.
UPDATE NODE command to change the password. On
the source server, issue the UPDATE SERVER
command to change the password to match the new
password on the target server. Retry the failing User response: Check both the source server and the
operation. target server for any additional messages that might
further describe the reason the transaction was aborted.
Retry the failing operation.
ANR4380E The source server was unable to update
the server validation key on target
server server name. ANR4384E Node node name is not allowed to
establish a session as a target server.
update it's server validation key on the target server. Explanation: The node specified has attempted to
An error occurred that prevented the source server establish a session with this system and this is not
from updating the target server. permitted due to the NODETYPE for this node.
System action: The operation fails. System action: The operation fails.
User response: On the target server, determine the User response: To allow the specified node to
cause of the problem and correct it. It may be necessary establish a session as a target server, the node must be
for an administrator to correct the keys with the registered with a NODETYPE of SERVER. Or else
following actions. On the source server, issue the change the node name on the target server to a node
UPDATE SERVER command with FORCESYNC=YES to name that is allowed to establish a session using a
cause an attempt to synchronize the keys on both the node name that was registered with the
source and target servers. Retry the failing operation. NODETYPE=SERVER parameter specified.
ANR4381E The source server was unable to register

with target server server name.
register with the shown target server. An error occurred


ANR4385I Session retry in progress with target
server server name.
ANR4390E CANCEL EXPIRATION failed - unable
Explanation: The source server is attempting to
to cancel expiration process.
re-establish a session with the shown target server.
Session retry processing occurs when the source server Explanation: The CANCEL EXPIRATION command
has lost the connection with a target server and a was issued but encountered an error. Due to this error,
RETRYPERIOD value is specified, the command was unable to cancel the process.
System action: The source server attempts to contact System action: Server operation continues.
the target server.
User response: Issue the command QUERY PROCESS
User response: Determine if the target server is to determine the process number for the expiration
having a problem and considering canceling the process and then issue the command CANCEL
operation on the source server or correcting the PROCESS for that process number. This will cancel the
problem with the target server. current expiration process.
ANR4386I Session retry was successful for target ANR4391I Expiration processing node node name,
server server name. filespace filespace name, fsId filespace id,
domain domain name, and management
Explanation: The source server has re-establish a
class management class name - for type
session with the shown target server.
type files.
System action: Source server processing continues.
Explanation: Expiration processing is currently
User response: None. evaluating information for the node, filespace, domain
name, and management class specified for the file type
indicated.
ANR4387E Session session number for node node
name (client platform) refused - node System action: Server operation continues.
name not registered as TYPE=CLIENT.
client session because the client node name is not
ANR4392I CONTAINER DEFRAGMENTATION
registered as a node of TYPE=CLIENT. This node name
started processing stgpool stgpool name.
is already in use either as a server definition as defined
Containers are only using util pct% of
by a DEFINE SERVER command or else as a node of
cntr space due to fragmentation.
TYPE=SERVER using the REGISTER NODE command.
Explanation: CONTAINER DEFRAGMENTATION is
attempting to free up fragmented space in the stgpool.
User response: Issue a QUERY NODE TYPE=SERVER
or a QUERY SERVER to determine which server
definition already is using this node name. This client User response: None.
should be registered using the REGISTER NODE
TYPE=CLIENT command and specify a name that is
not in use by any other nodes or server defined to this ANR4393I CONTAINER DEFRAGMENTATION
server. finished reclaiming freed bytes bytes of
unused space on cntr count containers in
stgpool stgpool name.
ANR4388W No expiration process to cancel.
Explanation: CONTAINER DEFRAGMENTATION
Explanation: The CANCEL EXPIRATION command freed up fragmented space in the stgpool.
was issued but there were no expiration processes
currently running. System action: Server operation continues.

ANR4394I The server database was previously
restored, and an audit of the affected
ANR4389I Expiration process cancelled. volumes will now start or restart.
Container-copy storage pool volumes
Explanation: The CANCEL EXPIRATION command
that were reused after the restore date
was issued and successfully cancelled the current
will be deleted.
process.
Explanation: After a server database is restored from a

previous version, the server scans the volume history Processing continues for all the volumes in the given
file to identify container-copy storage pool volumes volume list.
that were reused after the restore target date. The
User response: Examine previous error messages for
reused storage pool volumes are deleted.
the cause of failure.
System action: All reused container-copy storage pool
volumes will be deleted. Local protect and repair
ANR4445I Context parameter set to value.
processes are temporarily suspended during this
process. Explanation: Determines if context reporting will be
generated when an ANR9999D error occures. This is
turned on or off with the SET CONTEXT messaging
command.
ANR4395E command: The command is not allowed
for the node type of node node name.
Explanation: The command is incompatible with the
node type for the specified node.
ANR4446I No damaged data was identified by the
AUDIT CONTAINER command (process
User response: None. ID process ID).
Explanation: When you issued the AUDIT
ANR4396I The audit process is complete, and CONTAINER command and specified the
reused container-copy storage pool ACTION=SCANDAMAGED parameter, no damaged
volumes were deleted. number of volumes data extents were identified.
volumes and number of chunks extents
were deleted from container-copy pools.
Explanation: After a server database was restored
from a previous version, the server scanned the volume
history file to identify container-copy storage pool ANR4483I Node node name issued command: Set
volumes that were reused since the restore target date. Access copy type file space namehigh-level
Those reused volumes were deleted. addresslow-level address authorized node
name ,authorized owner name.
System action: All reused container-copy storage pool
volumes have been were deleted. Explanation: The SET ACCESS command completed.
User response: Issue the PROTECT STGPOOL System action: Processing continues.
command with a value of TYPE=LOCAL to resume
protection of the primary container storage pool to the User response: None.
container-copy storage pool.
ANR4484I Node node name issued command: Delete
ANR4399E NAS file server NAS file server name is Access copy type file space namehigh-level
reporting NDMP error number NDMP addresslow-level address authorized node
error number: NDMP error description. name ,authorized owner name.
System action: The process ends. Explanation: The DELETE ACCESS command
completed.
User response: To identify the cause of the network
data management protocol (NDMP) error, see the System action: Processing continues.
documentation for the network-attached storage (NAS) User response: None.
file server. Review the NDMP logs for the NAS file
server, resolve the error, and restart the operation.
ANR4485I A storage pool space trigger has been
defined and enabled for storage pool
ANR4444W Command: Input volume volume name storage pool name.
cannot be processed.
Explanation: A storage pool space trigger has been
Explanation: During a DSMSERV DISPLAY defined with a DEFINE SPACETRIGGER command for
DBBACKUPVOLUME command, the server cannot the specified storage pool.
display the necessary information about the specified
backup volume. System action: None.
System action: The volume is not processed. User response: None.

automatically for storage pool without a specific space

ANR4486I A default storage pool space trigger has
trigger.
been defined and enabled.
Explanation: A default storage pool space trigger has
been defined and enabled. It will be effective for any User response: None.
storage pools associated with a devtype=DISK device
class or a devtype=FILE device class.
ANR4491I The storage pool space trigger is
System action: None. updated and enabled for storage pool
storage pool name.
Explanation: An UPDATE SPACETRIGGER command
has successfully completed for the specified storage
ANR4487I The storage pool space trigger is defined
pool space trigger. The updated parameters specified
for storage pool storage pool name, but is
on the command are used to automatically trigger
disabled.
space expansion for the storage pool.
Explanation: A storage pool space trigger has been
defined for the indicated storage pool, but because the
space expansion percentage is currently set to 0, the User response: None.
space trigger is disabled.
System action: None. ANR4492I The default storage pool space trigger is
updated and enabled.
UPDATE SPACETRIGGER command to set the space Explanation: An UPDATE SPACETRIGGER command
expansion percentage to a value greater than 0. has successfully completed for the default storage pool
space trigger. The updated parameters specified on the
command are used to automatically trigger space
ANR4488I The default storage pool space trigger is
expansion for storage pools without a specific storage
defined, but it is disabled.
pool space trigger and which are associated with a
Explanation: A default storage pool space trigger has devtype=FILE or devtype=DISK device class.
been defined for storage pools associated with a
devtype=DISK or devtype=FILE device class. But it has
been defined without a space trigger; because the space User response: None.
expansion percentage is currently set to 0, the space
trigger is disabled.
ANR4493I The storage pool space trigger is
System action: None. updated, but disabled for storage pool
storage pool name.
UPDATE SPACETRIGGER command to set the space Explanation: An UPDATE SPACETRIGGER command
expansion percentage to a value greater than 0. has successfully completed for the specified storage
pool space trigger. However, the space expansion
percentage is currently set to 0, which disables the
ANR4489I The storage pool space trigger has been
space trigger.
deleted for storage pool storage pool
name. System action: None.
Explanation: A DELETE SPACETRIGGER command User response: To activate the space trigger, use the
has successfully completed for the indicated storage UPDATE SPACETRIGGER command with the
pool space trigger. Space expansions are no longer SPACEexpansion parameter to set a value greater than
triggered automatically for the specified storage pool. If zero.
a default storage pool space trigger exists, it will apply
to the specified storage pool.
ANR4494I The default storage pool space trigger is
System action: None. updated, but disabled.
User response: None. Explanation: An UPDATE SPACETRIGGER command
has successfully completed for the default storage pool
space trigger. However, the space expansion percentage
ANR4490I The default storage pool space trigger
is currently set to 0, which disables the space trigger.
has been deleted.
Explanation: A DELETE SPACETRIGGER command
has successfully completed for the default storage pool User response: To activate the space trigger, use the
space trigger. Space expansions are no longer triggered UPDATE SPACETRIGGER command with the

SPACEexpansion parameter to set a value greater than RECLAMATIONTYPE=SNAPLOCK storage pool.

zero.
ANR4499E Command: Base backup set name Backup
ANR4495E Command: Storage pool space trigger is Set Name could not be found.
not defined.
Explanation: No full backup sets whose name begins
Explanation: The storage pool space trigger cannot be with the specified backup set name prefix could be
updated or deleted because it is not currently defined. found.
If a storage pool was not specified, an attempt was
made to delete the default storage pool space trigger,
command.
but no default storage pool space trigger is defined.
User response: Use the QUERY BACKUPSET
command to list available full backup sets and reissue
command.
the command with the backup set name prefix of an
User response: None. existing full backup set. If no full backup set exists,
then do not specify the BASE parameter until after a
full backup set has been generated.
ANR4496E Command: Storage pool space trigger is
already defined.
ANR4500I Writing sequential volume history
Explanation: The storage pool space trigger cannot be
information to defined files.
defined because it is already defined for the storage
pool. If a default storage pool trigger is being defined, Explanation: The server is updating all sequential
a default storage pool trigger already exists. volume history files defined in the server options file
with information on sequential volume usage
information. The files updated are those specified with
command.
the VOLUMEHISTORY option in the server options
User response: Use the UPDATE SPACETRIGGER file.
command to modify the indicated space trigger
parameters.
ANR4497E Command: EXPansionprefix not valid for
storage pool space trigger with storage ANR4501I Sequential volume history information
pool Storage Pool. successfully written to file name.
Explanation: The storage pool space trigger cannot be Explanation: The server is updating all sequential
defined with an EXPansionprefix parameter because the volume history files defined in the server options file
specified storage pool is not associated with a with information on sequential volume usage
DISK-type device class. Sequential access storage pools information. Volume history information was
use their associated directories for creating space when successfully written to the file specified.
a space trigger is activated.
command.
User response: Use the UPDATE SPACETRIGGER
ANR4502W No files have been defined for
command to create a space trigger without using the
automatically storing sequential volume
EXPansionprefix parameter.
history information.
Explanation: The server is attempting to update all
ANR4498E Command: STGPOOL Storage Pool is not
sequential volume history files defined in the server
eligible for a storage pool space trigger.
options file with information on sequential volume
Explanation: The indicated storage pool cannot have a usage information. Because no files were configured for
space trigger defined, because it is not associated with receiving this information, the automatic operation
a DISK-type or a FILE-type device class, or it is a fails.
RECLAMATIONTYPE=SNAPLOCK storage pool.
User response: To have the server automatically
command.
record sequential volume history information to assist
User response: Use the DEFINE SPACETRIGGER in server recovery, use the VOLUMEHISTORY option
command to create a space trigger with a storage pool in the server options file to specify where history
whose device class is of type DISK or FILE, or is not a information should be written. If you update the

options file, restart the server.

ANR4508I Audit Container (Scan Damaged)
process started for container container
ANR4503W The server current date current date is name (process ID process ID).
earlier than the date in a server record
Explanation: As the result of an AUDIT CONTAINER
server date.
command that specified scan action for the container
Explanation: The server has detected that the current shown, the process whose ID is displayed has begun
system date is an earlier date than the date in a server auditing the previously marked damaged data extents
record that is being processed. Possible causes for this on a given container.
problem are the current system date is invalid, the
System action: The previously marked damaged data
server was previously run with a future date, or there
extents on a container are audited. If a data extent is no
is an error in the server record. If the server was run
longer damaged, it will be reset as not damaged.
with a future date, this message will continue to appear
until that date has passed, or all records with the future User response: None.
date have been deleted from the server.
System action: Processing continues. The processing ANR4510E The server could not write sequential
for the current object may not occur as expected. volume history information to volume
history file name. To restore the database,
User response: On the machine on which the server is
access to this file is required.
running, verify that the system date is correct.
Explanation: While attempting to write sequential
volume history information to defined history files, the
ANR4504E Command: The specified point in time is
server could not write to the specified file. The
earlier than the point in time of the base
database cannot be restored until this file can be
backup set.
accessed.
Explanation: The point in time specified for the
System action: The server does not write volume
differential backup set is earlier than the point in time
history information to the file specified
of its base backup set.
User response: Examine any error messages that may
have been displayed prior to this message and correct
command.
any problems. Ensure that the server has permission to
User response: Reissue the command, specifying a write to the file indicated and that there is sufficient
later point in time. space in the file system for the file. On MVS, ensure
that the data set has been allocated and that the server
has permission to write to the data set. After correcting
ANR4505E Required table of contents could not be the problem, use the BACKUP VOLHISTORY
created for backup set for node name as command to write sequential volume history
set name (data type data type). information to the file.
Explanation: A table of contents could not be created
for the named object set, but a table of contents was ANR4511E Volume history file volume history file
required (TOC=YES was specified or implied). name could not be opened. To restore the
System action: The backup set is deleted. database, access to this file is required.
User response: Correct the problem that prevented the Explanation: While attempting to read or write
table of contents from being created and generate the sequential volume history information from defined
backup set again. history files, the server was unable to open the
specified file name. The database cannot be restored
until this file can be accessed.
ANR4506W Backup set for node name as set name
(data type data type) requires a table of System action: The server does not read or write
contents. volume history information from the specified file.
Explanation: The specified backup set requires a table User response: Examine any error messages that may
of contents, but TOC=YES was not specified. have been displayed prior to this message and correct
any problems. Ensure that the server has permission to
System action: The server will attempt to create a write to the file indicated and that there is sufficient
table of contents for the backup set. If the table of space in the file system for the file. On MVS, ensure
contents creation fails, the backup set will be deleted. that the data set has been allocated and that the server
User response: None. has permission to write to the data set.


ANR4512E A database transaction failure was
encountered in processing sequential
volume history information.
Explanation: While attempting to process sequential and ARCHFAILOVERLOGDIRECTORY options in the
volume history information, the server encountered a dsmserv.opt file. An out of log space condition might
database transaction error. occur because the ACTIVELOGDIRECTORY location is
full.
System action: The operation fails. Usage for a
sequential volume was not properly recorded for later Alternatively, an out of log space condition might occur
reference. if there are log files in the ACTIVELOGDIRECTORY
problems, if possible. If this does not resolve the
problem, contact your support representative.
ANR4513E A database lock conflict was dsmserv.opt file and then restart the server.
encountered in processing sequential
volume history information.
ANR4516E Server could not read sequential volume
Explanation: While attempting to process sequential history information from any defined
volume history information, the server encountered a files.
database locking conflict.
Explanation: While attempting to read sequential
System action: The operation fails. This usually means volume history information from defined history files,
that usage for a sequential volume was not properly the server finds that it cannot open any of the files
recorded for later reference defined in the server options file.
User response: Examine error messages that may have System action: The server does not read volume
been displayed prior to this message and correct any history information. If the current server task requires
problems, if possible. If this does not resolve the this information, the task ends.
problem, contact your support representative.
ANR4514E Sufficient database space is not problems, if possible. Make sure that the server has
available for the server while processing proper authority to read from the defined volume
sequential volume history information. history files. If you are doing a database restore, issue
RESTORE DB DEVCLASS=VOL.
Explanation: While attempting to process sequential
volume history information, the server found that
sufficient database space was not available for updates. ANR4517E No files have been defined for storing
sequential volume history information -
System action: The operation fails. Usage for a information cannot be read.
sequential volume was not properly recorded for later
reference. Explanation: The server is attempting to read from at
least one of the volume history files defined in the
User response: To increase the amount of database server options file. Since no files were defined for this
space that is available to the server, issue the EXTEND information the read operation fails.
the database. System action: Server operation ends.
User response: You can restore the database specifying
ANR4515E Sufficient recovery log space is not the volume names for each restore operation (in order)
available for the server while processing up to the desired point-in-time. If a volume history file
sequential volume history information. is available, specify its name in the server options file
and retry the operation.
Explanation: While attempting to process sequential
volume history information, the server finds that
sufficient recovery log space is not available for ANR4518E Volume history file file name line line
updates. number does not have the proper format
- read operation fails.
System action: The operation fails. Usage for a
sequential volume was not properly recorded for later Explanation: The server is attempting to read from a
reference. volume history file and encounters a record that does
not have the proper format.

System action: Server operation terminates.

ANR4522E RESTORE DB failed with LOG file
User response: Examine the file specified to determine error.
if the invalid record can be located and corrected. If the
Explanation: The LOG file is not associated with the
file is corrupted or does not contain valid volume
current log sequence.
history entries, it cannot be used for the desired
operation. System action: RESTORE DB terminates.
User response: Issue REMOVE DB first and retry the
ANR4519W Volume History File does not reflect RESTORE DB.
latest Storage Agent Updates
Explanation: The storage agent failed to have the ANR4523I Storage Pool Space expansion triggered.
volume history file on the server updated with the Storage Pool storage pool name with
latest changes from the storage agent. capacity of capacity megabytes requires
percentage percent expansion for
System action: The storage agent continues
expansion amount bytes of additional
processing.
space.
User response: To bypass the problem, a BACKUP
Explanation: A triggered space expansion has started
VOLHIST command can be issued from an admin
for the indicated storage pool. The storage pool has a
client connected to the server. The problem may be due
capacity of the number of megabytes shown. It is being
to a temporary loss of communication with the server.
expanded by the indicated percentage as directed by
the storage pool space trigger for this storage pool, or
ANR4520I Storage Pool storage pool name is being by the default storage space trigger if this storage pool
skipped during a space allocation. A has no dedicated trigger of its own. The percentage is
request for request amount megabytes represented by the additional amount of space
was made but only available amount indicated.
megabytes were available.
System action: Space expansion begins.
Explanation: A request for storage was made in the
indicated storage pool. The storage pool has a capacity
of the number of megabytes shown. The requested
amount can not be satisfied in the storage pool being ANR4524I Volume volume name defined in Storage
skipped. The next storage pool, if any, will be tried in Pool storage pool name as a result of
an attempt to satisfy the request. storage pool triggered space expansion.
System action: The storage server skips the indicated Explanation: A triggered space expansion has caused
storage pool and tries to allocate storage in a "next" the indicated volume to be created in the storage
pool. shown in the message. The volume definition is the
result of a storage pool space trigger definition which
User response: More space can be created in the
allocates new space when the space trigger space
storage pool by increasing the number of scratch
threshold is met.
volumes allowed (use the UPDATE STGPOOL
poolname MAXSCRATCH=xx command), by creating System action: Processing continues.
private volumes in the storage pool (use the DEFINE
VOLUME poolname volname command ), or by
creating a storage pool space trigger to monitor storage
in the storage pool. The storage pool space trigger can ANR4525E Failure to define volume volume name in
also automatically create new FILE volumes when Storage Pool storage pool name. Return
space triggers are exceeded (use the DEFINE codereturn code.
SPACETRIGGER STG STGPOOL=poolname command).
Explanation: A triggered space expansion has caused
an attempt to create the indicated in the storage pool
ANR4521E The number of volumes specified in the shown in the message. The volume creation failed with
BACKUP DB command is not sufficient. the indicated return code. The volume was not added
The backup failed. to the storage pool. Additional messages with specific
information on the failure are displayed from the
Explanation: The backup volume provided in the
volume creation process.
input parameter for BACKUP DB command is not
sufficient. System action: Processing continues.
System action: BACKUP DB terminates. User response: It might be necessary to take action
based on the failure message from the volume creation
User response: Provide more input volumes.
process. Such actions might include changing the

storage space trigger definiton, ensuring that hardware System action: Server processing continues but the
is function properly, or ensuring that the server is set storage pool is not expanded. The storage pool space
up with sufficient permissions to access and create files trigger for the indicated storage pool remains disabled.
on the file system to which IBM Spectrum Protect is This message is re-issued periodically when expansion
writing. is required but the storage pool space trigger remains
disabled.
ANR4526E Storage Pool Space trigger for storage User response: Allocate additional storage space to
pool name is ended; the thread resource the server. For storage pools of device type FILE,
not available. additional directories may be added to the list of
directories that the associated device class uses for
Explanation: The server cannot start a thread to
storage. If this action is taken, the corresponding
handle storage pool expansion for the indicated storage
storage agent directories should be added via the
pool.
UPDATE PATH command. The storage pool space
System action: Server processing continues but the trigger may be re-enabled with the UPDATE
storage pool is not expanded. SPACETRIGGER STG STPOOL=xx command, where xx
is the storage pool for which expansion has failed ( no
User response: See the documentation for the space trigger parameters need be updated ).
application.
ANR4531I An automatic full database backup will
be started. The last log number used is
ANR4527W Storage Pool Space trigger for storage last log used and the first log number
pool name is disabled after volume used is first log used. The log file size is
definition failures expansion failures. log file size megabytes. The maximum log
Insufficient space for pool expansion. file size is maximum log file size
Explanation: The server failed to complete a storage megabytes.
pool expansion for the indicated storage pool. The Explanation: When the log space used since the last
number of failures in pool expansion is also displayed. database backup exceeds the maximum log file size, a
System action: Server processing continues but the full database backup is started.
storage pool is not expanded. The storage pool space System action:
trigger for the indicated storage pool is disabled.
User response:
User response: Allocate additional storage space to
the server. For storage pools of device type FILE,
additional directories may be added to the list of ANR4533E Database database name is invalid and
directories that the associated device class uses for cannot be created.
storage. If this action is taken, the corresponding
Explanation: Follow all of these rules when choosing
storage agent directories should be added via the
a database name or alias:
UPDATE PATH command. The storage pool space
trigger may be re-enabled with the UPDATE v Character strings that represent names of a database
SPACETRIGGER STG STPOOL=xx command, where xx can contain any of the following characters: a-z, A-Z,
is the storage pool for which expansion has failed ( no 0-9, @, #, and $.
space trigger parameters need be updated ). v A database name or alias must be unique in the
database instance.
ANR4528W Storage Pool Space Expansion for storage v A database name or alias is one to eight characters in
pool name is disabled due to previous length.
expansion failures. After addressing v The first character of the name must be an alphabetic
space requirements, an UPDATE character, or a @, a #, or a $ character.
SPACETRIGGER STG command must v The first three characters of the name cannot be any
be issued to allow automatic stgpool of the following strings: SYS, DBM, or IBM.
expansion.
System action: DSMSERV FORMAT processing stops.
Explanation: The server failed to complete a storage
pool expansion for the indicated storage pool. The User response: Choose a different database name
storage pool space trigger is disabled due to previous which meets the criteria indicated above and issue the
expansion failures. The storage pool space trigger may DSMSERV FORMAT command again.
be re-enabled with the UPDATE SPACETRIGGER STG
STPOOL=xx command, where xx is the storage pool for
which expansion has failed ( no space trigger
parameters need be updated ).

ANR4534E The active log size of active log size MB ANR4538E The server could not write sequential
exceeds the available space active log volume history information to the
space MB. volume history file name temporary file.
Explanation: There is not enough space for the active Explanation: The server failed to write to the specified
log size specified in the DSMSERV FORMAT command. file. The volume history file cannot be updated until
this temporary file can be accessed.
System action: No volume history information was
User response: Ensure that the file systems you are
written to the temporary file specified.
using for database and recovery log activities have
enough space. Reissue the DSMSERV FORMAT User response: Examine any error messages that
command and specify a smaller value for the active log might have been displayed prior to this message and
size. correct any problems. Ensure that the server has
permission to write to the specified file and that the file
system has sufficient space for the file.
ANR4535E The active log directory active log
directory is not valid.
ANR4539E There is a mismatch in directory count
Explanation: The active log directory that is specified
between Device Class device class name
in the DSMSERV FORMAT command does not exist.
and Path Definition for Server server
System action: The database format operation failed. name. The device class has directory count
directories while the path definition has
User response: Verify that the file systems you have path directory count directories.
specified for formatting the server database and
recovery log are valid. Reissue the DSMSERV FORMAT Explanation: The server was assigning a shared FILE
command with a valid active log directory. library volume to a server or storage agent. Share FILE
libraries require a matching number of directories in
the PATH definition for the server or storage agent's
ANR4536E File Processor Value Unit table xml file access to FILE drives and the server's device class
could not be found or opened for read definition. For example, if the server has the following
access. device class definition: DEFINE DEVCLASS SFILE
Explanation: The file could not be found or opened. DEVTYPE=FILE MOUNTL=10 SHARED=YES
DIR=D:\DIR1,E:\DIR2,F:\DIR3 a FILE library name
System action: Contents of the file are not parsed and SFILE will be created along with 10 drives named
loaded to the database. SFILE1 to SFILE10 in shared library SFILE. Each of
User response: Verify that the file exists in either the these drives might have scratch volumes created in
server instance directory or the server installation directories D:\DIR1, E:\DIR2 or F:\DIR3. (For UNIX
directory. If the file does exist verify permissions for Platforms, substitute UNIX style names in the
read access. If the file does not exist obtain a copy from example).
the IBM processor value unit website. For library clients and storage agents, the appropriate
directory paths from those systems must be defined
ANR4537I The active log space used is log space using the DEFINE PATH command. An example, in
used is megabytes, and the active log this case, might be DEFINE PATH STA1 SFILE1
space available is log space available SRCTYPE=SERVER DESTTYPE=DRIVE
megabytes. The ratio, active log used ratio, DIR=V:\DIR1,W:\DIR2,X:\DIR3 LIBRARY=SFILE
exceeds the threshold log utilization which means that server (or storage agent) STA1
threshold. accesses directory D:\DIR1 using V:\DIR1 from the
STA1 system, E:\DIR2 on the server is accessed using
Explanation: When the active log space used exceeds W:\DIR2 on STA1, and that F:\DIR3 is accessed using
the log utilization threshold, the active log space must X:\DIR3 on STA1. If the number of directories between
be increased. the PATH and DEVCLASS do not match, there could
System action: None. be problem in accessing the resulting file in the future.
User response: Increase the size of the active log System action: Processing continues. Another
space. For information about increasing the size of the directory path is chosen. This might result in a
active log space, search for "active log" in the product subsequent access failure by the storage agent.
information: (http://www.ibm.com/support/ User response: Use the QUERY DEVCLASS classname
knowledgecenter/SSEQVQ/). F=D and the QUERY PATH pathname F=D commands
to compare the directory lists for the device class and
the path and ensure that they are synchronized.

problems such as inconsistent status reporting.

ANR4540I Container container name is now pending
- Container will be deleted from storage System action: Server operation continues.
pool storage pool name after the reuse
delay period for this storage pool has User response: Make sure that the clocks on all
elapsed. servers are set correctly. If possible, use an internet time
service to automatically synchronize the clocks.
Explanation: All files have been deleted from the
indicated container. The container will not be removed
from the storage pool until the reuse delay time period ANR4548W command: The specified at-risk interval
for the indicated storage pool has elapsed. of interval hours exceeds the activity
summary retention of retention days.
Explanation: The activity summary is used to
User response: None. determine if a client has been backed up within the
at-risk interval. If the interval exceeds the activity
summary retention, the server may not be able to find
ANR4542E Audit command: Invalid server for device
a qualifying backup and would consider the client to
class device class id in DevClass.Dirs
be unprotected.
table. The server name in the table is
server name. System action: Processing continues.
Explanation: A database audit process finds a User response: Either invoke the command again to
directory entry with a server which is either not reduce the interval or use the SET
defined or has an invalid length in the DevClass.Dirs SUMMARYRETENTION command to increase the
table. This table relates directories to device classes and activity summary retention.
paths. The class ID of the table entry is shown, along
with the server name. However, if the server name has
an invalid length, only blanks are shown. ANR4550I Full database backup (process process ID)
completed. Total bytes backed up: total
System action: Audit processing continues. DB bytes.
User response: If the FIX=YES parameter was Explanation: A full database backup process has
specified, the data base record with the incorrect entry completed. The output volumes used in this backup
will be deleted. Otherwise, reissue the audit command may be used during a database restore operation.
with FIX=YES, so that the incorrect record can be
deleted. After records with incorrect entries have been System action: None.
removed, review directories associated with device User response: None.
classes and paths with the following commands:
QUERY DEVCLASS F=D QUERY PATH F=D
ANR4551I Incremental database backup (process
process ID) completed. Total bytes
ANR4546W A ping request to server 'server name' backed up: total DB bytes.
was not able to establish a connection
by using server credentials. Explanation: An incremental database backup process
has completed. The output volumes used in this
Explanation: The failure could indicate a problem on backup may be used in conjunction with any preceding
the source or target server, or in the connection volumes in the backup series during a database restore
between the servers. operation.
System action: No connection was established. System action: None.
User response: To identify and resolve the issue, User response: None.
complete the following steps: 1. Check the activity log
and server console for messages that indicate a failure
or problem on the source server. 2. Check the ANR4555I Database backup process process ID
communication connection between the servers. 3. canceled.
Verify the server definition and password on both Explanation: The database backup process was
servers. 4. Verify that the target server is running. 5. canceled by an administrator with the CANCEL
Correct any identified issues. PROCESS command.
System action: The database backup process is ended.
ANR4547W The clock on the remote server
server_name differs from the clock on the User response: None.
local server by seconds seconds.
Explanation: The clocks on the local and remote
servers are not consistent. This can cause various

configuration information file that is pointed to in the

ANR4558I Snapshot database backup (process
server options file.
process ID) completed. Total bytes
backed up: total DB bytes.
ANR4572E Database restore terminated - excessive
Explanation: A differential database backup process
read errors encountered.
has completed. The output volumes used in this
backup may be used in conjunction with preceding Explanation: During database restore, read errors
volumes in the full backup during a database restore occur that prevent the restore from continuing.
operation.
System action: Database restore processing stops.
User response: Use a different device for the restore
User response: None. operation. If the problem persists, contact your service
representative.
ANR4559I Backup DB is in progress.
ANR4573E Database backup terminated - excessive
Explanation: The database backup in process.
write errors encountered.
Explanation: During database backup, write errors
User response: None. occur that prevent the backup from continuing.
System action: If the database backup was started
ANR4570E Database backup/restore terminated - with the BACKUP DB command, the database backup
device class device class name not defined. is ended and server operation continues. If the database
backup was triggered automatically, the backup stops
Explanation: During database backup or restore
and the server waits for the retry period to expire and
processing, an error occurred because the specified
then tries the database backup again.
device class is not defined.
cause of the write errors. If the problem cannot be
with the BACKUP DB command, the database backup
corrected, contact your service representative.
is ended and server operation continues. If the database
and the server waits for the retry period to expire and ANR4574E Database backup/restore terminated -
then tries the database backup again. A database data transfer interrupted.
restore is terminated.
Explanation: During a database backup or restore
User response: For database backup, make sure the operation, a data transfer operation has been
specified device class is defined. For database restore interrupted and cannot be continued.
processing, make sure the device class has a definition
in a device configuration file that is pointed to in the
server options file.
ANR4571E Database backup/restore terminated - and the server waits for the retry period to expire and
insufficient number of mount points then tries the database backup again. A database
available for removable media. restore is ended.
Explanation: During database backup or restore, the User response: If possible, determine and correct the
server cannot allocate sufficient mount points for the cause of the interruption. If the problem cannot be
volumes required. corrected, contact your service representative.
with the BACKUP DB command, the database backup ANR4575E Database backup/restore terminated -
is ended and server operation continues. If the database sufficient recovery log space is not
backup was triggered automatically, the backup stops available.
then tries the database backup again. A database
operation, the server runs out of recovery log space.
restore is ended.
User response: For database backup, make more
mount points available if necessary. For database
restore processing, make sure the device class has
sufficient mount points defined in the device

then tries the database backup again. A database

ANR4578E Database backup/restore terminated -
required volume was not mounted.
server recovery log space available, if necessary. For
operation, a required volume cannot be mounted,
database restore, contact your service representative.
because the mount request was canceled.
ANR4576E Database backup/restore terminated -
available.
Explanation: During a database backup or restore and the server waits for the retry period to expire and
operation, the server runs out of database space. then tries the database backup again. A database
with the BACKUP DB command, the database backup User response: Issue the command again or wait for
is ended and server operation continues. If the database the server to retry the backup and make sure the
backup was triggered automatically, the backup stops necessary volumes are accessible. If you are restoring a
and the server waits for the retry period to expire and database to a given date or doing a roll-forward
then tries the database backup again. The database restore, restart the entire restore operation. If you are
restore process attempts to set the database capacity to restoring a single database backup with COMMIT=NO,
the required capacity to hold the database being reissue the restore command. If you are restoring a
restored. If this fails, the restore operation is ended. database backup with COMMIT=YES, restore the
complete backup series from the beginning.
server database space available, if necessary. For
database restore, make sure that the size of the online ANR4580E Database backup/restore terminated -
database is at least the same capacity as the database insufficient memory available.
being restored.
operation, there was not enough server memory
ANR4577E Database backup terminated - volume available.
already in use.
Explanation: During a database backup operation, a with the BACKUP DB command, the database backup
volume cannot be used because it is already defined in is ended and server operation continues. If the database
a storage pool, or has been previously used by an backup was triggered automatically, the backup stops
export, a database dump, or a database backup and the server waits for the retry period to expire and
operation (as recorded in the volume history) or is in then tries the database backup again. A database
use by another process. restore is terminated.
System action: If the database backup was started User response: If necessary, make more memory
with the BACKUP DB command, the database backup available to the server.
ANR4581W Database backup/restore terminated -
then tries the database backup again.
User response: Specify a volume that is not in use or
operation, the server encounters an internal error.
defined in a storage pool, and that has not been
previously used for an export, a database dump, or a System action: If the database backup was started
database backup operation as recorded in the server with the BACKUP DB command, the database backup
volume history information. The QUERY VOLUME is ended and server operation continues. If the database
command may be used to display the names of backup was triggered automatically, the backup stops
volumes that are defined to server storage pools. The and the server waits for the retry period to expire and
QUERY VOLHISTORY command may be used to then tries the database backup again. A database
display the names of volumes that have been used for restore is terminated.
export, database dump, or database backup operations.

System action: Database backup or restore operation

ANR4582E Database restore terminated - volume
failed and is terminated.
cannot be used.
User response: Verify that the configuration of the
Explanation: During a database restore operation, a
dsm.sys file used by the IBM Spectrum Protect API for
volume has been mounted but cannot be used.
the system where the server is installed. The server
System action: The restore operation is terminated. stanza in the dsm.sys file for the database backup must
be configured as follows:
User response: If a volume list was specified on the
command, make sure the correct volume is being v The NODENAME option must specify
specified and mounted. If no volume list was specified, $$_TSMDBMGR_$$.
contact your service representative. v If the server is configured for database backup and
restore using TCP/IP, the server TCP/IP address
must be loopback (127.0.0.1).
ANR4583E Database backup terminated - output
media full and scratch media could not v The server is configured to listen on the appropriate
be mounted. TCP/IP port or SHMPORT.
Explanation: During a database backup operation, an

out-of-space condition occurred writing to the ANR4588E A database backup configuration might
sequential media, and a scratch volume cannot be be incorrect.
mounted. Explanation: A server database backup operation
System action: The database backup is ended and failed. The server database backup and restore
server operation continues. operations are a restricted protocol and require the
explicit use of the client node name
User response: Reissue the command and specify $$_TSMDBMGR_$$.
additional volume names on the command, or specify
SCRATCH=YES. System action: The database backup operation fails
and is ended.
ANR4585W Volume History File does not exist - User response: Verify that the configuration of the
Backup/Restore DB operation requires dsm.sys file used by the IBM Spectrum Protect API for
volume history file. the system where the server is installed. The server
stanza in the dsm.sys file for the database backup must
Explanation: Volume history file is needed for the be configured as follows:
backup/restore DB operation. .
v The NODENAME option must specify
System action: . $$_TSMDBMGR_$$.
User response: Please specify volume history file in v If the server is configured for database backup and
the dsmserv.opt. restore using TCP/IP, the server TCP/IP address
must be loopback (127.0.0.1).
v The server is configured to listen on the appropriate
ANR4586E Not able to get a DB2 connection. TCP/IP port or SHMPORT.
Backup DB operation will be
terminated.
ANR4589W The DB2 connection was lost following
Explanation: DB2 connection is needed for the backup a database restore operation.
DB operation. .
Explanation: The server database was restored, but
System action: Backup DB operation is terminated. the DB2 connection failed. For this reason, if the path
User response: Verify database manager resources. to the DB2 log directory was changed as part of a DB
Submit command again. restore operation, the database path to the log directory
was not updated automatically.
ANR4587E Database backup or restore System action: The server database is restored.
configuration is incorrect; client node User response: If the path to the DB2 log directory
node name was attempted to be used for did not change, no action is needed. If the path to the
this operation. DB2 log directory changed, you must manually update
Explanation: A server database backup or restore the path when the server is started. To update the path,
operation was attempted and failed. The indicated connect to the DB2 database and change the
client node was used for the operation which is configuration, as described in the following example:
incorrect. The server database backup and restore v Start DB2: db2start
operations are a restricted protocol and require the v Connect to TSMDB1: db2 connect to TSMDB1
explicit use of client node name $$_TSMDBMGR_$$.

v Update the DB2 database configuration: db2 update System action: None.
db cfg using NEWLOGPATH (log path from server
User response: Evaluate the volume history file and
options, e.g. /ALOG/tsminst1)
available volumes to use for restore of the database.
v Terminate the connection to TSMDB1: db2 terminate Manually add entries to the volume history file for a
v Recycle DB2: db2stop/db2start backup series and corresponding volumes to consider
v Verify that the new log path is in takes effect: db2 for restore database processing.
connect to TSMDB1; db2 get db cfg | grep "Path to
log files ( on UNIX ) " ANR4594E Restore database expects volume
v Verify that the new log path is in takes effect: db2 volumeName for backup series seriesID
connect to TSMDB1; db2 get db cfg | find "Path to and operation operationID but it could
log files ( on Windows ) " not be found in the available volume
history files.
ANR4591I Selected backup series seriesId from date Explanation: Once the DSMSERV RESTORE DB
and time as best candidate available for command selects a candidate database backup series, it
restore database processing. will validate the information from the backup data
stream and compare it to the information available
Explanation: The DSMSERV RESTORE DB command
from the volume history file. In this case, the database
evaluates the volume history file using the criteria
backup requires the specified volume for restore
specified for the command to determine the best
processing of this backup series but this volume was
candidate database backup to use.
not found in the available volume history file
System action: None. information.
User response: Evaluate the backup series, date, and System action: None.
time reported to determine if this meets the desired
restore objectives. If these do not meet the objectives,
available volumes to use for restore of the database. If
re-issue the DSMSERV RESTORE DB with additional or
the specified volume is available, than add an entry to
changed information in order to achieve the desired
the volume history file for this volume and retry the
recovery objectives.
operation. If this volume is not available, than remove
all entries from the volume history that are assigned to
ANR4592I Restore database backup series seriesId this backup series ID. Once those entries are removed,
includes eligible operation opId with retry the database restore operation and it will attempt
volume volume name having sequence to select the next best candidate for processing.
sequence and using device class device
class.
ANR4595E Restore database expects a stream
Explanation: The DSMSERV RESTORE DB command sequence stream for backup series
evaluates the volume history file using the criteria seriesID and operation operationID but it
specified for the command to determine the best could not be found in the available
candidate database backup to use. The opId and volume volume history files.
name for the indicated device class are candidate
Explanation: Once the DSMSERV RESTORE DB
volumes that will be evaluated and used for the restore
command selects a candidate database backup series, it
database process.
will validate the information from the backup data
System action: None. stream and compare it to the information available
User response: Evaluate the backup series, date, and backup has information for the indicated stream
time reported to determine if this meets the desired sequence but it has been unable to find any
restore objectives. If these do not meet the objectives, information about volumes used for that stream within
re-issue the DSMSERV RESTORE DB with additional or this backup series and operation.
changed information in order to achieve the desired
recovery objectives. System action: None.
ANR4593E Restore database unable to find eligible available volumes to use for restore of the database. If
candidate to use for processing. additional volumes are available for this series and
operation, than add entries to the volume history file
Explanation: The DSMSERV RESTORE DB command for these volume and retry the operation. If no other
evaluates the volume history file using the criteria volumes are available, than remove all entries from the
specified for the command to determine the best volume history that are assigned to this backup series
candidate database backup to use. No eligible ID. Once those entries are removed, retry the database
candidate backup series was found. restore operation and it will attempt to select the next

best candidate for processing. failure as well. Removing this entry from the volume
history file to eliminate it from consideration for this
backup series and operation or correcting the operation
ANR4596E The restore database operation is unable
id and series id to an approprite value would also
to validate the selected database backup
resolve this. After considering the cases above and
for series seriesID and operation
taking action for one or the other of them, retry the
operationID against the actual data from
restore database operation.
the database backup stream.
Explanation: When the DSMSERV RESTORE DB
ANR4598I Validating database backup information
for selected backup series seriesId and
will validate the information from the backup data
operation operationId using volume
stream and compare it to the information available
volumeName.
backup is missing information that is needed in order Explanation: The database backup information for the
to perform a restore of the server database. selected backup series selected from the volume history
will be validated against the information from the
database backup itself. The volume history information
User response: This error can be caused by one of the will be cross-checked to insure that the backup series,
following conditions: 1. All of the necessary volumes necessary volumes, and other attributes of the database
are not available and specified in the volume history backup are correct and complete for this operation.
file. 2. The release level of the server database backup Note that if the database restore operation includes
is different from the release level of the server that is incremental database backups, the validation will be
being restored. For example, error ANR4596E will occur done using the volumes assigned to sequence number
when you restore a V6.2 database and you are using a 10001 for operationId 0 and the operationId
V6.3 IBM Spectrum Protect server. 3. You have the representing the best candidate for restore of the
wrong volume that is designated with sequence 10001. incremental database backup data.
If a volume in the volume history file for this backup
series and operation is assigned 10001, try assigning a
different volume as sequence 10001. The volume User response: If the information is cross-checked and
assigned sequence 10001 is expected to have the validated successfully, the database restore will be
self-describing validation information and signatures attempted using this database backup series and
that are used by the restore process for the validation corresponding volumes. If the information fails to
of an operation for a backup series. The restore will fail validate, additional messages will be issued indicating
if this information is not found or is incorrect. what is missing or why the selected database backup
series and volumes can not be used. In the case that the
validation failed, review the other messages and take
ANR4597E Operation operationId for backup series
the corrective action specified by those messages and
seriesID does not reference volume
than retry the database restore operation.
volumeName, the volume history
information is not correct.
ANR4599W Could not create the server database log
Explanation: Once the DSMSERV RESTORE DB
directory Log directory.
will validate the information from the backup data Explanation: During a database restore operation,
stream and compare it to the information available directories for active, archive, mirror, and archive
from the volume history file. In this case, the volume failover logs might be created. Errors can occur during
history information reports a volume assigned to a creation of these directories due to permission, path, or
given series and operation but that backup does not file system issues.
reference that volume.
System action: The database restore was successful.
System action: None. However, the server might not be running with the
specified log directories.
User response: This may be caused by one of two
possible cases. The first is that the transaction log User response: Review the server options file and the
information recorded for this backup to make this output of the QUERY LOG F=D command. Ensure that
database referentially consistent required more than one the configured log directories were created and have
volume to store this information. This should be the required access permissions. If you make changes,
referenced with a write sequence number greater than restart the server.
10001. If this was assigned a sequence value less than
this value, it would be considered as a database backup
volume which would result in this error. Alternatively,
if this volume simply does not belong to this database
backup series or operation, that would result in this

indicates that this volume is either corrupted or not

ANR4602E No volumes found for TODATE date
suitable for restoring the database. This volume may be
time.
a pre Version 6.3.0 database backup volume. It cannot
Explanation: No volumes were found in the volume be used to restore an IBM Spectrum Protect V6.3
history files that meet the date and time parameters database.
specified.
System action: The server does not process the DSMSERV RESTORE DB command.
command.
User response: Check the volume history file to make
User response: Reissue the command with a valid sure that this volume is a valid database backup
date and time. volume. If this volume is corrupted, restore the
database to a different time using a different set of
backup volumes.
ANR4603I The volume history file that existed
before the upgrade to Version 6.3 or
later was saved under another name: file ANR4606E Restore database volume header backup
name. series number series does not match the
expected backup series number of
Explanation: After an upgrade of IBM Spectrum
expected series. This volume cannot be
Protect server to V6.3 or later, if you want to revert to
used to restore the database.
the previous release, you must have the original
volume history file. The reason is that the V6.3 or later Explanation: Each database backup volume contains
volume history file has a different format than the an IBM Spectrum Protect backup series number in the
earlier volume history file. The newer volume history volume header. A mis-matched backup series number
file cannot be used to restore the IBM Spectrum Protect indicates that this volume is either corrupted or not
database to the previous release. suitable for restoring the database.
System action: The system saves the previous volume System action: The server does not process the
history file under another name to ensure that it is not DSMSERV RESTORE DB command.
overwritten.
User response: To restore the IBM Spectrum Protect sure this volume is valid for a database backup
database, use the saved volume history file. operation. If the volume is valid, the volume history
file can be modified to match this series number and
you can reissue the DSMSERV RESTORE DB command.
ANR4604E Restore database volume header magic
If the problem persists, this volume may be corrupted.
number magic does not match the
Restore the database to a different time using a
expected volume header magic number
different set of backup volumes.
of expected magic. This volume cannot be
ANR4607E Restore database volume header backup
Explanation: Each volume contains an IBM Spectrum
operation number operation does not
Protect volume header that begins with a header magic
match the expected backup operation
number. A bad magic number indicates that this
number of expected operation. This
volume is either corrupted or not suitable for restoring
volume cannot be used to restore the
the database.
database.
Explanation: Each database backup volume contains
DSMSERV RESTORE DB command.
an IBM Spectrum Protect backup operation number in
User response: Check the volume history file to make the volume header. A mis-matched backup operation
sure that this volume is a valid database backup number indicates that this volume is either corrupted
volume. If the volume is corrupted, restore the or not suitable for restoring the database.
backup volumes.
ANR4605E Restore database volume header version
sure this volume is valid for a database backup
number version does not match the
operation. If the volume is valid, the volume history
expected volume version number of
file can be modified to match this operation number
expected version. This volume cannot be
and you can reissue the DSMSERV RESTORE DB
command. If the problem persists, this volume may be
Explanation: Each database backup volume contains corrupted. Restore the database to a different time
an IBM Spectrum Protect version number in the using a different set of backup volumes.
volume header. A mis-matched version number


ANR4608E Restore database volume header backup
type backup type is invalid. This volume
operation. If this volume is corrupted, restore the
cannot be used to restore the database.
Explanation: Each database backup volume contains backup volumes.
an IBM Spectrum Protect backup type code in the
volume header. An invalid backup type code indicates
ANR4615E The server is unable to restore the
that this volume is either corrupted or not suitable for
database due to inaccessible media.
restoring the database.
Explanation: The database restore operation cannot be
completed. Possible reasons include:
v The device configuration file is not correctly defined
User response: Check the volume history file to make to access the media.
v There is a problem with the media.
operation. If this volume is corrupted, restore the
database to a different time using a different set of System action: The database is not restored.
backup volumes.
User response: Review the information in the message
explanation and take action to correct any problems
ANR4609I Restore database process found backup with the device configuration file or media. Reissue the
type database backup timestamp backup RESTORE DB command.
timestamp from database backup media.
Explanation: This is the backup timestamp that is ANR4616E Database restore terminated because the
used for a database restore operation. media header cannot be found - DB2
sqlcode sqlcode and DB2 error message
System action:
sqlerrmc.
User response:
Explanation: During a restore operation, the DB2
database was unable to find the media header. There
ANR4613E Meta data for restore database volume might be a problem with the media.
backup volume is not valid. This volume
System action: The database restore is terminated.
cannot be used to restore the database.
User response: Check if the IBM Spectrum Protect
Explanation: Backup volumes contain IBM Spectrum
server reports an error for the media. Ensure that the
Protect meta data. Invalid meta data indicates that this
media that is used for the database backup is working.
volume is either corrupted or not suitable for restoring
the database.
ANR4617I A ping request to server 'server name'
was able to establish a connection by
using server credentials.
Explanation: The server credentials are valid.
operation. If this volume is corrupted, restore the System action: The connection was established.
backup volumes. User response: No action is required.
ANR4614E The database backup timestamp of ANR4618I The server credentials can not be
backup timestamp on media on database authenticated for server server name
backup media with backup type backup because the server has no defined
type does not match the backup password.
timestamp backup timestamp from volhist Explanation: The server password is missing.
from the volume history file. This
volume cannot be used to restore the System action: Server operation continues.
database. User response: If you want to use server-to-server
Explanation: Mis-matched timestamps indicates that functions such as enterprise configuration or node
this volume is either corrupted or not suitable for replication, a server password is required. To specify a
restoring the database. password, issue the following command: UPDATE
SERVER server name SERVERPASSWORD=password The
System action: The server does not process the password must match the password that is set by the
DSMSERV RESTORE DB command. SET SERVERPASSWORD command.

ANR4620I Database backup series Backup series ANR4626I Database backup will use number of
operation backup operation device class streams streams for processing with the
device class. number originally requested number
requested.
Explanation: The device class used for the backup is
shown. Explanation: The database backup will be performed
using the specified number of streams. The original
number of streams requested, either through the
User response: None. command or the NUMSTREAM setting for SET
DBRECOVERY, is also displayed.
ANR4622I Volume volume sequence number in backup System action: The database backup will be
operation: volume name. performed with the indicated number of streams.
Explanation: The volume sequence and name for a User response: Note that if the number of streams
full or an incremental database backup are shown. used for the database backup differs from the number
requested, this indicates either a configuration error or
System action: None. that the device being used does not have as many
User response: None. drives available as was previously considered and
planned for. Review the device class and
NUMSTREAM settings used for the database backup
ANR4624I Preview processing for a database command to determine if changes are needed or if
restore operation has completed. actions are needed to bring drives back online.
Explanation: The database restore command was
issued with PREVIEW=YES specified. The server will ANR4627W The object might be incomplete for node
evaluate the volume history information and report the name: type=type, file space=filespace name,
details about what it found. It will report the candidate object=object name.
database backup that was selected based on the restore
command that was specified. If the database restore Explanation: The IBM Spectrum Protect V7.1.0 server
processing is unable to find a viable database backup to exported the object of type type for node name,
use for restore or other errors occur during this identified by file space and object name. The named
evaluation, these will also be reported. object might be imcomplete.
System action: None. System action: The IMPORT operation proceeds.
User response: Review the other messages issued to User response: Restore, retrieve, or recall the named
determine the outcome of the database restore preview object. Verify that all contents of the file are stored
operation. properly.
ANR4625W Database backup failure while ANR4628E Device device name failed to close with
attempting to use number of streams error code errno.
streams, backup will be retried using Explanation: The IBM Spectrum Protect server cannot
one stream. close the device.
Explanation: The database backup process failed System action: The close operation fails.
while attempting the operation with the specified
number of streams. The operation will be retried with a User response: Check the error code value, get the
single stream. device driver trace and contact the device vendor.
System action: The database backup will be

automatically retried using a single stream. ANR4629E Attempting to restore a fragmented file
through an earlier-level storage agent.
User response: Review the other messages issued to The file will not be restored: Node node
determine the reason for the failure of the database name, Type file type, File space filespace
backup while using multiple output streams. Also name, File name file name.
review the process completion and other message to
determine if the retry using a single stream was Explanation: When the storage agent attempts to
successful. restore a fragmented file, the file is not restored. This
behavior occurs during a classic restore by using a
storage agent earlier than version 7.1.
System action: The file is not restored.

User response: Complete one of the following actions

ANR4633W Storage pool directory dir name in
to resolve the problem:
storage pool stgpool name can not be
v Restore the file from LAN explicitly. accessed due to its access state access.
v Restore the file through a no-query restore.
Explanation: The specified container's directory is
v Upgrade the storage agent to a level at version 7.1 or restricted to access.
later.
Refer to APAR IT02547 for more information about the
problem. User response: Identify and modify the access state
for the stgpool directory if possible.
ANR4630W Container container name in storage pool

storage pool cannot be opened. Audit will ANR4634I Starting point-in-time database restore
mark the container as unavailable and to date date time.
all the data extents in it as damaged. Explanation: A point-in-time database restore with the
Explanation: The AUDIT CONTAINER process TODATE parameter specified has begun. When this
encountered an open error for the specified container restore is complete, the database will be committed to
while attempting to read a data extent. The container the point in time of this backup.
will be marked unavailable, and all extents within the System action: None.
container will be marked damaged.
User response: Identify and resolve the open error for ANR4635I Point-in-time database restore complete,
the container, if possible. Verify that the container's restore date date time.
physical device is functioning properly and that the
container is usable. Explanation: A point-in-time database restore with the
TODATE parameter specified has completed. The
database is committed to the point in time of this
ANR4631W Header of container container name in backup, which may be different than the TODATE
container storage pool storage pool is specified. If this is the case, an additional message will
corrupted. Audit will mark the container be displayed.
as unavailable and will record all
content as damaged. System action: None.
Explanation: While attempting to access the User response: None.

container's data, the container header was found to be
corrupted. The container will be marked unavailable. ANR4636I Starting roll-forward database restore.
System action: None. Explanation: A roll-forward database restore has
User response: Identify and resolve the invalid header begun. When this restore is complete, the database will
for the container if possible. Verify that the container's be returned to its most recent state.
physical device is functioning properly and that the System action: None.
container is usable.
ANR4632E Session session number cannot store data
in the container storage pool on the ANR4637I Roll-forward database restore complete.
target replication server. There is
Explanation: A roll-forward database restore has
insufficient space in the container
ended. All database backups in the most current
storage pool stgpool name.
backup series have been restored, and all updates to
Explanation: During replication processing, there was the database since the most recent backup have been
insufficient free space available in the container storage rolled forward. The database has been returned to its
pool on the target replication server. most recent state.
System action: The replication process fails. System action: None.

User response: Issue the DEFINE User response: None.
STGPOOLDIRECTORY to define a new storage pool
directory for the container storage pool on the target
replication server.

ANR4638I Restore of backup series backup series ANR4653E Incremental backup DB failed. Can not
number operation backup operation in series perform incremental DB backup without
in progress. a FULL DB backup performed first.
Explanation: During a DSMSERV RESTORE DB, the Explanation: A FULL DB backup has to be performed
server displays the backup series and operation at least once before any Incremental DB backup can be
currently being restored. performed.
System action: None. System action: The incremental DB backup is
terminated.
User response: Reissue the backup db command with
type=FULL.
ANR4640E Failed to retrieve space statistics from
directory directory name.
ANR4654I The restore db to most current time can
Explanation: The IBM Spectrum Protect server cannot
not be done since contents of the active
gather space statistics for the directory.
or archive log directories have been
System action: The directory space stats operation changed. The DB will be restored to the
fails. last full or full plus incremental state.
User response: Ensure that the directory has the Explanation: The restore DB can only restore to the
correct permissions and can be accessed by the IBM last FULL backup.
Spectrum Protect server.
System action:
User response: Do not modify contents of active or
ANR4645I The restore date reflects the most recent
archive log directories before attempting a dsmserv roll
backup available up to the specified
forward restore command.
TODATE.
Explanation: During a DSMSERV RESTORE DB with
ANR4656E Invalid key-ring file password Key Ring
the TODATE parameter, the date of the restored backup
password
was not identical to the date specified on the
command. The backup series that was restored is the Explanation: The specified key-ring file password
most recent backup series up to and including the exceeds the maximum password length of 64
specified date. characters.
System action: None. System action: None
User response: Make sure the date of the restored User response: Specify a key-ring file password using
database is satisfactory. If it is not, restore the database 1-64 characters. Ensure that the password is the same
again by specifying a different TODATE or by restoring value that was specified with the key-ring file
individual database backups. password utility.
ANR4652E No system message queues available for ANR4657E SNMP: Failed to connect to server at
communications. address address, port port.
Explanation: While IBM Spectrum Protect was trying Explanation: The SNMP client was attempting to run
to establish a communications session, an attempt to a session with the server at the indicated address and
acquire a system message queue failed. This usually port number in response to an SNMP Get Request,
means that the system-imposed limit on message which causes a Server Script to be run. The subagent
queues has been reached. failed to connect to the server.
System action: The communications session is not System action: The SNMP subagent ends this attempt
initialized due to lack of system resources. to run the script and continues operation.
User response: Increase the maximum number of User response: Ensure that the indicated server is up
message queues on the system and try the operation and able to initiate admin clients using the TCP/IP
again. This is normally accomplished by increasing the protocol.
value in the kernel's msgmni file.

ANR4658I No key-ring file password was found. ANR4662W Failure sending message to SNMP
subagent.
Explanation: Either a QUERY command was issued to
display the key-ring file password or a SET command Explanation: The server experienced an error return
was issued to inform the server of a change to the code from TCP/IP while sending to the SNMP
key-ring file password. A password was not recorded subagent. This message is also issued when the SNMP
by the server. subagent has an error sending a verb to the server
when acting as an SNMP client. This may be a normal
System action: None
event if either side of the connection is abruptly ended,
User response: To create a key-ring file or to generate as in the case of terminating the subagent program. The
a password, the server must run with secure sockets error is reflected in another message for TCP/IP which
layer (SSL) transmission control protocol (TCP) port further describes the error.
options. If the server did not run with SSL TCP port
System action: The session is ended. Server operation
options, start the server while the options file contains
continues. If a message is being forwarded to an SNMP
the SSLTCPPORT or SSLTCPADMINPORT option. Then
managing node, the message is not sent. If a heartbeat
issue the QUERY SSLKEYRINGPW command to
message was being sent to the subagent, this heartbeat
display the generated password. If you use an external
message is lost and the server attempts to re-start its
utility to change the key-ring file password after the
session with the SNMP subagent.
server creates the key-ring file and its password, issue
the SET SSLKEYRINGPW command to inform the User response: If the session is ended as a result of
server of the change. intentionally stopping either the subagent, no response
is required. Otherwise, ensure that the TCP/IP protocol
stack is functioning by using the tools that come with
ANR4659E SNMP: Communications failure: bad
the particular TCP/IP suite on the platform in use.
verb received (verb type).
Explanation: The SNMP client encountered an invalid
ANR4663W Failure receiving message from SNMP
communications verb during a session with the server
subagent.
and is not able to continue processing the session.
Explanation: The server experienced an error return
System action: The SNMP session ends and subagent
code from TCP/IP while receiving data from the SNMP
subagent. This may be a normal event if either side of
User response: Contact your service representative. the connection is abruptly ended, as in the case of
terminating the subagent program. The error is
reflected in another message for TCP/IP which further
ANR4660I Connected to SNMP subagent at SNMP describes the error.
subagent address on port port number.
Explanation: The server has successfully connected to continues. If a heartbeat message was being sent to the
the SNMP subagent at the indicated address and port. subagent, this heartbeat message is lost and the server
System action: The server will now register with the attempts to re-start its session with the SNMP
subagent. subagent. If the server was attempting to register to the
SNMP subagent, heartbeat messaging will be disabled
User response: None. until the server is re-started.
User response: If the session is ended as a result of
ANR4661E SNMP communication with the intentionally stopping either the subagent, no response
subagent failed because a thread is required. Otherwise, ensure that the TCP/IP protocol
resource was not available. stack is functioning by using the tools that come with
Explanation: The server could not continue with the particular TCP/IP suite on the platform in use.
SNMP communication to the SNMP subagent because
sufficient memory is not available for starting ANR4664W Failure in registering with SNMP
additional processes on the server. subagent.
System action: The server discontinues SNMP Explanation: The server experienced a problem while
processing and server operation continues. attempting to register with the SNMP subagent. This
User response: See the documentation for the may be due to problems with communication or the
operating system about how to increase memory for an SNMP subagent being unavailable.
application. System action: Heartbeat messaging will be disabled
until the server is re-started.
User response: Ensure that the subagent is running
and that the TCP/IP protocol stack is functioning by

using the tools that come with the particular TCP/IP System action: The server was able to successfully
suite on the platform in use. resynchronize with the SNMP subagent.
ANR4665W Failure retrying registration with SNMP
subagent.
ANR4669W Heartbeat message was not accepted by
Explanation: The server experienced a problem while SNMP subagent.
attempting to re-register with the SNMP subagent after
Explanation: The server experienced a problem while
losing contact. This may be due to problems with
attempting to send a heartbeat message to the SNMP
communication or the SNMP subagent being
subagent. The SNMP subagent was unable to accept the
unavailable.
heartbeat message. If the subagent was stopped and
System action: Registration is re-tried for a number of re-started, this is a normal message.
attempts before giving up.
System action: The server will attempt to contact the
User response: Ensure that the subagent is running SNMP subagent again and re-synchronize.
using the tools that come with the particular TCP/IP
suite on the platform in use.
ANR4666W Failure sending heartbeat message to
SNMP subagent.
ANR4670W Failure in opening session with SNMP
Explanation: The server experienced a problem while subagent.
subagent. This may be due to problems with
attempting to open a session with the SNMP subagent.
unavailable. System action: Processing continues. Heartbeat and
message forwarding function will not be available.
System action: The server will attempt to contact the
SNMP subagent again and re-synchronize. User response: Ensure that the subagent is running
suite on the platform in use. If heartbeat and message
forwarding functions are required, re-start the server.
ANR4671W SNMP subagent did not accept

ANR4667W Failure retrying heartbeat message to
registration of this server.
SNMP subagent.
attempting to open a session with the SNMP subagent.
The subagent is available but disallowed registration by
subagent. This may be due to problems with
this server.
unavailable. System action: Processing continues. Heartbeat and
message forwarding function will not be available.
System action: The server attempted to contact the
SNMP subagent again and re-synchronize, but this too User response: It may be necessary to stop the
failed. Heartbeat functions are disabled until the server subagent and re-start it. Then stop the server and
is re-started. re-start it if heartbeat and message forwarding
functions are required.
using the tools that come with the particular TCP/IP ANR4672W SNMP message forwarding to the
suite on the platform in use. Re-start the server if the SNMP subagent was not started because
heartbeat function is required. a thread resource was not available.
Explanation: The server could not continue with
ANR4668I Connection successfully re-established SNMP communication to the SNMP subagent for
with SNMP subagent. message forwarding because sufficient memory is not
available for starting additional processes on the server.
attempting to send a heartbeat message to the SNMP System action: The server discontinues SNMP
subagent. message processing and server operation continues.

User response: See the documentation for the messages are no longer being forwarded.
User response: Message forwarding can be
application.
re-initialized by either stopping the server and
re-starting it. Message forwarding will also be
ANR4674E Error starting DPI thread - Return code: re-started if the heartbeat function is in use and the
Return code received from called routine. server re-synchronizes with the subagent. This
re-synchronization occurs if the subagent, dsmsnmp, is
Explanation: The SNMP subagent could not start the
stopped for longer than a single heartbeat interval (the
DPI thread.
heartbeat interval is a server option and appears in the
System action: Initialization of the subagent fails. output of the QUERY OPT command) and then
restarted.
ANR4681W Connect to SNMP agent failed, will

ANR4675W command: This command may take a keep trying.
while to finish.
Explanation: The subagent has failed in an attempt to
Explanation: A command has been invoked that could connect to the SNMP agent.
potentially run for a while.
System action: The subagent keeps retrying the
System action: The administrator is asked whether to connection.
continue.
User response: Make sure that the SNMP daemon is
User response: Enter 'Y' to continue with the up, running and correctly configured.
command or 'N' to terminate the command.
ANR4682W A SNMP agent connection error

ANR4676E Unable to register another server. occurred. Attempting to re-establish
Explanation: The SNMP subagent received a request connection.
to register a new server and was unable to allocate the Explanation: An error has occurred in the
memory necessary to register the new server. communication between the subagent and the SNMP
System action: The subagent will not register the new agent.
server. System action: The subagent will attempt to
User response: Contact your service representative. reconnect.
ANR4677I Session established with server name: up, running and correctly configured.
The name of the registered server..
Explanation: The SNMP subagent completed the ANR4683E Unable to open trace file 'file name'.
registration of the identified server. Explanation: An error occurred while opening the file
System action: The subagent will wait for additional for writing trace data.
requests from the server. System action: The subagent continues operation
User response: None. without tracing.
User response: Ensure there is adequate space on the
ANR4678I Session closed with server name: The drive from which you are running the subagent and
name of the deregistered server.. retry the program.
Explanation: The SNMP subagent completed the

deregistration of the identified server. ANR4684E Trap request failed - RC: Return code from
the trap request. Server index: Server index
System action: None. number..
User response: None. Explanation: An error occurred while attempting to
process a trap request from a server. data.
ANR4679W Messages are no longer being forwarded System action: The subagent processing continues.
to the SNMP subagent.
Explanation: The server has encountered multiple up, running and correctly configured.
errors in forwarding messages to the SNMP subagent.
Messages are no longer being forwarded.
System action: The server continues operating, but

ANR4685E Insufficient memory for subagent ANR4690E Unexpected request type (The value of the
initialization. request that was received.) in trap data
header.
Explanation: The SNMP subagent could not initialize
due to the inability to obtain the required memory. Explanation: The SNMP subagent received an invalid
trap request from a server.
System action: Initialization of the subagent fails.
System action: The subagent will stop processing
User response: Allocate additional memory to the
requests from the server sending the invalid requests.
subagent.
ANR4686E Insufficient memory for subagent trace
initialization. ANR4691I DPI subagent (The subagent name.):
connected, ready to receive requests.
Explanation: The SNMP subagent trace could not
initialize due to the inability to obtain the required Explanation: The subagent has successfully connected
memory. to the SNMP agent.
System action: Initialization of the subagent fails. System action: The subagent is ready to receive
request from servers.
User response: Allocate additional memory to the
subagent. User response: None.
ANR4687E Server/subagent protocol violation - ANR4692I DPI subagent (The subagent name.):
expecting registration request. Received reconnected, ready to receive requests.
request: The value of the request that was
Explanation: The subagent has successfully
received.
reconnected to the SNMP agent.
Explanation: The SNMP subagent was expecting a
System action: The subagent is ready to receive
registration request. It actually received something
request from servers.
other than a registration request.
ANR4694E SNMP Subagent Port Confirmation Has
Failed.
Explanation: The server was communicating
ANR4688E Server/subagent protocol violation -
configuration data to the SNMP subagent. An error
incorrect request header version.
occurred in the exchange. The server could not
Explanation: The SNMP subagent received a request communicate interface information to the subagent.
from a server that was not at the same maintenance
System action: The server continues operation. The
level as the subagent.
SNMP administrative interface is inoperative.
User response: The most likely cause of this problem
is a temporary network failure. The server should be
User response: Ensure the server and subagent are at re-started to retry the connection to the SNMP
the same maintenance level. If they are, contact your subagent. If this problem occurs repeatedly, please
service representative. contact you service representative.
ANR4689E Invalid request type received (The value ANR4695E SNMP: Communications Failure in
of the request that was received.). Receiving "verb type" verb.
Explanation: The SNMP subagent received an Explanation: The SNMP client encountered a
unexpected request from the server. communications error in using the verb type verb to
transfer information to or from the server and an
SNMP client.
System action: The SNMP session ends and server
User response: This may not be a problem if the
SNMP subagent was terminated while the session was
in progress. Otherwise, ensure that TCP/IP

communications is running normally.

ANR4701I The server move size threshold has been
set to new threshold. Move operations
ANR4697E SNMP: Failed to authenticate to server that start after this point will use the
at address address, port port. new value.
Explanation: The SNMP client was attempting to run Explanation: A SETOPT commmand was used to set
a session with the server at the indicated address and the value for the move size threshold value. This
port number in response to an SNMP Get Request, setting determines the maximum number of megabytes
which causes a Server Script to be run. The subagent that are moved on the server in one database
connected to the indicated server, but failed in transaction, dependent also on the setting for the move
authentication. batch size. The setting influences file movement for
server migration, reclmation, storage pool backup, and
System action: The SNMP subagent ends this attempt move data operations.
to run the script and continues operation.
User response: Ensure that the indicated server has an move operations that are started after this message is
an administrative id of SNMPADMIN and that this issued.
adminstrative id has sufficient authority to run the
script and commands it contains. User response: Contact your service representative.
ANR4698E SNMP: Communications Failure in ANR4702I The server transaction group maximum
Sending "verb type" verb (command). has been set to new value. Client sessions
that are started after this point will use
Explanation: The SNMP client encountered a the new value.
communications error in using the verb type verb to
issue command command. Explanation: A SETOPT commmand was used to set
the value for the maxmimum number of files that can
System action: The SNMP client session ends and be sent from the client in a single database transaction.
subagent operation continues.
User response: Contact your service representative. client sessions that are started after this message is
issued.
ANR4699E SNMP: Receive Buffer overflow. User response: Contact your service representative.
Explanation: The SNMP client encountered an
overflow error in transferring information to or from ANR4704I key-ring filename and password have
the server. been set. Restart the server to use the
System action: The SNMP client session ends and new settings
subagent operation continues. Explanation: The key-ring filename have been set to
User response: Contact your service representative. the new value specified in the DEFINE KEYRING
command.
ANR4700I The server move batch size has been set System action: None.
to new batch size. Move operations that User response: Restart the server to use the new
start after this point will use the new key-ring information.
value.
Explanation: A SETOPT commmand was used to set ANR4707E Import/Loaddb command operation
the value for the move batch size value. This setting terminated - incomplete input volume
determines the maximum number of files that are list.
moved on the server in one database transaction,
dependent also on the setting for the move size Explanation: The list of volumes needed to process
threshold. The setting influences file movement for the command was incomplete. At least one volume
server migration, reclamation, storage pool backup, and needed for the operation is missing from the end of the
move data operations. list.
System action: The server uses this new setting for System action: The command operation is ended.
move operations that are started after this message is
issued.
sure the necessary volumes are included in the volume
User response: Contact your service representative. list.

versions of the product. Review the README for an

ANR4709W Intervention required to mount volume
explanation of supported storage agent levels for this
Volume Name on Library Manager Server
server. The storage agent will not startup and will
Server Name.
report ANR0454W indicating that it is down level.
Explanation: A volume mount is awaiting operator
intervention on the specified library manager server.
System action: The volume mount operation waits for
ANR4724E During the backup of node node (Node
operator intervention.
id) filespace filespace name (filespace id) a
User response: Refer to the server consol and/ir deletion activity occurred.
activity log on the named library manaer server to
Explanation: During full or incremental backup
determine the action that needs to be performed to
processing, files were deleted from the file space. The
complete the mount operation.
files were not deleted by expiration, but by some other
process. DELETE FILESPACE, DELETE VOLUME,
ANR4712E Command: The DEVCLASS parameter is AUDIT VOLUME, or some other administrator
only valid for volume history types command can cause files to be deleted. The file space
DBBACKUP or DBSNAPSHOT. image on the server will not be consistent with the
client until an incremental backup is completed for the
Explanation: The command failed because an invalid
node.
volume history type was specified for the TYPE=
parameter. System action: The server will continue processing.
System action: The command fails, and server User response: Perform an incremental backup for the
operation continues. client node.
User response: Re-issue the command and specify a
valid type value. ANR4725E Source file(line number): Server lock
Locktype, mode Lockmode failed.
ANR4713E Command: The "option" string is not valid Explanation: An internal error occurred in an attempt
for the Hex Filespace Field. to obtain a lock during processing.
Explanation: The command indicated specifies a value System action: The activity that generated this error
that is not valid for the Hex Filespace parameter. fails.
System action: The server does not process the User response: Retry the process. If the process fails
command. contact your service representative.
entry for the Hex Filespace parameter. ANR4726I The support module support module has
been loaded.
ANR4717E command: Replication or recovery of Explanation: The module indicated has been
damaged files is not supported by target successfully loaded. Operations involving this module
server due to unsupported transfer may be performed by the server.
method fasp.
System action: Functions which depend on this
Explanation: Replication recovery operations module may now be performed on the server.
originating from this server are not allowed because the
target replication server does not support fasp as a
transfer method.
ANR4728E Server connection to file server File
server name failed. Please check the
User response: Upgrade the target replication server attributes of the file server specified
to a level that supports replication recovery using fasp. during definition of the datamover.
Explanation: The server attempted to connect to a file
ANR4723E Session rejected for down level storage server. The connection failed because of one of the
agent storage agent name. following possible reasons:
Explanation: A down level storage agent attempted to v One of the parameters specified during datamover
connect to this server. The server can not support all definition was incorrect: TCP/IP address of the file
previous versions of the storage agent. server, user id, password, TCP/IP port
v File server does not support requested NDMP
System action: The server will not support
version
connections by storage agents at a specific lower

v File server is not accessible

ANR4731E Command: The pool type storage pool
v NDMP server limits the number of opened NDMP storage pool name is not defined.
sessions
Explanation: A DEFINE STGPOOL or UPDATE
v An unsupported model of the filer server was
STGPOOL command contained a storage pool that is
detected
not defined as either a copy storage pool or an
v If the message specifies address 127.0.0.1 or the active-data storage pool.
address of the server system, the
NDMPCONTROLPORT and/or NDMPPORTRANGE System action: The command fails.
options may be set to port numbers or ranges which User response: Verify that the copy or active-data
are already in use. storage pool name stated in the error message is
System action: IBM Spectrum Protect server correct. If using the COPYSTGPOOLS parameter,
backup/restore of the file server fails. correct the problem by using a copy storage pool that
already exists or define the copy storage pool. If using
User response: Check if file server is accessible the ACTIVEDATAPOOLS parameter, correct the
through the network; check each of the attributes problem by using an active-data storage pool that
specified during datamover definition; check NDMP already exists or define the active-data storage pool.
versions supported by the file server; check the number Retry the command.
of open NDMP sessions with the file server, verify that
file server model is supported by IBM Spectrum Protect
server. If the server's address is in the message ensure ANR4732E Command: The storage pool stgpool name
that the ports specified or defaulted for options is not a copy or active-data type storage
NDMPCONTROLPORT and/or NDMPPORTRANGE pool.
are available for use. Depending on the operating Explanation: A DEFINE STGPOOL or UPDATE
system, the netstat operating system command may be STGPOOL command contained a storage pool name
used to determine in-use port numbers. that is not a copy or active-data type storage pool.
ANR4729E Server connection to file server File
server name failed. The level of the file User response: Verify that the copy or active-data
server operating system is unsupported storage pool name stated in the error message is correct
by IBM Spectrum Protect server. Please or remove the storage pool name from the list. If using
upgrade the file server to the level of the COPYSTGPOOLS parameter, correct the problem by
the operating system supported by the using a copy storage pool that already exists or define
server. the copy storage pool. If using the
ACTIVEDATAPOOLS parameter, correct the problem
Explanation: The IBM Spectrum Protect server was by using an active-data storage pool that already exists
trying to connect to a file server with an unsupported or define the active-data storage pool. Retry the
level of the operating system. The server can establish command.
NDMP connection only to a file server with supported
level of the operating system. Please check the
following site for supported levels of file server ANR4733E Command: The pool type storage pool
operating systems: http://www.tivoli.com/storage contains a pool type storage pool name
that introduces a cycle into the storage
System action: The IBM Spectrum Protect server pool chain.
backup/restore of the file server fails.
Explanation: A DEFINE STGPOOL or UPDATE
User response: Upgrade the file server to a supported STGPOOL command contained a copy or active-data
level of the operating system. storage pool that eventually points to the storage pool
being processed.
ANR4730E Command: The number of stgpool type System action: None.
storage pool names specified with the
parameter name parameter exceeds the User response: Remove the storage pool name from
maximum number allowed. the copy or active-data storage pool list and retry the
command.
Explanation: The number of copy storage pools
combined with the number of active-data storage pools
for a given primary storage pool is limited to a ANR4734W The pool type storage pool pool name was
maximum of three. removed from the storage pool list
because of a failure for session Session
System action: The command fails. Id.
User response: Reissue the command, specifying a Explanation: The named storage pool was removed
total of three or fewer storage pool names. from the storage pool list for the current session

backup/archive/space management operation because

ANR4738E Command: One or more storage pools use
of an error. This removal is only for the session
pool name as a copy, active-data, or
indicated in the message and does not effect other
container-copy type storage pool.
session operation.
Explanation: The DELETE STGPOOL command
attempted to delete a storage pool that is defined as a
User response: The error that occured could be one of copy storage pool, active-data storage pool, or
many failure. Look for the following items in the active container-copy storage pool for another primary
log or on the server console. 1. Is the named storage storage pool.
pool currently unavailable? 2. Have any I/O error
occured on the destination devices (disk or tape
command.
drives)? 3. Is the mount limit on the device class
correctly set? 4. Is the node's MAXNUMMP value User response: If necessary, issue the UPDATE
sufficient to satisfy the request? STGPOOL command to update the other primary
storage pool. Use the COPYSTGPOOLS,
ACTIVEDATAPOOLS, or PROTECTLOCAL parameter
ANR4735W Server-free processing is not available.
to remove the reference to the storage pool to be
Initialization failed.
deleted. Repeat for all primary storage pools that
Explanation: An error occurred while initializing reference the storage pool to be deleted. Reissue the
server-free processing. Server-free data transfer is not command.
available to backup and restore images.
System action: Client backup and restore image ANR4739E Either the high-level address (hladdress),
requests will use lan-based data transfer. low-level address (lladdress), or both
were entered in error.
User response: Check for messages during server
initialization and correct the error. Explanation: The high-level or low-level addresses
supplied are incorrect.
ANR4736E Command: The number of container-copy System action: The server does not process the
type storage pool names specified with command.
the parameter name parameter exceeds the
User response: Both the high-level address and
maximum number allowed.
low-level address are required for an address to be
Explanation: The number of container-copy storage valid. For an update, both high-level address and
pools for a given primary storage pool is limited to a low-level address are required for the update to
maximum of two. succeed. For a new definition, both high-level address
and low-level address are required when
System action: The command fails. SESSIONINIT=SERVERONLY. Either the high-level
User response: Reissue the command, specifying a address or low-level address is missing from this
total of two or fewer storage pool names. command. Issue the command again and supply the
missing address represented by a "?" in this message.
ANR4737E Transaction failed for session session

number for node node name (client ANR4740W Either the high level address, low level
platform) - the copy continue attribute for address, or both were never entered for
storage pool storage pool name prevented the specified node( nodename ) and the
further retries. session initiation status is being
changed.
Explanation: During a backup session one or more
copy storage pools associated with the indicated Explanation: When the session initiation status of a
storage pool had a failure. The operation was halted node is changed by using the SESSIONINIT parameter
because the copy continue option for the indicated on the UPDATE NODE command, the scheduling table
storage pool caused the process to stop. is updated to reflect the address specified with HLA
and LLA keywords of the UPDATE NODE command.
System action: None. If one or both of these keywords have never been used
User response: Verify the following: 1. Does the to provide addressing information for the node,
device class(es) have enough mount points to satisfy server-initiated scheduling will not be able to contact
the request? 2. Was the node's MAXNUMMP value this node.
sufficient to satisfy the request? 3. Were there any System action: The server does not update the
errors reported during the transaction regarding I/O or scheduling table. Subsequent server initiated sessions
related issues? with the node are likely to fail, unless an additional
UPDATE NODE command provides both the

HLADDRESS and LLA parameters with correct address

ANR4743W An insufficient number of mount points
information.
are available in device class device class
User response: Both the high level address and low name.
level address are required for an address to be valid.
Explanation: During simultaneous write processing,
Issue the UPDATE NODE command for this node with
the server cannot allocate sufficient mount points for
complete addressing information through the
the specified device class. Possible reasons include:
HLADDRESS parameter for the node address, and the
LLADDRESS parameter for the node listen port v The mount limit specified for the device class does
information. not provide a sufficient number of mount points to
support the simultaneous write operation.
v The drives that service the device class are
ANR4741W This command will rename
inaccessible.
administrator has defined or updated System action: None.
schedules. Renaming this administrator
User response: Ensure that:
will cause these schedules to fail.
v The mount limit specified for the device class
Explanation: A RENAME ADMINISTRATOR provides a sufficient number of mount points to
command has been entered for an administrator that support the simultaneous write operation.
owns administrative schedules. If you confirm that you
v Enough drives are defined and on-line for the library
want to proceed with this command, the schedules
that services the device class.
owned by this administrator will fail when executed in
the future.
ANR4744W The server cannot acquire a sufficient
number of mount points.
Explanation: During simultaneous write processing,
User response: To process the RENAME
the server cannot acquire a sufficient number of mount
ADMINISTRATOR command, enter 'Y' to continue or
points to satisfy the request.
'N' to stop the process. To deal with schedules owned
by the administrator, use the QUERY SCHEDULE System action: None.
command, or an SQL SELECT statement on the
ADMIN_SCHEDULES table to determine which User response: Examine error messages that might
schedules were last updated by the administrator. Use have been displayed prior to, and after this message.
the UPDATE SCHEDULE command to update those Correct any problems, if possible.
schedules contolled by an administrator that has
authority to execute them, or use the DELETE ANR4746E Session rejected for up level storage
SCHEDULE command to remove the schedules. agent storage agent name.
Explanation: An up level storage agent attempted to
ANR4742W This command has renamed connect to this server. The storage agent can not be at
administrator adminName to higher level than the server.
newAdminName. This administrator has
defined or updated schedules. This will System action: The server will not support
cause these schedules to fail in the connections by storage agents at a higher version, at
future. the same version with a higher release, or at the same
version and release with a higher modification level.
Explanation: A RENAME ADMINISTRATOR The storage agent will not startup and will report
command has been entered and the administrator ANR0454W indicating that no resources are available.
renamed owns the administrative schedules. The
schedules will fail when executed in the future because User response: None.
they do not belong to the administrator's new name.
System action: The system renames the administrator. ANR4747W The web administrative interface is no
longer supported. Begin using the
User response: Use the QUERY SCHEDULE command Integrated Solutions Console instead.
or an SQL SELECT statement on the
ADMIN_SCHEDULES table to determine which Explanation: The web administrative interface is no
schedules were last updated by the administrator. Use longer supported. It has been replaced by an
the UPDATE SCHEDULE command to update those administrative interface based on the Integrated
schedules controlled by an administrator that has Solutions Console.
authority to execute them, or use the DELETE System action: The web administrative interface's web
SCHEDULE command to remove the schedules. page is not displayed.

User response: Install the IBM Spectrum Protect Explanation: The REPAIR STGVOL process has ended.
support for the Integrated Solutions Console and begin It processed volumes processed out of total volumes total
using it to manage your servers. volumes to be processed. The repaired volumes indicates
the number of volumes that needed database repairs
and were repaired. The failed volumes are volumes that
ANR4748E A NAS operation requiring NDMP
either failed during evaluation or during database
Version 4 was attempted for file server
repair if it was needed.
File server name , however the current
NDMP session uses NDMP Version 3. System action: None.
Please verfiy that file server supports
User response: If there were failed volumes, review the
NDMP version 4.
activity log for more information about the failure.
Explanation: A NAS operation which requires NDMP
Version 4 was attempted for a file server that is
ANR4754I REPAIR STGVOL process process number
currently configured to run NDMP Version 3.
ended, processed volumes processed of
System action: The IBM Spectrum Protect server total volumes total volumes with repaired
backup/restore or other operation on the file server volumes repaired.
fails.
Explanation: The REPAIR STGVOL process has ended.
User response: Verify that the file server supports It processed volumes processed out of total volumes total
NDMP Version 4. Verify that the file server is volumes to be processed. The repaired volumes indicates
configured to accept connections using NDMP Version the number of volumes that needed database repairs
4. and were repaired.
ANR4749I Key-ring filename and password have
been deleted from the server database.
Explanation: The key-ring filename and password
ANR4755W REPAIR STGVOL process process number
have been deleted. Upon restart the server will attempt
to generate a new password and new keyring file if
total volumes total volumes with repaired
options SSLTCPPORT or SSLTCPADMINPORT are set
volumes repaired.
and the keyring files cert.kdb,cert.crl,cert.rdb do not
exist. Explanation: The REPAIR STGVOL process has ended.
It processed volumes processed out of total volumes total
volumes to be processed. The repaired volumes indicates
User response: Before restarting the server you should the number of volumes that needed database repairs
delete the corresponding cert.kdb,cert.crl,cert.rdb and and were repaired.
cert.arm files from the server execution directory if they
exist. Restart the server to generate and use the new
key-ring information. User response: If the volumes processed is less than the
total volumes, this may be because the process was
cancelled before it could process all the needed
ANR4752I REPAIR STGVOL process process number
volumes. Review the activity log to determine if this is
started for number of volumes volumes.
the case and re-issue the command to complete this
Explanation: The REPAIR STGVOL process has been processing. Or if volumes were reclaimed or deleted
started as the reported process number. This will while this process was running, there may have been
evaluate and if needed repair the indicated number of fewer actual volumes to process than what was
volumes. calculated when the process started. If this is the case
no further action is necessary.
User response: This process may be monitored using
ANR4757I REPAIR STGVOL finished evaluating
the QUERY PROCESS command. If this process needs
volume volume name, no repair was
to be cancelled, issue the CANCEL PROCESS
needed.
command.
Explanation: The REPAIR STGVOL finished
evaluating volume name volume. No repair actions were
ANR4753E REPAIR STGVOL process process number
taken for the database because there were no errors
detected.
total volumes total volumes with repaired
volumes repaired and failed volumes System action: None.
failures.

ANR4758W REPAIR STGVOL repaired volume ANR4762E Command: The SPACEMANAGED or

volume name, database reference errors ARCHIVE type parameters are not valid
were found and corrected. for active data storage pool volumes.
Explanation: The REPAIR STGVOL evaluated volume Explanation: The QUERY CONTENT server command
name volume and determined that repair actions were has been entered with an invalid type parameter. The
needed. The necessary repairs were done successfully. SPACEMANAGED or ARCHIVE parameters are not
valid when the volume specified belongs to an
active-data type storage pool.
User response: Reissue the command with correct
ANR4759E REPAIR STGVOL failed to process
TYPE parameter for active data storage pool.
volume name.
Explanation: The REPAIR STGVOL failed for volume
ANR4763E Command: Invalid parameter - parameter.
name volume. This process either failed while
evaluating this volume or it had determined that repair Explanation: The specified server command has been
actions were needed and it failed performing those entered with an invalid parameter that is not applicable
actions. when using z/OS Media library for sequential FILE
storage.
User response: Review the activity log for an
indication of why processing for this volume failed. Try User response: Reissue the command and enter the
issuing "REPAIR STGVOL VOLNAME=volume name" to proper syntax. Neither NUMBEROFVOLUMES nor
process this volume again. If this volume was deleted FORMATSIZE parameter is valid when using z/OS
from the server, this message can be ignored. Media library for sequential FILE storage. The z/OS
Media server formats each FILE volume as it is being
filled.
ANR4760I REPAIR STGVOL reset processing
history.
ANR4764E Command: Invalid length for parameter
Explanation: The REPAIR STGVOL command was
parameter - parameter value.
issued with RESET=YES. This resets the processing
history. Resetting the processing allows the command Explanation: The length for (parameter value) specified
to be rerun and causes previously evaluated volumes to for the (parameter) parameter in command command
be re-evaluated. exceeds the maximum allowed length.
System action: None. System action: The command fails and server
User response: An administrator may want to
periodically reset the processing history and re-evaluate User response: Reissue the command and specify a
all volume in the server as a means of validating the valid length for the parameter.
server database.
ANR4765I The key-ring file password was set.
ANR4761E REPAIR STGVOL reset processing Restart the server to use the new
history failed. password.
Explanation: The REPAIR STGVOL command was Explanation: The password that is used by the server
issued with RESET=YES. This resets the processing for the key-ring file was set to a value that was
history. However, the reset of the processing history specified in the SET SSLKEYRINGPW command. This
failed. is typically done after the key-ring file's password is
changed using an external utility.
User response: The server is likely out of memory or
resources. This command should be re-issued after User response: Restart the server to use the new
either halting and restarting the server or after halting key-ring file password.
the server, rebooting the server machine, and than
restarting the server. If the reset still fails after these
steps, contact your IBM service representative.

ANR4766E The server could not access the key-ring ANR4769W Command: Alert trigger is already
file using the password specified in the defined for message number.
SET SSLKEYRINGPW command.
Explanation: A DEFINE ALERTTRIGGER command
Explanation: The password used by the server for the has been entered that specifies a message number that
key-ring file was checked for validity but was not is already defined with the server.
valid.
System action: The server skips the message number
System action: None and continues processing the command.
User response: The QUERY SSLKEYRINGPW User response: Use the UPDATE ALERTTRIGGER
command will show you the key-ring file password command to update the alert trigger if needed.
that the server is currently using. If the password was
changed with an external utility, ensure that the
ANR4770W Command:Invalid message number
password is the same as that which was specified in
message number.
the SET SSLKEYRINGPW command. If the password
was lost, issue the DELETE KEYRING command to Explanation: The message number is invalid because
delete the current key-ring file. When you restart the the message number is in an incorrect format or does
server it will generate a new key-ring file, password, not exist on the server.
and self-signed certificate. Issue the QUERY
SSLKEYRINGPW command to obtain the new System action: The server skips the specified message
password. Then use an external utility to import number and continues to process the rest of the
additional certificates again and designate one as the command.
new default. Restart the server to use the additional User response: Verify that the format of the message
certificates. number is correct and exists on the server. Reissue the
command specifying the correct message number.
ANR4767E The server was unable to change the
key-ring file password using the new ANR4771W Command: Administrator admin name
password specified on the SET cannot be processed because it is not
SSLKEYRINGPW command along with registered or is locked.
the old password that the server has
stored. Explanation: This command cannot be processed for
the indicated administrator name. The administrator
Explanation: The previous key-ring file password name is not registered or is locked.
remains in effect.
System action: The indicated administrator name is
System action: None not processed. The server continues to process the other
User response: The QUERY SSLKEYRINGPW administrator names specified with the command.
command will display the key-ring file password that User response: If the administrator name was
the server is currently using. If the SET specified incorrectly, reissue the command with the
SSLKEYRINGPW password UPDATE=YES command is correct name. If the administrator name is locked,
unable to update the key-ring file password, the determine if it can be unlocked. Use the UNLOCK
key-ring file and it's password can be deleted and ADMIN command to unlock it, and reissue the
re-created by: 1. Issuing the DELETE KEYRING command specifying the administrator name.
command to delete the server's record of the key-ring
file and password. 2. Stopping the server. 3. Deleting
files cert.* in the server's instance directory. 4. ANR4772I Alert trigger message number defined.
Restarting the server so that the key-ring file and it's Explanation: The requested alert trigger has been
password are regenerated by the server. added to the server in response to the command.
ANR4768E Command: Invalid volume name - volume
name. User response: None.

invalid FILE volume name for a ZOSMEDIA library ANR4773I Alert trigger message number deleted.
volume. Explanation: The requested alert trigger has been
System action: The server does not process the deleted from the server.
volume name that does not exceed 44 valid characters.

ANR4774I Command command processed. ANR4779E Command: The requested update for alert
id, alert identifer, is invalid. The alert is
Explanation: The specified command was processed.
not changed.
Explanation: The specified update request is invalid
User response: Review previous messages. Correct the or not correct for the alert. You can change the status of
problem and reissue the command. an alert from active to inactive or closed, or, from
inactive to closed. If you are specifying the ASSIGNED
or RESOLVEDBY parameters the value must be a
ANR4775W Command: Alert trigger message number is registered administrator name that is not locked.
not defined.
Explanation: The specified message number does not command.
refer to a defined alert trigger in the server database.
System action: The server skips the specified message valid status for the alert. Issue the QUERY
number and continues to process the rest of the ALERTSTATUS command to display a list of existing
command. alerts and status.
message number that is defined as an alert trigger. ANR4780I Node group node group name defined.
Issue the QUERY ALERTTRIGGER command to display
a list of defined message numbers. Explanation: A DEFINE NODEGROUP command has
created the node group indicated.
ANR4776I Command: Administrator admin name for System action: None.
message number is action.
Explanation: The command has performed the action
and added or deleted the administrator name
ANR4781E Command: Invalid node group name -
successfully for the specified alert trigger.
node group name.
User response: None. command fails because the node group name node group
ANR4777I Command: Administrator admin name is
already defined to alert message number. System action: Database changes for the command are
Explanation: The command specifies an administrator command is not successful in changing the server
name already defined to the alert. database.
System action: The server skips the administrator User response: Issue the command again and specify
name and continues processing the command. a node group name that conforms to the name
User response: None. requirements.
ANR4778E Command: Alert alert identifer could not ANR4782E Command: Description exceeds maximum
be found. length of length limit characters.
Explanation: The specified alert was not found in the Explanation: Server processing for the command
server database. command fails because the description specified is
longer than the length limit number of characters
System action: The specified alert identifier is allowed.
skipped. The server continues to process the next alert
identifier that is specified in the command. System action: Database changes for the command are
User response: Reissue the command, specifying an command is not successful in changing the server
alert identifier for an alert that has not been closed or database.
deleted on the server. To display a list of existing alerts,
issue the QUERY ALERTSTATUS command. User response: Issue the command again and specify
a shorter description.

ANR4783E Command: Node group node group name is ANR4787I Command: number of nodes members
not defined. defined in the node group node group
name.
command fails because the node group name node group Explanation: A DEFINE NODEGROUPMEMBER
name specified does not refer to a defined node group command has created the specified number of members
in the server database. in the indicated node group.
System action: Database changes for the command are System action: None.
database.
ANR4788I Command: number of nodes members
deleted from node group node group
node group name that is defined in the server database.
name.
For a list of the names of defined node groups in the
server database, issue the QUERY NODEGROUP Explanation: A DELETE NODEGROUPMEMBER
command. command has deleted the specified number of
members from the indicated node group.
ANR4784I Node group node group name updated. System action: None.
Explanation: In response to the UPDATE User response: None.
NODEGROUP command, the node group node group
name has been updated in the server database.
ANR4789I Node node name associated to node
System action: Server operation continues. group node group name.
User response: None. Explanation: This message is displayed in response to
the DEFINE NODEGROUPMEMBER command. Node
node name is associated with the node group name node
ANR4785I Node group node group name deleted.
group name.
NODEGROUP command, the node group node group
name has been deleted from the server database. User response: None.
ANR4790I Node node name disassociated from node
group node group name.
ANR4786E Command: Node group node group name
the DELETE NODEGROUPMEMBER command. Node
still contains at least one node.
node name is no longer associated with the node group
Explanation: Server processing for the delete name node group name.
command command fails because the node group node
group name specified refers to a node group that still
contains at least one node. A node group cannot be User response: None.
deleted if one or more client nodes are still assigned to
the node group.
ANR4791E Command: Node group node group name is
System action: Database changes for the command are already defined.
command is not successful in changing the server Explanation: Server processing for the command
database. command fails because the node group name node group
name specified refers to a node group that is already
User response: To remove remaining nodes from the defined in the server database.
node group, issue the DELETE NODEGROUPMEMBER
command. After all nodes are removed, issue the delete System action: Database changes for the command are
command again. rolled back and server operation continues. The
database.
node group name that is not defined in the server
database. For a list of the names of defined node

groups in the server database, issue the QUERY server supports NDMP 3-way operations. Verify that
NODEGROUP command. the network configuration of the system running the
IBM Spectrum Protect server is reporting a valid
TCP/IP host address. .
ANR4792E NDMP Tape server unable to initialize
due to error in LISTENing on port Port
ANR4795E The IBM Spectrum Protect tape server
Explanation: The server failed in attempting to listen
failed to open an NDMP data
for session requests on the server's internal tape server.
connection to the NAS file server File
System action: Server operation continues, but NDMP server name .
operations may fail.
Explanation: During a NAS filer-to-server restore
User response: Ensure that the operation the data connection from the IBM Spectrum
NDMPCONTROLPORT option defaults to or is set to a Protect server to the NAS file server failed. This may
port number which is available in the system. The occur if the NAS file server is not properly configured
QUERY OPTION command can be used to determine to support NDMP 3-way restore operations.
the port number associated with the
NDMPCONTROLPORT option. If this value requires
restore operation on the file server fails.
change, the server will have to be restarted after setting
the option in the server options file. User response: Verify that the file server supports
NDMP 3-way restore operations. .
ANR4793E NDMP Tape server is terminating due to
an error in accepting a new session on ANR4796E The IBM Spectrum Protect tape server
Port Port failed to open a listening socket for
accepting an NDMP data connection
Explanation: The server failed in attempting to accept
from a NAS file server using the
a new session on the server's internal tape server.
network interface network host name .
System action: Server operation continues, but NDMP
Explanation: During a NAS filer-to-server backup
operations may fail.
operation the IBM Spectrum Protect tape server failed
User response: Ensure that the to open a TCP/IP socket in order to listen for NDMP
NDMPCONTROLPORT option defaults to or is set to a data connections from a NAS file server. This may
port number which is available in the system. The occur if the network interface chosen for NDMP data
QUERY OPTION command can be used to determine connections is not running or does not support IP
the port number associated with the Version 4.
NDMPCONTROLPORT option. If this value requires
change, the server will have to be restarted after setting
backup operation of the file server fails.
the option in the server options file.
User response: Verify that the network interface
specified in the NDMPPREFDATAINTERFACE server
ANR4794E The NAS file server File server name
option is properly configured and running. .
failed to open an NDMP data
connection to the IBM Spectrum Protect
tape server. Please verify that the file ANR4797E Drive driveName is missing path
server is capable of outbound data information. Please check that all
connections. related paths are defined properly.
Explanation: During a NAS filer-to-server backup Explanation: A drive does not have sufficient path
operation the data connection from the file server to the information for the operation to complete. This is
IBM Spectrum Protect server failed. This may occur typically due to a path not being defined.
because a firewall exists between the file server and the
System action: The server fails the storage operation.
IBM Spectrum Protect server and is preventing
outbound network connections on the file server. This User response: Verify that all applicable paths are
may also occur if the network configuration of the defined for the drive. Also verify that the information
system running the IBM Spectrum Protect server is contained in the paths is correct.
reporting an invalid TCP/IP host address, for example
"127.0.0.1".
ANR4799I The AUDIT CONTAINER (Orphaned
System action: The IBM Spectrum Protect server Extent Identification) process started for
backup operation on the file server fails. storage pool stgpool name (process ID
process ID).
User response: Verify that the NAS file server is
capable of starting outbound network connections to Explanation: As the result of an AUDIT CONTAINER
the IBM Spectrum Protect server. Verify that the file

command that specified scan action for the storage pool System action: None.
shown, the process whose ID is displayed has begun
User response: Attempt to reset the node's password
checking the contents of the storage pool for orphaned
expiration period at a later time.
extents.
System action: The contents of the storage pool will
ANR4808W The password expiration period for all
be scanned, and objects not listed in the database as
administrators and nodes has been reset
valid extents will be marked as orphaned.
to the common password expiration
User response: None. period.
Explanation: All administrators not managed by a
ANR4802I Password expiration period for node profile and nodes on this server have had their
node name has been reset. password expiration period reset to the common
password expiration period.
Explanation: The node's password expiration period
has been reset to the common password expiration System action: None.
period.
User response: None. ANR4817E Command Command: Administrator
admin is not allowed to issue this
command while the system date is
ANR4803I Password expiration period for
suspect. Correct the system date or use
administrator administrator name has
the ACCEPT DATE command to
been reset.
establish the current date as valid.
Explanation: The administrator's password expiration
Explanation: The server has noted that the current
period has been reset to the common password
system date is suspect. An admin client session may
expiration period.
issue the ACCEPT DATE command to establish the
System action: None. current date as valid. No other commands are allowed
until the system date is corrected or the current date is
User response: None. established as valid.
ANR4804I Node node name already uses the
common password expiration period. User response: If the current system date is not valid,
reset the date. Otherwise, use the ACCEPT DATE
Explanation: The node's password expiration period is command to establish the current date as valid on the
currently set to the common password expiration server. Reissue the command.
period.
Accepting an invalid date can cause any of the
System action: None. following problems:
User response: None. v Premature deletion of data
v Excessive retention of data
ANR4805I Administrator administrator name already v Scheduling problems
uses the common password expiration v Event record problems
period.
v Password expiration problems
Explanation: The administrator's password expiration
period is currently set to the common password
expiration period. ANR4818E The text cannot be formatted and
written to the server console. The text is
System action: None. text. Try setting a wider screen width.
User response: None. Explanation: For the server command issued, the
server is unable to format and write output in table
format to the server console. The line width of some
ANR4807W The server is unable to reset
text of the output exceeds the size of the window.
administrator name password expiration
period to the common password System action: The server will not write the output to
expiration period. the console. The server continues operation.
Explanation: The administrator's password expiration User response: Increase the width of your window
period could not be reset to the common password and try the command again.
expiration period at this time.

ANR4819E Session session number for node node ANR4824E The loading or reading of a table of
name is not authorized to a table of contents for node node name, file space
contents session. file space name failed because of a lock
conflict.
Explanation: A client attempted to work with a table
of contents (TOC) session, but the node lacks proper Explanation: The server ends a table of contents
authorization. The server will not perform the request. (TOC) loading or reading for the specified node and
file space because the requested resource is already in
System action: The server will not perform the
use by another process.
request.
System action: The TOC loading or reading is ended
User response: Complete the work using a node with
proper authorization.
User response: Try the operation again at a later time.
ANR4820E Command The creation date and creation
time are both required to be specified. ANR4826E The object for the table of contents is
not found in the server for node node
Explanation: The server-free process did not complete
name, file space file space name.
due to the target being unreachable.
Explanation: The server ends a table of contents
(TOC) loading or reading for the object in the specified
User response: Reissue the command, specifying both node and file space, because the server cannot find the
creation date and creation time, or neither of them. object for the TOC.
ANR4821E Command: The creation date - date. and server operation continues. The TOC object could
is not valid be deleted from the server during server expiration or
volume deletion operation.
with an invalid creation date. User response: Make sure a correct TOC object is
specified.
ANR4827E The loading of a table of contents for
User response: Issue the command with a valid node node name, file space file space name
creation date. failed because a thread resource not
available.
ANR4822E Command: The creation time date Explanation: The server ends a table of contents
is not valid. (TOC) loading for the specified node and file space
Explanation: The specified command has been issued because sufficient memory is not available for starting
with an invalid creation time. additional processes on the server.
System action: Server operation continues, but the System action: The TOC loading is ended and server
command is not processed. operation continues.
User response: Issue the command with a valid User response: See the documentation for the
creation time. operating system about how to increase memory for an
application.
ANR4823E The loading or reading of a table of

contents for node node name, file space ANR4828E The loading or reading of a table of
file space name failed because sufficient contents for node node name, file space
memory is not available. file space name failed because an internal
server error was detected.
(TOC) loading or reading for the specified node and Explanation: The server ends a table of contents
file space because sufficient memory is not available on (TOC) loading or reading for the specified node and
the server. file space because an internal logic error is detected.
System action: The TOC loading or reading is ended System action: The TOC loading or reading is ended
and server operation continues. and server operation continues.
User response: See the documentation for the User response: Examine the server messages issued
operating system about how to increase memory for an prior to this message to determine the source of the
application. error. Issue the QUERY ACTLOG command to view the

activity log and search for messages. If the error cannot User response: Try the TOC loading or reading again
be isolated and resolved, contact your service and make sure the necessary volumes are accessible.
representative.
ANR4833W The loading or reading of a table of
ANR4829E The loading or reading of a table of contents for node node name, file space
contents for node node name, file space file space name failed. The file was
file space name failed. The transaction is deleted from server storage.
stopped.
Explanation: During the table of contents (TOC)
Explanation: An error was detected during transaction loading or reading operation the file has been deleted
commit. This message should be preceded by other from server storage by another process before the
messages that give additional information about the loading or reading is complete.
failed transaction.
System action: The table of contents (TOC) loading or and server operation continues.
reading is ended and server operation continues.
User response: Check for additional messages and if DELETE FILESPACE, DELETE VOLUME, or
eliminate the condition that caused the failed inventory expiration processes are running; these
transaction. If the error cannot be isolated and resolved, processes can delete files in server storage during TOC
contact your service representative. loading or reading.
ANR4830E The loading or reading of a table of ANR4834E The loading or reading of a table of
contents for node node name, file space contents for node node name, file space
file space name failed. Insufficient mount file space name failed. The data transfer is
points are available to satisfy the interrupted.
request.
Explanation: The server was unable to allocate (TOC) loading or reading for the specified node and
sufficient mount points to read the table of contents file space because data transfer to or from data storage
(TOC). was interrupted by an external event.
System action: The TOC loading or reading is ended System action: The TOC reading is ended and server
and server operation continues. operation continues.
User response: If necessary, make more mount points User response: Examine the messages issued prior to
available. this message to determine why the data transfer was
interrupted. Attempt the operation again if the problem
can be resolved.
ANR4831E The loading or reading of a Table of
Contents for node node name, file space
file space name failed. The input volume ANR4835E The reading of a table of contents for
is already in use. node node name, file space file space name
failed. A data integrity error was
Explanation: During the TOC loading or reading
detected.
operation, the requested input volume is already in use
by another process. Explanation: The server stops reading a table of
contents (TOC) for the specified node and file space
because a data integrity has been encountered on the
server.
User response: Try the operation again at a later time.
System action: The TOC reading is ended and server
ANR4832E The loading or reading of a table of
contents for node node name, file space
this message and contact your service representative.
file space name failed. The required
volume was not mounted.
ANR4836E The reading of a table of contents for
Explanation: During the table of contents (TOC)
node node name, file space file space name
loading or reading operation, a required volume cannot
failed. There was an error in reading
be mounted. The mount request may have been
from a device.
canceled.
(TOC) reading for the specified node and file space

because an I/O error has been encountered by the

ANR4841E The loading for the table of contents for
server in reading from a device.
System action: The TOC reading is ended and server failed. An invalid object type detected.
Explanation: The loading for the table of contents
User response: Examine the messages issued prior to (TOC) in the specified node and file space failed
this message that specify the device that is failing. The because the object type given is different than the one
server may need to be shut down with a HALT in the server database.
command to correct the hardware problem.
System action: The TOC loading is ended and the
ANR4837I The loading for the table of contents for
User response: Re-try the Table of Contents loading,
specifying a valid object type.
started.
Explanation: The loading for the table of contents
ANR4842E The loading of a table of contents for
(TOC) in the specified node and file space has been
node node name failed. The file space
started.
name was not found.
User response: None. (TOC) loading for the specified node because the server
could not find the file space name for the TOC object to
be loaded.
ANR4838I The loading for the table of contents for
node node name, file space file space name System action: The TOC loading is ended and server
was successful: total entries loaded operation continues.
number of entries.
User response: The file space could be deleted during
Explanation: The loading for the table of contents the TOC loading operation. Issue QUERY FILESPACE
(TOC) in the specified node and file space has been command to verify if the file space is deleted. Make
successfully finished. sure the correct file space name is specified. You can
issue a QUERY FILESPACE to ensure that the file space
System action: The server operation continues. exists. Re-issue the request with the correct file space
User response: None. name.
ANR4839E The loading for the table of contents for ANR4843I Command: Displayed number of objects
node node name, file space file space name objects, number of errors errors were
failed. See previous messages. encountered.
Explanation: The loading for the table of contents Explanation: QUERY TOC has completed. The
(TOC) in the specified node and file space has failed. number of objects displayed and the error count are
displayed.
System action: The TOC loading is ended and the
server operation continues. System action: The QUERY TOC command ends and
this message to determine the source of the problem. User response: If the error count is not equal to 0,
examine the object name displayed. The error count
represents the number of objects that have their names
ANR4840I The loading for the table of contents for displayed as '...'. This is because the conversion from a
node node name, file space file space name UTF-8 to a local code page for the file name failed. If
was cancelled. this is the case, re-issue the QUERY TOC command
Explanation: The loading for the table of contents with FORMAT=DETAILED. The object name will be
(TOC) in the specified node and file space has been displayed in a hexadecimal format when the
cancelled by the user. FORMAT=DETAILED is specified. The file may contain
an invalid character and may need to be renamed. A
System action: The TOC loading is ended and the new backup copy has to be made for the renamed file
server operation continues. so that the file can be displayed correctly and restored
User response: None. later.

User response: Run an audit container on the

ANR4844I Command: The specified table of
container.
contents for node node name, file space
file space name contains no entries.
ANR4848E Container container name is in a container
Explanation: The specified table of contents (TOC)
state state and cannot be audit.
exists, but it is empty. No entries are displayed.
Explanation: You cannot audit a container that is in a
pending state. You can audit containers that specify one
User response: None. of the following states: available, unavailable, or
readonly.
ANR4845E The writing of the of the table of System action: The command fails and server
contents for node node name, file space operation continues.
file space name failed: a directory path
User response: Reissue the command with a different,
exceeds max characters bytes in length.
valid container name.
File: lowLevel name, NDMP Node ID:
node id hi .node id lo, NDMP Parent Node
ID:Parent id hi. Parent id lo. ANR4849I The AUDIT COPYCONTAINER
command process process id completed:
Explanation: During a backup of a NAS filesystem,
delete chunk count damaged chunks
the server received a file history record from the NAS
deleted.
device with a directory path length which exceeded the
maximum length supported by IBM Spectrum Protect. Explanation: The AUDIT COPYCONTAINER
The server is unable to create a TOC for a NAS command that specifies the
filesystem which contains directory that is longer than ACTION=REMOVEDAMAGED parameter has
1024 bytes. If the TOC parameter on the BACKUP completed processing
NODE command is PREFERRED, the backup
continues. If the TOC parameter was YES, the backup The following information is displayed:
fails. v The number of damaged chunks deleted.
System action: The TOC creation is ended and server System action: None.
User response: If TOC=YES was specified on the
BACKUP NODE command, retry the command with
ANR4850W The repair storage pool process for
TOC=NO.
stgpool name on server this server from
stgpool name on server other server is
ANR4846E Operation process process ID terminated - complete. Some extents might not have
The server is unable to create a table of been repaired. Extents repaired: extents
contents for node node name, file space repaired of extents to repair. Extents failed:
file space. extents failed. Extents skipped: extents
skipped. Amount repaired: amount repaired
Explanation: While attempting to create a table of of amount to repair. Amount failed:
contents (TOC) for the specified node and file space in amount failed. Amount skipped: amount
the indicated TOC destination pool, a failure occurred. skipped. Elapsed time: elapsed time.
System action: The operation fails because TOC Explanation: The repair storage pool repair process is
creation is set to YES. complete, but some extents might have been skipped
User response: Look for previous messages giving a due to if the volume was unavailable. The following
specific reason for the failure. Take corrective action as list describes the information in the message:
appropriate. v Extents repaired: indicates the number of extents that
were successfully repaired.
ANR4847W command detected an extent with ID v Extents failed: indicates the number of extents that
extent id on container cntrname that is failed to be repaired.
marked damaged. v Extents skipped: indicates the number of extents that
were skipped.
Explanation: The extent is skipped during command
processing due to it being damaged. v Amount repaired: indicates the number of bytes that
were successfully repaired.
System action: The operation skips the extent and
v Amount failed: indicates the number of bytes that
failed to be repaired.

v Amount skipped: indicates the number of bytes that command are now provided by one or more new
were skipped. commands
v Elapsed time: indicates how long the process ran. System action: System operation continues.
User response: Issue the REPAIR STGPOOL command User response: Review information about product
again to ensure that all data extents are repaired. changes in the product information:
ANR4851W The preview of repair storage pool SSEQVQ/).
stgpool name on server other server is ANR4857I Command command subcommand is no
complete. Some extents might not have longer supported. The following options
been identified as needing repair. provide similar functions: newoptions.
Extents to be repaired: extents repaired. See the IBM Knowledge Center for
Amount to be repaired: amount repaired. details on the options or issue the HELP
Explanation: The repair storage pool repair process is command for the replacement options.
complete in preview mode, but some extents might Explanation: The functions formerly provided by this
have been skipped due to if the volume was command are now provided by one or more new
unavailable. The following list describes the options
information in the message:
System action: System operation continues.
v Extents to be repaired: indicates the number of
extents to be repaired. User response: Review information about product
v Amount to be repaired: indicates the number of changes in the product information:
bytes to be repaired. (http://www.ibm.com/support/knowledgecenter/
SSEQVQ/).
ANR4852W command detected damaged extents on

container cntr name. ANR4858I Option option name is no longer
supported and there is no direct
Explanation: The damaged extents are skipped during replacement for this capability.
command processing.
Explanation: The funtions formerly provided by this
System action: The operation skips the damaged option are no longer necessary
extents and continues processing.
System action: System operation continues.
User response: To analyze damaged extents, issue the
QUERY DAMAGED command for the specified User response: Review information about product
container. changes in the product information:
SSEQVQ/).
ANR4855I Command command subcommand is no
longer supported and there is no direct
replacement for this capability. ANR4859I Parameter parameter name on the
command command name is no longer
Explanation: The functions that were provided by this supported.
command are no longer neccessary.
Explanation: The function that was provided by this
System action: System operation continues. parameter is no longer necessary
User response: Review information about product System action: System operation continues.
changes in the product information:
(http://www.ibm.com/support/knowledgecenter/ User response: Review information about product
SSEQVQ/). changes in the product information:
SSEQVQ/).
ANR4856I Command command subcommand is no
longer supported. The following
commands provide similar functions: ANR4860W The correct value of ARCHRETENTION
newcommand. See the IBM Knowledge for domain domain name will not be sent
Center for details on commands, or to the managed servers. Please upgrade
issue HELP command for the the managed servers to be at least the
replacement commands. same level as that of the configuration
manager.
Explanation: The functions formerly provided by this
Explanation: The configuration manager has an

ARCHRETENTION value that is greater than the Explanation: The received value of the
managed server can manage. This is because the ACTIVEDESTINATION parameter contains active-data
managed server is at a lower level than the storage pool IDs that cannot be managed by the
configuration manager. The value of the managed server. The problem is that the release level of
ARCHRETENTION for the indicated domain is set to the configuration manager is earlier than the release
the maximum value that the managed server can level of the managed server.
process.
User response: Upgrade the configuration manager to
User response: To correctly send the value of the the same release level or later than that of the managed
ARCHRETENTION to the managed servers, please server.
upgrade the managed servers to at least the same level
as that of the configuration manager.
ANR4864E The module name support module was
not loaded.
ANR4861W The correct value of RETVER for the
Explanation: The indicated support module was not
archive copy group domain name policy set
loaded.
name mgmt class name cg name will not be
sent to the managed servers. Upgrade System action: The server cannot perform functions
the managed servers to at least the same that require this module.
level as that of the configuration
manager. User response: Restart the IBM Spectrum Protect
server and retry the operation. If the support module
Explanation: The configuration manager has a does not load, contact your service representative.
RETVER value that is greater than what the managed
server can process. This is because the managed server
is at a lower level than the configuration manager. The ANR4865W The server name has been changed.
value of the RETVER for the indicated copy group is Windows clients that use
set to NOLIMIT in the managed server. "passwordaccess generate" may be
unable to authenticate with the server.
Explanation: After the name of an IBM Spectrum
User response: To correctly send the value of RETVER Protect server is changed, the generated password on
for the copy group to the managed servers, please Windows backup-archive clients is not usable. The
upgrade the managed servers to at least the same level password is generated on backup-archive clients that
as that of the configuration manager. use "passwordaccess generate". The generated
password is not usable because the generated password
is stored in the Windows registry in a key that contains
ANR4862W The value of the
the server name, such as the following:
ACTIVEDESTINATION parameter for
HKLM\SOFTWARE\IBM\ADSM\CurrentVersion\
domain domain name will not be sent to
BackupClient\Nodes\<NODENAME>
the managed server server name because
\<SERVERNAME>\Password
the release level of the managed server
If the backup-archive client is not able to authenticate
is earlier than the release level of the
with the IBM Spectrum Protect server then scheduled
operations for that client will not run.
Explanation: The configuration manager has a value
System action: Until the password is reset, the
for the ACTIVEDESTINATION parameter that contains
Windows backup-archive clients that use
active-data storage pool names that cannot be managed
"passwordaccess generate" are unable to authenticate
by the managed server. The problem is that the release
with the IBM Spectrum Protect server.
level of the managed server is earlier than release level
of the configuration manager. User response: Either change the IBM Spectrum
Protect server name back to the original name, or reset
the password on the server using the UPDATE NODE
User response: Upgrade the managed server to the command to a known password and then use dsm,
same release level or later than that of the configuration dsmc, or dsmcutil to manually set the password on all
manager. Windows backup-archive clients that use
"passwordaccess generate".
ANR4863W The value of the
ACTIVEDESTINATION parameter for
domain domain name that was received
from the configuration manager will not
be used on the managed server.

the PING SERVER command can verify server

ANR4866I Node node name is not a member of a
credentials, upgrade a remote V6.3 server to V6.3.5 or
domain that is configured to use active
later, or a remote V7.1 server to V7.1.1 or later. Remote
data pool active data pool name.
servers at earlier levels accept the PING SERVER
Explanation: The primary storage pool to which the command without verifying credentials.
client node will write data is capable of using an active
data pool. However the client node is not a member of
ANR4870W Audit command: Storage pool storage pool
a domain that is authorized to write to the active data
name, specified as a Table of Contents
pool.
(TOC) destination for copy group copy
System action: Data from the node is not written to group name in management class
the active data pool. management class name, policy set set
name, domain domain name, does not
User response: If the client node data must be written
exist.
to an active data pool, move the client node to a
domain that is authorized for this action or update the Explanation: A database audit process finds a storage
current domain for active data pool processing. pool specified for the Table of Contents (TOC)
destination of the specified copy group that is not
defined in the server database. If this copy group is
used in an active policy set, then the NDMP backup
name (client platform) terminated - session
with a TOC creation operation may fail when
retry failed.
attempting to put TOC entries in the destination.
Explanation: The specified client session is ended by
the server because a previous error has been detected
on the server. Retry attempts were not able to resume User response: After the audit command completes,
the session. use the DEFINE STGPOOL command to define the
missing storage pool, or the UPDATE COPYGROUP
System action: The session is ended and server
command to update the copy group to refer to an
existing storage pool.
User response: If the session is a proxied LAN-Free
session for a storage agent, this error might be the
ANR4871I Collocation group collocation group name
result of a mount point or volume preemption on the
defined.
storage agent. Review the messages logged by the
storage agent to determine if a storage agent action Explanation: A DEFINE COLLOCGROUP command
caused the error. Review the messages logged by this has created the collocation group indicated.
session to determine alternate causes.
ANR4868I Canceling the Database Backup session
session number for node node name is not
allowed. ANR4872E Command: Invalid collocation group
name - collocation group name.
Explanation: The server cannot cancel the session that
is specified in the CANCEL SESSION command. Explanation: Server processing for the command
command fails because the collocation group name
collocation group name specified does not contain valid
User response: Database Backup sessions cannot be characters or contains too many characters.
cancelled with the CANCEL SESSION command. Issue
the CANCEL PROCESS command to terminate the
Database Backup operation.
database.
ANR4869I The server credentials cannot be
authenticated for server server name
a collocation group name that conforms to the name
because the server is not at a required
requirements.
level for authentication with the PING
SERVER command.
ANR4873E Command: Collocation group description
Explanation: For password authentication purposes,
exceeds maximum length of length limit
the server must be at the current level.
characters.
User response: No action is required. To ensure that command fails because the collocation group description

specified is longer than the length limit number of collocation group name that is defined in the server
characters allowed. database. For a list of the names of defined collocation
groups in the server database, issue the QUERY
COLLOCGROUP command.
database. ANR4878I Command: number of nodes members
defined in the collocation group
a shorter collocation group description.
Explanation: A DEFINE COLLOCMEMBER command
has created the specified number of members in the
indicated collocation group.
updated.
COLLOCGROUP command, the collocation group User response: None.
collocation group name has been updated in the server
database.
ANR4879I Command: number of nodes members
System action: Server operation continues. deleted from collocation group collocation
group name.
Explanation: A DELETE COLLOCMEMBER command
has deleted the specified number of members from the
indicated collocation group.
deleted.
COLLOCGROUP command, the collocation group User response: None.
collocation group name has been deleted from the server
database.
ANR4880I Node node name disassociated from
System action: Server operation continues. collocation group collocation group name.
User response: None. Explanation: This message is displayed in response to
the DELETE COLLOCMEMBER command. Node node
name is no longer associated with the collocation group
ANR4876W Command: Node node name cannot be
name collocation group name.
processed because it is not registered.
Explanation: This command cannot be processed for
the indicated node. The node is not registered. The User response: None.
other nodes can be processed if specified by the
command.
ANR4881E Command: Collocation group collocation
System action: The indicated node is not processed, group name is already defined.
but other nodes can be processed if specified by this
command.
command fails because the collocation group name
User response: If the node name was entered collocation group name specified refers to a collocation
incorrectly, issue the command again with the correct group that is already defined in the server database.
node name.
ANR4877E Command: Collocation group collocation command is not successful in changing the server
group name is not defined. database.
Explanation: Server processing for the command User response: Issue the command again, specifying a
command fails because the collocation group name collocation group name that is not defined in the server
collocation group name specified does not refer to a database. For a list of the names of defined collocation
defined collocation group in the server database. groups in the server database, issue the QUERY
COLLOCGROUP command.
database.

ANR4882E Command: Collocation group collocation ANR4886I Audit command (Scan) process started for
group name still contains at least one container container name (process ID
node. process ID).
Explanation: Server processing for the delete Explanation: As the result of an AUDIT CONTAINER
command command fails because the collocation group command that specified scan action for the container
collocation group name specified refers to a collocation shown, the process whose ID is displayed has begun
group that still contains at least one node. A collocation auditing the container.
group cannot be deleted if one or more client nodes are
System action: The container is audited and
still assigned to the collocation group.
inconsistent data is marked as damaged.
database. ANR4887I Audit command (Remove Damaged)
User response: To remove remaining nodes from the
name (process ID process ID).
collocation group, issue the DELETE
COLLOCMEMBER command. After all nodes are Explanation: As the result of an AUDIT CONTAINER
removed, issue the delete command again. command that specified delete action for the container
deleting data files depending on damaged data extents
ANR4883I Node node name associated to collocation
in the container.
group collocation group name.
System action: Data files associated with the damaged
data extents in the container are deleted.
the DEFINE COLLOCMEMBER command. Node node
name is associated with the collocation group name User response: None.
System action: Server operation continues. ANR4888I Audit command (Remove Damaged)
process started for storage pool directory
stgpooldir name (process ID process ID).
ANR4884W Node node name already associated to
command that specified delete action for the storage
pool directory shown, the process whose ID is
Explanation: This message is displayed in response to displayed has begun deleting data files depending on
the DEFINE COLLOCMEMBER command. Node node damaged data extents on the storage pool directory.
name is already associated with the collocation group
name collocation group name. The indicated node is not
data extents on the storage pool directory are deleted.
processed. The other nodes can be processed if
specified by the command. User response: None.
ANR4889I Audit command (Remove Damaged)
process started for storage pool stgpool
name (process ID process ID).
node name.
command that specified delete action for the storage
ANR4885E Command: Either node name or
pool shown, the process whose ID is displayed has
collocation group name must be
begun deleting data files dependent on damaged data
specified.
extents in the storage pool.
Explanation: The indicated command failed because
neither node name nor collocation group name is
data extents in the storage pool are deleted.
specified or the node name and the collocation group
name both are specified. User response: None.
System action: The indicated command fails. The
User response: Issue the command again, by
specifying either the node name or the collocation
group name.

STGPOOLDIRECTORY command is committed before

ANR4890W Audit container process terminated for
the UPDATE STGPOOLDIRECTORY command is
deleteion - process process ID canceled.
issued.
CONTAINER command for the container shown, the
ANR4894I Audit Container (Mark Damaged)
process performing the audit was canceled.
System action: The AUDIT CONTAINER command is name (process ID process ID).
ended.
User response: None. command that specified scan action for the container
auditing the container.
ANR4891I Audit command process process_id ended
for the container_name container: System action: The container is audited and
inspected_extents data extents inspected, inconsistent data is marked as damaged.
damaged_extents data extents marked as
damaged, undamaged_extents data extents
previously marked as damaged reset to
undamaged, and orphaned_extents data ANR4895E Deduplicated bitfile bitfile id on volume
extents marked as orphaned. volname has invalid links.
Explanation: The audit of the container generated the Explanation: While reading a deduplicated bitfile, the
following information: server detected invalid deduplication information.
v The number of data extents audited System action: If the operation is a server data
v The number of damaged data extents movement, the inconsistent bitfile is marked invalid
v The number of undamaged data extents that were and skipped, but the operation continues. If, however,
previously marked as damaged the operation is a client restore or retrieve, the bitfile is
marked as damaged.
v For cloud containers, the number of data extents that
were present on the cloud service provider but not User response: If the volume is in a primary storage
present in the server database; the audit marked pool, run a RESTORE VOLUME command to fix the
these extents as orphaned invalid bitfile. If the volume is in a copy storage pool,
run a DELETE VOLUME DISCARDDATA=YES
command to delete the volume, then backup the
User response: For directory containers, if you backed primary storage pool again.
up the storage pool data to a target storage pool server
To see what files may have been marked as damaged,
by using the PROTECT STGPOOL command, you can
use the QUERY CONTENT DAMAGED=YES
repair damaged extents in the directory-container
command.
storage pool by using the REPAIR STGPOOL
command. If you did not use the PROTECT STGPOOL
command to back up the storage pool data, you cannot ANR4896I Inventory client file expiration is
repair damaged extents in the directory-container restarting process process num from
storage pool. startdate.
To remove damaged extents from directory containers Explanation: The server is in the process of restarting
or cloud containers, and to remove orphaned extents a previously cancelled expiration process.
from cloud containers, issue the AUDIT CONTAINER
command and specify the System action: The server will continue expiring
ACTION=REMOVEDAMAGED parameter. eligible objects.
ANR4892E Command: Storage pool directory directory
is not defined in storage pool stgpool. ANR4897I Database restore of operation operation
Explanation: A nonexistent storage pool directory is ID will use device class device class name
specified for the issued command. and attempt to use number of streams
streams.
command. Explanation: The server restore database process for
the operation ID will be performed for the device class
User response: Reissue the command with a valid and number of streams indicated.
storage pool directory. If you are using the MACRO
command to define and update the storage pool System action: The server performs the database
directory, you must ensure that the DEFINE restore operation.

User response: None. is not supported for commercial or

production use.
ANR4898W This is a pre-release server_version IBM Explanation: An unsupported, pre-release version of
Spectrum Protect server (driver the IBM Spectrum Protect has been used with this
driver_number, build build_id). It is not database. The server can be used to test or evaluate
supported for commercial or production new features, but it can neither be used for any
use. commercial purpose nor placed into production.
Explanation: The IBM Spectrum Protect server is System action: No action is taken.
running a pre-release program. The program can be
User response: If the server is being used to evaluate
used to test or evaluate new features, but it can neither
new features, no action is required. If the server will be
be used for any commercial purpose nor placed into
used in a production environment or for a commercial
production.
purpose, remove the database. Create a new database
System action: No action is taken. using a fully-supported, released version.
User response: If the IBM Spectrum Protect server is
being used to evaluate new features, no action is ANR4902I Replication recovery of damaged files
required. If the server will be used in a production attribute set to value.
environment or for a commercial purpose, contact your
Explanation: The setting to control replication
IBM sales representative or authorized business partner
recovery of damaged files has been turned on or off as
to obtain a fully-supported, released version.
indicated with the SET REPLRECOVERDAMAGED
command.
ANR4899E The server database was formatted
System action: If setting the attribute to ON and there
using a pre-release server_version IBM
are damaged files, the server will evaluate the damaged
Spectrum Protect server (driver
file inventory. If no damaged files exist in the server
driver_number, build build_id). The server
inventory, and ON is specified, the attribute will cycle
is not supported for commercial or
to ON without having to evaluate damaged files. If the
production use.
setting specifies OFF, the server attribute cycles to OFF
Explanation: The server database was created using immediately.
an unsupported, pre-release version of the IBM
User response: If setting the attribute to ON and there
Spectrum Protect server. The server can be used to test
are damaged files, query the activity log for a process
or evaluate new features, but it can neither be used for
description of SET REPLRECOVERDAMAGED. If the
any commercial purpose nor placed into production.
process completes successfully the
System action: No action is taken. REPLRECOVERDAMAGED setting will be set ON. If
the process is canceled or completes unsuccessfully, the
User response: If the server is being used to evaluate
attribute remains unchanged.
new features, no action is required. If the server will be
used in a production environment or for a commercial
purpose, remove the database. Create a new database ANR4903I Replication recovery of damaged files
using a fully-supported, released version. for node(s) node list has been initiated
on target replication server recovery server
via process ProcId.
ANR4900W EMC Centera Software Development Kit
(SDK) libraries failed to load or are Explanation: The replication recovery process has
missing. started on the target replication server.
Explanation: The libraries are required to ensure that System action: A replication recovery process is
the IBM Spectrum Protect server can operate devices started on the target replication server.
with the defined CENTERA device class.
User response: Examine the results of replication
System action: None. recovery process on the target replication server.
User response: Ensure that the EMC Centera SDK is
installed on the system and that all libraries and ANR4904E command: Replication recovery of
associated links have the read permission. damaged files is disabled.
Explanation: Replication recovery operations
ANR4901E The server database has been used with originating from this server are disabled.
a pre-release server_version IBM
Spectrum Protect server (driver
driver_number, build build_id). The server User response: Use the SET
REPLRECOVERDAMAGED ON command to enable

the use of replication recovery of damaged files.

ANR4909I No files found for replication recovery
of damaged files.
ANR4905E command: Replication recovery of
Explanation: The replication recovery process has not
damaged files is not supported by target
started on the target replication server because no
server.
damaged files were found for the nodes specified on
Explanation: Replication recovery operations the REPLICATE NODE command.
originating from this server are not allowed because the
target replication server is downlevel.
User response: Upgrade the target replication server
ANR4910I A replication recovery preview was
to a level that supports replication recovery of
completed for the following nodes: node
damaged files.
list. Nodes to be recovered: nodes to
recover. Filespaces to be recovered:
ANR4906E Command: The "parameter" parameter is filespaces to recover. Files to be recovered:
not valid for a directory container files to recover. Bytes to be recovered:
storage pool. bytes to recover. Estimated run time:
estimated runtime.
Explanation: The command indicated specifies a
parameter that is not valid for a directory container Explanation: Information is provided about damaged
storage pool. data that can be recovered from a target replication
server:
command. v Nodes to be recovered indicates the number of nodes
that require recovery of damaged files.
User response: Reissue the command with parameters v Filespaces to be recovered indicates the number of
appropriate for a directory container storage pool. filespaces that require recovery of damaged files.
v Files to be recovered indicates the number of
ANR4907W The MAXRUNTIME parameter does not damaged files to be recovered.
cancel the scheduled command command. v Bytes to be recovered indicates the number of
Explanation: The administrative schedule that started damaged bytes to be recovered.
the command has a maximum run time. The maximum v Estimated run time is an estimate of how long the
run time is defined by the MAXRUNTIME parameter recovery process will run.
in the DEFINE or UPDATE SCHEDULE command. You
cannot use the MAXRUNTIME value to cancel the System action: None.
specified scheduled command. If the maximum run User response: No action is required. However, to
time is reached the MAXRUNTIME value is ignored recover damaged files from a target replication server,
and the scheduled command does not automatically you must issue the REPLICATE NODE command
cancel. again. To replicate the node and recover damaged files,
System action: The server operation continues. specify RECOVERDAMAGED=YES. To run the
command for the sole purpose of recovering damaged
User response: None. files, specify RECOVERDAMAGED=ONLY.
ANR4908E Replication recovery of damaged files ANR4911E File name is too long, the server is
not able to initiate a replication recovery unable to build a table of contents for
process on the target replication server. node node name, file space file space name,
Reason rc. file name file name, node identifier node
id, parent node identifier parent node id.
Explanation: The replication recovery process has not
Table of contents creation fails.
started on the target replication server.
Explanation: The file name must be 512 bytes or less.
If the size is larger than 512 bytes, the IBM Spectrum
User response: Examine the activity log for Protect server cannot create a table of contents (TOC)
communication errors. for a Network Appliance file server.
System action: The TOC creation fails.
User response: Rename the file with a shorter name.
For more information about the file name or the node
identifier, including locating and correcting the file or

directory, refer to Network Appliance documentation.

ANR4917I Point-in-time database restore with
Once the problem has been corrected, try the operation snapshot complete, restore date date time.
again.
Explanation: A point-in-time database restore with the
TODATE parameter specified has completed. The
ANR4912I Database restore type byte count. database is committed to the point in time of this
backup, which may be different than the TODATE
Explanation: A database restore is in progress. specified. If this is the case, an additional message will
System action: None. be displayed.
User response: None. System action: None.

not valid for a cloud container storage ANR4918W The filespace filespace name (filespace id)
pool. for node node name will not be included
Explanation: The command indicated specifies a in the backupset backupset name (data
parameter that is not valid for a cloud container type data type) because it was not created
storage pool. by the backup/archive client and cannot
be restored from the backupset.
command. Explanation: Data from the filespace will not be
included in the backupset because the filespace was not
User response: Reissue the command with parameters created by the backup/archive client and it cannot be
appropriate for a cloud container storage pool. restored from the backupset.
not valid for a cloud container storage User response: None.
pool.
Explanation: The command indicated specifies a ANR4919W The filespace filespace name (filespace id)
parameter that is not valid for a cloud container for node node name will not be included
storage pool. in the backupset backupset name (data
type data type) because it is not a
System action: The server does not process the supported application type.
command.
Explanation: Data from the filespace will not be
User response: Reissue the command with parameters included in the backupset because the filespace does
appropriate for a cloud container storage pool. not belong to a supported application type.
ANR4915I Audit command process started (process
ID process ID). User response: None.

command the process whose ID is displayed has begun ANR4920E Command: Administrator administrator
auditing the containers. name is not authorized to issue this
command for storage pool pool name.
System action: Container audit processes are started.
User response: None. the indicated command, but this administrator does not
have the proper authority necessary to run the
ANR4916I Starting point-in-time database restore command for the indicated pool. The indicated pool
snapshot to date date time. could be the storage pool being migrated or being
reclaimed, or the storage pool to which files are
Explanation: A point-in-time database restore with the migrated or reclaimed.
TODATE parameter and source snapshot specified has
begun. When this restore is complete, the database will System action: The server does not process the
be committed to the point in time of this backup. command.
System action: None. User response: Issue the command from a properly
authorized administrator ID, or contact the system
User response: None. administrator to have additional authority granted to
the current administrator ID.

ANR4921E Command: Primary storage pool pool name ANR4926W Migration terminated for volume volume
does not have a target pool. name - duration exceeded.
Explanation: The specified primary storage pool does Explanation: During migration for the indicated
not have a target storage pool for the specified volume, the duration for the migration has been
operation. exceeded.
System action: The server does not process the System action: The volume migration is terminated.
command.
User response: Define a target storage pool for the
pool specified on the command and re-issue the
ANR4927W Reclamation terminated for volume
command.
volume name - duration exceeded.
Explanation: During reclamation for the indicated
ANR4922E Command: Migration is currently
volume, the duration for the reclamation has been
running for the storage pool pool name.
exceeded.
Explanation: The migration operation is already
System action: The volume reclamation is terminated.
running for the specified storage pool.
command.
ANR4929E Command: The storage pool pool name is
User response: Re-issue the command when migration
not a sequential-access pool.
is not running.
Explanation: The specified storage pool is not a
sequential-access storage media for the specified
ANR4923E Command: Reclamation is currently
operation. The specified operation only applies to a
running for the storage pool pool name.
sequential-access storage media.
Explanation: The reclamation operation is already
running for the specified storage pool.
command.
User response: Re-issue the command for a
command.
sequential-access storage media.
User response: Re-issue the command when
reclamation is not running.
ANR4930I Reclamation process process ID started
for primary storage pool storage pool
ANR4924I Command: Migration is not needed for name automatically or manually,
the storage pool pool name. threshold=threshold value,
duration=duration.
Explanation: Either the current percentage utilization
of the specified storage pool is less than the low Explanation: Because the high reclamation threshold
migration threshold or the number of volumes for the storage pool shown has been exceeded, a
containing data has not reached the low migration process has been started to reclaim files from the
threshold. storage pool. Note: a duration value of None means
that the duration is not specified and hence the
reclamation runs without duration.
command.
System action: Data is moved from this storage pool
User response: Re-issue the command when migration
to the same pool or to the reclaim storage pool.
is needed for the pool.
for storage pool storage pool name - ANR4931I Reclamation process process ID started
duration exceeded. for copy storage pool storage pool name
automatically or manually,
threshold=threshold value,
storage pool, a process performing the migration has
offsiteRclmLimit=limit value,
been terminated because the migration duration has
duration=duration.
exceeded.
Explanation: Because the high reclamation threshold
System action: The migration process is terminated.
for the storage pool shown has been exceeded, a
User response: None. process has been started to reclaim files from the

storage pool. Note: a duration value of None means

ANR4936I The reclamation of the pool name storage
that the duration is not specified and hence the
pool is complete. Number of files
reclamation runs without duration.
reclaimed: number of reclaimed files.
System action: Data is moved from this storage pool Number of reclaimed bytes: number of
to the same pool or to the reclaim storage pool. reclaimed bytes. Number of reclaimed
deduplicated bytes: number of reclaimed
User response: None. dedup bytes. Number of reconstructed
files: number of reconstructed files. Number
ANR4932I Reclamation process process ID ended for of unreadable files: number of unreadable
storage pool storage pool name. files.
Explanation: A reclamation process for the named Explanation: Reclamation processing for the specified
storage pool ends. This action can occur because the storage pool ended with the displayed results.
threshold for the storage pool has been reached or System action: None.
because the duration has been exceeded.
System action: None. determine whether all reclamation processes ended
User response: None. successfully.
ANR4933I Space reclamation ended for offsite ANR4937E Command: Reclamation will not run -
volume volume name. delete filespace is currently running.
Explanation: Space reclamation for the named offsite Explanation: A delete filespace operation is running.
volume is complete. To Avoid the resource contention, reclamation will not
run when delete filespace is running.
User response: Re-issue the command when delete
ANR4934I Offsite reclamation ended for storage filespace is not running.
pool pool name, Number Processes
number of processes, Number Volumes
Reclaimed number of volume reclaimed, ANR4938E Command: Administrator administrator
Elapsed Time seconds seconds. name is not authorized to issue this
command for target storage pool pool
Explanation: Offsite reclamation ended successfully. name.
System action: None. Explanation: The specified administrator has entered
User response: None. the indicated command, but this administrator does not
have the proper authority necessary to run the
command for the indicated pool. The indicated pool is
ANR4935I The migration of the primary pool name the pool that to which files are migrated or reclaimed.
primary storage pool is complete.
Number of files migrated: number of System action: The server does not process the
migrated files. Number of bytes migrated: command.
number of migrated bytes. Number of User response: Issue the command from a properly
deduplicated migrated bytes: number of authorized administrator ID, or contact the system
migrated dedup bytes. Number of administrator to have additional authority granted to
unreadable files: number of unreadable the current administrator ID.
files.
Explanation: Migration processing for the specified ANR4939E Command: The "option" option is not
storage pool ended with the displayed results. valid for a DISK storage pool.
System action: None. Explanation: The command indicated specifies an
User response: Examine previous messages to option that is not valid for a DISK storage pool.
determine whether all migration processes ended System action: The server does not process the
successfully. command.
User response: Reissue the command with options
appropriate for a DISK storage pool.

System action: The volume definition fails.

ANR4940E Container container name is locked by
another operation and cannot be User response: Use the FORMATSIZE parameter to
modified. have the server pre-allocate space for the new volume.
Explanation: While attempting to modify the specified
container, the IBM Spectrum Protect was unable to ANR4943E Command: Volumes cannot be deleted
obtain the locks necessary to change it. from
RECLAMATIONTYPE=SNAPLOCK
System action: The operation fails. Server operation
storage pools.
continues.
Explanation: Deleting volumes from
User response: Wait for conflicting processes and
RECLAMATIONTYPE=SNAPLOCK storage pools is
sessions are reduced, and re-issue the command.
not allowed. Rather, deletion of empty volumes occurs
automatically during reclamation processing.
ANR4941E The server is unable to translate the
Unicode name while building table of
contents for node node name, file space User response: Allow deletion of empty volumes to
file space name, Unicode name unicode be done automatically during reclamation processing.
name node identifier node id, parent node
identifier parent node id. Table of
contents creation fails. ANR4944E Command: Volumes cannot be defined in
RECLAMATIONTYPE=SNAPLOCK
Explanation: While creating a table of contents (TOC) storage pools.
for a Network Appliance file server, the IBM Spectrum
Protect server attempted to translate the Unicode name Explanation: Defining volumes on
in the file history message from UCS-2 to UTF-8. The RECLAMATIONTYPE=SNAPLOCK storage pools is
translation failed. not allowed. Rather, the MAXSCRATCH parameter on
the DEFINE and UPDATE STGPOOL commands is
System action: The TOC creation fails. used to make storage pool space available for these
storage pools.
User response: Verify that the required support for
translations between UCS-2 and UTF-8 is properly System action: The operation fails.
installed and configured on the system where the IBM
Spectrum Protect is running. User response: Use the MAXSCRATCH parameter on
the DEFINE and UPDATE STGPOOL commands to
Verify that the reported Unicode name is valid. Note create space in the storage pool.
that the Unicode name is encoded in little-endian
UCS-2 and is reported in hexadecimal notation. If the
Unicode name is not valid, the problem may usually be ANR4945E Command:Error creating volume volume
corrected by deleting or renaming the corresponding name: FORMATSIZE exceeded the
file or directory on the Network Appliance file server. maximum size allowed.
The node identifier and parent node identifier are Explanation: When you define a volume, the server
provided by the Network Appliance NDMP server. detects whether the format size of the volume exceeds
Their values are NDMP-server implementation the maximum size allowed.
dependent but will typically be the inode number of
the file or directory. For more information about the System action: The operation fails.
Unicode name or the node identifiers, including using User response: Reissue the DEFINE VOLUME
them to locate and correct the invalid file or directory, command and specify the FORMATSIZE parameter
contact Network Appliance for support. with a value of 8388607 MB or less.
If possible, configure the Network Appliance file server
to always encode file and directory names as UTF-8. ANR4946W The character encoding of NDMP file
Once the problem has been corrected, try the operation history messages for node node name, file
again. system file system name is unknown. The
IBM Spectrum Protect server will use
the UTF-8 encoding to build a table of
ANR4942E Command: Volume volume name is not contents.
defined. The file name does not exist or
has no space. Explanation: While initializing a backup with a table
of contents (TOC) for the specified node and file
Explanation: A define volume command was issued system, the IBM Spectrum Protect server determines
for the indicated volume name. The volume name was that the character encoding of file history information
specified without the FORMATSIZE parameter, but it from the NAS file server is unknown. The IBM
either does not exist or exists as a file of size 0. Spectrum Protect server will assume file history

information is encoded as UTF-8 in order to build a Explanation: While creating a table of contents (TOC),
TOC. the server attempted to retrieve information contained
in a previous NDMP file history message. The
If the character encoding is not UTF-8 and non-English
information was not found. This could be caused by a
characters are present, the names will be improperly
problem with the NAS file server that is sending file
displayed and probably unreadable, making recovery
history messages. The NDMP node ID reported in the
difficult.
message is the node ID referenced in the current
System action: The operation continues. NDMP file history message.
User response: Verify that the encoding of file history System action: The TOC creation fails.
information is UTF-8. For Network Appliance NAS file
User response: Verify that the NDMP server is
servers, verify that the volume language for the
properly sending file history information. Otherwise,
specified node and file space is UTF-8, or a subset of
UTF-8 (for example 7-bit ASCII).
ANR4951E The writing of a table of contents for

ANR4947E Container container name is locked by
another operation and cannot be moved.
failed. The object is excluded from
Explanation: While attempting to move the specified storage pool pool name and all successor
container, the IBM Spectrum Protect was unable to pools because of its size.
obtain the locks necessary to move it.
System action: The operation fails. Server operation (TOC) creation for the specified node. The size of the
continues. TOC is larger than that allowed in the storage pool
specified by the TOC destination attribute of the
User response: Wait for conflicting processes and assigned management class backup copy group. No
sessions are reduced, and re-issue the command. successor storage pools to the one specified on the copy
group can accept the large TOC.
ANR4948E The list file named list file name contains System action: The TOC creation is ended and server
more than max entry count entries. operation continues.
Explanation: While reading a list file, the server User response: Increase the maximum file size for one
detects that the number of entries exceeds the or more of the storage pools in the storage hierarchy to
maximum allowed. accommodate the TOC. An authorized administrator
System action: The operation fails. can increase the MAXSIZE parameter by issuing the
UPDATE STGPOOL command.
User response: Consider breaking up the operation
into multiple commands, each handling a subset of the
required entries. ANR4952E The writing of a table of contents for
failed. No space is available in storage
ANR4949E The server is unable to write to table pool pool name and all successor pools.
table name because there is not enough
temporary space in the database. Table Explanation: The server ends a table of contents
of contents operation for node node (TOC) creation for the specified node. The storage pool
name, file space file space name fails. specified by the TOC destination attribute of the
backup copy group in the assigned management class
Explanation: While operating on a table of contents does not contain enough free space to hold the TOC.
(TOC), the server attempted to insert data into the No successor storage pools to the one specified on the
specified temporary database table, but there is not copy group contain enough free space.
enough temporary space in the server's database.
System action: The TOC creation is ended and server
System action: The TOC operation fails. operation continues.
User response: Ensure that sufficient temporary space User response: An authorized administrator can issue
is available in the server's database. the DEFINE VOLUME command to add storage to one
or more storage pools in the storage hierarchy. This
ANR4950E The server is unable to retrieve NDMP action may also involve creating storage space by using
file history information while building an operating system-specific utility.
table of contents for node node name, file
space file space name. NDMP node ID is
NDMP node ID. Table of contents
creation fails.

(TOC) creation for the specified node because sufficient

log space is not available on the server.
failed. The server encountered an error System action: The TOC creation is ended and server
when writing to the storage device. operation continues.
Explanation: The server ends a table of contents User response: To increase the amount of log space
(TOC) creation for the specified node because an I/O that is available to the server, evaluate the directories
error has been encountered by the server in writing to and file systems that are assigned to the
a device. ACTIVELOGDIRECTORY, ARCHIVELOGDIRECTORY,
User response: Query the activity log to find messages full.
preceding this one that specify the failing device.
Storage pool volumes can be varied offline (by using
the VARY command), or the server may need to be
halted to correct the hardware problem. After the
problem is corrected, try the operation again.
ANR4954E The writing of a table of contents for ARCHIVELOGDIRECTORY or
node node name, file space file space name ARCHFAILOVERLOGDIRECTORY options in the
failed. The data transfer was dsmserv.opt file and then restart the server.
interrupted.
Explanation: The server ends a table of contents ANR4957E The writing of a table of contents for
(TOC) creation for the specified node because data node node name, file space file space name
transfer to or from data storage was interrupted by an failed. The server does not have
external event. sufficient database space.
System action: The TOC creation is ended and server Explanation: The server ends a table of contents
operation continues. (TOC) creation for the specified node because sufficient
this message to determine why the data transfer was System action: The TOC creation is ended and server
interrupted. Attempt the operation again if the problem operation continues.
can be resolved.
ANR4955E The writing of a table of contents for DBSPACE command to add one or more directories to
node node name, file space file space name the database.
failed. The storage media is not
available.
Explanation: The server ends a table of contents node node name, file space file space name
(TOC) creation for the specified node because storage failed. The server is unable to start a
volumes are not available in the storage pools in which new thread.
the TOC is to be stored.
System action: The TOC creation is ended and server (TOC) creation for the specified node because sufficient
operation continues. memory is not available for starting additional
processes on the server.
User response: An authorized administrator can issue
the DEFINE VOLUME command to add storage to one System action: The TOC creation is ended and server
or more storage pools in the storage hierarchy. The operation continues.
VARY ONLINE command can be used to vary offline
make them available for TOC storage.
application.

failed. The server does not have
sufficient recovery log space.


failed. The server does not have User response: If necessary, make more mount points
sufficient memory. available.
(TOC) creation for the specified node because sufficient ANR4963E The writing of a table of contents for
memory is not available on the server. node node name, file space file space name
failed. See previous messages.
operation continues. Explanation: The server ends a table of contents
(TOC) creation for the specified node because a
previous error has occurred.
application. System action: The TOC creation is ended and server
ANR4960E The writing of a table of contents for User response: Examine the server messages issued
node node name, file space file space name prior to this message to determine the source of the
failed. The server detected an internal error. Issue the QUERY ACTLOG command to view the
error. activity log and search for messages. If the error cannot
representative.
(TOC) creation for the specified node because an
internal logic error is detected.
ANR4964I Space reclamation deleted number of
volumes WORM FILE volumes for
Explanation: During reclamation for the indicated
storage pool, the server deleted the indicated number
of empty WORM FILE volumes that have exceeded
their retention date.
representative. System action: Reclamation and server operations
continue.
ANR4961E The writing of a table of contents for User response: None.
failed. The server could not commit the
transaction. ANR4965E operation is ended for storage pool storage
pool name. Sufficient database space is
Explanation: An error was detected during transaction not available.
messages that give additional information about the Explanation: Insufficient server database space has
failed transaction. been encountered during the indicated operation for
the indicated storage pool.
System action: The table of contents (TOC) creation is
ended and server operation continues. System action: Either the Migration or Reclamation
stops, or the operation specified in the message stops.
eliminate the condition that caused the failed User response: To increase the amount of database
transaction. If the error cannot be isolated and resolved, space that is available to the server, issue the EXTEND
contact your service representative. DBSPACE command to add one or more directories to
the database.

node node name, file space file space name ANR4966E operation is ended for storage pool storage
failed. The server does not have pool name; sufficient recovery log space
sufficient mount points available to is not available.
satisfy the request. Explanation: Insufficient server recovery log space has
Explanation: The server was unable to allocate been encountered during the indicated operation for
sufficient mount points to write the table of contents the indicated storage pool.
(TOC). System action: Either the Migration or Reclamation
stops, or the operation specified in the message stops.

User response: To increase the amount of log space output to appear on the web interface or interfaces that
that is available to the server, evaluate the directories use the administrative API. Consult the language
and file systems that are assigned to the support information of the operating system for
ACTIVELOGDIRECTORY, ARCHIVELOGDIRECTORY, information on how to install UTF-8 code page,
and ARCHFAILOVERLOGDIRECTORY options in the conversion tool support, and ICONV support.
System action: The server operation continues without
converting the command output from the server's code
full.
page to UTF-8.
User response: Install the UTF-8 code page support on
the operating system. This is normally available by
installing the UTF-8 locale for your language.
necessary, specify a larger directory for the ANR4970E Audit command: Missing or incorrect
ARCHIVELOGDIRECTORY or reclamation retention date for WORM
ARCHFAILOVERLOGDIRECTORY options in the FILE volume volume name; run AUDIT
dsmserv.opt file and then restart the server. VOLUME FIX=YES for correction.
Explanation: The indicated audit process finds a
ANR4967W Expired WORM FILE volume volume WORM FILE storage volume for which the reclamation
name still contains valid data; data will retention date is missing or incorrect. To fix the missing
not be protected. or incorrect date, issue the AUDIT VOLUME with
FIX=YES command for the indicated volume. During
Explanation: During space reclamation, the server
AUDIT VOLUME processing, the server will indeed
detected the retention of the indicated WORM FILE
have interface to the Network Appliance filer to obtain
volume has expired but the volume still contains valid
the retention date of the SnapLock Log Volume for
data. The data on the volume will not be protected.
correction of the missing or incorrect date.
System action: Reclamation continues.
User response: Examine the server activity logs to
User response: Issue the AUDIT VOLUME command
find out why the reclamation does not move the valid
with FIX=YES, so that the reclamation retention date
data to another WORM FILE volume for protection.
can be created or corrected.
ANR4968W Reclamation failed on WORM FILE

ANR4971E Audit command: Missing or incorrect
volume volume name.
reclamation retention date for WORM
Explanation: During space reclamation, server failed FILE volume volume name. The
to move the files from the indicated WORM FILE reclamation retention date will be
volume. The files on the volume might not be protected created or corrected.
if the reclamation period is exceeded.
Explanation: The indicated audit process finds a
System action: Reclamation continues on other WORM FILE storage volume for which the reclamation
volumes. retention date is missing or incorrect. Since FIX=YES
has been specified for the audit command, the date will
User response: Examine the server activity logs to
be created or corrected.
find out why the reclamation does not move the valid
data to another WORM FILE volume for protection. To System action: Audit processing continues.
determine when the reclamation period is expired,
issue a QUERY VOLUME command for the indicated
volume.
ANR4972I Command: Migration is not needed for
the storage pool pool name.
ANR4969W Conversion from the server code page to
UTF-8 fails. Verify the installation of the Explanation: Migration is not needed for the specified
UTF-8 code page and tools for your storage pool because of one of the following reasons:
operating system. v The high migration threshold (percentage) is set to
Explanation: Converting the command results from 100 to prevent migration.
the server's code page to UTF-8 fails. Problems with v If the specified storage pool uses random-access disk
operating system conversion tool or missing code page or sequential-access disk, the data capacity utilization
conversion tool might cause this problem. The server is less than the low migration threshold.
will attempt to recover from the situation. However, the v If the specified storage pool uses tape or optical
recovery might result in unreadable characters or no media, the ratio of volumes that contain data to the

total number of volumes in the storage pool is less

ANR4976W The device class DevClassName is not the
than the low migration threshold.
same as device class DevClassName
System action: The server does not process the defined for the serverbackup node
command. $$_TSMDBMGR_$$.
User response: Re-issue the command when migration Explanation: The device class in this command is not
is needed for the pool. the same as the device class defined in the server
backup node.
ANR4973I Command: Reclamation is not allowed System action: The server will still process the
for the storage pool pool name. command.
Explanation: The high reclamation threshold User response:

(percentage) is set to 100 to prevent reclamation for the
specified storage pool.
ANR4977E Container container name was not found
System action: The server does not process the in any storage pool.
command.
Explanation: The container specified does not exist in
User response: Re-issue the command when migration any storage pool.
is needed for the pool.
ANR4974W The writing of a table of contents for
User response: Re-issue the command with a valid
container name.
was cancelled.
ANR4978E Container container name could not be
(TOC) creation for the specified node because the
opened.
process was cancelled.
Explanation: The container specified does not exist in
the file system and could not be opened.
User response: Re-issue the command with a valid
ANR4975E No Tcp port available for backup from
container name.
NAS node to server.
Explanation: The server was unable to set up a
ANR4979W Use of environment variable
TCP/IP port for use in backing up or restoring from or
DSMSERV_DIR is no longer supported.
to NAS nodes and the server. The server uses a range
of ports as defined by the NDMPPORTRANGE option. Explanation: The DSMSERV_DIR environment
If none of these ports can be set up for use, backups or variable was required in prior versions of IBM
restores from or to NAS nodes and server native Spectrum Protect to find loadable modules and
storage pools will fail. If the NDMPPORTRANGE language files. Now, however, the directory is
option is not specified, the server uses ephemeral ports determined automatically and this variable is ignored.
( ports that the operating system assigns from a
System action: Server operation continues, using the
dynamic pool ). If the system runs out of usable ports,
directory containing the server executable as the base
operations to or from NAS nodes and server native
server directory.
storage pools will fail.
System action: The specific operation is ended and
ANR4980I The protect storage pool process for
User response: Operating specific utilities, e.g. netstat,
stgpool name on server this server to
may be used to examine ports which are in use. It may
be necessary to specify the NDMPPORTRANGE option
complete. Extents protected: extents
( which requires a server restart ), to provide a
protected of extents to protect. Extents
sufficient number of ports.
failed to protect: extents failed to protect.
Extents deleted: extents deleted of extents
to delete. Amount protected: amount
protected of amount to protect. Amount
failed: amount transferred. Amount

transferred: amount transferred. Elapsed amount failed. Amount skipped: amount

time: elapsed time. skipped. Elapsed time: elapsed time.
Explanation: The protect storage pool process is Explanation: The storage pool repair process is
complete. The following list describes the information complete. The following list describes the information
in the message: in the message:
v Extents protected: Extents that were successfully v Extents repaired: indicates the number of extents that
protected by being linked to matching extents on the were successfully repaired.
target server. v Extents failed: indicates the number of extents that
v Extents failed to protect: Extents that were not failed to be repaired.
successfully protected during the process of v Extents skipped: indicates the number of extents that
protecting to the target server. were skipped.
v Extents deleted: Extents that were successfully v Amount repaired: indicates the number of bytes that
deleted from the target server because the extent did were successfully repaired.
not exist on the source server or because it was
v Amount failed: indicates the number of bytes that
damaged on the target server and needed to be
failed to be repaired.
resent.
v Amount skipped: indicates the number of bytes that
were skipped.
protected by being linked to matching extents on the
target server. v Elapsed time: indicates how long the process ran.
v Amount failed: Bytes that were not protected. See
previous messages for further details. ANR4983I The preview of repair storage pool
v Amount transferred: Bytes that were sent to the stgpool name on server this server from
target server during this process. The amount that stgpool name on server other server is
was transferred can be less than the amount that is complete. Extents to be repaired: extents
protected when the target server already has some of repaired. Amount to be repaired: amount
the extents or when compression is enabled. repaired.
v Elapsed time: How long the process ran. Explanation: The storage pool repair process is
complete in preview mode. The following list describes
the information in the message:
ANR4981I The preview of protect storage pool
stgpool name on server this server to v Extents to be repaired: indicates the number of
stgpool name on server other server is extents to be repaired.
complete. Extents to be protected: extents v Amount to be repaired: indicates the number of
to protect. Extents to be deleted: extents bytes to be repaired.
deleted. Amount to be protected: amount
protected.
ANR4984E Container container name was not found
Explanation: The storage pool protection preview is in storage pool stgpool name.
in the message: Explanation: The container specified does not exist in
the indicated storage pool.
v Extents to be protected: Extents that need to be
protected by being linked to matching extents on the System action: The command fails and server
target server. operation continues.
v Extents to be deleted: Extents that need to be deleted User response: Re-issue the command with a valid
because the extent does not exist on the source container name.
server.
v Amount to be protected: Bytes that need to be
ANR4985W This command will delete data files
protected by being linked to matching extents on the
associated with damaged data extents in
target server.
storage pool stgpool name.
Explanation: The execution of an AUDIT
ANR4982I The repair storage pool process for
CONTAINER command will remove data files that are
dependent on data extents stored in damaged
containers.
complete. Extents repaired: extents
repaired of extents to repair. Extents failed: System action: The administrator is asked whether to
extents failed. Extents skipped: extents continue.
skipped. Amount repaired: amount repaired
User response: Enter 'Y' to audit containers or 'N' to
of amount to repair. Amount failed:
stop the process.

ANR4992W Audit command has encountered an I/O ANR6200I Command name: Level compression audit
error for container container name in level compression audit started as
container storage pool storage pool while process process ID.
attempting to read a data extent.
Explanation: A compression audit at the specified
Explanation: The AUDIT CONTAINER process level has been started as a background server process
encountered an I/O error for the specified container with the process identifier reported.
while attempting to read a data extent. The data extent
is going to be marked as damaged.
background audit attempts to identify client files that
System action: None. may be affected by the client compression problem.
User response: Identify and resolve the I/O error for User response: None.
the container if possible. Verify that the container's
physical device is functioning properly and that the
ANR6201I Command name: Level compression audit
container is usable.
level compression audit starting as
background process process ID.
ANR4993W Audit container process terminated for
Explanation: A compression audit at the specified
container container name - process
level was started as a background server process
canceled.
having the process identifier reported.
CONTAINER command for the container shown, the
background audit attempts to identify client files that
process performing the audit was cancelled.
may be affected by the client compression problem.
System action: The AUDIT CONTAINER command is
ended.
ANR6202I Command name: Verifying candidates
from last audit.
ANR4994E Query whether the volume volume name
Explanation: A compression audit has started to verify
is in the library library name failed.
the client file candidates that were identified in a
Explanation: An attempt to query if the indicated previous compression audit execution. The verification
volume is in the specified library failed. It could be the process eliminates compression candidates that are now
library is offline or the library manager is down in a found to be expired by policy on the server.
library sharing environment.
System action: The audit operation continues.
System action: The requested operation failed.
User response: Re-attempt the request when the
library is brought up or when the library manager is
ANR6203I Command name: Starting level audit level
up and running in a library sharing environment.
compression audit from qualifying
entries in the candidates list.
ANR5001I Update Stgpooldir command
Explanation: A compression audit is starting to check
(Access=Destroyed) process started for
qualifying candidates from the candidates list for the
stgpooldir stgpooldir name (process ID
audit level specified. Client files that were identified as
process ID).
compression candidates at a lower level will be tested,
Explanation: As the result of an UPDATE subject to the qualifications that were specified for the
STGPOOLDIR command that specified command.
access=destroyed for the stgpooldir shown, the process
whose ID is displayed has begun updating the
stgpooldir. User response: The compression candidate list can be
displayed with the QUERY COMPRESSION command.
System action: The access of the stgpooldir is set to
The QUERY PROCESS command can be used to
destroyed
monitor the progress of the audit operation.

User response: The compression candidate list can be

ANR6204I Command name: Process process ID, level
audit level audit, ended successfully -
compression suspects = total number of
compression suspects.
Explanation: A compression audit ended and is
ANR6208I Command name: Process process ID, was
reporting the total number of suspect client files that
cancelled - number of candidate files
have been found.
candidate files were found in number of
System action: The audit operation completes. files examined files examined prior to
cancellation.
displayed with the QUERY COMPRESSION command. Explanation: A compression audit operation was
canceled with the CANCEL PROCESS command before
completion. The number of candidate files that were
ANR6205I Command name: Process process ID,
found prior to the cancellation are displayed.
continuing Level 1 compression audit
with object object ID high order System action: The audit operation ends.
number.object ID low order number.
User response: The compression audit may be
Explanation: A level 1 compression audit is starting to restarted with the AUDIT COMPRESSION command.
evaluate client files for signs that they may be affected The compression candidate list can be displayed with
by the client compression problem. Since a previous the QUERY COMPRESSION command.
level 1 audit has been executed, this audit will continue
where the last audit stopped starting with the object
whose identifier is specified.
audit level audit completed successfully -
System action: The audit operation continues. number of candidate files candidate files
were found in number of files examined
files examined.
The QUERY PROCESS command can be used to Explanation: A compression audit operation
monitor the progress of the audit operation. completed successfully. The number of candidate files
that were found are displayed.
ANR6206I Command name: Process process ID, System action: The audit operation ends.
starting base level 1 compression audit.
Explanation: A level 1 compression audit is starting to displayed with the QUERY COMPRESSION command.
evaluate client files for signs that they may be affected
by the client compression problem. The audit starts
with the first client file found on the server, even if
audit level audit completed successfully -
previous level 1 audits have been executed.
number of candidate files candidate files
System action: The audit operation continues were found.
User response: The compression candidate list can be Explanation: A compression audit operation
displayed with the QUERY COMPRESSION command. completed successfully. The number of candidate files
The QUERY PROCESS command can be used to that have been found are displayed.
System action: The audit operation ends.
audit level analysis detected candidate
file high-level object name low-level object
name in file space client filespace name for ANR6211I Command name: Process process ID, level
node client node name. audit level analysis detected candidate
file object name in file space client filespace
Explanation: A compression audit has found a
name for node client node name.
candidate file at the audit level specified. The name of
the client node, file space, and file are displayed. This Explanation: A compression audit has found a
message is issued whenever a candidate file is detected candidate file at the audit level specified. The name of
during a compression audit that was started with the the client node, file space, and file are displayed. This
VERBOSE=YES parameter specified. message is issued whenever a candidate file is detected
during a compression audit that was started with the
VERBOSE=YES parameter specified.

System action: The audit operation continues. that were promoted as candidates at this level of audit,
eliminated as candidates at this level of audit, and
found to be expired are reported.
The QUERY PROCESS command can be used to System action: The audit operation ends.
audit level analysis eliminated level
ANR6215I Command name: Backup for file high-level
candidate level candidate file object name
object name low-level object name in
in filespace client filespace name for node
filespace client filespace name for node
client node name from candidate status.
client node name could not be forced.
Explanation: A compression audit at the level
Explanation: It is not possible to force a backup for
specified has eliminated a candidate file through
the specified file using the FORCE BACKUP command.
further analysis. The name of the client node, file space,
This file was either backed up using an API client or by
and file are displayed. This message is issued whenever
an ADSM version 2 client or higher.
a candidate file is eliminated from consideration during
a compression audit that was started with the System action: The force backup operation continues,
VERBOSE=YES parameter specified. the state of the compression record for this file is
updated.
User response: If the file was backed up using a
Version 2 client, or higher, you may remove this entry
as a candidate, using the REMOVE COMPRESSION
command. If the file was backed up using an API
client, notify the client owner to again back this file up.
Do not remove this entry until it becomes an "inactive"
ANR6213I Command name: Process process ID, was entry.
cancelled - number of files promoted
candidate files were promoted as
ANR6220I Delete compression operation started as
candidates at level audit level, number of
process process ID.
files eliminated files were eliminated as
candidates, and number of files expired Explanation: A compression deletion operation was
candidates were eliminated because they started as a background server process with the
were found to be expired on the server. indicated identifier.
Explanation: A compression audit operation was System action: Server operation continues.
cancelled with the CANCEL PROCESS command
before completion. The number of candidate files that User response: None.
were promoted as candidates at this level of audit,
eliminated as candidates at this level of audit, and ANR6221I Force backup operation started as
found to be expired before the cancellation are process process ID.
reported.
Explanation: A force backup operation was started as
System action: The audit operation ends. a background server process with the indicated
User response: The compression audit can be restarted identifier.
with the AUDIT COMPRESSION command. The System action: Server operation continues.
compression candidate list can be displayed with the
QUERY COMPRESSION command. User response: None.
ANR6214I Command name: Process process ID, ANR6222I Command name: Process process ID was
completed successfully - number of files cancelled - number of files files were
promoted candidate files were promoted processed prior to cancellation.
as candidates at level audit level, number Explanation: The indicated process was cancelled
of files eliminated files were eliminated as prior to completion. This message displays the
candidates, and number of files expired indicated number of files that were processed before
candidates were eliminated because they the operation was cancelled.
were found to be expired on the server.
System action: The process ends.
Explanation: A compression audit operation
completed successfully. The number of candidate files User response: The operation may be restarted by

reissuing the indicated command. System action: Server operation continues.

User response: The CANCEL PROCESS command can
ANR6223I Delete compression process process ID be used to cancel the compression cleanup operation.
has completed - number of files files were The QUERY PROCESS command may be used to query
deleted. the status of the operation.
Explanation: The indicated process has completed
processing. All database references have been deleted ANR6228W Cleanup process name: Process process ID
for the indicated number of files. has been cancelled - cleanup processing
is incomplete.
Explanation: A compression cleanup operation has
been cancelled prior to successful completion.
ANR6224I Force backup process process ID has
completed - number of files files were User response: The CLEANUP COMPRESSION
marked for forced backup. command can be used to restart the cleanup operation.
Explanation: The indicated process has completed
processing. The indicated number of files have been ANR6229I Cleanup process name: Process process ID
marked for forced backup. These files will be backed completed successfully.
up during the next incremental backup.
System action: The process ends. successfully completed.
User response: None. System action: The cleanup process ends.
ANR6225I File identifier removed as a suspect for
compression errors.
ANR6300E Command name: Insufficient server
Explanation: The file with the specified identifier has memory available for the operation.
been removed from the database information
Explanation: A compression testing routine cannot
concerning files with possible compression errors.
continue because sufficient memory is not available on
Other database information concerning the file is not
the server.
affected.
User response: Increase the memory available to the
server by increasing the server region size, virtual
machine size, paging space available on the system, or
ANR6226I Command name: Started as background relocating the memory swap file, depending upon the
process process ID. platform on which the server is executing. Additional
memory may also be made available by limiting server
activity (sessions, migration, and other activities) while
been started to remove compression candidate
this operation is processing.
information and temporary database entries from the
server database. Client files are not affected by this
operation. ANR6301E Command name: Invalid LEVEL specified.
This command only supports a value of
1 or 2 for the LEVEL parameter.
User response: The CANCEL PROCESS command can
Explanation: An invalid LEVEL= parameter has been
be used to cancel the compression cleanup operation.
specified for the command.
The QUERY PROCESS command may be used to query
the status of the operation. System action: The command fails.
ANR6227I cleanup process name operation starting as value of 1 or 2 for the LEVEL parameter.
process process ID.
Explanation: A compression cleanup operation has ANR6302E Command name: Process process ID, failed
been started to remove compression candidate - number of candidate files candidate files
information and temporary database entries from the were found in number of files examined
server database. Client files are not affected by this files examined prior to failure.
operation.
Explanation: A compression audit operation failed

before completion. The number of candidate files that command to obtain the correct identifier for the file to
were found prior to the failure are displayed. be removed.
System action: The audit operation ends.
ANR6306E Cleanup process name: Process process ID
User response: Examine message that appear before
failed due to server error - cleanup
this message on the server console or in the activity log
processing is incomplete.
to determine the source of the failure. If the error can
be corrected, re-execute the compression audit. If the Explanation: A compression cleanup operation has
failure cannot be determined or corrected, contact your failed before successful completion.
service representative. The compression candidate list
System action: The cleanup process ends.
can be displayed with the QUERY COMPRESSION
command. User response: Examine messages that appear on the
server console or in the server activity log prior to this
message to determine the cause of the error. If the error
ANR6303E Command name: Process process ID, failed
can be identified and corrected, restart the cleanup
- number of files promoted candidate files
operation with the CLEANUP COMPRESSION
were promoted as candidates at level
command. If the error cannot be corrected, contact your
audit level, number of files eliminated files
were eliminated as candidates, and
number of files expired candidates were
eliminated because they were found to ANR6600E Command: Invalid machine name -
be expired on the server. machine name.
Explanation: A compression audit operation failed Explanation: The machine name specified in the
before completion. The number of candidate files that command is invalid.
were promoted as candidates at this level of audit,
eliminated as candidates at this level of audit, and System action: The server does not process the
found to be expired before the audit failure are command.
reported. User response: Issue the command again and specify
System action: The audit operation ends. a valid machine name.
User response: Examine message that appear before

this message on the server console or in the activity log ANR6601E Command: Description information
to determine the source of the failure. If the error can exceeds maximum length characters.
be corrected, re-execute the compression audit. If the Explanation: The description specified in the
failure cannot be determined or corrected, contact your command exceeds the maximum length of allowable
service representative. The compression candidate list characters.
can be displayed with the QUERY COMPRESSION
command.
ANR6304E Command name: Command cannot be User response: Issue the command again and specify
processed until compression audit is a valid description.
performed.
Explanation: The indicated command cannot be ANR6602E Command: Recovery instructions file
processed until a compression audit is performed using name exceeds maximum length characters.
the AUDIT COMPRESSION command. Explanation: The recovery instructions file name
System action: The command fails. specified in the command exceeds the maximum length
of allowable characters.
User response: Issue the AUDIT COMPRESSION
command and then repeat the attempted operation. System action: The server does not process the
command.
ANR6305E Command name: File identifier is not a User response: Issue the command again and specify
suspect for compression errors. a valid recovery instructions file name.
Explanation: The file with the specified identifier is

not listed in the database as a suspect for compression ANR6603E Command: Characteristics file name
errors. The file cannot be removed from the suspect list. exceeds maximum length characters.
System action: Server operation continues. Explanation: The characteristics file name specified in
the command exceeds the maximum length of
User response: Use the QUERY COMPRESSION allowable characters.


ANR6609I Machine machine name defined.
command.
Explanation: A DEFINE MACHINE command has
added the requested machine to the server.
a valid characteristics file name.
ANR6604E Command: Invalid building identifier - User response: None.
building.
Explanation: The building identifier specified in the ANR6610E Command: Invalid recovery media name -
command is invalid. recovery media name.
System action: The server does not process the Explanation: The recovery media name specified in
command. the command is invalid.
User response: Issue the command again and specify System action: The server does not process the
a valid building identifier. command.
ANR6605E Command: Invalid floor identifier - floor. a valid recovery media name.
Explanation: The floor identifier specified in the
command is invalid. ANR6611E Command: Location information exceeds
command. Explanation: The location specified in the command
exceeds the maximum length of allowable characters.
a valid floor identifier. System action: The server does not process the
command.
ANR6606E Command: Invalid room identifier - room. User response: Issue the command again and specify
a valid location.
Explanation: The room identifier specified in the
command is invalid.
ANR6612I Machine machine name updated.
command. Explanation: An UPDATE MACHINE command has
updated one or more attributes of a machine.
a valid room identifier. System action: None.
ANR6607E Command: Machine machine name is
already defined.
ANR6613I Machine machine name deleted.
Explanation: The machine specified in the command
Explanation: A DELETE MACHINE command has
is already defined to the server.
deleted the requested machine from the server.
command.
another machine.
ANR6614E Command: Machine machine name is not
defined.
ANR6608E Command: A machine containing a server
is already defined. Explanation: The machine specified in the command
is not defined to the server.
Explanation: The ADSMSERVER=YES parameter
specified in the command is invalid because another System action: The server does not process the
machine has already been defined with this parameter. command.
Only one machine can be defined to the server as
containing a server. User response: Issue the command again and specify
a valid machine.
command.
User response: Issue the command again and do not
specify ADSMSERVER=YES as a parameter.

ANR6615E Command: Failed to open input file - file ANR6620E Command: Machine and node association
name. is already defined.
Explanation: The input file specified in the command Explanation: The machine and node association
cannot be opened by the server. specified in the command is already defined to the
server.
command. System action: The server operation continues, but the
an input file that is in a file system accessible by the User response: Issue the command again and specify
server. a valid node.
ANR6616E Command: Invalid sequence number - ANR6621I Node node name disassociated from
sequence number. machine machine name.
Explanation: The sequence number specified in the Explanation: A DELETE MACHNODEASSOCIATION
command is invalid. command has deleted the requested association from
the server. The node node name is not associated with
the machine machine name.
command.
a valid sequence number. User response: None.
ANR6617W Command: Node node name cannot be ANR6622E Command: Recovery media recovery media
processed because it is not registered. name is not defined.
Explanation: The node indicated in the message Explanation: The recovery media specified in the
cannot be processed because it is not registered. command is not defined to the server.
System action: The indicated node is not processed, System action: The server does not process the
but another node can be processed if specified by this command.
command.
User response: Issue the command again and specify a valid recovery media.
a valid registered node.
ANR6623W Command: Machine machine name cannot
ANR6618E Command: No matching node registered. be processed because it is not defined.
Explanation: The node specified in the command does Explanation: The machine indicated in the message is
not match any node registered to the server. not defined to the server.
System action: The server does not process the System action: The indicated machine is not
command. processed, but another machine can be processed if
specified by this command.
a valid node. User response: Issue the command again and specify
a valid machine.
ANR6619I Node node name associated with machine
machine name. ANR6624E Command: No matching machine
defined.
Explanation: A DEFINE MACHNODEASSOCIATION
command has associated the specified node with the Explanation: The machine specified in the command
specified machine. The node node name is associated does not match any machine defined to the server.
with the machine machine name.
System action: None. command.
User response: None. User response: Issue the command again and specify
a valid machine.

ANR6625I Machine machine name associated with ANR6630E Command: Product information exceeds
recovery media recovery media name. maximum length characters.
Explanation: A DEFINE Explanation: The product information specified in the
RECOVERYMEDIAMACHASSOCIATION command command exceeds the maximum length of allowable
has associated the specified machine with the specified characters.
recovery media. The machine machine name is
associated with the recovery media recovery media name.
command.
User response: None. valid product information.
ANR6626E Command: Recovery media/machine ANR6631E Command: Missing volume list for boot
association is already defined. recovery media.
Explanation: The recovery media/machine association Explanation: Boot recovery media cannot be defined
specified in the command is already defined to the to the server without specifying a volume list.
server.
System action: The server operation continues, but the command.
User response: Issue the command again and specify the volume list for the boot recovery media.
a valid machine.
ANR6632I Recovery media recovery media name
ANR6627I Machine machine name disassociated defined.
from recovery media recovery media name.
Explanation: A DEFINE RECOVERYMEDIA command
Explanation: A DELETE has defined the recovery media to the server.
RECOVERYMEDIAMACHASSOCIATION command
has deleted the requested association from the server.
Machine machine name is not associated with the User response: None.
recovery media recovery media name.
System action: None. ANR6633I Recovery media recovery media name
updated.
Explanation: An UPDATE RECOVERYMEDIA
command has updated one or more attributes of the
ANR6628E Command: Volume list exceeds maximum
recovery media.
length characters.
Explanation: The volume list specified in the
command exceeds the maximum length of allowable User response: None.
characters.
System action: The server does not process the ANR6634I Recovery media recovery media name
command. deleted.
User response: Issue the command again and specify Explanation: A DELETE RECOVERYMEDIA
a valid volume list. command has deleted the requested recovery media
from the server.
ANR6629E Command: Product name exceeds System action: None.
Explanation: The product name specified in the
command exceeds the maximum length of allowable
characters. ANR6635E Command: Recovery media recovery media
name is already defined.
command. Explanation: The recovery media specified in the
command is already defined to the server.
a valid product name. System action: The server does not process the
command.


ANR6640E Command: Cannot delete volume list for
a different recovery media.
boot recovery media.
Explanation: A volume list cannot be deleted for boot
ANR6636E Command: The characteristics specified
recovery media. A volume list must exist for each boot
for machine machine name exceeds
recovery media defined to the server.
Explanation: The characteristics specified in the
command.
command exceeds the maximum length of allowable
characters. User response: To delete the volume list, issue an
UPDATE RECOVERYMEDIA command and specify a
recovery media type of OTHER and VOLUMES="". To
command.
change the recovery media type to BOOT, issue an
User response: Issue the command again and specify UPDATE RECOVERYMEDIA command and specify the
valid characteristics. volume list containing the boot recovery media and
TYPE=BOOT.
ANR6637E Command: The recovery instructions
specified for machine machine name ANR6641E Command: No association found for
exceeds maximum length characters. machine and node pair specified.
Explanation: The recovery instructions specified in the Explanation: No association found for the machine
command exceeds the maximum length of allowable and node pair specified in the command.
characters.
System action: The server does not process the command has no effect.
command.
User response: Issue the command again and specify a valid machine and node pair.
valid recovery instructions.
ANR6642E Command: No association found for
ANR6638E Command: The characteristics for recovery media and machine pair
machine machine name are already specified.
defined.
Explanation: No association found for the recovery
Explanation: The characteristics for the machine media and machine pair specified in the command.
specified in the command are already defined to the
server.
command.
a valid recovery media and machine pair.
User response: If the specified machine is defined to
the server, issue an UPDATE MACHINE command to
ANR6643E Command: Invalid parameter value -
update the existing characteristics. If the machine is not
parameter value.
defined to the server, run AUDIT DRM FIX to delete
the characteristics. Explanation: The parameter issued in the command is
invalid.
ANR6639E Command: The recovery instructions for System action: The server does not process the
machine machine name are already command.
defined.
Explanation: The recovery instructions for the a valid parameter.
machine specified in the command are already defined
to the server.
ANR6644E Command: A character string must be
System action: The server does not process the specified.
command.
Explanation: The INSERT command is invalid. A
User response: If the specified machine is defined to character string must be specified.
the server, issue an UPDATE MACHINE command to
update the existing recovery instructions. If the
command.
machine is not defined to the server, run AUDIT DRM
FIX to delete the recovery instructions.

User response: Issue the command again and specify User response: Reissue the audit command with
a valid character string. FIX=YES specified so that the DRM global attributes
can be corrected.
ANR6645W Node node name has already been
associated with machine machine name. ANR6650I Audit command: DRM machine ID
Assignments are incorrect - values will
Explanation: The node specified in the DEFINE
be corrected.
MACHNODEASSOCIATION command is invalid. The
node is already associated with another machine shown Explanation: A database audit process finds that the
in the message. A node can only be associated with one global attributes machine ID used for server DRM
machine. activities are incorrect. Since FIX=YES has been
specified on the AUDIT command, the attribute value
System action: The indicated node is not processed,
will be corrected in the server database.
but another node can be processed if specified by the
command. System action: Audit processing continues.
User response: Issue the command again and specify User response: None
a valid node name.
ANR6651I Audit command: Invalid priority value
ANR6646I Audit command: Auditing disaster encountered for machine machine name.
recovery manager definitions.
Explanation: A database audit process encounters an
Explanation: This message is displayed during a invalid priority value for the machine indicated.
database audit and indicates that the disaster recovery
manager definitions are being examined by the
database audit process. User response: Issue the command again and specify
FIX=YES to correct the priority. Or, issue an UPDATE
MACHINE command and specify a new priority value.
ANR6652I Audit command: Invalid priority value
ANR6647E Audit command: DRM global attributes encountered for machine machine name -
are missing. the default value will be set.
Explanation: A database audit process finds that the Explanation: A database audit process encounters an
global attributes used for server DRM activities are invalid machine priority value for the machine
missing. indicated. Because FIX=YES has been specified, the
audit function sets the machine priority value to the
default value.
FIX=YES to recreate the DRM global attributes.
User response: To override the default value, issue an
UPDATE MACHINE command to change the value
ANR6648I Audit command: DRM global attributes
after the audit command has completed.
are missing - default values will be used
to recreate the attributes.
ANR6653I Audit command: Invalid building value
Explanation: A database audit process finds that the
encountered for machine machine name.
global attributes used for server DRM activities are
missing. Because FIX=YES has been specified on the Explanation: A database audit process encounters an
AUDIT command, default attribute values will be used invalid building value for the machine indicated.
to recreate the administrative global attributes.
User response: None. FIX=YES to correct the building value. Or, issue an
UPDATE MACHINE command and specify a new
building value.
ANR6649E Audit command: DRM machine ID
assignments are incorrect.
global attributes machine ID used for server DRM
activities are incorrect.


ANR6654I Audit command: Invalid building value
encountered for machine machine name - User response: To set the room value for the specified
the building value will be removed. machine to another value, use the UPDATE MACHINE
command after the audit command has completed.
invalid building value for the machine indicated.
Because FIX=YES has been specified, the audit function ANR6659I Audit command: Invalid server value
removes the machine building value. encountered for machine machine name.
System action: Audit processing continues. Explanation: A database audit process encounters an
invalid server value for the machine indicated.
User response: To set the building value to another
value, issue an UPDATE MACHINE command after the System action: Audit processing continues.
audit command has completed.
FIX=YES to correct the server value. Or, issue an
ANR6655I Audit command: Invalid floor value UPDATE MACHINE command and specify a new
encountered for machine machine name. server value.
invalid floor value for the machine indicated. ANR6660I Audit command: Invalid server value
encountered for machine machine name -
the default value will be set.
FIX=YES to correct the floor value. Or, issue an
invalid server value for the machine indicated. Because
UPDATE MACHINE command and specify a new floor
FIX=YES has been specified, the audit function sets the
value.
machine server value to the default value.
ANR6656I Audit command: Invalid floor value
encountered for machine machine name - User response: To override the default value, issue an
the floor value will be removed. UPDATE MACHINE command to change the value
invalid floor value for the machine indicated. Because
FIX=YES has been specified, the audit function removes ANR6661I Audit command: Multiple machines are
the machine floor value. indicated as servers. Only one machine
should have the server indicator set to
YES.
User response: To set the floor value to another value,
issue an UPDATE MACHINE command after the audit
more than one machine with the server indicator set to
command has completed.
YES.
ANR6657I Audit command: Invalid room value
encountered for machine machine name. User response: For a list of machines with the server
indicator set to YES, issue a QUERY MACHINE
ADSMSERVER=YES command. Issue an UPDATE
invalid room value for the machine indicated.
MACHINE command for each machine that is not a
System action: Audit processing continues. server.
FIX=YES to correct the room value. Or, issue an ANR6662I Audit command: Characteristics for
UPDATE MACHINE command and specify a new machine machine name not found.
room value.
characteristics reference from a machine for
ANR6658I Audit command: Invalid room value characteristics that are not in the server database.
encountered for machine machine name -
the room value will be removed.
User response: Issue an UPDATE MACHINE
command to load the characteristics into the database
invalid room value for the machine indicated. Because
FIX=YES has been specified, the audit function removes
the machine room value.

ANR6663I Audit command: Recovery instructions for ANR6667I Audit command: Invalid type value
machine machine name not found. encountered for recovery media recovery
media name - the default value will be
set.
recovery instructions reference from a machine for
recovery instructions that are not in the server Explanation: A database audit process encounters an
database. invalid type value for the recovery media indicated.
Because FIX=YES has been specified, the audit function
sets the recovery media type value to the default value.
User response: Issue an UPDATE MACHINE
command to load the recovery instructions into the
database after the audit command has completed. User response: To override the default value, issue an
UPDATE RECOVERYMEDIA command to change the
value after the audit command has completed.
ANR6664I Audit command: Invalid access value
encountered for recovery media recovery
media name. ANR6668E Audit command: Machine is not found for
internal machine ID machine ID, which
is referenced by recovery media.
invalid access value for the recovery media indicated.
Explanation: A database audit process finds recovery
media that references a machine that is not defined in
User response: Issue the command again and specify the server database.
FIX=YES to correct the access value. Or, issue an
UPDATE RECOVERYMEDIA command and specify a
new access value. User response: Issue the command again and specify
FIX=YES to correct recovery media attributes.
ANR6665I Audit command: Invalid access value
encountered for recovery media recovery ANR6669I Audit command: Machine is not found for
media name - the default value will be internal machine ID machine ID, which
set. is referenced by recovery media - the
machine reference will be deleted.
invalid access value for the recovery media indicated. Explanation: A database audit process finds recovery
Because FIX=YES has been specified, the audit function media that references a machine that is not defined in
sets the recovery media access value to the default the server database. Because FIX=YES has been
value. specified for the audit command, the reference will be
removed from the server database.
User response: To override the default value, issue an
UPDATE RECOVERYMEDIA command to change the User response: None.
ANR6670E Audit command: Recovery media not
ANR6666I Audit command: Invalid type value found for internal recovery media ID
encountered for recovery media recovery recovery media ID, which is referenced by
media name. a machine.
Explanation: A database audit process encounters an Explanation: A database audit process finds a machine
invalid type value for the recovery media indicated. that references recovery media that is not defined in the
server database.
FIX=YES to correct the type value. Or, issue an User response: Issue the command again and specify
UPDATE RECOVERYMEDIA command and specify a FIX=YES to correct the recovery media attributes.
new type value.
ANR6671I Audit command: Recovery media not
found for internal recovery media ID
recovery media ID, which is referenced by
a machine - the recovery media
reference will be deleted.

Explanation: A database audit process finds m

ANR6676E Audit command: Machine not found for
machine that references recovery media that is not
defined in the server database. Because FIX=YES has
is referenced by characteristics.
been specified for the audit command, the reference
will be deleted from the server database. Explanation: A database audit process finds
characteristics that reference a machine that is not
ANR6672E Audit command: Client node not found
FIX=YES to correct the machine attributes.
for internal node ID node ID, which is
referenced by a machine.
ANR6677I Audit command: Machine not found for
Explanation: A database audit process finds a machine
that references a client node that is not defined in the
is referenced by characteristics - the
server database.
Explanation: A database audit process finds
User response: Issue the command again and specify characteristics that reference a machine that is not
FIX=YES to correct the machine attributes. defined in the server database. Because FIX=YES has
been specified for the audit command, the reference
will be removed from the server database.
ANR6673I Audit command: Client node not found
for internal node ID node ID, which is System action: Audit processing continues.
referenced by a machine - the client
node reference will be deleted.
Explanation: A database audit process finds a machine
that references a client node that is not defined in the
server database. Because FIX=YES has been specified
is referenced by recovery instructions.
for the audit command, the reference will be removed
from the server database. Explanation: A database audit process finds recovery
instructions that reference a machine that is not defined
in the server database.
is referenced by a client node.
Explanation: A database audit process finds a client
node that references a machine that is not defined in
is referenced by recovery instructions -
the server database.
the machine reference will be deleted.
Explanation: A database audit process finds recovery
User response: Issue the command again and specify instructions that reference a machine that is not defined
FIX=YES to correct the machine attributes. in the server database. Because FIX=YES has been
specified for the audit command, the reference will be
removed from the server database.
internal machine ID machine ID, which System action: Audit processing continues.
is referenced by a client node - the
Explanation: A database audit process finds a client
ANR6680E Audit command: Missing or invalid
node that references a machine that is not defined in
internal database attribute encountered
the server database. Because FIX=YES has been
for machine machine name.
specified for the audit command, the reference will be
removed from the server database. Explanation: A database audit process finds an invalid
attribute for the specified machine.


ANR6685E Command: Volume volume name not
defined.
Explanation: Volume volume name is not defined to the
ANR6681I Audit command: Missing or invalid
server.
internal database attribute encountered
for machine machine name - the attribute System action: The indicated command is not
will be corrected. processed if the volume name is explicitly specified on
the command. If a volume pattern is specified on the
Explanation: A database audit process finds an invalid
command, the volume shown is not processed, but the
attribute for the specified machine. Because FIX=YES
other volumes are processed.
has been specified for the audit command the invalid
attribute will be corrected. User response: Reissue the command specifying a
valid volume name.
ANR6686E Command: Volume volume name in use.
Explanation: The MOVE DRMEDIA *
ANR6682I Command command ended: number of
WHERESTATE=MOUNTABLE command displays the
volumes volumes processed.
message. Volume volume name is used for another
Explanation: The indicated command ended. The total operation.
number of volumes successfully processed is shown in
System action: The command is not processed if the
the message.
volume is explicitly specified on the command. If a
System action: The indicated command ends. volume pattern is specified on the command, the
indicated volume is not processed, but the other
User response: None. volumes are processed.
User response: Wait until the conflicting volume
ANR6683I Command: Volume volume name was activity has completed, and then reissue the command.
moved from from state state to to state. If the volume is currently mounted, but idle, dismount
Explanation: Volume volume name is successfully the volume by using a DISMOUNT VOLUME
moved from state1 to state2 by the indicated command. command and then retry this operation.
System action: The indicated volume is moved to the

destination state. ANR6687E Command: Executable command string
exceeds maximum length characters.
Explanation: The length of the executable command
string specified with the CMD parameter exceeds the
ANR6684I Command: Volume volume name was maximum length of allowable characters (255).
deleted.
Explanation: The MOVE DRMEDIA * command.
WHERESTATE=COURIERRETRIEVE command
displays the message. Volume volume name is deleted User response: Issue the command again and specify
from the server database. For database backup volume, a valid executable command with the CMD parameter.
after its expiration days have elapsed, the volume
history record is deleted when it is returned onsite. For ANR6688E command: The specified command failed
an empty scratch copy storage pool volume, or because the entry/exit port of library
active-data storage pool volume, the volume record is library name is full. Please remove the
deleted when it is returned onsite. volume(s) from the entry/exit port and
System action: The volume record is deleted from the re-issue the command name command.
server database. Explanation: The indicated operation has failed
User response: Issue the CHECKIN LIBVOLUME because the entry/exit port of the specified library is
command for each volume returned onsite if the full.
volume is reused by the server. System action: The command fails.
User response: Remove the volume(s) from the
entry/exit port and re-issue the command to process
any remaining eligible volumes.

ANR6690E Command: Copy storage pool cstgp name ANR6696I command: operation for volume volume
not defined for Offsite Recovery Media. name in library library name starting.
Explanation: The MOVE DRMEDIA or QUERY Explanation: The indicated operation is being started
DRMEDIA command displays the message. The for the volume shown in the given library.
indicated command was issued with a copy storage
System action: The server starts the operation in
pool name specified, but the specified pool name is not
response to the indicated command entered by an
defined to DRM for Offsite Recovery Media.
administrator.
System action: The indicated command is not
User response: For SCSI library users, remove the
processed.
volume from the slot and issue a REPLY command,
User response: Reissue the command, after defining along with the request ID, to tell the server the volume
the specified copy storage pool to DRM for Offsite was removed from the library.
Recovery Media.
ANR6697I command: operation for volume volume
ANR6691E Command: No match is found for this name in library library name completed
move. successfully.
Explanation: The indicated command was issued, but Explanation: The indicated operation has completed
no matching volumes are defined to the server or the successfully for the volume shown in the given library.
volume specified is not managed by the command.
System action: The volume is either deleted from the
System action: The command is not processed. library inventory (if its status is something other than
DATA) or marked not present (if its status is DATA).
User response: Reissue the command specifying the
valid volume. User response: None.
ANR6694E Command: The ORM state state is invalid ANR6698E command: operation for volume volume
for a volume with access mode access name in library library name failed.
mode.
Explanation: The indicated operation has failed for the
Explanation: The indicated command specifies an volume shown in the given library. This message
Offsite Recovery Media state that is invalid for a should be preceded by another error message which
volume with the access mode shown. Specify provides more detail about the error.
COURIER or COURIERRETRIEVE for a volume that
System action: The volume is not processed.
has access mode of OFFSITE.
User response: Check for additional message and
eliminate the condition that caused the failure, then
command.
retry the command.
COURIER or COURIERRETRIEVE as the state for a
ANR6699I Cancel in progress.
volume that has access mode of OFFSITE.
Explanation: The MOVE DRMEDIA command has
been canceled and will end when resources have been
freed for the background process. This message may be
not defined for volume volume name.
Explanation: The MOVE DRMEDIA or QUERY for a MOVE DRMEDIA command.
DRMEDIA command displays the message. The
volume being processed has associated with the device
class name shown that is not defined to the server. User response: None.
System action: The command is not processed if the
volume is explicitly specified on the command. If a ANR6700I Command command completed
volume pattern is specified on the command, the successfully.
indicated volume is not processed, but the other
volumes not associated with the indicated class are Explanation: The indicated command completed
processed. successfully.
User response: Reissue the command after the System action: None.
indicated device class is defined to the server. User response: None.

ANR6701E Command: Invalid courier name - courier ANR6706E Command: Invalid vault name - vault
name. name.
Explanation: The indicated command has been Explanation: The indicated command has been
entered with an invalid courier name. entered with an invalid vault name.
command. command.
User response: Reissue the command with a valid User response: Reissue the command with a valid
courier name. vault name.
ANR6702E Command: Invalid expiration days value ANR6707W Command: The state, access and location
- days value. attributes of the copy storage pool
volume volume name were not updated.
Explanation: The indicated command has been
entered that specifies an invalid expiration days value. Explanation: The MOVE DRMEDIA command could
not update the state, access and location of volume
volume name because it was in use by another server
command.
operation.
System action: If the volume was in an automated
expiration days value.
library, the MOVE DRMEDIA command may have
checked the volume out of the library.
ANR6703E Command: Invalid recovery plan prefix -
If a volume pattern is specified on the command, the
prefix.
server continues processing the other volumes.
entered with an invalid recovery plan prefix.
activity has completed, and then reissue the MOVE
System action: The server does not process the DRMEDIA command. Do not run the MOVE
command. DRMEDIA and BACKUP STGPOOL commands
concurrently. Ensure that the BACKUP STGPOOL
User response: Reissue the command with a valid command is complete before you issue the MOVE
recovery plan prefix. DRMEDIA command.
ANR6704E Command: Invalid plan instructions ANR6708W Command: Copy pool volume volume
prefix - prefix. name was not processed. The volume
Explanation: The indicated command has been was in use.
entered with an invalid plan instructions prefix. Explanation: The MOVE DRMEDIA command did not
System action: The server does not process the process volume volume name because it was in use by
command. another server operation.
User response: Reissue the command with a valid System action: The indicated command ends, if the
plan instructions prefix. volume was explicitly specified in the command. If a
volume pattern was specified in the command, the
server continues processing other volumes that match
ANR6705E Command: Invalid character for volume the pattern.
postfix - postfix character.
Explanation: The indicated command has been activity has completed, and then reissue the MOVE
entered with an invalid character that is to be added to DRMEDIA command.
the volumes names in the recovery plan file.
System action: The server does not process the ANR6709W Command: Active-data pool volume
command. volume name was not processed. The
User response: Reissue the command with a valid volume was in use.
character. Explanation: The MOVE DRMEDIA command did not
process volume volume name because it was in use by
another server operation.
System action: The indicated command ends, if the
volume was explicitly specified in the command. If a

volume pattern was specified in the command, the

ANR6713E Audit command: An invalid check label
value encountered.
the pattern.
invalid check label value.
DRMEDIA command. System action: Audit processing continues.
ANR6710W Command: The state, access and location FIX=YES to correct the check label value. Or, issue a
attributes of the active-data storage pool SET DRMCHECKLABEL command and specify a new
volume volume name were not updated. check label value.
Explanation: The MOVE DRMEDIA command could
not update the state, access and location of volume ANR6714I Audit command: An invalid check label
volume name because it was in use by another server value encountered - the default value
operation. will be set.
System action: If the volume was in an automated Explanation: A database audit process encounters an
library, the MOVE DRMEDIA command may have invalid check label value. Because FIX=YES has been
checked the volume out of the library. specified, the audit function sets the check label value
to the default value.
server continues processing the other volumes. System action: Audit processing continues.
User response: Wait until the conflicting volume User response: To override the default value, issue a
activity has completed, and then reissue the MOVE SET DRMCHECKLABEL command to change the value
DRMEDIA command. after the audit command has completed.
ANR6711E Audit command: An invalid database ANR6715E Audit command: An invalid file process
backup series expiration days value encountered.
encountered.
Explanation: A database audit process encounters an invalid file process value.
invalid value for database backup series expiration
days.
FIX=YES to correct the file process value. Or, issue a
User response: Issue the command again and specify SET DRMFILEPROCESS command and specify a new
FIX=YES to correct the expiration days. Or, issue an file process value.
SET DRMDBBACKUPEXPIREDAYS command and
specify a new expiration days value.
ANR6716I Audit command: An invalid file process
value encountered - the default value
ANR6712I Audit command: An invalid database will be set.
backup series expiration days
encountered - the default value will be
invalid file process value. Because FIX=YES has been
set.
specified, the audit function sets the file process value
Explanation: A database audit process encounters an to the default value.
invalid value for database backup series expiration
days. Because FIX=YES has been specified, the audit
function sets the expiration days value to the default User response: To override the default value, issue a
value. SET DRMFILEPROCESS command to change the value
User response: To override the default value, issue a
ANR6717E Audit command: Extraneous DRM global
SET DRMDBBACKUPEXPIREDAYS command to
attribute encountered.
change the value after the audit command has
completed. Explanation: A database audit process finds a
nonexistent DRM global attribute.

FIX=YES to delete the extraneous attribute. User response: None.
ANR6718I Audit command: Extraneous DRM global ANR6723E Audit command: Prefix for DRM recovery
attribute encountered - the attribute will plan not found.
be deleted.
Explanation: A database audit process finds no entries
Explanation: A database audit process finds a in server database for DRM recovery plan prefix
nonexistent DRM global attribute. Since FIX=YES has definitions.
been specified, the extraneous attribute will be deleted.
User response: Issue the audit command again and
User response: None. specify FIX=YES to correct the error.
ANR6719E Audit command: DRM machine ID ANR6724I Audit command: Prefix for DRM recovery
assignments not found. plan not found - entry will be created.
Explanation: A database audit process finds no entries Explanation: A database audit process finds no entries
in server database for DRM internal machine ID in server database for DRM recovery plan prefix
assignments. definitions. Because FIX=YES has been specified for the
audit command, the audit function creates an entry
using the default value in the server database for the
User response: Issue the command again and specify recovery plan file prefix.
FIX=YES to correct the error.
ANR6720I Audit command: DRM machine ID
SET DRMPLANFILEPREFIX command to change the
assignments not found - entry will be
created.
ANR6725E Audit command: Prefix for DRM recovery
in server database for DRM internal machine ID
plan instructions not found.
assignments. Because FIX=YES has been specified for
the audit command, the audit function creates an entry Explanation: A database audit process finds no entries
in the server database for the machine ID assignments. in server database for DRM recovery plan instructions
prefix definitions.
specify FIX=YES to correct the error.
ANR6721E Audit command: DRM recovery media ID
assignments not found.
ANR6726I Audit command: Prefix for DRM recovery
plan instructions not found - entry will
in server database for DRM internal recovery media ID
be created.
assignments.
in server database for DRM recovery plan instructions
User response: Issue the command again and specify prefix definitions. Because FIX=YES has been specified
FIX=YES to correct the error. for the audit command, the audit function creates an
entry using the default value in the server database for
the recovery plan instructions file prefix.
ANR6722I Audit command: DRM recovery media ID
assignments not found - entry will be System action: Audit processing continues.
created.
Explanation: A database audit process finds no entries SET DRMPLANINSTRPREFIX command to change the
in server database for DRM internal recovery media ID value after the audit command has completed.
assignments. Because FIX=YES has been specified for
the audit command, the audit function creates an entry
in the server database for the recovery media ID
assignments.


ANR6727E Audit command: Postfix for DRM
replacement volumes names not found. User response: Issue the audit command again and
in server database for DRM postfix definitions for
replacement volumes names. ANR6732I Audit command: Copy storage pools to be
managed by DRM not found - entry
will be created.
in server database for copy storage pools to be
managed by DRM. Because FIX=YES has been specified
ANR6728I Audit command: Postfix for DRM for the audit command, the audit function creates an
replacement volumes names not found - entry using the default value in the server database for
entry will be created. the copy storage pools to be managed by DRM.
Explanation: A database audit process finds no entries System action: Audit processing continues.
in server database for DRM postfix definitions for
replacement volumes names. Because FIX=YES has
SET DRMCOPYSTGPOOL command to change the
been specified for the audit command, the audit
function creates an entry using the default value in the
server database for the replacement volumes postfix.
ANR6733E Command: Cannot complete initialization
for process name process.
Explanation: The indicated process fails during
SET DRMPLANVPOSTFIX command to change the
process initialization.
System action: The indicated command is ended and
server processing continues.
ANR6729E Audit command: Primary storage pools to
be restored by DRM not found. User response: This usually indicates that sufficient
server memory is not available on the server.
in server database for primary storage pools to be See the documentation for the operating system about
restored by DRM. how to increase memory for an application.
processed: library library name not
defined.
Explanation: The indicated volume is not processed
ANR6730I Audit command: Primary storage pools to
since the designated library has not been defined or has
be restored by DRM not found - entry
been deleted.
will be created.
System action: The volume is not processed.
in server database for primary storage pools to be User response: Reissue the command using a different
restored by DRM. Because FIX=YES has been specified library name, or define the library before retrying the
for the audit command, the audit function creates an command.
entry using the default value in the server database for
the primary storage pools to be restored by DRM.
ANR6735E Audit command: Courier information for
System action: Audit processing continues. ORM not found.
User response: To override the default value, issue a Explanation: A database audit process finds no entries
SET DRMPRIMSTGPOOL command to change the in server database for courier name definitions used by
value after the audit command has completed. DRM Offsite Recovery Media (ORM).
ANR6731E Audit command: Copy storage pools to be
managed by DRM not found. User response: Issue the audit command again and
in server database for copy storage pools to be
managed by DRM.

(ORM). Because FIX=YES has been specified for the

ANR6736I Audit command: Courier information for
ORM not found - entry will be created.
using the default value in the server database for the
Explanation: A database audit process finds no entries database backup series expiration days definitions.
in server database for courier name definitions used by
DRM Offsite Recovery Media (ORM). Because FIX=YES
has been specified for the audit command, the audit User response: To override the default value, issue a
function creates an entry using the default value in the SET DRMDBBACKUPEXPIREDAYS command to
server database for the courier name definitions. change the value after the audit command has
completed.
ANR6741E Audit command: Check label indicator for
SET DRMCOURIERNAME command to change the
ORM not found.
in server database for check label definitions used by
ANR6737E Audit command: Vault name for ORM not
DRM Offsite Recovery Media (ORM).
found.
in server database for vault name definitions used by User response: Issue the audit command again and
DRM Offsite Recovery Media (ORM). specify FIX=YES to correct the error.
ANR6742I Audit command: Check label indicator for
in server database for check label definitions used by
ANR6738I Audit command: Vault name for ORM not
DRM Offsite Recovery Media (ORM ). Because
found - entry will be created.
Explanation: A database audit process finds no entries audit function creates an entry using the default value
in server database for vault name definitions used by in the server database for the check label definitions.
has been specified for the audit command, the audit
function creates an entry using the default value in the User response: To override the default value, issue a
server database for the vault name definitions. SET DRMCHECKLABEL command to change the value
ANR6743E Audit command: File process indicator for
SET DRMVAULTNAME command to change the value
ORM not found.
in server database for file process definitions used by
ANR6739E Audit command: Database backup series
DRM Offsite Recovery Media (ORM).
expiration days for ORM not found.
in server database for database backup series expiration User response: Issue the audit command again and
days definitions used by DRM Offsite Recovery Media specify FIX=YES to correct the error.
(ORM).
System action: Audit processing continues. ANR6744I Audit command: File process indicator for
specify FIX=YES to correct the error. Explanation: A database audit process finds no entries
in server database for file process definitions used by
ANR6740I Audit command: Database backup series
has been specified for the audit command, the audit
expiration days for ORM not found -
function creates an entry using the default value in the
entry will be created.
server database for the file process definitions.
in server database for database backup series expiration
days definitions used by DRM Offsite Recovery Media User response: To override the default value, issue a

SET DRMFILEPROCESS command to change the value User response: Issue a QUERY LICENSE command to
after the audit command has completed. determine which license terms are not in compliance.
ANR6745E Audit command: DRM recovery media ID ANR6751E Disaster recovery manager operation
assignments are incorrect. command being processed is denied - server
is not licensed for disaster recovery
manager support.
global attributes recovery media id used for server
DRM activities are incorrect. Explanation: The server refuses a disaster recovery
manager operation because the server is not licensed to
support the disaster recovery manager.
FIX=YES specified so that the DRM global attributes
can be corrected. User response: Obtain the license to support the
disaster recovery manager from your service provider
or reseller. Issue the REGISTER LICENSE command
ANR6746I Audit command: DRM recovery media ID
with this license to enable the disaster recovery
assignments are incorrect - values will
manager support.
be corrected.
ANR6752W Disaster recovery manager operation
global attributes recovery media ID used for server
Command being processed is in violation of
DRM activities are incorrect. Since FIX=YES has been
server license terms - server is not
specified on the AUDIT command, the attribute value
licensed for disaster recovery manager
will be corrected in the server database.
support.
Explanation: The server warns about a disaster
User response: None. recovery manager operation because the server is not
licensed to support disaster recovery manager.
ANR6747I Number of volumes processed: number System action: Server operation continues.
Explanation: The MOVE DRMEDIA command has User response: Obtain the license to support disaster
processed the number of volumes displayed. This recovery manager from your service provider or
message may be displayed in response to a QUERY reseller. Issue the REGISTER LICENSE command with
PROCESS command for a MOVE DRMEDIA command. this license to enable disaster recovery manager
support.
User response: None. ANR6753E command being processed encountered an
internal server error while checking
ANR6749I Command: process process ID terminated license compliance.
before completion - process canceled. Explanation: The server encountered an internal error
Explanation: The indicated background process in determining whether the server is in compliance
performing the command shown has been canceled. with license terms.
System action: If other processes are executing, these System action: Server operation continues.
processes continue. User response: Issue the QUERY LICENSE and
User response: None. QUERY STATUS commands to determine if the server
is in compliance with license terms. Start an AUDIT
LICENSES process to adjust server license information.
ANR6750E Disaster recovery manager operation When this process completes, start the session again. If
command being processed is denied - server the problem persists, contact your service
is not in compliance with license terms. representative.
Explanation: The server refuses a disaster recovery
manager operation because the current server ANR6754I Machine machine name characteristics
configuration is not in compliance with the license deleted.
terms.
System action: Server operation continues. Disaster deleted the requested characteristics from the server.
recovery operations cannot be performed until the
server is licensed for the disaster recovery manager System action: None.
product.

User response: None. support is not available for the indicated server
platform.
ANR6755I Machine machine name recovery System action: Server operation continues.
instructions deleted.
deleted the requested recovery instructions from the
ANR6760E Command: Executable command line
server.
exceeds maximum length characters for
System action: None. volume volume name.
User response: None. Explanation: While writing to a command file, one of
the following conditions occurred:
ANR6756E Machine machine name characteristics not v The length of the command line written to the
defined to the server. command file exceeds the LRECL specified for MVS
or exceeds the default length for the command line
Explanation: A DELETE MACHINE command cannot written (255).
delete the requested characteristics from the server. The
v The length of the command created after replacing
characteristics for the specified machine are not defined
the substitution variables &VOL, &VOLDSN, &NL,
to the server.
and &LOC exceeds the server allowable command
System action: The server operation continues, but the line length (1500).
User response: Issue the command again and specify command.
a machine that has characteristics defined to the server.
a valid executable command with the CMD parameter.
ANR6757E Machine machine name recovery
In the case where volumes are being ejected from the
instructions not defined to the server.
library, it is possible the server database does not reflect
Explanation: A DELETE MACHINE command cannot the true state of the volume. For MOVE DRMEDIA,
delete the requested recovery instructions from the rerun the command after determining the cause of the
server. The recovery instructions for the specified error. For MOVE MEDIA, an update volume command
machine are not defined to the server. should be issued setting the access of the volume to
read only.
System action: The server operation continues, but the
command has no effect. If this message is issued by a MOVE or QUERY
DRMEDIA command and the volume record has been
User response: Issue the command again and specify deleted from the server database, you can not use the
a machine that has recovery instructions defined to the MOVE or QUERY DRMEDIA commands to create the
server. command file entry for this volume. In this case, you
must manually issue the proper command.
ANR6758E Command: Only one character string can
be specified. ANR6761E Command: WHERESTATE parameter is
Explanation: The INSERT command is invalid. Either required.
a characteristics string can be specified or a recovery Explanation: The indicated command specifies a
instructions string can be specified on the command. volume name containing a pattern matching character
Both types of strings cannot be specified on the and the TOSTATE parameter. The WHERESTATE
command at the same time. parameter is not specified. The specification is invalid.
System action: The server does not process the Pattern-matching for volume names is only allowed
command. when the WHERESTATE parameter is specified.
User response: Issue the command again and specify System action: The server does not process the
one valid character string. command.
ANR6759E Disaster recovery manager operation specific volume name or by specifying the
command being processed is denied - WHERESTATE parameter along with the TOSTATE
disaster recovery manager support is not parameter.
available for server platform platform.
Explanation: The server refuses a disaster recovery
manager operation because disaster recovery manager

ANR6762E Command: The specified destination state ANR6767E Command: Invalid command file name -
tostate is invalid for volume volume name command file name.
in current state state.
Explanation: The indicated command specifies a entered with an invalid command file name.
destination state that is invalid for the volume name
shown in the indicated current state.
command.
volume.
command file name.
a valid destination state for the volume name shown.
ANR6768E command: Prefix exceeds maximum
characters characters.
ANR6763I Command: The specified command has
Explanation: The prefix specified for recovery plan
been written to file 'file name'.
files or for plan instructions files exceeds the maximum
Explanation: The command string specified with the valid length. The maximum valid length is shown in
CMD parameter on the command shown is written to the message.
the indicated file for each volume successfully
processed.
command.
User response: Execute the commands written to the valid prefix.
file.
ANR6769E Audit command: Not mountable name
ANR6764E command: Command file name exceeds information for ORM not found.
Explanation: The file name specified for containing in server database for not mountable location name
the executable commands generated by DRM exceeds definitions used by DRM Offsite Recovery Media
the maximum valid length shown. (ORM).
System action: The server does not process the System action: Audit processing continues.
command.
User response: Reissue the command specifying a specify FIX=YES to correct the error.
valid file name.
ANR6770I Audit command: Not mountable name
ANR6765E Command: Invalid not mountable information for ORM not found - entry
location name - not mountable name. will be created.
Explanation: The indicated command has been Explanation: A database audit process finds no entries
entered with an invalid not mountable location name. in server database for not mountable location name
definitions used by DRM Offsite Recovery Media
(ORM). Because FIX=YES has been specified for the
command.
User response: Reissue the command with a valid not using the default value in the server database for the
mountable location name. courier name definitions.
ANR6766E Command: No command string is
specified for FORMAT=CMD.
SET DRMNOTMOUNTABLENAME command to
Explanation: The indicated command has been change the value after the audit command has
entered with a FORMAT=CMD to write a command completed.
string to a file, but no command string is specified.
System action: The server does not process the ANR6771E Audit command: Command file name
command. information for ORM not found.
User response: Reissue the command specifying a Explanation: A database audit process finds no entries
command string to be written to a file. in server database for command file name definitions
used by DRM Offsite Recovery Media (ORM).


ANR6775E Command: Error writing to file 'file name'
User response: Issue the audit command again and for volume volume name.
Explanation: An error occurred while writing to the
file name shown for the indicated volume.
ANR6772I Audit command: Command file name
information for ORM not found - entry
command.
will be created.
in server database for command file name definitions
used by DRM Offsite Recovery Media (ORM). Because
proper authority to write to the file indicated. Reissue
the command after determining the cause of the error.
audit function creates an entry using the default value
in the server database for the command file name In the case where volumes are being ejected from the
definitions. library, it is possible the server database does not reflect
the true state of the volume. For MOVE DRMEDIA,
rerun the command after determining the cause of the
User response: To override the default value, issue a error. For MOVE MEDIA, an update volume command
SET DRMCMDFILENAME command to change the should be issued setting the access of the volume to
value after the audit command has completed. read only.
If this message is issued by a MOVE or QUERY
ANR6773E Command: Unable to open file 'command DRMEDIA command and the volume record has been
file name' for output. deleted from the server database, you can not use the
MOVE or QUERY DRMEDIA commands to create the
Explanation: An error occurred while opening the command file entry for this volume. In this case, you
command file name shown. The file name shown in the must manually issue the proper command.
message is specified with the indicated command, the
SET command, or the default name generated by the
indicated command. ANR6776E Command: Could not delete file: file name
System action: The server does not process the Explanation: The indicated command failed but the
indicated command. file created could not be deleted.
User response: Examine error messages that may have System action: None.
User response: Delete the file shown.
proper authority to write to the file indicated. In AIX,
make sure that the file name specified in the command ANR6777E Command: Command file 'file name'
or in the SET command is a full path file name, not a already in use.
directory path name. In MVS, make sure that the file
Explanation: The command indicated references a
name specified in the command or in the SET
command file name that is in use. The command file
command is a valid MVS file name. Reissue the
name shown is selected for use by the server in the
command after determining the cause of the error.
following order:
v The file name specified on the indicated command.
ANR6774E Command: Invalid volume transition
v The file name specified on the SET command.
states - from 'specified WHERESTATE'
state to 'specified TOSTATE' state. v The file name generated by the server (AIX only).
Explanation: The TOSTATE specified is an invalid System action: The server does not process the
destination state for the WHERESTATE specified. command.
System action: The server does not process the User response: Reissue the command at a later time
command. or reissue the command specifying a different
command file name.
a valid destination state.
processed: device type device type not
supported.
because the device type shown is not supported by the
function.

System action: The indicated volume is not processed. using the default value in the server database for the
recovery plan file expiration days definitions.
ANR6779E Disaster recovery manager operation User response: To override the default value, issue a
command being processed is denied - SET DRMRPFEXPIREDAYS command to change the
disaster recovery manager support is not value after the audit command has completed.
available for server platform.
Explanation: The server refuses a disaster recovery ANR6784I Number of volumes processed: number
manager operation because disaster recovery manager volumes processed. Volumes sent to library
support is not available for the server platform. library name for checkout: number volumes
sent.
Explanation: The MOVE DRMEDIA command has
processed the number of volumes shown. Currently, the
MOVE DRMEDIA command has sent for processing
ANR6780E Audit command: An invalid recovery plan the number of volumes shown to the library shown.
file expiration days encountered. This message may be displayed in response to a
QUERY PROCESS command for a MOVE DRMEDIA
Explanation: A database audit process encounters an command.
invalid value for recovery plan file expiration days.
FIX=YES to correct the expiration days. Or, issue an
SET DRMRPFEXPIREDAYS command and specify a ANR6785W Warning: The ADSM V3 Disaster
new expiration days value. Recovery Manager Disk Image Dump
function is not supported in the disaster
recovery manager . The ADSM V3 DRM
ANR6781I Audit command: An invalid recovery plan Disk Image Restore function has been
file expiration days encountered - the stabilized with no new maintenance or
default value will be set. hardware support planned.
Explanation: A database audit process encounters an Explanation: None.
invalid value for recovery plan file expiration days.
Because FIX=YES has been specified, the audit function System action: DRM Disk Image Dump and Restore
sets the expiration days value to the default value. function continues.
System action: Audit processing continues. User response: None.
SET DRMRPFEXPIREDAYS command to change the ANR6900I Command: The recovery plan file file
value after the audit command has completed. name was created.
Explanation: The recovery plan file was created.
ANR6782E Audit command: Recovery plan file
expiration days not found.
in server database for recovery plan file expiration days
definitions. ANR6901I Number of plan stanzas processed:
number.
Explanation: The PREPARE command has processed
the number of stanzas displayed. This message may be
for a PREPARE command.
ANR6783I Audit command: Recovery plan file
expiration days not found - entry will
be created. User response: None.
in server database for recovery plan file expiration days
definitions. Because FIX=YES has been specified for the

ANR6902I Number of plan stanzas processed: ANR6913W Command: No volumes with backup data
number. Currently processing stanza: exist in copy storage pool storage pool
recovery plan stanza name. name.
Explanation: The PREPARE command displays the Explanation: A copy storage pool does not contain
number of stanzas already processed and the name of any volumes with usable data.
the stanza currently being processed. This message may
System action: Stanzas in the recovery plan do not
be displayed in response to a QUERY PROCESS
include recovery information for any volumes in the
command for a PREPARE command.
storage pool.
User response: Determine why this storage pool has
User response: None. no volumes with usable data.
ANR6903I Cancel in progress. ANR6914W Command: No volumes with active data

exist in the active-data storage pool
Explanation: The PREPARE command has been
storage pool name.
canceled and will end when resources have been freed
for the background process. This message may be Explanation: An active-data storage pool does not
displayed in response to a QUERY PROCESS command contain any volumes with usable data.
for a PREPARE command.
System action: Server operation continues. include recovery information for any volumes in the
storage pool.
User response: Determine why this storage pool has
no volumes with usable data.
ANR6904I Sending recovery plan file to target
server.
ANR6915W Command: Storage pool storage pool name
Explanation: The PREPARE command is sending the
storage pool type is not defined to the
recovery plan file to the target server. This message
server.
may be displayed in response to a QUERY PROCESS
command for a PREPARE command. Explanation: A storage pool that is not defined to the
server was specified by SET DRMPRIMSTGPOOL, SET
DRMCOPYSTGPOOL, or on the PREPARE command
User response: None. line.
ANR6905I Command: Recovery plan file RPF volume include recovery information for the storage pool.
name was created. Specified device class
User response: Correct the storage pool specification
device class name.
or define the storage pool to the server.
Explanation: The recovery plan file was created on the
target server.
ANR6916W Command: No copy storage pools are
System action: Server operation continues. defined.
User response: None. Explanation: The server has no copy storage pools
defined.
ANR6912W Command: The database was not backed System action: Recovery plan file will not contain
up. copy storage pool information.
Explanation: No backups have been made of the User response: Define copy storage pools in the
server data base. server.
include database recovery information. ANR6918W Command: Recovery instructions file file
name not found.
User response: Backup the server data base by issuing
the BACKUP DB command. Explanation: A source file for recovery instructions
was not found.
System action: The recovery plan will not contain
recovery instructions.
User response: To get recovery instructions in the

recovery plan, ensure the corresponding instructions commands have been issued to define the recovery
source file exists. If it does, check authorizations to the media.
file.
ANR6924W Command: No recovery instructions
ANR6920W Command: S volume name is not valid for defined for machine machine name.
server device type device type. Original
Explanation: No recovery instructions have been
volume name: volume name. Stanza is
defined to the server for the specified machine.
stanza name.
System action: The recovery plan file does not contain
Explanation: Appending the replacement volume
the machine recovery instructions stanza.
name postfix (as defined with SET
DRMPLANVPOSTFIX) to the original volume name User response: If you want to include the machine
has created a name that is not valid for the server recovery instructions in the recovery plan file, issue the
device type shown. INSERT command. Reissue the PREPARE command
after the appropriate commands have been issued to
System action: Replacement volume name is used in
define the recovery media.
the recovery plan stanza.
User response: Devise a naming convention that
ANR6925W Command: No machine characteristics
allows the use of the replacement volume name postfix
defined for machine machine name.
or at restore time manually update the generated
recovery plan with a legal replacement name. Explanation: No characteristics have been defined to
the server for the specified machine.
ANR6921W Command: Cannot locate server options System action: The recovery plan file does not contain
file 'file name'. the machine characteristics stanza.
Explanation: The Prepare command cannot open the User response: If you want to include the machine
specified server options file. recovery instructions in the recovery plan file, issue the
INSERT command. Reissue the PREPARE command
System action: VOLHISTORY and DEVCONFIG
after the appropriate commands have been issued to
options are added to the recovery plan file stanza
define the recovery media.
DSMSERV.OPT.FILE.
ANR6926W Command: There is at least one invalid
generated volume name associated with
ANR6922W Command: No machine information was storage pool storage pool server device
defined for the machine that contains type device type in stanza stanza name.
server server name.
Explanation: The machine information has not been name postfix (as defined with SET
saved in the server data base. DRMPLANVPOSTFIX) to the original volume name
has created a name that is not valid for the server
device type shown.
the machine and recovery media information stanzas.
System action: Replacement volume name is used in
User response: If you want to include the machine
information in the recovery plan file, issue the DEFINE
MACHINE command to save the machine information User response: Devise a naming convention that
in the server data base and reissue the PREPARE allows the use of the replacement volume name postfix
command. or at restore time manually update the generated
recovery plan with a legal replacement name.
ANR6923W Command: No recovery media defined
for machine machine name. ANR6927W Command: Primary storage pool storage
pool name, storage pool data format, is not
Explanation: No recovery media has been defined to
managed by DRM.
the server for the specified machine.
Explanation: A SET DRMPRIMSTGPOOL or the
PREPARE command specified a primary storage pool
the machine recovery media stanza.
that is used for backing up NAS file servers, using
User response: If you want to include the machine NDMP. DRM does not manage a storage pool with this
recovery media information in the recovery plan file, data format.
issue the DEFINE RECOVERYMEDIA command.
Reissue the PREPARE command after the appropriate
include recovery information for the storage pool.

User response: Correct the storage pool specification.

ANR6938I No information found for stanza stanza
name.
ANR6928W Command: No eligible primary storage
Explanation: No information found for recovery plan
pools match the specified storage pool
file stanza shown.
name storage pool name .
System action: The server does not display the
Explanation: The storage pool specified by the SET
information for the stanza.
DRMPRIMSTGPOOL or on PREPARE command does
not match any eligible primary storage pool. Possible User response: None
reasons include:
v Primary storage pools were not defined. ANR6939E Command: Invalid recovery plan file
v Primary storage pools were defined, but their data stanza name - stanza name.
formats are for NAS file servers, or their device
Explanation: The specified recovery plan file stanza
classes use the CENTERA device type.
name is invalid.
v The name specified does not match eligible primary
storage pool names. System action: The server does not process the
command.
include recovery information for the storage pools. User response: Issue the command again and specify
a valid recovery plan file stanza name.
User response: Correct the storage pool specification
or define eligible storage pools to the server.
ANR6940E command command not allowed from
server console.
ANR6929W Command: No eligible primary storage
pools are defined to the server. Explanation: The indicated command is not allowed
to be issued from the server console.
Explanation: The server has no eligible primary
storage pools defined. System action: The command is not executed.
System action: Recovery plan file will not contain User response: Reissue the command from an
primary storage pool information. administrator using an Administrative Client.
User response: Define eligible primary storage pools

to the server. ANR6941E Query recovery plan file content is
waiting for mount point in device class
device class name.
ANR6930W Command: Primary storage pool storage
pool name, whose device class uses the Explanation: Query recovery plan file content has
CENTERA device type, is not managed begun to wait for a mount point that can be used for a
by DRM. volume in the device class shown.
Explanation: The SET DRMPRIMSTGPOOL or the System action: The function waits for the mount
PREPARE command specified a primary storage pool point.
whose device class uses the CENTERA device type. User response: Respond to any mount requests.
DRM does not manage storage pools that use the
CENTERA device type.
ANR6942E Query recovery plan file content is
System action: Stanzas in the recovery plan do not waiting for access to input volume
include recovery information for the storage pool. volume name.
User response: Correct the storage pool specification. Explanation: Query recovery plan file content has
begun to wait for availability of the input volume
ANR6937E command: parameter name parameter not shown.
allowed from the command line. System action: The function waits for the volume to
Explanation: The parameter shown is not allowed become available.
from the command line interface. User response: None.
command.
parameter from the web.

v Database corruption
ANR6943E Query recovery plan file content is
waiting for mount of input volume System action: The retrieve operation ends, and the
volume name. server operation continues.
Explanation: Query recovery plan file content has User response: Examine any prior error messages to
begun to wait for the mount of the input volume determine the source of the error. Use the QUERY
shown. ACTLOG command to view the activity log and search
System action: The function waits for mount.
restore or retrieve again. If retry of the operation
User response: Respond to any mount requests. continues to fail contact your service representative.
ANR6944E Command: Invalid recovery plan file ANR6948E Command: Cannot find the recovery plan
name - recovery plan file name. file for Recovery plan file name.
Explanation: The recovery plan file name specified in Explanation: The server cannot find the specified
the command is invalid. recovery plan file.
command. command.
User response: Issue the command again and specify User response: Issue the command again and specify
a valid recovery plan file name. a valid recovery plan file name. Use the QUERY
RPFILE command to view the name of the recovery
plan file that you are interested in displaying its
ANR6945E Command: Cannot find filespace filespace
content.
name for recovery plan file recovery plan
file name.
ANR6949E Command: No matching device class
Explanation: The server cannot find the filespace
defined.
(ADSM.SERVER) for recovery plan file specified in the
server. Explanation: The device class specified in the
command does not match any device class defined to
System action: The retrieve operation ends, and the
the server.
User response: Issue QUERY FILESPACE command
command.
on the target server to see if there is any filespaces
created for the recovery plan file. The filespace name User response: Issue the command again and specify
for the recovery plan file is ADSM.SERVER. a valid device class.
ANR6946E Command: Retrieve failed for recovery ANR6950E Command: The recovery plan file was not
plan file name - error on input storage created.
device.
Explanation: Due to a processing error, a recovery
Explanation: The server ends an retrieve operation plan file was not created.
because an I/O error has been encountered by the
System action: Recovery plan file not created.
server in reading from a device.
System action: The retrieve operation ends, and the
problems, if possible. Reissue the command, after
User response: Query the activity log to find messages determining the cause of the error.
preceding this one that specify the device that is failing.
The server may need to be shut down with the HALT
ANR6951E Command: Recovery plan file file name
command to correct the hardware problem.
was not created.
Explanation: Due to a processing error, a recovery
ANR6947E Command: Data storage retrieve failed
plan file was not created.
for recovery plan file name - error detected.
Explanation: The server ends the retrieve operation
because an error has been encountered on the server. User response: Examine error messages that may have
Some common reasons for the error are: been displayed prior to this message and correct any
v Data is corrupted on the input volume problems, if possible. Make sure that the server has
proper authority to write to the file indicated and that
v Hardware or media failure has occurred


ANR6962E Command: Query database failed.
Reissue the command, after determining the cause of
the error. Explanation: A server database query error occurred.
This message always accompanies another error
message and provides more detail about that error.
ANR6952E Command: File name file name already
exists. System action: The recovery plan file was not created.
Explanation: File already exits. User response: Issue a QUERY ACTLOG command to
view the activity log and search for messages. If the
error cannot be isolated and resolved, contact your
User response: Determine why file already exists. If service representative.
possible, delete it. Reissue the command, after
determining the cause of the error.
ANR6963E Command: Query log failed.
Explanation: A server database query error occurred.
ANR6953E Command: File write error.
Explanation: An error occurred while writing to the message and provides more detail about that error.
recovery plan file.
System action: The recovery plan file was not created.
User response: Issue a QUERY ACTLOG command to
User response: Examine error messages that may have view the activity log and search for messages. If the
been displayed prior to this message and correct any error cannot be isolated and resolved, contact your
problems, if possible. Make sure that there is sufficient service representative.
space in the file system for the file. Reissue the
command after determining the cause of the error.
ANR6964E Command: Query storage pool failed.
Explanation: An server database query error occurred.
ANR6954E Command: Unable to open file 'file name'
for output.
Explanation: An error occurred while opening the
recovery plan file for output.
User response: Examine error messages that may have error cannot be isolated and resolved, contact your
been displayed prior to this message and correct any service representative.
proper authority to write to the file indicated. Reissue
ANR6965E Command: Query volume failed.
the command after determining the cause of the error.
ANR6959E Command: Plan instructions prefix
'instructions prefix' is not valid.
Explanation: The prefix specified for recovery
instructions is not valid. User response: Issue a QUERY ACTLOG command to
error cannot be isolated and resolved, contact your
User response: Reissue the command specifying a service representative.
valid prefix.
ANR6966E Command: Query database volume failed.
ANR6960E Command: Recovery plan prefix 'plan
Explanation: A server database query error occurred.
prefix ' is not valid.
Explanation: The prefix specified for the recovery plan message and provides more detail about that error.
file is too long.
User response: Reissue the command specifying a view the activity log and search for messages. If the
valid prefix. error cannot be isolated and resolved, contact your

ANR6967E Command: Query log volume failed. ANR6972E Command: Query machine failed.
Explanation: A server database query error occurred. Explanation: A server machine query error occurred.
This message always accompanies another error This message always accompanies another error
message and provides more detail about that error. message and provides more detail about that error.
System action: The recovery plan file was not created. System action: The recovery plan file was not created.
User response: Issue a QUERY ACTLOG command to User response: Issue a QUERY ACTLOG command to
view the activity log and search for messages. If the view the activity log and search for messages. If the
error cannot be isolated and resolved, contact your error cannot be isolated and resolved, contact your
service representative. service representative.
ANR6968E Command: Query volume history failed. ANR6973E Command: Query recovery media failed.
Explanation: An server database query error occurred. Explanation: A server recovery media query error
This message always accompanies another error occurred. This message always accompanies another
message and provides more detail about that error. error message and provides more detail about that
error.
view the activity log and search for messages. If the User response: Issue a QUERY ACTLOG command to
error cannot be isolated and resolved, contact your view the activity log and search for messages. If the
service representative. error cannot be isolated and resolved, contact your
ANR6969E Command: Query device class failed.
ANR6974E Command: Unable to open file file name.
This message always accompanies another error Explanation: An error occurred while PREPARE was
message and provides more detail about that error. attempting to open the local recovery plan file copy in
order to send it to the target server.
System action: The recovery plan file is not stored on
the target server.
error cannot be isolated and resolved, contact your User response: Examine error messages that may have
service representative. been displayed prior to this message and correct any
problems, if possible. Reissue the command after
ANR6970E Command: A recovery plan file is already
being created.
ANR6975E Command: Unable to read file file name.
Explanation: The server command processor will not
start a background process to execute another Explanation: An error occurred while PREPARE was
PREPARE command. attempting to read the local recovery plan file copy in
order to send it to the target server.
operation continues. System action: The recovery plan file is not stored on
the target server.
User response: Reissue the command after the first
PREPARE command has completed. User response: Examine error messages that may have
problems, if possible. Reissue the command after
ANR6971E Command: Could not delete plan file plan
file name.
Explanation: Prepare command failed but the plan file
ANR6976E Command: The recovery plan file was not
created could not be deleted.
stored on another server and the local
System action: None. copy file name cannot be deleted.
User response: Delete the plan file. Explanation: Due to a processing error, a recovery
plan file was not stored on target server and the local
copy of the plan file cannot be deleted.
System action: PREPARE processing ends.


ANR6984E Command: Out of space on sequential
media, scratch media could not be
problems, if possible. After determining the cause of
mounted. Specified device class device
the error, re-issue the PREPARE command and delete
class name; maximum capacity: number of
the local recovery plan file.
bytes bytes.
Explanation: During command PREPARE processing,
ANR6977E Command: Device class name device class
name exceeds maximum characters
writing to the sequential media. Command PREPARE
characters.
ends when there is no more space on the sequential
Explanation: The command shown has been entered media for storing data.
and specifies a device class name that is too long. The
System action: Command PREPARE processing ends.
maximum valid length for a device class name is
Server processing continues.
shown in the message.
User response: Increase the device class maximum
capacity and reissue the PREPARE command. If an
command.
object was created on the target server, issue the
User response: Reissue the command specifying a RECONCILE VOLUMES FIX=YES to delete the object
valid device class name. from the target server.
ANR6978E Command: Invalid device class device class ANR6985E Command: Error encountered in accessing
name. data storage - volume already in use.
Explanation: The specified device class cannot be used Explanation: During command command processing, a
by the command shown. Possible reasons include: volume cannot be used because it is already defined in
v The device class is not defined. a storage pool, or has been previously used by an
export, database dump, database backup, or DRM
v The device class is defined but not of type SERVER. prepare operation or is in use by another process.
v The name specified is an invalid device class name.
System action: The server does not process the ended and server operation continues.
command.
User response: Re-issue the PREPARE command.
device class.
ANR6986E Command: The DELETELATEST
parameter is only valid for volume
ANR6979E Command: Recovery plan file was not history types RPFILE or
created. Specified device class device class RPFSNAPSHOT.
name.
Explanation: The command failed because an invalid
Explanation: A recovery plan file cannot be not volume history type was specified for the TYPE=
created using the specified device class. parameter.
System action: Recovery plan file not created. System action: The command fails, and server
been displayed prior to this message and correct any User response: Re-issue the command and specify a
problems, if possible. Reissue the command, after valid type value.
ANR6987W Command: Container-copy pool volume

ANR6980E Command: Prefix prefix exceeds maximum volume name was not processed. The
characters characters. volume was in use.
Explanation: The command shown has been entered Explanation: The MOVE DRMEDIA command did not
and specifies a plan or instructions prefix that is too process volume volume name because it was in use by
long. The maximum valid length is shown in the another server operation.
message.
System action: The indicated command ends, if the
System action: The server does not process the volume was explicitly specified in the command. If a
command. volume pattern was specified in the command, the
the pattern.
shorter prefix.

ANR6988W • ANR7802E (AIX)

ANR7800I (Windows) DSMSERV generated at time
on date.
DRMEDIA command.
Explanation: The server module was generated at the
indicated date and time.
ANR6988W Command: The state, access and location
attributes of the container-copy storage System action: Server operation continues.
pool volume volume name were not
updated.
Explanation: The MOVE DRMEDIA command could
ANR7801I (AIX) Subsystem process ID is process
not update the state, access and location of volume
identifier.
volume name because it was in use by another server
operation. Explanation: The server process has the indicated
process identifier.
System action: If the volume was in an automated
library, the MOVE DRMEDIA command may have System action: Server operation continues.
checked the volume out of the library.
server continues processing the other volumes.
ANR7801I (HP-UX) Subsystem (master) process ID is
User response: Wait until the conflicting volume process identifier.
DRMEDIA command. Explanation: The server's master HP-UX process has
the indicated process identifier.
ANR7800I (AIX) DSMSERV generated at time on date. System action: Server operation continues.
Explanation: The server module was generated at the User response: None.
System action: Server operation continues. ANR7801I (Linux) Subsystem process ID is process
identifier.
Explanation: The server process has the indicated
process identifier.
ANR7800I (HP-UX) DSMSERV generated at time on
date. System action: Server operation continues.
System action: Server operation continues. ANR7801I (Solaris) Subsystem process ID is process
identifier.
Explanation: The server process has the indicated
process identifier.
ANR7800I (Linux) DSMSERV generated at time on
date. System action: Server operation continues.
System action: Server operation continues. ANR7802E (AIX) Shared memory segments for a
server running in the current directory
User response: None. already exist. The -F parameter can be
used to overwrite.
ANR7800I (Solaris) DSMSERV generated at time on Explanation: Shared memory segments are created for
date. each instance of the server based on the current
directory. This message indicates that the shared
Explanation: The server module was generated at the
memory segments already exist. A server is presently
running from the current directory or a server running
System action: Server operation continues. from the current directory ended abnormally.
User response: None. System action: The server terminates.
User response: If the server running in the current
directory terminated abnormally, start dsmserv with the

ANR7803E (AIX) • ANR7804E (Solaris)
-F parameter to force the existing shared memory User response: Examine the contents of the lock file.
segments to be overwritten. If you want to run The process ID for the server that is running is
multiple instances of the server, each instance must be recorded in this file. Two servers cannot be started from
run from a separate directory with a separate the same directory. You can remove the lock file and
dsmserv.dsk file and have separate log, database, and attempt to start the server only if the recorded process
storage volumes. ID is not currently running dsmserv. The 'ps -e'
command can be used to display processes that are
currently running. Check the permissions of the
ANR7803E (AIX) Attempt to overwrite a shared
directory and file system and ensure that there is
memory segment, as directed with the -F
appropriate permission for the instance user ID to write
parameter, FAILED.
to the file. Check that there is enough space in the file
Explanation: The server has been started with the -F system.
parameter and unsuccessfully attempted to overwrite
existing shared memory segments. This error occurs
ANR7804E (Linux) Error reason.
when the user that starts the server with -F parameter
is not the owner of the shared memory segments and Explanation: The server attempted to open,lock, or
lacks the required authority. write to the specified file The open, lock, or write
operation failed. These are some common reasons for
System action: Server terminates.
the failure.
User response: Resolve the authorization problem and Another server is already running from this directory
restart the server. and has the file open or locked.
The instance user ID does not have enough write access
to the file.
ANR7804E (AIX) Error reason. The file system is full.
Explanation: The server attempted to open,lock, or System action: Server terminates.
write to the specified file The open, lock, or write
operation failed. These are some common reasons for User response: Examine the contents of the lock file.
the failure. The process ID for the server that is running is
Another server is already running from this directory recorded in this file. Two servers cannot be started from
and has the file open or locked. the same directory. You can remove the lock file and
The instance user ID does not have enough write access attempt to start the server only if the recorded process
to the file. ID is not currently running dsmserv. The 'ps -e'
The file system is full. command can be used to display processes that are
System action: Server terminates. directory and file system and ensure that there is
User response: Examine the contents of the lock file. appropriate permission for the instance user ID to write
The process ID for the server that is running is to the file. Check that there is enough space in the file
recorded in this file. Two servers cannot be started from system.
the same directory. You can remove the lock file and
attempt to start the server only if the recorded process ANR7804E (Solaris) Error reason.
ID is not currently running dsmserv. The 'ps -e' AIX
command can be used to display processes that are Explanation: The server attempted to open,lock, or
currently running. Check the permissions of the write to the specified file The open, lock, or write
directory and file system and ensure that there is operation failed. These are some common reasons for
appropriate permission for the instance user ID to write the failure.
to the file. Check that there is enough space in the file Another server is already running from this directory
system. and has the file open or locked.
The instance user ID does not have enough write access
to the file.
ANR7804E (HP-UX) Error reason. The file system is full.
Explanation: The server attempted to open,lock, or System action: Server terminates.
operation failed. These are some common reasons for User response: Examine the contents of the lock file.
the failure. The process ID for the server that is running is
Another server is already running from this directory recorded in this file. Two servers cannot be started from
and has the file open or locked. the same directory. You can remove the lock file and
The instance user ID does not have enough write access attempt to start the server only if the recorded process
to the file. ID is not currently running dsmserv. The 'ps -e'
The file system is full. command can be used to display processes that are
System action: Server terminates. directory and file system and ensure that there is

ANR7804E (Windows) • ANR7805E (Solaris)
appropriate permission for the instance user ID to write

ANR7805E (Linux) Volume volume name is in use by
to the file. Check that there is enough space in the file
another server.
system.
Explanation: The server has attempted to open a disk
volume but has discovered that the volume is in use by
ANR7804E (Windows) Error reason.
another server.
Explanation: The server attempted to open,lock, or
System action: The open operation fails for the
volume.
operation failed. These are some common reasons for
the failure. User response: To prevent concurrent RAW volume
Another server is already running from this directory access by more than one server, files are created in the
and has the file open or locked. /tmp directory to 'lock' these volumes. The names of
The instance user ID does not have enough write access these temporary files are /tmp/
to the file. adsm.disk.dev.<volumename> where <volumename> is
The file system is full. the name of the RAW volume defined in the /dev
directory. Please note that the name for a RAW logical
System action: Server terminates.
volume as defined in Solaris is in the /dev directory
User response: Examine the contents of the lock file. with a leading 'r' character (for example, a raw volume
The process ID for the server that is running is defined in Solaris on a regular SCSI drive as
recorded in this file. Two servers cannot be started from dsk/c0t0d0s0 will be represented in the /dev directory
the same directory. You can remove the lock file and as the file /dev/rdsk/c0t0d0s0). For a REGULAR DISK
attempt to start the server only if the recorded process volume, the server automatically locks/unlocks a
ID is not currently running dsmserv. Check the volume. Different linked file names pointing to the
permissions of the directory and file system and ensure same volume will cause this message since the server
that there is appropriate permission for the instance locks the linked volume, not the link name itself.
user ID to write to the file. Check that there is enough
You may use the Solaris 'ps -ef | grep dsmserv'
space in the file system.
command to determine if other dsmserv processes are
running. You may remove the temporary lock files for
ANR7805E (AIX) Volume volume name is in use by RAW volumes and attempt to re-start the server ONLY
another server. if there are no other dsmserv processes are running.
Explanation: The server has attempted to open a disk
volume but has discovered that the volume is in use by ANR7805E (Solaris) Volume volume name is in use by
another server. another server.
System action: The open operation fails for the Explanation: The server has attempted to open a disk
volume. volume but has discovered that the volume is in use by
another server.
User response: To prevent concurrent RAW volume
access by more than one server, files are created in the System action: The open operation fails for the
/tmp directory to 'lock' these volumes. The names of volume.
these temporary files are /tmp/
User response: To prevent concurrent RAW volume
adsm.disk.dev.<volumename> where <volumename> is
access by more than one server, files are created in the
the name of the RAW volume defined in the /dev
/tmp directory to 'lock' these volumes. The names of
directory. Please note that the name for the logical
these temporary files are /tmp/
volume as defined in SMIT is represented in the /dev
adsm.disk.dev.<volumename> where <volumename> is
directory with a leading 'r' character (for example, a
the name of the RAW volume defined in the /dev
raw volume defined in SMIT as dsmstg1 will be
directory. Please note that the name for a RAW logical
represented in the /dev directory as the file
volume as defined in Solaris is in the /dev directory
/dev/rdsmstg1).
with a leading 'r' character (for example, a raw volume
You may use the AIX 'ps -e' command to determine if defined in Solaris on a regular SCSI drive as
other dsmserv processes are running. You may remove dsk/c0t0d0s0 will be represented in the /dev directory
the temporary lock files and attempt to re-start the as the file /dev/rdsk/c0t0d0s0). For a REGULAR DISK
server ONLY if there are no other dsmserv processes volume, the server automatically locks/unlocks a
running volume. Different linked file names pointing to the
same volume will cause this message since the server
locks the linked volume, not the link name itself.
You may use the Solaris 'ps -ef | grep dsmserv'
command to determine if other dsmserv processes are
running. You may remove the temporary lock files for
RAW volumes and attempt to re-start the server ONLY

ANR7806W (AIX) • ANR7807W (Linux)
if there are no other dsmserv processes are running. authorization to open the file and not being the file's
owner.
ANR7806W (AIX) Unable to open file file.
ANR7806W (Windows) Unable to open file file.
Explanation: The server was unable to open the
indicated file. Explanation: The server was unable to open the
indicated file.
System action: The operation that was to use the
indicated file fails. A subsequent unnumbered message System action: The operation that was to use the
had details from the system. indicated file fails. A subsequent unnumbered message
had details from the system.
User response: Determine the reason for being unable
to open the file and re-attempt the operation. Common User response: Determine the reason for being unable
reasons for being unable to open the file include to open the file and re-attempt the operation. Common
providing the wrong name, having insufficient reasons for being unable to open the file include
authorization to open the file and not being the file's providing the wrong name, having insufficient
owner. authorization to open the file and not being the file's
owner. The file may be already opened by the server or
another program.
ANR7806W (HP-UX) Unable to open file file.
ANR7807W (AIX) Unable to get information for file
indicated file.
file.
Explanation: The server was unable to get information
indicated file fails. A subsequent unnumbered message
about the indicated file.
indicated file fails. A subsequent, unnumbered message
to open the file and re-attempt the operation. Common
has details from the system.
reasons for being unable to open the file include
providing the wrong name, having insufficient User response: Determine the reason for being unable
authorization to open the file and not being the file's to access the file and re-attempt the operation.
owner. Common reasons for being unable to access the file
include providing the wrong name, having insufficient
authorization to open the file and not being the file's
ANR7806W (Linux) Unable to open file file.
owner.
indicated file.
ANR7807W (HP-UX) Unable to get information for
System action: The operation that was to use the file file.
indicated file fails. A subsequent unnumbered message
about the indicated file.
providing the wrong name, having insufficient
authorization to open the file and not being the file's User response: Determine the reason for being unable
owner. to access the file and re-attempt the operation.
Common reasons for being unable to access the file
ANR7806W (Solaris) Unable to open file file.
Explanation: The server was unable to open the owner.
indicated file.
System action: The operation that was to use the ANR7807W (Linux) Unable to get information for
indicated file fails. A subsequent unnumbered message file file.
User response: Determine the reason for being unable about the indicated file.

ANR7807W (Solaris) • ANR7810E (Solaris)
User response: Determine the reason for being unable User response: Ensure that the Library Attach module
to access the file and re-attempt the operation. is installed to the system.
Common reasons for being unable to access the file
ANR7809I (AIX) Using scheduling policy policy.
authorization to open the file, not being the file's
owner, or too many soft links to the file. If trying to Explanation: All threads in the server will use the
access a RAW partition, the server must be started with specified scheduling policy.
superuser privileges.
System action: Operations continue.
ANR7807W (Solaris) Unable to get information for User response: None

file file.
Explanation: The server was unable to get information ANR7810W (AIX) Unable to create a new child
about the indicated file. process.
System action: The operation that was to use the Explanation: The server cannot create a new child
indicated file fails. A subsequent, unnumbered message thread.
has details from the system. System action: Server processing continues. Other
User response: Determine the reason for being unable error messages from the server component are
to access the file and re-attempt the operation. displayed.
Common reasons for being unable to access the file User response: Ensure that sufficient paging space is
include providing the wrong name, having insufficient available for AIX. If the server has been started from a
authorization to open the file, not being the file's non-root user ID, ensure that the AIX process limit per
owner, or too many soft links to the file. If trying to user is sufficient for the server. The server requires
access a RAW partition, the server must be started with approximately 24 processes, in addition to one process
superuser privileges. per client session, and one process for each background
operation. Each thread started by the server is an AIX
ANR7807I (Windows) Oracle Library Attach module process. To change the number of processes per user,
module name has been loaded. use the SMIT menus for System Environment, and
choose Change / Show Characteristics of Operating
Explanation: The module indicated has been System. You may also use SMIT to determine if the
successfully loaded. Operations involving this module number of applications is causing a memory shortage.
may now be performed by the server. It may be necessary to decrease the maximum number
of client sessions by changing the MAXSESSIONS
System action: The server now supports ACSLS
option in the server options file.
functions that depend on this module.
ANR7810E (HP-UX) Error creating console input
thread.
ANR7808W (AIX) root user authority required for
Explanation: Unable to start console input thread.
non-default scheduling policy.
System action: Server operation stops.
Explanation: The server was unable to use the
scheduling policy specified in the options file. The User response: See other issued messages.
server must be running with root authority to use any
scheduling policy other than the default.
ANR7810E (Linux) Error creating console input
System action: Operation continues but with the thread.
default scheduling policy.
Explanation: Unable to start console input thread.
User response: Run the server with root authority or
don't specify a scheduling policy in the options file. System action: Server operation stops.
User response: See other issued messages.
ANR7808W (Windows) Oracle Library Attach
module module name is not available ANR7810E (Solaris) Error creating console input
from the system. thread.
Explanation: The server attempted to load the Library Explanation: Unable to start console input thread.
Attach module. However, this module is not installed
to the system. System action: Server operation stops.
System action: Server operation continues, but User response: See other issued messages.
without ACSLS function.

ANR7811I (AIX) • ANR7813W (Linux)
ANR7811I (AIX) Using instance directory instance ANR7812E (Linux) Insufficient memory to buffer
directory. console input. The following input line
was discarded: discarded console input.
Explanation: The server is operating out of the
indicated directory. Explanation: An error occurs during an attempt to
allocate a buffer to hold the specified console input.
System action: The console input is discarded.
User response: Ensure that there is sufficient paging
space. It may be necessary to reduce the maximum
ANR7811E (HP-UX) Insufficient memory for console
number of client sessions by changing the
initialization.
MAXSESSIONS option in the server options file.
Explanation: The server is unable to allocate enough
memory for console initialization.
ANR7812E (Solaris) Insufficient memory to buffer
System action: Server operation stops. console input. The following input line
space for HP-UX. It may be necessary to reduce the Explanation: An error occurs during an attempt to
maximum number of client sessions by changing the allocate a buffer to hold the specified console input.
ANR7811E (Linux) Insufficient memory for console
space for Oracle Solaris. It may be necessary to reduce
initialization.
the maximum number of client sessions by changing
Explanation: The server is unable to allocate enough the MAXSESSIONS option in the server options file.
System action: Server operation stops. ANR7813W (AIX) The server mode-bit server is not
supported on a kernel mode-bit kernel.
space. It may be necessary to reduce the maximum Explanation: The 32-bit server is supported only when
number of client sessions by changing the running with the 32-bit kernel, and the 64-bit server is
MAXSESSIONS option in the server options file. supported only when running the 64-bit kernel.
ANR7811E (Solaris) Insufficient memory for console
User response: You must match the server mode with
initialization.
the kernel mode by either switching the kernel mode or
Explanation: The server is unable to allocate enough installing the correct server fileset.
System action: Server operation stops. ANR7813W (Linux) Unable to create a new child
thread.
space for Oracle Solaris. It may be necessary to reduce Explanation: The server cannot create a new child
the maximum number of client sessions by changing thread.
the MAXSESSIONS option in the server options file.
System action: Server processing continues. Other
error messages from the server component are
ANR7812E (HP-UX) Insufficient memory to buffer displayed.
console input. The following input line
User response: Ensure that sufficient swap space is
available for Solaris. The amount of swap available can
Explanation: An error occurs during an attempt to be obtained by executing 'swap -l'. If the number of
allocate a buffer to hold the specified console input. free blocks is low, you can add swap files while the
system is running by executing 'mkfile' and then 'swap
System action: The console input is discarded. -a'. See the Solaris man pages on 'mkfile' and 'swap' for
User response: Ensure that there is sufficient paging more details.
space for HP-UX. It may be necessary to reduce the If the server has been started from a non-root user ID,
maximum number of client sessions by changing the ensure that the process limit per user is sufficient to
MAXSESSIONS option in the server options file. accomodate the server. You can tune the 'maxusers=##'
parameter in the /etc/system file to increase the
number of number of users that can be on the system
at one time. This will also force the kernel to allocate

ANR7813W (Solaris) • ANR7820W (Windows)
more memory/swap for user-processes. User response: None.

A system reboot with the 'reconfigure' option is
required for the new user settings to take effect. It may ANR7820E (AIX) Insufficient memory to buffer
be necessary to decrease the maximum number of console input; the following input line
client sessions by changing the MAXSESSIONS option was discarded: discarded console input.
in the server options file.
Explanation: An error occurs during an attempt to
allocate a buffer large enough to read console input.
ANR7813W (Solaris) Unable to create a new child
thread.
User response: Ensure that sufficient paging space is
Explanation: The server cannot create a new child
available for AIX. You may also use SMIT to determine
thread.
if the number of applications is causing a memory
System action: Server processing continues. Other shortage. It may be necessary to decrease the maximum
error messages from the server component are number of client sessions by changing the
displayed. MAXSESSIONS option in the server options file.
User response: Ensure that sufficient swap space is
available for Solaris. The amount of swap available can ANR7820S (HP-UX) Server thread thread ID
be obtain by executing 'swap -l'. If the number of free terminated in response to program
blocks is low, you can add swap files while the system abort.
is running by executing 'mkfile' and then 'swap -a'. See
Explanation: The thread has ended due to a program
the Solaris man pages on 'mkfile' and 'swap' for more
abort.
details. If the server has been started from a non-root
user ID, ensure that the Solaris process limit per user is System action: The server completes termination
sufficient for the server. You can tune the 'maxusers=##' processing.
parameter in the /etc/system file to increase the
number of number of users that can be on the system User response: Note the associated messages and
at one time. This will also force the kernel to allocate contact your service representative.
more memory/swap for user-processes. A system
reboot with the 'reconfigure' option is required for the ANR7820S (Linux) Thread thread ID terminated in
new user settings to take effect. It may be necessary to response to program abort.
decrease the maximum number of client sessions by
changing the MAXSESSIONS option in the server Explanation: The thread has ended due to a program
options file. abort.
System action: The server completes termination
ANR7814I (HP-UX) Using instance directory instance processing.
directory. User response: Note the associated messages and call
Explanation: The server is operating out of the your service representative.
indicated directory.
System action: Server processing continues. ANR7820S (Solaris) Server thread thread ID
terminated in response to program
User response: None. abort.
ANR7814I (Linux) Using instance directory instance abort.
directory.
Explanation: The server is operating out of the processing.
indicated directory.
User response: Note the associated messages and call
System action: Server processing continues. your service representative.
ANR7820W (Windows) Insufficient Space Available
ANR7814I (Solaris) Using instance directory instance for file file name.
directory. Explanation: The server was attempting to create a file
Explanation: The server is operating out of the with the indicated name. There was insufficient space
indicated directory. for the file on the disk.
System action: Server processing continues. System action: Server processing continues. The file
creation request fails.

ANR7821I (HP-UX) • ANR7823E (AIX)
User response: Free additional space on the drive to

ANR7822I (HP-UX) Server thread thread ID
accomodate the file, specify a file name on a drive with
terminated in response to server
sufficient space, or change the space request to a value
shutdown.
consistent with the drive. Retry the operation.
Explanation: The thread has ended due to a server
shutdown.
ANR7821I (HP-UX) Server thread thread ID
terminated in response to external System action: The server completes termination
signal. processing.
Explanation: The thread has ended due to an external User response: None.
signal.
System action: The server completes termination ANR7822I (Linux) Thread thread ID terminated in
processing. response to server shutdown.
User response: None. Explanation: The thread has ended due to a server
shutdown.
ANR7821I (Linux) Thread thread ID terminated in System action: The server completes termination
response to external signal. processing.
signal.
System action: The server completes termination ANR7822I (Solaris) Server thread thread ID
processing. terminated in response to server
shutdown.
shutdown.
ANR7821I (Solaris) Server thread thread ID
terminated in response to external System action: The server completes termination
signal. processing.
signal.
System action: The server completes termination ANR7822W (Windows) File Already exists when
processing. creating volume file name.
User response: None. Explanation: The server was attempting to create a file
with the indicated name. The file already exists.
ANR7821W (Windows) Unable to create directory System action: Server processing continues. The file
when creating volume file name. creation request fails.
Explanation: The server was attempting to create a file User response: Specify a new file name. The server
with the indicated name. A new directory was being will not use an existing file name when creating a file.
created as well, but its creation failed.
System action: Server processing continues. The file ANR7823E (AIX) Insufficient memory for console
creation request fails. initialization.
User response: Specify a file name in an existing Explanation: Unable to allocate enough memory for
directory or change the name request to specify a console initialization.
different directory name.
ANR7822E (AIX) Error creating console input thread.
Explanation: Unable to start console input thread. if the number of applications is causing a memory
shortage. It may be necessary to decrease the maximum
User response: See other issued messages. MAXSESSIONS option in the server options file.

ANR7823S (Linux) • ANR7825W (Windows)
ANR7823S (Linux) Internal error internal error ANR7824S (Solaris) Server operation terminated.
detected.
Explanation: An error occurs that causes server
Explanation: An internal error is detected during operation to stop.
server initialization or operation.
User response: Retry the failing operation. If the
operation fails again, review additional information
ANR7824W (Windows) Unable to write volume file
that is available for this message: Search for
name.
"ANR7823S" in the product information
(http://www.ibm.com/support/knowledgecenter/ Explanation: The server was attempting to create a file
SSEQVQ/). with the indicated name. The server was able to
partially write to the file before running out of space.
ANR7823W (Windows) Unable to create file file name. System action: The server continues processing. The
file creation request fails. The file is still present on the
Explanation: The server was attempting to create a file
system.
with the indicated name. The system reported an error
in creating the file. User response: Specify a new file name where there is
sufficient space.
System action: The server continues processing. The
file creation request fails.
ANR7825E (Linux) Server unable to allocate a shared
User response: Specify a new file name.
memory segment of size Client requested
shared memory size.
ANR7824E (AIX) Error loading Async I/O support
Explanation: A shared memory client has requested a
module.
shared memory segment size that Solaris is unable to
Explanation: The server attempted to load the Async fulfill.
I/O support module, but the load failed. Refer to
System action: Client is not allowed to logon
accompanying error message for details on the load
failure. User response: See the shared memory tuning guide
for Solaris (an Oracle document). You may need to
increase the number/size of shared memory segments
without Async I/O support.
and/or message queues.
User response: Ensure that the correct support
module exists in the server bin directory and that the
ANR7825E (Solaris) Server unable to allocate a
aio subsystem has been configured on AIX, and that
shared memory segment of size Client
AIX was rebooted after the configuration.
requested shared memory size.
Explanation: A shared memory client has requested a
ANR7824S (HP-UX) Server operation terminated.
shared memory segment size that Solaris is unable to
Explanation: An error occurs that causes server fulfill.
operation to stop.
System action: Client is not allowed to logon
User response: See the shared memory tuning guide
User response: Contact your service representative. for Solaris (an Oracle document). You may need to
increase the number/size of shared memory segments
and/or message queues.
ANR7824S (Linux) Server operation terminated.
Explanation: An error occurs that causes server
ANR7825W (Windows) Unable to create volume file
operation to stop.
name. Return code= return code.
User response: Contact your service representative. with the indicated name. The attempt failed with the
indicated return code. The return code is an internal
code from the server.
User response: Specify a new file name. The return

ANR7826W (Windows) • ANR7832E (Solaris)
code may also be provided to your service function in the Oracle manuals for further details on
representative for interpretation. filesystems.
ANR7826W (Windows) Creation of Volume file name ANR7831E (Solaris) raw partition name has an existing
failed. Process was cancelled. filesystem.
Explanation: The server was attempting to create a file Explanation: The RAW partition specified has an
with the indicated name. The attempt was cancelled by existing Solaris file system on it. Writing to this
a cancel process command. partition will most likely destroy this filesystem.
System action: The server continues processing. The System action: Warn the user that an existing
file creation request fails. filesystem for the raw partition specified may be
destroyed if written to.
User response: The DEFINE command may be
re-entered. User response: Determine if user still wants the valid
filesystem data. If not, user needs to destroy the
filesystem by either formatting the partition, create a
ANR7830E (Linux) Invalid RAW Partition Name: A
program to destroy the filesystem header information
valid raw partition name is in the form
so that the server will not be able to detect the
of /dev/.../rdsk/.../* , where ... means 0 or
filesystem header information, or rearrange the starting
more directories.
and ending blocks of a partition by using the Solaris
Explanation: Use the proper format for specifying a format() command. The user can read the format()
Raw partition. The ... means zero or more directories. function in the Oracle Solaris manuals for further
details on filesystems.
System action: Inform the user to use the right RAW
partition specification.
ANR7832I (AIX) The thread process ID terminated
User response: Have user reenter the RAW partition with exit code program exit code.
with the proper partition name.
Explanation: The process has ended with the
indicated exit code. This error is due to the problem
ANR7830E (Solaris) Invalid RAW Partition Name: A caused and indicated by a preceding message.
valid raw partition name is in the form
of /dev/.../rdsk/.../* , where ... means 0 or System action: The server completes termination
more directories. processing.
Explanation: Use the proper format for specifying a User response: None.
Raw partition. The ... means zero or more directories.
System action: Inform the user to use the right RAW ANR7832E (Linux) raw partition name corresponds to a
partition specification. protected filesystem, such as / or /usr.
User response: Have user reenter the RAW partition Explanation: The RAW partition specified has an
with the proper partition name. existing file system on it. This filesystem is the / or
/usr partition. If the SERVER writes to it, it will most
likely crash the whole operating system.
ANR7831E (Linux) raw partition name has an existing
filesystem. System action: Disallow access to this raw partition.
Explanation: The RAW partition specified has an User response: Have user specify another RAW
existing Solaris file system on it. Writing to this partition that is not the / or /usr. It may be possible
Partition may/and most likely will destroy this that this is not the actual / or /usr partition of the boot
filesystem. disk. Check, using the Solaris format() command, if
your partition name tag is labeled incorrectly as / or
System action: Warn the user that an existing /usr.
filesystem for the raw partition specified may be
destroyed if written to.
ANR7832E (Solaris) raw partition name corresponds to
User response: Determine if user still wants the valid a protected filesystem, such as / or /usr.
filesystem data. If not, user needs to destroy the
filesystem by either formatting the partition, create a Explanation: The RAW partition specified has an
program to destroy the filesystem header information existing file system on it. This filesystem is the / or
so that the server will not be able to detect the /usr partition. If the SERVER writes to it, it will most
filesystem header information, or rearrange the starting likely crash the whole operating system.
and ending blocks of a partition by using the Solaris
System action: Disallow access to this raw partition.
format() command. The user can read the format()

ANR7833S (AIX) • ANR7835E (Linux)
User response: Have user specify another RAW write into the 0th cylinder. If allowed, the disk label
partition that is not the / or /usr. It may be possible would be corrupted.
that this is not the actual / or /usr partition of the boot
System action: Disallow access to this raw partition.
disk. Check, using the Solaris format() command, if
your partition name tag is labeled incorrectly as / or User response: Have the system administrator change
/usr. the starting cylinder of this partition to a number
greater than 0.
ANR7833S (AIX) The process thread ID terminated in
response to program abort. ANR7834E (Solaris) Specified raw partition name raw
partition cannot contain the 0th disk
cylinder.
abort.
Explanation: The raw partition specified has the 0th
disk cylinder. The server should not be allowed to
processing.
write into the 0th cylinder. It allowed, the disk label
User response: None. would be corrupted.
System action: Disallow access to this raw partition
ANR7833E (Linux) symbolic links has too many
User response: Have the system administrator change
symbolic links - the maximum
the starting cylinder of this partition to a number
allowable is 10.
greater than 0.
Explanation: The file specified has too many symbolic
links. The server will follow at most 10 links before
ANR7834I (Windows) The server thread thread ID (tid
ending this symbolic link name resolution.
Windows NT thread ID) terminated in
System action: Disallow access to this file. response to external signal.
User response: Have the user specify the actual file, Explanation: The thread has terminated due to an
where the file is not a symbolic link. Using ls -l, one external signal.
can see if the file is a symbolic link.
processing.
ANR7833E (Solaris) symbolic links has too many
symbolic links - the server only
supports a maximum of 10.
ANR7835I (AIX) The server thread thread ID
Explanation: The file specified has too many symbolic
terminated in response to server
links. The server will follow at most 10 links before
shutdown.
ending this symbolic link name resolution.
System action: Disallow access to this file
shutdown.
User response: Have the user specify the actual file,
where the file is not a symbolic link. Using ls -l, one
processing.
can see if the file is a symbolic link.
ANR7834I (AIX) The thread thread ID terminated in
response to external signal. ANR7835E (Linux) Specified raw partition name raw
partition is too big for this operating
Explanation: The thread has ended due to an external
system to handle.
signal.
Explanation: The raw partition specified has greater
than 2GB and the operating system is running below
processing.
Solaris 2.6. Operating system below Solaris 2.6 cannot
User response: None. handle files natively more than 2GB. For operating
system that is at Solaris 2.6 or above, the limit is 1TB.
ANR7834E (Linux) Specified raw partition name raw System action: Disallow access to this raw partition.
partition cannot contain the 0th disk
cylinder.
the RAW partition size to be less than 2GB (4194303
Explanation: The raw partition specified has the 0th 512-byte disk blocks) for Solaris 2.5.1 or below, less
disk cylinder. The server should not be allowed to than 1TB (2147483647 512-byte disk blocks) for Solaris
2.6 and above.

ANR7835E (Solaris) • ANR7843W (HP-UX)
User response: You must extend the log file when you
ANR7835E (Solaris) Specified raw partition name raw
receive ANR7837S, LOGSEG871 errors.
partition is too big for this operating
system to handle. Review additional information that is available for this
message: Search for "ANR7837S" in the product
Explanation: The raw partition specified has greater
information (http://www.ibm.com/support/
than 2GB and the operating system is running below
knowledgecenter/SSEQVQ/).
Solaris 2.6. Operating system below Solaris 2.6 cannot
handle files natively more than 2GB. For operating
system that is at Solaris 2.6 or above, the limit is 1TB. ANR7838S (AIX) Server operation terminated.
System action: Disallow access to this raw partition Explanation: An error occurs that causes server
operation to stop.
the RAW partition size to be less than 2GB (4194303 System action: Server operation stops.
512-byte disk blocks) for Solaris 2.5.1 or below, less
than 1TB (2147483647 512-byte disk blocks) for Solaris User response: Contact your service representative.
2.6 and above.
ANR7841S (AIX) Insufficient kernel memory
ANR7835I (Windows) The server thread thread ID (tid available.
Windows NT thread ID) terminated in Explanation: An error occurs due to insufficient kernel
response to server shutdown. memory.
Explanation: The thread has terminated due to a System action: Server operation stops.
server shutdown.
processing.
ANR7842S (AIX) Monitor kernel extension not
User response: None. initialized.
Explanation: The monitor kernel extension is not
ANR7836S (AIX) Server initialization terminated. initialized.
Explanation: An error occurs that causes server System action: Server operation stops.
initialization to end.
User response: Review additional information that is ANR7843W (AIX) Unable to determine real memory
available for this message: Search for "ANR7836S" in size.
the product information (http://www.ibm.com/
support/knowledgecenter/SSEQVQ/). Explanation: The server checks the amount of real
memory in the system to optimize use of storage in the
database buffer pool. The server uses Object Data
ANR7837S (AIX) Internal error internal error was Manager (ODM) to determine how much real memory
detected. is installed on the system. The routines used to call
Explanation: An internal error was detected during ODM failed or were unable to return the real memory
server initialization or operation. size.
System action: The server stops. System action: Server operation continues. The server
allows the data base buffer pool size to grow withoug
User response: You must extend the log file when you taking into account real memory.
receive ANR7837S, LOGSEG871 errors.
User response: The server may need to run as a root
Review additional information that is available for this user to obtain this information.
message: Search for "ANR7837S" in the product
information (http://www.ibm.com/support/
knowledgecenter/SSEQVQ/). ANR7843W (HP-UX) Unable to determine real
memory size.
ANR7837S (Windows) Internal error internal error was Explanation: The server checks the amount of real
detected. memory in the system to optimize use of storage in the
database buffer pool. The routines used to obtain this
Explanation: An internal error was detected during information returned a failing return code or were
server initialization or operation. unable to return the real memory size.
System action: The server stops. System action: Server operation continues. The server

ANR7843W (Linux) • ANR7855W (Windows)
allows the data base buffer pool size to grow withoug User response: None.
taking into account real memory.
User response: The server may need to run as a root ANR7850I (AIX) The process process ID has
user to obtain this information. terminated on signal signal number (signal
name).
ANR7843W (Linux) Unable to determine real Explanation: The specified process has ended due to
memory size. the specified signal.
Explanation: The server checks the amount of real System action: Server operation stops.
memory in the system to optimize use of storage in the
database buffer pool. The server uses Object Data
Manager (ODM) to determine how much real memory
is installed on the system. The routine s used to call ANR7851S (AIX) Error resetting handler for signal
ODM failed or were unable to return the real memory signal number (signal name).
size.
Explanation: An error occurs resetting the specified
System action: Server operation continues. The server signal handler.
allows the data base buffer pool size to grow withoug
taking into account real memory. System action: Server operation stops.
User response: The server may need to run as a root User response: Contact your service representative.
user to obtain this information.
ANR7852I (Windows) The current process affinity
ANR7843W (Solaris) Unable to determine real mask is: 0xThe process affinity mask..
memory size. Explanation: The server is running on the processors
Explanation: The server checks the amount of real indicated by the mask.
memory in the system to optimize use of storage in the System action: Server operation continues.
database buffer pool. The routines used to obtain this
information returned a failing return code or were User response: None.
unable to return the real memory size.
System action: Server operation continues. The server ANR7853W (Windows) Could not obtain the current
allows the data base buffer pool size to grow withoug process affinity mask. Reason: NT return
taking into account real memory. code..
User response: The server may need to run as a root Explanation: A problem was encounterd while
user to obtain this information. obtaining the current process affinity.
ANR7843W (Windows) Unable to determine real User response: None.
memory size.
Explanation: The server checks the amount of real ANR7854W (Windows) The process affinity mask
memory in the system to optimize use of storage in the (0xAffinity mask.) specified in
database buffer pool. The routines used to obtain this dsmserv.opt is out of range.
information returned a failing return code or were
unable to return the real memory size. Explanation: The affinity mask value was out of
range.
System action: Server operation continues. The server
allows the data base buffer pool size to grow withoug System action: Server operation continues.
taking into account real memory. User response: None.
user to obtain this information. ANR7855W (Windows) Could not set new process
affinity mask. Reason: NT return code.
ANR7849I (AIX) Server operation terminated - kernel Explanation: A problem was encounterd in setting a
extension has been reset. new process affinity mask.
Explanation: The kernel extension has been System action: Server operation continues.
reinitialized by the server in response to a previous
condition for which a message has been issued. User response: None.

ANR7856W (Windows) • ANR7860W (Linux)
ANR7856W (Windows) The affinity mask (0xNT ANR7859W (Solaris) Error reading from standard
return code.) was set to a value other than input.
what was requested
Explanation: A new affinity mask was set but on read from standard input.
verification it was found not to match what was
System action: The console input thread is terminated.
requested.
User response: This is normal if the server is running
as part of the installation, in a cron job, or is started in
User response: None. the background. This can occur if the server is started
in a telnet or ssh session and that session is killed
effectively creating a background process. If this is
ANR7859W (AIX) Error reading from standard input.
unintended, stop the server and restart in the
Explanation: An error occurs during an attempt to foreground.
read from standard input.
System action: The console input thread is terminated. ANR7860W (AIX) Insufficient Space Available for
file file name.
User response: This is normal if the server is running
as part of the installation, in a cron job, or is started in Explanation: The server was attempting to create a file
the background. This can occur if the server is started with the indicated name. There was insufficient space
in a telnet or ssh session and that session is killed for the file in the filesystem.
foreground.
ANR7859W (HP-UX) Error reading from standard
input.
ANR7860W (HP-UX) Insufficient Space Available for
System action: The console input thread is terminated. file file name.
User response: This is normal if the server is running Explanation: The server was attempting to create a file
as part of the installation, in a cron job, or is started in with the indicated name. There was insufficient space
the background. This can occur if the server is started for the file in the filesystem.
foreground. User response: Free additional space on the drive to
ANR7859W (Linux) Error reading from standard
input.
ANR7860W (Linux) Insufficient Space Available for
file file name.
System action: The console input thread is terminated.
User response: This is normal if the server is running with the indicated name. There was insufficient space
as part of the installation, in a cron job, or is started in for the file in the filesystem.
the background. This can occur if the server is started
unintended, stop the server and restart in the User response: Free additional space on the drive to
foreground. accomodate the file, specify a file name on a drive with

ANR7860W (Solaris) • ANR7863W (AIX)

ANR7860W (Solaris) Insufficient Space Available for
file file name.
User response: Specify a file name in an existing
directory or or change the name request to specify a
with the indicated name. There was insufficient space
for the file in the filesystem.
ANR7862W (AIX) File Already exists when creating
volume file name.
consistent with the drive. Retry the operation. System action: The server continues processing. The
ANR7861W (AIX) Unable to create directory when User response: Specify a new file name. The server
creating volume file name. will not use an existing file name when creating a file.
with the indicated name. A new directory was being ANR7862W (HP-UX) File Already exists when
created as well, but its creation failed. creating volume file name.
System action: The server continues processing. The Explanation: The server was attempting to create a file
file creation request fails. with the indicated name. The file already exists.
User response: Specify a file name in an existing System action: The server continues processing. The
directory or or change the name request to specify a file creation request fails.
User response: Specify a new file name. The server
will not use an existing file name when creating a file.
ANR7861W (HP-UX) Unable to create directory when
creating volume file name.
ANR7862W (Linux) File Already exists when creating
Explanation: The server was attempting to create a file volume file name.
with the indicated name. A new directory was being
created as well, but its creation failed. Explanation: The server was attempting to create a file
file creation request fails. System action: The server continues processing. The
User response: Specify a file name in an existing
directory or or change the name request to specify a User response: Specify a new file name. The server
different directory name. will not use an existing file name when creating a file.
ANR7861W (Linux) Unable to create directory when ANR7862W (Solaris) File Already exists when
creating volume file name. creating volume file name.
Explanation: The server was attempting to create a file Explanation: The server was attempting to create a file
with the indicated name. A new directory was being with the indicated name. The file already exists.
created as well, but its creation failed. System action: The server continues processing. The
System action: The server continues processing. The file creation request fails.
file creation request fails. User response: Specify a new file name. The server
User response: Specify a file name in an existing will not use an existing file name when creating a file.
directory or or change the name request to specify a
different directory name. ANR7863W (AIX) Unable to create file file name.
ANR7861W (Solaris) Unable to create directory when with the indicated name. The system reported an error
creating volume file name. in creating the file.
Explanation: The server was attempting to create a file System action: The server continues processing. The
with the indicated name. A new directory was being file creation request fails.
created as well, but its creation failed.

ANR7863W (HP-UX) • ANR7865W (Linux)
ANR7863W (HP-UX) Unable to create file file name. ANR7864W (Linux) Unable to write volume file name.
Explanation: The server was attempting to create a file Explanation: The server was attempting to create a file
with the indicated name. The system reported an error with the indicated name. The server was able to
in creating the file. partially write to the file before running out of space.
System action: The server continues processing. The System action: The server continues processing. The
file creation request fails. file creation request fails. The file is still present on the
system.
User response: Specify a new file name where there is
sufficient space.
ANR7863W (Linux) Unable to create file file name.
ANR7864W (Solaris) Unable to write volume file
with the indicated name. The system reported an error
name.
in creating the file.
with the indicated name. The server was able to
file creation request fails. The file is still present on the
ANR7863W (Solaris) Unable to create file file name. system.
Explanation: The server was attempting to create a file User response: Specify a new file name where there is
with the indicated name. The system reported an error sufficient space.
in creating the file.
System action: The server continues processing. The ANR7865W (AIX) Unable to create volume file name.
file creation request fails. Return code=return code.
User response: Specify a new file name. Explanation: The server was attempting to create a file
with the indicated name. The attempt failed with the
indicated return code. The return code is an the server
ANR7864W (AIX) Unable to write volume file name. internal code.
Explanation: The server was attempting to create a file System action: The server continues processing. The
with the indicated name. The server was able to file creation request fails.
System action: The server continues processing. The code may also be provided to your service
file creation request fails. The file is still present on the representative for interpretation.
system.
User response: Specify a new file name where there is ANR7865W (HP-UX) Unable to create volume file
sufficient space. name. Return code=return code.
ANR7864W (HP-UX) Unable to write volume file with the indicated name. The attempt failed with the
name. indicated return code. The return code is a server
Explanation: The server was attempting to create a file internal code.
with the indicated name. The server was able to System action: The server continues processing. The
partially write to the file before running out of space. file creation request fails.
System action: The server continues processing. The User response: Specify a new file name. The return
file creation request fails. The file is still present on the code may also be provided to your service
system. representative for interpretation.
User response: Specify a new file name where there is
sufficient space. ANR7865W (Linux) Unable to create volume file
name. Return code=return code.
indicated return code. The return code is an internal
code from the server.

ANR7865W (Solaris) • ANR7867I (Linux)

ANR7866W (Solaris) Creation of Volume file name
failed. Process was cancelled.
code may also be provided to your service
with the indicated name. The attempt was cancelled by
representative for interpretation.
a cancel process command.
ANR7865W (Solaris) Unable to create volume file
name. Return code=return code.
User response: The DEFINE command may be
re-entered.
indicated return code. The return code is a server
internal code. ANR7867I (AIX) file name is not a multiple of disk
block size block size. File size is file size,
but usable space is rounded down to
usable file size.
Explanation: The server was attempting to open a
code may also be provided to your service
random access file with the indicated name. The usable
representative for interpretation.
space was rounded down to the indicated value so that
the amount of space is an even multiple of the disk
ANR7866W (AIX) Creation of Volume file name block size. This facilitates improved performance in
failed. Process was cancelled. reading and writing the file.
Explanation: The server was attempting to create a file System action: The server continues processing. Some
with the indicated name. The attempt was cancelled by space in the file will go unused.
a cancel process command.
User response: No action is required. To use all space
System action: The server continues processing. The in the file, server utilities can be used to offload
file creation request fails. existing data to other volumes. The volume can then be
deleted and re-created using a multiple of the disk's
User response: The DEFINE command may be block size.
re-entered.
ANR7867I (HP-UX) file name is not a multiple of disk

ANR7866W (HP-UX) Creation of Volume file name block size block size. File size is file size,
failed. Process was cancelled. but usable space is rounded down to
Explanation: The server was attempting to create a file usable file size.
with the indicated name. The attempt was cancelled by Explanation: The server was attempting to open a
a cancel process command. random access file with the indicated name. The usable
System action: The server continues processing. The space was rounded down to the indicated value so that
file creation request fails. the amount of space is an even multiple of the disk
block size. This facilitates improved performance in
User response: The DEFINE command may be reading and writing the file.
re-entered.
System action: The server continues processing. Some
space in the file will go unused.
ANR7866W (Linux) Creation of Volume file name
failed. Process was cancelled. User response: No action is required. To use all space
in the file, server utilities can be used to offload
Explanation: The server was attempting to create a file existing data to other volumes. The volume can then be
with the indicated name. The attempt was cancelled by deleted and re-created using a multiple of the disk's
a cancel process command. block size.
file creation request fails. ANR7867I (Linux) file name is not a multiple of disk
User response: The DEFINE command may be block size block size. File size is file size,
re-entered. but usable space is rounded down to
usable file size.
Explanation: The server was attempting to open a
random access file with the indicated name. The usable

ANR7867I (Solaris) • ANR7869W (Linux)
block size. This facilitates improved performance in

ANR7868E (Linux) The server is unable to open or
reading and writing the file.
lock the file name file.
Explanation: The server attempted to open or lock the
instance lock file. The open or lock operation failed.
existing data to other volumes. The volume can then be User response: Ensure that the server is being
deleted and re-created using a multiple of the disk's initialized from the correct instance directory and that
block size. this server instance is not running. Ensure that the
instance owner has appropriate permissions to read
and write files on the specified path.
ANR7867I (Solaris) file name is not a multiple of disk
block size block size. File size is file size,
but usable space is rounded down to ANR7868E (Solaris) The server is unable to open or
usable file size. lock the file name file.
Explanation: The server was attempting to open a Explanation: The server attempted to open or lock the
random access file with the indicated name. The usable instance lock file. The open or lock operation failed.
block size. This facilitates improved performance in User response: Ensure that the server is being
reading and writing the file. initialized from the correct instance directory and that
this server instance is not running. Ensure that the
ANR7869W (AIX) Unable to create volume file name
existing data to other volumes. The volume can then be
with a format size of format size
deleted and re-created using a multiple of the disk's
megabytes.
block size.
Explanation: The server created a volume with the
indicated name, but the size of the volume is less than
ANR7868E (AIX) The server is unable to open or
the specified format size.
Explanation: The server attempted to open or lock the
volume is created, but the format size is not correct.
instance lock file. The open or lock operation failed.
User response: Due to an environment limitation on
the operating system, the format size of the volume is
User response: Ensure that the server is being less than the size that was specified. Update the
initialized from the correct instance directory and that operating system environment limitation and issue the
this server instance is not running. Ensure that the command again.
ANR7869W (Linux) Unable to create volume file name
with a format size of format size
ANR7868E (HP-UX) The server is unable to open or megabytes.
Explanation: The server created a volume with the
Explanation: The server attempted to open or lock the indicated name, but the size of the volume is less than
instance lock file. The open or lock operation failed. the specified format size.
System action: Server initialization fails. System action: The server continues processing. The
volume is created, but the format size is not correct.
User response: Ensure that the server is being
initialized from the correct instance directory and that User response: Due to an environment limitation on
this server instance is not running. Ensure that the the operating system, the format size of the volume is
instance owner has appropriate permissions to read less than the size that was specified. Update the
and write files on the specified path. operating system environment limitation and issue the
command again.

ANR7870W (AIX) • ANR8196I (Linux)
clients using the SSL TCP/IP protocol on the indicated

ANR7870W (AIX) Unable to initialize odm query.
port number.
Error message from odm is odm message.
Explanation: The server uses the AIX Object Data
Manager (ODM) to check information about AIX. For User response: None.
example, the server uses ODM to detemine how much
real memory is installed on the system. The routine
used to initialize an ODM query failed. ODM returned ANR8195I (Solaris) The SSL TCP/IP Version 4 driver
an error message as indicated. is ready for connection with clients on
port port number.
makes assumptions concerning information it could not Explanation: The server can now accept sessions with
obtain. clients using the SSL TCP/IP protocol on the indicated
port number.
user to obtain this information. System action: Server operation continues.
ANR7871W (AIX) Unable to complete odm query.
Error message from odm is odm message. ANR8195I (Windows) The SSL TCP/IP Version 4
Explanation: The server uses the AIX Object Data driver is ready for connection with
Manager (ODM) to check information about AIX. For clients on port port number.
example, the server uses ODM to detemine how much Explanation: The server can now accept sessions with
real memory is installed on the system. The routine clients using the SSL TCP/IP protocol on the indicated
used to perform and ODM query failed. ODM returned port number.
an error message as indicated.
makes assumptions concerning information it could not User response: None.
obtain.
User response: The server may need to run as a root ANR8196I (AIX) The SSL TCP/IP administrative
user to obtain this information. driver is ready for connection with
clients on port port number.
ANR8195I (AIX) The SSL TCP/IP Version 4 driver is Explanation: The server can now accept sessions with
ready for connection with clients on administrative clients using the SSL TCP/IP protocol
port port number. on the indicated port number.
Explanation: The server can now accept sessions with System action: Server operation continues.
clients using the SSL TCP/IP protocol on the indicated User response: None.
port number.
System action: Server operation continues. ANR8196I (HP-UX) The SSL TCP/IP administrative
User response: None. driver is ready for connection with
ANR8195I (HP-UX) The SSL TCP/IP Version 4 driver Explanation: The server can now accept sessions with
is ready for connection with clients on administrative clients using the SSL TCP/IP protocol
clients using the SSL TCP/IP protocol on the indicated User response: None.
port number.
System action: Server operation continues. ANR8196I (Linux) The SSL TCP/IP administrative
User response: None. driver is ready for connection with
ANR8195I (Linux) The SSL TCP/IP Version 4 driver Explanation: The server can now accept sessions with
is ready for connection with clients on administrative clients using the SSL TCP/IP protocol

ANR8196I (Solaris) • ANR8199E (Linux)
ANR8196I (Solaris) The SSL TCP/IP administrative ANR8198E (Linux) The SSL environment was not
driver is ready for connection with established. The GSK module gsk module
clients on port port number. return code is gsk return code.
Explanation: The server can now accept sessions with Explanation: Initialization of the SSL environment has
administrative clients using the SSL TCP/IP protocol failed. Connections to SSL ports are not possible.
on the indicated port number.
User response: Stop and restart the server.
ANR8198E (Solaris) The SSL environment was not
ANR8196I (Windows) The SSL TCP/IP established. The GSK module gsk module
administrative driver is ready for return code is gsk return code.
connection with clients on port port
Explanation: Initialization of the SSL environment has
number.
failed. Connections to SSL ports are not possible.
Explanation: The server can now accept sessions with
administrative clients using the SSL TCP/IP protocol
on the indicated port number. User response: Stop and restart the server.
ANR8198E (Windows) The SSL environment was not
established. The GSK module gsk module
return code is gsk return code.
ANR8197W (HP-UX) A TCP/IP driver is unable to set
the window size to TCPWindowsize for a
master socket on which the server
listens. The server will use the default System action: Server operation continues.
window size for listening to sessions.
Explanation: The reason that the window size cannot
be set to the requested size might be due to a lack of
memory for TCP/IP buffers. ANR8199E (AIX) The SSL TCP/IP driver was not
initialized on port port number.
System action: Server operation continues with the
default window size. Explanation: A problem with the SSL environment
prevents IBM Spectrum Protect from establishing the
User response: If necessary, restart the server with a SSL protocol on the indicated port number.
smaller window size in the options file. To determine
the setting of the server window size System action: Server operation continues.
(TCPWindowsize), issue the QUERY OPTION User response: None
command.
ANR8199E (HP-UX) The SSL TCP/IP driver was not

ANR8198E (AIX) The SSL environment was not initialized on port port number.
return code is gsk return code. Explanation: A problem with the SSL environment
Explanation: Initialization of the SSL environment has SSL protocol on the indicated port number.
User response: None
ANR8199E (Linux) The SSL TCP/IP driver was not

ANR8198E (HP-UX) The SSL environment was not initialized on port port number.
return code is gsk return code. Explanation: A problem with the SSL environment
Explanation: Initialization of the SSL environment has SSL protocol on the indicated port number.
User response: None

ANR8199E (Solaris) • ANR8201E (Linux)

ANR8199E (Solaris) The SSL TCP/IP driver was not
initialized on port port number. User response: None.
Explanation: A problem with the SSL environment
prevents IBM Spectrum Protect from establishing the ANR8200I (Windows) TCP/IP Version 4 driver ready
SSL protocol on the indicated port number. for connection with clients on port port
number.
User response: None
clients using the TCP/IP Version 4 protocol on the
indicated port number.
ANR8199E (Windows) The SSL TCP/IP driver was
not initialized on port port number.
Explanation: A problem with the SSL environment
SSL protocol on the indicated port number. ANR8201W (AIX) Unable to initialize TCP/IP driver
- insufficient memory.
Explanation: Because the operating system rejects a
User response: None
memory allocation request, the server cannot start
communications through TCP/IP.
ANR8200I (AIX) TCP/IP Version 4 driver ready for
server cannot accept sessions from clients using the
number.
TCP/IP protocol.
if the number of applications is causing a memory
System action: Server operation continues. shortage. It may be necessary to decrease the maximum
ANR8200I (HP-UX) TCP/IP Version 4 driver ready

ANR8201E (HP-UX) Unable to initialize TCP/IP
for connection with clients on port port
driver - socket creation failed; error error
number.
code.
Explanation: The server is now able to accept sessions
Explanation: The server is unable to initialize the
with clients using the TCP/IP Version 4 protocol on the
TCP/IP driver due to a socket creation error.
TCP/IP support is inoperative.
User response: Ensure that TCP/IP is operational on
your system by using the ping command with your
ANR8200I (Linux) TCP/IP Version 4 driver ready for TCP/IP address as a target. If TCP/IP is not active on
connection with clients on port port your system, you must activate it; then halt and restart
number. the server.

clients using the TCP/IP Version 4 protocol on the ANR8201E (Linux) Unable to initialize TCP/IP driver
indicated port number. - socket creation failed; error error code.
System action: Server operation continues. Explanation: The server is unable to initialize the
TCP/IP driver due to a socket creation error.
ANR8200I (Solaris) TCP/IP Version 4 driver ready
for connection with clients on port port User response: Ensure that TCP/IP is operational on
number. your system by using the ping command with your
TCP/IP address as a target. If TCP/IP is not active on
Explanation: The server can now accept sessions with your system, you must activate it; then halt and restart
clients using the TCP/IP Version 4 protocol on the the server.

ANR8201E (Solaris) • ANR8202W (Windows)

ANR8201E (Solaris) Unable to initialize TCP/IP
your system, you must activate it; then halt and restart
driver - socket creation failed; error error
the server. This message may also result from more
code.
than one server running on the same machine with the
Explanation: The server is unable to initialize the same TCP/IP port number. Make sure that the
TCP/IP driver due to a socket creation error. dsmserv.opt file TCPPort option is different for each
server.
ANR8202E (Linux) TCP/IP driver unable to initialize
due to error in using port TCP port
number; error error code.
your system, you must activate it; then halt and restart Explanation: The server is unable to initialize the
the server. TCP/IP driver due to a socket binding error.
ANR8201W (Windows) Unable to initialize TCP/IP TCP/IP support is inoperative.
driver - insufficient memory.
Explanation: The server is unable to communicate by your system by using the ping command with your
way of TCP/IP. A memory allocation request has been TCP/IP address as a target. If TCP/IP is not active on
rejected by the operating system. your system, you must activate it; then halt and restart
same TCP/IP port number. Make sure that the
TCP/IP protocol.
dsmserv.opt file TCPPort option is different for each
User response: Ensure that there is sufficient space for server. Make sure TCPPORT and TCPADMINPORT do
the Windows paging file. Click on the system icon in not specify or default to the same values.
the Windows control panel and then click on the
virtual memory button. Refer to the online help for
instructions on how to increase the amount of virtual
driver - socket bind operation for port
memory.
TCP port number failed; error error code.
ANR8202W (AIX) Unable to initialize TCP/IP driver
TCP/IP driver due to a socket binding error.
- error creating acceptor socket. Reason
code reason code. System action: Server operation continues, but
Explanation: Because TCP/IP rejects a request for a
socket on which to listen, the server cannot start User response: Ensure that TCP/IP is operational on
communications through TCP/IP. your system by using the ping command with your
TCP/IP protocol.
User response: Ensure that TCP/IP is operational on same TCP/IP port number. Make sure that the
your system by using the ping command with your dsmserv.opt file TCPPort option is different for each
TCP/IP address as a target. If TCP/IP is not started, server.
use the HALT command from a server prompt to stop
the server and restart it.
ANR8202W (Windows) Unable to initialize TCP/IP
driver - error creating acceptor socket.
ANR8202E (HP-UX) Unable to initialize TCP/IP Reason code reason code.
driver - socket bind operation for port
Explanation: The server is unable to communicate by
TCP port number failed; error error code.
way of TCP/IP. TCP/IP has rejected a request for a
Explanation: The server is unable to initialize the socket on which the server listens.
TCP/IP driver due to a socket binding error.
System action: Server operation continues, but server cannot accept sessions from clients using the
TCP/IP support is inoperative. TCP/IP protocol.
User response: Ensure that TCP/IP is operational on User response: Ensure that TCP/IP is operational on
your system by using the ping command with your your system by using the ping command with your
TCP/IP address as a target. If TCP/IP is not started,

ANR8203W (AIX) • ANR8204E (Linux)
issue the HALT command to stop the server, and then your system, you must activate it; then halt and restart
restart the server. the server.
ANR8203W (AIX) Unable to establish TCP ANR8203W (Windows) Unable to establish TCP
connection - accept error. connection - accept error.
Explanation: The server cannot accept a client session Explanation: The server cannot accept a client session
due to a failure in TCP/IP. due to failure in TCP/IP.
server cannot accept sessions from clients using the server cannot accept sessions from clients using the
TCP/IP protocol. TCP/IP protocol.
User response: Ensure that TCP/IP is operational on User response: Ensure that TCP/IP is operational on
your system by using the ping command with your your system by using the ping command with your
TCP/IP address as a target. If TCP/IP is not started, TCP/IP address as a target. If TCP/IP is not started,
use the HALT command from a server prompt to issue the HALT command to stop the server, and then
terminate the server and restart it. restart the server.
ANR8203E (HP-UX) Unable to initialize TCP/IP ANR8204W (AIX) Unable to establish TCP
driver - listen operation failed; error connection - insufficient memory.
error code.
Explanation: The server cannot accept a client session
Explanation: The server is unable to initialize the due to a memory allocation request failure.
TCP/IP driver due to a socket listen error.
System action: Server operation continues, but session request for this session fails.
User response: Ensure that TCP/IP is operational on available for AIX. You may also use SMIT to determine
your system by using the ping command with your if the number of applications is causing a memory
TCP/IP address as a target. If TCP/IP is not active on shortage. You may also decrease the maximum number
your system, you must activate it; then halt and restart of sessions that the server can accept with the
the server. MAXSESSIONS option in the server options file.
ANR8203E (Linux) Unable to initialize TCP/IP driver ANR8204E (HP-UX) Unable to initialize TCP/IP
- listen operation failed; error error code. driver - thread creation failed.
Explanation: The server is unable to initialize the Explanation: The server is unable to initialize the
TCP/IP driver due to a socket listen error. TCP/IP driver due to an error creating a server thread.
System action: Server operation continues, but System action: Server operation continues, but
TCP/IP support is inoperative. TCP/IP support is inoperative.
User response: Ensure that TCP/IP is operational on User response: This error often results from a lack of
your system by using the ping command with your memory. Ensure that your system has sufficient paging
TCP/IP address as a target. If TCP/IP is not active on space to support the current activities.
the server.
ANR8204E (Linux) Unable to initialize TCP/IP driver
- thread creation failed.
driver - listen operation failed; error
TCP/IP driver due to an error creating a server thread.
error code.
TCP/IP driver due to a socket listen error.
memory. Ensure that your system has sufficient paging
space to support the current activities.

ANR8204E (Solaris) • ANR8206E (HP-UX)

driver - thread creation failed.
TCP/IP driver due to an error creating a server thread.
System action: Server operation continues, but your system, you must activate it; then halt and restart
TCP/IP support is inoperative. the server.
memory. Ensure that your system has sufficient paging ANR8205E (Solaris) Terminating TCP/IP driver -
space to support the current activities. socket accept operation failed; error error
code.
ANR8204W (Windows) Unable to establish TCP Explanation: The server is unable to initialize the
connection - insufficient memory. TCP/IP driver due to a socket accept error.
Explanation: The server is unable to accept a client System action: Server operation continues, but
session due to a memory allocation request failure. TCP/IP support is inoperative.
System action: Server operation continues, but the User response: Ensure that TCP/IP is operational on
session request for this session fails. your system by using the ping command with your
User response: Ensure that there is sufficient space for
the Windows paging file. Click on the system icon in
the server.
the Windows control panel and then click on the
instructions on how to increase the amount of virtual ANR8205W (Windows) Unable to establish TCP
memory. You may also wish to cut down on the connection - server HALT in progress.
maximum number of sessions that the server can
Explanation: The server is unable to accept a client
accept with the MAXSESSIONS option in the server
session due to server HALT processing that is in
options file.
progress.
ANR8205W (AIX) Unable to establish TCP
session request for this session fails.
connection - server HALT in progress.
due to server HALT processing that is in progress.
ANR8206W (AIX) Socket socket (session session
number) closed abruptly.
Explanation: The server detects that the indicated
session on the specified TCP/IP socket is closed outside
of the server.
ANR8205E (HP-UX) Terminating TCP/IP driver -
accept operation failed; error error code.
session is ended.
TCP/IP driver due to a socket accept error.
ANR8206E (HP-UX) Unable to establish TCP/IP
session - invalid host address IP host
User response: Ensure that TCP/IP is operational on address (port port number).
Explanation: The server is unable to establish a
session because the designated address or port number
is not valid.
the server.
ANR8205E (Linux) Terminating TCP/IP driver - User response: Ensure that the specified host name is
socket accept operation failed; error error valid and is accessible over the network. If the
code. TCPCLIENTPort option is specified for the remote
system, ensure it does not conflict with another
application.
TCP/IP driver due to a socket accept error.

ANR8206E (Linux) • ANR8208W (AIX)
ANR8206E (Linux) Unable to establish TCP/IP ANR8207E (HP-UX) Unable to establish TCP/IP
session - invalid host address IP host session with IP host address due to
address (port port number). memory shortage.
Explanation: The server is unable to establish a Explanation: The server is unable to establish a
session because the designated address or port number session because of a memory shortage condition.
is not valid.
User response: Ensure that your system has sufficient
User response: Ensure that the specified host name is paging space to support the current level of system
valid and is accessible over the network. If the activities.
TCPCLIENTPort option is specified for the remote
ANR8207E (Linux) Unable to establish TCP/IP
application.
session with IP host address due to
memory shortage.
ANR8206E (Solaris) Unable to establish TCP/IP
session - invalid host address IP host
session because of a memory shortage condition.
address (port port number).
session because the designated address or port number User response: Ensure that your system has sufficient
is not valid. paging space to support the current level of system
activities.
User response: Ensure that the specified host name is
valid and is accessible over the network. If the
session with IP host address due to
TCPCLIENTPort option is specified for the remote
memory shortage.
application. Explanation: The server is unable to establish a
session because of a memory shortage condition.
ANR8206I (Windows) TCP/IP Version 4 System action: Server operation continues.
administrative driver ready for
connection with clients on port port User response: Ensure that your system has sufficient
number. paging space to support the current level of system
activities.
administrative clients using the TCP/IP Version 4
protocol on the indicated port number. ANR8207W (Windows) TCP/IP driver unable to
initialize due to socket initialization
System action: Server operation continues. error. Reason code reason code.
User response: None. Explanation: While initializing TCP/IP
communications, the server has failed to set up an
interface with TCP/IP for Windows.
ANR8207W (AIX) TCP/IP driver unable to initialize
due to socket initialization error. Reason System action: Server operation continues, but the
code reason code. server cannot accept sessions from clients using the
TCP/IP protocol.
Explanation: While initializing TCP/IP
communications, the server fails to set up an interface User response: Ensure that TCP/IP is properly
with TCP/IP. installed on your system. Ensure that TCP/IP has been
started on your system. Issue the TCP/IP ping
command to your own address to verify that TCP/IP is
both installed and active.
TCP/IP protocol.
User response: Ensure that TCP/IP has been started
ANR8208W (AIX) TCP/IP driver unable to initialize
and is active on your system. You may issue the
due to error in using port port, reason
TCP/IP ping command to your own address to verify
code reason code.
that TCP/IP is both started and active.
communications, the server fails to connect to a master
socket on which to listen for clients. The reason code is

ANR8208E (HP-UX) • ANR8209E (Linux)
the return code from the TCP/IP bind API.

ANR8208W (Windows) TCP/IP driver unable to
System action: Server operation continues, but the initialize due to error in using Port port,
server cannot accept sessions from clients using the reason code reason code.
TCP/IP protocol.
User response: Ensure that no other application is communications, the server has failed to connect to a
using the port number specified in the server options master socket on which to listen for clients. The reason
file with the TCPPORT option by issuing the TCP/IP code is the return code from the TCP/IP bind API.
netstat command. If the server was brought down and
client sessions were active, it may be necessary to
terminate the client sessions on the client systems
TCP/IP protocol.
before the port can be freed.
User response: Ensure that no other application is
using the port number specified in the server options
file with the TCPPORT option. If the server is brought
session with IP host address - socket
down and then started immediately, you may be within
creation failed; error error code.
the TCP/IP one minute timeout period for port
Explanation: The server is unable to establish a reusage. Bring down the server, wait one minute, and
session because of a socket creation error. then restart the server. If that does not work, it may be
necessary to restart Windows.
User response: Ensure that TCP/IP is operational on ANR8209W (AIX) TCP/IP driver unable to initialize
your system by using the ping command with your due to error in LISTENing on the
TCP/IP address as a target. If TCP/IP is not active on specified Port, reason code reason code.
the server. Explanation: While attempting to listen for session
requests from clients using TCP/IP, TCP/IP returns an
error. The reason code is the return code from the
ANR8208E (Linux) Unable to establish TCP/IP TCP/IP listen API.
session with IP host address - socket
creation failed; error error code. System action: Server operation continues, but the
server cannot accept additional sessions from clients
Explanation: The server is unable to establish a using the TCP/IP protocol.
session because of a socket creation error.
User response: Ensure that TCP/IP is running
System action: Server operation continues. properly by issuing the TCP/IP netstat -s and ping
User response: Ensure that TCP/IP is operational on commands to other nodes on your network. It may be
your system by using the ping command with your possible to bring the server down and restart it to
TCP/IP address as a target. If TCP/IP is not active on allow additional client sessions to start.
the server. ANR8209E (HP-UX) Unable to establish TCP/IP
session with IP host address - connection
ANR8208E (Solaris) Unable to establish TCP/IP refused.
session with IP host address - socket Explanation: The server is unable to establish a
creation failed; error error code. session because the remote system refused the
Explanation: The server is unable to establish a connection request.
session because of a socket creation error. System action: Server operation continues.
System action: Server operation continues. User response: Ensure that the specified remote
User response: Ensure that TCP/IP is operational on system is operational and is properly configured to run
your system by using the ping command with your TCP/IP. Ensure that the client options file specifies the
TCP/IP address as a target. If TCP/IP is not active on correct TCPServeraddress and TCPPort of the server
your system, you must activate it; then halt and restart you are attempting to contact.
the server.
refused.
session because the remote system refused the
connection request.

ANR8209E (Solaris) • ANR8210E (Solaris)

User response: Ensure that the specified remote session with IP host address - connection
system is operational and is properly configured to run request timed out.
TCP/IP. Ensure that the client options file specifies the
correct TCPServeraddress and TCPPort of the server
session because the remote system did not respond to
you are attempting to contact.
the connection request.
session with IP host address - connection User response: Ensure the following:
refused. v The specified remote system is operational and is
Explanation: The server is unable to establish a properly configured to run TCP/IP.
session because the remote system refused the v The client options file specifies the correct
connection request. TCPServeraddress and TCPPort of the server you are
attempting to contact.
v Necessary gateways and routers are functioning
User response: Ensure that the specified remote properly.
system is operational and is properly configured to run
correct TCPServeraddress and TCPPort of the server ANR8210E (Linux) Unable to establish TCP/IP
you are attempting to contact. session with IP host address - connection
request timed out.
ANR8209W (Windows) TCP/IP driver unable to Explanation: The server is unable to establish a
initialize due to error in LISTENing on session because the remote system did not respond to
the specified Port, reason code reason the connection request.
code. System action: Server operation continues.
Explanation: While attempting to listen for session User response: Ensure the following:
v The specified remote system is operational and is
properly configured to run TCP/IP.
TCP/IP listen API.
v The client options file specifies the correct
System action: Server operation continues, but the TCPServeraddress and TCPPort of the server you are
server cannot accept additional sessions from clients attempting to contact.
using the TCP/IP protocol.
v Necessary gateways and routers are functioning
User response: Ensure that TCP/IP is running properly.
properly. This may be done by issuing the TCP/IP
netstat -s and ping commands to other nodes on your
network. It may be possible to correct this condition by
restarting the server.
request timed out.
ANR8210W (AIX) TCP/IP driver is terminating due
session because the remote system did not respond to
to error in accepting a new session,
the connection request.
reason code reason code.
Explanation: While attempting to accept a session
request from a client using TCP/IP, TCP/IP returns an User response: Ensure the following:
error. The reason code is the return code from the v The specified remote system is operational and is
TCP/IP accept API. properly configured to run TCP/IP.
System action: Server operation continues, but the v The client options file specifies the correct
server cannot accept additional sessions from clients TCPServeraddress and TCPPort of the server you are
using the TCP/IP protocol. attempting to contact.
User response: Ensure that TCP/IP is running v Necessary gateways and routers are functioning
properly. This may be done by issuing the TCP/IP properly.
network. It may be possible to bring the server down
and restart it to allow additional client sessions to start.

ANR8210W (Windows) • ANR8212E (HP-UX)
routers are functioning properly.

ANR8210W (Windows) TCP/IP driver is terminating
due to error in accepting a new session,
reason code reason code. ANR8211E (Solaris) Unable to establish TCP/IP
session with IP host address -
system/network unreachable.
request from a client using TCP/IP, TCP/IP returns an
error. The reason code is the return code from the Explanation: The server is unable to establish a
TCP/IP accept API. session because the remote system or network is
unreachable.
server cannot accept additional sessions from clients System action: Server operation continues.
using the TCP/IP protocol.
User response: Ensure that TCP/IP is running system is operational and is properly configured to run
properly. This may be done by issuing the TCP/IP TCP/IP. Also, ensure that necessary gateways and
netstat -s and ping commands to other nodes on your routers are functioning properly.
ANR8211W (Windows) TCP/IP driver is terminating
due to error in creating a new thread.
ANR8211W (AIX) TCP/IP driver is terminating due
to error in creating a new thread. Explanation: The server cannot initialize due its
inability to create a new thread of execution.
Explanation: The server cannot initialize due to the
inability to create a new thread of execution. System action: Server operation continues, but
TCP/IP communications is inoperative.
TCP/IP communications is inoperative. User response: The most likely cause is a lack of
memory. Ensure that there is sufficient space for the
User response: The most likely cause is a lack of Windows paging file. Click on the system icon in the
memory. Ensure that sufficient paging space is available Windows NT control panel and then click on the
for AIX. You may also use SMIT to determine if the virtual memory button. Refer to the online help for
number of applications is causing a memory shortage. instructions on how to increase the amount of virtual
You may also decrease the maximum number of memory. You may also wish to cut down on the
sessions that the server can accept with the maximum number of sessions that the server can
MAXSESSIONS option in the server options file. accept with the MAXSESSIONS option in the server
options file.
session with IP host address - ANR8212W (AIX) Unable to resolve address for node
system/network unreachable. name.
Explanation: The server is unable to establish a Explanation: The server attempts to obtain a TCP/IP
session because the remote system or network is address for the indicated node name. The attempt is
unreachable. unsuccessful.
System action: Server operation continues. System action: The attempt to communicate with the
indicated node fails. Server operation continues.
system is operational and is properly configured to run User response: Ensure that the node name is properly
TCP/IP. Also, ensure that necessary gateways and specified and that it is accessible over the network. Use
routers are functioning properly. the TCP/IP ping command for this purpose.
ANR8211E (Linux) Unable to establish TCP/IP ANR8212E (HP-UX) Unable to establish TCP/IP
session with IP host address - session with IP host address - connect
system/network unreachable. failed; error error code.
Explanation: The server is unable to establish a Explanation: The server is unable to establish a
session because the remote system or network is session because of a connection error.
unreachable.
User response: Ensure that the specified remote system is operational and is properly configured to run
system is operational and is properly configured to run TCP/IP.
TCP/IP. Also, ensure that necessary gateways and

ANR8212E (Linux) • ANR8214E (AIX)

TCP/IP.
session with IP host address - connect
failed; error error code.
ANR8213E (Linux) Socket Socket identifier aborted due
to send error; error error code.
session because of a connection error.
Explanation: The session between the server and the
specified client system experienced a fatal error sending
User response: Ensure that the specified remote data.
TCP/IP.
ended.
session with IP host address - connect
TCP/IP.
failed; error error code.
ANR8213E (Solaris) Socket Socket identifier aborted
session because of a connection error.
due to send error; error error code.
User response: Ensure that the specified remote specified client system experienced a fatal error sending
system is operational and is properly configured to run data.
TCP/IP.
ended.
ANR8212W (Windows) Unable to resolve address for
node name.
Explanation: The server attempts to obtain a TCP/IP TCP/IP.
address for the indicated node name. The attempt is
unsuccessful.
ANR8213W (Windows) Session open with node name
System action: The attempt to communicate with the timed out.
Explanation: The server attempts to contact the
User response: Ensure that the node name is properly indicated node name. The attempt is unsuccessful.
specified and that it is accessible over the network. Use
System action: The attempt to communicate with the
the TCP/IP ping command for this purpose.
indicated node fails.
User response: Ensure that the node name is properly
ANR8213W (AIX) Session open with node name timed
out.
Explanation: The server attempts to contact the
indicated node name. The attempt is unsuccessful.
ANR8214E (AIX) Session open with IP host address
System action: The attempt to communicate with the failed due to connection refusal.
User response: Ensure that the node name is properly session because the remote system refused the
specified and that it is accessible over the network. Use connection request.
ANR8213E (HP-UX) Session Session identifier aborted
due to send error; error error code.
Explanation: The session between the server and the correct TCPServeraddress and TCPPort of the server
specified client system experienced a disruptive error you are attempting to contact.
sending data.
ended.

ANR8214E (HP-UX) • ANR8215W (Windows)
you are attempting to contact.

ANR8214E (HP-UX) The session stopped when no
data was read on socket socket number.
ANR8215W (AIX) Session open with IP host address
Explanation: The server is unable to read data on the
failed as unreachable.
indicated socket. This might be a normal event if either
side of the connection is abruptly ended. Explanation: The server is unable to establish a
session because the remote system is unreachable.
continues. System action: Server operation continues.
User response: If the session is ended as a result of User response: Ensure that the IP host address is
intentionally stopping either the client or server, no properly specified and that it is accessible over the
response is required. Otherwise, ensure that the client network. Use the TCP/IP ping command for this
and server can communicate through such means as purpose.
Telnet or FTP applications, which are part of the
TCP/IP suite.
ANR8215E (HP-UX) Session Session identifier aborted
due to receive error; error error code.
ANR8214E (Linux) Session terminated when no data
was read on socket socket number. Explanation: The session between the server and the
specified client system experienced a disruptive error
Explanation: The server is unable to read data on the receiving data.
indicated socket. This may be a normal event if either
side of the connection is abruptly ended. System action: The session with the remote system is
ended.
continues. User response: Ensure that the specified remote
User response: If the session is ended as a result of TCP/IP.
intentionally stopping either the client or server, no
response is required. Otherwise, ensure that the client
and server can communicate through such means as ANR8215E (Linux) Session Session identifier aborted
Telnet or FTP applications, which are part of the due to receive error; error error code.
TCP/IP suite. Explanation: The session between the server and the
specified client system experienced a fatal error
ANR8214E (Solaris) Session terminated when no receiving data.
data was read on socket socket number. System action: The session with the remote system is
Explanation: The server is unable to read data on the ended.
indicated socket. This may be a normal event if either User response: Ensure that the specified remote
side of the connection is abruptly ended. system is operational and is properly configured to run
System action: The session is ended. Server operation TCP/IP.
continues.
User response: If the session is ended as a result of ANR8215E (Solaris) Session Session identifier aborted
intentionally stopping either the client or server, no due to receive error; error error code.
response is required. Otherwise, ensure that the client Explanation: The session between the server and the
and server can communicate through such means as specified client system experienced a fatal error
Telnet or FTP applications, which are part of the receiving data.
TCP/IP suite.
ended.
ANR8214E (Windows) Session open with IP host
address failed due to connection refusal. User response: Ensure that the specified remote
Explanation: The server is unable to establish a TCP/IP.
session because the remote system refused the
connection request.
ANR8215W (Windows) Session open with IP host
System action: Server operation continues. address failed as unreachable.
User response: Ensure that the specified remote Explanation: The server is unable to establish a
system is operational and is properly configured to run session because the remote system is unreachable.
correct TCPServeraddress and TCPPort of the server System action: Server operation continues.

User response: Ensure that the IP host address is

ANR8216W (Windows) Error sending data on socket
properly specified and that it is accessible over the
socket number. Reason return code.
network. Use the TCP/IP ping command for this
purpose. Explanation: The server experiences an error return
code from TCP/IP while sending data over the
ANR8216W (AIX) The server experienced a TCP/IP
side of the connection is abruptly ended.
error while sending data on socket socket
number. Reason return code. System action: The session is ended. Server operation
continues.
Explanation: A communication error occurred on the
indicated socket. This may be a normal event if either User response: If the session is ended as a result of
side of the connection is abruptly ended. intentionally stopping either the client or server, no
and server can communicate through such means as
continues.
User response: If the session is ended as a result of TCP/IP suite.
action is required. Otherwise, ensure that the client and
server can communicate using Telnet or FTP
error while receiving data on socket
applications, which are part of the TCP/IP suite.
socket number. Reason return code.
Explanation: A communication error occurred on the
session with IP host address due to thread
creation error.
continues.
session because of an error creating a thread.
User response: Ensure that your system has sufficient action is required. Otherwise, ensure that the client and
paging space to support the current level of system server can communicate using Telnet or FTP
activities. applications, which are part of the TCP/IP suite.
ANR8216E (Linux) Unable to establish TCP/IP ANR8217W (HP-UX) TCP/IP driver is unable to set
session with IP host address due to thread the window size to TCPWindowsize for
creation error. client client. The default value will be
used.
session because of an error creating a thread. Explanation: The server cannot set the window size
for the indicated client to the requested size shown.
System action: Server operation continues. The server uses the default window size for the
User response: Ensure that your system has sufficient indicated session. There may be a lack of memory for
paging space to support the current level of system TCP/IP buffers.
activities. System action: Server operation continues and the
session continues with the default window size.
ANR8216E (Solaris) Unable to establish TCP/IP User response: Retry the session with a smaller
session with IP host address due to thread window size in the options file. Issue the QUERY
creation error. OPTION command to determine the setting of the
Explanation: The server is unable to establish a server TCPWindowsize.
session because of an error creating a thread.
System action: Server operation continues. ANR8217W (Linux) Unable to initialize TCP/IP
User response: Ensure that your system has sufficient
paging space to support the current level of system Explanation: Because the operating system rejects a
activities. memory allocation request, the server cannot start
communications through TCP/IP.
TCP/IP protocol.


ANR8218W (HP-UX) TCP/IP driver is unable to use
available for Solaris. You may also use ps -ef to
the TCP/IP NODELAY option for client
determine if the number of applications is causing a
client.
memory shortage. It may be necessary to decrease the
maximum number of client sessions by changing the Explanation: The server cannot set TCP/IP NODELAY
MAXSESSIONS option in the server options file. for the indicated client. The session proceeds with
TCP/IP Delay processing in effect. This causes TCP/IP
to buffer data prior to sending it to clients.
ANR8217W (Solaris) Unable to initialize TCP/IP
driver - insufficient memory. System action: Server operation continues and the
session continues with the delay processing on.
Explanation: Because the operating system rejects a
memory allocation request, the server cannot start User response: Further details for use in contacting
communications through TCP/IP. your service representative can be obtained by issuing
the following trace commands from an administrative
session or from the server console (proper
administrative authority is required): TRACE ENABLE
TCP/IP protocol.
TCPINFO TRACE BEGIN tcptrace.out. After a session
User response: Ensure that sufficient paging space is starts and displays message ANR8218W, issue the
available for Solaris. You may also use ps -ef to following commands: TRACE FLUSH TRACE END.
determine if the number of applications is causing a This will create trace data in file tcptrace.out and will
memory shortage. It may be necessary to decrease the terminate the trace. This file should be supplied to your
maximum number of client sessions by changing the server representative on request.
ANR8218W (Linux) Unable to resolve address for
ANR8217W (Windows) Error receiving data on node name.
socket socket number. Reason return code.
Explanation: The server attempts to obtain a TCP/IP
Explanation: The server experiences an error return address for the indicated node name. The attempt is
code from TCP/IP while receiving data on the unsuccessful.
User response: Ensure that the node name is properly
continues.
User response: If the session is ended as a result of the TCP/IP ping command for this purpose.
ANR8218W (Solaris) Unable to resolve address for
node name.
TCP/IP suite. Explanation: The server attempts to obtain a TCP/IP
address for the indicated node name. The attempt is
unsuccessful.
ANR8218W (AIX) Session terminated when no data
was read on socket socket number. System action: The attempt to communicate with the
Explanation: The server is unable to read data on the
indicated socket. This may be a normal event if either User response: Ensure that the node name is properly
side of the connection is abruptly ended. specified and that it is accessible over the network. Use
continues.
ANR8218W (Windows) Session terminated when no
data read on socket socket number.
response is required. Otherwise, ensure that the client Explanation: The server cannot read on the indicated
and server can communicate through such means as socket. This may be a normal event if either side of the
Telnet or FTP applications, which are part of the connection is abruptly ended.
TCP/IP suite.
continues.

ANR8219W (AIX) • ANR8220W (HP-UX)

ANR8219W (Solaris) Unable to establish TCP
connection - insufficient memory.
TCP/IP suite. Explanation: The server cannot accept a client session
due to a memory allocation request failure.
ANR8219W (AIX) TCP/IP driver is unable to accept a System action: Server operation continues, but the
new session with client at address session request for this session fails.
TCP/IP address due to an error in creating
a new thread.
available for Solaris. You may also use 'swap -l' to
Explanation: The server cannot accept a client session determine the amount of swap available. You may also
with the client at the indicated address due to an decrease the maximum number of sessions that the
inability to create a new thread. server can accept with the MAXSESSIONS option in
System action: Server operation continues, the session
request fails.
ANR8219W (Windows) TCP/IP driver is unable to
User response: The most likely cause is lack of
accept a new session due to error in
memory. Ensure that sufficient paging space is available
creating a new thread.
for AIX. You may also use SMIT to determine if the
number of applications is causing a memory shortage. Explanation: The server cannot accept a client session
You may also decrease the maximum number of due to the inability to create a new thread.
sessions that the server can accept with the
request fails.
User response: The most likely cause is a lack of
ANR8219W (HP-UX) Unable to initialize TCP/IP
Windows paging file. Click on the system icon in the
Explanation: Because the operating system rejects a Windows NT control panel and then click on the
memory allocation request, the server cannot start virtual memory button. Refer to the online help for
communications through TCP/IP. instructions on how to increase the amount of virtual
memory. You may also wish to to cut down on the
TCP/IP protocol.
options file.
available for HP-UX. You may also use SMIT to
ANR8220W (AIX) TCP/IP driver is unable to set the
window size to TCPWindowsize for client
memory shortage. It may be necessary to decrease the
session. The default value will be used.
maximum number of client sessions by changing the
MAXSESSIONS option in the server options file. Explanation: The server cannot set the window size
for the indicated session to the requested size shown or
cannot set the rfc1323 attribute when the window size
ANR8219W (Linux) Unable to establish TCP
is greater than 65535 bytes. The server uses the default
window size for the indicated session. There may be a
Explanation: The server cannot accept a client session lack of memory for TCP/IP buffers.
System action: Server operation continues and the
System action: Server operation continues, but the session continues with the default window size.
User response: Retry the session with a smaller
User response: Ensure that sufficient paging space is window size in the options file. Issue the QUERY
available for Solaris. You may also use 'swap -l' to OPTION command to determine the setting of the
determine the amount of swap available. You may also server TCPWindowsize.
decrease the maximum number of sessions that the
server can accept with the MAXSESSIONS option in
ANR8220W (HP-UX) Unable to establish TCP

ANR8220W (Linux) • ANR8221W (Linux)

ANR8221W (AIX) TCP/IP driver is unable to use the
available for HP-UX. You may also use SMIT to
TCP/IP NODELAY option for client
client.
memory shortage. You may also decrease the maximum
number of sessions that the server can accept with the Explanation: The server cannot set TCP/IP NODELAY
MAXSESSIONS option in the server options file. for the indicated client. The session proceeds with
TCP/IP Delay processing in effect. This causes TCP/IP
to buffer data prior to sending it to clients.
ANR8220W (Linux) TCP/IP driver is unable to set
the window size to TCPWindowsize for System action: Server operation continues and the
client client. The default value will be session continues with the delay processing on.
used.
User response: Further details for use in contacting
Explanation: The server cannot set the window size your service representative can be obtained by issuing
for the indicated client to the requested size shown. the following trace commands from an administrative
The server uses the default window size for the session or from the server console (proper
indicated session. There may be a lack of memory for administrative authority is required): TRACE ENABLE
TCP/IP buffers. TCPINFO TRACE BEGIN. After a session starts and
displays message ANR8221W, issue the commands
TRACE FLUSH TRACE END. This will create trace
session continues with the default window size.
data in file tcptrace.out and will terminate the trace.
User response: Retry the session with a smaller This file should be supplied to your service
window size in the options file. Issue the QUERY representative on request.
OPTION command to determine the setting of the
server TCPWindowsize.
ANR8221I (HP-UX) TCP/IP Version 4 administrative
driver ready for connection with clients
ANR8220W (Solaris) TCP/IP driver is unable to set on port port number.
the window size to TCPWindowsize for
client client. The default value will be
used.
protocol on the indicated port number.
Explanation: The server cannot set the window size
for the indicated client to the requested size shown.
The server uses the default window size for the User response: None.
indicated session. There may be a lack of memory for
TCP/IP buffers.
ANR8221W (Linux) TCP/IP driver is unable to use
System action: Server operation continues and the the TCP/IP NODELAY option for client
session continues with the default window size. client.
User response: Retry the session with a smaller Explanation: The server cannot set TCP/IP NODELAY
window size in the options file. Issue the QUERY for the indicated client. The session proceeds with
OPTION command to determine the setting of the TCP/IP delay processing in effect. This causes TCP/IP
server TCPWindowsize. to buffer data prior to sending it to clients.
ANR8220W (Windows) TCP/IP driver is unable to session continues with delay processing on.
contact node name due to an output
User response: Further details for use when
socket initialization error. Reason code
contacting your service representative can be obtained
reason code
by issuing the following trace commands from an
Explanation: The server attempts to contact the administrative session or from the console (proper
indicated node name. The attempt is unsuccessful due administrative authority is required): TRACE ENABLE
to the inability to initialize a local socket. TCPINFO TRACE BEGIN tcptrace.out. After a session
starts and displays message ANR8221W, issue the
following commands: TRACE FLUSH TRACE END.
This will create trace data in file tcptrace.out and will
User response: Ensure that TCP/IP is operating terminate the trace. This file should be supplied to your
properly on this node and that it can communicate service representative on request.
remotely. Use the TCP/IP ping command for this
purpose.

ANR8221W (Solaris) TCP/IP driver is unable to use ANR8222W (HP-UX) The TCP/IP administrative
the TCP/IP NODELAY option for client driver was unable to initialize due to
client. error using Port port, reason code reason
code.
Explanation: The server cannot set TCP/IP NODELAY
for the indicated client. The session proceeds with Explanation: While initializing TCP/IP
TCP/IP Delay processing in effect. This causes TCP/IP communications for administrative sessions, the server
to buffer data prior to sending it to clients. failed to connect to a master socket to listen for clients.
The reason code is the return code from the TCP/IP
bind API.
session continues with the delay processing on.
User response: Further details for use in contacting
server cannot accept administrative sessions from
your service representative can be obtained by issuing
clients using the TCP/IP protocol. This also includes
the following trace commands from an administrative
server-server sessions, storage agent to server sessions,
session or from the server console (proper
and library client to server sesssions.
TCPINFO TRACE BEGIN tcptrace.out After a session User response: Ensure that no other application is
starts and displays message ANR8221W, issue the using the port number specified in the server options
following commands: TRACE FLUSH TRACE END file with the TCPADMINPORT option. If the server was
This will create trace data in file tcptrace.out and will brought down and client sessions were active, it can be
terminate the trace. This file should be supplied to your necessary to end the client sessions on the client
service representative on request. systems before the port can be freed.
ANR8221W (Windows) TCP/IP driver is unable to ANR8222W (Linux) Unable to establish TCP
set the window size to TCPWindowsize connection - server HALT in progress.
for session session, client client. The
default value will be used.
due to server HALT processing that is in progress.
for the indicated session/client to the requested size
shown. The server will use the default window size for
the indicated session. User response: None.
session continues with the default window size. ANR8222W (Solaris) Unable to establish TCP
connection - server HALT in progress.
User response: The most likely cause is lack of
memory for TCP/IP buffers. You may retry with a Explanation: The server cannot accept a client session
smaller TCP window size in the options file. You can due to server HALT processing that is in progress.
issue the QUERY OPTION command to display the
current setting of the TCP window size. System action: Server operation continues, but the
ANR8222W (AIX) TCP/IP driver is unable to set the User response: None.
window size to TCPWindowsize for the
server master socket. The default value ANR8222W (Windows) TCP/IP driver is unable to
will be used. use the TCP/IP NODELAY option for
Explanation: The server cannot set the window size client client.
for the socket on which the server listens to the Explanation: The server cannot set TCP/IP NODELAY
requested size shown. The server uses the default for the indicated client. The session proceeds with
window size for listening for sessions. There may be a TCP/IP Delay processing in effect. This causes TCP/IP
lack of memory for TCP/IP buffers. to buffer data prior to sending it to clients.
System action: Server operation continues with the System action: Server operation continues and the
default window size. session continues with the delay processing on.
User response: Restart the server with a smaller User response: Further details for use in contacting
window size in the options file if necessary. Issue the your service representative can be obtained by issuing
QUERY OPTION command to determine the setting of the following trace commands from an administrative
the server TCPWindowsize. session or from the server console (proper
TCPINFO TRACE BEGIN tcptrace.out After a session

ANR8223W (AIX) • ANR8224W (AIX)
starts and displays message ANR8222W, issue the

ANR8223W (Solaris) TCP/IP driver is unable to
following commands: TRACE FLUSH TRACE END
accept a new session with client at
This will create trace data in file tcptrace.out and will
address TCP/IP address due to an error in
terminate the trace. This file should be supplied to your
creating a new thread.
service representative on request.
with the client at the indicated address due to an
ANR8223W (AIX) Unable to connect to remote
inability to create a new thread.
system RemoteSystem due to unexpected
return code ReturnCode System action: Server operation continues, the session
request fails.
Explanation: The server was unable to connect to a
remote system due to an unexpected return code from User response: The most likely cause is lack of
the connect Application Programming Interface. memory. Ensure that sufficient paging space is available
Common return code are handled with specific for Solaris. You may also use ps -ef to determine if the
messages. This return code was unexpected. number of applications is causing a memory shortage.
You may also decrease the maximum number of
System action: Server operation continues but the
connection to the remote system fails.
User response: TCP/IP return code are listed in file
/usr/include/sys/errno.h and may provide a pointer
ANR8223W (Windows) Failed to connect to system at
to the underlying problem. /usr/include/sys/errno.h
address address port port.
is part of fileset bos.adt.include.
Explanation: The server attempted to contact the
indicated node name at the specified port. The attempt
ANR8223W (HP-UX) The TCP/IP driver is unable to
is unsuccessful. The target port is not valid at the target
accept a new session with the client at
node.
address TCP/IP address, due to an error
in creating a new thread. System action: The attempt to communicate with the
with the client at the indicated address due to an User response: Ensure that the node name still has
inability to create a new thread. TCP/IP running and that the client is active in
SCHEDULE mode. If the server is attempting contact
with the SNMP subagent, ensure that the hostname and
session request fails.
port number for the subagent is correct in the server
User response: The cause is probably lack of memory. options file.
Ensure that sufficient paging space is available for AIX.
You might also use SMIT to determine if the number of
ANR8224W (AIX) TCP/IP Administrative driver was
applications is causing a memory shortage. You might
unable to initialize due to error in using
also decrease the maximum number of sessions that the
port port, reason code reason code.
server can accept with the MAXSESSIONS option in
the server options file. Explanation: While initializing TCP/IP
communications for administrative sessions, the server
has failed to connect to a master socket on which to
ANR8223W (Linux) TCP/IP driver is unable to accept
listen for clients. The reason code is the return code
a new session with client at address
from the TCP/IP bind API.
TCP/IP address due to an error in creating
a new thread. System action: Server operation continues, but the
with the client at the indicated address due to an
server to server sessions, storage agent to server
inability to create a new thread.
sessions, and library client to server sesssions.
request fails.
User response: The most likely cause is lack of file with the TCPADMINPORT or TCPPORT options. If
memory. Ensure that sufficient paging space is available the server was brought down and client sessions were
for Solaris. You may also use ps -ef to determine if the active, it may be necessary to terminate the client
number of applications is causing a memory shortage. sessions on the client systems before the port can be
You may also decrease the maximum number of freed.

ANR8224E (HP-UX) • ANR8225I (Solaris)

ANR8224E (HP-UX) The server is unable to open the
file due to the system limit .
Explanation: An error occurs when the server server to server sessions, storage agent to server
attempts to open a file. sessions, and library client to server sessions.
System action: Server operation continues, but files User response: Ensure that no other application is
cannot be opened until the problem is fixed. using the port number specified in the server options
file with the TCPADMINPORT option. If the server is
User response: Use the System Administrator
brought down and then started immediately, you can
Manager (SAM) program to increase the value of the
be within the TCP/IP one minute timeout period for
maxfiles parameter. This value determines the
port reusage. Bring down the server, wait one minute,
maximum number of files a process is allowed to open
and then restart the server. If that does not work, it
at one time. For proper server operation, increase the
may be necessary to restart Windows.
maxfiles value to at least 512.
ANR8225I (AIX) TCP/IP Version 4 administrative

ANR8224W (Linux) TCP/IP driver is unable to set
on port port number.
the server master socket. The default
value will be used. Explanation: The server can now accept sessions with
for the socket on which the server listens to the
requested size shown. The server uses the default System action: Server operation continues.
window size for listening for sessions. There may be a
lack of memory for TCP/IP buffers.
System action: Server operation continues with the
ANR8225W (Linux) TCP/IP Administrative driver
default window size.
was unable to initialize due to error in
User response: Restart the server with a smaller using port port, reason code reason code.
window size in the options file if necessary. Issue the
QUERY OPTION command to determine the setting of
communications for administrative sessions, the server
the server TCPWindowsize.
ANR8224W (Solaris) TCP/IP driver is unable to set from the TCP/IP bind API.
the server master socket. The default
value will be used.
Explanation: The server cannot set the window size server to server sessions, storage agent to server
for the socket on which the server listens to the sessions, and library client to server sesssions.
requested size shown. The server uses the default
window size for listening for sessions. There may be a
lack of memory for TCP/IP buffers.
file with the TCPADMINPORT or TCPPORT options. If
System action: Server operation continues with the the server was brought down and client sessions were
default window size. active, it may be necessary to terminate the client
sessions on the client systems before the port can be
User response: Restart the server with a smaller
freed.
window size in the options file if necessary. Issue the
QUERY OPTION command to determine the setting of
the server TCPWindowsize. ANR8225I (Solaris) TCP/IP Version 4 administrative
ANR8224W (Windows) TCP/IP Administrative driver
was unable to initialize due to error in Explanation: The server can now accept sessions with
using Port port, reason code reason code. administrative clients using the TCP/IP Version 4
communications for administrative sessions, the server System action: Server operation continues.
from the TCP/IP bind API.

ANR8225I (Windows) • ANR8227W (Solaris)
ANR8225I (Windows) TCP/IP Version 6 driver ready ANR8226W (Windows) Unable to initialize
for connection with clients on port port NETBIOS driver on adapter network
number. adapter number.
Explanation: The server can now accept sessions with Explanation: The server cannot obtain sufficient
clients using the TCP/IP Version 6 protocol on the NETBIOS resources to initialize communications on the
indicated port number. indicated network adapter.
System action: Server operation continues. System action: Server operation continues, but the
server will not accept sessions from clients that use the
NETBIOS protocol.
User response: Ensure that NETBIOS is configured on
ANR8226E (AIX) Error errno detecting version of
the system. Ensure that all NETBIOS resources are not
HBA-API library.
already in use. If the LAN Server or LAN Requester
Explanation: The server attempted to determine the application is running, you have NETBIOS configured.
level of the devices.common.IBM.fc.hba-api fileset and In that case, starting the server prior to starting LAN
encountered an error. Server or LAN Requester may allow the server to
obtain the necessary NETBIOS resources.
without accurate SAN device mapping.
ANR8227E (AIX) Fileset devices.common.IBM.fc.hba-
User response: None. api is not at the required level.
Explanation: The specified fileset is at a level that is
ANR8226I (Linux) TCP/IP Version 4 administrative incompatible with IBM Spectrum Protect operations.
driver ready for connection with clients Install the latest maintenance for this fileset if you use
on port port number. SAN devices.
Explanation: The server can now accept sessions with System action: Server operation continues, but
administrative clients using the TCP/IP Version 4 without accurate SAN device mapping.
User response: None. ANR8227W (Linux) Unable to connect to remote
system RemoteSystem due to unexpected
ANR8226W (Solaris) TCP/IP Administrative driver return code ReturnCode
was unable to initialize due to error in Explanation: The server was unable to connect to a
using port port, reason code reason code. remote system due to an unexpected return code from
Explanation: The TCP/IP administrative driver was the connect Application Programming Interface.
unable to initialize due to an error in running the BIND Common return code are handled with specific
API to the port. messages. This return code was unexpected.
System action: Server operation continues, but the System action: Server operation continues but the
server cannot accept administrative sessions from connection to the remote system fails.
clients using the TCP/IP protocol. This also includes User response: TCP/IP return code are listed in file
server to server sessions, storage agent to server /usr/include/asm/errno.h and may provide a pointer
sessions, and library client to server sesssions. to the underlying problem.
server cannot accept administrative sessions from ANR8227W (Solaris) Unable to connect to remote
clients using the TCP/IP protocol. This also includes system RemoteSystem due to unexpected
server-server sessions, storage agent to server sessions, return code ReturnCode
and library client-server sesssions.
Explanation: The server was unable to connect to a
User response: Ensure that no other application is remote system due to an unexpected return code from
using the port number specified in the server options the connect Application Programming Interface.
file with the TCPADMINPORT or TCPPORT options. If Common return code are handled with specific
the server was brought down and client sessions were messages. This return code was unexpected.
active, it can be necessary to terminate the client
sessions on the client systems before the port can be System action: Server operation continues but the
freed. connection to the remote system fails.
User response: TCP/IP return code are listed in file

ANR8227W (Windows) • ANR8230I (HP-UX)
/usr/include/sys/errno.h and may provide a pointer

ANR8229E (Linux) Session Session identifier aborted
to the underlying problem.
due to Aspera Write error; error error
code : error code2 .
ANR8227W (Windows) NETBIOS connection
terminated - insufficient memory,
specified partner system experienced a communication
network adapter network adapter number.
error sending data.
Explanation: The server cannot listen for client
sessions on the specified network adapter due to a
ended.
memory allocation request failure.
sessions will not be accepted on the specified adapter.
Aspera FASP.
Other network adapters remain unaffected.
ANR8229W (Windows) Unable to add server name
server name to adapter network adapter
number.
Windows NT control panel and then click on the
virtual memory button. Refer to the online help for Explanation: The server cannot initialize
instructions on how to increase the amount of virtual communications processing using the NETBIOS
memory. protocol on the indicated network adapter because the
server name cannot be added as a NETBIOS name on
the adapter.
ANR8228E (AIX) Fileset devices.common.IBM.fc.hba-
api is not installed on the system. System action: Server operation continues, but client
sessions from clients using the NETBIOS protocol will
Explanation: The specified fileset is required for the
not be accepted on this adapter. Other adapters are not
SAN discovery operation. Install the latest maintenance
affected.
for this fileset if the SANDISCOVERY option is set to
ON. User response: The most likely cause for this message
is the presence of another system on the network that
is using the same name for NETBIOS communications.
without accurate SAN device mapping.
This may be another server or client or a LAN
User response: Install the latest version of the Requester node. Changing or adding the
device.common.IBM.fc.hba-api fileset. NETBIOSNAME option for this adapter in your server
options file and restarting the server may allow this
adapter to be used with NETBIOS communications.
ANR8228E (Linux) Session Session identifier aborted
due to Aspera FASP Read error; error
error code : error code2 . ANR8230I (AIX) TCP/IP Version 6 driver ready for
Explanation: The session between the server and the number.
specified partner experienced a communication error
receiving data. Explanation: The server can now accept sessions with
System action: The session with the remote system is indicated port number.
ended.
system is operational and is properly configured to run User response: None.
Aspera FASP.
ANR8230I (HP-UX) The TCP/IP Version 6 driver is
ANR8228W (Windows) NETBIOS connection ready for connection with clients on
terminated - server HALT in progress. port port number.
Explanation: The server cannot accept a client session Explanation: The server is now able to accept sessions
due to server HALT processing that is in progress. with clients using the TCP/IP Version 6 protocol on the
session request for this session fails. System action: Server operation continues.

ANR8230I (Linux) • ANR8233E (HP-UX)
accept with the MAXSESSIONS or the

ANR8230I (Linux) TCP/IP Version 6 driver ready for
NETBIOSSESSIONS option, or both, in the server
options file.
number.
ANR8232W (Windows) Unable to create thread to
listen for NETBIOS sessions on adapter
network adapter number.
User response: None. inability to create a new thread of execution to monitor
the indicated network adapter.
ANR8230I (Solaris) TCP/IP Version 6 driver ready System action: Server operation continues, but
for connection with clients on port port NETBIOS communications is inoperative on the
number. indicated adapter. Other adapters remain unaffected.
Explanation: The server can now accept sessions with User response: The most likely cause is a lack of
clients using the TCP/IP Version 6 protocol on the memory. Ensure that there is sufficient space for the
indicated port number. Windows paging file. Click on the system icon in the
User response: None. instructions on how to increase the amount of virtual
memory. You may also wish to cut down on the
ANR8230W (Windows) Insufficient memory to start accept with the MAXSESSIONS or the
NETBIOS session on adapter network NETBIOSSESSIONS option, or both, in the server
adapter number. options file.
due to a memory allocation request failure on the ANR8233E (AIX) Unable to acquire local port
specified adapter. information. getaddrinfo return code
System action: Server operation continues, but the return code.
session request fails. Explanation: The server or storage agent used the
User response: The most likely cause is a lack of system getaddrinfo API to determine which TCP/IP
memory. Ensure that there is sufficient space for the protocols could be used. A failure occurred, as
Windows paging file. Click on the system icon in the indicated by the system error code that is shown. The
Windows NT control panel and then click on the server was initializing TCP/IP communications.
virtual memory button. Refer to the online help for System action: TCP/IP communications is inoperatve.
memory. You may also wish to cut down on the User response: System information concerning return
maximum number of sessions that the server can codes from the getaddrinfo system API should be
accept with the MAXSESSIONS or the consulted. Ensure that TCP/IP networking for either
NETBIOSSESSIONS option, or both, in the server TCP/IP version 4 or version 6 is operating correctly.
options file.
ANR8233E (HP-UX) Unable to acquire local port
ANR8231W (Windows) Unable to create thread to information. getaddrinfo return code
accept NETBIOS sessions. return code.
Explanation: The server cannot initialize due to the Explanation: The server or storage agent used the
inability to create a new thread of execution. system getaddrinfo API to determine which TCP/IP
protocols could be used. A failure occurred, as
System action: Server operation continues, but indicated by the system error code that is shown. The
NETBIOS communications is inoperative. server was initializing TCP/IP communications.
User response: The most likely cause is a lack of System action: TCP/IP communications is inoperatve.
Windows paging file. Click on the system icon in the User response: System information concerning return
Windows NT control panel and then click on the codes from the getaddrinfo system API should be
virtual memory button. Refer to the online help for consulted. Ensure that TCP/IP networking for either
instructions on how to increase the amount of virtual TCP/IP version 4 or version 6 is operating correctly.

ANR8233E (Linux) • ANR8235W (Windows)

ANR8233E (Linux) Unable to acquire local port
information. getaddrinfo return code System action: Server operation continues.
return code.
Explanation: The server or storage agent used the
system getaddrinfo API to determine which TCP/IP
protocols could be used. A failure occurred, as ANR8234I (HP-UX) The TCP/IP Version 6
indicated by the system error code that is shown. The administrative driver is ready for
server was initializing TCP/IP communications. connection with clients on port port
number.
System action: TCP/IP communications is inoperatve.
User response: System information concerning return administrative clients using the TCP/IP Version 6
codes from the getaddrinfo system API should be protocol on the indicated port number.
consulted. Ensure that TCP/IP networking for either
TCP/IP version 4 or version 6 is operating correctly. System action: Server operation continues.
ANR8233E (Solaris) Unable to acquire local port
information. getaddrinfo return code ANR8234I (Linux) TCP/IP Version 6 administrative
return code. driver ready for connection with clients
Explanation: The server or storage agent used the on port port number.
system getaddrinfo API to determine which TCP/IP Explanation: The server can now accept sessions with
protocols could be used. A failure occurred, as administrative clients using the TCP/IP Version 6
indicated by the system error code that is shown. The protocol on the indicated port number.
server was initializing TCP/IP communications.
User response: System information concerning return
codes from the getaddrinfo system API should be
consulted. Ensure that TCP/IP networking for either ANR8234I (Solaris) TCP/IP Version 6 administrative
TCP/IP version 4 or version 6 is operating correctly. driver ready for connection with clients
ANR8233W (Windows) Unable to create thread to Explanation: The server can now accept sessions with
handle NETBIOS session session number administrative clients using the TCP/IP Version 6
on adapter network adapter number. protocol on the indicated port number.
Explanation: The server cannot start a new client System action: Server operation continues.
session on the indicated adapter due to an inability to User response: None.
start a separate thread of execution for the indicated
session.
ANR8234I (Windows) TCP/IP Version 6
System action: Server operation continues, but this administrative driver ready for
session request fails. connection with clients on port port
User response: The most likely cause is a lack of number.
memory. Ensure that there is sufficient space for the Explanation: The server can now accept sessions with
Windows paging file. Click on the system icon in the administrative clients using the TCP/IP Version 6
Windows NT control panel and then click on the protocol on the indicated port number.
instructions on how to increase the amount of virtual System action: Server operation continues.
memory. You may also wish to cut down on the User response: None.
accept with the MAXSESSIONS or the
NETBIOSSESSIONS option, or both, in the server ANR8235W (Windows) Requested number of
options file. NETBIOS sessions are not available on
adapter network adapter number,
proceeding with available sessions.
ANR8234I (AIX) TCP/IP Version 6 administrative
driver ready for connection with clients Explanation: The server cannot acquire the requested
on port port number. number of NETBIOS sessions for the indicated adapter.
The server attempts to acquire the number of NETBIOS
Explanation: The server can now accept sessions with sessions as indicated by the NETBIOSSESSIONS

ANR8236W (Windows) • ANR8261W (Windows)
parameter of the server options file or, if this option is

ANR8237E (Windows) Unable to acquire local port
not specified, by the MAXSESSIONS option.
information. getaddrinfo return code
System action: Server operation continues, but the return code.
maximum number of NETBIOS sessions is limited to
Explanation: The server or storage agent used the
the number of sessions that are acquired.
system getaddrinfo API to determine which TCP/IP
User response: Ensure that the required number of protocols could be used. A failure occurred, as
NETBIOS resources are not already in use. If the LAN indicated by the system error code that is shown. The
Server or LAN Requester application is running, you server was initialize TCP/IP communications.
have NETBIOS configured. In that case, starting the
server prior to starting LAN Server or LAN Requester
may allow the server to obtain the requested NETBIOS User response: System information concerning return
resources. codes from the getaddrinfo system API should be
consulted. Ensure that TCP/IP networking for either
TCP/IP version 4 or version 6 is operating correctly.
ANR8236W (Windows) Failure while listening for
NETBIOS sessions on adapter network
adapter number, NETBIOS listen return ANR8238E (Windows) Session Session identifier
code=listen return code. aborted due to Aspera FASP Read error;
error error code : error code2 .
Explanation: The server cannot listen for NETBIOS
sessions on the indicated adapter. The indicated listen Explanation: The session between the server and the
return code was received from the NETBIOS listen API. specified partner experienced a communication error
If the return code is 24, (hex 18), the listen is retried. receiving data.
System action: Server operation continues. If the System action: The session with the remote system is
return code is 24 (hex 18), a new listen is setup because ended.
return code 24 indicates a temporary failure. Otherwise,
no additional NETBIOS sessions will start using the
indicated adapter until the problem is corrected and the
Aspera FASP.
server is restarted.
User response: A NETBIOS listen failure is an
ANR8239E (Windows) Session Session identifier
indication of a network problem, an adapter problem,
aborted due to Aspera Write error; error
or a NETBIOS configuration problem. The following
error code : error code2 .
system configuration and system environment listen
return codes (in hex) and resolution actions for a listen Explanation: The session between the server and the
failure are found in the IBM Local Area Network specified partner system experienced a communication
Technical Reference: error sending data.
Return Code Description System action: The session with the remote system is
11 The local session table is full. The ended.
maximum number of sessions are in User response: Ensure that the specified remote
use. Change NETBIOS configuration to system is operational and is properly configured to run
increase the maximum number of Aspera FASP.
sessions.
19 Name conflict. Ensure that the Server
NETBIOS name is not in use elsewhere ANR8260I (Windows) Named Pipes driver ready for
on the network. connection with clients.
22 There are too many commands pending. Explanation: The server is now able to accept sessions
The maximum number of sessions are in with clients using the Named Pipes protocol.
use. Change NETBIOS configuration to
increase the maximum number of System action: Server operation continues.
sessions. User response: None.
35 The operating system resources are
exhausted. A reboot is probably
required. ANR8261W (Windows) Named Pipes connection
terminated - insufficient memory.
System action: Server operation continues. Named
Pipes communications is inoperative.

User response: The most likely cause is a lack of intentionally stopping either the client or server, no
memory. Ensure that there is sufficient space for the response is required.
ANR8265W (Windows) Error open Named Pipes
Named Pipes name, CreateNamedPipe
return code return code.
maximum number of sessions that the server can Explanation: The server experiences an error return
accept with the MAXSESSIONS option in the server code when trying to open the indicated Named Pipes
options file. name for Named Pipes communication with a client.
The return code shown is returned by the Windows
CreateNamedPipe API.
ANR8262W (Windows) Named Pipes driver is
terminating due to error in creating a System action: The session is ended. Server operation
new thread. continues. Named Pipes communications is inoperative.
Explanation: The server cannot initialize due to the User response: The server may have run out of file
inability to create a new thread of execution. handles. Stop and restart the server to reenable Named
Pipes communications. It is not normal to run out of
System action: Server operation continues, but Named
file handles. A system or logic error may be the
Pipes communications is inoperative.
underlying cause.
ANR8266W (Windows) Error accepting connection
on Named Pipes Named Pipes name,
ConnectNamedPipe return code return
code.
memory. You may also wish to cut down on the Explanation: The server experiences an error return
maximum number of sessions that the server can code when trying to complete a connection on the
accept with the MAXSESSIONS option in the server indicated Named Pipes name for Named Pipes
options file. communication with a client. The return code shown is
returned by the Windows ConnectNamedPipe API.
ANR8263W (Windows) Error sending data on Named System action: The session is ended. Server operation
Pipes, session session number.WriteFile continues. Named Pipes communications is inoperative.
Return code is return code.
User response: A system problem may be preventing
Explanation: The server experiences an error return use of Named Pipes. Stop and restart the server to
code from the WriteFile Windows NT API while reenable Named Pipes communications.
writing data to Named Pipes over the indicated
session. This may be a normal event if either side of the
connection is abruptly ended. ANR8267W (Windows) Error initializing a security
descriptor for Named Pipes Named Pipes
System action: The session is ended. Server operation name, reason: System message.
continues.
Explanation: The server experiences an error return
User response: If the session is ended as a result of code when trying to initialize the indicated Named
intentionally stopping either the client or server, no Pipe for Named Pipes communication with a client.
response is required. The reason shown is returned by the Windows
FormatMessage API.
ANR8264W (Windows) Error reading data on Named System action: The session is ended. Server operation
Pipes, session session number. ReadFile continues. Named Pipes communications is inoperative.
return code is return code.
User response: Administrator Privileges are required.
Explanation: The server experiences an error return Login using an account wit h Administrator privileges
code from the ReadFile Windows API while reading and restart the server to reenable Named Pipes
data from Named Pipes in the indicated session. This communications.
may be a normal event if either side of the connection
is ended abruptly.
ANR8268W (Windows) Named Pipe communications
System action: The session is ended. Server operation were not enabled due to an error
continues. looking up the following Windows
group name: Windows group name. Use
the Windows User manager to add the

ANR8269W (Windows) • ANR8282I (Linux)
specified group. Members of the group

ANR8275W (Windows) Shared memory connection
will then use Windows unified logon to
terminated - insufficient memory.
access the server over Named pipes.
Explanation: The server experiences an error return
code when trying to initialize the indicated Named
Pipe for Named Pipes communication with a client. System action: Server operation continues. Shared
The system could not find the Windows Account name memory communications is inoperative.
System action: The session is ended. Server operation memory. Ensure that there is sufficient space for the
continues. Named Pipes communications is inoperative. Windows paging file. Click on the system icon in the
User response: To use Windows unified logon specify
the name of a valid Windows account or group name.
Restart the server to reenable Named Pipes
communications.
ANR8269W (Windows) Error opening Named Pipe options file.
Named Pipes name, reason: System message.
Explanation: The server experiences an error return ANR8276W (Windows) Shared memory connection
code when trying to open the indicated Named Pipe terminated - unable to initialize. Key
name for Named Pipes communication with a client. channel key, Reason: reason code.
The reason shown is returned by the Windows
FormatMessage API.
due being unable to initialize shared memory.
System action: Server operation continues. Shared
continues. Named Pipes communications is inoperative.
memory communications are inoperative.
User response: Consider the reason text and take
User response: Try a different shared memory session.
appropriate action. Stop and restart the server to
reenable Named Pipes communications.
ANR8277E (Windows) Shared memory unable to
initialize - Port: shm port number, Reason:
ANR8273I (Windows) Shared memory driver ready
reason code.
for connection with clients on port port
number. Explanation: The server cannot accept a client session
because it could not intialize a communication channel.
Make sure no other server or storage agent running on
with clients using the shared memory protocol on the
the same machine is using the same shm port number.
indicated port.
System action: Server operation continues. Shared
memory communications are inoperative.
User response: Try a different shared memory session.
ANR8274W (Windows) Shared memory

ANR8282I (HP-UX) SNMP driver ready for
communications driver is terminating
connection with subagent on port port
due to error in creating a new thread.
number.
SNMP subagents on the indicated port number.
System action: Server operation continues, but shared
memory communications is inoperative.
Windows paging file. Click on the system icon in the ANR8282I (Linux) SNMP driver ready for connection
Windows NT control panel and then click on the with subagent on port port number.
SNMP subagents on the indicated port number.
memory.

ANR8282I (Solaris) • ANR8284E (Solaris)
User response: None. subagents. The reason code is the return code from the
TCP/IP bind API.
ANR8282I (Solaris) SNMP driver ready for System action: Server operation continues, but the
connection with subagent on port port server cannot accept sessions from SNMP subagents to
number. run macro commands.
Explanation: The server can now accept sessions with User response: Ensure that no other application is
SNMP subagents on the indicated port number. using the port number specified in the server options
file with the PORT option. If TCP/IP is also in use for
client sessions, ensure that the same port number is not
User response: None. specified for TCP/IP communications and SNMP
communications.
ANR8283W (HP-UX) SNMP driver unable to
initialize due to error in using Port port, ANR8284E (AIX) The Shared Memory
reason code reason code. Communications Protocol could not
initialize.
communications, the server has failed to connect to a Explanation: The server was unable to initialize the
master TCP/IP socket on which to listen to SNMP Shared Memory Communications Protocol due to an
subagents. The reason code is the return code from the error.
TCP/IP bind API.
System action: Server operation continues without
System action: Server operation continues, but the Shared Memory Communications.
server cannot accept sessions from SNMP subagents to
run macro commands.
the cause of the failure.
ANR8284E (HP-UX) The Shared Memory
file with the SNMPSUBAGENT PORT option. If
Communications Protocol could not
TCP/IP is also in use for client sessions, ensure that the
initialize.
same port number is not specified for TCP/IP
communications and SNMP communications. This may Explanation: The server was unable to initialize the
be done by issuing the TCP/IP netstat command. Shared Memory Communications Protocol due to an
error.
ANR8283W (Linux) SNMP driver unable to initialize System action: Server operation continues without
due to error in BINDing to Port port, Shared Memory Communications.
reason code reason code.
Explanation: While initializing TCP/IP the cause of the failure.
communications, the server has failed to connect to a
master TCP/IP socket on which to listen to SNMP
ANR8284E (Linux) The Shared Memory
subagents. The reason code is the return code from the
Communications Protocol could not
TCP/IP bind API.
initialize.
Explanation: The server was unable to initialize the
server cannot accept sessions from SNMP subagents to
Shared Memory Communications Protocol due to an
run macro commands.
error.
Shared Memory Communications.
file with the PORT option. If TCP/IP is also in use for
client sessions, ensure that the same port number is not User response: Examine previous error messages for
specified for TCP/IP and SNMP communications. the cause of the failure.
ANR8283W (Solaris) SNMP driver unable to ANR8284E (Solaris) The Shared Memory
initialize due to error in BINDing to Communications Protocol could not
Port port, reason code reason code. initialize.
Explanation: While initializing TCP/IP Explanation: The server was unable to initialize the
communications, the server has failed to connect to a Shared Memory Communications Protocol due to an
master TCP/IP socket on which to listen to SNMP error.

ANR8285I (AIX) • ANR8286W (Windows)
Shared Memory Communications. User response: Ensure that there is sufficient paging
space for AIX. You may also use SMIT to determine if
the number of applications is causing a memory
the cause of the failure.
shortage. It may be necessary to cut down on the
maximum number of client sessions by changing the
ANR8285I (AIX) Shared Memory driver ready for MAXSESSIONS option in the server options file.
Explanation: The server is now able to accept sessions ANR8286W (HP-UX) Unable to initialize Shared
with clients using the Shared Memory protocol. Memory driver - insufficient memory.
System action: Server operation continues. Explanation: Because the operating system rejected a
User response: None. communications through the Shared Memory protocol.
ANR8285I (HP-UX) Shared Memory driver ready for server cannot accept sessions from clients using the
connection with clients on port port Shared Memory protocol.
Explanation: The server is now able to accept sessions User response: Ensure that there is sufficient paging
with clients using the Shared Memory protocol. space for HP-UX. You may also use SAM to determine
System action: Server operation continues. if the number of applications is causing a memory
shortage. It may be necessary to cut down on the
User response: None. maximum number of client sessions by changing the
ANR8285I (Linux) Shared Memory driver ready for
connection with clients on port port ANR8286W (Linux) Unable to initialize Shared
Explanation: The server is now able to accept sessions Memory driver - insufficient memory.
with clients using the Shared Memory protocol. Explanation: Because the operating system rejected a
System action: Server operation continues. memory allocation request, the server cannot start
communications through the Shared Memory protocol.
ANR8285I (Solaris) Shared Memory driver ready for Shared Memory protocol.
User response: Ensure that there is sufficient swap
Explanation: The server is now able to accept sessions space for Solaris. It may be necessary to cut down on
with clients using the Shared Memory protocol. the maximum number of client sessions by changing
System action: Server operation continues. the MAXSESSIONS option in the server options file.

ANR8286W (Solaris) Unable to initialize Shared
Memory driver - insufficient memory.
ANR8285I (Windows) SNMP driver ready for
connection with subagent on port port Explanation: Because the operating system rejected a
number. memory allocation request, the server cannot start
SNMP subagents on the indicated port number. System action: Server operation continues, but the
System action: Server operation continues. Shared Memory protocol.
User response: None. User response: Ensure that there is sufficient swap
space for Solaris. It may be necessary to cut down on
the maximum number of client sessions by changing
ANR8286W (AIX) Unable to initialize Shared
the MAXSESSIONS option in the server options file.
Memory driver - insufficient memory.
Explanation: Because the operating system rejected a
ANR8286W (Windows) SNMP driver unable to
initialize due to error in BINDing to
Port port, reason code reason code.
communications, the server has failed to connect to a
Shared Memory protocol.

master TCP/IP socket on which to listen to SNMP User response: If TCP/IP is not started, use the HALT
subagents. The reason code is the return code from the command from any prompt to stop the server, and
TCP/IP bind API. restart it.
server cannot accept sessions from SNMP subagents to ANR8287W (Solaris) Unable to initialize Shared
run macro commands. Memory driver - error creating acceptor
socket. Reason code reason code.
using the port number specified in the server options Explanation: Because TCP/IP rejected a request for a
file with the PORT option. If TCP/IP is also in use for socket on which to listen, the server cannot start
client sessions, ensure that the same port number is not communications through Shared Memory.
specified for TCP/IP communications and SNMP
communications. This may be done by issuing the
TCP/IP netstat -s command. If the server is brought
down and then started immediately, you may be within
the TCP/IP one minute timeout period for port User response: If TCP/IP is not started, use the HALT
reusage. Bring down the sever, wait one minute, and command from any server prompt to stop the server,
then restart the server. If that does not work, it may be and restart it.
necessary to restart Windows.
ANR8288W (AIX) Unable to establish Shared
ANR8287W (AIX) Unable to initialize Shared Memory connection - insufficient
Memory driver - error creating acceptor memory.
Explanation: Because TCP/IP rejected a request for a due to a memory allocation request failure.
socket on which to listen, the server cannot start
communications through Shared Memory. System action: Server operation continues, but the
server cannot accept sessions from clients using the User response: Ensure that there is sufficient paging
Shared Memory protocol. space for AIX. You may also use SMIT to determine if
the number of applications is causing a memory
User response: If TCP/IP is not started, use the HALT shortage. You may also wish to cut down on the
command from any server prompt to stop the server, maximum number of sessions that the server can
and restart it. accept with the MAXSESSIONS option in the server
options file.
ANR8287W (HP-UX) Unable to initialize Shared
Memory driver - error creating acceptor ANR8288W (HP-UX) Unable to establish Shared
socket. Reason code reason code. Memory connection - insufficient
memory.
Explanation: Because TCP/IP rejected a request for a
socket on which to listen, the server cannot start Explanation: The server cannot accept a client session
communications through Shared Memory. due to a memory allocation request failure.
server cannot accept sessions from clients using the session request for this session fails.
User response: If TCP/IP is not started, use the HALT space for HP-UX. You may also use SAM to determine
command from any server prompt to stop the server, if the number of applications is causing a memory
and restart it. shortage. You may also wish to cut down on the
ANR8287W (Linux) Unable to initialize Shared
options file.
Memory driver - error creating acceptor
ANR8288W (Linux) Unable to establish Shared
Explanation: Because TCP/IP rejected a request for a
Memory connection - insufficient
socket on which to listen, the server cannot start
memory.
communications through Shared Memory.
Shared Memory protocol. System action: Server operation continues, but the

ANR8288W (Solaris) • ANR8290W (HP-UX)

ANR8289W (Linux) Shared Memory driver is
User response: Ensure that there is sufficient swap terminating due to error in creating a
space for Solaris. You may also wish to cut down on new thread.
the maximum number of sessions that the server can
options file.
System action: Server operation continues, but Shared
Memory communications is inoperative.
ANR8288W (Solaris) Unable to establish Shared
Memory connection - insufficient User response: The most likely cause is a lack of
memory. memory. Ensure that there is sufficient swap space for
Solaris. You may also wish to cut down on the
System action: Server operation continues, but the options file.
User response: Ensure that there is sufficient swap ANR8289W (Solaris) Shared Memory driver is
space for Solaris. You may also wish to cut down on terminating due to error in creating a
the maximum number of sessions that the server can new thread.
options file.
ANR8289W (AIX) Shared Memory driver is
terminating due to error in creating a
new thread. User response: The most likely cause is a lack of
memory. Ensure that there is sufficient swap space for
Solaris. You may also wish to cut down on the
System action: Server operation continues, but Shared accept with the MAXSESSIONS option in the server
Memory communications is inoperative. options file.
memory. Ensure that there is sufficient paging space for ANR8290W (AIX) Error sending data through Shared
AIX. You may also use SMIT to determine if the Memory. Reason return code.
number of applications is causing a memory shortage.
You may also wish to cut down on the maximum
code while sending data through shared memory. This
number of sessions that the server can accept with the
is abruptly ended.
ANR8289W (HP-UX) Shared Memory driver is
continues.
terminating due to error in creating a
new thread. User response: If the session is ended as a result of
ANR8290W (HP-UX) Error sending data through
Shared Memory. Reason return code.
memory. Ensure that there is sufficient paging space for
HP-UX. You may also use SAM to determine if the
number of applications is causing a memory shortage.
is abruptly ended.
You may also wish to cut down on the maximum
number of sessions that the server can accept with the System action: The session is ended. Server operation
MAXSESSIONS option in the server options file. continues.

ANR8290W (Linux) • ANR8292W (AIX)

ANR8290W (Linux) Error sending data through
continues.
is abruptly ended.
ANR8291W (Linux) Error receiving data through
continues.
code while receiving data through the Shared Memory
protocol. This may be a normal event if either side of
the connection is abruptly ended.
ANR8290W (Solaris) Error sending data through
continues.
is abruptly ended.
ANR8291W (Solaris) Error receiving data through
continues.
ANR8290I (Windows) IPX/SPX driver ready for
continues.
connection with clients on socket IPX
socket number. User response: If the session is ended as a result of
with clients using the IPX/SPX protocol on the
indicated socket number.
ANR8291W (Windows) Unable to bind to IPX/SPX
master socket. Return code = return code.
Explanation: The server cannot initiate
communications on the socket number designated for
ANR8291W (AIX) Error receiving data through its use.
Explanation: The server experienced an error return communications using the IPX/SPX protocol is
code while receiving data through the Shared Memory inoperative.
User response: Ensure that SPX has been configured
to run on this system through the requester
System action: The session is ended. Server operation configuration program. Ensure that there is no other
continues. instance of the server running on the same system that
is using the same socket number. This is likely to be the
case if the return code is zero. Also ensure that the
number of SPX sessions (as specified in your NET.CFG
file) has not been exceeded through other applications
using the IPX/SPX protocol.
ANR8291W (HP-UX) Error receiving data through
ANR8292W (AIX) Session terminated when no data
Explanation: The server experienced an error return was read through Shared Memory.
Explanation: The server is unable to read data from
Shared Memory. This may be a normal event if either

ANR8292W (HP-UX) • ANR8293W (Solaris)
System action: The session is ended. Server operation accept with the MAXSESSIONS option in the server
continues. options file.
intentionally stopping either the client or server, no ANR8293W (AIX) Shared Memory driver unable to
response is required. initialize due to socket initialization
error.
ANR8292W (HP-UX) Session terminated when no Explanation: While initializing Shared Memory
data was read through Shared Memory. communications, the server failed to set up an interface
with TCP/IP.
Shared Memory. This may be a normal event if either System action: Server operation continues, but the
side of the connection is abruptly ended. server cannot accept sessions from clients using the
continues. User response: Ensure that TCP/IP has been started
ANR8293W (HP-UX) Shared Memory driver unable

ANR8292W (Linux) Session terminated when no data
to initialize due to socket initialization
was read through Shared Memory.
error.
Explanation: While initializing Shared Memory
Shared Memory. This may be a normal event if either
communications, the server failed to set up an interface
with TCP/IP.
continues.
User response: If the session is ended as a result of Shared Memory protocol.
User response: Ensure that TCP/IP has been started
ANR8292W (Solaris) Session terminated when no that TCP/IP is both started and active.
data was read through Shared Memory.
Explanation: The server is unable to read data from ANR8293W (Linux) Shared Memory driver unable to
Shared Memory. This may be a normal event if either initialize due to socket initialization
side of the connection is abruptly ended. error.
System action: The session is ended. Server operation Explanation: While initializing Shared Memory
continues. communications, the server failed to set up an interface
with TCP/IP.
intentionally stopping either the client or server, no System action: Server operation continues, but the
response is required. server cannot accept sessions from clients using the
ANR8292W (Windows) IPX/SPX connection User response: Ensure that TCP/IP has been started
terminated - insufficient memory. and is active on your system. You may issue the
Explanation: The server cannot accept a client session that TCP/IP is both started and active.
System action: Server operation continues. ANR8293W (Solaris) Shared Memory driver unable
User response: The most likely cause is a lack of to initialize due to socket initialization
memory. Ensure that there is sufficient space for the error.
Windows paging file. Click on the system icon in the Explanation: While initializing Shared Memory
Windows NT control panel and then click on the communications, the server failed to set up an interface
virtual memory button. Refer to the online help for with TCP/IP.
memory. You may also wish to cut down on the System action: Server operation continues, but the

ANR8293W (Windows) • ANR8295W (HP-UX)
server cannot accept sessions from clients using the assistance in resolving the error.
User response: Ensure that TCP/IP has been started ANR8294W (Solaris) Shared Memory session unable
and is active on your system. You may issue the to initialize.
Explanation: While initializing a Shared Memory
communications session, an error occurred during
initial setup.
ANR8293W (Windows) IPX/SPX driver unable to
initialize due to error in LISTENing on
session is terminated.
the master socket, return code = return
code. User response: Contact your service representative for
assistance in resolving the error.
Explanation: While attempting to listen for session
requests from clients using IPX/SPX, the server
encountered an error. ANR8294W (Windows) Unable to establish IPX/SPX
connection - accept error. Return code =
tli error.
using the IPX/SPX protocol. Explanation: The server cannot accept a client session
due to a failure in accepting the connection from
User response: Ensure that IPX/SPX is still running
IPX/SPX.
properly and that it has not been intentionally or
unintentionally stopped. This may be done by using System action: Server operation continues, but this
the getipxad command to determine if an endpoint can session request fails.
still be opened and bound; also determine if you can
still connect to a NetWare server. User response: Ensure that SPX has been configured
to run on this system through the requester
configuration program. Ensure that there is no other
ANR8294W (AIX) Shared Memory session unable to instance of the server running on the same system that
initialize. is using the same socket number. Also ensure that the
number of SPX sessions has not been exceeded through
Explanation: While initializing a Shared Memory
other applications using the IPX/SPX protocol, such as
communications session, an error occurred during
NetWare applications.
initial setup.
ANR8295W (AIX) Shared Memory driver unable to
session is terminated.
initialize due to error in BINDing to
User response: Contact your service representative for Port port, reason code reason code.
Explanation: While initializing Shared Memory
communications, the server failed to connect to a
ANR8294W (HP-UX) Shared Memory session unable master socket on which to listen for clients. The reason
to initialize. code is the return code from the TCP/IP bind API.
Explanation: While initializing a Shared Memory System action: Server operation continues, but the
communications session, an error occurred during server cannot accept sessions from clients using the
initial setup. Shared Memory protocol.
System action: Server operation continues, but the User response: Ensure that no application is using the
session is terminated. port number specified in the server options file with
the SHMPORT option by issuing the TCP/IP netstat
User response: Contact your service representative for
command. If the server was brought down and client
sessions were active, it may be necessary to terminate
the client sessions on the client systems before the port
ANR8294W (Linux) Shared Memory session unable can be freed.
to initialize.
Explanation: While initializing a Shared Memory ANR8295W (HP-UX) Shared Memory driver unable
communications session, an error occurred during to initialize due to error in using Port
initial setup. port, reason code reason code.
System action: Server operation continues, but the Explanation: While initializing Shared Memory
session is terminated. communications, the server failed to connect to a
master socket on which to listen for clients. The reason

ANR8295W (Linux) • ANR8296W (Linux)
code is the return code from the TCP/IP bind API. System action: The session is ended. Server operation
continues.
server cannot accept sessions from clients using the User response: If the session is ended as a result of
Shared Memory protocol. intentionally stopping either the client or server, no
response is required. Otherwise, ensure that IPX/SPX is
User response: Ensure that no application is using the
still active.
port number specified in the server options file with
the SHMPORT option by issuing the TCP/IP netstat
command. If the server was brought down and client ANR8296W (AIX) Shared Memory driver unable to
sessions were active, it may be necessary to terminate initialize due to error in LISTENing on
the client sessions on the client systems before the port the specified Port, reason code reason
can be freed. code.
ANR8295W (Linux) Shared Memory driver unable to requests from clients using TCP/IP, TCP/IP returns an
initialize due to error in BINDing to error. The reason code is the return code from the
Port port, reason code reason code. TCP/IP listen API.
Explanation: While initializing Shared Memory System action: Server operation continues, but the
communications, the server failed to connect to a server cannot accept additional sessions from clients
master socket on which to listen for clients. The reason using the Shared Memory protocol.
code is the return code from the TCP/IP bind API.
System action: Server operation continues, but the properly by issuing the TCP/IP netstat -s and ping
server cannot accept sessions from clients using the commands to other nodes on your network. It may be
Shared Memory protocol. possible to bring the server down and restart it to
allow additional client sessions to start.
port number specified in the server options file with
the SHMPORT option by issuing the TCP/IP netstat ANR8296W (HP-UX) Shared Memory driver unable
command. If the server was brought down and client to initialize due to error in LISTENing
sessions were active, it may be necessary to terminate on the specified Port, reason code reason
the client sessions on the client systems before the port code.
can be freed.
ANR8295W (Solaris) Shared Memory driver unable error. The reason code is the return code from the
to initialize due to error in BINDing to TCP/IP listen API.
Port port, reason code reason code.
Explanation: While initializing Shared Memory server cannot accept additional sessions from clients
communications, the server failed to connect to a using the Shared Memory protocol.
master socket on which to listen for clients. The reason
code is the return code from the TCP/IP bind API.
properly by issuing the TCP/IP netstat -s and ping
System action: Server operation continues, but the commands to other nodes on your network. It may be
server cannot accept sessions from clients using the possible to bring the server down and restart it to
Shared Memory protocol. allow additional client sessions to start.
port number specified in the server options file with ANR8296W (Linux) Shared Memory driver unable to
the SHMPORT option by issuing the TCP/IP netstat initialize due to error in LISTENing on
command. If the server was brought down and client the specified Port, reason code reason
sessions were active, it may be necessary to terminate code.
the client sessions on the client systems before the port
can be freed.
ANR8295W (Windows) Error sending data on session TCP/IP listen API.
session number. Reason return code.
Explanation: The server experiences an error return server cannot accept additional sessions from clients
code from IPX/SPX while sending data on the using the Shared Memory protocol.
indicated session. This may be a normal event if either

ANR8296W (Solaris) • ANR8298W (HP-UX)
commands to other nodes on your network. It may be

ANR8297W (Linux) Shared Memory driver is
possible to bring the server down and restart it to
terminating due to error in accepting a
new session, reason code reason code.
ANR8296W (Solaris) Shared Memory driver unable
request from a client using the Shared Memory
to initialize due to error in LISTENing
protocol, TCP/IP returns an error. The reason code is
on the specified Port, reason code reason
the return code from the TCP/IP accept API.
code.
using the Shared Memory protocol.
TCP/IP listen API. User response: Ensure that TCP/IP is running
ANR8297W (Solaris) Shared Memory driver is
commands to other nodes on your network. It may be
possible to bring the server down and restart it to
ANR8297W (AIX) Shared Memory driver is
the return code from the TCP/IP accept API.
the return code from the TCP/IP accept API. User response: Ensure that TCP/IP is running
error while writing data on socket socket
number. Reason return code.
Explanation: An error occurred during negotiation for
a shared memory session. This may be a normal event
ANR8297W (HP-UX) Shared Memory driver is
if either side of the connection is abruptly ended.
new session, reason code reason code. System action: The session is ended. Server operation
continues.
request from a client using the Shared Memory User response: If the session is ended as a result of
protocol, TCP/IP returns an error. The reason code is intentionally stopping either the client or server, no
the return code from the TCP/IP accept API. action is required. Otherwise, ensure that the client and
ANR8298W (HP-UX) The server experienced a
TCP/IP error while writing data on
network. It may be possible to bring the server down Explanation: An error occurred during negotiation for
and restart it to allow additional client sessions to start. a shared memory session. This may be a normal event

ANR8298W (Linux) • ANR8299W (Solaris)
System action: The session is ended. Server operation memory port is a TCP/IP port that the server uses to
continues. initiate communications, then switches to shared
memory communications.
action is required. Otherwise, ensure that the client and ANR8299W (HP-UX) The server experienced a
server can communicate using Telnet or FTP TCP/IP error while reading data on
applications, which are part of the TCP/IP suite. socket socket number. Reason return code.
ANR8298W (Linux) The server experienced a TCP/IP a shared memory session. This may be a normal event
error while writing data on socket socket if either side of the connection is abruptly ended or if
number. Reason return code. the client is configured incorrectly.
Explanation: An error occurred during negotiation for System action: The session is ended. Server operation
a shared memory session. This may be a normal event continues.
System action: The session is ended. Server operation intentionally stopping either the client or server, no
continues. action is required. Otherwise, ensure that the client and
action is required. Otherwise, ensure that the client and Check the client options file to ensure that the server's
server can communicate using Telnet or FTP shared memory port is set up and is not being
applications, which are part of the TCP/IP suite. confused with the server's TCP/IP port. The shared
memory port is a TCP/IP port that the server uses to
initiate communications, then switches to shared
ANR8298W (Solaris) The server experienced a
memory communications.
TCP/IP error while writing data on
ANR8299W (Linux) The server experienced a TCP/IP
error while reading data on socket socket
continues.
if either side of the connection is abruptly ended or if
User response: If the session is ended as a result of the client is configured incorrectly.
continues.
applications, which are part of the TCP/IP suite. User response: If the session is ended as a result of
error while reading data on socket socket
Check the client options file to ensure that the server's
shared memory port is set up and is not being
confused with the server's TCP/IP port. The shared
if either side of the connection is abruptly ended or if
memory port is a TCP/IP port that the server uses to
the client is configured incorrectly.
initiate communications, then switches to shared
System action: The session is ended. Server operation memory communications.
continues.
User response: If the session is ended as a result of ANR8299W (Solaris) The server experienced a
intentionally stopping either the client or server, no TCP/IP error while reading data on
action is required. Otherwise, ensure that the client and socket socket number. Reason return code.
Check the client options file to ensure that the server's if either side of the connection is abruptly ended or if
shared memory port is set up and is not being the client is configured incorrectly.
confused with the server's TCP/IP port. The shared

System action: The session is ended. Server operation Explanation: An I/O error has occurred while
continues. operating on the specified drive.
User response: If the session is ended as a result of System action: The operation fails.
User response: Ensure that the DEVICE parameter
associated with the drive was identified correctly in the
DEFINE PATH command and that the drive is
currently powered on and ready. The drive reference
Check the client options file to ensure that the server's manual usually contains tables that explain the values
shared memory port is set up and is not being of the KEY, ASC, and ASCQ fields. If the
confused with the server's TCP/IP port. The shared OP=SETMODE SCSI command fails and the KEY, ASC,
memory port is a TCP/IP port that the server uses to and ASCQ fields all display a value of FF, the tape
initiate communications, then switches to shared device driver that the IBM Spectrum Protect server uses
memory communications. does not issue this command to the tape drive. Ensure
that a correct version of a tape device driver is installed
on your system.
ANR8300E I/O error on library library name
(OP=internal code, CC=internal code,
KEY=internal code, ASC=internal code, ANR8303E I/O error on drive drive name
ASCQ=internal code, (OP=internal code, SENSE=internal code).
SENSE= sense data,
Explanation: An I/O error has occurred while
Description=error description). Refer to
operating on the specified drive.
the IBM Spectrum Protect
documentation on I/O error code System action: The operation fails.
descriptions.
Explanation: An I/O error has occurred while associated with the drive was identified correctly in the
operating on the specified library. DEFINE PATH command and that the drive is
currently powered on and ready.
ANR8304E Time out error on drive drive name in
associated with the library was identified correctly in
library library name.
the DEFINE PATH command and that the library is
currently powered on and ready. If the library has an Explanation: A time out condition occurred while
access door, make sure it is closed. The library waiting for the given drive to become ready so that
reference manual usually contains tables that explain automated library operations could be performed.
the values of the KEY, ASC, and ASCQ fields.
ANR8301E I/O error on library library name User response: Ensure that the DEVICE parameter
(OP=internal code, SENSE=internal code). associated with the drive was identified correctly in the
DEFINE PATH command, and that the device is
Explanation: An I/O error has occurred while currently powered on and ready.
operating on the specified library.
System action: The operation fails. ANR8305E Library library name is not ready or not
operational.
associated with the library was identified correctly in Explanation: The specified automated library device is
the DEFINE PATH command and that the library is either not ready or not in an operational state.
currently powered on and ready. If the library has an
access door, make sure it is closed. System action: Initialization of the library device fails.
User response: Ensure that the library is powered on
ANR8302E I/O error on drive drive name with and ready for automated operations. Further
volume volume name (OP=internal code, initialization attempts for the given library will usually
Error Number=internal code, CC=internal be postponed until the next attempt is made to access
code, rc = return code, KEY= internal code, the library for an automated operation. During server
ASC=internal code, ASCQ= internal code, startup, however, initialization may be retried after a
SENSE=sense data, short waiting period.
documentation on I/O error code
descriptions.

volume to be swapped out in order to make room for

ANR8306I Request number: Insert device type volume
the required volume.
volume name mount mode into the slot
with element number slot element of
library library name within time limit ANR8309E Mount attempt failed - library library
minutes; issue 'REPLY' along with the name is not defined.
request ID when ready.
Explanation: An attempt has been made to mount a
Explanation: A CHECKIN LIBVOLUME or a LABEL volume, but the attempt fails because the specified
LIBVOLUME command is in progress, and the library is not defined.
specified volume is needed. The server expects the
volume to be inserted into the slot with the specified System action: The operation fails.
element number of the given library within the time User response: Ensure that the LIBRARY attribute of
limit specified in the message. For the slot and element the device class associated with the mount operation
number diagram of your library, refer to the identifies a defined library. If not, correct the value of
documentation provided with the current ptf level. the LIBRARY attribute, or define the specified library
System action: The server waits until a REPLY and retry the operation.
command is issued, or until the time limit expires.
User response: Insert the volume into the slot and ANR8310E An I/O error occurred while accessing
issue a REPLY command, along with the request ID, to library library name.
tell the server that the volume has been inserted. Explanation: An I/O error occurs while accessing the
designated library.
ANR8307I Request number: Remove device type System action: The operation fails.
volume volume name from slot with
element number slot name of library User response: Ensure that the DEVICE parameter
library name; issue 'REPLY' along with associated with the library is identified correctly in the
the request ID when ready. DEFINE PATH command, and that the library is
Explanation: A CHECKOUT LIBVOLUME command access door, make sure it is closed. After checking and
has completed. You can remove the volume from the correcting these potential problems, retry the operation.
slot with the specified element number and store it
outside the library. For the slot and element number
diagram of your library, refer to the documentation ANR8311E An I/O error occurred while accessing
provided with the current ptf level. drive drive name for low-level operation
operation, errno = drive errno, rc = return
System action: The server waits until a REPLY code.
command is issued.
Explanation: An I/O error occurs while performing
User response: Remove the volume from the slot and the operation on the specified drive.
store it in a safe place. Issue a REPLY command, along
with the request ID, to tell the server that the volume System action: The operation fails.
has been removed. The volume can be returned to the User response: Ensure that the DEVICE parameter
library with the CHECKIN LIBVOLUME command. associated with the drive is identified correctly in the
DEFINE PATH command, and that the drive is
ANR8308I Request number: device type volume volume currently powered on and ready. After checking and
name is required for use in library library correcting these potential problems, retry the operation.
name; CHECKIN LIBVOLUME required For more information on I/O error codes, search on
within time limit minutes. I/O error code descriptions for server messages in the
IBM Knowledge Center.
Explanation: A mount request has been made for a
volume that is defined in a storage pool, but which is
currently checked out of the given library. ANR8312E Volume volume name could not be
located in library library name.
System action: The server waits until it detects that
the volume has been checked into the library, or the Explanation: The designated volume cannot be found
time limit expires. at its expected location in the given library.
User response: Obtain the required volume, and insert System action: The operation fails.
it into the library by issuing a CHECKIN LIBVOLUME User response: Perform an AUDIT LIBRARY
command. Use the SWAP=YES option of the CHECKIN operation on the designated library, which forces the
LIBVOLUME command if the library is currently full; server to reevaluate its inventory information for
this process allows the server to select an appropriate volumes in the library.

ANR8313E Volume volume name is not present in ANR8317I The volume in device type drive drive
library library name. name must be manually ejected.
Explanation: A mount request is made for the given Explanation: This device type does not automatically
volume in the specified library, but the volume is not eject the volume when it is dismounted and requires
currently checked into the library. that the volume be manually ejected from the drive.
System action: The mount operation fails. If the System action: None.
volume is being mounted for storage pool I/O (as
User response: Physically eject the volume from the
opposed to import/export I/O), its ACCESS attribute is
drive.
changed to UNAVAILABLE to prevent further mount
requests.
ANR8318I Request number: Mount side side of device
User response: Issue a CHECKIN LIBVOLUME
type volume volume name mount mode in
command to return the volume into the library, and
drive drive name of library library name
update the volumes ACCESS attribute to READONLY
within time limit< minutes.
or READWRITE using the UPDATE VOLUME
command. Retry the mount request. Explanation: The server requires that the specified
volume be mounted as requested. Since the volume is
two-sided, this message specifies which side (A or B) is
ANR8314E Library library name is full.
needed by the server for I/O operations.
Explanation: A library operation fails because all of
System action: The server waits for the volume to be
the library's storage locations are occupied.
mounted.
User response: Mount the volume in the specified
User response: Issue a CHECKOUT LIBVOLUME drive.
command to make room in the library. Retry the library
operation.
ANR8319I Request number: Insert device type volume
volume name mount mode into library
ANR8315E Command: The device type of drive drive library name within time limit minute(s).
name is not supported in library type
Explanation: A CHECKIN LIBVOLUME command is
libraries.
in progress, and the specified volume is needed. The
Explanation: Drives of the type identified in the server expects the volume to be inserted into the
command are not supported in the given type of library with the convenience I/O station mechanism.
library.
System action: The server waits until the volume is in
System action: The command is not processed. the library, or until the time limit expires.
User response: Determine whether the drive and User response: Insert the specified volume into the
library combination is supported by the installed level library. If the volume has already been inserted into the
of the server. If so, contact your service representative. library, no user action is necessary.
ANR8316E Selecting swap volume to be checked ANR8320I Request number: Insert device type volume
out of library library name. volume name mount mode in drive drive
name of library library name within time
Explanation: A CHECKIN LIBVOL command was
limit minute(s); issue 'REPLY ' along
issued for a library that has no empty slots to hold the
with the request ID when ready.
new cartridge. The SWAP=YES parameter was included
in the command. Explanation: A CHECKIN LIBVOLUME or a LABEL
LIBVOLUME command is in progress, and the
System action: A CHECKOUT LIBVOL command will
specified volume is needed. The server expects the
be automatically be issued, specifying either a scratch
volume to be inserted in the designated drive of the
volume or, if there are none, a volume with the lowest
given library within the time limit specified in the
number of mounts.
message.
User response: Use a supported type of drive. volume
System action: The server waits until a REPLY
from the library and store it in a safe place. Issue a
REPLY command to tell the server that the volume has
been removed. The volume can be introduced back into User response: Insert the volume into the drive, and
the library with the CHECKIN LIBVOLUME command. then issue a REPLY command, along with the request
ID, to tell the server that the volume has been inserted.

ANR8321I Request number: Remove device type ANR8324I Device type volume volume name is
volume volume name from drive drive expected to be mounted (mount mode).
name of library library name; issue
Explanation: The specified volume is expected to be
'REPLY' along with the request ID when
mounted in the near future so the server can access it
ready.
for reading or writing.
Explanation: A CHECKOUT LIBVOLUME or a
LABEL LIBVOLUME command has completed. You can
remove the specified volume from the designated drive User response: If the volume is stored offline, retrieve
and store it outside the library. it so that it is readily accessible when the server
requests that it be mounted.
command is issued.
ANR8325I Dismounting volume volume name -
User response: Remove the volume from the drive
mount retention period minute mount
and store it in a safe place. Issue a REPLY command,
retention expired.
along with the request ID, to tell the server that the
volume has been removed. The volume can be returned Explanation: The specified volume is dismounted
to the library with the CHECKIN LIBVOLUME because the given mount retention period has expired.
command.
System action: The volume is dismounted.
ANR8322I Request number: Remove device type User response: None.

volume volume name from entry/exit port
of library library name; issue 'REPLY' ANR8326I Request number: Mount device type volume
along with the request ID when ready. volume name mount mode in drive drive
Explanation: A CHECKOUT LIBVOLUME command name of library library name within time
has completed. You can remove the specified volume limit minutes.
from the entry/exit port of the given library and store Explanation: If the volume name includes the names
it elsewhere. EXP, IMP, DUMP, or DBBK, the request is for a scratch
System action: The server waits until a REPLY volume.
command is issued. System action: The server waits for the volume to be
User response: Remove the volume from the library mounted.
and store it in a safe place. Issue a REPLY command, User response: Mount the volume in the specified
along with the request ID, to tell the server that the drive.
volume has been removed. The volume can be returned
to the library with the CHECKIN LIBVOLUME
command. ANR8327E Command: Cannot cancel request request
number.
ANR8323I Request number: Insert device type volume Explanation: The request, whose number is specified
volume name mount mode into entry/exit by the given command, cannot be canceled. The
port of library library name within time requested operation must be completed.
limit minute(s); issue 'REPLY' along with System action: The cancel request command is not
the request ID when ready. processed.
Explanation: A CHECKIN LIBVOLUME or a LABEL User response: Proceed with the requested operation.
LIBVOLUME command is in progress, and the
specified volume is needed. Mount the volume in the
entry/exit port of the given library within the time ANR8328I Request number: device type volume volume
limit specified in the message. name mounted in drive drive name.
System action: The server waits until a REPLY Explanation: The server verifies that a requested
command is issued, or until the time limit expires. volume has been mounted properly in the given drive.
User response: Insert the volume into the library's System action: The volume is accessed for reading or
entry/exit port; and issue a REPLY command, along writing, or both.
with the request ID, to tell the server that the volume User response: None.
has been inserted.

use, meaning that read or write operations, or both are

ANR8329I Device type volume volume name is
being performed.
mounted mount mode in drive drive name,
status: IDLE. System action: None.
Explanation: In response to a QUERY MOUNT User response: None.
command, the server indicates that the given volume is
mounted in the specified drive. The volume is currently
idle, meaning no active operations are being performed. ANR8334I Number of matches matches found.
If the volume remains in the idle state for the amount Explanation: This is a summary message for the
of time specified by the device class mount retention QUERY MOUNT command. It indicates the total
period, it will be automatically dismounted. number of mount points that have been reported in the
System action: None. command output.
User response: None. System action: None.

mounted mount mode in drive drive name, ANR8335I Request number: Verifying label of device
status: IN USE. type volume volume name in drive drive
Explanation: In response to a QUERY MOUNT name.
command, the server indicates that the given volume is Explanation: The server verifies the label of the
mounted in the specified drive. The volume is currently volume that has been requested by an earlier mount
in use, meaning that read or write operations, or both, message. This is done to ensure that the correct volume
are being performed. has been mounted by the operator.
System action: None. System action: The server reads the volume label and
User response: None. checks it for validity.
mounted mount mode in drive drive name, ANR8336I Verifying label of device type volume
status: DISMOUNTING. volume name in drive drive name.
Explanation: In response to a QUERY MOUNT Explanation: The server verifies the label of a volume
command, the server indicates that the given volume is that is needed for read or write operations, or both.
mounted in the specified drive. The volume is currently This is done to ensure that the correct volume has been
being dismounted by the server. mounted.
System action: None. System action: The server reads the volume label and
User response: None. checks it for validity.
mounted mount mode, status: IDLE. ANR8337I Device type volume volume name mounted
Explanation: In response to a QUERY MOUNT in drive drive name.
command, the server indicates that the given volume is Explanation: The server verifies that the specified
mounted for I/O operations. The volume is currently mount request has been completed properly. Read or
idle, meaning no active operations are being performed. write operations, or both, can be performed on the
If the volume remains in the idle state for the amount volume.
of time specified by the device class mount retention
period, it will be automatically dismounted. System action: The label of the volume has been
verified.
ANR8338E Device type volume volume name cannot

ANR8333I Device type volume volume name is be overwritten by EXPORT operation.
mounted mount mode, status: IN USE.
Explanation: The specified volume already exists or
Explanation: In response to a QUERY MOUNT contains data, so that the server cannot allow new
command, the server indicates that the given volume is export data to be written to it.
mounted for I/O operations. The volume is currently in
System action: The server detects that the given

volume already contains some data that would be System action: The system cancels the mount request
overwritten by the requested export operation. and marks the volume as unavailable.
User response: If the specified volume does not User response: None.
contain any valuable data, delete it and retry the export
operation.
ANR8344E Command: Invalid request number -
request number.
ANR8339E Device type volume intended volume name
Explanation: A command has been entered with an
in drive drive name was replaced with
incorrect request number.
volume incorrect volume name.
Explanation: The server detects that a previously
command.
mounted and verified volume (the desired volume) has
been replaced with a different volume (the incorrect User response: Issue the command with the correct
volume). No further read or write operations, or both, request number.
can occur on the given drive, because data corruption
may occur.
ANR8345E Command: No match found for this
System action: The server dismounts the volume from request number.
the drive.
Explanation: The request number specified by the
User response: Mount the correct volume again if it is command is not in the list of outstanding mount
in a manual library and retry the operation. requests.
ANR8340I Device type volume volume name command.
mounted.
User response: Issue the command with the correct
Explanation: The server has mounted the given request number.
volume.
System action: Read or write operations, or both, will ANR8346I Command: No requests are outstanding.
commence for the volume.
Explanation: A QUERY REQUEST or CANCEL
User response: None. REQUEST command has been entered although no
mount requests are outstanding.
ANR8341I End-of-volume reached for device type System action: Server operation continues.
volume volume name.
Explanation: The server has detected an
end-of-volume condition for the given volume.
ANR8347E Command: Volume volume not found.
System action: The volume is marked full. If more
data must be stored, the server will access another Explanation: A DISMOUNT VOLUME command is
volume for it. issued, but the volume to be dismounted cannot be
found.
ANR8342I Request request number for volume User response: Ensure that the correct volume name is
volume name canceled by administrator entered.
name.
Explanation: A mount request is canceled by the given ANR8348E Command: Volume volume is not "Idle".
administrator. Explanation: A DISMOUNT VOLUME command has
System action: The system cancels the mount request. been issued, but the volume is still in use and cannot
be dismounted.
ANR8343I Request request number for volume User response: If it is necessary to dismount the
volume name canceled (PERMANENT) by volume, cancel the session or process that is using the
administrator name. volume, and reissue the command.
Explanation: A mount request is successfully canceled

with the PERMANENT option.

v The DEVICE parameter associated with the drive is

ANR8349E Command: Device device not found.
identified correctly in the DEFINE PATH command,
Explanation: A DISMOUNT DEVICE command has and the drive is currently powered on and ready.
been issued, but the device to be dismounted cannot be
After checking and correcting these potential problems,
found.
retry the operation.
User response: Ensure that the correct device has been ANR8354E Request number: Incorrect volume (volume
specified. name) mounted in drive drive name.
Explanation: The user has inserted the named volume
ANR8350E Command: Device device is not "Idle". into the indicated drive, but it is not the one requested
by the server.
Explanation: A DISMOUNT DEVICE command has
been issued, but the device is still in use and cannot be System action: The volume is ejected, and the server
dismounted. continues to wait for the requested volume to be
mounted.
User response: Ensure that the requested volume is
User response: If it is necessary to dismount the
inserted properly into the designated drive.
device, cancel the session or process that is using the
device, and reissue the command.
ANR8355E I/O error reading label for volume
volume name in drive drive name.
ANR8351E Request number: Mount request for
volume volume name has timed out. Explanation: The server detects an error while
reading/verifying the volume label for the volume in
Explanation: The mount request has not been satisfied
the specified drive.
in the requested time.
System action: The volume is dismounted by the
System action: The server fails the mount request.
server.
User response: Retry the mount request and ensure
User response: Ensure the following:
that the volume is mounted within the time limit for
the manual library. For an automated library, retry the v Check the integrity of the data on the volume by
mount request and increase the mount wait time for issuing an AUDIT VOLUME command. If this error
the device class. occurs on a volume that is stored inside a VTL or
SCSI library, the library itself may need to be audited
by using the AUDIT LIBRARY command.
ANR8352I Requests outstanding:
v The DEVICE parameter associated with the drive is
Explanation: This message provides a list of currently identified correctly in the DEFINE PATH command,
outstanding mount requests. and the drive is currently powered on and ready.
System action: The server lists all outstanding mount After checking and correcting these potential problems,
requests or the one specified on the QUERY REQUEST retry the operation.
command.
User response: None. ANR8356E Incorrect volume mounted volume name
was mounted instead of volume expected
volume name in library library name.
ANR8353E Request number: I/O error reading label
of volume in drive drive name. Explanation: The incorrect volume has been mounted
in the designated library. This error can occur if the
Explanation: The server detects an error while reading library inventory has been altered due to manual
the volume label from the volume in the specified intervention or movement of volumes, or both.
drive.
System action: The volume is dismounted; the
System action: The volume is ejected, and the server expected volume may be marked unavailable if this
continues to wait for the requested volume to be error occurs during normal volume mount activity.
mounted.
User response: Use the AUDIT LIBRARY command to
User response: Ensure the following: force the library to reevaluate its inventory of volumes.
v The requested volume is properly inserted in the
designated drive.
v The volume has been labeled by using the
DSMLABEL utility program before you attempt to
use it with the server.

ANR8357I Error reading label of volume from ANR8361E Command: Device type not specified.
slot-element element address in drive drive
Explanation: The specified command requires that the
name of library library name.
DEVTYPE parameter be supplied.
Explanation: While processing a search-mode
CHECKIN LIBVOLUME command for the designated
library, the server finds a volume whose label cannot be User response: Reissue the command, and specify a
read. valid DEVTYPE parameter.
System action: The volume is dismounted and is not
checked into the library. ANR8362E Command: The parameter parameter is
invalid for device type device type.
User response: Remove the volume from the library
and ensure that it is properly labeled. After doing so, Explanation: The specified parameter is not valid for a
the volume can be checked into the library. device class with the given device type.
ANR8358E Audit operation is required for library
library name. User response: Reissue the command with a correct
parameter.
Explanation: The server encounters a problem
managing the given library, and determines that an
AUDIT LIBRARY operation should be performed. ANR8363E Command: The parameter parameter is
required for device type device type.
System action: The server may continue to access the
library, but some volumes may not be accessible until Explanation: The specified command requires that the
an AUDIT LIBRARY command is issued against the given parameter be supplied when the indicated device
library. type is used.
User response: Issue an AUDIT LIBRARY command System action: The command is not processed.
against the library. User response: Reissue the command, providing the
required parameter value.
ANR8359E Media fault detected on device type
volume volume name in drive drive name ANR8364E Command: Cannot reduce MOUNTLIMIT
of library library name. below number of volumes currently
Explanation: The server encounters a media fault mounted.
while accessing the given volume using the specified Explanation: The MOUNTLIMIT value cannot be
drive. reduced below the number of currently mounted
System action: The operation that is attempting to volumes.
access the volume will fail, and the volume will be System action: The command is not processed.
immediately dismounted from the drive.
User response: Wait until the server finishes using
User response: In some cases, the server will some of the mounted volumes, or force the server to
automatically mark the volume readonly. This will dismount idle volumes using the DISMOUNT
prevent the server from trying to write to the volume. VOLUME command, then retry this command.
Issue an AUDIT VOLUME command to determine if
any data has been lost due to the media failure.
ANR8365E Command: The parameter parameter
cannot be changed.
ANR8360I Volume volume name has been deleted
from MANUAL library library name. Explanation: The specified parameter cannot be
changed from the value that was provided with the
Explanation: The specified volume has been deleted associated DEFINE command.
by the server. It can be returned to a scratch pool by
the mount operator if desired. System action: The command is not processed.
System action: The volume is removed from the User response: If it is necessary to use a different
server's inventory. value for the given parameter, the associated object
must be deleted and then redefined using the new
User response: None. parameter value.

re-establish communications with another server. If the

ANR8366E Command: Invalid value for parameter
volume remains in the retry state for the amount of
parameter.
time specified by the device class retry period, the
Explanation: An invalid value has been provided for operation will fail and the volume will be automatically
the specified parameter. dismounted.
System action: The command is not processed. System action: None.
User response: Reissue the command, and specify a User response: None.
valid parameter value. If this is for the ELEMENT
parameter on DEFINE DRIVE with AUTODETECT, this
ANR8371I I/O is being bypassed for volume volume
message can be issued because the library doesn't
name.
support the ability to determine the element number
dynamically. In this case, supply the actual element Explanation: The indicated volume is mounted but
number instead of using AUTODETECT for the the server is bypassing actual I/O operations for the
ELEMENT parameter. If this is for the volume. The pool associated with the volume matches
SCALECAPACITY parameter on a 3592 device class, the NULLPOOLNAME option in the options file or
verify that this device class has the attribute NULLFILEDEVCLASS YES has been specified in the
WORM=NO as WORM and SCALECAPACITY are not options file.
compatible.
ANR8367E Command: Multiple parameter values are User response: None.

not allowed.
Explanation: The designated parameter is specified ANR8372I Request number: Remove device type
more than once in the command; this is not allowed. volume volume name from drive drive
name of library library name.
Explanation: A LABEL LIBVOLUME command has
User response: Reissue the command, but specify the completed. You can remove the specified volume from
given parameter only once. the designated drive and store it outside the library.
ANR8368E Request number: Incorrect side (side) of
volume volume name mounted in drive User response: Remove the volume from the drive
drive name. and store it in a safe place.
Explanation: The user inserted the wrong side of the

requested volume into the indicated drive. ANR8373I Request number: Fill the bulk entry/exit
port of library library name with all device
System action: The volume is ejected, and the server type volumes to be processed within time
continues to wait for the requested side of the volume limit minute(s); issue 'REPLY' along with
to be mounted. the request ID when ready.
User response: Insert the correct side of the requested Explanation: A CHECKIN LIBVOLUME or LABEL
volume into the designated drive. LIBVOL command with SEARCH=BULK is in progress.
Load all volumes to be processed into the multi-slot
entry/exit port of the given library within the time
ANR8369E Library library name is not defined.
limit specified in the message.
Explanation: The designated library is not defined,
but has been referenced in a mount request.
System action: The mount request is rejected.
User response: Insert the volumes into the library's
User response: Define the given library, or update the entry/exit port; and issue a REPLY command, along
LIBRARY parameter of the device class that references with the request ID, to tell the server that the volumes
it. have been inserted.
ANR8370I Device type volume volume name is ANR8374E Unable to unmount mountpoint
mounted mount mode, status: RETRY. mountpoint name.
Explanation: In response to a QUERY MOUNT Explanation: A removable file device class mountpoint
command, the server indicates that the given volume is had to be unmounted using the operating system
mounted for I/O operations. The volume is currently in unmount function. The server did not have permission
RETRY, meaning an attempt is being made to to unmount the directory specified.

System action: The server continues, but cannot use

ANR8379I Mount point in device class Device class
the mountpoint for removable file support until the
name is waiting for the volume mount to
directory is unmounted.
complete, status: WAITING FOR
User response: It may be necessary to run the server VOLUME.
as a root user to mounted directories to be unmounted.
Explanation: In response to a QUERY MOUNT
command, the server indicates that there is a mount
ANR8375E Device type volume volume name cannot point in the given device class waiting for the volume
be overwritten by BACKUPSET mount to complete.
operation.
contains data, so that the server cannot allow new
backup set data to be written to it.
mounted mount mode in drive drive name,
volume already contains some data that would be
status: RETRY DISMOUNT FAILURE.
overwritten by the requested backup set operation.
Explanation: Because of the failure of a previous
User response: If the specified volume does not
dismount, the server is retrying the dismount of the
contain any valuable data, delete it and retry the
specified volume from the specified drive. In response
backup set operation.
to a QUERY MOUNT command, the server indicates
that the volume is mounted in the drive.
ANR8376I Mount point reserved in device class
Device class name, status: RESERVED.
point reserved for future I/O operations in the given ANR8381E Device type volume volume name could
device class. not be mounted in drive drive name.
System action: None. Explanation: The server could not complete the
specified mount request due to an error. Examine
previous messages for additional information regarding
the specified volume and the operation.
mounted mount mode, status:
DISMOUNTING. User response: Examine previous messages for
additional information regarding the specified volume
and the operation.
currently being dismounted.
ANR8382W Library library name is now full.
Explanation: During a library check-in operation from
a multi-slot entry/exit station, the last storage location
was filled before checking the remainder of the
ANR8378I Device type volume volume name is entry/exit slots.
mounted mount mode, status: RETRY
System action: The operation stops, but is considered
DISMOUNT FAILURE.
successful if at least one volume is checked in.
User response: If more volumes remain to be checked
command, the server indicates that it is currently
in, issue a CHECKOUT LIBVOLUME command to
retrying the dismount of the given volume because of a
make room in the library. Retry the library operation.
failure during the previous dismount.
ANR8383E Device class device class name directory
User response: None. directory name is not a SnapLock
directory.
Explanation: When processing the named device class,
it was discovered that a directory was specified for the
device class that is not a NetApp SnapLock WORM
Volume. All directories used by a device class for a

storage pool with RECLAMATIONTYPE=SNAPLOCK needs to be processed, verify that the Entry/Exit door
must be Snaplock directories. is closed, the slot is accessible, and the device has not
logged any device errors before trying the command
System action: If you are trying to define a storage
again. Contact the hardware vendor if slots are
pool with RECLAMATIONTYPE=SNAPLOCK, the
incorrectly being reported as inaccessible.
command fails. If you are trying to update a device
class that is pointed to by a
RECLAMATIONTYPE=SNAPLOCK storage pool, the ANR8387I Request number: All entry/exit ports of
command fails. library library name are full or
inaccessible. Empty the entry/exit ports,
User response: If you are trying to define a storage
close the entry/exit port door, and make
pool with RECLAMATIONTYPE=SNAPLOCK, you
the ports accessible.
need to specify a device class which has all directories
which are NetApp SnapLock WORM Volumes. You Explanation: A CHECKOUT LIBVOLUME command
may select another device class which has all SnapLock cannot find an empty and available entry/exit port to
directories specified in it. Or you may use the UPDATE place the volume to be removed.
DEVCLASS command to remove non-SnapLock
System action: The server waits until the operator
directories from the device class DIR list. If you modify
performs the actions requested.
an existing device class, you need to ensure that no
data is stored in directories that are to be removed User response: Make at least one entry/exit port
from the device class. If this message is issued when empty and accessible. Check the entry/exit ports or the
you are trying to update a device class, ensure that all library. Make sure the entry/exit door is closed. If all
directories specified in the directory are SnapLock the entry/exit ports are full remove at least one volume
directories. from the entry/exit port. If any of entry/exit are empty
then the empty entry/exit ports are inaccessible. Check
the library's documentation on how to make the
ANR8384E Request number: Incorrect volume (volume
entry/exit port accessible. If the library is incorrectly
name) inserted into library library name.
reporting the status of the entry/exit port contact the
Explanation: The user has inserted the named volume library vendor.
into the indicated library, but it is not the one requested
by the server.
ANR8388E Device class device class name has no
System action: The volume is skipped, and the server directories specified.
continues to wait for the requested volume to be
Explanation: When processing the named device class,
inserted.
which is referenced by a storage pool of type
User response: Ensure that the requested volume is RECLAMATIONTYPE=SNAPLOCK, it was discovered
inserted properly into the designated location in the that there were no directories specified for it. One or
library. more directories must be specified for a device class
that is used by a storage pool with
RECLAMATIONTYPE=SNAPLOCK, and all directories
ANR8385E All entry/exit ports of library library
must be NetApp SnapLock WORM Volumes.
name are empty.
Explanation: The entry/exit ports of the library do not
contain a volume that can be processed. User response: A device class that is referenced by a
storage pool of type
RECLAMATIONTYPE=SNAPLOCK needs to specify
User response: Ensure that the volume is inserted one or more directories which are NetApp SnapLock
properly into the entry/exit port of the library and that WORM Volumes. Use the UPDATE DEVCLASS
the library indicates the volume is inserted and issue command to define appropriate directories to the
the command again. Contact the hardware vendor if device class and retry your request.
the volume is inserted correctly and this error occurs.
ANR8389E Device class device class name has storage
ANR8386W Slot element number of library library pools using it with inconsistent
name is inaccessible. RECLAMATIONTYPE parameters, or
invalid directories specified in it.
Explanation: The slot in the library could not be
physically accessed at this time. Explanation: When processing the named device class,
it was discovered that it was not configured properly. A
System action: The slot is skipped and processing device class can be referenced by storage pools of type
continues with the next slot. RECLAMATIONTYPE=THRESHOLD or
User response: If there is a volume in the slot that RECLAMATIONTYPE=SNAPLOCK. For storage pools
of type RECLAMATIONTYPE=SNAPLOCK, all

directories specified in the device class must be on

ANR8391E The external library manager file name
NetApp SnapLock WORM Volumes.
can not be found. The library library
System action: If the IBM Spectrum Protect server is name is not available.
starting, the server continues; however, attempts made
Explanation: The external library manager listed for
to read from or write to that storage pool will fail until
this library was not found. The path or the file name is
the storage pools referencing the device class and the
not correct.
device class are properly configured.
System action: The library management operation
User response: Check the activity log for ANR8502,
fails.
ANR8383E, and ANR8388E messages. If these messages
have been issued, follow the instructions in the User User response: Verify the path and the name of the
Response section of those messages to resolve the external library mentioned. If it is correct, verify that
issues. the file is present on the system and that file
permissions allow the server to invoke the file.
If the problem is not resolved, use the QUERY
DEVCLASS command with the FORMAT=DETAILED
option to obtain the specified directories for the device ANR8392E The external library manager file name
class. Verify that each directory is available to the IBM does not have executable permission.
Spectrum Protect server, e.g., on-line, in read-write The library library name is not available.
mode, configured properly, etc.
Explanation: The external library manager listed for
If the problem is not resolved, for a device class used this library was not found. The path or the file name is
by RECLAMATIONTYPE=SNAPLOCK storage pools, not correct.
check that each directory is a NetApp SnapLock
WORM Volume. If not, use the UPDATE DEVCLASS
fails.
command to update the device class directory structure
appropriately. User response: Verify the path and the name of the
external library mentioned. If it is correct, verify that
If the problem is not resolved, use the QUERY
the file is present on the system and that the file
STGPOOL command with the FORMAT=DETAILED
permissions allow the server to invoke the file.
option to determine which storage pools are pointing to
the device class. Verify that storage pools of either type
RECLAMATIONTYPE=THRESHOLD or ANR8393E Failed to communicate with the external
RECLAMATIONTYPE=SNAPLOCK are using the library library name through it's defined
device class. If storage pools of both types are using the external library manager path.
device class, modify the storage pool definitions such
that only one type of storage pool uses the device class. Explanation: The external library manager executable
If you wish to have storage pools of both reclamation file did not start or exited immediately.
types pointing to the same directory structure, you may System action: The library management operation
create two device classes with the same directory fails.
structure, and have storage pools of one reclamation
type use one device class while storage pools of the User response: Verify the path and the file name of
other reclamation type uses the other device class. this library's external library manager. If it is correct,
verify that the file is present on the system and that the
If you have made updates to the storage pools and the file permissions allow the server to invoke the file.
device classes and the problem is not resolved, you The path and file name can be found by using the
may need to restart the IBM Spectrum Protect server. QUERY PATH command.
ANR8390W Failure connecting to library client ANR8394E The device class,device class
library client to manage volume volume. name,directory parameter is too long.
Explanation: The library manager failed to contact the Explanation: The directory parameter for the define
designated library client for a management operation device class command is too long.
for the specified volume.
fails. User response: Reissue the command, specifying a
valid DIRECTORY parameter. The directory parameter
User response: Review the other messages in the must be between 0 and 1400 characters.
activity log relating to this library client and this
volume to determine which operations were affected by
this failure.

ANR8395E Command: The parameters specified are ANR8399E The IBM Spectrum Protect server
only valid for a device class defined receives a status as acsls statuse from
with a ZosMedia library. ACSLS server.
Explanation: The specified parameter is not valid for a Explanation: The ACSLS CSI media server does not
device class unless a ZosMedia library is specified in receive a response from IBM Spectrum Protect server.
the Library parameter of the device class.
System action: The operation will fail.
User response: This is a communication problem.
User response: Reissue the command with a correct Check configurations of the network adapter and its
parameter. driver and then perform the operation again.
ANR8396E Command: Library library name is not ANR8400I Library library name defined.
capable of discovering the drives that it
Explanation: The designated library has been
owns.
successfully defined.
Explanation: The PERFORM LIBACTION command
System action: The library is defined and recorded in
failed. Either the library lacks the SCSI capability to
the database.
determine the serial and element numbers of its own
drives, or SAN Discovery failed to translate the serial User response: None.
number to the drive's special file name.
System action: The command is not processed. ANR8401E Command: Invalid library name library
name.
User response: Correct any issues with SAN
Discovery and reissue the PERFORM LIBACTION Explanation: The designated library name is invalid;
command. If the command cannot be processed, drive either it contains too many characters, or some of the
and drive path definitions for this library will need to characters are invalid.
be defined manually, one drive at a time.
ANR8397E Library name (library name) is too long to User response: Reissue the command using a valid
use as the default PREFIX value. An library name.
explicit PREFIX value is required.
Explanation: The PREFIX value must be specified ANR8402E Command: Library library name is already
with 25 characters or less. If a PREFIX value is not defined.
specified, the library name is used by default. However, Explanation: The designated library cannot be defined
if the library name is longer than 25 characters, it because it already exists.
cannot be used for the PREFIX parameter. Instead, the
PREFIX value must be specified explicitly. System action: The command is not processed.
System action: The command is not processed. User response: If you want to define an additional
library, reissue the command with a different library
User response: Reissue the PERFORM LIBACTION name.
command and specify the PREFIX parameter with a
value that contains 25 characters or less.
ANR8403E Command: Operation not allowed for
library type libraries.
ANR8398E The REMOVE=UNTILEEFULL option is
not supported with the MOVE Explanation: The requested operation is not allowed
DRMEDIA command for librarylibrary for libraries of the given type.
name with library type library type. System action: The command is not processed.
Explanation: The MOVE DRMEDIA command does User response: None.
not support the option as REMOVE=UNTILEEFULL for
this library type.
ANR8404I Drive Drive name defined in library
System action: The operation will fail. library name.
User response: This option is only supported with the Explanation: The designated drive has been
library type SCSI. Remove the successfully defined as a member of the specified
REMOVE=UNTILEEFULL option and perform the library.
operation again.
System action: The drive is defined and recorded in
the database.


ANR8410I Library library name deleted.
Explanation: The designated library has been deleted
ANR8405E Command: Invalid drive name drive name.
successfully.
Explanation: The designated drive name is invalid;
System action: The library is deleted.
either it contains too many characters, or some of the
characters are invalid. User response: None.
ANR8411E Command: One or more drives are still
User response: Reissue the command using a valid
defined in library library name.
drive name.
Explanation: The command failed because there are
drives defined to the designated library. For the
ANR8406E Command: Drive drive name is already
DELETE LIBRARY and PERFORM LIBACTION
(ACTION=DEFINE) commands, the specified library
Explanation: The designated drive cannot be defined cannot have drives currently defined within the library.
because it has already been defined for the specified
library.
User response: Delete all drives from the library, and
User response: If you want to define an additional
drive, reissue the command with a different drive
ANR8412I Drive drive name deleted from library
name.
library name.
Explanation: The designated drive has been deleted
ANR8407E Command: The MODEL parameter is
successfully from the specified library.
required for this command.
System action: The drive is deleted.
Explanation: The MODEL parameter has not been
provided; it is required. User response: None.
ANR8413E Command: Drive drive name is currently
User response: Reissue the command using the
in use.
MODEL parameter.
Explanation: The designated drive cannot be deleted
or updated because it is currently in use.
ANR8408E Command: The DEVICE parameter is
required for this command. System action: The command is not processed.
Explanation: The DEVICE parameter has not been User response: Wait until the drive is no longer in
provided; it is required. use, and reissue the command.
ANR8414E Command: Drive drive name is not
User response: Reissue the command using the
DEVICE parameter.
Explanation: The designated drive has not been
defined in the given library.
ANR8409E Command: Library library name is not
defined. System action: The command is not processed.
Explanation: The designated library has not been User response: Reissue the command using a different
defined. drive name. If appropriate, define the drive before
retrying the command.
User response: Reissue the command using a different
ANR8415E Command: The parameter parameter is
library name, or define the library before retrying the
command.
Explanation: The specified parameter must be
provided when processing the given command.
User response: Reissue the command, providing the
required parameter value.

ANR8416E Command: The parameter parameter is ANR8420E Command: An I/O error occurred while
invalid for library type library type. accessing drive drive name.
Explanation: The specified parameter is not valid for Explanation: An I/O error occurs while accessing the
libraries of the given type. The scratch category must specified drive.
be at lest 2 less than the private category for 349x
libraries.
associated with the drive is identified correctly in the
User response: Reissue the command, using only the DEFINE PATH command, and that the drive is
proper parameters. If using the scratch category make currently powered on and ready. After checking and
sure it is at least 2 less than the private category. correcting these potential problems, retry the command.
ANR8417E Command: The parameter parameter is ANR8421E Command: Unable to start a process for
invalid for drives in library type libraries. this command.
Explanation: The specified parameter is not allowed Explanation: The server cannot start a background
when defining or updating drives in a library of the process to carry out the designated command.
given type.
User response: Check for and correct memory
User response: Reissue the command, using only the shortages or other server resource constraints, and
proper parameters. reissue the command.
ANR8418E Command: An I/O error occurred while ANR8422I Command: Operation for library library
accessing library library name. name started as process process ID.
Explanation: An I/O error occurs while accessing the Explanation: A volume check-in process has been
designated library. started to handle the insertion of a volume into the
given library. The process is assigned the ID specified
in the message.
associated with the library is identified correctly in the
to perform the operation in response to the CHECKIN
DEFINE PATH command, and that the library is
LIBVOLUME command entered by an administrator.
access door, make sure it is closed. After checking and User response: To obtain status on the process, issue
correcting these potential problems, retry the operation. the QUERY PROCESS command. The process may be
canceled with the CANCEL PROCESS command.
ANR8419E Command: The drive or element conflicts
with an existing drive in library library ANR8423I CHECKIN LIBVOLUME process for
name. library library name has been canceled.
Explanation: Either there are no more physical drives Explanation: A background server process that has
in the library, or the specified ELEMENT parameter been working to check in one or more volumes for the
conflicts with an existing defined drive in the given given library is canceled by the CANCEL PROCESS
library. If this error occurred during a restore db command.
operation, the physical tape device environment or
configuration has changed. The original tape drives
were removed or are offline.
User response: Specify a valid ELEMENT parameter
ANR8424I Checking in volume volume name in
that is not used by any other drive in the library. If this
error occurred during a restore db operation, check the
physical device configuration. Ensure the definition of Explanation: In response to a QUERY PROCESS
devices in the devconf.dat file matches the physical command, this message displays the status for a
device configuration. CHECKIN LIBVOLUME process on the server. The
given volume is being checked in to the designated
library.

System action: The background process operation

ANR8429E Command: No drives are currently
continues.
User response: None. The process may be canceled by
Explanation: The command cannot be issued until at
an authorized administrator using the CANCEL
least one drive has been defined in the given library.
PROCESS command.
ANR8425I Checking in volumes in search mode in User response: Define a drive in the library, using the
library library name. DEFINE DRIVE command, as well as a path to the
drive, using the DEFINE PATH command. Then retry
Explanation: In response to a QUERY PROCESS
the failed command.
command, this message displays the status for a
CHECKIN LIBVOLUME process on the server. Volumes
are being checked into the given library automatically ANR8430I Volume volume name has been checked
using a search for previously-unknown volumes. into library library name.
System action: The background process operation Explanation: A search-mode CHECKIN LIBVOLUME
continues. process has found the given volume and automatically
checked it into the library.
an authorized administrator using the CANCEL System action: The volume is added to the given
PROCESS command. library's inventory.
ANR8426E CHECKIN LIBVOLUME for volume
volume name in library library name failed.
ANR8431I CHECKIN LIBVOLUME process
Explanation: The background process for a CHECKIN completed for library library name; volume
LIBVOLUME command has failed. count volume(s) found.
System action: The background process ends, but the Explanation: A search-mode CHECKIN LIBVOLUME
volume has not been checked into the library. process is completed. The specified number of volumes
have been successfully added to the library's inventory.
User response: Make sure the library and drive
devices associated with this command are powered on System action: The volumes are made available for
and ready, and then reissue the command. use by the server.
ANR8427I CHECKIN LIBVOLUME for volume
volume name in library library name
ANR8432E Command: Volume volume name is already
present in library library name.
Explanation: The specified volume was successfully
Explanation: The specified volume cannot be checked
checked in to the library during processing of a
into the given library because it is already present.
CHECKIN LIBVOLUME or LABEL LIBVOLUME
command. System action: The command is not processed.
System action: The volume is made available for User response: Provide the name of a volume that is
mounting in the given library. not already present in the given library. Use the
QUERY LIBVOLUME command to obtain a full list of
volumes that have already been checked into the
library.
ANR8428E Command: The STATUS parameter is
ANR8433E Command: Volume volume name does not
Explanation: The STATUS parameter must be exist in library library name.
provided with the given command.
Explanation: The volume cannot be accessed because
System action: The command is not processed. it does not exist in the library.
User response: Reissue the command, and provide a System action: The command is not processed.
valid STATUS parameter value.
User response: Specify the name of a volume that is
in the library. Use the QUERY LIBVOLUME command
to obtain a full list of volumes that reside in the library.
If you are using the AUDIT LIBVOLUME command,

the volume might be in use by another operation, or

ANR8438I CHECKOUT LIBVOLUME for volume
does not exist in the library.
volume name in library library name
ANR8434I Command: Operation for volume volume
Explanation: The background process for a
name in library library name started as
CHECKOUT LIBVOLUME command has completed
process process ID.
successfully.
Explanation: A volume check-out process has been
started to handle the removal of a volume from the
library's inventory (if its status is something other than
given library. The process is assigned the ID specified
DATA) or marked not present (if its status is DATA).
in the message.
to perform the operation in response to the
CHECKOUT LIBVOLUME command entered by an ANR8439I library type library library name is ready
administrator. for operations.
User response: To obtain status on the process, issue Explanation: The initialization process for the given
the QUERY PROCESS command. The process may be library has completed successfully, and the library is
canceled with the CANCEL PROCESS command. ready for use.
System action: The library is made ready for use.
ANR8435I CHECKOUT LIBVOLUME for volume
volume name in library library name has
been canceled.
ANR8440E Initialization failed for library type
library library name; will retry in delay
been working to check out the volume from the given
time minute(s).
library is canceled by the CANCEL PROCESS
command. Explanation: The initialization process for the given
library has failed. It will be retried automatically after
the specified amount of time has elapsed.
System action: The initialization will be retried later.
User response: Ensure that the library device is
powered on and ready. If the library has an access
ANR8436I Checking out volume volume name from
door, make sure it is in the closed position.
CHECKOUT LIBVOLUME process on the server.
Explanation: The initialization process for the given
library has failed, and will not be retried until the next
continues.
time the server needs to access the library.
System action: The library is made temporarily
unavailable.
PROCESS command.
User response: Make sure the library is powered on
and attached.
ANR8437E CHECKOUT LIBVOLUME for volume
volume name in library library name failed.
ANR8442E Command: Volume volume name in library
Explanation: The background process for a
library name is currently in use.
CHECKOUT LIBVOLUME command has failed.
System action: The background process ends, but the
because the specified volume is already being used for
volume has not been checked out of the library.
another operation.
devices associated with this command are powered on
and ready, then retry the command. User response: Wait until the conflicting volume
activity has completed, and then reissue the command.
If the volume is currently mounted, but idle, you can
dismount it with the DISMOUNT VOLUME command

and then retry this operation. an application other than the server may have the
driver opened. This message may also be issued if a
CHECKIN or LABEL command is issued and no drive
is available to service the operation. This can be
library name cannot be assigned a status
because all the drives are mounted by other processes
of SCRATCH.
or sessions, or the device type was incorrectly specified.
Explanation: The volume cannot be assigned to the
System action: The attempted operation is terminated.
given library's scratch pool because there is a storage
pool volume defined or a volume in the volume history User response: Use the QUERY DRIVE command to
file with this volume name. Such a volume may still check the online status of the drives. Drives that are
contain valid data. Assigning the volume to the marked "Unavailable since hh:mm yy/mm/dd" are
library's scratch pool might result in a destructive drives taken offline by the server at the time specified
overwrite of the volume's data. because of hardware failures or the inability to open
the drive. If the attempted operation is a CHECKIN or
LABEL command, use the QUERY MOUNT command
User response: Reissue the command, specifying that to determine if all the drives in the library are mounted
the volume be assigned a status of PRIVATE. and wait until one of these is available. If there are
mounted volumes with an IDLE status, use the
DISMOUNT VOLUME command to free its drive, and
ANR8444E Command: Library library name is retry the original operation.
currently unavailable.
Explanation: The requested operation cannot be ANR8448E Scratch volume volume name from library
completed because the specified library is unavailable library name rejected - volume name is
for I/O operations. The library may still be carrying already in use.
out its initialization operations.
Explanation: The designated volume has been used to
System action: The command is not processed. satisfy a scratch mount, but the volume is already
User response: Wait until the library initialization defined in a storage pool, or has been used to store
completes or the library becomes ready. server export, database dump, or database backup
information as recorded in the server volume history
file.
ANR8445I Volume volume name in library library
name updated. System action: The volume is rejected.
Explanation: The specified library volume has been User response: Use a volume that is not in use, or
updated successfully. check out and relabel the rejected volume, assigning it
a new name in the process, or delete the existing
System action: The library volume inventory is volume that caused the name conflict.
updated.
User response: None. ANR8449E Scratch volume volume name rejected -
volume name is already in use.
ANR8446W Manual intervention required for library Explanation: The designated volume has been used to
library name. satisfy a scratch mount, but the volume is already
Explanation: The specified library requires manual defined in a storage pool, or has been used to store
intervention. server export, database dump, or database backup
information as recorded in the server volume history
System action: Current library activity will be delayed file.
until the required intervention occurs.
System action: The volume is rejected.
User response: If the library has an access door, make
sure it is in the closed position. If it has a cartridge User response: Use a volume that is not in use, or
carousel, make sure the carousel is installed. The server rename the rejected volume or delete the existing
automatically detects when the appropriate action has volume that caused the name conflict.
been taken; it will then continue its operations.
ANR8450E Command: Library library name is
ANR8447E No drives are currently available in currently in use.
library library name. Explanation: The designated library cannot be deleted
Explanation: The attempted operation cannot be or updated because it is currently in use for an I/O
completed on the specified library because there are no operation.
available drives. A drive may be unavailable because System action: The command is not processed.

User response: Wait until the library is no longer in User response: If the volume is needed, it should be
use, and then retry the command. located and checked into the library using the
CHECKIN LIBVOLUME command.
ANR8451I 349X library library name is ready for
operations. ANR8456E Multiple volumes named volume name
were found during audit of library
library name.
library has completed successfully, and the library is
ready for use. Explanation: While processing an AUDIT LIBRARY
command for the given library, multiple physical
System action: The library is made ready for use.
volumes are found to have the same name.
System action: The first instance of the volume is
retained in the server inventory; all other instances are
ANR8452E Initialization failed for 349X library ignored.
library name; will retry in delay time
User response: Remove all of the redundant instances
minute(s).
of the volume from the library. If the volume which the
Explanation: The initialization process for the given server retained is found to be the incorrect one, it can
library has failed. It is retried automatically after the be checked out with the CHECKOUT LIBVOLUME
specified amount of time has elapsed. command; then the correct instance can be checked into
the library with a CHECKIN LIBVOLUME command.
User response: Ensure that the library device is ANR8457I Command: Operation for library library
powered on and ready. name started as process process ID.
Explanation: A library audit process has been started
ANR8453E Initialization failed for 349X library for the given library. The process is assigned the ID
library name. specified in the message.
Explanation: The initialization process for the given System action: The server starts a background process
library has failed and will not be retried until the next to perform the operation in response to the AUDIT
time the server needs to access the library. LIBRARY command entered by an administrator.
System action: The library is made temporarily User response: To obtain status on the process, issue
unavailable. the QUERY PROCESS command. The process may be
User response: None. canceled with the CANCEL PROCESS command.
ANR8454E Mismatch detected between external ANR8458I AUDIT LIBRARY process for library
label (volume name from external label) and library name has been canceled.
media label (volume name from media label) Explanation: A background server process that has
in 349X library library name. been working to audit the given library is canceled by
Explanation: The external label of a volume was the CANCEL PROCESS command.
found to differ from its media label in the designated System action: The server process is ended and server
library. operation continues.
System action: The volume will not be accessed. User response: None.
and ensure that it is properly labeled. ANR8459I Auditing volume inventory for library
library name.
ANR8455E Volume volume name could not be Explanation: In response to a QUERY PROCESS
located during audit of library library command, this message displays the status for an
name. Volume has been removed from AUDIT LIBRARY process on the server.
the library inventory.
Explanation: While processing an AUDIT LIBRARY
command for the given library, the server cannot find User response: None. The process may be canceled by
the given volume in the library. an authorized administrator using the CANCEL
PROCESS command.
System action: The volume is removed from the
library inventory.

ANR8460E AUDIT LIBRARY process for library ANR8464E command: Invalid update request for
library name failed. library library name.
Explanation: A background process that was initiated Explanation: An invalid update request has been
by the AUDIT LIBRARY command failed. made for the given library. This can occur if a new
device name is given and the characteristics of the
System action: System operations continue, but the
device do not match the characteristics of the original
background process ends.
device.
following steps: 1. Review the activity log to determine
command.
whether other error or warning messages were issued
during the audit process. Resolve any errors. 2. Ensure User response: If a different type of library device has
that the tape library and tape drives are powered on been installed, the old library definition must be
and ready for use. 3. Ensure that the paths that are deleted with a DELETE LIBRARY command, and a
associated with the tape drives are online. 4. If the file new library must be defined. The UPDATE LIBRARY
names for tape devices changed, ensure that the command cannot be used in this case.
SANDISCOVERY server option is set to ON. 5. Reissue
the AUDIT LIBRARY command.
ANR8465I Library library name updated.
Explanation: An UPDATE LIBRARY request has been
ANR8461I AUDIT LIBRARY process for library
successfully processed for the given library.
library name completed successfully.
System action: The server updates its information
Explanation: The background process for an AUDIT
about the library.
LIBRARY command has completed successfully.
System action: The library inventory is updated to
match the contents of the library as found during the
audit operation. ANR8466E command: Invalid update request for
drive drive name in library library name.
Explanation: An invalid update request has been
made for the given drive. This can occur if a new
ANR8462I End-of-side reached for device type
device name is given and the characteristics of the
volume volume name.
device do not match the characteristics of the original
Explanation: The server has detected an end-of-side device.
condition for the given two sided volume.
System action: The server will access the second side command.
of the volume.
User response: If a different type of drive has been
User response: None. installed, the old drive definition must be deleted with
a DELETE DRIVE operation, and a new drive must be
defined. The UPDATE DRIVE command cannot be
ANR8463E Device type volume volume name is write
used in this case.
protected.
Explanation: The server has detected a write-protect
ANR8467I Drive drive name in library library name
condition for the given volume.
updated.
System action: The server will dismount the volume
Explanation: An UPDATE DRIVE request has been
and continue processing with another volume.
successfully processed for the given drive.
User response: Adjust the write-protect switch on the
System action: The server updates its information
volume so that writing is allowed. If the write-protect
about the drive.
switch on the volume allows writing, verify that the
device special file for the drive has proper read and User response: None.
write permissions, at the operating system layer, for the
user who is starting the dsmserv process. If the volume
ANR8468I device type volume volume name
is an optical volume and the write-protect switch is
dismounted from drive drive name in
already set to allow writing, use the MOVE DATA
command to move the data off of the volume.
Rewritable volumes may be reformatted and reused Explanation: The specified volume has been
after the data is moved to another volume. dismounted from the given drive.

User response: If the type of the given library is issuing the UPDATE PATH command with the
MANUAL, the operator may elect to remove the ONLINE=YES option.
volume (which has already been ejected) from the drive
and store it in an appropriate location. For automated
ANR8472I Error reading label of volume in drive
libraries, this message is purely informational.
drive name of library library name.
Explanation: While processing a search-mode
ANR8469E Dismount of device type volume volume
CHECKIN LIBVOLUME command for the designated
name from drive drive name in library
library, the server finds a volume whose label cannot be
library name failed.
read.
Explanation: An attempt to dismount the designated
System action: The volume is dismounted and is not
volume failed due to an I/O error.
checked into the library.
User response: If the type of the given library is and ensure that it is properly labeled. After doing so,
MANUAL, the volume can be manually ejected and the volume can be checked into the library.
removed from the drive. For automated libraries,
manual intervention may be required to correct the
ANR8473I Volume volume name was found in
problem.
storage element slot element address in
library library name. It may still be in the
ANR8470W Initialization failure on drive drive name drive.
in library library name.
Explanation: The specified volume was found in the
Explanation: The specified drive could not be storage slot of a cleaner cartridge. After it was loaded
initialized at this time. into a drive for cleaning, IBM Spectrum Protect
determined that it is not a cleaner cartridge. IBM
System action: The initialization of the specified
Spectrum Protect encountered an error trying to move
library continues.
the cartridge back to the storage slot of the cleaner
User response: An internal validation of the specified cartridge. If the volume is a storage pool volume, IBM
drive and its path failed. Ensure that the drive's path Spectrum Protect already attempted to make it
definition to the local server is correct. Examine all unavailable. Review the output of the QUERY
previous messages for information regarding the VOLUME F=D command for storage pool volumes.
specified drive. If necessary, delete and redefine the Review the output of the QUERY VOLHISTORY
path from the local server to the specified drive. After command for non-storage pool volumes.
redefining the path or correcting any issues that were
reported by related error messages, the drive's
initialization is retried on the next attempt to mount the User response: Verify all other cleaner cartridges are
specified drive. in the correct storage slots. Issue the QUERY
LIBVOLUME command to obtain the storage slots of
all the cartridges currently checked into IBM Spectrum
ANR8471E Server no longer polling drive drive name
Protect. Remove the cartridge in the storage slot
in library library name - path path will be
identified in the ANR8911W message. Remove the
marked off-line.
specified volume from the drive. Issue an AUDIT
Explanation: The server is unable to use the LIBRARY command against the library.
mentioned drive via the specified path. This may be for
the following reasons:
ANR8474E Command: One or more paths are still
v The drive cannot be opened defined to library library name.
v In the case of a 3494 or a library that can be
Explanation: The designated library cannot be deleted
partitioned, the drive may be unavailable to the
because there are still paths defined to it.
library manager, may be in use by another
application, or may be loaded with a cartridge not System action: The command is not processed.
labeled for server use.
User response: Delete all paths to this library, and
System action: The path to the drive is offline and is reissue the command.
not used for tape operations.
User response: Determine the reason the path to the ANR8475I Dismount of volume volume name failed.
drive is inaccessible, such as hardware errors reported It may still be in the drive.
in the system logs. Render any needed corrections to
Explanation: The specified volume could not be
the hardware. Then the path may be made online by
dismounted. IBM Spectrum Protect encountered an

error trying to dismount the volume. If the volume is a in the library at least one drive is defined that can read
storage pool volume, IBM Spectrum Protect already the media, and that the drive is online and working
attempted to make it unavailable. Review the output of properly. Check the activity log for I/O errors related
the QUERY VOLUME F=D command for storage pool to hardware failure and repair.
volumes. Review the output of the QUERY
VOLHISTORY command for non-storage pool volumes.
ANR8480E The drive Drive Name was not found for
System action: None. library Library Name.
User response: Review message ANR8469E in the Explanation: The missing drive needs to be defined to
activity log. Check if the volume is still loaded in the successfully run the current operation.
drive. If the volume is not in the drive, determine
where the volume is located in the library.
User response: Make sure that the drive is defined. If
macros are being used, the COMMIT command needs
ANR8476E Operation is not supported for the
to be issued after the DEFINE DRIVE. Otherwise, this
libtype of library library name.
could indicate a server internal error.
Explanation: The operation failed because the libtype
of the library is not supported for the operation.
ANR8481I The library library name already has an
System action: The operation fails. AUDIT LIBRARY operation pending
mount activity.
User response: Use a different libtype such as
MANUAL to perform the operation. Explanation: Libraries of type SHARED can only have
one AUDIT LIBRARY operation waiting on mount
activity. All subsequent AUDIT LIBRARY operations
ANR8477E Device type device type is incorrect for
will be canceled.
drive drive name.
Explanation: The device type of the specified drive on
the library client is not compatible with the device type
for the same drive on the library manager. User response: None.
ANR8482E The checkout volume volume name failed
User response: Delete the drive definition on the
because the entry/exit port of library
library client, and re-define the drive specifying the
library name is full. Please remove the
correct device. If this does not correct the problem,
volume(s) from the entry/exit port and
contact your service representative for assistance.
re-issue the command.
Explanation: The indicated operation has failed
ANR8478W Invalid home slot address in inventory
because the entry/exit port of the specified library is
for library library name; volume = volume
full.
name;slot = slot number.
Explanation: The specified volume's home slot in the
library inventory does not match the database User response: Remove the volume(s) from the
inventory. entry/exit port and re-issue the command to process
any remaining eligible volumes.
User response: Run 'audit library' against the
ANR8483W A device class can not be found for the
specified library.
Explanation: A library client audits a SHARED type
ANR8479W Unable to audit slot-element slot-element
Library, but there is no device class defined for that
of library library name.
library.
Explanation: The library audit process was unable to
System action: The AUDIT LIBRARY command fails.
audit storage slot with the specified element address.
This is probably due to no drive device being available User response: Define or update a device class for the
into which to load the cartridge. It can also be due to library using the DEFINE DEVCLASS or UPDATE
library or drive I/O errors occurring during the audit DEVCLASS command.
process.
System action: The AUDIT LIBRARY command fails.
User response: Verify that for every type of cartridge

ANR8484E No drives are available to be mounted ANR8487I Mount point in device class Device class
in MODE mode with format FORMAT in name is waiting for the volume mount to
library LIBRARY NAME. complete -- owning server: owner name,
status: WAITING FOR VOLUME
Explanation: The attempted operation cannot be
(session: session ID, process: process
completed on the specified library. Either there are no
number).
available drives with the specified format, or the
volume has the wrong access mode. A drive can be Explanation: In response to a QUERY MOUNT
unavailable because another application opened the command, the server indicates that there is a mount
drive. This message can also be issued if a CHECKIN point in the given device class waiting for the volume
or LABEL command is issued and no drive is available mount to complete. The session and process values are
to service the operation. This can occur when all drives relative to the server that owns this mount point.
are mounted by other processes or sessions, or the
device type was incorrectly specified.
System action: The attempted operation ends.
User response: Use the QUERY DRIVE command to
check the online status of the drives. Drives that are
mounted mount mode in drive drive name
marked "Unavailable since hh:mm yy/mm/dd" are
-- owning server: owner name, status: IN
drives taken offline by the server at the time specified
USE (session: session ID, process: process
because of hardware failures or the inability to open
number).
the drive. Use the QUERY MOUNT command to query
mounted drives and their mount mode. If there are Explanation: In response to a QUERY MOUNT
mounted volumes with an IDLE status, use the command, the server indicates that the given volume is
DISMOUNT VOLUME command to free the drive, and mounted in the specified drive. The volume is currently
retry the original operation. in use, meaning that read or write operations, or both,
are being performed. The session and process values
are relative to the server that owns this mount point.
ANR8485E Unable to open a SCSI device drive
name, error code=error value set by server. System action: None.
Explanation: The indicated SCSI device cannot be User response: None.
opened by the server. The error code is set by IBM
Spectrum Protect. It indicates that this device does not
respond the open system function call. This can be ANR8489I Device type volume volume name is
caused by an inexistent device, a device with powered mounted mount mode in drive drive name
off, or a device with firmware/hardware problems. -- owning server: owner name, status:
IDLE (session: session ID, process: process
System action: The transaction needing the drive fails. number).
User response: Make sure the device is online and Explanation: In response to a QUERY MOUNT
connected to the host system. If the device is not command, the server indicates that the given volume is
removed or is powered off, do a power cycle to mounted in the specified drive. The volume is currently
reinitialize this device and make sure this device is in a idle, meaning no active operations are being performed.
normal state. If this device is still not in a normal state, If the volume remains in the idle state for the amount
call device's vendor support to fix the problem. of time specified by the device class mount retention
period, it will be automatically dismounted. The
session and process values are relative to the server
ANR8486I Mount point in device class Device class
that owns this mount point.
name is reserved -- owning server: owner
name, status: RESERVED (session: session System action: None.
ID, process: process number).
point reserved for future I/O operations in the given ANR8490I Device type volume volume name is
device class. The session and process values are relative mounted mount mode in drive drive name
to the server that owns this mount point. -- owning server: owner name, status:
DISMOUNTING (session: session ID,
System action: None. process: process number).
User response: None. Explanation: In response to a QUERY MOUNT
mounted in the specified drive. The volume is currently
being dismounted by the server. The session and

process values are relative to the server that owns this User response: None.
mount point.
System action: None. ANR8495E Device type volume volume name cannot
be written by BACKUP DB operation.
BACKUP DB data to be written to it. Or there is no
space available on the destination filespace to write this
-- owning server: owner name, status:
backup to.
RETRY DISMOUNT FAILURE (session:
session ID, process: process number). System action: The server detects that the given
overwritten by the requested BACKUP DB command,
command, the server indicates that it is currently
or that there is not enough space available.
retrying the dismount of the given volume because of a
failure during the previous dismount from the specified User response: If the specified volume does not
drive. The session and process values are relative to the contain any valuable data, delete it and retry the
server that owns this mount point. BACKUP DB command.
ANR8496E Device class device class not defined in
device configuration information file.
Explanation: The command that has been issued
requires that the specified device class be defined in the
device configuration information file. This definition
-- owning server: owner name, status:
was not found or the statements in the file are in the
RETRY (session: session ID, process:
wrong order.
process number).
command, the server indicates that the given volume is User response: Reissue the command, and specify a
mounted for I/O operations. The volume is currently in valid device class. Refresh your device configuration
RETRY, meaning an attempt is being made to information file by issuing the BACKUP DEVCONFIG
re-establish communications with another server. If the command.
volume remains in the retry state for the amount of
time specified by the device class retry period, the
ANR8497E Library library not defined in device
operation will fail and the volume will be automatically
configuration information file.
dismounted. The session and process values are relative
to the server that owns this mount point. Explanation: The specified command requires that the
specified library be defined in the device configuration
information file. This definition was not found or the
User response: None. statements in the file are in the wrong order.
ANR8493I device type volume volume name mounted
User response: Refresh your device configuration
in drive drive name in library library
information file by issuing the BACKUP DEVCONFIG
name.
command. Make sure a library is defined for the device
Explanation: The specified volume has been mounted class. Reissue the command.
in the specified drive.
System action: None. ANR8498E Drive not defined for library library in
device configuration information file.
User response: For automated libraries, this message
is purely informational. Explanation: The specified command requires that the
specified drive be defined in the device configuration
information file for the specified library. This definition
ANR8494E Command: An option specified is not
was not found or the statements in the file are in the
valid for library type libraries.
wrong order.
Explanation: A requested option is not valid for
libraries of the given type for the specified command.
User response: Refresh your device configuration

command. Make sure a drive is defined for the library DIR=K:\FILECLASS\DIR1,L:\FILECLASS\DIR2 and a
associated with the device class. Reissue the command. storage agent has the following PATH definition:
DEFINE PATH STA FILE1 SRCTYPE=SERVER
DESTTYPE=DRIVE LIBRARY=FILE DEVICE=FILE
ANR8499I Command accepted.
DIR=X:\DIR1,X:\DIR2 then system STA must have
Explanation: The command is accepted and processed drive X set to access directory L:\FILECLASS on the
by the server. server so that directories DIR1 and DIR2 correspond to
the correct destinations on the storage agent and that
System action: The server processes the command. the number of directories match between the PATH and
User response: None. the DEVCLASS definitions.
ANR8500E No valid path is defined for library ANR8502E Errno errno received checking WORM
library name or any of its drives in device directory directory name on Filer.
configuration information file. Explanation: The server attempted to access the
Explanation: The specified command requires that a named directory on the NetApp SnapLock Filer, but the
path be defined in the device configuration information attempt failed with the indicated error code.
file for the specified library and its drive. This valid System action: If you were trying to define a storage
definition was not found, or the statements in the file pool or update a device class associated with a storage
are in the wrong order. pool, the command fails. If this error is encountered
System action: The command is not processed. during server initialization, server initialization
continues, but operations involving this storage pool
User response: Refresh your device configuration will not be allowed until the issue is resolved.
command. Make sure a path is defined for the library User response: This may be caused by an error in the
and its drive associated with the device class. Verify the NetApp Filer or with the communications between
correct source is used in these path definitions. If the your server and the NetApp Filer. Verify that the
default server name is not used as the source, a SET network is operational, that the SnapLock Filer is
SERVERNAME command is required in the device accessible from your server, and consult NetApp
configruation information file. Reissue the command. SnapLock Filer documentation to resolve the issue;
then, retry the command.
ANR8501E System return code return code received

opening volume server volume name with ANR8503E A failure occurred in writing to volume
file name file name server volume name.
Explanation: The server or storage agent attempted to Explanation: The server or storage agent was writing
access the file name indicated but failed to open the to the indicated volume name when a failure occurred.
volume. The indicated system return code was System action: The server or storage agent stops
received. The actual volume name corresponds to the writing to the specified volume.
file name that the server uses. The server volume name
and the file name may be the same when the server User response: The server or storage agent can
experiences a failure in opening the file. recover from some failures by requesting access to
different volumes. If there is a directory definition
System action: The volume is not opened. problem, this message may be displayed multiple times
User response: The server or storage agent can during retries with different volumes. The directory
recover from some failures by requesting access to names associated with the device class definition in the
different volumes. If there is a directory definition server should be checked for correctness in the number
problem, this message may be displayed multiple times and names of directory entries.
during retries with different volumes. The directory The permissions associated with newly created files
names associated with the device class definition in the should be checked to ensure the server and storage
server should be checked for correctness in the number agent can write to newly created files. Depending on
and names of directory entries. PATH definitions for the system, a mask value may need to be adjusted. The
each of the FILE drives should be checked that the system error or event log should be checked for
number of directories in the PATH definition match the indications of hardware or software errors from file
number in the server's device class definition and that systems.
directories exist and are accessible to servers and
storage agents accessing server directories via their For a remotely mounted file system, ensure that the
own path names. For example, if the server has the remote file system is mounted and useable to the
following definition: storage agent. The file system should be checked to
ensure that sufficient space is available. While the
DEFINE DEVCLASS FILE DEVTYPE=FILE server checks space, multiple device classes or servers

using the same file system can cause the server's space For storage agents, PATH definitions for each of the
checking to underestimate available space. FILE drives should be checked to ensure that the
number of directories in the PATH definition matches
For storage agents, PATH definitions for each of the
the number in the server's device class definition and
FILE drives should be checked to ensure that the
that directories exist and are accessible to servers and
number of directories in the PATH definition matches
storage agents accessing server directories via their
the number in the server's device class definition and
own path names. For example, if the server has the
that directories exist and are accessible to servers and
following definition:
storage agents accessing server directories via their
own path names. For example, if the server has the DEFINE DEVCLASS FILE DEVTYPE=FILE
following definition: DIR=K:\FILECLASS\DIR1,L:\FILECLASS\DIR2 and a
storage agent has the following PATH definition:
DEFINE DEVCLASS FILE DEVTYPE=FILE
DIR=K:\FILECLASS\DIR1,L:\FILECLASS\DIR2 and a
storage agent has the following PATH definition:
drive X set to access directory L:\FILECLASS on the
server so that directories DIR1 and DIR2 correspond to
drive X set to access directory L:\FILECLASS on the
the number of directories match between the PATH and
server so that directories DIR1 and DIR2 correspond to
the DEVCLASS definitions.
the number of directories match between the PATH and
the DEVCLASS definitions. ANR8505I Verifying path definitions for library
library name between storage agent
storage agent and library manager primary
ANR8504E A failure occurred in flushing data to
library manager. Processing library count
volume server volume name.
out of total library count libraries.
Explanation: The server or storage agent was writing
Explanation: The specified library path definition is
to the indicated volume name when a failure occurred.
being verified for storage agent initialization.
The failure occurred during a flush operation when the
server was attempting to synchronize its progress of System action: The server processes the verification
data written with that of the file system. If the file for the specified library.
system becomes full, it is possible to receive no error
User response: If the server does not finish
indications until the flush operation is attempted.
verification for all the counted shared libraries, verify
System action: The server or storage agent stops connectivity and configuration of the primary library
writing to the specified volume. The transaction in manager paths. Check the library manager of the last
progress is rolled back. storage agent displayed in the library path verification
message.
User response: The server or storage agent can
recover from some failures by requesting access to
different volumes. If there is a directory definition ANR8506E The library library name is not
problem, this message may be displayed multiple times compatible with stand-alone, utility
during retries with different volumes. The directory operations.
names associated with the device class definition in the
Explanation: The specified library cannot operate in
server should be checked for correctness in the number
stand-alone mode such as DUMP DB or RESTORE DB.
and names of directory entries.
The permissions associated with newly created files
should be checked to ensure the server and storage User response: If this is a FILE library, use a device
agent can write to newly created files. Depending on class that does not use a FILE library. A FILE device
the system, a mask value may need to be adjusted. The class does not need a library, and thus, can be updated
system error or event log should be checked for with LIBRARY="" and SHARED=NO. Update your
indications of hardware or software errors from file device configuration file appropriately for the
systems. stand-alone operation, and then if needed, return the
device class to its original state using a FILE library or
For a remotely mounted file system, ensure that the
with SHARED=YES when the server is running.
remote file system is mounted and useable to the
storage agent. The file system should be checked to
ensure that sufficient space is available. While the
server checks space, multiple device classes or servers
using the same file system can cause the server's space
checking to underestimate available space.

ANR8507W Volume volume name is using an ANR8510E No valid path is defined for the
encryption key that is not unique and ZOSMEDIA library library name .
therefore is not secure.
Explanation: The storage operation requires that a
Explanation: Each volume should have a unique path be defined to the ZOSMEDIA library. Without a
encryption key. This volume inappropriately shares an PATH defined to the library, the mount request cannot
encryption key with other volumes. resolve the z/OS Media server name.
System action: The operation completes. System action: The mount request is not processed.
User response: Moving the data from this volume to User response: Define a library path and specify the
new volume will create a unique encryption key for the z/OS Media server with the ZOSMEDIASERVER
new volume and make the data more secure. Before parameter. For instance: consider a ZOSMEDIA library
moving the data, mark this volume READONLY to named ZLIB1 and an IBM Spectrum Protect server
prevent IBM Spectrum Protect from appending data to name of SERVER1. The z/OS Media server that is
the volume. Then, use the MOVE DATA command to accessible using IP address of 9.8.7.6 and is listening on
move the data from this volume to a new volume in port 1492 and is named is ZMEDSRV1. The following
your encryption storage pool. commands properly configure server SERVER1 for
accessing ZLIB1. . DEFINE LIBRARY ZLIB1
LIBTYPE=ZOSMEDIA DEFINE SERVER ZMEDSRV1
ANR8508E Device type volume volume name cannot
SERVERPASS=SECRET HLA=9.8.7.6 LLA=1492 DEFINE
be written by DB2's archive log
PATH SERVER1 ZLIB1 SRCTYPE=SERVER
operation.
DESTTYPE=LIBRARY
Explanation: The specified volume already exists or ZOSMEDIASERVER=ZMEDSRV1 .
archive log data to be written to it. Or there is no space
ANR8511E Unable to resolve ZOSMEDIASERVER
available on the destination filespace to write this
mediaservername from the library path.
backup to.
Explanation: The storage operation requires that a
server defintion exist that matches the
ZOSMEDIASERVER name of the library path. Without
overwritten by the DB's archive log operation, or that
a SERVER defined, the storage operation can not be
there is not enough space available.
completed because the request is unable to determine
User response: If the specified volume does not the z/OS Media servers HLA and LLA.
contain any valuable data, delete it.
System action: The mount request is not processed.
User response: Determine the High Level Address (
ANR8509E No compatible drives are available for
HLA ) and Low Level Address ( LLA ) of the z/OS
device class devclass name.
Media server and use DEFINE SERVER command to
Explanation: The attempted operation cannot be build a server definition that represents the z/OS
completed for the specified device class because there Media server. The servername that is used to define the
are no available drives. This message can indicate an z/OS Media server must match the
invalid FORMAT or DEVTYPE value for the specified ZOSMEDIASERVER name of the library PATH. For
device class. The message can also indicate that the instance: consider a ZOSMEDIA library named ZLIB1
FORMAT and DEVTYPE values are valid, but no and an IBM Spectrum Protect server name of SERVER1.
compatible drives are online. The z/OS Media server that is accessible using IP
address of 9.8.7.6 and is listening on port 1492 and is
System action: The attempted operation fails. named is ZMEDSRV1. The following commands
User response: Use the QUERY DEVCLASS command properly configure server SERVER1 for accessing
to check the device class's FORMAT and DEVTYPE ZLIB1. . DEFINE LIBRARY ZLIB1
values. Compare these values with the equivalent LIBTYPE=ZOSMEDIA DEFINE SERVER ZMEDSRV1
values for QUERY DRIVE F=D. There must be at least SERVERPASS=SECRET HLA=9.8.7.6 LLA=1492 DEFINE
one online drive with DEVTYPE and FORMAT values PATH SERVER1 ZLIB1 SRCTYPE=SERVER
that are compatible with the device class attempting DESTTYPE=LIBRARY
this operation. If there are no compatible drives, correct ZOSMEDIASERVER=ZMEDSRV1
this configuration and retry the operation.
ANR8512E Cannot specify RETENTION with
EXPIRATION during DEFINE or
UPDATE DEVCLASS.
Explanation: The DEFINE DEVCLASS cannot specify

both RETENTION and EXPIRATION, they are conflict inventory reflecting the deleted volume.
parameters.
Explanation: The z/OS Media server cannot be
System action: The command request is not reached during a volume deletion request. The IBM
processed. Spectrum Protect server continues the operation even
though the z/OS Media server cannot be reached.
User response: If a device class has an existing
EXPIRATION value, the devclass cannot update if System action: The volume is not deleted on the z/OS
RETENTION is specified. If a device class has existing Media server.
RETENTION value, the device class cannot update if
User response: Deremine why the z/OS Media server
EXPIRATION is specified. The two parameters
cannot be contacted. Examine the IBM Spectrum
(RETENTION and EXPIRATION ) are mutually
Protect activity log for message ANR8515W and
exclusive.
carefully consider removing the associated dataset on
the z/OS system.
ANR8513E zOS Media Server (server name)
password is too long to use for
ANR8516W The z/OS Media server is unreachable at
authentication with Tivoli Storage
HLA and LLA .
Manager for z/OS Media. The password
cannot exceed 16 characters. Explanation: The z/OS Media server cannot be
reached during a ZOSMEDIA library request. The IBM
Explanation: The SERVERPASSWORD must be
Spectrum Protect server may continue the operation
specified with 16 characters or less. The password must
even though the z/OS Media server cannot be reached.
match the passphrase option on the target z/OS Media
server. System action: The operation likely fails.
System action: The operation is not processed. User response: Determine why the z/OS Media server
cannot be contacted.
User response: Issue the UPDATE SERVER command
and specify a SERVERPASSWORD that does not exceed
16 characters and ensure it contains characters that ANR8517E The z/OS Media server is reachable at
match the passphrase option on the z/OS Media server. HLA and LLA however fails to connect
because of an authentication failure..
ANR8514W Tivoli Storage Manager for z/OS Media Explanation: The z/OS Media server could be reached
server (server name) could not extend the during a ZOSMEDIA library request. However,
FILE volume volume name. authentication could not be completed. The IBM
Spectrum Protect server will not continue the operation
Explanation: The z/OS Media server made an attempt
because the z/OS Media server connection can be
to EXTEND the VSAM LDS FILE volume using the
authenticated.
SECONDARYALLOCATION value from the FILE
device class and failed. System action: The operation fails.
System action: The WRITE operation fails and the User response: Determine why the z/OS Media server
FILE volume is marked "read-only". connection cannot be authenticated. Check to ensure
the PASSPHRASE option on the Tivoli Storage Manager
User response: Allow Tivoli Storage Manager for
for z/OS Media server matches the serverpassword of
z/OS Media server to create EA-enabled VSAM linear
the media server definiton on the IBM Spectrum
data set volumes. 1. Use SMS to manage the VSAM
Protect Server. The password cannot exceed 16
Linear data sets that are associated with the prefix
characters.
attribute of the FILE device class. 2. Associate the data
sets with a data class (an SMS construct) that specifies
the extended format and extended addressability ANR8518E command: Invalid update request for
options. To make this association between data sets and drive drive name in library library name.
the data class, use an automatic class selection (ACS)
routine to assign the Tivoli Storage Manager for z/OS Explanation: An invalid request has been made for
Media VSAM linear data sets to the relevant SMS data the specified drive. This drive is part of a virtual tape
class. The ACS routine does the assignment based on library(VTL). The requested operation does not apply
the data set name. for drives in a VTL.
ANR8515W The deletion of volume belonging to command.
z/OS Media library is imminent, User response: Do not attempt to change cleaning
however the z/OS Media server is settings for virtual drives. If this library is not a VTL,
unreachable resulting in the IBM use the UPDATE LIBRARY command to change the
Spectrum Protect Server volume library type to SCSI and retry the operation.

server. Check the HLA and LLA values on the server

ANR8519E The z/OS Media server is unable to
definition.
open volume using dataset name .
Explanation: The z/OS Media server cannot OPEN a
ANR8523E The path from the source server to the
volume during a ZOSMEDIA library request and the
destination library is taken offline.
IBM Spectrum Protect server fails the operation.
Explanation: Ensure the z/OS Media server is running
System action: The operation likely fails.
and listening on the appropriate port address. If the
User response: Determine why the z/OS Media server z/OS Media server is listening on the intended port
cannot OPEN the volume. Examine the z/OS Media address and the authentication is configured properly,
server joblog, and the z/OS SYSLOG for error there could a problem with the z/OS Media server
conditions associated with the volume or dataset name. version that requires the library path be taken offline.
System action: The library path is offline.
ANR8520E Command: StorageTek Automated
User response: Determine the service level the z/OS
Cartridge System Library Software
Media server. Check the current README for the
(ACSLS) API module is not available
installed IBM Spectrum Protect Server by searching for
from the system for ACSLS libraries.
z/OS Media server prerequisite specifications.
Explanation: The operatios of the ACSLS type library
require the ACSLS API module loaded to the system. If
ANR8524W The element address of the drive drive
this module is not loaded to the system, define ACSLS
name might be incorrect in the library
library will fail.
library name.
Explanation: The element=autodetect parameter on
User response: Ensure that ACSLS API module is the DEFINE DRIVE command is not supported for a
installed to the system. network attached SCSI (NAS) drive. An invalid element
address will be assigned to the device if the option is
used.
ANR8521E Unable to allocate dataset dynalloc rc =
dynalloc error = Hex and dynalloc info System action: The move tape volume operation fails.
=.
User response: Issue the QUERY DRIVE f=d
Explanation: The z/OS Media server cannot allocate a command to verify the value in the Element field. If
dataset during a ZOSMEDIA library request and the field is empty, issue the UPDATE DRIVE command and
IBM Spectrum Protect server fails the operation. specify a value for the element=address paramenter.
System action: The operation likely fails.
ANR8525E Unable to allocate the device specified
User response: Determine why the z/OS Media server
by unit value
cannot allocate the volume. Examine the z/OS Media
server joblog for ANZ5031I messages for a summary of Explanation: The z/OS media server cannot allocate
dynalloc related info and error messages. Review the the specified device during a ZOSMEDIA library
z/OS SYSLOG for error conditions associated with the request because the UNIT value in the device class that
failed allocation request. is associated with the volume mount request specifies a
device address that is already allocated.
ANR8522E The z/OS Media server is unreachable at System action: The IBM Spectrum Protect server fails
HLA with LLA and fails to complete a the operation.
connection because of a protocol
User response: Verify that the MOUNTLIMIT
violation.
parameter value in the device class is 1 if the UNIT
Explanation: The z/OS Media server may not be value specifies a device address. Additionally, you can
listening on the target LLA port. The IBM Spectrum update the MOUNTRETENTION parameter value to 0.
Protect server will not continue the operation because This will ensure that the mounted volume is
the z/OS Media server connection can be established. dismounted after each use.
ANR8526W The IBM tape device driver settings
User response: Determine why the z/OS Media server
have been updated and need to be
connection cannot be established. Check to ensure the
restarted. The device driver can be
z/OS Media server is listening on the target IP address
restarted by either restarting windows
and port address. The protocol violation indicates an
or reinstalling the IBM tape device
application is listening on the target HLA port,
driver.
however the application program is not a z/OS Media

ANR8527E • ANR8550E (Linux)
Explanation: The IBM tape device driver settings have

ANR8530W Volume volume name in drive drive name
been changed to not automatically reserve the drive. By
in library library name is not labeled.
allowing IBM Spectrum Protect to manage the
reservations this will elminate some reservation Explanation: The label is blank.
warnings and potential mount failures. This is a one
System action: This volume might be labeled
time change that requires the device driver to be
automatically if the AUTOLABEL parameter is set to
re-initalized. Reinitalizing the device driver can be
YES and the library supports automatic labeling.
accomplished by either restarting windows or
reinstalling the IBM tape device driver. Restarting User response: To label the volume manually, issue
windows is simpler; reinstalling the IBM tape device the LABEL LIBVOLUME command. Check the volume
driver is less disruptive. in by issuing the CHECKIN LIBVOLUME command.
System action: Possible reservation conflicts between
hosts. ANR8531W Deletion of FILE volume volume name
from file system did not complete
User response: Restart windows or reinstall the IBM
successfully.
tape device driver to cause the IBM device driver to
detect the registry change. Explanation: The server did not delete the file volume
from the file system because the server cannot find the
file volume. The file volume is no longer accessible
ANR8527E The default cartridge access port (CAP)
through the server but it might continue to occupy
ID is invalid for library library name.
space in the file system, if it still exists.
Explanation: The default CAP ID was specified in the
System action: The server continues operation, and
CHECKOUT LIBVOLUME command. If the default
the file volume is logically deleted within the server,
CAP ID is specified, the CAP priority value must be set
but it is not deleted from the file system.
to a nonzero value.
User response:
System action: The system failed to eject the tape
volumes.
ANR8550E (AIX) Error opening filespec.
User response: To verify the CAP priority value, issue
the QUERY CAP command. If the priority value is 0, Explanation: An error occurs while attempting an
set the CAP priority to a nonzero value and reissue the open operation.
CHECKOUT LIBVOLUME command.
ANR8528E The slot element address slot element User response:

address is invalid for the library name v Refer to the other displayed messages to determine
library. why the open operation has failed. Correct the
Explanation: The slot element address is no longer
valid. This issue might occur when a library is turned v If you have entered a file name ensure that the file
off or during a hardware malfunction. For a virtual name is correct and that it exists.
library, this problem also might occur after the library
is reconfigured or its firmware is updated. ANR8550E (HP-UX) Error opening file name.
System action: The slot in this library is unavailable. Explanation: An error occurs while the server
User response: Ensure that the library is turned on attempts a file open operation.
and that no hardware problems are evident. To verify System action: Server processing continues.
the slot element address, use the device driver tool or
virtual library configuration tool. User response:
v Refer to the other displayed messages to determine
why the open operation has failed. Correct the
ANR8529E Command: Unable to open library library
name by using an open system call.
v If you have entered a file name ensure that the file
Explanation: IBM Spectrum Protect cannot open the name is correct and that it exists.
library.
System action: The transaction that requires this ANR8550E (Linux) Error opening file name.
library fails.
Explanation: An error occurs while the server
User response: Inspect the library. Ensure that the attempts a file open operation.
library is turned on and ready. Ensure that the library
is configured correctly for the host system. System action: Server processing continues.

ANR8550E (Solaris) • ANR8552E (HP-UX)
User response:
ANR8551E (Linux) An error (error code) occurred
v Refer to the other displayed messages to determine during a write operation.
problem and restart the process. Explanation: An error occurs while the server
attempts a write operation.
name is correct and that it exists. System action: Server processing continues.
User response: Refer to the other displayed messages
ANR8550E (Solaris) Error opening file name. to determine why the write operation failed; correct the
attempts a file open operation.
ANR8551E (Solaris) An error (error code) occurred
during a write operation.
User response:
v Refer to the other displayed messages to determine attempts a write operation.
problem and restart the process. System action: Server processing continues.
v If you have entered a file name ensure that the file User response: Refer to the other displayed messages
name is correct and that it exists. to determine why the write operation failed. Correct
the problem and restart the process.
ANR8550E (Windows) Error opening filespec.
ANR8551E (Windows) An error (error code) occurred
during a write operation.
attempting an open operation.
attempting a write operation.
User response:
v Refer to the other displayed messages to determine
why the open operation has failed. Correct the User response: Refer to the other displayed messages
problem and restart the process. to determine why the write operation has failed.
Correct the problem and restart the process.
name is correct and that it exists.
ANR8552E (AIX) An error (error code) occurred during
a read operation.
ANR8551E (AIX) An error (error code) occurred during
a write operation. Explanation: An error occurs while attempting a read
operation.
Explanation: An error occurs while attempting a write
operation. System action: Server processing continues.
System action: Server processing continues. User response: Refer to the other displayed messages
to determine why the read operation failed; correct the
to determine why the write operation failed; correct the
ANR8552E (HP-UX) An error (error code) occurred
ANR8551E (HP-UX) An error (error code) occurred
during a write operation. Explanation: An error occurs while the server
attempts a read operation.
attempts a write operation. System action: Server processing continues.
System action: Server processing continues. User response: Refer to the other displayed messages
to determine why the read operation failed. Correct the
to determine why the write operation failed. Correct
the problem and restart the process.

ANR8552E (Linux) • ANR8554W (AIX)

ANR8552E (Linux) An error (error code) occurred
DUMPDB operation, or specify a different volume
name.
attempts a read operation.
ANR8553E (Linux) Device type volume volume name
System action: Server processing continues. cannot be overwritten by DUMPDB
operation.
to determine why the read operation failed; correct the Explanation: The specified volume already exists or
problem and restart the process. contains data, so that the server cannot allow new
DUMPDB data to be written to it.
ANR8552E (Solaris) An error (error code) occurred System action: The server has detected that the given
during a read operation. volume already contains data that would be
overwritten by the requested DUMPDB operation.
attempts a read operation. User response: If the specified volume does not
User response: Refer to the other displayed messages name.
to determine why the read operation failed. Correct the
ANR8553E (Solaris) Device type volume volume name
cannot be overwritten by DUMPDB
ANR8552E (Windows) An error (error code) occurred operation.
Explanation: The server detects an error while contains data, so that the server cannot allow new
attempting a read operation. DUMPDB data to be written to it.
System action: Server processing continues. System action: The server has detected that the given
volume already contains data that would be
User response: Refer to the other displayed messages overwritten by the requested DUMPDB operation.
to determine why the read operation has failed. Correct
the problem and restart the process. User response: If the specified volume does not
ANR8553E (AIX) Device type volume volume name name.
operation.
ANR8553E (Windows) Device type volume volume
Explanation: The specified volume already exists or name cannot be overwritten by
contains data, so that the server cannot allow new DUMPDB operation.
System action: The server has detected that the given contains data, so that the server cannot allow new
volume already contains some data that would be DUMPDB data to be written to it.
overwritten by the requested DUMPDB operation.
User response: If the specified volume does not volume already contains some data that would be
contain any valuable data, delete it and retry the overwritten by the requested DUMPDB operation.
DUMPDB operation.
User response: If the specified volume does not
ANR8553E (HP-UX) Device type volume volume name DUMPDB operation.
operation.
ANR8554W (AIX) Dump/load command: Device class
Explanation: The specified volume already exists or device class name not defined. Devtype of
contains data, so that the server cannot allow new FILE is assumed.
Explanation: The specified device class name is not
System action: The server has detected that the given defined with the DUMPLOADDB DEVCLASS option,
volume already contains data that would be to the server in the server options file or the server is
overwritten by the requested DUMPDB operation. not able to define the specified device class.
User response: If the specified volume does not System action: Processing continues. The dump/load

ANR8554W (HP-UX) • ANR8555E (Windows)
process assumes the device class is devtype=FILE and

ANR8555E (AIX) Error error code (error string)
writes to or reads from a file.
occurred during a read operation from
User response: Refer to the other displayed messages disk disk name.
to determine why the device class is not defined.
Explanation: An error occured while attempting a
Correct the problem and restart the command if you do
read from disk.
not wish to write to or read from a file.
ANR8554W (HP-UX) Dump/load command: Device User response: Correct the problem and start the
class device class name not defined. process again.
Devtype of FILE is assumed.
Explanation: The specified device class name is not ANR8555E (HP-UX) An error (error code, error string)
defined with the DUMPLOADDB DEVCLASS option, occurred during a read operation from
to the server in the server options file or the server is disk disk name.
not able to define the specified device class.
System action: Processing continues. The dump/load read from disk.
process assumes the device class is devtype=FILE and
writes to or reads from a file.
User response: Correct the problem and restart the
process.
not wish to write to or read from a file. ANR8555E (Linux) An error (error code, error string)
occurred during a read operation from
disk disk name.
ANR8554W (Linux) Dump/load command: Device class
device class name not defined. Devtype of Explanation: An error occured while attempting a
FILE is assumed. read from disk.
Explanation: The specified device class name is not System action: Server processing continues.
defined with the DUMPLOADDB DEVCLASS option,
to the server in the server options file or the server is User response: Correct the problem and restart the
not able to define the specified device class. process.
System action: Processing continues. The dump/load

process assumes the device class is devtype=FILE and ANR8555E (Solaris) An error (error code, error string)
writes to or reads from a file. occurred during a read operation from
disk disk name.
to determine why the device class is not defined. Explanation: An error occured while attempting a
Correct the problem and restart the command if you do read from disk.
not wish to write to or read from a file. System action: Server processing continues.
ANR8554W (Solaris) Dump/load command: Device process.
class device class name not defined.
Devtype of FILE is assumed.
ANR8555E (Windows) An error (error code) occurred
Explanation: The specified device class name is not during a read operation from disk disk
defined with the DUMPLOADDB DEVCLASS option, name.
to the server in the server options file or the server is
not able to define the specified device class. Explanation: An error occured while attempting a
read from disk.
System action: Processing continues. The dump/load
process assumes the device class is devtype=FILE and System action: Server processing continues.
writes to or reads from a file. User response: Correct the problem and restart the
User response: Refer to the other displayed messages process.
not wish to write to or read from a file.

ANR8556E (AIX) • ANR8577E (HP-UX)
ANR8556E (AIX) Error error code (error string) ANR8557W (AIX) Retrying failed I/O operation for
occurred during a write operation to disk disk name, error number number.
disk disk name.
Explanation: An error occured while attempting an
Explanation: An error occured while attempting a I/O operation on a disk volume. The request will be
write to disk. retried.
System action: Server processing continues. System action: The failed I/O operation is attempted
again.
process. User response: Correct the problem being reported to
avoid more errors in the future, or contact AIX support
for assistance.
ANR8556E (HP-UX) An error (error code, error string)
occurred during a write operation to
disk disk name. ANR8558E (AIX) I/O vector element bufP: buffer
address, len: buffer length, offset: file offset,
errno: errno.
write to disk.
Explanation: This is a diagnostic message showing
details of an AIO request which had an error. This
User response: Correct the problem and restart the message is normally proceeded by ANR8555E or
process. ANR8556E and offers additional information related to
the I/O error.
ANR8556E (Linux) An error (error code, error string) System action: Server processing continues.
User response: Correct the problem and start the
disk disk name.
process again.
write to disk.
ANR8577E (AIX) IBM Spectrum Protect was not able
System action: Server processing continues. to open the SSL key-ring file file name.
The GSKit return code is return code.
process. Explanation: Initialization of the SSL environment
ANR8556E (Solaris) An error (error code, error string) System action: Server operation continues.
User response: Verify that the correct SSL key-ring file
disk disk name.
is in the server instance directory. If the password was
Explanation: An error occured while attempting a changed with an external utility, use the SET
write to disk. SSLKEYRINGPW command to resynchronize the
key-ring file password with the value that the server
System action: Server processing continues. uses. If the problem persists then delete the key-ring
User response: Correct the problem and restart the file and run the DELETE KEYRING server command so
process. that the server can generate a new key-ring file.
ANR8556E (Windows) An error (error code) occurred ANR8577E (HP-UX) IBM Spectrum Protect was not
during a write operation to disk disk able to open the SSL key-ring file file
name. name. The GSKit return code is return
code.
write to disk. Explanation: Initialization of the SSL environment
process. User response: Verify that the correct SSL key-ring file
changed with an external utility, use the SET
SSLKEYRINGPW command to resynchronize the
uses. If the problem persists then delete the key-ring
file and run the DELETE KEYRING server command so

ANR8577E (Linux) • ANR8578E (Windows)
that the server can generate a new key-ring file.

ANR8578E (AIX) The IBM Spectrum Protect database
does not have a password for the SSL
ANR8577E (Linux) IBM Spectrum Protect was not key-ring file.
able to open the SSL key-ring file file
name. The GSKit return code is return
code.
Explanation: Initialization of the SSL environment
failed. Connections to SSL ports are not possible. User response: Delete the key-ring file so that IBM
Spectrum Protect can generate a new one.
ANR8578E (HP-UX) The IBM Spectrum Protect
database does not have a password for
changed with an external utility, use the SET
the SSL key-ring file.
key-ring file password with the value that the server Explanation: Initialization of the SSL environment has
uses. If the problem persists then delete the key-ring failed. Connections to SSL ports are not possible.
file and run the DELETE KEYRING server command so
User response: Delete the key-ring file so that IBM
ANR8577E (Solaris) IBM Spectrum Protect was not
able to open the SSL key-ring file file
name. The GSKit return code is return ANR8578E (Linux) The IBM Spectrum Protect
code. database does not have a password for
the SSL key-ring file.
failed. Connections to SSL ports are not possible. Explanation: Initialization of the SSL environment has
is in the server instance directory. If the password was User response: Delete the key-ring file so that IBM
changed with an external utility, use the SET Spectrum Protect can generate a new one.
uses. If the problem persists then delete the key-ring ANR8578E (Solaris) The IBM Spectrum Protect
file and run the DELETE KEYRING server command so database does not have a password for
that the server can generate a new key-ring file. the SSL key-ring file.
ANR8577E (Windows) IBM Spectrum Protect was failed. Connections to SSL ports are not possible.
not able to open the SSL key-ring file System action: Server operation continues.
file name. The GSKit return code is return
code. User response: Delete the key-ring file so that IBM
ANR8578E (Windows) The IBM Spectrum Protect
System action: Server operation continues. database does not have a password for
User response: Verify that the correct SSL key-ring file the SSL key-ring file.
is in the server instance directory. If the password was Explanation: Initialization of the SSL environment has
changed with an external utility, use the SET failed. Connections to SSL ports are not possible.
key-ring file password with the value that the server System action: Server operation continues.
uses. If the problem persists then delete the key-ring User response: Delete the keyring file so that IBM
file and run the DELETE KEYRING server command so Spectrum Protect can generate a new one.

ANR8579E (AIX) • ANR8581E (AIX)
ANR8579E (AIX) The SSL key ring file does not ANR8580E (AIX) An SSL write error occurred on
exist, but the IBM Spectrum Protect session session. The GSKit return code is
database contains a password for it. gsk return code.
Explanation: Initialization of the SSL environment has Explanation: An error occurred during an SSL write
failed. Connections to SSL ports are not possible. operation.
User response: Restore a copy of the key ring file or User response: Retry the operation.
use DELETE KEYRING so that IBM Spectrum Protect
can generate a new keyring file and password.
ANR8580E (HP-UX) An SSL write error occurred on
session session. The GSKit return code is
ANR8579E (HP-UX) The SSL key ring file does not gsk return code.
exist, but the IBM Spectrum Protect
Explanation: An error occurred during an SSL write
database contains a password for it.
operation.
User response: Restore a copy of the key ring file or
ANR8580E (Linux) An SSL write error occurred on
gsk return code.
Explanation: An error occurred during an SSL write
ANR8579E (Linux) The SSL key ring file does not
operation.
database contains a password for it. System action: Server operation continues.
Explanation: Initialization of the SSL environment has User response: Retry the operation.
System action: Server operation continues. ANR8580E (Solaris) An SSL write error occurred on
gsk return code.
can generate a new keyring file and password. Explanation: An error occurred during an SSL write
operation.
ANR8579E (Solaris) The SSL key ring file does not System action: Server operation continues.
database contains a password for it. User response: Retry the operation.

failed. Connections to SSL ports are not possible. ANR8580E (Windows) An SSL write error occurred
on session session. The GSKit return
System action: Server operation continues. code is gsk return code.
User response: Restore a copy of the key ring file or Explanation: An error occurred during an SSL write
use DELETE KEYRING so that IBM Spectrum Protect operation.
ANR8579E (Windows) The SSL key ring file does User response: Retry the operation.
not exist, but the IBM Spectrum Protect
database contains a password for it. ANR8581E (AIX) An SSL read error occurred on
Explanation: Initialization of the SSL environment has session session. The GSKit return code is
failed. Connections to SSL ports are not possible. gsk return code.
System action: Server operation continues. Explanation: An error occurred during an SSL read
operation.
use DELETE KEYRING so that IBM Spectrum Protect System action: Server operation continues.
can generate a new keyring file and password. User response: Retry the operation.

ANR8581E (HP-UX) An SSL read error occurred on ANR8582E (Linux) An SSL open-socket error
session session. The GSKit return code is occurred on session session. The GSKit
gsk return code. return code is gsk return code.
Explanation: An error occurred during an SSL read Explanation: An error occurred during an SSL
operation. socket-open operation.
User response: Retry the operation. User response: Retry the operation.
ANR8581E (Linux) An SSL read error occurred on ANR8582E (Solaris) An SSL open-socket error
ANR8581E (Solaris) An SSL read error occurred on ANR8582E (Windows) An SSL open-socket error
ANR8581E (Windows) An SSL read error occurred on ANR8583E (AIX) An SSL socket-initialization error
operation. handshake process.
User response: Retry the operation. User response: Verify that the client is properly
configured for SSL and retry the operation.
ANR8582E (AIX) An SSL open-socket error occurred
on session session. The GSKit return ANR8583E (HP-UX) An SSL socket-initialization
code is gsk return code. error occurred on session session. The
GSKit return code is gsk return code.
Explanation: An error occurred during an SSL
socket-open operation. Explanation: An error occurred during an SSL
handshake process.
User response: Verify that the client is properly
ANR8582E (HP-UX) An SSL open-socket error
occurred on session session. The GSKit
return code is gsk return code. ANR8583E (Linux) An SSL socket-initialization error
occurred on session session. The GSKit
return code is gsk return code.
socket-open operation.
handshake process.

ANR8583E (Solaris) • ANR8585I (Linux)

ANR8584I (Solaris) The SSL TCP/IP Version 6 driver
is ready for connection with clients on
port port number.
ANR8583E (Solaris) An SSL socket-initialization
error occurred on session session. The
port number.
handshake process.
User response: None
ANR8584I (Windows) The SSL TCP/IP Version 6
driver is ready for connection with
ANR8583E (Windows) An SSL socket-initialization
error occurred on session session. The
port number.
handshake process.
User response: None
ANR8585I (AIX) The SSL TCP/IP Version 6 driver is
ready for connection with administrative
ANR8584I (AIX) The SSL TCP/IP Version 6 driver is
ready for connection with clients on
port port number.
port number. User response: None.
ANR8585I (HP-UX) The SSL TCP/IP Version 6 driver
User response: None
is ready for connection with
administrative clients on port port
ANR8584I (HP-UX) The SSL TCP/IP Version 6 driver number.
is ready for connection with clients on
port port number.
Explanation: The server can now accept sessions with on the indicated port number.
port number.
User response: None
ANR8585I (Linux) The SSL TCP/IP Version 6 driver
is ready for connection with
ANR8584I (Linux) The SSL TCP/IP Version 6 driver administrative clients on port port
is ready for connection with clients on number.
port port number.
Explanation: The server can now accept sessions with administrative clients using the SSL TCP/IP protocol
clients using the SSL TCP/IP protocol on the indicated on the indicated port number.
port number.
User response: None

ANR8585I (Solaris) • ANR8587E (Linux)
ANR8585I (Solaris) The SSL TCP/IP Version 6 driver ANR8586E (Solaris) The server was not able to create
is ready for connection with the key-ring file file name. The GSKit
administrative clients on port port key-management return code is return
number. code.
User response: Verify that permissions to the server
User response: None. instance directory are correct.
ANR8585I (Windows) The SSL TCP/IP Version 6 ANR8586E (Windows) The server was not able to
driver is ready for connection with create the key-ring file file name. The
administrative clients on port port GSKit key-management return code is
number. return code.
User response: None. instance directory are correct.
ANR8586E (AIX) The server was not able to create ANR8587E (AIX) The server was not able to create
the key-ring file file name. The GSKit the SSL self-signed certificate. The
key-management return code is return GSKit key management return code is
code. return code.
Explanation: Initialization of the SSL environment has Explanation: Initialization of the SSL environment has
failed. Connections to SSL ports are not possible. failed. Connections to SSL ports are not possible.
User response: Verify that permissions to the server User response: Check the GSKit return code and take
instance directory are correct. appropriate action.
ANR8586E (HP-UX) The server was not able to create ANR8587E (HP-UX) The server was not able to create
code. return code.
ANR8586E (Linux) The server was not able to create ANR8587E (Linux) The server was not able to create
code. return code.

ANR8587E (Solaris) • ANR8589E (Linux)
ANR8587E (Solaris) The server was not able to create ANR8588E (Solaris) The server was not able to
the SSL self-signed certificate. The export to the SSL public certificate file
GSKit key management return code is file name. The GSKit key-management
return code. return code is return code.
Explanation: Initialization of the SSL environment has Explanation: The certificate export file could not be
failed. Connections to SSL ports are not possible. generated for use by the IBM Spectrum Protect clients.
User response: Check the GSKit return code and take User response: Verify that permissions to the server
appropriate action. instance directory are correct.
ANR8587E (Windows) The server was not able to ANR8588E (Windows) The server was not able to
create the SSL self-signed certificate. export to the SSL public certificate file
The GSKit key management return code file name. The GSKit key-management
is return code. return code is return code.
Explanation: Initialization of the SSL environment has Explanation: The certificate export file could not be
failed. Connections to SSL ports are not possible. generated for use by the IBM Spectrum Protect clients.
User response: Check the GSKit return code and take User response: Verify that permissions to the server
appropriate action. instance directory are correct.
ANR8588E (AIX) The server was not able to export ANR8589E (AIX) The server was not able to
to the SSL public certificate file file initialize the GSKit key-management
name. The GSKit key-management environment. The GSKit
return code is return code. key-management return code is return
code.
Explanation: The certificate export file could not be
generated for use by the IBM Spectrum Protect clients. Explanation: The GSKit key-management subsystem
could not be initialized.
instance directory are correct. User response: Verify that permissions to execute the
GSKit key management dynamic-link libraries are
correct.
ANR8588E (HP-UX) The server was not able to
export to the SSL public certificate file
file name. The GSKit key-management ANR8589E (HP-UX) The server was not able to
return code is return code. initialize the GSKit key-management
environment. The GSKit
key-management return code is return
generated for use by the IBM Spectrum Protect clients.
code.
Explanation: The GSKit key-management subsystem
User response: Verify that permissions to the server could not be initialized.
instance directory are correct.
User response: Verify that permissions to execute the
ANR8588E (Linux) The server was not able to export
to the SSL public certificate file file
correct.
name. The GSKit key-management
return code is return code.
ANR8589E (Linux) The server was not able to
initialize the GSKit key-management
generated for use by the IBM Spectrum Protect clients.
System action: Server operation continues. key-management return code is return
code.
instance directory are correct. Explanation: The GSKit key-management subsystem

ANR8589E (Solaris) • ANR8592I (HP-UX)
User response: Verify that permissions to execute the User response: None
correct.
ANR8590I (Solaris) Session session connection is
using SSL version SSL version, cipher
ANR8589E (Solaris) The server was not able to specification cipher specification.
Explanation: An SSL connection was established using
the listed SSL version and cipher specification.
code. System action: Server operation continues.
Explanation: The GSKit key-management subsystem User response: None
System action: Server operation continues. ANR8590I (Windows) Session session connection is
User response: Verify that permissions to execute the
specification cipher specification.
correct. Explanation: An SSL connection was established using
ANR8589E (Windows) The server was not able to System action: Server operation continues.
environment. The GSKit User response: None
code. ANR8591E (Windows) IBM GSKit version 8 must be
Explanation: The GSKit key-management subsystem installed on the system.
could not be initialized. Explanation: The server requires IBM GSKit version 8.
System action: Server operation continues. System action: Server operation stops.
User response: Verify that permissions to execute the User response: To install IBM GSKit version 8, you
GSKit key management dynamic-link libraries are must install the server and restart it.
correct.
ANR8592I (AIX) Session session connection is using

ANR8590I (AIX) Session session connection is using SSL version SSL version, cipher
SSL version SSL version, cipher specification cipher specification,
specification cipher specification. certificate serial number certificate serial
Explanation: An SSL connection was established using number.
the listed SSL version and cipher specification. Explanation: An SSL connection was established using
System action: Server operation continues. the listed SSL version, cipher specification, and
certificate serial number.
User response: None
ANR8590I (HP-UX) Session session connection is User response: None.

specification cipher specification. ANR8592I (HP-UX) Session session connection is
Explanation: An SSL connection was established using using SSL version SSL version, cipher
the listed SSL version and cipher specification. specification cipher specification,
certificate serial number certificate serial
System action: Server operation continues. number.
User response: None Explanation: An SSL connection was established using
the listed SSL version, cipher specification, and
certificate serial number.
ANR8590I (Linux) Session session connection is using
SSL version SSL version, cipher System action: Server operation continues.

ANR8592I (Linux) • ANR8593E (Windows)
ANR8592I (Linux) Session session connection is using ANR8593E (HP-UX) Failure to update key-ring file
SSL version SSL version, cipher password.
specification cipher specification certificate
Explanation: A SET SSLKEYRINGPW password
serial number certificate serial number.
UPDATEPW=YES command was issued to change the
Explanation: An SSL connection was established using key-ring file password. The server was unable to
the listed SSL version, cipher specification and change the key-ring file's password to the specified
ceritificate serial number. new password. The server's record of the password
may be incorrect or the specified new password may
not be acceptable as a new password.
User response: None
User response: To have the server generate a new
ANR8592I (Solaris) Session session connection is
key-ring file password, issue the DELETE KEYRING
command; then halt and restart the server. Any 3rd
specification cipher specification,
pary certificates which had been imported to the
key-ring file previously must be re-imported.
number.
ANR8593E (Linux) Failure to update key-ring file
the listed SSL version, cipher specification, and
password.
cerificate serial number.
User response: None. key-ring file password. The server was unable to
change the key-ring file's password to the specified
new password. The server's record of the password
ANR8592I (Windows) Session session connection is may be incorrect or the specified new password may
using SSL version SSL version, cipher not be acceptable as a new password.
certificate serial number certificate serial System action: Server operation continues.
number.
Explanation: An SSL connection was established using key-ring file password, issue the DELETE KEYRING
the listed SSL version, cipher specification, and command; then halt and restart the server. Any 3rd
cerificate serial number. pary certificates which had been imported to the
key-ring file previously must be re-imported.
User response: None. ANR8593E (Solaris) Failure to update key-ring file
password.
ANR8593E (AIX) Failure to update key-ring file Explanation: A SET SSLKEYRINGPW password
password. UPDATEPW=YES command was issued to change the
Explanation: A SET SSLKEYRINGPW password key-ring file password. The server was unable to
UPDATEPW=YES command was issued to change the change the key-ring file's password to the specified
key-ring file password. The server was unable to new password. The server's record of the password
change the key-ring file's password to the specified may be incorrect or the specified new password may
new password. The server's record of the password not be acceptable as a new password.
may be incorrect or the specified new password may System action: Server operation continues.
System action: Server operation continues. key-ring file password, issue the DELETE KEYRING
User response: To have the server generate a new command; then halt and restart the server. Any 3rd
key-ring file password, issue the DELETE KEYRING pary certificates which had been imported to the
command; then halt and restart the server. Any 3rd key-ring file previously must be re-imported.
key-ring file previously must be re-imported. ANR8593E (Windows) Failure to update key-ring file
password.
key-ring file password. The server was unable to
change the key-ring file's password to the specified

ANR8594I (AIX) • ANR8595I (Solaris)
new password. The server's record of the password

ANR8594I (Windows) Session to address session is
may be incorrect or the specified new password may
Explanation: An outbound SSL connection is being
User response: To have the server generate a new established to the indicated address using the listed
key-ring file password, issue the DELETE KEYRING SSL version and cipher specification.
command; then halt and restart the server. Any 3rd
key-ring file previously must be re-imported. User response: None
ANR8594I (AIX) Session to address session is using ANR8595I (AIX) Session to address session is using
SSL version SSL version, cipher SSL version SSL version, cipher
specification cipher specification. specification cipher specification,
number.
established to the indicated address using the listed
SSL version and cipher specification. Explanation: An SSL connection is being established
to the indicated address using the listed SSL version,
cipher specification, and cerificate serial number.
User response: None
ANR8594I (HP-UX) Session to address session is
specification cipher specification. ANR8595I (HP-UX) Session to address session is
SSL version and cipher specification.
number.
Explanation: An SSL connection is being established
User response: None to the indicated address using the listed SSL version,
ANR8594I (Linux) Session to address session is using System action: Server operation continues.
SSL version SSL version, cipher
ANR8595I (Linux) Session to address session is using
SSL version SSL version, cipher
System action: Server operation continues. certificate serial number certificate serial
number.
User response: None
ANR8594I (Solaris) Session to address session is cipher specification, and cerificate serial number.
specification cipher specification. System action: Server operation continues.
Explanation: An outbound SSL connection is being User response: None.
ANR8595I (Solaris) Session to address session is
System action: Server operation continues. using SSL version SSL version, cipher
User response: None certificate serial number certificate serial
number.

ANR8595I (Windows) • ANR8597E (AIX)
User response: None. ownership information does not match the domain
name or IP address.
ANR8595I (Windows) Session to address session is System action: The session ends.
User response: Ensure that the server domain name or
the IP address (the value of the HLADDRESS
parameter of the DEFINE SERVER command) is
number.
correct. If you are using a self-signed certificate, ensure
Explanation: An SSL connection is being established that it was created on a server at the same address as
to the indicated address using the listed SSL version, specified in the DEFINE SERVER command.
System action: Server operation continues. ANR8596E (Solaris) The certificate identity could not
be verified.
Explanation: The server was unable to open an SSL
connection to the server at address address because the
ANR8596E (AIX) The certificate identity could not be
certificate identity could not be verified. Lack of
verified for the server at address address.
verification happens when the certificate ownership
Explanation: The server was unable to open an SSL information does not match the domain name or IP
connection to the server at the indicated address address.
because the certificate identity could not be verified.
System action: The session ends.
Lack of verification happens when the certificate
ownership information does not match the domain User response: Ensure that the server domain name or
name or IP address. the IP address (the value of the HLADDRESS
User response: Ensure that the server domain name or that it was created on a server at the same address as
the IP address (the value of the HLADDRESS specified in the DEFINE SERVER command.
ANR8596E (Windows) The certificate identity could
that it was created on a server at the same address as
not be verified for the server at address
specified in the DEFINE SERVER command.
address.
ANR8596E (HP-UX) The certificate identity could not
connection to the server at the indicated address
be verified.
because the certificate identity could not be verified.
Explanation: The server was unable to open an SSL Lack of verification happens when the certificate
connection to the server at address address because the ownership information does not match the domain
certificate identity could not be verified. Lack of name or IP address.
verification happens when the certificate ownership
information does not match the domain name or IP
address. User response: Ensure that the server domain name or
the IP address (the value of the HLADDRESS
User response: Ensure that the server domain name or correct. If you are using a self-signed certificate, ensure
the IP address (the value of the HLADDRESS that it was created on a server at the same address as
parameter of the DEFINE SERVER command) is specified in the DEFINE SERVER command.
that it was created on a server at the same address as
ANR8597E (AIX) Certificate information could not
specified in the DEFINE SERVER command.
be retrieved for a connection to the
server at address address.
ANR8596E (Linux) The certificate identity could not
Explanation: The server was unable to obtain
be verified for the server at address
certificate information for an SSL connection to the
address.
server at the indicated address.
connection to the server at the indicated address
because the certificate identity could not be verified. User response: Ensure that the certificate for the target
Lack of verification happens when the certificate server was imported to this server's key-ring file. If you
are using a 3rd-party certificate, you can test it with a

ANR8597E (HP-UX) • ANR8598I (Windows)
session to the target server's SSL port with a browser

ANR8598I (AIX) Outbound SSL Services were
such as Firefox.
loaded.
Explanation: The server is enabled to run SSL sessions
ANR8597E (HP-UX) Certificate information could not
from the server to other servers during node
be retrieved.
replication.
Explanation: The server was unable to obtain
certificate inforamtion for an SSL connection to the
server at address address. User response: None. The server can communicate via
SSL to other servers. Prior to starting the server,
certificates must be loaded in the server's keyring file
User response: Ensure that the certificate for the target (cert.kdb).
server was imported to this server's key-ring file. If you
ANR8598I (HP-UX) Outbound SSL Services were
loaded.
such as Firefox.
Explanation: The server is enabled to run SSL sessions
from the server to other servers during node
ANR8597E (Linux) Certificate information could not
replication.
be retrieved for a connection to the
server at address address. System action: Processing continues.
Explanation: The server was unable to obtain User response: None. The server can communicate via
certificate information for an SSL connection to the SSL to other servers. Prior to starting the server,
server at the indicated address. certificates must be loaded in the server's keyring file
(cert.kdb).
User response: Ensure that the certificate for the target
ANR8598I (Linux) Outbound SSL Services were
loaded.
session to the target server's SSL port with a browser Explanation: The server is enabled to run SSL sessions
such as Firefox. from the server to other servers during node
replication.
ANR8597E (Solaris) Certificate information could not System action: Processing continues.
be retrieved.
User response: None. The server can communicate via
Explanation: The server was unable to obtain SSL to other servers. Prior to starting the server,
certificate inforamtion for an SSL connection to the certificates must be loaded in the server's keyring file
server at address address. (cert.kdb).
ANR8598I (Solaris) Outbound SSL Services were
User response: Ensure that the certificate for the target
loaded.
are using a 3rd-party certificate, you can test it with a Explanation: The server is enabled to run SSL sessions
session to the target server's SSL port with a browser from the server to other servers during node
such as Firefox. replication.
ANR8597E (Windows) Certificate information could
not be retrieved for a connection to the
server at address address.
Explanation: The server was unable to obtain (cert.kdb).
certificate information for an SSL connection to the
server at the indicated address.
ANR8598I (Windows) Outbound SSL Services were
System action: The session ends. loaded.
User response: Ensure that the certificate for the target Explanation: The server is enabled to run SSL sessions
server was imported to this server's key-ring file. If you from the server to other servers during node
are using a 3rd-party certificate, you can test it with a replication.
such as Firefox.


ANR8677E (AIX) User specified module: Cannot load
into server, AIX system error number
number.
(cert.kdb).
Explanation: The server was unable to load the
module specified. The module is not a properly
ANR8675E (AIX) File name: File already exists for File
C-compiled and linked dynamic module.
or Filetext Exit.
System action: Server initialization stops or server
Explanation: The specified file already exists and the
continues running if already up.
file-exit option was set to PRESERVE.
User response: Use the server supplied sample
System action: Server continues running.
makefile and export files to compile-link the user-exit
User response: Specify a non-existent file. module. Make sure the export.ref file contains the
server-defined function name, and the module actually
contains the server-defined function name, with one
ANR8675E (HP-UX) File name with environment variable void parameter declared.
DSMSERV_DIR: File already exists for
File or FileText Exit.
ANR8677E (HP-UX) User specified module, with
Explanation: The specified file already exists and the environment variable DSMSERV_DIR:
file-exit option was set to PRESERVE. Cannot load into server, system errno =
System action: Server continues running. Error number generated by HP-UX.
User response: Specify a non-existent file. Explanation: The server was unable to load the
ANR8675E (Linux) File name with environment variable
DSMSERV_DIR: File already exists for System action: Server initialization stops or server
File/FileText Exit, overwrite option not continues running if already up.
set to YES. User response: Use the server supplied sample
Explanation: The specified file already exists and the makefile and export files to compile-link the user-exit
overwrite option was not set to Yes. module. Make sure the export.ref file contains the
System action: Server continues running. contains the server-defined function name, with one
User response: Specify another file or set the void parameter declared.
overwrite option to YES in the server options file.
ANR8677E (Linux) User specified module, with
ANR8675E (Solaris) File name with environment variable environment variable DSMSERV_DIR:
DSMSERV_DIR: File already exists for Cannot load into server, system errno =
File/FileText Exit, overwrite option not Error number generated by Solaris.
set to YES. Explanation: The server was unable to load the
Explanation: The specified file already exists and the module specified. The module is not a properly
overwrite option was not set to Yes. C-compiled and linked dynamic module.
System action: Server continues running. System action: Server continues running.
User response: Specify another file or set the User response: Use the supplied sample makefile, c ,
overwrite option to YES in the server options file. and h files to generate the user-exit module. Make sure
the module contains product-defined function name
adsmV3UserExit, and the module actually contains the
ANR8675E (Windows) File name with path within product-defined function name, with one void *
registry.: File already exists for File or parameter declared, and returns void.
FileText Exit.
Explanation: The specified file already exists and the ANR8677E (Solaris) User specified module, with
File/FileText exit option was set to PRESERVE. environment variable DSMSERV_DIR:
System action: Server continues running. Cannot load into server, system errno =
Error number generated by Solaris.
User response: Specify a non-existent file.

ANR8677E (Windows) • ANR8679W (AIX)

ANR8678E (Linux) Cannot bind User specified module,
User response: Use the server supplied sample with environment variable DSMSERV_DIR
makefile, c, and h files to generate the user-exit into server, system errno = Error number
module. Make sure the module contains server-defined generated by Solaris.
function name adsmV3UserExit, and the module
Explanation: The server was unable to bind with the
actually contains the server-defined function name,
module specified. The server could not find a function
with one void * parameter declared, and returns void.
named adsmV3UserExit in the module.
ANR8677E (Windows) User specified module, with path
within registry: Cannot load into server, User response: Use the supplied sample makefile, c
system errno = Error number generated by and header files to create the user exit module. Make
Windows. sure the shared library module contains a function
named adsmV3UserExit of type void, with one
parameter of a void *.
ANR8678E (Solaris) Cannot bind User specified module,
with environment variable DSMSERV_DIR
User response: Use the server supplied sample into server, system errno = Error number
makefile compile-link the user-exit module. generated by Solaris.
ANR8678E (AIX) Cannot bind User specified module module specified. The server could not find a function
into server. AIX system error number. named adsmV3UserExit in the module.
Explanation: The server was unable to bind with the System action: Server continues running.
module specified.
System action: Server initialization stops or server makefile, c and header files to create the user exit
continues running if already up. module. Make sure the shared library module contains
a function named adsmV3UserExit of type void, with
User response: Use the server supplied sample one parameter of a void *.
makefile and export files to compile-link the user-exit
module. Make sure the export.ref file contains the
server-defined function name, and the module actually ANR8678E (Windows) Cannot find/set User specified
contains the server-defined function name, with 1 void function name within DLL. in User specified
parameter declared. The module may contain a global DLL library name, with registry path,
variable name that conflicts with the server's. system errno = Error number generated by
Windows.
ANR8678E (HP-UX) Cannot bind User specified Explanation: The server was unable to find and/or
module, with environment variable bind with the function name in the DLL specified.
DSMSERV_DIR into server, system errno
= Error number generated by HP-UX.
makefile to compile-link the user-exit module. Make
module specified.
sure there is a function name in the DLL as specified in
System action: Server initialization stops or server the server options file. Make sure the function only
continues running if already up. accepts one argument, a void pointer.
makefile and export files to compile-link the user-exit ANR8679W (AIX) A user-exit module is already
module. Make sure the export.ref file contains the loaded.
Explanation: A user-exit module was loaded
contains the server-defined function name, with one
previously. Another user-exit module cannot be loaded.
void parameter declared. The module may contain a
global variable name that conflicts with the server's. System action: Server initilization stops or server
User response: To load a new user-exit module, halt
the server and then restart the server with the new
user-exit module.

ANR8679W (HP-UX) • ANR8681I (AIX)
filetext exit, halt the server, then restart the server with
ANR8679W (HP-UX) There is already an user-exit
the new file name.
loaded.
Explanation: There was a previous successful load of
ANR8680W (HP-UX) There is already a file used for
an user-exit module, thus server cannot load another
the file or filetext exit.
one.
Explanation: There was a previous file open for the
file or filetext exit. The server cannot open another one.
User response: To load a new user-exit module, the
server must be halted and then restart the server with
the new user-exit module. User response: To start a new file for the file or
filetext exit, halt the server, then restart the server with
a new file name.
ANR8679W (Linux) Unable to unload user exit
module: system errno = Error number
generated by Solaris. ANR8680W (Linux) There is already a file used for
the file or filetext exit.
Explanation: The server was not able to unload the
user-exit module. Explanation: There was a previous file open for the
file or filetext exit. The server cannot open another one.
User response: The server should be stopped at the
earliest possible time before the user exit is to be
reactivated. User response: To start a new file for the exit, halt the
server, then restart the server with a new file name.
ANR8679W (Solaris) Unable to unload user exit
module: system errno = Error number ANR8680W (Solaris) There is already a named file
generated by Solaris. used for the file or filetext exit.
Explanation: The server was not able to unload the Explanation: There was a previous file open for the
user-exit module. file or filetext exit. The server cannot open another one.
System action: Server continues running. System action: Server initialization stops or server
User response: The server should be stopped at the
earliest possible time before the user exit is to be User response: To start a new file for the file or the
reactivated. filetext exit, halt the server, then restart the server with
a new file name.
ANR8679W (Windows) There is already an user-exit
loaded. ANR8680W (Windows) There is already a file used
for the file or filetext exit.
Explanation: There was a previous successful load of
an user-exit module, thus server cannot load another Explanation: There was a previous file open for the
one. file or filetext exit. The server cannot open another one.
System action: Server continues running. System action: Server continues running.
User response: To load a new user-exit module, halt User response: To start a new file for the exit, halt the
the server and then restart the server with the new server, then restart the server with a new file name.
user-exit module.
ANR8681I (AIX) Connected to Tivoli event server at

ANR8680W (AIX) A file used for the file or filetext node name on port port.
exit is already opened.
Explanation: The server successfully established a
Explanation: A file for the file or filetext exit was connection with the Tivoli event server on the specified
previously opened. The server cannot open another node name and port.
one.
System action: The server sends events to the Tivoli
System action: Server initialization stops or server event server using this connection.
User response: To start a new file for the file or

ANR8681I (HP-UX) • ANR8682E (Windows)
ANR8681I (HP-UX) Connected to Tivoli event server ANR8682E (HP-UX) Unable to determine port of
at node name on port port. Tivoli event server on node name.
Explanation: The server successfully established a Explanation: The server was unable to determine the
connection with the Tivoli event server on the specified TCP/IP port on which the Tivoli event server on node
node name and port. name is listening.
System action: The server sends events to the Tivoli System action: Event logging to the Tivoli event
event server using this connection. server is disabled.
User response: None. User response: Ensure that the Tivoli event server is
running on the specified system. If the system on
which the event server is running does not support the
ANR8681I (Linux) Connected to Tivoli event server
TCP/IP Portmapper, then ensure that TECPORT is
at node name on port port.
Explanation: The server successfully established a
connection with the Tivoli event server on the specified
ANR8682E (Linux) Unable to determine port of
node name and port.
Tivoli event server on node name.
Explanation: The server was unable to determine the
event server using this connection.
TCP/IP port on which the Tivoli event server on node
User response: None. name is listening.
System action: Event logging to the Tivoli event
ANR8681I (Solaris) Connected to Tivoli event server server is disabled.
at node name on port port.
User response: Ensure that the Tivoli event server is
Explanation: The server successfully established a running on the specified system. If the system on
connection with the Tivoli event server on the specified which the event server is running does not support the
node name and port. TCP/IP Portmapper, then ensure that TECPORT is
event server using this connection.
ANR8682E (Solaris) Unable to determine port of
User response: None. Tivoli event server on node name.
ANR8681I (Windows) Connected to Tivoli event TCP/IP port on which the Tivoli event server on node
server at node name on port port. name is listening.
Explanation: The server successfully established a System action: Event logging to the Tivoli event
connection with the Tivoli event server on the specified server is disabled.
node name and port.
System action: The server sends events to the Tivoli running on the specified system. If the system on
event server using this connection. which the event server is running does not support the
User response: None. TCP/IP Portmapper, then ensure that TECPORT is
ANR8682E (AIX) Unable to determine port of Tivoli

event server on node node name. ANR8682E (Windows) Unable to determine port of
Tivoli event server on node name.
TCP/IP port for the Tivoli event server on node node Explanation: The server was unable to determine the
name. TCP/IP port on which the Tivoli event server on node
name is listening.
server is disabled. System action: Event logging to the Tivoli event
server is disabled.
running on the specified system. If the system on User response: Ensure that the Tivoli event server is
which the event server is running does not support the running on the specified system. If the system on
TCP/IP Portmapper, then ensure that TECPORT is which the event server is running does not support the
specified in the server options file. TCP/IP Portmapper, then ensure that TECPORT is

ANR8683E (AIX) • ANR8684E (HP-UX)

ANR8683E (AIX) Unable to connect to the Tivoli
TCP/IP Portmapper, then ensure that the value
event server at node node name on port
specified for TECPORT in the server options file is
port.
correct.
Explanation: The server was unable to establish a
TCP/IP connection with the Tivoli event server on
ANR8683E (Windows) Unable to connect to the
node node name at port port.
Tivoli event server at node name on port
System action: Event logging to the Tivoli event port.
server is disabled.
User response: Ensure that the Tivoli event server is TCP/IP connection with the Tivoli event server on node
running on the specified system. If the system on name at port port.
server is disabled.
correct. User response: Ensure that the Tivoli event server is
ANR8683E (HP-UX) Unable to connect to the Tivoli
event server at node name on port port.
Explanation: The server was unable to establish a correct.
TCP/IP connection with the Tivoli event server on node
name at port port.
ANR8684E (AIX) Unable to connect to the Tivoli
System action: Event logging to the Tivoli event event server because TCP/IP is not
server is disabled. available.
User response: Ensure that the Tivoli event server is Explanation: The server was unable to establish a
running on the specified system. If the system on TCP/IP connection with the Tivoli event server because
which the event server is running does not support the TCP/IP services were not available.
server is disabled.
correct.
User response:
ANR8683E (Linux) Unable to connect to the Tivoli v Ensure that COMMMETHOD TCPIP is specified in
event server at node name on port port. the server options file.
v If COMMMETHOD TCPIP was specified, use the
BEGIN EVENTLOGGING TIVOLI command to
TCP/IP connection with the Tivoli event server on node
manually start event logging to the Tivoli event
name at port port.
server once server initialization has completed.
server is disabled.
ANR8684E (HP-UX) Unable to connect to the Tivoli
User response: Ensure that the Tivoli event server is event server because TCP/IP is not
running on the specified system. If the system on available.
TCP/IP connection with the Tivoli event server because
TCP/IP services were not available.
correct.
server is disabled.
ANR8683E (Solaris) Unable to connect to the Tivoli
event server at node name on port port. User response:
Explanation: The server was unable to establish a v Ensure that COMMMETHOD=TCPIP is specified in
TCP/IP connection with the Tivoli event server on node the server options file, or that
name at port port. COMMMETHOD=NONE is not specified.
v If COMMMETHOD=TCPIP was specified, use the
server is disabled.
manually start event logging to the Tivoli event
User response: Ensure that the Tivoli event server is server once server initialization has completed.

ANR8684E (Linux) • ANR8742E
ANR8684E (Linux) Unable to connect to the Tivoli ANR8685I (AIX) Core dump being generated to file
event server because TCP/IP is not core dump file
available.
Explanation: The server has started generating a
Explanation: The server was unable to establish a coredump to the specified file as a result of a user
TCP/IP connection with the Tivoli event server because request.
server is disabled.
User response:
ANR8686I (AIX) Core dump successfully generated
v Ensure that COMMMETHOD=TCPIP is specified in
the server options file, or that Explanation: The server has successfully generated the
COMMMETHOD=NONE is not specified. requested core dump.
v If COMMMETHOD=TCPIP was specified, use the System action: Server operation continues.
manually start event logging to the Tivoli event User response: None.
server once server initialization has completed.
ANR8687E (AIX) Error generating core dump, errno
ANR8684E (Solaris) Unable to connect to the Tivoli system errno.
event server because TCP/IP is not Explanation: The server was unable to generate the
available. requested core dump. The errno indicates the reason
Explanation: The server was unable to establish a AIX was unable to complete the request.
TCP/IP connection with the Tivoli event server because System action: Server operation continues.
server is disabled.
ANR8740W Number of automated library slots (slots
User response: in use) exceeds license terms (slots
v Ensure that COMMMETHOD=TCPIP is specified in licensed).
the server options file, or that
Explanation: The number of slots in use within
COMMMETHOD=NONE is not specified.
automated libraries exceeds the licensed value.
BEGIN EVENTLOGGING TIVOLI command to System action: The operation completes.
manually start event logging to the Tivoli event User response: Contact your service representative to
server once server initialization has completed. update license values for slots in automated libraries,
or reduce the number of slots in use by issuing
ANR8684E (Windows) Unable to connect to the CHECKOUT LIBVOLUME commands as necessary.
Tivoli event server because TCP/IP is
not available. ANR8741E CHECKIN LIBVOLUME not permitted
Explanation: The server was unable to establish a with current license terms.
TCP/IP connection with the Tivoli event server because Explanation: The CHECKIN LIBVOLUME operation is
TCP/IP services were not available. not permitted because the current license terms do not
System action: Event logging to the Tivoli event allow it.
server is disabled. System action: The command fails.
User response: User response: Contact your service representative to
v Ensure that COMMMETHOD=TCPIP is specified in update license values for slots in automated libraries,
the server options file, or that or reduce the number of slots in use by issuing
COMMMETHOD=NONE is not specified. CHECKOUT LIBVOLUME commands as necessary.
BEGIN EVENTLOGGING TIVOLI command to ANR8742E This server is not licensed to support
manually start event logging to the Tivoli event the device type device type. Device
server once server initialization has completed. Support Module module number is
required.
Explanation: A DEFINE DRIVE command or a

volume mount operation cannot be processed because

ANR8747I Checking in volume volume name in
the server is not licensed to support the required device
library library name- CANCEL
type.
PENDING.
User response: Contact your service representative to command, this message displays the status for a
update the server license terms so that support for the CHECKIN LIBVOLUME process on the server. The
required device type is enabled. given volume was being checked in to the designated
library, but the process was canceled by an
administrator.
ANR8743E This server is not licensed to support
library device name. Device Support System action: The background process operation is in
Module module number is required. a wait queue. When the process comes off the queue, it
will be terminated.
Explanation: Either a DEFINE LIBRARY command, a
volume mount operation, or library initialization cannot User response: None.
be processed because the server is not licensed to
support the given library.
ANR8748I Checking in volumes in search mode in
System action: The operation fails. library library name- CANCEL
PENDING.
User response: Contact your service representative to
update the server license terms so that support for the Explanation: In response to a QUERY PROCESS
given library device is enabled. command, this message displays the status for a
CHECKIN LIBVOLUME process on the server. Volumes
were being checked into the given library in search
ANR8744E Command: Current license terms do not mode, but the process was canceled by an
permit this operation. administrator.
Explanation: The specified command failed because System action: The background process operation is
the current license terms do not permit it. being terminated.
System action: The operation fails. User response: None.
update the server license terms so that the requested ANR8749E Library order sequence check on library
operation can be processed. library name.
Explanation: An attempt has been made to mount or
ANR8745E Support for the 3590 device type is demount a volume, but the attempt fails for one of the
disabled for library library name. following reasons:
Explanation: The requested operation fails because v Mount is already in progress or a volume is already
support for the 3590 device type is not currently mounted.
enabled for the specified library. v Mount is already pending.
System action: The operation fails. v Demount is already pending.
User response: Make sure the ENABLE3590LIBRARY v Demount was requested but no volume is mounted.
option is specified in the server options file, and that System action: The operation fails.
the scratch category number for 3590 volumes does not
conflict with the private category or the CARTRIDGE User response: This error usually occurs when a
volume scratch category. demount fails and a cartridge is left in the drive. All
subsequent mounts fail while attempting to insert
another cartridge into the same drive. Demount the
ANR8746E Device type device type is not supported cartridge using the library manager or perform an
in this release. AUDIT LIBRARY operation on the designated library.
Explanation: The specified device type cannot be used Retry the operation.
by this release/platform of the server.
System action: The device cannot be used. ANR8750E Volume is incompatible with specified
device type in library library name.
User response: Contact your sales or service
representative to upgrade to the latest release of the Explanation: An attempt has been made to mount or
server. check in a volume, but the attempt fails because the
cartridge being mounted is not compatible with the

drive (For example, attempting to mount a 3590

ANR8754E Command: There is already a request to
cartridge on a 3490 drive).
delete library libary name.
Explanation: The designated library cannot be deleted
User response: Ensure the DEVTYPE parameter on or updated because there is a request to delete the
the CHECKIN command matches the device type of library already.
the drive. Retry the operation.
ANR8751W This server is not licensed to support
the device type device type. Managed
Library license is required. ANR8755E Command: There is already a request to
update library library name.
Explanation: This message is issued when a DEFINE
DRIVE command or a volume mount operation uses a Explanation: The designated library cannot be deleted
device class that is not licensed on the server. because there is a request to update the library already.
System action: The operation fails if this is a System action: The command is not processed.
try-and-buy server. For purchased servers, this message
is to warn you that you are not in compliance with
registered license terms.
ANR8756E For optical libraries, you must specify
CHECKLABEL=YES.
update the server license terms so that support for the
required device type is enabled. Explanation: Optical libraries require the
CHECKLABEL parameter to be set to YES
ANR8752W This server is not licensed to support System action: The command fails.
library device type. Managed Library
license is required. User response: Reissue the command and specify the
CHECKLABEL=YES option.
LIBRARY command or a volume mount operation uses
a device class that is not licensed on the server. ANR8757W This server is not licensed to support
library device type. Extended Edition
System action: The operation fails if this is a license is required.
is to warn you that you are not in compliance with Explanation: This message is issued when a DEFINE
registered license terms. LIBRARY command or a volume mount operation uses
a device class that is not licensed on the server.
update the server license terms so that support for the System action: The operation fails if this is a
required device type is enabled. try-and-buy server. For purchased servers, this message
is to warn you that you are not in compliance with
registered license terms.
ANR8753W This server is not licensed to support
library library name. Library Sharing is User response: Contact your service representative to
required. update the server license terms so that support for the
required device type is enabled.
LIBRARY command or library initialization for a
library that requires library sharing and library sharing ANR8758W The number of online drives in the
is not licensed on the server. virtual tape library library name does not
match the number of online drive paths
System action: The operation fails if this is a for source source name.
is to warn you that you are not in compliance with Explanation: If the number of online drives in the
registered license terms. library does not match the number of online paths to
drives in the library for any applicable source, the
User response: Contact your service representative to server might choose a drive that lacks a valid path
update the server license terms so that support for the definition. The server then retries the mount operation,
required device type is enabled. and any retry might adversely affect mount
performance.
System action: Server operations continue. However,
this message indicates that there might be a mount

retry if the selected drive does not have a valid online

ANR8762E The drive drive name in the library library
path defined.
name was unable to obtain an encryption
User response: To resolve the issue, complete the key from the encryption key
following steps: 1. Evaluate all drive path definitions. 2. management.
For any drives that lack a path definition for any
Explanation: The encryption key manager did not
applicable source (for example, storage agents), define
respond to the drive or library that is managed by the
drive paths. 3. Validate that all drive path definitions
IBM Spectrum Protect server. Since IBM Spectrum
are online. 4. If a drive path is offline because of a
Protect is not managing the encryption keys, there is an
hardware issue, resolve the hardware issue and update
issue with the encryption key manager, the drive, or
the path so that it is online. 5. If SAN-attached and
the library.
NAS tape drives are configured in the same library,
separate the tape drives into two libraries. Ensure that System action: The operation fails.
each library has only one type of attachment tape
User response: This is most likely a problem with the
drive.
encryption key manager (for example, a timeout or
communication failure between the encryption key
ANR8759W The drive name drive in the lib name manager and the drive or library). Correct any issues
library is owned by owner name. with the encryption key manager and try the operation
again. If the problem persists, contatct IBM hardware
Explanation: If a drive is owned by a library client or
support.
a storage agent, the library manager does not verify the
drive access and readiness during the library manager
initialization. ANR8763E Command: Volume volume name not
processed: library library name not
defined.
User response: In a shared library environment, the
owner of a tape drive can change. If a tape drive is
since the designated library has not been defined or has
owned by a library client or storage agent, the library
been deleted.
manager cannot access the tape drive. For example, if a
library client or storage agent owns a tape drive, but System action: The volume is not processed.
the library manager halts or fails to respond, on
startup, the library manager remembers the library
library name, or define the library before retrying the
client or storage agent that owns the drive, and skips
command.
processing this drive. If the library client or storage
agent is not synchronized with the library manager and
has no record of owning the drive, this can result in an ANR8764E Command: Volume volume name not
inability to use the drive. In this case, you might need processed: the operation is not allowed
to reset the drive reservation from the host machine of for library type library type.
the library client or storage agent.
since the requested operation is not allowed for
ANR8760I Cancel in progress. libraries of the given type.
Explanation: The MOVE MEDIA command has been System action: The volume is not processed.
canceled and will end when resources have been freed
for the background process. This message may be User response: None.
for a MOVE MEDIA command. ANR8765I Request number: device type volume volume
System action: Server operation continues. name in location location name is required
for use in library library name; CHECKIN
User response: None. LIBVOLUME required within time limit
minutes.
ANR8761I Number of volumes processed: number Explanation: A mount request has been made for a
volume that is defined in a storage pool, but which is
Explanation: The MOVE MEDIA command has
currently checked out of the given library and stored in
processed the number of volumes displayed. This
the location shown.
message may be displayed in response to a QUERY
PROCESS command for a MOVE MEDIA command. System action: The server waits until it detects that
the volume has been checked into the library, or the
time limit expires.
User response: Obtain the required volume from the

indicated location, and insert it into the library by have the same name as the label.
issuing a CHECKIN LIBVOLUME command. Use the
SWAP=YES option of the CHECKIN LIBVOLUME
ANR8769E External media management function
command if the library is currently full; this process
request type returned result=result.
allows the server to select an appropriate volume to be
swapped out in order to make room for the required Explanation: A request of the indicated function type
volume. was sent to the external library manager program,
which returned a result code which was not SUCCESS.
ANR8766I MOVE MEDIA command: CHECKOUT System action: The server continues, but the server
LIBVOLUME command for volume volume operation that was being attempted fails.
name in library library name completed
successfully; Place the ejected volume in User response: Consult the documentation for the
location location name. external media management program to determine how
to recover from the error condition. Then attempt the
Explanation: The CHECKOUT LIBVOLUME operation server operation again.
has completed successfully for the indicated volume in
the given library. Place the ejected volume in the
indicated location. ANR8770W Unable to load external library manager
filespec.
library inventory (if its status is something other than Explanation: A library of LIBTYPE=EXTERNAL is
DATA) or marked not present (if its status is DATA). defined but the server cannot load the external library
manager.
User response: If an *UNKNOWN* location is
displayed, issue UPDATE STGPOOL OVFLOCATION System action: The server continues, but the external
command to define an overflow location name to be library cannot be accessed.
used on the subsequent MOVE MEDIA command. For User response: Verify that the EXTERNALMANAGER
the volumes ejected with an *UNKNOWN* location, parameter for the external library is specified correctly
use UPDATE VOLUME LOCATION command to on the DEFINE LIBRARY or UPDATE LIBRARY
update its location to your overflow location name. command.
ANR8767I Number of volumes processed: number ANR8771E Volume volume name in library library
volumes processed. Volumes sent to library name is deleted. External Library is not
library name for checkout: number volumes synchronized with the server. Audit
sent. required.
Explanation: The MOVE MEDIA command has Explanation: The server deleted a volume from its
processed the number of volumes shown. Currently, the inventory, and its attempt to inform the external library
MOVE MEDIA command has sent for processing the manager has failed.
number of volumes shown to the library shown. This
message may be displayed in response to a QUERY System action: The server may continue to access the
PROCESS command for a MOVE MEDIA command. library, but some volumes may not be accessible until
the external library is synchronized with the server.
User response: Perform the appropriate type of
User response: None. processing on the external library in order to
synchronize it with the server.
ANR8768E File file name on volume drive name could
not be found. ANR8772I Moving volume volume name (if known)
Explanation: The server was unable to find the from drive drive name to slot slot element
specified file name on the indicated volume. For number in library library name.
removable file device classes, each volume maintains Explanation: A volume found in the drive during
data using a file name which is the same as the volume library initialization is being moved to the slot.
name and the label value on the volume.
System action: The volume is moved from the drive
System action: The volume is rejected. to the slot.
User response: Ensure that the proper volume has User response: None.
been placed into the drive. If you are creating a
removable file device class volume by copying data
from a FILE device class volume, the media must have
a label which is the same as the volume name. The file
which is copied to the volume must be renamed to

ANR8773E Incompatible options ANR8776W Volume volume name in drive drive name
CHECKLABEL=NO and SEARCH=YES contains lost VCR data; performance
for library type library. may be degraded.
Explanation: If a barcode reader is not installed and Explanation: The Vital Cartridge Records of the
detected by the server, the server requires the ability to cartridge in the drive are lost or corrupted. This results
check the tape label when searching for new volumes in the inability of the drive to do fast locates to file
in a VTL or SCSI tape library. The CHECKLABEL=NO positions on the cartridge, which causes the locate
and SEARCH=YES parameters on the CHECKIN performance for read or append operations to become
LIBVOL command are not compatible. degraded.
System action: The command fails. System action: The server continues the operation.
User response: Reissue the CHECKIN LIBVOL User response: There are two methods to restore the
command and specify CHECKLABEL=YES. VCR data. The first method uses the MOVE DATA
command to move the data off the tape and to return
the tape to scratch or empty status. The VCR data is
ANR8774W Volume volume name not checked into
rebuilt when the empty tape is rewritten from the
library library name but is using category
beginning-of-tape. The second method rebuilds the
category number.
VCR by loading the tape and locating directly to the
Explanation: While processing a DEFINE LIBRARY or end-of-data. This is done by the server in normal use
AUDIT LIBRARY command for the given library, the when new data is appended to the end of the tape. It
server found a volume that was not checked into the can also be done independent of the server by loading
library (with the CHECKIN LIBVOL command), but is the tape in an unused drive and using the tapeutil
assigned to one of the categories in use by that library. program. Select the tapeutil option "Space to
End-of-Data".
System action: If the volume category equals the
value of the library SCRATCHCAT the category is
changed to the value of the library PRIVATECAT. This ANR8777E Mount for volume volume name failed;
is to prevent the library from loading the volume when media performance is degraded.
a scratch volume is requested.
Explanation: The VCR data on the volume is lost or
User response: If the volume is to be used by the corrupted, resulting in degraded tape positioning. The
server, it does not have to be reassigned but it must be mount fails because the tape drive was configured to
checked into the library with the CHECKIN LIBVOL fail mounts that indicate this condition.
command. If the volume is not to be used by the
System action: The client command fails and the
server, use the mtlib program to reassign the volume to
transaction is rolled back.
its correct category. For details about the mtlib
program, refer to the documentation provided with the User response: Until the VCR data can be restored,
library device. the user can issue the UPDATE VOLUME command to
make the volume unavailable. There are two methods
to restore the VCR data. The first method uses the
ANR8775I Drive drive name unavailable at library
MOVE DATA command to move the data off the tape
manager.
and to return the tape to scratch or empty status. The
Explanation: The specified drive availability status at VCR data is rebuilt when the empty tape is rewritten
the library manager has changed from available to from the beginning-of-tape. The second method
unavailable. rebuilds the VCR by loading the tape and locating
directly to the end-of-data. This is done by the server in
System action: The drive status on the server is normal use whenever data is appended to the end of
updated to reflect the availability to that of the library the tape. It can also be done independent of the server
manager. The drive will not be considered as a by loading the tape in an unused drive and using the
candidate for the mount or demount request. tapeutil program. Select the tapeutil option "Space to
User response: Contact your service representative to End-of-Data".
determine the cause of the drive becoming unavailable.
Once the service representative has determined the ANR8778W Scratch volume volume name changed to
cause and changed the availability status to available at Private Status to prevent re-access.
the library manager, the server will resume use of the
drive. Explanation: The scratch volume encountered an error
during mount processing that makes it unusable. The
status of the volume is changed to private so that it is
not selected for future scratch mounts. (Although the
status has become private, it is not defined to a storage
pool.)

System action: Processing continues with another User response: Use the appropriate labeling utility to
scratch volume. label the media. In Windows NT, the LABEL command
is used to label removable disk cartridges, diskettes and
User response: See previous error messages to
other media which appear as drive letters. This label
determine the cause of the mount failure, and correct
must still conform to server requirements.
the problem. If the problem is a mislabeled volume or
unreadable label, relabel the scratch volume using the
dsmlabel utility with the "-overwrite" option. If the ANR8782E Volume volume name could not be
volume is missing from its home slot, issue the AUDIT accessed by library library name.
LIBRARY command against the library. If the volume
Explanation: The designated volume is in the
has lost or corrupted VCR-data, relabel the volume.
inventory of the Library Manager, but the physical
(This reinitializes the VCR-data by writing to the
location is either inaccessible or unknown.
volume from beginning-of-tape.) Once the problem is
corrected, update the status of the volume to scratch by System action: The operation fails. The access mode of
using the UPDATE LIBVOL command. the volume is changed to UNAVAILABLE.
User response: Ensure that the cartridge is physically
ANR8779E Unable to open drive drive name, error in the library, and reinventory the library. If the volume
number= errno value from open system call. location is resolved, restore the access mode of the
volume to its previous value using the UPDATE
Explanation: The drive cannot be opened by the
VOLUME command.
server. On UNIX and Linux systems, an error number
is a value of an errno returned by the operating system.
On Windows, an error number is a Windows error ANR8783E Label on volume in drive drive name
message number. could not be read.
System action: The transaction that needs the drive Explanation: The server was unable to read the label
fails. on the indicated drive.
User response: Use the error number in conjunction System action: The volume is rejected.
with operating system documentation to narrow the
scope of the cause. Inspect the drive. Ensure that the User response: Use the appropriate labeling utility to
drive is powered on and ready, that the cables are label the media. In Windows NT, the LABEL command
properly connected and terminated, and that the device is used to label removable disk cartridges, diskettes and
is properly configured to the operating system. other media which appear as drive letters. This label
must still conform to server requirements.
ANR8780E Volume in drive drive name has no label.

ANR8784E File file name on volume drive name could
Explanation: The volume in the indicated drive does not be created.
not have a label. The server requires that all media be
uniquely labeled. Explanation: The server was unable to create the
indicated file on the indicated volume. The server
System action: The volume is rejected and the server creates a file on removable media in which to store
prompts for a new volume. data.
User response: Use the appropriate labeling utility to System action: The volume is rejected.
label the media. In Windows NT, the LABEL command
is used to label removable disk cartridges, diskettes and User response: Ensure that the media is not defective,
other media which appear as drive letters. and is properly formatted. Ensure that there are not
large numbers of files already in the root of the file
system. Some file systems have limits on the number of
ANR8781E Volume in drive drive name has invalid files that may be created in the root directory.
label label.
Explanation: The volume in the indicated drive has ANR8785E Out-of-space in file system for device
the label shown. The name does not conform with type volume volume name.
server requirements. The server requires that all media
be uniquely labeled and, for removable media, that the Explanation: The server detected an out-of-space
label with file naming conventions. The label found condition for the file system in which the given volume
exceeded the maximum label size for removable media resides.
or did not conform to server labeling requirements. If System action: The operation fails.
????? is shown for the label, it indicates that server was
unable to read the label. User response: The file system must be expanded to
accommodate volume growth.
System action: The volume is rejected.

barcode reader is configured and is functioning

ANR8786I Request number: Remove device type
properly, if necessary.
volume from entry/exit port; insert
volume volume name mount mode into
entry/exit port of library library name ANR8789W Dynamic drive recovery being attempted
within time limit minute(s); issue 'REPLY' on device type volume volume name due to
along with the request ID when ready. errors.
Explanation: A CHECKIN LIBVOLUME command is Explanation: Due to a drive or media fault, the server
in progress, and the specified volume is needed. is moving the volume to a new drive.
However, there is a volume awaiting to be removed
from the entry/exit port before the specified volume is System action: Read or write operations resume on
inserted into the port of the given library. the volume once it is remounted.
System action: The server waits until a REPLY User response: None.
command is issued.
User response: Remove the volume from the library ANR8790I device type volume volume name
and insert the correct volume into the entry/exit port. re-mounted in drive drive name.
Issue a REPLY command, along with the request ID, to Explanation: Due to a drive or media fault, the server
tell the server that the volume has been removed and a has moved the volume to the specified drive. Read or
new volume has been inserted. write operations resume on the volume.
System action: The label of the volume has been
ANR8787W Unable to read the barcode label(s) in verified.
Explanation: A command is issued with the
CHECKLABEL=BARCODE option. The library is
unable to detect that the cartridges have valid barcode ANR8791E Unable to move device type volume
labels. The barcode reader is disabled or it is unable to volume name to another drive.
read the labels. Explanation: Dynamic drive recovery was being
System action: Unless the command is checking in attempted on the volume, but was unable to move the
cleaning cartridges, the process continues by loading volume to another drive.
the cartridges into the library's drives and reading the System action: The originating process terminates.
label from the tape. Cleaning cartridges have no
internal label that can be checked by loading it in the User response: See previous error messages to
drive. determine the cause of the DDR failure, and correct the
problem. If the problem is an unreadable label, any
User response: Cancel the process if you do not want data on the volume may be lost.
to load all of the cartridges into the library's drives.
Examine the cartridges to ensure they have barcode
labels and they are compatible with the barcode reader. ANR8792E Unrecoverable drive failures on drive
Not all vendors' labels are readable by all libraries. drive name; drive is now marked offline.
Check that the barcode reader is configured and Explanation: The drive has been determined to be
functioning properly, if necessary. faulty because of recurrent failures.
System action: The drive is now marked offline.
ANR8788W Unable to read the barcode of cartridge
in slot-id Element number of slot in library User response: Service the drive for failures. Delete
library name; loading in drive to read and redefine the drive to bring it back online.
label.
Explanation: The library barcode reader is unable to ANR8793E Dynamic drive recovery failed for device
read the label of a tape cartridge. The cartridge is type volume volume name because not
found in the slot with the given element number. enough drives are available.
System action: The cartridge is loaded into a drive Explanation: To recover a volume on another drive,
and its label will be read from the tape. there must be at least one other drive available that is
not associated with the transaction which is driving the
User response: Cancel the process if you do not want recovery. In addition, the maximum number of drives
to load any cartridges into the library's drives. Examine that can have dynamic drive recovery performed at the
the cartridge to ensure it has a barcode label and that it same time is one less than the number of drives. This is
is compatible with the barcode reader. Not all vendors' to prevent deadlock from occurring between two
labels are readable by all libraries. Check that the recovering transactions. One of these criteria has failed.

System action: No DDR is performed and the system logs. Render any needed corrections to the
transaction fails. drive. The drive will be brought online automatically
when the polling process detects that is has become
User response: Restart the transaction.
accessible.
ANR8794E Retry of operation name operation failed

ANR8798W Drive drive name in library library name is
for device type volume volume name.
busy; some transactions may fail.
Explanation: After successfully mounting the volume
Explanation: The drive being made offline is currently
on another drive, due to an I/O error, the original
mounted with an open tape volume. If the transaction
operation fails when retried.
using the volume requires subsequent tape mounts and
System action: No further recovery is performed and is unable to acquire a drive, the transaction will fail.
the transaction fails.
System action: If this tape volume is one of a
User response: Restart the transaction. sequence of volumes that are required to process a
transaction, a drive must be available for each mount.
This may be any drive in the library, but if all other
ANR8795I Retry of operation name operation for library drives are currently busy and are still busy at
device type volume volume name is the time the new tape must be mounted, the
successful. transaction will fail.
Explanation: After mounting the volume on another User response: If possible, make the drive online until
drive, due to an I/O error, the operation is tried the transaction using it ends. If there is an idle volume
successfully. on the drive, dismount the volume first.
System action: The transaction continues from the
point of interruption from the failure. ANR8799I Command: Operation for library library
User response: None. name started as process process ID.
Explanation: A LABEL process has been started to
ANR8796W Drive drive name of library library name is write the label on the specified volume in the given
not online; UPDATE DRIVE required. library. The process is assigned the ID specified in the
message.
Explanation: During the initialization of a library, the
server finds that the drive was updated to be offline. System action: The server starts a background process
to perform the operation in response to the LABEL
System action: The drive will not be accessible by the command entered by an administrator.
library during tape operations.
User response: To obtain status on the process, issue
User response: The drive may be made online by the QUERY PROCESS command. The process may be
issuing the UPDATE DRIVE command with the canceled with the CANCEL PROCESS command.
ONLINE=YES option.
ANR8800I LABEL LIBVOLUME for volume volume

ANR8797W command: Drive drive name of library name in library library name completed
library name is inaccessible. successfully.
Explanation: The server is unable to use the Explanation: The background process to LABEL a
mentioned drive. This may be for the following volume has succeeded.
reasons:
System action: The volume's label has been rewritten.
v The drive cannot be opened.
v In the case of a 3494 or a library that can be User response: None.
partitioned, the drive may be unavailable to the
library manager, may be in use by another ANR8801I LABEL LIBVOLUME process process Id
application, or may be loaded with a cartridge not for library library name completed; count
labeled for server use. of labeled volumes volume(s) labeled, count
System action: The drive is temporarily made offline of checked in volumes volume(s)
and is not used for tape operations. The server polls checked-in.
the drive at one-half minute intervals to check if the Explanation: A search-mode process to LABEL
condition has cleared. Once the drives is accessible volumes has succeeded.
again, the drive is brought online.
System action: The volumes have been labeled.
User response: Determine the reason the drive is
inaccessible, such as hardware errors reported in the User response: None.

ends. The volume is not labeled and is not checked into

ANR8802E LABEL LIBVOLUME process process Id
the library.
for library library name failed.
Explanation: The Label process terminated with a
failure.
and ready, and then reissue the command.
User response: See previous error messages to ANR8807W Could not write label volume name on
determine the cause of the failure, and correct the the volume in drive drive name of library
problem. library name because volume is already
labeled existing volume name.
ANR8803I LABEL VOLUME process process Id for Explanation: The check in or label process could not
library library name has been canceled; write the label on the tape specified because the
count of labeled volumes volume(s) labeled, volume is already labeled.
count of checked in volumes volume(s)
System action: The check in process will not overwrite
checked-in.
volumes that are already labeled, and the label process
Explanation: A background server process that has will only overwrite volumes when OVERWRITE=YES
been working to label the volumes for the given library is specified. The volume is not labeled and cannot be
is canceled by the CANCEL PROCESS command. The checked in to the library. If SEARCH=YES, the process
counts provided are for any volumes processed prior to continues to the next volume. For an individual
the cancel. volume, the process ends.
System action: The server process is ended and server User response: Reissue the command with the correct
operation continues. parameters.
ANR8808E Could not write label label name on the
volume in drive drive name of library
ANR8804I Labeling volume volume name in library
library name because that volume is
library name.
already labeled with volume name which
Explanation: In response to a QUERY PROCESS is still defined in a storage pool or
command, this message displays the status for a volume history.
LABEL process on the server.
Explanation: An attempt was made to overwrite the
System action: The background process continues. label of a volume that is still defined to a storage pool
or is still found in the volume history file. Such a
User response: None. The process may be canceled by volume may still contain valid data.
PROCESS command. System action: The server process is ended and server
ANR8805I Labeling volumes in library library name; User response: It is usually not necessary to re-label
volume count volume(s) labeled. volumes. If the volume must be relabeled, that volume
must first be removed from the storage pool or volume
Explanation: In response to a QUERY PROCESS history file where it is defined.
command, this message displays the status of a LABEL
process with the SEARCH option.
ANR8809I Request number: Please provide the label
System action: The background process continues. name for the volume in slot element slot
User response: None. The process may be canceled by element number of library library name by
an authorized administrator using the CANCEL issuing REPLY n LABEL=xxx within time
PROCESS command. limit minutes, where n is the request ID
and xxx is the desired label name.
ANR8806E Could not write volume label volume Explanation: A LABEL LIBVOLUME command is in
name on the tape in library library name. progress, and the name of the next volume is needed.
Explanation: The Label process could not write the System action: The server waits until a REPLY
label on the tape specified. command is issued.
System action: For a LABEL operation with User response: Issue a REPLY command, along with
SEARCH=YES, the background process continues to the the request ID, and the volume name for the next
next volume. For an individual volume, the process cartridge.

System action: The server continues normal operation.

ANR8810I Volume volume name has been labeled in
library library name. User response: Remove the specified volume from the
library.
Explanation: The Label process with the search option
has found and labeled a volume.
ANR8815I Remove volume Volume name from port
element Port element number of library
User response: None. Library name.
Explanation: LABEL LIBVOLUME has ended for the
ANR8811E Command: The LABELSOURCE specified volume and that volume must be removed
parameter is required when using from the library because either it was not checked in or
SEARCH with this command. there was an error.
Explanation: The LABELSOURCE parameter must be System action: The server continues normal operation.
provided with the given command.
User response: Remove the specified volume from the
System action: The command is not processed. library.
User response: Reissue the command, and provide a
valid LABELSOURCE parameter value. ANR8816E command: Volume Volume name in library
Library name cannot be labeled because
it is currently defined in a storage pool
ANR8812E Command: The SEARCH parameter is
or in the volume history file.
required when using LABELSOURCE
with this command. Explanation: During command command processing, a
volume cannot be used because there is a storage pool
Explanation: When using the LABELSOURCE option
volume defined or a volume in the volume history file
with this command, the SEARCH parameter must be
with this volume name. Such a volume may still
also provided.
contain valid data. Applying the volume name to the
System action: The command is not processed. cartridge can overwrite data and or cause library
inventory corruption. If the volume is in the volume
User response: Reissue the command, and provide a history file, it has been previously used by for an
valid SEARCH parameter value. export, database dump, database backup operation, or
by a library client (as recorded in the volume history).
ANR8813W Unable to read the barcode of cartridge System action: If the SEARCH=YES option was
in slot element Element number of slot in specified, the current volume is skipped and command
library library name. processing continues with the next volume found. If
Explanation: The library barcode reader is unable to SEARCH=NO was specified, command processing
read the label of a tape cartridge. The cartridge is terminates.
found in the slot with the given element number. User response: If the volume is present in an
System action: When LABELSOURCE=BARCODE is automated library, it should either be removed or
specified on the LABEL LIBVOLUME command, checked into the library's inventory in the PRIVATE
volumes without a barcode cannot be labeled. When category.
the VOLRANGE or VOLLIST option is specified on the
CHECKIN LIBVOLUME command, volumes without a ANR8817E Name length for volume "Volume name"
barcode cannot be checked in. invalid; max is Maximum name length.
User response: Examine the cartridge to ensure it has Explanation: During LABEL LIBVOL processing, the
a barcode label and that it is compatible with the volume name provided to be written on the label
barcode reader. Not all vendors' labels are readable by exceeds the maximum length for the type of cartridge.
all libraries. Check that the barcode reader is
configured and is functioning properly, if necessary. System action: The label process fails for that
cartridge.
ANR8814I Remove volume Volume name from slot User response: Reissue the LABEL LIBVOL command
element Slot element number of library and provide a volume name that is not longer than the
Library name. maximum listed.
Explanation: LABEL LIBVOLUME has ended for the
specified volume and that volume must be removed
from the library because either it was not checked in or
there was an error.

User response: Replace the cartridge's barcode with

ANR8818E I/O Error on library library name; request
one that is supported by the library and whose number
for op. operation/function to the 3494
of characters does not exceed the maximum length.
Library Manager has timed out.
Explanation: A command for the operation was issued
ANR8822E 'Volume name' is not a valid volume
to the Library Manager and a response was not
name.
received within the maximum timeout period.
Explanation: The specified string is not a valid
System action: The operation and the transaction fails.
volume name.
User response: Verify that communications with the
System action: The program prompts for a new
library is operational, that it is online and ready for
volume name.
commands. Increase the time-out limit of the Library
Manager Control Point device driver. If the problem User response: Enter a volume name that is within
persists, provide your service representative with the the length constraints for the media type being labeled,
3494 Library Manager transaction logs. and which contains only alphanumeric characters.
ANR8819E Unable to read the barcode label(s) in ANR8823E Hardware configuration error in library
library library name. library name: number of drives drives,
number of storage slots storage slots.
Explanation: A LABEL command was issued with the
LABELSOURCE=BARCODE option. The library was Explanation: The library device returned a count of
unable to detect that the cartridges had valid barcode zero for either the drives or the slots. The drives may
labels or the library did not have a barcode reader. If a have not yet been configured to the operating system,
barcode reader is present the reader might be disabled or to the library. The library must have at least one
or it is unable to read the labels. drive and multiple slots when properly configured in
order to be defined to the server.
System action: Examine the cartridges to ensure they
have barcode labels and they are compatible with the System action: The operation fails.
barcode reader. Not all vendors' labels are readable by
all libraries. Check that the barcode reader is User response: Configure the drives to the operating
configured and functioning properly. system, and reinitialize the library.

ANR8824E I/O Error on library library name; request
request id for operation operation/function
ANR8820W Repairing VCR data for Volume volume to the 3494 Library Manager been lost.
name in drive drive name; dismount may
be delayed. Explanation: A command for the operation was issued
to the Library Manager and a response was not
Explanation: The Vital Cartridge Records of the received within the maximum timeout period.
cartridge in the drive are lost or corrupted, which
results in the inability of the drive to do fast locates to System action: The operation and the transaction fails.
file positions on the cartridge. The VCR is being rebuilt User response: Verify that communications with the
during the volume dismount process in order to avoid library is operational, that it is online and ready for
performance degradation on future mounts of the commands. If the problem persists, provide your
volume. service representative with the 3494 Library Manager
System action: The server continues the dismount transaction logs and the request id from the failed
operation. There may be a long delay because the VCR operation.
is rebuilt by spacing the tape forward to the
end-of-data. ANR8825E 'Volume range' is not a valid volume
User response: None. range.
Explanation: The specified string is not a valid
ANR8821E Barcode of element slot element address, volume range.
'hardware barcode string', exceeds maximum System action: The program prompts for a new
length characters in length. volume range.
Explanation: A barcode is encountered that was User response: Enter the volume names in the range
longer than a valid volume name. that is within the length constraints for the media type
System action: The barcode is not considered valid being labeled, and which contains only alphanumeric
and will not be used for the server process. characters. The volume names of the beginning and
ending volume must be the same in length and the

incrementals must be in digits. User response: Check system error logs for entries
made by the device relative to media errors. It is
recommended to move the data off the volume in order
ANR8826E No Entry/Exit found on library library
to minimize the impact of future errors and further
name.
damage to the media.
Explanation: A CHECKIN LIBVOLUME
SEARCH=BULK command was issued on a library that
ANR8831W Because of media errors for volume
has no Entry/Exit ports.
Volume name, data should be removed as
System action: None. soon as possible.
User response: None. Explanation: Errors previously encountered on the

volume leave the access to the data in a questionable
state. The errors may be permanent temporary media
ANR8827E No Entry/Exit port is available on failures such as the corruption of the Volume Control
library library name. Region of a Magstar drive.
Explanation: A CHECKOUT LIBVOL command was System action: None.
issued on a library where all its Entry/Exit Ports were
found to be full or inaccessible. User response: Move the data off the volume. This
can be done with the MOVE DATA command. In some
System action: None. cases the tape is reusable by returning it to scratch.
User response: Empty all the entry/exit ports on the Check system error logs for entries made by the device
library, close the entry/exit port door, make sure the relative to media errors. If the errors cannot be isolated
ports are accessible, and try the command again. ore resolved, contact your support representative.
Return the tape to scratch or dispose of it.
ANR8828E Slot element number of library library

name is inaccessible. ANR8832E CHECKIN LIBVOLUME for volumes in
search mode in library library name
Explanation: The slot in the library could not be failed.
physically accessed at this time.
Explanation: The background process for a CHECKIN
System action: None. LIBVOLUME command has failed.
User response: Verify that the Entry/Exit door is System action: The background process ends, but
closed and the device has not logged any device errors volumes have not been checked into the library.
before trying the command again.
ANR8829I Remove volume volume name from slot and ready, and then reissue the command.
element number of library library name at
your convenience.
Explanation: A volume has been checked out from the library name is currently being checked
library and placed in a multiple entry/exit port library. in or checked out.
The volume needs to be removed from the library, but
the operation is not critical. Explanation: The command cannot be processed
because the specified volume is being checked in or
System action: None. checked out of the library.
User response: Remove the volume from the System action: The command is not processed.
entry/exit slot.
User response: Wait until the conflicting checkin or
checkout has completed, and then reissue the
ANR8830E Internal Device type drive diagnostics command.
detect excessive media failures for
volume Volume name (MIM MIM Code).
Access mode is now set to "read-only". ANR8834E Library volume volume name is still
present in library library name drive drive
Explanation: The tape drive's microcode performed an name, and must be removed manually.
analysis of the media during the prior mount of the
volume and determined that the number of temporary Explanation: Library operations cannot be performed
errors and other indicators exceed the threshold for using the drive because a volume is still mounted in it.
reliable data recording. This may be due to a prior dismount failure that
occurred on the drive.
System action: The volume is made read-only.

System action: The command fails. The drive may be

ANR8838E I/O error on drive drive name: excessive
taken offline.
unit attentions received from device.
User response: See previous error messages and the
Explanation: An operation to the drive failed with a
system error logs to determine the cause of the
device unit attention. These are normally cleared when
dismount failure or any other reason the volume would
the operation is retried, but in this case subsequent
still be loaded in the drive. Hardware diagnostics may
recover and retry attempts persistently fail with unit
be required. If necessary, remove the volume manually
attention. This indicates a device failure.
and place it in its storage cell. If the storage cell is
unknown, place the volume in any cell and issue the System action: The operation fails.
AUDIT LIBRARY command. Use the QUERY DRIVE
User response: See accompanying error messages and
command to determine the online status of the drive. If
the system error logs to determine any reason for the
the drive is still functioning, change the status with the
drive failure. Hardware diagnostics may be required. It
UPDATE DRIVE command.
may be necessary to manually unload the volume and
mark the drive offline with the UPDATE DRIVE
ANR8835W Error returning volume volume name to command.
scratch.
Explanation: The server external library manager sent ANR8839W Drive drive name of library library name is
a RELEASE request to the external agent for the named accessible.
volume, but the external agent was unable comply with
Explanation: The server is now able to use the
the request. The server, however, marked the volume
mentioned drive that was inaccessible. However, the
scratched in its inventory; consequently, the server
administrator has marked the drive offline while the
inventory and the external agent inventory are not
drive was being polled.
consistent. This message is issued to inform the
customer that the external agent inventory must be System action: The drive is left offline and is not used
made consistent with the server inventory using the for tape operations.
facilities of the external agent.
User response: Issue the UPDATE DRIVE command
System action: The server has returned the volume to to bring the drive back online.
scratch status.
User response: Consult the documentation for the ANR8840E Unable to open device device name with
external agent and take the appropriate action to make error number error number and PVRRC
the agent inventory consistent with the server return code.
inventory.
Explanation: The library is not accessible. As a result,
an open request failed. This in turn causes the pending
ANR8836E Function RSM_function failed in request to fail.
server_function processing, return return
code, call call number. System action: A drive is marked inaccessible. The
server polls the drive to determine if both the library
Explanation: The library function that uses the API to and drive are inaccessible. In most case, the library had
the Windows NT Removable Storage Manager failed a temporary failure and recovers. When the server
with a return code from the API. The call number determines that the library is available, the drive is
represents the exact API call issued in the program. brought back on-line.
System action: The function fails. User response: Use the error number in conjunction
with operating system documentation to narrow the
User response: Use the RSM documentation to
scope of the cause. Inspect the library. Ensure that the
determine the source of the problem.
library is powered on and ready, that the cables are
properly connected, and that the device is properly
ANR8837E RSM Library Library Name not supported configured to the system.
on this Windows platform.
Explanation: The libtype=RSM was used on a ANR8841I Remove volume from slot element number
Windows platform that does not support RSM. of library library name at your
convenience.
System action: The function fails.
Explanation: A volume has been placed in a multiple
User response: Use another library type to define the
entry/exit port library because the volume should be
library.
placed back in the entry/exit port as result of the
successful completion of a server command, or there
was a problem during a server command. The volume

needs to be removed from the library, but the operation properly connected and terminated, and the device is
is not critical. properly configured to the operating system.
ANR8845E Loadable module module name is
User response: Remove the volume from the
required for remote operation.
entry/exit slot. Examine previous messages for
additional information regarding the specified volume Explanation: The indicated loadable module is
and the command. required by the server to perform an operation on a
remote drive or library, but the module has not loaded.
Message ANR4726I is issued during server initialization
ANR8842E The Device type drive detected a
when the module is loaded.
marginal sector and could not reallocate
the sector for volume Volume name. System action: The remote operation fails.
Access mode is now set to "read-only".
User response: Check the server activity log for
Explanation: The optical drive detected a marginal message ANR4726I, indicating if the module was
sector (media error) while reading the volume. The loaded. If you see this message during server
drive read the sector successfully but could not initialization for this module, please contact your
reallocate the sector because of a previous media error. service representative. If you do not see this message,
make sure the loadable module has not been delete, or
System action: The volume is made read-only.
User response: Check system error logs for entries
made by the device relative to media errors. It is
ANR8846E Volume volume name is assigned to a
recommended to move the data off the volume in order
category that does not belong to library
to minimize the impact of future errors and further
library name.
damage to the media.
Explanation: The attempted operation on the volume
cannot proceed because it is assigned to a category
other than the insert, private, or scratch category used
library library name - the library will be
by the library.
inaccessible.
System action: The attempted operation is terminated.
library has failed. The server is unable to use the User response: Use the mtlib utility to query the
library. This may be for the following reasons: volume's category. If the volume is not in use by
v The library is defined without a path. another library, use mtlib to reassign the category or
choose another volume that is assigned to the proper
v The device for the library is removed by a DELETE
category.
PATH command.
v The data mover controlling the library is offline.
ANR8847E No device type type drives are currently
v The path to the library is offline.
available in library library name.
System action: The library is made offline and will
Explanation: The attempted operation cannot be
not be used for any library operations.
completed on the specified library because there are no
User response: Determine the reason the library is available drives of the specified type. A drive may be
inaccessible. Render any needed corrections to the unavailable because a different application has the
library, shut down the server, and re-bring up the drive opened. This message may also be issued if a
server so that the library can be completely initialized. CHECKIN or LABEL command is issued and no drive
is available to service the operation. This can be
because all the drives are mounted by other processes
ANR8844E Unable to open remote drive drive name, or sessions, or the device type was incorrectly specified.
error code=error value from server plugin. This can also be issued when incorrect barcode labels
Explanation: The indicated remote drive cannot be are placed on the wrong type of media (e.g. LTO2
opened by the server. The error code displayed is the barcode label on an LTO1 cartridge).
return code from server plugin routine. System action: The attempted operation is terminated.
System action: The transaction needing the drive fails. User response: Use the QUERY DRIVE command to
User response: Use the return code displayed to check the online status of the drives. Drives that are
determine the cause of the open failure or any other marked "Unavailable since hh:mm yy/mm/dd" are
reason the drive cannot be opened. Hardware drives taken offline by the server at the time specified
diagnostics may be required. Inspect the drive. Ensure because of hardware failures or the inability to open
that the drive is powered on and ready, the cables are the drive. If the attempted operation is a CHECKIN or
LABEL command, use the QUERY MOUNT command

to determine if all the drives in the library are mounted

ANR8851E Initialization failed for ACSLS library
and wait until one of these is available. If there are
library name; will retry in delay time
mounted volumes with an IDLE status, use the
minute(s).
DISMOUNT VOLUME command to free its drive, and
retry the original operation. Finally, the DEVTYPE Explanation: The initialization process for the given
parameter is required for CHECKIN and LABEL library has failed. It is retried automatically after the
commands specifying 3590 volumes in a 349X library specified amount of time has elapsed.
that also contains 3490 drives. This is because this
library also supports 3490 volumes, and the default
device type on CHECKIN and LABEL commands is User response: Ensure that the library device is
CART (3490). powered on and ready.
ANR8848W Drive drive name of library library name is ANR8852E Initialization failed for ACSLS library
inaccessible; server has begun polling library name.
drive.
Explanation: The server is unable to use the library has failed and will not be retried until the next
mentioned drive. This may be for the following time the server needs to access the library.
reasons:
System action: The library is made temporarily
v The drive cannot be opened unavailable.
v In the case of a 3494 or a library that can be
partitioned, the drive may be unavailable to the User response: None.
library manager, may be in use by another
application, or may be loaded with a cartridge not ANR8853E Incompatible options
labeled for server use. CHECKLABEL=NO and SEARCH=YES
System action: The drive is temporarily made offline for ACSLS libraries.
and is not used for tape operations. The server polls Explanation: The CHECKLABEL=NO and
the drive at one-half minute intervals to check if the SEARCH=YES parameters on the CHECKIN LIBVOL
condition has cleared. Once the drives is accessible command are not compatible.
again, the drive is brought online.
User response: Determine the reason the drive is
inaccessible, such as hardware errors reported in the User response: Reissue the CHECKIN LIBVOL
system logs. Render any needed corrections to the command and specify CHECKLABEL=YES.
drive. The drive will be brought online automatically
when the polling process detects that is has become ANR8854E ACSAPI(command name) invocation
accessible. failed, status= acs status.
Explanation: The ACSLS library API invocation for
ANR8849E Command: There is already a request to the given command failed.
delete drive drive name.
System action: Depends on the server function and
Explanation: The designated drive cannot be deleted command, library may be unavailable.
or updated because there is a request to delete the
drive already. User response: Contact your ACS System
Administrator and perform ACSLS library problem
System action: The command is not processed. determination.
ANR8855E ACSAPI(command name) response with
ANR8850I ACSLS library library name is ready for unsuccessful status, status=acs status.
operations. Explanation: The ACSLS library API responded with
Explanation: The initialization process for the given an unsuccessful status as indicated.
library has completed successfully, and the library is System action: Depends on the server function and
ready for use. command, library may be unavailable.
System action: The library is made ready for use. User response: If the status indicates
User response: None. STATUS_CAP_IN_USE, it might be CAP priorities not
set to non-zero. It might also be CAPs are not set to
automatic mode, or CAPs are in manual mode during
manual checkin. If CAP mode and priorities are set

correctly, contact your ACS System Administrator and

ANR8860W Volume volume id is already locked by
perform ACSLS library problem determination.
user id.
Explanation: The specified volume is already locked
ANR8856E ACSAPI sequence(sequence number)
by other user or has a different lock id.
request (request number) timed out,
elapse time=hours: minutes:seconds. System action: Depends on the function, the volume
maybe bypassed or the process maybe terminated.
Explanation: The ACSLS client has received no
response from the ACSLS server for the period as User response: This may not be an error in a shared
indicated in the elapsed time. The ACSLS library API configuration. However, if the existing volume lock is
function with the associated sequence number is not needed. contact your ACSLS system administrator
canceled if the request number is non-zero. to clear the lock the volume.
command, library may be unavailable. ANR8861I Wait and monitor the ACSSA console
message to remove volume volume id
User response: Contact your ACS System
from CAP.
Administrator and perform ACSLS library problem
determination. Explanation: The specified volume is about to put into
CAP for removal. Monitor the ACSSA console and
removed the volume after it has been placed into the
ANR8857I ACS access control set to user_id - user
CAP as indicated in the ACSSA message.
id, status= acs status.
Explanation: The ACSLS ACCESSID structure for
command and volume access control is set the user_id User response: Monitor the ACSSA console and wait.
as indicated.
System action: None. ANR8862I Unable to access ACS volume volume id.
User response: Ensure the indicated user_id is the Explanation: The specified ACSLS volume can not be
same as specified in the environment variable accessed in the library. The possible reasons might be
ACSAPI_USER_ID. the volume is in use, the user is not authorized, the
volume does not exist in the library.
ANR8858W Unable to lock drive drive id,drive id, System action: Depends on the server function and
drive id,drive id, status= acs status. command, library volume is unavailable.
Explanation: The ACSLS library function User response: Contact your ACS System
acs_lock_drive failed for the specified drive. Administrator and perform ACSLS library problem
determination if the problem persist..
command, library drive may be unavailable. or may be
temporary unavailable in a shared library environment. ANR8863I Unlocking library library name volumes
from the ACSLS server.
User response: Contact your ACS System
Administrator and perform ACSLS library problem Explanation: The volumes of the specified library are
determination if the problem persists. being unlocked from the ACSLS server.
System action: The operation continues. The process
ANR8859W Unable to lock volume volume id, status= may take a while depends on the number of volumes
acs status. in the library.
Explanation: The ACSLS library function User response: None.
acs_lock_volume failed for the specified volume.
System action: Depends on the server function and ANR8864I ACSLS library library name is being
command, library volume is unavailable. re-initialized.
User response: Contact your ACS System Explanation: The specified ACSLS library is being
Administrator and perform ACSLS library problem re-initialized.
determination if the problem persist.
System action: The operation continues. The process
may take a while depends on the number of volumes
in the library. All volumes in the library are being
locked.

library. If there is path defined to the library, make sure

ANR8865W Volume volume name bypassed for
the path is online and the source entity of the path is
command, status=acs_status.
also online.
Explanation: The specified volume is bypassed. The
volume is not in a valid status for the specified
ANR8871I The device name device name specified
function.
has been changed to device name.
Explanation: The specified device name on the
User response: Determine the volume status from the DEFINE PATH or UPDATE PATH command has been
ACSSA and re-issue the command if necessary. changed to recommended device name.
ANR8866E Incompatible option REMOVE=BULK
for ACSLS libraries.
Explanation: The REMOVE=BULK option is not
ANR8872E No path is available for drive drive name
supported for ACSLS libraries. The final response of
- could not unload volume volume name
ACSAPI acs_eject does not return to the application
from drive.
until the volume is removed from CAP.
Explanation: There is no path to the given drive or
the path to the drive is offline or the source of the path
User response: Reissue the CHECKOUT LIBVOL to the drive is offline. The indicated volume may be
command and specify REMOVE=YES or NO. still on the drive.
System action: The drive is inaccessible.
ANR8867I Processing volume volume id for the
User response: Ensure that a path is defined to the
command command.
drive. If there is a path defined to the drive, make sure
Explanation: The specified volume is being processed that the path is online and that the source of the path is
for the specified command. also online. Run the AUDIT LIBRARY command after
the problem is corrected.
ANR8873E The path from source source name to
destination drive name is taken offline.
ANR8868E Ejecting Volume volume name Failed,
Explanation: There is problem using the indicated
status = acs_status .
path. The path is now marked offline.
Explanation: The volume is failed to be ejected from
System action: The path is inaccessible.
the library due to the status as indicated
User response: Determine the reason the path is
inaccessible, such as hardware problem. Render any
User response: Determine the volume status from the needed corrections. Then, the path may be made online
message and do something as needed by issuing the UPDATE PATH command with the
ONLINE=YES option.
ANR8869E Command: There is already a request to

update drive drive name. ANR8874E The type of device used by the media in
element element number of library library
Explanation: The designated drive cannot be deleted name cannot be determined by the
because there is a request to update the drive already. hardware. Volume is not processed.
System action: The command is not processed. Explanation: The library's mechanism for determining
User response: None. the type of media in a slot or EE port failed. This is
usually the barcode reader or some other sensor that is
part of the robotics.
ANR8870E The path to the library library name is
unavailable. System action: The volume is skipped by the process.
Explanation: There is no path to the given library, or User response: Determine the reason the library could
the path to the library is offline, or the source entity of not determine the media type, such as deteriorated
the path to the library is offline. barcode, scanner failure, or other hardware problem as
determined by system engineer. If the barcode label is
System action: The library is inaccessible. replaced on a private volume containing data, it must
User response: Ensure that a path is defined to the be with a label having the volume name. Scratch

volumes or empty private volumes can be replaced

ANR8878E Failed to close the remote library library
with any barcode but they must be re-labeled if the
name (device name).
barcode name changes.
Explanation: An attempt to close a remote Library
device attached to a NAS File Server failed.
ANR8875E An illegal move was attempted
involving the media in element element System action: The operation fails.
number of library library name. Its type is
User response: Examine previous messages for
incompatible with the destination
additional information regarding the specified library.
element element number.
Explanation: The server tried to move one type of
ANR8879E Failed to close the SCSI session for the
volume into a drive or slot of another type that is
remote library library name(device name).
incompatible. This is most likely because another
volume has taken its slot, or the server's information Explanation: An attempt to close a SCSI session for a
for this volume has otherwise been corrupted. remote Library device attached to a NAS File Server
failed.
System action: The process fails.
User response: Issue the AUDIT LIBRARY command,
and retry the operation. User response: Examine previous messages for
additional information regarding the specified library.
ANR8876E The media in element element number of
library library name is a cleaner. ANR8880W Device type of drive Drive name in
library Library name was determined to
Explanation: The library hardware has determined
be GENERIC_TAPE.
that the media in the stated slot is a cleaner cartridge.
It cannot be processed by the CHECKIN command Explanation: The device type of a drive is determined
without the STATUS=CLEANER parameter, and it when the path for that drive is defined. If the wrong
cannot be labeled by the LABEL command. device file was used in the device parameter of
DEFINE PATH the device type of the drive will often
System action: The process skips the media, or if it is
be GENERIC_TAPE. If you are using the or the IBM
the only media being processed the process fails.
tape device driver, then you should not have a device
User response: Issue the AUDIT LIBRARY command, type of GENERIC_TAPE. You should only have a
and retry the operation. device type of GENERIC_TAPE if you are using the
native OS device driver.
ANR8877E Volume volume name is incompatible System action: None.
type with device class devclass name in
User response: Verify that GENERIC_TAPE is the
desired device type for this drive. While the device
Explanation: An attempt has been made to service a type GENERIC_TAPE is valid, it is often a mistake, and
mount request, but the attempt fails because the media thus, should be verified that it is the intended device
type of the cartridge being mounted is not compatible type. If GENERIC_TAPE is not the intended device
with the devclass requesting the mount. This is usually type, all paths for this drive and the drive itself will
a conflict between WORM and Read-Write have to be deleted and redefined.
characteristics.
System action: The operation fails. ANR8881W Insufficient space for new volume in
directory directory for device class device
User response: If this is not a 3592 device or media,
class name.
The volume was probably not checked in with the
CHECKLABEL=YES parameter of the CHECKIN Explanation: The server found that the indicated
command. Check the volume out (the REMOVE=NO directory had insufficient space in which to create a
may be useful) and check the volume back into the new volume.
library with this parameter to ensure that the
System action: Other directories available to the
mediatype is determined and saved. If this is a 3592
device class are used, if any. If no directories with
device or media, the volume probably has an incorrect
space are available, the operation fails. This message is
barcode label indicating that it had the wrong WORM
issued periodically as requests are made for space in
property. The label needs to be swapped for the
this directory.
opposite WORM type (e.g. WORM to non-WORM or
non-WORM to WORM) or simply removed entirely User response: The file system must be expanded to
from the library. accommodate volume growth.

User response: Verify that GENERICTAPE is the

ANR8882I Request number: Please provide the label
desired device type for this drive. While the
name for the volume in drive drive name
GENERICTAPE device type is valid, it is not
of library library name by issuing REPLY
recommended for a tape drive that is supported by the
n LABEL=xxx within time limit minutes,
IBM Spectrum Protect server. If GENERICTAPE is not
where n is the request ID and xxx is the
the intended device type, delete all paths to this drive
desired label name.
and delete the drive itself. Then redefine the drive and
Explanation: A mount is in progress with a path without specifying GENERICTAPE=Yes.
AUTOLABEL, and the name of the volume is needed.
System action: The server waits until a REPLY ANR8886E Element address mismatch: Element
command is issued. element number of library library name is
reported by the library to be element
User response: Issue a REPLY command, along with
element number.
the request ID, and the volume name for the cartridge.
Explanation: The library configuration appears to
have changed. Verify that no other management
ANR8883W The volume volume name in slot element
interfaces are modifying the library inventory.
number is in the library library name but
not in the IBM Spectrum Protect's System action: None.
inventory database. Please either check
User response: Examine previous messages for
in this volume or remove it from the
additional information regarding the specified volume
library.
and the command that was issued. Retry the operation.
Explanation: . It may be necessary to audit the library using the
AUDIT LIBRARY command
System action: .
User response: The Audit Library command found
ANR8887E Volume volume name in the drive drive
this volume in this library but they are not in IBM
name has incompatible block size.
Spectrum Protect's inventory database. This volume can
be either checked in or removed from this library. Explanation: The drive cannot read the label or data
from the volume. This issue can be attributed to a
different data block size set to this volume.
ANR8884W Attempted to label a written WORM
medium in the drive drive name with System action: The operation fails.
volume volume name (OP=internal code,
User response: If this issue appears during the tape
Error Number=internal code, CC=internal
label operation, this tape might be already labeled by
code, KEY=internal code, ASC=internal
the third-party application. In this case, this error can
code, ASCQ=internal code,
be ignored. If this issue appears during a normal read
SENSE=sense data,
data operation, check the tape device driver and ensure
that the correct version of the device driver is installed.
documentation on I/O error code
descriptions. ANR8888W The persistent reserve key for the device
drive name with the serial number drive
Explanation: An I/O error has occurred while labeling
serial numberis cleared.
on the written WORM medium.
Explanation: The server is unable to preempt this
device with the persistent key of the IBM Spectrum
User response: Ensure the WORM medium in the Protect server. Therefore, the server clears this key,
drive is not a written WROM medium. which is set to this device.
System action: N/A
ANR8885W The device type of drive Device Name is
User response: Check the SAN configuration, ensure
determined to be GENERICTAPE.
that this device is used by the IBM Spectrum Protect
Explanation: You have specified GENERICTAPE=Yes server.
when defining a path to this drive. The tape drive is
supported and we recommend using with the IBM
ANR8901E Command: Incompatible options
Spectrum Protect tape format instead of the generic
STATUS=CLEANER and
tape format. To use the IBM Spectrum Protect tape
CHECKLABEL=YES.
format, do not specify GENERICTAPE=Yes when
defining a path to the drive. Explanation: Cleaner cartridges do not have internal

labels that can be checked by loading them into the

ANR8905I CLEAN DRIVE process for drive drive
drive.
name in library library name is been
System action: The command fails. canceled.
User response: Reissue the CHECKIN LIBVOL Explanation: A background server process is has been
command and include the parameter, working to clean the specified drive and is canceled by
CHECKLABEL=BARCODE (with SEARCH=YES the CANCEL PROCESS command.
specified), or include the parameter
System action: The cleaning process is ended.
CHECKLABEL=NO (with the required volume name
specified in the CHECKIN command). User response: None.
ANR8902W Unable to read the barcode of cleaner ANR8906I Cleaning drive drive name in library
cartridge in slot-id Element number of slot library name.
in library library name; cleaner not
checked in.
Explanation: The library barcode reader is unable to CLEAN DRIVE process on the server. The given
read the label of a cartridge that is checked in as a volume is being checked in to the designated library.
cleaner. The cartridge is found in the slot with the
given element number.
continues. The process may be canceled by an
System action: The cartridge is not checked in. If the authorized administrator using the CANCEL PROCESS
library is being searched, the checkin process continues command.
with the next volume.
User response: Examine the cartridge to ensure it has an authorized administrator using the CANCEL
a barcode label and that it is compatible with the PROCESS command.
barcode reader. Not all vendors' labels are readable by
all libraries. Check that the barcode reader is
ANR8907E CLEAN DRIVE for drive drive name in
configured and is functioning properly. The cleaner
library library name failed.
cartridge can be checked in without use of the barcode
label by issuing the CHECKIN LIBVOL command. Explanation: The background process for a CLEAN
DRIVE fails.
ANR8903E Command: Missing CLEANINGS System action: The background process ends, but the
parameter for cleaner cartridge checkin. drive is not cleaned.
Explanation: When checking in a cleaner cartridge, the User response: Make sure the library and drive
CLEANINGS parameter is required. devices associated with this command are powered on
and ready. Reissue the command.
User response: Reissue the CHECKIN LIBVOL
ANR8908I CLEAN DRIVE for drive drive name in
command and specify a value for the CLEANINGS
library library name completed
parameter which is used to determine the number of
successfully.
times a cleaner can be mounted to clean a drive.
Explanation: The specified drive is successfully
cleaned in the library during processing of a CLEAN
ANR8904I Command: Cleaning operation for drive
DRIVE command.
drive name in library library name started
as process process ID. System action: The drive is available for normal
library operations.
Explanation: A command-driven process is started to
clean the specified drive. The process is assigned the ID User response: None.
that is in the message.
System action: In response to the CLEAN DRIVE ANR8909I Cleaning drive drive name in library
command that is issued by an administrator, the server library name- CANCEL PENDING.
starts a background process to perform the operation.
User response: To obtain status on the process, issue command, this message displays the status for a
the QUERY PROCESS command. The process may be CLEAN DRIVE process on the server.
System action: The background process operation is
terminated.


ANR8913I Drive drive name in library library name is
currently busy; Cleaning flag is set and
ANR8910I No cleaner, or no cleaner with cleanings will be cleared when the drive has been
left, found in library library name. successfully cleaned.
Explanation: A drive is selected to be loaded with a Explanation: A background process to clean the drive
cleaner cartridge, but no cleaner, or cleaner with is unable to acquire the drive because the drive is busy.
cleanings left, is found in the library's inventory.
System action: The drive is available for normal completes. The drive cleaning flag is set and will be
library operations. cleaned.
User response: A cleaner should be checked in to the User response: None.

library by issuing the CHECKIN LIBVOL command.
ANR8914I Drive drive name in library library name
ANR8911W The cartridge in storage element slot needs to be cleaned.
element address in library library name is
Explanation: The drive has returned indicating to the
not a cleaner cartridge as was expected.
server that it needs to be cleaned.
Explanation: The cartridge is listed in the library's
System action: The server marks the drive to be
inventory with a cleaner volume status. After loading
cleaned. If the drive is enabled for server-managed
the cartridge in the specified storage cell into a drive
cleaning, and a cleaner cartridge is checked into the
for cleaning, it is determined that it is not a cleaner
library, the server will load the cleaner into the drive
cartridge.
after the current volume is dismounted. See the
System action: The drive is available for normal DEFINE DRIVE and QUERY DRIVE commands for
library operations. information on enabling server-managed cleaning. See
the CHECKIN LIBVOL command for checking a
User response: Verify all other cleaner cartridges are cleaner into the library.
in the correct storage cells. Issue the QUERY
LIBVOLUME command to obtain the storage cells of all User response: None.
the cartridges currently checked into IBM Spectrum
Protect. The cartridge should be checked out of the
ANR8915I Cleaning cartridge cleaner name in library
library by issuing the CHECKOUT LIBVOL command
library name is near end of life; has
if the cartridge is still listed in the library's inventory
cleanings left uses left.
with a cleaner volume status. If necessary a cleaner
cartridge should be checked in to replace it. Explanation: A cleaner cartridge is found and used,
but its number of uses it has left is nearly exhausted.
ANR8912E Unable to verify the label of volume System action: The cleaning operation continues.
from slot-element element-address in drive
User response: As the cleaner is used, monitor the
drive name in library library name.
number of cleanings that remain with the QUERY
Explanation: The volume from the slot that is LIBVOL command. Remove the cleaner when all
identified by the element address is loaded into a drive. cleanings are exhausted. A new cleaner may be checked
The drive cannot be opened following the load. The in so that the library is not left without a useful cleaner
label cannot be read to process the volume. when the old cleaner is exhausted.
System action: The volume is stored, and processing
continues with the next available slot. ANR8916I Drivemapping for drive Drive name in
library library name on storage agent
User response: Check the system error logs for errors
storage agent name defined.
reported by the drive that are related to this volume.
Make sure that the cartridge is not a cleaner cartridge Explanation: A drive mapping has been successfully
that would have been loaded by mistake. If the defined for the specified drive.
cartridge is a cleaner, issue the QUERY LIBVOL
System action: The drivemapping is defined and
command to get the correct storage slot for the cleaner
recorded in the database.
and move the cleaner to that slot. If the cleaner is not
in the library's inventory, use the CHECKIN LIBVOL to User response: None.
check the cleaner in. During Audit Library, remove the
bad volume from the reported slot and run Audit
Library again.

User response: Since the polling thread did not start,

ANR8917I Drive mapping for drive Drive name in
the user must restart the server in order for library
sharing to correctly work. Failure to restart the server
storage agent name updated.
and get these polling services running can cause
Explanation: An UPDATE DRIVEMAPPING request unusual results for library clients.
has been successfully processed for the given drive.
System action: The server updates its information ANR8922I A device class for library library name
about the drive mapping. was not found.
User response: None. Explanation: A library client request a mount
operation to be performed by the library manager. The
library manager is missing a device class definition for
ANR8918I Drive mapping for drive Drive name in
that library.
storage agent name deleted. System action: None.
Explanation: The drive mapping for the specified User response: Define a device class for the library
storage agent, library, and drive has been deleted using the DEFINE DEVCLASS command.
successfully.
System action: The drive mapping is deleted. ANR8923I Dismount failed because drive drive
name in library library name is not
currently owned by drive owner name.
Explanation: A library client attempted to dismount a
ANR8919I Initialization and recovery has started
drive that was not currently owned by the library
for shared library library name.
client.
Explanation: The shared library has started to
initialize or recover to resynchronize the library
manager and library client. User response: None.
ANR8925W Drive drive name in library library name
User response: This process should resynchronize all
has not been confirmed for use by
of the drives that are currently being used by this
server server name for over elapsed time
library client. This process might also start after a
seconds. Drive will be reclaimed for use
communication error or if the library client has not
by others.
been able to verify drive status with the library
manager. Explanation: The library server was unable to contact
the library client for the given interval to verify that the
library client is still using the drive. At this point the
ANR8920I Initialization and recovery has ended for
error recovery logic of the library manager will reclaim
shared library library name.
the drive (including dismounting the client's volume if
Explanation: Initialization or recovery has ended the possible) and allow other to use the drive.
library manager and library client should be
synchronized.
User response: Verify that the library client with the
above server name is still running. Verify that the
User response: The drives previously owned by the sessions have not been disabled and the network is still
library client should now indicate they are free on the working between the two host machines. Verify that
library manager. Verify this with the QUERY DRIVE the server definition (QUERY SERVER) on both the
command on the library manager. If ownership of the library manger and the library client are correct.
drives is still in question restart the library client and
library manager.
ANR8926W An Error was encountered while
confirming the use of drive drive name in
ANR8921E Unable to start library polling thread. shared library library name.
Explanation: Library sharing requires that this polling Explanation: The library client was unable to confirm
thread starts. This thread keeps the library manager the usage of the drive to the with the library manager.
and library client synchronized with regards to drive
ownership. These thread are started when the library is
defined or when the server is first initialized. User response: Verify that the sessions have not been
disabled and the network is still working between the

two host machines. Verify that the server definition Explanation: When a shared device class is created or
(QUERY SERVER) on both the library manger and the updated, an attempt is made to define additional file
library client are correct. drives in the associated library up to the mount limit, if
the number of drives is less than the mount limit. One
or more failures occurred in defining additional drives.
ANR8927W This library client has been unable to
The number of drives does not correspond to the
contact the library manager for elapsed
mount limit for the associated device class. This can
time seconds. Releasing ownership of all
cause resource balancing problems between the server
drives in the shared library library name.
and storage agents.
Explanation: The library client was unable to confirm
System action: The server continues operation.
the usage of the drive with the library manager. The
library client will now dismount all volumes that it User response: Use the QUERY DRIVE command to
currently owns. get the names of the drives associated with the library.
Use the QUERY DEVCLASS deviceclass F=D command
to find the mount limit of the associated device class.
User response: Verify that the sessions have not been Use the DEFINE DRIVE command along with the
disabled and the network is still working between the DEFINE PATH command for this new drive with
two host machines. Verify that the server definition DEVICE=FILE to define additional drives in the file
(QUERY SERVER) on both the library manger and the library to match the mountlimit of the associated device
library client are correct. class.
ANR8928W Library library name specified for shared ANR8931W An attempt to delete drives to delete
file device class device class name was not drives failed for library library name. The
defined as shared. The device class will device class has a mount limit of mount
not be shareable unless the library is limit but the number of drives in the
updated. associated library is greater than the
mount limit.
Explanation: A pre-existing library was specified for a
new shared file device class. However, files in the Explanation: When a shared device class is updated
device class cannot be shared unless the library is also and the number of drives in the associated library is
shared. greater than the mount limit of the device class, an
attempt is made to delete drives so that there are as
System action: None. many drives as the mount limit. One or more failures
User response: Issue the UPDATE LIBRARY libname occurred in deleting drives. The number of drives does
SHARED=YES command to make the library shared. not correspond to the mount limit for the associated
device class. This can cause resource balancing
problems between the server and storage agents.
ANR8929E Library library name specified for shared
file device class device class name was not System action: The server continues operation.
defined as a FILE library. User response: Use the QUERY DRIVE command to
Explanation: A pre-existing library was specified for a get the names of the drives associated with the library.
new shared file device class. However, the existing Use the QUERY DEVCLASS deviceclass F=D command
library was not created with the LIBTYPE=FILE to find the mount limit of the associated device class.
parameter. Use the DELETE DRIVE command to delete drives
until the number of drives in the library corresponds to
System action: None. The device class is not created. the device class's mount limit.
User response: Specify a library name that was
created with the LIBTYPE=FILE and SHARED=YES ANR8932W The drive map for server servername,
parameters, or specify a library name which does not library library name, drive name drive
exist, in which case, the library will be created. You can name has directory directory which is
also not specify the LIBRARY parameter, a library name different than other drive maps for
will be created. drives within the same library.
Explanation: A shared file was about to be created. In
ANR8930W An attempt to define drives to create doing so, it was determined that there are differing
drives failed for library library name. The definitions for the directories associated with the drive
device class has a mount limit of mount maps between the indicated drive map and other drive
limit but the number of drives in the maps for drives in the same library. This could cause
associated library is less than the mount data to be written in unanticipated locations or may
limit. prevent data from being written.

System action: The server continues operation using

ANR8935E A compatible device class for shared
the indicated directory.
library library name on server server name
User response: Use the QUERY DRIVEMAP command was not found.
with the F=D parameter to list the directories
Explanation: The library client server has a device
associated with drive maps for drives in the indicated
class definition that is not compatible with the device
library and ensure that the directories are correct and
class definition on this server. The device type and
identical. Use the UPDATE DRIVEMAP command to
recording format need to be the same on both servers
update any incorrect directory entries.
or one of the servers can have a device type of generic
tape.
ANR8933W File volumename in library library does
not exist in the expected directory.
ANR8936W The path conversion of drive drive name
Explanation: A FILE volume was being dismounted in library library name with device name
from a file drive. The file does not exist in the directory device name failed. UPDATE DRIVE
in which it was expected to be found. required.
System action: The server continues operation. Explanation: During the initialization of a library, the
server finds that the drive path was removed.
User response: It is possible that a drive mapping is
incorrect and that a storage agent is using a valid, but System action: The drive will not be accessible by the
different directory than that of the server. In this case, library during tape operations.
the storage agent can access the file, but the server
User response: The drive may be made accessible by
cannot. Use the QUERY PATH command with the F=D
issuing the UPDATE DRIVE command with the
parameter to list the directories associated with drive
DEVICE= option.
maps for drives in the indicated library and ensure that
the directories are correct and identical. Use the
UPDATE PATH command to update any incorrect ANR8937W The device name for drive drive name in
directory entries. To move the file into the correct library library name is missing. UPDATE
directory, use the Windows move command or the DRIVE required.
Unix mv command, depending on your platform.
Explanation: The device name for a drive was found
to be missing.
ANR8934W File volumename in library library
System action: The drive will not be accessible by the
associated with device class device class
server for tape operations.
could not be inserted into the library
inventory. User response: The drive may be made accessible by
issuing the UPDATE DRIVE command with the
Explanation: A FILE volume was being inserted into
DEVICE= option.
the library inventory. The file was not found in the
directory associated with the device class that
references the library. However, an entry for the ANR8938E Initialization failed for Shared library
indicated file name is already in the library inventory. library name; will retry within delay time
minute(s).
System action: The server continues operation.
User response: It is possible that a drive mapping is
library has failed. It will be retried automatically in the
incorrect and that a storage agent is using a valid, but
specified time.
different directory than that of the server. In this case,
the storage agent can access the file, but the server System action: The initialization will be retried later.
cannot. Use the QUERY DRIVEMAP command with
the F=D parameter to list the directories associated User response: Ensure that the library manager server
with drive maps for drives in the indicated library and is running, and the library is initialized.
ensure that the directories are correct and identical. Use
the UPDATE DRIVEMAP command to update any ANR8939E The adapter for tape drive drive name
incorrect directory entries. To move the file into the cannot handle the block size needed to
correct directory, use the Windows move command or use the volume.
the Unix mv command, depending on your platform.
Explanation: The adapter cannot read and write the
block size need for the volume because the
MAXIMUMSGLIST parameter of the adapter is set to
less than hex 41.
System action: The volume will not be mounted in
the drive.

User response: The adapter must be updated to

ANR8942E Could not move volume volume name
handle a larger block size. The setting is usually
from slot-element element-address to
MAXIMUMSGLIST in the Windows registry under:
slot-element element-address.
HKEY_LOCAL_MACHINE->SYSTEM->Current Control
Explanation: Could Not move volume from slot to
Set->Services->{vendor device name}->Parameters-
slot.
>Device
System action: Move volume operation failed.
Note that "{vendor device name}" should be substituted
with the name of the vendors device. For example, the User response: Check previous error messages related
Qlogic 2200 would use "Ql2200" for the respective to this operation for more information. If the
vendor device name. recommended actions from other error messages do not
resolve the situation (or there are no other errors
MAXIMUMSGLIST should be set to hex 41 to work
messages), issue the AUDIT LIBRARY command to
properly with IBM Spectrum Protect.
detect and remedy inconsistencies in the library
You can also run the DSMMAXSG utility to set the inventory. This command restores the library volume
MaximumSGList value to 0x41(65) for all HBAs. inventory to a consistent state with the volumes that
physically reside in the library. After the AUDIT
For additional information, see the HBA documentation LIBRARY command completes, if the volume is not in
or contact the vendor for the HBA. the library inventory, it will need to be checked back
For additional questions, contact IBM support. into the library with the CHECKIN LIBVOLUME
command.
ANR8940E Path definition for file drive drive name

in library library name for server server or ANR8943E A hardware or media error occurred
storage agent name does not have a during an operation on library library
matching directory in the device class name (OP=internal code, CC=internal code,
directory attribute for volume volume KEY=internal code, ASC=internal code,
name. ASCQ=internal code,
SENSE=sense data,
Explanation: A library client or storage agent Description=error description). Refer to
requested a mount of a file volume in a drive that is the IBM Spectrum Protect
contained in a file library but the path definition does documentation on I/O error code
not contain a matching directory name. There must be description.
a matching directory in the PATH definition for each
drive in a file library and the corresponding directories Explanation: A hardware or media error occurred
in the device class associated with the library. The during an operation on the specified library.
directories in the PATH definition must point to the System action: The operation fails.
same storage as those of the device class definition,
from the perspective of the specific server or storage User response: Ensure that the DEVICE parameter
agent. The list of directories must have entries for each that is associated with the library is identified correctly
directory in which file volumes are to be read or in the DEFINE PATH command and that the library
written by the specified server or storage agent. device is turned on and ready. If the library has an
access door, make sure it is closed. If a cleaning
System action: The operation will fail. threshold is exceeded for a tape drive in this library,
User response: Ensure that DIRECTORY attribute of clean the tape drive. For more information about the
the above path definition contains matching directories values of the KEY, ASC, and ASCQ fields, see the
for each of the directories in the server's device class library and drive reference manuals.
definition.
ANR8944E Hardware or media error on drive drive
ANR8941W The volume from slot-element name with volume volume
element-address in drive drive name in name(OP=internal code, Error Number=
library library name is blank. internal code, CC=internal code,
KEY=internal code, ASC=internal code,
Explanation: The volume in the slot is not labeled and ASCQ=internal code,
is blank. SENSE=sense data,
System action: The volume is skipped, and processing Description=error description). Refer to
continues with the next available slot. If the volume is the IBM Spectrum Protect
checked in, it is removed from the inventory. documentation on I/O error code
descriptions.
User response: Label the volume using LABEL
LIBVOL, and check it in using CHECKIN LIBVOL. Explanation: A hardware or media error has occurred
while operating on the specified drive.


ANR8949E Device device, volume volume has issued
User response: Ensure that the DEVICE parameter the following Critical TapeAlert:
associated with the drive was identified correctly in the alertmessage
DEFINE PATH command and that the drive is
Explanation: The specified device regardless loaded or
currently powered on and ready. The drive reference
not without the named volume has issued a TapeAlert
manual usually contains tables that explain the values
critical message. This message is a feature of the
of the KEY, ASC, and ASCQ fields.
hardware and is from the host interface, not the IBM
Spectrum Protect server. It is surfaced at the
ANR8945W Scratch volume mount failed volume termination of the current operation but is independent
name. of the operation.
Explanation: Scratch volume mount failed. System action: The operation will fail. The TapeAlert
message does not by itself indicate failure. See other
System action: Scratch volume mount operation messages related to the device or volume in the activity
failed. log.
User response: None. User response: Proper response may be indicated in
the text of the TapeAlert. The context of the TapeAlert
ANR8946W There were more labels in the vollist may need to be determined from other activity log
than volumes available to label. messages in order to follow its recommendations.
Explanation: Label Libvolume command still finishes

without error, but the last labels provided were not ANR8950W Device device, volume volume has issued
used. Labeling finished when there were no more the following Warning TapeAlert:
volumes available. alertmessage
System action: All available volumes were labeled, Explanation: The specified device without the volume
but additional volume names were not utilized from name has issued a TapeAlert Warning message. This
the vollist. message is a feature of the hardware and is from the
device, not the IBM Spectrum Protect server. It is
User response: None. surfaced at the termination of the current operation but
is independent of the operation.
ANR8947W There were less labels in the vollist than System action: The operation will fail. See other
volumes available. messages related to the device or volume in the activity
Explanation: Label Libvolume command still finishes log.
without error, but volumes are left unlabeled. User response: Proper response may be indicated in
System action: Additional volumes were left the text of the TapeAlert. The context of the TapeAlert
unlabeled. may need to be determined from other activity log
messages in order to follow its recommendations.
ANR8951I Device device, volume volume has issued

ANR8948S Device device, volume volume name has the following Information TapeAlert:
issued the following Critical TapeAlert: alertmessage
alertmessage
Explanation: The specified device while loaded with
Explanation: The specified device while loaded with the named volume has issued a TapeAlert information
the named volume has issued a TapeAlert critical message. This message is a feature of the hardware and
message. This message is a feature of the hardware and is from the device, not the IBM Spectrum Protect
is from the device, not the IBM Spectrum Protect server. It is surfaced at the termination of the current
server. It is surfaced at the termination of the current operation but is independent of the operation.
operation but is independent of the operation.
System action: The operation may or may not fail,
System action: The operation may or may not fail, depending on other error indications such as check
depending on other error indications such as check conditions from the device. The TapeAlert message
conditions from the device. The TapeAlert message does not by itself indicate failure. See other messages
does not by itself indicate failure. See other messages related to the device or volume in the activity log.
related to the device or volume in the activity log.
User response: Proper response may be indicated in
User response: Proper response may be indicated in the text of the TapeAlert. The context of the TapeAlert
the text of the TapeAlert. The context of the TapeAlert may need to be determined from other activity log
may need to be determined from other activity log messages in order to follow its recommendations.
messages in order to follow its recommendations.

does not match with the serial number discovered. The

ANR8952E Library serial number does not match
newly discovered serial number will replace the
that defined for library name .
existing definition for this drive since autodetect is on.
Explanation: The serial number defined for the
System action:
specified library does not match the serial number
discovered. The pending operation will fail. User response: None.
System action: The library is taken offline when the
mismatch is discovered. Verify the serial number and ANR8956E Serial number defined for library library
the device name for the library against those defined. If name does not match the discovered
they do not match, the definitions for the library are serial number.
incorrect and need updated. Once the serial number is
updated, the library will be brought back online. Explanation: The serial number for the library defined
does not match the serial number discovered due to
User response: Update the serial number or device autodetect is set to NO. The pending operation will fail.
name for the specified library with the correct values.
System action: A mismatch between the serial number
for library and the newly discovered serial number is
ANR8953I Library library name with serial number detected.
serial number is updated with the newly
discovered serial number serial number. User response: Update the serial number for the
specified library with the correct values.
Explanation: The serial number for the library defined
does not match with the serial number discovered. The
newly discovered serial number will replace the ANR8957E Command: The serial number reported
existing definition for this library since autodetect is on. by the library did not match the serial
number in the library definition.
System action: The existing serial number for the
specified library is replaced by the newly discovered Explanation: The serial number of the library in the
serial number. database did not match the serial number of the library
found using the device special file specified. UPDATE
User response: None. PATH cannot be used to change libraries, and thus, the
new device must have the same serial number as
stored in the database unless the serial number in the
ANR8954E Failed to obtain a path for drive drive
database is empty.
name for library library name.
Explanation: An attempt to acquire a path for the
drive failed. This most likely means that a path is not User response: Reissue the command, and specify a
defined for this drive. valid DEVICE parameter value. If this is a new or
different library with a different serial number, a new
library and path should be defined with DEFINE
User response: Ensure that a path is defined for this LIBRARY and DEFINE PATH.
drive. If one is defined, make sure it is defined
correctly with the correct source and destination type.
ANR8958E Command: Autodetect is OFF and the
If the drive is in a shared FILE library:
serial number reported by the drive did
Ensure that the number of paths defined for the storage not match the serial number in the drive
agent is the same as the number of drives within the definition.
library.
Explanation: An invalid value has been provided for
Ensure that the directories are correct in the server the specified parameter.
device-class definition and the storage-agent path
definitions.
User response: Reissue the command, and specify a
Ensure that the number and order of directories for
valid parameter value.
each path for the storage agent is the same as the
number and order of directories in the device-class
directory definition. ANR8959W Path to the library or the device does
not exist.
ANR8955I Drive drive name in library library name Explanation: A path to the library or the device does
with serial number serial number is not exist yet.
updated with the newly discovered
serial number serial number. System action: This may not be an error.
Explanation: The serial number for the drive defined User response: None.

device to see if there is a hardware problem.

ANR8960I Command: The display of Tape Alerts
from SCSI devices is status.
ANR8964W Unable to update the path in the
Explanation: Whether the status of Tape Alerts from
database path source name and drive drive
SCSI devices will be display.
name.
System action: The command is processed.
Explanation: The system is not able to update the
User response: None. path information in the database.
System action: .
ANR8961E Serial number defined for library library
name and drive drive name is blank and
does not match the discovered drive
serial number serial number. ANR8965W The server is unable to obtain the serial
number of the SCSI device device name.
Explanation: A device has been swapped and we are
not able to get the new path. Explanation: The server cannot detect a device serial
number from the HBAAPI or the device itself, so the
System action: .
server is not able to automatically correct the path for
User response: None. the device.
ANR8962E Unable to find path to match the serial
User response: Verify the following:
number defined for library library name.
v The device name in the path definition is correct.
Explanation: Either a device has hardware problems
v The correct version of the HBAAPI is installed to the
or a device path has been changed and the IBM
system.
Spectrum Protect server cannot find the new path with
the SAN Discovery option set to ON. v The SANdiscovery option is set to ON in the options
file.
System action: .
User response: None. ANR8966E Cannot get device number for the drive
drive name.
ANR8963E Unable to find path to match the serial Explanation: The server is unable to obtain the device
number defined for drive drive name in number for the specified drive. This could occur if an
library library name. invalid device name is specified for the drive or if there
Explanation: A device may have hardware problems is hardware errors.
or a device path may have been changed and the IBM System action: The drive is temporarily made offline
Spectrum Protect server cannot find the new path with and is not used for tape operations. The server polls
the SAN Discovery option set to ON. The IBM the drive at one-half minute intervals to check if the
Spectrum Protect server cannot get device information condition has cleared. Once the drives is accessible
when it cannot open the device. Therefore, the IBM again, the drive is brought online.
Spectrum Protect server cannot validate the drive serial
number to see if this drive with the failed open User response: Determine the reason the drive is
operation is the same drive as it previously used. The inaccessible, such as hardware errors reported in the
causes of this failed open device may be a bad cable, a system logs or an invalid device name was specified
bad drive or a bad HBA card. However, if an incorrect for the drive. Render any needed corrections to the
drive is used (for example, an incorrect device path) drive. The drive will be brought online automatically
and with the SAN discovery option set to OFF or when the polling process detects that is has become
UNSCANNEDPATHOFF, the IBM Spectrum Protect accessible.
server will not search the SAN environment to get a
proper device. ANR8967E Command: The drive serial conflicts with
System action: The IBM Spectrum Protect server may an existing drive in library library name.
mark this device offline for SAN Discovery option ON Explanation: The serial number already exists in the
or UNSCANNEDPATHOFF. drives in the given library.
User response: Users should check the IBM Spectrum System action: The command is not processed.
Protect server option file first. If SAN discovery option
is set to OFF or UNSCANNEDPATHOFF, set it to ON User response: Specify a valid serial parameter for
and check for hardware errors on the device. If the this drive.
SAN discovery option is set to ON, then check the

System action: The command fails. The server

ANR8968E Unable to create path for device device.
continues.
Explanation: An attempt to contact the drive with a
User response: Make sure that the directory exists and
given device name failed. This probably means the
can be accessed by the server.
device name is incorrect, but this attempt can also fail
for other reasons.
ANR8972E command: Unable to find the element
System action: Operation failed.
number for drive drive name in library
User response: The device parameter is probably not library name.
valid. This could be temporary, but not necessarily. If
Explanation: Because the drive serial number does not
this occurs while upgrading from IBM Spectrum
match any drive serial number in the serial/element
Protect Version 4.1 or previous (where paths were not
number map reported by the library, the element
used), then the drive needs to be deleted, redefined,
number cannot be determined.
and a new path needs to be defined with a valid device
parameter. If this occurs on an IBM Spectrum Protect System action: The command is not processed.
server that already has paths (Version 4.2 or higher),
then just update the drive to online. The device User response: Make sure the serial number entered
parameter on the drive path can also be updated before for the drive is correct if AUTODETECT is not active. If
the drive is turned online, if you know the device AUTODETECT is active, the drive serial number might
parameter should be changed. be incorrect or the library reported an incorrect
serial/element number map. Contact your service
representative.
ANR8969E The owner of volume Volume name can
not be updated to owner Owner name.
ANR8973E Device reset failed to break the
Explanation: A command was issued updating reservation set by another system for
ownership of a volume. The owner of this particular device device name with path path name.
volume can not be changed.
Explanation: The attempt to reset the device
System action: The command is not processed. reservation set by another system failed.
User response: None. System action: No system action taken.
User response: If this tape device is a Fibre Channel
ANR8970E Unable to open special file specialfile for direct attached device on Windows 2003, make sure
tracing parameter device driver; errno = that the HBA driver is a StorPort driver by checking
errno. the HBA vendor's support web site. The device reset
(LUN Reset) on Windows 2003 requires a StorPort
Explanation: The special file created by the device
driver. Otherwise, you might need to restart the device
driver for tracing purposes could not be opened by the
to reset the reservation so that the device is accessible.
server. This file should be created when the device
If this device is a tape device that is attached to an AIX
driver is configured on the system
system, make sure that this device is not configured by
System action: Device driver tracing could not be the AIX generic tape driver. Use the system command
started. "lsdev" to verify it as follows: "lsdev -Cs fcp | grep
mt". The device cannot reset if the "RESETDrives"
User response: Make sure that the special file exists
keyword for the UPDATE LIBRARY command is set to
and can be accessed by the server. If the device driver
"No", device reset will not be attempted.
has not been completely configured and special files
created for all devices, do so. The device driver can
also be traced by specifying the name of a library or ANR8974I Found new path for path source name and
drive that has been defined to the IBM Spectrum target name target name old path old path
Protect Server. name new path new path name. Path
information will be updated remotely.
ANR8971E Unable to validate directory name Explanation: A new path has been found for the
directory name for parameter command. device on the library client or storage agent. Will try to
update the path information on the library manager.
Explanation: The specified directory name was being
used in the indicated command. The server attempted System action: .
to validate that the directory was accessible so that it
User response: The path change may be caused by
could be used in the command definition. The server
system reboot or cable swap or device addition or
was unable to validate that the directory was
removal.
accessible.

Spectrum Protect server to capture the new

ANR8975I Found new path for path source name and
configuration.
target name target name old path old path
name new path new path name. Path
information is updated. ANR8979I Command: Operation for library library
name started as process process ID.
Explanation: A new path has been found for the
device and the path information has been updated. Explanation: A sacn library process has been started
for the given library. The process is assigned the ID
System action: .
specified in the message.
User response: The path change may be caused by
system reboot or cable swap or device addition or
to perform the operation in response to the SCAN
removal.
LIBRARY command entered by an administrator.
User response: To obtain status on the process, issue
ANR8976E Unable to open special file specialfile for
the QUERY PROCESS command. The process may be
LUN reset with errno = errno.
Explanation: The special file created by the device
driver for LUN reset purposes could not be opened by
ANR8980I SCAN LIBRARY process for library
the server. This file should be created when the device
library name has been canceled.
driver is configured on the system
System action: LUN reset could not be started.
been working to scan the given library is canceled by
User response: Make sure that the special file exists the CANCEL PROCESS command.
and can be accessed by the server. If the device driver
has not been completely configured with special files
created for all devices, resolve the device driver
configuration. User response: None.
ANR8977W The volume loaded into library library ANR8981I Scanning for library library name.
name did not have a valid label. Please
load a scratch volume with a valid label. Explanation: In response to a QUERY PROCESS
command, this message displays the status for an
Explanation: During normal operations a MANUAL SCAN LIBRARY process on the server.
library will prompt the user for the desired volume
name if the volume does not have a valid label and the System action: Server operation continues.
AUTOLABEL parameter is turned on. However, the User response: None. The process may be canceled by
utility mode of DUMPDB cannot prompt the user for a an authorized administrator using the CANCEL
desired volume name. PROCESS command.
System action: The server unloads the volume and
asks for a new scratch volume with a valid label. ANR8982E SCAN LIBRARY process for library
User response: The user needs to insert scratch library name failed.
volumes with valid labels or reissue the DUMPDB Explanation: The background process for an SCAN
command and specify the desired volume name on the LIBRARY command has failed.
command line with the VOLUMENAMES parameter.
See the DUMPDB documentation. System action: The background process ends.
ANR8978W The number of drives in library library devices associated with this command are powered on
name has been increased from original and ready, then reissue the command.
drive count to new drive count Please
restart the IBM Spectrum Protect server ANR8983I SCAN LIBRARY process for library
to update the configuration; library name completed successfully.
Explanation: The number of drives in the library has Explanation: The background process for an SCAN
been increased. The new configuration will be recorded LIBRARY command has completed successfully.
if IBM Spectrum Protect server is restarted.
System action: The library has been scaned.
System action: .
User response: Number of drives in the library has
been increased. The user needs to restart the IBM

parameter on the device class to a value other than

ANR8984E The drive drive name in library library
ON.
name is incapable of performing any
drive encryption operations.
ANR8987W The server will not encrypt the volume
Explanation: The server queried the drive's encryption
volume name.
capability, and the query failed or the query showed
that the drive does not have encryption capabilities. Explanation: Drive encryption with the device class
parameter setting of DRIVEENCRYPTION=ON will
System action: The mount operation fails.
only encrypt storage pool volumes. Thus, backupsets,
User response: If this message occurs on a scratch DB backups, and export volumes will not be encrypted.
mount and drive encryption has not been utilized yet,
System action: The mount continues, but encryption is
you can turn drive encryption off by updating the
not used.
DRIVEENCRYPTION parameter on the device class.
Otherwise, verify your hardware configuration. First, User response: If encryption is needed for this volume
verify that all the drives in this logical library support or other backupsets, DB backups, or export volumes,
drive encryption. Second, verify that the device driver use a different method of encryption: use a device class
controlling all of the drives in this library also supports parameter of DRIVEENCRYPTION=ALLOW and a
drive encryption. If both the drives and the device hardware method of 'Library' or 'System' (do not use
driver support drive encryption, call your drive the 'Application' method).
hardware support.
ANR8988W Library Library Name failed to relabel
ANR8985E The drive drive name in library library volume Volume Name after it returned to
name is using an encryption method that scratch.
is incompatible with the current server
settings. Explanation: The RELABELSCRATCH option is
enabled, and while attempting to relabel the volume
Explanation: The server requires the drive to use the operation failed.
various drive encryption methods based on the
DRIVEENCRYPTION device class parameter for empty System action: None.
volumes or based on the previous encryption method User response: This warning may be issued if the
used for filling volumes. The server is unable to relabeling operation attempts to relabel the same
properly handle the volume's encryption key without volume as another library volume operation: LABEL
resolving this conflict. LIBVOLUME, CHECKIN LIBVOLUME, CHECKOUT
System action: The mount operation fails. LIBVOLUME, or another relabeling operation. For
example, suppose two relabeling operations run on the
User response: If this message occurs while mounting same volume. If the first relabeling operation succeeds
an empty volume the encryption method setup in your and the second operation fails, no action is required.
hardware environment is incompatible with the
DRIVEENCRYPTION setting in your device class. Verify the volume is still checked into the library with
Either update the device class or your hardware's the QUERY LIBVOL command. If it is not checked in,
encryption method such that these setting no longer use LABEL LIBVOL or CHECKIN LIBVOL to check the
conflict. If this message occurs while mounting a filling volume back into the library.
volume, either update your hardware configuration to
the same method used while originally backing up this ANR8989E Unable to establish a communication
volume, which can be determined by the QUERY session with the primary library
VOLUME FORMAT=DETAIL command, or update this manager.
volume's access to UNAVAILABLE.
Explanation: The requested operation required that a
communication session be established with a library
ANR8986E The server currently doesn't allow AES manager. The library manager was found to be
encryption which is required for drive unavailable at this time.
encryption support with the
DRIVEENCRYPTION=ON parameter on System action: None.
the device class. User response: Verify the primary library manager is
Explanation: Without AES encryption support the up and operational. Once the server is verified to be
server cannot generate adequately strong enough operational, retry the operation.
encryption keys for drive encryption.
System action: The mount operation fails.
User response: Update the DRIVEENCRYPTION

ANR8990E Device Device Name is not supported by ANR8994W Append-only mode is not supported on
the IBM Spectrum Protect server. drive Drive Name.
Explanation: The device product identification is not Explanation: The server attempted to enable
recognized by the IBM Spectrum Protect server. Append-Only mode on the tape drive for data
overwrite protection. However, the tape drive does not
support Append-Only mode.
User response: Determine if the installed level of the
System action: The server will not enable append-only
server supports the device. See the device support web
mode on the tape drive for data overwrite protection.
page for Linux systems at IBM Tivoli Storage Manager
Supported Devices for Linux or the device support User response: No action is required. You can set the
page for all other systems at IBM Tivoli Storage server option CHECKTAPEPOS to No or TSMonly if
Manager Supported Devices for AIX, HP-UX, Solaris, you do not wish the server to use append-only mode
and Windows. for data overwrite protection on the tape drives that
support append-only mode.
If the device is a tape drive and is not supported, you
can use it with the generic tape format. To use the
drive, specify GENERICTAPE=Yes when defining a ANR8995E Unable to write to volume Volume Name
path to the drive. If the device is supported and this in drive Drive Name.
message is received, search the IBM Spectrum Protect
Explanation: The server is unable to write to the
Support Web site for known solutions:
volume because the drive is in append-only mode and
IBM Spectrum Protect product documentation the volume is write-protected.
If no solution is found, report the issue to IBM System action: The server will dismount the volume
Spectrum Protect Support. and continue processing with another volume.
ANR8991E The GENERICTAPE format is not assistance.
supported with drive Device Name.
Explanation: The device driver does not support all ANR8996W Unable to query or enable append-only
features required for the GENERICTAPE format. mode on drive Drive Name.
System action: None. Explanation: The server was unable to query or
enable append-only mode on the tape drive.
User response: Make sure the tape drive is controlled
by the native device driver. The IBM Spectrum Protect System action: The server will not enable append-only
device driver does not support the generic tape format. mode for the volume during this mount. The server
If the drive is controlled by the IBM Spectrum Protect will attempt to enable append-only mode the next time
device driver and you intend to use the IBM Spectrum a volume is mounted if the server option
Protect tape format with the drive, do not specify CHECKTAPEPOS is set to Yes or DRIVEonly.
GENERICTAPE=Yes when defining a path to the drive.
User response: If the problem persists, contact your
service representative for assistance. If you do not want
ANR8992E The library state refresh for library name the server to use append-only mode for data overwrite
failed. protection, you can set the server option
CHECKTAPEPOS to No or TSMonly.
Explanation: The operation to re-initialize the library's
state failed.
ANR8997W The current version of the device driver
for drive Drive Name is Driver Version. To
User response: To refresh the library state, halt and enable append-only mode, version
restart the IBM Spectrum Protect server. Required Version or later is required.
Explanation: The device driver for the drive does not
ANR8993I The library state refresh for library name meet the version requirement to support append-only
was successful. mode.
Explanation: The server successfully re-initialized the System action: The server will not enable append-only
library's state. mode on the tape drive for data overwrite protection.
System action: None. User response: Upgrade the device driver for the
drive to the required version.

logical block protection enabled on the volume.

ANR8998W Encryption has been disabled for drive
drive name in library library name. User response: If the media type supports logical
block protection, mark the volume access to
Explanation: The server determined that the drive's
READONLY so that the server cannot write to the
encryption method was Application Managed
volume.
Encryption (AME). Since the server is assumed
responsibility for encryption settings when device class
uses DRIVEENCRYPT=ALLOW and the drive uses ANR9002E The version of the device driver for
AME, encryption has been disabled. drive Drive Name is Driver Version. Driver
version Required Version or later is
System action: The mount continues with encryption
required for logical block protection.
disabled.
Explanation: The device driver for the drive does not
User response: If encryption is intended to be used
meet the version requirement for logical block
for this operation, with IBM Spectrum Protect
protection.
managing the encryption keys, then the
DRIVEENCRYPT parameter should be set to ON. If System action: The mount operation fails.
encryption is intended to be used for this operation,
without IBM Spectrum Protect managing the User response: Upgrade the device driver for the
encryption keys (for example, NEC, Fujitsu, and drive to the required version.
SpectraLogic provide AME encryption solutions
without IBM Spectrum Protect managing encryption), ANR9003E The block CRC validation failed on
then the DRIVEENCRYPT parameter should be set to volume volume name in drive drive name.
EXTERNAL. In either of these situations, data on the
volume used in this operation will need to be moved to Explanation: The data block was corrupted while it
a new volume with the correct settings to encrypt the was transferred to or from the drive.
data. System action: The operation fails.
User response: Restart the operation to try the volume
ANR8999E Directory name directory name has been in a different drive. If the problem persists, check the
duplicated in parameter command. hardware connections and the tape drive.
Explanation: When defining or updating multiple
directories for a device class, you can only specify a ANR9004E The server has detected that drive name
directory name once in the command. can also be accessed by other
System action: The command fails. The server applications through the st device
continues. special file device name. All st device
special files for this drive must be
User response: Ensure that the directory name is deleted.
specified only once in the command.
Explanation: When more than one device driver can
access a drive, tape labels or other data can be
ANR9000E Drive drive name does not support overwritten. To prevent possible data integrity issues,
logical block protection. you must delete all st device special files for this tape
Explanation: The LBPROTECT parameter associated drive.
with the device class is set to enable logical block System action: The operation fails or the drive is
protection. However, the tape drive does not support temporarily taken offline and is not available for tape
logical block protection. operations. The server polls the drive at thirty second
System action: The mount operation fails. intervals to verify that all of the st device special files
for the tape drive have been deleted. Once all files have
User response: Update drive firmware to the level been deleted, the drive is brought back online.
that supports logical block protection.
User response: Run the rmstdev utility with -d as the
root user to locate and delete the st device special files.
ANR9001W Volume volume name does not have Then, retry the operation.
logical block protection.
Explanation: The server cannot enable logical block ANR9005E Command: Library library name has an
protection for this volume. Data that is already on the active relabel process and can not be
volume does not have logical block protection, or the deleted.
media type is not compatible with logical block
protection. Explanation: The designated library can not be
deleted or updated because it is currently in use for a
System action: The operation will continue without relabel operation.


ANR9009E The cartridge access port (CAP) for
User response: Wait until the relabel operation library library name is not available. The
completes, and then retry the command. CAP status is cap status.
Explanation: An error occurs in the CAP while
ANR9006E Tape volumes must be physically accessing the specified library.
removed from an ACSLS cartridge
access port (CAP).
User response: Ensure that the CAP is empty, all tape
Explanation: Tape volumes are located in the ACSLS
volumes are removed from the CAP, and the CAP door
CAP. The ACSLS server requires users to physically
is closed.
remove these volumes from the CAP within 30
minutes. When REMOVE=YES is set for the
CHECKOUT LIBVOLUME command, a tape ejection ANR9010W Unable to verify drive drive name.
operation is scheduled. If the user fails to remove the
Explanation: The mount operation fails because the
tape from the CAP within 30 minutes, the ACSLS
SANDISCOVERY option is not enabled. Therefore, the
server sets a failure status for the tape ejection
SAN discovery function did not verify whether the
operation.
specified drive must be opened.
System action: The ACSLS library ejected tape
System action: The SAN discovery function is not
volumes and relocated them to a CAP.
turned on.
User response: Remove the volumes from the CAP. If
User response: Verify the SANDISCOVERY option
there are no tape cartridges in the CAP, check the
value in the dsmserv.opt file. If the value is set to OFF
ACSLS library to ensure that no tapes are lodged there.
or UNSCANNEDPATHOFF, change the value to ON.
ANR9007E Command: The library cartridge access

ANR9011E Position error: the volume volume name
port (CAP) ID is invalid for library
in drive drive name is not at the expected
library name.
expected position : The actual volume
Explanation: Tape volumes were not ejected from the position is: expected volume position.
ACSLS library because the library CAP ID was not
Explanation: The CHECKTAPEPOS server option has
specified in the CHECKOUT LIBVOLUME command.
determined that there is a volume position error IBM
By default, all CAPs initially have a priority value of 0,
Spectrum Protect has not repositioned the tape. Writing
which means that the ACSLS server does not
is halted to prevent data loss.
automatically select a CAP.
System action: The write operation fails.
System action: The system failed to eject the tape
volumes. User response: See the IBM Spectrum Protect
documentation about preventing tape label overwrites
User response: To verify the CAP priority value, issue
in the IBM Knowledge Center at http://
the QUERY CAP command. If the priority value is 0,
www.ibm.com/support/knowledgecenter/SSGSG7.
reissue the CHECKOUT LIBVOLUME command with a
CAP ID. Alternatively, set the CAP priority to a
non-zero value and reissue the CHECKOUT ANR9012E There is no drive available for the
LIBVOLUME command. database restore operation for device
class device class name.
ANR9008E Unable to determine the drive type for Explanation: The database restore operation cannot be
Device of type Device Inquiry String. completed. There are no available mount points.
Possible reasons include:
Explanation: The drive could not be opened. This
version of IBM Spectrum Protect may not support the v The device configuration file is not correctly defined
drive type. to acccess the media.
v There is a problem with the media.
System action: The system failed to identify the drive
type. System action: The database restore operation fails.
User response: Verify that the drive type is supported. User response: Review the information in the message
See the device support web page for Linux systems at explanation and take action to correct any problems
IBM Tivoli Storage Manager Supported Devices for with the device configuration file or media. Reissue the
Linux or the device support page for all other systems RESTORE DB command.
at IBM Tivoli Storage Manager Supported Devices for
AIX, HP-UX, Solaris, and Windows.

CANCEL PROCESS command. You cannot cancel the

ANR9013W The library library name does not use
background server process because of a tape firmware
RESETDRIVES.
limitation when you run the AUDIT LIBVOLUME
Explanation: In a cluster failover environment when command.
running the DEFINE LIBRARY command, you must set
System action: The background server process
the RESETDRIVES parameter to YES when the
continues.
SHARED parameter value is NO (a default value).
The RESETDRIVES parameter specifies that the server
cleans up the reservation in tape drives after a cluster
failover occurrs. For example, host A is a primary host ANR9017I Command: Operation for volume volume
system and host B is a secondary host system in a name in library library name started as
cluster failover environment. Before failover occurs, process process ID.
host A uses a tape drive. After failover occurrs from
host A to host B, host A continues to reserves this tape Explanation: A volume audit process is in progress for
drive. If the RESETDRIVES parameter is set to NO, a specific library. The process is assigned the ID that is
host B does not clean up the reservation from this tape specified in the message.
drive. Host B no longer has access to this tape drive. If System action: When you run the AUDIT
the RESETDRIVES parameter is set to YES, host B LIBVOLUME command, the server starts the volume
cleans up the reservation from this tape drive and can audit process.
has access to this drive. For more information on the
RESETDRIVES parameter, see the DEFINE LIBRARY User response: Issue the QUERY PROCESS command
command. to display information about background processes.
System action: A server cannot access tape drives that

are reserved by another server in a cluster failover ANR9018E AUDIT LIBVOLUME for volume volume
environment after a failover has occurred. name in library library name failed.
User response: Issue the UPDATE LIBRARY Explanation: The background process for an AUDIT
command and specify the RESETDRIVES=YES option. LIBVOLUME command failed.
System action: The background process ends, but the
ANR9014E Volume volume name is incompatible volume is not audited.
with drive drive name. User response: Ensure that the library and the drive
Explanation: The drive cannot read the volume devices that are associated with the AUDIT
format. This can be attributed to a different generation LIBVOLUME command are turned on, and run the
media format or an encrypted tape. command again.

ANR9019I AUDIT LIBVOLUME for volume volume
User response: Make sure that the volume is correctly name in library library name completed
formatted for this drive, and validate the device class successfully.
settings for this operation. If it is encrypted, the drive
must be configured to decrypt the cartridge. Explanation: The AUDIT LIBVOLUME process
ANR9015E The device device name path symlink System action: None.
appears to be circular. User response: None.
Explanation: When the server attempts to validate the
device path the symlink is too long. ANR9020E You cannot issue the AUDIT
System action: A server cannot access the device due LIBVOLUME command by using the
to a device symlink problem. drive drive name for volume volume name
in library library name.
User response: Issue the autoconf script to re-establish
the links. Explanation: The background process for the AUDIT
LIBVOLUME command failed. You cannot issue the
AUDIT LIBVOLUME command by using the specified
ANR9016W Process process number: AUDIT type of drive.
LIBVOLUME for volume volume name in
library library name cannot be cancelled. System action: The background process ends and but
the volume is not audited.
Explanation: If you use the AUDIT LIBVOLUME
command to audit a volume in a specific library, you User response: Issue the AUDIT LIBVOLUME
cannot cancel a background server process by using the command on a library that has any of the following

ANR9021I • ANR9580W (Linux)
tape drives: - IBM 3592 generation 4 drive or later -

ANR9025E There are no available NAS drives
IBM LTO generation 5 drive or later
attached to the required node of a NAS
cluster.
ANR9021I Auditing volume volume name from
Explanation: The server cannot find any valid drives
library library name with process process
for the NAS operation. In most cases, this prevents a
ID uses drive drive name.
NAS clustered node from accessing the drives.
Explanation: When the IBM Spectrum Protect server
locates a drive to process the AUDIT LIBVOLUME
command, a status message is displayed. User response: If any drives or paths are offline, use
the UPDATE DRIVE or UPDATE PATH commands to
System action: The AUDIT LIBVOLUME background
bring them back online. For a clustered NAS device,
process operation continues.
verify that a path is defined using the correct device
User response: None. name. For a drive attached to a clustered NAS device,
the device name contains the node name within the
cluster in which the device is attached.
ANR9022E Volume volume name could not be
mounted for the AUDIT LIBVOLUME
command because all of the drives are ANR9579W (HP-UX) Command: The file file name
in use in library library name. cannot be found.
Explanation: The background process for the AUDIT Explanation: The specified file cannot be found.
LIBVOLUME command fails.
System action: For the default server executable file,
System action: The background process ends. The the PREPARE command uses /opt/IBMadsm-s/bin/
volume is not audited. dsmserv.
User response: Ensure that a drive is available before User response: Determine why the file does not exist
you issue the AUDIT LIBVOLUME command. You can and create it if necessary.
dismount an idle volume in a tape drive or wait until a
drive is available before you issue the command again.
ANR9579W (Linux) Command: The file file name
cannot be found.
ANR9023E The AUDIT LIBVOLUME command
Explanation: The specified file cannot be found.
failed for drive drive name with the
current tape device driver version current System action: For the default server executable file,
driver version. Use driver version the PREPARE command uses /opt/IBMadsm-s/bin/
supported driver version and above to dsmserv.
issue the AUDIT LIBVOLUME
User response: Determine why the file does not exist
command.
and create it if necessary.
Explanation: The background process for a AUDIT
LIBVOLUME command fails.
ANR9579W (Solaris) Command: The file file name
System action: The background process ends, but the cannot be found.
volume has not been audited.
User response: Install a supported drive version and
try the command again.
the PREPARE command uses /opt/IBMadsm-s/bin/
dsmserv.
ANR9024E There are no drives available.
Explanation: The server cannot find any valid drives. and create it if necessary.
In most cases, this prevents client nodes from accessing
the drives.
ANR9580W (Linux) Command: Generated replacement
System action: The operation fails. volume name volume name may
not be a valid raw partition name.
User response: If any drives or paths are offline, use
Original volume name:volume name.
the UPDATE DRIVE or UPDATE PATH commands to
Stanza is stanza name.
bring them back online.
name postfix to the original volume name has created a
name that may not be a valid raw partition name.

ANR9580W (Solaris) • ANR9583E (HP-UX)
System action: Replacement volume name is used in included in the recovery plan stanza.
User response: Determine why file does not exist;
User response: Manually update the generated create if necessary.
recovery plan stanza with a legal replacement name.
The replacement name can be another raw partition
ANR9582E (HP-UX) Command: Generated file name
name or a regular file name.
too long. Length of directory or prefix
'prefix' plus 'name' exceeds maximum
ANR9580W (Solaris) Command: Generated characters characters.
replacement volume name volume name
Explanation: The file name generated is too long. The
may
maximum valid length is shown in the message.
not be a valid raw partition name.
Original volume name:volume name. System action: The recovery plan file was not created.
Stanza is stanza name.
Explanation: Appending the replacement volume valid prefix. The following commands are used to
name postfix to the original volume name has created a specify the prefix:
name that may not be a valid raw partition name. v SET DRMPLANPREFIX
System action: Replacement volume name is used in v SET DRMINSTRPREFIX
the recovery plan stanza. v PREPARE
User response: Manually update the generated
recovery plan stanza with a legal replacement name. ANR9582E (Linux) command: Generated file name too
The replacement name can be another raw partition long. Length of directory or prefix
name or a regular file name. 'prefix' plus 'name' exceeds maximum
ANR9581W (HP-UX) Command: Volume file name not Explanation: The file name generated is too long. The
found while building stanza recovery maximum valid length is shown in the message.
plan stanza name.
Explanation: This volume is defined to the server but
does not exist. The device class associated with the User response: Reissue the command specifying a
volume is DISK or the device class device type is FILE. valid prefix. The following commands are used to
specify the prefix:
System action: The entry for the volume is not
included in the recovery plan stanza. v SET DRMPLANPREFIX
v SET DRMINSTRPREFIX
create if necessary. v PREPARE
ANR9581W (Linux) command: Volume file name not ANR9582E (Solaris) Command: Generated file name
found while building stanza recovery too long. Length of directory or prefix
plan stanza name. 'prefix' plus 'name' exceeds maximum
does not exist. The device class associated with the Explanation: The file name generated is too long. The
volume is DISK or the device class device type is FILE. maximum valid length is shown in the message.
System action: The entry for the volume is not System action: The recovery plan file was not created.
included in the recovery plan stanza. User response: Reissue the command specifying a
User response: Determine why file does not exist; valid prefix. The following commands are used to
create if necessary. specify the prefix:
v SET DRMPLANPREFIX
ANR9581W (Solaris) Command: Volume file name not v SET DRMINSTRPREFIX
found while building stanza recovery v PREPARE
plan stanza name.
Explanation: This volume is defined to the server but ANR9583E (HP-UX) Command: Cannot generate fully
does not exist. The device class associated with the qualified file name for 'name'.
volume is DISK or the device class device type is FILE.
Explanation: A failure occurred expanding the
System action: The entry for the volume is not specified file name.

ANR9583E (Linux) • ANR9586E (Linux)

ANR9584E (Solaris) Command: Cannot generate
User response: Reissue the command specifying a server options file name.
valid prefix. The following commands are used to
Explanation: A failure occurred generating the server
specify the prefix:
options file name.
v SET DRMPLANPREFIX
v PREPARE User response: See accompanying messages for more
information.
ANR9583E (Linux) command: Cannot generate fully

qualified file name for 'name'. ANR9585E (HP-UX) Command: Cannot generate a
volume history file name.
Explanation: A failure occurred expanding the
specified file name. Explanation: A failure occurred generating the volume
history file name.
valid prefix. The following commands are used to User response: See accompanying messages for more
specify the prefix: information.
v SET DRMPLANPREFIX
v SET DRMINSTRPREFIX ANR9585E (Linux) command: Cannot generate a
v PREPARE
Explanation: A failure occurred generating the volume
history file name.
ANR9583E (Solaris) Command: Cannot generate fully
qualified file name for 'name'. System action: Recovery plan file not created.
Explanation: A failure occurred expanding the User response: See accompanying messages for more
specified file name. information.
ANR9585E (Solaris) Command: Cannot generate a
valid prefix. The following commands are used to
specify the prefix: Explanation: A failure occurred generating the volume
v SET DRMPLANPREFIX history file name.
v SET DRMINSTRPREFIX System action: Recovery plan file not created.
v PREPARE User response: See accompanying messages for more
information.
ANR9584E (HP-UX) command: Cannot generate server
options file name. ANR9586E (HP-UX) Command: Cannot generate a
Explanation: A failure occurred generating the server device configuration file name.
options file name. Explanation: A failure occurred generating the device
System action: Recovery plan file not created. configuration file name.
User response: See accompanying messages for more System action: Recovery plan file not created.
information. User response: See accompanying messages for more
information.
ANR9584E (Linux) command: Cannot generate server
options file name. ANR9586E (Linux) command: Cannot generate a
Explanation: A failure occurred generating the server device configuration file name.
options file name. Explanation: A failure occurred generating the device
System action: Recovery plan file not created. configuration file name.
User response: See accompanying messages for more System action: Recovery plan file not created.
information. User response: See accompanying messages for more
information.

ANR9586E (Solaris) • ANR9604E (AIX)
User response: If the error given is "ENOSPC", the

ANR9586E (Solaris) Command: Cannot generate a
maximum number of system message queue have
device configuration file name.
likely been exceeded. update "/etc/system" with "set
Explanation: A failure occurred generating the device shmsys:msginfo_msgmni=100". Any other error
configuration file name. suggests an internal problem and shoud be reported.
ANR9602E (AIX) Invalid JOB information passed to
User response: See accompanying messages for more
the NETLS Interface.
information.
Explanation: The server licensing functions
encountered an internal error in accessing license
ANR9600E (AIX) Invalid information passed to
information for the server storage capacity and number
NETLS license interface.
of registered clients.
System action: Server operation continues. New
licensing information is not used by the server.
of registered clients. User response: Contact your service representative for
ANR9602E (Solaris) Error errno while attaching
memory segment for shared memory
communications.
Explanation: An error occurred while attempting to
ANR9600E (Solaris) Failed to allocate memory for
attach a shared memory segment for a shared
shared memory communications. Error:
communications session.
error text.
System action: The shared memory communications
Explanation: An error has occurred when attempting
session does not initialize.
to get memory for the shared communications option.
User response: Check the Oracle documentation for
System action: Shared memory communications will
the shmat subroutine and determine what the errno
not be activated.
indicates, and take the appropriate action to correct the
User response: The maximum shared memory is, most error.
likely, too small. To increase on Oracle Solaris, update
"/etc/system" with "set
ANR9603E (AIX) The NETLS Nodelock file could
shmsys:shminfo_shmmax=268435456" (a recommended
not be created.
size).
Explanation: The server was not able to create the file
/usr/lib/netls/conf/nodelock which is used for storing
ANR9601E (AIX) The NETLS license interface was
license password information.
not initialized properly.
information for the server storage capacity and number User response: If the server is not running with root
of registered clients. authority, make sure that directory authorities in the
/usr/lib/netls/conf path are set so that the user ID
under which the server is running can create, read, and
write to the /usr/lib/netls/conf/nodelock file. If the
User response: Contact your service representative for server is running with root authority, contact your
assistance in resolving the error. service representative for assistance in resolving this
problem.
ANR9601E (Solaris) Failed to allocate message queue
for the shared memory communications ANR9604E (AIX) The NETLS license interface
Error: error text. encountered an internal error.
Explanation: An error has occurred when attempting Explanation: The server licensing functions
to get memory for the shared communications option. encountered an internal error in accessing license
System action: Shared memory communications will of registered clients.
not be activated.


ANR9609E (AIX) Incorrect license entered:
User response: Contact your service representative for Password entered = password
assistance in resolving the error. Annotation entered = annotation.
Explanation: The license information entered for a
ANR9605E (AIX) An invalid vendor ID was passed REGISTER LICENSE command is not correct.
to NETLS.
User response: Register the license again with the
REGISTER LICENSE command. Be sure to correctly
enter the license information.
ANR9610E (AIX) Unable to create directory: directory.
Explanation: The REGISTER LICENSE command is
unable to either create or verify the specified directory
structure.
ANR9606E (AIX) NETLS failed to find socket
families to contact a server. User response: If the server is not running with root
authority, make sure that directory authorities in the
write to the /usr/lib/netls/conf/nodelock file. If the
server is running with root authority, contact your
System action: Server operation continues. New service representative for assistance in resolving this
licensing information is not used by the server. problem.
assistance in resolving the error. ANR9610E (Linux) Unable to create directory:
directory.
ANR9607E (AIX) No NETLS Servers found. Explanation: The REGISTER LICENSE command is
unable to either create or verify the specified directory
Explanation: The server licensing functions structure.
information for the server storage capacity and number System action: None.
User response: If the server is not running with root
System action: Server operation continues. New authority, make sure that directory authorities in the
licensing information is not used by the server. given directory path are set so that the user under
which the server is running can create, read, and write
User response: Contact your service representative for to the server's license file. If the server is running with
assistance in resolving the error. root authority, contact your service representative for
assistance in resolving this problem.
ANR9608E (AIX) A NETLS Security Breach was
encountered. ANR9610E (Solaris) Unable to create directory:
Explanation: The server licensing functions directory.
encountered an internal error in accessing license Explanation: The REGISTER LICENSE command is
information for the server storage capacity and number unable to either create or verify the specified directory
of registered clients. structure.
System action: Server operation continues. New System action: None.
User response: If the server is not running with root
User response: Contact your service representative for authority, make sure that directory authorities in the
assistance in resolving the error. given directory path are set so that the user under
which the server is running can create, read, and write
to the server's license file. If the server is running with
root authority, contact your service representative for
assistance in resolving this problem.

ANR9611E (AIX) • ANR9614E (Linux)
module is only installed when you purchase the

ANR9611E (AIX) Unable to open NODELOCK file:
product.
file.
ANR9613W (Linux) Error loading modname for
unable to either create or open the nodelock file.
Licensing function.
Explanation: The server cannot load file module
User response: If the server is not running with root modname to initialize licensing functions.
System action: Server operation continues. Default
licensing values are in effect for running the server.
write to the /usr/lib/netls/conf/nodelock file. If the User response: dsmreg.lic is accessed as part of the
server is running with root authority, contact your load process for licensing. It should be in the same
service representative for assistance in resolving this directory as the dsmserv executable file or it must be in
problem. a directory that is pointed to by the DSMSERV_DIR
environment variable. The dsmreg.lic module is only
installed when you purchase the product.
ANR9612E (AIX) Error writing to NODELOCK file.
Explanation: The REGISTER LICENSE command fails
ANR9613W (Solaris) Error loading modname for
writing to the nodelock file.
Licensing function.
User response: If the server is not running with root modname to initialize licensing functions.
licensing values are in effect for running the server.
write to the /usr/lib/netls/conf/nodelock file. If the User response: dsmreg.lic is accessed as part of the
server is running with root authority, contact your load process for licensing. It should be in the same
service representative for assistance in resolving this directory as the dsmserv executable file or it must be in
problem. a directory that is pointed to by the DSMSERV_DIR
environment variable. The dsmreg.lic module is only
installed when you purchase the product.
ANR9613W (AIX) Error loading modname for
Licensing function.
ANR9614E (AIX) Unable to open license file: file.
modname to initialize licensing functions. Explanation: The REGISTER LICENSE command is
unable to create or open the server license file.
licensing values are in effect for running the server. System action: None.
User response: The dsmreg.lic module is accessed as User response: Make sure that the user ID under
part of the load process for licensing. It should be in which the server is running has the authority required
the same directory as the dsmserv executable or it must to create or write, or both, to the license file in the
be in a directory that is pointed to by the directory in which the server is running. If this does
DSMSERV_DIR environment variable. The dsmreg.lic not resolve the problem, contact your service
module is only installed when you purchase the representative for assistance.
product.
ANR9614E (Linux) Unable to open license file: file.

ANR9613W (HP-UX) Error loading modname for
Licensing function. Explanation: The REGISTER LICENSE command is
unable to either create or open the server license file.
modname to initialize licensing functions. System action: None.
System action: Server operation continues. Default User response: Make sure that the user ID under
licensing values are in effect for running the server. which the server is running has the authority required
to create or write, or both, to the license file in the
User response: The dsmreg.lic module is accessed as directory in which the server is running. If this does
part of the load process for licensing. It should be in not resolve the problem, contact your service
the same directory as the dsmserv executable or it must representative for assistance.
be in a directory that is pointed to by the
DSMSERV_DIR environment variable. The dsmreg.lic

ANR9614E (Solaris) • ANR9617I (AIX)
ANR9614E (Solaris) Unable to open license file: file. ANR9616I (AIX) Invalid license record record value
found in license file - it will be
skipped.
unable to either create or open the server license file.
Explanation: The license manager found an invalid
record in the server license file (adsmserv.licenses). The
User response: Make sure that the user ID under record is ignored.
which the server is running has the authority required
System action: The invalid record is ignored.
to create or write, or both, to the license file in the
directory in which the server is running. If this does User response: Erase the adsmserv.licenses file and
not resolve the problem, contact your service reregister your licenses.
ANR9616W (Linux) Invalid license record record value
ANR9615E (AIX) Error writing to adsmserv.licenses found in license file - it will be ignored.
file.
Explanation: The REGISTER LICENSE command fails record in the server license file (adsmserv.licenses). The
writing to the server license file. record is ignored.
System action: None. System action: The invalid record is ignored.
User response: Make sure that the user ID under User response: Erase the adsmserv.licenses file and
which the server is running has the authority required reregister your licenses. Refer to the licenses provided
to create or write, or both, to the license file in the to you to ensure that only valid licenses are specified
directory in which the server is running. Also, ensure with the REGISTER LICENSE command.
that free space is available in the file system so that the
license information can be written to the file. If this
ANR9616W (Solaris) Invalid license record record
does not resolve the problem, contact your service
value found in license file - it will be
ignored.
ANR9615E (Linux) Error writing to adsmserv.licenses
record in the server license file (adsmserv.licenses). The
file.
record is ignored.
System action: The invalid record is ignored.
writing to the server license file.
User response: Erase the adsmserv.licenses file and
reregister your licenses. Refer to the licenses provided
User response: Make sure that the userid under which to you to ensure that only valid licenses are specified
the server is running has the authority required to with the REGISTER LICENSE command.
create and/or write to the license file in the directory in
which the server is running. Also ensure that there is
ANR9617I (AIX) Invalid license authorization:
free space available in the filesystem so that the license
authorization string.
information can be written to the file. If this does not
resolve the problem contact your service representative Explanation: The license authorization specified for a
for assistance. REGISTER LICENSE command is not valid.
System action: Server operation continues; licensing
ANR9615E (Solaris) Error writing to terms are not changed by the REGISTER LICENSE
adsmserv.licenses file. command.
Explanation: The REGISTER LICENSE command fails User response: Examine the license authorization
writing to the server license file. string that was entered with the REGISTER LICENSE
command. Reenter the command if the license
authorization was not specified correctly. If the license
User response: Make sure that the userid under which authorization has been specified correctly, contact your
the server is running has the authority required to service representative.
create and/or write to the license file in the directory in
which the server is running. Also ensure that there is
free space available in the filesystem so that the license
information can be written to the file. If this does not
resolve the problem contact your service representative
for assistance.

ANR9617W (Linux) • ANR9623I (AIX)
User response: The license authorization file is

ANR9617W (Linux) Invalid license authorization:
required for formal licensing for the server. The file is
delivered when the product is purchased, but is not
Explanation: The license authorization specified for a available in the product service stream or with
REGISTER LICENSE command is not valid. demonstration copies of the server. If you have
purchased the server, please contact your service
representation for assistance in resolving this problem.
terms are not changed by the REGISTER LICENSE
command.
ANR9618E (Solaris) License registration is not
User response: Examine the license authorization that
supported on this server.
was entered using the REGISTER LICENSE command.
Reenter the command if the license authorization was Explanation: The REGISTER LICENSE command
not specified correctly. If the license authorization has failed because the license authorization module could
been specified correctly, contact your service not be found.
representative.
ANR9617W (Solaris) Invalid license authorization: command.
Explanation: The license authorization specified for a required for formal licensing for the server. The file is
REGISTER LICENSE command is not valid. delivered when the server is purchased, but is not
available in the product service stream or with
demonstration copies of the server. If you have
purchased the server, please contact your service
command.
representation for assistance in resolving this problem.
User response: Examine the license authorization that
was entered using the REGISTER LICENSE command.
ANR9622I (AIX) An EVALUATION LICENSE for
Reenter the command if the license authorization was
support of IBM Spectrum Protect for
not specified correctly. If the license authorization has
Space Management will expire on
been specified correctly, contact your service
expiration date.
representative.
Explanation: The AIX/6000 server is distributed with
an evaluation license for IBM Spectrum Protect for
ANR9618E (AIX) License registration is not
Space Management support. If no formal license is
found for the server and the evaluation period has not
Explanation: The REGISTER LICENSE command fails lapsed, this message is displayed each time the server
because the license authorization module cannot be checks the server license terms.
found.
System action: The IBM Spectrum Protect for Space
System action: Server operation continues; licensing Management license allows clients to utilize the server
terms are not changed by the REGISTER LICENSE for storing files migrated during space management.
command. The server checks this license when files are migrated
to the server from client nodes to ensure that the server
User response: The license authorization file is is licensed to perform this function.
required for formal licensing for the AIX/6000 server.
The file is delivered when the product is purchased, User response: If you are interested in using the
but it is not available in the product service stream or server, contact your service representative to obtain
with demonstration copies of the server. If you have formal licenses for the server before the evaluation
purchased the server, contact your service period has elapsed. Without formal licenses, the server
representative for assistance in resolving this problem. will not support IBM Spectrum Protect for Space
Management after the expiration date shown.
ANR9618E (Linux) License registration is not
supported on this server. ANR9623I (AIX) An EVALUATION LICENSE for
support of disaster recovery manager
Explanation: The REGISTER LICENSE command will expire on expiration date.
failed because the license authorization module could
not be found. Explanation: The AIX/6000 server is distributed with
an evaluation license for disaster recovery manager
System action: Server operation continues; licensing support. If no formal license is found for the server and
terms are not changed by the REGISTER LICENSE the evaluation period has not lapsed, this message is
command. displayed each time the server checks the server license
terms.

ANR9624E (AIX) • ANR9624I (Windows)
System action: The disaster recovery manager license will not support IBM Spectrum Protect for Space
allows customers to store information in the server Management after the expiration date shown.
regarding machines and recovery media, allows
management of offsite recovery media, collects and
ANR9624I (Linux) An EVALUATION LICENSE for
stores information in the server for server recovery and
allows data base and storage pool backups to a device
class of type server. The server checks this license when
expiration date.
machines or recovery media are defined to the server,
when PREPARE or MOVE DRMMEDIA are invoked Explanation: The server is distributed with an
and when a data base backup or storage pool backup evaluation license for IBM Spectrum Protect for Space
to a device class of type server are performed to ensure Management support. If no formal license is found for
that the server is licensed to perform this function. the server and the evaluation period has not lapsed,
this message is displayed each time the server checks
User response: If you are interested in using the
the server license terms.
server, contact your service representative to obtain
formal licenses for the server before the evaluation System action: The IBM Spectrum Protect for Space
period has elapsed. Without formal licenses, the server Management license allows clients to utilize the server
will not support disaster recovery manager after the for storing files migrated during space management.
expiration date shown. The server checks this license when files are migrated
is licensed to perform this function.
ANR9624E (AIX) Unexpected error encountered in
iFor/LS (SystemView License Use User response: If you are interested in using the
Management) routine license interface server, contact your service representative to obtain
name status=xreported status code. formal licenses for the server before the evaluation
period has elapsed. Without formal licenses, the server
Explanation: The server encountered an unexpected
will not support IBM Spectrum Protect for Space
error in accessing the SystemView License Use
Management function specified.
System action: The server license monitoring
ANR9624I (Solaris) An EVALUATION LICENSE for
operation fails
User response: The SystemView License Use Space Management will expire on
Management product is installed during normal AIX expiration date.
server installation. Check to make sure that server was
Explanation: The server is distributed with an
installed correctly. If the installation was successful,
evaluation license for IBM Spectrum Protect for Space
re-boot your AIX system and re-start the server. If this
Management support. If no formal license is found for
message continues to be issued, contact your service
the server and the evaluation period has not lapsed,
representative.
ANR9624I (HP-UX) An EVALUATION LICENSE for
Management license allows clients to utilize the server
for storing files migrated during space management.
expiration date.
The server checks this license when files are migrated
Explanation: The server is distributed with an to the server from client nodes to ensure that the server
evaluation license for IBM Spectrum Protect for Space is licensed to perform this function.
formal licenses for the server before the evaluation
System action: The IBM Spectrum Protect for Space will not support IBM Spectrum Protect for Space
Management license allows clients to utilize the server Management after the expiration date shown.
ANR9624I (Windows) An EVALUATION LICENSE
for support of IBM Spectrum Protect for
User response: If you are interested in using the expiration date.
evaluation license for IBM Spectrum Protect for Space

ANR9625E (AIX) • ANR9625I (Solaris)

ANR9625I (Linux) An EVALUATION LICENSE for
support of disaster recovery manager
will expire on expiration date.
Management license allows clients to utilize the server
evaluation license for disaster recovery manager
support. If no formal license is found for the server,
and the evaluation period has not lapsed, this message
is displayed each time the server checks the server
license terms.
System action: The disaster recovery manager license
allows customers to store information in the server
regarding machines and recovery media, allows
management of offsite recovery media, collects and
will not support IBM Spectrum Protect for Space
stores information in the server for server recovery, and
allows data base and storage pool backups to a device
class of type server. The server checks this license when
ANR9625E (AIX) Could not open file file name. machines or recovery media are defined to the server,
when PREPARE or MOVE DRMMEDIA are invoked,
Explanation: The server could not open the license and when a data base backup or storage pool backup
certificate file specified. to a device class of type server are performed to ensure
System action: The license registration command fails. that the server is licensed to perform this function.
User response: Examine the file specification entered, User response: If you are interested in using the
including wildcard characters, to determine if it names server, contact your service representative to obtain
the license certificate file(s) you intended to use. If an formal licenses for the server before the evaluation
error is found, re-try the command with the corrected period has elapsed. Without formal licenses, the server
specification. If an error cannot be found, contact your will not support disaster recovery manager after the
service representative. expiration date shown.
ANR9625I (HP-UX) An EVALUATION LICENSE for ANR9625I (Solaris) An EVALUATION LICENSE for
support of disaster recovery manager support of disaster recovery manager
will expire on expiration date. will expire on expiration date.
Explanation: The server is distributed with an Explanation: The server is distributed with an
evaluation license for disaster recovery manager evaluation license for disaster recovery manager
support. If no formal license is found for the server and support. If no formal license is found for the server and
the evaluation period has not lapsed, this message is the evaluation period has not lapsed, this message is
displayed each time the server checks the server license displayed each time the server checks the server license
terms. terms.
System action: The disaster recovery manager license System action: The disaster recovery manager license
allows customers to store information in the server allows customers to store information in the server
regarding machines and recovery media, allows regarding machines and recovery media, allows
management of offsite recovery media, collects and management of offsite recovery media, collects and
stores information in the server for server recovery and stores information in the server for server recovery and
allows data base and storage pool backups to a device allows data base and storage pool backups to a device
class of type server. The server checks this license when class of type server. The server checks this license when
machines or recovery media are defined to the server, machines or recovery media are defined to the server,
when PREPARE or MOVE DRMMEDIA are invoked when PREPARE or MOVE DRMMEDIA are invoked
and when a data base backup or storage pool backup and when a data base backup or storage pool backup
to a device class of type server are performed to ensure to a device class of type server are performed to ensure
that the server is licensed to perform this function. that the server is licensed to perform this function.
User response: If you are interested in using the User response: If you are interested in using the
server, contact your service representative to obtain server, contact your service representative to obtain
formal licenses for the server before the evaluation formal licenses for the server before the evaluation
period has elapsed. Without formal licenses, the server period has elapsed. Without formal licenses, the server
will not support disaster recovery manager after the will not support disaster recovery manager after the
expiration date shown. expiration date shown.

ANR9625I (Windows) • ANR9631E (Windows)
specified for the file. If the problem persists after these

ANR9625I (Windows) An EVALUATION LICENSE
corrections have been made, contact your service
for support of disaster recovery manager
representative.
will expire on expiration date.
ANR9628E (Windows) Unexpected error encountered
evaluation license for disaster recovery manager
in iFor/LS (SystemView License Use
support. If no formal license is found for the server and
Management) routine license interface
the evaluation period has not lapsed, this message is
name status=xreported status code.
displayed each time the server checks the server license
terms. Explanation: The server encountered an unexpected
error in accessing the SystemView License Use
System action: The disaster recovery manager license
allows customers to store information in the server
regarding machines and recovery media, allows System action: The server license monitoring
management of offsite recovery media, collects and operation fails
stores information in the server for server recovery and
allows data base and storage pool backups to a device User response: The SystemView License Use
class of type server. The server checks this license when Management product is installed during normal server
machines or recovery media are defined to the server, installation. Check to make sure that the product was
when PREPARE or MOVE DRMMEDIA are invoked installed correctly. If the installation was successful,
and when a data base backup or storage pool backup re-boot your system and re-start the server. If this
to a device class of type server are performed to ensure message continues to be issued, contact your service
that the server is licensed to perform this function. representative.

server, contact your service representative to obtain ANR9629E (Windows) Could not open file file name.
formal licenses for the server before the evaluation Explanation: The server could not open the license
period has elapsed. Without formal licenses, the server certificate file specified.
will not support disaster recovery manager after the
expiration date shown. System action: The license registration command fails.
User response: Examine the file specification entered,
ANR9626E (AIX) Invalid license certificate file: file including wildcard characters, to determine if it names
name. the license certificate file(s) you intended to use. If an
error is found, re-try the command with the corrected
Explanation: The specified file does not contain valid specification. If an error cannot be found, contact your
license certificate information. service representative.
System action: The license registration command
ignores the contents of the file. ANR9630E (Windows) Invalid license certificate file:
User response: Examine the file specification entered, file name.
including wildcard characters, to determine if it names Explanation: The specified file does not contain valid
the license certificate file(s) you intended to use. If an license certificate information.
specification. If an error cannot be found, contact your System action: The license registration command
service representative. ignores the contents of the file.
ANR9627E (AIX) Cannot access node license lock including wildcard characters, to determine if it names
file: file name. the license certificate file(s) you intended to use. If an
Explanation: The server was not able to access the specification. If an error cannot be found, contact your
specified file. The node lock file contains licensing service representative.
information for the server.
System action: The license function fails. ANR9631E (Windows) Cannot access node license
User response: Examine the file specification lock file: file name.
displayed and ensure that the file attributes will allow Explanation: The server was not able to access the
the server to access the file. The location of the file is specified file. The node lock file contains licensing
either in the directory from which the server is started, information for the server.
or in the directory specified by the DSMSERV_DIR
environment variable. Re-specify the DSMSERV_DIR System action: The license function fails.
environment variable if this specification is in error. User response: Examine the file specification
Also ensure that there is sufficient space on the drive

ANR9632I (Windows) • ANR9635E (HP-UX)
displayed and ensure that the file attributes will allow User response: Examine the file specification entered,
the server to access the file. The location of the file is including wildcard characters, to determine if it names
either in the directory from which the server is started, the license certificate file(s) you intended to use. If an
or in the directory specified by the DSMSERV_DIR error is found, re-try the command with the corrected
environment variable. Re-specify the DSMSER-DIR specification. If an error cannot be found, contact your
environment variable if this specification is in error. service representative.
ANR9634E (Linux) command name: No license
certificate files were found with the file
representative.
name specification specification.
Explanation: The server did not find any license
ANR9632I (Windows) Cannot load licensing DLL
certificate file(s) with the file name specification
library: DLL file name : the server will
entered.
assume evaluation licensing mode.
System action: The license registration command fails.
Explanation: The server was not able to load the
specified dynamic link library. User response: Examine the file specification entered,
including wildcard characters, to determine if it names
System action: Server licensing asumes Try and Buy
the license certificate file(s) you intended to use. If an
mode with licenses for 180 days.
User response: The named DLL library(ies) are specification. If an error cannot be found, contact your
required for the server to support feature licensing. If service representative.
you are running an evaluation copy of the server, this
message should not cause concern and is normal. If the
ANR9634E (Solaris) command name: No license
libraries are installed and this message continues to be
issued, contact a support representative for assistance.
ANR9634E (AIX) command name: No license certificate
files were found with the file name
entered.
specification specification.
certificate file(s) with the file name specification User response: Examine the file specification entered,
entered. including wildcard characters, to determine if it names
User response: Examine the file specification entered, specification. If an error cannot be found, contact your
including wildcard characters, to determine if it names service representative.
the license certificate file(s) you intended to use. The
file name specification indicates the fully qualified file
ANR9634E (Windows) command name: No license
name the server was trying to read. The directory used
to locate the license certificate files when no explicit
path is provided is determined as follows:
v The directory path pointed by the environmental Explanation: The server did not find any license
variable DSMSERV_DIR if this variable is defined certificate file(s) with the file name specification
entered.
v The current working directory of the server process if
the DSMSERV_DIR variable is not defined System action: The license registration command fails.
If an error is found, re-try the command with the User response: Examine the file specification entered,
corrected specification. If an error cannot be found, including wildcard characters, to determine if it names
contact your service representative. the license certificate file(s) you intended to use. If an
specification. If an error cannot be found, contact your
ANR9634E (HP-UX) command name: No license
ANR9635E (HP-UX) Invalid license certificate file:
file name.
entered. Explanation: The specified file does not contain valid
license certificate information.

ANR9635E (Linux) • ANR9637E (HP-UX)
System action: The license registration command User response: Examine the file specification entered,
ignores the contents of the file. including wildcard characters, to determine if it names
service representative. ANR9636E (Linux) Could not open file file name.
Explanation: The server could not open the license
ANR9635E (Linux) Invalid license certificate file: file certificate file specified.
name.
Explanation: The specified file does not contain valid
System action: The license registration command the license certificate file(s) you intended to use. If an
ignores the contents of the file. error is found, re-try the command with the corrected
error is found, re-try the command with the corrected ANR9636E (Solaris) Could not open file file name.
certificate file specified.
ANR9635E (Solaris) Invalid license certificate file: file
name. User response: Examine the file specification entered,
System action: The license registration command specification. If an error cannot be found, contact your
ignores the contents of the file. service representative.
including wildcard characters, to determine if it names ANR9636E (Windows) Could not open file file name.
service representative. System action: The license registration command fails.
ANR9635E (Windows) Invalid license certificate file: including wildcard characters, to determine if it names
file name. the license certificate file(s) you intended to use. If an
System action: The license registration command
ignores the contents of the file.
ANR9637E (HP-UX) Cannot access node license lock
User response: Examine the file specification entered, file: file name.
Explanation: The server was not able to access the
specified file. The node lock file contains licensing
service representative. System action: The license function fails.
User response: Examine the file specification
ANR9636E (HP-UX) Could not open file file name. displayed and ensure that the file attributes will allow
the server to access the file. The location of the file is
either in the directory from which the server is started,
System action: The license registration command fails. environment variable. Re-specify the DSMSERV_DIR

ANR9637E (Linux) • ANR9638W (Solaris)
environment variable if this specification is in error. Also ensure that there is sufficient space on the drive
Also ensure that there is sufficient space on the drive specified for the file. If the problem persists after these
specified for the file. If the problem persists after these corrections have been made, contact your service
corrections have been made, contact your service representative.
representative.
ANR9638W (HP-UX) License registration is not
ANR9637E (Linux) Cannot access node license lock supported on this server.
file: file name.
Explanation: The server was not able to access the because the license authorization module cannot be
specified file. The node lock file contains licensing found.
System action: The license function fails. terms are not changed by the REGISTER LICENSE
command.
displayed and ensure that the file attributes will allow User response: The license authorization file is
the server to access the file. The location of the file is required for formal licensing for the HP-UX server. The
either in the directory from which the server is started, file is delivered when the server is purchased, but it is
or in the directory specified by the DSMSERV_DIR not available in the product service stream or with
environment variable. Re-specify the DSMSERV-DIR demonstration copies of the server. If you have
environment variable if this specification is in error. purchased the server, contact your service
Also ensure that there is sufficient space on the drive representative for assistance in resolving this problem.
ANR9638W (Linux) License registration is not
representative.
ANR9637E (Solaris) Cannot access node license lock
because the license authorization module cannot be
file: file name.
found.
command.
System action: The license function fails.
User response: Examine the file specification required for formal licensing for the server. The file is
displayed and ensure that the file attributes will allow delivered when the product is purchased, but it is not
the server to access the file. The location of the file is available in the product service stream or with
either in the directory from which the server is started, demonstration copies of the server. If you have
or in the directory specified by the DSMSERV_DIR purchased the server, contact your service
environment variable. Re-specify the DSMSERV-DIR representative for assistance in resolving this problem.
environment variable if this specification is in error.
ANR9638W (Solaris) License registration is not
representative. Explanation: The REGISTER LICENSE command fails
because the license authorization module cannot be
found.
ANR9637E (Windows) Cannot access node license
lock file: file name. System action: Server operation continues; licensing
command.
information for the server. User response: The license authorization file is
required for formal licensing for the Oracle Solaris
server. The file is delivered when the server is
User response: Examine the file specification purchased, but it is not available in the product service
displayed and ensure that the file attributes will allow stream or with demonstration copies of the server. If
the server to access the file. The location of the file is you have purchased the server, contact your service
either in the directory from which the server is started, representative for assistance in resolving this problem.
environment variable. Re-specify the DSMSER-DIR

ANR9638W (Windows) • ANR9641W (HP-UX)
ANR9638W (Windows) License registration is not ANR9640E (HP-UX) Unable to load procedure
supported on this server. address from shared library shared
library.
because the license authorization module cannot be Explanation: The server module is unable to load the
found. address of a routine in the indicated shared library.
System action: Server operation continues; licensing System action: Server operation continues, but the
terms are not changed by the REGISTER LICENSE function that requires the shared library will be
command. inoperative.
User response: The license authorization file is User response: Ensure that the shared library is
required for formal licensing for the Windows server. accessible. If the problem persists, contact your service
The file is delivered when the product is purchased, representative.
but it is not available in the product service stream or
with demonstration copies of the server. If you have
ANR9640E (Linux) Unable to load procedure address
purchased the server, contact your service
from shared library shared library license
representative for assistance in resolving this problem.
module.
Explanation: The server module is unable to load the
ANR9639W (HP-UX) Unable to load shared library
address of a routine in the indicated shared library for
shared library.
license loading.
indicated shared library.
function that requires the shared library will be
System action: Server operation continues, but the inoperative.
User response: Ensure that the shared library is
inoperative.
accessible. If the problem persists, contact your
User response: Ensure that the shared library is Customer Service Representative.
accessible. If this is an evaluation copy of the server,
then this message is normal for the DSMREG library,
ANR9640E (Solaris) Unable to load procedure
since the library is only provided with purchased
address from shared library shared library
servers. The server licensing will assume "Try and Buy"
license module.
mode with sample licensed options for a period of
time. Explanation: The server module is unable to load the
address of a routine in the indicated shared library for
license loading.
ANR9639W (Linux) Unable to load Shared License
File shared library. System action: Server operation continues, but the
Explanation: The server was unable to loaded the
inoperative.
shared library.
User response: Ensure that the shared library is
accessible. If the problem persists, contact your
functions that require the shared library will be
customer service representative.
inoperative.
User response: Make sure the shared library is
ANR9641W (HP-UX) One or more EVALUATION
accessible/readable. This message is normal for those
LICENSES will expire on expiration date.
servers in the Try-N-Buy mode.
Explanation: Although you are running with a
purchased version of the server, there are one or more
ANR9639W (Solaris) Unable to load Shared License
licenses registered that will expire on the date specified.
File shared library.
This is usually the case when you have been using
Explanation: The server was unable to loaded the evaluation licenses prior to purchasing the product.
shared library.
User response: Halt the server and erase the nodelock
functions that require the shared library will be
file in the server startup directory. After restarting the
inoperative.
server, use the REGISTER LICENSE command to define
User response: Make sure the shared library is the licensed features that you have purchased with
accessible/readable. This message is normal for those your server. These licenses should NOT have an
servers in the Try and Buy mode. expiration date, so this message should not appear after

ANR9641W (Linux) • ANR9654E (Solaris)
re-registering the proper licenses. If this message

ANR9653E (HP-UX) Unexpected error encountered in
iFor/LS (SystemView License Use
Management) routine license interface
ANR9641W (Linux) One or more EVALUATION name status=xreported status code.
Explanation: The server encountered an unexpected
System action: Server operation continues. error in accessing the SystemView License Use
file in the server startup directory. After restarting the System action: The server license monitoring
server, use the REGISTER LICENSE command to define operation fails
the licensed features that you have purchased with
User response: The SystemView License Use
your server. These licenses should NOT have an
Management product is installed during normal AIX
expiration date, so this message should not appear after
re-boot your AIX system and re-start the server. If this
message continues to be issued, contact your service
ANR9641W (Solaris) One or more EVALUATION representative.
System action: Server operation continues. ANR9653E (Solaris) Unexpected error encountered in
iFor/LS (SystemView License Use
User response: Halt the server and erase the nodelock Management) routine license interface
file in the server startup directory. After restarting the name status=xreported status code.
server, use the REGISTER LICENSE command to define
the licensed features that you have purchased with Explanation: The server encountered an unexpected
your server. These licenses should NOT have an error in accessing the SystemView License Use
expiration date, so this message should not appear after Management function specified.
System action: The server license monitoring
operation fails
User response: The SystemView License Use
ANR9642E (HP-UX) The specified license
Management product is installed during normal AIX
authorization code (license authorization
code) is invalid.
Explanation: The license authorization code which re-boot your AIX system and re-start the server. If this
you entered using the REGISTER LICENSE command is message continues to be issued, contact your service
invalid. representative.
System action: No additional licenses are registered.
Server operation continues. ANR9654E (HP-UX) Could not open file file name.
User response: Obtain a valid license authorization Explanation: The server could not open the license
code and try the command again. certificate file specified.
ANR9642E (Linux) The specified license
authorization code (license authorization
code) is invalid.
Explanation: The license authorization code which error is found, re-try the command with the corrected
you entered using the REGISTER LICENSE command is specification. If an error cannot be found, contact your
invalid. service representative.
System action: No additional licenses are registered.

Server operation continues. ANR9654E (Solaris) Could not open file file name.
User response: Obtain a valid license authorization Explanation: The server could not open the license
code and try the command again. certificate file specified.

error is found, re-try the command with the corrected System action: The license function fails.
displayed and ensure that the file attributes will allow
the server to access the file. The location of the file is
ANR9655E (HP-UX) Invalid license certificate file: either in the directory from which the server is started,
file name. or in the directory specified by the DSMSERV_DIR
environment variable. Re-specify the DSMSERV_DIR
System action: The license registration command specified for the file. If the problem persists after these
ignores the contents of the file. corrections have been made, contact your service
representative.
the license certificate file(s) you intended to use. If an ANR9676E (AIX) Error errno attaching memory
error is found, re-try the command with the corrected segment for shared memory
specification. If an error cannot be found, contact your communications.
ANR9655E (Solaris) Invalid license certificate file: file communications session.
name.
System action: The shared memory communications
Explanation: The specified file does not contain valid session does not initialize.
User response: Check the AIX documentation for the
System action: The license registration command shmat subroutine and determine what the error
ignores the contents of the file. number indicates. On AIX, if the error number is
EMFILE, make sure the EXTSHM environment variable
User response: Examine the file specification entered, is set to ON before starting the server. This allows the
including wildcard characters, to determine if it names server to support more than 3 concurrent shared
the license certificate file(s) you intended to use. If an memory sessions.
service representative. ANR9676E (HP-UX) Error errno attaching memory
segment for shared memory
communications.
ANR9656E (HP-UX) Cannot access node license lock
file: file name. Explanation: An error occurred while attempting to
Explanation: The server was not able to access the communications session.
information for the server. System action: The shared memory communications
session does not initialize.
User response: Examine the file specification shmat subroutine and determine what the error
displayed and ensure that the file attributes will allow number indicates. On AIX, if the error number is
the server to access the file. The location of the file is EMFILE, make sure the EXTSHM environment variable
either in the directory from which the server is started, is set to ON before starting the server. This allows the
or in the directory specified by the DSMSERV_DIR server to support more than 3 concurrent shared
environment variable. Re-specify the DSMSERV_DIR memory sessions.
specified for the file. If the problem persists after these ANR9676E (Linux) Error errno attaching memory
corrections have been made, contact your service segment for shared memory
representative. communications.
ANR9656E (Solaris) Cannot access node license lock attach a shared memory segment for a shared
file: file name. communications session.
Explanation: The server was not able to access the System action: The shared memory communications
specified file. The node lock file contains licensing session does not initialize.

ANR9677E (AIX) • ANR9680W (AIX)
shmat subroutine and determine what the error

ANR9678E (Linux) Failed to allocate message queue
number indicates. On AIX, if the error number is
for the shared memory communications
EMFILE, make sure the EXTSHM environment variable
Error: error text.
is set to ON before starting the server. This allows the
server to support more than 3 concurrent shared Explanation: An error has occurred when attempting
memory sessions. to get memory for the shared communications option.
ANR9677E (AIX) Failed to allocate memory for not be activated.
error text.
ANR9678W (Windows) File name used for server
executable. A server is currently running
System action: Shared memory communications will as a service.
not be activated.
Explanation: The name of the executable used when
the server is running as a service cannot be used in the
ANR9677E (HP-UX) Failed to allocate memory for plan file.
System action: PREPARE uses file name identified in
error text.
the message within the plan file and generation of the
Explanation: An error has occurred when attempting plan file continues.
not be activated.
ANR9679W (AIX) Command: The file file name cannot
User response: None. be found.
ANR9677E (Linux) Failed to allocate memory for
the PREPARE command uses /opt/IBMadsm-s/bin/
error text.
dsmserv.
and create it if necessary.
not be activated.
ANR9679W (Windows) Command: Unable to locate
User response: None. file file name.
ANR9678E (AIX) Failed to allocate message queue
System action: PREPARE uses the following default
for the shared memory communications
file names in the plan file:
Error: error text.
v For the server executable the default is
Explanation: An error has occurred when attempting c:\progra~1\tivoli\tsm\server\dsmserv.
System action: Shared memory communications will create if necessary.
not be activated.
ANR9680W (AIX) Command: Could not obtain AIX

ANR9678E (HP-UX) Failed to allocate message queue logical volume information for volume
for the shared memory communications name while building stanza recovery plan
Error: error text. stanza name.
Explanation: An error has occurred when attempting Explanation: This volume is defined to the server but
to get memory for the shared communications option. PREPARE can not obtain AIX logical volume
System action: Shared memory communications will information for it from the AIX Object Data Manager
not be activated. (ODM).
User response: None. System action: The entry for the volume is not
included in the recovery plan stanza.
User response: This message should be preceded by

ANR9680W (HP-UX) • ANR9683E (AIX)
another error message which contains the ODM error

ANR9681W (Windows) Command: Volume file name
code.
not found while building stanza recovery
plan stanza name.
ANR9680W (HP-UX) Command: Could not obtain
logical volume information for volume
does not exist. The device class associated with the
name while building stanza recovery plan
volume is DISK or the device class device type is FILE.
stanza name.
PREPARE can not obtain logical volume information
for it. User response: Determine why file does not exist;
create if necessary.
ANR9682E (AIX) Command: Generated file name too
User response: This message should be preceded by
long. Length of directory or prefix
another error message which contains an error code.
'prefix' plus 'name' exceeds maximum
ANR9680W (Solaris) Command: Could not obtain
Explanation: The file name generated is too long. The
logical volume information for volume
name while building stanza recovery plan
stanza name. System action: The recovery plan file was not created.
Explanation: This volume is defined to the server but User response: Reissue the command specifying a
PREPARE can not obtain logical volume information valid prefix. The following commands are used to
for it. specify the prefix:
System action: The entry for the volume is not v SET DRMPLANPREFIX
included in the recovery plan stanza. v SET DRMINSTRPREFIX
User response: This message should be preceded by v PREPARE
another error message which contains an error code.
ANR9682E (Windows) Command: Generated file
ANR9680W (Windows) Unable to locate path for name too long. Length of directory or
component in registry. prefix 'prefix' plus 'name' exceeds
Explanation: The path to the component could not be
found in the registry. Explanation: The file name generated is too long. The
System action: PREPARE uses the following default
path names in the plan file: System action: The recovery plan file was not created.
v For the components installation directory the default User response: Reissue the command specifying a
is c:\progra~1\tivoli\tsm\server\ valid prefix. The following commands are used to
v For the administrative command line client the specify the prefix:
default is c:\progra~1\tivoli\tsm\baclient\ v SET DRMPLANPREFIX
v For the disk formatting utility the default is v SET DRMINSTRPREFIX
c:\progra~1\tivoli\tsm\utils\ v PREPARE
User response: Determine why path does not exist;
install components if necessary. ANR9683E (AIX) Command: Cannot generate fully
qualified file name for 'name'.
ANR9681W (AIX) Command: Volume file name not Explanation: A failure occurred expanding the
found while building stanza recovery specified file name.
plan stanza name.
does not exist. The device class associated with the User response: Reissue the command specifying a
volume is DISK or the device class device type is FILE. valid prefix. The following commands are used to
specify the prefix:
v SET DRMPLANPREFIX
User response: Determine why the file does not exist;
v PREPARE
create it if necessary.

ANR9683E (Windows) • ANR9756I
ANR9683E (Windows) Command: Cannot generate ANR9686E (AIX) Command: Cannot generate a device
fully qualified file name for 'name'. configuration file name.
Explanation: A failure occurred expanding the Explanation: A failure occurred generating the device
specified file name. configuration file name.
System action: Recovery plan file not created. System action: Recovery plan file not created.
User response: Reissue the command specifying a User response: See accompanying messages for more
valid prefix. The following commands are used to information.
specify the prefix:
v SET DRMPLANPREFIX ANR9686E (Windows) Command: Cannot generate a
v SET DRMINSTRPREFIX device configuration file name.
v PREPARE Explanation: A failure occurred generating the device
configuration file name.
ANR9684E (AIX) Command: Cannot generate server System action: Recovery plan file not created.
options file name.
User response: See accompanying messages for more
Explanation: A failure occurred generating the server information.
options file name.
System action: Recovery plan file not created. ANR9687W (Windows) Cannot load the Microsoft
User response: See accompanying messages for more dll NTMSAPI.DLL. Removable Media
information. Support will not be available.
Explanation: The Microsoft dll NTMSAPI.DLL is
ANR9684E (Windows) Command: Cannot generate required for removable media. It is usually found in the
server options file name. Windows System32 directory but can be removed if the
Windows feature called Removable Media is turned off.
Explanation: A failure occurred generating the server In Windows 2008, Removable Media is off by default.
options file name.
User response: Ignore this message if storing to a
User response: See accompanying messages for more drive or turn on the Removable Media feature in
information. Windows.
ANR9685E (AIX) Command: Cannot generate a ANR9751E The volume in drive 'drive name' is not
volume history file name. compatible with the drive.
Explanation: A failure occurred generating the volume Explanation: The volume cannot be used in the drive.
history file name. It is most likely an outdated media type that the drive
System action: Recovery plan file not created. cannot write.
User response: See accompanying messages for more System action: The volume is not labeled.
information. User response: Remove the volume; replace it with a
different type known to work in the drive, or press
ANR9685E (Windows) Command: Cannot generate a ENTER to end the program.
Explanation: A failure occurred generating the volume ANR9756I No volumes were found.
history file name. Explanation: No volumes are found in the library.
System action: Recovery plan file not created. This means that in a 349x ATL, no volumes were found
in the insert category (xFF00), and that in a SCSI
User response: See accompanying messages for more autochanger, no cartridges were loaded into the library.
information.
System action: The program terminates normally.
User response: Insert cartridges into the library. For a
349x ATL, this may involve changing the category of
previously inserted cartridges to be relabeled.

volume, or swap the barcode label with a label of the

ANR9757E SAN discovery is unable to complete.
opposite WORM characteristic (WORM for non-WORM
Explanation: SAN discovery will not complete if a or vice versa) and retry the check in command.
drive serial number is not specified.
System action: None. ANR9774W Volume volume name should be freed of
data as soon as possible.
User response: Check the library configuration with
the IBM Tape Diagnostic Tool (ITDT) or lbtest utility. Explanation: The server has received an indication
Ensure that the element addresses of the tape drives are from the 3995 that the indicated volume is out of spare
configured correctly in the tape library, and verify that sectors for re-allocation. Spare sectors are reserved to
all of the tape drives exist in the library with their take the place of sectors that experience I/O problems.
serial number. If there is an existing tape drive without The re-allocation can take place on either a read or
a serial number, contact the library vendor for write.
assistance.
System action: The indicated volume is marked
read-only by the server.
ANR9758W Error mounting volume 'volume name'.
User response: A MOVE DATA command should be
Explanation: An error occurs while mounting the used as soon as possible to move the data from this
volume to the drive. This may not be an error since the cartridge to other cartridges in the library. This
volume or drive maybe in use or locked in a shared cartridge should NOT be marked read-write again
environment. through the UPDATE VOLUME command.
System action: The specified volume is bypassed for
labeling. ANR9775E Error while writing on volume volume
name (RC=internal code).
User response: Ensure that the volume is not locked
or in use if label is required. Explanation: An I/O error has occurred while writing
on the specified volume.
ANR9761E The path of drive drive name in library System action: The operation fails.
library name has been changed from
User response: Ensure that the 3995 volume is
original drive path to new drive path The
accessible and that the media is usable. Diagnostics
new path will not be updated because
may have to be run on the 3995 with the specified
we can not get the model type using
volume. If the problem persists, contact your service
new path.
representative and provide the internal code values
Explanation: The drive's new path can not be updated from this message. The internal code is returned to the
because we detect a different device type compared to server from the OS/2 operating system.
the Database using this new path. The problem may be
the new path has an incorrect format for the device
ANR9776I File file name is being erased and
driver.
deleted. Data erasure may take several
System action: . minutes.
User response: The user needs to check if there are Explanation: A file is being deleted from an optical
two device special file names for the same drive. For library cartridge. The file is deleted when a LAN3995
AIX, please make sure the IBM drive is /dev/rmt and device class volume is deleted. File deletion includes
IBM Spectrum Protect drive is /dev/mt. For Solaris, erasure of data. The erasure process can take several
please make sure the Solaris native device driver is not minutes to complete.
installed.
ANR9771E Volume volume name has an incorrect
barcode label describing the volume's
WORM type. ANR9778E Unable to establish a communication
session with the primary library
Explanation: In an attempt to CHECKIN or LABEL a
manager.
volume it was discovered that the volume's true
WORM characteristic didn't match that described by its Explanation: The requested operation required that a
barcode label. communication session be established with a library
manager. The library manager was found to be
System action: The volume is not checked in.
unavailable at this time.
User response: The volume was probably mislabeled.
Find the volume in the library. Simply remove the

User response: Verify the primary library manager is User response: Define the server to this server using
up and operational. Once the server is verified to be the DEFINE SERVER command.
operational, retry the operation.
ANR9783E Primary Library Manager does not
ANR9779E Unable to acquire a drive for volume contain a valid value.
volume name from the library manager.
Explanation: The primary library manager server has
Explanation: The library manager was unable to not be defined to this server.
assign a drive to the library client. There are a couple
of situations that can cause this error.
v All drives are currently allocated to other library User response: Define the server to this server using
clients or the library manager. the DEFINE SERVER command.
v The request for a specific drive cannot be satisfied.
This can occur if a drive on the library client side is ANR9784E Secondary Library Manager secondary
marked offline or is currently busy with another library manager name is NOT defined as a
process. server.
v A communication error occurred during the request Explanation: The secondary library manager server
to mount a volume. name has not be defined to this server.
v The requested volume was not present in the library
manager's inventory System action: None.
System action: None. User response: Define the server to this server using
the DEFINE SERVER command.
User response: Verify that a drive is available on the
library manager side and the drive is currently not
busy or marked offline on the library client. Set the ANR9785E Drive drive name, is not defined on the
mount retention on the device class on the library library manager.
manager and the library clients to a lower value. Using Explanation: A drive is being defined that does not
a lower mount retention value can free up drives. exist or is being managed by the library manager.
ANR9780E Volume volume name is not mounted in
drive from the library drive name. User response: Verify drive name with the library
manager.
Explanation: A communication error occurred while
dismount the volume.
ANR9786E A communication error has occurred.
System action: None. Operation ending.
User response: Verify the library manager is up and Explanation: A communication error occurred.
operational. Verify that the library manager and library
client can communicate using command routing. System action: None.
User response: Verify the library manager is up and
ANR9781E Volser volume name was not found to be operational. Verify that the library manager and library
mounted on the library manager. client can communicate using command routing.
Explanation: According to the library manager the

requested volume is no longer mounted. The can ANR9787E The owner name specified is not
occurred if the library manager forced the volume to be defined to this server.
dismounted because of a communication error. Explanation: A command was issued specifying
System action: None. ownership of a volume. The name of the owner given
was not defined to this server.
User response: Verify that the volume has been
dismounted. System action: None.
User response: Define the server to this server using
ANR9782E Primary Library Manager primary library the DEFINE SERVER command.
manager name is NOT defined as a
server.
Explanation: The primary library manager server has
not be defined to this server.

shared, update the library shared status to yes.

defined - the primary library manager
not defined. ANR9793I process name in library library name-
CANCEL PENDING.
Explanation: The designated library is not defined
because the primary library manager is not defined as a Explanation: In response to a QUERY PROCESS
server to this server. command, this message displays the status for a
process on the server. The command was started, but
the process was canceled by an administrator.
System action: The background process operation is
being terminated.
defined - the secondary library manager
not defined. ANR9794E Unable to load the RSM dynamic link
library dynamic link library.
Explanation: The designated library is not defined
because the secondary library manager is not defined Explanation: The server module is unable to load the
as a server to this server. indicated dynamic link library.
System action: The command is not processed. System action: Server operation continues, but the
function that requires the dynamic link library will be
inoperative.
User response: Ensure that the installed Windows
version supports RSM. Ensure that the Removable
ANR9790W Request to mount volume Volume Name
Storage Manager is installed and the system DLL is
for library client Library Client Name
accessible.
failed.
Explanation: A library client requested a volume to be
ANR9795E Command: Invalid storage agent name
mount by the library manager, which in turn failed.
storage agent name.
Explanation: The designated storage agent name is
User response: Verify the status of all drives are invalid; either it contains too many characters, or some
currently online and not in use by other library clients of the characters are invalid.
or the library manager itself. Free up drive resources as
needed.
User response: Reissue the command using a valid
storage agent name.
ANR9791I Volume Volume Name in library Library
Name ownership is changing from
Current volume owner to New Volume ANR9796E Command: Drive mapping is already
owner. defined for drive drive name in library
library name on storage agent storage agent
Explanation: In a shared library, the volume
name.
ownership has been changed from current owner to
new owner. Explanation: The designated drive mapping cannot be
defined because it has already been defined for the
specified drive, library, and storage agent.
User response: If you want to define an additional
ANR9792E Library Library Name on library manager
drive mapping, reissue the command with a different
Library Manager Name is currently not
drive name.
being shared.
Explanation: A define library command attempted to
ANR9797E Command: Drive mapping for drive drive
define a shared library that was not being shared by
name is not defined in library library
the library manager.
name on storage agent storage agent name.
Explanation: The designated drive map has not been
User response: Verify the library on the library defined for the given drive in the given library on the
manager is being shared. If the library is not being given storage agent.

ANR9798E • ANR9900W (Linux)
System action: The command is not processed. driver is not available to process requests from the
server.
drive name. If appropriate, define the drive before User response: For minimum storage requirements,
retrying the command. refer to Licensed Program Specifications/2. You must have
sufficient memory in your system to initialize Windows
and the device drivers you want to use.
ANR9798E Command: One or more paths are still
defined for drive drive name in library
library name. ANR9810I (Windows) ANR9810: SCSI Tape Device
Driver Initializing...
Explanation: The designated drive cannot be deleted
because there are still paths defined for it. Explanation: The server SCSI tape device driver has
been invoked by the system and is initializing.
User response: Delete all paths for the drive, and
reissue the command. User response: None.
ANR9799E Command: Library Library Name is ANR9820I (Windows) ANR9820: SCSI Autochanger
currently not being shared. Device Driver Initializing...
Explanation: The command attempted to perform an Explanation: The server SCSI automatic changer
operation that is not allowed unless the library is device driver has been invoked by the system and is
allowed to be shared. initializing.
System action: None. System action: Processing continues.
User response: Verify the library on the library User response: None.
manager is being shared. If the library is not being
shared, update the library shared parameter to yes.
ANR9900W (AIX) Attention -- Accounting records
could not be written to the file: filespec.
ANR9800E Library Library Name is currently not
Explanation: The server detects an error while trying
being shared and attempted an
to open the accounting file.
operation only allowed for shared
libraries. System action: Server processing continues.
Explanation: The command attempted to perform an User response: Ensure that there is sufficient disk
operation that is not allowed unless the library is space and that the accounting file is not marked as
allowed to be shared. read-only.
ANR9900W (HP-UX) Attention -- Accounting records
User response: Verify the library on the library
could not be written to the file: file name.
manager is being shared. If the library is not being
shared, update the library shared parameter to yes. Explanation: The server detects an error while trying
ANR9801I (Windows) ANR9801: Ready for System action: Server processing continues, but no
operations. accounting records are written.
Explanation: The device driver has successfully User response: Ensure that there is sufficient disk
initialized and is ready to accept requests from the space and that the accounting file is not marked as
server. read-only.
ANR9900W (Linux) Attention -- Accounting records
ANR9803W (Windows) ANR9803: ERROR!
Insufficient free memory to initialize
driver. System action: Server processing continues, but no
accounting records are written.
Explanation: The server device driver is unable to
initialize due to an inability to acquire dynamic storage. User response: Ensure that there is sufficient disk
space and that the accounting file is not marked as
System action: Processing continues. The device
read-only.

ANR9900W (Solaris) • ANR9902W (Linux)
ANR9900W (Solaris) Attention -- Accounting records ANR9901W (Solaris) Attention -- Accounting records
could not be written to the file: file name. could not be written to the file: file name.
Explanation: The server detects an error while trying Explanation: The server detects an error while trying
to open the accounting file. to write an accounting record.
System action: Server processing continues, but no System action: Server processing continues.
accounting records are written.
User response: Ensure that there is sufficient disk
User response: Ensure that there is sufficient disk space and that the accounting file is not marked as
space and that the accounting file is not marked as read-only.
read-only.
ANR9901W (Windows) Attention -- Accounting
ANR9900W (Windows) Attention -- Accounting records could not be written to the file:
records could not be written to the file: filespec.
filespec.
Explanation: The server detects an error while trying to write an accounting record.
read-only.
ANR9902W (AIX) Attention -- Accounting records
ANR9901W (AIX) Attention -- Accounting records could not be written to the file: filespec.
Explanation: The server detects an error while trying to close the accounting file.
to write an accounting record.
User response: Ensure that sufficient disk space is
User response: Ensure that there is sufficient disk available and that the accounting file is not marked as
read-only.
ANR9902W (HP-UX) Attention -- Accounting records
ANR9901W (HP-UX) Attention -- Accounting records could not be written to the file: file name.
read-only.
ANR9902W (Linux) Attention -- Accounting records
ANR9901W (Linux) Attention -- Accounting records could not be written to the file: file name.
read-only.

ANR9902W (Solaris) • ANR9905W (Solaris)
ANR9902W (Solaris) Attention -- Accounting records ANR9905W (AIX) Unable to open file file. Error
could not be written to the file: file name. message generated by AIX
Explanation: The server detects an error while trying Explanation: The server was unable to open the
to close the accounting file. indicated file.
System action: Server processing continues. System action: The operation that was to use the
indicated file fails.
space and that the accounting file is not marked as User response: Determine the reason for being unable
read-only. to open the file and re-attempt the operation. Common
ANR9902W (Windows) Attention -- Accounting
records could not be written to the file:
owner.
filespec.
ANR9905W (HP-UX) Unable to open file file. Error
to close the accounting file.
message generated by HP-UX.
User response: Ensure that there is sufficient disk indicated file.
space and that the accounting file is not marked as
read-only.
indicated file fails.
ANR9903W (HP-UX) Create thread failed. Your
system is configured for a maximum of
thread count threads. Consider
configuring a maximum of 1024 threads.
Explanation: The server is unable to create a new owner.
thread.
System action: Server processing continues. ANR9905W (Linux) Unable to open file file. Error
message generated by Linux.
User response: Consider increasing the maximum
thread count on the system. Explanation: The server was unable to open the
indicated file.
ANR9904E (AIX) Adapter device Device name failed System action: The operation that was to use the
to open. indicated file fails.
Explanation: Permission was denied. The server did User response: Determine the reason for being unable
not complete the logical unit number (LUN) reset to open the file and re-attempt the operation. Common
function to clear the reservation from the tape drive. reasons for being unable to open the file include
System action: Server operations continue, but the authorization to open the file and not being the file's
target tape drive is inaccessible. owner.
User response: To resolve the issue, take one of the
following actions: - Run a power cycle to the target ANR9905W (Solaris) Unable to open file file. Error
tape drive - If the tape drive supports persistent message generated by Solaris.
reserve, change the reservation type from SCSI-2 to the
persistent reserve type that is used for the tape device Explanation: The server was unable to open the
driver. indicated file.
ANR9904W (HP-UX) Create thread failed. Try the indicated file fails.
operation again later.
Explanation: The server is unable to create a new to open the file and re-attempt the operation. Common
thread due to resource constraints. reasons for being unable to open the file include
System action: Server processing continues. authorization to open the file and not being the file's
User response: Try the operation again later. owner.

ANR9905W (Windows) Unable to open file file. Error ANR9953E (Windows) Command: Invalid value
message generated by Windows. specified for number of licensed clients
- value.
indicated file. Explanation: The specified command has been issued
indicated file fails. System action: Server operation continues, but the
to open the file and re-attempt the operation. Common User response: Issue the command using a valid
reasons for being unable to open the file include value.
ANR9955W (Windows) Unable to load dynamic link
owner.
library dynamic link library.
ANR9906E (AIX) The volume named volume name is
indicated dynamic link library.
larger than is allowed for a volume on
your system. Maximum allowed size is System action: Server operation continues, but the
allowed size. function that requires the dynamic link library will be
inoperative.
Explanation: While attempting to open a volume the
server detected that the volume size exceeds the User response: Ensure that the dynamic link library
maximum allowed. directories are accessible. If this is an evaluation copy
of the server, then this message is normal for the
DSMREG library, since the library is only provided
User response: Define multiple smaller volumes. with purchased Windows servers. The server licensing
will assume "Try and Buy" mode with sample licensed
options for a period of time.
ANR9950W (Windows) Attention -- License option
ANR9956E (Windows) Unable to load procedure
address from dynamic link library
to write to the options file.
dynamic link library.
User response: Ensure that there is sufficient disk address of a routine in the indicated dynamic link
space and that the options file is not marked as library.
read-only.
function that requires the dynamic link library will be
ANR9951W (Windows) Attention -- License option inoperative.
User response: Ensure that the dynamic link library
Explanation: The server detects an error while trying directories are accessible. If the problem persists,
to close the options file. contact you service representative.
ANR9957W (Windows) One or more EVALUATION
User response: Ensure that there is sufficient disk LICENSES will expire on expiration date.
space and that the options file is not marked as
read-only. Explanation: Although you are running with a
purchased version of the server, there are one or more
licenses registered that will expire on the date specified.
ANR9952E (Windows) Command: Invalid value This i usually the case when you have been using
specified for licensed storage capacity - evaluation licenses prior to purchasing the server for
value. Windows.
Explanation: The specified command has been issued System action: Server operation continues.
System action: Server operation continues, but the file in the server startup directory. After restarting the
command is not processed. server, use the REGISTER LICENSE command to define
User response: Issue the command using a valid the licensed features that you have purchased with
value. your Windows server. These licenses should NOT have

ANR9958W (Windows) • ANR9966I (Windows)
an expiration date, so this message should not appear

ANR9962W (Windows) Node entry node name was
after re-registering the proper licenses. If this message
renamed in this server's definition in
Active Directory.
Explanation: In response to a RENAME NODE
removed from this server's definition in
renamed to the new name shown.
Active Directory.
Explanation: In response to a REMOVE NODE
command, the requested backup-archive node has been User response: None.
removed from this server's definition in Active
Directory.
System action: None. not renamed in this server's definition
in Active Directory.
Explanation: In response to a RENAME NODE
command, the requested backup-archive node has not
been renamed.
not removed from this server's
definition in Active Directory. System action: None.
Explanation: In response to a REMOVE NODE User response: To Rename Node in the Active
command, the requested backup-archive node has not Directory, the options "adregister" and "adunregister"
been removed from this server's definition in Active have to be set to "yes" in the server options file. A
Directory. domain controller must also be available. The Active
Directory Configuration wizard can be used to
manually update the server definition.
User response: To remove a node entry in the Active
Directory, the option "adunregister" has to be set to
ANR9964W (Windows) Failed to access Active
"yes" in the server options file. A domain controller
Directory. RC: return code
must also be available. The Active Directory
Configuration wizard can be used to manually update Explanation: Could not communicate with an Active
the server definition. Directory server.
ANR9960W (Windows) Node entry node name has
User response: Try using the option "adsetdc" in the
been added to this server's definition in
server options file to explicitly provide the TCP/IP
Active Directory.
address of the domain controller where Active
Explanation: The requested backup-archive node entry Directory is located.
has been added to this server's definition in Active
Directory in response to a REGISTER NODE command.
ANR9965W (Windows) Could not create the inital
System action: None. node list in Active Directory for this
server.
Explanation: At startup the server's registered nodes
could not be added to the server definition in Active
ANR9961W (Windows) Node entry node name has not
Directory
been added to this server's definition in
Active Directory. System action: Server operation continues.
Explanation: The requested backup-archive node entry User response: Try using the option "adsetdc" in the
has not been added to this server's definition in Active server options file to explicitly provide the TCP/IP
Directory in response to a REGISTER NODE command. address of the domain controller where Active
Directory is located.
User response: To register a node entry in the Active
ANR9966I (Windows) NodeName node name.
Directory, the option "adregister" has to be set to "yes"
in the server options file. A domain controller must also Explanation: The NodeName is registered in Active
be available. The Active Directory Configuration wizard Directory.
can be used to manually update the server definition.

ANR9967I (Windows) • ANR9999D
ANR9967I (Windows) Server server name was defined

in Active Directory.
Explanation: The server is registered in Active
Directory.
ANR9968I (Windows) Success accessing Active

Directory.
Explanation: Active Directory Server could be
contacted.
System action:
ANR9969E (Windows) Unable to open volume

volume name. The most likely reason is
that another IBM Spectrum Protect
server is running and has the volume
allocated.
Explanation: Only one IBM Spectrum Protect server
can have a given volume open at a time.
System action: The IBM Spectrum Protect server does
not start.
User response: See if another IBM Spectrum Protect
server is already running and if so use it.
ANR9999D (component)(code):(text)
Explanation: The diagnostic text of this message is
related to a server process or algorithm. The
information is intended for reporting processing
exceptions and other non-standard situations that occur
on the server. The (component), (code), and (text) vary,
and server processing may continue, depending upon
the cause of the message and the server process or
algorithm issuing the message.
System action: Issue the SET CONTEXTMESSAGING
command and set the message context reporting to ON.
This allows you to receive additional information when
the server produces its message.
User response: Examine any error messages that were
displayed before or after this message and correct any
problems, if possible. If you cannot determine or
resolve the cause of this message, contact your support
representative. Report the entire text of this message
when contacting your support representative.

Chapter 4. Descriptions of I/O codes in server messages
IBM Spectrum Protect messages can contain input/output (I/O) codes. The codes
can be operation codes, completion codes, additional sense codes (ASC), and
additional sense code qualifier (ASCQ) codes.
Code descriptions are provided for I/O error messages from the IBM Spectrum
Protect server for all supported operating systems.
Code Description
OP I/O operation that failed. These values can be displayed:
v READ
v WRITE
v FSR (forward space record)
v RSR (reverse space record)
v FSF (forward space file)
v RSF (reverse space file)
v WEOF (write end of file mark)
v OFFL (rewind and unload the tape)
v FLUSH (flush)
v GET_MEDIUM_INFO (get medium information)
v LOCATE (locate)
v QRYLBP (query logical block protection)
v RDBLKID (read block ID)
v SETLBP (set logical block protection)
v SETMODE (set mode)
v REW (rewind)
v SPACEEOD (space end of data)
v TESTREADY (test drive ready)
CC I/O completion code. This value is returned by the device driver to the
server when an error occurs. For a list of completion codes, see
“Completion code and operation code values overview” on page 712. For
information about tape library system calls and error descriptions for the
library I/O control requests, see technote S7002972.
KEY Byte 2 of the sense bytes from the error. The following lists some
definitions:
0 = no additional sense bytes available

1 = recovered error
2 = not ready
3 = medium error
4 = hardware error
5 = incorrect request
6 = unit attention (for example, a SCSI bus reset)
7 = data protect
8 = blank check
9 = vendor specific
A = copy canceled

B = canceled command
C = obsolete
D = volume overflow
E = miscompare
F = reserved
ASC/ASCQ
ASC and ASCQ codes are bytes 12 and 13 of the sense bytes. The drive or
library reference manual provided with the device contains tables
explaining the values of the KEY, ASC, and ASCQ fields. “Descriptions of
standard ASC and ASCQ codes” on page 716 provides additional
information about standard values of ASC and ASCQ codes.
Operating system error codes
When a command fails, the operating system returns an error number. To
determine what the error codes mean, take the following action:
On AIX®, HP-UX, and Solaris, platforms, view the errno.h file in the
/usr/include/sys directory. This file provides definitions for error
codes.
On Linux platforms, view the errno-base.h and errno.h files in the
/usr/include/asm-generic directory. These files provides definitions for
codes.
On Windows platforms, contact Microsoft Support for help with error
messages.
Completion code and operation code values overview

IBM Spectrum Protect messages can contain device driver completion codes from
the device drivers.
Device drivers completion codes: Common codes

IBM Spectrum Protect device drivers provide completion codes that are common to
all device classes.
The following table shows common completion code values for IBM Spectrum
Protect device drivers. Each entry provides a description for the I/O error message
and the recommended action. After completing the recommended action, try the
failing operation again.
Table 1. Completion code values common to all device classes
Decimal Hexadecimal Description Recommended action
200 X'C8' The device indicated a failure condition, Try the failing operation again.
but sense data was unavailable.
201 X'C9' The device driver failed. Contact IBM Spectrum Protect Support.
202 X'CA' The device EEPROM failed. Test the device. Service the device if
necessary.
203 X'CB' Manual intervention is required. Correct the problem on the device. The
problem can be a stuck tape, dirty
heads, or a jammed library arm.
204 X'CC' The system recovered from an I/O error; No action necessary.
for your information only.
205 X'CD' The SCSI adapter failed. Check for loose cables, bent pins, bad
cables, bad SCSI adapters, improper
termination, or bad terminators.

Table 1. Completion code values common to all device classes (continued)
206 X'CE' A general SCSI failure occurred. Check for loose cables, bent pins, bad
cables, bad SCSI adapters, improper
termination, or bad terminators.
207 X'CF' The device cannot perform the requested Ensure that the device is on and ready.
action. Ensure that the drive was defined
appropriately with the DEFINE DRIVE
command. Ensure that the device class
was defined appropriately with the
DEFINE DEVCLASS command.
208 X'D0' The command stopped. Contact IBM Spectrum Protect Support.
209 X'D1' A failure is detected in the device Check the microcode level of the drive.
microcode. Contact the drive manufacturer and
request the latest level.
210 X'D2' The device was reset due to device Try the failing operation again.
power-up, SCSI bus reset, or manual
tape load/eject.
211 X'D3' The SCSI bus is busy. Ensure that the SCSI IDs are correctly
assigned to the correct device, and the
device is not being accessed by another
process.
212 X'D4' Persistent reservation is not supported No action is necessary.
on this device.
213 X'D5' A persistent reservation operation failed. Reset the device and try the operation
again. If the problem persists, contact
IBM Spectrum Protect Support.
Device drivers completion codes: Media changers

IBM Spectrum Protect device drivers provide completion codes that are specific to
media changer devices.
The following table shows completion code values for IBM Spectrum Protect
device drivers for media changers. Each entry provides a description for the I/O
error message and the recommended action. After performing the recommended
action, try the failing operation again.
Table 2. Completion code values for media changers
300 X'12C' Cartridge entry/exit error Check the entry/exit ports for a
jammed volume.
301 X'12D' Cartridge load failure Check the drive for jammed volumes.
On AIX, display the errpt to check for
hardware errors.
302 X'12E' Cartridge in failed drive Check the drive for jammed volumes.
hardware errors.
303 X'12F' Carousel not loaded Ensure that the carousel is correctly in
place and the door is shut.
304 X'130' Changer failure On AIX, display the errpt to check for
hardware errors.
Chapter 4. I/O code descriptions in server messages 713

Table 2. Completion code values for media changers (continued)
305 X'131' Drive failure Ensure that the heads are clean. On
AIX, display the errpt to check for
hardware errors.
306 X'132' Drive or media failure Ensure that the heads are clean. On
hardware errors.
307 X'133' Entry/exit failure Check the tape library interface for
hardware errors. If there are no errors,
contact IBM Spectrum Protect Support.
308 X'134' Entry/exit port not present Check the tape library interface for
309 X'135' Library audit error Ensure that there are no jammed
volumes. It is possible that the library
audit is failing due to hardware errors.
hardware errors.
310 X'136' Library full Check for jammed volumes. Ensure that
the volumes are not rearranged. If the
library is not full, start the AUDIT
LIBRARY command.
311 X'137' Media export Check the tape library interface for
312 X'138' Slot failure Ensure that nothing is jammed in the
slot.
313 X'139' Slot or media failure Ensure that the volume is not jammed
in the slot and that the volumes are not
rearranged. If the problem persists, start
314 X'13A' The source slot or drive was empty in an Ensure that the volumes are not
attempt to move a volume rearranged. If the problem persists, start
315 X'13B' The destination slot or drive was full in Ensure that the volumes are not
an attempt to move a volume rearranged, or that a volume is not
stuck in the drive. If problem persists,
start the AUDIT LIBRARY command.
316 X'13C' Cleaner cartridge installed Contact IBM Spectrum Protect support.
317 X'13D' Media not ejected Ensure that the volumes are not
rearranged, or that a volume is not
stuck in the drive. If problem persists,
start the AUDIT LIBRARY command.
318 X'13E' I/O port not configured Contact IBM Spectrum Protect Support.
319 X'13F' First destination empty Ensure that the volumes are not
rearranged. If problem persists, start the
AUDIT LIBRARY command.
320 X'140' No inventory information Start the AUDIT LIBRARY command.

Table 2. Completion code values for media changers (continued)
321 X'141' Read element status mismatch Ensure that host bus adapter drivers
and firmware are at current levels.
Check the tape library interface for
322 X'142' Initialize range failed Check the tape library interface for
Device drivers completion codes: Tape drives

IBM Spectrum Protect device drivers provide completion codes that are specific to
tape drives.
The following table shows completion code values for IBM Spectrum Protect
device drivers for tape drives. Each entry provides a description for the I/O error
message and the recommended action. After trying the recommended action, try
the failing operation again.
Table 3. Completion code values for tape drives
400 X'190' Physical end of media encountered Ensure that the heads are clean on the
drive.
401 X'191' End of data detected Contact IBM Spectrum Protect Support.
402 X'192' Media corrupted Ensure that the heads are clean. Ensure
that the media is not physically
damaged and has not reached the end
of life as specified by the media
manufacturer.
403 X'193' Media failure Ensure that the heads are clean. Ensure
manufacturer.
404 X'194' Media incompatibility Ensure that the correct length and type
of media is being used.
406 X'196' Sector that is requested is invalid Internal server error. Contact IBM
Spectrum Protect Support.
407 X'197' Write protect Ensure that the volume is not write
protected.
408 X'198' Clean the media and the drive Clean the drive heads with a cleaning
cartridge.
409 X'199' Media fault Ensure that the heads are clean. Ensure
manufacturer.
410 X'19A' Cleaning complete Try the failing operation again.
411 X'19B' Logical end of media encountered ContactIBM Spectrum Protect Support.

Table 3. Completion code values for tape drives (continued)
412 X'19C' Media not present in drive Ensure that the media is correctly
positioned in the drive. If problem
persists, start the AUDIT LIBRARY
command.
413 X'19D' Encountered the beginning of the media Contact IBM Spectrum Protect Support.
414 X'19E' Erase failure Clean the drive heads.
415 X'19F' Attempted to overwrite written WORM Internal server error. ContactIBM
media Spectrum Protect Support.
416 X'1A0' An incorrect length block was read. Ensure that the heads are clean. On
hardware errors.
417 X'1A1' Open read only Contact IBM Spectrum Protect Support.
418 X'1A2' Open write only Contact IBM Spectrum Protect Support.
419 X'1A2' Media scan failed Clean the drive and media.
420 X'1A4' Logical write protect Ensure that the heads are clean. Check
operating system error logs for
hardware errors. Verify that the write
protect tab is off. Turn off SAN tape
acceleration or set CHECKTAPEPOS to OFF
or TSMonly.
422 X'1A6' Cleaning is required Clean the tape drive.
423 X'1A7' Media error Check operating system error logs for
hardware errors. Check for bad media.
424 X'1A8' Encryption-related error occurred Check your encryption setting on your
device class and tape drive.
425 X'1A9' Decryption-related error occurred Check your encryption setting on your
device class and tape drive.
425 X'1AA' An external, encryption-related error Check the encryption setting on your
occurred device class and tape drive.
426 X'1AB' A CRC mismatch occurred Ensure that the media has not reached
the end of life as specified by the media
manufacturer. Try the operation again.
Descriptions of standard ASC and ASCQ codes

Standard ASC and ASCQ codes are described.
The ASC and ASCQ codes are bytes 12 and 13 for SCSI-2 devices. On Windows
systems, these codes are displayed in the Windows Event Log, but the information
is in different bytes.
See server message ANR8300E or ANR8302E for the recommended action.
The following table provides standard descriptions for some ASC and ASCQ codes.
Each value has a prefix of 0x, which indicates that it is a hexadecimal constant.
Note that descriptions vary among devices. For an accurate description of ASC and
ASCQ codes for any device, see the documentation that comes with the device.

Table 4. Descriptions of standard ASC and ASCQ codes
ASC ASCQ Description
0x00 0x00 No additional sense
0x00 0x01 Filemark detected
0x00 0x02 End-of-medium detected
0x00 0x03 Setmark detected
0x00 0x04 Beginning of medium
0x00 0x05 End of data
0x00 0x06 I/O process terminated
0x02 0x00 No seek complete
0x03 0x00 Device write fault
0x03 0x01 No write current
0x03 0x02 Excessive write errors
0x04 0x00 Logical unit not ready
0x04 0x01 Becoming ready
0x04 0x02 Not ready, initializing command required
0x04 0x03 Not ready, manual intervention required
0x04 0x04 Not ready, formatting
0x05 0x00 No response to select
0x06 0x00 No reference position found
0x07 0x00 Multiple devices selected
0x08 0x00 Communication failure
0x08 0x01 Communication timeout
0x08 0x02 Communication parity error
0x09 0x00 Track following error
0x0A 0x00 Error log overflow
0x0C 0x00 Write error
0x11 0x00 Unrecovered read error
0x11 0x01 Read retries exhausted
0x11 0x02 Error too long to correct
0x11 0x03 Multiple read errors
0x11 0x08 Incomplete block read
0x11 0x09 No gap found
0x11 0x0A Miscorrected error
0x14 0x00 Recorded entity not found
0x14 0x01 Record not found
0x14 0x02 Filemark/setmark not found
0x14 0x03 End-of-data not found
0x14 0x04 Block sequence error
0x15 0x00 Random positioning error
0x15 0x01 Mechanical positioning error
0x15 0x02 Read positioning error

Table 4. Descriptions of standard ASC and ASCQ codes (continued)
0x17 0x00 No error correction applied
0x17 0x01 Recovered with retries
0x17 0x02 Recovered with positive head offset
0x17 0x03 Recovered with negative head offset
0x18 0x00 ECC applied
0x1A 0x00 Parameter list length error
0x1B 0x00 Synchronous data transfer error
0x20 0x00 Invalid operation code
0x21 0x00 Block out of range
0x21 0x01 Invalid element address
0x24 0x00 Invalid field in CDB
0x25 0x00 LUN not supported
0x26 00 Invalid field in parameter list
0x26 0x01 Parameter not supported
0x26 0x02 Parameter value invalid
0x26 0x03 Threshold parameters not supported
0x27 0x00 Write protected
0x28 0x00 Not-ready to ready
0x28 0x01 Import/export element accessed
0x29 0x00 Power-on, reset, bus reset
0x2A 0x00 Parameters changed
0x2A 0x01 Mode parameters changed
0x2A 0x02 Log parameters changed
0x2B 0x00 Copy cannot run
0x2C 0x00 Command sequence error
0x2D 0x00 Overwrite error on update
0x2F 0x00 Command cleared by initiator
0x30 0x00 Incompatible media
0x30 0x01 Media unknown format
0x30 0x02 Media incompatible format
0x30 0x03 Cleaning cartridge installed
0x31 0x00 Media format corrupted
0x33 0x00 Tape length error
0x37 0x00 Rounded parameter
0x39 0x00 Saving parameters not supported
0x3A 0x00 Medium not present
0x3B 0x00 Sequential positioning error
0x3B 0x01 Positioning error at BOT
0x3B 0x02 Positioning error at EOT
0x3B 0x08 Reposition error

Table 4. Descriptions of standard ASC and ASCQ codes (continued)
0x3B 0x0D Medium destination element full
0x3B 0x0E Medium source element empty
0x3D 0x00 Invalid bits in message
0x3E 0x00 LUN not self-configured
0x3F 0x00 Operating conditions changed
0x3F 0x01 Microcode changed
0x3F 0x02 Changed operating definition
0x3F 0x03 Inquiry data changed
0x3F 0x0E Reported LUNs data changed
0x43 0x00 Message error
0x44 0x00 Internal target failure
0x45 0x00 Select/reselect failure
0x46 0x00 Unsuccessful soft reset
0x47 0x00 SCSI parity error
0x48 0x00 Initiator detected message received
0x49 0x00 Invalid message error
0x4A 0x00 Command phase error
0x4B 0x00 Data phase error
0x4C 0x00 LUN failed self-configuration
0x4E 0x00 Overlapped commands attempt
0x50 0x00 Write append error
0x50 0x01 Write append position error
0x50 0x02 Position error (timing)
0x51 0x00 Erase failure
0x52 0x00 Cartridge fault
0x53 0x00 Load/media eject failed
0x53 0x01 Unload tape failure
0x53 0x02 Media removal prevented
0x5A 0x00 Operator state changed
0x5A 0x01 Operator media removal
0x5A 0x02 Operator write protect
0x5A 0x03 Operator write permit
0x5B 0x00 Log exception
0x5B 0x01 Threshold condition met
0x5B 0x02 Log counter at maximum
0x5B 0x03 Log list codes exhausted

ASC and ASCQ codes in the Windows Event Log
ASC and ASCQ codes are displayed in the Windows Event Log.
The ASC and ASCQ codes are displayed as hexadecimal values in the Data area of
the Windows Event Log. The Event Log omits the 0x prefix for the displayed
information.
In the Windows Event Log, the entries with source AdsmScsi are produced by the
IBM Spectrum Protect AdsmScsi device driver. Entries from the AdsmScsi device
driver or any Windows tape device driver contain the following information:
v Byte 3E is the sense key
v Byte 3D is the ASC
v Byte 3C is the ASCQ
If byte 44 is 'ef', the error logged is not a check condition error. Examples of such
errors are command timeouts or device selection errors.

Chapter 5. Device error codes in the AIX system error log
Some device error codes are logged in the AIX system error log.
ADSM_DD_LOG1 (0xAC3AB953)
DEVICE DRIVER SOFTWARE ERROR
This error is logged by the IBM Spectrum Protect device driver when a
problem is suspected in the IBM Spectrum Protect device driver software.
If the IBM Spectrum Protect device driver issues a SCSI I/O command
with an illegal operation code, the command fails and the error is logged
with this identifier. Report this error immediately to IBM Spectrum Protect
Support.
Detail Data: Sense Data
The sense data contains information that can determine the cause of the
error. Report all data in the error entry to IBM Spectrum Protect Support.
ADSM_DD_LOG2 (0x5680E405)
HARDWARE/COMMAND-ABORTED ERROR
This error is logged by the IBM Spectrum Protect device driver when the
device reports a hardware error or stop-command error in response to a
SCSI I/O command.
The sense data contains information that can determine which hardware
component failed and why. To interpret the sense data for a particular
device, refer to the SCSI specification manual for the device.
ADSM_DD_LOG3 (0x461B41DE)
MEDIA ERROR
This error is logged by the IBM Spectrum Protect device driver when a
SCSI I/O command fails because of corrupted or incompatible media, or
because a drive requires cleaning.
The sense data contains information that can determine the cause of the
error. To interpret the sense data for a particular device, refer to the SCSI
specification manual for the device.
ADSM_DD_LOG4 (0x4225DB66)
TARGET DEVICE GOT UNIT ATTENTION
This error is logged by the IBM Spectrum Protect device driver after
receiving certain UNIT ATTENTION notifications from a device. UNIT
ATTENTIONs are informational and usually indicate that some state of the
device changed. For example, this error would be logged if the door of a
library device was opened and then closed. Logging this event indicates
that the activity occurred and that the library inventory might be changed.
The sense data contains information that describes the reason for the UNIT
ATTENTION. To interpret the sense data for a particular device, see the
SCSI specification manual for the device.

ADSM_DD_LOG5 (0xDAC55CE5)
PERMANENT UNKNOWN ERROR
receiving an unknown error from a device in response to a SCSI I/O
command. If the error persists, report it to IBM Spectrum Protect support
personnel.
The sense data consists of information that can determine the cause of the
error. Report all data in the error entry to IBM Spectrum Protect Support.
ADSM_DD_LOG6 (0xBC539B26)
WARNING OR INFORMATIONAL MESSAGE FOR TARGET DEVICE
receiving a warning or informational message from a device in response to
a SCSI I/O command. These informational messages might not be an
indication of a problem. If the message persists, report it to IBM Spectrum
Protect Support.
The sense data consists of information that can determine the reason for
the message. Report all data in the entry to IBM Spectrum Protect Support.

Appendix. Accessibility features for the IBM Spectrum Protect
product family
Accessibility features assist users who have a disability, such as restricted mobility
or limited vision, to use information technology content successfully.
Overview
The IBM Spectrum Protect family of products includes the following major
accessibility features:
v Keyboard-only operation
v Operations that use a screen reader
The IBM Spectrum Protect family of products uses the latest W3C Standard,
WAI-ARIA 1.0 (www.w3.org/TR/wai-aria/), to ensure compliance with US Section
508 (www.access-board.gov/guidelines-and-standards/communications-and-it/
about-the-section-508-standards/section-508-standards) and Web Content
Accessibility Guidelines (WCAG) 2.0 (www.w3.org/TR/WCAG20/). To take
advantage of accessibility features, use the latest release of your screen reader and
the latest web browser that is supported by the product.
The product documentation in IBM Knowledge Center is enabled for accessibility.

The accessibility features of IBM Knowledge Center are described in the
Accessibility section of the IBM Knowledge Center help (www.ibm.com/support/
knowledgecenter/about/releasenotes.html?view=kc#accessibility).
Keyboard navigation
This product uses standard navigation keys.
Interface information
User interfaces do not have content that flashes 2 - 55 times per second.
Web user interfaces rely on cascading style sheets to render content properly and
to provide a usable experience. The application provides an equivalent way for
low-vision users to use system display settings, including high-contrast mode. You
can control font size by using the device or web browser settings.
Web user interfaces include WAI-ARIA navigational landmarks that you can use to
quickly navigate to functional areas in the application.
Vendor software
The IBM Spectrum Protect product family includes certain vendor software that is
not covered under the IBM license agreement. IBM makes no representation about
the accessibility features of these products. Contact the vendor for accessibility
information about its products.

Related accessibility information
In addition to standard IBM help desk and support websites, IBM has a TTY
telephone service for use by deaf or hard of hearing customers to access sales and
support services:
TTY service
800-IBM-3383 (800-426-3383)
(within North America)
For more information about the commitment that IBM has to accessibility, see IBM
Accessibility (www.ibm.com/able).

Notices
This information was developed for products and services offered in the US. This
material might be available from IBM in other languages. However, you may be
required to own a copy of the product or product version in that language in order
to access it.
IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing

IBM Corporation
North Castle Drive, MD-NC119
Armonk, NY 10504-1785
US
For license inquiries regarding double-byte character set (DBCS) information,

contact the IBM Intellectual Property Department in your country or send
inquiries, in writing, to:
Intellectual Property Licensing

Legal and Intellectual Property Law
IBM Japan Ltd.
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, Japan
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS

PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of
express or implied warranties in certain transactions, therefore, this statement may
not apply to you.
This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM websites are provided for

convenience only and do not in any manner serve as an endorsement of those

websites. The materials at those websites are not part of the materials for this IBM
product and use of those websites is at your own risk.
IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:
IBM Director of Licensing

IBM Corporation
North Castle Drive, MD-NC119
Armonk, NY 10504-1785
US
Such information may be available, subject to appropriate terms and conditions,

including in some cases, payment of a fee.
The licensed program described in this document and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement or any equivalent agreement
between us.
The performance data discussed herein is presented as derived under specific

operating conditions. Actual results may vary.
Information concerning non-IBM products was obtained from the suppliers of

those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which

illustrate programming techniques on various operating platforms. You may copy,
modify, and distribute these sample programs in any form without payment to
IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating
platform for which the sample programs are written. These examples have not
been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or
imply reliability, serviceability, or function of these programs. The sample
programs are provided "AS IS", without warranty of any kind. IBM shall not be
liable for any damages arising out of your use of the sample programs.

Each copy or any portion of these sample programs or any derivative work must
include a copyright notice as follows: © (your company name) (year). Portions of
this code are derived from IBM Corp. Sample Programs. © Copyright IBM Corp.
_enter the year or years_.
Trademarks
IBM, the IBM logo, and ibm.com® are trademarks or registered trademarks of
International Business Machines Corp., registered in many jurisdictions worldwide.
Other product and service names might be trademarks of IBM or other companies.
A current list of IBM trademarks is available on the Web at "Copyright and
trademark information" at www.ibm.com/legal/copytrade.shtml.
Adobe is a registered trademark of Adobe Systems Incorporated in the United

States, and/or other countries.
Linear Tape-Open, LTO, and Ultrium are trademarks of HP, IBM Corp. and
Quantum in the U.S. and other countries.
Intel and Itanium are trademarks or registered trademarks of Intel Corporation or

its subsidiaries in the United States and other countries.
Linux is a registered trademark of Linus Torvalds in the United States, other

countries, or both.
Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation in

the United States, other countries, or both.
Java™ and all Java-based trademarks and logos are trademarks or registered
trademarks of Oracle and/or its affiliates.
SoftLayer® is a registered trademark of SoftLayer, Inc., an IBM Company.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Terms and conditions for product documentation
Permissions for the use of these publications are granted subject to the following
terms and conditions.
Applicability
These terms and conditions are in addition to any terms of use for the IBM
website.
Personal use
You may reproduce these publications for your personal, noncommercial
use provided that all proprietary notices are preserved. You may not
distribute, display or make derivative work of these publications, or any
portion thereof, without the express consent of IBM.
Commercial use
You may reproduce, distribute and display these publications solely within
your enterprise provided that all proprietary notices are preserved. You
may not make derivative works of these publications, or reproduce,
distribute or display these publications or any portion thereof outside your
enterprise, without the express consent of IBM.
Notices 727
Rights Except as expressly granted in this permission, no other permissions,
licenses or rights are granted, either express or implied, to the publications
or any information, data, software or other intellectual property contained
therein.
IBM reserves the right to withdraw the permissions granted herein
whenever, in its discretion, the use of the publications is detrimental to its
interest or, as determined by IBM, the above instructions are not being
properly followed.
You may not download, export or re-export this information except in full
compliance with all applicable laws and regulations, including all United
States export laws and regulations.
IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE
PUBLICATIONS. THE PUBLICATIONS ARE PROVIDED "AS-IS" AND
WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR
IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES
OF MERCHANTABILITY, NON-INFRINGEMENT, AND FITNESS FOR A
PARTICULAR PURPOSE.
Privacy policy considerations

IBM Software products, including software as a service solutions, (“Software
Offerings”) may use cookies or other technologies to collect product usage
information, to help improve the end user experience, to tailor interactions with
the end user, or for other purposes. In many cases no personally identifiable
information is collected by the Software Offerings. Some of our Software Offerings
can help enable you to collect personally identifiable information. If this Software
Offering uses cookies to collect personally identifiable information, specific
information about this offering’s use of cookies is set forth below.
This Software Offering does not use cookies or other technologies to collect
personally identifiable information.
If the configurations deployed for this Software Offering provide you as customer
the ability to collect personally identifiable information from end users via cookies
and other technologies, you should seek your own legal advice about any laws
applicable to such data collection, including any requirements for notice and
consent.
For more information about the use of various technologies, including cookies, for
these purposes, see IBM’s Privacy Policy at http://www.ibm.com/privacy and
IBM’s Online Privacy Statement at http://www.ibm.com/privacy/details in the
section entitled “Cookies, Web Beacons and Other Technologies,” and the “IBM
Software Products and Software-as-a-Service Privacy Statement” at
http://www.ibm.com/software/info/product-privacy.

Glossary
A glossary is available with terms and definitions for the IBM Spectrum Protect family of products.
See the IBM Spectrum Protect glossary.
To view glossaries for other IBM products, see IBM Terminology.

IBM®
Product Number: 5725-W98

5725-W99
5725-X15
5725-X18
Printed in USA

TSM Guide

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

TSM Guide

Загружено:

Авторское право:

Доступные форматы

IBM Spectrum Protect

Server Messages and Error Codes

Server Messages and Error Codes

© Copyright IBM Corp. 1993, 2016 iii

Who should read this publication

To view IBM product documentation, see IBM Knowledge Center.

© Copyright IBM Corp. 1993, 2016 v

IBM Spectrum Protect server and client messages format

Code Severity Meaning

© Copyright IBM Corp. 1993, 2016 1

The callouts identify each element of the message.

Explanation: The server installation procedure

System Action: Server completes installation System Action

User Response: None. User Response

Interpreting return code messages

But the first command also yields a descriptive message:

And the second command also yields a unique, descriptive message:

2 IBM Spectrum Protect: Server Messages and Error Codes

Example two for DEFINE VOLUME command

Chapter 1. Introduction to messages 3

ANE messages list

These files are in the installation_directory\doc directory for Windows

System action: IBM Spectrum Protect processing

© Copyright IBM Corp. 1993, 2016 5

6 IBM Spectrum Protect: Server Messages and Error Codes

Chapter 2. ANE messages 7

ANE4022E Error processing 'filespace Solaris 2.6 or higher

System action: processing stops. UnixWare

8 IBM Spectrum Protect: Server Messages and Error Codes

has exceeded the maximum file size limitation on your

ANE4033E Error processing 'filespace

Chapter 2. ANE messages 9

User response: Obtain a machine with more memory

ANE4040E Error processing 'filespace

10 IBM Spectrum Protect: Server Messages and Error Codes

differ only in case on this platform and cannot

Chapter 2. ANE messages 11

ANE4049I Established LAN-Free connection. ANE4052E Error processing 'filespace

12 IBM Spectrum Protect: Server Messages and Error Codes

ANE4057I The secondary server is configured as

System action: Processing stops. Explanation: A write failure is often a result of

Chapter 2. ANE messages 13

primary server and processing stops.

14 IBM Spectrum Protect: Server Messages and Error Codes

Because the file cannot be restored, IBM Spectrum

ANE4083I New node password has been

ANE4089W File server file-server-name has been

Chapter 2. ANE messages 15

System action: Processing continues. Explanation: This message reports statistics or

User response: The instant access/restore operation

16 IBM Spectrum Protect: Server Messages and Error Codes

ANE4107I Candidates : Number of migration ANE4113I Waiting for dsmautomig

Chapter 2. ANE messages 17

ANE4118I Objects scanned in hash : Number of ANE4124I NO INFORMATION AVAILABLE

18 IBM Spectrum Protect: Server Messages and Error Codes

Chapter 2. ANE messages 19

ANE4140I Backup VM command complete ANE4146I Starting Full VM backup of Virtual

Explanation: This message reports statistics or User response: None required.

System action: Processing continues.

20 IBM Spectrum Protect: Server Messages and Error Codes

User response: Check the local client error log for

Chapter 2. ANE messages 21

22 IBM Spectrum Protect: Server Messages and Error Codes