B Msgs Server PDF

IBM Tivoli Storage Manager
Version 7.1
Server Messages and Error Codes

IBM Tivoli Storage Manager
Version 7.1
Server Messages and Error Codes

Note:
Before using this information and the product it supports, read the information in Notices on page 767.
First edition (December 2013)

This edition applies to version 7, release 1, modification 0 of IBM Tivoli Storage Manager (product numbers
5608-E01, 5608-E02, 5608-E03, 5608-E07) and to all subsequent releases and modifications until otherwise indicated
in new editions.
Copyright IBM Corporation 1993, 2013.
US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Tables . . . . . . . . . . . . . . . v Receiving notification of product fixes . . . . 762
Contacting IBM Software Support . . . . . . 762
About this publication . . . . . . . . vii Setting up and managing support contracts . . 763
Determining the business impact . . . . . . 763
Who should read this publication . . . . . . . vii
Describing the problem and gathering
Publications . . . . . . . . . . . . . . vii
background information . . . . . . . . . 763
Submitting the problem to IBM Software
Chapter 1. Introduction to messages . . 1 Support . . . . . . . . . . . . . . 764
Tivoli Storage Manager server and client messages
format . . . . . . . . . . . . . . . . 1
Appendix B. Accessibility features for
Interpreting return code messages . . . . . . . 2
Example one for QUERY EVENT command . . . 3 the Tivoli Storage Manager product
Example two for DEFINE VOLUME command . . 3 family. . . . . . . . . . . . . . . 765
Chapter 2. ANE messages . . . . . . . 5 Notices . . . . . . . . . . . . . . 767

ANE messages list . . . . . . . . . . . . 5 Trademarks . . . . . . . . . . . . . . 769
Privacy policy considerations . . . . . . . . 769
Chapter 3. ANR messages . . . . . . 47
ANR messages list . . . . . . . . . . . . 47 Glossary . . . . . . . . . . . . . 771
A . . . . . . . . . . . . . . . . . 771
Chapter 4. Descriptions of I/O codes B . . . . . . . . . . . . . . . . . 773
C . . . . . . . . . . . . . . . . . 774
in server messages . . . . . . . . . 747
D . . . . . . . . . . . . . . . . . 775
Completion code and operation code values
E . . . . . . . . . . . . . . . . . 777
overview . . . . . . . . . . . . . . . 748
F . . . . . . . . . . . . . . . . . 778
Device drivers completion codes: Common
G . . . . . . . . . . . . . . . . . 778
codes . . . . . . . . . . . . . . . 748
H . . . . . . . . . . . . . . . . . 779
Device drivers completion codes: Media
I. . . . . . . . . . . . . . . . . . 780
changers . . . . . . . . . . . . . . 749
J. . . . . . . . . . . . . . . . . . 780
Device drivers completion codes: Tape drives 751
K . . . . . . . . . . . . . . . . . 780
Descriptions of standard ASC and ASCQ codes . . 752
L . . . . . . . . . . . . . . . . . 781
ASC and ASCQ codes in Windows Event Log 755
M . . . . . . . . . . . . . . . . . 782
N . . . . . . . . . . . . . . . . . 783
Chapter 5. Device error codes in the O . . . . . . . . . . . . . . . . . 784
AIX system error log . . . . . . . . 757 P . . . . . . . . . . . . . . . . . 784
Q . . . . . . . . . . . . . . . . . 785
Appendix A. Tivoli support R . . . . . . . . . . . . . . . . . 786
information . . . . . . . . . . . . 759 S . . . . . . . . . . . . . . . . . 787
T . . . . . . . . . . . . . . . . . 790
Communities and other learning resources . . . 759
U . . . . . . . . . . . . . . . . . 790
Searching knowledge bases . . . . . . . . . 761
V . . . . . . . . . . . . . . . . . 791
Searching the Internet . . . . . . . . . 761
W . . . . . . . . . . . . . . . . . 793
Using IBM Support Assistant . . . . . . . 761
Finding product fixes. . . . . . . . . . 762
Copyright IBM Corp. 1993, 2013 iii

iv IBM Tivoli Storage Manager: Server Messages and Error Codes
Tables
1. Completion code values common to all 3. Completion code values for tape drives 751
device classes . . . . . . . . . . . 748 4. Descriptions of standard ASC and ASCQ
2. Completion code values for media changers 749 codes . . . . . . . . . . . . . . 752
Copyright IBM Corp. 1993, 2013 v

vi IBM Tivoli Storage Manager: Server Messages and Error Codes
About this publication
IBM Tivoli Storage Manager 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 Tivoli Storage Manager server.
Who should read this publication

The target audience for this publication is system administrators who service the
IBM Tivoli Storage Manager components. In this publication, it is assumed that
you have a working knowledge of the Tivoli Storage Manager server and client
components.
Publications
Publications for the Tivoli Storage Manager family of products are available online.
The Tivoli Storage Manager product family includes IBM Tivoli Storage
FlashCopy Manager, IBM Tivoli Storage Manager for Space Management, IBM
Tivoli Storage Manager for Databases, and several other storage management
products from IBM Tivoli.
To search across all publications or to download PDF versions of individual

publications, go to the Tivoli Storage Manager information center at
http://pic.dhe.ibm.com/infocenter/tsminfo/v7r1.
You also can find the Tivoli Storage Manager product family information centers
and other information centers that contain official product documentation for
current and previous versions of Tivoli products at Tivoli Documentation Central.
Tivoli Documentation Central is available at http://www.ibm.com/
developerworks/community/wikis/home/wiki/Tivoli Documentation Central.
Copyright IBM Corp. 1993, 2013 vii

viii IBM Tivoli Storage Manager: Server Messages and Error Codes
Chapter 1. Introduction to messages
Messages, error codes, and return codes are issued by the IBM Tivoli Storage
Manager 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 HSM (Hierarchical Storage Management) client.
Tivoli Storage Manager 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
See the IBM Tivoli Storage Manager Administrator's Guide for more information
about activity logs.
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.
Tivoli Storage Manager server and client messages format

Tivoli Storage Manager server and client messages consist of the following
elements:
v A three-letter prefix. Messages have different prefixes to help you identify the
Tivoli Storage Manager 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 ANS prefix.
Backup-archive client events that are logged to server have ANE prefix. Server
common and server platform-specific messages have 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. The severity codes and their meanings are as
follows:
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.
Copyright IBM Corp. 1993, 2013 1

Code Severity Meaning
I Information Processing continues. User response is not necessary.
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's messages publications and in
the command line help.
The following image presents a typical Tivoli Storage Manager 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 Tivoli Storage Manager: 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 IBM Tivoli Storage Manager server. All messages
with ANE prefix are client events logged to the server.
ANE messages list

IBM Tivoli Storage Manager server ANE messages are listed in ascending
numerical order. All elements of the message are documented, including message
ID, message text, explanation, system action, and user response.
volume label, and retry the operation.

ANE4000E Error processing 'filespace-name': file
space does not exist.
ANE4003E Error processing 'filespace-name':
Explanation: The specified file space (domain) is
duplicate volume label encountered
incorrect or does not exist on the workstation. If the
message results from the BACKUP IMAGE command Explanation: The selected drive has a duplicate
with the -MODE=INCREMENTAL option, it means that volume label. Because TSM uses the volume label to
you have entered the name of a raw logical volume. keep track of backup/archive information, it cannot
The MODE=INCREMENTAL option is not valid for back up or archive files from a drive with a duplicate
raw logical volumes. volume label.
System action: Processing stops. System action: TSM cannot select the drive.
User response: Try the operation again, specifying an User response: If the volume needs to be available to
existing domain (drive letter or file system name). If the system, exit TSM, and assign a volume label to the
the message resulted from improper use of the drive. Restart TSM and retry the operation.
MODE=INCREMENTAL option, try the command
again, omitting that option.
ANE4004E Error processing 'filespace
namepath-namefile-name': destination file
ANE4001E The file space for domain 'filespace-name' or directory is write locked
could not be found on the TSM server.
Explanation: The file or directory being restored or
Explanation: The specified file space was expected to retrieved from the server cannot be written to because
be found on the server, but it no longer exists. It is the destination is write locked. Another operation
possible that a command was issued to delete the file might have the file open and will not allow it to be
space from the server while the current operation was updated.
in progress.
System action: File skipped.
System action: TSM processing stops.
User response: Either determine which operation has
User response: Try the operation again. If the problem the file write locked, or restore the file to another name
recurs, check the error log for any other messages that or location.
might indicate a reason for the failure. Try to correct
any indicated problems, then try the operation again. If
the problem persists, contact IBM technical support for ANE4005E Error processing 'filespace
further assistance. namepath-namefile-name': file not found
Explanation: The file being processed for backup,
ANE4002E Error processing 'filespace-name': volume archive or migrate no longer exists on the client.
label does not exist Another process deletes the file before it can be backed
up, archived or migrated by TSM.
Explanation: The selected drive does not have a label.
System action: TSM is unable to do the requested
operation without a drive or label entered. User response: None.
User response: If the drive is a floppy drive, place a

disk with a volume label in it and retry the operation.
If the disk is a hard drive, ensure the drive has a

ANE4006E ANE4013E
User response: Select the appropriate action for this

object. Create some free space on the destination disk
namepath-namefile-name': directory path
before you retry the operation. Another option is to
not found
restore or retrieve the file to another disk.
Explanation: The operating system returned a "path
not found" status when IBM Tivoli Storage Manager
attempted to access the directory. You either have
namepath-namefile-name': stale NFS handle
specified a directory that does not exist, as shown in
the message (path-name), or the directory being Explanation: An NFS file system becomes stale.
processed no longer exists on the client because another
process deleted it before it could be backed up or System action: File system skipped.
archived by IBM Tivoli Storage Manager. User response: Check the NFS mounted filesystem.
System action: The directory is skipped, processing
continues ANE4011E Error processing 'filespace
User response: Recheck all spelling and punctuation, namepath-namefile-name': no file handles
particularly the placement of directory delimiters (for available
example, "\"). Correct the syntax if it is incorrect, then Explanation: All file handles for your system are
retry the operation. Ensure that the path is specified currently in use. No more are available.
correctly and that the directory actually exists. Retry
the command with the corrected path and directory System action: Processing stopped.
name. If you cannot correct the directory name, use the User response: Either free some file handles by ending
Exclude option to exclude the directory from the other processes, or modify your system setup to allow
operation. for more files to be open at the same time.
ANE4007E Error processing 'filespace ANE4012E 'filespace namepath-namefile-name' already

namepath-namefile-name': access to the exists. It will be skipped.
object is denied
Explanation: The client tried to restore or retrieve the
Explanation: Access to the specified file or directory is specified file, but the file already existed in the target
denied. You tried to read from or write to a file and restore location and the user chose not to replace the
you do not have access permission for either the file or existing file.
the directory.
System action: The file is skipped, a message is
System action: Processing stopped. logged in dsmerror.log, and restore or retrieve
User response: Ensure that you specified the correct processing continues with the next object.
file or directory name, correct the permissions, or User response: The file was skipped because either
specify a new location. REPLACE NO was in effect, causing all existing files
and directories to be skipped, or REPLACE PROMPT
ANE4008E Error processing 'filespace was in effect, and when prompted, the user chose to
namepath-namefile-name': file is skip this file or all existing directories and files. No
temporarily unavailable additional action is necessary if the decision to skip the
file was deliberate. Otherwise the operation can be
Explanation: File is temporarily unavailable. retried using either REPLACE ALL REPLACE
System action: File skipped. PROMPT.
User response: Check and see if file is locked by other

process. If not, retry the command. ANE4013E Error processing 'filespace
namepath-namefile-name': invalid file
handle
namepath-namefile-name': disk full Explanation: An internal system error occurred. A file
condition operation failed because an invalid file handle was
passed.
Explanation: No more files can be restored or
retrieved because the destination disk is full. System action: Processing stopped.
System action: The client prompts you for action: User response: Report the problem to your system
administrator, and then retry the operation.
v Retry this object
v Skip this object
v Abort the action

ANE4014E ANE4022E
System action: File is skipped.

namepath-namefile-name': unknown system User response: See the appropriate Using the
error (error-code) encountered. Program Backup-Archive Client book for the particular operating
ending. system, for the file names that are handled by TSM.
Explanation: An unrecognized and unexpected
error-code occurred within the client program. This is a ANE4019E Error processing 'filespace
programming failure and the client program ends. namepath-namefile-name': file system is
locked by system
System action: processing stops.
Explanation: File system cannot be accessed because it
User response: Try the operation again. If the problem
is locked by the system.
continues, report the error to your TSM administrator.
System action: TSM cannot complete the operation.
ANE4015E Error processing 'filespace User response: See your system administrator.
namepath-namefile-name': unexpected TSM
error (error-code) encountered
ANE4020E The data format for object 'filespace
Explanation: An unexpected error occurred. This namepath-namefile-name' is unknown. The
might be a low-level system or communication error unknown format usually occurs when
that TSM cannot handle or recover from. the file was backed up or archived by a
later version of IBM Tivoli Storage
System action: processing stops.
Manager.
Explanation: When a file is backed up or archived,
continues, look for other indications of system
IBM Tivoli Storage Manager includes some additional
problems to determine where the problem exists. Most
information about the file. This message is issued if
systems have error or event logs which may contain
IBM Tivoli Storage Manager cannot recognize the
additional information. See your system administrator
information during a restore or retrieve operation. The
or TSM administrator for further help.
most likely cause is that the file was backed up or
archived with a newer version of IBM Tivoli Storage
ANE4016E Error processing 'filespace Manager. If the file was backed up from a
namepath-namefile-name': file is being case-preserving but not case-sensitive file system, the
executed; write permission denied file name might be displayed with incorrect casing. The
incorrect casing does not otherwise affect processing
Explanation: The current file cannot be opened to
since the file is skipped.
write to because it is currently being run by another
operation. System action: The file is not restored or retrieved.
Processing continues with the next file.
User response: Try the restore or retrieve operation
User response: Stop the operation that is running the
again with a current version of the IBM Tivoli Storage
file and retry the operation, or restore or retrieve the
Manager client software. If the problem persists, contact
file to a different name or directory.
IBM technical support for further assistance.

namepath-namefile-name': too many
namepath-namefile-name': file system not
symbolic links were detected while
ready
resolving name
Explanation: The file system/drive was not ready for
Explanation: While trying to resolve the file name, too
access.
many symbolic links were found.
System action: Processing stopped.
User response: Ensure that the drive is available to
User response: Ensure that you do not have a looping
TSM, and then retry the operation.
symbolic link for the file.

namepath-namefile-name': file system is
namepath-namefile-name': file name too
invalid.
long
Explanation: The drive was not available for access.
Explanation: The file name specified is too long to be
handled by TSM. System action: processing stops.
Chapter 2. ANE messages 7

ANE4023E ANE4029E
User response: Ensure that the drive is operational, Windows ME (FAT32)

and then try the operation again. If this is unsuccessful, 4,294,967,295 (4GB)
check the error log.
Windows NT/2000 (NTFS)
17,592,185,978,880 (16TB-64K)
namepath-namefile-name': file input/output
error User response: Ensure that the system limits are set
properly.
Explanation: An error was found while reading from
or writing to the file.
ANE4026W Error processing 'filespace
namepath-namefile-name': size of 'file-size'
User response: Check your system to ensure that it is exceeded the maximum file size limit on
operating properly. For OS/2, run CHKDSK /F for the your system
failing drive which can be found in dsmerror.log.
Explanation: You tried to restore or retrieve a file that
has exceeded the maximum file size limitation on your
ANE4024E Error processing 'filespace system.
namepath-namefile-name': file write error
System action: TSM cannot restore or retrieve the file.
Explanation: An error was found while writing to the
User response: Restore or retrieve this file on a system
file.
that supports the file size. See your system
System action: File skipped. administrator.
User response: Check your system to ensure that it is
operating properly. ANE4027S Error processing 'filespace
namepath-namefile-name': internal program
message 'value' encountered
namepath-namefile-name': file exceeds user Explanation: An unexpected catastrophic program
or system file limit failure occurred, indicated by value.
Explanation: A file being backed up/restored or System action: Processing stopped.
archived/retrieved exceeds system set limits for this
User response: Retry the operation. If the problem
user. Shown below are the filesize limits corresponding
continues, see your system administrator or service
to various platforms.
representative.
AIX 68,589,453,312 (64GB)
HP-UX 1,099,511,627,775 (1TB-1) ANE4028E Error processing 'filespace
namepath-namefile-name': cannot create
Linux 2,147,483,647 (2GB)
file/directory entry
Mac pre-OS9
Explanation: The directory path for files being
2,147,482,624 (2GB-1K)
restored or retrieved cannot be created.
Mac OS9
18,446,744,073,709,551,616 (16EB)
User response: Ensure that you have the proper
NetWare
authorization to create the directory for file being
4,294,963,200 (4GB -4KB)
restored or retrieved.
NUMA-Q DYNIX/ptx
4.5 1,095,216,660,480 (1TB-4GB)
OS/390 namepath-namefile-name': unable to build
4,294,967,295 (4GB) a directory path; a file exists with the
same name as a directory
SGI 18,446,744,073,709,551,615 (16EB-1)
Explanation: TSM tried to create a directory path, but
Solaris 2.6 or higher is unable to because a file exists that has the same
1,099,511,627,775 (1TB-1) name as a directory.
Tru64 UNIX System action: Processing stopped.
1,099,511,627,776 (1TB)
User response: Remove the file that has the same
UnixWare name as the directory. Refer to the last restore/retrieve
2,147,483,647 (2GB) operation and check all directories along the path.

ANE4030E ANE4037E
backed up and compressed on another client

workstation that had more memory than your client
namepath-namefile-name': disk space limit
workstation. You cannot restore this file. When the file
for this process reached
is restored, it is expanded and your workstation does
Explanation: The disk space allocated for the client not have enough memory.
owner is full.
System action: TSM canceled the operation.
User response: Obtain a machine with more memory
User response: Free up disk space and retry the and retry the operation.
restore or retrieve operation.
ANE4031E Error processing namepath-namefile-name': unknown system
'file_space_namepath_namefile_name'. Name error
exceeds an internal TSM limit.
Explanation: An unknown error occurred. This might
Explanation: During a file operation, TSM be a low-level system or communication error that TSM
encountered a filename where at least one component cannot handle or recover from.
of the file name (file_space_name, path_name or
directory_name or file_name) exceeded an internal TSM
maximum. The internal TSM limits should not be User response: Retry the operation. If the problem
confused with the operating system limits for continues, determine where the problem exists. See
file_space_name, path_name or directory_name, your system administrator for further help.
file_name.
Shown below are the TSM internal file name limits for ANE4035W File 'filespace namepath-namefile-name'
various platforms. currently unavailable on server.
AIX HP-UX Solaris Explanation: You tried to restore or retrieve a file that
File_space_name 1024
is currently not available from the TSM server.
Path_name or directory_name 1023
File_name 256 System action: TSM Cannot restore or retrieve the file.
Linux User response: Try to restore or retrieve after the file
File_space_name 1024 was made available on the server. See your system
Path_name or directory_name 768 administrator.
File_name 256
Windows XP/2000/2003 ANE4036E An error occurred saving the registry

File_space_name 1024 key.
Path_name or directory_name 248
File_name 248 Explanation: The active registry key cannot be copied
to the ADSM.SYS staging directory.
System action: The file is skipped.
System action: Registry backup operation terminates.
User response: Reduce the size of the filename so that
it is smaller that the TSM internal limits. User response: Check the space available on the
Windows boot partition to ensure there enough space
to contain a copy of the Windows registry. This might
ANE4032E Error processing 'filespace require several megabytes of free space. Also check the
namepath-namefile-name': file is not Windows permissions on the ADSM.SYS staging
compressed. directory and ensure that the Windows user under
Explanation: A file that was flagged as compressed which you are running TSM has full access to that
was not compressed, and the system failed. directory and its contents.

ANE4037E Object 'file-namefile-namefile-name'
User response: See your system administrator to changed during processing. Object
report this problem. This error is a system failure. skipped.
Explanation: The specified file-name was skipped
ANE4033E Error processing 'filespace during backup, archive, or migrate because it was
namepath-namefile-name': file compressed changing during the attempt to process it.
on a different client machine that has
more memory System action: TSM skipped the object.
Explanation: You are trying to restore a file that was User response: If you want the file backed up,

ANE4038E ANE4045E
archived, or migrated, retry the operation. If it fails, User response: Recall some files, or ask the system
determine why the object is being changed. For more administrator to increase the quota for this file system.
information on backing up, archiving, or migrating
changing objects, see your system administrator.
ANE4041W Error processing 'filespace
namepath-namefile-name': Out of free space
ANE4038E An error occurred processing file system or inodes in file system to migrate or
'filespace name'. recall.
Explanation: File system 'filespace name' is corrupted or Explanation: The file system is full. No more free
contains one or more corrupted directories and cannot space or free inodes are available to be allocated for the
be processed. transaction file that is needed when a file is being
migrated or recalled.
System action: File system is skipped.
System action: TSM terminates the current operation
User response: Check your system to ensure that it is
for this file system.
operating properly. For the Windows environment, run
CHKDSK utility for the failing drive. More information User response: Remove some files in the file system,
about corrupted directories can be found in and then run reconciliation. Retry the operation.
dsmerror.log.
ANE4042E Object name 'filespace
ANE4039E Error processing 'filespace namepath-namefile-name' contains one or
namepath-namefile-name': compressed file more unrecognized characters and is not
is corrupted and cannot be expanded. valid.
Explanation: The compressed file cannot be expanded Explanation: The file name, directory name, or
correctly due to one of the following reasons: volume label syntax is incorrect.
v There is a problem on the tape. System action: The file is skipped.
v There is a communications problem.
User response: Check the disk for errors.
v The compressed file was corrupted on the TSM
Server.
ANE4043I Total number of objects recalled: Number
System action: File skipped. of objects
User response: 1) The compressed file is corrupted Explanation: This message reports statistics or
because there is a problem on the tape. To know if this information for a client operation performed to this
is the problem, please issue the following command on server. This is logged for informational purposes.
the TSM Server: audit volume <volume_name> fix=no
If there is any problem reported, you could move the System action: Processing continues.
data from that volume to a new one (see command User response: None required.
MOVE DATA) and try again the restore. 2) There are
communications problems between the TSM Server and
the TSM Client and the results is that the file is ANE4044E Error processing 'filespace-namepath-
corrupted during the transmission. If you use a gigabit namefile-name': Case-sensitive name
ethernet adapter on the Server please upgrade the card conflict exists.
driver (AIX platform) or add provided by SUN
Explanation: While processing the specified file on the
suggested changes to some system network options
workstation, another file name was encountered with a
which have resolved this problem (SUN platform). 3)
similar name which only differed in case. The
Please verify with your network support if during the
Backup-Archive client does not allow names which
restore there are no any problems between the TSM
differ only in case on this platform and cannot
Client/Server that is originating the file corruption.
guarantee the integrity of the file, so the file is skipped.
System action: This object will be skipped.
namepath-namefile-name': file system User response: Rename the file in question to a
filespace name has exceeded its space unique name.
management quota.
Explanation: TSM detects that the file system has ANE4045E Error processing 'filespace-namepath-
exceeded its quota. No more data can be migrated out namefile-name': Case-sensitive name
of this file system. conflict exists. The directory tree will be
skipped.
System action: TSM will not migrate files from this
file system. Explanation: While processing the specified file on the

ANE4046E ANE4051E
workstation, another object name was encountered with

ANE4049I Established LAN-Free connection.
a similar name which only differed in case. The
Backup-Archive client does not allow names which Explanation: ENABLELANFREE option is set to YES
differ only in case on this platform and cannot for this session and the TSM client successfully
guarantee the integrity of the file, so the directory and established LAN-Free connection with server, after the
all of the objects contained within it are skipped. LAN-Free connection was broken.
System action: This object will be skipped. System action: The TSM client will communicate with
the server via LAN-Free.
User response: Rename the file in question to a
unique name. User response: Review the TSM error.log for
LAN-Free errors. Check your LAN-Free setup and
verify that all components are working properly.
ANE4046E There is an error processing
'filespace-namepath-namefile-name': the
object is corrupted and unreadable. ANE4050W Scheduled action 'schedule-action' did not
execute for schedule 'schedule-name' as
Explanation: You tried to read from or write to a file
the TSM administrator has been
or directory that is corrupted. The corrupted file is
disabled from executing the scheduled
skipped. If this is a directory, the objects contained in
action on the client.
the directory and its subdirectories are skipped.
Explanation: One or more of the client options -
System action: This object will be skipped.
schedcmddisabled, srvprepostscheddisabled,
User response: Check your system to ensure that the srvprepostsnapdisabled, restretrscheddisabled, have
filespace is not corrupted by using system tools like been set to YES on the client thereby preventing the
chkdsk (Windows) or fsck (UNIX). TSM administrator from executing one of the following
scheduled actions on the client - preschedule,
postschedule, presnapshot, postsnapshot or scheduled
ANE4047E There is a read error on operating system commands, restore or retrieve
'file-namefile-namefile-name'. The file is operations.
skipped.
System action: The scheduled operation will not be
Explanation: The specified file-name was skipped executed and a message will be logged to TSM Server
during backup archive because the file could not be indicating this.
read.
User response: None required.
If you are performing a JFS2 snapshot based operation,
it is possible that the snapshot was not large enough to
contain all the changes made to the filesystem after the ANE4051E Error processing 'filespace
snapshot was created. This could cause the snapshot to namepath-namefile-name': The decryption
become invalid thereby preventing TSM client from option is in effect, but the user ID
reading the snapshot. under which back-up or archive is being
run is not authorized to decrypt this
System action: TSM skipped the file. encrypted-file-system (EFS) file.
User response: Check your system to ensure that it is Explanation: The file being processed is encrypted by
operating properly. an encrypted file system (EFS). The option is specified
If you are performing a JFS2 snapshot based operation, to back-up or archive the file in decrypted form. The
please use the default snapshotcachesize of 100% and user ID under which the back-up or archive is being
ensure that the volume group has sufficient disk space run does not have decryption rights for this file.
to allocate snapshots at least as large as the file system System action: The file is skipped.
and retry the operation.
User response: There are three possible ways to make
decryption work:
ANE4048W LAN-Free connection failed.
v Re-encrypt the file under the encryption key of a
Explanation: ENABLELANFREE option is set to YES group to which both the owner and the
for this session, but an attempt to establish LAN-Free back-up/archive user IDs belong
connection failed. v Add the back-up/archive user ID to the list of users
System action: The TSM client will failover to non authorized to decrypt this file
LAN-Free support. v Run the back-up or archive under the owner's user
ID, if possible
User response: Review the TSM error.log for
LAN-Free failures. Check your LAN-Free setup and
verify that all components are working properly.

ANE4052E ANE4056E
encryption key, required to decrypt the file, is not

loaded in the kernel keyring.
namepath-namefile-name':
Encrypted-file-system (EFS) file cannot System action: The file is skipped.
be restored, because file system does
not support restore from the raw-EFS User response: There are three situations in which this
back-up data, or possibly because the problem can occur:
restore function does not have write v You just performed initial activation of EFS on the
access to the directory. AIX system, and have not logged out. AIX does load
the keys for the session running at the time of initial
Explanation: The file being processed is encrypted by activation. Solution: Logout and login again.
an encrypted file system (EFS). The file was backed up
in the raw encrypted format. Either the target v The login password has been changed recently, and
filesystem does not support the encrypted format, or you normally run with the EFS password the same
restore does not have write access to the directory to as the login password. AIX does not automatically
which the file is to be restored. change the EFS password when you change the login
password. Solution: Issue 'efskeymgr -n' to set the
System action: The restore is terminated. EFS password to be the same as the login password.
User response: v You need to run the decrypting backup when the
EFS password is different from the login password.
v The file cannot be restored to this location if the file
Solution: Issue 'efskeymgr -o ksh' to launch a new
system is not the AIX Enhanced Journaled File
shell with the keys loaded. AIX will prompt you for
System (JFS2)
the EFS password as you launch the shell. Run the
v If the file is JFS2 but EFS is not enabled, then EFS backup from the new shell.
must be enabled before the file can be restored
v If the user ID under which restore is being run does
ANE4055E Cannot update file space 'filespace-name':
not have write permission for the directory, the
the file space version on the TSM server
permissions must be changed or the restore must be
is not compatible with this client
run under a different user ID
Explanation: The file space on the TSM server is not
compatible with this client. This is caused by
ANE4053E Error processing 'filespace path filename':
performing a backup or archive operation with a client
The file cannot be restored because the
and then using a down-level client and attempting a
file system or operating system does not
backup or archive operation targeting the same file
support the Encrypting File System
space. This problem occurs specifically after a Windows
(EFS) data.
or AIX client V6.1 or higher performs a backup or
Explanation: The specified object was backed-up as archive operation and then a subsequent backup or
raw Encrypting File System (EFS) data. The client is archive operation is attempted with a client V5.5 or
trying to restore or retrieve the object to a destination lower.
that does not support the EFS data. The location might
System action: Processing stops.
not support the EFS data for one of the following
reasons: User response: Use the correct level of the client.
v The operating system does not provide the support,
or is a release that does not include the support ANE4056E Object 'object-name' returned by the IBM
v EFS support has not been activated on the operating Tivoli Storage Manager server has a
system high-level name that exceeds the
v The target file system does not support the EFS data maximum length of 6000 characters. The
file or directory cannot be processed.
System action: The object is not restored or retrieved.
Processing continues with the next object. Explanation: The IBM Tivoli Storage Manager server
returned information about a backup or archive version
User response: If this file must be restored, restore it with a high level name that exceeds 6000 characters.
to an AIX operating system environment supporting The high-level name is the directory path that contains
EFS data. the object (file or directory).
This message is displayed when all of the following
ANE4054E Error processing 'filespace conditions are true:
namepath-namefile-name': The encryption
v The object was backed up or archived by a version
key is not loaded.
6.1 or lower IBM Tivoli Storage Manager client.
Explanation: The file being processed is encrypted by v The object was backed up or archived to a version
an encrypted file system (EFS). The option is specified 5.5 or lower IBM Tivoli Storage Manager server.
to backup or archive the file in decrypted form. The

ANE4057I ANE4063W
v IBM Tivoli Storage Manager client version 6.2 or client will fail to connect to the primary server and
higher is attempting to perform an operation that processing stops.
causes the IBM Tivoli Storage Manager server to
User response: No response is required.
return information about this object to the client.
Note: During incremental backup, the server returns
information to the client about active backup ANE4060I Session established in failover mode to
versions which is used to determine which files have secondary server
changed.
Explanation: This message reports statistics or
information for a client operation performed to this
Beginning with IBM Tivoli Storage Manager server
server. This is logged for informational purposes.
version 6.1, the maximum high level name length was
reduced from 8192 characters to 6000 characters. System action: Processing continues.
Objects with high level names that exceed 6000
characters are not supported for backup or archive. User response: None required.
Beginning with IBM Tivoli Storage Manager
backup-archive client version 6.2, the maximum high ANE4061I Connected to secondary server secondary
level name length was similarly reduced. server; in fail over mode. Home server is:
System action: The file or directory specified in the home server;
message is skipped. Processing will continue with the Explanation: The node is configured for replication
next object. and has successfully connected to the secondary server.
User response: Contact your IBM Tivoli Storage This message is to notify the server administrator that a
Manager server administrator for further assistance. node has connected to the secondary server in fail over
mode.
ANE4057I The secondary server is configured as System action: Processing continues.

read-only. The file-space-name; configured User response: None.
access is read only and the request
requires read write access.
ANE4062I The secondary server access is not
Explanation: This message reports statistics or configured. Unconfigured access for file
information for a client operation performed to this space file-space-name;.
System action: Processing continues. information for a client operation performed to this
User response: None required. server. This is logged for informational purposes.
System action: Processing continues.
ANE4058I A write failure occurred while User response: None required.
attempting to save node replication
failover values to the options file.
ANE4063W IBM Tivoli Storage Manager application
Explanation: A write failure is often a result of protection did not copy the
insufficient access permissions to the options file, but SqlServerWriter.xml and/or
could also be caused by the lack of available disk SQLDBINFO.XML files from VM 'VM'.
space. The replication server connection information Individual SQL Database restore from
can not be saved and failover will not be possible. this backup is not supported.
System action: The operation failed. Explanation: The SqlServerWriter.xml and/or
User response: Check the local disk for possible sqldbinfo.xml files were not found on the guest
causes of the write error, and check to see that machine.
sufficient access to the options file is configured. System action: The operation completes. However, the
SqlServerWriter.xml or sqldbinfo.xml files were not
ANE4059I The option USEREPLICATIONFailover copied.
is set. The node will not attempt a fail User response: Make sure that the 'SQL Server VSS
over to the secondary server Writer' and the 'SQL Server' services are running on
Explanation: This option will prevent the node from this guest machine. Then try the operation again.
connecting to the replication server in the event of a
failure of the primary server.
System action: The configuration set by the TSM
administrator will be saved to the options file. The

ANE4064I ANE4085I
v If a backup copy of the file is not necessary, you can

ANE4064I Restoring vCloud Director vApp 'vapp
exclude it from backup.
name' from Organization VDC 'org vdc
name' from organization 'org name' Target
vApp name is 'restored vapp name' ANE4081E Error processing 'filespace-name': file
Restore VAPP command started. Total space type is not supported.
number of vApps to process: vapps num
to restore Explanation: The specified file space type is not
currently supported by TSM on this platform.
Explanation: The restore vApp operation completed.
System action: The unsupported file system is
System action: This message is for informational skipped. Processing continues with the next file system.
purposes only.
User response: Refer to the documentation for
User response: No action is required. information on what file space types are supported.
ANE4065E Proxy rejected: data mover node 'dm ANE4082I Node password has been reset to the
node' has not been granted proxy administrative id password.
authority for target node 'target_node',
associated with Organization vDC Explanation: The client logged in using administrative
'OVDC name' of Organization 'Org Name'. id rather than node name. The node password has been
reset to be in sync with the administrative password.
Explanation: The operation requires that a proxy
access for the data center node is granted to the data System action: Processing continues.
mover node. User response: None.
System action: Operation is canceled for the specified
vApp. ANE4083I New node password has been
User response: Run configuration wizard or generated.
configuration editor to configure proper nodes Explanation: The client logged in using administrative
relashionship. id rather than node name. New random node password
has been generated and recorded.
ANE4077E File 'filespace namepath-namefile-name' is System action: Processing continues.
encrypted by Microsoft EFS and
contains at least one sparse data stream. User response: None.
The operating system does not support
restore for this file so it is not backed ANE4084E Error processing 'filespace-namepath-
up or restored. namefile-name': cannot get file status.
Explanation: An error in the Microsoft Windows API Explanation: While processing the file, the lstat() call
prevents successful restore of files that meet the set EOVERFLOW error code.
following conditions:
System action: This file will be skipped.
v The file is encrypted by Microsoft Encrypting File
System (EFS) at the time it was backed up User response: The file is skipped. Processing
v The file includes at least one data stream (alternate continues with the next file.
"named" stream or unnamed stream) that is sparse
v The operating system is any edition of Microsoft XP, ANE4085I Assigned 'number' objects from previous
Microsoft Windows Server 2003, or Microsoft systemstate backup to the new
Windows Server 2003 R2 systemstate backup.
Because the file cannot be restored, IBM Tivoli Storage Explanation: Objects in the previous System State
Manager does not back it up. The problem is backup have not changed and were assigned to the
documented by Microsoft at http:// new System State backup.
support.microsoft.com/kb/2525290.
System action: The file is not backed up or restored.
Processing continues with the next object or ends if User response: None.
there are no further objects.
User response: If this message is issued during a
backup operation, you can do the following:
v Disable EFS encryption for the file so that it can be
backed up.

ANE4086W ANE4099E
ANE4086W Failed to assign unchanged objects from ANE4090I File server file-server-name has been
previous systemstate backup to the new upgraded to Data ONTAP version
systemstate backup. Objects will be 'version.modifcation.submodification'.
backed up. Perform a full incremental backup by
specifying option
Explanation: Objects in the previous System State
createnewbase=migrate as soon as
backup have not changed and should be assigned to
possible.
the new systemstate backup. Due to error assign
operation failed and objects will be backed up. Explanation: The file server has been upgraded to a
version that supports unicode file names for
incremental backup using snapshot difference. Perform
User response: Retry the operation. If the problem a full incremental in order to backup any files with
persists, contact TSM technical support. unicode names that may have been skipped by the
previous version of the IBM Tivoli Storage Manager
client.
ANE4087E An attempt to load data for the wizard
failed. For more information, please see System action: Processing continues.
the log file.
User response: Perform a full incremental backup by
Explanation: An attempt to load data for the wizard specifying the command line option
failed as the remote agent is probably unavailable. createnewbase=migrate with the snapdiff option as
soon as possible.
User response: Check the log for reason for the ANE4091I Starting Full VM Incremental backup of
failure. Virtual Machine 'vmname'
ANE4088I Error 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 System action: Processing continues.
User response: None required. ANE4092E Data mover platform is not supported
for instant access/restore operations.
ANE4089W File server file-server-name has been Explanation: The instant access/restore operation
upgraded to Data ONTAP version failed.
'version.modifcation.submodification'.
Perform a full incremental backup by System action: The instant access/restore operation
specifying option failed. The reason for the failure is unsupported
createnewbase=migrate as soon as platform.
possible.
User response: The instant access/restore operation
Explanation: The file server has been upgraded to a should be performed from a supported data mover
version that supports unicode file names for platform.
incremental backup using snapshot difference. Perform
a full incremental in order to backup any files with
ANE4099E The system volume cannot be
unicode names that may have been skipped by the
identified. Therefore the system state
previous version of the IBM Tivoli Storage Manager
cannot be backed up.
client.
Explanation: The system volume contains the
hardware-specific system state files that are needed to
User response: Perform a full incremental by start Windows, such as Ntldr, Boot.ini, Ntdetect.com or
specifying the command line option Bootmgr. If the system volume cannot be identified,
createnewbase=migrate with the snapdiff option as then these files cannot be backed up. Therefore it is not
soon as possible. possible to back up the system state.
System action: Systemstate backup stops.
persists, obtain a service trace that captures the
problem and contact IBM technical support for

ANE4100I ANE4111I
additional assistance. Your TSM administrator can help

ANE4106I Migrated Objects : Number of objects New
you configure the trace.
: Number of new objects
ANE4100I Objects Scanned : Number of objects
ANE4107I Candidates : Number of migration
candidates Migrated : Number of migrated
ANE4101I Files : Number of files New : Number of objects Premigrated : Number of
new files premigrated objects
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.
ANE4102I Directories : Number of directories New : ANE4108I Objects Removed : Number of objects
Number of new directories
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.
ANE4109I Searching for premigrated candidates
ANE4103I Entries Entered : Number of entries
ANE4110I Searching for largest and oldest
ANE4104I Resident Objects : Number of objects New candidates (level1)
: Number of new objects
ANE4111I Searching for largest or oldest
ANE4105I Premigrated Objects : Number of objects candidates (level2)
New : Number of new objects

ANE4112I ANE4123I
ANE4112I Searching for remaining candidates ANE4118I Objects scanned in hash : Number of
(level3) objects
ANE4113I Waiting for dsmautomig ANE4119I Premigrated candidates : Number of

objects
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
ANE4114I Waiting for a new scan
ANE4120I Level 1 candidates : Number of objects
ANE4115I Creating pool file
ANE4116I Search finished
ANE4117I Current search state :
ANE4123I Total candidates found : Number of objects

ANE4124I ANE4135I
ANE4124I NO INFORMATION AVAILABLE ANE4130I Scanned Number of objects objects per

second
ANE4125I Search is currently running. Running
since Number of seconds seconds ANE4131I ------------------------ Currently Searching:
-----------------------------
ANE4126I Scan is currently running. Running
since Number of seconds seconds ANE4132I Backup of Virtual Machine 'vmname'
started
ANE4127I Currently scanning Number of objects
objects per second ANE4133I Mount virtual machine disk on backup
proxy for VM 'vmname'
ANE4128I Scan complete
ANE4134I Incremental backup of Virtual Machine
'vmname'
server. This is logged for informational purposes. Explanation: This message reports statistics or
ANE4129I Scan time was Number of seconds seconds
ANE4135I Querying all_local drives for VM
'vmname'

ANE4136I ANE4147I

ANE4136I Searching for VM 'vmname' volumes for
backup at location: volname User response: None required.
information for a client operation performed to this ANE4142I virtual machine vmname backed up to
server. This is logged for informational purposes. nodename nodename
System action: Processing continues. Explanation: This message reports statistics or
namepath-namefile-name': exceeded User response: None required.
maximum number of links allowed
Explanation: Link cannot be restored or retrieved ANE4143I Total number of virtual machines failed:
because the destination file system has exceeded num
maximum number of links allowed.
System action: The client prompts you for action: information for a client operation performed to this
v Skip this object server. This is logged for informational purposes.
v Abort the action System action: Processing continues.
User response: Select the appropriate action for this User response: None required.
object. Restore or retrieve the link to another file
system.
ANE4144I virtual machine vmname
ANE4138I Filespace Query for 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.
server. This is logged for informational purposes. User response: None required.
User response: None required. ANE4145I Backup VM command started. Total
number of virtual machines to process:
num
ANE4139I Successful incremental backup of
Virtual Machine 'vmname' Explanation: This message reports statistics or
server. This is logged for informational purposes. System action: Processing continues.
System action: Processing continues. User response: None required.

ANE4146I Starting Full VM backup of Virtual
Machine 'vmname'
ANE4140I Backup VM command complete
ANE4147I Successful Full VM backup of Virtual
ANE4141I Total number of virtual machines Machine 'vmname'
backed up successfully: num

ANE4148E ANE4156E
System action: Processing continues. System action: The backup can not continue.
User response: None required. User response: Refer to IBM Tivoli Storage Manager
error log for detailed messages.
ANE4148E Full VM backup of Virtual Machine
'vmname' failed with RC rc ANE4153E Hostname could not be found for
Virtual Machine 'vmname'
Explanation: The Full VM backup of virtual machine
failed. Explanation: The backup of virtual machine failed.
System action: The full 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. written to the local client error log.
User response: Check the local client error log for User response: Check the local client error log for
reason for the failure. reason for the failure.
ANE4149I Total number of virtual machines ANE4154E Possible cause Virtual Machine is not
processed: num running and does not have a static IP
address.
information for a client operation performed to this Explanation: The backup of virtual machine failed.
System action: The backup of the virtual machine
System action: Processing continues. 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.
User response: Check the local client error log for
ANE4150E Incremental backup of Virtual Machine
reason for the failure.
'vmname' failed with RC rc
Explanation: The incremental backup of virtual
ANE4155E Virtual Machine 'vmname' could not be
machine volumes failed.
found on VMware server.
Explanation: The backup of virtual machine failed.
finished with failures. The next virtual machine in the
vmlist will be processed. The reason for the failure is System action: The backup of the virtual machine
written to the local client error log. finished with failures. The next virtual machine in the
ANE4151E Failure mounting Virtual Machine
'vmname'. RC=rc
ANE4156E File level VM backup of virtual machine
Explanation: The VMware failed to mount virtual
'vmname' not supported. File level VM
machine disk.
backup not support on non Windows
System action: The backup of the virtual machine can platform guest OS. Platform type:
not continue. The next virtual machine in the vmlist 'platform'.
will be processed. Refer to dsmerror.log for detailed
Explanation: The backup of virtual machine failed.
error message for the reason for the failure.
User response: Refer to dsmerror.log for detailed error
message.
ANE4152E Failure initializing VMware virtual
User response: Back up the virtual machine using the
machine environment. RC=rc. Refer to
VMBACKUPType=FULLvm option.
IBM Tivoli Storage Manager error log
for detailed error messages.
Explanation: Failure initializing VMware virtual
machine environment. Refer to IBM Tivoli Storage
Manager error log for detailed error messages.

ANE4157I ANE4164W
User response: Choose a unique name for the virtual

ANE4157I backuptype BACKUP VM of virtual
machine.
machines specified in option option.
ANE4162E The virtual machine
'virtual-machine-name' has not been
previously backed up.
Explanation: The specified virtual machine has not
User response: None required. been previously backed up, so can not be specified for
restore.
ANE4158I backuptype BACKUP VM of virtual System action: The specified virtual machine is
machines 'option'. skipped, and the next virtual machine in the restore list
is processed.
information for a client operation performed to this User response: Verify the virtual machine name to be
server. This is logged for informational purposes. restored, and re-try the operation.
ANE4163I Encryption is currently enabled, but the
virtual machine backup for
'virtual-machine-name' will not be
ANE4159E Backup of Virtual Machine 'vmname' encrypted.
failed. rc=rc.
Explanation: Virtual Machine files are not encrypted
Explanation: The backup of virtual machine failed. when backed up to the TSM server.
System action: The backup of the virtual machine System action: The virtual machine files are not
finished with failures. The next virtual machine in the encrypted during the backup processing.
User response: No user action is necessary.
ANE4164W Compression is currently enabled, but
the virtual machine backup for
'virtual-machine-name' is not compressed
ANE4160E Proxy Rejected: Proxy authority has not because client-side deduplication is not
been granted to Agent Node: 'agent_node' being used.
for Target Node: 'target_node'.
Explanation: Compression can only be used with
Explanation: The backup of virtual machine failed. virtual machine CTL and Data files when the files are
stored in a storage pool that is enabled for client-side
System action: The backup of the virtual machine deduplication. This message is issued when the client is
finished with failures. The next virtual machine in the configured for compression and virtual machine CTL or
vmlist will be processed. The reason for the failure is Data files are directed to a storage pool that is not
the node has not been granted proxy authority to enabled for client-side deduplication.
access the node named by the backup proxy node. The
TSM administrator must first grant proxy authority. System action: Backup continues, and data is not
compressed.
User response: The TSM server administrator must
grant proxy authority for this node. See the User response: If you intend to compress virtual
administrator command "Grant Proxynode". machine CTL and Data files, then update your Tivoli
Storage Manager configuration so that both types of
files are directed to storage pools that are enabled for
ANE4161E Duplicate virtual machine name client-side deduplication. If you intend to compress
'vmname' was detected in the same virtual machine Data files but not CTL files, then
backup operation. Backup of virtual update your Tivoli Storage Manager configuration so
machine 'vmfullname' can not continue that the Data files are directed to a storage pool that is
without a unique object name. enabled for client-side deduplication. Set the
Explanation: The backup of virtual machine failed. VMSKIPCTLCOMPRESSION to YES in your client
options file. If you do not intend to use compression,
System action: The backup of the virtual machine then set COMPRESSION NO in your client options file.

ANE4165E ANE4171E
ANE4165E Creating a Virtual Machine, but the ANE4169E A write failure occurred on the local
hostname 'virtual-machine-name' was not disk proxy used to temporarily store the
found. virtual machine virtual disk
information. The write failure can be
Explanation: The Virtual Machine being creating must
caused by the lack of available disk
have a valid hostname to be created.
space on the drive used to store this
System action: Check the virtual machine hostname information. The VMBACKDIR option
specified for correctness. can be used to assign a different disk
location for this purpose. Check the
User response: Correct the virtual machine hostname drive being used and ensure that there
specified and retry the restore. is enough space available for this
operation.
ANE4166E Creating a Virtual Machine, but the Explanation: There was a write error from the local
datacenter 'virtual-machine-name' was not disk used to store the virtual machine virtual disk
found. The name may be incorrect or information. Usually the write error is due to lack of
may be located in a VMware folder and disk space, lack of write permissions, or some similar
require the folder name such as problem with the local disk. The VMBACKDIR option
vmfolder/dcname. can be used to assign a different disk location if the
Explanation: The Virtual Machine being created must local drive does not have enough free space for the
have a valid datacenter to be created. operation.
System action: Processing stops. System action: A disk write error occurred, and the
operation failed.
User response: Check the virtual machine datacenter
specified for correctness. If the datacenter is contained User response: Check the local disk for possible
in a folder then the full datacenter name, complete with causes of the write error, and use the VMBACKDIR
the folder path, must be specified, such as option to assign another disk if needed.
vmfolder/dcname.
ANE4170E Can not create a Virtual Machine on
ANE4167E Creating a Virtual Machine, but the VMware release 'release-version-target'
datastore 'virtual-machine-name' was not which was backed up from VMware
found. release 'release-version-source'.
Explanation: The Virtual Machine being creating must Explanation: The Virtual Machine being created was
have a valid datastore to be created. backed up from a version of VMware which is not
compatible with the target VMware release version
System action: Check the virtual machine datastore being used for the restore.
specified for correctness.
User response: Correct the virtual machine datastore
specified and retry the restore. User response: Restore the Virtual Machine to a
VMware system which is compatible with the level
from which the Virtual Machine was backed up.
ANE4168E VMware has reported an error via their
SOAP interface. On the Detailed Status
Report panel, view the last error ANE4171E Backup of virtual machine 'vmname'
message reported. Also check the error failed. VM could not be contacted
log for more information about the because of 'vmfullname' connection state.
problem that occurred. Explanation: The backup of virtual machine failed.
Explanation: The command to VMware failed to System action: The backup of the virtual machine
complete. The error returned is displayed on the finished with failures. The next virtual machine in list
Restore or Backup summary panel under the Last Error will be processed.
Message section.
User response: Correct the connection state from
System action: An error occurred, and the operation VMware vCenter and assign VM to an ESX Server.
failed.
User response: Check the reported error and correct
the problem. Usually the reason for the error is a
user-supplied value which is not valid for the
operation.

ANE4172I ANE4178W
ANE4172I Starting Full VM backup of VMware ANE4176I Successful Full VM restore of VMware
Virtual Machine 'vmname' mode: Virtual Machine 'vmname' target node
'full_or_incr' target node name: name='target_node_name', data mover
'target_node_name' data mover node node name='data_mover_node_name'
name: 'data_mover_node_name' application
protection type:
'application_protection_type' application(s)
protected: 'application_list'
information for a client operation performed to this User response: None required.
System action: Processing continues. ANE4177E Full VM restore of VMware Virtual
Machine 'vmname' failed with RC=rc
target node name='target_node_name',
data mover node
ANE4173I Successful Full VM backup of VMware name='data_mover_node_name'
Virtual Machine 'vmname' mode:
Explanation: The Full VM restore of the virtual
'full_or_incr' target node name:
machine failed.
'target_node_name' data mover node
name: 'data_mover_node_name' System action: The full restore of the 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.
ANE4178W Compression is currently enabled, but
ANE4174E Full VM backup of VMware Virtual the virtual machine control files for
Machine 'vmname' failed with RC=rc 'virtual-machine-name' will not be
mode=full_or_incr, target node compressed because client-side
name='target_node_name', data mover deduplication is not being used for the
node name='data_mover_node_name' management class default or specified
by the -vmctlmc option for
Explanation: The Full VM backup of virtual machine
'vm-ctl-mgmt-class-name'.
failed.
Explanation: Virtual machine control files are not
System action: The full backup of the virtual machine
compressed because data is stored in a storage pool
that is not enabled for client-side data deduplication.
The virtual machine control files are not compressed
during the backup processing unless data is stored in a
User response: Check the local client error log for storage pool that is enabled for client-data
reason for the failure. deduplication.
System action: Backup continues, and control file data
ANE4175I Starting Full VM restore of VMware is not compressed.
Virtual Machine 'vmname' target node
User response: Ensure that the storage pool is enabled
name='target_node_name', data mover
for client-side data deduplication: run "q stg <pool
node name='data_mover_node_name'
name> f=d" and verify that the value of "Deduplicate
Explanation: This message reports statistics or Data?" is "yes". Ensure that client-side data
information for a client operation performed to this deduplication is enabled on the server. To enable
server. This is logged for informational purposes. client-side data deduplication, use the
DEDUPLICATION parameter on the REGISTER NODE
System action: Processing continues. or UPDATE NODE server command. Set the value of
User response: None required. 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
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

ANE4179I ANE4188I
CLIENTOPT command to set the DEDUPLICATION

ANE4184I ACTIVITY_TYPE='ACTIVITY_TYPE'
option in a client option set. To prevent the client from
overriding the value in the client option set, specify Explanation: This message reports statistics or
FORCE=YES. Ensure that the deduplication parameter information for a client operation performed to this
for the node is "ClientOrServer": The value of the server. This is logged for informational purposes.
DEDUPLICATION option on the client must be set to
YES.
ANE4179I IBM Tivoli Storage Manager application
protection did not truncate the Microsoft ANE4185I RC='RC'
SQL Server logs on VM 'VM'.
Explanation: The SQL server logs were not truncated information for a client operation performed to this
because the following option was specified for this server. This is logged for informational purposes.
virtual machine: INCLUDE.VMTSMVSS vname
OPTIONS=KEEPSQLLOG System action: Processing continues.
System action: The operation completes. User response: None required.
User response: Remove the OPTIONS=KEEPSQLLOG

option to enable truncation of the SQL logs when a ANE4186I ENTITY='ENTITY'
backup completes. Explanation: This message reports statistics or
ANE4180I BYTES='BYTES' server. This is logged for informational purposes.
Explanation: This message reports statistics or System action: Processing continues.

System action: Processing continues. ANE4187W CPU and Memory Resource Allocation
User response: None required. configuration settings cannot be restored
when the IBM Tivoli Storage Manager
data mover node is connected directly to
ANE4181I ACTIVITY_DETAILS='DETAILS' a Virtual Center managed ESX/ESXi
host. These settings have been skipped.
information for a client operation performed to this Explanation: The VMware vStorage APIs do not
server. This is logged for informational purposes. support the restore of CPU and Memory Resource
Allocation configuration settings when connected
directly to an ESX/ESXi host that is managed by a
User response: None required. Virtual Center.
System action: CPU and Memory Resource Allocation
ANE4182I AS_ENTITY='AS_ENTITY' configuration settings are skipped. Processing
continues.
information for a client operation performed to this User response: Virtual machine CPU and Memory
server. This is logged for informational purposes. Resource Allocation configuration settings will be
restored when the IBM Tivoli Storage Manager data
mover node connects directly to a vCenter Server.
User response: None required. Modify the VMCHOST to connect the TSM data mover
to a vCenter Server.
ANE4183I SUB_ENTITY='SUB_ENTITY'
ANE4188I EXAMINED='EXAMINED'

ANE4189I ANE4199W
User response: Look for errors in error log and correct

ANE4189I AFFECTED='AFFECTED'
any problems. Run configuration wizard or
Explanation: This message reports statistics or configuration editor to ensure proper nodes
information for a client operation performed to this configuration.
System action: Processing continues. ANE4194E Encryption is currently enabled, but is
not supported for incremental forever
backups of virtual machines
(-MODE=IFFULL or
ANE4190I FAILED='FAILED' -MODE=IFINCREMENTAL) .
Explanation: This message reports statistics or Explanation: Client encryption of VMware

information for a client operation performed to this incremental forever backups (-mode=IFFULL or
server. This is logged for informational purposes. -mode=IFINCREMENTAL) is not supported. In order
to avoid the unintentional storage of unencrypted data
System action: Processing continues. on the server, the backup operation stops.
User response: None required. System action: The virtual machine backup stops.
User response: Remove the encryption options for this
ANE4191E Restore VM operation failed using 'san' operation and run it again. You can use Secure Sockets
transport mode. In some cases switching Layer (SSL) encryption to encrypt the data over the
from SAN to network-based VM network. If the backup data must be encrypted in TSM
restores can be successful. storage pools, use an alternative backup method such
Explanation: Restore VM operations that fail using as full and incremental backups (-mode=FULL and
SAN transport mode can often be successful over a -mode=INCREMENTAL), or in-guest backups.
LAN path. If a restore vm operation fails using the
'SAN' transport mode, set the client option ANE4195E The target node for Organization VDC
VMVSTORTRANSPORT to "nbd:nbdssl" and try the 'OrgVDC name' in Organization 'Org
restore vm operation again. name' was not found. As a result, vApp
System action: Restore VM operation failed using 'san' 'vApp name' cannot be backed up.
transport mode. Restore may be successful using Explanation: Either the TSM node for the specified
'nbd:nbdssl' transport modes. organization VDC was not found on the TSM server, or
User response: Restore VM operation failed using information about the Organization VDC node was not
'san' transport mode. In some cases network-based VM found in the Provider VDC node.
restores can be successful when using 'nbd' or 'nbdssl' System action: Back up of the specified vApp stops.
transport modes. The VMVSTORTRANSPORT option Processing continues to the next vApp.
can used to restrict the TSM client to use only the
specified transport modes. User response: Go to the Configuration page and click
'Run the Configuration Wizard' to verify that all
required TSM nodes are registered on the TSM server.
ANE4192I Years='Years' Months='Months' If required, register a new data mover node. Make sure
Days='Days' Hours='Hours' that the organization VDC belongs to the provider
Minutes='Minutes' Seconds='Seconds' VDC that this data mover node protects.
information for a client operation performed to this ANE4198I Total bytes after deduplication: bytes
System action: Processing continues. information for a client operation performed to this
ANE4193E vApp 'vApp name' cannot be processed User response: None required.
because data mover 'dm node' cannot
connect to the target node 'target_node'.
ANE4199W File 'file name' is not backed up as part
Explanation: The operation requires that a proxy of the system state because cluster disk
access for the data center node is granted to the data 'volume name' is not accessible.
mover node.
Explanation: The indicated file or directory was
System action: Operation is canceled for the specified returned by VSS as part of the backup file list of the
vApp.

ANE4200I ANE4207I
writer. However, the cluster disk where the file is Windows Installer error codes, search on "Windows
located is not accessible. The reasons for this problem Installer Error Messages" document at the Microsoft
can be that the cluster disk is offline or belongs to Developers Network site: msdn.microsoft.com.
another node.
Check the install log on the client computer.
System action: The file is not backed up. Processing
continues.
ANE4203I The Deployment Manager successfully
User response: This problem is documented in retrieved system information.
Microsoft knowledge base topic 980794
http://support.microsoft.com/kb/980794. The topic
includes a hotfix. With the hotfix, you can specify a
registry key that contains a list of one or more files to
be excluded from VSS enumeration. IBM Tivoli Storage System action: Processing continues.
Manager does not back up files that are not
enumerated by VSS. If the volume is brought online to User response: None required.
the node performing the system state backup, then it
cannot be backed up. You must remove the volume ANE4204E The Operating System of the client
from the registry key and restart the system before you computer: os name is not supported by
can back up the volume. If you do not want to the target version: target version.
implement the hotfix for this problem, IBM Tivoli
Storage Manager continues to issue this message. Explanation: The operating system level of the client
computer is no longer supported by the target level.
ANE4200I architecture, schedule-name, domain-name: System action: Processing stops.

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 information about Microsoft System action: Processing continues.

ANE4208E ANE4217E

ANE4213E Automatic restart of the client computer
was required because reason
ANE4208E The Deployment Manager could not
Explanation: The Deployment Manager determined
shut down TSM service: service name.
that the deployment requires restarting the client.
Explanation: None
Automatic restart is not enabled. The Deployment
System action: Processing continues. Manager process cancels the deployment.
User response: None The current client is not uninstalled or updated.

System action: Deployment Manager cancels the client
ANE4209I The Deployment Manager successfully deployment and stops
installed package: client package name.
User response: Reschedule the client deployment.
ANE4214E The operating system platform of the
client package 'OS platform of package' is
System action: Processing continues. incompatible with the client computer
'OS platform of client computer'.
Explanation: None
ANE4210E The Deployment Manager failed to System action: Processing stops.

install package: client package name. The
User response: Reschedule the client deployment. Use
Microsoft Installer error code was error
a client package with the appropriate operating system
code.
platform.
Explanation: The previous client package has been
uninstalled, and the installation of the new client
ANE4215E The automatic deployment path from
package failed.
the current client code version 'source
System action: Processing stops. version' to the client package version
'target version' is not supported.
User response: For information about Microsoft
Installer error codes go to the Microsoft Developers Explanation: None
Network (http://msdn.microsoft.com/en-US/) and
search for "Windows Installer Error Messages".
User response: Refer to the Tivoli Storage Manager
Backup-Archive Client documentation in the
information center.
Reschedule the client deployment with an appropriate
restarted service: service name.
target level.
ANE4216E The TSM API library version API version
is at an earlier version than the version
System action: Processing continues. of the client package package version.
User response: None required. Explanation: The client package for automatic
deployment is invalid. In the client package, the API
version does not match the Deployment Manager
ANE4212E The Deployment Manager failed to version.
restart service: service name.
System action: Deployment Manager stops processing.
Explanation: After the automatic client deployment,
the TSM client services failed to start. User response: Please make sure that the installation
package is valid.
User response: Log on to the client machine and ANE4217E The Deployment Manager received an
check the backup-archive client error log. error while setting up the client API.
The standard API function being
invoked is API setup function name.
Explanation: The Deployment Manager process failed
when setting up the client API.

ANE4218E ANE4226E
System action: Processing stops. System action: Processing stops.

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

ANE4227E ANE4234E
information on the format of the post schedule

ANE4230I The client computer will be shut down
command of the client deployment schedule.
and restarted immediately.
Explanation: The Deployment Manager needs to
ANE4227E The Deployment Manager failed to
restart the client computer to complete the client
install package: client package name. The
deployment. It is possible the other messages provide
client computer is out of disk space. The
details of the deployment.
Microsoft Installer error code was error
code. System action: The Deployment Manager process
continues. The client computer will be shut down and
Explanation: The previous client package has been
restarted immediately after all language packs are
uninstalled, and the installation of the new client
deployed, or immediately if there are no language pack
package failed because the client computer is out of
to install.
disk space.
User response: None
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
possible the other messages provide details of the
deployment.
ANE4228E The Deployment Manager failed to
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.
User response: Check the error log on the client
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. Reschedule 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
install one or more language packs. It is possible the
other messages provide details of the installation.

ANE4235I ANE4243I
System action: The Deployment Manager process

ANE4239E Processor Architecture information is
continues.
missing in the client package.
User response: Check the error log and installation on
Explanation: It is possible the client deployment
the client computer. Identify the language packs that
package is missing or corrupted.
failed to install and manually deploy them.
System action: Processing stops. Client deployment
will not start.
ANE4235I The deployment manager cannot log
events to the server. User response: Ensure that the client package is
available and imported to the server correctly.
Explanation: The Deployment Manager is unable to
log events to the server. It is possible the other
messages provide details of the communications. ANE4240E Client version information is missing in
the client package.
continues. Events will be logged locally on the client Explanation: It is possible the client deployment
machine only. package is missing or corrupted.
User response: Check network connection and the System action: Processing stops. Client deployment
error log on the client computer. will not start.
User response: Ensure that the client package is
ANE4236E The setup script was unable to query available and imported to the server correctly.
the registry for the Tivoli Storage
Manager client installation directory.
ANE4241I Architecture of the package: package
Explanation: The setup script encountered an error architecture does not match the current
while querying the Windows registry for client: system architecture. The setup
[HKLM\SOFTWARE\IBM\ADSM\CurrentVersion\ script is attempting to retrieve the
BackupClient]. matching package.
System action: Processing stops, and client Explanation: The setup script is trying to retrieve the
deployment will not begin. matching client package from the server.
User response: Check the release documentation for System action: Processing continues.
information on supported Windows platforms and
User response: Ensure that the client packages for all
ensure the REG.EXE command is available on the client
architectures are available on the server.
computer.
ANE4242E The setup script encountered a warning

ANE4237W Query system information was
or error while retrieving the client
completed with warnings or errors.
package for architecture. The error level
ErrorLevel was error level
is error level.
Explanation: The setup script encountered warnings
Explanation: It is possible the client package is not
or errors while querying system information.
available on the server.
System action: Processing continues. The Deployment
Manager will check to see if required system
information is available. Client deployment could be User response: Ensure that client packages for all
cancelled if required information is missing. architectures are available on the server. Check the
backup-archive client error log for more detailed error
User response: Check the error log of the
messages.
backup-archive client for warning and error messages.
ANE4243I The setup script successfully retrieved

ANE4238E Processor Architecture information is
the client package for architecture.
missing in the system information.
Explanation: The client package that was downloaded
Explanation: It is possible the setup script
matches the processor architecture of the current client.
encountered a warning or error while querying system
information. System action: Processing continues.
System action: Processing stops. Client deployment User response: None
will not start.
User response: Check the error log of the
backup-archive client for warning and error messages.

ANE4244E ANE4252E
ANE4244E The setup script failed to install the ANE4249E The setup script was unable to query
Microsoft Visual C++ redistributable the registry for the client scheduler
package. Error Level is error level. service name.
Explanation: The Microsoft Visual C++ redistributable Explanation: The setup script encountered an error
package is required by the new client. while querying the Windows registry for
[HKLM\SOFTWARE\IBM\ADSM\CurrentVersion\
BackupClient\Scheduler Service].
User response: Check the installation log file for
System action: Processing stops, and client
names with "vcredist*.log" file in system temp directory.
deployment will not begin.
User response: Check the release documentation for
ANE4245I The setup script successfully installed
information on supported Windows platforms and
the Microsoft Visual C++ redistributable
ensure the REG.EXE command is available on the client
package.
computer.
Explanation: The Microsoft Visual C++ redistributable
package is required by the new client.
ANE4250E There is already a deployment manager
System action: Processing continues. running on this computer.
User response: none Explanation: Only one instance of client deployment

manager can be active at a time. This client computer
might be configured with multiple node names, but the
ANE4246E The setup script failed to start the new client code only needs to be deployed to one node
Deployment Manager program. Error per computer. Each client deployment instance can take
Level is error level. a few minutes to complete.
Explanation: The setup script could not start the client System action: Processing stops.
deployment process.
User response: Ensure only one client deployment
System action: Processing stops. task is scheduled to run at a time.
User response: Check the log files on the client
computer for more details. Ensure the client package is ANE4251W writername file 'filename': not found.
not corrupted.
Explanation: The indicated VSS writer file or directory
was returned by VSS as part of the backup file list of
ANE4247I The setup script successfully started the the writer. However, the object does not exist on the
Deployment Manager program. disk. .
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: Refer to the Tivoli Storage Manager User response: Ensure that the Windows Task
Backup-Archive Client documentation in the Scheduler service is running. It is possible that the
information center. system event log contains more details about the
failure. Reschedule the client deployment.
Reschedule the client deployment with an appropriate
target level.

ANE4253E ANE4261E

ANE4253E There was not enough disk space on the
client computer. Required space: package User response: Check the error log file on the client
space bytes; available space: system space workstation.
bytes.
Explanation: The deployment manager determined ANE4258E The deployment manager received the
there was insufficient free disk space for the client Windows "OpenSCManager failed" error
deployment. message.
System action: Processing stops. Explanation: The deployment manager could not
connect to the Windows service control manager to
User response: Free up required disk space and
start the client scheduler. In general, this error occurs
reschedule the client deployment.
because the user who is initiating the task does not
have sufficient authority.
ANE4254E The deployment manager detected an
HSM client on the workstation that it
needs to deploy the Backup-Archive User response: Ensure that the user who starts the
client to. client scheduler has administrative privileges.
Explanation: An attempt was made to deploy the
Backup-Archive client to a workstation that already has ANE4259E The client scheduler is not started as a
the HSM client installed. The Backup-Archive client root user.
cannot be deployed to a workstation that has the HSM
client. 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. User response: Log in as root and start the client
scheduler.
ANE4255E There is not enough memory for the

deployment manager to create the ANE4260E The installation file system is not
system information object writeable.
Explanation: The system information object could not Explanation: The deployment manager cannot write
be created because there is not enough available RAM to the installation file system.
to temporarily write the data into. System action: Processing stops.
System action: Processing stops. User response: Check the installation file system
User response: Close all unneeded applications on the permissions. It is possible that the current client node
client workstation and reschedule the deployment. runs in a virtualized environment using the client code
installed in a shared storage of the physical
environment. Reschedule the client deployment with
ANE4256E The DSMI_DIR environment variable is the client node in the physical environment.
not defined.
Explanation: The deployment manager cannot initiate ANE4261E The deployment manager cannot
a connection to the server because the DSMI_DIR upgrade the Backup-Archive Client.
environment variable is not set. This error can occur if
the deployment manager is started without using the Explanation: The Backup-Archive Client cannot be
client scheduler. upgraded because either the current location is not the
default installation location or the DSM_DIR,
System action: Processing stops. DSMI_DIR, DSM_CONFIG and DSMI_CONFIG
environment variables are defined with a relative path
User response: Read the available documentation to
and not an absolute path.
determine how to use the client scheduler to create a
client deployment task. System action: Processing stops.
User response: Check the installation directory of the
ANE4257E The deployment manager cannot parse current Backup-Archive Client. If the Backup-Archive
information in file: file name. Client is not installed in the default location, manually
upgrade the Backup-Archive Client. If the DSM_DIR,
Explanation: The deployment manager could not
DSMI_DIR, DSM_CONFIG and DSMI_CONFIG
parse or extract the required information from the
environment variables are defined with a relative path,
specified file.

ANE4262E ANE4270I
define them with an absolute path and try the client

ANE4266I The deployment manager failed to
deployment again.
install non-English language pack(s).
Explanation: The previous packages were uninstalled,
ANE4262E The preview of the client installation
and the installation of one or more new language packs
failed.
were not successful.
Explanation: The deployment manager did not
uninstall the current client. The client code is
unchanged. User response: Check the deployment trace file on the
client workstation for specific language pack
information.
User response: Check the deployment manager log
and trace files on the client workstation for specific
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.
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.
User response: Obtain log and trace files from the
download directory for problem determination. The
files are found within the log/ sub-directory.

ANE4271E ANE4279I
ANE4271E The deployment package is missing one ANE4275E The deployment manager cannot restart
or more required installation image the scheduler or the CAD processes.
files.
Explanation: Before exiting, the deployment manager
Explanation: The client deployment package might could not restart the Backup-Archive Client scheduler
not have been imported correctly to the server. It is or CAD processes. The deployment manager stopped
possible that the deployment package is not retrieved the processes prior to the client upgrade.
completely to the client computer, due to a lack of disk
space.
User response: Log on to the Backup-Archive Client
workstation and check the error log file. If you have set
User response: Ensure that client packages are environment variables make sure they are not defined
available on the server and there is sufficient disk space using relative path.
on the client computer. Check the backup-archive client
error log file for more detailed error messages.
ANE4276E The deployment manager cannot obtain
information about the scheduler or the
ANE4272E The processor type of the package: CAD processes.
package processor type does not match the
Explanation: The deployment manager needs process
current client: system processor type. .
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 TSM version being
Explanation: An attempt was made to deploy the deployed is supported by the target operating system.
Backup-Archive Client to a workstation that already
has the JBB client installed. On some platforms, the
Backup-Archive Client cannot be deployed to a ANE4278E The deployment manager cannot obtain
workstation that has the JBB client installed. information about the Logical Volume
Snapshot Agent (LVSA).
Explanation: The deployment manager needs to
User response: Uninstall the JBB client and reschedule determine whether an LVSA is installed on the client
the Backup-Archive Client deployment. workstation.
ANE4274E The deployment manager cannot stop
the scheduler or the CAD processes. User response: Log on to the Backup-Archive Client
workstation and check the error log file and the
Explanation: The deployment manager tried to shut deployment manager error log file.
down the Backup-Archive Client scheduler or CAD
processes but the Backup-Archive Client might be busy
with other tasks. ANE4279I Server information is not available in
the deployment schedule.
User response: Reschedule the Backup-Archive Client information for a client operation performed to this
deployment. server. This is logged for informational purposes.

ANE4280E ANE4289I
User response: None required. System action: Processing stops.

User response: Free up the required amount of disk
ANE4280E Automatic client deployment is not space and reschedule the automatic client deployment.
allowed on the client workstation.
Explanation: One or more of the running client ANE4284E The deployment is cancelled because an
services include AUTODEPLOY = NO in the option automatic client deployment task was
file. scheduled for a sparse-root, non-global
zone that shares the /usr file system
with the global zone.
User response: Change the AUTODEPLOY option on
Explanation: The automatic client deployment task
the client and reschedule the client deployment.
that was attempted is not supported and will be
cancelled.
ANE4281E The update manager cannot remove the
TIVsmCapi package from non-global
zone(s): zone name. User response: Install the Backup-Archive Client from
the global zone or manually upgrade the
Explanation: APAR IC57433 prevents the removal of
Backup-Archive Client.
the TIVsmCapi package on Solaris on a sparse-root,
non-global zone if uninstalling is done from the global
zone. ANE4285E The update restore operation to an
existing virtual machine 'VmName'
failed. The virtual machine is not in
User response: Manually uninstall the Tivoli Storage power off state.
Manager client directly from the non-global zones and
Explanation: The update restore operation to an
reschedule the deployment.
existing virtual machine is not supported for a running
machine and will be aborted.
ANE4282E Sparse-root non-global zone(s) were
System action: Restore aborted.
found with Tivoli Storage Manager
Backup-Archive Client that was User response: Turn off the virtual machine and
installed from the non-global zone: zone re-run the update restore command.
names.
Explanation: One or more non-global zones are ANE4286I SCHEDULE_NAME=
sharing the /usr file system with the global zone. The 'SCHEDULE_NAME'
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
cannot update the Tivoli Storage Manager
Backup-Archive Client in the global zone because it System action: Processing continues.
will update the version of GSKit that is shared with the
sparse-root non-global zones that are not part of the User response: None required.
automatic deployment.
System action: Processing stops. ANE4289I Backup of VMware vApp 'vApp name' in
Organization VDC 'Org VDC name' of
User response: Manually upgrade the Backup-Archive organization 'Org name' completed
Client or install it from the global zone without using successfully mode: 'Incremental Forever
the -G parameter. This ensures that you have the same - full_or_incr' target node name:
version between the global zone and the sparse-root 'target_node_name' data mover node
non-global zones, and you can then deploy the client name: 'data_mover_node_name' VMs
automatically on all such zones. backup status: number of VM backed up
out of number of VMs in vApp VMS
backed up successfully
ANE4283E There is not enough disk space on path
to uncompress GSKit packages. Explanation: This message reports statistics or
Required space: req_space bytes; information for a client operation performed to this
available space: avail_space bytes. server. This is logged for informational purposes.
Explanation: The deployment manager determined System action: Processing continues.
that there is not enough free disk space to uncompress
GSKit packages. User response: None required.

ANE4290E ANE4298E
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 Number of vApps backed up User response: Check the warning messages from the
successfully: total number Number of server administration center, the server activity log, or
vApps failed: total number error log on the client computer for more information.
information for a client operation performed to this ANE4298E architecture, schedule-name, domain-name:
server. This is logged for informational purposes. The client deployment was canceled.
System action: Processing continues. The previous event causing the
cancellation is: event.
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

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

ANE4324I ANE4907E
ANE4324I Starting backup of VMWare vCloud ANE4903I Successful instant access of VMware
Director vApp 'vapp name' from Virtual Machine 'vmname' target node
organization VDC 'org vdc name' of name='target_node_name', data mover
organization 'org name'. mode: node name='data_mover_node_name'
'full_or_incr' target node name:
'target_node_name' data mover node
name: 'data_mover_node_name' number of
virtual machines: 'num vms'
System action: Processing continues. ANE4904E Instant access of VMware Virtual
Machine 'vmname' failed. target node
ANE4900W Schedule 'schedule-name' has opened a
Explanation: The instant access of the virtual machine
new session with the server.
failed.
Explanation: A scheduled event endsbecause of a
System action: The instant access of the the virtual
connection failure. The scheduled event had to be
machine finished with failures. The reason for the
restarted outside its normal startup window to
failure is written to the local client error log.
continue the operation.
System action: The scheduled event is completed
using more than one session.
User response: None required. If this is a recurrent
ANE4905I Starting instant restore of VMware
condition, you may want to check for network
problems.
ANE4901E The following object contains one or
more unmatched quotation marks and
cannot be processed: 'filespace path
filename'.
Explanation: The file name in the file list contains
unmatched quotes. If a line in the file list begins with a User response: None required.
single or double quotation mark this quotation mark is
considered to be an opening quotation mark. The
corresponding closing quotation mark of the same type ANE4906I Successful instant restore of VMware
must be at the end of the line. If there is no closing Virtual Machine 'vmname' target node
quotation mark or the closing quotation mark has been name='target_node_name', data mover
encountered in the middle of the line, it is an invalid node name='data_mover_node_name'
input. Explanation: This message reports statistics or
System action: The object is skipped. information for a client operation performed to this
User response: Correct the specification of the object.
ANE4902I Starting instant access of VMware User response: None required.

name='target_node_name', data mover ANE4907E Instant restore of VMware Virtual
node name='data_mover_node_name' Machine 'vmname' failed. target node
Explanation: This message reports statistics or name='target_node_name', data mover
information for a client operation performed to this node name='data_mover_node_name'
server. This is logged for informational purposes. Explanation: The instant restore of the virtual machine
System action: Processing continues. failed.
User response: None required. System action: The instant restore of the the virtual
machine finished with failures. The reason for the
failure is written to the local client error log.

ANE4908I ANE4942E
User response: Check the local client error log for User response: None required.
ANE4913I Backup for 'Data Protection Product'
ANE4908I Starting cleanup of VMware Virtual finished.
Machine 'vmname' from snapshot of
'origvmname' target node
System action: Processing continues. ANE4939I Total snapshot difference objects:
Number
ANE4909I Successful cleanup of VMware Virtual
Machine 'vmname' from snapshot of
'origvmname' target node System action: Processing continues.
node name='data_mover_node_name' User response: None required.

information for a client operation performed to this ANE4940I Backing up object 'writer-name'
server. This is logged for informational purposes. component 'component-name' using
shadow copy.
User response: None required. information for a client operation performed to this
ANE4910E Cleanup of VMware Virtual Machine System action: Processing continues.
'vmname' failed. target node
name='target_node_name', data mover User response: None required.
Explanation: The cleanup of the virtual machine ANE4941I Backup of object 'writer-name'
failed. component 'component-name' finished
successfully.
System action: The cleanup of the the virtual machine
finished with failures. The reason for the failure is Explanation: This message reports statistics or
written to the local client error log. information for a client operation performed to this
reason for the failure. System action: Processing continues.
ANE4911I VMware Virtual Machine 'vmname' is
ready for use ANE4942E The file specification 'string' is invalid.
Explanation: This message reports statistics or Explanation: The operating system indicated that the
information for a client operation performed to this file specification is invalid. One possible reason is that
server. This is logged for informational purposes. the file specification contains unrecognized characters.
System action: Processing continues. Another possible cause is incorrect use of quotation
marks in the file specification.
ANE4912I Backup for 'Data Protection Product' User response: Enter a correct file specification as
started successfully. described in the Using the Backup-Archive Client book
for the particular operating system. Ensure that the file
Explanation: This message reports statistics or specification contains valid characters. Verify correct
information for a client operation performed to this use of quotation marks for specifications that contain
server. This is logged for informational purposes. blanks spaces. If multiple file specifications are used,
make sure that any use of quotation marks does not

ANE4943I ANE4952I
cause the file specifications to be treated as a single file command with the -preview option to display a listing
specification. of the disk labels which exist on the virtual machine.
Check the spelling of the disk label and correct the disk
label and then retry the 'backup vm' operation.
ANE4943I Existing filespace name 'filespace-name'
has been renamed to 'filespace-name'
ANE4948E A specified virtual disk was not found
on the virtual machine.
server. This is logged for informational purposes. Explanation: You must specify a virtual disk label
name which exists on the virtual machine.
User response: For a backup operation, use the "dsmc
backup vm ..." command with the -preview option to
ANE4944I Virtual machine: 'vm-name' disk:
display a listing of the disk labels which exist on the
'disk-name' is excluded by user.
virtual machine. For a restore operation, use the "dsmc
Explanation: This message reports statistics or query vm ..." command with the -detail 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 backup. Check the spelling of the disk
label and correct the disk label and then retry the
System action: Processing continues. operation.
ANE4949I Virtual machine: 'vm-name' disk:
ANE4945I Virtual machine: 'vm-name' disk: 'disk-name' was excluded when the
'disk-name' is included by user. backup was performed.
ANE4946W Warning: virtual machine: 'vm-name' ANE4950I Virtual machine: 'vm-name' disk:
disk: 'disk-name' excluded by user, was 'disk-name' is excluded from restore by
not found. user.
Explanation: The specified virtual disk does not exist Explanation: This message reports statistics or
on the virtual machine. information for a client operation performed to this
User response: Use the "dsmc backup vm ..."
command with the -preview option to display a listing User response: None required.
of the disk labels which exist on the virtual machine.
Since the disk was specified to be excluded from the ANE4951I Total number of objects assigned:
backup, the backup will continue. However it is Number of objects
possible that a disk will included in the backup which
was not desired, check the spelling of the disk label, Explanation: This message reports statistics or
and correct the disk label if an undesired disk is now information for a client operation performed to this
included in the backup operation. server. This is logged for informational purposes.
ANE4947E Error: virtual machine: 'vm-name' disk:
'disk-name' included by user, was not
found.
ANE4952I Total number of objects inspected:
Explanation: The specified virtual disk does not exist
Number of objects
on the virtual machine.
User response: Use the "dsmc backup vm ..." server. This is logged for informational purposes.

ANE4953I ANE4964I

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
ANE4958I Total number of objects updated:
Number of objects
server. This is logged for informational purposes. User response: None required.

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

of objects ANE4974E Error processing 'filespace
namepath-namefile-name': a required NT
Explanation: This message reports statistics or privilege is not held.
server. This is logged for informational purposes. Explanation: The user account running TSM does not
possess a required NT user right/pr ivilege for
System action: Processing continues. performing the current operation.
User response: None required. System action: The object is skipped.
User response: Your system administrator has the
authority to grant the needed privilege.

ANE4975I ANE4986I
ANE4975I Total number of bytes processed: ANE4981I Deduplication reduction: Number%

Number of bytes
ANE4982I Total objects deduplicated: Number of
ANE4976I Total data reduction ratio: Number% objects
ANE4977I Total number of bytes inspected: bytes ANE4983I Files Deduplicated:

ANE4978I Deduplication Reduction: ANE4984I Total bytes before deduplication: number

of bytes
ANE4979I Total Data Reduction:
ANE4985I Session
ANE4980I Total Bytes Inspected:
ANE4986I Node

ANE4987E ANE4996I
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 TSM.
another process. You tried to read from or write to a
System action: TSM logs the application message.
file that is currently being used by another process.
User response: Refer to the documentation for the
application that you are using.
User response: Ensure that the file is not locked by
another process. If the file is not locked, retry the
ANE4992W Application Type Application Message Id
command.
Application Message
Explanation: This is a message sent by the application
ANE4988W File 'filespace namepath-namefile-name' is
you are currently running with TSM.
currently unavailable on server and has
been skipped. System action: TSM logs the application message.
Explanation: You tried to restore or retrieve a file that User response: Refer to the documentation for the
is currently not available from the TSM server. This is application that you are using.
most likely a temporary condition.
System action: TSM 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 TSM administrator for you are currently running with TSM.
assistance.
System action: TSM logs the application message.
ANE4989E Error processing 'filespace User response: Refer to the documentation for the
namepath-namefile-name': the directory is application that you are using.
in use by another process. All objects in
the directory and any of its ANE4994S Application Type Application Message Id
subdirectories are skipped. Application Message
Explanation: The specified directory is being used by Explanation: This is a message sent by the application
another process. You tried to read from or write to a you are currently running with TSM.
directory that is currently being used by another
process. The objects contained in the directory and its System action: TSM logs the application message.
subdirectories are not backed up. User response: Refer to the documentation for the
System action: Processing stopped for that directory. application that you are using.
If other files and directories were also specified in this
backup, they are processed ANE4995I @1%s @2%s @3%s
User response: Ensure that you specified the correct Explanation: This message reports statistics or
directory name, correct the permissions, or specify a information for a client operation performed to this
new location.If the directory name is correct, retry the server. This is logged for informational purposes.
backup when no process has exclusive use of the
directory. System action: Processing continues.
ANE4990I @1%s
Explanation: This message reports statistics or ANE4996I @1%s @2%s @3%s
System action: Processing continues. server. This is logged for informational purposes.
User response: None required. System action: Processing continues.


ANE4997E ANE4999I

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, contact IBM 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 IBM Tivoli Storage Manager server. Some ANR
messages are common to all server platforms, and some are specific to platform.
ANR messages list

IBM Tivoli Storage Manager server ANR messages are listed in ascending numeric
order. All parts of the message are documented, including message ID, message
text, explanation, system action, and user response.
Explanation: The minimum memory required is 12

ANR0010W Unable to open message catalog for
GB. 16 GB is required if you are using data
language language. The default language
deduplication. At least 32 GB is needed for heavily
message catalog will be used.
used servers. Using 32 GB or more of memory
Explanation: The message catalog for the specified enhances performance of the Tivoli Storage Manager
language could not be found. server database inventory.
System action: The server continues to initialize with If you plan to run multiple instances, each instance
the default English message catalog. requires the memory listed for one server. Multiply the
memory for one server by the number of instances
User response: To resolve the issue, complete the
planned for the system.
following steps:
v If you specified a LANGUAGE option in the server Node replication processing requires additional
options file, verify that you specified a supported memory. Use a minimum of 32 GB of memory for node
language. replication without data deduplication. Node
replication with data deduplication requires a
v If you specified environment variables for the
minimum of 64 GB of memory. You will require an
system locale, ensure that you specified a supported
active log at least 64 GB in size to run replication. If
locale and that the locale is installed on your system.
replication and deduplication are both being used, an
v Ensure that the Tivoli Storage Manager language active log at least 128 GB in size is required.
package for the specified language is installed on
your system. System action: Server operation continues.
v Restart the server. User response: Increase the amount of memory on the
system.
ANR0011W Unable to set locale to first locale. Using
locale second locale for message ANR0099W This operating system is not supported.
formatting.
Explanation: The system has detected one of the
Explanation: The first locale could not be set. following items:
System action: The server continues to initialize using v a release of the operating system that is not
the second locale. supported
v the required maintenance for the operating system is
User response: To resolve the issue, complete the
not installed
following steps:
v If you specified a LANGUAGE option in the server See the software requirements section in the
options file, ensure that you specified a supported information center for more details.
locale and that the locale is installed on your system.
System action: Server operation continues.
v If you specified environment variables for the
system locale, ensure that you specified a supported User response: See the software requirements section
locale and that the locale is installed on your system. in the information center and upgrade to a supported
v Restart the server. operating system.
ANR0098W This system does not meet the ANR0100E Source file(line number): Error error code
minimum memory requirements. creating table "table name".

ANR0101E ANR0106E
Explanation: An internal error has occurred in an An error code value of 2 indicates that the record being
attempt to create a server database table. This message updated does not exist in the database. This type of
always accompanies another error message and error might be caused by a timing issue with the server
provides more detail about that error. or a synchronization issue involving server processes,
client sessions, or other server actions. Review the
System action: The activity that generated this error
activity log file to determine what operations were in
fails.
progress and were affected by this error. Try the
User response: Contact your service representative. operation again and change the timing so that it does
not run with the same processes or actions as when the
error occurred.
ANR0101E Source file(line number): Error error code
opening table "table name".
Explanation: An internal error occurred when a server deleting row from table "table name".
database table was being accessed. This error message
always accompanies another error message which Explanation: An internal error occurred when data
provides more details about the error. was being removed from a server database table. This
error message always accompanies another error
System action: The activity that generated this error message which provides more details about the error.
fails.
User response: If the server or storage agent stops in fails.
response to a HALT command, you can ignore this
error message. 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.
ANR0102E Source file(line number): Error error code An error code value of 2 indicates that the record being
inserting row in table "table name". deleted does not exist in the database. This type of
Explanation: An internal error occurred when data error might be caused by a timing issue with the server
was added to a server database table. This error or a synchronization issue involving server processes,
message always accompanies another error message client sessions, or other server actions. Review the
which provides more details about the error. activity log file to determine what operations were in
progress and were affected by this error. Try the
System action: The activity that generated this error operation again and change the timing so that it does
fails. not run with the same processes or actions as when the
User response: An error occurred when a row was error occurred.
inserted into a server database table. Typically, this
error causes an error code value of 1 to be displayed. ANR0105E Source file(line number): Error setting
An error code value of 1 indicates that the record being search bounds for table "table name".
inserted already exists in the database. This type of
error might be caused by a timing issue with the server Explanation: An internal error occurred when data
or a synchronization issue involving server processes, was being accessed from a server database table. This
client sessions, or other server actions. Review the error message always accompanies another error
activity log file to determine what operations were in message which provides more details about the error.
progress and were affected by this error. Try the System action: The activity that generated this error
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: Review the activity log file to
determine what operations were in progress and were
affected by this error. Try the operation again and
ANR0103E Source file(line number): Error error code change the timing so that it does not run with the same
updating row in table "table name". processes or actions as when the error occurred.
Explanation: An internal error occurred when data
was updated in a server database table. This error ANR0106E Source file(line number): Unexpected error
message always accompanies another error message error code fetching row in table "table
which provides more details about the error. name".
System action: The activity that generated this error Explanation: An internal error occurred when data
fails. was being accessed from a server database table. This
User response: An error occurred when a row was error message always accompanies another error
inserted into a server database table. Typically, this message which provides more details about the error.
error causes an error code value of 2 to be displayed.

ANR0107W ANR0113E
System action: The activity that generated this error install date or has suddenly moved into the future by
fails. 30 days or more.
User response: Review the activity log to determine System action: The server is disabled for client, server
what operations were in progress and were affected by and administrative access. Most server processes will
this error. Try the operation again and change the not execute.
timing so that it does not run with the same processes
User response: If the current system date is not valid,
or actions as when the error occurred.
reset the date. Use the ACCEPT DATE command to
establish the current date as valid on the server. After
ANR0107W Source file(line number): Transaction executing this command, you can use the ENABLE
transaction ID was not committed due to SESSIONS ALL command to enable the server for
an internal error. sessions. Accepting an invalid date can cause any of the
following problems: Premature deletion of data
Explanation: An internal error was detected during
Excessive retention of data Scheduling problems Event
transaction commit. This message is typically preceded
record problems Password expiration problems.
by another error message which provides more details
about the error.
ANR0111E Command: The BEGINNODEID and
ENDNODEID are both required to be
fails.
specified.
User response: Review the activity log to determine
Explanation: The BEGINNODEID and ENDNODEID
what operations were in progress and were affected by
are both required to be specified or neither of them are
this error. Try the operation again and change the
required.
timing so that it does not run with the same processes
or actions as when the error occurred. System action: The server fails the command.
User response: Reissue the command, specifying both
ANR0108E Source file(line number): could not start a BEGINNODEID and ENDNODEID, or neither of them.
new transaction.
Explanation: An error occurred while attempting to ANR0112E Command: The specified
start a new transaction. Possibly there is not enough BEGINNODEID node id is greater than
memory. the ENDNODEID node id.
System action: The activity that generated this error Explanation: Either the BEGINNODEID or the
fails. ENDNODEID is invalid because the value of the
BEGINNODEID is greater than the ENDNODEID.
User response: See the documentation for the
operating system about how to increase memory for an System action: The server fails the command.
application.
User response: Reissue the command, specifying the
ENDNODEID to be greater than the BEGINNODEID,
ANR0109E Attempt number att_num Unable to load or both to be equal.
cryptography module from 'icc location'.
Explanation: An error occurred while attempting to ANR0113E Command: The storage pool list specified
load the cryptography module. with the parameter parameter name
includes storage pool storage pool name
System action: The application will not start.
more than once for simultaneous write.
User response: Verify that the ICC cryptography
Explanation: The storage pool name specified has
directory is located in either the application root
been specified more than once. The name occurs more
directory or the directory specified in the platform
than once in the COPYSTGPOOLS list, more than once
specific environment variable (the DSMSERV_DIR for
in the ACTIVEDATAPOOLS list, or it has been
Unix platforms or the Windows registry).
specified in both lists.
System action: The command fails.
ANR0110E An unexpected system date has been
detected; the server is disabled. Verify User response: Reissue the command specifying
the system date and use the ACCEPT unique storage pool names.
DATE command to establish the current
date as valid.
Explanation: The server has noted that the current
system date is suspect. It is earlier than the server
Chapter 3. ANR messages 49

ANR0114E ANR0121E
backup, archive, or space-managed data.

ANR0114E Command: The NUMBER parameter is
required on this command. The current System action: Processing continues.
default value is 0.
User response: In order to change the archive data
Explanation: The NUMBER parameter is required for retention protection state, the server must contain no
the FORMAT LFVOLUME COMMAND when the backup, archive, or space-managed data. Either
LFVOLUMEFORMATCOUNT option is set to 0. re-initialize the server database, or delete all stored
data and try the command again.
System action: The command is not executed.
User response: Either reissue the command with the
ANR0118W The client option client option is not
NUMBER parameter or else use the the SETOPT
valid and will not be sent to the client.
command to change the LFVOLUMEFORMATCOUNT
Use the INCLEXCL option instead.
value.
Explanation: The client options INCLUDE and
EXCLUDE are not valid and have been replaced by the
ANR0115W The server script script name attempted
combined INCLEXCL. If INCLUDE and EXCLUDE are
to start more parallel commands than
used in client option sets, use the INCLEXCL option
are allowed for a single script. A single
along with the specific include or exclude option that
script is limited to parallel command limit
you want the clients to use.
parallel commands.
System action: The option is ignored and is not sent
Explanation: The server waits for all previous parallel
to the client. The server continues processing.
commands started by the script to complete. When all
previous parallel commands are complete, the server User response: Client options INCLUDE and
allows the script to continue. The script can attempt to EXCLUDE are not valid; use the INCLEXCL option
start more parallel commands. along with the specific include or exclude option that
you want the clients to use.
System action: The server waits for all previous
parallel commands before allowing the script to
continue. ANR0119W The client option client option is not
valid and will not be sent to the client.
User response: If you need to start more parallel
Delete it from client option set.
commands than the script limit allows, modify the
script to invoke multiple scripts in parallel, each of Explanation: The client option is not supported by
which can start multiple parallel commands, up to the this server and should be deleted from the client option
script limit. set.
System action: The option is ignored and is not sent
ANR0116W The server script script name attempted to the client. The server continues processing.
to start more parallel commands than
are allowed for the server. The server is User response: Delete the option from the option set.
limited to parallel command limit parallel Check the documentation for a possible replacement for
commands. the option.
Explanation: The server waits for all previous parallel

commands started by the script to complete. When all ANR0120I Archive data retention protection is set
previous parallel commands are complete, the server to state of archive data retention protection.
allows the script to continue. The script can attempt to Explanation: The archive data retention protection
start more parallel commands. If the limit is exceeded, state has been set.
the command will run serially.
System action: The server waits for all previous
parallel commands before allowing the script to User response: None.
continue.
User response: Reduce the number of parallel ANR0121E command is not allowed when archive
commands or scripts that are running on the server at data retention is enabled.
any one time. Explanation: The specified command is not allowed
when archive data retention protection is enabled on
ANR0117E The server contains stored data. Archive the server.
data retention protection cannot be System action: Processing continues.
changed.
User response: None.
Explanation: The archive data retention protection
state cannot be changed while the server contains any

ANR0122E ANR0130E
v The object is part of a deletion hold.

ANR0122E command: A node cannot be assigned to
a new domain when archive data System action: Processing continues.
retention is enabled.
Explanation: A previously defined node cannot be
assigned to a new domain when archive data retention
protection is enabled on the server. ANR0127E command to another server is not
allowed when data retention protection
System action: Processing continues. is enabled on the target server.
User response: None. Explanation: The specified command is not allowed
when data retention protection is enabled on the target
server.
ANR0123E command: A device type of SERVER is
not allowed when archive data retention System action: Processing continues.
is enabled.
Explanation: The specified device type is not allowed
when archive data retention protection is enabled on
the server. ANR0128W The previous database upgrade did not
complete successfully.
Explanation: At server startup, the server discovered
User response: None. that a previously started database upgrade operation
did not complete successfully. To complete the database
upgrade, specify the UPGRADEDB parameter when
ANR0124W Object object name (object id hi ) for node
starting the server.
node name (node id), filespace filespace
name (filespace id) is retention protected System action: Processing continues.
and can not be deleted.
User response: Check the server error messages on
Explanation: The specified object can not be deleted console to determine the reason the previous database
because: upgrade did not complete successfully. Correct the
v Archive retention protection is enabled and the problem, and perform the database upgrade again, if
object's retention period has not elapsed, or possible. If the problem cannot be corrected, contact
your service representative.
v The object is part of a deletion hold.
ANR0129I Database upgrade completed
User response: None. successfully.
Explanation: The requested database upgrade
ANR0125W DELETE FILESPACE filespace name for operation completed successfully.
node node name contains retention
protected data and cannot be deleted.
Explanation: The specified file space cannot be deleted
because it contains one or more objects that must be
retained for one of the following reasons: ANR0130E Diagnostic(ID): Server LOG space
v Archive retention protection is enabled and the exhausted.
object's retention period has not elapsed. Explanation: There is no space to write data to the
v The object is part of a deletion hold. server recovery log.
System action: The file space is not deleted. System action: The activity that generated this error
fails.
User response: To increase the amount of log space
available to the server, evaluate the directories and
ANR0126W DELETE VOLUME: Volume volume name
filesystem assigned to the ACTIVELOGDIR,
contains retention protected data and
ARCHIVELOGDIR, and ARCHFAILOVERLOGDIR. An
can not be deleted.
out of log space condition may occur because the
Explanation: The specified volume cannot be deleted ACTIVELOGDIR location is full. Alternatively, an out
because it contains one or more objects that must be of log condition may occur if the log files in the
retained because of one of the following: ACTIVELOGDIR which are no longer active can not be
v Archive retention protection is enabled and the archived to the ARCHIVELOGDIR and
object's retention period has not elapsed. ARCHFAILOVERLOGDIR locations. If necessary, a

ANR0131E ANR0139I
larger ARCHIVELOGDIR or ARCHFAILOVERLOGDIR

ANR0135I Table maintenance performed
can be specified by updating this option in the
successfully for processed tables of total
dsmserv.opt file and then restarting the server.
tables.
Explanation: The server periodically performs
ANR0131E Diagnostic(ID): Server DB space
maintenance on the database tables. The maintenance
exhausted.
processing allows the database to update statistics used
Explanation: There is no space to write data to the to determine how to best access a given table. The
server database. maintenance processing will periodically process all
tables for the server. And during other processing
System action: The activity that generated this error cycles, it will only process those tables that have
fails. changes such as inserts, updates, or deletes for records
User response: To increase the amount of database in that table.
space available to the server, an authorized System action: Server operation continues.
administrator can add database volumes by using the
DEFINE DBSPACE command. Once additional space User response: No user action required.
has been added for the database, the server database
manager will automatically extend into that space and
ANR0136I Table updating statistics performed
use it.
successfully for processed tables of total
tables.
ANR0132E Diagnostic(ID): Memory allocation failed:
Explanation: The server periodically performs
object object name, size size.
maintenance on the database tables. The maintenance
Explanation: The server cannot obtain enough processing allows the database to update statistics
memory to create the object named. determine how to best access a given table. The
maintenance processing will periodically process all
System action: The activity that generated this error tables for the server.
fails.
operating system about how to increase memory for an User response: No user action required.
application.
ANR0133E Error loading module modname: error allocating num rows database rows.
string
Explanation: An internal error has occurred in an
Explanation: The error specified by error string attempt to allocate storage for the requested number of
occurred when the server attempted to load module database rows indicated.
modname
System action: Server operation continues, but the fails.
function provided by the module is not available.
User response: Contact your service representative.
User response: Refer to the error string and correct
the condition causing the load to fail.
ANR0138E Value primary logs for number of
primary logs is invalid.
ANR0134W There is an error reading from standard
Explanation: The command has been issued with an
input; the console input daemon
invalid number of primary logs.
stopped.
System action: Server installation stops.
Explanation: Warning: warning string
User response: Reissue the command with a valid
System action: Server operation continues, but
number of primary logs.
standard input is not available.
User response: If the server was started in the
ANR0139I This command has been disable for
background, there is no error, or else standard input is
DB2.
in an error state.
Explanation: During DB2 development cycle. This
command/function has been temporarily disable.
System action: System operation continues.

ANR0140I ANR0150E
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, and failed failed.
message. There may be one or more segments
displayed for a given message insert. Explanation: Inventory file expiration processing
finished processing for the node name and filespace name
System action: The entire message insert segment is
indicated. For this node name and filespace name the
displayed.
indicated copygroup and object types were evaluated.
User response: None. And the ending statistics show the number of objects
examined, deleted, retrying and those that failed to be
processed.

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

ANR0174E ANR0190I
ANR0174E Diagnostic(ID): Maximum DB2 ANR0186E There is insufficient authority to start

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

ANR0185E The data in primary storage pool name can
Database manager license has expired
not be copied to active data pool name.
The active-data pool is not defined to a Explanation: Database manager license has expired.
domain.
System action: The server process ends.
User response: Define the active-data pool to a
domain using the ACTIVEDESTINATION parameter on
ANR0190I Inventory file expiration started
either the DEFINE DOMAIN or UPDATE DOMAIN
processing node node name for backup
command.
sets.
Explanation: Expiration processing is currently
evaluating information for backup sets for the node
specified.

ANR0191I ANR0200I
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: TSM will attempt to remove the Explanation: The server was not able to remove
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. ANR0200I Recovery log assigned capacity is size
megabytes.
System action: System operation continues and future
operations on the specified volume should work Explanation: The amount of space allocated to the
normally. recovery log is shown.
User response: The server successfully repaired the System action: None.
specified volume.

ANR0201I ANR0209E

ANR0206W Partial write detected on database
volume volume name, logical page logical
ANR0201I Database assigned capacity is size page number (physical page physical page
megabytes. number).
Explanation: The amount of space allocated to the Explanation: During a write of a database page, an
database is shown. error occurred so that the page was not completely
written to disk.
System action: The failed I/O operation is retried on a
User response: None. mirrored volume.
User response: See accompanying messages for
ANR0202W Database volume volume name varied information about the volume in error.
offline due to excessive read errors.
Explanation: The database volume shown has been ANR0207E Page address mismatch detected on
varied offline because too many read errors have been database volume volume name, logical
encountered. page logical page number (physical page
System action: If available, a mirrored copy of the physical page number); actual: logical page
volume is used. number.
User response: Correct the cause of the read errors. Explanation: During a read of a database page, the
page does not contain the expected page address.
ANR0203W Database volume volume name varied System action: The failed I/O operation is retried on a
offline due to excessive write errors. mirrored volume.
Explanation: The database volume shown has been User response: See accompanying messages for
varied offline because too many write errors have been information about the volume in error.
encountered.
System action: If available, a mirrored copy of the ANR0208W Partial write detected on recovery log
volume is used. volume volume name, logical page logical
page number (physical page physical page
User response: Correct the cause of the write errors. number).
Explanation: During a write of a recovery log page,
ANR0204W Recovery log volume volume name varied an error occurs so that the page is not completely
offline due to excessive read errors. written to disk.
Explanation: The recovery log volume shown has System action: The failed I/O operation is retried on a
been varied offline because too many read errors have mirrored volume.
been encountered.
System action: If available, a mirrored copy of the information about the volume in error.
volume is used.
User response: Correct the cause of the read errors. ANR0209E Page address mismatch detected on
recovery log volume volume name, logical
ANR0205W Recovery log volume volume name varied page logical page number (physical page
offline due to excessive write errors. physical page number); actual: logical page
number.
Explanation: The recovery log volume shown has
been varied offline because too many write errors have Explanation: During a read of a recovery log page, the
been encountered. page does not contain the expected page address.
System action: If available, a mirrored copy of the System action: The failed I/O operation is retried on a
volume is used. mirrored volume.
User response: Correct the cause of the write errors. User response: See accompanying messages for
information about the volume in error.

ANR0210S ANR0219I
ANR0210S Inconsistency found in LVM data page ANR0215W Recovery log volume volume name is in
page number - partial write detected. the offline state - VARY ON required.
Explanation: During a write of an LVM internal page, Explanation: At system startup, the server finds that
an error occurs so that the page is not completely the recovery log volume shown is in the offline state.
written to disk.
System action: The volume is not accessed.
User response: Determine the reason for the volume
mirrored volume.
being offline; if possible, vary it online.
ANR0216I Database volume volume name is in the
"stale" state - synchronization process
ANR0211S Inconsistency found in LVM data page started.
page number - page address mismatch
Explanation: At system startup, the server finds that
(actual page number).
the database volume shown is not synchronized.
Explanation: During a read of an LVM internal page,
System action: A process is started to synchronize the
the page does not contain the expected page address.
volume.
mirrored volume.
ANR0217I Recovery log volume volume name is in
the "stale" state - synchronization
process started.
ANR0212E Unable to read disk definition file file
Explanation: At system startup, the server finds that
specification.
the recovery log volume shown is not synchronized.
Explanation: At startup, the server cannot read the
System action: A process is started to synchronize the
indicated file in order to obtain a list of disk volumes
volume.
to mount.
System action: Server initialization fails.
User response: Use a text editor to recreate the file; it
ANR0218I Unable to install database volume
should contain one line with the name of a single log
volume name - capacity must be at least 5
or database volume. Then restart the server.
megabytes.
Explanation: An attempt has been made to add a
ANR0213W Unable to rewrite disk definition file.
database volume that is smaller than the server
Explanation: An error occurs trying to update the disk minimum.
definition file.
System action: The volume is not added.
User response: Increase the size of the volume or
User response: Attempt to determine the cause of the supply another larger volume.
write error and correct it.
ANR0219I Unable to install recovery log volume
ANR0214W Database volume volume name is in the volume name - capacity must be at least 5
offline state - VARY ON required. megabytes.
Explanation: At system startup, the server finds that Explanation: An attempt has been made to add a
the specified database volume is in the offline state. recovery log volume that is smaller than the server
minimum.
System action: The volume is not accessed.
System action: The volume is not added.
User response: Determine the reason for the volume
being offline; if possible, vary it online. User response: Increase the size of the volume or
supply another larger volume.

ANR0220I ANR0228S
a unique name for each database and recovery log

ANR0220I Synchronization of database volume
volume.
volume name started as process process ID.
Explanation: A background process was started to
ANR0225S Invalid use of the -S command-line
synchronize the contents of the database volume shown
option.
with its copy volume. The background process was
assigned the process ID shown. Explanation: The -S option cannot be specified on the
command line if the database ID file (dsmserv.dbid) is
System action: The background process starts to
intact. This option is to be used only if the ID file does
synchronize the volume and server operation continues.
not exist.
User response: The administrator may query the
System action: The server does not start.
status of the background process by using the QUERY
PROCESS command, or cancel the process by using the User response: Start the server without specifying the
CANCEL PROCESS command. -S command-line option.
ANR0221I Synchronization of recovery log volume ANR0226S The database ID file could not be found
volume name started as process process ID. for server startup.
Explanation: A background process was started to Explanation: The server's database ID file
synchronize the contents of the recovery log volume (dsmserv.dbid) could not be found. This file is created
shown with its copy volume(s). The background when the database is formatted, is stored in the
process was assigned the process ID shown. directory from which the format is performed, and is
required for normal server operation.
System action: The background process starts to
synchronize the volume and server operation continues. System action: The server does not start.
User response: The administrator may query the User response: Ensure that you are starting the server
status of the background process by using the QUERY from the correct instance directory, and that the
PROCESS command, or cancel the process by using the dsmserv.dbid file exists and can be read. If no
CANCEL PROCESS command. dsmserv.dbid file exists, restart the server with the -S
option to create a new database ID file.
ANR0222E Error action disk definition file file
specification. ANR0227S Incorrect database opened. Server
cannot start.
Explanation: An error occurred creating or changing
the disk definition file. Explanation: The ID of the database opened does not
match the ID stored in the database ID file
(dsmserv.dbid).
User response: Attempt to determine the cause of the
write error and correct it.
User response: Ensure that you are in the proper
instance directory for the database being opened, and
ANR0223E Error writing list of disks to disk
that the environment is set up correctly. The instance
definition file.
directory is generally the directory from which you
Explanation: The disk definition file cannot be formatted the database, or, if on UNIX, have specified
written. with the -i command-line option.
System action: Installation ends. When the ID of the database that is opened does not
match the ID that is stored in the database ID file
User response: Determine the cause of the write error
(dsmserv.dbid), the server will not start. Use the -S
and correct it.
(skip DB ID check) parameter after deleting the
dsmserv.dbid file. After the initial use of the -S
ANR0224E Volume volume name is specified more parameter in a restore scenario, the server creates a
than once - server installation failed. new dsmserv.dbid file in the instance directory.
Explanation: The specified volume name was

specified more than once in the server installation ANR0228S Error errno opening the database ID file
execution. for server startup.
System action: Installation ends. Explanation: The server's database ID file

(dsmserv.dbid) could not be opened. The errno
User response: Reinitialize the server install specifying indicates the reason for the failure.

ANR0229W ANR0238E

ANR0233I Synchronization process canceled for
User response: Ensure that you are starting the server recovery log volume volume name.
from the correct instance directory, and that the
Explanation: The process that was attempting to
dsmserv.dbid file has the correct ownership and
synchronize the database volume shown has been
permission. If the file is empty, erase the file, and
canceled.
restart the server with the -S command-line option to
generate a new database ID file. System action: The volume is in the stale state.
User response: If desired, issue a VARY ONLINE
ANR0229W Server is unable to add entries to the command to start another synchronize process.
Activity Log. Console messages will not
be logged until database access is
ANR0234I Synchronization complete for database
available.
volume volume name.
Explanation: The process that monitors the default
Explanation: The synchronization process for the
(console) output stream and maintains the activity log
database volume named has finished successfully.
cannot update the activity log. The error is due to the
inability of the server to access the server database. System action: The volume is varied online.
System action: The server does not update the activity User response: None.
log. The activity log will continue to run and attempt
to recover from this situation.
ANR0235I Synchronization complete for recovery
User response: Access to the server database is log volume volume name.
temporarily unavailable. The server database manager
will attempt to recover from this situation and Explanation: The synchronization process for the
reestablish access to the server database. When access recovery log volume named has finished successfully.
to the server database is reestablished, the activity log System action: The volume is varied online.
processing will continue. If the server database access
fails to be reestablished, additional messages will be User response: None.
issued providing more information.
ANR0236E Fail to start the database manager due to
ANR0230E Synchronization process failed for an I/0 error. Check for filesystem full
database volume volume name. conditions, file permissions, and
operating system errors.
synchronize the database volume shown has failed. Explanation: The TSM server encountered an I/O
error while attempting to start the database manager.
System action: The volume is in the stale state.
User response: See accompanying messages for more
information. User response: Review the filesystems assigned to the
server for the database and recovery log.
ANR0231E Synchronization process failed for

recovery log volume volume name. ANR0237E Fail to start the database manager. An
unexpected system error occurred.
synchronize the recovery log volume shown has failed. Explanation: An unexpected system error occurred.
System action: The volume is in the stale state. Some common reasons for this error are:
v The system name where you ran the server has been
changed
information.
v The system date and time is set incorrectly
ANR0232I Synchronization process canceled for System action: The server process ends.
database volume volume name. User response: Contact your service representative.
synchronize the database volume shown has been ANR0238E A database recovery task is prohibiting
canceled. activation of db name with sqlcode
System action: The volume is in the stale state. dbCode.
User response: If desired, issue a VARY ONLINE Explanation: While attempting to activate the database
command to start another synchronize process. an error occurred because the database was busy

ANR0239E ANR0246E
performing a BACKUP, RESTORE or was in System action: The volume is not deleted.
ROLLFORWARD pending state. Examine the sqlcode to
determine the condition that is preventing the database
information.
from activating. The following sqlcodes are most likely
to occur during the activate database step and will
prevent the server from starting. SQLE_RC_BKP_PEND ANR0241E Deletion process failed for recovery log
( -1116 ) indicates a database BACKUP is pending and volume volume name.
must complete prior to activating the database. Once
the database BACKUP is complete,the database can be Explanation: The process that was attempting to
activated by starting the server. delete the recovery log volume shown has failed.
SQLE_RC_ROLLFWD_PEND ( -1117 ) indicates a System action: The volume is not deleted.
database Roll Forward operation is pending and must
complete before activating the database. After the Roll User response: See accompanying messages for more
Forward recovery step is complete, the database can be information.
activated by starting the server.
SQLE_RC_BKP_INPROG ( -1118 ) occurs when an ANR0242I Deletion process canceled for database
attempt to activate the database fails because a volume volume name.
database BACKUP was in progress. Prior to activating
the database, it is necessary to rerun database BACKUP. Explanation: The process that was attempting to
Once the database BACKUP completes successfully, the delete the database volume shown has been canceled.
database can be activated by starting the server. System action: The volume is not deleted.
SQLE_RC_RST_INPROG ( -1119 ) shows that a
database RESTORE was in progress when the database User response: None.
failed to activate. The RESTORE database must be
restarted and allowed to complete successfully before
ANR0243I Deletion process canceled for recovery
activating the database. Once the database RESTORE in
log volume volume name.
complete, the database can be activated by starting the
server. SQLE_RC_BR_INPROG ( -1120 ) means that Explanation: The process that was attempting to
either a database BACKUP or RESTORE must complete delete the recovery log volume shown has been
before activating the database. Ensure that either a canceled.
BACKUP or RESTORE operation completes successfully
System action: The volume is not deleted.
before activating the database.
System action: The server is not started because the
database cannot be activated.
ANR0244I Deletion complete for database volume
User response: See message explanation for more
volume name.
information.
Explanation: The delete process for the database
volume named has finished successfully.
ANR0239E The DB2 instance name instance name
may not be valid or is not configured System action: The volume is deleted.
properly. The return code was sqlcode
Explanation: TSM Server attempted to connect using
the database instance set by the DB2INSTANCE
environment variable, but the attempt failed. ANR0245I Deletion complete for recovery log
volume volume name.
System action: The server is not started because the
database instance is not valid. Explanation: The delete process for the recovery log
volume named has finished successfully.
User response: Verify that the database instance exists
and that it is configured properly. You can list DB2 System action: The volume is deleted.
instances by issuing the db2ilist command from the User response: None.
instance directory, under the DB2 installation directory.
Example: c:\Program Files\tivoli\tsm\db2\instance\
db2ilist ANR0246E Error reading logical page logical page
number (physical page physical page
number) from database volume volume
ANR0240E Deletion process failed for database name.
volume volume name.
Explanation: An error has been encountered when
Explanation: The process that was attempting to attempting to read a page from the specified database
delete the database volume shown has failed. volume.

ANR0247I ANR0254E
System action: The failed I/O operation is retried on a User response: None.
mirrored volume, if available.
User response: See accompanying messages for ANR0251E Unable to read recovery log page logical
information about the volume in error. If the error page number from any alternate copy.
persists and another mirrored copy of the volume is
Explanation: After a read error, the server is unable to
available, the failing volume should be taken offline by
read the desired page from another mirrored volume
using the VARY OFF command, and repaired.
because no other mirrored volume was in the
Otherwise, halt the server and repair the volume. Then
synchronized state. This message is normally preceded
restart the server.
by a message indicating which volume failed.
System action: Processing is ended.
ANR0247I Database page logical page number
successfully read from an alternate copy User response: You can repair the failed volume by
on volume volume name. halting the server and correcting the volume errors.
Explanation: After a read error, the server is able to
read the desired page from another synchronized ANR0252E Error writing logical page logical page
mirrored volume. number (physical page physical page
number) to database volume volume name.
attempting to write a page to the specified database
volume.
ANR0248E Unable to read database page logical page
System action: If a mirrored volume is available then
number from any alternate copy.
the failing volume is forced into the offline state.
Explanation: After a read error, the server is unable to
User response: Repair the failing volume, and then
read the desired page from another mirrored volume
use the VARY ON command to bring the volume back
because no other mirrored volume is in the
online.
synchronized state. This message is normally preceded
ANR0253E Unable to write database page logical
page number to any alternate copy.
User response: You can repair the failed volume by
Explanation: After a write error, the server is unable
halting the server and correcting the volume errors.
to write the desired page to another mirrored volume
because no other mirrored volume is in the
ANR0249E Error reading logical page logical page synchronized state. This message is normally preceded
number (physical page physical page by a message indicating which volume failed.
number) from recovery log volume
volume name.
User response: Repair the failed volume.
attempting to read a page from the specified recovery
log volume. ANR0254E Error writing logical page logical page
number (physical page physical page
number) to recovery log volume volume
mirrored volume, if available.
name.
information about the volume in error. If the error
attempting to write a page to the specified recovery log
persists and another mirrored copy of the volume is
volume.
available, the failing volume should be taken offline, by
using the VARY OFF command, and repaired. System action: If a mirrored volume is available, the
failing volume is forced into the offline state.
ANR0250I Recovery log page logical page number User response: Repair the failing volume, and then
successfully read from an alternate copy use the VARY ON command to bring the volume back
on volume volume name. online.
Explanation: After a read error, the server is able to
read the desired page from another synchronized
mirrored volume.

ANR0255E ANR0263I
information from any of the defined database or

ANR0255E Unable to write recovery log page logical
recovery log volumes.
page number to any alternate copy.
System action: Server restart is ended.
Explanation: After a write error, the server is unable
to write the desired page to another mirrored volume User response: Ensure that all defined database and
because no other mirrored volume is in the recovery log volumes are available for use by the
synchronized state. This message is normally preceded server.
System action: Processing is ended. ANR0260I Database page logical page number
successfully resynchronized.
User response: You can repair the failed volume by
halting the server and correcting the volume errors. Explanation: After detecting a partially-written
database page, the server is able to rewrite the page by
using a synchronized mirror copy.
ANR0256E Error writing physical page physical page
number to restart/checkpoint area on System action: Processing continues.
database volume volume name.
attempting to write a page to the specified database
volume. ANR0261I Recovery log page logical page number
successfully resynchronized.
System action: If a mirrored volume is available, the
failing volume is forced into the offline state. Explanation: After detecting a partially-written
recovery log page, the server is able to rewrite the page
User response: Repair the failing volume, and then by using a synchronized mirror copy.
use the VARY ON command to bring the volume back
online. System action: Processing continues.
ANR0257E Error writing physical page physical page
number to restart/checkpoint area on ANR0262W Incompatible database restart/recovery
recovery log volume volume name. area has been detected.
Explanation: An error has been encountered when Explanation: The restart/recovery area of the server
attempting to write a page to the specified database database and recovery log volumes were written in a
volume. format that is not compatible with the restart/recovery
System action: If a mirrored volume is available, the area written by other versions of the server.
failing volume is forced into the offline state. System action: The server starts normally. If the
User response: Repair the failing volume, and then database and recovery log are writable (not Read
use the VARY ON command to bring the volume back Only), then the restart/recovery area will be converted
online. to a compatible format. Message ANR0263I will be
issued when the conversion has been completed.
ANR0258E Unable to write complete User response: None.

restart/checkpoint information to disk.
Explanation: While writing restart/checkpoint ANR0263I Database restart/recover area
information to disk, the server encounters an error successfully converted to compatible
writing to a database or recovery log volume for which format.
no synchronized mirrored copy is available. This Explanation: The server converted the
message is normally preceded by a message indicating restart/recovery areas of its database and recover log
which volume failed. volumes to a format compatible with the
System action: Processing is ended. restart/recovery area written by other versions of the
server. This is a one time conversion, and will only be
User response: Repair the failing volume. performed if the restart/recovery area was not already
in the compatible format.
ANR0259E Unable to read complete System action: The restart/recovery area was
restart/checkpoint information from any successfully converted.
database or recovery log volume.
Explanation: During server restart, the server is
unable to read a complete set of restart/checkpoint

ANR0264E ANR0271E

ANR0264E A database file IO error is prohibiting
activation of db name with sqlcode User response: Restart the server installation process
dbCode. with more memory available.
Explanation: While attempting to activate the database
an IO error occurred when processing a database file. ANR0267E Log volume volume name is not available.
The problem may have occurred in one of the
following situations: The system cannot open, read Explanation: The specified volume cannot be found
from, or write to a database file. The system cannot during installation.
create the database because an error occurred while the System action: Server installation stops.
system was creating a database file or a directory for
the database. The system cannot drop the database User response: Determine the reason the disk is
because an error occurred while the system was unavailable, and correct the problem. Restart the server
deleting a database file or a directory for the database. installation process.
The system cannot create the database because an
interrupt was received while the system was creating ANR0268E Database volume volume name is not
or deleting a database file or a directory for the available.
database. The system cannot locate the database
subdirectory or database configuration file during Explanation: The specified volume cannot be found
connect. Problem causes are ordered in terms of their during installation.
frequency of occurrence: A log file cannot be found in System action: Server installation stops.
the active log path directory. There may be a problem
with the database directory the operation is being User response: Determine the reason the disk is
attempted on. There may be inadequate disk space to unavailable, and correct the problem. Restart the server.
complete the operation. The database cannot be used.
System action: The server is not started because the ANR0269E Process for Log volume volume name
database cannot be activated. terminated - thread resource not
available.
User response: Appropriate responses for the problem
causes described above are: To verify if a log file is Explanation: During installation for the indicated
missing, check the db2diag.log for the presence of a volume, the server cannot start a thread to service I/O
logging error (return code contains SQLO_FNEX). If requests.
present, this error will contain the name of the missing
log file. Ensure that the file is located in the active log
path directory. If the file cannot be located, restore and User response: See the documentation for the
roll-forward the database to an earlier point in time operating system about how to increase memory for an
referenced in a log file preceding the missing log file application.
(use a timestamp that is earlier than that of the missing
Restart the server installation process.
file). There may be a problem with the database
directory. Check the integrity of the directory. Examples
of potential problems include: permissions issues, ANR0270E Process for Database volume volume
mount point problems, corruption. Increase filesystem name terminated - thread resource not
size. available.
Explanation: During installation for the indicated
ANR0265E Log disk processing failed: sufficient volume, the server cannot start a thread to service I/O
memory is not available. requests.
Explanation: At server installation, the server is System action: Server installation stops.
unable to process the server log disks due to
insufficient memory. User response: See the documentation for the
operating system about how to increase memory for an
System action: Server installation stops. application.
User response: Restart the server installation process Restart the server installation process.
with more memory available.
ANR0271E Maximum number of recovery log
ANR0266E Database disk processing failed: volumes exceeded.
sufficient memory is not available.
Explanation: More recovery log volumes have been
Explanation: At server installation, the server is specified than the server can manage.
unable to process the server database disks due to
insufficient memory. System action: Server installation stops.

ANR0272E ANR0287W
User response: Reduce the number of recovery log User response: None
volumes specified. Restart the server installation
process.
ANR0277E Schema reconciliation for table table
failed.
ANR0272E Maximum number of database volumes
Explanation: The server was unable to reconcile the
exceeded.
schema differences for the indicated table.
Explanation: More database volumes have been
System action: Server operation terminates.
specified than the server can manage.
User response: Contact your IBM service
representative.
User response: Reduce the number of database
volumes specified. Restart the server installation
ANR0278S The database manager cannot create the
process.
database because of a virtual memory
shortage.
ANR0273W Not initializing library library name
System action: Server operation stops.
because the library is set offline .
User response: Stop other applications running on the
Explanation: The External Library is set offline. It will
system, especially those that use large amounts of
not be used for new transactions until it is set online
shared memory.
again.
System action: This server skips the initialization of
ANR0285I Database page shadowing started using
the library. The server continues processing.
file file name.
User response: Refer to the UPDATE PATH command
Explanation: The database page shadowing function
for details on changing the online option.
was started. The file specified is used to store the
shadowed database pages.
ANR0274E Attempt to access library library name
failed, because the library is set offline.
Explanation: The Library is set offline. It will not be
used for new transactions until it is set online again.
ANR0286W Database page shadowing using file file
System action: This mount fails.
name failed to start.
User response: Refer to the UPDATE PATH command
for details on changing the online option.
could not start. An error has been encountered
accessing the page shadow file specified.
ANR0275I Detected schema change for table table,
attempting to reconcile.
User response: Verify that there is enough space for
Explanation: The schema for the table referenced does
the page shadow file. That page shadow file requires
not match the server definition for this table. The
approximately 65 kilobytes of space, if this space is not
schema difference for this table will be reconciled.
available a new location for the file should be specified.
System action: Server startup continues if the schema
difference was successfully reconciled. Server startup
ANR0287W Contents of the page shadow file file
will fail if the schema reconciliation failed.
name are not valid.
User response: The schema for this table will attempt
to be reconciled. Specifically, the server will try to
could not use the contents of the existing file. Restart
modify the table in the database to match the schema
recovery using this file is not possible.
that was expected. A message will be issued indicating
the success or failure of the schema reconciliation. System action: The server attempts to start without
having the database page shadow file available.
ANR0276I Schema reconciliation for table table User response: The database page shadow file
succeeded. contents are not valid. This can be caused by: a partial
write to the page shadow file itself, the file being
Explanation: The schema differences for this table
manipulated by a process outside of the server, the file
were successfully reconciled.
being overlaid by a different file, or the file could have
System action: Server operation continues. been erased.

ANR0288W ANR0295I
space for the file. If enough space is available, check

ANR0288W One or more database pages in the last
the filesystem, drive, or disk that it resides on for an
batch written is corrupt - contents of
indication of the error. Once the error preventing the
database page shadow file will be used
server from writing to the page shadow file has been
to fix the page or pages.
resolved, restart the server.
Explanation: One or more pages from the last batch of
pages written to the server database has been detected
ANR0292W Database page shadow file file name does
to be corrupt. The server will attempt to use the
not exist.
contents of database page shadow file and replace the
corrupted database page. Explanation: The server attempted to use the page
shadow file referenced but was unable to open the file.
System action: Server startup continues.
The file does not exist.
User response: A corruption of a database page within
System action: The server will continue to operate
the server database, is typically caused by a partial
and will attempt to create this as a new database page
write. A partial write may occur when the server is
shadow file.
brought down external to normal server processing. If
the server terminated without a halt command being User response: None.
issued or if the machine the server is running on
crashed unexpectedly, this may account for the partial
write. Other possible causes of a partial write are a disk ANR0293I Reorganization for table table name
drive failure, improperly terminated SCSI bus, or a started.
failure in a device controller. Please try to identify the Explanation: The server is performing an online
cause of the partial write and take the appropriate reorganization for the table referenced.
action to prevent this from occurring in the future.
System action: The server will continue to operate.
ANR0289W Damaged database pages were User response: Monitor the available log space in the
successfully replaced using contents of active log and archive log storage paths. If the log
page shadow file. space available to the filesystem begins to fill up, then
perform a BACKUP DATABASE command with the
Explanation: The damaged database pages were TYPE=FULL parameter in order to initiate pruning of
replaced using the corresponding pages from the page the archive log space.
shadow file. The pages were successfully replaced.
System action: The server continues to restart. ANR0294I Reorganization for table table name
User response: None. ended.
Explanation: The server online reorganization for the
ANR0290W Failure occurred attempting to replace table referenced has ended.
one or more damaged database pages System action: The server will continue to operate.
using the contents of the page shadow
file. User response: Review the available log space in the
active log and archive log storage paths. If the log
Explanation: The damaged database pages could not space available to the filesystem has to filled up or is
be replaced using the corresponding pages from the close to filling up, then perform a BACKUP
page shadow file. DATABASE command with the TYPE=FULL parameter
System action: The server continues to restart. in order to initiate pruning of the archive log space.

ANR0295I A full database backup is needed. The
active log space used is log space used is
ANR0291E Error writing to database page shadow megabytes, and the active log space
file. available is log space available megabytes.
The ratio, active log used ratio, exceeds the
Explanation: The server encountered an error writing
threshold log utilization threshold.
to the database page shadow file. The page shadowing
for the server is currently disabled. Explanation: When the active log space used exceeds
the log utilization threshold, a database backup is
System action: Database page shadowing for the
needed.
server will remain disabled until the server is halted
and restarted. System action: None.
User response: Check the file specified as the database User response: None.
page shadow file. It may be that there is not enough

ANR0296I ANR0306I
ANR0296I A full database backup is needed. The ANR0300I Recovery log format started; assigned
total space used in log file system is log capacity count megabytes.
space used megabytes, and the total space
Explanation: Initial formatting of the server recovery
available in the log file system is log
log has started.
space available megabytes. The ratio is log
file system used ratio and is greater than System action: The log is formatted for use by the
the threshold log file system utilization server.
threshold.
Explanation: When the space used in the log file
system exceeds the threshold for log file system
utilization, a full database backup is required. ANR0301I Recovery log format in progress; count
megabytes of count.
Explanation: The amount of the server recovery log
User response: None. shown has been successfully formatted.
System action: Formatting continues.
ANR0297I A full database backup might be
required. The last log number used is User response: None.
last log used and the first log number
used is first log used. The log file size is ANR0302I Recovery log formatting took mseconds
log file size megabytes. The maximum log milliseconds.
file size is maximum log file size
megabytes. Explanation: Formatting of the recovery log has
completed and took the number of milliseconds shown.
Explanation: When the log space used since the last
database backup exceeds the maximum log file size, System action: None.
either a full database backup is required, or the User response: None.
maximum log file size must be increased.
System action: None. ANR0303I Format rate: rate pages/second.
User response: None. Explanation: During formatting, the formatter
processed the number of pages indicated each second.
ANR0298S Authority is insufficient to access the System action: None.
database.
Explanation: If the server is starting, then the user ID
under which the dsmserv process is running does not
have sufficient authority to access the database. If the ANR0304I Page service time: rate ms.
server is running and a server operation failed, then the Explanation: During formatting, the formatter
user ID does not have sufficient authority to perform required the number of milliseconds indicated to
the operation. process each page.
System action: If the server is starting, the dsmserv System action: None.
process ends. If the server is running, the server stops.
User response: Ensure that the user ID under which
the server is running is either the instance user ID, or is
authorized to access the database. ANR0305I Recovery log format complete.
Explanation: Formatting of the server recovery log
ANR0299I A full database backup will be started. completed successfully.
The archive log space used is archive
log% and the archive log space used
threshold is arch log threshold%. User response: None.
Explanation: When the archive log space used exceeds
the threshold, a full database backup will be started. ANR0306I Recovery log volume mount in progress.
System action: None. Explanation: During restart, the server is mounting
required recovery log volumes.

ANR0307I ANR0318I
lower the database backup trigger if one is

ANR0307I Recovery log extend in progress; count
defined
megabytes of count formatted.
Refer to the DEFINE DBBACKUPTRIGGER or
Explanation: As a result of an EXTEND LOG
UPDATE DBBACKUPTRIGGER commands.
command, the additional recovery log pages are being
formatted.
ANR0315E LOG SCAN ERROR encountered. The
System action: Formatting continues.
recovery log is unusable and the server
User response: None. is unable to continue.
Explanation: The server encountered corrupted
ANR0309I Recovery log extend terminated - information in the recovery log. Typically, the
process canceled. corruption is caused by a hardware or environmental
failure external to TSM.
Explanation: The process started as a result of an
EXTEND LOG command and has been canceled. System action: Server operation terminates.
System action: The EXTEND command is ended. User response: If the server database and recovery log
are mirrored, set the MIRRORREAD LOG VERIFY and
MIRRORREAD DB VERIFY options in the server
options file and restart the server. If database and
ANR0311I Recovery log reduce in progress; count recovery log mirrors are not available, or all mirrors are
megabytes of count moved. corrupted, restore the server database to the latest
backup and restart the server.
Explanation: As a result of a REDUCE LOG
command, the amount of data from the recovery log
shown has been moved. ANR0316W A full backup for database DB Name
cannot be started. This backup is
System action: The REDUCE LOG command required.
continues.
Explanation: An automatic full backup was attempted
User response: None. for this database. However, the device class for
database backups has not been specified.
ANR0313I Recovery log reduce terminated - System action: The database backup operation is not
process canceled. started.
Explanation: The process started as a result of a User response: Issue the SET DBRECOVERY
REDUCE LOG command and has been canceled. command to specify the default device class for
System action: The REDUCE command is ended. automatic database backups. Then, issue the BACKUP
DB command and specify TYPE=FULL to back up the
User response: None. database.
ANR0314W Recovery log usage exceeds utilization ANR0317I Reorganization of indices for table table
percentage % of its assigned capacity. name started.
Explanation: This message is issued to notify the Explanation: The server is performing an online
administrator that the server recovery log utilization reorganization for the indices of the referenced table.
exceeds 90% or more of its assigned capacity.
User response: Monitor the available log space in the
User response: active log and archive log storage paths. If the log
v If the server is operating in NORMAL log mode, space available to the filesystem begins to fill up, then
depending upon the size of your recovery log, add perform a BACKUP DATABASE command with the
recovery log volumes, or extend the recovery log, or TYPE=FULL parameter in order to initiate pruning of
both, before it fills completely. Refer to the DEFINE the archive log space.
LOGVOL, and EXTEND LOG commands for more
information on these operations.
ANR0318I Reorganization of indices for table table
v If the server is operating in ROLLFORWARD log name ended with sqlCode dbCode.
mode:
Explanation: The server online reorganization for the
backup the database, or
indices for the table referenced has ended.
define a database backup trigger if one is not
already defined, or System action: The server will continue to operate.

ANR0319W ANR0323E
User response: Review the available log space in the release. For example, if the server is version 5.3.0.0 and
active log and archive log storage paths. If the log the storage agent is version 5.2.3.0, the storage agent
space available to the filesystem has to filled up or is needs to be upgraded to version 5.3.0.0 to perform the
close to filling up, then perform a BACKUP requested function.
DATABASE command with the TYPE=FULL parameter
If this was a restore or retrieve operation and the client
in order to initiate pruning of the archive log space.
node DATAREADPATH setting was ANY or LANFREE,
the server will override this to be LAN only. This will
ANR0319W The file system for the database archive cause the operation to fail on the storage agent and
log has insufficient free space. message ANR0416W to be issued. Retry the operation
after performing one of the following actions:
Explanation: The usage of the file system for the
database archive log has exceeded the v Halt the storage agent, upgrade the storage agent
ARCHLOGUSEDTHRESHOLD. Space is used by files program, and then restart the storage agent.
that are not database archive log files, and the v Set the ENABLELANFREE client option to NO, and
BACKUP DB command cannot free space in the then restart the client
filesystem..
If this was a no-query restore operation, the data was
not restored by the storage agent using LAN-Free data
User response: Create sufficient free space on the file transfer. If the client node is allowed to read data over
system so that usage does not exceed the the LAN, the data was restored over the LAN. If the
ARCHLOGUSEDTHRESHOLD. operation failed because the client node is not allowed
to read data over the LAN, consider updating the
DATAREADPATH setting for this node by using the
ANR0320W Storage agent storage agent is not able to
UPDATE NODE command.
use device class device class for storage
pool storagepool for LAN-Free data
If this was an operation performed by an agent node
movement operations.
with proxy node authority to a target node, the session
Explanation: The storage agent referenced is not able failed with a protocol error. The operation was
to perform LAN-Free data movement operations using attempted by a version 5.3 or higher client and server,
this storage pool and device class. The storage agent is but the storage agent is not able to support this
back-level and is not able to support LAN-Free operation. To allow an agent node to perform
operations using this device class. operations for a target node, the storage agent must be
upgraded to version 5.3.0 or later.
System action: LAN-Free data movement operations
are not performed. The operations are either sent via
the LAN or else proxied by the storage agent directly ANR0322E The NEWSTGPOOL parameter is not
to the server. valid for deduplicated volume volume
name.
User response: In TSM version 5.3, a change was
made to the way the FILE and device classes are Explanation: The volume contains one or more
supported. This change prevents back-level storage deduplicated objects and must be restored to the
agents from being able to use these device classes. The original storage pool.
storage agent should be upgraded to the same version
System action: The operation is not allowed.
and release as the server. Until the storage agent is
upgraded, any LAN-Free data movement operations User response: To restore the volume to the original
that are attempted will be done 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.
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

ANR0324E ANR0330W
v Amount replicated indictaes the size of the files that

ANR0324E command: Replication parameters cannot
were replicated out of the size of the files that
be used with the TYPE=SERVER
needed to be replicated
parameter.
v Amount transferred indicates the number of bytes
System action: The command failed. transferred for the files that were replicated. This can
User response: Reissue the command without be less than the amount replicated if deduplication is
replication parameters. Replication parameters include used to reduce the amount of data transferred.
REPLSTATE, REPLMODE, BKREPLRULEDEFAULT, v Elapsed time indicate how long the process ran
ARREPLRULEDEFAULT and SPREPLRULEDEFAULT.
ANR0325E command: Operation is not allowed
because node nodename is a replica.
ANR0328I Replication preview of node(s) node list
Explanation: The specified node is a replica of a node
completed. Files current: files current.
on another server, created using the REPLICATE NODE
Files to be replicated: files to replicate.
command.
Files to be updated: files to update. Files
You can restore or retrieve data from this node, but you to be deleted: files to delete. Amount to
cannot store new data or alter existing data in any way. replicated: amount to replicate. Estimated
run time: estimated runtime.
System action: Client sessions that attempt to store
new data or change existing data will be terminated Explanation: The replication process has completed in
with a protocol error. IMPORT operations will skip the preview mode. The meanings of the numbers are:
node. v Files current indicates the number of files that do not
User response: Perform the operation on the server on need to be replicated.
which the original node resides. v Files to be replicated indicates the number of files
requiring replication.
ANR0326E command: The ROLEOVERRIDE v Files to be updated indicates the number of files
parameter cannot be used with either requiring a meta-data update.
the TYPE=SERVER or TYPE=NAS v Files to be deleted indicates the number of files to be
parameter. deleted from the target server.
System action: The command failed. v Amount to be replicated indictaes the size of the files
that require replication.
User response: Reissue the command without the
v Estimated run time is an estimate of how long the
ROLEOVERRIDE parameter.
process will run.
ANR0327I Replication of node node list completed.
Files current: files current. Files User response: None.
replicated: files replicated of files to
replicate. Files updated: files updated of
ANR0329I Starting replication of data type data for
files to update. Files deleted: files deleted of
node node name, filespace ID filespace id.
files to delete. Amount replicated: amount
replicated of amount to replicate. Amount Explanation: The replication process has started
transferred: amount transferred. Elapsed processing data for the specified node and file space
time: elapsed time. ID.
Explanation: The replication process has completed. System action: None.
The meanings of the numbers are:
v Files current indicates the number of files that do not
need to be replicated.
v Files replicated indicates the number of files ANR0330W Session session number for node node
successfully replicated out of the number of files that name (client platform) refused - invalid
we attempted to replicate. authentication protocol requested.
v Files updated indicates the number of files which Explanation: The server refuses a request to start a
had meta-data updated on the target server out of session because an invalid authentication protocol was
the number of files that needed an update. requested during sign-on processing. This might be due
v Files deleted indicates the number of files deleted to a down-level client, server, or storage agent that is
from the target server out of the number that needed accessing a server or storage agent that is configured to
to be deleted. disallow such attempts.

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

ANR0340E ANR0343W
User response: Use the ENABLE REPLICATION DRSRV to PRODSRV. Backup and space-managed
command to re-enable the use of replication. data will not be replicated to PRODSRV.
4. On DRSRV, set the target replication server by
ANR0340E command: Outbound replication issuing the following command: SET REPLSERVER
operations are disabled because the PRODSRV.
database was restored. 5. On DRSRV, replicate data belonging to NODE1 by
issuing the following command: REPLICATE NODE
Explanation: The database for this server was
NODE1. Replication processing changes the
restored. Data that was on this server but that is not
replication mode of NODE1 to SEND on DRSRV
referenced by the restored database is no longer
and to RECEIVE on PRODSRV.
accessible. To prevent this server from deleting copies
of data that might exist on the target replication 6. On PRODSRV and DRSRV, remove NODE1 from
servers, replication operations originating from this replication by issuing the following command:
server are disabled. REMOVE REPLNODE NODE1.
7. Update NODE1 definitions:
a. On PRODSRV, issue the following command:
User response: Disabling replication after a database UPDATE NODE NODE1
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
operations. 8. On PRODSRV, enable replication by issuing the
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 User response: None.
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 Tivoli Storage Manager
database backup and restore.

ANR0344E ANR0351I

ANR0347E Database database name is reporting a
User response: Node $$_TSMDBMGR_$$ is only used drive is invalid and the database can not
for Tivoli Storage Manager database backup or restore. be removed.
The server does not create a file space with this special
Explanation: This message is issued to notify the
node since there is no running database backup or
administrator that the server has detected that the API
restore session.
is reporting an invalid drive condition during a
User response: Use another node name to create this REMOVE DB process.
filespace.
System action: Server REMOVE DB stops.
User response: Interrogate the database, correct the
ANR0344E The server failed to restore the database.
problem then issue the command again.
Missing ARCHIVELOGDIR value in the
server option file.
ANR0348S Database restart record version version is
Explanation: While attempting to restore the database,
not recognized.
the Tivoli Storage Manager server detects a missing
value for ARCHIVELOGDIR in the server option file. Explanation: During server initialization, the server
database initialization failed because the version of the
System action: Server database restore stops.
restart record is not recognized.
User response: Before reissuing the command to
System action: The Server is terminated.
restore the database, check the following items:
v Ensure that ARCHIVELOGDIR option has a valid User response: Install the latest version of the Server
value. or restore the database to a point in time prior to the
previous upgrade.
v Ensure that the command is using the correct options
file for the server. If you are using the -o option with
the command to specify a server options file, ensure ANR0349S The database has been upgraded from
that the name and location of the file is correct. Express.
Explanation: The Express server has been started with
ANR0345E The database manager cannot start a database that has been upgraded from Express to
while file file name exists. base TSM. Once the database is upgraded from
Express, it cannot be used by an Express server.
System action: The server stops.
System action: The Server is terminated.
User response: Remove or rename the specified file
and restart the server. User response: Either restore the database from a
version taken prior to the upgrade, or use a base TSM
Server with the current database.
ANR0346W Database restore is performing a
point-in-time recovery because the
archive logs are not available. ANR0350I Recovery checkpoint started.
Explanation: A database restore to the most current Explanation: During server initialization, the process
state was requested but it is not possible to perform of bringing the server database back to a state of
this action. The archive logs are not available. This consistency has begun.
might be because the archive log files have been moved
or deleted, or the entire archive log directory has been
moved, deleted, or renamed. The server performs the User response: None.
database restore to the most recent point-in-time
possible.
ANR0351I Recovery checkpoint complete.
System action: Database restore processing continues
using point-in-time mode. Explanation: During server initialization, the process
of bringing the server database back to a state of
User response: Review the ARCHIVELOGDIR server consistency has completed successfully.
option in the server options file and determine why
this directory is no longer available to the server. If the System action: None.
archive log directory and its contents can be recovered User response: None.
and made available to the server RESTORE DB
processing, retry the DSMSERV RESTORE DB
command.

ANR0352I ANR0363I
ANR0352I Transaction recovery complete. ANR0359E Database initialization failed: unable to

read database restart record.
Explanation: During server initialization, the process
of recovering any incomplete transactions has Explanation: During server initialization, the server
completed successfully. database initialization fails because the required restart
record cannot be read.
System action: Initialization fails.
ANR0353I Recovery log analysis pass in progress.
ANR0360E Database initialization failed: database
Explanation: During server initialization, the process
size mismatch; LVM size = size, expected
of analyzing the server recovery log has begun.
size = size.
Explanation: During server initialization, the server
User response: None. database initialization fails because the size of the
database does not match its prior size.
ANR0354I Recovery log redo pass in progress. System action: Initialization fails.
Explanation: During server initialization, the process User response: Contact your service representative.
of committing incomplete transactions has begun.
System action: None. ANR0361I Recovery is in progress following a
database failure.
Explanation: During server initialization, the database
manager indicated that the database requires failure
ANR0355I Recovery log undo pass in progress. recovery. A database failure can occur in the event of a
Explanation: During server initialization, the process power outage or other abnormal termination of the
of rolling back incomplete transactions has begun. database manager. Failure recovery can take extensive
time, depending on how many transactions in the log
System action: None. require examination.
User response: None. System action: The server initialization is delayed
while the database is recovered.
ANR0356I Recovery log compression started. User response: No action is required.
Explanation: The process of removing unneeded data
from the server recovery log has begun. ANR0362W Database usage exceeds utilization
System action: None. percentage % of its assigned capacity.
User response: None. Explanation: This message is issued to notify the

administrator that the server database utilization
exceeds 80% or more of its assigned capacity.
ANR0357I Recovery log compression ended.
Explanation: The process of removing unneeded data
from the server recovery log has completed. User response: Depending upon the size of your
database, add database volumes, or extend the
System action: None. database, or both, before it fills completely. The server
User response: None. expiration process may also free up database space
making it available to other server processes. Refer to
the EXPIRE INVENTORY, DEFINE DBVOL, and
ANR0358E Database initialization failed: sufficient EXTEND DB commands for more information on these
memory is not available. operations.
Explanation: During server initialization, the server
database fails initialization because sufficient server ANR0363I Database was automatically upgraded to
memory is not available. the server program level.
System action: Initialization fails. Explanation: This message is issued to notify the
administrator that the server database was
User response: Make more memory available to the
automatically upgraded to the current server program
server.
level. The upgrade is performed when the

ANR0364W ANR0371E
UPGRADEDB parameter is specified at server startup User response: Before reissuing the command to
and the server is started over a database that was format a new database, check the following items:
written by a down-level version of the server program. v Remove the old database using command 'DSMSERV
System action: Server operation continues. REMOVEDB DB_NAME'.
v Ensure that the command is using the correct options
User response: None. The UPGRADEDB parameter
does not need to be specified during future server
the command to specify a server options file, ensure
start-ups.
that the name and location of the file is correct.
ANR0364W Server has detected a zero bit mismatch

ANR0368I Formatting server's database: database
error.
name.
System action: The server is done creating its
administrator that the server has detected a zero bit
database
mismatch error during a RESTORE DB process. The
recovery process is the database must be restored with User response: None.
a process that includes a DSMSERV FORMAT. Either
the data base volumes must be formatted then a
ANR0369I Stopping the database manager because
DSMSERV RESTORE DB performed from a data base
of a server shutdown.
backup that does not have this problem, or a
DSMSERV UNLOADDB followed by the formatting, System action: Stopping the server's database
then a DSMSERV LOADDB. Do not use DSMSERV manager.
DUMPDB on the data base for this recovery.
System action: Server RESTORE DB continues.
User response: Perform one of the data base recovery ANR0370E Diagnostic(ID) During the format
actions after the RESTORE DB completes. operation, the server cannot create files
in one or more directories that you
specified for log type. Ensure that the file
ANR0365E Database database name is currently in
system where the directory is located
use and can not be removed.
has sufficient space.
Explanation: Space is not available for the server to
administrator that the server has detected that the
write data to the directory.
database is currently in use during a REMOVE DB
process. System action: The format operation stops.
System action: Server REMOVE DB stops. User response: Before reissuing the command to
format a new database, check the following items:
User response: Drop all database connections then
issue the command again. v Check whether the format operation created a
database but did not remove the database after the
failure. If the database that was created was not
ANR0366I Database database name was removed removed, use the utility DSMSERV REMOVEDB
successfully. db_name to remove it.
Explanation: This message is issued to notify the v Check that space is available to the directories that
administrator that the server has removed the server you specified for
database successfully. ACTIVELOGDIR,ARCHIVELOGDIR, and
ARCHFAILOVERLOGDIR. Ensure that the amount
of space meets requirements. For example, the
User response: The server database was removed. In directory for ACTIVELOGDIR must have at least 8
order to run the TSM server, you need to format a new GB space available.
database using the 'DSMSERV FORMAT' command. v Remove any files that are in the directories that you
want to use for the recovery logs.
ANR0367W The server failed to format the database
database name. This database name ANR0371E Error setting environment variable
already exists. environment variable name with value value
Explanation: While attempting to format a database, - return code return code value.
the Tivoli Storage Manager server has found that this Explanation: The server is unable to set the content of
database name already exists. the environment variable on the operating system to
System action: Server format stops. the value specified in the message. The return code in

ANR0372E ANR0379W
the message is the last error code set in the operating

ANR0376E Database database name is not found and
system. The return code, or, last error code is a system
can not be removed.
error code as a result of the failed function call to set
the environment variable. Explanation: This message is issued to notify the
System action: The server operation stops.
is reporting the DB cannot be found during a REMOVE
User response: Refer to the list of system error codes DB process.
provided by the operating system to determine the
cause of the problem. Resolve the problem and retry
the server operation. User response: Interrogate the database, correct the
ANR0372E Database database name is currently
damaged and can not be removed. ANR0377E Database database name is reporting a
drive is not found and can not be
removed.
database is damaged during a REMOVE DB process. Explanation: This message is issued to notify the
is reporting a database drive cannot be found during a
User response: Interrogate the database, correct the REMOVE DB process.
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
drive is not found and can not be
database is reporting a File error during a REMOVE DB
removed.
process.
User response: Interrogate the database, correct the is reporting a warning during a REMOVE DB process.
System action: Server REMOVE DB completed
successfully.
ANR0374E Database database name is invalid and
User response: The drop database command has
can not be removed.
completed successfully, however, there are some nodes
Explanation: This message is issued to notify the where the database alias or database name was not
administrator that the server has detected that the API found. It is possible that DROP DATABASE AT NODE
is reporting an Invalid DB error during a REMOVE DB was already performed on these nodes.
process.
System action: Server REMOVE DB stops. ANR0379W A server database deadlock situation has
been encountered; the lock request for
User response: Interrogate the database, correct the the lock name lock, key name will be
problem then issue the command again. denied to resolve the deadlock.
Explanation: The server detected a deadlock situation
ANR0375E Database database name is reporting an between a number of processes attempting to access
authorization error and can not be database information. A lock request for one of the
removed. processes will be denied to resolve the database
Explanation: This message is issued to notify the deadlock. When the server processes encounter a
administrator that the server has detected that the database deadlock, they usually try to run the function
database is reporting an authorization error during a that was in progress when the deadlock was
REMOVE DB process. encountered again. Not all process can explicitly try an
operation again. For example, migration and
System action: Server REMOVE DB stops. reclamation will eventually try again. However,
User response: Interrogate the database, correct the something like a delete volume run in a macro will
problem then issue the command again. only be tried again if the delete command is reissued
either in the macro or the command line.
System action: A lock request fails for one of the

ANR0380W ANR0387I
deadlocked processes. Server operation continues. current value for the maximum utilization.
User response: If a process can be retried (like
migration), monitor the retry effort to see if it succeeds. ANR0383I The recovery log maximum utilization
If the process or command cannot be retried, reissue statistic was successfully reset.
the command or macro that caused the action.
Explanation: The recovery log maximum utilization
Consider what other processes are running at the time statistic has been reset by the RESET
the deadlock is reported. For example, if a process is LOGMAXUTILIZATION command to the current
started manually, as opposed to running as part of your utilization.
regularly scheduled server maintenance tasks, that
process may have caused the deadlock. You might have
to adjust the scheduling of your server maintenance User response: The QUERY LOG command
tasks to avoid the problem. (FORMAT=DETAILED) can be used to display the
current value for the maximum utilization.
ANR0380W The database buffer pool recovered
from an overcommit of number of pages ANR0384I The recovery log consumption statistic
pages. Consider increasing your buffer was successfully reset.
pool size by kilobytes needed kilobytes
under current server load. Explanation: The recovery log consumption statistic
has been reset by the RESET LOGCONSUMPTION
Explanation: During normal processing, additional command.
buffer pool space is required beyond that specified in
the BUFPOOLSIZE in the server options file. The System action: Server operation continues.
additional kilobytes of buffer pool space that are User response: The QUERY LOG command
required are indicated in the message. (FORMAT=DETAILED) can be used to display the
System action: Server operation continues; the current value for recovery log consumption.
additional buffer pool space is obtained from available
server memory. ANR0385I Could not free sufficient buffers to
User response: If the current server load is typical, reach reduced BUFPoolsize.
consider increasing the size specified for your Explanation: A reduction in the database buffer pool
BUFPOOLSIZE option by the number of kilobytes size was requested. However, too many buffers were in
specified in the message. To do this, you must halt the use to reach the lower buffer pool size.
server, change the options file, and then restart the
server. System action: Server operation continues. Whatever
buffer pool size reduction that could be achieved is in
effect. The new bufpoolsize is written to the options file
ANR0381I Buffer pool statistics were successfully for use on the next server startup.
reset.
Explanation: Buffer pool statistics, such as the Cache
Hit Ratio, have been reset. The RESET BUFPOOL
command and the ESTIMATE DBREORGSTATS ANR0386I The BUFPoolsize has been changed to
command will reset the buffer pool statistics. buffer pool size.
System action: Server operation continues. Explanation: The BUFPoolsize option has been
changed to the indicated value.
User response: The QUERY DB command
(FORMAT=DETAILED) can be used to to display the System action: Server operation continues.
current values for the buffer pool statistics. User response: None.
ANR0382I The database maximum utilization ANR0387I Evaluating node node name using storage
statistic was successfully reset. agent storage agent for LAN-free data
Explanation: The database maximum utilization movement.
statistic has been reset by the RESET Explanation: The server is evaluating whether the
DBMAXUTILIZATION command to the current node and storage agent can use storage pools capable
utilization. of LAN-free data movement.
System action: Server operation continues. System action: The server evaluates the storage pool
User response: The QUERY DB command destinations available to this node and reports which
(FORMAT=DETAILED) can be used to display the storage pools can and cannot be used for LAN-free
data movement.

ANR0388I ANR0393I
User response: Review the results of this processing to deadlocked processes. Server operation continues.
determine if the appropriate LAN-free environment is
User response: If a process can try again (like
configured.
migration), then monitor the subsequent attempt to see
if it succeeds or not. If it fails, contact a service
ANR0388I Node node name using storage agent representative. If the process or command is not able to
storage agent has capable count storage automatically try again, then reissue the command or
pools capable of LAN-free data macro that caused the action to occur. If it fails again,
movement and not capable count storage contact a service representative for further assistance to
pools not capable of LAN-free data better isolate the deadlock condition.
movement.
Explanation: The server has completed evaluation of ANR0391I Evaluating LAN-free destination for
the LAN-free and non-LAN-free storage pool node node name using storage agent
destinations for this node using this storage agent. The storage agent.
server determined that there are capable count storage
Explanation: The server is evaluating to determine
pools that are capable of LAN-free data movement. It
LAN-free destination storage pools for the node and
also determined that there are not capable count storage
storage agent referenced.
pools that cannot be used for LAN-free data
movement. System action: The server will evaluate the storage
pool destinations available to this node and report
which pools may be used LAN-free and for those that
User response: Review the other messages issued to can not be used LAN-free it will report why that pool
determine which storage pools are capable of LAN-free can not be used.
data movement and those which are not capable of
User response: Review the results of this processing to
LAN-free data movement for this node using this
determine if the appropriate LAN-free environment is
storage agent.
configured.
ANR0389W Node node name has data path

ANR0392I Node node name using storage agent
restrictions.
storage agent has LAN-free count storage
Explanation: The node name has data path restrictions. pools enabled for LAN-free data transfer
The registered node has data write path, data read and non-LAN-free count storage pools that
path, or both, configured to not allow LAN-free are not enabled for LAN-free data
operations. transfer.
System action: None. Explanation: The server has completed evaluation of
the storage pool destinations for this node using this
User response: Issue the command QUERY NODE
storage agent. The server determined that there are
node name F=D and evaluate the data read path and
LAN-free count storage pools that are LAN-free enabled.
data write path settings. To store data or read data
It also determined that there are non-LAN-free count
using LAN-free data movement, set the data write path
storage pools that are not enabled for LAN-free data
to ANY or LANFREE.
transfer for this node.
ANR0390W A server database deadlock situation has
been encountered; the lock request for User response: Review the other messages issued to
transaction transaction ID will be denied. determine which storage pools are capable of LAN-free
data transfer and those which are not capable of
Explanation: The server detected a deadlock situation
LAN-free data transfer for this node using this storage
between a number of processes that were attempting to
agent.
access database information. A lock request for one of
the processes is denied, to resolve the database
deadlock. When server processes encounter a database ANR0393I Management class management class with
deadlock, they usually reattempt the function that was destination storage pool for operation type
in progress when the deadlock was encountered. Not operations is enabled for LAN-free data
all process can explicitly try an operation again. For transfer for nodee node name using
example, migration and reclamation will eventually be storage agent storage agent name.
tried again. However, something such as a delete
Explanation: The storage pool is capable of LAN-free
volume run in a macro will only be tried again if the
data transfer operations for node node name using
delete command is reissued either in the macro or the
storage agent storage agent name.
command line.
System action: A lock request fails for one of the

ANR0394W ANR0400I
User response: None. not capable of LAN-free operations. In this case, the
destination for this node or the domain that this node
is assigned to should be changed to one that is
ANR0394W Management class management class with
LAN-free enabled. The next reason a storage pool is
destination storage pool for operation type
reported as not LAN-free capable is if there are no
operations is not enabled for LAN-free
paths defined for a device to this storage agent. Use the
data transfer for node node name using
QUERY PATH, QUERY SERVER, QUERY STGPOOL,
storage agent storage agent name because
QUERY LIBRARY, and QUERY DRIVE commands to
this destination is a CENTERA device.
determine the drive or drives that need paths defined
Explanation: The destination storage pool is not capable to this server (storage agent). The final reason a storage
of LAN-free data transfer operations for node node pool is reported as not LAN-free enabled is if there are
name using storage agent storage agent name. This define paths to this storage agent but no paths are
storage pool uses a CENTERA device and as such can online. Use the QUERY PATH and QUERY DRIVE
not be used for LAN-free operations. commands to evaluate this and if necessary use update
those paths to be online.
User response: To configure this node for LAN-free ANR0397I Session session number for node
data transfer operations, update the destination storage agent_node has begun a proxy session for
pool for the copygroup or assign this node to a domain node target_node.
that has LAN-free storage pool destinations.
Explanation: A client session has begun proxy
operations.
destination storage pool for operation type System action: The server granted a proxy session to
operations is not enabled for LAN-free a client node.
data transfer for node node name using
storage agent storage agent name because
this destination is configured for
simultaneous write. ANR0398W Session session number for node
agent_node has failed to begin a proxy
Explanation: The destination storage pool is not capable
session for node target_node.
of LAN-free data transfer operations for node node
name using storage agent storage agent name. This Explanation: A client session attempted to begin a
storage pool is configured for simultaneous write proxy operation. The server failed the client request.
operations. Simultaneous write operations are only This can occur if the agent node does not have a proxy
allowed for data sent directly to the server. Configuring association with the target node.
a storage pool for simultaneous write operations
System action: The server blocks the proxy
disqualifies it from being eligible for use for LAN-free
authorization attempt.
operations.
User response: To configure this node for LAN-free
ANR0399I Session session number for node
data transfer operations, update the destination storage
agent_node has ended a proxy session for
pool for the copygroup or assign this node to a domain
node target_node.
that has LAN-free storage pool destinations. Or update
this storage pool to disable simultaneous write by Explanation: A proxy session has been ended. The
setting the copy storage pools field to blank. server terminates a session if there is an error in the
protocol. On the other hand, the client can also
terminate the session.
destination storage pool for operation type System action: The server, or the client, has ended a
operations is not LAN-free enabled for proxy session for a client node.
node node name using storage agent name
because no online paths are available. User response: None.
Explanation: The destination storage pool is not capable

of LAN-free data transfer operations for node node ANR0400I Session session number started for node
name using storage agent storage agent name. node name (client platform) (communication
method).
Explanation: A new client session has been initiated
User response: A storage pool can be reported as not by the specified node. The session number, client
having LAN-free enabled paths for a number of platform type and communication method used by this
reasons. First, if this is a DISK storage pool, these are

ANR0401I ANR0410E
session are included in the message.

ANR0406I Session session number started for node
System action: The server begins a communications node name (client platform) (communication
session to service the client node. method communication address).
User response: None. Explanation: A new client session has been initiated
by the specified node. The session number, client
platform type, communication method and address
ANR0401I Session session number started for node used by this session are included in the message.
node name (client platform) (communication
method) (WDSF client). System action: The server begins a communications
session to service the client node.
Explanation: A new WDSF client session has been
initiated by the specified node. The session number, User response: None.
client platform type and communication method used
by this session are included in the message.
ANR0407I Session session number started for
System action: The server begins a communications administrator administrator ID
session to service the client node. (administrators platform) (communication
method communication address).
Explanation: A new administrator client session has
been initiated by the specified administrator. The
ANR0402I Session session number started for session number, administrators platform type,
administrator administrator ID communication method and address used by this
(administrators platform) (communication session are included in the message.
method).
System action: The server begins a communications
Explanation: A new administrator client session has session to service the administrator client.
been initiated by the specified administrator. The
session number, administrators platform type and User response: None.
communication method used by this session are
included in the message.
ANR0408I Session session number started for server
System action: The server begins a communications server name (servers platform)
session to service the administrator client. (communication method) for purpose.
User response: None. Explanation: A new server session has been initiated
by the specified server for the specified purpose. The
session number, servers platform type and
ANR0403I Session session number ended for node communication method used by this session are
node name (client platform). included in the message.
Explanation: A client session has completed normally. System action: The server begins a communications
System action: Server operation continues. session to service the administrator client.
User response: None. User response: None.
ANR0404I Session session number ended for node ANR0409I Session session number ended for server
node name (client platform) (WDSF client). server name (client platform).
Explanation: A WDSF client session has completed Explanation: A server has completed normally.
normally. System action: Server operation continues.
System action: Server operation continues. User response: None.
ANR0410E EXPORT operation to server server name
ANR0405I Session session number ended for rejected - administrator administrator is
administrator administrator ID (client not authorized to perform the import
platform). operation on the target server.
Explanation: An administrative client session has Explanation: An export operation to the named server
completed normally. was rejected, because the administrator issuing the
export command is not defined on the target server or
System action: Server operation continues. does not have sufficient authority to perform the
User response: None. import operation on the target server.

ANR0411I ANR0419W
System action: Server operation continues. System action: Server operation continues.
ANR0411I Session session number for administrator ANR0416W Session session number for node node
administrator name logged in as node node name not allowed to operation using path
name restored or retrieved object type data transfer path.
object: node node name, filespace filespace
Explanation: This session attempted this operation
name, object object name.
using the specified data transfer path. This operation is
Explanation: This message logs information about an not permitted for this client.
object that was restored or retrieved by an
administrator logged in for a node.
User response: Issue QUERY NODE
FORMAT=DETAILED for this node to see the current
User response: None. DATA WRITE PATH or DATA READ PATH settings.
These settings determine if a given operation is
permitted using a specific data transfer path. If this
ANR0412I Session session number for node node
client node should be permitted to perform this
name(Userid=user id), restored or
operation using this data transfer path, the UPDATE
retrieved object type object: node node
NODE command should be used to correct this.
name, filespace filespace name, object object
name.
ANR0417W Session session number for node node
Explanation: This message logs information to the
name terminated - data transfer path not
activity log about an object that was restored or
allowed.
retrieved by a user logged in for a node. A user ID
with no value indicates that an administrative or root Explanation: This session attempted an operation that
user on the platform initiated the restore. needed a data transfer path that this node is not
allowed to use.
System action: This client session terminates.
User response: Refer to the ANR0416W message that
was issued for this client session to determine which
ANR0413I Session session number for administrator
operation and data transfer path was attempted.
administrator name logged in as node node
name is restoring backup set: node node
name, set filespace name. ANR0418W Session session number for administrator
administrator name (client platform) is
Explanation: This message logs information about a
refused because an incorrect password
backup set restored by an administrator logged in for a
was submitted.
node.
Explanation: The server refuses a request to start a
client session because an invalid password has been
User response: None. submitted by the client during sign-on processing.
System action: The server will continue to deny access
ANR0414I Session session number for node node attempts by this client until a valid password is
name is restoring backup set: node node submitted.
name, set filespace name.
User response: Enter the proper password. If you
Explanation: This message logs information about a have forgotten the password, contact an authorized
backup set restored by a node. administrator, who can assign a new password using
the UPDATE ADMIN command.
User response: None. ANR0419W Administrative client userid
administrative ID cannot be used when
ANR0415I Session session number proxied by storage authentication is on.
agent name started for node node name. Explanation: The server refuses a request for a client
Explanation: This session is started for the indicated (administrative) session because the user ID specified
node and the storage agent acts as the proxy for the cannot be used when authentication of IDs is in effect.
node. Client node sessions are used to perform SERVER_CONSOLE is an administrative ID that has
LAN-free operations between the client and server. this restriction.

ANR0420W ANR0427W
User response: Use an administrative ID that was User response: Register the administrator name with
registered for this server and that has a password. the server before establishing a session. An authorized
administrator must use the REGISTER ADMIN
command to register the administrator with the server.
name (client platform) refused - server
disabled for user access. ANR0424W Session session number for node node
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. Explanation: The server refuses a request to start a
client session because an invalid password has been
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
issue the ENABLE SESSION command before client
nodes are permitted access to the server. User response: Enter the proper password. If the
password has been forgotten by the user, an authorized
administrator can assign a new password by using the
UPDATE NODE command.
name (client platform) refused - sign-on
protocol violation.
Explanation: The server refuses a request for a client
name (client platform) refused - node
session because sign-on protocol has been violated.
password has expired.
Explanation: The server refuses the specified session
User response: This error is usually the result of a because the client nodes password has expired.
client programming error in which the sign-on verb has
been incorrectly formatted and delivered to the server.
This error can also result when the server is contacted User response: Upon receipt of this error condition,
by an application that is not a part of this product. the client program immediately reconnects to the server
specifying a password update session and prompts the
user for a new password. After the user enters a new
password, the client reconnects to the server for normal
operations. Alternatively, an authorized administrator
name not registered.
can update the client password using the UPDATE
Explanation: The server refuses a request to start a NODE command.
client session because the client node name is not
registered in the server database.
System action: Server operation continues. name (client platform) refused - open
registration not permitted.
User response: Register the node name with the
server before establishing a session. If the server is Explanation: The server refuses a client session
running with OPEN registration, no action is required; because an open registration action has been attempted
the client prompts the user for a password and and the server is running with CLOSED registration.
registers the client with the server. If CLOSED
registration is in effect on the server, an authorized
administrator must use the REGISTER NODE User response: Ask an authorized administrator to
command to register the client node name with the submit the request using the REGISTER NODE or
server. REGISTER ADMIN command.
ANR0423W Session session number for administrator ANR0427W Session session number for node node
administrator ID (client platform) refused - name (client platform) refused - server
administrator name not registered. version is down-level with this client.
Explanation: The server refuses a request to start an Explanation: The server refuses a client session
administrative session because the administrator name because the client program version level is newer than
is not registered in the server database. that supported by the server program.

ANR0428W ANR0434W

ANR0431W Session session number refused -
User response: Apply service to the server program to administrator administrator ID (client
make it compatible with the newer client program, or platform) is locked.
use an older client program to contact the server.
Explanation: The server refuses the specified
administrative session because the administrator is
ANR0428W Session session number for node node locked from server access (with the LOCK ADMIN
name (client platform) refused - client is command or by the LDAP directory server).
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 ANR0432W Session session number for node node
make it compatible with the newer server program. name (client platform) refused -
insufficient memory.
ANR0429W Session session number for node node Explanation: The server ends the specified session
name (client platform) refused - maximum because sufficient memory (virtual memory) is not
server sessions (max sessions allowed) available.
exceeded.
System action: The server ends the session and
Explanation: The server refuses the specified client or continues operation.
administrative session because the maximum number
of concurrent client sessions has been exceeded.
System action: Server operation continues. application.
User response: If necessary, increase the maximum

number of permitted sessions. To do this, update the ANR0433W Session session number for node or
value for the MAXSESSIONS parameter in the server administrator ID (client platform) was
options file and restart the server with the updated refused because of insufficient recovery
options file. Note that increasing the MAXSESSIONS log space.
value requires additional memory resource by the
Explanation: If a log runs out of space, the current
server. You may want to retry the connection at a later
transaction is rolled back. The server issues an error
time.
message and halts. You cannot restart the server until
the recovery log size is increased.
name is locked. User response: Monitor archive logs and active logs. If
the recovery log space is insufficient, monitor the
Explanation: The server refuses the specified client
archive log space first. If the archive log space is full or
session because the node is locked from server access
nearly full, run a full database backup to remove
(with the LOCK NODE command or by the LDAP
archive logs and consider adding more disk space to
directory server).
the archive log directory. If the archive log space is not
System action: Server operations continue. full and the active log space is full or nearly full,
update the value of the ACTIVELOGSIZE option in the
User response: Before the client node is permitted to dsmserv.opt file. Set the value of the ACTIVELOGSIZE
access the server, a properly authorized administrator option to the new maximum size of the active log.
must unlock the node. Nodes using LOCAL
authentication can be unlocked with the UNLOCK
NODE command. Nodes using LDAP authentication ANR0434W Session session number for node or
can be unlocked from within the LDAP directory administrator ID (client platform) was
server. refused because of insufficient database
space.
Explanation: The server ends the specified client or

ANR0435W ANR0441W
administrative session because of insufficient database restart the session. If the problem persists, contact your
space. service representative.
System action: The server ends the session, but
continues operation. ANR0438W Session session number archive operation
for client client node name (client platform)
User response: To increase the amount of database
has been denied - Server is not in
space that is available to the server, issue the EXTEND
compliance with license terms.
DBSPACE command. Add one or more directories to
the database. Explanation: The server refuses a client archive
operation because the current server configuration is
not in compliance with license terms.
name (client platform) refused - internal System action: Server operation continues. Clients
error detected. may perform any action except backup or archive.
Explanation: The server ends the specified session User response: Use the QUERY LICENSE command to
because an internal logic error is detected. determine the license terms that are no longer in
compliance.
System action: The server ends the session and
continues operation.
ANR0439W Session session number backup operation
User response: To determine the source of the error,
for client client node name (client platform)
the administrator can examine server messages issued
has been denied - Server is not in
prior to this message. The QUERY ACTLOG command
can be used to view the activity log and search for
messages. If the error cannot be isolated and resolved, Explanation: The server refuses a client backup
contact your service representative. operation because the current server configuration is
not in compliance with license terms.
ANR0436W Session session number refused - a WDSF System action: Server operation continues. Clients
client is attempting to access the server may perform any action except backup or archive.
using client name client node name (client
User response: Use the QUERY LICENSE command to
platform), associated with a non-WDSF
determine the license terms that are no longer in
client.
compliance.
Explanation: The server refuses a client session
because a Workstation DataSave Facility (WDSF) client
ANR0440W Protocol error on session session number
is attempting to access the server using a node name
for node client node name (client platform) -
associated with a non-WDSF client. When converting
invalid verb header received.
from WDSF, WDSF client programs cannot be used to
access the server with a specific node name once the Explanation: The server detects a protocol error on the
non-WDSF client program has been used to access the specified session because an invalid verb header has
server with that node name. been received from the client. Verb headers always
precede communication sent to the server from the
client or from the server to the client.
User response: Access the server using a non-WDSF
System action: The server ends the client session.
client program for the node name.
User response: Correct the programming error in the
client program if it has been written by your
ANR0437W Session session number for node client
installation using WDSF verbs. Otherwise, contact your
node name (client platform) encountered an
service representative.
internal server error while checking
license compliance.
Explanation: The server encountered an internal error
in determining if the server is in compliance with
invalid data length received.
license terms.
Explanation: The server detects a protocol error on the
System action: The client session is ended.
specified session because an invalid verb length has
User response: Use the QUERY LICENSE and QUERY been received from the client.
STATUS commands to determine if the server is in
compliance with license terms. Start an AUDIT
LICENSES process to readjust server license User response: Correct the programming error in the
information. When this process completes you may client program if it has been written by your

ANR0442W ANR0448W
installation using WDSF verbs. Otherwise, contact your User response: Correct the programming error in the
service representative. client program if it has been written by your
invalid stream mode switch. ANR0446W Session session number client client node
name compression method unsupported -
Compression forced OFF. Please obtain
specified session because the client has attempted an
the latest level of the client code.
illegal stream operation.
Explanation: The client is using a compression
method that is no longer supported by the Server.
System action: Server operation continues. The clients
backup operation continues, without compressing the
installation. Otherwise, contact your service
data.
representative.
User response: The compression method used by the
client is no longer supported. In order to use
compression, the client needs to be upgraded to a client
service level that supports the newer compression
invalid "field name" field found in "verb
method.
name" verb (offset offset position).
ANR0447W Session session number space
specified session because an invalid field has been
management migration operation for
found in a verb sent from the client node.
client client node name (client platform) has
System action: The server ends the client session. been denied - Server is not in
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. ANR0448W Session session number space
management migration operation for
User response: If the client generating the error is not client client node name (client platform) has
an API client, contact your service representative. If the been denied - server is not licensed for
client generating the error is an API client, contact the space management support.
owner of the API client. If the client generating the
error is a client that you have created using WDSF Explanation: The server refuses a client space
verbs, correct the programming error in your client management migration operation because the server is
program. not licensed to support space-managed clients.
User response: Licenses to support space-managed
clients can be obtained from your service provider or
maximum group transaction size
re-seller. The REGISTER LICENSE command can be
exceeded.
used with these licenses to enable space management
Explanation: The server detects a protocol error on the support.
specified session because the client has attempted to
group more than the maximum database update
operations in a single database transaction.

ANR0449W ANR0454E
ANR0449W Session session number space ANR0452W Session for server server name refused -
management migration operation for server name not defined for server to
client client node name (client platform) is server communications.
in violation of server license terms -
Explanation: The server refuses a request to start a
server is not licensed for space
server to server session because a server name is not
management support.
defined in the server database, or the server definition
Explanation: The server warns about a client space does not have a SERVERPASSWORD. Server to server
management migration operation because the server is communications using the serverpassword requires that
not licensed to support space-managed clients. the each server has had a server definition for the other
server.
User response: Licenses to support space-managed
clients can be obtained from your service provider or User response: Register the server names on both
re-seller. The REGISTER LICENSE command can be servers before establishing a session, or update the
used with these licenses to enable space management server's existing server definition and set a
support. SERVERPASSWORD. An authorized administrator
must use the DEFINE SERVER or UPDATE SERVER
command register the servers and set the passwords.
ANR0450W Session session number for server server
name (client platform) refused - server
name not defined for server to server ANR0453W Server to server session refused - no
communications. password defined.
Explanation: The server refuses a request to start a Explanation: The server to server session cannot be
server session because the requesting server name is initiated because no server password has been defined
not defined in the server database, or the requesting for this server.
server definition does not have a SERVERPASSWORD,
or a password or node name is not setup for virtual
volume use on the source server. User response: Define a server password with the SET
SERVERPASSWORD command and retry the
command.
User response: Register the requesting server name
with the server before establishing a session, or update
ANR0454E Session rejected by server server name,
the existing requesting server definition and set a
reason: rejection reason.
SERVERPASSWORD. An authorized administrator
must use the DEFINE SERVER or UPDATE SERVER Explanation: The server tried to open a session with
command to register the requesting server and set the the named server. The session was rejected for the
password. For a virtual volume environment, the indicated reason.
source server must have a definition for the target
server which includes a node name and password. System action: The operation fails.
User response: Check both the servers for any
ANR0451W Session session number for server server additional messages that might further describe the
name (server platform) refused - invalid reason the session was rejected. For a reason of
password submitted. AUTHENTICATION FAILURE, ensure that all
passwords have been set correctly on both servers. The
Explanation: The server refuses a request to start a password for the server (set by SET
server session because an invalid password has been SERVERPASSWORD on server X) and the password in
submitted during sign-on processing. The server will the server definition (set by DEFINE or UPDATE
continue to deny access attempts by that server until SERVER X SERVERPASSWORD=) are the same
valid passwords are submitted. password. For a reason of VERIFICATION FAILURE,
use the QUERY SERVER command to determine that
the HLADDRESS and LLADDRESS of the target server
User response: Set the proper passwords. If the are correct. If they are not, correct them with the
password has been changed on either server, an UPDATE SERVER command. If they are correct,
authorized administrator can set new passwords by resynchronize with the target server by issuing the
using the UPDATE SERVER command with the UPDATE SERVER FORCESYNC=YES. For a reason of
SERVERPASSWORD parameter. COMMUNICATION FAILURE ensure that the target
server is available and that TCPIP is available on both
servers. For a reason of NO RESOURCE, ensure that
the receiving server is enabled, has sufficient DB, LOG,
and memory resource to support the source server

ANR0455W ANR0462W
session. For a reason of INTERNAL ERROR, use the

ANR0459W Signon for administrator administrator
messages on the target server to determine the
name refused - invalid administrator
problem. For all reasons, if none of the above are
name and/or password submitted.
applicable, ensure that the shown server has not
disabled this server with the DISABLE SESSIONS Explanation: The server refuses a request to start an
SERVER command. administrative session because an invalid administrator
name and/or password has been submitted by the user
during sign-on processing. The server will continue to
ANR0455W Invalid Command command name for
deny access attempts by this administrator until a valid
SNMP session.
password is submitted, or until the administrator is
Explanation: An SNMP administrative session locked due to maximum number of invalid password
attempted to run a command which is not an macro attempts being exceeded.
invocation. SNMP administrative sessions are only
allowed to issue macro commands.
User response: Enter the proper password. If the
password has been forgotten by the user, an authorized
User response: Enter commands through the SNMP administrator can assign a new password by using the
administrative interface which are macros defined on UPDATE ADMIN command.
the server.
ANR0460W Open registration failed for session
ANR0456W Session rejected for server server name - session number - node name node name
the server name at High level address, Low (client platform) already exists.
level address does not match.
Explanation: The server refuses a client session during
Explanation: The server name at the address specified open registration because the client has specified a
does not match the name in the server definition. The node name that is already registered on the server.
connection is not established.
System action: The server continues.
User response: The client program user must specify a
User response: Ensure the HLADDRESS and different node name for the client in the client options
LLADDRESS in the define server command are correct, file.
and that the servername on the server being contacted
matches the name used in the DEFINE SERVER
command.
session number for node node name (client
platform) - policy domain STANDARD
ANR0457W Session for server server name refused - does not exist.
crossdefine is not allowed on this
server.
open registration because the STANDARD policy
Explanation: The server refuses a request to start a domain does not exist. All nodes added to the server
server to server session for crossdefine because it is not database under open registration are automatically
allowed on this server. The server will deny any assigned to the STANDARD policy domain. This policy
sessions for crossdefine until crossdefine is allowed on domain must be defined and have an active policy set
this server. to support open registration.
User response: An authorized administrator must use User response: If you want to support open
the SET CROSSDEFINE ON command to allow cross registration, define a policy domain using the DEFINE
registration of servers. DOMAIN command with the name STANDARD and
activate a valid policy set in the domain. You can issue
the UPDATE NODE command to move nodes to
ANR0458S Server server name does not support different policy domains after the nodes have registered
access by the Storage Agent. themselves through open registration.
Explanation: The storage agent attempted to contact a
Database Server, but the server contacted was not at ANR0462W Open registration failed for session
the correct level. session number for node node name (client
System action: The Storage Agent terminates. platform) - invalid node name.
User response: Specify a correct Database Server in Explanation: The server refuses a client session during
the devconfig file for the Storage Agent. open registration because the node name specified by
the client is not valid.

ANR0463W ANR0470W

ANR0466E The SETSTORAGESERVER command
User response: Specify a node name in the options file did not complete successfully.
of the client program that contains valid characters and
Explanation: The SETSTORAGESERVER command
does not exceed the maximum length in size. Refer to
encountered an error and did not complete successfully.
Backup-Archive Clients Installation and Users Guide for a
description of the node name restrictions. System action: Storage agent operation terminates.
User response: Please review prior error messages and
ANR0463W Open registration failed for session take the necessary corrective actions.
platform) - invalid password.
ANR0467I The SETSTORAGESERVER command
Explanation: The server refuses a client session during completed successfully.
open registration because the password name specified
Explanation: The SETSTORAGESERVER command
by the user is not valid.
has completed successfully, and the appropriate device
System action: Server operation continues. configuration files have been updated.
User response: Specify a password that uses valid System action: Storage agent operation terminates.
characters and is less than the maximum length in size.
User response: None
Refer to Backup-Archive Clients Installation and Users
Guide for a description of the password restrictions.
ANR0468E Server-to-server export and import not
allowed with server server name. Export
server is at version export version; import
server is at version import version.
platform) - exceeded number of nodes
available under license terms. Explanation: An attempt was made to export to an
outdated server. The server on which the import is
Explanation: The server detected an attempt to
performed must be at the same or later level than the
register more nodes than allowed by the terms of the
server from which the data was exported.
current license.
System action: The export operation ends and server
System action: Server operation continues, but the
REGISTER NODE command fails, and the node is not
registered. User response: Export to a server that is at the same
or later level.
compliance. ANR0469W Session session number for node node
name (client platform) refused - client is
not configured for archive retention
protection.
platform) - policy domain STANDARD Explanation: The server refuses a client session
does not have an ACTIVE policy set. because the client is not configured for archive
retention protection.
open registration because the STANDARD policy System action: Server operation continues.
domain does not have an active policy set. All nodes
added to the server database under open registration User response: Either disable archive retention
are automatically assigned to the STANDARD policy protection on the server or configure the client for
domain. This policy domain must be defined and have archive retention protection.
an active policy set to support open registration.
System action: Server operation continues. ANR0470W Session session number for administrator
administrator name refused -
User response: If you want to support open administrator password has expired.
registration, define a policy domain using the DEFINE
DOMAIN command with the name STANDARD and Explanation: The server refuses the specified session
activate a valid policy set in the domain. You can issue because the administrators password has expired.
the UPDATE NODE command to move nodes to System action: Server operation continues.
different policy domains after the nodes have registered
themselves through open registration. User response: Upon receipt of this error condition,
the client program immediately reconnects to the server
specifying a password update session and prompts the

ANR0472E ANR0477W
user for a new password. After the user enters a new specify the port to be used for administrative sessions.
password, the client reconnects to the server for normal This is typically specified by the TCPADMINPORT
operations. Alternatively, an authorized administrator option in both client and server option files.
can update the client password using the UPDATE
ADMIN command.
name (client platform) refused - node is
ANR0472E The database manager did not start. A not allowed to initiate sessions on
tablespace container is inaccessible. administrative port.
Explanation: The server was unable to start the Explanation: The server had refused to start a session
database manager. with the specified client node because the node
connected to the server on the server's administrative
port. When different port numbers are used for
User response: Before restarting the server, check the administrative and client sessions, client sessions may
following items: be started only on the port used for client sessions.
v Reboot the system. System action: Server operation continues.
v Check that the directories for dbdir, log, or devices
User response: The client option file should be
exists and that the file system is mounted (if it is on
updated to specify the port to be used for client
a separate file system).
sessions. This is typically specified by TCPPORT option
v Make sure that the hardware and network in both client and server option files. The MVS server
connection are working properly. also uses the ICSPORT option.
v Fix any errors in the system log or db2diag.log.
ANR0473W Session session number for administrator name (client platform) refused - node is
administrator ID (client platform) refused - not allowed to initiate sessions.
administrator name does not have the
Explanation: The server had refused to start a session
correct level of authority over client
with the specified client node because the node is not
node.
allowed to initiate session. Only server initiated
Explanation: The server refuses a request to start an sessions are allowed with this client. The SESSIONINIT
administrative session because the administrator name parameter of the REGISTER NODE and UPDATE
does not have appropriate authority over the node. NODE commands control the ability of a client to
initiate sessions.
User response: Use command GRANT AUTHORITY
to grant appropriate authority to the current User response: An administrator can use the UPDATE
administrator ID. NODE command with the SESSIONINIT parameter to
specify that the client may initiate sessions.
Alternatively, sessions can be scheduled with the client
ANR0474W Session session number for administrator that are stared by the server through server-prompted
administrator ID (administrator platform) scheduling commands ( DEFINE SCHEDULE, DEFINE
was refused because administrators are ASSOCIATION ).
not allowed to initiate sessions on the
client port.
ANR0477W Session session number refused - The
Explanation: The server did not start the specified client client node name cannot access the
administrative session because the administrator server with a platform type of client
connected to the server on the server port that is used platform.
for client sessions, and the option
ADMINONCLIENTPORT is set to NO. When different Explanation: A client with a invalid combination of
port numbers are used for administrative and client node type and platform type has requested a session
sessions (controlled by the TCPPORT and with the server. For example, a node id of type NAS
TCPADMINPORT options), and option can only sign on with a platform type of "TSMNAS",
ADMINONCLIENTPORT is set to NO, administrative all other node types cannot use this platform type.
sessions can be started only on the port used for
System action: The session request is refused. The
administrative sessions (as specified by the
server operation continues.
TCPADMINPORT option).
User response: Verify that the Id used by a client to
sign on has the proper platform type.
User response: Update the client options file to

ANR0478W ANR0484W
System action: The server rolls back the transaction

ANR0478W Session request refused. Server is
that was in progress and the session is ended. Server
running in standalone mode.
Explanation: A client has requested a session with the
User response: If this message appears frequently,
server. The server is running in a mode in which it
consider incrementing the value specified for the
cannot start client sessions.
COMMTIMEOUT option. Use the SETOPT command to
System action: The session request is refused. The change the value of the COMMTIMEOUT option
server operation continues. without stopping or restarting the server. This update
changes the amount of time that the server waits for an
User response: No response is required. To reduce or
expected client message during an operation that
disable the display of this message, you can update the
causes a database update.
server options before running in standalone mode with
the COMMMETHOD NONE option. This will allow the
server to run without enabling client connections. ANR0482W Session session number for node node
name (client platform) terminated - idle for
more than idletimeout minutes minutes.
ANR0479W Session session number for server server
name (server platform) terminated - Explanation: The server ends a client session because
connection with server severed. it has been idle for more minutes than specified in the
IDLETIMEOUT parameter in the server options file.
Explanation: If server A has opened a connection with
The client program will automatically attempt to
server B, server B's session is ended because the
reconnect to the server when necessary.
communications link has been closed by a network
error or by server A's program. System action: Server operation continues.
System action: Server A continues operation. User response: If the problems persists, increase the
value specified for the IDLETIMEOUT parameter in the
User response: If server B halts operation or in some
server options file and restart the server. Many times,
way stops communicating with server A, this message
the client program is idle while waiting for the user to
will be displayed on server A indicating that the
choose an action to perform (for example, backup,
connection was closed suddenly by server B. A network
archive, restore, or retrieve files). If a user starts the
failure can also cause this message to be displayed. If a
client program and does not choose an action to
large number of these messages occur simultaneously,
perform, the session will eventually time out. The client
check the network for failure and correct any problems.
program automatically reconnects to the server when
the user chooses an action that requires server
ANR0480W Session session number for node node participation. Note that a large number of idle sessions
name (client platform) terminated - can inadvertently prevent other users from connecting
connection with client severed. to the server, so care should be used when increasing
the IDLETIMEOUT parameter.
Explanation: The specified client session is ended
because the communications link has been closed by a
network error or by the client program. ANR0483W Session session number for node node
name (client platform) terminated - forced
System action: Server operation continues. by administrator.
User response: If a user breaks out of a client Explanation: The server ends a client session in
program, this message will be displayed on the server response to a CANCEL SESSION command issued by
as the connection is suddenly closed by the client. A an authorized administrator.
network failure can also cause this message to be
displayed. If a large number of these messages occur System action: The server rolls back any transactions
simultaneously, check the network for failure and in progress for the terminated client session.
correct any problems.

name (client platform) was terminated. The
name (client platform) terminated -
client did not respond within
protocol violation detected.
commtimeout seconds seconds.
Explanation: The server ends the specified session
Explanation: The server ends a client session because
because a communications protocol error by the client
the client was holding database locks during a
has been detected.
transaction. The client did not respond within the
number of seconds specified by the COMMTIMEOUT System action: The server ends the client session.
server option.
User response: Examine the client message to

ANR0485W ANR0489W
determine the problem. Correct the programming error

in the client program. If the error cannot be isolated
name (client platform) terminated -
and resolved, contact your service representative.
transfer rate is less than (transfer rate)
If this session is a proxied LAN-Free session for a and more than (elapsed time since first data
storage agent, this error may be the result of a mount transfer) minutes have elapsed since first
point or volume preemption on the storage agent. data transfer.
Review the messages logged by the storage agent to
Explanation: The server is canceling client session
determine if a storage agent action caused this to occur.
number session number. Depending on the state of the
session, it may take a while for the session to be
ANR0485W Session session number for node node canceled. The server ends a client session because it has
name (client platform) terminated - been active for more minutes than specified in the
sufficient memory is not available. THROUGHPUTTIMETHRESHOLD parameter in the
server options file and the data transfer rate is less than
Explanation: The server ends the specified session the amount specified with the
because sufficient memory (virtual memory) is not THROUGHPUTDATATHRESHOLD parameter in the
available. server options file. The client is transferring data to the
System action: The server ends the session and server at an abnormally slow rate and may have
continues operation. become a bottleneck for handling data from other
clients. If the client has caused log records to be
User response: See the documentation for the written, it is possible that this client will prevent log
operating system about how to increase memory for an space reclamation.
application.
System action: The session is canceled and server
name (client platform) terminated - User response: If a low data transfer rate is not a
internal error detected. problem, the THROUGHPUTTIMETHRESHOLD or
THROUGHPUTDATATHRESHOLD parameters in the
Explanation: The specified client session is ended by server options file can be set to zero - this will disable
the server because an internal processing error has been the throughput check. The change can be made without
detected on the server. A programming error may have taking down the server and restarting it by using the
occurred in the server program. SETOPT THROUGHPUTTIMETHRESHOLD or the
System action: The session is ended and server SETOPT THROUGHPUTDATATHRESHOLD
operation continues. commands. If a low data transfer rate is not expected,
external causes should be investigated. This would
User response: If this session is a proxied LAN-Free include network problems and problems in accessing
session for a storage agent, this error may be the result data on the client node. The client program may
of a mount point or volume preemption on the storage automatically reconnect to the server, so this message
agent. Review the messages logged by the storage may appear on subsequent sessions until the data
agent to determine if a storage agent action caused this transfer problem is resolved. The default server
to occur. operation is not to perform a throughput check.
If the cause of the error can not be determined after
reviewing the activity log, contact your service ANR0489W Session session number refused for client
representative. node name - NAS type nodes are not
supported by a storage agent.
ANR0487W Session session number for node node Explanation: The specified client tried to connect to a
name (client platform) terminated - storage agent. The storage agent does not support a
preempted by another operation. node that is defined as TYPE=NAS.
Explanation: The server ends a client session in System action: The session request is refused. The
response to a cancel request issued by a higher priority server operation continues.
operation that needed the mount point that the client
was using. User response: The client should be re-configured to
not try LAN-free operations. This may be done by
System action: The server rolls back any transactions setting UPDATE NODE ENABLELANFREE=NO for the
in progress for the terminated client session. client.
User response: Reissue the operation. If this message
appears frequently, consider increasing the mountlimit
value for the affected device class.

ANR0490I ANR0497W
ANR0490I Canceling session session number for ANR0494I Volume volume name in use. Session
node node name (client platform) . session number for node node name (client
platform) being preempted by higher
Explanation: The server is canceling client session
priority operation.
number session number. This message is displayed in
response to the CANCEL SESSION command. Explanation: When a high priority operation
Depending on the state of the session, it may take a attempted to acquire a specific volume, it was being
while for the session to be canceled. used. To free the volume for this operation, the client
session identified is being cancelled by the system.
operation continues. System action: The lower priority client session is
cancelled to free up the volume.
User response: Restart the session that was cancelled,
it will wait until the higher priority operation if
ANR0491I No matching session(s) found to cancel.
finished with the volume. This cancelled session was
Explanation: The server cannot find any sessions to most likely a backup/archive session and you may just
cancel matching the specifications entered in the want to let it restart automatically during its next
CANCEL SESSION command. scheduled backup window.

ANR0495I Cannot cancel the specified
User response: Use the QUERY SESSION command to EXPORT/IMPORT session.
ensure that the session you wish to cancel is connected.
Reissue the command using the appropriate session Explanation: The server cannot cancel the session
number to cancel the client session. specified in the CANCEL SESSION command.
ANR0492I All drives in use. Session session number
User response: Export/Import sessions cannot be
for node node name (client platform) being
canceled using CANCEL SESSION. The user should
preempted by higher priority operation.
use the CANCEL PROCESS command to terminate the
Explanation: When a high priority operation EXPORT/IMPORT operation.
attempted to find an available drive, all the drives were
being used. To free up a drive for this operation, the
ANR0496E Session session number operation for
client session identified is being cancelled by the
client client node name (client platform) has
system.
been denied because verb (type verb
System action: The lower priority client session is name) is not allowed when archive
cancelled to free up a mount point (drive). retention is active.
User response: When a drive again becomes available, Explanation: The server refuses the specified client
restart the session that was cancelled. This session was operation because archive retention protection is active.
most likely a backup/archive session and you may just
want to let it restart automatically during its next
scheduled backup window. If this message appears User response: Do not send the specified operation to
frequently, you may want to increase the number of the server when archive retention protection is active.
drives available. See the MOUNTLIMIT parameter on
the UPDATE DEVCLASS command.
ANR0497W Session request refused from
non-Express client.
ANR0493I Restore session session number canceled.
Explanation: A non-Express client has requested a
Explanation: The specified session was canceled with session with the Express server. Only connections from
the CANCEL RESTORE command. an Express client will be accepted by an Express server.
System action: The restore session is canceled and System action: The session request is refused. The
server operation continues. server operation continues.

ANR0498W ANR0506I
can be used to update copy groups associated with

ANR0498W Session session number refused for client
space management and/or backup storage pools so
node name because restore DB is in
that they point to valid destinations.
progress.
Explanation: Restore DB is in progress, only
ANR0503I Session session number for administrator
connection from Client related to restore DB are
administrator name logged in as node node
allowed.
name restored or retrieved object type
System action: The session request is refused. The object: node node name, filespace filespace
server Restore DB operation continues. name, object object name, version version
of total version.
Explanation: This message logs information about an
object that was restored or retrieved by an
ANR0500W Transaction failed for session session
administrator logged in for a node.
number for node node name (client
platform) - invalid password submitted. System action: Server operation continues.
Explanation: The server ends a password update User response: None.
transaction because the user has not correctly specified
the current password.
ANR0504I Session session number for node node
System action: Server operation continues. name(Userid=user id), restored or
retrieved object type object: node node
User response: Update your password by correctly
name filespace filespace name, object object
specifying the current password. If the current
name, version version of total version.
password has been misplaced, the administrator can
reassign a password for the client by using the Explanation: This message logs information to the
UPDATE NODE or UPDATE ADMIN command. activity log about an object that was restored or
retrieved by a user logged in for a node. A user ID
with no value indicates that an administrative or root
user on the platform initiated the restore.
platform) - invalid policy binding System action: Server operation continues.
specified.
Explanation: The server ends a database update
transaction for the specified session because an invalid
ANR0505E The database manager encountered a
management class has been specified for a file or
null value for column name during the
directory object.
data fetching.
System action: The specified session is ended and
Explanation: The server received an unexpected data
value.
System action: The server cannot process the
command.
service representative. User response: Before reissuing the command, try the
following actions:
ANR0502E Transaction failed for session session v Reboot the system.
number for node node name (client v Check that the directories for dbdir, log, or devices
platform) - A storage pool for the target exists and that the file system is mounted (if it is on
destination is associated with a device a separate file system).
class that has a Centera device type. v Make sure that the hardware and network
Explanation: The server ends a database update connection are working properly.
transaction for the specified session because an invalid v Fix any errors in the system log or db2diag.log.
management class has been specified. Centera device
types may be used only for archive objects.
ANR0506I A full backup has been started for
System action: The specified session is ended and database DB Alias. This backup is
server operation continues. required.
User response: Ensure that Centera device types are Explanation: This level of the Tivoli Storage Manager
associated with device classes that are used only for server uses a new version of the database manager that
archive operations. The UPDATE COPYGRP command has a new format for log files. Database backups

ANR0507E ANR0516E
created prior to this level of the server cannot be used

ANR0511I Session session number opened output
to restore the database. A new database backup image
volume volume name.
is needed to ensure that the database is protected.
Explanation: The indicated session has opened the
System action: A full database backup is started.
specified volume for output processing.
ANR0507E Protocol error on session session number
for node client node name (client platform)
because an owner was not properly ANR0512I Process process number opened input
provided for the indicated node. volume volume name.
Explanation: The session does not adhere to the Explanation: The indicated process has opened the
client-server exchange sequence, therefore the server specified volume for input processing. You may or may
detected a protocol error on the specified session. not see an associated ANR0515I message for this
process/volume combination, since some volumes are
shared between multiple processes.
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 User response: None.
the client in a non-standard environment.
ANR0513I Process process number opened output
ANR0508E An automatic full database backup for volume volume name.
database DB Alias has failed.
Explanation: The indicated process has opened the
Explanation: A full database backup failed. This specified volume for output processing. You may not
message always accompanies one or more other see an associated ANR0515I message for this
message that provides more details about the error. process/volume combination, since some volumes are
shared between multiple processes.
System action: The server operation continues.
User response: Examine the server messages that were
issued prior to this message to determine the source of User response: None.
the error. Issue the QUERY ACTLOG command to view
the activity log and search for messages.
ANR0514I Session session number closed volume
volume name.
ANR0509E The database restore failed on DB Alias
Explanation: The indicated session has finished using
due to the log format differences
the specified volume.
between database manager versions.
Explanation: The database restore failed because the
backup image was produced by a previous version of User response: None.
the database manager.
System action: The database restore terminates. ANR0515I Process process number closed volume
volume name.
User response: If you need to restore the database
immediately, uninstall the upgraded server, re-install Explanation: The indicated process has finished using
the previous version of the server, then run the restore the specified volume. It is possible that the process
command. Otherwise, start the upgraded server. The indicated was not the process that opened the volume.
upgraded server creates a new backup image
automatically. After the database backup completes, run System action: Processing continues.
the server restore utility again. User response: None.
ANR0510I Session session number opened input ANR0516E SQL processing for statement statement
volume volume name. failed.
Explanation: The indicated session has opened the Explanation: The indicated select statement failed. The
specified volume for input processing. failure was caused by a syntax error with the statement
System action: Processing continues. itself.
User response: None. System action: The select statement failed.

ANR0517E ANR0522W
User response: Review the server activity log for

message ANR0162W for an explanation of the error
that caused this statement to fail.
platform) - storage pool pool name is not
defined.
ANR0517E command: The DEDUPLICATION
Explanation: The server rolls back a database update
parameter cannot be used with either
transaction for the specified session because the
the TYPE=SERVER or TYPE=NAS
destination specified for a management class copy
parameter.
group specifies the named storage pool, but that
System action: The command failed. storage pool does not exist.
User response: Reissue the command without the System action: Server operation continues.
DEDUPLICATION parameter.
User response: An administrator with policy authority
over the client policy domain must correct management
ANR0518W NDMP restore failed for session session class definitions so that copy group destinations refer
number for node node name (client to defined storage pools, or the specified storage pool
platform), file space filespace. must be created by an authorized administrator.
Explanation: The server ends a restore operation for

the specified NAS node because an error has been ANR0521W Transaction failed for session session
encountered on the server. Some common reasons for number for node node name (client
the error are: platform) - object excluded by size in
v The input volume is unavailable storage pool pool name and all successor
pools.
v The storage pool is unavailable
v Data is corrupted on the input volume Explanation: The server ends a database update
transaction for the specified session because the size of
v Hardware or media failure has occurred a file sent from the client node is larger than that
v The server database is corrupted allowed in the storage pool specified in the clients
management class copy group. No successor storage
System action: The server ends the restore operation.
pools to the one specified on the copy group can accept
User response: Examine any prior error messages to the large file.
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
the restore again. You can also refer to the Problem User response: If the client is not using compression
Determination Guide for problem determination hints to send files to the host, turn compression on for the
and information. If the data is also backed up in a copy client (using the UPDATE NODE command) to try and
storage pool, the retry operation will attempt to read resolve the problem. Otherwise, the maximum file size
the file from the alternate location. If retry of the for one or more of the storage pools in the storage
restore operation continues to fail contact your service hierarchy can be increased to accommodate the file. An
representative. authorized administrator can increase the MAXSIZE
parameter by issuing the UPDATE STGPOOL
command.
ANR0519E A retrieve or restore operation failed for
session session number for node node name
(client platform). An invalid partial object ANR0522W Transaction failed for session session
request was received. number for node node name (client
platform) - no space available in storage
Explanation: The server ended a file retrieve or restore
pool pool name and all successor pools.
operation for the specified session because an invalid
value for the offset, length, or both was received from Explanation: The server ends a database update
the client application for the object being retrieved or transaction for the specified session because the storage
restored. pool specified in the clients management class copy
group does not contain enough free space to hold the
System action: The server ends the specified operation
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: Specify an offset, length, or both free space.
within the bounds of the object to be retrieved or
restored, and rerun the application.
User response: An authorized administrator can issue
the DEFINE VOLUME command to add storage to one

ANR0523W ANR0529W
or more storage pools in the storage hierarchy. This

ANR0526W A transaction failed for session session
action may also involve creating storage space by using
an operating system specific utility.
platform) because of insufficient recovery
log space.
platform) - error on output storage
device.
transaction for the specified client because an I/O error
has been encountered by the server in writing to a User response: Monitor archive logs and active logs. If
device. the recovery log space is insufficient, monitor the
User response: Query the activity log to find messages the archive log directory. If the archive log space is not
preceding this one that specify the failing device. full and the active log space is full or nearly full,
Storage pool volumes can be varied offline (by using update the value of the ACTIVELOGSIZE option in the
the VARY command), or the server may need to be dsmserv.opt file. Set the value of the ACTIVELOGSIZE
halted to correct the hardware problem. After the option to the new maximum size of the active log.
problem is corrected, the client should retry the
operation.
ANR0527W A transaction failed for session session
ANR0524W Transaction failed for session session platform) because of insufficient database
number for node node name (client space.
platform) - data transfer interrupted.
Explanation: The database transaction associated with transaction for the specified session because the server
session session number was aborted because data has insufficient database space.
transfer to or from data storage was interrupted by an
System action: The server ends the specified session,
external event.
but server operation continues.
User response: Examine the messages issued prior to DBSPACE command. Add one or more directories to
this message to determine why the data transfer was the database.
interrupted. Attempt the client operation again if the
problem can be resolved.
ANR0525W Transaction failed for session session platform) - thread resource not available.
platform) - storage media inaccessible.
transaction for the specified session because sufficient
Explanation: The server ends a transaction for the memory is not available for starting additional
specified session because storage volumes are not processes on the server.
available in the storage pools in which the clients files
System action: The server ends the specified session
are to be stored.
User response: An authorized administrator can issue application.
or more storage pools in the storage hierarchy. The
VARY ONLINE command can be used to vary offline
storage volumes online in the storage hierarchy to
platform) - insufficient memory.
make them available to client nodes for file storage.
transaction for the specified session because sufficient
memory is not available on the server.

ANR0530W ANR0534W

number - compression method used by
User response: See the documentation for the client not supported. Please obtain the
operating system about how to increase memory for an latest level of the client code.
application.
Explanation: The server ends the transaction for the
specified session because the compression method that
ANR0530W Transaction failed for session session is used by the client is no longer supported by the
number for node node name (client server.
platform) - internal server error detected.
Explanation: The server ends a database update and server operation continues.
transaction for the specified session because an internal
User response: The client must either backup the data
logic error is detected.
with compression turned off, or upgrade to a client that
System action: The server ends the specified session supports the newer compression method. If the client is
and server operation continues. a WDSF client, upgrade to a non-WDSF client in order
to use the compression performed by the client.
issued prior to this message to determine the source of
the error. Issue the QUERY ACTLOG command to view ANR0534W Transaction failed for session session
the activity log and search for messages that indicate number for node node name (client
the source of the error. platform) - size estimate exceeded and
server is unable to obtain additional
space in storage pool pool name.
number for node node name (client Explanation: The server ends a database update
platform) - invalid file space identifier transaction for the specified session because the size
specified by client. estimate provided by the client is too small. The server
has attempted to obtain additional space in the
Explanation: The server ends a database update indicated storage pool, but was unable to do so.
transaction for the specified session because the file
space identified by the client for the transaction does System action: The specified session is ended and
not exist. server operation continues. If pool name is a random
access storage pool with caching enabled, it is also
System action: This action usually occurs when a possible that additional space can be made available in
client is operating on a file space that is currently being this storage pool by eliminating cached files. When the
deleted as a result of an administrative command or server allocates space based on the size estimate
client action. The server ends the specified session and provided by the client, it frees space occupied by
server operation continues. cached files if this space is needed to obtain the
User response: Use the QUERY PROCESS command estimated space. However, if the server later determines
to monitor and wait for any file space deletion that the file size estimate was too low, it attempts to
processes to complete, or cancel the process if you do obtain additional space that is not utilized, but does not
not want to delete the file space. Try the client action delete cached files to do so. If the client sending the
again after this action has been taken. data has the option COMPRESSALWAYS YES set, it is
possible that a file grew during the compression
operation and when the client sent it to the server it
ANR0532W Diagnostic(ID): Transaction transaction ID exceeded the space available in storage pool pool name.
was aborted for session session number
for node node name (client platform). User response: This message may indicate that there
is no additional space in pool name. The following are
Explanation: An error has been detected during a possible circumventions:
transaction commit for the specified session. This
message should be preceded by other messages that An authorized administrator can issue the DEFINE
give additional information about the failed transaction. VOLUME command to add storage to this pool.
System action: The activity that generated this error If the suspected cause of the failure is that pool name is
fails. a DISK storage pool and that space in use by cached
files was not freed, turn off caching for the storage pool
User response: Check for additional messages and and issue the MOVE DATA command for the volumes
eliminate the condition that caused the failed in pool pool name.
transaction. If the error cannot be isolated and resolved,
contact your service representative. If the suspected cause of the failure is that a file grew
in size during compression on the client, another
possible circumvention is to set the

ANR0535W ANR0541W
COMPRESSALWAYS option in the client options file to User response: Either a server deadlock situation has
NO and retry the operation. This may allow the client occurred or the resource timeout value is set too low.
to accurately report the file size and possibly avoid the Check the setting for the RESOURCETimeout server
out of space condition in the storage pool. option and increase the value. If the problem persists
with a higher timeout then contact your service
representative.
platform) - insufficient mount points ANR0539W Transaction failed for session session
available to satisfy the request. number for node node name. This node
has exceeded its maximum number of
Explanation: The server was unable to allocate
mount points.
sufficient mount points to process the transaction.
Explanation: The server ends the transaction because
System action: The operation is ended and server
the node requires mount points to store data, and
either the node is not allowed to acquire any mount
User response: If necessary, make more mount points points, or the node is already using the maximum
available or validate your device class and library number of mount points allowed for the node. The
configuration. 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
ANR0536W Transaction failed for session session UPDATE NODE command.
platform) - down-level client does not System action: The server ends the specified session
support format of stored files. and server operation continues.
Explanation: A client attempts to perform an User response: If the number of mount points that the
operation involving files that are stored in a format that node is allowed to use on the server are already
is not supported by that client level. acquired, reduce the number of client sessions for the
specified node that are running concurrently. For
System action: The operation is ended and server example, decrease the value of the client option
operation continues. RESOURCEUTILIZATION. If sufficient mount points
User response: Upgrade the client to a later level. (for example, drives) are available to satisfy the data
store operations, issue the UPDATE NODE command
to increase the value of the MAXNUMMP parameter.
ANR0537E Transaction failed for session session
number for node node name (client If the node is not allowed to acquire any mount points
platform) - filespace name cannot be (the node's MAXNUMMP option is set to zero), issue
renamed from or to a Unicode name. the UPDATE NODE command to change the value of
the MAXNUMMP parameter.
transaction for the specified session because a file space
was attempted to be renamed to or from unicode. ANR0540W Retrieve or restore failed for session
System action: The server ends the specified platform) - data integrity error detected.
transaction and server operation continues.
Explanation: The server ends a file retrieval operation
User response: Do not attempt to rename a unicode for the specified session because an internal database
file space to a non-unicode name or a non-unicode file integrity error has been encountered on the server.
space to a unicode name.
and continues operation.
ANR0538I A resource waiter has been aborted.
Explanation: The server aborts a resource wait
because of waiting too long for a resource to become
available. This could cause a process or session to fail. ANR0541W Retrieve or restore failed for session
If this causes a process or a session to fail then there session number for node node name (client
will be other messages at this time indicating which platform) - error on input storage device.
process or session has failed. Resources are internal Explanation: The server ends a client retrieval or
server resources such as locks and synchronization restore operation for the specified session because an
objects. I/O error has been encountered by the server in
System action: The server terminates the resource reading from a device.
with request and server operation continues. System action: The server ends the specified session
ANR0542W ANR0548W
User response: Query the activity log to find messages

ANR0545W Retrieve or restore failed for session
preceding this one that specify the device that is failing.
Storage pool volumes can be varied offline (by using
platform) - insufficient memory.
the VARY OFFLINE command), or the server may need
to be shut down by using the HALT command to Explanation: The server ends a file retrieval or restore
correct the hardware problem. After the problem is operation for the specified session because sufficient
corrected, the client may try the operation again. memory is not available on the server.
ANR0542W Retrieve or restore failed for session and server operation continues.
platform) - storage media inaccessible.
Explanation: The server ends a client retrieval or application.
restore operation for the specified session because a
needed storage pool volume has been varied offline or
the storage pool is unavailable.
System action: The server ends the specified session platform) - internal server error detected.
Explanation: The server ends a file retrieval or restore
User response: Use the VARY ONLINE command to operation for the specified session because an internal
vary offline storage volumes online in the storage logic error is detected in the server program.
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
mode is UNAVAILABLE, use the UPDATE STGPOOL User response: Examine the server messages issued
command to update it to READONLY or READWRITE. prior to this message to determine the source of the
error. Use the QUERY ACTLOG command to view the
activity log and search for messages. If the error cannot
be isolated and resolved, contact your service
representative.
platform) - data transfer interrupted.
Explanation: The database transaction associated with
ANR0547E Invalid data was encountered in the
session session number was aborted because data
command processor output stream:
output formatting terminated for the last
external event.
command entered.
Explanation: The server console session encounters an
error in formatting output from a command.
User response: Examine the messages issued prior to
System action: The command output is discarded and
this message to determine why the data transfer was
interrupted. Attempt the client operation again, if the
problem can be resolved. User response: Use the server QUERY command to
determine if the command you entered had the desired
affect in the server. Use the QUERY ACTLOG
command to see if a server error condition (like out of
memory) occurred prior to the command. Resolve the
platform) - thread resource not available.
error if it is found. Contact your service representative
Explanation: The server ends a file retrieval or restore if you cannot resolve the error, or if an error is not
operation for the specified session because sufficient found.
memory is not available for starting additional
processes on the server.
System action: The server ends the specified session session number for node node name (client
and server operation continues. platform) processing file space filespace
filespace id for file file name stored as
storage repository - error detected.
application. Explanation: The server ends a file retrieval operation
for the specified session because an error has been
encountered on the server. Some common reasons for
the error are:

ANR0549W ANR0554E
v The input volume is unavailable

ANR0551E The client operation failed for session
v The storage pool is unavailable session number for node node name (client
v Data is corrupted on the input volume platform) - lock conflict.
v Hardware or media failure has occurred Explanation: An operation that requires the server to
v Database corruption lock a system resource has been initiated. The operation
cannot be executed because the resource is already in
System action: The server ends the specified session use by another command or process.
System action: The server does not process the
User response: Try the restore or retrieve operation command.
again, and if the file is also backed up in a copy storage
pool, the operation will attempt to read the file from User response: Try the command again at a later time.
the alternate location. If retry of the restore or retrieve
operation continues to fail examine any prior error
ANR0552E Client operation failed for session
messages to determine the source of the error. Use the
QUERY ACTLOG command to view the activity log
platform) - destination storage pool
and search for messages if needed. Correct the problem
storage pool was skipped.
and try the restore or retrieve again. You can also refer
to the Problem Determination Guide for problem Explanation: The indicated client operation failed
determination hints and information. If retry of the because the destination storage pool was skipped. A
restore or retrieve operation continues to fail contact storage pool may be skipped because it does not have
your service representative. enough available space, or because it has a MAXSIZE
value that is less than the size of the object to be
inserted.
number for node node name (client System action: The operation fails.
platform) - no existing restore session
User response: Ensure that the destination storage
found.
pool is available, has an adequate MAXSIZE setting,
Explanation: A client attempted to start an additional and has adequate space. The MAXSIZE setting may be
no query restore session to increase restore throughput, changed using the UPDATE STGPOOL command.
but the original restore session was not found. 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
are offline, use the VARY ONLINE command to vary
User response: Check the status of the original restore. them online and make them available for use. Correct
It may have already completed or been cancelled. The the problem and try the command again.
QUERY SESSION command and the QUERY RESTORE
commands can provide information about existing
ANR0553E Client operation failed for session
sessions and restore sessions which are restartable.
session number - administrator
administrator name does not have
ANR0550E The client operation failed for session adequate authority over node node name.
Explanation: The specified administrator does not
platform) - see previous error messages.
have the proper authority necessary to perform this
Explanation: The indicated operation has failed. This operation on the specified node.
message is always preceded by one or more other error
System action: The server does not perform the query.
messages which provide more detail about why the
command failed. User response: Issue the command from a properly
authorized administrator ID, or contact the system
administrator to have additional authority granted to
the current administrator ID.
User response: Examine the previous error messages
to determine the source of the error. Use the QUERY
ANR0554E command name: The parameter name
parameter is only valid if the
for messages if needed. Correct the problem and try the
TOSERVER parameter is specified.
command again.
Explanation: The command failed because the
TOSERVER parameter was not specified.
System action: The command fails and server
ANR0555E ANR0562I
User response: Reissue the command and specify the User response: Verify that both nodes were imported
TOSERVER parameter. For information on valid values properly and issue the import command again. Or, use
for the command parameter,refer to the Administrators the GRANT PROXYNODE command to manually
Reference for your particular platform. create the proxynode association.
ANR0555E command name: The parameter name ANR0559E Too many domains are specified on the
parameter cannot be specified when the EXPORT NODE command.
TOSERVER parameter is specified.
Explanation: The maximum length of the domain list
Explanation: The command failed because the cannot exceed approximately 1400 characters.
TOSERVER parameter was not specified.
System action: The EXPORT command is ended.
User response: If you specified DOMAIN=* on the
command, issue the command again without specifying
User response: Reissue the command and omit the the domain to let it default to all domains. If you
TOSERVER parameter. For information on valid values specified a domain list, then split up the EXPORT into
for the parameter for the command parameter, refer to multiple export commands to reduce the number of
the Administrators Reference for your particular domains specified on the command.
platform.
ANR0560E Import command: Unable to decrypt
ANR0556E command name: DATES=RELATIVE encrypted password or key.
parameter value cannot be specified
Explanation: The server is not able to decrypt the
when merging imported files using the
password associated with a node or administrator, or
MERGE=YES parameter value.
the client encryption key associated with an object
Explanation: When importing files and merging them being imported. The password or key was encrypted
into existing file spaces, the DATES=RELATIVE with the AES encryption standard, but the server does
parameter value cannot be specified. not support AES.
System action: The command fails and server System action: The object is not imported.
User response: Rerun the export command, specifying
User response: Reissue the command and omit the the ENCryptionstrength=DES option. Or, rerun the
DATES=RELATIVE parameter. For information on valid import on a server that supports AES.
values for the parameter for the command, refer to the
Administrators Reference for your particular platform.
ANR0561E Export command: Process aborted - sign
on to server, target server name, failed.
ANR0557I Import command: An invalid export
Explanation: The server export process encountered
record (version version, copy type copy
an error in establishing a communication session with
type, object type object type) was found.
the target server.
Explanation: An invalid import record was found for
System action: The export process ends and server
the specified version, copy type and object type. The
object will be skipped, and import processing will
continue. User response: Check the activity log and server
console for messages that indicate a failure or problem
on the server issuing this command and on the target
User response: Issue QUERY ACTLOG to determine server. Next, check the server definition, administrator
the source of the error. name, and password on both the server issuing the
command and the server specified. Also, check the
communication connection between the two servers.
ANR0558W Import processing did not create a
And finally, verify that the target server specified is
proxynode association for nodes
running. If the problem is not resolved, contact your
node_id_target and node_id_agent.
Explanation: Import processing did not create a
proxynode association between the two nodes. The
ANR0562I Export command: Data transfer complete,
association fails if either of the nodes does not exist on
deleting temporary data.
the server, or if import processing was not allowed to
complete. Explanation: The server export process has completed
writing data to the target media or server. Temporary
System action: The server does not create the
specified proxynode association.

ANR0563W ANR0568W
data used during the operation is now being deleted

from the database.
System action: The export process continues until all platform). The storage volume volume
temporary data is removed. name is inaccessible.
User response: None. Explanation: The server ends a client retrieval or

restore operation for the specified session because a
needed storage pool volume has been varied offline.
ANR0563W NDMP restore failed for node node name,
file space filespace. System action: The server ends the specified session
Explanation: The server ends a restore operation for
the specified NAS node because an error has been User response: Use the VARY ONLINE command to
encountered on the server. Some common reasons for vary offline storage volumes online, and make them
the error are: available to client nodes for file storage.
v The storage pool is unavailable ANR0566W Retrieve or restore failed for session
v Data is corrupted on the input volume session number for node node name (client
platform) - file was deleted from data
v Hardware or media failure has occurred storage during retrieval.
v The server database is corrupted
System action: The server ends the restore operation. for the specified session because the file has been
deleted from data storage by another process before
User response: Examine any prior error messages to
retrieval is complete.
ACTLOG command to view the activity log and search System action: The server ends the specified session
for messages if needed. Correct any problem and try and continues operation.
the restore again. You can also refer to the Problem
Determination Guide for problem determination hints User response: Contact your administrator to find out
and information. If the data is also backed up in a copy if DELETE FILESPACE, DELETE VOLUME, or
storage pool, the retry operation will attempt to read inventory expiration processes are running; these
the file from the alternate location. If retry of the processes can delete data storage files during retrieval.
restore operation continues to fail contact your service Reissue the restore or retrieve operation and specify a
representative. different file version.
ANR0564E Restartable restore request failed for ANR0567W Retrieve or restored failed for session
session session number, restartable restore session number for node node name (client
session restore session number - sessions platform) - insufficient mount points
are active from the original restore. available to satisfy the request.
Explanation: A client attempted to restart a restartable Explanation: The server was unable to allocate
no query restore session; However, sessions from the sufficient mount points to process the retrieve or
original no query restore invocation are still active. restore operation.
Both the current and restartable restore session System action: The operation is ended and server
numbers are shown. operation continues.
System action: The restartable restore request is ended User response: If necessary, make more mount points
and server operation continues. The restore's available.
restartability status does not change.
User response: Check the status of the original restore. ANR0568W Session session number for admin admin
The QUERY RESTORE command can be used to show name (client platform) terminated -
the status of restartable restores. The restartable restore connection with client severed.
session number is the one for which sessions were
found to be running. Sessions may be active on either Explanation: The specified admin session is ended
the server or a storage agent. Restartable restores may because the communications link has been closed by a
be cancelled by issuing the CANCEL RESTORE network error or by the client program.
command, after which the restore may be retried. Once System action: Server operation continues.
CANCEL RESTORE is issued for a restore session, it is
not eligible to be restarted. User response: If a user breaks out of a client
program, this message will be displayed on the server
as the connection is suddenly closed by the client. A
ANR0569I ANR0575E

ANR0572E Export command: Invalid value for
displayed. If a large number of these messages occur
DAYOFWEEK parameter detected while
simultaneously, check the network for failure and
exporting administrative schedule
schedule name - default or existing value
is used during import.
ANR0569I Object not processed for node name:
Explanation: During processing of command export
type=type, file space=filespace name,
command, an invalid value is encountered for the
object=object name.
DAYOFWEEK parameter for administrative schedule
Explanation: An error occurred. The object for node schedule name.
name, identified by type, file space and object name was
System action: Export processing continues, but the
not processed.
exported data contains an unknown DAYOFWEEK
System action: Server action is defined by the error value for this schedule. If this data is imported, the
that occurred. server uses the default or existing DAYOFWEEK value.
User response: Issue QUERY ACTLOG to determine User response: Update the DAYOFWEEK value for
the source of the error. this schedule and restart the export command.
Alternatively, use the export data with the unknown
value, and check and update the DAYOFWEEK value
ANR0570E Export command: Invalid value for after import processing has been performed.
DURUNITS parameter detected while
schedule name - default or existing value ANR0573I Export/import command: Processing
is used during import. administrative schedule schedule name.
Explanation: During processing of command export Explanation: The background export or import
command, an invalid value is encountered for the process to service the command export/import command
DURUNITS parameter for administrative schedule is currently processing the schedule definition
schedule name. information for administrative schedule schedule name.
System action: Export processing continues, but the System action: Export or import processing for the
exported data contains an unknown DURUNITS value command continues.
for this schedule. If this data is imported, the server
uses the default or existing DURUNITS value.
User response: Update the DURUNITS value for this
ANR0574E Import command: Invalid value for
schedule and restart the export command. Alternatively,
DURUNITS or PERUNITS parameter in
the export data with the unknown value can be used,
exported data for administrative
and the DURUNITS value can be checked and updated
schedule schedule name.
after import processing has been performed.
Explanation: During preview processing of command
import command, an invalid value is encountered for the
DURUNITS or PERUNITS parameter for administrative
PERUNITS parameter detected while
schedule name - default or existing value System action: Processing of the command continues.
is used during import. If a later command is issued that causes the data to be
imported, the default or existing values are used for
DURATION, DURUNITS, PERIOD, and PERUNITS.
PERUNITS parameter for administrative schedule User response: If the data is imported with a later
schedule name. command, verify that the correct values for
DURATION, DURUNITS, PERIOD, and PERUNITS are
used for this schedule.
exported data will contain an unknown PERUNITS
value for this schedule. If this data is imported, the
server uses the default or existing PERUNITS value. ANR0575E Import command: Invalid value for
DAYOFWEEK parameter in exported
User response: Update the PERUNITS value for this
data for administrative schedule schedule
name.
use the export data with the unknown value, and check
and update the PERUNITS value after import Explanation: During preview processing of command
processing has been performed. import command, an invalid value is encountered for the
DAYOFWEEK parameter for administrative schedule
schedule name.

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

SPACEMGTECHNIQUE parameter in
MIGREQUIRESBKUP parameter in
exported data for management class
exported data for management class
management class name in domain domain
name, set policy set name.
name, set policy set name.
SPACEMGTECHNIQUE parameter for management
class management class name, in policy domain domain
management class name, in policy domain domain name,
name, policy set policy set name.
System action: Processing of the command continues.
If a later command is issued that causes the data to be
If a later command causes the data to be imported, the
imported, the default or existing
default or existing MIGREQUIRESBKUP value is used.
SPACEMGTECHNIQUE value is used.
User response: None. If the data is imported with a
later command, verify that the correct
later command, verify that the correct
MIGREQUIRESBKUP value is used for this
SPACEMGTECHNIQUE value is used for this
management class.
management class.

exported data - management class
exported data - management class
name, set policy set name defined with
name, set policy set name defined with
default MIGREQUIRESBKUP value.
default SPACEMGTECHNIQUE value.
management class name, in policy domain domain name,
class management class name, in policy domain domain
name, policy set policy set name.
by using the default MIGREQUIRESBKUP value for
by using the default SPACEMGTECHNIQUE value for
this management class.
this management class.
MIGREQUIRESBKUP value has been used for this
SPACEMGTECHNIQUE value has been used for this

exported data - MIGREQUIRESBKUP
exported data - SPACEMGTECHNIQUE
value for management class management
value for management class management
class name in domain domain name, set
class name in domain domain name, set
policy set name was not updated.
policy set name was not updated.
MIGREQUIRESBKUP parameter.

ANR0588E ANR0595W
System action: Processing of the command continues, valid FILELIST parameter. For information on valid
by using the existing MIGREQUIRESBKUP value for values for the FILELIST parameter for the command,
this management class. refer to the Administrators Reference for your particular
platform.
MIGREQUIRESBKUP parameter has been used for this
management class. Update this value, if necessary. ANR0592E Export/import command: Invalid value for
table of contents parameter - parameter
value.
ANR0588E Import command: Server is down-level
compared to export data version version Explanation: The value (parameter value) specified for
number. the table of contents (TOC) parameter in command
export/import command is not a valid value for this
Explanation: An attempt is made to import data to a
parameter.
down-level server. The server on which the import is
performed must be at the same or later level than the System action: The command fails and server
server from which the data was exported. operation continues.
System action: The import process ends and server User response: Reissue the command and specify a
operation continues. valid TOC parameter. For information on valid values
for the TOC parameter for the command, refer to the
User response: Import to a server that is at the same
or later level than the server from which the export
was performed.
ANR0593E Export/import command: Invalid value for
NOSPAN parameter - parameter value.
ANR0589E Import command: Preview processing
terminated abnormally - server is Explanation: The value (parameter value) specified for
down-level. the NOSPAN parameter in command export/import
command is not a valid value for this parameter.
Explanation: Processing for the command import
command in preview mode ends when it is determined System action: The command fails and server
that the server is down-level compared to the export operation continues.
data.
User response: Reissue the command and specify a
System action: Import processing ends and server valid NOSPAN parameter. For information on valid
operation continues. values for the NOSPAN parameter for the command,
refer to the Administrators Reference for your particular
platform.
was performed.
ANR0594E device class: NOSPAN parameter can only
be used with a 3590 device class.
ANR0590E Import command: Processing terminated
abnormally - server is down-level. Explanation: The device class specified must be a 3590
device class when NOSPAN is set to True.
Explanation: Processing for the command import
command ends when it is determined that the server is System action: The command fails and server
down-level compared to the export data. operation continues.
System action: Import processing ends and server User response: Reissue the command and specify a
operation continues. valid NOSPAN/Device Class parameter. For
information on valid values for the NOSPAN parameter
for the command, refer to the Administrators Reference
for your particular platform.
was performed.
ANR0595W The server deleted object count objects

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

ANR0604I ANR0613I

ANR0609I Command started as process process ID.
Explanation: A background process has been started
ANR0604I Export command: No schedules were
to service the command command. The background
found in policy domain domain name for
process is defined as process process ID.
exporting.
find any schedules defined for policy domains User response: To query the progress of the
matching domain name. background process, use the QUERY PROCESS
command. To cancel the background process, use the
System action: The export process continues and no
CANCEL PROCESS command. Use the process ID
schedules are exported for the domain.
number to specify this specific process.
ANR0610I Command started by administrator name as
ANR0605I Export command: No schedule process process ID.
associations were found in policy
Explanation: A background process has started to
domain domain name for exporting.
service the command command entered by administrator
Explanation: The background export process does not administrator name. The background process is defined
find any schedule node associations defined for policy as process process ID.
domains matching domain name.
System action: The export process continues and no
User response: To query the progress of the
schedule associations are exported for the domain.
background process, use the QUERY PROCESS
User response: None. command. To cancel the background process, use the
number to specify this specific process.
ANR0606I Export command: No node definitions
were found for exporting.
ANR0611I Command started by administrator name as
Explanation: The background export process does not process process ID has ended.
find any node definitions to export as specified in the
command export command. Explanation: The background process to service the
command command by administrator administrator name
System action: The export process continues. has completed processing.
User response: None. System action: The specified process ends, and server
ANR0607I Export command: No administrator User response: None.
definitions were found for exporting.
Explanation: The background export process does not ANR0612I Import command: Reading EXPORT
find any administrator definitions to export as specified SERVER data from server server name
in the command export command. exported export date export time.
System action: The export process continues. Explanation: The background import process to
User response: None. service the command import command is importing
information exported from server server name with the
EXPORT SERVER command on export date at export
ANR0608I Export command: No file spaces were time.
found for exporting.
System action: Import processing continues.
find any file space definitions to export as specified in User response: None.
the command export command.
System action: The export process continues. ANR0613I Import command: Reading EXPORT
POLICY data from server server name
User response: None. exported export date export time.
Explanation: The background import process to
service the command import command is importing
ANR0614I ANR0621I
EXPORT POLICY command on export date at export User response: None.

time.
System action: Import processing continues. ANR0618I Export/import command: Preview
processing canceled before completion.
Explanation: The background export or import
process to service the command export/import command
ANR0614I Import command: Reading EXPORT
in preview (Preview=Yes) mode has been canceled with
ADMIN data from server server name
the CANCEL PROCESS command.
exported export date export time.
System action: Export or import processing for the
command ends. Statistics on the projected number and
type of objects moved, together with the projected total
number of bytes copied, are displayed on the server
EXPORT ADMIN command on export date at export
console following this message.
time.
System action: Import processing continues.
ANR0619I Command: Processing canceled before
completion.
ANR0615I Import command: Reading EXPORT
Explanation: The background process to service the
NODE data from server server name
command command has been canceled with the
exported export date export time.
CANCEL PROCESS command.
System action: Processing for the command command
ends. Statistics on the number and type of objects
moved, together with the total number of bytes copied,
EXPORT NODE command on export date at export time.
are displayed on the server console following this
System action: Import processing continues. message.
ANR0616I Export/import command: Preview ANR0620I Export/import command: Copied number

processing completed successfully. domain(s).
Explanation: The background export or import Explanation: The background export or import
process to service the command export/import command process to service the command export/import command
in preview (Preview=Yes) mode has completed copies number policy domain definitions from the
successfully. server database to export media or from export media
into the server database. Data is not actually moved if
System action: Export or import processing for the Preview=Yes is specified in the command export/import
command completes. Statistics on the projected number command.
and type of objects moved, together with the projected
total number of bytes copied, are displayed on the System action: Export or import processing for the
server console following this message. command completes. Server operation continues.
ANR0617I Export/import command: Processing ANR0621I Export/import command: Copied number

completed with status status. policy sets.
has completed with status status. If the status is copies number policy set definitions from the server
INCOMPLETE, some files have been skipped due to database to export media or from export media into the
errors reading or writing the file. server database. Data is not actually moved if
Preview=Yes is specified in the command export/import
System action: Export or import processing for the command.
command completes. Statistics on the number and type
of objects moved, together with the total number of System action: Export or import processing for the
bytes copied, are displayed on the server console command completes. Server operation continues.
following this message. A summary of the number of
files that were skipped is also displayed.

ANR0622I ANR0630I
ANR0622I Export/import command: Copied number ANR0626I Export/import command: Copied number
management classes. node definitions.
copies number management class definitions from the copies number client node definitions from the server
server database to export media or from export media database to export media or from export media into the
into the server database. Data is not moved if server database. Data is not moved if Preview=Yes is
Preview=Yes is specified in the command export/import specified in the command export/import command.
command.
System action: Export or import processing for the command completes. Server operation continues.
command completes. Server operation continues.
ANR0627I Export/import command: Copied filespace
ANR0623I Export/import command: Copied number number file spaces archive number archive
copy groups. files, backup number backup files, and
spacemg number space managed files.
process to service the command export/import command Explanation: The background export or import
copies number copy group definitions from either the process to service the command export/import command
server database to export media or from export media copies filespace number client file space definitions,
into the server database. Data is not moved if archive number archive file copies, backup number backup
Preview=Yes is specified in the command export/import file copies, and spacemg number space-managed files
command. from either the server database to export media or from
import media into the server database. Data is not
actually moved if Preview=Yes is specified in the
command export/import command.
ANR0624I Export/import command: Copied number
schedules.
bytes of data.
copies number schedule definitions from either the
server database to export media or from export media Explanation: The background export or import
into the server database. Data is not moved if process to service the command export/import command
Preview=Yes is specified in the command export/import copies number bytes of data from the server database
command. and data storage to the export media or from the
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
User response: None. used during export preview processing to estimate the
number of removable media volumes needed to hold
the exported information from the server.
administrators. System action: Export or import processing for the
process to service the command export/import command User response: None.
copies number administrator definitions from either the
server database to export media or from export media
into the server database. Data is not moved if
kilobytes of data.
command. Explanation: The background export or import
copies number kilobytes 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
storage. This figure can be used during export preview
processing to estimate the number of removable media
ANR0631I ANR0637I
volumes needed to hold the exported information from

ANR0634I Export/import command: Detected number
the server.
errors.
User response: None. detects number errors while copying information from
the server database and data storage to the export
media or from the export media to the server database
ANR0631I Export/import command: Copied number and data storage.
megabytes of data.
Explanation: The background export or import command completes. Server operation continues.
copies number megabytes of data from the server User response: Examine the server messages issued
database and data storage to the export media or from prior to this message to view the error. Use the QUERY
the export media to the server database and data ACTLOG command to view the activity log and search
storage. This figure can be used during export preview for messages.
volumes needed to hold the exported information from
ANR0635I Export/import command: Processing node
the server.
node name in domain domain name.
User response: None. is currently processing the client node definition
information for node node name. The node will be
imported to domain domain name.
gigabytes of data. System action: Export or import processing for the
command continues.
process to service the command export/import command User response: None.
copies number gigabytes of data from the server
ANR0636I Import command: Processing file space
the export media to the server database and data
filespace name for node node name as file
space new filespace name.
volumes needed to hold the exported information from Explanation: The background import process to
the server. service the command import command is currently
processing the client file space definition information
for file space filespace name belonging to client node
node name. The file space is imported under the name
User response: None. new filespace name. During import processing, file spaces
defined for clients are not replaced, and file copy
information in the file spaces are imported to new file
ANR0633I Export/import command: Copied number space names so that client file copies are not mixed
terabytes of data. with existing definitions. Import processing can then
Explanation: The background export or import create file spaces with names generated by the import
process to service the command export/import command processor for client nodes that existed prior to the
copies number terabytes of data from the server import operation.
database and data storage to the export media or from System action: Import processing for the command
the export media to the server database and data continues.
processing to estimate the number of removable media User response: None; however, clients may want to
volumes needed to hold the exported information from examine the contents of the file space with the name
the server. new filespace name so that they know where certain file
copies are kept.
ANR0637I Export/import command: Processing file
User response: None. space filespace name for node node name
fsId filespace id .

ANR0638I ANR0645I
is currently processing client node file space

ANR0642I Export/import command: Processing
information for file space filespace name belonging to
backup copy group in domain domain
client node node name.
name, set set name, management class
System action: Export or import processing for the class name.
command continues.
User response: None. process to service the command export/import command
is currently processing the backup copy group
definition information for management class class name
ANR0638I Export/import command: Processing belonging to policy set set name in policy domain
administrator administrator name. domain name.
Explanation: The background export or import System action: Export or import processing for the
process to service the command export/import command command continues.
is currently processing the administrator definition
information for administrator administrator name. User response: None.

command continues. ANR0643I Export/import command: Processing
archive copy group in domain domain
User response: None. name, set set name, management class
class name.
ANR0639I Export/import command: Processing Explanation: The background export process to
domain domain name. service the command export/import command is currently
Explanation: The background export or import processing the archive copy group definition
process to service the command export/import command information for management class class name belonging
is currently processing the policy domain definition to policy set set name in policy domain domain name.
information for domain domain name. System action: Export processing for the command
System action: Export or import processing for the continues.
command continues. User response: None.
ANR0644I Export command: Processing copy group
ANR0640I Export/import command: Processing policy of unknown type in domain domain
set set name in policy domain domain name, set set name, management class
name. class name.
process to service the command export/import command process to service the command export command is
is currently processing the policy set definition currently processing copy group definition information
information for policy set set name belonging to policy for management class class name belonging to policy set
domain domain name. set name in policy domain domain name. The type of
copy group being processed is unknown.
command continues. System action: Export or import processing for the
command continues. The import or export process
User response: None. assumes that the copy group is a backup copy group.
User response: After policy definitions are imported,
ANR0641I Export/import command: Processing use the QUERY MGMTCLASS and QUERY
management class class name in domain COPYGROUP commands to query the server
domain name, set set name. definitions for management class class name to ensure
Explanation: The background export or import that the copy groups defined have the desired
process to service the command export/import command attributes and types. Alternatively, the copy group can
is currently processing the management class definition be deleted and defined with the correct type, and then
information for management class class name belonging the export command can be issued again.
to policy set set name in policy domain domain name.
System action: Export or import processing for the ANR0645I Export/import command: Processing
command continues. schedule schedule name in domain domain
name.
ANR0646I ANR0652W
is currently processing the schedule definition v Domain STANDARD does not exist
information for schedule schedule name belonging to
User response: If Preview=Yes, consider defining
policy domain domain name.
domain domain name before nodes are actually
System action: Export or import processing for the imported. Otherwise, domain domain name can be
command continues. 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

ANR0650W IMPORT: Archive copygroup copy group
Explanation: The background export or import name in management class management
process to service the command export/import command class name for domain domain name is not
has received the message message from the server. defined, default management class will
be used.
command continues, but errors may have been Explanation: During import processing, the server
encountered. finds that a management class or copy group bound to
an archive file being imported does not exist in the
User response: Examine the documentation for the active policy set for the domain to which the node is
message message and resolve the problem reported. assigned.
System action: The default management class for the
ANR0647I Cancel in progress nodes policy domain is bound to the archive file and
Explanation: The export or import operation has been import processing continues.
canceled and will end when resources have been freed User response: If you want to define the missing
for the background process. This message may be management class, an authorized administrator may
displayed in response to a QUERY PROCESS command cancel the import operation, define the missing
for an export or import operation. management class or copy group for the domain, and
System action: Server operation continues. process the import operation again.

ANR0651W IMPORT: Backup copygroup copy group
name in management class management
ANR0648I Have copied the following: class name for domain domain name is not
Explanation: The export or import operation has defined, default management class will
copied the number and types of objects displayed. This be used.
message may be displayed in response to a QUERY Explanation: During import processing, the server
PROCESS command for an export or import operation. finds that a management class or copy group bound to
System action: Server operation continues. a backup file being imported does not exist in the
active policy set for the domain to which the node is
User response: None. assigned.
System action: The default management class for the
ANR0649I Import command: Domain domain name nodes policy domain is bound to the backup file copy
does not exist - the system will attempt and import processing continues.
to import node node name to domain
STANDARD. User response: If you want to define the missing
management class, an authorized administrator may
Explanation: The background import process to cancel the import operation, define the missing
service the command import command is currently management class or copy group for the domain, and
processing client node node name. This node was process the import operation again.
assigned to domain domain name at the time of export.
However, domain domain name does not exist on the
server to which the import is being performed. ANR0652W IMPORT: Archive copygroup not found
for default management class in domain
System action: Import processing continues, but node domain name - archive files bound to
node name will be assigned to domain STANDARD management class management class name
during import unless one of the following conditions in this domain cannot be imported.
exist:
v Preview=Yes
finds that a management class or copy group bound to
v Node node name is already registered and an archive file being imported does not exist in the
Replacedefs=No active policy set for the domain to which the node is

ANR0653W ANR0658W
assigned. When trying to rebind the archive file to the System action: The server ends the command and
default management class for the domain, the server continues operation.
finds that an archive copy group is not defined for the
User response: Contact your administrator to find out
default management class.
if DELETE FILESPACE, DELETE VOLUME, or
System action: The file is not imported; import inventory expiration processes are running; these
processing continues. processes can delete data storage files during retrieval.
Reissue the command after these processes have been
User response: If you want to define the missing copy
completed or canceled.
group, an authorized administrator may cancel the
import operation, define the missing management class
or copy group for the domain, and process the import ANR0656W Export/import command: Skipped archive
operation again. number archive files, backup number
backup files, and spacemg number space
managed files.
ANR0653W IMPORT: Backup copygroup not found
for default management class in domain Explanation: The background export or import
domain name - backup files bound to process to service the command export/import command
management class management class name skipped archive number archive file copies, backup
in this domain cannot be imported. number backup file copies, and spacemg number
space-managed files from either the server database to
export media or from import media into the server
finds that a management class or copy group bound to
database. Data is not actually moved if Preview=Yes is
a backup file being imported does not exist in the
specified in the command export/import command.
active policy set for the domain to which the node is
assigned. When trying to rebind the backup file to the System action: Export or import processing for the
default management class for the domain, the server command completes. Server operation continues.
finds that a backup copy group is not defined for the
User response: Check previous messages for the
default management class.
names of the files that were not exported or imported,
System action: The file is not imported; import and problem determination information.
processing continues.
User response: If you want to define the missing copy ANR0657W Export command: Invalid authorization
group, an authorized administrator may cancel the rule type rule type encountered for file
import operation, define the missing management class space filespace name fsId filespace id in
or copy group for the domain, and process the import node node name - both backup and
operation again. archive will be assumed during import.
ANR0654I Restartable export command with export encounters an invalid file space authorization rule type
identifier exportID started as process for the indicated file space and node.
process ID.
User response: After import processing is completed,
service the command command. The background
ask the user of node node name to query the access rules
and ensure that they are specified as desired. The user
System action: Server operation continues. should correct any rules that grant access to objects that
the user does not want others to access.
background server-to-server export process, issue the
QUERY PROCESS or QUERY EXPORT command. To ANR0658W Export command: The password for
suspend the process, issue the SUSPEND EXPORT administrator administrator name could
command. To cancel the background process, issue the not be obtained. The value 'password
CANCEL PROCESS command. Use the process ID value' will be assumed: The system
number to specify this specific process. administrator may wish to change this
password after importing administrator
administrator name.
ANR0655W Command: Retrieve or restore failed - file
was deleted from data storage during Explanation: During processing of command export
retrieval. command, the export processor cannot obtain the
password for administrator administrator name. The
value password value is assigned as the password for the
for the specified command because the file has been
administrator on the export media.
retrieval is complete. System action: Processing of the command continues.
ANR0659W ANR0665W
User response: After the administrative definition has writing to a device. Possible reasons include:
been imported to another server, an authorized v I/O error writing to a device
administrator should use the UPDATE ADMIN
v No storage space.
command to set a password for the administrator
administrator name. v Incompatible storage pool data format.
System action: The command command operation ends
ANR0659W Export command: The password for node and server operation continues.
node name could not be obtained. The User response: Query the activity log to find messages
value 'password value' will be assumed: preceding this one to determine the cause of the error.
The system administrator may wish to After the problem is corrected, the command can be
change this password after importing retried.
node node name.
Explanation: During processing of command export ANR0663E Command: Data transfer was interrupted
command, the export processor cannot obtain the in accessing data storage.
password for client node node name. The value password
value is assigned as the password for the client node on Explanation: The database transaction associated with
the export media. command command operation failed because data
System action: Processing of the command continues. external event.
User response: After the client node definition has System action: The command command operation is
been imported to another server, an authorized ended and server operation continues.
administrator should use the UPDATE NODE
command to set a password for the node node name. User response: Examine the messages issued prior to
interrupted. Reissue the command command after the
ANR0660E Command: Insufficient memory available problem is resolved.
in accessing data storage.
Explanation: The server encounters a memory ANR0664E Export/import command: Media not
shortage in accessing data storage during command accessible in accessing data storage.
command operation.
Explanation: The server ends a transaction for an
System action: The command command operation ends export or import operation because storage volumes are
and server operation continues. not available in the storage pools in which the client
User response: See the documentation for the files are to be stored.
operating system about how to increase memory for an System action: The server ends the export or import
application. operation and server operation continues.
ANR0661E Command: Internal error encountered in the DEFINE VOLUME command to add storage to one
accessing data storage. or more storage pools in the storage hierarchy. The
Explanation: The server encounters an internal error VARY ONLINE command can be used to vary offline
in accessing data storage while processing command storage volumes online in the storage hierarchy to
command operation. make them available for file storage.
System action: The command command operation is

ended and server operation continues. ANR0665W Import command: Transaction failed -
storage pool pool name is not defined.
User response: Use the QUERY ACTLOG command to
examine messages prior to this error to determine the Explanation: The server rolls back a database update
cause of the data storage failure. If the failure can be transaction for an import operation because the
found and resolved, reissue the command command destination specified for a management class copy
operation. If the failure cannot be found, contact your group specifies the named storage pool, but that
service representative for assistance in resolving the storage pool does not exist.
problem. System action: The import operation is ended and
ANR0662E Command: Output error encountered in User response: An administrator with policy authority
accessing data storage. over the client policy domain must correct management
Explanation: The command command operation ends class definitions so that copy group destinations refer
because an error has been encountered by the server in to defined storage pools, or the specified storage pool
must be created by an authorized administrator.

ANR0666W ANR0672W
ANR0666W Import command: Transaction failed - ANR0669W Export/import command: Transaction failed
object excluded by size in storage pool - data transfer interrupted.
pool name and all successor pools.
Explanation: The server ends a database update an export or import operation failed because data
transaction for an import operation because the size of transfer to or from data storage was interrupted by an
an imported file is larger than that allowed in the external event.
storage pool specified in the bound management class
System action: The export or import operation is
copy group for the file. No successor storage pools to
ended and server operation continues.
the one specified on the copy group can accept the
large file. User response: Examine the messages issued prior to
System action: The import operation is ended and
interrupted. Attempt the export/import operation again
after problem is resolved.
User response: The maximum file size for one or more
of the storage pools in the storage hierarchy can be
ANR0670W Export/import command: Transaction failed
increased to accommodate the file. An authorized
- storage media inaccessible.
administrator can increase the MAXSIZE parameter by
issuing the UPDATE STGPOOL command. Explanation: The server ends a transaction for an
Alternatively, the appropriate copygroup definition can export or import operation because storage volumes are
be updated so that a different destination storage pool not available in the storage pools in which the client
is specified. files are to be stored.
System action: The server ends the export or import
ANR0667W Import command: Transaction failed - no operation and server operation continues.
space available in storage pool pool name
and all successor pools. User response: An authorized administrator can issue
Explanation: The server ends an import operation or more storage pools in the storage hierarchy. The
because the storage pool specified in a management VARY ONLINE command can be used to vary offline
class copy group does not contain enough free space to storage volumes online in the storage hierarchy to
hold the files being imported. Successor storage pools make them available for file storage.
to the one specified on the copy group do not contain
enough free space.
ANR0671W Export/import command: Transaction failed
System action: The import operation is ended and - sufficient recovery log space is not
server operation continues. available.
User response: An authorized administrator can issue Explanation: The server ends a database update
the DEFINE VOLUME command to add storage to one transaction for an export or import operation because
or more storage pools in the storage hierarchy. sufficient log space is not available on the server.
ANR0668W Export/import command: Transaction failed operation and server operation continues.
- error on output storage device.
Explanation: The server ends an export or import the DEFINE LOGVOLUME command to add volumes
operation for the specified session because an I/O error for use by the log, and the EXTEND LOG command to
has been encountered by the server in writing to a extend the size of the log so that the new volumes are
device. used.
operation and server operation continues. ANR0672W Export/import command: Transaction failed
- sufficient database space is not
available.
preceding this one that specify the device that is failing.
Storage pool volumes can be varied offline (by using Explanation: The server ends a database update
the VARY OFFLINE command), or the server may need transaction for an export or import operation because
to be shut down by using the HALT command to sufficient database space is not available on the server.
correct the hardware problem. After the problem is
corrected, the client may be able to try the operation System action: The server ends the export or import
again. operation and server operation continues.
the DEFINE DBVOLUME command to add volumes
ANR0673W ANR0681E
for use by the database, and the EXTEND DB

ANR0676E EXPORT/IMPORT: Invalid
command to extend the size of the log so that the new
Communications Buffer State in SEND.
volumes are used.
Explanation: The server export/import process
encounters a communications error in transferring
ANR0673W Export/import command: Data storage
information to or from the server.
retrieve or restore failed - error detected.
System action: The export or import process ends and
Explanation: The server ends an export or import
operation because an error has been encountered on the
server. Some common reasons for the error are: User response: Contact your service representative.
v The storage pool is unavailable ANR0677E EXPORT/IMPORT: Invalid
v Data is corrupted on the input volume Communications Buffer State in
RECEIVE.
v Hardware or media failure has occurred
v Database corruption Explanation: The server export/import process
encounters a communications error in transferring
System action: The server ends the export or import information to or from the server.
operation and continues operation.
User response: Examine any prior error messages to server operation continues.
ACTLOG command to view the activity log and search User response: Contact your service representative.
restore or retrieve again. You can also refer to the ANR0678E EXPORT/IMPORT: Communications
Problem Determination Guide for problem determination Failure in Sending "verb type" verb.
hints and information. If retry of the operation
continues to fail contact your service representative. Explanation: The server export/import process
encounters a communications error in using the verb
type verb to transfer information to or from the server.
ANR0674W Export command: Retrieve failed - error
on input storage device. System action: The export or import process ends and
Explanation: The server ends an export operation for
the specified session because an I/O error has been User response: Contact your service representative.
encountered by the server in reading from a device.
The object for which the I/O was issued is reported in ANR0679E EXPORT/IMPORT: Communications
a later message. Failure in Receiving "verb type" verb.
System action: Export processing skips this file, and Explanation: The server export/import process
continues operation. encounters a communications error in using the verb
User response: Query the activity log to find messages type verb to transfer information to or from the server.
preceding this one that specify the device that is failing. System action: The export or import process ends and
Storage pool volumes can be varied offline (by using server operation continues.
the VARY OFFLINE command), or the server may need
to be shut down with the HALT command to correct User response: Contact your service representative.
the hardware problem.
ANR0681E EXPORT/IMPORT: Authentication
ANR0675E EXPORT/IMPORT: Error starting the Failure.
Export/Import Session.
Explanation: The server export/import process is not encounters an authentication error in transferring
able to start the session to export information from the information to or from the server.
server or import information into the server.
System action: The export or import process ends and server operation continues.
application.

ANR0682E ANR0690E
ANR0682E EXPORT/IMPORT: Communications ANR0687E Export/import command: Transaction

Failure in Sending "verb type" verb failure - could not commit database
(command). transaction.
Explanation: The server export/import process Explanation: During processing of command
encounters a communications error in using the verb export/import command, a database transaction cannot be
type verb to issue command command. committed to the server database.
System action: The export or import process ends and System action: Processing of the command ends.
User response: Examine the server messages issued
User response: Contact your service representative. prior to this message to determine the source of the
ANR0683E EXPORT/IMPORT: Receive Buffer
overflow.
representative.
encounters an overflow error in transferring
ANR0688E Export/import command: Transaction
information to or from the server.
failure - commit called when no
System action: The export or import process ends and transaction started.
Explanation: During processing of command
User response: Contact your service representative. export/import command, a database transaction cannot be
started in the server database.
ANR0684E EXPORT/IMPORT: Communications System action: Processing of the command ends.

failure: bad verb received (verb type).
Explanation: The server encounters an invalid prior to this message to determine the source of the
communications verb during export or import error. Use the QUERY ACTLOG command to view the
processing and is not able to continue processing. activity log and search for messages. If the error cannot
System action: The export or import process ends and representative.
User response: Contact your service representative. ANR0689W Import command: Client platform type
(platform type) for imported node node
ANR0685E EXPORT/IMPORT: Internal error: name conflicts with an existing node
Invalid table output handle detected. with the same name - the node will not
be imported.
encounters an internal error in transferring information Explanation: During import processing, the server
to or from the server. encounters an imported node definition that has the
same name as an existing node, but has a different
System action: The export or import process ends and client platform type (for example, OS/2 or AIX).
server operation continues. Because file data may not be compatible across
User response: Contact your service representative. different client platforms, the node is not imported.
System action: Import processing continues, and the
ANR0686E Export/import command: Transaction named node is skipped by import processing.
failure - could not start database User response: If you want to import the named
transaction. node, cancel the import process, rename the existing
Explanation: During processing of command node to a new name by using the RENAME NODE
export/import command, a database transaction cannot be command, and run the import again. After you have
started in the server database. imported the node, use the RENAME NODE command
to set the node names as you desire.
System action: Processing of the command terminates.
User response: Examine the server messages issued ANR0690E Export/import command: Transaction
prior to this message to determine the source of the failure - server aborted the transaction
error. Use the QUERY ACTLOG command to view the (abort code).
be isolated and resolved, contact your service Explanation: During processing of command
representative. export/import command, a database transaction cannot be
ANR0691E ANR0697E
committed in the server database. The reason code abort

ANR0694E Import command: Invalid record format
code is returned.
(format code) detected on import.
System action: Processing of the command ends.
User response: Examine the server messages issued command, an invalid record type is detected when
prior to this message to determine the source of the reading the exported information from the export
error. Use the QUERY ACTLOG command to view the media.
representative. User response: Examine the server messages issued
prior to this message to determine the source of the
ANR0691E Export command: Error abort code writing
export data.
Explanation: During processing of command export representative.
command, an input/output error occurs when writing
the exported information to the export media.
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.
ANR0692E Command: Out of space on sequential
media, scratch media could not be
mounted.
representative.
Explanation: During command command processing,
the process encounters an out-of-space condition
ANR0696E Export command: Output table error
writing to the sequential media. Command command
encountered - 0 columns reported in the
ends when there is no more space on the sequential
table.
media for storing data and SCRATCH=NO has been
specified on command command. Explanation: During processing of command export
command, an unexpected error is detected.
System action: Command command processing ends.
Server processing continues. System action: Processing of the command ends.
User response: Reissue the command and specify User response: Examine the server messages issued
SCRATCH=YES or specify additional volume names on prior to this message to determine the source of the
the command. error. Use the QUERY ACTLOG command to view the
ANR0693E Import command: Error abort code reading
representative.
export data.
ANR0697E Export command: Output table error
command, an input/output error occurs when reading
encountered - not positioned to the first
the exported information from the export media.
column in the 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
representative.

ANR0698E ANR0708E
ANR0698E Export/import command: Invalid value for ANR0705E Export command: The VOLUMENAMES
FILEDATA parameter - parameter value. parameter must be specified when
SCRATCH=NO is specified.
the FILEDATA parameter in command export/import Explanation: The SCRATCH parameter is specified as
command is not a valid value for this parameter. NO for the command export command but the
VOLUMENAMES parameter is not specified. When
scratch volumes are not allowed, the VOLUMENAMES
parameter must be specified to indicate the volumes
User response: Reissue the command and specify a that can be used for the command.
valid FILEDATA parameter. For information on valid
values for the FILEDATA parameter for the command,
platform. User response: Reissue the command and specify a
valid VOLUMENAMES parameter. For information on
valid parameter values for the command, refer to the
ANR0699E Export/import command: Device class
DISK cannot be specified for this
command.
ANR0706E Export command: A device class must be
Explanation: The DEVCLASS value DISK cannot be
specified unless PREVIEW=YES is
specified for the command export/import command.
specified.
Explanation: The DEVCLASS parameter is not
specified in the command export command. Unless
User response: Reissue the command and specify a PREVIEW=YES is specified, a DEVCLASS value must
valid device class. Issue the QUERY DEVCLASS be specified.
command for a list of valid device classes for the
server.
valid device class. Issue the QUERY DEVCLASS
PREVIEW parameter - parameter value.
command for a list of valid device classes for the
Explanation: The value (parameter value) specified for server.
the PREVIEW parameter in command export/import
ANR0707E Export command: The FILESPACE
System action: The command fails and server parameter cannot be specified.
Explanation: The FILESPACE parameter is specified
User response: Reissue the command and specify a for the command export command, but the FILEDATA
valid PREVIEW parameter. For information on valid parameter is specified as NONE, or is not specified and
values for the PREVIEW parameter for the command, defaults to NONE. File spaces are only copied if the
refer to the Administrators Reference for your particular FILEDATA parameter is specified with a value other
platform. than NONE.
ANR0701E Export/import command: Invalid value for operation continues.
SCRATCH parameter - parameter value.
Explanation: The value (parameter value) specified for valid FILEDATA parameter. For information on valid
the SCRATCH parameter in command export/import parameter values for the command, refer to the
command is not a valid value for this parameter. Administrators Reference for your particular platform.

operation continues. ANR0708E Import command: The FILESPACE
parameter cannot be specified unless the
User response: Reissue the command and specify a FILEDATA parameter specifies that files
valid SCRATCH parameter. For information on valid should be imported.
values for the SCRATCH parameter for the command,
refer to the Administrators Reference for your particular Explanation: The FILESPACE parameter is specified
platform. for the command import command, but the FILEDATA
parameter is specified as NONE, or is not specified and
defaults to NONE. File spaces are only copied if the
ANR0709E ANR0716E
FILEDATA parameter is specified with a value other User response: Reissue the command and specify a
than NONE. valid DATES parameter. For information on valid
values for the DATES parameter for the command,
platform.
valid FILEDATA parameter. For information on valid
parameter values for the command, refer to the
REPLACEDEFS parameter - parameter
value.
ANR0709E Command: No matching nodes registered
the REPLACEDEFS parameter in command import
in the specified domains.
Explanation: The DOMAIN parameter has been
specified for this command, but no nodes matching the
node name specification are found in the domains
specified. User response: Reissue the command and specify a
valid REPLACEDEFS parameter. For information on
valid values for the REPLACEDEFS parameter for the
command, refer to the Administrators Reference for your
User response: Reissue the command and specify a particular platform.
valid combination of node and domain names. Use the
QUERY NODE command to view the names of nodes
ANR0714E Import command: The EXTFILE device
in the domains that you are interested in exporting.
class cannot be specified when the
VOLUMENAMES parameter is
ANR0710E Command: Unable to start background specified.
process.
Explanation: An invalid combination of parameters
Explanation: The server command processor is not has been entered for command import command. The
able to start a background process to perform the EXTFILE device class cannot be used in combination
command command. with the VOLUMENAMES parameter.
System action: The command process ends and server System action: The command fails and server
operation continues. operation continues.
User response: See the documentation for the User response: Reissue the command with the correct
operating system about how to increase memory for an syntax.
application.
ANR0715E Import command: A device class must be
ANR0711E Import command: Unable to start import specified.
process.
Explanation: The command import command has been
Explanation: The server import command processor is specified, but does not include specification of the
not able to start a background process to perform the DEVCLASS parameter. The DEVCLASS parameter
import operation. must be specified for this command.
System action: The export or import process ends and System action: The command fails and server
server operation continues. operation continues.
User response: See the documentation for the User response: Reissue the command and specify a
operating system about how to increase memory for an valid device class. For a list of valid device classes for
application. the server, issue the QUERY DEVCLASS command.
ANR0712E Import command: Invalid value for ANR0716E Import command: Invalid export data
DATES parameter - parameter value. detected.
Explanation: The value (parameter value) specified for Explanation: The command import command
the DATES parameter in command import command is encounters invalid data on the export media while
not a valid value for this parameter. trying to import server information.
System action: The command fails and server System action: The command fails and server
operation continues. operation continues.

ANR0717E ANR0723E
User response: Ensure that the mounted export tapes

ANR0720E command: Processing terminated
are in the correct order (mounted in the same order as
abnormally - insufficient memory.
they were mounted during export). Reissue the
command, and mount the tapes in the correct order. If Explanation: Processing for the command ends
the VOLUMENAMES parameter has been specified, because sufficient memory is not available on the
make sure that the volume names in the command are server.
specified in the correct order.
System action: Command processing is ended and
ANR0717E Export/import command: Preview
processing terminated abnormally -
communications send or receive failed.
application.
Explanation: Processing for the command export/import
command in preview mode has been terminated when
an internal communications error is encountered in the
server.
unexpected verb received from server.
System action: Export/import processing is ended
command in preview mode ends when an internal
User response: Examine the server messages issued communications error is encountered in the server.
System action: Export/import processing ends and
be isolated and resolved, contact your service User response: Examine the server messages issued
representative. prior to this message to determine the source of the
ANR0718E Export/import command: Processing
terminated abnormally -
representative.
communications send or receive failed.
command ends when an internal communications error
terminated abnormally - unexpected
is encountered in the server.
verb received from server.
command ends when an internal communications error
User response: Examine the server messages issued is encountered in the server.
representative.
command in preview mode is ended because sufficient
transaction failure.
command in preview mode ends when a database
User response: See the documentation for the transaction error is encountered in the server.
application.
ANR0724E ANR0730E
activity log and search for messages. If the error cannot command in preview mode ends when an internal error
be isolated and resolved, contact your service is encountered in the server.
representative.
terminated abnormally - transaction
failure.
Explanation: Processing for the command export/import activity log and search for messages. If the error cannot
command ends when a database transaction error is be isolated and resolved, contact your service
encountered in the server. representative.
server operation continues. ANR0728E Export/import command: Processing
terminated abnormally - internal error.
prior to this message to determine the source of the Explanation: Processing for the command export/import
error. Use the QUERY ACTLOG command to view the command ends when an internal error is encountered in
activity log and search for messages. If the error cannot the server.
representative.
authentication failure.
Explanation: Processing for the command export/import be isolated and resolved, contact your service
command in preview mode ends when an authentication representative.
error is encountered in the server.
System action: Export/import processing ends and ANR0729E Import command: Syntax error from
server operation continues. command 'server command'.
User response: Examine the server messages issued Explanation: During processing of the command
prior to this message to determine the source of the import command, an internal syntax error is encountered
error. Use the QUERY ACTLOG command to view the in the server.
System action: Import processing continues, but the
indicated command will have no effect.
representative.
terminated abnormally - authentication
activity log and search for messages. After import
failure.
processing is complete, it may be necessary to issue
Explanation: Processing for the command export/import additional commands manually to obtain the necessary
command ends when an authentication error is definitions.
encountered in the server.
System action: Export/import processing ends and ANR0730E Import command: Internal error from
server operation continues. command 'server command'.
User response: Examine the server messages issued Explanation: Processing for the command import
prior to this message to determine the source of the command ends when an internal command error is
error. Use the QUERY ACTLOG command to view the encountered in the server.
System action: Import processing ends and server
representative.
internal error.
Explanation: Processing for the command export/import representative.

ANR0731E ANR0738E
ANR0731E Import command: Invalid value for ANR0735E Import command: Invalid value for
COMPRESSION parameter in exported ARCHDELETE parameter in exported
data for node node name. data - node node name registered with
default ARCHDELETE value.
import command, an invalid value is encountered for the Explanation: During processing of command import
COMPRESSION parameter for node node name. command, an invalid value is encountered for the
ARCHDELETE parameter for node node name.
If a later command causes the data to be imported, the System action: Processing of the command continues,
default or existing COMPRESSION value is used. by using the default ARCHDELETE value for this node.
User response: None. If the data is imported with a User response: Verify that the correct ARCHDELETE
later command, verify that the correct COMPRESSION value has been used for this node. Update this value, if
value is used for this node. necessary.
ARCHDELETE parameter in exported BACKDELETE parameter in exported
data for node node name. data - node node name registered with
default BACKDELETE value.
ARCHDELETE parameter for node node name. command, an invalid value is encountered for the
BACKDELETE parameter for node node name.
default or existing ARCHDELETE value is used. by using the default BACKDELETE value for this node.
User response: None. If the data is imported with a User response: Verify that the correct BACKDELETE
later command, verify that the correct ARCHDELETE value has been used for this node. Update this value, if
value is used for this node. necessary.
BACKDELETE parameter in exported COMPRESSION parameter in exported
data for node node name. data - existing COMPRESSION value
for node node name was not updated.
BACKDELETE parameter for node node name. command, an invalid value is encountered for the
COMPRESSION parameter for node node name.
default or existing BACKDELETE value is used. by using the existing COMPRESSION value for this
node.
later command, verify that the correct BACKDELETE User response: Verify that the correct COMPRESSION
value is used for this node. value has been used for this node. Update this value, if
necessary.
COMPRESSION parameter in exported ANR0738E Import command: Invalid value for
data - node node name registered with ARCHDELETE parameter in exported
default COMPRESSION value. data - existing ARCHDELETE value for
node node name was not updated.
command, an invalid value is encountered for the Explanation: During processing of command import
COMPRESSION parameter for node node name. command, an invalid value is encountered for the
ARCHDELETE 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.
ANR0739E ANR0744E
value has been used for this node. Update this value, if
ANR0742E Import command: Invalid value for TYPE
necessary.
parameter in exported data for copy
group copy group name in domain domain
ANR0739E Import command: Invalid value for name, set policy set name, management
BACKDELETE parameter in exported class management class name - this copy
data - existing BACKDELETE value for group will not be imported.
node node name was not updated.
Explanation: During processing of command import command, an invalid value is encountered for the TYPE
command, an invalid value is encountered for the parameter for copy group copy group, in policy domain
BACKDELETE parameter for node node name. domain name, policy set policy set name, management
class management class name.
by using the existing BACKDELETE value for this System action: Processing of the command continues.
node. However, this copy group is not imported because a
TYPE value cannot be assigned.
User response: Verify that the correct BACKDELETE
value has been used for this node. Update this value, if User response: Manually define this copy group, if
necessary. necessary.
ANR0740E Import command: Invalid value for TYPE ANR0743E Import command: Invalid value for
parameter in exported data for copy MODE parameter in exported data for
group copy group name in domain domain archive copy group copy group name in
name, set policy set name, management domain domain name, set policy set name,
class management class name - backup is management class management class name.
assumed.
Explanation: During processing of command import import command, an invalid value is encountered for the
command, an invalid value is encountered for the TYPE MODE parameter for archive copy group copy group
parameter for copy group copy group, in policy domain name, in policy domain domain name, policy set policy set
domain name, policy set policy set name, management name, management class management class name.
System action: Processing of the command continues. If a later command causes the data to be imported, the
Based upon other copy group parameters, a copy group default or existing MODE value is used.
type of backup is assigned.
User response: Verify that the assigned TYPE value of later command, verify that the correct MODE value is
backup for this copy group is correct. used for this archive copy group.
ANR0741E Import command: Invalid value for TYPE ANR0744E Import command: Invalid value for
parameter in exported data for copy MODE parameter in exported data for
group copy group name in domain domain backup copy group copy group name in
name, set policy set name, management domain domain name, set policy set name,
class management class name - archive is management class management class name.
assumed.
Explanation: During processing of command import import command, an invalid value is encountered for the
command, an invalid value is encountered for the TYPE MODE parameter for backup copy group copy group
parameter for copy group copy group, in policy domain name, in policy domain domain name, policy set policy set
domain name, policy set policy set name, management name, management class management class name.
System action: Processing of the command continues. If a later command causes the data to be imported, the
Based upon other copy group parameters, a copy group default or existing MODE value is used.
type of archive is assigned.
User response: Verify that the assigned TYPE value of later command, verify that the correct MODE value is
archive for this copy group is correct. used for this backup copy group.

ANR0745E ANR0750E
SERIALIZATION parameter in exported MODE parameter in exported data -
data for archive copy group copy group backup copy group copy group name in
name in domain domain name, set policy domain domain name, set policy set name,
set name, management class management management class management class name
class name. defined with default MODE value.
Explanation: During preview processing of command Explanation: During processing of command import
import command, an invalid value is encountered for the command, an invalid value is encountered for the
SERIALIZATION parameter for archive copy group MODE parameter for backup copy group copy group
copy group name, in policy domain domain name, policy name, in policy domain domain name, policy set policy set
set policy set name, management class management class name, management class management class name.
name.
System action: Processing of the command continues. by using the default MODE value for this backup copy
If a later command causes the data to be imported, the group.
default or existing SERIALIZATION value is used.
User response: Verify that the correct MODE value
User response: None. If the data is imported with a has been used for this copy group. Update this value, if
later command, verify that the correct SERIALIZATION necessary.
value is used for this archive copy group.
ANR0746E Import command: Invalid value for SERIALIZATION parameter in exported
SERIALIZATION parameter in exported data - archive copy group copy group
data for backup copy group copy group name in domain domain name, set policy
name in domain domain name, set policy set name, management class management
set name, management class management class name defined with default
class name. SERIALIZATION value.
Explanation: During preview processing of command Explanation: During processing of command import
import command, an invalid value is encountered for the command, an invalid value is encountered for the
SERIALIZATION parameter for backup copy group SERIALIZATION parameter for archive copy group
copy group name, in policy domain domain name, policy copy group name, in policy domain domain name, policy
set policy set name, management class management class set policy set name, management class management class
name. name.
System action: Processing of the command continues. System action: Processing of the command continues,
If a later command causes the data to be imported, the by using the default SERIALIZATION value for this
default or existing SERIALIZATION value is used. archive copy group.
User response: None. If the data is imported with a User response: Verify that the correct
later command, verify that the correct SERIALIZATION SERIALIZATION value has been used for this copy
value is used for this backup copy group. group. Update this value, if necessary.
MODE parameter in exported data - SERIALIZATION parameter in exported
archive copy group copy group name in data - backup copy group copy group
domain domain name, set policy set name, name in domain domain name, set policy
management class management class name set name, management class management
defined with default MODE value. class name defined with default
SERIALIZATION value.
command, an invalid value is encountered for the Explanation: During processing of command import
MODE parameter for archive copy group copy group command, an invalid value is encountered for the
name, in policy domain domain name, policy set policy set SERIALIZATION parameter for backup copy group
name, management class management class name. copy group name, in policy domain domain name, policy
set policy set name, management class management class
name.
by using the default MODE value for this archive copy
group. System action: Processing of the command continues,
by using the default SERIALIZATION value for this
backup copy group.
has been used for this copy group. Update this value, if
necessary. User response: Verify that the correct
ANR0751E ANR0756E
SERIALIZATION value has been used for this copy by using the existing SERIALIZATION value for this
group. Update this value, if necessary. archive copy group.
ANR0751E Import command: Invalid value for SERIALIZATION value has been used for this copy
MODE parameter in exported data - group. Update this value, if necessary.
existing MODE value for archive copy
name, set policy set name, management
SERIALIZATION parameter in exported
class management class name was not
data - existing SERIALIZATION value
updated.
for backup copy group copy group name
Explanation: During processing of command import in domain domain name, set policy set
command, an invalid value is encountered for the name, management class management class
MODE parameter for archive copy group copy group name was not updated.
name, in policy domain domain name, policy set policy set
name, management class management class name.
System action: Processing of the command continues, SERIALIZATION parameter for backup copy group
by using the existing MODE value for this archive copy copy group name, in policy domain domain name, policy
group. set policy set name, management class management class
name.
has been used for this copy group. Update this value, if System action: Processing of the command continues,
necessary. by using the existing SERIALIZATION value for this
backup copy group.
ANR0752E Import command: Invalid value for User response: Verify that the correct
MODE parameter in exported data - SERIALIZATION value has been used for this copy
existing MODE value for backup copy group. Update this value, if necessary.
name, set policy set name, management
class management class name was not
ACTION parameter in exported data for
updated.
schedule schedule name in domain domain
Explanation: During processing of command import name.
MODE parameter for backup copy group copy group
name, in policy domain domain name, policy set policy set
ACTION parameter for schedule schedule name in policy
name, management class management class name.
domain domain name.
by using the existing MODE value for this backup copy
group.
default or existing ACTION value is used.
User response: If the data is imported with a later
has been used for this copy group. Update this value, if
command, verify that the correct ACTION value is
necessary.

SERIALIZATION parameter in exported
data - existing SERIALIZATION value
exported data for schedule schedule name
for archive copy group copy group name
in domain domain name.
in domain domain name, set policy set
name, management class management class Explanation: During preview processing of command
name was not updated. import command, an invalid value is encountered for the
DURUNITS or PERUNITS parameter for schedule
schedule name in policy domain domain name.
SERIALIZATION parameter for archive copy group System action: Processing of the command continues.
copy group name, in policy domain domain name, policy If a later command causes the data to be imported, the
set policy set name, management class management class default or existing values are used for DURATION,
name. DURUNITS, PERIOD, and PERUNITS.
System action: Processing of the command continues, User response: If the data is imported with a later

ANR0757E ANR0763E
command, verify that the correct values for

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

ANR0770E ANR0774E
ACTION parameter for schedule schedule name in Explanation: During processing of command export
domain domain name. command, an invalid value is encountered for the
domain domain name.
exported data will contain an unknown ACTION value
for this schedule. If this data is imported, the default or System action: Export processing continues, but the
existing ACTION value is used. exported data contains an unknown DAYOFWEEK
value for this schedule. If this data is imported, the
User response: Update the ACTION value for this
default or existing DAYOFWEEK value is used.
use the export data with the unknown value, and check User response: Update the DAYOFWEEK value for
and update the ACTION value after import processing this schedule and restart the export command.
has been performed. Alternatively, use the export data with the unknown
value, and check and update the DAYOFWEEK value
DURUNITS parameter detected while
exporting schedule schedule name in ANR0773E Export command: Invalid lock status
domain domain name - default or existing detected while exporting administrator
value is used during import. administrator name - this administrator
will not be locked during import.
command, an invalid value is encountered for the Explanation: During processing of command export
DURUNITS parameter for schedule schedule name in command, an invalid value is encountered for the lock
domain domain name. status for administrator administrator name.
System action: Export processing continues, but the System action: Export processing continues, but the
exported data contains an unknown DURUNITS value exported data contains an unknown lock status for this
for this schedule. If this data is imported, the default or administrator. If this data is imported, the
existing DURUNITS value is used. administrator will not be locked.
User response: Update the DURUNITS value for this User response: An administrator with the proper
schedule and restart the export command. Alternatively, authorization must issue the LOCK NODE or
use the export data with the unknown value, and check UNLOCK NODE command to achieve the desired lock
and update the DURUNITS value after import status, and then restart the export command.
processing has been performed. Alternatively, use the export data with the unknown
status, and issue a LOCK ADMIN or UNLOCK
ADMIN command after import processing has been
performed.
PERUNITS parameter detected while
exporting schedule schedule name in
domain domain name - default or existing ANR0774E Export command: Invalid value for
value is used during import. COMPRESSION parameter detected
while exporting node node name - default
or existing value is used during import.
PERUNITS parameter for schedule schedule name in Explanation: During processing of command export
domain domain name. command, an invalid value is encountered for the
COMPRESSION parameter for node node name.
exported data will contain an unknown PERUNITS System action: Export processing continues, but the
value for this schedule. If this data is imported, the exported data contains an unknown COMPRESSION
default or existing PERUNITS value is used. value for this node. If this data is imported, the default
or existing COMPRESSION value is used.
User response: Update the PERUNITS value for this
schedule and restart the export command. Alternatively, User response: Update the COMPRESSION parameter
use the export data with the unknown value, and check for this node and restart the export command.
and update the PERUNITS value after import Alternatively, use the export data with the unknown
processing has been performed. value, and check and update the COMPRESSION value
DAYOFWEEK parameter detected while
domain domain name - default or existing
value is used during import.
ANR0775E ANR0782E
ANR0775E Export command: Invalid lock status ANR0778E Command: Error encountered in accessing
detected while exporting node node name data storage - device class device class
- this node will not be locked during name is not defined.
import.
Explanation: During processing of command export an error occurred because the specified device class is
command, an invalid value is encountered for the lock not defined.
status for node node name.
System action: The command command is ended and
System action: Export processing continues, but the server operation continues.
exported data contains an unknown lock status for this
User response: Make sure the specified device class is
node. If this data is imported, the node will not be
defined.
locked.
User response: Lock or unlock the node to achieve the
ANR0779E Command: Error encountered in accessing
desired lock status, and then restart the export
data storage - disk volume specified.
command. Alternatively, use the export data with the
unknown status, and lock or unlock the node after Explanation: During command command processing,
import processing has been performed. an error occurred because a specified volume is a disk
volume rather than a tape volume.
ANR0776E Export command: Invalid value for System action: The command command is ended and
ARCHDELETE parameter detected server operation continues.
while exporting node node name - default
or existing value is used during import. User response: Make sure that all volumes specified
for the command command are tape volumes.
ARCHDELETE parameter for node node name. ANR0780E Export/import command: Process aborted -
a server communications session could
System action: Export processing continues, but the not be established.
exported data contains an unknown ARCHDELETE
value for this node. If this data is imported, the default Explanation: The server export/import process
or existing ARCHDELETE value is used. encounters an internal error in establishing an
intermemory communications session with other server
User response: Update the ARCHDELETE parameter components.
for this node and restart the export command.
Alternatively, use the export data with the unknown System action: The export or import process ends and
value, and check and update the ARCHDELETE value server operation continues.
after import processing has been performed. User response: See the documentation for the
ANR0777E Export command: Invalid value for application.
BACKDELETE parameter detected while If the error is not resolved, contact your service
exporting node node - default or existing representative.
value is used during import.
Explanation: During processing of command export ANR0781E Export/import command: Process aborted -
command, an invalid value is encountered for the server sign on failed.
BACKDELETE parameter for node node name.
System action: Export processing continues, but the encounters an internal error in establishing an
exported data contains an unknown BACKDELETE intermemory communications session with other server
value for this node. If this data is imported, the default components.
or existing BACKDELETE value is used.
User response: Update the BACKDELETE parameter server operation continues.
for this node and restart the export command.
Alternatively, use the export data with the unknown User response: Contact your service representative.
value, and check and update the BACKDELETE value
after import processing has been performed. ANR0782E Export/import command: Process aborted -
a server data storage session could not
be established (rc return code).
encounters an internal error in establishing a session

ANR0783E ANR0789E
with the data storage services. activity log and search for messages. If the error cannot
representative.
ANR0786E Import command: Invalid export version
version number in exported data.
activity log and search for messages. If the error cannot Explanation: The server import process encounters an
be isolated and resolved, contact your service internal error in reading data from the export media.
representative. An invalid export version number (version number) is
encountered during the read operation.
ANR0783E Export/import command: Process aborted - System action: The export or import process ends and
a server data storage Export/Import server operation continues.
stream could not be established (rc
return code).
Explanation: The server export/import process error. Use the QUERY ACTLOG command to view the
encounters an internal error in establishing a session activity log and search for messages. If the error cannot
with the data storage services. be isolated and resolved, contact your service
representative.
ANR0787E Import command: Import of file space
filespace name in node node name aborted
by server (abort reason).
activity log and search for messages. If the error cannot Explanation: The server import process encounters an
be isolated and resolved, contact your service internal error in importing file space filespace name for
representative. client node node name. The reason code abort reason is
encountered.
ANR0784E Export/import command: Process aborted - System action: The export or import process ends and
internal error detected with the server operation continues.
Export/Import level: level number.
Explanation: The server export/import process prior to this message to determine the source of the
encounters an internal error in evaluating the error. Use the QUERY ACTLOG command to view the
export/import level (SERVER, NODE, ADMIN, activity log and search for messages. If the error cannot
POLICY). be isolated and resolved, contact your service
representative.
ANR0788E Import command: Error error code during
import of data storage data.
error. Use the QUERY ACTLOG command to view the Explanation: The server import process encounters an
activity log and search for messages. If the error cannot internal data storage error. The error code error code is
be isolated and resolved, contact your service encountered.
representative.
ANR0785E Import command: Invalid record type
xrecord type read from export data.
Explanation: The server export/import process error. Use the QUERY ACTLOG command to view the
encounters an internal error in reading data from the activity log and search for messages. If the error cannot
export media. An invalid record type of record type is be isolated and resolved, contact your service
encountered during the read operation. representative.
server operation continues. ANR0789E Import command: Failure in normalizing
transaction identifier for sending to the
server.
error. Use the QUERY ACTLOG command to view the Explanation: The server import process encounters an
ANR0790E ANR0795E
internal database transaction error in importing Because the imported information for the rule is
information into the server database. ambiguous, the server assumes that the rule is for
backup data.
server operation continues. System action: The import process continues.
User response: Examine the server messages issued User response: The user for node node name should
prior to this message to determine the source of the query the access rules for the specified node name after
error. Use the QUERY ACTLOG command to view the the import process has completed, and correct or delete
activity log and search for messages. If the error cannot any access rules that are in error or not needed.
representative.
ANR0790E Import command: Error in absorbing data error accessing data storage.
records.
Explanation: The server import process encounters an in accessing data storage while executing an import or
internal error in importing information into the server export preview operation.
database.
System action: The export or import process ends and ended and server operation continues.
User response: Examine the server messages issued examine messages prior to this error to determine the
prior to this message to determine the source of the cause of the data storage failure. If you find and
error. Use the QUERY ACTLOG command to view the resolve the error, retry the export or import operation.
activity log and search for messages. If the error cannot If you cannot find the error, contact your service
be isolated and resolved, contact your service representative for assistance in resolving the problem.
representative.
ANR0791E Export/import command: Protocol error - terminated abnormally - error accessing
verb "verb type" with length verb length data storage.
received, expected "expected type".
Explanation: The server export or import process in accessing data storage while executing an import or
encounters an internal protocol error in exporting export operation.
information from or importing information into the
server database. The verb verb type is encountered with
a length of verb length when a verb type of expected type
was expected. User response: Use the QUERY ACTLOG command to
examine messages prior to this error to determine the
cause of the data storage failure. If the import or export
operation involves a session with another server, run
User response: Examine the server messages issued the QUERY ACTLOG command to examine messages
prior to this message to determine the source of the on the other server as well. Messages on the other
error. Use the QUERY ACTLOG command to view the server can help you troubleshoot the error on the local
activity log and search for messages. If the error cannot server. If you find and resolve the error, retry the
be isolated and resolved, contact your service export or import operation. If you cannot find the error,
representative. contact your service representative for assistance in
resolving the problem.
ANR0792E Import command: Invalid copy type
encountered in an imported file space ANR0795E Command: Error encountered in accessing
authorization rule for node node name, data storage - invalid volume name
file space filespace name - a type of specified.
BACKUP will be assumed.
Explanation: The server encounters an error in
Explanation: During import processing for command accessing data storage while processing command
import command, an invalid copy type is encountered command. The error occurred because an attempt has
for an authorization rule that grants access for file been made to access a volume with an invalid name.
space filespace name on node node name. Authorization
rules typically specify copy types of backup or archive,
depending on whether backup file access or archive file
access is granted by the file space owner to other users.

ANR0796E ANR0803I
User response: Issue the command with a valid defined to server storage pools. Use the QUERY
volume name. VOLHISTORY command to display the names of
volumes that have been used for export, database
dump, or database backup operations.
data storage - insufficient number of
mount points available for removable ANR0800I Command command for node node name
media. started as process process ID.
Explanation: During command command processing, Explanation: A file space deletion process has started
the server cannot allocate sufficient mount points. to delete one or more file spaces for the specified node.
The process is assigned the ID specified in the message.
ended and server operation continues. System action: The server starts a background process
to perform the operation in response to the DELETE
User response: If necessary, make more mount points
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
data storage - required volume was not
PROCESS command.
mounted.
Explanation: During command command processing, a
ANR0801I DELETE FILESPACE filespace name for
required volume cannot be mounted. The mount
node node name started as process process
request may have been canceled.
ID.
Explanation: The specified client node has started a
file space deletion process (on the server) to delete one
User response: Issue the command again and make or more file spaces. The process has been assigned the
sure the necessary volumes are accessible. ID specified in the message.
System action: The server starts a background process
ANR0798E Import command: Error encountered in to perform the operation in response to a request from
accessing data storage - volume cannot the client node.
be used.
User response: To obtain status on the file space
Explanation: During import processing, a volume has deletion process, issue the QUERY PROCESS command.
been mounted but cannot be used. The process may be canceled by an authorized
administrator using the CANCEL PROCESS command.
System action: The import operation is ended and
ANR0802I DELETE FILESPACE filespace name
User response: Query the activity log for messages (backup/archive data) for node node name
preceding this one that give additional information. started.
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
ANR0799E Command: Error encountered in accessing belonging to the node indicated. If a file space name is
data storage - volume already in use. not included in the message, all file spaces belonging to
Explanation: During command command processing, a the node are deleted.
volume cannot be used because it is already defined in System action: The background process deletes
a storage pool, or has been previously used by an backup and archive objects for the specified file space
export, database dump, or database backup operation while server operation continues.
(as recorded in the volume history) or is in use by
another process. User response: To obtain status on the file space
System action: The command command operation is The process may be canceled by an authorized
ended and server operation continues. administrator using the CANCEL PROCESS command.
User response: Specify a volume that is not in use or
defined in a storage pool, and that has not been ANR0803I DELETE FILESPACE filespace name
previously used for an export, database dump, or (backup data) for node node name
database backup operation as recorded in the server started.
volume history information. Use the QUERY VOLUME
command to display the names of volumes that are Explanation: A background server process has started
ANR0804I ANR0813I
(on the server) to delete backup objects in the specified

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

for node node name: number of objects ANR0813I Inventory file expiration process process
objects were deleted. ID canceled prior to completion:
processed number of nodes nodes,
Explanation: A server process deleted file space data examined number of objects objects,
for the specified node. The total number of deleted deleting number of backup objects backup
objects is reported in the message. objects, number of archive objects archive
System action: The deletion process is complete, but objects, number of DB backup volumes DB
server operations continue. backup volumes, and number of recovery
plan files recovery plan files. retry count
User response: None. objects were retried and error count
errors were encountered.

ANR0814I ANR0820I
Explanation: The inventory file expiration process was volumes to the server log and extend the log size.
canceled by an administrator. The number of objects
If the server is low on memory, do the following:
examined and deleted prior to the cancelation are
reported. A total error count is also displayed. See the documentation for the operating system about
how to increase memory for an application.
System action: The server ends the file expiration
process.
ANR0816I Expiration retry was successful.
Explanation: In accordance with management class
policy, server roll-off processing has been successful in
ANR0814I Expiration retry retry number of maximum
retrying a client file expiration.
retries in number of seconds seconds.
System action: Server roll-off processing continues.
Explanation: Server roll-off processing has
encountered an error in attempting to remove expired User response: None.
client file copies from the server database. The
operation will be tried again in the number of seconds
indicated. ANR0818I Waiting to retry expiration because of
insufficient resources.
System action: The server waits for the number of
seconds indicated and retries the file expiration Explanation: The server inventory expiration process
operation. is waiting to retry expiration processing that failed
because of insufficient memory, database, or log
User response: Expiration retry processing occurs resources on the server.
when the server database is full, the log is full, or
sufficient server memory is not available to continue System action: Server operation continues. The
processing. Use the QUERY ACTLOG command to look expiration processing is reattempted automatically.
for messages issued prior to this one that indicate the User response: Use the QUERY ACTLOG command to
type of error encountered. examine messages issued prior to this one, which
If the server is out of database space, issue the DEFINE indicated the resource that is not available to the
DBVOLUME and EXTEND DB commands to add expiration process. Correct the shortage.
volumes to the server database and extend the database
size. ANR0819I Cancel in progress
If the server is out of log space, issue the DEFINE Explanation: This message is displayed in response to
LOGVOLUME and EXTEND LOG commands to add a QUERY PROCESS command, and indicates that an
volumes to the server log and extend the log size. inventory expiration process has been canceled. The
If the server is low on memory, do the following: process will end shortly.
See the documentation for the operating system about System action: The expiration process terminates and
how to increase memory for an application. server operation continues.
See the documentation for the operating system about User response: None.
ANR0820I Sorting information for number objects
ANR0815I Expiration retry in progress. has been deleted.
Explanation: The server is retrying an operation Explanation: A background server process has deleted
during client file roll-off processing. Expiration retry sorting information for number files from the server
processing occurs when the server database is full, the database. This process is started during initialization to
log is full, or sufficient server memory is not available remove any sorting information which is left over from
to continue processing. previous export operations.
System action: The roll-off operation is retried. System action: The actual backup or archive objects
were not deleted, but only information used to sort
User response: Use the QUERY ACTLOG command to these objects during the previous export operation.
look for messages issued prior to this one that indicate
the type of error encountered. If the server is out of User response: None.
database space, issue the DEFINE DBVOLUME and
EXTEND DB commands to add volumes to the server
database and extend the database size.
If the server is out of log space, issue the DEFINE
LOGVOLUME and EXTEND LOG commands to add
ANR0821E ANR0829E
encountered a transaction failure.

ANR0821E Filespace identifier fsId is not valid.
System action: The server process is retried if the
Explanation: The identifier assigned for a filespace is
maximum number of retry attempts have not been
out of range.
exceeded.
System action: The file space is not added.
User response: Transaction failure usually indicates
User response: Contact your service representative. that a database deadlock was detected during file space
deletion. These deadlock conditions are sometimes
encountered when multiple file space deletion
ANR0822I command: Filespace filespace name
processes are running at the same time. No action is
(fsId=filespace id) successfully renamed
required unless the DELETE FILESPACE terminates
to new filespace name for node node name.
without completing the deletion process (see message
Explanation: The file space specified was renamed to ANR0828).
the new name specified for the node. This message is
displayed in response to successful completion of the
ANR0827I DELETE FILESPACE filespace name will
RENAME FILESPACE command.
be retried for node node name.
System action: The system renames the file space for
Explanation: A file space deletion process for the node
the node as indicated
indicated is being retried because an error was
User response: None. encountered.
System action: The server process is retried.
ANR0823E command: Filespace filespace name cannot
be renamed to new filespace name, a
filespace with this name already exists
for node node name. ANR0828W DELETE FILESPACE filespace name for
node node name terminated before
Explanation: The file space name specified as a target
completion due to transaction failure:
name for the command was found to already exist for
number of objects objects deleted.
the node specified. The command fails.
Explanation: A background server process that has
System action: Server operation continues, the
been deleting file space data for the indicated node is
command fails.
terminated prematurely because of transaction failure.
User response: Reissue the command with a different The number of objects deleted before the operation
target filespace name ended are reported in the message.
ANR0824I Delete Filespace filespace name operation continues.
(space-managed data) for node node name
User response: Termination of this process because of
started.
transaction failure usually indicates that a database
Explanation: A background server process has started deadlock was detected during file space deletion. These
(on the server) to delete space-managed objects in the deadlock conditions are sometimes encountered when
specified file space belonging to the node indicated. If a multiple file space deletion processes are running at the
file space name is not included in the message, then the same time. The command should be started again
space-managed objects for all file spaces that belong to when fewer file space deletion processes are active. An
the node are deleted. authorized administrator can issue the DELETE
FILESPACE command to delete remaining files in the
System action: The background process deletes file space(s).
space-managed objects for the specified file space while
ANR0829E Command: Invalid combination of TYPE
User response: To obtain status on the file space and DATA parameters.
The process may be canceled by an authorized Explanation: The specified command has been issued
administrator using the CANCEL PROCESS command. with an invalid combination of the TYPE and DATA
parameters. DATA=IMAGES can only be specified if
TYPE=ANY or TYPE=BACKUP.
node node name encountered a System action: Server operation continues, but the
transaction failure. command is not processed.
Explanation: A background server process that has User response: Issue the command and specify a valid
been deleting file space data for the indicated node combination of parameters.

ANR0830W ANR0834W
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
group: DEFAULT management class User response: No action is required. A policy
attributes will be used for expiration. administrator with authority over the specified domain
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.
System action: The server obtains the DEFAULT
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
User response: No action is required. A policy PERIOD will be used for expiration.
administrator with authority over the specified domain
server found a client file copy whose management class
or archive copy group no longer exists. The DEFAULT
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
ANR0831W The DEFAULT management class class the specified policy domain to determine if client file
name in domain domain name does not copies need to be expired and removed from the server
have a BACKUP copy group: GRACE database.
PERIOD will be used for expiration.
System action: The server obtains the GRACE
Explanation: During policy roll-off processing, the PERIOD retention values for the specified domain and
server found a client file copy whose management class then determines if archive file copies need to be
or backup copy group no longer exists. The DEFAULT expired.
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
uses the GRACE PERIOD retention value defined for
the specified policy domain to determine if client file
MGMTCLASS, and ACTIVATE POLICYSET commands
copies need to be expired and removed from the server
to define and activate a policy set that contains
database.
definitions for the missing management class or backup
System action: The server obtains the GRACE copy group.
PERIOD retention values for the specified domain and
then determines if backup file copies need to be
ANR0834W Inventory client file expiration cannot
expired.
start because of insufficient memory -
User response: No action is required. A policy will retry in number of seconds seconds.
Explanation: The server inventory expiration process
is pausing to retry an operation that failed because
sufficient memory is not available on the server.
for the missing management class or backup copy System action: Server operation continues; the
group. expiration process will be retried after the stated delay.
ANR0832W Management class class name in domain operating system about how to increase memory for an
domain name used by node node name in application.
filespace filespace name is no longer
active, or no longer has an ARCHIVE
copy group: DEFAULT management
class attributes will be used for
expiration.
server found a client file copy whose management class
or archive copy group no longer exists.
ANR0835W ANR0840I
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 and error count
When a management class or backup copy group no
errors were encountered.
longer exists, the number of backup client file copies
that have been deleted using the default management Explanation: An administrator or schedule issued the
class or the retention grace period is displayed in the command EXPIRE INVENTORY ... DURATION=xxx,
message. When a management class or archive copy where xxx is the number of minutes for the expire
group no longer exists, the number of archive client inventory process to run. That xxx number of minutes
files that have been deleted using the default has been reached, so the expire inventory process ends.
management class or the retention grace period is
displayed in the message. System action: The expire inventory process ends.
System action: The server obtains the DEFAULT User response: None.
backup copy group or archive copy group version and ANR0838I Pass pass of group table conversion
retention parameters to determine if file copies need to processing beginning.
be expired. If, however, the needed backup copy group
or archive copy group does not exist in the DEFAULT Explanation: The contents of the group information
management class, the server will use the retention tables needs to be updated before the server can fully
grace period for the domain. initialize. This is an informational message indicating
that processing has begun for a particular pass of the
User response: No action is required. This message is conversion.
only issued when expiration processing has been
started with the QUIET option to suppress detailed System action: Server processing continues.
messages. Expiration processing can be started without User response: None.
the QUIET option to see the detailed messages which
will indicate specific node and filespaces and will
further distinguish between backup and archive copy ANR0839I Pass pass of group table conversion
groups. A policy administrator with authority over the processing complete.
specified domain may use the DEFINE COPYGROUP, Explanation: The contents of the group information
DEFINE MGMTCLASS, and ACTIVATE POLICY tables have been successfully converted for the
commands to define and activate a policy set that specified pass.
contains definitions for the missing management class
or copy group. System action: If all passes of the conversion are
complete, server processing continues. If not, additional
passes will be performed.
ANR0836W No query restore processing session
session id for node node name and filespace User response: None.
name failed to retrieve file high-level file
namelow-level file name - file being
ANR0840I Converting group table information for
skipped.
node node.
Explanation: The no query restore processing for the
Explanation: The group table information for the
session listed relating to the specified node name and
displayed node is being converted.
filespace failed to retrieve the specified file. An error
occurred while retrieving this file so it will be skipped. System action: Server processing continues
System action: The no query restore operation User response: None.
continues.
User response: Determine the cause of the file retrieve
failure and correct it. After this situation is correct, the

ANR0844E ANR0853E
ANR0844E Command: node name is not a ANR0850E Command: Cannot Start process name
backup-archive node. Process.
Explanation: The specified node name is not a Explanation: The indicated DELETE FILESPACE
backup-archive node. process cannot be started on the server.
System action: Processing fails for the command. System action: The DELETE FILESPACE command is
Server operation continues. ended and server processing continues.
User response: Reissue the command with a valid User response: This usually indicates that sufficient
node name. server memory is not available on the server.
See the documentation for the operating system about
ANR0847I CLEANUP BACKUPGROUPS evaluated how to increase memory for an application.
number of groups groups, and deleted
groups deleted orphan groups with
ANR0851E Cannot start delete file space thread for
members deleted members deleted.
node node name.
Explanation: The CLEANUP BACKUPGROUPS has
Explanation: The indicated DELETE FILESPACE
finished processing, and has deleted the specified
process cannot be started on the server. Sufficient
number of orphan groups and members.
memory on the server may not be available.
System action: The DELETE FILESPACE command is
User response: None. ended and server processing continues.
ANR0848W Expiration failed to delete file type file operating system about how to increase memory for an
file name for node node name and application.
filespace filespace name - file will be
skipped.
ANR0852E Command: No matching file spaces
Explanation: The expiration process was unable to found for node node name.
delete the indicated file. The file will be skipped by
Explanation: The server did not find any file spaces
expiration.
for the node indicated matching the names specified in
System action: The expiration process continues. the command.
User response: Try expiration again to determine if System action: The server ends the command.
the cause of the deletion failure was an intermittent
User response: Enter the command with file space
problem or if it is a permanent problem. If after a
names that refer to defined file spaces for the specified
subsequent expiration attempt the file still is not
node. Note that file space names are case sensitive.
deleted, contact your service representative.
Enter them by using exactly the same uppercase and
lowercase characters that match the file space name
ANR0849E Command: Not permitted for node Node defined on the server. Use the QUERY FILESPACE
Name - node of type SERVER. command to determine which file spaces are defined
for a node on the server.
Explanation: The indicated DELETE FILESPACE
process is not started because the node specified is of
NODETYPE=SERVER. A DELETE FILESPACE may ANR0853E Transaction failed in file space deletion,
only be processed for nodes of this type with the DELETE FILESPACE process aborted.
TYPE=SERVER parameter specified.
Explanation: A database transaction fails while the
System action: The DELETE FILESPACE command is server is deleting file space data.
ended and server processing continues.
System action: The server ends the file space deletion
User response: If this filespace must be deleted, process.
Reissue the command with the TYPE parameter set to
TYPE=SERVER. Please use caution when using the
TYPE=SERVER parameter as this can impact the
error. Issue the QUERY ACTLOG command to view the
availability of data for the server that owns these files.
representative.
ANR0854E ANR0861E
ANR0854E Inventory file space query failure, ANR0858E Inventory object search failure, DELETE
DELETE FILESPACE process aborted. FILESPACE process aborted.
Explanation: The server encounters an error in Explanation: The server encounters an error accessing
querying the inventory database during a file space the inventory database during file space deletion
deletion process. processing.
System action: The server ends the file space deletion System action: The server ends the file space deletion
process. process.
User response: Examine the server messages issued User response: Examine the server messages issued
prior to this message to determine the source of the prior to this message to determine the source of the
error. Issue the QUERY ACTLOG command to view the error. Issue the QUERY ACTLOG command to view the
activity log and search for messages. If the error cannot activity log and search for messages. If the error cannot
be isolated and resolved, contact your service be isolated and resolved, contact your service
representative. representative.
ANR0855E Server LOG space exhausted, DELETE ANR0859E Data storage object erasure failure,
FILESPACE process aborted. DELETE FILESPACE process aborted.
Explanation: Insufficient server log space has been Explanation: The server encounters an error in
encountered during file space deletion processing. removing file copies from data storage during file space
deletion processing.
System action: The server ends the file space deletion
process. System action: The server ends the file space deletion
process.
available to the server, an authorized administrator can User response: Examine the server messages issued
add log volumes by using the DEFINE LOGVOLUME prior to this message to determine the source of the
command, and can extend the size of the log by using error. Issue the QUERY ACTLOG command to view the
the EXTEND LOG command. activity log and search for messages. If the error cannot
representative.
ANR0856E Server database space exhausted,
DELETE FILESPACE process aborted.
ANR0860E Expiration process process ID terminated
Explanation: Insufficient server database space has
due to internal error: examined number of
been encountered during file space deletion processing.
objects objects, deleting number of backup
System action: The server ends the file space deletion objects backup objects, number of archive
process. objects archive objects, number of DB
backup volumes DB backup volumes, and
User response: To increase the amount of database number of recovery plan files recovery plan
space available to the server, an authorized files. retry count objects were retried and
administrator can add log volumes using the DEFINE error count errors were encountered.
DBVOLUME command and can extend the size of the
database using the EXTEND DB command. 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
ANR0857E Data storage session failure, DELETE total error count is also displayed.
FILESPACE process aborted.
System action: The server ends the expiration process.
Explanation: The server encounters an error accessing
data storage during file space deletion processing. User response: Examine the server messages issued
System action: The server ends the file space deletion error. Issue the QUERY ACTLOG command to view the
process. 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.
activity log and search for messages. If the error cannot ANR0861E Transaction failed in expiration,
be isolated and resolved, contact your service inventory expiration aborted.
representative.
Explanation: The server encounters a database
transaction failure during policy roll-off processing.

ANR0862E ANR0867E
System action: The server ends roll-off processing. activity log and search for messages.
User response: Examine the server messages issued If the server is out of database space, issue the DEFINE
prior to this message to determine the source of the DBVOLUME and EXTEND DB commands to add
error. Issue the QUERY ACTLOG command to view the volumes to the server database and extend the database
activity log and search for messages. If the error cannot size.
representative.
volumes to the server log and extend the log size.
ANR0862E Expiration processing suspended -
Explanation: The server ends policy roll-off processing
because sufficient server memory is not available.
If the error cannot be isolated and resolved, contact
System action: The server ends policy roll-off
processing and server operation continues.
ANR0866E Expiration processing retries failed - no
success after maximum retries retries.
application.
Explanation: Server policy roll-off processing ends
because retry processing has not been successful in
expiring client file copies from the server database.
insufficient DB space.
because sufficient server database space is not
available. User response: Examine the server messages issued
activity log and search for messages.
If the server is out of database space, issue the DEFINE
space available to the server, an authorized
DBVOLUME and EXTEND DB commands to add
volumes to the server database and extend the database
DEFINE DBVOLUME command and can extend the
size.
size of the database using the EXTEND DB command.
volumes to the server log and extend the log size.
insufficient LOG space.
because sufficient server log space is not available. See the documentation for the operating system about
processing and server operation continues. If the error cannot be isolated and resolved, contact
available to the server, an authorized administrator can
add log volumes by using the DEFINE LOGVOLUME ANR0867E Unable to open policy domain for node
command and can extend the size of the log by using node name during server operation.
the EXTEND LOG command.
Explanation: Policy roll-off processing on the server
encounters an error while obtaining policy information
ANR0865E Expiration processing failed - internal related to the specified node.
server error.
System action: The server ends roll-off processing and
Explanation: Server retry processing during policy server operation continues.
roll-off fails.
System action: The server ends policy roll-off prior to this message to determine the source of the
processing. error. Issue the QUERY ACTLOG command to view the
representative.
ANR0868E ANR0875E

ANR0868E Cannot find management class name for
representative.
ID management class ID.
ANR0872E Grace Period retention for domain
encounters an error while obtaining policy information.
domain name could not be obtained.
encounters a database error in obtaining GRACE
User response: Examine the server messages issued PERIOD values for the specified policy domain.
ANR0869E Cannot find policy domain for node
node ID.
representative.
encounters an error while obtaining policy information
ANR0873E Invalid copy type encountered in
related to the specified node.
expiring files: copytype ID
encounters a database error in obtaining copy group
User response: Examine the server messages issued information.
ANR0870E Cannot find node name for node node
ID.
representative.
encounters a database error in obtaining information
ANR0874E Backup object object not found during
for a client node.
inventory processing.
Explanation: Inventory processing on the server
encounters a database error in obtaining backup
User response: Examine the server messages issued information in data storage.
System action: The server ends roll-off processing, or
client session(s) and server operation continues.
ANR0871E Cannot find file space name for node
node ID, file space file space ID.
representative.
encounters a database error in obtaining information
ANR0875E Archive object object.ID not found
for a client node.
during expiration processing.
encounters a database error in obtaining archive
User response: Examine the server messages issued information in data storage.

ANR0876E ANR0883E
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.
ANR0876E Data storage erasure failed during
expiration processing.
Explanation: Policy roll-off processing on the server representative.
encounters a database error while deleting information
from data storage.
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
ANR0877E Copy type not backup for object
file space name (in proper case).
object.ID.
ANR0881E Policy Error : the GRACE PERIOD
encounters a database error in accessing inventory
archive retention value could not be
information.
obtained for domain domain ID during
System action: The server ends roll-off processing and client inventory processing.
Explanation: The server encounters an internal error
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

ANR0878E Entry for backup object object.ID not domain for node node name during client
found. inventory query processing.
Explanation: Policy roll-off processing on the server Explanation: The server encounters an internal error
encounters a database error in accessing inventory in accessing policy information.
information.
System action: The client operation is ended and
System action: The server ends roll-off processing and server operation continues.
error. Issue the QUERY ACTLOG command to view the ANR0883E Cannot obtain node name for node node
activity log and search for messages. If the error cannot ID.
be isolated and resolved, contact your service Explanation: The server encounters an internal error
representative. in accessing client node information.
ANR0879E Error opening inventory file space operation continues.
query.
ANR0884E ANR0890I
server finds a client file copy with a management class

ANR0884E Error code during deletion of sorting
or a backup copy group that no longer exists.
information for number objects.
System action: The server skips the files in error.
Explanation: A background server process
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
domain name used by node node name in
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
contact your service representative. 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 ANR0889E The server is not licensed for Central
processing is then able to import file data by using the Administration functions. This includes
renamed management class. the ability to issue SQL commands.
System action: Import processing for the command Explanation: An SQL command was issued but the
continues. server is not licensed to support Central Administrative
functions, including SQL query support.
User response: None. However, an administrator may
want to examine the policy definitions for new System action: The server ignores the command and
management class name so they are aware of the continues processing.
management classes that may be used if the policy set User response: If you have purchased the Central
containing this management class is activated. Administration license, use the REGISTER LICENSE
command to enable the license on the server. If you
ANR0886E Management class class name in domain have not purchased the license and wish to do so,
domain name used by node node name in contact your service representative.
file space filespace name has no BACKUP
copy group with id copy group id; ANR0890I Export/import command: Processing
Expiration will not be performed for optionset optionset name.
files from this node and filespace that
are bound to this management class and Explanation: The background export or import
copy group id. process to service the command export/import command
is currently processing optionset definition information.

ANR0891I ANR0903W

ANR0895E Command: Cannot Start process name
command continues.
Process.
Explanation: The indicated process cannot be started
on the server.
System action: The specified command is ended and
optionset definitions.
server processing continues.
User response: This usually indicates that sufficient
server memory is not available on the server.
copies number client optionset definitions from the
server database to export media or from export media See the documentation for the operating system about
into the server database. Data is not moved if how to increase memory for an application.
command.
ANR0900I Processing options file filespec.
Explanation: At server initialization, the server is
reading the server options file whose name is shown in
User response: None. the message.
System action: The server reads and processes the
ANR0892I Export command: No matching optionsets options in this file.
found for exporting.
find any client optionsets for export command.
ANR0901W Invalid option statement found in file
System action: The export process continues and no filespec.
option sets from the server.
Explanation: While processing the server options file
User response: None. named, the server has encountered an invalid
statement. The invalid statement type is shown in the
message. The lines following this message provide
ANR0893I Are you sure that you want to accept the
more information.
current system date as valid ?
System action: The server ignores the statement in
Explanation: This message is displayed when the
error. Server initialization continues. The default value
ACCEPT DATE command has been issued to confirm
is used for any missing or ignored options.
that you want to accept the date on the system as
valid. Accepting an invalid date can cause any of the User response: Ignore the error, or use a text editor to
following problems: Premature deletion of data correct the error and restart the server.
Excessive retention of data Scheduling problems Event
record problems Password expiration problems.
ANR0902W Unsupported keyword found in file
System action: The command waits for you to filespec.
confirm the action.
Explanation: While processing the server options file
User response: Specify Yes if you want to accept the named, the server has encountered an invalid keyword
system date as valid, or No if you do not want to on an option statement. The lines following this
execute the command. message provide more information.
System action: The server ignores the option
ANR0894I Current system has been accepted as statement in error. Server initialization continues. The
valid. default value is used for any missing or ignored
options.
ACCEPT DATE command has been issued and the date User response: Ignore the error, or use a text editor to
has been accepted as valid by the server. correct the error and restart the server.
System action: The current system date is accepted as
valid by the server. The server will begin processing ANR0903W Excessive option statement found in file
using the current system date. filespec.
User response: Issue the ENABLE SESSIONS ALL Explanation: While processing the specified server
command to allow client, server and administrative options file, the server has encountered more of the
sessions to start. named statement type than can be processed.
ANR0904W ANR0915E
System action: The server ignores the extra statement.

ANR0911I Archive conversion processing for node
Server initialization continues.
name completed successfully. The
User response: Ignore the error, or use a text editor to description tables have description count
correct the error and restart the server. descriptions, directory count directories,
file count and files and object set count
object sets.
ANR0904W Duplicate option statement found in file
filespec. Explanation: CONVERT ARCHIVE for the specified
node completed successfully. The node can now query
Explanation: While processing the server options file for archive objects specifying a non-wildcarded
named, the server has encountered a duplicate description.
statement of the type shown.
System action: The server ignores the duplicate
statement. Server initialization continues. User response: None.
User response: Ignore the error, or use a text editor to

correct the error and restart the server. ANR0912I Undo conversion processing for node
node name completed successfully. The
node is no longer converted.
ANR0905W Options file filespec not found.
Explanation: UNDO ARCHCONVERSION was issued
Explanation: At server initialization, the server is for the specified node. The node will no longer use the
unable to locate the server options file named. archive description tables.
System action: The server uses the default values for System action: Processing continues.
all options. Server initialization continues.
User response: If the default values are acceptable,
ignore the error. Otherwise, move a valid server
options file to the proper location, rename a valid ANR0913E Archive conversion processing for node
options file to the proper name, or use a text editor to node name did not complete (result).
build the proper server options file, and then restart the
Explanation: Archive conversion for the indicated
server.
node did not complete because of the specified result.
System action: Archive conversion ends. Server
ANR0909E Insufficient memory to process options
processing continues.
file.
User response: Check previous messages for error
Explanation: At server initialization, the server is
conditions.
unable to process the server options file due to
ANR0914E Diagnostic(ID): a request failed because
System action: Server initialization ends.
object (object name), size (size), exceeds
User response: Restart the server with more memory the maximum size of maximum size.
available. Refer to the Administrators Guide for your
Explanation: The size of the specified object exceeds
particular platform.
the maximum size defined for that object. The server
cannot handle the new object.
ANR0910W Archive entries for nodeName are already
converted.
fails.
Explanation: Archive entries for nodeName have
User response: Determine why the new object's length
already been converted to the description tables. They
exceeds the maximum specified for the object. Reduce
will not be converted again.
the length of the object.
User response: To force the reconversion of the ANR0915E Unable to open language language name
archive entries for nodeName, use the FORCE=Yes for message formatting.
option to the CONVERT ARCHIVE command.
Explanation: The server is unable to open the
specified message repository.
System action: Server initialization continues with the
default message repository.
User response: Ensure that a valid language is

ANR0916I ANR0926E
specified in the LANGUAGE option of the server User response: None.

options file. If a change is made to the options file,
restart the server to activate changes.
ANR0921I Tracing is now active to file file spec.
Explanation: In response to a TRACE START
ANR0916I Product Name distributed by Company is
command, server trace records are being written to the
now ready for use.
file named.
Explanation: The server has completed startup
processing and is now ready for use.
ANR0922I Trace ended.
Explanation: In response to a TRACE END command,
server trace records are no longer being written.
name (client platform) - in domain domain
name failed because of policy length. System action: None.
Explanation: The client cannot handle very long User response: None.
policies.
System action: The client operation is ended and ANR0923E Tracing is inactive.
Explanation: A TRACE END command has been
User response: Upgrade the client to the latest level, entered, but tracing is not active.
or activate a policy set with fewer management classes.
System action: The command is ignored.
ANR0918E Inventory operation for node node name User response: If tracing is desired, use the TRACE
terminated - lock conflict. ENABLE and TRACE START commands to activate
server tracing.
Explanation: During the indicated operation, the
server needs to obtain a lock that is not available.
ANR0924E Tracing is already active to file file spec.
System action: The indicated operation ends.
Explanation: A TRACE BEGIN command has been
User response: Restart the operation. entered, but tracing is already active to the file named.
ANR0919E Filespace name fsName with length
length was encountered for nodes node User response: If the current trace output file is
list. acceptable, no action is required. Otherwise use the
TRACE END command to stop tracing and then reissue
Explanation: The specified filespace name was found the TRACE BEGIN command as desired.
for the nodes in the list. The name is not allowed. The
error may occur while processing an administrative
command or client request. ANR0925E Tracing is already active to standard
output.
Explanation: A TRACE BEGIN command has been
User response: If the error occurs during processing entered, but tracing is already active to the standard
for an administrative command such as EXPORT output destination (usually the server console).
NODE or RENAME FILESPACE, rename the filespace
for the nodes in the list using a valid name. If found System action: The command is ignored.
while processing a client request, contact your service User response: If the current trace output destination
representative. is acceptable, no action is required. Otherwise use the
TRACE END command to stop tracing and then reissue
ANR0920I Tracing is now active to standard the TRACE BEGIN command as desired.
output.
Explanation: In response to a TRACE START ANR0926E Missing or invalid TRACE command
command, server trace records are being written to the parameter.
standard output destination (usually the server Explanation: The TRACE command issued contains
console). an invalid parameter, or is missing a required
System action: None. parameter.
ANR0927E ANR0942E
User response: Reissue the command with the proper

ANR0937I Expiration process process ID is ending.
parameters.
Explanation: The expiration process referenced is
ending either because it has been cancelled or because
ANR0927E Unknown trace class keyword - class.
it has completed the necessary actions. This message is
Explanation: A TRACE ENABLE command has been only issued in the case where expiration was processing
entered which specifies an unknown trace class. a long-running operation, such as deleting a group of
related files (for example, a backup group). This
System action: The command is ignored. message indicates the time when the long-running
User response: Reissue the TRACE command with the operation ended.
correct class. System action: None.
ANR0928E Unable to open trace file file spec for
appending.
ANR0939E Error error code occurred while locating
Explanation: A TRACE BEGIN command specifies an base object (baseId) for subfile (subfileId):
output file, but the server cannot write to that file. Node node name, File space filespace name,
System action: The command is ignored. Type file type, File name file name.
User response: Check the file for proper access Explanation: Export processing did not find the base
permissions, or reissue the TRACE command object for the specified subfile. Export processing does
specifying a different output file. not continue.
System action: Export processing stops. Server
ANR0929E Insufficient memory to activate tracing. operation continues.
Explanation: A TRACE BEGIN command has been User response: Audit the database to correct the
entered, but the server has insufficient memory entries.
available to activate tracing.
System action: The command is ignored. ANR0940I Cancel request accepted for process
process ID.
User response: If tracing is required, make more
memory available to the server then restart the server. Explanation: A CANCEL PROCESS command has
been entered for the specified process. Some processes
will experience a delay before they terminate. This
ANR0936E Session session ID for session name failed delay may be lengthy for processes that involve remote
sending verb verb name because client data movement.
not able to handle extended qualifier
attribute. System action: None.
Explanation: A server was going to send the reported User response: None.
verb for the indicated session but was not able to send
it. The verb could not be sent to the client because it ANR0941I Command: Cancel for process process ID
contains extended information about the low-level is already pending.
qualifier. The extended low-level qualifier is used to
store names up to 512 bytes in length. The client that Explanation: A CANCEL PROCESS command has
this verb was supposed to be sent to does not support been entered for the specified process, but a cancel is
the extented low-level qualifier information. already pending for that process.
System action: The send of the verb to the reported System action: The server ignores the command.
session fails and this server operation will fail and
report a communication error.
User response: The client session reported needs to
ANR0942E Command: Process process ID cannot be
have the installed client upgraded to TSM version 5.1.5
found.
or higher in order to support the extended low-level
qualifier. Explanation: A CANCEL PROCESS command has
been entered for the specified process, but the process
is not active. Either the process has already ended or
the wrong process number has been entered.
System action: The server ignores the command.
User response: If the wrong process number has been

ANR0943E ANR0955I
entered, reissue the command with the correct process

ANR0947E Error writing to trace file file spec.
number.
Explanation: An error occurred while writing to the
specified trace file.
ANR0943E Command: Process process ID could not be
canceled. System action: Trace is disabled.
Explanation: A CANCEL PROCESS command has User response: Check the file for proper access
been entered for the specified process, but the process permissions, or for the out of space issue for the trace
specified is an automatic process, such as migration or file. Once this is corrected, reissue the TRACE BEGIN
reclamation, that cannot be canceled. command, specifying either the same or a different
output file.
User response: If the process is a REPLICATE NODE
ANR0952W The filespace Filespace name cannot be
process and is on the target server, it cannot be
included in the backup set because it
canceled if the process is in progress and the source
contains encrypted data.
server is available. The target server monitors
communications with the source server. If 5 minutes Explanation: Data from the filespace cannot be
have expired since the last communications, the target included in the backup set because the filespace
server assumes that the source server is no longer contains encrypted data.
available, and the process is canceled. To view the
System action: The filespace is skipped.
length of time during which the process has been idle,
issue the QUERY PROCESS command and specify the User response: None.
process ID for the replication process.
ANR0953W Audit command: Redundant encryption

ANR0944E Command: No active processes found. keys for the archive object (object.ID) do
not match.
Explanation: A QUERY PROCESS command has been
entered, and no processes are active. Explanation: The encryption key stored for the archive
object in the Object.Ids table does not match the
encryption key stored in the Archive.Objects table. The
User response: None. audit command is not able to determine which key is
the correct key.
ANR0945W Diagnostic(ID): Transaction transaction ID System action: The object's encryption keys are not
was aborted for process process ID. modified.
Explanation: An error is detected during transaction User response: Contact your service representative.
commit for the specified process. This message should
be preceded by other messages that give additional
ANR0954W Audit command: Redundant encryption
information about the failed transaction.
keys for the backup object (object.ID) do
System action: The activity that generated this error not match.
fails.
Explanation: The encryption key stored for the backup
User response: Check for additional messages and object in the Object.Ids table does not match the
eliminate the condition that caused the failed encryption key stored in the Backup.Objects table. The
transaction. If the error cannot be isolated and resolved, audit command is not able to determine which key is
contact your service representative. the correct key.
System action: The object's encryption keys are not
ANR0946E Archive processing fails: Object objId not modified.
found.
Explanation: Archive processing fails because the
specified object was not found. An archive request is
completed in stages. The object may have been deleted
node node name failed deletion because
by an archive delete request, delete filespace or
of a restartable restore session.
expiration that began and completed between these
stages. Explanation: The reported node and filespace have a
restartable restore session active or restartable. A
System action: System processing continues.
filespace cannot be deleted while the restartable restore
User response: Check the client log for error and retry session exists.
messages. Reissue the archive request if the retry failed.
System action: The server process is retried if the
ANR0956I ANR0964I
maximum number of retry attempts have not been

ANR0959I Conversion of grouping table is percent
exceeded.
done percent complete.
User response: Use the QUERY RESTORE command
Explanation: An internal data base table is being
to view active and restartable restores sessions for this
converted, and the conversion process is the indicated
filespace. Either wait for the sessions to complete or
amount complete.
cancel the sessions with the CANCEL RESTORE
command, and reissue the DELETE FILESPACE System action: Server processing continues.
command. To view restartable restore sessions issue the
command QUERY RESTORE. Either:
v wait to reissue the DELETE FILESPACE command
after this restartable restore has completed ANR0960I Process process ID waiting for mount
point in device class device class name.
v cancel the restartable restore session with the
CANCEL RESTORE command Explanation: The process whose ID is shown has
begun to wait for a mount point that can be used for a
volume in the device class shown.
ANR0956I Audit command: Active version for
inactive inventory object (object.ID) does System action: The process waits for the mount point.
not exist. The expiring object entry must
be corrected. User response: Respond to any mount requests.
Explanation: A database audit process found an

expiring object entry for an inactive inventory object ANR0961I Process process ID waiting for multiple
that indicates an active version of the object exists, but mount points in device class device class
the active version does not exist. Because FIX=NO has name.
been specified for the command, the expiring object Explanation: The process whose ID is shown has
entry is not corrected. begun to wait for multiple mount points that can be
System action: Audit processing continues. used for a volume in the device class shown.
User response: None. System action: The process waits for the mount
points.
ANR0957I Audit command: Active version for User response: Respond to any mount requests.
inactive inventory object (object.ID) does
not exist. The expiring object entry will ANR0962I Process process ID waiting for mount
be corrected. points in device classes device class name
Explanation: A database audit process found an and device class name.
expiring object entry for an inactive inventory object Explanation: The process whose ID is shown has
that indicates an active version of the object exists, but begun to wait for mount points that can be used for a
the active version does not exist. Because FIX=YES has volume in the two device classes shown.
been specified for the command, the expiring object
entry will be corrected. System action: The process waits for the mount
points.
System action: Audit processing continues.
User response: Respond to any mount requests.
ANR0963I Process process ID waiting for mount of

ANR0958I CLEANUP BACKUPGROUPS evaluated input volume volume name.
objectcount group objects, found
errorcount errors, and deleted deleted Explanation: The process whose ID is shown has
group objects with completion state begun to wait for the mount of the input volume
state. shown.
Explanation: The CLEANUP BACKUPGROUPS utility System action: The process waits for the mount.
ended with the presented state. User response: Respond to any mount requests.
User response: None. ANR0964I Process process ID waiting for mount of
output volume volume name.
Explanation: The process whose ID is shown has
begun to wait for the mount of the output volume
shown.

ANR0965I ANR0982E
System action: The process waits for the mount.

ANR0980E The server database must be audited
User response: Respond to any mount requests. with FIX=YES before the server can be
started.
ANR0965I Process process ID waiting for mount of Explanation: The server has been restarted after a
scratch volume. DSMSERV LOADDB command processed a database
image that was known to have inconsistencies. In order
Explanation: The process whose ID is shown has to bring the database back to a consistent state, you
begun to wait for the mount of a scratch volume. must run the AUDITDB command.
System action: The process waits for the mount. System action: Server initialization stops.
User response: Respond to any mount requests. User response: Issue the DSMSERV AUDITDB
FIX=YES command. For complete details on this
ANR0966I Process process ID waiting for access to command, refer to the Administrators Reference.
input volume volume name.
Explanation: The process whose ID is shown has ANR0981E The server database must be restored
begun to wait for availability of the input volume before the server can be started.
shown. Explanation: This message is issued in one of two
System action: The process waits for the volume to cases: 1) The server has been restarted after an
become available. incomplete RESTORE DB. In order to start the server,
you must restore the database to a consistent state
User response: None. using the DSMSERV RESTORE DB command; 2)
During server operation, an error condition occurred
ANR0967I Process process ID waiting for access to such that the TSM server cannot continue. This
output volume volume name. message is issued, and the server halts. Before you can
start the server again, you need to use the DSMSERV
Explanation: The process whose ID is shown has RESTORE DB command to restore the database.
begun to wait for availability of the output volume
shown. System action: Server initialization stops, or the server
stops.
System action: The process waits for the volume to
become available. User response: If there are other messages issued with
this error message which have instructions associated
User response: None. with them, follow the instructions in those messages.
Then issue the DSMSERV RESTORE DB command. For
ANR0969E The server database must be formatted complete details on this command, refer to the
and loaded or restored before the server Administrators Reference. After the DSMSERV RESTORE
can be started. DB command completes successfully, restart the TSM
server.
Explanation: The server has been restarted after
toleration of a zero bit mismatch error. In order to start
the server, you must recover the database with a ANR0982E The server database must be initialized
process that includes a DSMSERV FORMAT. Perform before the database can be loaded.
one of the following procedures. Either do these steps: Explanation: The server database must be initialized
1. Format the volumes using DSMSERV FORMAT before it can be loaded with the LOADDB parameter,
2. Restore the database using DSMSERV RESTORE DB by issuing the DSMSERV LOADFORMAT command.
The server database is not currently in the initialized
Or do these steps: state.
1. Unload the database using DSMSERV UNLOADDB System action: Server LOADDB processing stops.
2. Format the volumes using DSMSERV FORMAT
User response: Issue the DSMSERV LOADFORMAT
3. Load the database using DSMSERV LOADDDB command. For complete details on this command, refer
Note: Do not use DSMSERV DUMPDB on the database to the Administrators Reference.
for this recovery.
System action: Server initialization stops.
User response: Perform one of the database recovery
actions.
ANR0983W ANR0988I
ANR0983W The server database was recorded by a ANR0986I Process process ID for process name
down-level version of the server running in the process state processed
program. The UPGRADEDB parameter items processed items for a total of bytes
is required to start the server and processed bytes with a completion state
automatically upgrade the database of completion state at process start time.
contents to the current server version.
Explanation: A completion state of FAILURE indicates
Please refer to installation instructions
that the operation encountered an error condition or
for precautionary backup procedures
terminated before completion. A completion state of
prior to doing this.
SUCCESS indicates that the operation ran to
Explanation: At server startup, the server has completion, but in some situations may have
discovered that the database information was written encountered and reported conditions that would affect
by an earlier version of the server program and is not the outcome of the operation.
compatible with this version. To automatically upgrade
the server database to this version of the server
program, the UPGRADEDB parameter must be User response: If the completion state is FAILURE,
specified when starting the server. then review the activity log and the event log to try to
determine the cause of the failure. If the completion
System action: The server ends.
state is SUCCESS, the activity log and the event log can
User response: Refer to installation instructions for still be checked for warning messages regarding
specific information on precautionary measures that conditions that could have affected the operation.
you may want to take to back up the database prior to
upgrading it to the current server level. After you have
ANR0987I Process process ID for process name
taken these measures, start the server and specify the
running in the process state processed
UPGRADEDB parameter. This parameter only needs to
items processed items with a completion
be specified once to start the server, and should NOT
state of completion state at process start
be included in any automated programs that start the
time.
server.
ANR0984I Process process ID for process name started
in the process state at process start time.
Explanation: The process whose ID is shown has been completion, but in some situations may have
started for the process indicated by the process name encountered and reported conditions that would affect
running in the indicated state. the outcome of the operation.
System action: None. System action: None.
User response: None. 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
running in the process state completed
still be checked for warning messages regarding
with completion state completion state at
conditions that could have affected the operation.
process start time.
running in the process state processed
bytes processed bytes with a completion
state of completion state at process start
completion, but in some situations may have
time.
encountered and reported conditions that would affect
the outcome of the operation. Explanation: A completion state of FAILURE indicates
User response: If the completion state is FAILURE, SUCCESS indicates that the operation ran to
then review the activity log and the event log to try to completion, but in some situations may have
determine the cause of the failure. If the completion encountered and reported conditions that would affect
state is SUCCESS, the activity log and the event log can the outcome of the operation.
User response: If the completion state is FAILURE,
then review the activity log and the event log to try to

ANR0989E ANR1000I
determine the cause of the failure. If the completion User response: None.
ANR0994W This server has not been properly
installed.
Explanation: The server was started for normal
ANR0989E The server database must be inserted or
operation, but had not yet been installed.
restored before the server can be started.
Explanation: The server is restarted after the
LOADFORMAT command is run. To start the server, User response: Install the server properly before
you must upgrade the database by issuing DSMSERV starting it.
INSERTDB or else the database needs to be restored
using the DSMSERV RESTORE DB command.
ANR0995W This version of the server program is
System action: Server initialization stops. down-level with respect to the
information recorded on disk; a newer
User response: Issue the DSMSERV INSERTDB or
version of the program should be used.
DSMSERV RESTORE DB command. For complete
details on these commands, refer to the Administrators Explanation: At server startup, the server has
Reference. Alternatively, the server can be installed using discovered that the disk information was written by a
the DSMSERV FORMAT command in order to prepare later version of the server program. This version of the
it for regular use without needing to upgrade an earlier server program should not be used.
version server with the DSMSERV INSERTDB
command or restoring the database with the DSMSERV System action: The server ends.
RESTORE DB command. User response: Start a version of the server program
that is at the same level as the prior server program
ANR0990I Server restart-recovery in progress. used.
Explanation: The server has been restarted after a halt

or system failure. If necessary, the server performs ANR0996W The information on disk was recorded
recovery processing in order to bring the system back by a down-level version of the server
to a consistent state. program; reinstallation is required to
use this version.
System action: Server initialization continues.
Explanation: At server startup, the server has
User response: None. discovered that the disk information was written by an
earlier version of the server program and is not
compatible with this version.
ANR0991I server shutdown complete.
Explanation: In response to a HALT command, the
server or storage agent has completed its termination User response: Install this version of the server to
processing. bring the information up to the level of the program
being used.
System action: The server or storage agent ends.
ANR1000I Migration process process ID started for
storage pool storage pool name
ANR0992I Server's database formatting complete. automatically or manually,
highMig=highMig value, lowMig=lowMig
Explanation: The server formatting procedure has
value, duration=duration.
completed successfully. The server is now available for
normal operation. Explanation: Because the high migration threshold for
the storage pool shown has been exceeded, a process
System action: Server completes formatting
has been started to migrate files from the storage pool.
processing.
Note: a duration value of No means that the duration
User response: None. is not specified and hence the migration runs without
duration.
ANR0993I Server initialization complete. System action: Data is moved from this storage pool
to the next (target) pool.
Explanation: The server has been restarted after a halt
or system failure. It is now ready to resume normal User response: None.
operation.
System action: Server completes initialization.
ANR1001I ANR1014W
ANR1001I Migration process process ID ended for ANR1013I During a store operation, the server is
storage pool storage pool name. switching to a next pool in the storage
hierarchy. The next storage pool will
Explanation: A migration process for the named
inherit the simultaneous write
storage pool ends. This action can occur because the
configuration from the destination
low migration threshold for the storage pool has been
primary storage pool.
reached, there are no more nodes with files to be
migrated, there are no more volumes to be migrated, or Explanation: If during a backup, archive, client
the duration specified has been reached. migration, or server import operation, the server must
write data to a next pool in a storage pool hierarchy,
the following rules will apply:
User response: None. 1. If the destination storage pool specified in the
management class copy group has one or more
ANR1002I Migration for storage pool storage pool copy storage pools associated with it for
name will be retried in number of seconds simultaneous write operations:
seconds. a. The server will write the data to the next storage
pool and to the copy pools that are associated
Explanation: Because of a problem encountered with the original destination primary storage
attempting migration for the named storage pool, pool.
migration is delayed but will be retried after the time
period shown. b. The setting of the COPYCONTINUE attribute of
the original destination primary pool will be
System action: The server waits for the specified inherited by the next pool.
period and then retries migration for the storage pool. c. If the next pool is configured for simultaneous
This delay applies to a single migration process. After a write operations, the copy storage pools
number of unsuccessful retries, the server will associated with the next pool will be ignored as
automatically cancel the process. If other migration well as the value of its COPYCONTINUE
processes are executing for the named storage pool, attribute.
these processes will continue migration.
2. If the primary storage pool specified in the
User response: If possible, correct the condition that management class copy group does not have copy
has caused delayed migration. pools associated with it for simultaneous write
operations:
ANR1003I Migration retry delay ended; checking a. The server will write the data to the next storage
migration status for storage pool storage pool.
pool name. b. If the next pool is configured for simultaneous
write operations, the copy pools associated with
Explanation: Because migration for the indicated
the next pool will be ignored.
storage pool had been delayed due to a problem, the
system waited before retrying. The retry wait period System action: The server operation continues.
has ended, and the system will now retry migration.
User response: None. Refer to the Administrators
System action: Migration processing for the storage Guide for details about simultaneous write
pool resumes. configurations.
ANR1014W The pool type storage pool pool name is
either not available, or does not have
ANR1004I Server formatting complete, database
enough space for a simultaneous write
ready for loading.
operation.
Explanation: The server formatting procedure has
Explanation: During a backup, archive, client
completed successfully. The server is ready to be
migration, or import operation that is using
loaded by issuing the DSMSERV LOADDB or the
simultaneous write, the server cannot write data to the
DSMSERV RESTORE DB command.
specified storage pool. Possible reasons include:
System action: Server completes formatting v The storage pool is unavailable.
processing.
v There is not enough space available in the specified
User response: The DSMSERV LOADDB or the storage pool.
DSMSERV RESTORE DB command is required to load
System action: The result of the simultaneous write
the database before the server will be ready for use. For
operation depends on the setting of the
complete details on these commands, refer to the
COPYCONTINUE attribute of the original destination
Administrators Reference.
primary pool destination:

ANR1015I ANR1022W
v If the value of the COPYCONTINUE attribute of the started for the storage pool shown.
destination primary pool is YES, the server will stop
writing to the failing copy pool for the remainder of
the session, but continue storing files into a primary User response: None.
pool in the storage hierarchy and any other
remaining copy pools.
ANR1019W Unable to get the node attributes for
v If the value of the COPYCONTINUE attribute of the node name.
destination primary pool is NO, the server will fail
the transaction and discontinue the operation. Explanation: The HBAAPI function cannot obtain the
node's attributes. Removing devices from the SAN
Refer to the Administrators Guide for details about the without reconfiguring the system can cause this
simultaneous write COPYCONTINUE attribute. problem.
User response: Ensure the copy storage pool is set for System action: None.
READWRITE access. If needed, make more space
available in the copy storage pool. After the problem is User response: SAN discovery is not working for this
corrected, take one of the following actions: device. Check the device configuration on the system.
v If the value of the COPYCONTINUE attribute of the
destination primary pool is YES, issue the BACKUP ANR1020W Migration process process ID terminated
STGPOOL commands to back up any files in for storage pool storage pool name -
primary storage pools in the storage pool hierarchy process canceled.
that have not been copied to the copy pool that
failed. Explanation: During migration for the indicated
storage pool, a process performing the migration has
v If the value of the COPYCONTINUE attribute of the
been canceled.
destination primary pool is NO, run the
simultaneous write operation again. System action: The migration process is terminated. If
other migration processes are executing for the named
storage pool, these processes will continue migration.
ANR1015I Storage pool pool name has pending bytes
duplicate bytes pending removal. User response: None.
Explanation: The number of bytes indicated have been
identified as duplicate bytes in the storage pool, but the ANR1021W Migration process process ID terminated
volumes on which the data resides have not yet been for storage pool storage pool name -
reclaimed. storage media inaccessible.
System action: None Explanation: During migration for the indicated
storage pool, a required volume could not be mounted.
User response: None
System action: The indicated migration process ends.
The server waits for the retry period to expire and then
ANR1016W Fibre Channel adapters on the system
tries the migration again. If other migration processes
cannot be opened.
are executing for the named storage pool, these
Explanation: Due to problems with the HBAAPI or processes will continue migration.
Fibre Channel HBA driver, the HBAAPI function
User response: One possible cause for this failure is
cannot open any Fibre Channel host bus adapters
that the access state for the target volume or storage
(HBAs) on the system.
pool for this operation is not set to READWRITE.
System action: None. Check the access state for the requested output volume
and storage pool and ensure they are set to
User response: The Tivoli Storage Manager SAN ACCESS=READWRITE.
discovery function is not working. Check your Fibre
Channel host bus adapter (HBA) vendor and upgrade
your HBAAPI or Fibre Channel HBA driver version. ANR1022W Migration process process ID terminated
For a list of supported HBAs and required driver levels for storage pool storage pool name -
by operating system, go to http://WWW.IBM.COM/ excessive read errors encountered.
SUPPORT and search for "supported HBAs".
Explanation: During migration for the indicated
storage pool, read errors occur that prevented the
ANR1018I Volume deduplication process process ID migration from continuing.
started for storage pool storage pool name,
identify processes=number of identify
processes.
Explanation: A volume deduplication process was are executing for the named storage pool, these
ANR1023W ANR1029W
processes will continue migration. storage pool, because a file is larger than what is
allowed on the next storage pool.
User response: If possible, correct the cause of the
read errors. System action: The indicated migration process ends.
ANR1023W Migration process process ID terminated
for storage pool storage pool name -
processes will continue migration.
excessive write errors encountered.
User response: Use the UPDATE STGPOOL command
to change the next storage pool maximum file size or to
storage pool, write errors occur that prevent the
change the next storage pool target.
migration from continuing.
sufficient recovery log space is not
available.
storage pool, the server runs out of recovery log space.
write errors.
tries the migration again.
for storage pool storage pool name - data
transfer interrupted. User response: If necessary, make more server
recovery log space available.
storage pool, a data transfer operation was interrupted
and could not be continued. ANR1028W Migration process process ID terminated
sufficient database space is not
available.
are executing for the named storage pool, these Explanation: During migration for the indicated
processes will continue migration. storage pool, the server runs out of database space.
User response: If possible, correct the cause of the System action: The indicated migration process ends.
interruption. The server waits for the retry period to expire and then
ANR1025W Migration process process ID terminated User response: If necessary, make more server
for storage pool storage pool name - database space available.
insufficient space in subordinate storage
pool.
Explanation: During migration for the indicated for storage pool storage pool name - lock
storage pool, the server cannot move the data from the conflict.
storage pool, because there is not enough space on the
next storage pool to hold it.
storage pool, the server needs to obtain a lock that is
System action: The indicated migration process ends. not available.
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.
storage pool, the server cannot move the data from the

ANR1030W ANR1042I
User response: Check for additional messages and

eliminate the condition that caused the failed
for storage pool storage pool name - thread
transaction.
resource not available.
ANR1034W Files stored on volume volume name
storage pool, the server cannot start a thread for the
cannot be migrated - volume is offline
migration process.
or access mode is "unavailable" or
System action: The indicated migration process ends. "destroyed".
Explanation: During migration, files on the indicated
volume cannot be migrated either because the volume
has been varied offline or because of the volumes
access mode.
User response: Wait for the server to retry the
System action: The server continues migration
migration. If the error persists, it may indicate a
processing, but skips files stored on the indicated
shortage of server memory.
volume.
User response: If necessary, use the VARY ON or
UPDATE VOLUME command for this volume.
ANR1040I Space reclamation started for volume
volume name, storage pool storage pool
storage pool, there is not enough server memory
name (process number process ID).
available.
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
the volume is moved to another volume so that the
User response: If necessary, make more memory volume can be reclaimed.
available to the server.
System action: The server starts volume space
reclamation.
internal server error detected.
ANR1041I Space reclamation ended for volume
volume name.
storage pool, the server encounters an internal error.
Explanation: Space reclamation for the volume named
is complete.
tries the migration again. If other migration processes System action: None.
processes will continue migration. User response: None.

ANR1042I Space reclamation for storage pool
storage pool name will be retried in
ANR1033W Migration process process ID terminated number of seconds seconds.
transaction aborted. Explanation: Because of a problem encountered
attempting space reclamation for the named storage
Explanation: During migration for the indicated pool, reclamation stops but will be retried after the
storage pool, the server detected an error while time period shown. After a number of unsuccessful
attempting to commit a transaction. This message retries, the process will be automatically cancelled.
should be preceded by other messages that give
additional information about the failed transaction. System action: The system waits for the specified
period and then retries space reclamation for the
System action: The indicated migration process ends. storage pool.
tries the migration again. If other migration processes User response: If possible, correct the condition that
are executing for the named storage pool, these has stopped reclamation.
ANR1043I ANR1049W
ANR1043I Space reclamation retry delay ended; ANR1047E command: Database upgrade not
checking volume reclamation status for currently supported for this server
storage pool storage pool name. because it uses NAS backups with
TOCs.
Explanation: Because space reclamation for the
indicated storage pool had been stopped due to a Explanation: The current version of the TSM 6.1
problem, the system waited before retrying. The retry server does not support NAS backups that use a table
wait period has ended, and the system can now retry of contents (TOC). However, the server being upgraded
space reclamation. uses TOCs, and so cannot be upgraded at this time.
Note that this is a temporary limitation that will be
System action: Reclamation for the pool begins.
lifted in a future TSM 6.1 Server Fix Pack.
System action: The command ends without inserting
any data into the database.
ANR1044I Removable volume volume name is
User response: Rerun the command using a version of
required for space reclamation.
the TSM 6.1 server that supports NAS backups with
Explanation: During space reclamation processing, the TOCs.
server determines that a removable volume is required
in order to complete processing.
ANR1048E command: Protocol error -
System action: The server attempts to mount the out-of-sequence verb (type verb name)
removable volume. received.
User response: Respond to any mount request for the Explanation: The server detects a protocol error while
indicated volume. upgrading the database because a verb has been
received that does not adhere to the defined verb
sequence. This error may be the result of using a
ANR1045E Reclamation has ended for volume version of the DSMUPGRD utility that is not
volume name. The files on the volume are compatible with the TSM 6.1 version to which you are
too large for the target storage pool, upgrading.
storage pool name.
System action: The command ends without inserting
Explanation: During reclamation for the indicated any data into the database.
volume, the server cannot move the data from the
volume because a file is larger than allowed for the User response: Rerun the command using a version of
indicated storage pool. the server compatible with the version of DSMUPGRD
used to extract the data. Or reextract the data using an
System action: Reclamation of the volume stops. If older version of DSMUPGRD that is compatible with
other reclamation processes are running, these the version of the server.
processes will continue the reclamation.
User response: Use the UPDATE STGPOOL command ANR1049W The server is unable to obtain
to change the value of the MAXSIZE parameter for the number-formatting information from the
storage pool. Specify the value as NOLIMIT, or specify system-locale attributes. The server
a value larger than the largest file to be reclaimed. substitutes alternate number format
nmbrFmt.
ANR1046E command: Database upgrade not Explanation: The server is unable to format some
currently supported for this server numbers because it is unable to obtain a valid thousand
because it uses backup sets. and decimal separator value from the system locale.
Explanation: The current version of the TSM 6.1 System action: The server continues. An alternate
server does not support backup sets. However, the number format is used. Numbers are displayed using a
server being upgraded uses backup sets, and so cannot comma character as the thousand separator and a
be upgraded at this time. Note that this is a temporary period character as the decimal separator.
limitation that will be lifted in a future TSM 6.1 Server
Fix Pack. User response: Check whether errors occurred during
server initialization that might indicatea problem
System action: The command ends without inserting initializing the locale . Check whether the server is
any data into the database. 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 TSM 6.1 server that supports backup sets.

ANR1053E ANR1061W
Reference for your particular platform.

ANR1053E Command: Invalid process number -
processIdvalue
ANR1058E command name: TODATE must be
Explanation: A QUERY EXPORT command was
specified when TOTIME is specified.
issued that specifies an invalid process number.
Explanation: A command supporting the TODATE
and TOTIME parameters was issued with the TOTIME
command.
parameter specified but without the TODATE
User response: Reissue the command with a valid parameter. When the TOTIME parameter is used, the
process number. TODATE parameter must be specified.
System action: The server ignores the command and
ANR1054E Command: Invalid export operation state continues processing.
- export state
User response: Reissue the command and specify both
Explanation: A QUERY EXPORT command was the TODATE and TOTIME parameters.
issued that specifies an invalid export state.
System action: The server does not process the ANR1059I Selective restore of NAS node nodename,
command. file system file system, started as process
process ID by administrator administrator.
Specified files and/or directory trees
export operation state.
will be restored to destination
destination.
ANR1055E Command: Invalid export session
Explanation: A restore is started for the indicated file
identifier name - export sess name.
system of a NAS node. The operation is initiated by the
Explanation: The issued command specifies an invalid administrator shown. Selected files and/or directory
export session identifier. trees specified by the administrator will be restored to
the indicated destination.
command. System action: The indicated process is started.
User response: Reissue the command with a valid User response: None.
export session identifier.
ANR1060W Error initiating space reclamation for
ANR1056E command name: The PROCESS parameter storage pool storage pool name - lock
is not valid if an export identifier is conflict.
specified.
Explanation: While attempting to initiate space
Explanation: The command failed because of an reclamation for the indicated storage pool, the server
invalid combination of arguments. needs to obtain a lock that is not available.
System action: The command fails and server System action: Space reclamation stops. The server
operations continue. waits for the retry period to expire and then tries the
reclamation again.
User response: Reissue the command with a valid set
of parameters. For information on valid values for the User response: Wait for the server to retry the
command parameter, refer to the Administrators reclamation.
ANR1057E command name: The PROCESS parameter storage pool storage pool name - sufficient
is not valid when the STATE parameter memory is not available.
is specified with a value of
Explanation: During an attempt to initiate space
INITIALIZING or SUSPENDED
reclamation for the indicated storage pool, there is not
Explanation: The command failed because of an enough server memory available.
invalid combination of arguments.
System action: Space reclamation stops. The server
System action: The command fails and server waits for the retry period to expire and then tries the
operations continue. reclamation again.
User response: Reissue the command with a valid set User response: If necessary, make more memory
of parameters. For information on valid values for the available to the server.
command parameter, refer to the Administrators
ANR1062W ANR1071E
Explanation: A restore is started for the indicated file

system of a NAS node. The operation is initiated by the
storage pool storage pool name - internal
administrator shown. The restore will be performed
server error detected.
using a full image plus a differential image of this file
Explanation: During an attempt to initiate space system. The file system will be restored to the indicated
reclamation for the indicated storage pool, an internal destination.
server error is encountered.
System action: The indicated process is started.
System action: Space reclamation stops. The server
will wait for the retry period to expire and then tries
the reclamation again.
ANR1067I Operation process process ID completed.
Explanation: The indicated operation completed.
ANR1063I Full backup of NAS node nodename, file System action: The indicated process ends.
system file system, started as process
process ID by administrator administrator. User response: None.
Explanation: A full backup is started for the indicated

file system of a NAS node. The operation is initiated by ANR1068W Operation process process ID terminated -
the administrator shown. process cancelled.
System action: The indicated process is started. Explanation: During the indicated operation, a
background process was cancelled.
System action: The indicated process ends.
ANR1064I Differential backup of NAS node User response: None.

nodename, file system file system, started
as process process ID by administrator ANR1069E Operation process process ID terminated -
administrator. insufficient number of mount points
Explanation: A differential backup is started for the available for removable media.
indicated file system of a NAS node. Only files that Explanation: During the indicated operation, the
have changed since the last full backup will be server could not allocate sufficient mount points for the
processed. The operation is initiated by the volumes required.
administrator shown.
User response: None. available.
ANR1065I Restore of NAS node nodename, file ANR1070E Operation process process ID terminated -
system file system, started as process write errors encountered.
A full image for this file system will be Explanation: During the indicated operation, write
restored to destination destination. errors prevent the operation from continuing.
Explanation: A restore is started for the indicated file System action: The indicated process ends.
system of a NAS node. The operation is initiated by the User response: If possible, correct the cause of the
administrator shown. The restore will be performed errors and restart the operation.
using a full image of this file system. The file system
will be restored to the indicated destination.
ANR1071E Operation process process ID terminated -
System action: The indicated process is started. read errors encountered.
User response: None. Explanation: During the indicated operation, read
errors prevent the operation from continuing.
ANR1066I Restore of NAS node nodename, file System action: The indicated process ends.
system file system, started as process
process ID by administrator administrator. User response: If possible, correct the cause of the
A full image plus a differential image errors and restart the operation.
for this file system will be restored to
destination destination.

ANR1072E ANR1082E
messages that give additional information about the

failed transaction.
insufficient space in destination storage
pool. System action: The indicated process ends.
Explanation: During the indicated operation, there is User response: Check for additional messages and
not enough space available in the destination storage eliminate the condition that caused the failed
pool. transaction.
User response: Make more space available in the
storage pool and restart the operation.
server encounters an internal error.
sufficient recovery log space is not System action: The indicated process ends.
available.
server runs out of recovery log space.
ANR1079I Server-free backup of node nodename,
System action: The indicated process ends. file system file system, started as process
User response: If necessary, make more server
recovery log space available. Explanation: The administrator initiates a server-free
backup of the node's file system.
ANR1074E Operation process process ID terminated - System action: The indicated process is started.
available. User response: None.

server runs out of database space. ANR1080W Space reclamation is ended for volume
volume name. The process is canceled.
Explanation: During space reclamation for the
User response: If necessary, make more server indicated volume, the process performing the
database space available. reclamation has been canceled.
System action: Space reclamation of the volume stops.
ANR1075E Operation process process ID terminated - If other reclamation processes are running, these
lock conflict. processes will continue the reclamation.
Explanation: During the indicated operation, the User response: None.
server needs to obtain a lock that is not available.
System action: The indicated process ends. ANR1081E Space reclamation is ended for volume
volume name. Storage media is
User response: Restart the operation.
inaccessible.
indicated volume, a required volume cannot be
mounted.
Explanation: During the indicated operation, not
enough server memory is available.
If other reclamation processes are executing, these
System action: The indicated process ends. processes will continue the reclamation.
User response: If necessary, make more memory User response: None.
available to the server, and then restart the operation.
ANR1082E Space reclamation is ended for volume
ANR1077E Operation process process ID terminated - volume name. There is an insufficient
transaction aborted. number of mount points available for
removable media.
server detected an error while attempting to commit a Explanation: During space reclamation for the
transaction. This message should be preceded by other indicated volume, the server could not allocate
sufficient mount points for the volumes required.
ANR1083E ANR1090E
System action: Space reclamation of the volume stops. User response: Make more space available on other
If other reclamation processes are running, these volumes in the storage pool. If necessary, define the
processes will continue the reclamation. next storage pool.
available. ANR1087E Space reclamation is ended for volume
volume name. Sufficient recovery log
space is not available.
volume name. Excessive read errors were Explanation: During space reclamation for the
encountered. indicated volume, the server runs out of recovery log
space.
indicated volume, read errors occur that prevent System action: Space reclamation stops.
reclamation from continuing.
System action: Space reclamation of the volume stops. recovery log space available.
If other reclamation processes are running, these
User response: If possible, determine and correct the volume name. Sufficient database space is
cause of the read errors. not available.
ANR1084E Space reclamation is ended for volume indicated volume, the server runs out of database
volume name. Excessive write errors were space.
encountered.
System action: Space reclamation stops.
indicated volume, write errors occur that prevent
database space available.
reclamation from continuing.
volume name. There is a lock conflict.
User response: If possible, determine and correct the
indicated volume, the server needed to obtain a lock
cause of the write errors.
that is not available.
volume name. Data transfer was
interrupted.
User response: Wait for the server to try the
reclamation again.
indicated volume, a data transfer operation has been
interrupted and cannot be continued.
volume name. Thread resource is not
available.
indicated volume, the server cannot start a thread for
cause of the interruption.
the reclamation process.
ANR1086E Space reclamation is complete for
volume volume name. The storage pool
has insufficient space.
User response: Wait for the server to try the
reclamation again. If the error persists, it might indicate
indicated volume, data could not be moved from the
a shortage of server memory.
volume due to insufficient space on other volumes in
the storage pool.
processes continue the reclamation.

ANR1091E ANR1096E
v The storage pool is a random-access storage pool and

this operation requires a sequential-access storage
volume name. Sufficient memory is not
pool
available.
v The storage pool is not a primary storage pool
v The storage pool has a NATIVE or NONBLOCK data
indicated volume, there was not enough server
format, which is not supported for this operation
memory available.
v The storage pool is not a NONBLOCK data format,
System action: Space reclamation of the volume stops. which is required for server-free operations
v The data format of the storage pool does not match
the data format of the data mover
User response: If necessary, make more memory
System action: The operation fails.
User response: This message usually indicates a
configuration problem with either the storage pool or
the policy. Ensure that the destination storage pool has
volume name. An internal server error
appropriate attributes, including data format, for this
was detected.
operation. Check the copy group of the assigned
Explanation: During space reclamation for the management class. If the destination is incorrect, either
indicated volume, the server encounters an internal assign a new management class, or change the
error. destination in the copy group and activate the changed
policy. Also, consider whether you must define a new
storage pool or data mover.
ANR1095E Data mover operation for node node
name and file space filespace name cannot
issued prior to this message to determine the source of
be started - an operation involving this
the error. Issue the QUERY ACTLOG command to view
node and file space is already in
the activity log and to look for messages that indicate
progress.
the source of the error. Correct any errors that might
have caused the space reclamation to fail and try the Explanation: A request has been made to use a data
operation again. mover to perform an operation involving the indicated
node and file space. The indicated file space was either
specified as the source for a backup operation or the
destination location for a restore operation. However, a
volume name. The transaction is ended.
data mover operation involving that node and file
Explanation: During space reclamation for the space is already in progress; the indicated file space is
indicated volume, the server detected an error while either the source for a currently running backup
attempting to commit a transaction. operation or is the destination for a currently running
restore operation. To avoid possible conflicts, the new
System action: Space reclamation of the volume stops. operation is not performed.
processes will continue the reclamation. System action: The operation fails.
User response: Check for additional messages and User response: Allow the current operation to
eliminate the condition that caused the failed complete before starting a new operation for this node
transaction. and file space.
ANR1094E Invalid destination storage pool storage ANR1096E Operation process process ID terminated -
pool name specified for storage of an storage media inaccessible.
object using data mover data mover.
Explanation: During the indicated operation, a
Explanation: While attempting to store an object using required volume cannot be mounted.
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: If possible, correct the problem and
is specified as the copy group destination of the restart the operation.
assigned management class.
This storage pool could be invalid for any of the
following reasons:
v The storage pool is not defined
ANR1097E ANR1106W
System action: The server attempts to mount the

removable volume.
data transfer interrupted.
User response: Respond to any mount request for the
Explanation: During the indicated operation, a data
indicated volume.
transfer operation is interrupted and cannot be
continued.
server-free input/output errors
User response: If possible, correct the problem and encountered.
restart the operation.
Explanation: During the indicated operation,
input/output errors were encountered which prevent
ANR1098E Operation process process ID terminated - the operation from continuing.
file deleted from data storage during
retrieval.
User response: Check previous messages for problem
Explanation: During the indicated operation, a file
determination information.
was deleted from data storage during retrieval.
User response: None. NAS datamover NAS datamover name
reported NDMP session errors.
ANR1099E Operation process process ID terminated - Explanation: During the indicated operation, the
thread resource not available. NDMP session with the NAS file server reported errors
which prevent the operation from continuing.
server cannot start a thread. System action: The indicated process ends.
System action: The indicated process ends. User response: For details about how to identify the
cause of the terminated NDMP operations, see the NAS
User response: The problem may indicate a shortage
file-server documentation. Check the NDMP logs for
of memory. If necessary, make more memory available
the NAS file server and, if possible, correct the cause of
to the server, and then restart the operation.
the errors and restart the operation.
ANR1100I Migration started for volume volume

ANR1106W An incorrect destination storage pool
name, storage pool storage pool name
storage pool name was specified for
(process number process ID).
storing a table of contents for an image.
Explanation: Because the high migration threshold for A table of contents will not be created
the indicated storage pool has been exceeded, for the image.
migration of files from the volume shown begins.
Explanation: While attempting to store an image
System action: The system moves the data from this object, the server determined that the indicated table of
volume to the next (target) pool. contents (TOC) destination storage pool was invalid.
The indicated storage pool is used because it is
User response: None. specified as the copy group TOC destination of the
ANR1101I Migration ended for volume volume This storage pool could be invalid for any of the
name. following reasons:
Explanation: Because the low migration threshold for v The storage pool is not defined
the indicated storage pool has been reached, migration v The storage pool is not a primary storage pool
of files from the indicated volume ends.
v The storage pool has a data format other than
System action: None. NATIVE or NONBLOCK
User response: None. System action: The operation continues because TOC
creation is preferred, but not required. A TOC will not
be created for the stored image object.
required for migration. User response: This message usually indicates a
configuration problem with either the storage pool or
Explanation: During migration processing, the server
the policy. Ensure that the TOC destination storage
determines that a removable volume is required in
pool has appropriate attributes, including data format.
order to complete processing.
Check the copy group of the assigned management

ANR1107E ANR1112W
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.
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 User response: This message indicates a configuration
NATIVE or NONBLOCK 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,
in the copy group and activate the changed policy. message number, was specified.
Explanation: A MSGSTACKTRACE ENABLE or
ANR1108W The server is unable to create a table of MSGSTACKTRACE DISABLE command has been
contents for node node name, file space entered that specifies an invalid message number.
file space in storage pool storage pool name. Messages must be between 3 and 8 digits. No letters
are allowed on message numbers.
Explanation: While attempting to create a table of
contents (TOC) for the specified node and file space in System action: The server does not process the
the indicated TOC destination pool, a failure occurred. command.
System action: The operation continues because TOC User response: Reissue the command with a valid
creation is preferred, but not required. A TOC will not message number.
be created for the stored image object.
User response: Look for previous messages giving a ANR1112W Command: No table of contents
specific reason for the failure. Take corrective action as destination storage pool available for
appropriate. backup set for node Node name (data
type data type). The table of contents
will not be created.
ANR1109W Command: A table of contents was
requested, but there is no table of Explanation: While preparing to create a table of
contents destination storage pool contents (TOC), the server determined that the TOC
specified. The table of contents will not destination storage pool is not specified in the backup
be created, but the operation continues. copy group for the assigned management class.
Explanation: While preparing to create a table of System action: The operation continues because TOC
contents (TOC), the server determined that the TOC creation is preferred, but not required. A TOC will not
destination storage pool is not specified in the backup be created.
copy group for the assigned management class. User response: This message indicates a configuration
System action: The operation continues because TOC problem with the policy. Either assign a new
ANR1113E ANR1120W
management class with appropriate attributes, or the retry period to expire and then tries the migration
correct the assigned management class by setting the again.
TOC destination in the backup copy group and
activating the changed policy.
ANR1113E Command: No table of contents

ANR1117W Error initiating migration for storage
destination storage pool available for
pool storage pool name - internal server
backup set for node Node name (data
error detected.
type data type). The backup set will not
be generated. Explanation: While trying to start migration for the
indicated storage pool, the server encounters an
Explanation: While preparing to create a table of
internal error.
contents (TOC), the server determined that the TOC
destination storage pool is not specified in the backup System action: Migration stops. The server waits for
copy group for the assigned management class. the retry period to expire and then tries the migration
again.
User response: This message indicates a configuration
problem with the policy. Either assign a new
management class with appropriate attributes, or ANR1118I Command: Table of contents successfully
correct the assigned management class by setting the generated for node Node name, backup
TOC destination in the backup copy group and set backup set name.
activating the changed policy. If a TOC is not required,
change the value of the TOC parameter on the Explanation: You requested a table of contents to be
command. generated for the specified backup set and data type.
The table of contents was successfully generated.
ANR1114E Command: No nodes or data types are System action: Server operation continues.
eligible for a backup set operation. User response: None.
Explanation: None of the specified nodes or data
types are eligible to be included in the backup set for ANR1119W Command: Table of contents already
the GENERATE BACKUPSET or DEFINE BACKUPSET exists for node Node name, backup set
command. backup set name (data type data type). The
System action: The operation fails. table of contents will not be created.
User response: Check previous messages for problem Explanation: You requested a table of contents to be
determination information. generated for the specified backup set and data type,
but the table of contents already exists.
ANR1115W Error initiating migration for storage System action: The server will not generate a table of
pool storage pool name - lock conflict. contents for this backup set and data type.
Explanation: While trying to start migration for the User response: If the specified backup set name and
indicated storage pool, the server needs to obtain a lock data type are not correct, re-issue the command with
that is not available. the correct parameters.
System action: Migration stops. The server waits for

the retry period to expire and then tries the migration ANR1120W Migration is ended for volume volume
again. name. The process is canceled.
User response: Wait for the server to retry the Explanation: During migration for the indicated
migration. volume, the process performing the migration has been
canceled.
ANR1116W Error initiating migration for storage System action: The migration process stops. If other
pool storage pool name - sufficient migration processes are running, these processes will
memory is not available. continue migration.
Explanation: While trying to start migration for the User response: None.
indicated storage pool, there is not enough server
memory available.

ANR1121E ANR1128E
ANR1121E Migration is ended for volume volume ANR1125E Migration is ended for volume volume
name - storage. Media is inaccessible. name. Data transfer is interrupted.
Explanation: During migration for the indicated Explanation: During migration for the indicated
volume a required volume cannot be mounted. volume a data transfer operation was interrupted and
could not be continued.
System action: Migration of the volume stops. If other
migration processes are running, these processes will System action: Migration of the volume stops. If other
continue migration. migration processes are running, these processes will
continue migration.
User response: One possible cause for this failure is
that the access state for the target volume or storage User response: If possible, determine and correct the
pool for this operation is not set to READWRITE. cause of the interruption.
Check the access state for the requested output volume
and storage pool and ensure they are set to
ANR1126E Migration is ended for volume volume
ACCESS=READWRITE.
name. There is insufficient space in
subordinate storage pools.
name. An insufficient number of mount
volume, the server cannot move the data from the
points are available for removable
volume because there is not enough space on the next
media.
storage pool, or the next storage pool is not defined.
volume the server could not allocate sufficient mount
migration processes are running, these processes will
points for the volumes required.
continue migration.
User response: Ensure that the next storage pool is
defined, and make more space available in the next
continue migration.
storage pool. Use the UPDATE STGPOOL command to
User response: If necessary, make more mount points change the next storage pool to one with more space.
available.
ANR1123E Migration is ended for volume volume name. - The server is unable to move
name. Excessive read errors were files to subordinate storage pools
encountered. because the files are too large.
Explanation: During migration for the indicated Explanation: During migration for the indicated
volume, read errors occurred that prevent the migration volume, the server cannot move the data from the
from continuing. volume because a file size is larger than allowed on the
next storage pool.
migration processes are running, these processes will System action: Migration of the volume stops. If other
continue migration. migration processes are running, these processes will
continue migration.
read errors. User response: Use the UPDATE STGPOOL command
to change the next storage pool maximum file size or to
change the next storage pool target.
name. Excessive write errors were
encountered. ANR1128E Migration is ended for volume volume
name. Sufficient recovery log space is
not available.
volume, write errors occurred that prevent the
migration from continuing. Explanation: During migration for the indicated
volume, the server runs out of recovery log space.
migration processes are running, these processes will System action: Migration stops.
continue migration.
User response: If possible, correct the cause of the recovery log space available.
write errors.
ANR1129E ANR1137E
ANR1129E Migration is ended for volume volume ANR1134E Migration is ended for storage pool
name. Sufficient database space is not storage pool name. There is an insufficient
available. number of mount points available for
removable media.
volume pool, the server runs out of database space. Explanation: During migration for the indicated
storage pool the server could not allocate sufficient
System action: Migration stops.
mount points in the next storage pool.
the retry period to expire and then tries the migration
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.
volume, the server detected an error while attempting
continue migration.
to commit a transaction.
User response: Wait for the server to try the migration
again.
continue migration.
name. A thread resource is not available.
Explanation: During migration for the indicated transaction.
volume, the server cannot start a thread for the
migration process.
ANR1136W Operation process process ID completed -
System action: Migration of the volume stops. If other There is no data to process for the
migration processes are running, these processes will differential backup of NAS node node
continue migration. name, file space file space.
User response: Wait for the server to try the migration Explanation: The NAS file server reported zero bytes
again. If the error persists, it might indicate a shortage stored at the conclusion of an NDMP backup of the
of server memory. specified file space. The command ends without
updating the server's database.
ANR1132E Migration is ended for volume volume System action: The indicated process ends.
name. Sufficient memory is not
available.
volume, there is not enough server memory available.
object excluded by size in destination
System action: Migration stops. storage pool and all successor pools.
User response: If necessary, make more memory Explanation: During the indicated operation, the size
available to the server. 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.
name. An internal server error is System action: The indicated process ends.
detected.
User response: Increase the maximum file size for one
Explanation: During migration for the indicated or more of the storage pools in the storage hierarchy to
volume, the server encounters an internal error. accommodate the file. An authorized administrator can
increase the MAXSIZE parameter by issuing the
System action: Migration of the volume stops. If other UPDATE STGPOOL command.
continue migration.

ANR1138I ANR1146W

ANR1138I entries were created for the no-query
restore with timestamp timestamp.
ANR1142I Moving data for collocation cluster
Explanation: The no-query restore operation identified
cluster number of total clusters on volume
by the timestamp now has the indicated number of
volume name.
entries in the Restore.Srvobj table. This no-query restore
operation continues to find restore candidates until the Explanation: As a result of a MOVE DATA command,
server issues message ANR1183I. data moves from the volume indicated to new volumes;
the message shows the total number of clusters (data
objects) on the volume and the current cluster being
User response: This informational message reports processed.
that the no-query restore operation is still searching for
candidates. You can cancel the restore operation by
issuing the CANCEL RESTORE or CANCEL SESSION User response: None.
command.
ANR1143W Move data process terminated for

ANR1139E The command name command failed volume volume name - process canceled.
because some data was missing.
Explanation: During move data processing for the
Explanation: An attempt to gather database statistics indicated volume, the process performing the move
from the database manager failed. This failure can data was canceled. It is possible that the server may
occur if either of these conditions is met: issue this message more than once while the server is
v The buffer pool monitor switch ending this process.
(DFT_MON_BUFPOOL) has been set to 'OFF.' The System action: The server ends the MOVE DATA
buffer pool monitor switch controls the collection of command.
database statistics.
v The file systems or drives are in a remote network. User response: None.
There might be a network problem causing the
server fail to collect the statistics of those volumes. ANR1144W Move data process terminated for
System action: The command fails, and the server volume volume name - storage media
operation continues. inaccessible.
User response: Take one of the following actions, and Explanation: During move data processing for the
then try running the QUERY DBSPACE command indicated volume, a required volume cannot be
again: mounted.
v Stop and restart the server. System action: The server ends the MOVE DATA
v Set the buffer pool monitor switch to 'ON' using this command.
DB2 command: 'db2 update dbm cfg using User response: None.
DFT_MON_BUFPOOL ON'.
v If you cannot obtain drive or file system statistics by
running operating system commands, fix the
volume volume name - insufficient
problem, then try running the command again.
number of mount points available for
removable media.
ANR1140I Move data process started for volume
volume name (process ID process ID).
indicated volume, the server could not allocate
Explanation: As a result of a MOVE DATA command, sufficient mount points for the volumes required.
a process begins to move data from the volume shown.
System action: The server ends the MOVE DATA
System action: The server moves all data from the command.
volume.
User response: None. available.
ANR1141I Move data process ended for volume ANR1146W Move data process terminated for
volume name. volume volume name - excessive read
errors encountered.
Explanation: The MOVE DATA command for the
volume shown completes. Explanation: During move data processing for the
ANR1147W ANR1153W
indicated volume, read errors occurred that prevented allowed on the next storage pool.
the move from continuing.
System action: The server ends the MOVE DATA or
System action: The server ends the MOVE DATA MOVE NODEDATA command.
command.
User response: Use the UPDATE STGPOOL command
User response: If possible, correct the cause of the to change the next storage pool maximum file size or to
read errors and then reissue the MOVE DATA change the next storage pool target, and then reissue
command. the MOVE DATA or MOVE NODEDATA command.
ANR1147W Move data process terminated for ANR1151W Move data process terminated for
volume volume name - excessive write volume volume name - sufficient recovery
errors encountered. log space is not available.
Explanation: During move data processing for the Explanation: During move data processing for the
indicated volume, write errors occurred that prevented indicated volume, the server runs out of recovery log
the move from continuing. space.
System action: The server ends the MOVE DATA System action: The server ends the MOVE DATA
command. command.
User response: If possible, correct the cause of the User response: If necessary, make more server
write errors and then reissue the MOVE DATA recovery log space available.
command.
ANR1148W Move data process terminated for volume volume name - sufficient database
volume volume name - data transfer space is not available.
interrupted.
Explanation: During move data processing for the indicated volume, the server runs out of database
indicated volume a data transfer operation was space.
interrupted and could not be continued.
System action: The server ends the MOVE DATA command.
command.
User response: If possible, determine and correct the database space available.
cause of the interruption.
ANR1149W Move data process terminated for volume volume name - lock conflict.
volume volume name - insufficient space
Explanation: During move data processing, the server
in target storage pool.
was unable to obtain the volume specified because a
Explanation: During move data processing for the lock was not available or a restartable restore is active
indicated volume, the server cannot move the data for data on the volume and has it locked. .
from the volume, because there is not enough space on
the destination storage pool to hold it or the access for
command.
the storage pool is either unavailable or readonly.
User response: Check for restartable restores by
issuing the QUERY RESTORE command. If the volume
command.
specified contains any data from the node and filespace
User response: Make more space available in the next identifed by the QUERY RESTORE command, the
storage pool, or specify a storage pool with more space, MOVE DATA command will fail. The restartable
and reissue the MOVE DATA command. restores must complete or be cancelled before the
MOVE DATA command can succeed.
ANR1150W Move data process terminated for If the volume does not contain data from the node and
volume volume name - unable to move filespace identified by the QUERY RESTORE command,
file to target storage pool due to the reissue the MOVE DATA command.
exclusion by size.
indicated volume, the server cannot move the data
from the volume because a file size is larger than

ANR1154W ANR1162W

fails.
volume volume name - thread resource
not available. User response: Check for additional messages and
indicated volume, the server cannot start a thread for
contact your service representative.
the migration process.
ANR1161W The move process is skipping a
command.
damaged file on volume volume name:
User response: Reissue the MOVE DATA command. If Node node name, Type file type, File space
the error persists, it may indicate a shortage of server filespace name, File name file name.
memory.
Explanation: During the move process, a file is
encountered that was previously found to be damaged.
ANR1155W Move data process terminated for If this file is part of an aggregate, the entire aggregate
volume volume name - sufficient memory was previously marked damaged, possibly because an
is not available. error was detected for some other file within the
aggregate.
indicated volume, there is not enough server memory System action: The damaged file is not moved.
available.
User response: Perform the following actions:
System action: The server ends the MOVE DATA v Audit the indicated volume with FIX=NO to verify
command. that the file is damaged. The audit will reset the file
User response: If necessary, make more memory status if the file is found to be undamaged during
available to the server, and then reissue the MOVE the audit. If the file is part of an aggregate, the audit
DATA command. will reset the aggregate status if the entire aggregate
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,
volume volume name - internal server
attempt to restore damaged files by using the
error detected.
RESTORE STGPOOL command.
indicated volume, the server encounters an internal
ANR1162W Space reclamation skipping damaged
error.
file on volume volume name: Node node
System action: The server ends the MOVE DATA name, Type file type, File space filespace
command. name, File name file name.
User response: Contact your service representative. Explanation: During reclamation, a file is encountered
that was previously found to be damaged. If this file is
part of an aggregate, the entire aggregate was
ANR1157I Removable volume volume name is previously marked damaged, possibly because an
required for move process. integrity error was detected for some other file within
Explanation: During move data or move node data the aggregate.
processing, the server determines that the indicated System action: The damaged file is not moved.
removable volume is required in order to complete
processing. User response: Audit the indicated volume with
FIX=NO to verify that the file is damaged. The audit
System action: The server attempts to mount the will reset the file status if the file is found to be
removable volume. undamaged during the audit. If the file is part of an
User response: Respond to any mount request for the aggregate, the audit will reset the aggregate status if
indicated volume. the entire aggregate is found to be undamaged. If this
volume is in a primary storage pool that has previously
been backed up to a copy storage pool, attempt to
ANR1160W Transaction was aborted for volume restore damaged files by using the RESTORE
volume name. STGPOOL command.
Explanation: An error was detected during transaction
commit. This message should be preceded by other
failed transaction.
ANR1163W ANR1167E
accessed for future operations involving the file.

ANR1163W Offsite volume volume name still
contains files which could not be User response: If the indicated storage pool is a
moved. primary pool, and a usable copy of the file exists in a
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 server might not move some files if the storage the case, the primary copy of the file may be made
pool is collocated and the volume being moved or accessible by changing the access mode of the primary
reclaimed contains files that require different output pool or volume.
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
If the files in the storage pool are deduplicated, they file type, File space filespace name, fsId
could be skipped due to the unavailability of an on-site filespace id, File name file name.
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
System action: None. to which the file belongs.
User response: Check for messages that indicate why System action: The file will skipped and will not be
files could not be moved. To complete the move moved from the offsite volume.
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
v Make the primary volumes available and reissue a RESTORE STGPOOL command. After the restore, you
MOVE DATA command to reclaim the volume. can reissue the MOVE DATA command.
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
output volumes until the volume being moved or Explanation: A reclamation process of offsite volumes
reclaimed is empty. It might take more than one cannot locate an undamaged copy of the specified file
attempt to totally empty the volume. in any storage pool accessible by the server. If this file
is part of an aggregate, the process could not locate an
undamaged copy of the aggregate to which the file
ANR1165E Error detected for file in storage pool belongs.
storage pool name: Node node name, Type
file type, File space filespace name, fsId System action: The file is skipped and will not be
filespace id, File name file name. moved from the offsite volume.
Explanation: The server has detected an error for the User response: The indicated storage pool is a
indicated file. primary pool that contains a damaged copy of the file.
The only usable copy of the file may now only reside
System action: The file will be marked damaged in on an offsite volume that was involved in the
the server database, and will not be accessed for future reclamation process, but was not totally reclaimed. If
operations. If this file is part of an aggregate, the entire you bring this volume back onsite, you can recreate the
aggregate will be marked damaged. If a usable copy of file in the primary pool by using the RESTORE
the file exists in another storage pool, that copy may be STGPOOL command.

ANR1168W ANR1173E
System action: The files are not moved, but are

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

processing of a volume that is offsite, there was no ANR1173E Space reclamation for offsite volume(s)
volume available in the specified target copy storage cannot copy file in storage pool storage
pool. pool name: Node node name, Type file type,
File space filespace name, fsId filespace id,
System action: The operation is terminated. File name file name.
User response: Define volumes to the copy storage Explanation: A reclamation process of offsite volumes
pool or raise the MAXSCRATCH value. cannot locate a copy of the specified file in any storage
pool accessible by the server. If this file is part of an
ANR1171W Unable to move files associated with aggregate, the process could not locate a copy of the
node node name, filespace filespace name aggregate to which the file belongs on an accessible
fsId filespace id on volume volume name volume.
due to restore in progress. System action: The file is skipped and will not be
Explanation: During movement of data (migration, moved from the offsite volume.
reclamation, move data) from a sequential volume, one User response: The indicated storage pool is a
or more files were encountered that were locked by a primary pool that should contain a copy of the file.
restore operation. Perhaps the volume on which that file resides is on a
ANR1174W ANR1181E
destroyed volume. The only usable copy of the file may

ANR1178I Copying active files from primary
now only reside on an offsite volume that was involved
storage pool primary pool name to active
in the reclamation process, but was not totally
data pool active data pool name started as
reclaimed. If you bring this volume back onsite, you
process process ID.
can recreate the file in the primary pool by using the
RESTORE STGPOOL command. Explanation: A process has been started to copy active
data from a primary storage pool to the indicated
active data.
ANR1174W One or more cached files were not
deleted on volume volume name. System action: For every noncached, active file in the
primary pool, a copy is made in the active data pool, if
Explanation: The MOVE DATA command could not
a copy of that file does not already exist.
delete one or more cached files on the disk volume
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
started as process process ID.
User response: If you want the remaining cached files
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
files are not copied.
Explanation: After reclamation of the indicated
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.
ANR1180W Access mode for volume volume name
System action: The volume is marked unavailable so has been set to "unavailable" due to file
it will not be chosen again for reclamation. read or integrity errors.
User response: Explanation: During processing of a storage pool
v Use the UPDATE VOLUME command to set the volume, input/output or other errors occur that force
volume access to readonly. the server to mark the volume unavailable for further
processing.
v Try using the MOVE DATA command to manually
reclaim the volume. System action: The server sets the volume status to
v If files still exist on the volume, audit the volume unavailable.
using AUDIT VOLUME FIX=YES. User response: Correct the errors that set the volume
v Try using the MOVE DATA command again. to unavailable, or use the DELETE VOLUME command
v Use the RESTORE VOLUME command to restore to remove it from the system.
files marked damaged.
ANR1181E Diagnostic(ID): Data storage transaction
ANR1176I Moving data for collocation set set transaction ID was aborted.
number of total sets on volume volume Explanation: A database transaction failed because of
name. an error that was detected during data storage
Explanation: As a result of a move operations, such as processing. This message should be preceded by other
MOVE DATA, MOVE NODEDATA, migration, or messages that give additional information about the
reclamation, the server is moving data from the volume failed transaction.
indicated to new volumes. This message shows the System action: The server operation that encountered
total sets of data on the volume to be processed. this error during data storage processing fails.
Depending upon the collocation setting of the
destination storage pool, a set can be file spaces that User response: Check for additional messages and
belong to the same collocation group, file spaces for a eliminate the condition that caused the failed
node, or a single filespace. transaction.


ANR1182I ANR1210I
executing for the named storage pool, these processes

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

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

ANR1220E ANR1228I
write errors and reissue the backup command. User response: To increase the amount of database
DBSPACE command. Add one or more directories to
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
needs to obtain a lock that is not available.
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.
User response: Monitor archive logs and active logs. If
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.
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.
ANR1229W ANR1235I
ANR1229W Volume volume name cannot be backed ANR1231I Restore preview of primary storage pool
up to a copy storage pool or copied to primary pool name started as process
an active-data storage pool.- the volume process ID.
is offline, in use by another process, not
Explanation: A preview process has been started to
currently mountable, or access mode is
restore a primary storage pool.
"unavailable" or "destroyed".
System action: Preview information about the restore
Explanation: During storage pool backup or the
operation is collected and displayed, but files are not
copying of active data, the contents of a volume cannot
restored. The restore preview includes noncached files
be backed up or copied if one of the following
that reside in the specified primary storage pool and
conditions exists:
that meet either of the following conditions:
v The volume is offline.
v The file is stored on a volume whose access mode is
v The volume is in use by another process. destroyed
v The volume cannot be be mounted. v The primary file has been identified as having
v The access mode of the volume does not allow the data-integrity errors during a previous operation
operation.
System action: The server continues backup
processing, but skips the indicated volume.
ANR1232I Restore of volumes in primary storage
User response: Take one of the following actions: pool primary pool name started as process
v If the volume is offline, issue the VARY ONLINE process ID.
command for the indicated volume. Explanation: A process has been started to restore one
v If the access mode of the volume is unavailable, issue or more volumes in the indicated primary storage pool.
the UPDATE VOLUME command to change the
System action: Noncached files that reside on selected
access mode to readwrite or readonly. If the access
volumes in the primary storage pool are restored.
mode of the volume is destroyed, verify with an
administrator whether the access mode should be User response: None.
updated. If it should, issue the UPDATE VOLUME
command to change the access mode to readwrite or
readonly. ANR1233I Restore preview of volumes in primary
storage pool primary pool name started as
v If the volume is in use by another process, wait for process process ID.
that process to complete, and then retry the BACKUP
STGPOOL command or the COPY ACTIVEDATA Explanation: A preview process has been started to
command. restore one or more volumes in the indicated primary
v If the volume is not currently mountable, verify that storage pool.
the drive can mount the volume, and then retry the System action: Preview information about the restore
BACKUP STGPOOL command or the COPY operation is collected and displayed, but files are not
ACTIVEDATA command. restored. The restore preview includes noncached files
that reside on selected volumes in the primary storage
ANR1230I Restore of primary storage pool primary pool.
pool name started as process process ID. User response: None.
Explanation: A process has been started to restore the
indicated primary storage pool. ANR1234I Restore process process ID ended for
System action: Non-cached files that reside in the storage pool storage pool name.
named primary storage pool are restored if either of the Explanation: A restore process for the named primary
following criteria are met: storage pool has ended.
v The file is stored on a volume whose access mode is
destroyed
v The primary file has been identified as having User response: None.
data-integrity errors during a previous operation
User response: None. ANR1235I Restore process process ID ended for
volumes in storage pool storage pool
name.
Explanation: A restore process for volumes in the
named primary storage pool has ended.

ANR1236I ANR1243E

ANR1240I The restore of volumes in the primary
User response: None. pool name primary storage pool is
complete. Number of files restored:
number of restored files. Number of bytes
ANR1236I Restore process process ID terminated for restored: number of restored bytes. Number
storage pool storage pool name - process of deduplicated bytes restored: number of
canceled. restored dedup bytes. Number of
Explanation: During restore of the indicated primary unreadable files: number of unreadable
storage pool, a process performing the restore has been files. Number of unreadable bytes:
canceled. number of unreadable bytes.
System action: If other restore processes are executing Explanation: Restore processing for volumes in the
for the named storage pool, these processes continue. specified storage pool ended with the displayed results.
User response: None. System action: None.

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

ANR1255W ANR1259W
User response: Respond to any mount request for the

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 volumes 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 volumes 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 volumes 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.
ANR1260W ANR1269I
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.
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.

ANR1270I ANR1277E

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 ANR1290I
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.
transaction aborted.
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.
transaction aborted.
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.

ANR1291E ANR1296W
User response: Examine previous messages to moved or copied to the DISK storage pool.
determine whether all of the move node data processes
System action: The server moves or copies all files
ended successfully.
from the volume that do not have deduplicated extents.
Those files that do have deduplicated extents are
ANR1291E Audit command: Incorrect information skipped.
detected in a schedule event record for
User response: If attempting a MOVE
node nodename, domain domain, schedule
DATA/NODEDATA to move the files with
schedule. Specify FIX=YES to delete the
deduplicated extents to the DISK storage pool, one
record.
must first perform a MOVE DATA/NODEDATA to
Explanation: A database audit process detects another sequential storage pool that does not have
incorrect information for a schedule event record. deduplication enabled. This move will restore the
deduplicated files to their complete state in the target
storage pool. Once all deduplicated data has been
User response: Rerun the AUDITDB operation moved, perform a MOVE DATA or MOVE
specifying FIX=YES so that the incorrect schedule event NODEDATA to the DISK storage pool from the target
record can be deleted. storage pool. It is recommended to use a FILE storage
pool as the target.
ANR1292E Audit command: Incorrect information If attempting a RESTORE STGPOOL/VOLUME to copy

detected in a schedule event record for the files with deduplicated extents, one must first
node nodename, domain domain, schedule perform a RESTORE STGPOOL/VOLUME to another
schedule. The record will be deleted. sequential storage pool that does not have
deduplication enabled. This will restore the
Explanation: A database audit process detects deduplicated files to their complete state in the target
incorrect information for a schedule event record. The storage pool. Once all deduplicated data has been
record will be deleted. A subsequent QUERY EVENT restored, perform a MOVE DATA/NODEDATA to the
will report this event as "Missed." DISK storage pool from the target storage pool. It is
System action: Audit processing continues. recommended to use a FILE storage pool as the target.

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
accessible storage pools. Explanation: Tivoli Storage Manager computes and
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
System action: The Tivoli Storage Manager server file system was unable to fulfil the request. It was,
skips files that do not have copies. The server does not however, able to set the date to the Snaplock retention
move the files from offsite storage-pool volumes. date, which is farther in the future than the requested
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
process, enable trace AFUNAVAILABLE and look in the This warning message is only issued once per volume,
trace log. when this condition is detected when data is first
placed on the volume.
ANR1294I Process process ID skipped skipped files System action: The operation continues.
files on volume volume name because of User response: Verify that the Tivoli Storage Manager
deduplicated files. COPYGROUP attributes and the retention settings of
Explanation: While moving or copying files from the the Network Appliance file system are consistent with
sequential FILE volume shown to a DISK storage pool, your requirements for WORM volume storage.
files that had deduplicated extents were encountered.
As a result, the files were skipped. ANR1296W Storage pool storage pool name does not
The sequential FILE volume shown is assigned to a contain WORM FILE volumes.
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
ANR1297E ANR1302E
other such situations when it is determined that data Explanation: The server failed to delete an object in a
on WORM volumes might be moved to other media. It Centera storage device after server records concerning
names a storage pool that does not contain WORM the object were deleted. The object is no longer
FILE volumes. accessible through the server. The object continues to
occupy space in the Centera storage device. The return
When it is issued during the DEFINE and UPDATE
code that is returned is either from the server interface
STGPOOL commands, it indicates that the storage pool
to Centera services, or it can be directly from the
being defined or updated is being configured with
Centera device.
WORM FILE volumes (Reclamationtype is SnapLock),
but other storage pools being specified on the storage System action: The server continues operation, and
pool definition (for example, the Next or Reclaim or the object is logically deleted within the server, but
Copy storage pool parameters) do not contain WORM continues to occupy space in the Centera device.
FILE volumes (Reclamationtype is Threshold). Such
User response: The server can continue to operate in
configurations might cause data on those WORM FILE
spite of this error. Centera service can be required if the
volumes to be moved to a storage pool that does not
volume of unpurged objects becomes a problem.
support WORM FILE volumes.
For other situations, this message might be issued
ANR1299E The server encountered an invalid
when there will be a movement of data from a storage
storage format while attempting a
pool with WORM FILE volumes (Reclamationtype is
partial object retrieve for object seg_id.
SnapLock) to a storage pool that does not have WORM
FILE volumes (Reclamationtype is Threshold). Explanation: A partial object retrieve was attempted
on a file that was stored in a format that does not
The server allows this type of movement, but the
support partial object retrieves.
customer needs to be aware that if data is moved from
a WORM FILE volume to another type of media, the System action: The transaction ends and the retrieve
data may no longer be protected from inadvertent or request fails.
malicious deletion. In addition, if this data is on
WORM volumes to meet data retention and protection User response: Try the retrieve again, using a regular
requirements for certain legal purposes and is moved or full retrieve instead of a partial object retrieve.
to other media, the data might no longer meet those
requirements. ANR1300I VARY ONLINE command initiated for
System action: The command continues. disk volume volume name.
User response: Verify that the storage pools being Explanation: A VARY ONLINE command has caused
used meet your requirements for data protection and a vary-on process to be started for the volume
retention. specified.
System action: The volume is varied online.
ANR1297E Storage pools with User response: None.
RECLAMATIONTYPE=SNAPLOCK can
only be defined on servers with archive
data retention protection enabled. ANR1301I VARY OFFLINE command initiated for
disk volume volume name.
Explanation: Defining storage pools with
RECLAMATION=SNAPLOCK is only supported on a Explanation: A VARY OFFLINE command has caused
server with archive data protection enabled. a vary-off process to be started for the volume
specified.
System action: The define storage pool command
fails. System action: The volume is varied offline.
User response: Define the storage pool with User response: None.
RECLAMATIONTYPE=THRESHOLD on this server. Or
else enable archive data retention protection on this ANR1302E Disk volume volume name is already
server, and try the command again. online.
Explanation: A VARY ONLINE command specified a
ANR1298W The server encountered an error in volume that was already online.
attempting to delete an object in a
Centera storage device. The Centera System action: None.
representation of the name is Centera User response: None.
object string. The server was keeping
track of the object in volume id volume
id. The return code received was return
code.

ANR1303E ANR1311E
and restarted to synchronize the storage agent with the

ANR1303E Disk volume volume name is already
server.
offline.
Explanation: A VARY OFFLINE command specified a
ANR1309W Shred value zero for storage pool storage
volume that was already offline.
pool name may render deleted data non
System action: None. shreddable.
User response: None. Explanation: This message is issued during the define
or update of a storage pool when a SHRED value of
zero has been found with a storage pool in the storage
ANR1304E Disk volume volume name is currently in
pool hierachy.
use.
The server allows this type of operation, but the
Explanation: A VARY OFFLINE command specified a
administrator needs to be aware that if data is stored or
volume that is currently in use and cannot be varied
moved to the affected storage pool, the data cannot be
offline at this time.
shredded after deletion.
When it is issued during the DEFINE command, it
User response: Try the command again at a later time, indicates that the storage pool definition is being
or attempt to determine how it is currently being used configured with a non zero SHRED value, however
and free it. other storage pools being specified on the definition
(for example, the Next or Reclaim or Copy storage pool
parameters) have a SHRED value of zero.
ANR1305I Disk volume volume name varied online.
When issued during the UPDATE command, it
Explanation: The specified volume has been varied indicates the specified storage pool may be altering the
online as the result of a VARY ONLINE command. SHRED value from non zero to zero or that the
System action: None. specified Copy, Next or Reclaim storage pool has a
SHRED value zero. Such configurations may result in
User response: None. data to become non shreddable if data from the
primary random access storage pool is moved to one of
ANR1306I Disk volume volume name varied online the storage pools with a zero SHRED value.
(read-only). System action: The command continues.
Explanation: The specified volume has been varied User response: Verify that the storage pools being
online in read-only mode as the result of a VARY used meet your requirements for data protection.
ONLINE command.
System action: None. ANR1310E Vary-on failed for disk volume volume
User response: None. name - insufficient memory.
Explanation: A VARY ONLINE command has been
ANR1307I Disk volume volume name varied offline. issued for the disk volume specified, but sufficient
memory is not available to process the command.
Explanation: The specified volume has been varied
offline as the result of a VARY OFFLINE command. System action: The volume is not varied online.
System action: None. User response: Reissue the command at a later time,
or make more memory available to the server.
ANR1311E Vary-on failed for disk volume volume

ANR1308W Storage agent not sychronized with name - unable to access disk device.
server - restart needed.
Explanation: The storage agent has detected that a issued for the disk volume specified, but the server is
policy, storage pool, device class, or other attributes unable to access the disk.
that is read from the server at initialization is no longer
valid. System action: The volume is not varied online.
System action: The operation of the storage agent User response: Attempt to determine the cause of the
continues. Depending upon what has changed on the inability to access the volume and correct the problem.
server the storage agent behavior may be
unpredicatable and other failures may result.
User response: The storage agent should be halted
ANR1312E ANR1320W
ANR1312E Vary-on failed for disk volume volume ANR1317E Command: Storage pool storage pool name
name - error reading disk. is not a shreddable pool.
Explanation: A VARY ONLINE command has been Explanation: The command indicated specifies the
issued for the disk volume specified but the server name of a storage pool which is not a shreddable pool.
encounters an error reading the disk. The command syntax requires that
SHREDTONOSHRED=YES be specified when data is
System action: The volume is not varied online.
moved from a shreddable storage pool to a non
User response: Attempt to determine the cause of the shreddable storage pool.
read error and correct the problem.
command.
User response: Reissue the command with
name - unsupported block size (block
SHREDTONOSHRED=YES.
size).
ANR1318I The process of copying active data from
issued for the disk volume specified, but the volume is
the primary pool name primary storage
formatted with a block size that cannot be used.
pool to the active data pool name active
System action: The volume is not varied online. data pool is complete. Number of
copied files: number of copied files.
User response: Reformat the disk with a block size Number of copied bytes: number of copied
that is an evenly divisible by 4096. bytes. Number of copied deduplicated
bytes: number of copied dedup bytes.
ANR1314E Vary-on failed for disk volume volume Number of unreadable files: number of
name - reduced capacity (was count unreadable files. Number of unreadable
blocks, now count blocks. bytes: number of unreadable bytes.
Explanation: A VARY ONLINE command has been Explanation: The process of copying active data for
issued for the disk volume specified, but the size of the the specified storage pool ended with the displayed
volume does not match the size expected. results.
System action: The volume is not varied online. System action: None.
User response: Restore the volume or otherwise User response: Examine previous messages to
correct the disk volume size, and reissue the command. determine whether all copy active data processes ended
successfully.

name - invalid label block. ANR1319I The preview of copying active data from
the primary pool name primary storage
Explanation: A VARY ONLINE command has been pool to the active data pool name active
issued for the disk volume specified, but the label block data pool is complete. Number of files
of the volume is invalid or cannot be read. copied: number of copied files. Number of
System action: The volume is not varied online. copied bytes: number of copied bytes.
Number of copied deduplicated bytes:
User response: Restore or reformat the disk volume. number of copied dedup bytes.
Explanation: The preview of copy active data
ANR1316E Vary-on failed for disk volume volume processing for the specified storage pool ended with
name - internal error detected. the displayed results.
Explanation: A VARY ONLINE command has been System action: None.
issued for the disk volume specified, but fails due to an
internal server error. User response: No action is required.

ANR1320W Vary-on not possible for disk volume
User response: Contact your service representative. volume name - access state is
"unavailable".
issued for the disk volume specified, but the status of
the volume is unavailable.

ANR1321W ANR1330E
User response: If necessary, use the UPDATE ALLOWSHREDDABLE=YES parameter when exporting
VOLUME command to change the status of the objects from a shreddable storage pool. Using this
volume, and reissue the command. 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
skipping skipped bytes bytes.
issued for the disk volume specified, but the status of
the volume is destroyed. Explanation: The shredding process has completed.
The amount of data successfully shredded and the
amount of data that was skipped are reported.
User response: If necessary, use the UPDATE
System action: Server operation continues. If any data
VOLUME command to change the status of the
was skipped, the server will attempt to shred it the
volume, and reissue the command.
next time shredding runs.
ANR1322W The shredding mode is already shredding
mode.
ANR1327I Automatic shredding stopped. Total
Explanation: A SETOPT SHREDDING command was
bytes shredded was shredded bytes and
issued to change the shredding mode, but the new
total bytes skipped was skipped bytes
mode is the same as the existing mode.
bytes.
System action: The shredding mode is unchanged.
Explanation: The automatic shredding process has
User response: None. ended. The amount of data successfully shredded and
skipped during automatic shredding is reported.
ANR1323E Command SHRED DATA is invalid for System action: Server operation continues. If any data
automatic shredding mode. was skipped, the server will attempt to shred it the
next time shredding runs.
Explanation: A SHRED DATA command was issued
while shredding mode is set to Automatic. User response: None.

ANR1328E The server has detected an attempt to
User response: Set the shredding mode to Manual or restore or retrieve a shredded object.
wait for automatic shredding to shred the data.
Explanation: An attempt was made to retrieve or
restore an object which has already been shredded. This
ANR1324E Process process number is already running can happen if your datasbase was recently restored,
a SHRED DATA. and data which existed at the time of the database
Explanation: A SHRED DATA command was issued backup has since been erased and shredded.
while another SHRED DATA process is still executing. System action: Server operation continues.
Only a single SHRED DATA process is allowed at any
time. User response: Perform an AUDIT VOLUME
operation on the volume containing the shredded data.
User response: Wait for the current SHRED DATA ANR1329I Automatic shredding started.
process to finish, and issue the command again.
Explanation: The automatic shredding of deleted
objects is starting.
ANR1325W Shreddable object for node name:
type=type, file space=filespace name, System action: Server operation continues.
object=object name skipped.
Explanation: The object for node name, identified by
type, file space and object name was found in a
ANR1330E The server has detected possible
shreddable storage pool and is skipped, however the
corruption in an object that is being
EXPORT continues.
restored or moved. The actual values for
System action: The server process continues exporting the incorrect frame are: magic magic hdr
and will skip all shreddable objects. version ver hdr length hdrLen sequence
number seqNum data length length server
User response: Specify the ID srvId segment ID segId crc crc.
ANR1331E ANR1338E
Explanation: An invalid frame was detected. This command before rerunning the DSMSERV INSERTDB
might indicate corruption within the object that is being command.
restored or moved.
System action: The object is not restored or moved. ANR1336I command: Ready for connections from
the source server. Remaining time:
User response: Retry the failing operation. If the
remaining time
operation fails again, see the troubleshooting topic
"Analyzing error messages ANR1330E and ANR1331E" Explanation: The command has completed its
in the Tivoli Storage Manager Information Center. initialization, and is ready to begin receiving database
information from the source server.
ANR1331E Invalid frame detected. Expected magic System action: The command will continue to wait
magic sequence number seqNum server id until the source server establishes a server-to-server
servId segment id segId. connection and begins sending database information, or
until the specified amount of time has passed.
Explanation: This message indicates the expected
values when an invalid frame is detected. User response: Initiate a session from the source
server.
User response: If contacting support, please provide
ANR1337I A trigger type trigger has been removed.
the information from this message.
Explanation: The DSMSERV INSERTDB command
encountered a database backup trigger, a database
ANR1332W Shredding cancelled prior to
space trigger, or recovery log space trigger, and
completion. Total bytes shredded was
removed it as part of the database upgrade process.
shredded bytes and total bytes skipped
was skipped bytes bytes. System action: The trigger is deleted from the
upgraded database.
Explanation: The shredding process was cancelled
either because the specified duration has elapsed, or User response: None.
because the CANCEL PROCESS command was used to
cancel it. The amount of data successfully shredded
ANR1338E One or more constraint violations were
and skipped is reported.
detected. Examine log file log file name
System action: Server operation continues. If any data for details.
was skipped or not processed, the server will attempt
to shred it the next time shredding runs.
encountered one or more instances where data being
User response: None. inserted into the database violated a constraint or was
otherwise invalid. Information about the error, along
with the data that caused the error, was logged in the
ANR1335E command: Database database name cannot
specified log file.
be the target of an upgrade because it is
not empty. System action: The offending row was not inserted
into the database. Instead, the contents of the row were
Explanation: The DSMSERV INSERTDB operation
written to the specified log file along with additional
cannot insert data into the specified database because
information about the specific error.
the database already contains data from another server.
User response: Because some data was not inserted
Possible causes for this error include:
into the database, the database is in an inconsistent
v The wrong database was specified in the state. The server should not be started until the
DATABASEALIAS option in the server's options file. problem is corrected.
v The database was formatted using the DSMSERV
Contact your service representative for assistance in
FORMAT command instead of the DSMSERV
correcting the problem. You may be directed to
LOADFORMAT command.
examine the log file, and in some cases, correct the
System action: The DSMSERV INSERTDB command erroneous data and insert it into the database.
terminates. However, due to the sensitive nature of the database,
you should never attempt to do this unless directed to
User response: Verify that the correct database name do so by your service representative.
is specified in the server's options file. If the correct
database is specified, and the database is not in use by
a different TSM server, then drop the database and
recreate it using the DSMSERV LOADFORMAT

ANR1339W ANR1345I

ANR1339W Session session id underestimated a size
allocation request - additional spaceMB User response: None.
more space was allocated to allow the
operation to continue.
ANR1343I Unable to delete scratch volume volume
Explanation: This session required additional space name.
megabytes of space in order for the operation to
continue. The client is responsible for accurately Explanation: A scratch volume cannot be deleted from
reporting the size of a file to be stored to the server. the server and returned to scratch at this time because
The size reported by the client is used to reserve space all the locks have not be released. A number of retries
in the DISK storage pool to store this file. If this size is have been attempted.
underestimated, the server may not be able to allocate System action: None
the additional space needed for this file to continue
with this operation. User response: The scratch volume will be
automatically deleted when the server is restarted. Or,
System action: None, the operation was able to you may manually delete this volume later, using the
continue. DELETE VOLUME command.
User response: The installed version of the client for
this node should be evaluated. In most cases, if a client ANR1344I Volume volume name cannot be reused.
has underestimated the sizes of files reported to the Remove the volume from server storage.
server, this may have been corrected in a newer version
of the client. If this is an application using the TSM API Explanation: A volume that was full and is now
that is not an IBM product, contact the vendor for the empty cannot be reused by the server because the
application to have this corrected. volume is on WORM media.
System action: The volume is in a state where the
ANR1340I Scratch volume volume name is now access mode is READONLY, the status is FULL, and the
defined in storage pool storage pool name. percent utilized is 0. The server considers the volume
to be empty when calculating the occupancy and
Explanation: The scratch volume specified has been utilization fields for the volume.
added to the storage pool shown.
User response: The volume remains in the library and
System action: None. in the storage pool, with the attributes described in the
User response: None. System Action section. If this is not a volume in a
RECLAMATIONTYPE=SNAPLOCK storage pool, you
may remove the volume by performing these steps:
ANR1341I Scratch volume volume name has been 1. Remove the volume from the storage pool by
deleted from storage pool storage pool issuing the DELETE VOLUME command.
name.
2. Remove the volume from the library by issuing the
Explanation: The scratch volume specified is no CHECKOUT LIBVOLUME command.
longer in use and has been removed from the indicated
storage pool. If this is a volume in a
RECLAMATIONTYPE=SNAPLOCK storage pool, you
System action: None. cannot remove the volume. Rather, allow Tivoli Storage
Manager reclamation processing to delete the volume.
ANR1345I Volume volume name cannot be reused

ANR1342I Scratch volume volume name is now
by other applications and will remain in
pending - volume will be deleted from
the storage pool.
storage pool storage pool name after the
reuse delay period for this storage pool Explanation: A WORM (write-once-read-many)
has elapsed. volume that has been written by the server cannot be
used by other applications. This volume was not full
Explanation: All files have been deleted from the
and has been emptied due to expiration, delete
indicated scratch volume. The volume will not be
commands, or transaction failure.
removed from the storage pool until the reuse delay
time period for the indicated storage pool has elapsed. System action: The volume remains in the storage
If the storage pool does not have a reuse tdelay pool to be reused by IBM Tivoli Storage Manager,
specified, the indicated volume was emptied after it unless it is manually deleted. The remaining space on
had been requested by another process. It will be in the the volume will be used in the normal course of server
full or filling state if the process places more data on operation.
the tape, or it will be removed from the storage pool
after it is no longer required. User response: If the volume is no longer to be used,
ANR1346E ANR1352I
manually delete it from the storage pool. remove any sorting information which is left over from
previous export operations.
ANR1346E Export/import command: Preview System action: The backup or archive objects were not
processing terminated abnormally - deleted. Only the information used to sort these objects
error accessing data storage. during the previous export operation was deleted. The
background process was terminated before all sorting
information was deleted. The system will not perform
in accessing data storage while executing an import or
further export processing of file data until this problem
export preview operation.
is resolved.
User response: Use the QUERY ACTLOG command to error. Issue the QUERY ACTLOG command to view the
examine messages prior to this error to determine the activity log and search for messages, then restart the
cause of the data storage failure. If you find and server. If the error cannot be isolated and resolved,
resolve the error, retry the export or import operation. contact your service representative.
If you cannot find the error, contact your service
representative for assistance in resolving the problem.
ANR1350E Command: Invalid time range specified.
FROM: fromdate fromtime TO: todate
ANR1347E Export/import command: Processing totime.
terminated abnormally - error accessing
Explanation: A command was issued that specifies an
data storage.
invalid FROM and TO date or time range. This error
Explanation: The server encountered an internal error can occur when the FROM date or time is not before
in accessing data storage while executing an import or the TO date or time.
export operation.
System action: The export or import operation is command.
User response: Use the QUERY ACTLOG command to date or time range.
cause of the data storage failure. If you find and
resolve the error, retry the export or import operation.
suspended with status status.
If you cannot find the error, contact your service
representative for assistance in resolving the problem. Explanation: The background process to service the
command command was suspended with a SUSPEND
command.
ANR1348I Export Operation information for number
objects has been deleted. System action: Processing for the command command
stops. Statistics on the number and type of objects
Explanation: A background server process deleted
export operation information for number files from the
server database. This process started during
message.
initialization to remove any unneeded export
information. User response: None.
System action: The actual backup or archive objects
were not deleted. Only information used to sort these ANR1352I Command started by administrator name as
objects during the previous export operation was process process ID has been suspended.
deleted.
User response: None. command command by administrator administrator name
suspended processing.
ANR1349E Error code during deletion of export System action: The specified process suspends, and
operation information for number server operations continue.
objects.
Explanation: A background server process
encountered an internal error after deleting export
operation information for number files from the server
database. This process started during initialization to

ANR1353I ANR1363I
System action: The command runs and server

ANR1353I Command: Cannot cancel the EXPORT
operations continue.
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.
System action: The command runs and server System action: Server operation continues.
operations continue. User response: None.
ANR1360I Output volume volume name opened
ANR1355I command name: An export operation (sequence number sequence number).
already exists with the Explanation: During a sequential data operation, the
EXPORTIDentifier export ID. volume specified has been opened for output as the
Explanation: The export command fails. volume number shown.
System action: The command fails and server System action: None.
operations continue. User response: None.
User response: Reenter the export command with an
unused export identifier. ANR1361I Output volume volume name closed.
Explanation: During a sequential data operation, the
ANR1356I Command: Cannot restart the EXPORT volume specified has been closed because the export or
operation with export identifier exportId. dump is complete.
The operation is currently active.
Explanation: The server cannot restart the export
operation specified in the RESTART EXPORT command User response: None.
because the export operation is currently running as an
active process. ANR1362I Output volume volume name closed
System action: Server operations continue. (full).
User response: Only suspended Export operations Explanation: During a sequential data operation, the
may be restarted using RESTART EXPORT command. volume specified has been closed because the volume is
Issue the QUERY EXPORT command to identify the full.
current state the EXPORT operation. System action: None.
ANR1357I command name: The EXPORTIDentifier
parameter is not supported when the
PREVIEWIMPORT parameter is ANR1363I Input volume volume name opened
specified. Running as non-restartable (sequence number sequence number).
export. Explanation: Because of a sequential data operation,
Explanation: The EXPORTIDentifier parameter is the volume specified has been opened for input as the
ignored while the command continues. volume number shown.
ANR1364I ANR1372I
System action: None. System action: The volume is not used.

User response: None. User response: Supply the volume with the proper
sequence number. The volume history file can help you
choose the correct volume.
ANR1364I Input volume volume name closed.
ANR1369E Input volume volume name contains
volume specified has been closed because the operation
Version 1 dump.
is complete.
volume specified has been mounted but appears to
User response: None. contain a version 1 database dump.
System action: The volume is not used. The operation
ANR1365I Volume volume name closed (end is terminated.
reached).
User response: Make sure you specified the correct
Explanation: During a sequential data operation, the volume for the operation. A Version 1 database dump
volume specified has been closed because processing of may not be loaded into a Version 2 server. The Version
the volume is complete. 1 database dump must only be loaded into a Version 1
server.
User response: None. ANR1370E Insufficient number of mount points
available in device class device class name.
ANR1366W Input volume volume name contains an Explanation: During IMPORT or EXPORT processing,
invalid identifier. the server cannot allocate sufficient mount points for
Explanation: During a sequential data operation, the the device class specified. The device class associated
volume specified has been mounted but contains an with the EXPORT or IMPORT drive only has a mount
invalid identifier. limit of one. The operation needs to read or write file
data from or to the same device class because file data
System action: The volume is not used. is being imported or exported.
User response: Make sure you specified the correct System action: The IMPORT or EXPORT command is
volume for the operation. If a LOADDB operation was ended and server operation continues.
being performed on MVS, the command syntax may be
specified by using a ddname or by specifying a device User response: Make more mount points available.
class name. You must use the same method that was
used when the database was originally dumped. If you ANR1371I Command: The export operation with
did not, this error message will be displayed. Try export identifier Export Id has been
loading the data base by using the other method of deleted.
syntax (ddname).
Explanation: The suspended server-to-server export
operation has been deleted. This operation may no
ANR1367W Import volume volume name was written longer be restarted. This message is be displayed in
by a different export process. response to a CANCEL EXPORT command.
Explanation: During an IMPORT operation, the System action: Server operation continues.
volume specified has been mounted but contains an
export identifier that does not match the import User response: None.
process.
System action: The volume is not used. ANR1372I Suspend export request accepted for
export process with export Identifier
User response: Supply a volume created by the proper Export Id ( process process ID).
export process.
Explanation: A SUSPEND EXPORT command has
been entered for the specified server-to-server export
ANR1368W Input volume volume name contains process. Some processes will experience a delay before
sequence number sequence number; they suspend. This delay may be lengthy for processes
volume sequence number sequence that involve remote data movement.
number is required.
volume specified has been mounted but contains the User response: None.
wrong volume sequence number.

ANR1373I ANR1382E
ANR1373I Process process Id for Command has been ANR1378I command: No connection was received
suspended on source server. after session wait time minutes.
Explanation: The background import process has been Explanation: The command waited the specified
suspended on the source server. amunt of time for the source server to connect, but no
connection was established.
System action: The specified process ends, and server
operation continues. System action: The command terminates.
User response: None. User response: Rerun the command. Either specify a
larger value for the SESSWAIT parameter, or establish a
connection from the source server more quickly.
ANR1374I Process process Id for Command has been
canceled on source server.
ANR1379I command: Read bytes bytes and inserted
Explanation: The background import process has been
database entries database entries in elapsed
canceled on the source server.
time (read rate megabytes per hour).
System action: The specified process ends, and server
Explanation: The command read the indicated
number of bytes, and wrote the indicated number of
User response: None. database entries.
ANR1375I Command: Cannot suspend the export
operation export Id because the current
state is not valid.
ANR1380I The buffer pool monitor switch is
Explanation: This message is returned in response to a
enabled.
SUSPEND EXPORT command which specified an
export operation that is not currently suspendible. The Explanation: The server has turned the buffer pool
export operation may not be running, or it may be in monitor switch to 'ON'.
the process of being suspended.
System action: Server continues processing.
System action: The specified command fails, and
ANR1381W The buffer pool monitor switch is
disabled 'OFF'. A manual update might
ANR1376I Analyst authority has been revoked for be needed.
administrator administrator name.
Explanation: The server failed to turn the buffer pool
Explanation: The DSMSERV INSERTDB command monitor switch to 'ON'.
encountered an administrator with analyst authority,
and revoked the authority as part of the database
upgrade process. User response: No action is required at this time. But
a manual update might be needed before executing
System action: The analyst authority is revoked.
command 'Q DBS' or 'Q DB F=D'. Refer to message
User response: None. 1139I.
ANR1377I Analyst authority has been revoked for ANR1382E The server failed with error code return
administrator id administrator id. code when attempting to update a
database parameter.
encountered an administrator with analyst authority, Explanation: Cannot update a database parameter
and revoked the authority as part of the database with the value specified in the server options file.
upgrade process.
System action: The server initialization fails.
System action: The analyst authority is revoked.
User response: None. prior to this message to determine the source of the
error. Contact your service representative for further
ANR1383I ANR1391E
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
correct.
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 TSM
server database to instance memory in
MBMB failed.
ANR1388E Schema verification for the database
Explanation: Attempt to set memory dedicated to
insert process detected inconsistencies.
TSM server database failed.
Explanation: Inconsistencies were detected during
database schema verification.
User response: Collect all messages prior to this one
System action: The database insert process terminates.
and contact your service representative for further
assistance. User response: Contact your service representative.
ANR1385E The database name is either invalid or ANR1389I The database insert process is
missing in the server option file. terminating because
CHECKSCHEMA=ONLY was specified.
Explanation: While attempting to format a database,
the Tivoli Storage Manager server has found that the Explanation: The database insert process is
database name is either invalid or missing. terminating after verifying the database schema
because the CHECKSCHEMA=ONLY parameter was
System action: Server format stops.
specified.
User response: Before reissuing the command to
format the database, check the following items:
v Ensure that the server options file has a valid name User response: Rerun the command without
for for Tivoli Storage Manager server database. The specifying the CHECKSCHEMA=ONLY parameter.
database name is specified with the
DATABASEALIAS option. The database name is a ANR1390E Column source column name (source
unique character string containing from one to eight column number) in legacy table source
letters, numbers, or keyboard characters. The name table name is mapped to an invalid
can contain any of the following characters: a-z, A-Z, column (target column number) in target
0-9, @, #, and $. table target table name (maximum column
v Ensure that the command is using the correct options is table size).
Explanation: The database insert process has detected
the command to specify a server options file, ensure
a discrepency while verifying the data base schema. A
that the name and location of the file is correct.
column in the source database table was mapped to an
invalid column in the target table. The target column
ANR1386I Beginning schema verification for the number is higher than the number of columns in the
database insert process. target table.
Explanation: The database insert process is verifying System action: The database insert process terminates.
that the database schema is correct.
System action: The server will verify the correctness
of the database schema before inserting any database
ANR1391E Column source column name (source
records.
column number) in legacy table source
User response: None. table name is mapped to the wrong
column target column name (target column
number) in target table target table name.
column in the source database table was mapped to the

ANR1392E ANR1401W
wrong column in the target table.

ANR1397I Insertdb command: Found number of
System action: The database insert process terminates. database objects database objects.
User response: Contact your service representative. Explanation: This message indicates the total number
of database objects that were found during database
insert processing.
ANR1392E Column target column name (target column
number) in target table target table name is System action: Server processing continues.
not set by upgrade, but does not allow
NULLs and has no default value.
ANR1398I Insertdb command: Processed number of
database objects database objects.
column in the target database table is not set, does not
have a default value and does not allow NULLs. Explanation: This message indicates the total number
of database objects that were successfully processed
during database insert processing.
ANR1393I Memory usage by the database manager
is set to AUTOMATIC.
ANR1399I Insertdb command: Failed to process
Explanation: The memory dedicated to TSM server
number of database objects database
database was set to automatic successfully.
objects.
Explanation: This message indicates the total number
User response: None. of database objects that were not successfully processed
during database insert processing.
ANR1394E The update to set memory used by TSM System action: Server processing continues.
server database to AUTOMATIC failed.
Explanation: Attempt to set memory dedicated to
TSM server database to automatic failed.
ANR1400W Mount request denied for volume
System action: Server operation continues. volume name - mount canceled.
User response: Collect all messages prior to this one Explanation: The volume shown cannot be mounted
and contact your service representative for further because the mount request has been canceled.
assistance.
System action: The volume is not mounted.
ANR1395I Insertdb command: Process process number,
database insert, has completed.
Explanation: The database insert process process
volume name - mount failed.
number has completed.
Explanation: The volume shown cannot be mounted
System action: Database insert processing ends.
because the mount request cannot be completed
User response: None. successfully. Possible reasons include, an error in device
specifications to the server or the mount request timed
out.
ANR1396E Insertdb command: Process process number,
database insert, has completed with System action: The volume is not mounted.
errors.
User response: If the device specifications (DEFINE
Explanation: The database insert process process DEVCLASS and so forth) are in error, correct them and
number has completed, but errors were encountered by reissue the command that requested the volume to be
the process. mounted.
System action: Database insert processing ends.

User response: Review any messages that were issued
by the process, and take corrective action as
appropriate.
ANR1402W ANR1409W
message is issued if one of the previously acquired

mount points cannot be released.
volume name - volume unavailable.
System action: At least one mount point acquired by
Explanation: The volume shown cannot be mounted
simultaneous write operation is not released.
because it is not available.
System action: The volume is not mounted.
User response: If the attempted mount occurs in a
ANR1407W Scratch volume mount request denied -
library sharing environment and the library manager
storage pool pool name has reached
was recently recycled, try again in five minutes. In this
maxscratch limit.
case the library manager and library client need a few
minutes to reestablish communication and synchronize Explanation: A scratch volume cannot be mounted
the mounting information between the two servers. because the storage pool has reached the maximum
scratch volume limit allowed by the MAXSCRATCH
parameter.
mount canceled. System action: A scratch volume is not mounted.
Explanation: A scratch volume cannot be mounted User response: Use the UPDATE STGPOOL poolname
because the mount request has been canceled. MAXSCRATCH=xx command command to increase the
number of scratch volumes allowed in the storage pool.
System action: The scratch volume is not mounted.
ANR1408I Insertdb command: PREVIEW=YES was
specified. No data will be inserted into
ANR1404W Scratch volume mount request denied - the database.
mount failed.
Explanation: PREVIEW=YES was specified on the
Explanation: A scratch volume cannot be mounted INSERTDB command. Database data will be read and
because the mount request cannot be completed checked for errors, but no data will be written into the
successfully. Possible reasons include, an error in device database.
specifications to the server or the mount request timed
out.
System action: The scratch volume is not mounted.
User response: If the device specifications (for
ANR1409W Volume volume name already in use -
example, DEFINE DEVCLASS) are in error, correct
skipped.
them and reissue the command that requested the
volume to be mounted. Explanation: During an export or database backup, a
volume cannot be used because it is already defined in
a storage pool, or has already been used by the current
operation, or has been previously used by an export or
no scratch volume available.
database backup operation (as recorded in the volume
Explanation: A scratch volume cannot be mounted history) or is in use by another process.
because no scratch volume is available.
System action: The operation continues and the
System action: The scratch volume is not mounted. volume is skipped.
User response: None. User response: Use the QUERY VOLUME command
to display the names of volumes that are defined to
server storage pools. Use the QUERY VOLHISTORY
ANR1406E Simultaneous write operation could not
command to display the names of volumes that have
release all the acquired mount points.
been used for export or database backup operations. If
Explanation: A simultaneous write to a primary and no volume names are displayed using the query
copy storage pools failed to release all the acquired commands described above, ensure that the volume
mount points. When a simultaneous write operation identified in this message has not been specified or
begins it will attempt to acquire all of the necessary used more than once in the operation being performed.
mount points. If a mount point cannot be acquired or
the simultaneous write operation has to wait for a
mount point, then the operation will release any mount
points it has already acquired. This prevents the
simultaneous write operation from holding mount
points and other mount requests from completing. This

ANR1410W ANR1419E
the case, the server also issues an ANR1316E message.

now set to "unavailable". System action: None.
Explanation: The status of the volume shown has User response: You can issue the RESTORE VOLUME
been set to unavailable. server command to restore the volume if a storage pool
backup is available.
ANR1416W Volume volume name access mode is
"offsite".
Explanation: At server startup, the status of the
now set to "read-only" due to write
indicated volume is offsite.
error.
Explanation: Because of an unrecoverable write error
on the volume shown, the status of the volume has User response: None.
been set to read-only.
System action: None. ANR1417W Access mode for volume volume name
now set to "read-only" due to excessive
read error.
Explanation: Because of an numerous read errors on
the volume shown, the status of the volume has been
"unavailable".
set to read-only.
Explanation: At server startup, the status of the
indicated volume is unavailable.
User response: Use QUERY VOLUME
FORMAT=DETAILED for the volume to view the
User response: None. access mode and number of read errors. You may want
to use the MOVE DATA command to move the
retrievable data from this volume to another volume.
For the damaged files, use the RESTORE VOLUME
"read-only".
command to restore a readable copy of the file to the
Explanation: At server startup, the status of the storage pool.
indicated volume is read-only.
System action: None. ANR1418E command name: Export commands that
target another server cannot be issued
User response: None. from the server console.
Explanation: An EXPORT command that targets
ANR1414W Volume volume name access mode is another server was issued from the server console. This
"read-only" due to previous write error. command cannot be issued from the server console
Explanation: At server startup, the status of the because it requires authentication of the issuing
indicated volume is read-only due to an unrecoverable administrator on the target server.
write error, or because an administrator used the System action: The server ignores the command and
UPDATE VOLUME command to set the volume access continues processing.
mode to read-only.
User response: Issue the command from an
System action: None. administrative client.
ANR1419E command name : FROMDATE must be
ANR1415W Volume volume name access mode is specified when FROMTIME is
DESTROYED. specified.
Explanation: At server startup, the status of the Explanation: A command that supports the
indicated volume is DESTROYED. This status can FROMDATE and FROMTIME parameters was issued
result because the access mode was set to DESTROYED with the FROMTIME parameter specified, but without
by a storage administrator. This status can also result the FROMDATE parameter. When the FROMTIME
because the server determined that the database parameter is used, the FROMDATE parameter must be
records associated with this volume are damaged and specified.
set the status of the volume to DESTROYED. If this is
ANR1420W ANR1427E

ANR1425W Scratch volume volume name is empty
continues processing.
but will not be deleted - volume state is
User response: Reissue the command with both the "mountablenotinlib".
FROMDATE and FROMTIME parameters specified.
Explanation: The named scratch volume is empty but
will not be deleted at this time because the state of the
ANR1420W Read access denied for volume volume volume is MOUNTABLENOTINLIB. Possible reasons
name - volume access mode = include, a MOVE MEDIA command was used to check
"unavailable". the volume out of the library and the volume was
subsequently checked into the library using CHECKIN
Explanation: An attempt to access the named volume LIBVOL without first running a MOVE MEDIA
for reading fails because the volume status is command to update the volume state back to
unavailable. MOUNTABLEINLIB state. If this should happen, the
System action: The volume is not used for read QUERY MEDIA will display the volume to be in
access. MOUNTABLEINLIB state since QUERY MEDIA does
verify if the volume is actually in the library before
User response: None. displaying the state of the volume.
System action: The volume is not deleted.
ANR1421W Read access denied for volume volume
name - volume is offline. User response: The following steps may be used if the
volume is to be deleted:
Explanation: An attempt to access the named volume
1. Run CHECKOUT LIBVOL to check the affected
for reading failed because the volume is offline.
volume out of the library, the REMOVE=NO option
System action: The volume is not used. may be used to prevent actual volume movement
User response: None. 2. Run MOVE MEDIA * STG=*
WHERESTATE=MOUNTABLENOTINLIB
WHERESTATUS=EMPTY. When the volume is
ANR1422W Read access denied for volume volume moved by MOVE MEDIA
name - volume access mode="offsite". WHERESTATE=MOUNTABLENOTINLIB, the
Explanation: An attempt to access the named volume scratch empty volume is deleted
for reading failed because the volume status is offsite. 3. Check the volume back into the library using
CHECKIN LIBVOL command
System action: The volume is not used for read
access.
ANR1426I All legacy FILE volumes have been
User response: None. marked FULL.
Explanation: As part of the conversion of the database
ANR1423W Scratch volume volume name is empty to Tivoli Storage Manager version 5.3, all existing
but will not be deleted - volume access non-full volumes of devtype FILE have been marked
mode is "offsite". FULL to keep them from being extended.
Explanation: The named scratch volume is empty but System action: All FILE volumes that were not
will not be deleted at this time because the access mode already FULL have been marked FULL and cannot be
is offsite. appended to.
System action: The volume is not deleted. User response: None.
User response: After bringing the volume onsite,
change the access mode to read-only so the volume will ANR1427E No legacy FILE volumes were marked
be deleted. FULL.
Explanation: As part of the conversion of the database
ANR1424W Read access denied for volume volume to Tivoli Storage Manager Version 5.3, all existing
name - volume access mode="destroyed". non-full volumes of devtype FILE were attempted to be
Explanation: An attempt to access the named volume made FULL. However, a database error prevented the
for reading failed because the volume status is conversion, and the status of these volumes remains
destroyed. unchanged.
System action: The volume is not used for read System action: The volumes are not marked FULL.
access. User response: Examine the server messages issued
User response: None. prior to this message to determine the source of the

ANR1428W ANR1435E
activity log and search for messages. Contact your investigate the cause of the error and may want to
service representative for further assistance. move data from this volume.
ANR1428W Shredding access denied for volume ANR1432I Updating device configuration
volume name - volume is offline. information to defined files.
Explanation: An object on the indicated volume Explanation: The server is updating device
cannot be shredded because the volume is offline. configuration information for the files or data sets
specified with the DEVCONFIG option in the server
System action: The object is not shredded at this time.
options file.
When the volume is put back online, another attempt
will be made to shred the object. System action: Server operation continues.
User response: Determine why the volume is offline, User response: None.
and, if possible, place the volume back online.
ANR1433I Device configuration information
ANR1429E Transaction failed for Import process - successfully written to file name.
invalid file space filespace name for node
Explanation: Device configuration information was
node name was detected.
successfully written to the file specified.
encounters an invalid file space name.
System action: This action usually occurs when the
import is operating on a file space that is currently
being deleted as a result of an administrative command ANR1434W No files have been identified for
or client action. The server ends import operation. automatically storing device
configuration information.
User response: Use the QUERY PROCESS command
to monitor and wait for any file space deletion Explanation: The server is unable to automatically
processes to complete, or cancel the process if you do update device configuration file. No files were
not want to delete the file space. Try the import identified using the DEVCONFIG option in the server
operation again after this action has been taken. options file.
ANR1430W Retrieval request denied for storage
pool storage pool name - access User response: If you would like to have the server
mode="unavailable". automatically record device configuration information
to assist in server recovery, use the DEVCONFIG
Explanation: An attempt was made to retrieve a file option in the server options file to specify where device
from the storage pool shown, but the access mode of configuration information should be written. If you
the storage pool is unavailable. update the options file, halt and then restart the server
so the changes can take effect.
System action: The file is not retrieved from this
storage pool. If possible, the file is retrieved from
another storage pool. ANR1435E Server could not write device
configuration information to devconfig
User response: Consider changing the access mode for
file name.
the storage pool.
Explanation: While attempting to write device
configuration information to defined files, the server
ANR1431E An error occurred while writing to side
cannot write to the file name specified.
A of volume volume name. An attempt
will be made to write to side B of this System action: The server cannot write device
volume. configuration information to the specified file.
Explanation: An error occurred while writing to side User response: Examine error messages that may have
A of a two-sided volume. been displayed prior to this message and correct any
problems, if possible. Make sure that the server has
System action: No additional data will be written to
proper authority to write to the file indicated and that
side A of this volume. Any remaining space on side A
there is sufficient space in the file system for the file.
will not be used. An attempt will be made to use the
On MVS, make sure that the data set has been allocated
reverse side (side B) of the volume.
and that the server has authority to write to the data
User response: None required if the side B can be set. After the problem has been corrected, use the
used successfully. However, the administrator should BACKUP DEVCONFIG command to write device
ANR1436E ANR1442E
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
proper authority to write to the file indicated and that information.
there is sufficient space in the file system for the file.
On MVS, make sure that the data set has been allocated
ANR1440I All drives in use. Process process number
and that the server has authority to write to the data
being preempted by higher priority
set. After the problem has been corrected, use the
operation.
BACKUP DEVCONFIG command to write device
configuration information to the file. Explanation: When a high priority operation
attempted to find an available drive, all the drives were
in use. To make a drive available for this operation, the
ANR1437E No device configuration files could be
indicated process is being cancelled by the system.
used.
System action: The lower priority process is cancelled
Explanation: The server attempts to read device
to make a mount point (drive) available.
configuration information from defined files and cannot
open any of the files. User response: When a drive again becomes available,
restart the process that was cancelled. If the process
System action: The operation is ended.
was a migration or reclamation process, it will be
User response: Examine error messages that may have automatically restarted when needed. If this message
been displayed prior to this message and correct any appears frequently, you may want to increase the
problems, if possible. Ensure that the defined device number of drives available. See the MOUNTLIMIT
configuration files have been created. If you can start parameter on the UPDATE DEVCLASS command.
the server, you can create the files by using the
BACKUP DEVCONFIG command. If you cannot start
ANR1441I Volume volume name is in use. Process
the server, you will need to create a device
process number being preempted by
configuration file by editing the file and adding the
higher priority operation.
appropriate DEFINE commands for the device class,
drive, and library definitions. The contents and Explanation: When a high priority operation
requirements for this file are described in the attempted to use a volume, it was in use. To make a
Administrators Guide. Make sure that the server has volume available for this operation, the indicated
proper authority to read from the defined device process is being cancelled by the system.
configuration files.
System action: The lower priority process is cancelled
to the volume available.
ANR1438W Skipping device configuration file:
User response: Restart the process that was cancelled.
devconfig file name.
It will wait until the higher priority process is finished
Explanation: While attempting to read device with the volume. If the cancelled process was a
configuration information from a defined device migration or reclamation process, it will be
configuration file, the server encounters problems in automatically restarted when needed.
processing the definitions included in the file.
System action: The specified file is skipped, and the ANR1442E Invalid storage pool for store operation:
next one specified in the server options file will be storage pool.
used.
Explanation: The storage pool selected for a store
User response: Examine error messages that may have operation (for example, backup or archive) was not a
been displayed prior to this message to understand NATIVE or NONBLOCK data format storage pool. This
why the file could not be used. When you can start the may be caused by an incorrect management class being
server again, you can refresh this file by using the assigned to an object.
BACKUP DEVCONFIG command.

ANR1443W ANR1452E

ANR1448I command name: Beginning serial SCRIPT
User response: Ensure that the copy group destination command execution on line line number.
storage pool of the assigned management class has the
Explanation: This message is issued during a RUN
appropriate NATIVE or NONBLOCK data format.
command (VERBOSE=YES) to indicate that a SERIAL
command was encountered and following SCRIPT
ANR1443W Process process ID terminated from commands will be executed serially.
session session id. A potential
System action: The SCRIPT command continues.
drive-contention deadlock was detected.
User response: See the output of the commands
Explanation: See message.
following the SERIAL command to determine their
User response: No action is required. results.
ANR1444E No device configuration file is defined. ANR1449I command name: Beginning parallel
SCRIPT command execution on line line
Explanation: No device configuration file is defined. number.
Check DEVCONFIG option in server options file.
System action: The specified configuration parameter command (VERBOSE=YES) to indicate that a
is skipped. PARALLEL command was encountered and following
User response: Add the DEVCONFIG option to the SCRIPT commands will be executed in parallel.
server options file, specifying a valid file or data set System action: The SCRIPT command continues.
name to use for the device configuration file.
User response: See the output of the commands
following the PARALLEL command to determine their
ANR1445I Insertdb command: Throughput was results.
megabytes per hour megabytes per hour.
Explanation: This message indicates the total ANR1450E command name: Invalid command script
throughput (megabytes/hour) during database insert name: command script name.
processing.
Explanation: An invalid script name was specified for
System action: Server processing continues. a DEFINE, UPDATE, or DELETE SCRIPT command.
User response: None. System action: The operation fails.
User response: Reenter the command specifying a
ANR1446I RUNSTATS: Table updating statistics valid command name.
started.
Explanation: This message indicates the update ANR1451E command name: Invalid command:
statistics for all tables started. command.
System action: Server processing continues. Explanation: An invalid command was specified for a
User response: None. DEFINE, UPDATE, or DELETE SCRIPT command.
ANR1447W command name: The server is not able to User response: Reenter the command specifying a
begin a new thread to execute the valid server command.
command on line line number in parallel.
The command will run serially.
ANR1452E command name: Invalid line number: line
Explanation: This message is issued during a RUN number.
command to indicate that thread resources are not
available to run the command in parallel. The Explanation: An invalid line number was specified for
command will be executed serially. a DEFINE, UPDATE, or DELETE SCRIPT command.
System action: The SCRIPT continues. System action: The operation fails.
User response: Increase the resources available to the User response: Reenter the command specifying a
server or reduce the number of parallel commands or valid line number.
scripts that are running on the server at any one time.
ANR1453E ANR1464E
ANR1453E command name: Command script command ANR1459E command name: Command script command
script name already exists. script name, line line number does not
exist.
Explanation: The script name specified in a DEFINE
SCRIPT command already exists. Explanation: The line in command script name
specified in a UPDATE, or DELETE SCRIPT command
does not exist.
different command name.
different line number.
ANR1454I command name: Command script command
script name defined.
Explanation: The script name specified in a DEFINE
script name copied to new command script
SCRIPT command was successfully defined.
name.
System action: None
Explanation: The specified command script was
User response: None copied to a new script with the COPY SCRIPT
command.
ANR1455E command name: Command script command System action: None

script name does not exist.
User response: None
Explanation: The script name specified in a DEFINE,
UPDATE, or DELETE SCRIPT command does not exist.
ANR1461I command name: Executing command
System action: The operation fails. script command script name.
User response: Reenter the command specifying a Explanation: The specified command script is being
different command name. executed as a result of a RUN command.
System action: None
User response: None
script name updated.
Explanation: The script name specified in an UPDATE
SCRIPT command was successfully updated.
script name completed successfully.
System action: None
Explanation: The specified command script, started
User response: None with a RUN command, has successfully completed.
System action: None
User response: None
script name deleted.
Explanation: The script name specified in a DELETE
ANR1463E command name: Command script command
COMMAND command was successfully deleted.
script name completed in error.
System action: None
User response: None with a RUN command, encountered errors.
System action: Part or all of the command lines in the
ANR1458I command name: Line line number was script ended in error. Command processing is
deleted from command script command terminated.
script name.
User response: Examine the messages preceeding this
Explanation: The specified line number was deleted message to determine the cause of the error. Correct the
from the command script as a result of a DELETE command script and reissue the command.
SCRIPT command.
System action: None ANR1464E command name: Command script command
script name, line line number, parameter
User response: None parameter number was not specified:
command line.
Explanation: All parameters required to execute a

ANR1465E ANR1474E
command script were not specified in the RUN User response: Correct the script and reenter the RUN
command. command.
User response: Reenter the RUN command specifying
script name completed successfully
all required parameters.
(PREVIEW mode).
with a RUN command, has successfully completed.
script name, line line number, parameter is
invalid: command line. System action: None.
Explanation: An invalid parameter was encountered User response: None.
in a command script.
System action: The command fails. ANR1471E command name: Command script command
script name completed in error
User response: Correct the script definition and
(PREVIEW mode).
reexecute the RUN command.
with a RUN command, encountered errors.
script name, Line line number : command System action: Part or all of the command lines in the
line. command script ended in error. Command processing
is terminated.
Explanation: The specified line for the command
script is being executed. The contects of the line being User response: Examine the messages preceeding this
executed are displayed. message to determine the cause of the error. Correct the
script and reissue the command.
System action: None
User response: None
script name renamed to new command
ANR1467E command name: Command script command script name.
script name, did not end in a
Explanation: The specified command script was
non-continued line command line.
renamed with the RENAME SCRIPT command.
Explanation: The specified command script did not
end in a line that had no continuation character (-).
User response: Correct the specified script so that it
ANR1473E command name: A command line cannot
ends in a line that is not continued to the next line.
be specified when the FILE= parameter
is used.
Explanation: The FILE= parameter was specified in
script name, continued line is too long
the DEFINE SCRIPT command AND a command line
Explanation: The specified command script with was also specified for the SCRIPT. When the FILE=
continuation lines is too long to be executed. parameter is specified, a command line cannot be
specified.
User response: Correct the specified command script
so that it is shorter. User response: Reenter the command without the
command line OR the FILE= parameter.

script name, Line line number is an ANR1474E command name: A line number cannot be
INVALID command : command line. specified when the FILE= parameter is
used.
Explanation: The specified line for the command
script is not a valid server command. This message is Explanation: The FILE= parameter was specified in
displayed when a RUN command is executed with the the DEFINE SCRIPT command AND a line number
PREVIEW=YES parameter specified. was also specified for the SCRIPT. When the FILE=
parameter is specified, a line number cannot be
System action: Command Preview processing fails specified.
ANR1475E ANR1484I

ANR1479I command name: Query output was
User response: Reenter the command without the line written to file file name.
number OR the FILE= parameter.
Explanation: The output from the specified query was
successfully written to the specified file.
ANR1475E command name: File file name could not be
System action: The command completes successfully.
opened.
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.
User response: Examine any messages that might
Explanation: The specified description text is too long
appear prior to this one in the activity log to determine
for a command that allows description text to be
if the error can be found. If the file was to exist for use
specified.
by the command, ensure that the file does exists and
that the server has proper authority to access the file. If System action: The command fails.
the file was to be created by the command, ensure that
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.
User response: Add script command lines to the file
command line or description text.
or specify another file and reenter the command.
ANR1482I command name: Found label statement label

ANR1477E command name: The OUTPUTFILE
on line line number and continuing.
parameter may only be specified when
FORMAT=RAW is specified. Explanation: This message is issued during a RUN
command (VERBOSE=YES) to indicate that the target
Explanation: The OUTPUTFILE parameter was
label for a GOTO statement was found.
specified in a QUERY SCRIPT command but the
FORMAT parameter did not specify RAW output. System action: Command processing continues.
When outputting the QUERY to a file, you MUST
specify RAW output format. User response: None.

ANR1483I command name: Line line number
User response: Reenter the command specifyingthe condition IF(condition) is NOT true -
proper value for the FORMAT parameter or do not statement is skipped.
specify the OUTPUTFILE parameter.
command (VERBOSE=YES) to indicate that the a return
ANR1478E command name: Error writing to file file code condition check failed and the IF(..) statement is
name. skipped.
Explanation: An error was encountered while writing System action: Command processing continues.
to the file specified.
User response: Examine any messages that might ANR1484I command name: Line line number
appear prior to this one in the activity log to determine condition IF(condition) is TRUE -
if the error can be found. Ensure that the filesystem has statement will be executed.
sufficient space and that the server has authority to
create the file in the location specified. Explanation: This message is issued during a RUN
command (VERBOSE=YES) to indicate that the a return

ANR1485I ANR1493E
code condition check succeeded and the IF(..) statement System action: Command processing fails.
is executed.
User response: Correct the SCRIPT definition and
System action: Command processing continues. reenter the RUN command.
ANR1490W command name: Command script command
script name does not contain any
ANR1485I command name: Ending SCRIPT with
commands.
EXIT statement on line line number.
Explanation: The script name specified in a RUN
command does not contain any commands.
command (VERBOSE=YES) to indicate that an EXIT
statement was encountered and SCRIPT termination System action: The RUN operation fails (has nothing
will end. to do).
System action: The SCRIPT command ends. 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

ANR1491E Server command scripts cannot be
GOTO label name.
started from the server console.
Explanation: A server command script RUN
command (VERBOSE=YES) to indicate that a GOTO
command was issued from the server console. Server
statement was encountered and processing will skip to
command scripts cannot be started from the server
the named label.
console because they may require a long time to
System action: SCRIPT processing continues. complete and the server console should be available to
control other server functions.
continues processing.
ANR1487I command name: Command return code is
symbolic return code (return code severity). User response: Start the server command script from
an administrative client or schedule it for execution
Explanation: This message is issued during a RUN using the administrative command scheduler.
command (VERBOSE=YES) to indicate the return code
that was returned from the latest command.
ANR1492E command name: A loop has been detected
System action: SCRIPT processing continues. in server command script RUN
User response: None. commands - command failed.
Explanation: A server command script DEFINE or
ANR1488E command name: Line line number UPDATE command has created a situation where one
condition IF(condition) is not a valid or more scripts invoke each other in a loop that can
condition. cause the scripts to run idefinitely.
Explanation: This message is issued if an IF() System action: The command fails to update the
statement in a SCRIPT does not specify proper server command script.
condition values. User response: Server command scripts can invoke
System action: Command processing fails. each other, but not in a fashion that causes a potential
loop in their execution. Specify the scripts in a manner
User response: Reenter the command using valid that does not cause them to invoke each other in a
conditions for the IF() statement. loop.
ANR1489E command name: Line line number is a ANR1493E Command: Administrator administrator
GOTO to a label (label name) that does name is not authorized to update or
not exist or is associated with a line delete command script command script
prior to line line number. name.
Explanation: This message is issued if a GOTO Explanation: The specified administrator has entered
statement in a SCRIPT does not specify a label that the indicated command, but this administrator does not
exists in the SCRIPT, or that does exist but is associated have the proper authority necessary to update or delete
with a line prior to the line that contains the GOTO this command script. If an administrator does not have
statement.
ANR1494I ANR1504I
system authority, they must have previously created or

ANR1499S
updated the script.
Explanation: The ISSUE MESSAGE command with a
severity indicator of SEVERE was issued.
command.
User response: Issue the command from a properly
authorized administrator ID, or contact the User response: None.
administrator that created the script.
ANR1500I Policy domain domain name defined.
ANR1494I command name: Command return code is
Explanation: In response to the DEFINE DOMAIN
numeric return code.
command, the policy domain domain name has been
Explanation: This message is issued during a RUN defined in the server database.
command (VERBOSE=YES) to indicate the numeric
return code that was returned from the latest
command. User response: None.
System action: SCRIPT processing continues.
ANR1501I Policy domain domain name deleted.
Explanation: In response to the DELETE DOMAIN
ANR1495E command name: command script name is
deleted from the server database. All policy sets,
currently running. Define, update or
management classes, copy groups, and schedules
delete can not be performed.
related to the domain have also been removed.
Explanation: An DEFINE, UPDATE or DELETE
SCRIPT was attempted on a script that is currently
running. User response: None.
ANR1502I Policy domain domain name updated.
User response: Reenter the command when the script
is not running. Explanation: In response to the UPDATE DOMAIN
updated in the server database.
ANR1496I
severity indicator of INFORMATION was issued. User response: None.
ANR1503I Policy domain domain name copied to
domain target domain.
Explanation: In response to the COPY DOMAIN
ANR1497W
Explanation: The ISSUE MESSAGE command with a copied to a new policy domain named target domain.
severity indicator of WARNING was issued. All policy sets, management classes, and copy groups
are also copied to the target domain policy domain.
ANR1498E
ANR1504I Command: No matching domains.
severity indicator of ERROR was issued. Explanation: The server cannot find any policy
domains with names that match the specification
entered in the command command.
User response: Reissue the command with a
specification that matches an existing policy domain
name. Use the QUERY DOMAIN command to obtain a
list of the names of existing policy domains.

ANR1505W ANR1512I
ANR1505W The BACKUP copy group in ANR1508E Command: An incorrect table of contents
management class management class name load retention retention value was
specifies a table of contents destination specified.
storage pool : storage pool name that does
Explanation: A SET TOCLOADRETENTION
not exist. If this pool does not exist
command has been entered that specifies an invalid
when policy set policy set name is
table of contents (TOC) retention period.
activated, the creation of the table of
contents may fail for an image backup System action: The server does not process the
when this management class is used for command.
the backup.
Explanation: This message may be returned from the retention period.
DEFINE COPYGROUP, UPDATE COPYGROUP,
VALIDATE POLICYSET or ACTIVATE POLICYSET
command. During the indicated command processing, ANR1509E Error writing option option name to file
the server has found a backup copy group that has a file name.
table of contents (TOC) destination referring to an Explanation: An error was encountered while writing
undefined storage pool named storage pool name. If this an option entry to server option file.
storage pool is undefined when the policy set is
activated, the creation of the TOC for an image backup System action: The format command fails.
will fail if its TOC creation binds to the management User response: Examine any messages that might
class whose copy groups reference this pool. appear prior to this one in the activity log to determine
System action: Server operation continues. if the error can be found. Ensure that the filesystem has
sufficient space and that the server has authority to
User response: To locate the copy groups that refer to update the server option file then reissue the format
the undefined storage pool, issue the QUERY command.
COPYGROUP command. To change the TOC
destination to refer to an existing storage pool, issue
the UPDATE COPYGROUP command. To define the ANR1510I Policy set set name defined in policy
storage pool, an authorized administrator can issue the domain domain name.
DEFINE STGPOOL command. Explanation: In response to the DEFINE POLICYSET
command, the policy set named set name has been
ANR1506E Command: An incorrect storage pool defined in the policy domain named domain name in the
name - storage pool name was specified server database.
for the TOC destination. System action: Server operation continues.
Explanation: Server processing for the command User response: None.
command fails because the storage pool name pool name
specified for the table of contents (TOC) is an invalid
destination storage pool type. A copy storage pool or ANR1511I Policy set set name deleted from policy
an active-data storage pool is not a valid copy group domain domain name.
TOC destination. Explanation: In response to the DELETE POLICYSET
System action: The command fails and server command, the policy set set name has been deleted from
operation continues. the policy domain domain name in the server database.
User response: Reissue the command using a storage System action: Server operation continues.
pool name that is not a copy pool or active-data pool. User response: None.
For a list of names of defined storage pools, issue the
QUERY STGPOOL command.
ANR1512I Policy set set name updated in policy
domain domain name.
ANR1507I Table of contents load retention is set to
number of minutes minutes. Explanation: In response to the UPDATE POLICYSET
command, the policy set set name has been updated in
Explanation: The number of minutes that the the policy domain domain name in the server database.
unreferenced table of contents (TOC) data will remain
loaded in the server database has been set to the value System action: Server operation continues.
indicated with the SET TOCLOADRETENTION
command.
ANR1513I ANR1520I
ANR1513I Policy set set name copied to set new set ANR1516E Command: Storage pool storage pool name
name in policy domain domain name. is not enabled for deduplication.
Explanation: In response to the COPY POLICYSET Explanation: The command indicated specifies the
command, the policy set set name has been copied to name of a storage pool which does not have
the policy set new set name in the policy domain named deduplication enabled. The command requires that
domain name. All management classes and copy groups deduplication be enabled on the storage pool before the
are also copied to the policy set new set name. command can execute.
System action: Server operation continues. System action: The server does not process the
command.
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
policy set will be used by clients that start sessions Explanation: This message indicates the total number
after this command is committed. Clients that currently of database records that were successfully inserted
have sessions established with the server will use the during database insert processing.
policy definitions in the previously active policy set for
the domain.
System action: The server replaces the active
management class and copy group definitions for the
policy domain with the definitions found in the ANR1518I Insertdb command: Read number of bytes
specified policy set. These values are returned to client bytes.
nodes that start a session with the server after this
command is committed to the server database. Explanation: This message indicates the total number
of bytes that were successfully read during database
User response: None. insert processing.
ANR1515I Policy set set name validated in domain
domain name (ready for activation). User response: None.
Explanation: This message may be displayed in

response to a VALIDATE POLICYSET command. The ANR1519I Insertdb command: Elapsed time was
policy set set name has been checked in the domain elapsed time.
domain name to see if the management class and copy Explanation: This message indicates the total amount
group definitions are adequate for activating the policy of time that elapsed during database insert processing.
set. This message indicates that the policy set may be
activated. Warning messages may be issued prior to System action: Server processing continues.
this message if there are discrepancies in the policy set User response: None.
with respect to the set that is currently active in the
policy domain.
ANR1520I Management class class name defined in
System action: The server checks its definitions to policy domain domain name, set set name.
determine the policy sets qualifications for activation.
The server does not activate the policy set. Explanation: In response to the DEFINE
MGMTCLASS command, the management class named
User response: If you are satisfied with any warning class name has been defined in the policy set set name
messages that may have been issued prior to this belonging to the policy domain named domain name.
message concerning any possible discrepancies in the
policy set, issue the ACTIVATE POLICYSET command System action: Server operation continues.
to activate the policy set in the policy domain. User response: None.
Otherwise, correct the discrepancies prior to activating
the policy set. Before the ACTIVATE POLICYSET
command is used to activate the policy set, use the
validate command to check policy set contents.

ANR1521I ANR1530I
ANR1521I Management class class name deleted ANR1526I Insertdb command: Building indices and
from policy domain domain name, set set checking table integrity.
name.
Explanation: The database insert process has begun to
Explanation: In response to a DELETE MGMTCLASS create indices and check the integrity of the database
command, the management class named class name has tables.
been deleted from the policy set set name belonging to
the policy domain domain name. All copy groups
defined for the management class are also removed. User response: None.
ANR1527I command: Checked database objects of
database objects database objects in elapsed
time.
ANR1522I Management class class name updated in
Explanation: The command has checked the integrity
policy domain domain name, set set name.
of the indicated number of database tables.
Explanation: In response to the UPDATE
MGMTCLASS command, the management class named
class name has been updated in the policy domain User response: None.
domain name, policy set set name.
System action: Server operation continues. ANR1528I RUNSTATS: Table updating statistics
completed in elapsed time.
Explanation: This message indicates the update
statistics for all tables completed.
ANR1523I Management class class name copied to
class new class name in policy domain System action: Server processing continues.
domain name, set set name.
Explanation: In response to the COPY MGMTCLASS
command, the management class named class name has
been copied to a new management class named new ANR1529I Process process ID skipped File state
class name in policy set set name belonging to policy deduplicated extent Extent id on volume
domain domain name. All copy groups defined for Volume name.
management class class name are also copied to Explanation: While moving or copying deduplicated
management class new class name. extents from a sequential FILE volume, extents were
System action: Server operation continues. encountered that were marked deleted or damaged. As
a result, the extents were skipped.
System action: The server moves or copies all extents
from the volume that are not marked damaged or
ANR1524I Insertdb command: Beginning database deleted. The damaged or deleted extents are skipped.
update phase.
User response: If the deduplicated extent was marked
Explanation: The database insert process has damaged, audit the indicated volume with FIX=NO to
completed inserting database records, and has begun verify whether the file is damaged. The audit will reset
making updates to the inserted records. the file status if the deduplicated extent is not
damaged.
If the deduplicated extent has been marked deleted, it
is not copied to another storage pool.
ANR1525I command: Updated database entries of

ANR1530I Backup copy group group name defined
database entries database entries in elapsed
in policy domain domain name, set set
time.
name, management class class name.
Explanation: The command has updated the indicated
Explanation: In response to the DEFINE
number of database entries.
COPYGROUP command, a backup copy group named
System action: None. group name has been defined for the management class
named class name in the policy set set name belonging to
ANR1531I ANR1538I
User response: None. However, doing so can result in unrecoverable data loss
if a data-integrity error occurs. As a best practice, do
not change the default.
ANR1531I Backup copy group group name deleted
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
COPYGROUP command, the backup copy group
named group name has been deleted from the Explanation: In response to the DEFINE
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
named class name in the policy set set name belonging to
ANR1532I Backup copy group group name updated
name, management class class name. ANR1536I Archive copy group group name deleted
from policy domain domain name, set set
COPYGROUP command, the backup copy group
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
name belonging to policy domain domain name. named group name has been deleted from the
management class named class name in the policy set set
name belonging to policy domain domain name.
ANR1533E command: The target client version that
was specified is not valid. The value
name value: value in the form V.R.M.F. ( ANR1537I Archive copy group group name updated
Version, Release, Modification, and Fix in policy domain domain name, set set
Level ) is incorrect. name, management class class name.
Explanation: During pre-processing of command Explanation: In response to the UPDATE
command, an invalid value was encountered for the COPYGROUP command, the archive copy group
client target level. The correct client target level should named group name has been updated in the
be formatted like 6.2.0.0 management class named class name in the policy set set
name belonging to policy domain domain name.
System action: The register/update node fails.
User response: Specify the correct client target level,
then reissue the command. User response: None.
ANR1534I Process process ID skipped Num Files ANR1538I Default management class set to class
deduplicated files on volume Volume name for policy domain domain name, set
name because copies of the files were set name.
not found.
Explanation: The default management class for the
Explanation: The DEDUPREQUIRESBACKUP server policy set set name in policy domain domain name has
option is set to YES. If the value of this option is YES been set to the management class named class name.
(the default), files within a deduplicated storage pool
System action: If this policy set is activated, clients
must be backed up to a non-deduplicated copy storage
use this management class for backup-archive
pool before the files can be moved.
processing by default, or if other management classes
System action: The operation skips the files without specified for binding do not exist in the policy set.
copies and continues the operation.
User response: Ensure that all files in the primary
storage pool are backed up to a non-deduplicated copy
storage pool. You can also change the value of the
DEDUPREQUIRESBACKUP server option to NO.

ANR1539S ANR1546W
ANR1539S A previous database upgrade did not ANR1543E Export command: Preview processing
succeed. The server cannot start. stopped. The connection with the target
server is broken.
Explanation: A DSMSERV INSERTDB command used
to upgrade from Tivoli Storage Manager V5 failed or Explanation: The communications link with the target
was cancelled. The result is a database that does not server broke because of a network error or because the
contain all of the data from the original database. The target-server import process stopped.
server cannot be run with an incomplete database.
System action: The export process ends.
System action: The server will not start.
User response: Examine the activity log of the target
User response: Rerun the DSMSERV INSERTDB server to determine if the import process stopped. A
command. network failure can also cause this message to be
displayed. If many communication error messages
occur simultaneously, check the network for failure and
ANR1540E Import command: The processing stopped.
The connection with the source server is
broken.
ANR1544I The DEDUPTIER3FILESIZE option
Explanation: The communications link with the source
value is temporarily updated from old
server broke because of a network error or because the
value to new value.
source-server export process stopped.
Explanation: The value for the DEDUPTIER3FILESIZE
System action: The import process ends.
option must be greater than or equal to the value for
User response: Examine the activity log of the source the DEDUPTIER2FILESIZE option. The value for the
server to determine if the export process stopped. A DEDUPTIER3FILESIZE option is increased to match the
network failure can also cause this message to be value for the DEDUPTIER2FILESIZE option until the
displayed. If many communication error messages server is restarted or until the value for the
occur simultaneously, check the network for failure and DEDUPTIER3FILESIZE option is updated with the
correct any problems. SETOPT command.
ANR1541E Export command: The processing stopped.
User response: Use the SETOPT command to update
The connection with the target server is
the value for either the DEDUPTIER2FILESIZE option
broken.
or the DEDUPTIER3FILESIZE option. Ensure that the
Explanation: The communications link with the target value for the DEDUPTIER3FILESIZE option is greater
server broke because of a network error or because the than or equal to the value for the
target-server import process stopped. DEDUPTIER2FILESIZE option when you are specifying
the values.
System action: The export process ends.
User response: Examine the activity log of the target ANR1545W The diagpath ( path ) file system or disk
server to determine if the import process stopped. A is becoming full. Space available: space
network failure can also cause this message to be available MB of total space MB. Percent
displayed. If many communication error messages full: file system used ratio percent.
occur simultaneously, check the network for failure and
correct any problems. Explanation: The file system or disk containing the
db2diag.log file is becoming full. This could cause
problems with the server if other DB2 or server
ANR1542E Import command: Preview processing databases are in this space.
stopped. The connection with the source
server is broken. System action: None.
Explanation: The communications link with the source User response: Add space to the file system or free up
server broke because of a network error or because the space on the file system or disk.
source-server export process stopped.
System action: The import process ends. ANR1546W Available space for the directory (path) is
less than 1 GB. If there is no space
User response: Examine the activity log of the source available the server can no longer
server to determine if the export process stopped. A function correctly.
displayed. If many communication error messages Explanation: There is less than 1 GB of available space
occur simultaneously, check the network for failure and in the file system or disk where the server database
correct any problems. files are located. When a server is initially created, with
the DSMSERV FORMAT utility or with the
ANR1547W ANR1551W
configuration wizard, a server database and recovery primary storage pool to remove the specified next
log are created. In addition, files are created to hold storage pool from the parameter NEXTSTGPOOLS.
database information used by the database manager. Alternatively, an authorized administrator can enable
The specified path is the location of the database LAN-free backup to the specified next storage pool.
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
System action: None. 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
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
Explanation: There was not enough free space in the policy set set name is activated, files bound to this
filesystem or drive to create db2diag.log files. management class in domain domain name are
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
and logattr.chk have been updated, you must change User response: If you do not want files to be rebound
them to the current value so that they are consistent to the default management class, define a management
with the value stored in the database manager. Free the class with the name specified in the message for the
required disk space and update the DBDIAGLOGSIZE policy set. To define the proper copy group attributes,
option. reference the management class definition in the
ACTIVE policy set or copy the management class class
name from the ACTIVE policy set to policy set set name
ANR1548E The server failed to format or initialize using the COPY MGMTCLAS command.
because the available space (free
spacebytes) in the diagnostic data
directory path path is less than 2MB to ANR1551W BACKUP copygroup group name in
allocate db2diag.log files; management class class name is NOT
defined in policy set set name but is
Explanation: There was not enough free space in the defined in the ACTIVE policy set for
diagnostic directory to allocate 2MB db2diag.log files. domain domain name: files bound to this
System action: The server stops. management class will no longer be
backed up if/when set name is activated.
User response: Free the required disk space in the
diagnostic directory to at least 2MB and then run the Explanation: This message may be returned from the
command again. VALIDATE POLICYSET or ACTIVATE POLICYSET
server has found a backup copy group named group
ANR1549W Transaction failed for session session name for management class class name in the currently
number for node node name (client active policy set, but the copy group is not defined for
platform). The next storage pool pool name the management class in the policy set being validated
for the primary storage pool pool name or activated (set name). If policy set set name is
cannot be a target for LAN-free backup. activated, files bound to management class class name in
Explanation: The server rolled back a database update domain domain name will no longer be eligible for
transaction for the specified session because the backup processing.
specified next storage pool of the specified primary System action: Server operation continues.
storage pool cannot be a target for LAN-free backup.
User response: If you want files bound to this
System action: The specified session is ended and management class to be eligible for backup processing,
server operation continues. define an archive copy group for management class
User response: An authorized administrator can issue class name by using the DEFINE COPYGROUP
the UPDATE STGPOOL command for the specified command.

ANR1552W ANR1555W
ANR1552W ARCHIVE copygroup group name in ANR1554W DEFAULT Management class class name
management class class name is NOT in policy set domain name set name does
defined in policy set set name but is not have an ARCHIVE copygroup: files
defined in the ACTIVE policy set for will not be archived by default if this
domain domain name: attempting to set is activated.
archive files specifiying this
management class will fail if set name is
activated.
command. During policy set validation for policy set
Explanation: This message may be returned from the set name in policy domain domain name, the server has
VALIDATE POLICYSET or ACTIVATE POLICYSET found that the default management class named class
command. During policy set validation processing, the name does not have an archive copy group. This
server has found an archive copy group named group message warns the administrator that activation of this
name for management class class name in the currently policy set will result in client files not being allowed
active policy set, but the copy group is not defined for archive processing unless they are bound to a
the management class in the policy set being validated management class (which has an archive copy group)
or activated (set name). If policy set set name is other than the default.
activated, attempting to archive files specifiying this
management class will fail. Existing archives bound to
this management class on the TSM server will be User response: To define a backup copy group for the
expired based on the defmgmtclass values, or the management class, issue the DEFINE COPYGROUP
archive retention grace period for the policy domain, if command. To assign a different default management
the default management class does not contain an class for the domain, issue the ASSIGN
archive copygroup. DEFMGMTCLASS command. Take either action if you
want files to be eligible for archive processing by
default.
User response: To archive files specifying this
management class, define an archive copy group for
ANR1555W The BACKUP copy group in
management class class name by using the DEFINE
COPYGROUP command.
specifies a destination that does not
refer to a defined storage pool: storage
ANR1553W DEFAULT Management class class name pool name. If this pool does not exist
in policy set domain name set name does when policy set policy set name is
not have a BACKUP copygroup: files activated, clients will fail when using
will not be backed up by default if this this management class to backup files to
set is activated. the server.
Explanation: This message may be returned from the Explanation: This message may be returned from the
VALIDATE POLICYSET or ACTIVATE POLICYSET VALIDATE POLICYSET or ACTIVATE POLICYSET
command. During policy set validation for policy set command. During policy set validation for set name, the
set name in policy domain domain name, the server has server has found a backup copy group destination that
found that the default management class named class references an undefined storage pool named pool name.
name does not have a backup copy group. This message If this storage pool is undefined when the policy set is
warns the administrator that activation of this policy activated, backup or archive operations will fail for
set results in client files not being backed up, unless clients with files bound to the management class whose
they are bound to a management class (which has a copy groups reference this pool.
copy group) other than the default.
User response: To locate the copy groups that refer to
User response: To define a backup copy group for the the undefined storage pool, issue the QUERY
management class, issue the DEFINE COPYGROUP COPYGROUP command. To change the destination to
command. To assign a different default management refer to an existing storage pool, issue the UPDATE
class for the domain, issue the ASSIGN COPYGROUP command. To define the storage pool, an
DEFMGMTCLASS command. Take either action if you authorized administrator can issue the DEFINE
want files to be backed up by default. STGPOOL command.
ANR1556W ANR1560E
ANR1556W The ARCHIVE copy group in ANR1558E The space management migration
management class management class name destination in management class
specifies a destination that does not management class name in policy set policy
refer to a defined storage pool: storage set name refers to copy storage pool:
pool name. If this pool does not exist storage pool name. Copy storage pools are
when policy set policy set name is not a valid migration destination.
activated, clients will fail when using
this management class to archive files to
the server.
command. During policy set validation for set name, the
Explanation: This message may be returned from the server has found a space management migration
VALIDATE POLICYSET or ACTIVATE POLICYSET destination that references a copy storage pool named
command. During policy set validation for set name, the pool name.
server has found a archive copy group destination that
System action: Server operation continues. The policy
references an undefined storage pool named pool name.
set is not activated.
If this storage pool is undefined when the policy set is
activated, backup or archive operations will fail for User response: To locate the management class that
clients with files bound to the management class whose refers to the copy storage pool, issue the QUERY
copy groups reference this pool. MGMTCLASS command. To change the destination to
refer to a non-copy storage pool, issue the UPDATE
MGMTCLASS command.
User response: To locate the copy groups that refer to
the undefined storage pool, issue the QUERY
ANR1559E The copy group destination for type
COPYGROUP command. To change the destination to
copy group type in management class
refer to an existing storage pool, issue the UPDATE
management class name in policy set policy
COPYGROUP command. To define the storage pool, an
set name refers to copy storage pool:
authorized administrator can issue the DEFINE
storage pool name. Copy storage pools are
STGPOOL command.
not a valid copy group destination.
ANR1557W The space management migration
destination in management class
command. During policy set validation for set name, the
management class name does not refer to a
server has found a copy group destination that
defined storage pool: storage pool name. If
references a copy storage pool named pool name.
this pool does not exist when policy set
policy set name is activated, clients will System action: Server operation continues. The policy
fail when using this management class set is not activated.
to migrate space-managed files to the
server. User response: To locate the management class that
refers to the copy storage pool, issue the QUERY
Explanation: This message may be returned from the MGMTCLASS command. To change the destination to
VALIDATE POLICYSET or ACTIVATE POLICYSET refer to a non-copy storage pool, issue the UPDATE
command. During policy set validation for set name, the MGMTCLASS command.
server has found a space management migration
destination that references an undefined storage pool
named pool name. If this storage pool is undefined ANR1560E Command: Invalid policy domain name -
when the policy set is activated, space management domain name.
migration operations will fail for clients with files Explanation: Server processing for the command
bound to the management class that references this command fails because the policy domain name domain
pool. name specified does not contain valid characters or
System action: Server operation continues. contains too many characters.
User response: To locate the management class that System action: Database changes for the command are
refers to the undefined storage pool, issue the QUERY rolled back and server operation continues. The
MGMTCLASS command. To change the destination to command is not successful in changing the server
refer to an existing storage pool, issue the UPDATE database.
MGMTCLASS command. To define the storage pool, an User response: Reissue the command and specify a
authorized administrator can issue the DEFINE policy domain name that conforms to these name
STGPOOL command. requirements. For information on the character and
length specifications for valid policy domain names,
platform.

ANR1561E ANR1567E
for the DEFINE COPYGROUP or UPDATE

ANR1561E Command: Missing policy domain name.
COPYGROUP commands, refer to the Administrators
Explanation: Server processing for the command Reference for your particular platform.
command fails because the required policy domain
parameter has not been specified.
ANR1565E Command: Invalid policy set name - set
System action: Database changes for the command are name.
rolled back and server operation continues. The
Explanation: Server processing for the command
command is not successful in changing the server
command fails because the policy set name set name
database.
specified does not contain valid characters or contains
User response: Reissue the command and specify a too many characters.
valid policy domain name.
System action: Database changes for the command are
ANR1562E Command: Policy domain description command is not successful in changing the server
exceeds length limit characters. database.
Explanation: Server processing for the command User response: Reissue the command and specify a
command fails because the policy domain description policy set name that conforms to valid name
specified is longer than the length limit number of requirements. For information on the character and
characters allowed. length specifications for valid policy set names, refer to
the Administrators Reference for your particular
platform.
database. ANR1566E Command: Policy set description exceeds
length limit characters.
shorter policy domain description. Explanation: Server processing for the command
command fails because the policy set description
specified is longer than the length limit number of
ANR1563E Command: Invalid retention period for
characters allowed.
BACKRETN parameter - retention value.
Explanation: Server processing for the copy group
command command fails because the value (retention
value) specified for the BACKRETN parameter is not
database.
valid.
shorter policy set description.
database. ANR1567E Command: Invalid management class
name - class name.
valid BACKRETN value. For valid BACKRETN values Explanation: Server processing for the command
for the DEFINE COPYGROUP or UPDATE command fails because the management class name class
COPYGROUP commands, refer to the Administrators name specified does not contain valid characters or
Reference for your particular platform. contains too many characters.
ANR1564E Command: Invalid retention period for rolled back and server operation continues. The
ARCHRETN parameter - retention value. command is not successful in changing the server
database.
command command fails because the value (retention User response: Reissue the command and specify a
value) specified for the ARCHRETN parameter is not management class name that conforms to valid name
valid. requirements. For information on the character and
length specifications for valid management class names,
platform.
database.
valid ARCHRETN value. For valid ARCHRETN values
ANR1568E ANR1574E
characters or contains too many characters.

ANR1568E Command: Management class description
exceeds length limit characters. System action: Database changes for the command are
command fails because the management class
database.
description specified is longer than the length limit
number of characters allowed. User response: Reissue the command and specify a
storage pool name that conforms to valid name
requirements. For information on the character and
length specifications for valid storage pool names, refer
to the Administrators Reference for your particular
database.
platform. For a list of names of defined storage pools,
User response: Reissue the command and specify a issue the QUERY STGPOOL command.
shorter management class description. Refer to the
Administrators Guide for your particular platform for
ANR1572E Command: Missing copy destination.
more information.
command command fails because the required copy
ANR1569E Command: Invalid copy group name -
group destination is not specified.
group name.
command fails because the copy group name group name
specified does not contain valid characters or contains
database.
too many characters.
User response: Reissue the command and specify the
required copy group destination (DEST).
database. ANR1573E Command: Invalid copy type - type value.
User response: Reissue the command and specify a Explanation: Server processing for the copy group
copy group name that conforms to valid name command command fails because the value (type value)
requirements. For information on the character and specified for the TYPE parameter is not valid.
length specifications for valid copy group names, refer
to the Administrators Reference for your particular System action: Database changes for the command are
platform. rolled back and server operation continues. The
database.
ANR1570E Command: Invalid copy frequency -
frequency value. User response: Reissue the command and specify a
valid TYPE value. For valid TYPE values for the
Explanation: Server processing for the copy group DEFINE COPYGROUP or UPDATE COPYGROUP
command command fails because the value (frequency commands, refer to the Administrators Reference for
value) specified for the FREQUENCY parameter is not your particular platform.
valid.
System action: Database changes for the command are ANR1574E Command: Invalid version count for
rolled back and server operation continues. The VEREXISTS parameter - version value.
database. Explanation: Server processing for the copy group
command command fails because the value (version
User response: Reissue the command and specify a value) specified for the VEREXISTS parameter is not
valid FREQUENCY value. For valid FREQUENCY valid.
values for the DEFINE COPYGROUP or UPDATE
COPYGROUP commands, refer to the Administrators System action: Database changes for the command are
Reference for your particular platform. rolled back and server operation continues. The
database.
ANR1571E Command: Invalid copy destination - pool
name. User response: Reissue the command and specify a
valid VEREXISTS value. For valid VEREXISTS values
Explanation: Server processing for the command for the DEFINE COPYGROUP or UPDATE
command fails because the storage pool name pool name COPYGROUP commands, refer to the Administrators
specified for the copy group destination or for the table Reference for your particular platform.
of contents (TOC) destination does not contain valid

ANR1575E ANR1581E

ANR1575E Command: Invalid version count for
VERDELETED parameter - version value.
Explanation: Server processing for the copy group database.
command command fails because the value (version
value) specified for the VERDELETED parameter is not
valid RETVER value. For valid RETVER values for the
valid.
DEFINE COPYGROUP or UPDATE COPYGROUP
System action: Database changes for the command are commands, refer to the Administrators Reference for
rolled back and server operation continues. The your particular platform.
database.
ANR1579E Command: Invalid copy mode - mode
User response: Reissue the command and specify a value.
valid VERDELETED value. For valid VERDELETED
values for the DEFINE COPYGROUP or UPDATE
command command fails because the value (mode value)
specified for the MODE parameter is not valid.
RETEXTRA parameter - retention value.
database.
valid MODE value. For valid MODE values for the
value) specified for the RETEXTRA parameter is not
DEFINE COPYGROUP or UPDATE COPYGROUP
valid.
commands, refer to the Administrators Reference for
System action: Database changes for the command are your particular platform.
ANR1580E Command: Invalid copy serialization
database.
mode - serialization value.
valid RETEXTRA value. For valid RETEXTRA values
command command fails because the value (serialization
for the DEFINE COPYGROUP or UPDATE
value) specified for the SERIALIZATION parameter is
not valid.
RETONLY parameter - retention value.
database.
valid SERIALIZATION value. For valid
value) specified for the RETONLY parameter is not
SERIALIZATION values for the DEFINE COPYGROUP
valid.
or UPDATE COPYGROUP commands, refer to the
System action: Database changes for the command are Administrators Reference for your particular platform.
ANR1581E Command: The option option is valid only
database.
for backup copy groups.
Explanation: Server processing for the archive copy
valid RETONLY value. For valid RETONLY values for
group command command fails because the option
the DEFINE COPYGROUP or UPDATE COPYGROUP
specified is only valid for backup copy group
commands, refer to the Administrators Reference for
definitions.
your particular platform.
ANR1578E Command: Invalid version count for
RETVER parameter - retention value.
database.
User response: Reissue the command specifying valid
archive copy group options, or specify TYPE=BACKUP
value) specified for the RETVER parameter is not valid.
if the intent is to operate on a backup copy group. For
ANR1582E ANR1587E
valid archive copy group options, refer to the MODE parameter because the default value for MODE
Administrators Reference and Administrators Guide for is ABSOLUTE for archive copy groups. For valid
your particular platform. archive copy group options, refer to the Administrators
Reference and Administrators Guide for your particular
platform.
ANR1582E Command: The option option is valid only
for archive copy groups.
ANR1585E Command: Policy set ACTIVE cannot be
Explanation: Server processing for the backup copy
modified.
group command command fails because the option
specified is only valid for archive copy group Explanation: Server processing for the command
definitions. command fails because the policy set name ACTIVE is
specified. Objects in the ACTIVE policy set for a
domain may only be changed through activation of
another policy set.
database. System action: Database changes for the command are
User response: Reissue the command specifying valid
backup copy group options, or specifying
database.
TYPE=ARCHIVE if the intent is to operate on an
archive copy group. For valid backup copy group User response: Reissue the command specifying a
options, refer to the Administrators Reference and policy set other than ACTIVE. To copy the ACTIVE
Administrators Guide for your particular platform. policy set for a policy domain to another name so that
commands may be used to change its contents, issue
the COPY POLICYSET command. Then to activate the
ANR1583E Command: Copy frequency for archive
changes, issue the ACTIVATE POLICYSET command.
copy groups must be CMD - frequency
value is not valid.
ANR1586E Command: Invalid migration destination
Explanation: Server processing for the archive copy
- pool name.
group command command fails because a value other
than CMD has been specified for the FREQUENCY Explanation: Server processing for the command
parameter. The only value that may be specified for the command fails because the storage pool name pool name
archive copy group FREQUENCY parameter is CMD. specified for the migration destination is a copy pool. A
copy pool is not a valid migration destination.
rolled back and server operation continues. The System action: Database changes for the command are
command is not successful in changing the server rolled back and server operation continues. The
database. command is not successful in changing the server
database.
User response: Reissue the command specifying CMD
for the FREQUENCY parameter, or omitting the User response: Reissue the command using a storage
FREQUENCY parameter because the default value for pool name that is not a copy pool. For a list of names
FREQUENCY is CMD for archive copy groups. For of defined storage pools, issue the QUERY STGPOOL
valid archive copy group options, refer to the command.
Administrators Reference and Administrators Guide for
your particular platform.
ANR1587E Command: Invalid copy group
destination - pool name.
ANR1584E Command: Copy mode for archive copy
groups must be ABSOLUTE - mode value
command fails because the storage pool name pool name
is not valid.
specified for the copy group destination is a copy pool
Explanation: Server processing for the archive copy or active-data pool. A copy pool or active-data pool is
group command command fails because a value other not a valid copy group destination.
than ABSOLUTE has been specified for the MODE
parameter. The only value that may be specified for the
archive copy group MODE parameter is ABSOLUTE.
System action: Database changes for the command are database.
User response: Reissue the command using a storage
pool name that is a primary pool, not a copy pool or
database.
active-data pool. For a list of names of defined storage
User response: Reissue the command specifying pools, issue the QUERY STGPOOL command.
ABSOLUTE for the MODE parameter, or omitting the

ANR1588W ANR1594E
ANR1588W The value of the ANR1591E Command: Policy domain domain name is
ACTIVEDESTINATION parameter already defined.
received from the configuration manager
specifies a storage pool storage pool name
command fails because the policy domain name domain
for domain domain name that is not
name specified refers to a policy domain that is already
defined on the managed server.
defined in the server database.
Explanation: If the storage pool on the managed
server is undefined, the value of the
ACTIVEDESTINATION parameter for domain domain
name is not updated.
database.
User response: Reissue the command specifying a
User response: Define an active-data storage pool on policy domain name that is not defined in the server
the managed server with the same name as that on the database. For a list of the names of defined policy
configuration manager. domains in the server database, issue the QUERY
DOMAIN command.
ANR1589E Error reason code updating database
manager security plugin file name. ANR1592E Command: Policy domain domain name
still contains at least one policy set.
Explanation: The server was unable to update the
database manager security plugin. This plugin controls Explanation: Server processing for the delete
access to the database manager from the Tivoli Storage command command fails because the policy domain
Manager server. The reason code is the errno from the name domain name specified refers to a policy domain
fopen subroutine for the file. Some common reason that still contains at least one policy set.
codes are:
v 26 - The file is in use. rolled back and server operation continues. The
v 13 - Permission to write to the file is denied. On command is not successful in changing the server
Windows, this reason code can also indicate that the database.
file is in use.
User response: To delete the policy set from the policy
For other reason codes, refer to your operating system domain, issue the DELETE POLICYSET command.
reference guide for errno values.
System action: The server stops. ANR1593E Command: Policy domain domain name
still contains at least one node.
User response: Manually copy the file from the
installation directory to the location identified in the Explanation: Server processing for the delete
message, and restart the server. On AIX, you might also command command fails because the policy domain
need to run the /usr/sbin/slibclean command as root name domain name specified refers to a policy domain
after halting the server but before copying the file. This that still contains at least one node. A policy domain
procedure will unload the plugin from the kernel cannot be deleted if one or more client nodes are still
memory. assigned to the domain.
ANR1590E Command: Policy domain domain name is rolled back and server operation continues. The
not defined. command is not successful in changing the server
database.
command fails because the policy domain name domain User response: To remove remaining nodes from the
name specified does not refer to a defined policy policy domain, issue the REMOVE NODE command.
domain in the server database. After all nodes are removed, issue the delete command
again.
command is not successful in changing the server ANR1594E Command: Policy domain domain name
database. has no active policy set.
User response: Reissue the command specifying a Explanation: Server processing for the update or
policy domain name that is defined in the server register node command command fails because the
database. For a list of the names of defined policy policy domain name domain name specified refers to a
domains in the server database, issue the QUERY policy domain that does not have an active policy set
DOMAIN command. defined. Nodes cannot be assigned to policy domains
that do not have an active policy set.
ANR1595E ANR1600E

ANR1598E Command: No default management class
has been assigned for policy set set name
in domain domain name.
database.
User response: To activate a policy set for the
command fails because the policy set set name in policy
specified policy domain, issue the ACTIVATE
domain domain name does not have a default
POLICYSET command. After a policy set has been
management class assigned.
activated, client nodes may be assigned to the policy
domain. System action: Database changes for the command are
ANR1595E Command: Policy set set name is not
database.
defined in policy domain domain name.
User response: To assign a default management class
in the policy set, issue the ASSIGN DEFMGMTCLASS
command.
specified does not refer to a defined set in policy
domain domain name in the server database.
ANR1599E Command: Management class class name
is not defined in policy domain domain
name, set set name.
database. Explanation: Server processing for the command
command fails because the management class name class
name specified does not refer to a defined management
policy set name that is defined in the policy domain.
class in policy set set name belonging to policy domain
For a list of the names of defined policy sets in the
domain name.
policy domain, issue the QUERY POLICYSET
command. System action: Database changes for the command are
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 ANR1607E
names of defined copy groups and management classes

ANR1602E Command: Backup copy group group name
in the policy domain or policy set, issue the QUERY
is not defined in policy domain domain
COPYGROUP command.
name, set set name, management class
class name.
ANR1605E Command: Archive copy group group
name is already defined in policy
command fails because the backup copy group named
domain domain name, set set name,
group name specified for management class class name
management class class name.
does not refer to a defined backup copy group in
policy set set name belonging to policy domain domain Explanation: Server processing for the command
name. 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
policy set set name belonging to policy domain domain
name.
database.
copy group name that is defined. For a list of the
names of defined copy groups and management classes
database.
in the policy domain or policy set, issue the QUERY
COPYGROUP command. User response: Reissue the command specifying a
copy group that is not defined in the policy set. For a
list of the names of defined copy groups for
ANR1603E Command: Backup copy group group name
management classes in the policy domain and policy
is already defined in policy domain
set, issue the QUERY COPYGROUP command.
domain name, set set name, management
class class name.
ANR1606E Out of server LOG space in accessing
policy tables.
command fails because the specified backup copy group
named group name refers to a copy group that is Explanation: The server ends a database update
already defined for management class (class name) in transaction for policy information because sufficient log
policy set set name belonging to policy domain domain space is not available on the server.
name.
System action: The policy operation is ended and
System action: Database changes for the command are server operation continues.
command is not successful in changing the server User response: An authorized administrator can issue
database. the DEFINE LOGVOLUME command to add volumes
for use by the log and can issue the EXTEND LOG
User response: Reissue the command specifying a command to extend the size of the log so that the new
copy group that is not defined in the policy set. For a volumes are used.
list of the names of defined copy groups for
management classes in the policy domain and policy
set, issue the QUERY COPYGROUP command. ANR1607E Out of server DB space in accessing
policy tables.
ANR1604E Command: Archive copy group group Explanation: The server ends a database update
name is not defined in policy domain transaction for policy information because sufficient
domain name, set set name, management database space is not available on the server.
class class name. System action: The policy operation is ended and
Explanation: Server processing for the command server operation continues.
command fails because the archive copy group named User response: An authorized administrator can issue
group name specified for management class class name the DEFINE DBVOLUME command to add volumes
does not refer to a defined archive copy group in policy for use by the database and can issue the EXTEND DB
set set name belonging to policy domain domain name. command to extend the size of the database so that the
System action: Database changes for the command are new volumes are used.
database.
copy group name that is defined. For a list of the
ANR1608E ANR1614E

ANR1608E Error fetching entry for domain domain
name, set set name.
database.
Explanation: An internal server database error occurs
User response: Reissue the command and specify
while retrieving policy information for policy set set
another management class name.
name in domain domain name.
ANR1612E Command: Management class management
class name in policy set set name, domain
User response: Examine the server messages issued domain name specifies
prior to this message to determine the source of the MIGREQUIRESBKUP=YES, but
error. Use the QUERY ACTLOG command to view the contains no backup copy group.
Explanation: During policy set validation or activation
for policy set set name in policy domain domain name,
representative.
the server has found that the management class named
class name specifies the MIGREQUIRESBKUP=YES
ANR1609E Policy error: unable to find management parameter but does not contain a backup copy group.
class ID for class class name in policy set Policy set validation or activation fails in this case
set name belonging to domain domain because it would not be possible to ensure that
name. space-managed client files are backed up prior to being
migrated to the server.
Explanation: An internal server database error has
been encountered while retrieving policy information System action: Database changes for the command are
for management class class name in policy set set name rolled back and server operation continues. The
belonging to policy domain domain name. command is not successful in changing the server
database.
server operation continues. User response: To define a backup copy group within
the management class, issue the DEFINE COPYGROUP
command. To change the MIGREQUIRESBKUP
parameter, issue the UPDATE MGMTCLASS command.
be isolated and resolved, contact your service ANR1613E Command: Invalid retention initiation -
representative. retention initiation value.
ANR1610E Internal Server error: invalid copy type command command fails because the value (retention
copy type integer encountered in policy initiation value) specified for the RETINIT parameter is
set validation. not valid.
Explanation: An internal server database error has System action: The command fails.
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. For valid RETINIT values for
POLICYSET command.
the DEFINE copy group or UPDATE copy group
System action: The policy operation is ended and commands, refer to the Administrators Reference.
User response: Examine the server messages issued ANR1614E Command: Invalid number of days for
prior to this message to determine the source of the RETMIN parameter - days value.
Explanation: The command fails.
be isolated and resolved, contact your service System action: Database changes for the command are
representative. rolled back and server operation continues. The
database.
ANR1611E Command: Invalid management class
name - management class name. User response: Issue the command again and specify
a valid RETMIN value. For valid RETMIN values for
the DEFINE copy group or UPDATE copy group
command fails because the specified management class
commands, refer to the Administrators Reference.
name may not be used as a management class name.

ANR1615E ANR1621E
ANR1615E Command: RETVER of NOLIMIT cannot ANR1618W Command: the new RETMIN value (new
be specified with RETINIT value of days) is less than the value previously
EVENT. stored (old days) for domain policy set
management class.
command command fails because the retain versions Explanation: Processing for the copy group command
value of NOLIMIT is not allowed with the retention command detected that the new retain minimum
initiation value of EVENT. If this is the UPDATE copy number of days is less than the number of days
group command, at least one of the values might have currently stored for the copy group. The policy set
been defined already. might not activate when archive retention protection is
active, because the retain minimum days value is not
allowed to decrease.
command is not successful in changing the server System action: The copy group is updated and system
database. operation continues.
User response: Issue the command again and specify User response: The copy group will be updated, but
a valid RETVER or RETMIN value. For valid values for the copy group might fail validation when the policy
the DEFINE copy group or UPDATE copy group set is validated or activated.
commands, refer to the Administrators Reference.
ANR1619E The RETVER of NOLIMIT is not
ANR1616W Command: the specified RETMIN value allowed with the RETINIT value of
(new days) will be ignored because the EVENT for domain policy set management
RETINIT value is CREATION for class.
domain policy set management class.
Explanation: This message can be returned from the
Explanation: Processing for the copy group command VALIDATE POLICYSET or ACTIVATE POLICYSET
command detected that a retain minimum number of command. During policy set validation processing, the
days value was specified either with the retention server has found the the copy group in the policy has
initiation value of CREATION, or the current retention specified an invalid combination of options. Retain
initiation value stored for the copy group is versions of NOLIMIT and retention initiation of
CREATION. The retain minimum number of days EVENT are not allowed. The policy will not be
value is not used when the retention initiation value is validated or activated.
CREATION. The copy group will be defined or
updated, but the RETMIN value will not be stored.
User response: Update the RETVER or REINIT values
System action: The copy group is defined or updated
in the copy group. For valid values, refer to the
and system operation continues.
Administrators Reference for your platform.
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.
ANR1617W Command: the new RETVER value (new
days) is less than the value previously
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
ANR1622E ANR1627I

ANR1624E Command: Invalid active pool list - active
pool list name.
server has found that archive retention protection is
active and the the copy group has a retain minimum Explanation: Server processing for the command
days value that is less than the value in the ACTIVE command fails because the active pool list active pool list
policy set. The policy will not be validated or activated. specified does not contain valid pool.
System action: Server operation continues. System action: Database changes for the command are
User response: Update the RETMIN value in the copy
group.
database.
ANR1622E Management class class name is not
active pool list that conforms to these name
defined in policy set set name, but is
defined in the active policy set for
length specifications for valid active-data pool names,
domain domain name. Archive retention
protection is active, so validation fails.
platform.
ANR1625E command: Server is down-level compared
to the version of data being inserted
server found a management class named class name in
into the database: data version.
the currently active policy set, but not defined in the
policy set being validated or activated (set name). When Explanation: The DSMSERV INSERTDB command
archive retention protection is active, all management encountered data written by a version of the
classses in the active policy set must be included in the DSMUPGRD EXTRACTDB command that is newer
policy set being validated. Policy validation will fail. than what is supported by the server version.
System action: Server operation continues. System action: The command ends without inserting
any data into the database.
User response: Define a management class with the
name specified in the message for the policy set. To User response: Rerun the command using a version of
define the proper copy group attributes, reference the the server compatible with the version of DSMUPGRD
management class definition in the active policy set or used to extract the data. Or reextract the data using an
copy the management class class name from the active older version of DSMUPGRD that is compatible with
policy set to the policy set set name, using the COPY the version of the server.
MGMTCLAS command.
ANR1626I The previous message (message number
ANR1623E Management class class name in policy message number) was repeated repeat count
set set name for domain domain name does times.
not have an archive copy group. Archive
Explanation: The message issued prior to this message
retention protection is active, so
was issued repeatedly.
validation fails.
System action: The duplicate messages were
suppressed.
command. During policy set validation processing, the User response: No action is required.
server found a management class named class name in
the policy set being validated or activated (set name).
The management class does not have an archive copy ANR1627I The previous message was repeated
group. When archive retention protection is active, all repeat count times.
management classses in the policy set being validated Explanation: The message issued prior to this message
must have an archive copy group. Policy validation was issued repeatedly.
will fail.
System action: The duplicate messages were
System action: Server operation continues. suppressed.
User response: Define an archive copy group in User response: No action is required.
specified management class, then try the validation
again.

ANR1628I ANR1636W
now be used to accept client data.

ANR1628I The database manager is using port port
number for server connections. System action: Server operation continues.
Explanation: The server configures the database User response: None.
manager environment to use the indicated port for
connections from the server. Initially, connections from
the server do not use TCP/IP. After the number of ANR1632E command: Command failed. Replication
connections exceeds a pre-determined threshold, state information for the specified nodes
connections are made through TCP/IP to the specified could not be removed.
port. If the port is being used by another application, Explanation: A REMVOVE REPLNODE command
the database manager cannot receive connections from failed to complete. The replication state for the
the server after the change to TCP/IP connections is specified node is not changed.
necessary. After this situation occurs, future connections
to the database manager might fail. System action: Server operation continues.
System action: Server operation continues. User response: The server reported a problem running
the REMOVE REPLNODE command. See
User response: No action is required. accompanying messages for further information.
ANR1629W command: This command will result in ANR1633E Command: Node node name is set up for
ending the replication relationship for replication and cannot be renamed or
all nodes that match the pattern node removed.
pattern. Replication will no longer be
performed for the specified node(s). Explanation: Any node that is set up for replication
on either a source or target replication server cannot be
Explanation: A REMOVE REPLMODE command with renamed or removed.
prevent the specified nodes from being replicated. The
replication relationship is removed for each node. No System action: The requested operation fails.
node data is removed from this or any of the other User response: If you want to rename or remove the
replication servers. node, you must first remove the node from replication
System action: The system asks whether you wish to by issuing the REMOVE REPLNODE command.
continue with the REMOVE REPLNODE command.
User response: To process the REMOVE REPLNODE ANR1634I Default replication server name set to
command, enter 'Y' to continue or 'N' to stop the server name.
process. Explanation: The name of the default
target-replication server was set to the value that was
ANR1630W command: node name is not configured for specified with the SET REPLSERVER command. If you
replication. did not specify a value with the command, the existing
target replication server was removed, and client node
Explanation: The node specified in the command is data will not be replicated.
not configured for replication. A node is configured for
replication if the replication state of the node is System action: None.
ENABLED or DISABLED. To determine the replication User response: None.
state, issue the QUERY NODE FORMAT=DETAILED
command.
ANR1635I The server machine GUID, machine
System action: The operation continues but the node GUID, has initialized.
is skipped for this operation.
Explanation: The specified globally unique identifier
User response: Verify that the nodes specified in the (GUID) has initialized for the server machine.
command are configured for replication and try the
command again. Nodes may be configured for System action: Server operation continues.
replication with the UPDATE NODE command. User response: None.
ANR1631I command: Replication state information ANR1636W The server machine GUID changed: old
for the specified nodes have been value (old value), new value (new value).
removed.
Explanation: The globally unique identifier (GUID)
Explanation: All replication state information for the has changed for the server machine. The old and new
specified node has been removed from the database values are displayed.
and the node is no longer configured for replication. If
the node was a target of a replication operation it may System action: Server operation continues.
ANR1637W ANR1645I
User response: None. User response: Re-run the command with a node of
the correct type.
ANR1637W Error (error) occurred initializing the
server machine GUID. ANR1642E command: The node node name is locked.
Explanation: An error occurred while initializing the Explanation: The node is locked and cannot be used
server machine globally unique identifier (GUID). in this command.
System action: Server operation continues. System action: The command fails.
User response: Handle problems appropriately. A User response: Unlock the node and re-run the
write error may occur because the server needs root command.
authority to write the GUID. A read error may occur if
the server does not have authority to read the GUID.
ANR1643I Command: All file spaces for node node
Other error codes are received from the GUID utility.
name, will be moved.
Explanation: The server will attempt to move data for
ANR1638W Error (error) occurred initializing the
all the file spaces for the specified node name based on
server machine GUID. Old value was
the criteria entered in the MOVE NODEDATA
old GUID.
command.
Explanation: An error occurred while initializing the
System action: Server moves data for the indicated
server machine globally unique identifier (GUID). The
node.
old value is displayed.
User response: Handle problems appropriately. A
ANR1644E Command: Move node data operation
write error may occur because the server needs root
already in progress for storage pool
authority to write the GUID. A read error may occur if
storage pool.
the server does not have authority to read the GUID.
Other error codes are received from the GUID utility. Explanation: A command has been issued to move
node data for the specified storage pool but there is
already a move node data operation in progress for one
ANR1639I Attributes changed for node nodeName:
or more nodes that have been specifed for that same
changed attribute list.
storage pool.
Explanation: The TCP/IP name or address, or the
globally unique identifier (GUID) has changed for the
command.
specified node. The old and new values are displayed
for entries that have changed. User response: Check the activity log for a previous
MOVE NODEDATA command to determine what
processes for moving node data are in progress for the
User response: None. storage pool. Reissue the command for the node(s) and
storage pool you desire that are not already in progress,
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.

ANR1646I ANR1654E
ANR1646I Command: Node Node name, no filespaces ANR1650E Server server name is not defined.
found to move for this node.
Explanation: The server name was not created using
Explanation: A node and filespace were entered in a the DEFINE SERVER command. This entry was created
MOVE NODEDATA command but no filespaces were using the REGISTER NODE TYPE=SERVER command
found for the specifed node. and is not a valid reference.
System action: The server continues to move other System action: The current action for the device class
filespaces for any other nodes specified in the MOVE referring to this server fails.
NODEDATA command.
User response: The device class referring to this node
User response: None. as the SERVERNAME should be updated to refer to a
valid server entry. Specifically, it should refer to an
entry created using the DEFINE SERVER command.
ANR1647E Cannot find file space name for node
node ID, file space file space ID.
ANR1651E Server information for server name is not
Explanation: The server could not obtain filespace
available.
information for that node.
Explanation: The information for server name was not
available.
System action: The current server action fails.
error. Issue the QUERY ACTLOG command to view the User response: Please review any other messages
activity log and search for messages. If the error cannot prior to this message to determine the cause of the
be isolated and resolved, contact your service failure.
representative.
ANR1652E Server information for server name could
ANR1648W Command:This command will move data not be read from a device configuration
for nodes stored in volumes in storage file.
pool source storage pool to other volumes
Explanation: An attempt to a server definition for
within the same storage pool; the data
server name from any device configuration files failed.
will be inaccessible to users until the
operation completes. System action: The current action for the device class
referring to this server fails.
Explanation: A MOVE NODEDATA command has
been entered that will move data to other volumes in User response: Please verify the existence of a device
the same storage pool. While the data is being moved, configuration file and the DEFINE SERVER stanza
it will not be available to users. within that file.
System action: The administrator is asked whether to
continue. ANR1653E Resource lock acquisition for server
server name failed.
User response: Enter 'Y' to continue or 'N' to end the
process. Explanation: The acquisition of the resource lock for
server server name failed.
ANR1649W Command:This command will move data System action: The current action for the device class
for nodes stored in storage pool source referring to this server fails.
storage pool to storage pool destination
storage pool; the data will be inaccessible User response: Retry the action referring to the device
to users until the operation completes. class that refers to this server name. If the lock failure
persists, please contact your service representative.
Explanation: A MOVE NODEDATA command has
been entered that will move data from the source
storage pool to the destination storage pool shown. ANR1654E Server server name will not be written to
While the data is being moved it, will not be available a device configuration file.
to users. Explanation: An error occurred accessing the
System action: The administrator is asked whether to information for server name while trying to write this
continue. information to a device configuration file.
User response: Enter 'Y' to continue or 'N' to end the System action: This DEFINE SERVER entry is not
process. processing.
User response: Verify that the necessary DEFINE
ANR1655E ANR1664W
SERVER entries were written to a device configuration

ANR1659E Command: Server or server group server
file. If this error persists, please contact your service
or group name is already defined.
representative.
Explanation: A DEFINE SERVER or DEFINE
SERVERGROUP command has been entered that
ANR1655E Failure processing password for Server
specifies a server or server group name that already
server name when writing a device
exists. The name specified must be a unique name. It
configuration file.
must not duplicate a node name used by a registered
Explanation: An error occurred processing the node, a server name used by a defined server, or a
password for server name while trying to write this server group name used by a defined server group.
information to a device configuration file.
System action: This DEFINE SERVER entry is written command.
to the device configuration file without the password.
User response: To define the server or server group,
User response: The password needs to be specified reissue the command and specify a different name.
after PASSWORD= for this DEFINE SERVER entry in
the device configuration file.
ANR1660I Server server name defined successfully.
Explanation: The requested server has been defined to
ANR1656E Failure writing server definitions to a
the system in response to a DEFINE SERVER
device configuration file.
command.
Explanation: An error occurred writing the server
information to a device configuration file.
System action: The BACKUP DEVCONFIG action
fails.
ANR1661I Server server name deleted.
User response: Check that the device configuration
file exists and that the file system the file resides on is Explanation: In response to a DELETE SERVER
not out of space. command, the requested server has been removed from
the system.
ANR1657E Command: Invalid server or group name System action: None.
- server or group name.
Explanation: The command shown specifies an invalid
server or server group name.
ANR1662I Server server name updated.
Explanation: One or more attributes of a server have
command.
been updated by an UPDATE SERVER command.
name.
ANR1658E Command: Failure determining
NODENAME for server server name. ANR1663E command: Server server name not defined
Explanation: The command shown was unable to Explanation: The server server name is not defined to
determine a node name either from the NODENAME= the system.
parameter on this command or from the server name
previously set using the SET SERVERNAME command. System action: The command fails.
System action: The server does not process the User response: None.
command.
User response: Reissue the command with a valid ANR1664W Command: Server server name is currently
node name parameter or else update the server name in use.
using the SET SERVERNAME command so that a valid Explanation: The command shown specifies a server
name is available. that is currently in use for one or more of the following
purposes:
v The server is referenced by a device class of
DEVTYPE=SERVER that specifies this server for the
'SERVERNAME=' parameter.
v The server is defined as the target replication server.

ANR1665E ANR1674I
v A connection with this server is currently open.

ANR1669I Server event server name is defined as the
System action: The server does not process the event server.
command.
Explanation: The specified server is defined.
User response: Reissue the command at a later time.
In order to delete the server specified, it must not be
currently connected, it must not be referenced in a User response: None.
device class, and it must not be defined as the target
replication server.
ANR1670E Server event server name is already
defined as the event server. You must
ANR1665E command: Failure updating password for issue the DELETE EVENTSERVER
server server name. command before defining a new event
server.
Explanation: An error occurred updating the
password for server name. Explanation: An event server is already defined.
System action: The command fails. System action: The command fails.
User response: Re-try the command specifying a User response: Delete the existing Event Server and
different password. try the command again.
ANR1666E command: FILEAGGR not allowed with ANR1671I The event server definition has been
TYPE=SERVER. deleted.
Explanation: The FILEAGGR= parameter may not be Explanation: The event server definition has been
specified with the TYPE=SERVER parameter also being deleted.
specified.
User response: If an event server definition is desired,
User response: Reissue the command command use the DEFINE EVENTSERVER command.
without the FILEAGGR= parameter if this node is of
type SERVER.
ANR1672I No event server is currently defined.
Explanation: A query was issued to get the name of
ANR1667E command: Action not permitted against
the event server; however, no event server is currently
node node name.
defined.
Explanation: The command is not permitted against
the entry for node node name. This node entry has a
type of SERVER. User response: If an event server definition is desired,
use the DEFINE EVENTSERVER command.
ANR1673I Server group group name defined
successfully.
ANR1668E command: Not allowed for server server
Explanation: The requested server group is defined to
name.
the system in response to a DEFINE SERVERGROUP
Explanation: The DELETE SERVER command is not command.
permitted for server server name. The specified server is
either the event server or else it is a node entry rather
than a server definition. User response: None.
ANR1674I Member member name defined
User response: If the specified server is the event
successfully in server group group name.
server, and you want to delete it, issue the DELETE
EVENTSERVER command and then reissue the Explanation: The requested member is defined in the
DELETE SERVER command. To remove a node entry, server group in response to a DEFINE GRPMEMBER
issue the REMOVE NODE command for the specified command.
name.
ANR1675I ANR1685I
ANR1675I Server group server group name deleted. ANR1681E Command: Member member name is
already in server group server group
Explanation: The requested server is removed from
name.
the system in response to a DELETE SERVERGROUP
command. Explanation: The member member name is defined in
server group server group name.
User response: Retry the command and specify a new
member name.
ANR1676I Member member name deleted from
server group server group name.
ANR1682E A group cannot be a member of itself.
Explanation: The requested member is removed from
the server group in response to a DELETE Explanation: The member and group name are the
GRPMEMBER command, same. A group may not be a member of itself.
System action: None. System action: The command fails.
User response: None. User response: Retry the command and specify
another member name.
ANR1677I Server group server group name updated.
ANR1683E Command: Member member name not
Explanation: One or more attributes of a server group
defined.
is updated by an UPDATE SERVERGROUP command.
Explanation: The member member name is not defined
to the system. Server group members must be a
User response: None. defined server or server group.
ANR1678I Server group original server group name
User response: Retry the command specifying existing
renamed new server group name.
server or group.
Explanation: A server group is renamed by a
RENAME SERVERGROUP command. The original
ANR1684E Route:command: Routed commands
name is not valid.
cannot be routed.
Explanation: The command part of a routed command
User response: None. may not contain route information itself. The allowable
syntax for routed commands is route : command. The
command may not contain route information. Only one
ANR1679E Command: Server group server group name level of routing is allowed.
not defined.
System action: The command is not processed.
Explanation: The server server group name is not
defined to the system. User response: Reissue the command without
specifying route information in the command portion
System action: The command fails. of this routed command.
User response: Retry the command specifying an
existing group. ANR1685I Server group server group copied to
server group new server group.
ANR1680E Command: Member member name not Explanation: This message is displayed in response to
defined in server group server group the COPY SERVERGROUP command. The server group
name. named server group is copied to the server group named
Explanation: The member member name is not defined new server group.
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.

ANR1686I ANR1695W
ANR1686I Member member name moved from ANR1691E Error receiving response from server
server group group name to server group server name for command 'command'.
new group name.
Explanation: An error was encountered receiving the
Explanation: The requested member member name is response from the server indicated for the command
moved from server group group name to the server that was issued against it.
group new server group in response to a MOVE
GRPMEMBER command.
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.
ANR1687I Output for command 'command' issued
against server server name follows:
ANR1692E Response for command 'command' from
Explanation: The output for the command issued
server server name contains invalid data.
against the indicated server follows this message.
Explanation: The output returned from the specified
server for the command that was issued, contains
User response: None. invalid output. The command response can not be
processed.
ANR1688I Output for command 'command' issued System action: Output processing for this command
against server server name completed. response terminates.
Explanation: This message marks the end of the User response: Please contact your local service
output for the command specified that was issued representative.
against the indicated server.
System action: None. ANR1693E Unable to issue command 'command'
against server server name - failure
User response: None. starting thread.
Explanation: A thread could not be started to issue
ANR1689E Output for command 'command' issued the specified command against the server indicated.
against server server name terminated.
System action: This command is not issued against
Explanation: An error condition occurred causing the the server specified. The process will attempt to issue
output for the command issued against the specified the command against any other servers that were
server to be terminated. specified for the command routing information.
System action: None. User response: Examine the server messages issued
User response: Retry the command against the prior to this message to determine the source of the
requested server once the error condition has been error. Retry routing this command to the indicated
resolved. If the cause of the error can not be server after the cause of the error has been determined
determined, please contact your local service and resolved. If the error cannot be isolated and
representative. resolved, contact your service representative.
ANR1690E Error sending command 'command' to ANR1694I Server server name processed command
server server name. 'command' and completed successfully.
Explanation: An error was encountered sending the Explanation: The server indicated processed the
specified command to the server indicated. command successfully.
User response: Retry the command against the User response: None.
requested server once the error condition has been
resolved. If the cause of the error can not be ANR1695W Server server name processed command
determined, please contact your local service 'command' but completed with warnings.
representative.
Explanation: The server indicated processed the
command but encountered warnings. However, the
ANR1696E ANR1704E
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.
Explanation: The server indicated processed the
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
command is not processed.
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
System action: None. failure. Once the cause has been resolved, reissue the
User response: Check to see that valid route command.
information was provided for the command or else
check the activity log for error messages that indicate ANR1704E Failure obtaining or using credentials
why the command was not issued to the other servers. for administrator admin name.
Explanation: An error occurred obtaining or using the
ANR1699I Resolved route information to number of credentials for the administrator referenced.
servers server(s) - issuing command
command against server(s). System action: Command processing fails.
Explanation: The route information was resolved to User response: If the administrator
the number of servers indicated. The specified SERVER_CONSOLE was being used for a PING or
command will be issued against those servers. VALIDATE LANFREE command, the command may
fail. The administrator SERVER_CONSOLE is not able

ANR1705W ANR1712W
to perform these commands where the source server,

ANR1708I Define server for Server name failed
the target server, or both servers have authentication
because the crossdefine failed.
enabled. The command should be retried using an
administrator other than SERVER_CONSOLE. Explanation: The define server command failed
because the crossdefine parameter was included, and
Check the activity log and server console for other
the crossdefine was not successful.
messages about the cause of the failure. Once the cause
has been resolved, reissue the command. System action: The command fails.
User response: Check this server, and the server being
ANR1705W Ping for server 'server name' was not able defined for other messages indicating the reason for the
to establish a connection. failure.
Explanation: The ping command was unable to
establish a connection to the server specified. This ANR1709E Command.: Failure determining current
could indicate a problem on the server issuing the ping, usage for server or group name Server
a problem with the communication connection between name.
the two servers, or else it is a problem with the other
Explanation: The specified command failed to
server.
determine the current use of the server name or server
System action: None. group specified.
User response: Check the activity log and server System action: The command fails.
User response: Retry the command. If it continues to
on the server issuing this command. Next, check the
fail and the cause of the failure can not be determined,
communication connection between the two servers.
please contact your local service representative.
Also, check the server definition and password on both
the server issuing the command and the server
specified. And finally, verify that the server specified is ANR1710E Command.: Name Name not valid for this
running. command.
Explanation: The name specified for this command is
ANR1706I Ping for server 'server name' was able to not valid for this operation. The first case is that a
establish a connection. server name was specified for a command requiring a
server group name. The other case is where a server
Explanation: The ping command was able to establish
group name was specified for a command requiring a
a connection to the server specified.
server name.
User response: Check the activity log and server
User response: Retry the command specifying the
proper name.
on the server issuing this command. Next, check the
communication connection between the two srevers.
And finally, verify the operation of the server specified. ANR1711E Error accessing the server or server
group name Name.
ANR1707E Server information not complete, Explanation: A server operation attempted to access
crossdefine not allowed. the server name or server group name specified. An
error occurred while trying to access the information
Explanation: The SERVERHLADDRESS,
for this server name or server group name.
SERVERLLADDRESS or SERVERPASSWORD has not
been set for this server. These are required for the System action: The server operation fails.
CROSSDEFINE option on the define server command.
User response: Review the activity log to try to
System action: The command fails. determine the cause of the failure. If a cause can not be
determines, please contact your local service
User response: Use the QUERY STATUS command to
representative.
find what values need to be set. An authorized
administratormust issue the SET SERVERHLADDRESS,
SET and SERVERLLADDRESS or SET ANR1712W Command routing not allowed from
SERVERPASSWORD command to set the missing server console.
values.
Explanation: Command routing is not allowed from
the server console.
ANR1713I ANR1720I
User response: Reissue the command from an System action: The server does not process the
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
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
User response: Reissue the command without
managed object on this server. The password must be
specifying that aggregates should be reconstructed.
updated on the named configuration manager server.
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
not a valid pool name or pool type.
ANR1715E Event server cannot be deleted - it is
currently active. Explanation: If the source storage pool specified in the
command is a primary storage pool, then the
Explanation: The event server cannot be deleted since destination storage pool specified must also be a
it is currently active for event logging. 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
source storage pool.
User response: In order to delete the event server, it
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 User response: Provide a valid primary storage pool
EVENTLOGGING EVENTSERVER. Then reissue the name as the destination storage pool if the source pool
DELETE EVENTSERVER command. 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
name has been defined.
Explanation: In response to the DEFINE PATH
User response: None. command, the path from the source name to the
destination name has been defined in the server
ANR1717E Command: Command failed - database.
Non-Compatible Filespace name types System action: Server operation continues.
have been specified.
Explanation: A server command has been entered but
cannot be processed because Non-Compatible Filespace
name types have been specified.

ANR1721I ANR1730I
User response: Issue the command again with a valid

ANR1721I A path from source name to destination
source or destination name.
name has been deleted.
Explanation: In response to the DELETE PATH
ANR1726E A operation using the path from
command or to an UPDATE DEVCLASS command
sourcename to destname is currently being
with the MOUNTLIMIT parameter, the path from the
used.
source name to the destination name has been deleted
in the server database. Explanation: This path was in use when the command
was entered. The attributes of a path may not be
changed while it is being used.
User response: Wait until the operation using this
ANR1722I A path from source name to destination
path is complete, or cancel the operation using this
name has been updated.
path, and then reissue the command.
Explanation: In response to the UPDATE PATH
command, the path from the source name to the
ANR1727E A path from sourcename to destname does
destination name has been updated in the server
not exist.
database.
Explanation: The path being updated or deleted does
not exist.
User response: Reissue the command with a different
ANR1723E A path is already defined using source
source or destination name or define a new path.
name and destination name.
Explanation: In response to the DEFINE PATH
ANR1728E The library libname is not a SCSI or VTL
command, the server determines that a path with the
library.
same source name and the same destination name
already exists in the server database. Explanation: A drive that is to be used by a NAS data
mover must be attached to a SCSI or VTL library.
User response: Correct the source name or destination
name and re-enter this command. User response: Reissue the command with a different
drive name.
ANR1724W Command: Server server name is currently
in use. ANR1729E A path using the data mover source name
still exists.
Explanation: The command shown specifies a server
that is currently in use. The server is referenced in a Explanation: In the DELETE DATAMOVER command,
PATH used for LANFree access to a FILE device type the data mover name supplied is either the source or
drive in a shared library. the destination in a path that still exists in the server
database.
command. System action: Server operation continues.
User response: Reissue the command at a later time. User response: Delete the existing path and reissue
In order to delete the server specified, it must not be this command.
currently connected to the server, it may not be
referenced in a device class, it can not be defined to be
the event server, and it cannot be referenced within a ANR1730I Data mover mover name has been
PATH definition as a FILE device type drive. defined.
Explanation: The data mover has been defined in the
ANR1725E The source or destination name name is server database.
invalid and the command command System action: Server operation continues.
failed.
Explanation: The source or destination name is invalid
in the DEFINE PATH, DELETE PATH, or PERFORM
LIBACTION command.
ANR1731I ANR1741E
User response: Reissue the command and enter the

ANR1731I Data mover mover name has been
proper syntax.
deleted.
Explanation: The data mover has been deleted in the
ANR1737E Command: Device name device specified
server database.
is invalid.
Explanation: The specified command has been entered
User response: None. with an invalid device name.
System action: The command failed.
updated.
device name.
Explanation: The data mover has been updated in the
server database.
ANR1738I Unable to begin a server-free operation
System action: Server operation continues. with data mover data mover name;
received error error.
Explanation: The server attempted to begin a
server-free operation with the specified data mover but
ANR1733E Data mover mover name is already
was unable to do so.
defined.
Explanation: A DEFINE DATAMOVER command was
entered for a data mover that already exists in the User response: The server-free data movement will
server database. fail and the client may retry the request using LAN or
LAN-free data transfer.
User response: Use the UPDATE DATAMOVER to
ANR1739I Unable to update configuration of data
change the attributes in this data mover. Otherwise use
mover data mover name; received error
a different data mover name.
error.
Explanation: The server attempted to notify the
ANR1734E Data mover mover name is not defined.
specified data mover that a change in the SAN requires
Explanation: An UPDATE DATAMOVER command that the configuration be updated. The update failed
was entered for a data mover that does not exist in the because the data mover was busy.
server database.
User response: The data mover must finish its current
User response: Correct the data mover name or use operation before the configuration can be updated. The
the DEFINE DATAMOVER command to define a new server-free data movement will fail and the client will
data mover. retry the request using LAN or LAN-free data transfer.
ANR1735E Data mover data mover is currently being ANR1740E For the path defined from disk node
used. name disk name received lun actual lun
from client, expected expected lun.
Explanation: A data mover was in use when the
command was entered. The attributes of a data mover Explanation: A client attempted to backup the disk,
may not be changed while it is being used. but the server path definition was different than that
which was detected by the client.
User response: Wait until the operation using this
data mover is complete, or cancel the operation using User response: Correct the path definition from the
this data mover, and then reissue the command. disk to a datamover.
ANR1736E Command: Parameter parameter length is ANR1741E For the path defined from disk node
invalid. name disk name received serial number
actual serial from client, expected expected
Explanation: The specified server command has been serial.
entered with a parameter that is longer or smaller in
length than the allowed length. Explanation: A client attempted to backup the disk,
but the server path definition was different than that

ANR1742E ANR1750E
which was detected by the client.

ANR1746E The path from data mover datamover
System action: Server operation continues. name to drive library name drive name is
not online.
User response: Correct the path definition from the
disk to a datamover. Explanation: A server-free operation requested the
specified device. The device cannot be used because the
path from the datamover to the device is not online.
ANR1742E The disk node name disk name is not
online. System action: Server operation continues.
Explanation: An operation requested the specified User response: Determine the reason for the path
disk. The disk cannot be used because it is not online. being offline; if possible, update the path status to
online.
User response: Determine the reason for the disk ANR1747E The library libname is not a ZOSMEDIA
being offline; if possible, update the disk status to enabled library.
online.
Explanation: Defining a PATH to a library using the
ZOSMEDIASERVER parameter requires the library be a
ANR1743E The path from data mover datamover ZOSMEDIA library ( e.g., DEFINE LIB libname
name to disk node name disk name is not LIBTYPE=ZOSMEDIA ).
online.
Explanation: An operation requested the specified
disk. The disk cannot be used because the path from User response: Reissue the command with the correct
the datamover to the disk is not online. library name.
ANR1748W The disk node name disk name was not
User response: Determine the reason for the path found on the SAN. The path definition
being offline; if possible, update the path status to for this disk has been marked offline.
online.
Explanation: During device discovery on a storage
area network a device was not found that has the same
ANR1744E The world wide name is invalid for the serial number as the disk defined to TSM.
destination of the path being defined.
Explanation: A path was being defined from a
datamover to a destination and that destination has an User response: Verify that the serial number of the
incorrect world wide name specified. disk definition is correct and that the disk is
operational.
User response: Update the destination's definition ANR1749W The drive library name drive name was not
with the correct world wide name. found on the SAN. The path definition
for this drive has been marked offline.
ANR1745I The HBA is busy and SAN devices Explanation: During device discovery on a storage
cannot be discovered. area network a device was not found that has the same
Explanation: The SAN device discovery function is serial number as the drive defined to TSM.
busy. The requested HBA API query cannot be System action: Server operation continues.
completed at this time. This type of timeout is
generally caused by a bad HBA adapter in a system User response: Verify that the serial number of the
with multiple HBAs. drive definition is correct and that the drive is
operational.
User response: Check all HBA adapters on the system ANR1750E The server detected an internal error,
and ensure that all of them are functioning correctly. return code = return code.
Reissue the QUERY SAN command.
Explanation: An unexpected error occured during
server operation.
ANR1751I ANR1760E
cause of the data storage failure. If the failure can be User response: None.
found and resolved, retry the operation. If the failure
cannot be found, contact your service representative for
ANR1757E A path using the disk disk name still
assistance in resolving the problem.
exists.
Explanation: The name supplied in a DELETE DISK
ANR1751I Disk disk name has been defined.
command is the destination in a path that still exists in
Explanation: In response to the DEFINE DISK the server database.
command, the disk has been defined in the server
database.
User response: Delete the existing path using the
DELETE PATH command and re-enter the DELETE
User response: None. DISK command.
ANR1752E Disk disk name is already defined. ANR1758E A path from disk node name disk name to
a datamover cannot be determined.
Explanation: A DEFINE DISK command was entered
for a disk that already exists in the server database. Explanation: During a backup operation a path from
the disk cannot be found.
User response: Use the UPDATE DISK command to
change the attributes of this disk. Otherwise, use a User response: Define a path from the disk to a
different disk name. datamover.
ANR1753E Disk disk name is currently being used. ANR1759E Command: A device with SCSI
datamover capabilities was not found in
Explanation: A disk was in use when the command
the system configuration for datamover
was entered. The attributes of a disk may not be
datamover name.
changed while it is being used.
Explanation: The scsi address could not be
determined for a device that is capable of performing
User response: Wait until the operation using this disk datamover operations.
is complete, or cancel the operation using this disk, and
then reissue the command.
User response: Verify that the hardware that can
perform SCSI datamover operations is installed and
ANR1754E Disk disk name is not defined.
powered on.
Explanation: An UPDATE, DELETE or client function
requested the specified disk, but the disk has not been
ANR1760E Command: Command failed for node
defined to the server.
node name, filespace filespace name -
System action: Server operation continues. destination storage pool storage pool was
skipped.
User response: Correct the disk name or use the
DEFINE DISK command to define a new disk. Explanation: The indicated command failed because
the destination storage pool was skipped. A storage
pool may be skipped because it does not have enough
ANR1755I Disk disk name has been updated. available space, or because it has a MAXSIZE value
Explanation: In response to the UPDATE DISK that is less than the size of the object to be inserted.
command, the disk attributes have been updated in the System action: The operation fails.
server database.
User response: Ensure that the destination storage
System action: Server operation continues. pool is available, has an adequate MAXSIZE setting,
User response: None. 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
ANR1756I Disk disk name has been deleted. scratch volumes or defining new volumes in the
Explanation: In response to the DELETE DISK storage pool. If volumes in the destination storage pool
command, the disk has been deleted in the server are offline, use the VARY ONLINE command to vary
database. them online and make them available for use. Correct
the problem and reissue the command.

ANR1761E ANR1768E
ANR1761E Command: Command failed for node ANR1765E Command:The number of copy threads
node name, filespace filespace name - entered, copythreads, exceed the
storage media is inaccessible. capabilities of the datamover.
Explanation: The indicated command failed because Explanation: A datamover has an upper limit of the
required storage media is unavailable. number of copy threads that it is capable of executing.
The copythreads parameter provided is greater than
this limit.
User response: Ensure that there are sufficient
volumes available for storing backups and that any
volumes required for restore are checked in and User response: Make sure the value entered for the
available. Correct the problem and try the command copythreads parameter is less than the maximum for
again. this datamover. Using the default for the number of
copythreads sets the number of copythreads to the
datamover's maximum value.
ANR1762E Command: Command failed for node
node name, filespace filespace name -
mount point unavailable. ANR1766I The number of sessions currently active
for datamover datamover, exceed the
Explanation: The indicated command failed because
number of copy threads defined for this
sufficient mount points are not available.
datamover.
Explanation: The datamover definition has a paramter
User response: Ensure that sufficient mount points are that is used to limit the number of operations involving
available and working correctly. Correct the problem that datamover. This limit was reached.
and try the command again.
System action: The operation continues using another
method.
ANR1763E Command: Command failed - see
User response: Verify that the number of copy threads
previous error messages or view the
in the datamover definition is sufficient enough to
activity log.
allow mutliple server-free operations, or define another
Explanation: The indicated server command has datamover to handle additional server-free operations.
failed. This message is always preceded by one or more
other error messages which provide more detail about
ANR1767W A datamover with a online path to both
why the command failed.
the disk, nodename diskname, and the
System action: The operation fails. drive, libraryname drivename cannot be
found.
to determine the source of the error. Use the QUERY Explanation: To perform server-free data movement, a
ACTLOG command to view the activity log and search path must exist from the datamover to both the disk
for messages if needed. Correct the problem and try the and the drive. If either path is not defined or is offline
command again. to all datamovers defined then the data movement
cannot occur via server-free.
ANR1764E Command: Command failed - loadable System action: The operation continues using another
module module name is not available. method.
Explanation: The indicated server command has failed User response: Define the appropriate paths from a
because it requires the availability of the specified datamover to the disks and drives. If a path is defined
loadable module, but the module is not loaded. from a datamover to a drive in a library then all drives
in that library should have paths defined from that
System action: The operation fails. same datamover. A path may have to be updated to
User response: Make sure the necessary loadable specify online=yes.
module is available for your platform. Not all modules
are available on all platforms. If the module is available ANR1768E Command: The device name provided
for your platform and is installed, contact your service conflicts with a device name that is
representative for assistance. already in use.
Explanation: The device name provided in the
command is already used by an existing path.
ANR1769E ANR1776I
User response: Specify a valid DEVICE parameter that

ANR1773W Unable to update the path in the
is not used by any other drive or library.
database path source name and drive drive
name .
ANR1769E Command: Command failed - multiple
Explanation: The system is unable to update the path
actions between commit actions not
information in the database table.
allowed.
System action: .
Explanation: A server script that performs multiple
actions between commit actions is not allowed. For User response: None.
example, deletion of multiple paths before each of the
deletions is committed is not allowed.
ANR1774E The Query Status command failed, and
System action: The server does not process the server initialization has not completed.
command. Allow server initialization to complete,
and then try the command again.
User response: Rewrite the script or macro so that no
new command is issued until the previous command is Explanation: The command Query Status failed
committed. because server initialization has not completed.
ANR1770E Processing for session session id found
User response: Allow server initialization to complete,
destination new destination. Expected
and then try the command again.
current destination.
Explanation: While processing a remote image
operation, the specified session was working with the
defined, however a connection to the
current destination. But the server received a client
data mover failed. Please check the
request with a new destination name.
attributes of the file server specified in
System action: Server operation continues. the definition of the data mover.
User response: From the client, quit the current Explanation: The data mover has been defined in the
remote image request. Reissue the request, if desired. server database, however the server cannot connect to
the file server associated with the data mover. The
connection failed because of one of the following
ANR1771E The path from remote server remote
possible reasons:
server name to destination destination name
with the destination device type is not v One of the parameters specified during datamover
valid. definition was incorrect: TCP/IP address of the file
server, user id, password, TCP/IP port
Explanation: The library manager receives a command
v File server is not accessible
to update the path for the remote server. The device
type field of the destination device is not valid. The v NDMP server limits the number of opened NDMP
destination for update path from remote server must be sessions
either drive or library. System action: The data mover is defined to the
System action: Server operation continues. server.
User response: Determine why the device type field of User response: Check that the file server associated
the destination device is not valid. with the data mover is accessible through the network;
check each of the attributes specified during datamover
definition; check the number of open NDMP sessions
ANR1772E The path from source source name to with the file server.
destination drive name is taken offline.
Explanation: The path is now marked offline. ANR1776I Data mover mover name has been
System action: The path is inaccessible. updated, however a connection to the
data mover failed. Please check the
User response: Determine the reason the path is attributes of the file server specified in
inaccessible, such as a hardware problem. Make any the update command.
needed corrections. Then, issue the the UPDATE PATH
command with the ONLINE=YES option to make the Explanation: The data mover has been updated in the
path online. server database, however the server cannot connect to
the file server associated with the data mover. The
connection failed because of one of the following
possible reasons:

ANR1777I ANR1785I
v One of the parameters specified during datamover System action: This process performs extensive
update was incorrect: TCP/IP address of the file database I/O and may impact other server operations
server, user id, password, TCP/IP port and processes while it is running.
v File server is not accessible User response: This process may be monitored using
v NDMP server limits the number of opened NDMP the QUERY PROCESS command. If this process needs
sessions to be cancelled, issue the CANCEL PROCESS
command.
System action: The data mover definition is updated.
User response: Check that the file server associated
ANR1783E ESTIMATE DBREORG process process
with the data mover is accessible through the network;
number failed and only evaluated pages
check each of the attributes specified in the datamover
evaluated database pages.
update command; check the number of open NDMP
sessions with the file server. Explanation: The ESTIMATE DBREORG process failed
to complete successfully. It only evaluated pages
evaluated database pages.
ANR1777I module(offset): Object object id hi.object id lo
is object name for node node name (node System action: None.
id), filespace filespace name (filespace id ).
User response: If the has been cancelled, this message
Explanation: The server reported a problem with the will be issued. If this processed failed to process but
specified object. See accompanying messages for further was not cancelled, it is likely that it failed because it
information. was not able to acquire access to the necessary database
pages to perform the evaluation. Retry the operation.
ANR1784I A database reorganization would reduce
the database utilization by an estimated
ANR1778E Command: Invalid or missing parameter. space recovered MB.
Explanation: The specified server command has been Explanation: The ESTIMATE DBREORGSTATS process
entered with an invalid parameter, or, is missing a completed and determined that the database space
required parameter. utilized would be reduced by space recovered megabytes
if a database reorganization were performed.
System action: Server operations continue normally,
User response: Reissue the command and enter the and the ESTIMATE DBREORGSTATS process
proper syntax. completes.
User response: This message reports the estimated
ANR1779I backupset process name process completed: database space recovered if a database reorganization
successful count backupset(s) were were to be performed. The Tivoli Storage Manager
generated or defined out of total count administrator should evaluate this information relative
backupset(s) requested by the to their current database utilization, expected database
command's specifications. growth and changes, and determine whether or not a
Explanation: A GENERATE or DEFINE BACKUPSET database reorganization is needed for this server. To
command has finished successfully, and the backupsets reorganize the server database, refer to DSMSERV
described in previous messages have been created. UNLOADDB, DSMSERV LOADFORMAT, and
DSMSERV LOADDB in the Administrator's Reference.
System action: The backupsets described have been
created.
ANR1785I ESTIMATE DBREORG process is
User response: None. already running.
Explanation: The ESTIMAGE DBREORG process is
ANR1782W ESTIMATE DBREORG process process already running. The server does not allow more than
number started - server performance may one instance of this process to be running at a time.
be degraded while this process is
running. System action: None.
Explanation: The ESTIMAGE DBREORG process has User response: Use the QUERY PROCESS command
been started as the reported process number. This to monitor the existing process. If the existing process
process estimates the amount of space that the database needs to be cancelled, issue the CANCEL PROCESS
will reduced by if a database reorganization is command.
performed.
ANR1786W ANR1792W
problem with the HBA firmware, HBA or the HBA

ANR1786W HBAAPI not able to get adapter name.
verdor's HBAAPI driver. For the list of supported
Explanation: The HBAAPI function getAdapterName HBAs and required driver levels by operating system
failed. The server will continue to access next adapter if go to http://WWW.IBM.COM/SUPPORT.
it exists.
System action: None. ANR1791W HBAAPI wrapper library file name failed
to load or is missing.
User response: The Tivoli Storage Manager SAN
discovery will not work with this Host Bus Adapter. Explanation: This library is provided by Tivoli Storage
For the list of supported HBAs and required driver Manager. It is required for discovery of devices on a
levels by operating system go to http:// SAN.
WWW.IBM.COM/SUPPORT. v For windows, the HBAAPI wrapper library is
hbaapi.dll.
ANR1787W Unable to open adapter adapter name. v For AIX, the HBAAPI wrapper library is
libHBAAPI.a.
Explanation: The HBAAPI function to open the host
bus adapter (HBA) failed. v For Solaris, the HBAAPI wrapper library is
libhbaapi32.so for 32 bit application and
System action: None. libhbaapi64.so for 64 bit application.
User response: The Tivoli Storage Manager SAN v For Linux, 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 go to http://
WWW.IBM.COM/SUPPORT.
User response: Make sure the HBAAPI wrapper
library for this platform is in the same directory as the
ANR1788W Unable to retrieve the adapter attributes
IBM Tivoli Storage Manager server executable. AIX is
for adapter name.
the only exception with HBAAPI wrapper library
Explanation: The HBAAPI function failed to retrieve libHBAAPI.a in /usr/lib.
the adapter' attributes. This problem is caused by a
nonfunctional Fibre Channel adapter on the system.
ANR1792W HBAAPI vendor library failed to load or
Check this adapter to ensure it works properly. This
is missing.
problem also can be caused by other non Fibre Channel
types of adapters on the system, such as, a SAS or a Explanation: The HBAAPI vendor library failed to
parallel SCSI adapter. This message can be ignored if load or is missing. This HBAAPI library is provided by
you are using a non Fibre Channel adapter. the Host Bus Adapter (HBA) vendor. It is required for
Tivoli Storage Manager server to discover devices on
the SAN.
User response: SAN discovery does not work for this
adapter. For the list of supported HBAs and required
driver levels by operating system visit User response: Ensure the HBAAPI file exists on the
http://WWW.IBM.COM/SUPPORT. system. If the driver level on your system is not
supported, go to the HBA vendor's website and
download/install the HBA driver. For the list of
ANR1789W Get HBA target mapping failed.
supported HBAs and required driver levels by
Explanation: The HBAAPI function to get the target operating system go to http://WWW.IBM.COM/
mapping failed. SUPPORT. The following is an example of some of the
HBA vendor's HBAAPI file:
v For UNIX systems, This HBAAPI vendor library's
User response: SAN discovery will not work for this location is indicated in /etc/hba.conf. For example:
adapter. For the list of supported HBAs and required qla2x00 /usr/lib/libqlsdm.so
driver levels by operating system go to com.emulex.emulexapilibrary
http://WWW.IBM.COM/SUPPORT. /usr/lib/libemulexhbaapi.so
v For Windows systems, verify the location of the
ANR1790W SAN discovery failed. HBAAPI vendor library by checking LibraryFile in:
Explanation: SAN discovery failed. HKEY_LOCAL_MACHINE

SOFTWARE
System action: None. SNIA
HBA
User response: SAN discovery failed. This may be a <HBAAPI library>

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

either by default by the SANDISCOVERY OFF option
depending on the platform or by the SANDISCOVERY ANR1799E The Tivoli Storage Manager device
UNSCANNEDPATHOFF option. For the list of driver is not installed, or one or more
supported HBAs and required driver levels by device driver files are missing.
operating system go to http://WWW.IBM.COM/
SUPPORT. Explanation: The server command has failed because
the Tivoli Storage Manager device driver is not
installed, or one or more device driver files are missing.
ANR1795I The device driver has been updated
successfully for device old device name. System action: The operation fails.
The new device name is new device name.
User response: Make sure the Tivoli Storage Manager
Explanation: This message is displayed in response to device driver is installed. and the following files are not
the CHANGE DEVDRIVER command. The device missing. %WINDIR%\system32\drivers\tsmscsi.sys (or
driver for device old device name has been updated tsmscsi64.sys for 64-bit Windows), %WINDIR%\inf\
successfully. tsmmt.inf, and %WINDIR%\inf\tsmlb.inf.

ANR1800E Missing or invalid EVENTLOG
User response: None. command parameter.
Explanation: The event logging command issued
ANR1796E Invalid device name device name. contains an invalid parameter, or is missing a required
Explanation: The device name is not in the form of parameter.
TAPEx or CHANGERx. System action: The command is ignored.
System action: The server fails the command. User response: Reissue the command with the proper
User response: Change the device name to TAPEx or parameters.
CHANGERx and retry the command.
ANR1801E ANR1810E
ANR1801E Eventlog command: Invalid event or event ANR1805E command: Invalid value paths for
class - Event or event class name. NUMDBDIRS parameter.
Explanation: An event logging command has been Explanation: During processing of command EXTEND
entered which specifies an unknown event or event DBSpace command, an invalid value is encountered for
class. the NUMDBDIRS parameter. The value should be from
1 to 3
System action: The command is ignored for the
invalid event or event class. Any valid events or classes System action: Server operation continues, but the
specified are processed. command is not processed.
User response: Reissue the command with the correct User response: Issue the command with a valid value.
event or event class.
ANR1806I Table reorganizing and updating
ANR1802E Device device name was not found. statistics performed successfully for
processed table.
Explanation: The device was not found in the device
information set. The vendor ID and/or product ID, or Explanation: Reorganize and Runstat successfully run
device name may be invalid, or the device has been on that table.
removed from the system.
User response: No user action required.
fails.
User response: Reissue the command with the correct
ANR1807I Table updating statistics performed
vendor ID and product ID, or device name.
successfully for processed table.
Explanation: Runstat successfully run on that table.
ANR1803W SAN discovery module module name is
not installed correctly. System action: Server operation continues.
Explanation: The server attempted to load the SAN User response: No user action required.
discovery module, but the permissions or ownership of
the file are incorrect.
ANR1808E Unable to open event log file file spec for
System action: Server operation continues, but appending.
without SAN discovery function.
Explanation: The server cannot write to a file which
User response: Ensure that the SAN discovery module has been specified for event logging.
is executable, has the setuid bit turned on, and is
owned by root. The SAN discovery module is called System action: No logging will be done to the file
'dsmqsan' and must reside in the server or storage receiver.
agent executable directory. User response: Check the file for proper access
permissions, or specify a different file for logging.
ANR1804W Command: Process process number
skipping volume volume name in storage ANR1809E Insufficient memory to activate event
pool pool name because the volume is in logging.
use by another process.
Explanation: A BEGIN EVENTLOGGING command
Explanation: The command shown specifies the has been entered, but the server has insufficient
volume to be processed, but that volume is currently memory available to activate logging.
being used by another operation.
System action: The server skips the volume and
processes the next available volume. User response: If logging is required, make more
memory available to the server then restart the server.
User response: Check the activity log to determine
which operation was using the volume. If the operation
using the volume is complete reissue the Command to ANR1810E Eventlog command: Invalid receiver -
process the skipped volume. receiverName.
Explanation: An event logging command has been
entered which specifies an unknown event log receiver
(maybe unknown just to this platform).
System action: The command is ignored for the

ANR1811W ANR1816W
invalid receiver. Any valid receivers specified are

ANR1814W The database manager cannot load the
processed.
security plugin file name.
Explanation: The database manager cannot load the
receiver.
security plugin. This plugin controls access to the
database manager from the Tivoli Storage Manager
ANR1811W The Host Bus Adapter API package server.
might not be installed.
User response: Inspect the DB2 diagnostic log file to
User response: The HBA API does not provide the identify the reason the database manager cannot load
number of Fibre Channel adapters from the host the security plugin. Correct the problem and restart the
system. The HBA API file version that is on your server.
operating system might not be supported or the HBA
API package might not be installed. Go to the HBA
ANR1815W Check target server for storage problems
vendor website to obtain the latest version of the HBA
during replication of node node list.
API. For a list of supported HBAs and required HBA
API levels by operating system, go to Explanation: During the replication process for the
http://www-1.ibm.com/support/ specified nodes, there were problems storing data at
docview.wss?uid=swg21193154. the replication target server.
ANR1812E DELETE FILESPACE filespace name for
User response: Check the activity log of the target
node node name failed deletion because
server for specific error messages relating to data
of a replication in progress.
storage during the replication process.
Explanation: The reported filespace belonging to the
reported node is currently being replicated as part of a
ANR1816W The names of one or more files were
REPLICATE NODE command. A filespace cannot be
truncated. Examine log file log file name
deleted while the replication is in progress.
for details.
System action: The DELETE FILESPACE ends with a
state of FAILURE.
attempted to insert a database row describing a file
User response: Use the QUERY PROCESS command whose path name is longer than the maximum path
to view active REPLICATE NODE processes. Either name supported by Tivoli Storage Manager V6. The
wait for the replication to complete or cancel the Tivoli Storage Manager V5 server supported path
replication process with the CANCEL PROCESS or names of up to 8000 bytes, but the V6 server does not
CANCEL REPLICATION commands, and reissue the allow path names to be longer than 6000 bytes.
DELETE FILESPACE command.
System action: The name of the file was replaced by a
system-generated name. Information needed to restore
ANR1813W Filespace filespace name for node node the file to its original name was written to the specified
name is a replication replication role. log file.
Explanation: The reported filespace is either the The log file contains two sections. The first section lists
source or target of a replicated node. The DELETE files whose names were truncated. The second section
FILESPACE command will delete the data on this identifies the node names and filespace names of the
server, but will not delete the data on any other truncated files.
replication servers.
The first section is identified by the header "--
System action: The DELETE FILESPACE command Truncated Files --". Each line of this section identifies
continues. one file whose name was truncated. The line consists of
four fields, separated by tabs:
User response: If this message indicates this filespace
is the source of replicated data, then login to all servers v Node ID - a numeric identifier for the node that
containing replicated data from this filespace and issue owns the file.
the DELETE FILESPACE command to remove the data v Filespace ID - a numeric identifier for the file's
from those servers. If this message indicates this filespace.
filespace is the target of replicated data, ensure that the v New Name - the system generated name that was
filespace on the source server is either deleted, or assigned to the file.
updated to no longer replicate to this server.
v Original Name - the original name of the file.
ANR1817W ANR1821W
The second section is identified by the header "-- Node docview.wss?uid=swg21321130

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
tabs: Explanation: The server attempted to connect to the
v Node ID - a numeric identifier for the node that database by using TCP/IP, but it was not able to do so.
owns the file. System action: The server stops.
v Node Name - the name of the node associated with
the node ID. User response: First, verify that the port number is
not already in use. Possible methods include:
v Filespace ID - a numeric identifier for the file's
filespace. v On Unix systems, inspect /etc/services for an
occurance of the port number.
v Filespace Name - the name of the filespace associated
with the filespace ID. v Use the netstat command to determine if a service is
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
identified for import on target server If no conflict is found, use the "db2 get database
tgtServerName. manager config" command to verify that the
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
System action: None. 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"
ANR1818W command: No valid nodes were command to set the environment variable and restart
identified for import. the server.
Explanation: During a server import process none of

the node definitions in the import data were valid for ANR1821W Event logging is not started for the
import. No node data was imported. receiverName receiver.
System action: None. Explanation: In response to a BEGIN

EVENTLOGGING command, recording of event log
User response: Check for warning or error messages records to the specified receiver was attempted. The
during the import process on the server and handle as event logging for the specified receiver is already
needed. started because either the receiver is currently running
or the receiver was terminated previously and is still in
the process of writing the messages that were queued
ANR1819E Permission denial to device device name.
up for processing.
Explanation: A read-only attribute is assigned to
non-root users and their tape device files. If this
attribute is not changed, non-root users cannot store User response: Check to see if the event log receiver is
data to tape devices. This only affects HP-UX, Linux, already started by issuing the QUERY STATUS
and Solaris operating systems. command, and checking the Active Receivers field.
Some event log receivers such as FILETEXT,
System action: The open operation fails.
FILETEXTEXIT, USEREXIT, and Tivoli receiver, can be
User response: Issue the CHMOD system command started during server initialization if they are
to change the read-only attribution for specific tape configured in the server options file.
device files and run the previously failed operation v If the event log receiver is already started you do not
again. See Technote 1321130 for details about resolving take any further action.
this problem: https://www-304.ibm.com/support/

ANR1822I ANR1842E
v If the event log receiver is not currently running then User response: Reissue the command with the correct
wait and try to start it again after a short delay. receiver.
ANR1822I Event logging ended for the receiverName ANR1828E Eventlog command: No valid event
receiver. specified.
Explanation: In response to an END Explanation: An event logging command has been
EVENTLOGGING command or because an error entered and no valid events or event classes were
occurred, event log records are no longer being output specified.
to the specified receiver.
User response: None. events or event classes.
ANR1823I Event logging ended for all receivers. ANR1829E Eventlog command: Server events may not
be disabled for the activity log receiver.
Explanation: In response to an END
EVENTLOGGING command, event log records are no Explanation: A DISABLE EVENT command has been
longer being output to any receiver. entered for the activity log receiver.
System action: None. System action: The command is ignored for the
activity log receiver. Any valid receivers specified are
processed.
ANR1824E Event logging is inactive for the
receiver.
specified receiver.
Explanation: An END EVENTLOGGING command
ANR1830E receiverName receiver options not defined
has been entered, but logging is not active for the
in the server options file.
specified receiver.
Explanation: A BEGIN EVENTLOGGING command
has been entered for a receiver, but the required
User response: If logging is desired, use the ENABLE receiver options were not specified in the server
EVENT and BEGIN EVENTLOGGING commands to options file.
activate event logging.
System action: Logging is not started for the specified
receiver.
ANR1825I Event logging active for the receiverName
User response: Enter the receiver options in the server
receiver.
options file and restart the server.
Explanation: In response to a BEGIN
EVENTLOGGING command, event log records are now
ANR1831I Event logging of client events ended for
being output to the specified receiver.
ACTLOG receiver.
Explanation: An END EVENTLOGGING command
User response: None. has been entered for the activity log receiver.
System action: The server no longer records client
ANR1826I Event logging active for all receivers. events in the activity log. Server events continue to be
recorded in the activity log.
Explanation: In response to a BEGIN
EVENTLOGGING command, event log records are now User response: None.
being output to all receivers.
System action: None. ANR1842E An error occurred on the receiverName
receiver.
Explanation: An error occurred on the specified
receiver.
ANR1827E Eventlog command: No valid receiver
specified. System action: The server no longer sends events to
the receiver.
Explanation: An event logging command has been
entered, and no valid receivers were specified. User response: Issue a BEGIN EVENTLOGGING
ANR1843I ANR1856W
command for the receiver to attempt to start logging User response: Most likely you are using very long
events to the receiver again. server names and/or have excessive hops from server
to server. Either use shorter server names or change
your configuration to reduce the number of hops.
ANR1843I Event log receiver initialization in
progress.
ANR1852E Unable to send header to TEC at TEC
Explanation: Initialization is starting for the eventlog
server rc return code
receivers.
Explanation: A network error has occurred in
attempting to send the event header to the Tivoli
User response: None. Enterprise Console.
ANR1844I Eventlog command command processed.
User response: Verify network connections and
Explanation: The specified command was processed. contact your service representative if this error persists.

ANR1853E Unable to send data to TEC at TEC
User response: If any previous messages indicate that server rc return code
parts of the command failed, reissue the command for
those parts only. Explanation: A network error has occurred in
attempting to send the event data to the Tivoli
Enterprise Console.
ANR1850E Circular event logging detected. The
event server has previously handled System action: None.
event Event number from Source trail. To
prevent looping, events which have
contact your service representative if this error persists.
already been logged by the event server
are not sent again. Please correct the
situation causing circular logging to ANR1854E Unable to flush data to TEC at TEC
avoid wasting system resources. server rc return code
Explanation: The server is attempting to log an event Explanation: A network error has occurred in
which has previously been handled by the event server attempting to flush data to the Tivoli Enterprise
that is currently defined. Console .
System action: The event is not sent to the event System action: None.
server. Other events will still be sent, and this message
will be issued periodically if this situation is detected
again.
User response: Determine what is wrong with the
ANR1855E Failure validating protocol between
server to server event logging setup, and fix the
client and server for node node on
problem.
session session number
Explanation: For a node having the "VALIDATE
ANR1851E The source trail for server to server
PROTOCOL" option set to either "DATAONLY" or
event logging has exceeded the
"ALL", a validation error occurred. The transaction is
maximum length of Maximum sourcetrail
aborted and an indication is sent to the client indicating
length bytes.
the failure.
Explanation: While attempting to log an event to the
event server, the server has found that the source trail
length is too long. User response: Verify network connections and
System action: The server continues to try to send the
event to the event server, but the source trail may be
truncated and appear something like: ANR1856W Command: No volumes selected to
process.
name1>...>namex>namey
where, Explanation: No volumes were eligible for processing
name1 is the originator of the event. by the AUDIT VOLUME command based upon the
parameters specified.
... is where intervening server name(s)
have been left off the source trail. System action: The AUDIT VOLUME process ends
without processing any volumes.

ANR1857I ANR1864E
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
port port and target target lun lun does
Explanation: The AUDIT VOLUME command will
not match with the library libraryPath .
process a range of volumes due to one or more of the
following parameters having been specified: Explanation:
FROMDATE, TODATE, or STGPOOL. The AUDIT
System action:
VOLUME processing will start a process for each
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
the library libraryPath .
continue. Explanation:
User response: Enter 'Y' to audit the volume or 'N' to 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
User response: Enter 'Y' to audit the volume or 'N' to command, enter 'Y' to continue or 'N' to stop the
stop the process. process.
ANR1859W Node node on session session id received ANR1863E library libraryPath and serial serial does
CRC protocol validation information not support Read Element Status
when it is not configured to do so. command. It is very old and should be
replaced with newer model.
Explanation: The server received protocol validation
information for the session and node specified. The Explanation:
settings for this node are not configured to perform System action:
protocol validation and any CRC information received
will be ignored. User response:

ANR1864E library libraryPath does not support Read
User response: The server administrator should Element Status command and it does
evaluate whether or not this node should perform not have a serial number. It is very old
protocol validation. If so, issue the UPDATE NODE and should be replaced with newer
command and specify the VALIDATEPROTOCOL model.
option with the appropriate setting to enable protocol
validation. Explanation:
If this is a TYPE=SERVER node for the target of a System action:

virtual volume operation and protocol validation is not User response:
desired, the server definition on the source server
ANR1865I ANR1871I

ANR1865I export command : Summary for
Restartable Export operation export
identifier : ANR1869W Export/import command: Skipped archive
number archive files, backup number
Explanation: A summary of the total number of
backup files, and spacemg number space
objects transmitted in the restartable export operation
managed files.
with export identifier is displayed following this
message. Explanation: The background export or import
System action: Export processing for the command
skipped archive number archive file copies, backup
ends. Server operation continues.
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
database. Data is not actually moved if Preview=Yes is
specified in the command export/import command.
suspended with status status.
command command was suspended with a SUSPEND
command. User response: Check previous messages for the
names of the files that were not exported or imported,
and problem determination information.
stops. Statistics on the number and type of objects
are displayed on the server console following this ANR1870I Export/import command: Copied number
message. bytes of data.
User response: None. Explanation: The background export or import
copies number bytes of data from the server database
and data storage to the export media or from the
completed with status status.
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. Statistics on the number and type command completes. Server operation continues.
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
files that were skipped is also displayed. ANR1871I Export/import command: Copied number
kilobytes of data.
ANR1868I Export/import command: Copied filespace
copies number kilobytes of data from the server
number file spaces archive number archive
files, backup number backup files, and
spacemg number space managed files.
Explanation: The background export or import processing to estimate the number of removable media
process to service the command export/import command volumes needed to hold the exported information from
copies filespace number client file space definitions, the server.
archive number archive file copies, backup number backup
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 User response: None.
actually moved if Preview=Yes is specified in the
command export/import command.

ANR1872I ANR1878E

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
server and correct the cause of the errors and restart
copies number terabytes of data from the server
the operation.
storage. This figure can be used during export preview ANR1878E A database manager configuration
processing to estimate the number of removable media parameter cannot be updated. The value
volumes needed to hold the exported information from of the DIAGSIZE parameter is greater
the server. than the amount of free space available
in the database manager's diagnostic
data directory.
Explanation: The error occurred because the current
value of the DIAGSIZE database manager configuration
parameter is greater than the amount of free space in
ANR1875I Export/import command: Detected number the drive or the file system that containsing the
errors. diagnostic data directory.
Explanation: The background export or import System action: The operation fails. Depending on the
process to service the command export/import command configuration parameter that is being updated, the
detects number errors while copying information from server might stop.
the server database and data storage to the export
User response: Complete one of the following options:
media or from the export media to the server database
and data storage. v Specify a smaller value for DIAGSIZE.
ANR1879E ANR1883E
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 ANR1881E Command or operation: Failure because the
configuration parameter, issue the following database LDAPUSER password is expired.
command:
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". System action: The operation fails.
User response: The administrator for the LDAP
To change the value of the DIAGSIZE configuration
directory server must update the password for the
parameter, issue the following command:
LDAPUSER account in the LDAP directory server.
Then, after the LDAP administrator updates the
db2 update dbm cfg using DIAGSIZE new_size
password, issue the LDAPPASSWORD command to
match the new password. Reissue the command that
where new_size is the new value for DIAGSIZE in failed.
megabytes. Valid values range from 2 and greater.
See the following topic in the information center: ANR1882E Command or operation: A password was
http://publib.boulder.ibm.com/infocenter/tsminfo/ reset and must change while accessing
v6r3/topic/com.ibm.itsm.tshoot.doc/ the LDAP administrator or node entry
r_pdg_db2logfilelocation.html 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
password on the LDAP directory server.
Explanation: During a REMOVE REPLSERVER
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 User response: If the operation used the LDAPUSER
information, only a single replication server ID can be credentials, update the password for the user account
removed at a time. 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.
User response: Issue the REMOVE REPLSERVER
command with a more specific replication server ID
value such that only one matching server ID is selected. ANR1883E Command or operation: An access failure
occurred while accessing the LDAP
administrator or node entry admin or node
ANR1880W Server transaction was canceled because name with administrator/node name or
of a conflicting lock on table table name. LDAPUSER credentials.
Explanation: The server online reorganization for the Explanation: The command failed after the Tivoli
referenced table could not be completed because of a Storage Manager server accessed an entry in the LDAP
lock conflict between the reorganization process and a directory server and received a locked account error.
server process. The server process was canceled to
allow the reorganization process to be completed. In System action: The operation fails.
some cases, the server might need to cancel multiple User response: If the operation used the LDAPUSER
server processes to resolve the lock conflict. credentials, unlock the user account specified as the
Consequently, this message might be displayed LDAPUSER in the LDAP directory server. If the
multiple times as server processes are forced to stop. In operation used a node or administrator credentials,
addition, other server application error messages might unlock the node or administrator by issuing the
be displayed as the lock conflicts are resolved. UPDATE NODE or UPDATE ADMIN command with a
System action: The server will continue to operate; password or directly unlock the node or administrator
however, until the lock conflict is resolved, no new account in the LDAP directory server.
reorganizations will be started.

ANR1884E ANR1889W
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
credentials were used. v A communication error occurred with the LDAP
directory server
Explanation: The Tivoli Storage Manager server tried
v The LDAPURL is invalid or missing (wrong
to authenticate and access was denied.
hostname or base DN)
System action: The operation fails. v The LDAPUSER is invalid or missing (wrong value
User response: Validate that the LDAPUSER, the or locked)
LDAPPASSWORD, and the LDAPURL are set to the v The LDAPPASSWORD is invalid or missing (wrong
correct values. Correct any invalid setting and reissue value or expired)
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 Tivoli
Storage Manager 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 Tivoli Storage Manager 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 Tivoli
ANR1889W Session session number was terminated
Storage Manager server tried an operation on an LDAP
during backup for node node name (client
entry that was not found on the LDAP directory server.
platform), with file space filespace id or
System action: The operation fails. name because a restore operation is in
progress.
User response: The Tivoli Storage Manager server
tried an operation with the LDAP directory server and Explanation: During a file backup operation, the
the operation failed because the entry could not be server ends a node session because one or more files
found. To insert a new entry for this node or are locked by a restore operation.
administrator, issue an UPDATE NODE or UPDATE
System action: The backup session is terminated by
ADMIN command and provide a password.
the server.
User response: Issue the QUERY RESTORE command
ANR1887E Command or operation: Failure when
with FORMAT=DETAILED to determine if the restore
working with the LDAP directory
operation is active or is in a restartable state. A
server.
restartable restore operation keeps files locked until the
Explanation: The command or operation failed amount of time that is specified for the
because of an error returned by the LDAP directory RESTOREINTERVAL server option is reached. You can
sterver. lower this value to free up locked files. Issue the
QUERY OPTION command to display the current
setting for the RESTOREINTERVAL option.
User response: The Tivoli Storage Manager server ran
If you received this message due to a client backup
an operation with the LDAP directory server and the
operation, restart the operation after the restore
ANR1890W ANR1897I
operation has completed in order to move any

ANR1894E Replication for node node name, file
remaining files. You can also cancel the restartable
space file space name failed because of a
restore session with the CANCEL RESTORE command.
lock conflict.
Explanation: The server could not obtain a resource
ANR1890W Backup operation for session session
that is required to replicate the indicated file space.
number node client node name failed due
to root-only restriction. System action: The command continues, but
replication of the indicated file space fails.
Explanation: The backup operation failed because a
non-root user attempted the operation. A restriction is User response: To increase the probability of acquiring
in place to disallow backup operations by non-root all the necessary resources for replication, run the
users for the indicated node. REPLICATE NODE command when server activity is
relatively low.
System action: The backup operation is terminated. A
message is issued by the client. For clients that are
levels prior to 6.3, message ANS0350E may appear. ANR1895W Command or operation: The password for
the node node name now uses
User response: Retry the backup operation as the root
case-sensitive passwords.
user.
Explanation: The node is authenticating with an
LDAP directory server. The LDAP authentication
password policy is dictated by the LDAP directory
completed with a completion state of
server and this usually requires passwords to be
SUCCESS.
case-sensitive.
Explanation: The process completed with a
completion state of SUCCESS without any warnings or
more-severe messages. User response: None.
ANR1896E Unable to allocate volume volume name
because it is still referenced in the
volume history.
ANR1892W Process process ID for process name
Explanation: The volume cannot be allocated because
completed with a completion state of
the active volume history record shows the volume as
SUCCESS but warning or more-severe
being in use.
messages were issued.
System action: The active volume history record
Explanation: The process completed with a
shows the volume as being in use.
completion state of SUCCESS but warning messages or
more-severe messages were issued by this process. This User response: The volume is being managed by the
process may not have completed all of the processing. server or it might be incorrectly referenced in the
volume history table due to out-of-date records. To
check the records and confirm the volume history
User response: Review the messages in the activity status, issue the QUERY VOLHISTORY command. If
and event logs that were issued by this process. there is an invalid volume history record, use the
Determine if the conditions that caused these messages DELETE VOLHISTORY command to remove the
to be issued had an affect on the operation. record. If the DELETE VOLHISTORY command fails,
contact IBM Software Support to remove the record.
ANR1893E Process process ID for process name

completed with a completion state of ANR1897I LDAP password removed.
FAILURE.
Explanation: The password that the server uses to
Explanation: The process completed with a state of authenticate with the LDAP server was removed by the
FAILURE. SET LDAPPASSWORD command.
User response: Review the messages in the activity User response: None.
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.

ANR1898I ANR1905E
ANR1898I LDAP user name removed. ANR1901I The specified session is associated with
process name process process id and can
Explanation: The LDAP user distinguished name
not be cancelled.
(DN) that the server uses to authenticate with the
LDAP server was removed by the SET LDAPUSER Explanation: The server can not cancel the session
command. because it is associated with a running process.
System action: None. System action: Server operation continues.
User response: None. User response: The session can only be cancelled by
cancelling the associated process. Use the CANCEL
PROCESS command to cancel a process.
ANR1899W Command or operation: Unable to work
with the LDAP directory server.
ANR1902W Node node name on server server name is
Explanation: The command or operation finished, but
not enabled for replication. It will not
the Tivoli Storage Manager server did not work with
be replicated.
the LDAP directory server because the LDAP directory
server configuration is incomplete. If a node or Explanation: The server is not able to replicate the
administrator was being created or updated on the specified node because the node on the specified target
LDAP server, you cannot use it to logon until the server is not enabled for replication.
server is able to use LDAP directory server
System action: The node is not replicated to the
information.
specified server. Server operation continues.
System action: The operation finished, but
User response: Enable the node on the target server
information was not added to the LDAP directory
for replication and rerun the replication command.
server.
User response: An operation was run on the Tivoli
ANR1903E Export export name is not defined.
Storage Manager server with the LDAP directory
server. The operation succeeded, but information was Explanation: An NFS client attempted to mount the
not added to the LDAP directory server because the specified name as a mount point. The specified name is
LDAP directory server configuration is incomplete. not currently being exported by the server.
Common incomplete configuration scenarios are as
follows: System action: The server does not provide an export
of the specified directory.
v LDAPURL values were not provided in the server
options file User response: Ensure that an NFS ADDEXPORT
v The LDAPUSER is invalid (wrong value or locked) command was issued for the specified node.
v The LDAPPASSWORD is invalid (wrong value or
expired) ANR1904E Missing or invalid value for option. A
valid directory needs to be defined for
Update the LDAP directory server information or this.
contact your LDAP administrator to resolve this issue. Explanation: The server detects a missing or invalid
After completing the LDAP configuration, when you value for a server option. A valid directory needs to be
add a node or admin with LDAP authentication, you defined for this option.
are required to submit a new password when you log
on to the Tivoli Storage Manager server. System action: Server initialization stops.
User response: Correct the error and restart the server.
ANR1900E Path between server server source and
library parm is not allowed.
ANR1905E Path dir name for parm does not exist or
Explanation: You must specify a path from the current is not empty.
server to the library when you are defining the library.
Explanation: The directory specified does not exist or
You cannot specify a path from a different server.
is not empty.
source or destination name or define a new path.
path name.
ANR1906E ANR1916I
User response: Issue the command again, specifying a

ANR1906E Command: failed to extend the database
directory that is not in the argument list.
space.
Explanation: A failure occurred during the extend
ANR1911W Invalid value for option name option -
database space. This occurred during the processing of
option valuetype . The default value
a 'EXTEND DBSPACE' command.
default valuetype is used for this option.
Explanation: The value (option value) specified for the
User response: Review error messages to determine (option) option is not valid. The server uses the default
the cause of the failure and retry the 'EXTEND value for this parameter.
DBSPACE' once the issue has been resolved. If unable
to determine the cause of the failure or to resolve it,
please contact your IBM service representative for User response: Verify that the correct value have been
further assistance. used. Update the value, if necessary.
ANR1907E The server can not resolve absolute path ANR1912I Stopping the activity log because of a
of directory dir name. That path might server shutdown.
not exist.
System action: Stopping the activity log because of a
Explanation: The directory specified does not exist or server shutdown.
is not accessible.
System action: The server operation stops.
User response: Reissue the command with a valid ANR1913I command successfully started number of
path name. processes IDENTIFY processes.
System action: The server successfully started the
ANR1908W Invalid value for parameter parameter - indicated number of IDENTIFY processes.
parameter valueMB. The default value
default valueMB is used for this User response: Review the status of the identify
parameter. processes using the QUERY PROCESS or QUERY
ACTLOG commands.
the (parameter) parameter is not a valid. The server uses
the default value for this parameter. ANR1914I command successfully ended number of
processes IDENTIFY processes.
System action: Processing of the command continues
by using the default value. System action: The server successfully ended the
indicated number of IDENTIFY processes.
User response: Verify that the correct value have been
used. Update the value, if necessary. User response: Review the status of the identify
processes using the QUERY ACTLOG command.
ANR1909W Invalid value for option name option -

option valuetype . The default value ANR1915I Autocopy process process ID started
default valuetype is used for this option. transferring data to target storage pool
storage pool name.
Explanation: The value (option value) specified for the
(option) option is not valid. The server uses the default Explanation: An autocopy process to the named
value for this parameter. active-data or copy storage pool has started.
System action: Server operation continues. System action: None.
User response: Verify that the correct value have been User response: None.
used. Update the value, if necessary.
ANR1916I Autocopy process process ID ended
ANR1910E Directory directory name is already successfully for storage pool storage pool
defined for other path in the command. name. Files Transferred: number of files,
Bytes Transferred: number of bytes.
Explanation: While processing the command
argument list, a duplicate path name has been Explanation: An autocopy process to the named
encountered. active/copy storage pool has ended successfully.
System action: The command terminates. System action: None.


ANR1917E ANR1924W
ANR1917E Autocopy process process ID failed for ANR1921W A query for the name of an HBA
storage pool storage pool name. Files adapter has timed out with a current
Backed Up: number of files,Bytes value of timeout value.
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
active/copy storage pool has ended in failure.
User response: Check all of the HBA adapters on the
system and ensure that they are configured correctly. If
User response: Check the activity log for messages there is an FC adapter that is not functional, remove it
that were issued prior to completion. The messages from the system and reconfigure the HBA driver. If
may give more information about the failure. there is no device on an FC port, increase the
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
timed out with a current value of timeout
active-data or copy storage pool has been disabled.
value.
Explanation: The HBAAPI function to open an FC
User response: Check the activity log for messages adapter failed with a time out.
that were issued before the process stopped. The
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
ANR1919W Autocopy process process ID was
there is an FC adapter that is not functional, remove it
disabled for storage pool Storage pool
from the system and reconfigure the HBA driver. If
name . At least one storage pool in the
there is no device on an FC port, increase the
hierarchy is enabled for deduplication.
SANDISCOVERYTIMEOUT value and try again. If the
Explanation: All autocopy processes have been SANDISCOVERYTIMEOUT option is not set, set it with
disabled because at least one target storage pool is a higher value.
enabled for deduplication.
System action: None. ANR1923W A query for fibre channel adapter
attributes has timed out after timeout
User response: Either disable deduplication for all value seconds.
storage pools in the storage-pool hierarchy or remove
the deduplicated storage pool from the autocopy Explanation: A request to the HBAAPI library to
storage-pool hierarchy. obtain attributes for a fibre channel (FC) adapter has
failed to respond within the allotted time.
ANR1920W A query for the number of HBA System action: None.

adapters has timed out with a current
User response: Ensure all fibre channel adapters on
value of timeout value.
the system are configured correctly. If there is an
Explanation: The HBAAPI function to get the number adapter that is non-functional, remove it from the
of HBA adapters failed with a time out. system. If there is no device on an adapter port,
increase the SANDISCOVERYTIMEOUT value to allow
System action: None. the operating system sufficient time to respond. If the
User response: Check all of the HBA adapters on the SANDISCOVERYTIMEOUT option is not set, set it with
system and ensure that they are configured correctly. a value higher than the default value.
Increase the SANDISCOVERYTIMEOUT value and try
again. If the SANDISCOVERYTIMEOUT option is not ANR1924W A query for fibre channel (FC) port
set, set it with a higher value. attributes has timed out after timeout
value seconds.
Explanation: A request to the HBAAPI library to
obtain port attributes for a fibre channel (FC) adapter
has failed to respond within the allotted time.
ANR1925W ANR1931E
User response: Ensure all fibre channel adapters on

ANR1928W The file descriptor table for the SAN
the system are configured correctly. If there is an
discovery process is full.
adapter that is not functional, remove it from the
system. If there is no device attached to a particular Explanation: There might be too many paths that
adapter, increase the SANDISCOVERYTIMEOUT value have been changed and updated by the SAN discovery
to allow the operating system sufficient time to process.
respond. If the SANDISCOVERYTIMEOUT option is
not set, set it with a value higher than the default
value. User response: Use one of the following methods to
resolve this problem:
ANR1925W A query for the fibre channel (FC) target v Use the SANREFRESHTIME option to increase the
mapping has timed out after timeout amount of time elapsed before the cached SAN
value seconds. discovery information is refreshed. For example:
setopt sanrefreshtime 600.
v Increase the nofiles (descriptors) in ulimit and
obtain target mappings for a fibre channel (FC) adapter
restart the Tivoli Storage Manager server.
has failed to respond within the allotted time.
ANR1929E Replication of node node name to target
User response: There might be too many devices to be replication server target server failed. The
discovered, given the allotted time. If the replication mode of the source node is
SANDISCOVERYTIMEOUT option is set, increase the SYNCSEND, and the node is not
value. If the SANDISCOVERYTIMEOUT option is not defined on the target replication server.
set, set the option to a value higher than the default
Explanation: In order to replicate a node that is in
value.
Sync Send mode the target node must exist on the
target replication server and be in Sync Receive mode.
ANR1926W A SCSI inquiry has timed out after
System action: The replication of the node's data fails.
timeout value seconds.
Server operation continues.
User response: Issue the REMOVE REPLNODE
query SCSI devices has failed to respond within the
command for the node on the source server, and then
allotted time.
issue the UPDATE NODE command and specify
System action: None. ENABLED or DISABLED. The replication mode of the
node on the source replication server is automatically
User response: Ensure all devices connected to the
set to SEND after the UPDATE NODE command is
fibre channel (FC) adapters are operational. Remove
issued. After issuing the command, try the replication
non-functional devices from the SAN and reconfigure
operation again.
the devices on the system. If there is no device on an
FC port, increase the SANDISCOVERYTIMEOUT value
and try again. If the SANDISCOVERYTIMEOUT option ANR1930E command: There are no eligible
is not set, set it with a value higher than the default filespaces for node node name.
value.
Explanation: The specified node has no filespaces that
can be replicated.
ANR1927W Autocopy process process ID stopped for
System action: The operation continues.
storage pool Storage pool name . The data
format or device type was not User response: Check replication settings for the
compatible with the data format or filespaces belonging to the node and retry the
device type of the primary pool. command.
active-data or copy storage pool was disabled. ANR1931E command: No replication-eligible data
was found for the specified nodes and
file spaces.
User response: Use the QUERY STGPOOL command
System action: The operation ends.
to check the data format of the storage pools. Use the
QUERY DEVCLASS command to check the device User response: Verify that the specified nodes have
types of the device classes associated with the storage data and file spaces. Verify that replication is enabled
pools. for data types in file spaces that you want to replicate.
To determine the replication status for a file space, use
the QUERY FILESPACE command .

ANR1932I ANR1939W
User response: Allow some time for the server

ANR1932I command: A NAS backup image for node
initialization to complete and retry the session. If this
node name, file space filespace name was
message occurs regularly, consider increasing the value
skipped for replication.
of the SESSIONSERVERINITTIMEOUT option in the
Explanation: The replication process has determined server options file.
that a NAS backup image is not eligible for replication
because the image, or one of its dependent files is
ANR1936E Replication of data type data for file
stored in a non-native storage pool.
space filespace name (fsId filespace id) on
System action: Replication processing continues. node node name failed with reason:
reason.
Explanation: The server could not replicate the
specified file space for the reason indicated in the
ANR1933W Replication of BACKUP data for file
message text.
space filespace name on node node name
skipped because of a restore operation System action: The command continues, but
on target server target server. replication of the file space fails.
Explanation: During replication processing, the file User response: Review the reason for the failure and
space on target replication server has a pending restore correct the problem, if possible. Then rerun the
operation. Files can not be stored into the file space REPLICATE NODE command.
while the pending restore is active.
System action: The files are not replicated on the ANR1937I Failover Session session num for replica
target replication server. node nodename (platform) is enabled for
store operations.
User response: Use the QUERY RESTORE command
and specify the FORMAT=DETAILED parameter to Explanation: The specified replica node is in failover
determine if the restore operation is restartable on mode and is now elgible for store operations.
target replication server. A restartable restore operation
System action: Any store operations request by the
locks the files. The files cannot be moved until the
client on this session will be allowed to proceed.
value for the RESTOREINTERVAL server option is
reached. Use the QUERY OPTION command to display User response: None.
the RESTOREINTERVAL value. You can lower the
RESTOREINTERVAL value to remove a restartable
restore operation earlier in the replication process and ANR1938W The next storage pool is no longer
to unlock the file space. Reissue the REPLICATE NODE defined for source pool storage pool name.
command after the restore operation has completed to Explanation: The storage pool that is being migrated
replicate any remaining files. no longer has a next storage pool to migrate data to.
System action: The migration fails because there is no
ANR1934W REPLICATE NODE: Node node name is target storage pool.
disabled.
User response: Ensure that the storage pool being
Explanation: The requested node is disabled for migrated has a next storage pool before running any
replication, and has been skipped. further migration operations.
System action: The replication proceeds, but this node
is skipped. ANR1939W Session session number for node node
User response: Enable the node for replication using name (client platform) No failover server
the UPDATE NODE command and retry the information currently exists for this
REPLICATE NODE command. node.
Explanation: No failover server is identified for the
ANR1935W Session session number for node node node. The client removes any failover configuration
name (client platform) refused because the that is stored in the client options file.
server initialization is not complete after System action: Server operation continues.
timeout value minutes.
User response: To ensure that failover can occur,
Explanation: The specified session is refused because replicate this node to a secondary server.
the server initialization did not complete within the
specified time.
System action: The session is ended and server
initialization continues.
ANR1940E ANR1948W
ANR1940E Source file(line number): Unique ID ANR1945I Option set option set name successfully
generation failed with Return code. replicated to server target server.
Explanation: An internal error occurred when a Explanation: An option set on this server has been
unique ID is created. This error message always successfully replicated to the target server.
accompanies another error message which provides
more details about the error.
User response: None
User response: Review the reason for the failure and
ANR1946W Option set option set name already exists
correct the problem, if possible.
on target server target server and is not
replicated.
ANR1941I Replicating option set option set name
Explanation: An option set on this server could not be
from source server source server name.
replicated to the target server because an option set
Explanation: A new option set which is referenced by with the same name already exists on the target server.
a replicated node is is created by the replication process
from the definition on the source replication server.
User response: A node that is replicated references an
option set that exists on both the source and target
User response: None. servers. Determine which option set is used on the
target server. When you decide which option to use,
rename the definition on the other server by copying it
ANR1942W Option set option set name already exists.
to a new option set name and deleting the original
Skipping for replication from source
option set.
server source server name.
Explanation: A new option set which is referenced by
ANR1947E Replication of option set option set name
a replicating node is not replicated because an option
to target server target server failed. See
set with the same name already exists on this server.
activity log on target server for possible
The option set is not a replica of the option set for the
errors.
source server.
Explanation: An error occurred on the target server
while replicating the specified option set.
User response: In order to repicate the required option
set, consider copying the option set to an option set
with a different name an update the replicating node to User response: Check the activity log of the target
reference the new option set. server for possible errors.
ANR1943I Replicated option set option set name ANR1948W Volume mount request for volume name
being updated with option set from denied - server operation cannot wait
source server source server name. for the volume.
Explanation: An existing replicated option set on this Explanation: If an operation acquired a volume and a
server is updated with an option set with the same second operation waits for that same volume, the first
name from the source server. operation does not wait to acquire any other volumes.
If the first operation was allowed to wait for another
volume, a deadlock could occur.
User response: None
System action: Server operations continue, volume
acquisition may be tried again, including attempts to
ANR1944I Replicating option set option set name mount scratch tapes, but the server operation does not
with option count options needed by wait to acquire the volume.
node referencing node to server target
User response: If the server operation succeeds, no
server.
action is required. However, if the operation fails, you
Explanation: An option set on this server is replicated need to supply more scratch tapes to the storage pool.
to a target server because it is referenced by a node
which is being replicated.
User response: None

ANR1949W ANR1955E
System action: The device class will be modified to

use the new library.
name (client platform) refused - the node
has a unicode filespace but the client User response: No action is required.
does not use unicode.
Explanation: The server cannot accept the client ANR1953E command: target platform cannot be the
session because the client's platform does not use target of a database upgrade from source
unicode and the node already contains a unicode platform.
filespace. The server records whether or not the client's
data is unicode, and does not let the node change this Explanation: A cross-platform database upgrade is not
attribute. supported between the indicated source and target
platforms.
node session is refused. System action: The INSERTDB command stops.
User response: Logon to the server from a client with User response: Rerun the INSERTDB command on a
a platform that uses unicode data. For example, the supported platform.
original platform that was used to create the existing
filespaces for this node. Alternatively, if the client node ANR1954W Library definition library was not sent to
needs to change to the platform that is currently being downlevel storage agent stagent.
attempted, remove the existing filespaces that contain
unicode data and try the node connection again. Explanation: The storage agent has requested a
definition for a library type that is not supported and
the server has not sent the definition.
ANR1950W Device type device type in device class
device class is not supported during a System action: The storage agent does not process the
migration from z/OS to AIX, or from library definition.
z/OS to Linux on System z. The device User response: Upgrade the storage agent to a level
class will be skipped. that supports the library type.
Explanation: During a migration from z/OS to AIX,
or from z/OS to Linux on System z, a device class was ANR1955E The level of DB2 installed on the
encountered that had a device type that is not system (current db2 level) is lower than
supported on the target platform. the required level (required db2 level).
System action: The device class will not be added to Explanation: The DB2 level on the system does not
the target database. meet the requirements for this server. The server
User response: No action is required.. package includes the required DB2 level which is
installed along with the server. If the DB2 level is
incorrect, it is possible that DB2 failed to upgrade
ANR1951W Device class device class uses a recording during the server upgrade process.
format format (format code) that is not
supported for device type device type. System action: The server stops.
FORMAT=DRIVE will be used instead. User response: To resolve the issue, complete the
Explanation: During a migration from z/OS to AIX, following steps: :
or from z/OS to Linux on System z, a device class was v 1. Verify the level of DB2 installed on the system:
encountered that uses a recording format that is not Run 'db2level'
supported by the device type on the target platform. v 2. Review the installation log files to determine the
System action: The recording format will be replaced problem that caused the DB2 upgrade failure.
with FORMAT=DRIVE. v 3. Fix the problem and install the server again.
User response: Verify whether FORMAT=DRIVE v Do not alter the DB2 software that is installed with
supports your media type. If not, update the device Tivoli Storage Manager installation packages and fix
class, specifying a supported recording format. packs. Do not install or upgrade to a different
version, release, or fix pack of DB2 software. If you
are unable to fix the problem, contact IBM Software
ANR1952I Library library name was added to the Support.
definition of device class device class.
Explanation: During a migration from z/OS to AIX,
or from z/OS to Linux on System z, a device class
definition was updated to include a library that will be
used for accessing media through the z/OS Media
Server.
ANR1956W ANR1963E
ANR1956W The password for the administrator ANR1960I Status monitor finished collecting data
administrator name is expired. at time and will sleep for refreshinterval
minutes.
Explanation: The administrator is attempting to open
a session to a remote server. The password is expired Explanation: The status monitor processing finished a
on the local server. data collection cycle and will sleep for the indicated
number of minutes before waking up and attempting
System action: Operation continues. The remote
to process again.
session may be refused.
System action: The status monitor data collection
User response: Update the password at your earliest
process is idle.
convenience.
User response: The monitor status processing is
enabled using the SET MONITORSTATUS command.
ANR1957W Command or operation: The password for
The interval with which it collects data is controlled by
the administrator administrator name now
the SET STATUSREFRESHINTERVAL. If the status data
uses case-sensitive passwords.
is being collected too frequently, increase the collection
Explanation: The administrator is authenticating with interval. Note that the administrative graphical user
an LDAP directory server. The LDAP authentication interface relies upon this data, do not turn off the status
password policy is dictated by the LDAP directory monitor processing if this interface will be used for the
server and this usually requires passwords to be administration of Tivoli Storage Manager.
case-sensitive.
System action: None. ANR1961I Status monitor collector finished and
exiting.
Explanation: The status monitor processing collector is
terminating processing because the status monitoring
ANR1958I Command: Administrator administrator ID function has been set to off.
is already registered and locked.
System action: None, the status monitor collector
Explanation: An import process is trying to import an terminates.
administrator ID that is registered and locked on the
server. User response: The monitor status processing was
turned off usingthe SET MONITORSTATUS command.
System action: The process continues without As a result of this, the administrative graphical user
importing the ID. interface will not be able to manage this server.
User response: Unlock admin ID ADMIN_CENTER or
log off the administrator. Try the operation again. ANR1962W command: This command is being routed
to one or more servers, so its potential
ANR1959I Status monitor collecting current data at effect cannot be determined. Depending
time. on the parameters that you specify, the
command can be destructive or can
Explanation: The status monitor processing is produce a large amount of output.
collecting a current set of data for the server at the Destructive commands can halt the
indicated time. server, delete data, or change data
System action: The process collects the monitored placement or retention policies.
status data elements. Explanation: The command is destructive or produces
User response: The monitor status processing is a large amount of output.
enabled using the SET MONITORSTATUS command. System action: Tivoli Storage Manager prompts the
The interval with which it collects data is controlled by user to continue.
the SET STATUSREFRESHINTERVAL. If the status data
is being collected too frequently, increase the collection User response: Enter 'Y' to continue with the
interval. Note that the administrative graphical user command. Enter 'N' if you do not want to continue
interface relies upon this data, do not turn off the status with the command.
monitor processing if this interface will be used for the
administration of Tivoli Storage Manager. ANR1963E command: This command cannot be
issued from the server console.
Explanation: This command cannot be issued from the
server console because it may require a long time to
complete and the server console should be available to
control other server functions.

ANR1964W ANR1970E
System action: The server ignores the command and value, the filespace name must be partially-qualified or
continues processing. fully-qualified.
User response: Issue the command from an System action: Server operations continue, but the
administrative client. command is not processed.
User response: Issue the command and specify a
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
name is not valid. The filespace name
must be the wildcard character when
continue.
you specify the CODETType parameter
User response: Enter 'Y' to continue with the
Explanation: The command was issued, but there is a
command or 'N' to terminate the command.
mismatch between the filespace name and the
CODEType value. When you specify the CODEType
ANR1965E Command: You requested to add or value, the filespace name must be a wildcard character.
remove filespace filespace name for the
System action: Server operations continue, but the
node collocation group collocation group
name. Filespaces cannot be added to or
removed from node collocation groups. User response: Issue the command and specify a
wildcard character for the filespace name in
Explanation: The command was issued and the
combination with the NAMEType parameter.
specified collocation group exists. However, the
collocation group is a node collocation group and a
filespace cannot be added to or removed from a node ANR1969E Command: filespace name is not a valid
collocation group. filespace ID. Filespace IDs must be
numeric values when the NAMEType
parameter is FSID.
Explanation: The command was issued, but the list of
filespace IDs are not numeric. When you specify the
registered collocation group that can contain filespace
NAMEType=FSID parameter, the filespace names in the
collocation group members.
filespace name list must contain only numbers.
ANR1966E Command: A filespace name must be
provided so you can add or remove a
collocation group member for filespace User response: Issue the command and specify a list
collocation group collocation group name. of filespace IDs that contain only numbers.
Explanation: The command was issued, and the
specified collocation group exists. However, the ANR1970E Command: An invalid node name list
collocation group is a filespace collocation group, and a node name was specified. A single node
filespace name was not provided when issuing this name must be specified when working
command. with filespace collocation group
members.
command is not processed. Explanation: The command was issued, but the list of
node names is invalid. When working with filespace
collocation group members, only one node name can be
filespace name to be added to the filespace collocation
specified.
group.
ANR1967E Command: The filespace name cannot be
a wildcard character when you specify User response: Issue the command and specify a
the NAMEType parameter for a single node name.
filespace collocation group.
Explanation: The command was issued, but there is a
mismatch between the filespace name and the
NAMEType value. When you specify the NAMEType
ANR1971W ANR1978W

ANR1971W Command: No matching file space was
command has no effect.
found for file space filespace name on
node node name using the specified User response: Issue the command and specify
NAMEType and CODEType parameters. different filespaces.
Explanation: The server did not find a matching file
space name or file space ID for the file space and node ANR1975W Node node name is already associated
that are specified in the command. with node collocation group node
collocation group name. File spaces that
System action: The server ends the command.
belong to same node name cannot be
User response: Enter the command with file space added to the user specified collocation group
names or file space IDs that refer to defined file spaces collocation group.
for the specified node. Note that file space names are
Explanation: This message is displayed in response to
case sensitive. Enter the file space names by using
the DEFINE COLLOCMEMBER command that is used
exactly the same upper- and lowercase characters that
for creating file space collocation group members. Node
match the file space name that is defined on the server.
node name is already associated with the node
File space name searches are also sensitive to
collocation group name collocation group name and file
NAMEType (SERVER, UNICode, FSID) and CODEType
spaces that belong to a node that is already in a node
(BOTH, UNICode, NONUNIcode) parameters. Issue the
collocation group cannot be added to a file space
QUERY FILESPACE command to determine which file
collocation group. The indicated file spaces are not
spaces and file space IDs are defined for a node on the
processed.
server.
ANR1972W Command: No new file space associations User response: If the node name was entered
were added to the collocation group. incorrectly, issue the command again with the correct
node name.
Explanation: The specified command was issued but
no new file space associations are defined for the
collocation group. ANR1976I Command: number of filespace members are
defined in the collocation group
collocation group name.
Explanation: A DEFINE COLLOCMEMBER command
User response: Issue the command and specify
created the specified number of filespace members in
different filespaces.
the indicated collocation group.
ANR1973W Command: Nodes in the NODE
parameter list node list may not contain User response: None.
wildcard characters when dealing with
filespace groups. No filespace
associations were deleted from the ANR1977I File space filespace name on node node
collocation group. name is associated with filespace
collocation group collocation group name.
no file space associations are deleted. Explanation: This message is displayed in response to
the DEFINE COLLOCMEMBER command. File space
System action: Server operations continue, but the filespace name on node node name is associated with the
command has no effect. filespace collocation group name collocation group name.
User response: Issue the command and specify a valid System action: Server operations continue.
client node without wildcards.
ANR1974W Command: Filespaces in the FILESPACE

parameter list filespace list are not ANR1978W File space filespace name on node node
associated with the filespace collocation name is already associated to filespace
group collocgroup name. No filespace collocation group collocation group name.
associations were deleted from the Explanation: This message is displayed in response to
collocation group. the DEFINE COLLOCMEMBER command. Filespace
Explanation: The specified command was issued but filespace name is already associated with a filespace
no file space associations are deleted. collocation group with the name collocation group name.
The indicated filespace is not processed. The other

ANR1979W ANR1985E
filespaces can be processed if specified by the System action: Server operations continue.
command.
User response: If the filespace name was entered
System action: Server operations continue. incorrectly, issue the command again with the correct
filespace name.
User response: If the filespace name was entered
incorrectly, issue the command again with the correct
filespace name. ANR1983W The collocation group collocgroup 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.
no file spaces are associated with the collocation group.
the DEFINE COLLOCMEMBER command. Node node
name is already associated with at least one filespace System action: Server operations continue, but the
collocation group name. The indicated node is not command has no effect.
processed. The other nodes can be processed if
specified by the command.
different nodes.
User response: If the node name was entered ANR1984E command: Replication server server name
incorrectly, issue the command again with the correct is in use by an active replication process
node name. and cannot be removed.
Explanation: When you issue the REMOVE
ANR1980I File space filespace name is disassociated REPLSERVER command, the replication server that you
from filespace collocation group specify to remove is in use by an active replication
collocation group name. process. You cannot remove a replication server that is
used in an active replication process.
the DELETE COLLOCMEMBER command. Filespace System action: The command is stopped by the
filespace name is no longer associated with the filespace server.
collocation group name collocation group name.
User response: Issue the QUERY PROCESS command
System action: Server operations continue. from the source replication server or the target
replication server to identify active replication
processes. Issue the CANCEL PROCESS command from
the source replication server to stop the replication
ANR1981I Command: number of filespace filespace process. If running this command on a target
members were deleted from filespace replication server, log on to the source replication
collocation group collocation group name. server and issue the CANCEL PROCESS command.
When the replication process stops, reissue the
Explanation: A DELETE COLLOCMEMBER command REMOVE REPLSERVER command.
has deleted the specified number of filespace members
from the indicated collocation group.
ANR1985E The remote monitoring admin admin
System action: None. name does not exist.
User response: None. Explanation: The administrator used to monitor
remote servers does not exist.
ANR1982W File space filespace name exists on node System action: Remote monitoring sessions will be
node name but the filespace is not a ended.
member of the specified collocation
group collocation group name. User response: Use the SET MONITORINGADMIN
command to set a new administrator for monitoring
Explanation: This message is displayed in response to remote servers.
the DELETE COLLOCMEMBER command. Filespace
filespace name is not associated with a filespace
collocation group with the name collocation group name.
The indicated filespace is not processed. The other
filespaces can be processed if specified by the
command.
ANR1986E ANR1995E
ANR1986E The remote monitoring server group ANR1990I Remote monitoring started for server
group name does not exist. server name.
Explanation: The server group being remotely Explanation: The specified remote server is now being
monitored does not exist. monitored.
System action: Remote monitoring sessions will be System action: Server operation continues.
ended.
User response: Use the SET
MONITOREDSERVERGROUP command to set a new
ANR1991I Remote monitoring ended for server
group for monitoring remote servers.
server name.
Explanation: The specified remote server is no longer
ANR1987E A communication error occurred during
being monitored.
session session number with monitored
server server name. System action: Server operation continues.
Explanation: The communication error occurred while User response: None.
the system was receiving information from the
specified monitored server.
ANR1992E Command: The parameter parameter is
System action: The monitoring that was in progress missing.
failed. The server will attempt to re-establish
communications with the monitored server. Explanation: The specified server command has been
entered without all required parameters. At least the
User response: If this error occurs frequently, consult named parameter is missing.
your network administrator. Also review the activity
log on both servers for messages that are related to System action: The server ignores the command.
remote monitoring. User response: Reissue the command and enter the
proper syntax.
ANR1988W The remote monitoring session for
server server name was refused - server is ANR1993I command has been removed.
down-level.
Explanation: The specified command was a valid
Explanation: The specified remote server cannot be server command, but is no longer needed due to new
monitored because it must be V6.3.4 or later. capabilities in the TSM server. The command has been
System action: Server operation continues. removed.
User response: Upgrade the specified remote server or System action: The server ignores the command.
remove it from the remote monitoring server group User response: None.
using the DELETE GRPMEMBER command.
ANR1994I Activity log pruning started: removing

ANR1989W Remote monitoring of server server name delete megabytes M based on current size
could not be started. Will retry in current size megabytes M and retention
minutes minutes. setting retention size megabytes M.
Explanation: An error occurred while attempting to Explanation: Server activity log exceeds the retention
monitor the specified remote server. size by the delete megabytes specified. The activity log
System action: Server operation continues. The pruning will delete as many records as necessary to
specified remote server is not being monitored. The reduce the current activity log size by the delete
server will attempt to start monitoring again after the megabytes size.
specified number of minutes. System action: None.
User response: Check previous messages in the User response: None.
activity log. Verify that the specified remote server is
running and is available on the network. If you no
longer want this remote server to be monitored, remove ANR1995E Command: Invalid Formatsize value -
it from the remote monitoring server group using the formatsize value for device class Device
DELETE GRPMEMBER command. Class
Explanation: A value was specified for the Formatsize
parameter which is larger than the maximum capacity
value for the device class indicated in the message. The

ANR1996E ANR2004E
device class is associated with the storage pool Administrators Reference for your particular platform.
specified in the DEFINE VOLUME command and is a
FILE device type. The maximum capacity value of the
ANR1999I Command completed successfully.
device class is the limit of data that the server will
write to the volume. Explanation: Processing for the specified command
completed successfully.
command. System action: Server processing continues.
User response: Reissue the command with a User response: None.
Formatsize value which is less than the maximum
capacity value of the storage pool. The maximum
capacity can be displayed with the QUERY DEVCLASS ANR2000E Unknown command - command.
classname F=D command. Explanation: The specified command is not a valid
server command.
ANR1996E Command: Invalid volume name prefix - System action: The server ignores the command.
volume name. Room for additional
characters is required. User response: Reissue the correct command.
Explanation: The command is being used for multiple

volume names. The suffix for the names is being ANR2001E Insufficient server memory to initiate
generated in the indicated command. When the suffix command.
is taken into account, the specified name is too long by Explanation: A command has been entered, but the
the indicated number of characters. Three characters server cannot obtain enough internal memory to
must be allowed for the suffix. process the command.
System action: The server does not process the System action: The server ignores the command.
command.
User response: Reissue the command with a prefix operating system about how to increase memory for an
short enough to allow for the suffix. Three extra application.
characters are needed for the suffix.
ANR2002E Missing closing quote character.

ANR1997E Command: The Formatsize parameter
must be specified when more than 1 Explanation: A server command that contains a
volume is created. quoted parameter has been entered, but a matching
closing quote is missing.
Explanation: The command specified the createion of
more than one volume with the Numberofvolumes System action: The server ignores the command.
parameter. When multiple volumes are created, the User response: Reissue the command with properly
Formatsize parameter must also be specified to provide matched quotes.
the size of the volumes. Each volume will be created
with the same size.
ANR2003E Illegal use of keyword parameter
System action: The server does not process the character (=) - parameter.
command.
Explanation: A server command contains the
User response: Reissue the command with the parameter shown followed by an equal sign (=), but the
Formatsize parameter or define a single volume parameter is not a keyword parameter.
without the Formatsize parameter.
ANR1998E Command: Invalid value for parameter User response: Reissue the command and enter the
parameter - parameter value. proper syntax.
the (parameter) parameter in command command is not a ANR2004E Missing value for keyword parameter -
valid value for this parameter. parameter.
System action: The command fails and server Explanation: A server command containing a keyword
operation continues. parameter has been entered, but the value for the
parameter is missing.
valid parameter value. For information on valid values System action: The server ignores the command.
for the parameter for the command, refer to the
User response: Reissue the command and supply a
ANR2005E ANR2012W
value for the keyword parameter.

ANR2009E Activity log process has stopped -
database error.
ANR2005E Keyword parameter character (=) may
not be surrounded by blanks.
Explanation: A server command contains a keyword cannot continue due to a server database error.
parameter followed by an equal sign (=), but the equal
System action: The server stops updating the activity
sign is preceded or followed by a blank, or both.
log.
User response: Reissue the command without blanks
next to the equal sign.
ANR2010W The active log space is full. Console
messages cannot be logged until log
ANR2006E Activity log process was not started, the space becomes available.
default output stream cannot be opened.
Explanation: The process that monitors the default transaction is rolled back. The server issues an error
(console) output stream and maintains the activity log message and halts. You cannot restart the server until
cannot access that output stream. the recovery log size is increased.
System action: The server does not update the activity System action: The server halts.
log.
User response: Contact your service representative. the recovery log space is insufficient, monitor the
ANR2007E Activity log process was not started, due archive logs and consider adding more disk space to
to an internal error. the archive log directory. If the archive log space is not
Explanation: The process that monitors the default full and the active log space is full or nearly full,
(console) output stream and maintains the activity log update the value of the ACTIVELOGSIZE option in the
cannot start due to a server internal error. dsmserv.opt file. Set the value of the ACTIVELOGSIZE
option to the new maximum size of the active log.
System action: The server does not update the activity
log.
ANR2011W The server ran out of database space
User response: Examine the server messages issued while entries were being added to the
prior to this message to determine the source of the active log. Console messages will not be
error. Issue the QUERY ACTLOG command to view the logged until database space becomes
activity log and search for messages. If the error cannot available.
representative. Explanation: The process that monitors the console
output stream and maintains the active log cannot
update the active log because of insufficient database
ANR2008E Activity log process has stopped - space.
database transaction could not be
started. System action: The server fails to update the active
log.
(console) output stream and maintains the activity log User response: To increase the amount of database
cannot continue due to a server transaction failure. This space that is available to the server, issue the EXTEND
may be a memory shortage error. DBSPACE command. Add one or more directories to
the database.
log.
ANR2012W Activity log process has encountered
User response: See the documentation for the unexpected table data output in the
operating system about how to increase memory for an default output stream.
application.
has detected invalid data in the console stream.
log.

ANR2013E ANR2021E

ANR2017I Administrator Administrator Name issued
command: Command
ANR2013E The activity log process has encountered
Explanation: This message records the fact that the
unexpected output data in the console
named administrator issued the command specified.
output stream. The process will be
The messages is issued and logged to provide an audit
restarted.
trail for administrative commands.
Explanation: The process that monitors console output
System action: Server operation continues
and maintains the activity log has detected invalid data
(unknown data type) in the console stream. User response: None.
System action: The server restarts the activity log
recording process. While the process is restarting, the ANR2018E Administrator Command: Unicode
server may not be able to record some console conversion failed for argument Command
messages in the activity log. Argument
User response: See the documentation for the Explanation: The specified command argument could
operating system about how to increase memory for an not be converted to a Unicode string. Conversion can
application. fail if the string includes characters that are not
available in the server code page, or if the server has a
problem accessing system conversion routines. If you
ANR2014E Activity log pruning process could not
issued a RENAME FILESPACE command, the new
be started, due to an internal error.
filespace name might be too long.
Explanation: The process that removes expired records
System action: The server command fails.
from the server activity log cannot begin execution due
to a server internal error. User response: Ensure that the server locale is
configured correctly. If you issued a RENAME
System action: The server does not prune the activity
FILESPACE command, consider specifying a shorter
log.
name for the new filespace.
ANR2019I Command: No nodes updated.
activity log and search for messages. If the error cannot Explanation: An UPDATE NODE command has been
be isolated and resolved, contact your service entered, but no objects were updated.
representative.
ANR2015E Activity log failure - database
transaction could not be started.
ANR2020E Command: Invalid parameter - parameter.
Explanation: The process that removes expired records
from the server activity log has failed due to a database Explanation: The specified server command has been
transaction failure, which may be a memory shortage entered with an invalid parameter.
error.
System action: The server ends activity log pruning.
User response: See the documentation for the proper syntax.
application.
ANR2021E Command: Missing subcommand
keyword.
ANR2016E Activity log failure - database error.
Explanation: The specified server command has been
Explanation: The process that removes expired records entered without a valid subcommand (second
from the server activity log has failed due to a server parameter).
database error.
System action: The server ends activity log pruning.
User response: Contact your service representative. proper syntax.
ANR2022E ANR2030E
ANR2022E Command: One or more parameters are ANR2027E Command: Command failed - sufficient
missing. server recovery log space is not
available.
entered without all required parameters. Explanation: A server command has been entered but
cannot be processed because sufficient recovery log
proper syntax.
command.
ANR2023E Command: Extraneous parameter -
the DEFINE LOGVOLUME command to add volumes
parameter.
for use by the log, and can issue the EXTEND LOG
Explanation: The specified server command contains command to extend the size of the log so that the new
more positional parameters than is allowed. volumes are used.

ANR2028E Command: Command failed - sufficient
User response: Reissue the command and enter the server database space is not available.
proper syntax.
Explanation: A server command has been entered but
cannot be processed because sufficient database space
ANR2024E Command: Too many parameters is not available. For certain operations, like SQL
specified. commands, this message can be issued when the
Explanation: The specified server command contains database has space, but it is unusable for the current
more positional parameters than is allowed. request due to the DB allocation history. In this case,
the database query will show a Maximum Reduction of
System action: The server ignores the command. 0.
User response: Reissue the command and enter the System action: The server does not process the
proper syntax. command.
ANR2025E Command: Command failed - server the DEFINE DBVOLUME command to add volumes
thread resource not available. for use by the database, and can issue the EXTEND DB
Explanation: A server command, which has a command to extend the size of the database so that the
requirement to start a server thread, has been entered new volumes are used. If the database has space, but
but cannot be executed because no server thread is the Maximum Reduction is 0, then a database
available. reorganization can also be used to solve the problem.
See the IBM Tivoli Storage Manager Guide, Managing
System action: The command is not executed. the Database and Recovery Log for information on how
User response: Reissue the command. If the command to reorganize the database.
fails with the same error, wait for server activity to
decrease and try again. ANR2029E Command: Transaction failed; command
not executed.
ANR2026E Command: Command failed - sufficient Explanation: A command that is part of the current
server memory is not available. transaction has failed; therefore, any additional
Explanation: A server command has been entered but commands fail.
cannot be processed because sufficient memory is not System action: The server does not process the
available to the server. command.
System action: The server does not process the User response: Stop the administrative session, restart
command. it, and try the command again. If this problem persists,
User response: See the documentation for the contact your service representative.
application. ANR2030E Commit not accepted; transaction failed.
Explanation: A command that is part of the current
transaction has failed; therefore, a COMMIT command
cannot be processed.

ANR2031E ANR2038E
System action: The server does not process the command, in some cases issuing the command again
COMMIT command. will yield a match.
User response: Stop the administrative session, restart
it, and try the command again. If this problem persists, ANR2035E Command: Administrator administrator
contact your service representative. name is not authorized to issue this
command.
ANR2031E Command: At least one attribute must be Explanation: The specified administrator has entered
specified for update. the indicated command, but this administrator does not
have the proper authority necessary to run the
Explanation: The specified UPDATE command has
command. Note: This message can be issued as a result
been entered, but no attributes have been specified for
of the server option REQSYSAUTHOUTFILE YES being
updating.
in effect.
User response: Reissue the UPDATE command with command.
one or more attributes to be updated.
User response: Examine previous messages for any
additional information. Issue the command from a
ANR2032E Command: Command failed - internal properly authorized administrator ID, or contact the
server error detected. system administrator to have additional authority
granted to the current administrator ID.
Explanation: An internal error has occurred during an
attempt to process a server command. This message
always accompanies another error message and ANR2036E Command: Process could not be started -
provides more detail about that error. sufficient memory is not available.
System action: The server does not process the Explanation: A background process cannot be started
command. for the indicated command because sufficient memory
is not available to the server.
prior to this message to determine the source of the System action: A new process is not started to execute
error. Issue the QUERY ACTLOG command to view the this command.
representative.
application.
ANR2033E Command: Command failed - lock

ANR2037E Command: Process could not be started -
conflict.
lock conflict.
Explanation: A server command that requires the
Explanation: A background process cannot be started
server to lock a system resource has been entered. The
for the indicated command because a required system
command cannot be executed because the resource is
resource is already locked by another command or
already in use by another command or process.
process.
System action: A new process is not started to execute
command.
this command. If other processes have been started for
User response: Try the command again at a later time. this command, these processes may execute
successfully.
ANR2034E Command: No match found using this User response: If necessary, try the command again at
criteria. a later time.
Explanation: The specified command has been

entered, but no objects that match the criteria can be ANR2038E Command: Process could not be started -
found. In some cases when using the SELECT server thread resource not available.
command, this message is issued when there is
contention for a record.
for the indicated command because no server thread is
System action: None. available.
User response: Verify that all the specified parameter System action: A new process is not started to execute
values are correct. If a mistake is found, correct it and this command. If other processes have been started for
reissue the command. If you issued a SELECT this command, these processes may execute
successfully.
ANR2039E ANR2046I
User response: If necessary, reissue the command. If another location, the destroyed volume will be deleted
the command fails with the same error, wait for server from the database.
activity to decrease and try again.
continue.
ANR2039E Command: Process could not be started -
User response: Enter 'Y' to restore the volumes, 'N'
otherwise.
for the indicated command because an internal error
ANR2042E Command: Copied parameter not valid
has occurred.
for pool type storage pool volume.
System action: A new process is not started to execute
Explanation: The QUERY CONTENT server command
this command. If other processes have been started for
has been entered with an invalid parameter. COPIED is
this command, these processes may execute
not a valid parameter when the volume specified
successfully.
belongs to a copy or active-data type storage pool.
error. Issue the QUERY ACTLOG command to view the User response: Reissue the command without the
activity log and search for messages. If the error cannot COPIED parameter.
representative.
ANR2043E Command: WAIT parameter not allowed
from server console.
ANR2040W This command attempts to restore all
files in storage pool storage pool which Explanation: The WAIT parameter is not allowed for
have previously been found to be commands issued from the server console.
damaged or which reside on a volume System action: The command is not executed.
with access mode "destroyed"; existing
references to files in storage pool storage User response: Either reissue the command without
pool will be deleted from the database the WAIT parameter or else reissue the command from
after the files have been restored. an administrator using an Administrative Client.
Explanation: Issuing the RESTORE STGPOOL

command will result in deletion of existing files in the ANR2044E Command: Invalid option's value -
indicated primary storage pool after these files have Option's value.
been restored from a copy storage pool. If a volume Explanation: The set option command has been
with access mode destroyed becomes empty because all entered with an invalid value.
files on the volume have been restored to another
location, the destroyed volume will be deleted from the System action: The server does not process the
database. command.
System action: The administrator is asked whether to User response: Reissue the command with a valid
continue. value.
User response: Enter 'Y' to restore the storage pool,

'N' otherwise. ANR2045E Command: An error (error code) occurred
during a write operation.
ANR2041W This command attempts to restore all Explanation: The server detects an error while
files in storage pool storage pool which attempting a write operation.
reside on one of the volumes specified System action: Server processing continues.
in the command; existing references to
files on these volumes will be deleted User response: Refer to the other displayed messages
from the database after the files have to determine why the write operation has failed.
been restored.
Explanation: Issuing the RESTORE VOLUME ANR2046I optionset name: Optionset optionset name
command causes the access mode of the specified defined.
volumes to be updated to destroyed. Existing files will
Explanation: The requested option set has been added
be deleted from the specified volumes after these files
to the system in response to a DEFINE OPTIONSET
have been restored from a copy storage pool. If a
command.
volume with access mode destroyed becomes empty
because all files on the volume have been restored to System action: None.

ANR2047E ANR2056E

ANR2052E Command: Option option name, sequence
number sequence number is not defined
ANR2047E Command: Optionset optionset name is in optionset option set name.
already defined.
Explanation: The requested option is not defined in
Explanation: A DEFINE OPTIONSET command has the optionset specified by the DELETE CLIENTOPT
been entered that specifies an optionset name already command.
System action: The server does not process the command.
command.
User response: To define the optionset, reissue the
command and specify a different optionset name.
ANR2053I Command: Option option name, sequence
number sequence number, has been
ANR2048I Command: Optionset optionset name deleted from optionset option set name.
deleted.
Explanation: The requested option has been deleted
Explanation: The requested option set has been from the specified optionset in response to a DELETE
deleted from the system in response to a DELETE CLIENTOPT command.
OPTIONSET command.
ANR2054I Command: Optionset optionset name
ANR2049E Command: Optionset optionset name is not updated.
defined.
Explanation: The requested option set has been
Explanation: The command shown specifies an updated in the system in response to an UPDATE
optionset that is not defined in the server. OPTIONSET command.
System action: The server does not process the System action: None.
command.
ANR2055I Command: Optionset source optionset name
ANR2050I Command: Option option name defined in copied to optionset target optionset name.
optionset option set name.
Explanation: The requested option has been added to the COPY OPTIONSET command. The optionset
the specified optionset in response to a DEFINE named source optionset name has been copied to the
OPTIONSET command. optionset named target optionset name.
System action: None. System action: Server operation continues.
User response: None. User response: None. The requested option set has
been added to the system in response to a COPY
OPTIONSET command.
ANR2051E Command: Option option name, sequence
number sequence number is already
defined in optionset option set name. ANR2056E Command: Invalid option name - option
name. Retry using the full optionname.
Explanation: The requested option already exists in
the optionset specified by the DEFINE CLIENTOPT Explanation: The command shown specifies an invalid
command. option name.
System action: The server does not process the System action: The server does not process the
command. command.
User response: None. User response: Reissue the command with a valid
option name.
ANR2057E ANR2068I
ANR2057E Command: Invalid option value - option ANR2062I Node node name renamed to new node
value. name.
Explanation: The command shown specifies an invalid Explanation: In response to a RENAME NODE
option value. command, the requested backup-archive node has been
renamed to the new name shown.
command. System action: None.
option value.
ANR2063I Node node name updated.
ANR2058W Command: Options file Filespec not found
Explanation: One or more attributes of a
- user needs to update the file manually.
backup-archive node have been updated by an
Explanation: The server options file cannot be opened UPDATE NODE command.
or found.
System action: The command is processed but the
option is not updated in the options file.
User response: Use a text editor to update the server
ANR2064I Node node name locked.
options file if the user wants to use this value when the
server restarts later. If the user does not update the file, Explanation: In response to a LOCK NODE command,
the current value in the options file will be used when the indicated backup-archive node has been locked.
the server restarts.
ANR2059W Command: Error occurs when writing to User response: None.

Filespec - user needs to update the file
manually. ANR2065I Node node name is already locked.
Explanation: An error occurs when trying to write the Explanation: The indicated backup-archive node
new value to the server options file. referenced in the LOCK NODE command is already
System action: The command is processed but the locked.
option is not updated in the options file. System action: None.
User response: Use a text editor to update the server User response: None.
options file if the user wants to use this value when the
server restarts later. If the user does not update the file,
the current value in the options file will be used when ANR2066I Node node name unlocked.
the server restarts. Explanation: In response to an UNLOCK NODE
command, the indicated backup-archive node is
ANR2060I Node node name registered in policy unlocked.
domain domain name. System action: None.
Explanation: The requested backup-archive node has User response: None.
been added to the system in response to a REGISTER
NODE command and has been assigned to the policy
domain indicated. ANR2067I Node node name is already unlocked.
System action: None. Explanation: The indicated backup-archive node

referenced in the UNLOCK NODE command is not
User response: None. locked.
ANR2061I Node node name removed from policy
domain domain name. User response: None.
Explanation: In response to a REMOVE NODE

command, the requested backup-archive node has been ANR2068I Administrator administrator ID registered.
removed from the system. Explanation: In response to a REGISTER ADMIN
System action: None. command, the requested administrator ID has been
added to the system.

ANR2069I ANR2080I

ANR2075I Administrator administrator ID is already
User response: None. unlocked.
Explanation: The indicated administrator ID
ANR2069I Administrator administrator ID removed. referenced in the UNLOCK ADMIN command is not
locked.
Explanation: In response to a REMOVE ADMIN
command, the requested administrator ID has been System action: None.
removed from the system.
User response: None. ANR2076I System privilege granted to
administrator administrator ID.
ANR2070I Administrator administrator ID renamed Explanation: In response to a GRANT AUTHORITY

to new administrator ID. command, system privilege class has been granted to
the indicated administrator.
Explanation: In response to a RENAME ADMIN
command, the requested administrator ID has been System action: None.
changed to the new name shown.
User response: None. ANR2077I Unrestricted policy privilege granted to
ANR2071I Administrator administrator ID updated. Explanation: In response to a GRANT AUTHORITY

command, unrestricted policy privilege has been
Explanation: One or more attributes of an granted to the indicated administrator.
administrative user have been updated by an UPDATE
ADMIN command. System action: None.
System action: None. User response: None.

ANR2078I Restricted policy privilege granted to
administrator administrator ID - policy
ANR2072I Administrator administrator ID locked. domain domain name.
Explanation: In response to a LOCK ADMIN Explanation: In response to a GRANT AUTHORITY
command, the indicated administrator ID has been command, restricted policy privilege for the specified
locked. policy domain has been granted to the indicated
System action: None. administrator.

ANR2073I Administrator administrator ID is already
locked. ANR2079I Unrestricted storage privilege granted to
Explanation: The indicated administrator ID administrator administrator ID.
referenced in the LOCK ADMIN command is already Explanation: In response to a GRANT AUTHORITY
locked. command, unrestricted storage privilege has been
System action: None. granted to the indicated administrator.

ANR2074I Administrator administrator ID unlocked.
Explanation: In response to an UNLOCK ADMIN ANR2080I Restricted storage privilege granted to
command, the indicated administrator ID is unlocked. administrator administrator ID - storage
pool storage pool name.
Explanation: In response to a GRANT AUTHORITY
User response: None. command, restricted storage privilege for the specified
storage pool has been granted to the indicated
administrator.
ANR2081I ANR2090I

ANR2086I Storage privilege revoked for
User response: None. administrator administrator ID.
Explanation: In response to a REVOKE AUTHORITY
ANR2081I Analyst privilege granted to command, storage privilege class for all storage pools
administrator administrator ID. has been revoked from the indicated administrator.
Explanation: In response to a GRANT AUTHORITY System action: None.

command, analyst privilege class has been granted to
the indicated administrator.
ANR2087I Restricted storage privilege revoked for
User response: None. administrator administrator ID - storage
pool storage pool name.
ANR2082I Operator privilege granted to Explanation: In response to a REVOKE AUTHORITY

administrator administrator ID. 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. System action: None.

ANR2088I Analyst privilege revoked for
ANR2083I System privilege revoked for
administrator administrator ID. Explanation: In response to a REVOKE AUTHORITY
command, analyst privilege class has been revoked
Explanation: In response to a REVOKE AUTHORITY from the indicated administrator.
command, system privilege class has been revoked
from the indicated administrator. System action: None.
ANR2089I Operator privilege revoked for
ANR2084I Policy privilege revoked for
administrator administrator ID. Explanation: In response to a REVOKE AUTHORITY
command, operator privilege class has been revoked
Explanation: In response to a REVOKE AUTHORITY from the indicated administrator.
command, policy privilege class for all policy domains
has been revoked from the indicated administrator. System action: None.
ANR2090I Activity log retention set to value for
management by management style.
ANR2085I Restricted policy privilege revoked for
administrator administrator ID - policy Explanation: The server activity log has been set to
domain domain name. the value indicated with the SET ACTLOGRETENTION
command for the indicated management style. If the
Explanation: In response to a REVOKE AUTHORITY management style is DATE, the value is the number of
command, restricted policy privilege for the specified days that messages will be kept in the activity log
policy domain has been revoked from the indicated before being deleted. If the management style is SIZE,
administrator. the value is the size in megabytes that the activity log
System action: None. will be allowed to occupy in the server database.


ANR2091I ANR2102I
ANR2091I Accounting parameter set to value. ANR2097I Server now disabled for backup/archive
client access.
Explanation: Accounting record generation has been
turned on or off as indicated with the SET Explanation: The server has been made unavailable
ACCOUNTING command. for use by backup-archive clients with the DISABLE
command.
ANR2092I Password expiration period set to
number of days days. ANR2098E Command: Invalid URL specification -
url.
Explanation: The number of days that a password can
be used before it must be changed has been set to the Explanation: The specified URL is too long.
value indicated with the SET PASSEXP command.
User response: Reissue the command and enter a URL
User response: None. value that is 200 characters or less.
ANR2093I Registration parameter set to registration ANR2099I Administrative userid admininstrator

method. name defined for OWNER access to node
node name.
Explanation: Backup-archive node registration has
been set to the method indicated with the SET Explanation: An administrator with the specified
REGISTRATION command. name was created having OWNER access to the client
node. This administrator is created for accessing the
client node from an interactive interface.
ANR2094I Server name set to server name.
Explanation: The name that the server displays and
ANR2100I Activity log process has started.
communicates to backup-archive nodes has been set to
the value indicated with the SET SERVERNAME Explanation: The automatic server process that
command. removes expired server activity log records has begun
processing.
ANR2095I Authentication parameter set to value.
ANR2101I Activity log process stopped, activity log
Explanation: The requirement for a node or
retention set to 0.
administrator to enter a password when establishing a
session with the server has been turned on or off as Explanation: A SET ACTLOGRETENTION command
indicated with the SET AUTHENTICATION command. has set the retention period to zero days. As a result,
activity logging stops.
System action: The activity log process stops
recording console output in the server activity log.
ANR2096I Server now enabled for backup/archive
client access.
ANR2102I Activity log pruning started: removing
Explanation: The server has been made available for
entries prior to date time.
use by backup-archive clients with the ENABLE
command. Explanation: Server activity log records older than the
date and time indicated are being removed from the
activity log.
ANR2103I ANR2110I
ANR2103I Activity log pruning completed: number ANR2107I Server HALT command: Database update
of records records removed. activity is now quiesced.
Explanation: All expired (older than the log archive Explanation: The server has stopped all database
retention value) server activity log records have been update transaction activity. This action occurs when
removed; the number of records deleted is shown. HALT QUIESCE is specified to halt the server with the
database in a consistent state.
System action: The server program ends.
ANR2104I Activity log processing is now restarted.
ANR2108I Server HALT command: Reattempting to
Explanation: The process that records data in the
quiesce database update activity.
server activity log had suspended logging messages
because of insufficient space in the server recovery log Explanation: The server is quiescing transactions that
or database or because access to the database failed. update the database so that the database is in a
The condition that caused the activity log processing to consistent state when the server is halted. The previous
fail has been resolved and the activity log processing is attempt at quiescing database activity failed because of
able to resume. the current transaction load on the server. The quiesce
operation is being reattempted. This action occurs when
System action: Activity log processing resumes.
HALT QUIESCE is specified to halt the server with the
User response: None. database in a consistent state.
System action: When database update transaction
ANR2105W Command: Node was registered in excess activity has been stopped, the server program ends.
of license terms - node registration will
fail after 120% of the licensed quantity
of nodes have been registered.
ANR2109I Server HALT command: Database update
Explanation: The server has detected the addition of a
transaction activity could not be
node in excess of the terms under which the server is
successfully quiesced.
licensed. The REGISTER NODE command will fail after
120% of the licensed number of nodes have been Explanation: After repeated attempts, server database
registered. update transaction activity could not be quiesced. The
server is not halted with the HALT QUIESCE
command. Attempts to quiesce database update
User response: Use the QUERY LICENSE command to transaction activity can fail if heavy transaction load is
determine the license terms that are no longer in on the server when a HALT QUIESCE command is
compliance. You may remove nodes to reduce the entered.
number of registered nodes or purchase additional
client node connections. If additional nodes have been
purchased, issue the AUDIT LICENSES command to User response: You may disable the server, cancel all
resynchronize the server configuration with license client sessions accessing the server, cancel all processes,
terms. and reenter the HALT QUIESCE command to stop
server processing. The HALT command may also be
used to stop server processing without quiescing
ANR2106I Server HALT command: Quiescing
database transaction update activity. Server recovery
database update activity.
logic will be used when the server is restarted to
Explanation: The server is quiescing transactions that reconcile database transaction activity.
update the database so that the database is in a
consistent state when the server is halted. This action
ANR2110I Command started as process process ID.
occurs when HALT QUIESCE is specified to halt the
server with the database in a consistent state. Explanation: A background process has been started
to service the command command. The background
System action: When database update transaction
activity has been stopped, the server program ends.
System action: The server processes the indicated
command.
background process, use the QUERY PROCESS
command. To cancel the background process, use the

ANR2111W ANR2118E

ANR2115E Command: Access mode for volume
number to specify this process.
volume name cannot be changed to
"destroyed" - volume is still online.
ANR2111W Command: There is no data to process for
Explanation: A RESTORE VOLUME command cannot
storage pool.
change the access mode of the indicated volume to
Explanation: The indicated command does not have destroyed because the volume is still online.
any data to process. This can occur if the command
specifies a storage pool with no volumes, or with no
command.
volumes that contain data. This can also occur if there
are no volumes in the storage pool with an access state User response: Issue the VARY OFFLINE command,
of READWRITE or READONLY. and reissue the RESTORE VOLUME command.
System action: The command ends without starting a
background process. ANR2116E Command: Access mode for volume
User response: Issue the QUERY VOLUME F=D
"destroyed" - volume does not belong to
command to verify that there is at least one volume in
a primary storage pool.
the storage pool that contains data, and that the storage
pool volumes have an access state of READWRITE or Explanation: The access mode for the indicated
READONLY. volume cannot be changed to destroyed because the
volume does not belong to a primary storage pool.
ANR2112E Command: Volume volume name is not in System action: The access mode for this volume is not
a primary storage pool. changed.
Explanation: The command indicated specifies the User response: None.
name of a volume that does not belong to a primary
storage pool. The command syntax requires that a
ANR2117E Command: Access mode for volume
volume in a primary storage pool be specified.
System action: The server does not process the "offsite" - volume either does not belong
command. to a copy storage pool or from a device
class of DEVTYPE=SERVER.
User response: Reissue the command with a volume
in a primary pool. 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
ANR2113E Command: Volume volume name does not
or is of a device class with a DEVTYPE of SERVER.
belong to the same storage pool (storage
pool name) as previously listed volumes. System action: The access mode for this volume is not
changed.
Explanation: The indicated command accepts a list of
one or more volumes which belong to the same storage User response: None.
pool. The named volume does not belong to the same
storage pool as the previously listed volumes.
ANR2118E Storage pool storage pool name specified
System action: The server does not process the on the MOVE DATA command is not a
command. valid poolname and or pooltype for
volume volume name.
User response: Issue the command with a list of
volumes that belong to the same storage pool. Explanation: If the volume belongs to a primary
storage pool, then the storage pool specified must also
be a primary storage pool. If the volume belongs to a
ANR2114I Command: Access mode for volume
copy storage pool, then the specified storage pool must
volume name updated to "destroyed".
be the same storage pool as that of the volume.
Explanation: A RESTORE VOLUME command has
System action: The MOVE DATA process fails.
updated the access mode of the indicated volume to
destroyed. User response: Provide a valid primary storage pool
name if the volume belongs to a primary storage pool.
System action: Restore processing continues.
If the volume belongs to a copy storage pool, remove
User response: None. the storage pool name from the command.
ANR2119I ANR2128I
be specified, or the DOMAINS parameter may be

ANR2119I The Option option has been changed in
specfied, but both should not be specified at the same
the options file.
time.
Explanation: The option is updated in the server
options file.
User response: Reenter the command specifying either
System action: Server continues.
the NODES parameter or the DOMAINS parameter, but
User response: None. not both.
ANR2120E Command: Invalid platform name - ANR2124E command name: Invalid Client authority
platform name. specified: authority.
Explanation: The command shown specifies an invalid Explanation: An invalid client authority was specified
platform name. in a GRANT AUTHORITY or REVOKE AUTHORITY
command when the CLASS=NODE parameter was
specified.
command.
platform name. User response: Reenter the command specifying a
valid client authority.
ANR2121W ATTENTION: More than amount changed
unit megabytes, gigabytes or terabytes of the ANR2125I command name: Administrator
database has changed and the last administrator name was granted OWNER
database backup was more than hours authority for client client name.
name hours ago. Use the BACKUP DB
Explanation: The named administrator was granted
command to provide for database
OWNER authority over the named client node as the
recovery.
result of a GRANT AUTHORITY command.
Explanation: The server issues this warning when a
significant amount of database change activity has
occurred and the server database has not been backed User response: None.
up.
System action: Server operation continues. ANR2126I command name: Administrator
administrator name was granted ACCESS
User response: To provide for server database
authority for client client name.
recovery should a hardware or software problem affect
your database, use the BACKUP DB command to back Explanation: The named administrator was granted
up the database. ACCESS authority over the named client node as the
result of a GRANT AUTHORITY command.
ANR2122E command name: The DOMAINS System action: Processing continues.
parameter cannot be specified when the
NODES parameter is specified. User response: None.
Explanation: Both the NODES and DOMAINS

parameters were specified. The NODES parameter may ANR2127I command name: Owner authority for node
be specified, or the DOMAINS parameter may be client node was revoked for administrator
specified, but both should not be specified at the same administrator.
time. Explanation: OWNER authority over the named client
System action: The command fails. node was revoked from the named administrator as a
result of a REVOKE AUTHORITY command.
User response: Reenter the command specifying either
the NODES parameter or the DOMAINS parameter, but System action: Processing continues.
not both. User response: None.
ANR2123E command name: The NODES parameter ANR2128I command name: Access authority for node
cannot be specified when the client node was revoked for administrator
DOMAINS parameter is specified. administrator.
Explanation: Both the NODES and DOMAINS Explanation: ACCESS authority over the named client
parameters were specified. The NODES parameter may node was revoked from the named administrator as a

ANR2129I ANR2139E
result of a REVOKE AUTHORITY command.

ANR2134I Server url set to url.
Explanation: The url that other servers use to
User response: None. communicate with this server has been set to the value
indicated with the SET SERVERURL command.
ANR2129I Administrative userid admininstrator System action: None.
name defined ONLY for authority over
node node name has been removed.
Explanation: The specified administrator has been
ANR2135I Crossdefine set to state.
removed because the client node was removed and the
administrator only had OWNER access to the specified Explanation: The ability for another server to
node. automatically define itself to this server has been
turned on or off as indicated with the SET
CROSSDEFINE command.
ANR2130S Early Product Version has Expired.
Server is HALTing.
ANR2136I Administrator administrator name already
Explanation: This server is pre-release version of the
has POLICY access for domain policy
server. The pre-release version's expiration date has
domain name.
been reached.
Explanation: The named administrator already has
POLICY authority over the named policy domain. An
User response: Install the product version of the attempt to grant client authority over this domain is
server. ignored.
System action: The policy domain is skipped.
ANR2131I Server password set.
allow other servers to communicate with it has been
set, changed or removed with the SET
has POLICY access for domain policy
SERVERPASSWORD command.
domain name to which node node name
System action: None. belongs.
User response: None. Explanation: The named administrator already has

POLICY authority over the named policy domain. An
attempt to grant client authority for a client in this
ANR2132I Server hladdress set to hladdress. domain is ignored.
Explanation: The high level address that other servers System action: The client is skipped.
use to communicate with this server has been set to the
value indicated with the SET SERVERHLADDRESS User response: None.
command.
System action: None. ANR2138I Minimum password length set to length.
User response: None. Explanation: The minimum length of a password a

node or administrator may send to the server is
indicated with the SET MINPWLENGTH command.
ANR2133I Server lladdress set to lladdress.
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.
ANR2139E Command: The value supplied for the
System action: None. minimum password length is not valid -
length.
Explanation: A SET MINPWLENGTH command has
been entered that specifies a value for the length is not
valid. Valid values are from 0 to 64, inclusive.
ANR2140E ANR2149E
System action: The server does not process the administrator. Ensure that the new password is
command. different from the old password. If you are
authenticating to an LDAP directory server ensure that
the new password meets all other password policy
value.
rules specified by the LDAP directory server. Reissue
the command with a valid password.
ANR2140E Command: Invalid activity log retention
period - retention value.
ANR2145E Command: Contact information exceeds
Explanation: A SET ACTLOGRETENTION command maximum characters characters.
has been entered that specifies an invalid log retention
Explanation: A REGISTER NODE or REGISTER
period.
ADMIN command has been entered that specifies a
System action: The server does not process the contact information value that is too long. The
command. maximum valid length is shown in the command.
User response: Reissue the command with a valid System action: The server does not process the
retention period. command.
User response: Reissue the command with less contact
ANR2141E Command: Invalid password expiration information.
period - days value.
Explanation: A SET PASSEXP command has been ANR2146E Command: Node node name is not
entered that specifies an invalid days value. registered.
System action: The server does not process the Explanation: The command shown specifies a node
command. that is not registered with the server.
User response: Reissue the command with a password System action: The server does not process the
expiration period. command.
ANR2142E Command: Invalid server name - server
name.
ANR2147E Command: Node node name is already
Explanation: A SET SERVERNAME command has registered.
been entered that specifies an invalid server name.
Explanation: A REGISTER NODE command has been
System action: The server does not process the entered that specifies a node name already registered
command. with the server.
server name. command.
User response: To register the node, reissue the
ANR2143E Command: Invalid node name - node command and specify a different node name.
name.
Explanation: The command shown specifies an invalid ANR2148E Command: Administrator administrator ID
node name. is not registered.
System action: The server does not process the Explanation: The command shown specifies an
command. administrator ID that is not registered with the server.
node name. command.
ANR2144E Command: Invalid password - password.
Explanation: The command specifies an invalid node ANR2149E Command: Administrator administrator ID
or administrator password. is already registered.
System action: The server does not process the Explanation: A REGISTER ADMIN command has
command. been entered that specifies an administrator ID already
registered with the server.
User response: Ensure that the password adheres to
naming convention rules and meets the minimum System action: The server does not process the
password length requirement as set by your command.

ANR2150E ANR2158E
User response: To register the administrator, reissue

ANR2154E Command: Invalid administrator name -
the command and specify a different administrator ID.
administrator ID.
ANR2150E Command: Node node name is currently
administrator ID.
accessing the server.
Explanation: The command shown specifies a node
command.
that has an active session with the server.
administrator ID.
command.
User response: Reissue the command at a later time,
ANR2155E Command: Invalid privilege class -
or if necessary, cancel the current session and reissue
privilege class.
the command.
Explanation: A command specifies an invalid
administrative privilege class.
ANR2151E Command: Administrator administrator ID
is currently accessing the server. System action: The server does not process the
command.
Explanation: An UPDATE ADMIN or REMOVE
ADMIN command has been entered that specifies an User response: Reissue the command with a valid
administrator ID that is having an active session with privilege class.
the server.
System action: The server does not process the ANR2156E Command: Administrator administrator ID
command. has already been granted system
privilege.
User response: Reissue the command at a later time,
or if necessary, cancel the current session and reissue Explanation: A GRANT AUTHORITY command has
the command. been issued to grant system authority to an
administrator ID that already has system authority.
ANR2152E Command: Inventory references still exist System action: The server does not process the
for node node name. command.
Explanation: A REMOVE NODE command has been User response: None.
entered for a node for which the server is still storing
backup or archive data, or both.
ANR2157E Command: Other privileges cannot be
System action: The server does not process the granted with system privilege.
command.
Explanation: A GRANT AUTHORITY command has
User response: To remove the node, delete all of its been issued to grant system authority to an
file spaces and any virtual file space mapping administrator ID, and at the same time to grant other
definitions from the server and reissue the command. privileges.
ANR2153E Command: Invalid file space name - command.
filespace name.
User response: Reissue the GRANT AUTHORITY
Explanation: The specified server command has been command specifying only system privilege class.
entered with a file space name that is longer than
allowed. Note that the maximum length of a unicode
ANR2158E Command: Policy domains cannot be
file space name is eight characters less than the
specified for unrestricted policy
maximum length of a non-unicode file space name.
Explanation: A REVOKE AUTHORITY command has
command.
been issued to revoke an administrators policy
User response: Reissue the command with a valid file authority over a specific policy domain, but the
space name. administrator has unrestricted policy authority.
command.
ANR2159E ANR2168E
ANR2159E Command: Storage pools cannot be ANR2164E Command: Command rejected -

specified for unrestricted storage administrator ID is the only system
administrator administrator ID. administrator.
Explanation: A REVOKE AUTHORITY command has Explanation: A REMOVE ADMIN or REVOKE
been issued to revoke an administrators storage AUTHORITY command has been issued to remove or
authority over a specific storage pool, but the revoke the authority of the last administrator who had
administrator has unrestricted storage authority. system authority.
command. command.
User response: None. User response: To remove or revoke this ID, grant
system authority to another administrator ID before
reissuing the command.
ANR2160E Command: No new privileges granted to
ANR2165E Command: Invalid begin date - date.
Explanation: A GRANT AUTHORITY command has
been issued to grant authority to an administrator ID, Explanation: A QUERY ACTLOG command has been
but the administrator already has all privileges entered that specifies an invalid begin date as a search
specified. criteria.
command. command.
begin date.
ANR2161E Command: Only system privilege can be
revoked for administrator administrator ANR2166E Command: Invalid begin time - time.
ID.
Explanation: A QUERY ACTLOG command has been
Explanation: A REVOKE AUTHORITY command has entered that specifies an invalid begin time as a search
been issued to revoke one or more of an criteria.
administrators privileges, but the administrator has
system authority.
command.
command.
begin time.
ANR2167E Command: Invalid end date - date.
ANR2162E Command: No privileges revoked for
entered that specifies an invalid end date as a search
Explanation: A REVOKE AUTHORITY command has criteria.
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 command with a valid end
date.
command.
ANR2168E Command: Invalid end time - time.
ANR2163E Command: Command is invalid for
entered that specifies an invalid end time as a search
administrator ID.
criteria.
Explanation: The command specified cannot be issued
for the server console. For instance, the server console
command.
administrator ID cannot be removed.
User response: Reissue the command with a valid end
time.
command.

ANR2169E ANR2177I
ANR2169E Command: Invalid message number - ANR2174E Administrator administrator ID is not

message number. registered. Schedule schedule name is not
processed and is marked as failed.
entered that specifies an invalid message number as a Explanation: The command shown specifies an
search criteria. administrator ID that is not registered with the server.
The schedule and related command are not processed.
command. System action: The server does not process the
command.
message number. User response: Update the command schedule with a
valid administrator ID which has the proper authority
to execute the scheduled command.
ANR2170E Command: Invalid message search string
argument - search string.
ANR2175I Invalid password limit set to password
attempts limit attempts.
entered that specifies an invalid search string as a
search criteria. Explanation: The maximum number of consecutive
invalid passwords a node or administrator may send to
the server is indicated with the SET INVALIDPWLIMIT
command.
command.
search string.
ANR2171E Command: Invalid time range - Begin:
date time End: date time. ANR2176E Command: The value supplied for the
invalid password attempts limit is not
valid - password attempts limit.
entered that specifies an invalid beginning and ending
date/time range. This error can occur when the Explanation: A SET INVALIDPWLIMIT command has
beginning date/time is not before the ending been entered that specifies a value for the consecutive
date/time. invalid password attempts limit that is not valid. Valid
values are from 0 to 9999, inclusive.
command.
date/time range. User response: Reissue the command with a valid
value.
ANR2172E Command: No matching administrators.
ANR2177I node/admin name has count invalid
Explanation: The command shown specified an
sign-on attempts. The limit is limit.
administrator ID that does not match any administrator
registered with the server. Explanation: The server detected an invalid password
for the specified node during sign-on processing. The
node currently has sent count consecutive invalid
User response: If desired, reissue the command with a passwords. The maximum allowed is limit. The server
different administrator ID. will lock the node when limit is reached.
System action: The node or administrator session will
ANR2173E Command: Location information exceeds be refused.
maximum characters characters.
User response: Before the client node is permitted to
Explanation: A DEFINE or UPDATE VOLUME access the server, a properly authorized administrator
command has been entered that specifies a location must unlock the node or administrator with the
information value that is too long. The maximum valid UNLOCK NODE or UNLOCK ADMIN command.
length is shown in the command.
command.
User response: Reissue the command with less
location information.
ANR2178E ANR2184W
for use by the database, and can issue the EXTEND DB

ANR2178E node/admin name has been locked. Invalid
command to extend the size of the database so that the
sign-on attempt limit (limit) reached.
new volumes are used.
Explanation: The specified node has been locked by
the server. The limit for consecutive invalid passwords
ANR2182W Unable to update last access date for
has been reached.
administrator administrator ID - internal
System action: The node or administrator session will server error.
be refused.
Explanation: While establishing an administrative
User response: Before the client node is permitted to session for the indicated ID, the server cannot update
access the server, a properly authorized administrator the administrators date of last access due to a server
must unlock the node or administrator with the internal error.
UNLOCK NODE or UNLOCK ADMIN command.
System action: The server establishes the
administrative session, but the last access date is not
ANR2179E Administrator administrator should have updated.
been locked, but was not.
Explanation: The indicated administrator reached the prior to this message to determine the source of the
limit for consecutive invalid passwords and should error. Issue the QUERY ACTLOG command to view the
have been locked. If it were locked, there would be no activity log and search for messages. If the error cannot
means to execute commands requiring system be isolated and resolved, contact your service
authority. representative.
System action: The administrator session will be
refused. ANR2183W Diagnostic(ID): Transaction transaction ID
was aborted.
User response: Sign-on again using the correct
password. Explanation: An error was detected during transaction
commit that caused this transaction to be aborted. This
message may have been preceded by other messages
that give additional information about the failed
administrator administrator ID -
transaction.
insufficient recovery log space.
fails.
session for the indicated ID, the server is unable to
update the administrators date of last access due to User response: Check for additional messages and
insufficient recovery log space. eliminate the condition that caused the failed
transaction. If this was encountered while the server
was halting then this can be ignored. During server
HALT processing, existing in-flight transactions may be
updated.
aborted as a normal part of server shutdown
User response: An authorized administrator can issue processing. If the error cannot be isolated and resolved,
the DEFINE LOGVOLUME command to add volumes contact your service representative.
ANR2184W Diagnostic(ID): Transaction transaction ID
volumes are used.
was aborted for command command.
commit for the specified server command. This
administrator administrator ID -
message should be preceded by other messages that
insufficient database space.
give additional information about the failed transaction.
session for the indicated ID, the server cannot update
fails.
the administrators date of last access due to
insufficient database space. User response: Check for additional messages and
updated.

ANR2185W ANR2192E

ANR2185W Transaction was aborted for command
command.
ANR2189W Diagnostic(ID): Transaction transaction ID
was aborted for node/admin name.
messages that give additional information about the Explanation: An error is detected during a transaction
failed transaction. commit for the specified node or administrator name.
This message should be preceded by other messages
fails.
transaction.
fails.
contact your service representative. User response: Check for additional messages and
ANR2186W Transaction was aborted for session
platform).
ANR2190E command: Device class DISK cannot be
specified for this command.
messages that give additional information about the Explanation: The DEVCLASS value DISK cannot be
failed transaction. specified for the command.
System action: The activity that generated this error System action: The command fails and server
fails. operation continues.
User response: Check for additional messages and User response: Reissue the command and specify a
eliminate the condition that caused the failed valid device class. Issue the QUERY DEVCLASS
transaction. If the error cannot be isolated and resolved, command for a list of valid device classes for the
contact your service representative. server.
ANR2187W Transaction was aborted for node/admin ANR2191E command: Volume list contains defined
name. and undefined volumes.
Explanation: An error is detected during a transaction Explanation: The list of volumes specified on the
commit for the specified node or administrator name. SALVAGE VOLUME command must all be defined to
This message should be preceded by other messages the server, or all not defined to the server.
transaction. System action: The command fails and server
fails. User response: Reissue the command and specify a
valid list of volumes.
transaction. If the error cannot be isolated and resolved, ANR2192E Command: Unable to start background
contact your service representative. process.
Explanation: The server command processor is not
ANR2188W A Transaction was aborted. The activity able to start a background process to perform the
is terminating. command command.
Explanation: An error is detected during a transaction System action: The command process ends and server
commit. This message should be preceded by other operation continues.
messages that give additional information about the User response: See the documentation for the
failed transaction. operating system about how to increase memory for an
System action: The activity that generated this error application.
ends.
ANR2193E ANR2203I
ANR2193E Command: Invalid option set name - ANR2198I Command: Web authentication time-out
option set name. set to time-out value minutes.
Explanation: The command shown specifies an invalid Explanation: The time-out value that determines how
option set name. often WEB browser administrative users need to
re-authenticate with the server has been set with the
SET WEBAUTHTIMEOUT command to the value
command.
displayed.
option set name.
ANR2194E Command: Invalid option set description
- too long. ANR2199I Password expiration period for node
node name set to number of days days.
description. The description is too long. 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
command.
command.
description.
ANR2195E Command: Invalid option sequence
number - option sequence number name. ANR2200I Storage pool storage pool name defined
(device class device class name).
option sequence number. Explanation: A DEFINE STGPOOL command has
created the storage pool indicated of the device class
shown.
command.
option sequence number. User response: None.
ANR2196E Command: Option name and/or Option ANR2201I Storage pool storage pool name deleted.
value is missing for define.
Explanation: A DELETE STGPOOL command has
Explanation: The specified DEFINE command has deleted the storage pool indicated.
been entered, but no attributes have been specified for
the definition.
command.
ANR2202I Storage pool storage pool name updated.
User response: Reissue the DEFINE command with
one or more attributes to be defined Explanation: An UPDATE STGPOOL command has
updated the storage pool indicated.
ANR2197E Command: The value supplied for the System action: None.
WEB authentication time out is not
valid - time-out value. User response: None.
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
System action: The server does not process the created the device class indicated.
value.

ANR2204I ANR2214E
ANR2204I Device class device class name deleted. ANR2209W Volume volume name contains no data.
Explanation: A DELETE DEVCLASS command has Explanation: The AUDIT VOLUME or MOVE DATA
deleted the device class indicated. command entered specifies a volume that contains no
data.
command.
ANR2205I Device class device class name updated.
Explanation: An UPDATE DEVCLASS command has
ANR2210I Vary online initiated for disk volume
updated the device class indicated.
volume name.
Explanation: A VARY ONLINE command for the
User response: None. volume shown is being processed, and if no errors
occur the volume will be varied online.
ANR2206I Volume volume name defined in storage System action: None.

pool storage pool name (device class device
class name).
Explanation: A DEFINE VOLUME command has
ANR2211I Vary offline initiated for disk volume
defined the volume indicated in the storage pool
volume name.
shown that belongs to the device class shown.
Explanation: A VARY OFFLINE command for the
volume shown is being processed and, if no errors
User response: None. occur, the volume will be varied offline.
ANR2207I Volume volume name updated.
Explanation: An UPDATE VOLUME command has
updated the volume indicated.
ANR2212I Command: No volumes updated.
Explanation: An UPDATE VOLUME command has
User response: None. been entered, but no objects were updated.
ANR2208I Volume volume name deleted from
storage pool storage pool name.
Explanation: The volume indicated has been deleted
ANR2213I Command: Storage pool storage pool name
by one of the following:
renamed to storage pool name.
v A DELETE VOLUME command was issued.
Explanation: A RENAME STGPOOL command has
v The volume was empty and the volumes access
been entered. The rename of the storage pool was
mode was updated to destroyed.
successful.
v The volume was empty, scratch, and offsite, and the
access mode was changed to readwrite, readonly, or System action: None.
unavailable. User response: None.
v The volume was scratch, not offsite, and was
emptied by DELETE FILESPACE, RECLAMATION,
ANR2214E Command: Invalid backup set name -
or RESTORE VOLUME/STGPOOL.
backup set name.
v The volume was an empty scratch WORM FILE
volume and deleted by RECLAMATION since the Explanation: The command shown specifies an invalid
retention of the volume has expired. backup set name.
System action: None. System action: The command fails.
backup set name.
ANR2215E ANR2223I
ANR2215E Command: Description text is too long. ANR2220W This command will delete volume
volume name from its storage pool after
Explanation: The specified description text is too long
verifying that the volume contains no
for a command that allows description text to be
data.
specified.
Explanation: A DELETE VOLUME command with the
System action: The command fails
Discarddata=No option has been entered.
System action: The system asks whether you wish to
shorter description
continue with the command.
User response: To process the DELETE VOLUME
ANR2216E Command: Device class must be a
command, enter 'Y' to continue or 'N' to stop the
sequential device class.
process.
Explanation: The device class specified on the
command is not a sequential device class.
ANR2221W This command will result in the
System action: The command fails deletion of all inventory references to
the data on volume volume name, thereby
User response: Reissue the command specifying the rendering the data unrecoverable. If the
name of a sequential device class volume being deleted contains
deduplicated data, the server invalidates
ANR2217E Command: Invalid backup set retention all files that reside in the storage pool
period - retention value. that are dependent upon the data stored
on this volume. Files on other volumes
Explanation: Server processing for the backup set might be marked as damaged and result
command command fails because the value (retention in warning messages when that data is
value) specified for the RETENTION parameter is not accessed.
valid.
Explanation: A DELETE VOLUME command with the
System action: The command fails Discarddata=Yes option has been entered.
User response: Reissue the command specifying a System action: The system asks whether you wish to
valid RETENTION value. continue with the command.
User response: To process the DELETE VOLUME
ANR2218E Command: A device class must be command, enter 'Y' to continue or 'N' to stop the
specified. process.
Explanation: The DEVCLASS parameter is not
specified in the command command name. A DEVCLASS ANR2222I Discard Data process started for volume
value must be specified. volume name (process ID process ID).
System action: The command fails. Explanation: As a result of a DELETE VOLUME
User response: Reissue the command specifying a command with the Discarddata=Yes option, the process
valid device class. Issue the QUERY DEVCLASS whose ID is displayed has begun to delete the data on
command for a list of valid device classes for the the volume shown.
server. System action: The server deletes the data on the
volume.
ANR2219I Discard Data process ended for volume User response: None.
volume name - volume is not deleted
from storage pool storage pool name
because the volume access is offsite. ANR2223I Discard Data process ended for volume
volume name - volume deleted from
Explanation: The process that deleted data for the storage pool storage pool name.
volume shown has ended, but the volume has not been
deleted because the volume access is marked as offsite. Explanation: The process that deleted data for the
volume shown has ended, and the volume has been
System action: None. deleted.
User response: To delete the volume, change the System action: None.
volume access to readwrite, readonly, or unavailable.

ANR2224W ANR2234W
User response: Reissue the command at a later time. If

ANR2224W Discard Data process terminated for
this problem persists, contact your service
volume volume name - process canceled.
representative.
Explanation: The process that was deleting data for
the volume shown, in preparation for deleting the
ANR2229W Discard data process terminated for
volume, has been canceled.
volume volume name - internal server
System action: The server does not delete the volume. error detected.
User response: None. Explanation: The process that was deleting data for
the volume shown, in preparation for deleting the
volume, has ended due to a server internal error.
ANR2225W Discard Data process terminated for
volume volume name - volume still System action: The server does not delete the volume
contains data.
Explanation: The process that was deleting data for issued prior to this message to determine the source of
the volume shown, in preparation for deleting the the error. Issue the QUERY ACTLOG command to view
volume, has ended. However, the volume contains the activity log and search for messages that indicate
data. the source of the error.
System action: The server does not delete the volume.
ANR2232W This command will move all of the data
stored on volume volume name to other
volumes within the same storage pool;
ANR2226W Discard data process terminated for the data will be inaccessible to users
volume volume name - sufficient recovery until the operation completes.
log space is not available.
Explanation: A move data has been entered that will
Explanation: The process that was deleting data for move data from the indicated volume to other volumes
the volume shown, in preparation for deleting the in the same storage pool. While the data is being
volume, has ended due to a shortage of recovery log moved, it will not be available to users.
space.
System action: The server does not delete the volume. continue.
User response: An authorized administrator can issue User response: Enter 'Y' to continue with the
the DEFINE LOGVOLUME command to add volumes command or 'N' to end the process.
ANR2233W This command will move all of the data
volumes are used.
stored on volume volume name to other
volumes in storage pool storage pool
ANR2227W Discard data process terminated for name; the data will be inaccessible to
volume volume name - sufficient memory users until the operation completes.
is not available.
Explanation: A move data has been entered that will
Explanation: The process that was deleting data for move data from the indicated volume to volumes in
the volume shown, in preparation for deleting the the storage pool shown. While the data is being moved
volume, has ended due to a shortage of memory. it will not be available to users.
System action: The server does not delete the volume. System action: The administrator is asked whether to
continue.
operating system about how to increase memory for an User response: Enter 'Y' to continue with the
application. command or 'N' to end the process.
ANR2228W Discard data process terminated for ANR2234W This command will halt the server; if
volume volume name - lock conflict the command is issued from a remote
detected. client, it may not be possible to restart
the server from the remote location.
Explanation: The process that was deleting data for
the volume shown, in preparation for deleting the Explanation: A HALT command has been entered.
volume, has ended due to a locking conflict.
System action: The server does not delete the volume. continue.
ANR2235W ANR2242I
User response: Enter 'Y' to halt the server or 'N' to System action: The system removes the authority.
leave the server activated.
ANR2235W This command will remove

ANR2238W This command will result in the
administrator adminName. This
deletion of all inventory references to
administrator has defined or updated
the data on filespaces that match the
schedules. Removing this authority
pattern filespace name for node node name,
WILL cause these schedules to fail.
whereby rendering the data
Explanation: A REMOVE ADMINISTRATOR unrecoverable.
command has been entered for an administrator that
Explanation: A DELETE FILESPACE command has
owns administrative schedules. If you confirm that you
been entered.
want to proceed with this command, the schedules
owned by this administrator will fail when executed in System action: The system asks whether you wish to
the future. continue with the command.
System action: The system asks whether you wish to User response: To process the DELETE FILESPACE
continue with the command. command, enter 'Y'; otherwise, enter 'N'.
User response: To process the REMOVE
ADMINISTRATOR command, enter 'Y' to continue or ANR2239W This command will revoke privileges
'N' to stop the process. To deal with schedules owned for administrator adminName. This
by the administrator, use the QUERY SCHEDULE administrator has defined or updated
command OR an SQL SELECT statement on the schedules. Revoking this authority may
ADMIN_SCHEDULES table to determine which cause schedules to fail.
schedules were last updated by the administrator. Use
the UPDATE SCHEDULE command to update those Explanation: A REVOKE AUTHORITY command has
schedules under an administrator that has authority to been entered.
execute them, or use the DELETE SCHEDULE System action: The system asks whether you wish to
command to remove the schedules. continue with the command.
User response: To process the REVOKE AUTHORITY
ANR2236W This command has removed command, enter 'Y' to continue or 'N' to stop the
administrator adminName. This process.
schedules. This WILL cause these
schedules to fail in the future. ANR2240I Database volume volume name defined.
Explanation: A REMOVE ADMINISTRATOR Explanation: A DEFINE DBVOLUME command has

command has been entered and the administrator defined the database volume indicated.
removed owns administrative schedules. The schedules System action: None.
will fail when executed in the future because they do
not belong to a valid administrator. User response: None.
System action: The system removes the administrator.

ANR2241I Database volume copy volume name
User response: Use the QUERY SCHEDULE command defined.
OR an SQL SELECT statement on the
ADMIN_SCHEDULES table to determine which Explanation: A DEFINE DBCOPY command has
schedules were last updated by the administrator. Use defined the database volume indicated.
the UPDATE SCHEDULE command to update those System action: None.
schedules under an administrator that has authority to
execute them, or use the DELETE SCHEDULE User response: None.
command to remove the schedules.
ANR2242I Database volume copy volume name
ANR2237W This command has revoked privileges defined; synchronization process started
for administrator adminName. This (process ID process ID).
Explanation: A DEFINE DBCOPY command has
schedules. This may cause these
added the volume shown as a database copy volume.
schedules to fail in the future.
The process whose ID is displayed will copy data to
Explanation: A REVOKE AUTHORITY command has the new volume to synchronize it with existing
been entered. volumes.

ANR2243I ANR2253W

ANR2249I Database extension process initiated
User response: None. (process ID process ID).
Explanation: In response to an EXTEND DB
ANR2243I Database volume volume name deleted. command, the process with the process ID shown has
been started to extend the database.
Explanation: A DELETE DBVOLUME command has
deleted the database volume indicated. System action: None.

ANR2250I Database assigned capacity has been
reduced.
ANR2244I Delete process initiated for database
volume volume name (process id process Explanation: A REDUCE DB command has decreased
ID). the storage capacity of the database.
Explanation: In response to a DELETE DBVOLUME System action: None.
command, the process with the process ID shown has
been started to delete the volume.
ANR2251I Database reduction process initiated
User response: None. (process ID process ID).
Explanation: In response to a REDUCE DB command,
ANR2245I Database volume volume name varied the process with the process ID shown has been started
online. to reduce the database.
Explanation: A VARY ONLINE command has put the System action: None.
database volume indicated into an online state.
User response: None. ANR2252W Database volume copy volume name is
larger than volume volume name by count
megabyte(s).
ANR2246I Vary online process initiated for
database volume volume name (process Explanation: A DEFINE DBCOPY command has
ID process ID). defined a database copy volume whose size is larger
than the volume it mirrors by the amount shown.
Explanation: In response to a VARY ONLINE
command, the process with the process ID shown has System action: The excess capacity is ignored.
been started to vary on the database volume indicated.
User response: None. ANR2253W The database volume copy to be defined
(volume name) is larger than volume
volume name; use of the volume will
ANR2247I Database volume volume name varied result in count megabyte(s) of unusable
offline. space.
Explanation: A VARY OFFLINE command has put the Explanation: A DEFINE DBCOPY command is
indicated database volume into an offline state. attempting to define a database copy volume whose
System action: None. size is larger than the volume it mirrors by the amount
shown. The excess capacity would not be used.
continue.
ANR2248I Database assigned capacity has been
extended. User response: Enter 'Y' to define the copy, 'N'
otherwise.
Explanation: An EXTEND DB command has increased
the storage capacity of the database.
ANR2254E ANR2263I
ANR2254E Command: The VOLUMENAMES ANR2258E Command: Invalid summary retention

parameter must be specified when period - retention value.
SCRATCH=NO is specified.
Explanation: A SET SUMMARYRETENTION
Explanation: The SCRATCH parameter is specified as command has been entered that specifies an invalid
NO for the command Command but the retention period.
VOLUMENAMES parameter is not specified. When
scratch volumes are not allowed, the VOLUMENAMES
command.
parameter must be specified to indicate the volumes
that can be used for the command. User response: Reissue the command with a valid
retention period.
ANR2259I Summary retention period set to number
valid VOLUMENAMES parameter.
of days days.
Explanation: The number of days that activity sumary
ANR2255E Command: The VOLUMENAMES
records are kept in the server database has been set to
parameter must be specified.
the value indicated with the SET
Explanation: The VOLUMENAMES parameter must SUMMARYRETENTION command.
be specified to indicate the volumes that can be used
for the command.
ANR2260I Recovery log volume volume name
valid VOLUMENAMES parameter.
defined.
Explanation: A DEFINE LOGVOLUME command has
ANR2256E Command: The RETENTION parameter
defined the recovery log volume indicated.
must be specified.
Explanation: The RETENTION parameter must be
specified to indicate the retention period to be used for User response: None.
the command.
System action: The command fails. ANR2261I Recovery log volume copy volume name
defined.
valid RETENTION parameter. Explanation: A DEFINE LOGCOPY command has
defined the recovery log volume indicated.
ANR2257E Command: Administrator administrator System action: None.
name is not authorized to issue this
command for node node name. User response: None.
Explanation: The specified administrator has entered

the indicated command, but this administrator does not ANR2262I Recovery log volume copy volume name
have the proper authority necessary to run the defined; synchronization process started
command for the indicated node. Note: This message (process ID process ID).
can be issued as a result of the server option Explanation: A DEFINE LOGCOPY command has
REQSYSAUTHOUTFILE YES being in effect. added the volume shown as a log copy volume. The
System action: The server does not process the process whose ID is displayed copied data to the new
command for the indicated node. If multiple nodes volume to synchronize it with existing volumes.
were specified on the command, the server may System action: None.
continue processing the command for the other nodes.
User response: Examine previous messages for any
additional information. Issue the command from a
properly authorized administrator ID, or contact the ANR2263I Recovery log volume volume name
system administrator to have additional authority deleted.
granted to the current administrator ID. Explanation: A DELETE LOGVOLUME command has
removed the recovery log volume indicated.

ANR2264I ANR2274I

ANR2270I Recovery log assigned capacity has been
reduced.
ANR2264I Delete process initiated for recovery log
Explanation: A REDUCE LOG command has
volume volume name (process id process
decreased the storage capacity of the recovery log.
ID).
Explanation: In response to a DELETE LOGVOLUME
command, the process with process ID shown has been User response: None.
started to delete the volume.
System action: None. ANR2271I Recovery log reduction process initiated
(process ID process ID).
Explanation: In response to a REDUCE LOG
command, the process with the process ID shown has
ANR2265I Recovery log volume volume name varied
been started to reduce the recovery log.
online.
Explanation: A VARY ONLINE command has put the
recovery log volume indicated into an online state. User response: None.
ANR2272W Recovery log volume copy volume name
is larger than volume volume name by
count megabytes.
ANR2266I Vary online process initiated for
Explanation: A DEFINE LOGCOPY command has
recovery log volume volume name
defined a recovery log copy volume whose size is
(process ID process ID).
larger than the volume it mirrors by the amount
Explanation: In response to a VARY ONLINE shown.
command, the process with process ID shown has been
System action: The excess capacity is ignored.
started to vary on the recovery log volume indicated.
ANR2273W The recovery log volume copy to be
defined (volume name) is larger than
ANR2267I Recovery log volume volume name varied volume volume name; use of the volume
offline. will result in count megabytes of
unusable space.
Explanation: A VARY OFFLINE command has put the
recovery log volume indicated into an offline state. Explanation: A DEFINE LOGCOPY command is
attempting to define a recovery log copy volume whose
System action: None. size is larger than the volume it mirrors by the amount
User response: None. shown. The excess capacity would not be used.
ANR2268I Recovery log assigned capacity has been continue.
extended. User response: Enter 'Y' to define the copy or 'N' to
Explanation: An EXTEND LOG command has stop the process.
increased the storage capacity of the recovery log.
System action: None. ANR2274I Data Base Space trigger defined and
enabled.
Explanation: The database space trigger has been
defined with a DEFINE SPACETRIGGER command.
ANR2269I Recovery log extension process initiated The percentage of utilization specified with the
(process ID process ID). FULLPCT parameter is used to automatically expand
Explanation: In response to an EXTEND LOG the database.
command, the process with the process ID shown has System action: None.
been started to extend the recovery log.
ANR2275I ANR2283I
ANR2275I Data Base Space trigger defined, but is ANR2280I Full database backup started as process
disabled. process ID.
Explanation: A database space trigger has been Explanation: A background process was started to
defined, but because the space expansion percentage is backup the contents of the database. The full database
currently set to 0, the space trigger is disabled. backup process was assigned the process ID shown.
System action: None. System action: The database backup process starts
User response: To activate the space trigger, use the
UPDATE SPACETRIGGER command to set the space User response: The administrator may query the
expansion percentage to a value greater than 0. status of the database backup process by using the
QUERY PROCESS command, or cancel the process with
ANR2276I Data Base Space trigger updated and
enabled.
ANR2281I Incremental database backup started as
Explanation: An UPDATE SPACETRIGGER command
process process ID.
has successfully completed for the data base space
trigger. The updated parameters specified on the Explanation: A background process was started to
command are used to automatically trigger space backup the contents of the database. The incremental
expansion for the database. database backup process was assigned the process ID
shown.
System action: The database backup process starts
ANR2277I Database Space trigger updated, but
status of the database backup process by using the
disabled.
Explanation: An UPDATE SPACETRIGGER command the CANCEL PROCESS command.
has successfully completed for the data base space
trigger. However, the space expansion percentage is
ANR2282I Database backup trigger defined and
currently set to 0, which disables the space trigger.
enabled.
Explanation: A database backup trigger has been
User response: To activate the space trigger, use the defined with a DEFINE DBBACKUPTRIGGER
UPDATE SPACETRIGGER command with the command. The percentage of recovery log utilization
SPACEexpansion parameter to set a value greater than specified with the LOGFULLPCT parameter is used to
zero. automatically trigger database backups.
ANR2278I Database Space trigger deleted.
Explanation: A DELETE SPACETRIGGER command
has successfully completed for the database space
ANR2283I Database backup trigger defined, but is
trigger. Space expansions are no longer triggered
disabled.
automatically for the database.
Explanation: A database backup trigger has been
defined, but because the recovery log mode is currently
User response: None. set to NORMAL, the database backup trigger is
disabled. Database backups can only be triggered when
the log mode is set to ROLLFORWARD with a SET
ANR2279I Recovery Log Space trigger defined and LOGMODE command.
enabled.
Explanation: The recovery log space trigger has been
defined with a DEFINE SPACETRIGGER command. User response: To activate the database backup
The percentage of utilization specified with the trigger, use the SET LOGMODE ROLLFORWARD
FULLPCT parameter is used to automatically expand command.
the recovery log.

ANR2284I ANR2292W

ANR2284I Database backup trigger updated and
enabled.
ANR2289I Administrative userid admininstrator
Explanation: An UPDATE DBBACKUPTRIGGER
name defined for authority over node
command has successfully completed. The updated
node name has not been removed.
parameters specified on the command are used to
automatically trigger database backups. Explanation: The specified administrator was not
removed.
ANR2285I Database backup trigger updated, but
disabled. ANR2290W Changing the log mode to NORMAL
will prevent roll-forward recovery.
Explanation: An UPDATE DBBACKUPTRIGGER
command has successfully completed, but because the Explanation: The system has determined that
recovery log mode is currently set to NORMAL, the changing the recovery log mode from ROLLFORWARD
database backup trigger is disabled. Database backups to NORMAL mode will cause the log records being
can only be triggered when the log mode is set to kept for ROLLFORWARD and single database volume
ROLLFORWARD with a SET LOGMODE command. restore processing to be discarded. Without these log
records, only point-in-time database restores can be
performed.
User response: To activate the database backup
trigger, use the SET LOGMODE ROLLFORWARD
continue.
command.
User response: Enter 'Y' to change the LOGMODE, 'N'
otherwise.
ANR2286I Database backup trigger deleted.
Explanation: A DELETE DBBACKUPTRIGGER
ANR2291W Changing the log mode to NORMAL
command has successfully completed. Database
will disable the database backup trigger.
backups are no longer triggered automatically by
recovery log utilization. Explanation: Changing the recovery log mode from
ROLLFORWARD to NORMAL disables the setting
specified in the DEFINE DBBACKUPTRIGGER
User response: None. command. Database backups can only be triggered
when the recovery log mode is set to ROLLFORWARD
with the SET LOGMODE command.
ANR2287I Snapshot database backup started as
process process ID. System action: The administrator is asked whether to
continue.
backup the contents of the database. The snapshot User response: Enter 'Y' to change the log mode, 'N'
database backup process was assigned the process id otherwise. Responding 'Y' does not delete the DEFINE
shown. DBBACKUPTRIGGER settings.
System action: The database backup process starts
and server operation continues. ANR2292W Changing the log mode to
ROLLFORWARD will enable the
database backup trigger.
started process by using the QUERY PROCESS
command, or may cancel the process using the Explanation: Changing the recovery log mode from
CANCEL PROCESS command. NORMAL to ROLLFORWARD causes a previously
issued DEFINE DBBACKUPTRIGGER command to
become effective, and immediately start a full database
ANR2288I Subfile set to state.
backup. Database backups can only be triggered when
Explanation: The SET SUBFILE command has been the recovery log mode is set to ROLLFORWARD with a
used to specify whether this server will allow clients to SET LOGMODE command.
back up subfiles. If a value of CLIENT is specified,
clients are given the option of backing up subfiles. If a
continue.
value of NO is specified, clients are not allowed to back
up subfiles. User response: Enter 'Y' to change the log mode, 'N'
otherwise.
ANR2293I ANR2301E
ANR2293I Only point-in-time database recovery is ANR2297I Command: Optionset optionset name,
now possible. option option name, sequence number old
sequence number, has been changed to
Explanation: An administrator has changed the
new sequence number.
recovery log mode from ROLLFORWARD to NORMAL
with a SET LOGMODE command. Only point-in-time Explanation: The requested option sequence number
database restores can be performed. ROLLFORWARD has been updated in response to an UPDATE
database restores and individual database volume CLIENTOPT command.
restores are not possible.
ANR2298I Command: Optionset optionset name,
ANR2294I Log mode set to log mode. option option name, sequence number old
sequence number, is not updated.
Explanation: The mode for saving recovery log
records has been set as indicated by the SET Explanation: The requested option sequence number
LOGMODE command. When set to NORMAL, only is not updated in response to an UPDATE CLIENTOPT
those log records needed to resume database processing command.
if a system failure occurs are saved. When set to
ROLLFORWARD, all log records created since the last
database backup are saved. ROLLFORWARD mode User response: Reissue the UPDATE CLIENTOPT
also enables the database backup trigger to be used to command with a valid old sequence number.
automatically start database backups based on the
percentage of recovery log utilization.
ANR2299I Password expiration period for
System action: None. administrator administrator name set to
number of days days.
Explanation: The number of days that the
administrator's password can be used before it must be
ANR2295I Log mode set to ROLLFORWARD;
changed has been set to the value indicated with the
database backup trigger enabled.
SET PASSEXP command.
records has been set to ROLLFORWARD, and a
previously defined database backup trigger has been User response: None.
enabled. All log records created since the last database
backup are saved in this mode. The database backup
trigger will automatically start a database backup based ANR2300E Could not open "file spec" the server help
on the percentage of recovery log utilization. file.
System action: None. Explanation: The named help file could not be
accessed.
System action: The requested help text is not
displayed.
ANR2296I Log mode set to NORMAL; database
backup trigger disabled. User response: Contact the system administrator.

records has been set to NORMAL mode, and the ANR2301E Errors were encountered while setting
defined database backup trigger is disabled. Only those up the index to the help text.
log records needed to resume database processing if a Explanation: Either insufficient memory or a help file
system failure occurs are saved in this mode. Database read failure has occurred during setup of the help
backups can only be started using the BACKUP DB index.
command.
System action: The server does not display the
System action: None. requested help text.
User response: None. User response: Contact the system administrator.

ANR2302E ANR2309E
ANR2302E The argument operand is not valid for ANR2307E No help text could be found for this
the HELP command. message: message ID.
Explanation: The argument supplied on the HELP Explanation: The message ID you entered for the help
command is not an integer or the name of a command. command does not match any message entry in the file
of help text.
System action: The server does not process the HELP
command. System action: The help command is not processed.
User response: Issue the HELP command with no User response: Contact the system administrator.
operands and select from the numbered list displayed
in response.
ANR2308W Audit Volume marking damaged file as
damaged on volume volume name: Node
ANR2303E There is no help section numbered node name, Type file type, File space
section number. filespace name, fsId filespace id, File Name
file name is number version of total
Explanation: The numeric operand supplied on the
versions versions.
HELP command is either less than 1 or greater than the
highest-numbered entry in the help index. Explanation: As the result of an AUDIT VOLUME
command that specified FIX=YES for the volume
System action: The server does not process the HELP
shown, the file whose information is displayed is
command.
marked as damaged in the server. The file is marked as
User response: Issue the HELP command with no damaged because it can be recovered from a copy
operands and select from the numbered list (help known to exist in a COPY storage pool. If this file
index) displayed in response. belongs to an aggregate, the entire aggregate is marked
damaged, and this message will be issued for every file
in the aggregate. The version numbers for the file are
ANR2304E I/O error reading "help file name" the file numbered from most recent (1) to least recent (n, where
of help text. n is the total number of versions.
Explanation: An error is detected when reading help System action: The file is marked as damaged in the
text from the named file. server database.
System action: The server ends display of the help User response: To recover the damaged file use the
text. RESTORE STGPOOL or RESTORE VOLUME command.
User response: Contact the system administrator.
ANR2309E The server log mode is currently set to
ANR2305E No such command/subcommand: roll-forward. You may run out of log
command subcommand. space when auditing the server in this
mode. Specify LOGMODE=NORMAL
Explanation: The operands you entered for the HELP to set the log mode to NORMAL for the
command do not match any named entry into the file audit operation, or
of help text. LOGMODE=ROLLFORWARD to force
System action: The server does not process the HELP the audit operation with the logmode
command. set to roll-forward.
User response: Check your input for a misspelled Explanation: An AUDITDB operation was specified
command or subcommand name. and the server log mode is set to roll-forward mode.
When in roll-forward mode, the server may run out of
log space during the AUDITDB operation, requiring an
ANR2306E No help text could be found for this emergency extend of the recovery log to re-start the
command/subcommand: command. server. The recommended log mode for executing an
Explanation: The operands you entered for the HELP AUDITDB operation is NORMAL.
command, although valid command/subcommand System action: The AUDITDB operation fails
names, do not match any named entry into the file of
help text. User response: To force the server log mode to
NORMAL for the AUDITDB operation, specify
System action: The server does not process the HELP LOGMODE=NORMAL on the AUDITDB command.
command. Specify LOGMODE=ROLLFORWARD on the
User response: Contact the system administrator. AUDITDB command to allow the audit to run with a
roll-forward log mode setting.
ANR2310W ANR2316W

ANR2310W This command will compare all
inventory references to volume volume
name with the actual data stored on the ANR2314I Audit volume process ended for volume
volume and will report any volume name; file count files inspected, file
discrepancies; the data will be count damaged files deleted, file count
inaccessible to users until the operation damaged files marked as damaged.
completes.
Explanation: The AUDIT VOLUME command
Explanation: During the execution of an AUDIT specifying FIX=YES for the volume shown has ended.
VOLUME command, any data the volume named The number of files audited and the number of
would be unavailable to users. inconsistent files deleted or marked as damaged are
displayed. The number of files marked as damaged
includes all files belonging to aggregates that were
continue.
marked damaged during the audit. Files are marked as
User response: Enter 'Y' to audit the volume or 'N' to damaged in primary storage pools and not deleted
stop the process. when backup copies for the files are known to exist in
COPY storage pools.
ANR2311W This command will discard any System action: None.
inventory references to volume volume
User response: To recover files that have been marked
name associated with missing or
as damaged on the volume, use the RESTORE
inconsistent stored data, thereby
STGPOOL or RESTORE volume command.
rendering the data unrecoverable; the
valid data on the volume will be
inaccessible to users until the operation ANR2315I Audit volume process ended for volume
completes. volume name; file count files inspected, file
count damaged files found and marked
Explanation: During the execution of an AUDIT
as damaged.
VOLUME command, any data the volume named
would be unavailable to users. After the command has Explanation: The AUDIT VOLUME command
ended, any inconsistent data found will be discarded. specifying FIX=NO for the volume shown has ended.
The number of files audited and the number of
inconsistent files found are displayed. The number of
continue.
files marked damaged includes all files belonging to
User response: Enter 'Y' to audit the volume or 'N' to aggregates that were marked damaged during the
stop the process. audit. Inconsistent files are marked as damaged in the
database and can be recovered by using the RESTORE
STGPOOL or RESTORE VOLUME command if copies
ANR2312I Audit Volume (Repair) process started
of the files reside in a COPY storage pool. Another
for volume volume name (process ID
AUDIT VOLUME command may be able to access the
process ID).
files and reset the damaged indicator in the database if
Explanation: As the result of an AUDIT VOLUME the audit volume process cannot access the files due to
command that specified FIX=YES for the volume hardware problems (for example, dirty tape heads).
shown, the process whose ID is displayed has begun
auditing the volume.
User response: If you suspect that files were
System action: The volume is audited and
inaccessible because of hardware problems such as
inconsistent data is discarded.
dirty tape heads, correct the hardware problem and
User response: None. reissue the AUDIT VOLUME FIX=NO command for
this volume. To remove damaged file references, issue
the AUDIT VOLUME command and specify FIX=YES.
ANR2313I Audit Volume (Inspect Only) process
started for volume volume name (process
ID process ID). ANR2316W Audit Volume deleting damaged file on
Explanation: As the result of an AUDIT VOLUME Type file type, File space filespace name,
command that specified FIX=NO for the volume fsId filespace id, File Name file name is
shown, the process whose ID is displayed has begun number version of total versions versions.
auditing the volume.
Explanation: As the result of an AUDIT VOLUME
System action: The volume is audited and command that specified FIX=YES for the volume
inconsistent data is displayed. shown, the file whose information is displayed is
deleted from the server. The version numbers for the

ANR2317W ANR2324W
file are numbered from most recent (1) to least recent User response: If possible, determine and correct the
(n, where n is the total number of versions. cause of the interruption, and reissue the command.
System action: The file is deleted.
ANR2321W Audit volume process terminated for
volume volume name - storage media
inaccessible.
ANR2317W Audit Volume found damaged file on
Explanation: During processing of an AUDIT
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
number version of total versions versions. System action: The AUDIT VOLUME command is
ended.
Explanation: As the result of an AUDIT VOLUME
command that specified FIX=NO for the volume User response: None.
shown, the file whose information is displayed is found
to be in error and not accessible. If this file belongs to
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.
System action: The AUDIT VOLUME command is
ended.
User response: If necessary, make more recovery log
space available to the server.
volume volume name - process canceled.
VOLUME command for the volume shown, the process
volume volume name - sufficient database
performing the audit was canceled.
ended.
VOLUME command for the volume shown, the server
User response: None. does not have sufficient database space to continue.
ANR2319W Audit volume process terminated for ended.
volume volume name - error reading
User response: If necessary, make more database
device.
space available to the server.
VOLUME command for the volume shown, an
unrecoverable read error occurred on the volume.
volume volume name - thread resource
System action: The AUDIT VOLUME command is not available.
ended.
User response: Attempt to correct the cause of the VOLUME command for the volume shown, the server
read error, and reissue the command. cannot start a thread for the audit process.
ANR2320W Audit volume process terminated for ended.
volume volume name - data transfer
User response: Reissue the AUDIT VOLUME
interrupted.
command. If the error persists, it may indicate a
Explanation: During processing of an AUDIT shortage of server memory.
VOLUME command for the volume shown, a data
transfer operation has been interrupted and cannot be
continued.
ended.
ANR2325W ANR2336W
ANR2325W Audit volume process terminated for ANR2333W Missing or incorrect information
volume volume name - sufficient memory detected by AUDIT VOLUME for
is not available. volume volume name.
Explanation: During processing of an AUDIT Explanation: An AUDIT VOLUME command detects
VOLUME command for the volume shown, the server missing or incorrect information for the specified
does not have enough memory available to complete volume.
the command.
User response: Reissue the audit command with
ended.
FIX=YES so that the information can be created or
User response: If necessary make more memory corrected.
ANR2334W Missing or incorrect information
ANR2326W Audit volume process terminated for detected by AUDIT VOLUME for
volume volume name - lock conflict volume volume name - information will
detected. be created or corrected.
Explanation: During processing of an AUDIT Explanation: An AUDIT VOLUME process detects
VOLUME command for the volume shown, the server missing or incorrect information for the specified
cannot obtain a required lock. 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. User response: None.
ANR2327W Audit volume process terminated for ANR2335W Audit Volume has encountered an I/O
volume volume name - internal server error for volume volume name while
error detected. attempting to read: Node node name,
Type file type, Filespace filespace name,
fsId filespace id, File Name file name.
VOLUME command for the volume shown, an internal
server error occurs. Explanation: The AUDIT VOLUME process
encountered an I/O error for the specified volume
while attempting to read the specified file. If this file
ended.
belongs to an aggregate, the entire aggregate is marked
User response: Contact your service representative. damaged, and this message will be issued for every file
in the aggregate.
ANR2332W Object object.ID deleted by another System action: None.

process during execution of an AUDIT
User response: Identify and resolve the I/O error for
VOLUME command for volume volume
the volume if possible. Verify that the volumes device
name.
is functioning properly and that the volume is usable.
Explanation: During processing of an AUDIT For example, if the volume is a tape volume, make sure
VOLUME command, a data storage object was deleted the drive is clean or that the tape volume is usable by
from the volume that was being audited. The AUDIT testing it by using a different drive.
VOLUME process was unable to locate this object on
the specified volume. Normally, this action is not
ANR2336W Audit Volume terminated for volume
considered an error condition, because the object was
volume name - insufficient number of
probably deleted by a process such as a DELETE
mount points available for removable
FILESPACE command.
media.
System action: Processing of the AUDIT VOLUME
Explanation: During Audit Volume for the indicated
command continues.
volume, the server could not allocate sufficient mount
User response: Check the activity log to verify that points for the volume required.
some process (such as a DELETE FILESPACE
System action: Audit Volume stops.
command) was in progress during the AUDIT
VOLUME command that would account for the deleted User response: If necessary, make more mount points
object. If no such process can be identified, contact your available.

ANR2337W ANR2346E
User response: Reissue the command with a storage

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

sets from the server and reissue the command. ANR2345E Command: Invalid volume name - volume
name.
ANR2340E Command: Invalid storage pool name - Explanation: The command indicated contains an
storage pool name. invalid volume name.
Explanation: The command indicated contains an System action: The server does not process the
invalid storage pool name. command.
System action: The server does not process the User response: Reissue the command with a valid
command. volume name.

storage pool name. ANR2346E Command: Volume name "volume name" is
not valid for device class device class
name.
ANR2341E Command: Missing next storage pool
name. Explanation: The command indicated specifies the
name of a volume that cannot be used with the device
Explanation: The command indicated requires a class shown.
storage pool name, but none has been entered.
command.
ANR2347E ANR2356E
volume name.
ANR2352E Command: Device class device class name
ANR2347E Command: Volume name "volume name" is may not be deleted.
ambiguous; resolves to multiple defined
Explanation: A DELETE DEVCLASS command
volume names.
specifies the class name DISK, which is a
Explanation: The command shown was entered with a system-defined device class and may not be deleted.
volume name pattern that matches more than one
volume. The command can only process a single
command.
volume.
User response: Reissue the command with a more
specific volume name.
may not be updated.
Explanation: An UPDATE DEVCLASS command
specifies the class name DISK, which is a
valid for a volume assigned to a primary
system-defined device class and may not be changed.
storage pool.
Explanation: The command indicated specifies an
command.
option that is not valid for a volume in a primary
storage pool. User response: None.
command. ANR2354E Command: Device class device class name
is still referenced by one or more
User response: Reissue the command with valid
storage pools, or database backup, or
options for a volume in a primary storage pool.
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 copy
pools assigned to it, or is referenced by database
storage pool.
backup, export volumes or backupset volumes.
option that is not valid for a volume in a copy storage
command.
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 copy 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.
is not defined. ANR2356E Command: Incompatible parameters
specified - first parameter, second
Explanation: The command indicated references a
parameter.
device class that does not exist.
entered with mutually exclusive parameters. The two
command.
parameters are listed.

ANR2357E ANR2365I

ANR2361E Command: A full database backup is
User response: Reissue the command and enter the required.
proper syntax.
Explanation: A BACKUP DB command specified an
incremental backup, but a full backup is required.
ANR2357E Command: The DISK device class is not
supported for copy storage pools.
command.
Explanation: An attempt is made to define a copy
User response: Reissue the command specifying a full
storage pool using a device of DISK. Copy storage
backup.
pools can only be assigned to a sequential device class.
ANR2362E Command: Database backup is not
command.
currently possible - compressed log
User response: Reissue the command specifying a records exist in the current transaction
sequential device class. checkpoint.
Explanation: A BACKUP DB command was issued
ANR2358E Command: Device class device class name but a database backup cannot be started. Log
is still referenced in the volume history compression has recently taken place, and the
file. compressed log records are still part of the current
transaction checkpoint. After these log records are no
Explanation: The DELETE DEVCLASS command has longer part of the current checkpoint a backup can take
attempted to delete a device class that is associate with place.
entries in the volume history file. These entries are for
volumes that contain database backup or export data. System action: The server does not process the
command.
command. User response: Reissue the command at a later time.
User response: Use the DELETE VOLHIST command

to remove that entries before deleting the device class. ANR2363E Command: One of the following
parameter must be supplied but is
missing - missing parameter, missing
ANR2359E Command: Volume name "volume name" parameter, missing parameter, missing
must be specified with a DISK or FILE parameter.
STGPOOL.
Explanation: The command indicated specifies the entered without one of the mutually exclusive required
name of a volume that must be specified with a storage parameters. One of the parameters from the list must
pool associated with a device class of type DISK or be specified.
FILE.
command. User response: Reissue the command and enter the
proper syntax.
volume name and storage pool.
ANR2364E Command: Missing reclaim-storage pool
name.
may not be used for database backup. Explanation: The command indicated requires a
storage pool name, but none has been entered.
Explanation: The command specifies the DISK device
class, which cannot be used for database backup, System action: The server does not process the
backup trigger, or restore operations. command.
System action: The server does not process the User response: Reissue the command with a storage
command. pool name.
device class. ANR2365I Backupset backup set name for node node
name (data type data type) has been
deleted.
Explanation: The backup set has been deleted.
System action: The server has deleted the backupset.
ANR2366I ANR2374E

ANR2370E Command: Database backup trigger is
already defined.
ANR2366I Backupset backup set name for node node
Explanation: The database backup trigger cannot be
name (data type data type) would have
defined because it is already defined.
been deleted.
Explanation: The backup set would have been deleted
command.
as the result of a DELETE BACKUPSET command, but
the PREVIEW=YES parameter was specified. User response: Use the UPDATE
DBBACKUPTRIGGER command to modify the
database backup trigger parameters.
User response: If the backup set is to be deleted,
reissue the command without specifying
ANR2371E Command: Database backup trigger is
PREVIEW=YES.
not defined.
Explanation: The database backup trigger cannot be
ANR2367I Retention period for backupset backup
updated or deleted because it is not currently defined.
set name for node node name (data type
data type) has been updated. System action: The server does not process the
command.
Explanation: The backup set's retention period has
been updated. User response: None.
System action: The server has updated the
backupset's retention period. ANR2372E Command: Database Space trigger is
already defined.
Explanation: The database space trigger cannot be
defined because it is already defined.
ANR2368I Retention period for backupset backup
set name for node node name (data type System action: The server does not process the
data type) would have been updated. command.
Explanation: The backup set's retention period would User response: Use the UPDATE SPACETRIGGER
have been updated as the result of an UPDATE command to modify the indicated space trigger
BACKUPSET command, but the PREVIEW=YES parameters.
parameter was specified.
System action: None. ANR2373E Command: Database backup trigger is
not defined.
User response: If the backup set is to be updated,
reissue the command without specifying Explanation: The database space trigger cannot be
PREVIEW=YES. updated or deleted because it is not currently defined.
ANR2369I Database backup volume and recovery command.
plan file expiration starting under
process process ID.
Explanation: The server has started expiration
ANR2374E Command: Recovery Log Space trigger is
processing to remove expired database backup volumes
already defined.
and recovery plan files created on a remote server. This
message is issued only if DRM is licensed on the Explanation: The recovery log space trigger cannot be
server. The DB backup volumes expired is based on the defined because it is already defined.
value specified on the SET
DRMDBBACKUPEXPIREDAYS. The recovery plan files System action: The server does not process the
expired is based on the value specified on the SET command.
DRMRPFEXPIREDAYS. Server inventory expiration User response: Use the UPDATE SPACETRIGGER
processing deletes the DB backup volumes and command to modify the indicated space trigger
recovery plan files only if the volumes or plan files are parameters.
created on the server to server virtual volumes.
System action: Server operation continues. The
expiration process is cancellable.

ANR2375E ANR2384E
ANR2375E Command: Recovery Log trigger is not ANR2380E Command: Storage pool storage pool name
defined. is not defined.
Explanation: The recovery log space trigger cannot be Explanation: A nonexistent storage pool is specified
updated or deleted because it is not currently defined. for the issued command.
command. command.
storage pool name. If you are using the MACRO
command to define and update the storage pool, you
ANR2376I Recovery Log Space trigger defined, but
must ensure that the DEFINE STGPOOL command is
is disabled.
committed before the UPDATE STGPOOL command is
Explanation: A recovery log space trigger has been issued. See the Administrator's Guide for more
defined, but because the space expansion percentage is information on processing commands in a macro.
currently set to 0, the space trigger is disabled.
System action: None. ANR2381E Command: Storage pool storage pool name
is already defined.
UPDATE SPACETRIGGER command to set the space Explanation: A DEFINE STGPOOL command specifies
expansion percentage to a value greater than 0. the name of a storage pool that already exists.
ANR2377I Recovery Log Space trigger updated and command.
enabled.
has successfully completed for the recovery log space
ANR2382E Command: Storage pool storage pool name
trigger. The updated parameters specified on the
still contains at least one volume.
command are used to automatically trigger space
expansion for the database. Explanation: A DELETE STGPOOL command specifies
a storage pool that has volumes assigned to it.
command.
User response: Delete the volume belonging to the
ANR2378I Recovery Log Space trigger updated, but
storage pool and reissue the command.
disabled.
is currently in use by clients and/or data
trigger. However, the space expansion percentage is
management operations.
currently set to 0, which disables the space trigger.
storage pool that is in use.
UPDATE SPACETRIGGER command with the
command.
SPACEexpansion parameter to set a value greater than
zero. User response: Reissue the command at a later time.
ANR2379I Recovery Log Space trigger deleted. ANR2384E Command: Next or Reclaim storage pool
storage pool name introduces a cycle into
the storage pool chain.
trigger. Space expansions are no longer triggered Explanation: A DEFINE STGPOOL or UPDATE
automatically for the recovery log. STGPOOL command specifies a next storage pool that
eventually points to the pool being processed.
command.
next pool value.
ANR2385E ANR2392E
ANR2385E Command: Storage pool storage pool name ANR2389E Command: The "option" option is not
is in use as the next or reclaim pool for valid for a primary storage pool.
one or more other storage pools.
Explanation: A DELETE STGPOOL command specifies option that is not valid for a primary storage pool.
a pool that is the next pool or the reclaim pool for
other storage pools.
command.
User response: Reissue the command with options
command.
appropriate for a primary storage pool.
User response: If necessary, update other storage
pools so that they do not reference the pool to be
deleted, and reissue the command.
valid for a pool type storage pool.
ANR2386E Command: High migration threshold
option that is not valid for either a copy or active-data
must be set greater than or equal to the
type storage pool.
low migration threshold.
Explanation: A DEFINE or UPDATE STGPOOL
command.
command has attempted to set the storage pool low
migration threshold (LOWMIG) parameter greater than User response: Reissue the command with options
the high migration threshold (HIGHMIG). appropriate for the specified storage pool type.
command. ANR2391E Command: Server could not write device
configuration information to file name.
User response: Reissue the command with a low
migration threshold less than or equal to the high Explanation: The BACKUP DEVCONFIG command
migration threshold. does not successfully complete because the server
ANR2387E Command: Storage pool storage pool name System action: The server does not process the
is not a primary pool. command.
Explanation: The command indicated specifies the User response: Make sure that the server has proper
name of a storage pool which is not a primary pool. authority to write to the file indicated and that
The command syntax requires that a primary storage sufficient space is available in the file system for the
pool name be specified. file. On MVS, make sure that the data set has been
allocated and that the server has authority to write to
the data set.
command.
ANR2392E Command: An internal error was
primary storage pool name.
encountered in writing device
configuration information to file name.
Explanation: The BACKUP DEVCONFIG command
is not a copy or an active-data pool type
does not successfully complete because the server
pool.
Explanation: The command indicated specifies the
name of a storage pool which is not a copy pool or an
command.
active-data pool. The command syntax requires that a
copy storage pool name or an active-data pool name be User response: Examine error messages on the server
specified. console that may have been displayed prior to this
message and correct any problems, if possible. Make
sure that the server has proper authority to write to the
command.
file indicated and that sufficient space is available in
User response: Reissue the command with a valid the file system for the file. On MVS, make sure that the
copy storage pool name or active-data pool name. data set has been allocated and that the server has
authority to write to the data set.

ANR2393I ANR2399E

ANR2393I Command: Server device configuration
information was written to file name.
Explanation: This message is displayed in response to the file system for the file. On MVS, make sure that the
the BACKUP DEVCONFIG command and indicates data set has been allocated and that the server has
that device configuration information was successfully authority to write to the data set.
written to the file name indicated.
System action: The server records device ANR2397E Command: An internal server error was
configuration information to the file name specified encountered in writing device
configuration information to one or
more of the defined device
ANR2394I Command: Server device configuration
Explanation: The BACKUP DEVCONFIG command
information was written to all device
does not complete successfully because the server
cannot write to one or more of the defined device
Explanation: This message is displayed in response to configuration files.
the BACKUP DEVCONFIG command and indicates
that device configuration information was successfully
command.
written to all files that were specified in the server
options file. User response: Examine error messages on the server
console that may have been displayed prior to this
System action: The server records device
message and correct any problems, if possible. Contact
configuration information to the device configuration
your service representative if you are unable to resolve
files.
the problem.
ANR2398E Command: The device configuration file
ANR2395I Command: Device configuration files contains a statement with invalid
have NOT been defined for automatic syntax.
recording - specify a file name for
Explanation: While processing the device
device configuration information.
configuration information, an invalid statement has
Explanation: This message is displayed in response to been encountered.
the BACKUP DEVCONFIG command and indicates
System action: The server ends the operation being
that device configuration information cannot be written
performed.
because no files were specified in the options file.
User response: Examine error messages on the server
System action: The device configuration information
is not written. Server operation continues.
message and correct any problems if you have
User response: Reissue the BACKUP DEVCONFIG constructed the device configuration file manually.
command and specify the name of a file to which you Make sure the statements are in the proper order. If
would like to have device configuration information you let the server construct the device configuration file
recorded. If desired, you may configure files that automatically, restart the server, refresh the device
should be automatically updated with the configuration file by issuing the BACKUP DEVCONFIG
DEVCONFIG option and restart the server. command, and reissue the operation. If the problem
persists, contact your service representative.
ANR2396E Command: An I/O error was encountered

in writing device configuration ANR2399E Command: Storage pool storage pool name
information to one or more of the is not a sequential pool.
defined device configuration files.
Explanation: The BACKUP DEVCONFIG command name of a storage pool which is not a sequential pool.
does not complete successfully because the server All storage pools are either fixed disk or sequential
cannot write to one or more of the defined device archival. All tape devices, as well as optical and file
configuration files. device classes, are sequential.
command. command.
User response: Examine error messages on the server User response: Reissue the command with a valid
console that may have been displayed prior to this sequential storage pool name.
ANR2400E ANR2408E

ANR2400E Command: Volume volume name is already
command.
defined in a storage pool or has been
used previously to store export, database User response: Check the spelling of the volume name
dump, or database backup information. to ensure it is correct. If the volume does not exist,
preallocate it with the appropriate mechanism for the
operating system on which the server is running.
name of a storage pool volume that already exists or
has been used to store server export, database dump,
or database backup information as recorded in the ANR2405E Command: Volume volume name is
server volume history file. currently in use by clients and/or data
management operations.
command. Explanation: The command indicated specifies the
name of a data storage volume that is currently in use.
User response: Specify a volume that is not in use, is
not defined in a storage pool, and which has not been System action: The server does not process the
previously used for an export, a database dump, or command.
database backup operation as recorded in the server
volume history information. Use the QUERY VOLUME User response: Verify that the volume is unavailable
command to display the names of volumes that are by issuing the QUERY VOLHISTORY command. If the
defined to server storage pools. Use the QUERY volume is listed in the command output, then it is
VOLHISTORY command to display the names of being used and unavailable. Wait until the conflicting
volumes that have been used for export, a database volume activity has completed, and then retry this
dump, or database backup operations. operation. If the volume is currently mounted, but idle,
dismount it using the DISMOUNT VOLUME
command, and then retry the operation.
ANR2401E Command: Volume volume name is not
defined in a storage pool.
ANR2406E Command: Volume volume name still
Explanation: The command indicated specifies the contains data.
name of a storage pool volume that does not exist.
Explanation: The indicated command tries to delete a
System action: The server does not process the data storage volume that contains data.
command.
User response: None. command.
online.
ANR2407E Command: Maximum number of
Explanation: A VARY ONLINE command specifies the mirrored copies exceeded.
name of a volume that is already online.
Explanation: A DEFINE LOGCOPY or DEFINE
System action: The server does not process the DBCOPY command has attempted to add a mirror
command. volume, but the maximum number of mirrors for the
target volume already exists.
command.
ANR2403E Command: Volume volume name is not
online. User response: None.
name of a volume that is not online. ANR2408E Command: Capacity of volume volume
name must be at least as large as
capacity of volume volume name.
command.
Explanation: A DEFINE LOGCOPY or DEFINE
DBCOPY command has attempted to add a mirror
volume, but the size of the volume to be added is less
ANR2404E Command: Volume volume name is not than the size of the target volume.
available.
Explanation: The command indicated has attempted command.
to access a volume that cannot be found.
User response: Use a larger mirror volume.

ANR2409E ANR2416E
ANR2409E Command: Capacity of volume volume ANR2413E Command: Audit operation already in
name must be at least 5 megabytes. progress for associated volume volume
name.
Explanation: A define command for a database or log
volume or copy has specified a volume that is too Explanation: The command shown would require
small to be used by the server for a database or log access to the volume whose name is displayed (because
volume. The minimum size for one of these volumes is data from the volume specified in the command spans
5 megabytes. into this volume); the volume shown cannot be
accessed because it is in use by an audit volume
operation.
command.
command.
volume that is at least 5 megabytes in size.
User response: Reissue the command after the audit
volume operation ends.
ANR2410E Command: Unable to access volume
volume name - access mode is set to
"unavailable". ANR2414E Command: Deletion operation already in
progress for volume volume name.
Explanation: The command shown specifies the
volume whose name is displayed, but the volume Explanation: The command specified a volume that is
cannot be accessed because its status is unavailable. currently in use by a delete volume operation.
System action: The server does not process the System action: If the command is a MOVE
command. NODEDATA command the server will skip the volume
and continues moving node data on other volumes.
User response: If necessary, reset the status of the
Other commands are not processed.
volume and reissue the command.
User response: Reissue the command after the delete
ANR2411E Command: Unable to access associated
volume volume name - access mode is set
to "unavailable". ANR2415E Command: Deletion operation already in
progress for associated volume volume
Explanation: The command shown would require
name.
access to the volume whose name is displayed (because
data from the volume specified in the command spans Explanation: The command shown would require
into this volume); the volume shown cannot be access to the volume whose name is displayed (because
accessed because its status is unavailable. data from the volume specified in the command spans
into this volume); the volume shown cannot be
accessed because it is in use by a delete volume
command.
operation.
command.
User response: Reissue the command after the delete
ANR2412E Command: Audit operation already in
progress for volume volume name.
Explanation: The command specified a volume that is
ANR2416E Command: Move Data operation already
currently in use by an audit volume operation.
in progress for volume volume name.
System action: If the command is a MOVE
Explanation: The command specified a volume that is
NODEDATA command the server will skip the volume
currently in use by a move data operation.
Other commands are not processed. System action: If the command is a MOVE
User response: Reissue the command after the audit
User response: Reissue the command after the move
data process ends.
ANR2417E ANR2425E
ANR2417E Command: Move Data operation already ANR2421E Command: Space reclamation operation
in progress for associated volume volume already in progress for associated
name. volume volume name.
Explanation: The command shown would require Explanation: The command shown would require
access to the volume whose name is displayed (because access to the volume whose name is displayed (because
data from the volume specified in the command spans data from the volume specified in the command spans
into this volume); the volume shown cannot be into this volume); the volume shown cannot be
accessed because it is in use by a move data operation. accessed because it is in use by a reclamation operation.
command. command.
User response: Reissue the command after the move User response: Reissue the command after the
data operation ends. reclamation ends.
ANR2418E Command: Migration operation already ANR2422E Command: Volume volume name is not a
in progress for volume volume name. defined disk volume.
Explanation: The command specified a volume that is Explanation: The command shown specifies a volume
currently in use by a migration operation. name that does not match any known disk volume.
System action: If the command is a MOVE System action: The server does not process the
NODEDATA command the server will skip the volume command.
volume name.
User response: Reissue the command after the
migration ends.
ANR2423E Command: Volume volume name is still
online.
ANR2419E Command: Migration operation already
Explanation: An UPDATE VOLUME command
in progress for associated volume volume
specifies access=unavailable for a disk volume that is
name.
still online.
Explanation: The command shown would require
command.
data from the volume specified in the command spans
into this volume); the volume shown cannot be User response: Issue the VARY OFFLINE command,
accessed because it is in use by a migration operation. and reissue the UPDATE VOLUME command.
command. ANR2424E Command: Unable to access volume
volume name - access mode is set to
"destroyed".
migration ends.
Explanation: The command shown specifies the
volume whose name is displayed, but the volume
ANR2420E Command: Space reclamation operation
cannot be accessed because its status is destroyed.
already in progress for volume volume
name. System action: The server does not process the
command.
Explanation: The command specified a volume is
currently in use by a reclamation operation. User response: If necessary, reset the status of the
System action: If the command is a MOVE
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".
reclamation ends. Explanation: The command shown specifies the
volume whose name is displayed, but the volume
cannot be accessed because its status is offsite.
command.

ANR2426I ANR2435E

ANR2431E Command: Volume volume name is not a
defined database volume.
Explanation: A DELETE DBVOLUME command
ANR2426I Backupset backup set name defined for
specifies the name of a database volume that does not
node node name (data type data type).
exist.
Explanation: The backup set has been defined for the
indicated node.
command.
System action: The server has defined the backupset.
ANR2432E Command: Maximum number of
ANR2427E Backupset backup set name for node node database volumes exceeded.
name (data type data type) was not
Explanation: A DEFINE DBVOLUME command has
deleted. Device class device class name
attempted to add more database volumes than the
was not found.
server can manage.
Explanation: The specified backup set was not deleted
because the device class used to generate it was not
command.
found.
System action: The backup set is not deleted.
User response: If the device class was inadvertently
ANR2433E Command: A database define, delete,
deleted, redefine it, then delete the backup set again.
extend, reduce, or backup operation is
already in progress.
ANR2428E Backupset backup set name for node node
Explanation: The specified command has been entered
name (data type data type) has not been
while a command that is modifying or backing up the
deleted due to error error code.
database is already active.
Explanation: The backup set has not been deleted.
System action: The server has not deleted the command.
backupset.
User response: Wait for other activity to end, and
User response: Check related error messages. reissue the command.
ANR2429E Command: Maximum database capacity ANR2434E Command: Insufficient space on other
exceeded. database volumes to delete volume
volume name.
Explanation: Do not allocate any volume that would
cause the database to exceed 500GB. A subsequent Explanation: A DELETE DBVOLUME command has
DEFINE DBVOLUME command for that volume would been entered, but the data on the volume to be deleted
fail. cannot be copied to other volumes due to insufficient
free space.
command.
User response: Make more database space available,
and reissue the command.
defined as a database volume.
ANR2435E Command: Unable to delete database
Explanation: A DEFINE DBVOLUME command volume volume name - mirrored copies
specifies the name of a database volume that already not synchronized.
exists.
Explanation: A DELETE DBVOLUME command has
System action: The server does not process the been entered, but mirrors of the volume to be deleted
command. are not up to date.
User response: None. System action: The server does not process the
command.
User response: Try the command at a later time (after
ANR2436E ANR2445E
database volumes have been synchronized). System action: The server does not process the
command.
ANR2436E Command: Insufficient space to extend User response: None.
database by requested amount.
Explanation: An EXTEND DB command has been ANR2441E Command: Volume volume name is already
entered, but not enough allocated, unused space is defined as a recovery log volume.
available to the database to add the amount of space
Explanation: A DEFINE LOGVOLUME command
requested.
specifies the name of a recovery log volume that
System action: The server does not process the already exists.
command.
User response: Make more database space available, command.
and reissue the command.
ANR2437E Command: Output error encountered

ANR2442E Command: Volume volume name is not a
while attempting to extend database.
defined recovery log volume.
Explanation: An EXTEND DB command has been
Explanation: A DELETE LOGVOLUME command
entered, but an I/O error occurs during the command.
specifies the name of a recovery log volume that does
System action: The server does not process the not exist.
command.
User response: Reissue the command. If the problem command.
persists, identify and remove or repair the volume that
caused the error.
ANR2443E Command: Maximum number of recovery

ANR2438E Command: Insufficient database space
log volumes exceeded.
would be available following a
reduction by the requested amount. Explanation: A DEFINE LOGVOLUME command
attempts to add more recovery log volumes than the
Explanation: A REDUCE DB command has been
server can manage.
entered, but the database does not have enough free
space to reduce by the amount specified. System action: The server does not process the
command.
ANR2444E Command: A recovery log define, delete,
extend, or reduce operation is already in
ANR2439E Command: Unable to vary database
progress.
volume volume name offline - mirrored
copies not synchronized. Explanation: The specified command has been entered
while a command that is modifying the recovery log is
Explanation: A VARY OFFLINE command has been
already active.
entered, but mirrors of the volume to be varied are not
up to date. System action: The server does not process the
command.
command. User response: Wait for other activity to end, and
reissue the command.
database volumes have been synchronized).
ANR2445E Command: Insufficient space on other
recovery log volumes to delete volume
ANR2440E Command: Unable to vary database
volume name.
volume volume name offline - only copy.
Explanation: A DELETE LOGVOLUME command has
been entered, but the data on the volume to be deleted
entered, but the database volume has no mirrors and
cannot be copied to other volumes due to insufficient
therefore contains the only copy of the data on that
free space.
volume.

ANR2446E ANR2453E

ANR2450E Command: Unable to vary recovery log
command.
volume volume name offline - mirrored
User response: Make more recovery log space copies not synchronized.
available, and reissue the command.
been entered, but mirrors of the volume to be deleted
ANR2446E Command: Unable to delete recovery log are not up to date.
volume volume name - mirrored copies
not synchronized.
command.
been entered, but mirrors of the volume to be deleted
recovery log volumes have been synchronized).
are not up to date.
ANR2451E Command: Unable to vary recovery log
command.
volume volume name offline - only copy.
recovery log volumes have been synchronized).
entered, but the recovery log volume has no mirrors
and contains the only copy of the data on that volume.
ANR2447E Command: Insufficient space to extend
recovery log by requested amount.
command.
Explanation: An EXTEND LOG command has been
entered, but there is not enough allocated, unused
space available to the recovery log to add the amount
of space requested. ANR2452E Command: Maximum recovery log
capacity exceeded.
command. Explanation: Do not allocate any volume that would
cause the recovery log to exceed 13GB. A subsequent
User response: Make more recovery log space
DEFINE LOGVOLUME command for that volume
available, and reissue the command.
would fail.
ANR2448E Command: Output error encountered
command.
while attempting to extend recovery log.
Explanation: An EXTEND LOG command has been
entered, but an I/O error occurs during the command.
ANR2453E Command: Unable to reduce recovery log
- log mode must be set to NORMAL.
command.
Explanation: A REDUCE LOG command has been
User response: Reissue the command. If the problem
entered, but the recovery log mode of the server is
persists, identify and remove or repair the volume that
currently set to ROLLFORWARD. The recovery log can
caused the error.
only be reduced when the log mode is set to NORMAL
with a SET LOGMODE command.
ANR2449E Command: Insufficient recovery log space
would be available following a
command.
reduction by the requested amount.
User response: Set the log mode to NORMAL with
Explanation: A REDUCE LOG command has been
the SET LOGMODE command, reissue the REDUCE
entered, but the recovery log does not have enough free
LOG command, and set the log mode back to
space to reduce by the amount specified.
ROLLFORWARD with the SET LOGMODE command.
System action: The server does not process the If you change the log mode to NORMAL, you can only
command. recover your database to the time of the last complete
database backup.
ANR2454E ANR2461E
ANR2454E Command: Unable to reduce database - ANR2458E Command: Restore of primary storage
LOGMODE must be set to NORMAL. pool primary pool name (or volumes in
that storage pool) already in progress.
Explanation: A REDUCE DB command has been
entered, but the recovery log mode of the server is Explanation: The command shown cannot be
currently set to ROLLFORWARD. The database can processed because a restore operation involving the
only be reduced when log mode is set to NORMAL indicated storage pool is already in progress. Either a
with the SET LOGMODE command. RESTORE STGPOOL command is in progress for the
indicated storage pool or a RESTORE VOLUME
command is in progress for volumes that belong to the
command.
indicated storage pool.
User response: Set the log mode to NORMAL with
the SET LOGMODE command, reissue the REDUCE
command.
DB command, and reset the log mode to
ROLLFORWARD with the SET LOGMODE command. User response: Reissue the command after the current
If you change the log mode to NORMAL, you can only restore operation ends.
recover your database to the time of the last complete
database backup.
ANR2459E Command: Volume volume name cannot be
updated - a restore operation involving
ANR2455E Command: Unable to access associated that volume is in progress.
Explanation: The indicated volume has an access
to "destroyed".
mode of destroyed. Either a RESTORE STGPOOL
Explanation: The specified command would require command or a RESTORE VOLUME command is in
access to the volume whose name is displayed (because progress to restore the contents of the indicated
data from the volume specified in the command spans volume.
accessed because its status is destroyed.
command.
User response: If necessary, cancel the restore
command.
processing and update the volume.
ANR2460E Command: Server could not write
sequential volume history information
ANR2456E Command: Unable to access associated to File name.
Explanation: The BACKUP VOLHISTORY command
to "offsite".
Explanation: The command shown would require cannot write to the file name specified.
data from the volume specified in the command spans
command.
accessed because its status is offsite. User response: Make sure that the server has proper
authority to write to the file indicated and that
sufficient space is available in the file system for the
command.
file. On MVS, make sure that the data set has been
User response: If necessary, reset the status of the allocated and that the server has authority to write to
volume and reissue the command. the data set.
ANR2457E Command: Backup of primary storage ANR2461E Command: An internal error was
pool primary pool name to copy storage encountered in writing sequential
pool copy pool name already in progress. volume history information to file name.
Explanation: The command shown specifies a backup Explanation: The BACKUP VOLHISTORY command
operation that is already in progress. does not complete successfully because the server
command.
User response: Reissue the command after the current
backup operation ends. User response: Examine error messages on the server

ANR2462I ANR2468E
console that may have been displayed prior to this Explanation: The BACKUP VOLHISTORY command
message and correct any problems, if possible. Make does not complete successfully because the server
sure that the server has proper authority to write to the cannot write to one or more of the defined volume
file indicated and that sufficient space is available in history files.
the file system for the file. On MVS, make sure that the
data set has been allocated and that the server has
command.
authority to write to the data set.
User response: Examine error messages on the server
ANR2462I Command: Server sequential volume
history information was written to file
name.
Explanation: This message is displayed in response to the file system for the file. On MVS, make sure that the
the BACKUP VOLHISTORY command and indicates data set has been allocated and that the server has
that sequential volume history information was authority to write to the data set.
successfully written to the file name indicated.
System action: The server records sequential volume ANR2466E Command: An internal server error was
history information to the file name specified. encountered in writing sequential
volume history information to one or
more of the defined volume history
files.
ANR2463I Command: Server sequential volume
Explanation: The BACKUP VOLHISTORY command
history information was written to all
configured history files.
cannot write to one or more of the defined volume
Explanation: This message is displayed in response to history files.
the BACKUP VOLHISTORY command and indicates
that sequential volume history information was
command.
successfully written to all files that were specified in
the server options file. User response: Examine error messages on the server
System action: The server records sequential volume
message and correct any problems, if possible. Contact
history information to the configured files.
your service representative if you are unable to resolve
User response: None. the problem.
ANR2464I Command: Volume history files have ANR2467I Command: number of entries deleted
NOT been defined for automatic history sequential volume history entries were
recording - specify a file name for successfully deleted.
recording history information.
Explanation: The DELETE VOLHISTORY command
Explanation: This message is displayed in response to successfully deleted the number of entries specified.
the BACKUP VOLHISTORY. It indicates that sequential
volume history information cannot automatically be
written because no files were defined in the server User response: None.
options file for recording this information.
System action: The sequential volume history ANR2468E Command: An internal server error was
information is not written. Server operation continues. encountered while deleting server
sequential volume history information.
User response: Reissue the BACKUP VOLHISTORY
command and specify the name of a file for recording Explanation: The DELETE VOLHISTORY command
sequential volume history information. If desired, you fails because an internal server error has been
may configure files that should be automatically encountered.
updated with the VOLUMEHISTORY parameter and
System action: The DELETE VOLHISTORY command
restart the server.
fails, and server operation continues.
User response: Examine the messages in the activity
ANR2465E Command: An I/O error was encountered
log or server console that were displayed prior to the
in writing sequential volume history
error to see if the error can be resolved. Contact your
information to one or more of the
service representative if this error cannot be resolved.
defined volume history files.
ANR2469E ANR2477I
ANR2469E Command: Invalid volume history type: ANR2474E Command: Input volume names must be
history type. specified with the VOLumenames=
parameter.
Explanation: The command failed because an invalid
sequential volume history type was specified for the Explanation: The command failed because input
TYPE= parameter. volume names were not specified with the
VOLumenames parameter.
System action: The command fails, and server
operation continues. System action: The command fails.
User response: Refer to the Administrators Reference User response: On some platforms, or with certain
for an explanation of the valid types for this command. device classes, the server cannot prompt to mount
Reissue the command and specify a valid type value. input removable media volumes, so the names of the
required volumes must be specified in the command.
Reissue the command specifying the name(s) of
ANR2470I Message output being re-directed to file
volumes that should be mounted for input.
file name.
Explanation: The message output is being redirected
ANR2475E Command: File file name could not be
to the specified file instead of being displayed at the
opened.
console.
Explanation: The DSMSERV command could not be
completed successfully because the file specified (to
User response: None. contain the list of volumes to be used) cannot be
opened.
ANR2471E Message output re-direction to file file System action: The DSMSERV command fails.
name failed - unable to open file.
User response: Examine the file name that was
Explanation: An error occurs while trying to open the specified in the DSMSERV command. Correct the
file. The message output will not be redirected to the specification, if necessary, so that it specifies the name
specified file. of a file that exists and is accessible by the server
program. Reissue the DSMSERV command if this can
System action: None. be corrected. Contact your service representative if this
User response: Determine the cause of the file open error cannot be resolved.
failure and take corrective action.
ANR2476I License storage auditing is disabled, no
ANR2472E Command: Invalid volume specified: output available.
volume name. Explanation: The license storage occupancy function is
Explanation: The command failed because the currently disabled.
sequential history volume specified is not a DB DUMP, System action: None.
DB BACKUP, or EXPORT volume.
User response: To obtain storage occupancy results,
System action: The command fails, and server remove the NOAUDITSTORAGE or AUDITSTORAGE
operation continues. NO option from the server options file, then restart the
User response: Reissue the command and specify a server and issue the AUDIT LICENSES command.
valid volume name.
ANR2477I License storage auditing is disabled,
ANR2473I Command for volume volume name storage values may be outdated and
completed. should be ignored.
Explanation: The command completed and the Explanation: The license storage occupancy function is
volume history file has been updated. currently disabled.
System action: The server records sequential volume System action: None.
history information. User response: To obtain storage occupancy results,
User response: None. remove the NOAUDITSTORAGE or AUDITSTORAGE
NO option from the server options file, then restart the
server and issue the AUDIT LICENSES command.

ANR2478E ANR2487E
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 ANR2504I

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

ANR2505I ANR2513I
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
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.
ANR2514E ANR2523I
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.
Explanation: In response to the DEFINE
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.
Explanation: The specified command has been issued
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 ANR2534I

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 ANR2543E
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.

ANR2544E ANR2551I
Virtual file space and the associated file space

ANR2544E Unable to open the centera device at hla
definition, if one exists.
hla.
System action: NAS Backup processing for the
Explanation: The server cannot start communication
command continues.
with the device at the specified HLA.
User response: None; however, users should make
System action: The transaction needing this device
note of the original Virtual file space filespace name and
fails.
the new new filespace name so that they know where the
User response: Verify that the hla specified in the backup data for this Virtual file space is located. Note,
device class is correct, verify that the centera device is the RENAME FILESPACE command may be used to
operational. rename the Virtual file space to a more appropriate
name.
ANR2545E The version of the centera library,
version, is not compatible with the ANR2549E Command: Invalid virtual file space
server. name. A virtual file space mapping
name must have a forward slash as the
Explanation: The centera library must be at least
first character.
version 2 to be able to be compatible with the server.
System action: The transaction fails.
entered with a virtual file space name that is does not
User response: Contact your service representative. have a forward slash as the first character.
ANR2546E The centera device is not capable of command.
performing the required operation,
version.
virtual file space name.
Explanation: The centera device must be capable of
reading, writing and deleting objects. The device is not
ANR2550W command name: Administrative schedule
capable of performing at least one of these operations.
schedule name does not have valid
System action: The transaction fails. activation information.
User response: Contact your service representative. Explanation: This message is displayed during a
database audit and indicates that the 'ACTIVE=YES or
NO' information is not recorded correctly for an
ANR2547E A Centera device (devclass) reported error administrative schedule in the server database.
"message,error" during command Centera
command. System action: Server database audit operation
continues.
Explanation: The Centera device reported an error
while performing the specified command. User response: Execute the AUDITDB operation
specifying FIX=YES so that the activation information
System action: The operation fails. can be corrected.
User response: Verify that the IP addresses specified
in the device class associated with the storage pool are ANR2551I command name: Administrative schedule
correct. Contact your service representative if the schedule name does not have valid
problem persists. activation information - activation
information will be deleted.
ANR2548I NAS command: Renaming file space Explanation: This message is displayed during a
filespace name for node node name to file database audit and indicates that the 'ACTIVE=YES or
space new filespace name. NO' information is not recorded correctly for an
Explanation: The NAS Backup process detected a administrative schedule in the server database. The
name conflict between the Virtual file space filespace audit operation corrects this discrepancy by removing
name and a file space on the NAS device associated the invalid activation information.
with the node node name. The Virtual file space is System action: Server database audit operation
renamed to the new filespace name. During a NAS continues.
backup process, if the object to be backed up is a
Virtual file space, TSM will verify that this name does User response: The named administrative schedule
not also exist as a file space on the NAS device. If a will now appear to be inactive in the server database
name conflict exists, TSM will rename the existing (as if ACTIVE=NO was specified). If you want this
schedule to be active, execute the UPDATE SCHEDULE
ANR2552I ANR2559W
command with the ACTIVE=YES parameter to activate server to at least TSM Version 5 Release 3.
the schedule when the server is restarted.
ANR2557W The managed server server name is not
ANR2552I Server now enabled for session type capable of using the enhanced style
access. administrative schedule schedule name.
The administrative schedule will not be
Explanation: The server has been made available for
propagated to this server.
use by the specified session types with the ENABLE
command. Explanation: The managed server server name is
subscribed to an administrative schedule that uses
enhanced style syntax. The managed server is not
User response: None. capable of using an enhanced style schedule. Only TSM
servers that are at least Version 5 Release 3 are capable
of using enhanced style schedules.
ANR2553I Server now disabled for session type
access. System action: Server operation continues. The
administrative schedule will not be propagated to the
Explanation: The server has been made unavailable managed server.
for use by the specified session types with the
DISABLE command. User response: Consider upgrading the managed
server to at least TSM Version 5 Release 3.
User response: None. ANR2558W command: One or more managed servers
that subscribe to domain domain name
ANR2554I Format lfvolume process process id ended which contains client schedule schedule
for storage pool pool name, number of name are not capable of using an
volumes requested volumes requested, enhanced style schedule.
number of volumes formatted volumes Explanation: The client schedule schedule name uses
formatted. enhanced style schedule syntax. The schedule is in a
Explanation: The FORMAT LFVOLUME process for domain which is a managed object and one or more of
the storage pool shown has ended. The number of the managed servers that subscribe to it are not capable
volumes requested to be formatted, and the number of of using an enhanced style schedule. Only TSM servers
volumes actually formatted are displayed. that are at least Version 5 Release 3 are capable of using
enhanced style schedules. During configuration refresh
System action: None. processing, the domain will not be propagated to
User response: If the number of volumes formatted is managed servers that are not capable of using it.
less than the number of volumes requested to be System action: Server operation continues.
formatted, check the activity log for messages
indicating the reason for the difference. Possible User response: Consider upgrading managed servers
reasons include the process was canceled, no more to at least TSM Version 5 Release 3.
scratch volumes are allowed in the storage pool, or an
error occurred processing a scratch volume. ANR2559W command: One or more managed servers
that subscribe to administrative
ANR2556W The managed server server name is not schedule schedule name are not capable of
capable of using enhanced style client using an enhanced style schedule.
schedule schedule name in domain domain Explanation: The administrative schedule schedule
name. The domain will not be name uses enhanced style schedule syntax. The
propagated to this server. schedule is a managed object and one or more of the
Explanation: The managed server server name is managed servers that subscribe to it are not capable of
subscribed to domain domain name that contains client using an enhanced style schedule. Only TSM servers
schedule schedule name that uses enhanced style syntax. that are at least Version 5 Release 3 are capable of using
The managed server is not capable of using an enhanced style schedules. During configuration refresh
enhanced style schedule. Only TSM servers that are at processing, The schedule will not be propagated to
least Version 5 Release 3 are capable of using enhanced managed servers that are not capable of using it.
style schedules. System action: Server operation continues.
System action: Server operation continues. The User response: Consider upgrading managed servers
domain will not be propagated to the managed server. to at least TSM Version 5 Release 3.
User response: Consider upgrading the managed

ANR2560I ANR2569E
ANR2560I Schedule manager started. ANR2566E An error occurred while deleting

immediate client action schedules.
Explanation: The schedule manager is started when
the server is initialized. The schedule manager Explanation: Processing did not complete for deleting
maintains entries of scheduled operations. schedules that were generated by the DEFINE
CLIENTACTION command.
User response: Check the activity log for other
messages that might relate to this failure. Correct any
ANR2561I Schedule prompter contacting node name
memory or space problems.
(session session number) to start a
scheduled operation.
ANR2567W Schedule prompter skipped contact
Explanation: The schedule prompter contacts the
attempt with node name to start a
client scheduler for node node name because a
scheduled operation.
scheduled operation should be started for that node.
Explanation: The schedule prompter skipped the
contact attempt with the client scheduler for node node
User response: None. name because the start-up window has passed for that
node, or the node was locked.
ANR2562I Automatic event record deletion started. System action: Server operation continues.
Explanation: A process has been started to delete User response: Check the length of the schedule
event records for which the retention period has start-up window to see if it needs to be increased.
elapsed. Check the activity log for ANR2716E messages. These
messages are associated with failures to contact a client
System action: Server operation continues. scheduler. If there are an excessive number of these
User response: None. messages the schedule window could have elapsed
waiting for TCP/IP timeouts from these failed
attempts. Also, check to see if the client node is locked.
ANR2563I Removing event records dated prior to The contact attempt would be skipped for a locked
date time. node.
Explanation: Events that were scheduled to start prior
to date time are automatically deleted unless their ANR2568E Request for node node to start schedule
startup window has not yet elapsed. schedule at startTime is denied. Current
System action: Server operation continues. time is now.
User response: None. Explanation: The client scheduler attempted to start

the specified instance of a schedule for a node. The
request was denied because that instance is still in the
ANR2564I Automatic event record deletion ended - future.
record count records deleted.
System action: Server operation continues. The node
Explanation: The event deletion process has ended. A does not start the schedule.
total of record count event records have been deleted
from the database. User response: Check the client schedule and error
logs for problems with the network or the preschedule
System action: Server operation continues. command. Also, you may need to upgrade the client.
ANR2569E Request by node node to report results
ANR2565I schedules schedules for immediate client (result, code code) for schedule schedule at
actions have been deleted. startTime is denied. Current time is now.
Explanation: A total of schedules that were generated Explanation: The client scheduler attempted to report
by the DEFINE CLIENTACTION command have the results of executing the specified schedule.
expired and been deleted from the database. However, the schedule occurs in the future. The results
will not be saved.
System action: Server operation continues. The results
User response: None. will not be saved.
User response: Check the client schedule and error
ANR2570W ANR2575W
logs for problems with the network or the preschedule window for the scheduled event has elapsed.
command. Also, you may need to upgrade the client.
User response: To change the total number of
sessions, alter the MAXSESSIONS parameter in the
ANR2570W A scheduled session has been denied. server options file and then restart the server. The
The schedule manager is not active. percentage of sessions that are available for scheduled
operations can be increased by using the SET
Explanation: The client scheduler attempts to connect
MAXSCHEDSESSIONS command.
with the server, but it is denied a session because the
schedule manager is not active.
ANR2573W Sufficient memory is not available for
System action: Server operation continues, but central
the central scheduler - will retry in
scheduling is not operational.
number of seconds seconds.
User response: Issue the QUERY OPTION command
Explanation: The server suspends central scheduler
to determine if the option DISABLESCHEDS YES has
processing because sufficient server memory is not
been specified in the server options file. If so,
available.
scheduling can be enabled by updating the server
options file with DISABLESCHEDS NO and restarting System action: Server operation continues; the
the server. If DISABLESCHEDS YES was not specfied scheduler operation will be retried after the specified
in the server options file, determine the source of the delay.
error by examining the QUERY ACTLOG command to
view the activity log and search for messages. After the
error has been resolved, restart the server to restore
application.
central scheduler operations. If the error cannot be
isolated and resolved, contact your service
representative. ANR2574W The central scheduler has insufficient
recovery log space. The current
transaction will be tried again in number
ANR2571W Scheduled session from node node name
of seconds seconds.
(platform name) has been denied,
scheduled sessions are not currently Explanation: If a log runs out of space, the current
available. transaction is rolled back. The server issues an error
Explanation: The client scheduler for node node name
attempts to connect with the server, but is denied a
session. All sessions that have been allocated for System action: The server halts.
scheduled operations are already in use.
System action: Server operation continues. the recovery log space is insufficient, monitor the
User response: Issue the QUERY OPTION command
to determine if the option DISABLESCHEDS YES has
been specified in the server options file. If so,
the archive log directory. If the archive log space is not
scheduling can be enabled by updating the server
full and the active log space is full or nearly full,
options file with DISABLESCHEDS NO and restarting
the server. If DISABLESCHEDS YES was not specfied
dsmserv.opt file. Set the value of the ACTIVELOGSIZE
in the server options file, change the total number of
option to the new maximum size of the active log.
sessions by altering the MAXSESSIONS parameter in
the server options file and then restarting the server.
The percentage of sessions that are available for ANR2575W The central scheduler has insufficient
scheduled operations can be increased by using the SET database space. The current transaction
MAXSCHEDSESSIONS command. will be tried again in number of seconds
seconds.
ANR2572W Schedule prompter session to node node Explanation: The server suspends central scheduler
name has been denied, scheduled processing because of insufficient database space.
sessions are not currently available.
System action: Server operation continues; the
Explanation: The server attempts to prompt the client scheduler operation will be tried again after the
scheduler for node node name, but all sessions that have specified delay.
been allocated for scheduled operations are already in
use. User response: To increase the amount of database
System action: The server continues to attempt DBSPACE command. Add one or more directories to
contact with the client scheduler until the startup the database.

ANR2576W ANR2583E
ANR2576W An attempt was made to update an ANR2580E Schedule schedule name in domain domain
event record for a scheduled operation name for node node name failed.
which has already been executed for
node node name.
server finds that a scheduled start window has elapsed
Explanation: The server cannot update the event for a client schedule and the client is not currently
record for the specified client node. The existing record running the schedule.
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 for the failure. Ensure that the
occurred. client scheduler is started.
existing event record is not modified. No further ANR2581W Schedule schedule name of an
processing is performed for this scheduled operation. administrative command has missed its
scheduled start up window.
User response: Contact the user for this client node,
and make sure that only one client scheduler is Explanation: This message is displayed when the
running. scheduled startup window for this schedule has passed
and the schedule has not begun.
ANR2577I Schedule schedule name defined. System action: Server operation continues. The
scheduled operation is not processed by the server.
the DEFINE SCHEDULE command. The schedule User response: Ensure that the duration and period
named schedule name in the server database. specified in the schedule are long enough to allow the
schedule to start. Refer to Administrators Guide and
Administrators Reference for more information on setting
User response: None. up scheduling operations.
ANR2578W Schedule schedule name in domain domain ANR2582E Command: Specified device class cannot
name for node node name has missed its be used with storage pools with
scheduled start up window. different reclamation types.
Explanation: This message is displayed when the Explanation: Storage pools can be defined with
scheduled startup window for this schedule has passed RECLAMATIONTYPE=THRESHOLD or
and the schedule has not begun. RECLAMATIONTYPE=SNAPLOCK. A device class can
only be used with either
RECLAMATIONTYPE=THRESHOLD or
scheduled operation is not processed by the server.
RECLAMATIONTYPE=SNAPLOCK storage pools. An
User response: Ensure that a scheduled session for attempt was made to define a storage pool with one
node node name has been initiated from the client to the type of reclamation type with a device class that is
server. Refer to Administrators Guide and Administrators already associated with another storage pool of the
Reference for more information on setting up scheduling other reclamation type.
operations.
ANR2579E Schedule schedule name in domain domain
another device class that is referenced by storage pools
name for node node name failed (return
with the same reclamation type as your new storage
code return code).
pool. You may need to define another device class.
Explanation: This message is displayed when a client
reports failure in executing a scheduled action. The
return code reported by the client is displayed.
is not a LAN-free storage pool.
User response: Examine the node's schedule log to name of a storage pool which is not a LAN-free pool.
determine the cause for the failure. The command syntax requires that a LAN-free storage
poolname be specified.
command.
ANR2584E ANR2589E
User response: Reissue the command with a valid multiple servers, it is recommended that all of the
LAN-free storage pool name. servers have unique names.
System action: Tivoli Storage Manager prompts the
ANR2584E Command: An email address exceeds user to continue.
User response: Enter 'Y' to change the server name.
Explanation: A REGISTER NODE or REGISTER Enter 'N' if you do not want to change the server name.
ADMIN command has been entered that specifies a list
of email addresses, and one of those addresses is too
ANR2587W TSM encountered a zero verb on
long. The maximum valid length for a single email
backupset volume Volume and skipped
address is shown in the command.
to the next volume.
Explanation: TSM detected the problem described in
command.
APAR PK12572 . The server options file contains
User response: Reissue the command with a shorter SKIPONZEROVERBBACKUPSET ON. TSM verified
email address. there was no further data on the volume, and skipped
to the next volume.
ANR2585E Command: An email address contains System action: Processing continues.
invalid syntax.
User response: If the backupset volume was written
Explanation: A server command has been entered that before TSM 5.2.7, or 5.3.3 was put on the system and
specifies an invalid email address. Email addresses meets the PK12572 criteria, no action is required. If not,
must be in the format "name@domain", where the the volume has encountered a read error, and should
name must be between 1 and 64 characters long, and read again on a server without the
the domain must be between 1 and 255 characters long. SKIPONZEROVERBBACKUPSET ON option to get the
correct error messages for problem determination.
command.
ANR2588E Command: Storage pool "StgPool" cannot
User response: Reissue the command with a correct
have CACHE set to YES with a non zero
email address.
SHRED attribute.
Explanation: Storage pools can be defined or updated
ANR2586W Setting the server name to serverName
with a non zero SHRED attribute only if the storage
can adversely affect or stop operations
pool CACHE attribute is NO. Existing storage pools
that depend on communcations such as
with CACHE attribute of YES cannot be updated with
for the following purposes:
a non zero SHRED attribute. Likewise, existing storage
administration from the Administration
pools with a non zero SHRED attribute cannot be
Center, client operations from
updated with CACHE = YES. Existing storage pools
backup-archive clients, library sharing
with CACHE set to YES cannot be updated with a non
with the library manager or library
zero SHRED attribute. New storage pools cannot be
clients, or other server to server
define nor can existing storage pools be modified with
operations such as virtual volumes,
CACHE set to YES and a non zero SHRED value.
event logging, or enterprise
configuration. See the administrator's System action: The command fails.
guide for more information about these
components and the impact of changing
SHRED value of zero or CACHE = NO.
the server name.
Explanation: The name that the server displays and
ANR2589E Backupset backup set name for node node
communicates with has been set to the value indicated
name (data type data type) is in use and
with the SET SERVERNAME command.
cannot be deleted.
Communication with the Tivoli Storage Manager server
is based on the name assigned to the server. If this is a Explanation: The server attempted to delete the
source server for a virtual volume operation, changing backup set, but the operation could not be completed,
this value can impact the ability of the source server to because the backup set was in use by another process.
access and manage the data it has stored on the
corresponding target server. Windows clients use the System action: The server does not process the
server name to identify which passwords belong to command.
which servers. Changing the server name after the User response: Reissue the command at a later time.
clients are connected forces the clients to re-enter the
passwords. On a network where clients connect to

ANR2590E ANR2597W
communication with the LDAP server specified in the

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

ANR2608E ANR2617E

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.
ANR2618E ANR2627E
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.
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.
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 ANR2637E
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 Tivoli Storage Manager instance,
ANR2632E Command: Invalid begin time - date. does not have the authority to create files in one or
Explanation: The specified command has been issued more of 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 Tivoli
command is not processed. Storage Manager 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 Tivoli
Storage Manager instance.
User response: Issue the command with a valid end
date.
ANR2638W ANR2648E
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 TSM ANR2643E Command: Invalid schedule query period
server database. Are you sure you want - value.
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.
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 ANR2656E
ANR2649E Command: Schedule schedule name is not ANR2653W Command: Node node name cannot be
defined. processed because it is not registered 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. Either the node is not registered or
it is not assigned to the required domain.
User response: Issue the command with a schedule
System action: The indicated node is not processed,
that has already been defined.
but other nodes may be processed if specified by this
command.
ANR2650E Command: Schedule schedule name is
User response: If the node name was entered
already defined.
incorrectly, reissue the command with the correct node
Explanation: The specified command has been issued name.
with a schedule name that has already been defined.
System action: Server operation continues, but the ANR2654E Command: The NODES parameter cannot
command is not processed. be used when querying administrative
schedules.
User response: Issue the command with a schedule
name that has not already been defined. Explanation: A QUERY SCHEDULE command has
been issued with TYPE=ADMINISTRATIVE and the
NODES parameter both specified. The NODES
ANR2651E Command: Invalid combination of one or parameter cannot be specified when querying
more of the following parameters: cmd, administrative schedules.
type, action, objects, options.
Explanation: The specified command has been issued command is not processed.
with an invalid combination of the CMD, ACTION,
OBJECTS, and OPTIONS parameters. This message is User response: Issue the command without the
displayed when the CMD parameter is specified and NODES parameter.
TYPE=CLIENT is not specified, or when
TYPE=ADMIN is specified, and one or more of the
ANR2655E Command: Invalid client action schedule
following is specified: ACTION, OBJECTS, or
duration - days.
OPTIONS.
with an invalid number of days. Valid values are 1 to
9999 inclusive. days specifies the length of time during
User response: Issue the command with a valid which a schedule defined by the DEFine CLIENTAction
combination of parameters. command must be executed by an associated node.
After that, the schedule will be deleted from the
database.
ANR2652E Command: Invalid combination of one or
more of the following parameters: System action: Server operation continues, but the
active, cmd, type. command is not processed.
Explanation: The specified command has been issued User response: Reissue the command with a valid
with an invalid combination of the TYPE, CMD, or number of days.
ACTIVE parameters. This message is displayed when
TYPE=CLIENT is specified and one or more of the
ANR2656E Command: Invalid schedule style
following is specified: ACTIVE, CMD.
schedStyle.
with an invalid schedule style.
combination of parameters.
schedule style.
ANR2657E ANR2664E

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.

ANR2665W ANR2671E
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
is used during import.
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 &arg1;percent.
server command SET DEDUPVERIFICATIONLEVEL is
issued. Setting the deduplication-verification level helps
ANR2672E ANR2678E
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.
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
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 TSM server database. This occurred during the
value, if necessary. processing of a 'DSMSERV FORMAT' command.
System action: Server format processing terminates.
SCHEDSTYLE parameter in exported User response: Review error messages to determine
data for administrative schedule schedule the cause of the failure and retry the 'DSMSERV
name. FORMAT' once the issue has been resolved.


ANR2679E ANR2688E
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.
ANR2689W ANR2696E

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: All of the nodes provided are
invalid. ANR2696E Export command: Invalid value for
SUBACTION parameter detected while
specified command, no valid node was found.
System action: The server ends the command. value is used during import.
User response: Verify that the nodes specified are Explanation: During processing of command export
correct and all are registered. Then, reissue the command, an invalid value is encountered for the
command. ACTION parameter for schedule schedule name in
domain domain name.
ANR2692E Command: Invalid subaction - action. System action: Export processing continues, but the
exported data will contain an unknown SUBACTION
Explanation: The specified command has been issued value for this schedule. If this data is imported, the
with an invalid subaction. default or existing SUBACTION value is used.
System action: Server operation continues, but the User response: Update the SUBACTION value for this
command is not processed. schedule and restart the export command. Alternatively,
User response: Issue the command and specify a valid use the export data with the unknown value, and check
subaction. and update the SUBACTION value after import
processing has been performed.

ANR2697E ANR2707E
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
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, 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.
name was not updated.
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: An authorized administrator can use
System action: Server operation continues, but the the DEFINE LOGVOLUME command to add volumes
central scheduler is not operational. for use by the log and can issue the EXTEND LOG
ANR2708E ANR2716E

ANR2714E Node node1 trying to report scheduled
volumes are used.
operation results for node node2 -
session rejected.
ANR2708E Out of server database space in central
Explanation: The client scheduler for node node1 has
scheduler.
attempted to report the results of a scheduled operation
Explanation: The server ends a database update using another node name, node2.
transaction for the central scheduler because sufficient
database space is not available on the server.
results that were sent from node node1 are not be stored
System action: Server operation continues, but the in the servers database.
database update fails.
User response: Try restarting the client scheduler for
User response: An authorized administrator can use node node1. If the problem persists, contact your service
the DEFINE DBVOLUME command to add volumes representative to resolve the client program error.
for use by the database and can use the EXTEND DB
ANR2715E Client node node id unable to register
valid address for server prompting: type
address type (high address low address).
ANR2709E Schedule manager : Unable to start
Explanation: The client scheduler for node node id has
event record deletion.
attempted to register an invalid address for
Explanation: Event record deletion cannot be started server-prompted central scheduling. The address was
because sufficient memory is not available. type address type with high-level field high address and
low-level field low address. The only valid address type
System action: Server operation continues, but event is 1.
records are not automatically deleted after their
retention period has elapsed. System action: Server operation continues, but the
node node id will not be prompted to perform
User response: See the documentation for the scheduled operations.
application. User response: Verify that the address type and
address are correct for this client. The only valid
address type is 1 (for TCP/IP). Make sure the client
ANR2712E Node node1 requested scheduling scheduler is not using an invalid address obtained from
information for node node2 - session the clients options file or from the command line when
rejected. the client scheduler was started.
Explanation: A request for pending scheduled
operations has been sent from the client scheduler for ANR2716E Schedule prompter was not able to
node node1. However, the request is for scheduling contact client node name using type
information concerning another node node2. address type (high address low address).
System action: Server operation continues, but the Explanation: The server has attempted to prompt the
client scheduler for node node1 will not be able to client scheduler for node node name because a
process pending operations. scheduled operation should be started. The server is
User response: Try restarting the client scheduler for unable to contact the client by using address type
node node1. If the problem persists, contact your service address type, with high-level field high address and
representative to resolve the client program error. low-level field low address.
System action: Server operation continues, but node
ANR2713E Node node1 trying to start scheduled node name is not prompted to start the scheduled
operation for node node2 - session operation. If operations should be started for other
rejected. nodes, the server will attempt to prompt the client
schedulers for these nodes. This error is usually caused
Explanation: The client scheduler for node node1 has by network outages or the client scheduler program not
attempted to execute a scheduled operation for another being run on the client node.
node, node2.
User response: Verify that the address type and
System action: Server operation continues, but the address are correct for this client. The only valid
scheduled operation is not processed. address type is 1 (for TCP/IP). Make sure that the
User response: Try restarting the client scheduler for client scheduler is not using an invalid address,
node node1. If the problem persists, contact your service obtained at the time the client scheduler was started,
representative to resolve client program error. from either the clients options file or from the
command line. Verify that the client scheduler for node

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

for ACTION=DEPLOY. User response: None.
System action: Server operations will continue, but
the command is not processed. ANR2725I The server is disabled for sessions with
User response: Reissue the command with valid server server name
ACTION=DEPLOY parameters. Explanation: The server cannot initiate sessions to the
named server.
ANR2720E Command: Node node name is currently System action: None.
being replicated.
that is currently being replicated to another server.
command.
ANR2726E ANR2733W
User response: Enter 'Y' to change the domain. Enter

ANR2726E Command: None of the specified nodes
'N' if you do not want to change the domain.
are configured for replication or they are
part of an active replication process.
ANR2730I Default authentication set to defaultAuth.
Explanation: The replication command did not start
because data belonging to the specified nodes was Explanation: This message is displayed in response to
being replicated, or because the nodes are not the Set DEFAULTAUTHentication command. It
configured for replication. indicates the current default AUTHENTICATION value
for the REGISTER NODE and REGISTER ADMIN
commands.
User response: Verify that the specified nodes are
correct and that they are configured for replication.
Verify that the nodes are not part of an active User response: 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 ANR2731E An invalid command was issued: issued
QUERY NODE FORMAT=DETAILED command. To command. The command prerequisite
configure nodes for replication, issue the UPDATE command must be issued first.
NODE command. After the situation has been Explanation: The specified server command was
corrected, reissue the REPLICATE NODE command. 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.
ANR2732E Unable to communicate with the
System action: The local server does not process the external LDAP directory server.
command.
Explanation: The server tried to communicate with
User response: Reissue the command at a later time, the external LDAP directory server but was unable to
or if necessary, cancel the current session and reissue do so.
the command.
ANR2728E Command: Node node name cannot be User response: Validate that the external LDAP
replicated because it is not in the SEND directory server is actively running. Also, validate that
or SYNCSEND mode. the LDAPURL option is set appropriately and refers to
a valid LDAP directory server.
Explanation: The replication mode of a specified node
is RECEIVE or SYNCRECEIVE. To replicate, the
replication mode must be SEND or SYNCSEND. ANR2733W Unable to authenticate with the external
LDAP directory server to process the
System action: The server processes the command. SET LDAPUSER command.
However the specified node is is skipped for this
operation. Explanation: The LDAPUSER value or the
LDAPPASSWORD value or both are invalid.
User response: Verify that all of the nodes to be
replicated are in SEND or SYNCSEND mode. Reissue System action: The server command continues.
the command, or, if necessary, cancel the replication User response: During the SET LDAPUSER command,
process and reissue the command. the Tivoli Storage Manager server tried to authenticate
to the external LDAP directory server. If the
ANR2729W This command will register the node to LDAPPASSWORD is not set or is invalid, the
new domain domainname. Changing the authentication fails, but the SET LDAPUSER command
domain will cause the node to be succeeds. The LDAPUSER value and the
disassociated from the schedule of LDAPPASSWORD value both must be set correctly
original domain. before the server can communicate with the external
LDAP directory server. The SET LDAPPASSWORD
Explanation: The schedule belongs to the domain. The command fails if authentication with the external
node will be disassociated from the schedule if the LDAP directory server fails with the current
node is registered to new domain. LDAPUSER and new LDAPPASSWORD.
System action: Tivoli Storage Manager prompts the You can validate the current LDAPUSER by issuing the
user to continue. QUERY STATUS command. The LDAPUSER and

ANR2734E ANR2741I
LDAPPASSWORD commands can be corrected with the

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

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

removed and the command needs to be re-issued by ANR2747W Administrator admin name was located in
the originating administrator. the database but not in the LDAP
directory server.
User response: Review the activity log for the
command processed. Explanation: An inconsistency between the LDAP
directory server and the Tivoli Storage Manager
database was discovered. An administrator in the Tivoli
Storage Manager database a does not have a
corresponding entry in the LDAP directory server.
Without an entry in the LDAP directory server, the
administrator is inaccessible until action is taken. See
the user response for recommended action.
User response: To make the administrator accessible,
you need to add the administrator to the LDAP
directory server. Issue the UPDATE ADMIN command

ANR2748W ANR2755E
with a password to create an LDAP administrator entry

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

name ( scheduled command ). SCHEDULE parameter CMD='command'
Explanation: This message is displayed when the - not eligible for scheduling.
server starts the execution of a scheduled command. Explanation: The specified command is not eligible for
The name of the schedule and the actual command scheduling.
scheduled is displayed.
System action: The DEFINE SCHEDULE or UPDATE
System action: Server operation continues, the SCHEDULE command is not processed.
scheduled command is processed.
ANR2756I ANR2764E
User response: To delete the virtual file space

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

ANR2765E ANR2772E
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 ANR2781E

ANR2773E Move data process terminated for
volume volume name - drive path or data User response: None.
mover unavailable.
Explanation: MOVE DATA processing terminated for ANR2777I Audit command: Inventory object
the indicated volume for one of the following reasons: (object.ID) is part of an incomplete
v None of the data movers with paths to the drives in group.
the library containing the source storage pool is Explanation: A database audit process found an
available. inventory object that is part of an incomplete group.
v None of the data movers with paths to the drives in
the library containing the target storage pool is System action: Audit processing continues.
available. User response: Run the audit command again with
System action: The indicated process ends. FIX=YES, so that the error can be corrected.

device class to which the source or target storage pool ANR2778I Audit command: Storage entry for an
belong. Use QUERY DEVCLASS to obtain the library inventory object (object.ID) cannot be
name that contains the source or target storage pool. found. The inventory entry will be
Then, use the QUERY DATAMOVER and QUERY deleted.
PATH commands to verify that at least one data mover Explanation: A database audit process cannot find the
has paths to the drives in the library. storage entry for the specified inventory object. Because
FIX=YES has been specified for the command, the
ANR2774E Command: Process process ID terminated - inventory entry is deleted.
data format mismatch. System action: Audit processing continues.
Explanation: During restore processing, a data format User response: None.
mismatch occurred between the storage pool being
restored and the copy storage pool.
ANR2779I Audit command: Storage entry for an
System action: The indicated restore process inventory object (object.ID) cannot be
terminates. found.
User response: Examine the previous error message to Explanation: A database audit process cannot find the
determine the name of the copy storage pool used for storage entry for the specified inventory object.
the restore. If possible, specify a copy storage pool that
has the same data format as the storage pool being System action: Audit processing continues.
restored on the restore command. User response: Run the audit command again with
FIX=YES, so that the error can be corrected.
ANR2775W Command: Process Process id encountered
an output error. File on volume volume ANR2780W Command: Updates for nodes previously
name skipped - Node node name, type file processed during this command will be
type, file space filespace name, file name rolled back.
file name, fsId filespace id.
Explanation: An error has occurred during an
Explanation: During copy or move operation, an UPDATE NODE operation. If the UPDATE NODE
output error was encountered. The indicated file was command was processing more than one node, updates
skipped. for nodes which were previously processed will be
System action: The file will not be processed. rolled back.
User response: If possible, correct the error and re-run System action: Server operation continues.
the command. User response: Correct the error and reissue the
command.
ANR2776I Audit command: Inventory object
(object.ID) is part of an incomplete ANR2781E command name: keyword value longer than
group. The inventory entry will be max length characters.
deleted.
Explanation: The directory specified for the indicated
Explanation: A database audit process found an keyword is too long. Specify a directory less than or
inventory object that is part of an incomplete group. equal to the number of characters indicated. This is a
Because FIX=YES has been specified for the command, limitation of the underlying database.
the inventory entry is deleted.

ANR2782I ANR2791E
System action: Server database format processing

ANR2787E The server failed with error code last
terminates.
error when attempt to access path name.
User response: Specify a valid value for the indicated
Explanation: The server failed to access the directory
keyword.
specified.
System action: The command stops.
ANR2782I SET DBRECOVERY completed
successfully and device class for User response: Verify the existence of that directory
automatic DB backup is set to value. and reissue the command.
Explanation: The device class requirement for
automatic database backup is set with the SET ANR2788E Database log path path name is not
DBRECOVERY command. empty.
System action: None. Explanation: When specifying a new active, archive,
or mirror log directory in the server options file or
when formatting a server, the indicated directory must
be empty to prevent and accidental overwrite of
ANR2783E FORMAT: Required keyword keyword existing data.
not specified.
System action: If a FORMAT operation was being
Explanation: A required keyword was not specified performed, the operation stops. If this was a change to
for database format processing. the server options file to specify a new log directory,
the new directory is ignored, and the existing directory
System action: Server database format processing is used.
terminates.
User response: Verify the directory that was specified.
User response: Reissue the format command with the Delete any data in that directory if the data is not
required parameters. needed, or create a new directory. Reissue the format
command.
ANR2784E FORMAT: The mirror log diretory must
not be the same as the active log ANR2789W Command: Node node name is registered,
directory. but the server cannot remove it because
Explanation: The server found an error when it is reserved.
processing the format command. Explanation: The command shown specifies a node
System action: Server stops the format. that is reserved by the server.
User response: Select a different directory for mirror System action: The server does not process the
log and reissue command. command.
ANR2785E An error occurred when trying to access
path name. ANR2790E Too many symbolic links were found
Explanation: An access denied error occurred while while traversing file path path name.
attempting to access a directory. System action: The server stops processing the
System action: The command stops. command.
User response: Verify permission for that directory is User response: Refer to your operating system's
set correctly then reissue the command. manual for the maximum number of symbolic links
allowed on a path name. Reduce the number of
symbolic links that lead to the file path, and then
ANR2786E The server was unable to find path name. reissue the command.
Explanation: The server could not find the directory
specified. ANR2791E The file or volume name path name is
System action: The command stops. too long.
User response: Verify the existence of that directory System action: The server stops processing the
and reissue the command. command.
User response: Check your operating system's limits
on files and pathss length.Reissue the command with a
shorter file or volume name.
ANR2792E ANR2803I

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

ANR2804W ANR2814I
for use by the log and can issue the EXTEND LOG
ANR2804W Insufficient memory is available for the
license manager - will retry in number of
volumes are used.
seconds seconds.
Explanation: The server suspends license manager
ANR2808E Out of server database space in license
processing because sufficient server memory is not
manager.
available.
System action: Server operation continues; the license
transaction for the license manager because sufficient
manager operation will be retried after the specified
delay.
application. User response: An authorized administrator can use
for use by the database and can use the EXTEND DB
ANR2805W Insufficient recovery log space available
for the license manager - will retry in
number of seconds seconds.
ANR2811I Audit License completed - Server is in
processing because sufficient recovery log space is not
available.
Explanation: The results from the AUDIT LICENSES
command indicate the server is in compliance with the
manager operation will be retried after the specified
terms of the current license.
delay.
available to the server, an authorized administrator can User response: None.
add log volumes using the DEFINE LOGVOLUME
command, and can extend the size of the log using the
EXTEND LOG command. 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.
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.
administrator can add database volumes using the ANR2813I Server is licensed for a capacity of
DEFINE DBVOLUME command, and can extend the capacity gigabytes and number of clients
size of the log using the EXTEND DB command. clients.
Explanation: This message is issued during server
ANR2807E Out of server log space in license startup.
manager. System action: Server operation continues.
Explanation: The server ends a database update User response: None.
transaction for the license manager because sufficient
recovery log space is not available on the server.
ANR2814I Audit command: License audit period
System action: Server operation continues, but the changed to number of days days.
User response: An authorized administrator can use the SET LICENSEAUDITPERIOD command used to
ANR2815E ANR2823I
change the interval in days between automatic license

ANR2819I Command: Licensed capacity changed to
audits.
capacity GB with number of clients clients.
Explanation: The license information has been
User response: None. changed to the indicated values with the REGISTER
LICENSE command.
ANR2815E Command: Invalid value specified for System action: None.

interval between license audits - value.
User response: To implement the changed license
Explanation: The specified command has been issued information, issue an AUDIT LICENSES command or
with an invalid value. wait until an automatic license audit occurs.

command is not processed. ANR2820I Automatic license audit started as
process process ID.
to audit the server for license compliance.
ANR2816E Command: License audit or register
operation already in progress. System action: The server checks storage utilization
and registered nodes for the server and licensed factors,
Explanation: The server is currently performing a comparing these against the values for which the server
register license or license audit. is licensed.
System action: The server does not process the User response: The administrator may query the
specified command. status of the background process using the QUERY
User response: Reissue the command after the license PROCESS command.
audit process or the register license command ends.
Only one REGISTER LICENSE command or AUDIT ANR2821E Automatic license audit could not be
LICENSE process can be running at a time. The started: diagcode.
REGISTER LICENSE command and the AUDIT
LICENSE process may not run at the same time. Explanation: The license manager cannot start an
automatic process to audit server licenses because
sufficient memory is not available. Diagnostic code
ANR2817I Command: License audit started as diagcode is issued.
process process ID.
to audit the server for license compliance. User response: See the documentation for the
System action: The server checks the existing application.
configuration for the server and compares it against the
values for which the server is licensed.
ANR2822I Cancel in progress
status of the background process by using the QUERY Explanation: The license audit operation has been
PROCESS command, or cancel the process with the cancelled and will end when resources have been freed
CANCEL PROCESS command. for the background process. This message may be
displayed in response to a QUERY PROCESS command
for an AUDIT LICENSES operation.
ANR2818I Command: Licensed capacity is capacity
GB with number of clients clients. System action: Server operation continues.
Explanation: This message displays the license User response: None.

information that existed before issuing the REGISTER
LICENSE command.
ANR2823I Have audited number of nodes nodes
Explanation: An AUDIT LICENSES operation is in
User response: None. progress. The process has audited the specified number
of nodes. This message may be displayed in response
to a QUERY PROCESS command for an AUDIT
LICENSES operation.

ANR2824I ANR2834W
ANR2824I License audit process process number ANR2829E Command: parameter - parameter is not
canceled - number of nodes nodes audited. allowed.
Explanation: A background server process to audit Explanation: The UPDATE NODE command has been
server licenses has been canceled by using the entered with a parameter that is not allowed.
CANCEL PROCESS command. The number of nodes
that have been audited before the operation ended are
reported in the message. User response: When updating the REPLMODE and
REPLSTATE parameters on a node definition, there are
restrictions that prohibit changing certain values.
Several conditions are enforced during command
User response: None. processing that prevents unintended updates. The
syntax processing is strictly enforced and in many
cases, it might be necessary to issue other commands
ANR2825I License audit process process number
prior to using UPDATE NODE. Refer to the
completed successfully - number of nodes
Administrator's Reference in the Tivoli Storage
nodes audited.
Manager Information Center for a complete description
Explanation: A background server process to audit of the command restrictions for UPDATE NODE.
server licenses has completed successfully after
auditing the specified number of nodes.
ANR2832I Command: The License Manager has not
System action: The server process is ended and server yet completed initialization - please
operation continues. retry this command later.
User response: None. Explanation: While attempting to process the specified

license command, the server detects that the licensing
component of the server had not completed
ANR2826I License audit process process number initialization. The licensing facility used on some
terminated in error - number of nodes platforms may require some time to initialize because
nodes audited. network calls are involved, and waits may occur.
Explanation: A background server process to audit System action: Server operation continues; the
server licenses encounters an error and is ended. The command is not processed.
number of nodes that have been audited before the
operation ended is reported in the message. User response: Reissue the command after waiting 10
minutes. If this message is displayed after a number of
System action: The server process is ended and server retry attempts, contact your service representative.
User response: None. ANR2833I Command: Auditing license definitions.
Explanation: The server has started to audit database
ANR2827I Server is licensed to support feature name definitions that describe licensing information.
for a quantity of licensed quantity.
System action: Server database audit operation
Explanation: This message is issued during server continues.
startup.
User response: None. ANR2834W License Audit completed - WARNING:
Server is NOT in compliance with
ANR2828I Server is licensed to support feature license terms.
name. Explanation: The results from the AUDIT LICENSES
Explanation: This message is issued during server command indicate that the server is not in compliance
startup. with the terms of the current license.
System action: Server operation continues. System action: Server operation continues, but the
REGISTER NODE command fails.
compliance. Remove nodes or purchase additional
client node connections. After these actions have been
taken, reissue the AUDIT LICENSES command to
ANR2835I ANR2853I
resynchronize the server configuration with license User response: None.

terms.
ANR2843I Server is licensed to support UNIX
ANR2835I Server is licensed for number of clients clients.
clients.
Explanation: This message is issued during server startup.
startup and in one hour increments there after.
User response: None. UNIX is a registered trademark
User response: None. in the United States and other countries, licensed
exclusively through X/Open Company Limited.
ANR2836I Command: License audit started as
process process ID. ANR2844I Server is licensed to support desktop
clients.
to audit the server for license compliance. Explanation: This message is issued during server
startup and in one hour increments there after.
System action: The server checks registered nodes for
the server and compares this against the value for System action: Server operation continues.
which the server is licensed.
status of the background process using the QUERY
ANR2847W The addition of client client node name is
PROCESS command, or cancel the process with the
beyond the client capacity that the
server is licensed to support.
Explanation: This message is issued when a new
ANR2839I Automatic license audit started as
client node is added to the server with the REGISTER
process process ID.
NODE command, or through open registration, and the
Explanation: A background process has been started actual number of nodes registered on the server
to audit the server for license compliance. exceeds the servers licensed capacity.
System action: The server checks registered nodes and System action: Server operation continues.
compares them against the value for which the server
User response: This message is issued as a reminder
is licensed.
to the administrator that the server is not operating
User response: The administrator may query the within compliance of its license. Contact your service
status of the background process by using the QUERY representative if more licenses are required for your
PROCESS command. server.
ANR2841W Server is NOT IN COMPLIANCE with ANR2852I Current license information:

license terms.
Explanation: This message is issued during a
Explanation: This message is issued periodically when REGISTER LICENSE command to display the current
the server configuration does not comply with the licensing information for the server before the new
terms for which it is licensed. license has been interpreted by the command. Messages
appearing after this message display the factors under
which the server is currently licensed.
display the current server configuration with respect to
licensed terms to discover which factors of the User response: None.
configuration do not conform to your license. Contact
your service representative to obtain more licenses, if
ANR2853I New license information:
required.
Explanation: This message is issued during a
REGISTER LICENSE command to display the updated
ANR2842I Server is licensed to support number of
licensing information for the server after the new
gigabytes gigabytes of storage.
license has been interpreted by the command. Messages
Explanation: This message is issued during server appearing after this message display the updated
startup. factors under which the server is licensed.

ANR2854I ANR2901W
User response: Check to make sure that the new User response: None.
license information includes the updates that you
intended for the REGISTER LICENSE command. If the
ANR2864I Server is licensed to support
license terms do not change, check the parameters and
Server-to-Server Virtual Volumes.
reissue the command, if you find that it was not
entered correctly. If the REGISTER LICENSE command Explanation: This message is issued during server
does not produce the desired updates in terms of startup.
licensing, contact your service representative.
ANR2854I Server is licensed for device support User response: None.

module module number.
Explanation: This message may be issued during ANR2865W The server is NOT licensed to support
server startup. Enterprise Administration functions. By
performing this action you are no longer
System action: Server operation continues. in compliance with license terms.
User response: None. Explanation: This message is issued when enterprise
administration functions are used, but the server is
NOT licensed to support the functions.
ANR2855I Server is licensed to support Tivoli
Space Manager clients. System action: Server operation continues.
Explanation: This message is issued during server User response: To bring your installation back into
startup. conformance with license terms, obtain a license for
enterprise administration functions or remove central
logging definitions. Contact your service representative
User response: None. if you have any questions or concerns with this
message.
ANR2859I Server is licensed for Secondary Server
Attachment. ANR2868E The server is NOT licensed to support
Enterprise Administration functions.
Explanation: This message may be issued during
server startup. Explanation: This message is issued when Enterprise
Administration functions are used, but the server is
NOT licensed to support the functions.
User response: Contact your service representative if
ANR2860I Server is licensed to support Tivoli
you want to obtain a license for enterprise
Disaster Recovery Manager.
administration.
startup.
ANR2900W The character string 'string' was
System action: Server operation continues. truncated during assignment.
User response: None. Explanation: Truncation occurred during assignment

of an SQL character string. For example, the expression
CAST( 'Hello' AS CHAR(2) ) will result in truncation
ANR2861I Server is licensed to support because the string 'Hello' (length 5) can not fit in the
NETWORK connections. target type CHAR(2) without loss of trailing characters.
Explanation: This message is issued during server System action: This warning can occur before or after
startup. SQL query processing, but does not terminate query
System action: Server operation continues. processing.
ANR2863I Server is licensed to support Enterprise ANR2901W The result of character string
Administration functions. concatenation was truncated.
Explanation: This message is issued during server Explanation: Truncation occurred when the
startup. concatenation of character strings resulted in a length
that exceeds the maximum character string length (250
ANR2902E ANR2912E
for data type CHAR, and 2000 for data type

ANR2907E Unexpected SQL operator token - 'token'.
VARCHAR).
Explanation: A syntax error occurred because an SQL
System action: This warning can occur before or after
operator token was found that can not legally be used
SQL query processing, but does not terminate query
at the specified position within the SQL statement.
processing.
Examples of SQL operator tokens are +, *, <, and =.
System action: The SQL query is terminated.
ANR2902E Insufficient memory was available to
process the SQL statement.
ANR2908E Unexpected SQL punctuation token -
Explanation: Sufficient memory was not available to
'token'.
complete the processing of an SQL query.
punctuation token was found that can not legally be
User response: None. used at the specified position within the SQL statement.
Examples of SQL punctuation tokens are the period,
the comma, and the parenthesis.
ANR2903E An SQL parser stack overflow occurred
while processing token 'token'. System action: The SQL query is terminated.
Explanation: The internal stack used by the SQL User response: None.
query parser has overflowed. This typically occurs
when too many column names or expressions have
ANR2909E The SQL statement is incomplete;
been specified in the SELECT clause.
additional tokens are required.
Explanation: A syntax error occurred because,
User response: None. although the syntax of the SQL query expression was
correct up to the end of the string, the parser expected
additional tokens in order to form a
ANR2904E Unexpected SQL key word token - syntactically-correct SQL statement.
'token'.
key word was found that can not legally be used at the User response: None.
specified position within the SQL statement. Examples
of SQL key words are SELECT, FROM, and WHERE.
ANR2910E Invalid SQL token - 'token'.
Explanation: An invalid SQL token was found. For
User response: None. example, the token formed by the character sequence
"::!" is not a valid SQL token.
ANR2905E Unexpected SQL identifier token - System action: The SQL query is terminated.
'token'.
identifier was found that can not legally be used at the
ANR2911E Invalid SQL numeric literal token -
specified position within the SQL statement. Examples
'token'.
of SQL identifiers are table names and column names.
Explanation: An invalid SQL numeric literal token
was found. For example, the floating point literal
User response: None. "1.456E" is not valid.
ANR2906E Unexpected SQL literal token - 'token'.
literal token was found that can not legally be used at
ANR2912E Invalid character string literal token -
the specified position within the SQL statement.
'token'.
Examples of SQL literal tokens are 'abc', 1.567, and
DATE '1/1/96'. Explanation: An invalid SQL character string literal
token was found. For example, the hexadecimal literal
X'78FG' is not valid because it contains the character
User response: None. 'G'.

ANR2913E ANR2922E

ANR2918E The SQL data type of expression
User response: None. 'expression' is data type; expecting a
Boolean expression.
ANR2913E Invalid SQL identifier token - 'token'. Explanation: An SQL expression of data type
BOOLEAN is expected.
Explanation: An invalid SQL identifier token was
found. For example, the character sequence "ABC.123" System action: The SQL query is terminated.
is not a valid identifier because the second part of the
identifier, "123", does not begin with a letter.
numeric expression.
ANR2914E SQL identifier token 'token' is too long; Explanation: An SQL expression of numeric data type
name or component exceeds 18 SMALLINT, INTEGER, DECIMAL, NUMERIC, REAL,
characters. FLOAT, or DOUBLE_PRECISION is expected.
Explanation: An SQL identifier token was found that System action: The SQL query is terminated.
exceeds the maximum length of 18 characters per
component.
numeric or interval expression.
ANR2915E The SQL token beginning with 'token' is Explanation: An SQL expression of numeric data type
missing an ending delimiter. (SMALLINT, INTEGER, DECIMAL, NUMERIC, REAL,
FLOAT, DOUBLE) or of interval data type (INTERVAL)
Explanation: An SQL token was found that is missing is expected.
its ending delimiter. For example, each of the tokens
'abc, "abc, and X'abc is missing its ending delimiter. System action: The SQL query is terminated.
System action: The SQL query is terminated. User response: None.

'expression' is data type; expecting a
ANR2916E The SQL data types data type and data character string expression.
type are incompatible for operator
'operator'. Explanation: An SQL expression of character string
type CHAR or VARCHAR is expected.
Explanation: The data types of the operands are not
compatible when used with the specified operator. For System action: The SQL query is terminated.
example, the expression 3 + 'abc' is not valid because
the operand data types INTEGER and CHAR(3) are not
compatible for the addition operator "+".
'expression' is data type; expecting a date,
User response: None. timestamp, character string date,
character string timestamp, or interval
expression.
'expression' is data type; expecting an Explanation: An SQL expression was expected of one
integer expression. of the types DATE, TIMESTAMP, CHAR, VARCHAR,
or INTERVAL as the operand to the EXTRACT
Explanation: An SQL expression of data type function. In the case of CHAR or VARCHAR, the
SMALLINT, INTEGER, or DECIMAL with scale zero is expression must be a valid character string
expected. representation of a date or a timestamp.
System action: The SQL query is terminated. System action: The SQL query is terminated.
ANR2923E ANR2931E
type INTERVAL YEAR, INTERVAL MONTH,

INTERVAL DAY, INTERVAL HOUR, INTERVAL
'expression' is data type; expecting a time,
MINUTE, or INTERVAL SECOND, all of which contain
timestamp, character string time,
a single date-time field. Multi-field interval types (for
character string timestamp, or interval
example, INTERVAL DAY TO SECOND) are not
expression.
allowed.
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. ANR2928E A number can not be converted to SQL
data type INTERVAL if the interval
System action: The SQL query is terminated. contains multiple date-time fields.
User response: None. Explanation: An attempt was made to convert a
number to the data type INTERVAL, but the target
interval contains multiple date-time fields (for example,
INTERVAL DAY TO SECOND). Only the single-field
'expression' is data type; expecting a date
interval types INTERVAL YEAR, INTERVAL MONTH,
or character string date expression.
INTERVAL DAY, INTERVAL HOUR, INTERVAL
Explanation: An SQL expression was expected of one MINUTE, or INTERVAL SECOND can be specified.
of the types DATE, CHAR, or VARCHAR. In the case
of CHAR or VARCHAR, the expression must be a valid
character string representation of a date. User response: None.
ANR2929E The expression 'expression' is not an
integer constant.
Explanation: An integer constant such as 1 or -9 is
expected. For example, the DECIMAL function requires
'expression' is data type; expecting a time
that the precision and scale operands be integer
or character string time expression.
constants. A decimal constant such as 1.67 is not valid.
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 User response: None.
character string representation of a time.
System action: The SQL query is terminated. ANR2930E A subquery used in an SQL expression
must specify a single result column.
Explanation: A subquery used in an expression can
not specify multiple result columns. For example, the
expression X > (select A,B from T) is invalid because it
'expression' is data type; expecting a date,
specifies two result columns (A and B).
timestamp, character string date, or
character string timestamp expression. System action: The SQL query is terminated.
Explanation: An SQL expression was expected of one User response: None.
of the types DATE, TIMESTAMP, CHAR, or
VARCHAR. In the case of CHAR or VARCHAR, the
expression must be a valid character string ANR2931E A subquery expression may not contain
representation of a date or a timestamp. a reference to a column name that is
contained in an outer query expression.
Explanation: A subquery contains a reference to a
User response: None. column name in an outer query expression.
'expression' is data type; expecting an User response: None.
interval containing a single date-time
field.
Explanation: An SQL expression was expected of data

ANR2932E ANR2940E
ANR2932E The maximum nesting depth for ANR2937E An SQL subquery expression can not be
subquery expressions has been nested within an aggregate function.
exceeded.
Explanation: An expression containing a subquery
Explanation: Too many nested subqueries were was found nested within one of the aggregate functions
specified. COUNT, MAX, MIN, SUM, AVG, VARIANCE, or
STDDEV.
ANR2933E The WHERE clause must not contain an
aggregate function. ANR2938E The column 'column' is not allowed in
this context; it must either be named in
Explanation: The use of the aggregate functions
the GROUP BY clause or be nested
COUNT, MAX, MIN, SUM, AVG, VARIANCE, or
within an aggregate function.
STDDEV in the WHERE clause is not allowed.
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
COUNT, MAX, MIN, SUM, AVG, VARIANCE, or
STDDEV. The use of the column reference is prohibited
ANR2934E The result data type of a CASE because either 1) the GROUP BY clause has been
expression can not be determined; at specified, 2) the HAVING clause has been specified, or
least one non-null THEN or ELSE 3) at least one aggregate function is present.
expression must be specified.
Explanation: The result data type of a CASE
expression can not be determined because all of the User response: None.
THEN expressions and the ELSE expression (if present)
specifies the NULL key word.
ANR2939E The reference 'reference' contains an
System action: The SQL query is terminated. unknown SQL table name.
User response: None. Explanation: A table name in the SQL command is not
one of the base tables defined by the server's database.
The rows of the table SYSCAT.TABLES can be selected
ANR2935E The date-time field field is not present in to obtain a list of all of the valid base tables.
the expression 'expression' (data type data
type). System action: The SQL query is terminated.
Explanation: The specified date-time field (YEAR, User response: Retry the command using a table that
MONTH, DAY, HOUR, MINUTE, or SECOND) is not is defined by the Tivoli Storage Manager server
contained in the data type of the expression. database.
ANR2940E The command 'reference' contains an
User response: None. unknown SQL column name.
Explanation: A column name in the SQL command is
ANR2936E The SQL aggregate function function can not one of the base table columns defined by the
not be nested within another aggregate server's database. The rows of the table
function. SYSCAT.COLUMNS can be selected to obtain a list of
Explanation: One of the aggregate functions COUNT, all of the valid base table columns. If a two-part
MAX, MIN, SUM, AVG, VARIANCE, or STDDEV was (compound) column reference such as X.Y is specified,
found nested within another aggregate expression. then the correlation name X must be one of the active
correlation names for the query.
ANR2941E ANR2949E
ANR2941E The column reference 'column reference' ANR2946E Too many arguments are specified for
matches more than one SQL column SQL scalar function function.
name.
Explanation: Too many function arguments were
Explanation: The specified column reference is specified. For example, the expression UPPER(x,y) is
ambiguous because it matches the columns associated invalid because the UPPER function requires exactly
with multiple tables. one argument.
System action: The SQL query is terminated. System action: The SQL query is terminated.
ANR2942E The column reference 'column reference' is ANR2947E Division by zero was detected for
not allowed in this context because it is operator 'operator'.
part of an outer SQL query expression.
Explanation: An attempt to divide by the number zero
Explanation: The specified column reference is not was detected for the specified SQL operator. The most
allowed because it names a columns of some outer likely cause of the problem is that one of the values of
query expression. Such references are not allowed when a column is zero, and that column is used in the
contained within the expressions of the HAVING and denominator of a division operation. To protect against
SELECT clauses. this case the NULLIF function can be used. For
example, instead of the expression 1/X, specify
1/NULLIF(X,0), which will set the expression to null
User response: None. whenever the value if X is zero.
ANR2943E The column reference 'column reference' is
a duplicate of another SQL column
name in the same list.
ANR2948E The value 'value' can not be assigned or
Explanation: A duplicate column reference was
converted to SQL data type data type.
specified within the same GROUP BY or ORDER BY
list of columns. Explanation: A value could not assigned or converted
to a value in the specified SQL data type because either
1) the data type of the value can not be legally cast to
User response: None. the target data type (for example, data type TIME can
not be converted to data type INTEGER); 2) the
assignment of the value results in overflow in the
ANR2944E The reference 'reference' is an unknown target data type (for example, the decimal value
SQL scalar function name. 12345678.34 can not be assigned to data type
Explanation: The specified function reference is not DECIMAL(3,2) because the precision of the target type
the name of a valid scalar function. is exceeded); or 3) the syntax of a character string value
is not appropriate for the target data type (for example,
System action: The SQL query is terminated. the string 'abc' can not be converted to data type
User response: None. DATE).
ANR2945E Too few arguments are specified for User response: None.
SQL scalar function function.
Explanation: Too few function arguments were ANR2949E Arithmetic overflow occurred for SQL
specified. For example, the expression LEFT(x) is operator 'operator'.
invalid because the LEFT function requires at least two
arguments. Explanation: An arithmetic overflow occurred for the
specified operator. Examples of this include: 1) the
System action: The SQL query is terminated. application of the unary negation operator to the
User response: None. smallest INTEGER value (-2147483648) causes overflow
because the result can not be represented in 2's
complement; 2) the sum of the set of INTEGER column
values applied to the SUM aggregate function can not
be represented within the precision of INTEGER type.

ANR2950E ANR2958E
User response: None. making it ambiguous as to which value should be

returned.
ANR2950E Arithmetic or date-time overflow System action: The SQL query is terminated.
occurred for SQL operator 'operator' for
User response: Respecify the subquery (for example,
values 'value' (data type data type) and
using the WHERE clause) so that the subquery returns
'value' (data type data type).
at most one row.
Explanation: An arithmetic or date-time overflow
occurred for the specified operator. The values that
ANR2955E The SQL character string expression
caused the overflow (and their SQL data types) are
'expression' must return a single
displayed.
character.
Explanation: A single-character character string was
User response: None. expected for the ESCAPE clause of the LIKE operator,
for the trim character of the TRIM operator, or for the
pad character of the LEFT or RIGHT function. For
ANR2951E The value 'value' (data type data type) is
example, the string 'Hello' is invalid because it contains
not a valid argument for operator
multiple characters.
'operator'.
Explanation: An invalid value was specified as an
argument to an SQL operator. For example, the User response: None.
expression SQRT(-1) is not valid because the argument
to the SQRT function is negative.
ANR2956E Unable to access SQL base table 'table'.
Explanation: An error occurred when attempting to
User response: None. read rows from one of the SQL base tables. This
message is typically preceded by another error
describing the condition.
not a valid character string System action: The SQL query is terminated.
representation of an SQL date or a
timestamp for operator 'operator'.
Explanation: An invalid character string
ANR2957E An error occurred inserting a row in an
representation of a DATE or TIMESTAMP was
SQL temporary table. The server
specified. For example, the string 'abc' is neither a valid
database size may need to be increased
date nor a timestamp.
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
this error can be resolved by increasing the size of the
server database. Free space in the database is used to
not a valid character string
store temporary tables created during the execution of
representation of an SQL time or a
an SQL SELECT query.
timestamp for operator 'operator'.
Explanation: An invalid character string
representation of a TIME or TIMESTAMP was User response: None.
specified. For example, the string 'g pm' is neither a
valid time nor a timestamp.
ANR2958E SQL temporary table storage has been
System action: The SQL query is terminated. exhausted.
User response: None. Explanation: The result of an SQL query could not be
computed because temporary table storage space was
unavailable. By issuing the QUERY DB command and
ANR2954E An SQL subquery used in a scalar
viewing the Maximum Reduction parameter, you can
expression must yield a table that
determine the amount of space that is available for
contains at most one row.
temporary table storage space. If the parameter is less
Explanation: This error results when a subquery used than 4, the storage space becomes exhausted and the
in a scalar expression returns multiple rows, thereby SQL query can no longer run. Complex SQL queries
such as the ORDER BY clause, the GROUP BY clause,
ANR2959E ANR2966E
and the DISTINCT operator can cause additional one enumerated type, its type could not be resolved.
temporary table space to be required. For example, the enumerated value name YES belongs
to more than one enumerated type, and so the result
type of the expression YES = YES can not be resolved.
User response: If your database is full, increase the A list of all of the enumerated types declared by the
size of the database. If your database is fragmented server can be found in the SQL catalog table
(Where the Available space parameter is greater than 4, SYSCAT.ENUMTYPES.
but the Maximum Reduction parameter is less than 4),
you must either unload and load your database or add
avolume. User response: None.
ANR2959E SQL temporary table row is too wide. ANR2963W This SQL query may produce a very
large result table, or may require a
Explanation: A row could not be inserted into an SQL
significant amount of time to compute.
temporary table because the row is too wide. This can
occur if 1) there are too many columns in the row being Explanation: An SQL query has been posed that could
inserted, or 2) the sum of the lengths of the columns in potentially cause a very large number of rows to be
the row is too wide. Temporary tables are used when 1) returned and displayed, or may involve a large amount
the ORDER BY clause is specified; 2) the GROUP BY of processing time before the first result table row can
clause is specified; or 3) the DISTINCT operator is be generated.
specified.
System action: The SQL query is terminated. continue.
User response: Reduce the number of columns User response: Enter 'Y' to continue with SQL query
specified in the ORDER BY and/or GROUP BY clauses. processing or 'N' to terminate the query.
ANR2960E Unexpected SQL enumerated type name ANR2964E The reference 'reference' is not a column
token - 'token'. of the SQL result table.
Explanation: A syntax error occurred because an SQL Explanation: The ORDER BY clause specified a
enumerated type name was found that can not legally column that is not part of the result table for the SQL
be used at the specified position within the SQL query. Only those columns named in the select list are
statement. A list of all of the enumerated types declared part of the result table.
by the server can be found in the SQL catalog table
SYSCAT.ENUMTYPES.
ANR2965E An SQL temporary table cannot be
built. required columns columns are
ANR2961E Invalid SQL enumerated type name - needed. maximum columns is the
'name'. maximum.
Explanation: A syntax error occurred because an SQL Explanation: A temporary table required columns wide
enumerated type name was expected, but the specified is needed to complete processing for an SQL query. The
name is not one of the declared enumerated types. For maximum degree of an SQL table is maximum columns.
example, the literal expression XXX::YYYY is illegal The table will not be created.
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 User response: If the ORDER BY and/or GROUP BY
SYSCAT.ENUMTYPES. clauses were specified, reduce the number of columns
needed for the result table.
ANR2966E Command/process: Database temporary
table storage has been exhausted.
ANR2962E Unable to resolve SQL enumerated type
Explanation: The named command or operation could
for value 'value'.
not be completed because insufficient temporary table
Explanation: A syntax error occurred because an storage space was available. Free space in the server
unqualified SQL enumerated value name was specified, database is used to store temporary tables created
but, because that value name is a member of more than

ANR2967I ANR2969E
during the execution of the named command or resolved correctly by issuing the command "ping
process. localhost" from a system command window. If the
ping of localhost fails, consider changing the
System action: The named command or process is
TCPSERVERADDRESS to the explicit loopback
terminated.
address of 127.0.0.1. As an alternative to setting the
User response: Extend the server database (after explicit loopback address of 127.0.0.1, verify the
adding database volumes if necessary) and rerun the TCP/IP configuration and whether or not
commmand or process. "localhost" is configured correctly. For example, for
Unix or Linux systems, verify that /etc/hosts has
an appropriate entry for "localhost".
ANR2967I Differential database backup started as
process process ID. 3. 106 - Ensure that the DB2 Instance DSMI_DIR
environment variable is pointing to the location of
Explanation: A background process was started to the Tivoli Storage Manger API executables and the
backup the contents of the database. The differential dsm.sys configuration file. If the DSMI_DIR setting
database backup process was assigned the process ID is wrong, correct it for the DB2 instance, and then
shown. restart the DB2 instance.
System action: The database backup process starts 4. 137 - Ensure that the DB2-instance DSMAPIPW
and server operation continues. command was run and that it specified nodename
$$_TSMDBMGR_$$ and the password TSMDBMGR.
5. 400 - Ensure that the options specified in the Tivoli
status of the database backup process by using the
Storage Manager API options file are valid.
the CANCEL PROCESS command. 6. 406 - Ensure that the DB2 instance owner has at
least read access to the Tivoli Storage Manger API
options file. Ensure that the DB2-instance
ANR2968E Database backup terminated. DB2 DSMI_CONFIG environment variable is pointing to
sqlcode: sqlcode. DB2 sqlerrmc: sqlerrmc. a valid options file for the Tivoli Storage Manager
Explanation: DB2 detected a problem during the API. If the DSMI_CONFIG setting is wrong, correct
backup operation. Sources of the problem might it for the DB2 instance, and then restart the DB2
include: instance.
1. Tivoli Storage Manager API configuration errors for 7. 450,451 - Ensure that the server options file and the
the DB2 instance in which the Tivoli Storage Tivoli Storage Manager API options file both
Manager server database resides. contain the COMMMETHOD SHAREDMEM
option. Ensure that the values for the SHMPORT
2. An error related to the DB2 backup operation.
option in each options file correspond. Restart the
3. Errors related to the target backup device. server if you change any values in the server
System action: The database backup is terminated. options file.
8. For descriptions of other sqlerrmc values, look in
User response: If the message indicates DB2 sqlcode the dsmrc.h file that is installed with the Tivoli
2033, then the problem is probably the Tivoli Storage Storage Manager API.
Manager API configuration. The DB2 instance uses the
Tivoli Storage Manager API to copy the Tivoli Storage
If this message is issued with a DB2 sqlcode that is not
Manager database-backup image to the Tivoli Storage
2033, then look for more information about the error by
Manager server-attached storage devices. Common
opening a DB2 command-line processor window and
sqlerrmc codes include:
typing: ? SQLsqlcode. For example, db2 => ? sql2428
1. 50 - To determine whether an error created the API
timeout condition, look for any Tivoli Storage
Manager server messages that occurred during the ANR2969E Database restore terminated. DB2
database-backup process and that were issued sqlcode: sqlcode. DB2 sqlerrmc: sqlerrmc.
before ANR2968E. Ensure that the Tivoli Storage Explanation: DB2 detected a problem during the
Manager API options file has the correct restore operation. Sources of the problem might
TCPSERVERADDR and TCPPORT options specified include:
for the Tivoli Storage Manager server being backed
1. Tivoli Storage Manager API configuration errors for
up. If the option settings are wrong, correct them
the DB2 instance in which the Tivoli Storage
for the DB2 instance.
Manager server database resides.
2. 53 - Ensure that the NODENAME option in the
2. Errors related to the DB2 restore operation.
Tivoli Storage Manager API options files is set to
$$_TSMDBMGR_$$. Also verify the 3. Errors related to the target backup device.
TCPSERVERADDRESS setting. If the keyword
"localhost" is being used verify that this is being
ANR2970E ANR2972E
4. The Tivoli Storage Manager API client configuration If the message indicates DB2 sqlcode 2542, then the
used by the current instance is not able to access the problem is probably because Tivoli Storage Manager
backup image. API version for database restore is not the same API
version for database backup. Check Tivoli Storage
System action: The database restore operation is
Manager API version:
terminated.
1. AIX - /bin/sh -c "lslpp -lcq
User response: If the message indicates DB2 sqlcode tivoli.tsm.client.api.64bit"
2033, then the problem is most likely the Tivoli Storage
2. SUN- /bin/sh -c "cat /var/sadm/pkg/
Manager API configuration. The DB2 instance uses the
TIVsmCapi/pkginfo | grep VERSION
Tivoli Storage Manger API to copy the Tivoli Storage
Manager database restore image from the Tivoli Storage 3. HP- /bin/sh -c "cat /var/adm/sw/products/
Manager server-attached storage devices to DB2. TIVsm64/CLIENT_API64/INDEX| grep ^revision
Common sqlerrmc codes include: 4. Linux - rpm -q TIVsm-API64-* --qf
1. 50 - To determine whether an error created the API %{VERSION}.%{RELEASE}\\n
timeout condition, look for any Tivoli Storage 5. Windows - reg query "HKEY_LOCAL_MACHINE\
Manager server messages that occurred during the SOFTWARE\IBM\ADSM\CurrentVersion\Api"
backup DB process and that were issued before
ANR2969E. Ensure that the Tivoli Storage Manager If this message is issued with a DB2 sqlcode that is not
API options file has the correct TCPSERVERADDR 2033 or 2542, then look for more information about the
and TCPPORT options specified for the Tivoli error by opening a DB2 command-line processor
Storage Manager server being backed up. If the window and typing: ? SQLsqlcode. For example, db2
option settings are wrong, correct them for the DB2 => ? sql2428
instance.
2. 53 - Ensure that the NODENAME option in the ANR2970E Database rollforward terminated - DB2
Tivoli Storage Manager API options files is set to sqlcode sqlcode sqlerrmc sqlerrmc
$$_TSMDBMGR_$$.
3. 106 - Ensure that the DB2-instance DSMI_DIR Explanation: There is a problem detected by DB2.
environment variable is pointing to the location of System action: The database rollforward is
the Tivoli Storage Manager API executables and the terminated.
dsm.sys configuration file. Ensure that you have the
correct permissions to access these locations. If the User response: More information about the error is
DSMI_DIR setting is wrong, correct it for the DB2 available by opening a DB2 command-line processor
instance, and then restart the DB2 instance. window and typing: ? SQLsqlcode. For example, db2
=> ? sql2428
4. 137 - Ensure that the DB2-instance DSMAPIPW
command was run and that it specified the
nodename $$_TSMDBMGR_$$ and the password ANR2971E Database backup/restore/rollforward
TSMDBMGR. terminated - DB2 sqlcode sqlcode error.
5. 400 - Ensure that the options specified in the Tivoli Explanation: There is a problem detected by DB2.
Storage Manager API options file are valid.
System action: The database backup/restore/
6. 406 - Ensure that the DB2 instance owner has at
rollforward is terminated.
least read access to the Tivoli Storage Manager API
options file. Ensure that the DB2 Instance User response: More information about the error is
DSMI_CONFIG environment variable is pointing to available by opening a DB2 command-line processor
a valid options file for the Tivoli Storage Manager window and typing: ? SQLsqlcode. For example, db2
API. If the DSMI_CONFIG setting is wrong, correct => ? sql2428
it for the DB2 instance, and then restart the DB2
instance.
ANR2972E Restore DB Command: Database
7. 450,451 - Ensure that the server options file and the restore/rollforward terminated - Not
Tivoli Storage Manager API options file both able to clean up log directory directory
contain the COMMMETHOD SHAREDMEM name.
option. Ensure that the values for the SHMPORT
option in each options file correspond. Restart the Explanation: TSM tried to clean up this log directory
server if you change any values in the server before PIT restore DB and not able to.
options file.
System action: The database restore/rollforward is
8. For descriptions of other sqlerrmc values, look in terminated.
the dsmrc.h file that is installed with the Tivoli
Storage Manager API. User response: Please clean up this directory
manually before performing DB PIT restore.

ANR2973E ANR2983E
ANR2973E Restore DB Command: Database ANR2979E Internal error - Control descriptor is

restore/rollforward terminated - Log NULL.
directory is required and does not exist
Explanation: Something is wrong the control
directory name.
descriptor is NULL.
Explanation: The log direcotry is required and it does
not exist. PIT restore DB is terminated.
System action: The database restore/rollforward is
terminated.
ANR2980E Database backup terminated TCPIP
User response: Create the specified directory and
failure - DB2 sqlcode sqlcode sqlerrmc
retry.
sqlerrmc.
Explanation: There is a TCPIP failure detected by
ANR2974I Offline DB backup for database DB
DB2.
Alias completed successfully.
System action: The database backup is terminated.
Explanation: Offline DB backup completed
successfully. User response: Correct the TCPIP setup problem
between TSM and DB2 and retry.
ANR2981E Database backup terminated due to
environment or setup issue related to
ANR2975E Offline DB backup for database DB file access - DB2 sqlcode sqlcode
Alias failed with sqlcode sqlcode and sqlerrmc sqlerrmc.
sqlerrmc sqlerrmc.
Explanation: There is a problem related to
Explanation: The Offline Database backup failed. environment or setup detected by DB2.
System action: System action: The database backup is terminated.
User response: User response: Ensure that you specified the correct
file or directory name, correct the permissions, or
specify a new location and retry.
ANR2976I Offline DB backup for database DB
Alias started.
ANR2982E Database backup terminated due to
Explanation: Offline DB backup started.
environment or setup issue related to
System action: None. password - DB2 sqlcode sqlcode sqlerrmc
sqlerrmc.
environment or setup detected by DB2.
ANR2977E Command: Command failed - Restore DB
failed with command error in device System action: The database backup is terminated.
config file.
User response: If the TSM parameter
Explanation: Restore DB failed due to error in device PASSWORDACCESS is set to GENERATE, ensure that
configuration file. the system administrator has used the dsmapipw utility
to set the password. If PASSWORDACCESS is set to
System action: None. PROMPT, ensure that the TSM_NODENAME and
User response: Correct the problem in device TSM_PASSWORD database configuration parameters
configuration file and retry. have been set correctly.
ANR2978E Command: Invalid directory name - ANR2983E Database backup terminated due to
directory name. environment or setup issue related to
DSMI_DIR - DB2 sqlcode sqlcode
Explanation: Restore DB failed due to invalid target sqlerrmc sqlerrmc.
directory name in device target directory file.
System action: None. environment or setup detected by DB2.
User response: Correct the problem in target directory System action: The database backup is terminated.
file and retry.
User response: Ensure that DSMI_DIR points to a
ANR2984E ANR2991E
directory containing the correct version of db2tca, "DBMTRUSTEDIPADDR ipaddr" to set a local host
restart the instance, and execute the command again. address that can be accepted.
ANR2984E Database backup terminated due to ANR2988W Attempt to add the last backup db
environment or setup issue related to volume used entry back in to the
DSMI_CONFIG - DB2 sqlcode sqlcode volume history was unsuccessful.
sqlerrmc sqlerrmc.
Explanation: Restore db operation was successful
Explanation: There is a problem related to however the attempt to add the last backup db volume
environment or setup detected by DB2. used back in to the volume history failed.
System action: The database backup is terminated. System action: The database restore operation is
successful. Entry for last backup db volume used in the
User response: Ensure that the DSMI_CONFIG
operation might be missing from volume history.
environment variable points to a valid TSM options
file. Ensure that the instance owner has read access to User response: Keep a copy of the volume history file
the dsm.opt file. Ensure that the DSMI_CONFIG that was used to do the restore operation. After you
environment variable is set in the db2profile. have verified the restore db operation do a backup db
type=full. Manually track the volume that was not
added back in to the volume history.
ANR2985E Database backup terminated due to I/O
error related to TCPIP - DB2 sqlcode
sqlcode sqlerrmc sqlerrmc. ANR2989E Database Database Name backup failed -
Missing volume history file.
Explanation: There is a TCPIP problem detected by
DB2 and caused the database backup to fail. Explanation: Backup DB failed due to volume history
file is not defined in the dsmserv.opt.
User response: The possible TCPIP problem are
connection time out, connection refused, bad host name User response: Correct the problem in dsmserv.opt file
or network unreachable. Correct the TCPIP problem and retry.
between TSM and DB2 and retry.
ANR2990E Database restore is terminated due to an
ANR2986E Database backup terminated due to I/O invalid database path sqlerrmc and DB2
error - DB2 sqlcode sqlcode sqlerrmc sqlcode sqlcode
sqlerrmc.
Explanation: DB2 detected invalid database path.
Explanation: There is a I/O problem detected by DB2
System action: The database restore is terminated.
and caused the database backup to fail.
User response: Ensure the path exists and permissions
are correct and issue restore DB command again or
User response: Correct the I/O problem between TSM issue restore DB command again with ON parameter to
and DB2 and retry. specify a new valid database storage path.
ANR2987W Session ended because of machine ANR2991E The Incremental Database backup was
GUID or local host IP address terminated because a full database
mismatch. backup is required - DB2 sqlcode sqlcode
sqlerrmc sqlerrmc.
Explanation: Backup or Restore DB commands are
only allowed when the TSM database being backed up Explanation: The Incremental Database backup was
or restored and the TSM api and the TSM server are on terminated. A FULL database backup is required before
the same machine. Either the GUID of the TSM api an Incremental Database backup can be completed.
client in use by the database manager does not match
System action: The incremental database backup is
the GUID of the TSM server or the local host IP
terminated.
address indicated by the TSM client is not accepted.
User response: Complete a FULL database backup
System action: The database backup or restore
first, then retry the incremental database backup.
operation is terminated.
User response: Default acceptable local host addresses
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 TSM server option

ANR2992W ANR3001E
transactions. The log utilization is now at a lower level

ANR2992W The total DB used in DB space is log
and the server is no longer delaying transactions.
space used megabytes, and the total space
available in the DB space is log space System action: Server processing continues.
available megabytes. The ratio is log file
system used ratio. User response: Continue to monitor server activity
and log usage. If log usage is low enough, you may
Explanation: The DB space used exceeds the threshold consider reducing the amount of space allocated to the
for DB space utilization, please define more DB space log.
using EXTend DBSpace command.
System action: ANR2997W The server log is log full percentage
percent full. The server will delay
User response:
transactions by delay time milliseconds.
Explanation: The server log utilization is very high. In
ANR2993E The database backup terminated with a
order to prevent the server log from becoming full, the
log problem. DB2 sqlcode: sqlcode. DB2
server will begin delaying transactions by the specified
sqlerrmc: sqlerrmc.
amount of time.
Explanation: The database backup was terminated by
DB2 because one or more of the log files needed could
not be retrieved. User response: Monitor server activity and log usage.
If possible, delay adding new work to the server load.
User response: If the message did not indicate which
ANR2998W The server log is log full percentage
log directory path caused the problem, look in the
percent full. The server has cancelled
db2diag.log for additional information. Common
the oldest transaction in the log.
problems are a missing directory or permission denied.
Explanation: The server log utilization is dangerously
high. In order to prevent the server log from becoming
ANR2994E The automatic database backup was
exhausted, the server has cancelled the oldest
terminated.
transaction in the log. Once the server activity
Explanation: The operation was terminated because associated with this transaction is able to perform
the device class that is used for the automatic database cleanup processing, log space will be freed.
backup is not defined.
System action: The automatic database backup is
User response: Monitor server activity and log usage.
terminated.
If possible, delay adding new work to the server load.
command to define the device class for the automatic
ANR3000E Command: Command can only be issued
database backup.
on a configuration manager.
Explanation: The command can only be issued on a
server that is a configuration manager.
is used for the automatic database
backup. System action: Server operation continues. The
Explanation: The DELETE DEVCLASS command was
issued to delete a device class that is in use for the User response: Issue this command from a
automatic database backup. configuration manager.
command. ANR3001E Command: Command can only be issued
on a managed server.
command to define a new device class for automatic Explanation: The command can only be issued on a
database backup before deleting this device class. managed server.
ANR2996I The server log is log full percentage command is not processed.
percent full. The server is no longer
delaying transactions. User response: Issue this command from a managed
server.
Explanation: The server log utilization was
dangerously high and the server was delaying
ANR3002E ANR3010W
ANR3002E Command: Profile name exceeds maximum ANR3007E Command: The option option must be
length characters. specified.
Explanation: The profile name specified in the Explanation: When the command is issued on a a
command is longer than the maximum length allowed. server that is neither a configuration manager nor a
managed server, the specified option must be supplied.
command is not processed. System action: Server operation continues. The
User response: Select a profile name that does not
exceed the maximum length. User response: Reissue the command with the
specified option.
ANR3003E Command: Profile description exceeds
maximum length characters. ANR3008I Database backup was written using
client API: API information.
Explanation: The profile description specified in the
command is longer than the maximum length allowed. Explanation: The database backup was written using
the indicated Tivoli Storage Manager Backup/Archive
API.
System action: Database restore processing continues.
User response: Select a description that does not
exceed the maximum length. User response: This information will be used during
the database restore operation. If the API used during
the restore is not compatible, additional messages will
ANR3004E Command: The configuration manager
be issued and the operation will fail.
name exceeds maximum length characters.
Explanation: The configuration manager name
ANR3009E Database restore not possible, client API
specified in the command is longer than the maximum
is not compatible: API information.
length allowed.
Explanation: The Tivoli Storage Manager client API
version being used for this database restore operation is
not compatible with the version used to write the
User response: Select a configuration manager name database backup.
that does not exceed the maximum length.
System action: Database restore processing terminates.
User response: Install a newer version of the Tivoli
ANR3005E Command: The server name exceeds
Storage Manager client API and retry this database
maximum length characters.
restore operation. The client API version currently
Explanation: The configuration manager name available and used for this database restore operation is
specified in the command is longer than the maximum not compatible with what was used to originally write
length allowed. the database backup.

command is not processed. ANR3010W This command will delete an object that
is associated with one or more profiles
User response: Select a configuration manager name on a configuration manager. Subsequent
that does not exceed the maximum length. configuration refresh processing will
delete the object on managed servers
ANR3006E Command: The configuration refresh that subscribe to a profile with which
interval value must be between minimum the object is associated.
value and maximum value. Explanation: A command has been entered that will
Explanation: The specified command has been issued delete an object from a configuration manager. Since
with an invalid refresh interval. this object is associated with one or more profiles on a
configuration manager, configuration refresh processing
System action: Server operation continues. The will delete this object on subscribing managed servers.
User response: Issue the command and specify a valid continue with the command.
refresh interval value.
User response: To process the command, enter 'Y' to
continue or 'N' to stop the process.

ANR3011E ANR3020E
ANR3011E command: Subscription for profile profile ANR3015E command: One or more profiles still
name was not deleted because one or exist.
more objects could not be discarded.
Explanation: A configuration manager state cannot be
Explanation: This message was issued because one or set to OFF is one or more profiles still exist.
more objects could not be discarded by the indicated
command. A previous message gives an explanation for
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
User response: Examine previous messages to 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
Explanation: The command has successfully set the performed after the specified number of minutes of
configuration manager state. elapsed.
System action: The command succeeded. System action: The command succeeded.
ANR3013W command: Configuration manager state ANR3017I command: Profile profile name defined.
already set to state.
Explanation: The command has successfully define a
Explanation: The specified state is already in force on profile.
the server.
System action: The command succeeded.
User response: This server is already set to the
ANR3018E command: Profile profile name already
specified state. If the state should be set differently,
exists.
reissue the command specifying the new state value.
Explanation: The profile specified already exists on
the configuration manager.
ANR3014E command: One or more subscriptions still
exist. System action: Server operation continues. The
Explanation: A configuration manager state cannot be
set to OFF is one or more subscription still exist. The User response: Decide on another profile name and
server still has a record of one or more subscriptions to reissue the command.
its profiles.
System action: Server operation continues. The ANR3019I command: Profile profile name updated.
Explanation: The command has successfully updated
User response: Use the QUERY SUBSCRIBERS a profile.
command to determine which subscriptions still exist.
The DELETE SUBSCRIBER command can be used to System action: The command succeeded.
remove the record of these subscriptions. You may User response: None.
instead want to delete the actual subscription(s) on the
managed server(s). When there are no more
subscriptions recorded on the configuration manager, ANR3020E command: Profile profile name not found.
you must then delete all the profiles. Once the profiles Explanation: The profile specified could not be found.
have been deleted, you can reissue the command.
ANR3021I ANR3030I
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
configuration manager. Alternatively, the FORCE=YES
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,
informing the managed server that the profile has been
ANR3023I command: Profile profile name locked. deleted.
Explanation: The command has successfully locked
the profile. No configuration information can be ANR3028E command: Profile profile name is locked.
propagated to the subscribers of the profile until it is
unlocked. Explanation: The specified command cannot be
performed on a locked profile.
User response: None. command is not processed.
User response: Unlock the profile using the UNLOCK
ANR3024W command: Profile profile already locked PROFILE command and then reissue the command.
with timeout interval greater than
interval.
ANR3029E command: Profile name not specified.
Explanation: An attempt was made to lock the
specified profile. The profile is already locked with a Explanation: A profile name must be specified on this
timeout interval greater than the value specified. command using the PROFILE= parameter.
System action: The profile remains locked with the System action: Server operation continues. The
original timeout interval. command is not processed.
User response: If you want to lower the timeout User response: Reissue the command and specify a
interval, unlock the profile and then lock the profile profile name.
again specifying the lower value.
ANR3030I command: Subscription defined for
ANR3025I command: Profile profile name unlocked. profile profile name.
Explanation: The command has successfully unlocked Explanation: The command has successfully defined a
the profile. Configuration information can now be subscription to the specified profile. A refresh of the
propagated to the subscribers of the profile. configuration information has been initiated.

ANR3031W ANR3039E

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
found in the configuration manager's records as being a
valid subscriber of any profiles.
User response: Check to make sure you specified the
correction profile name, and reissue the command if
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.
System action: Server operation continues. The ANR3037I command: Subscription deleted for
command is not processed. profile profile name.
User response: Reissue the command and specify a Explanation: The command has successfully deleted a
server name. subscription for the specified profile. A refresh of the
configuration information has been initiated.
ANR3033E command: Server server is not the System action: The command succeeded.
managed server's configuration manager.
Explanation: A server name was specified on the
command which does not match the current
ANR3038E command: Subscription for profile profile
configuration manager. A managed server may only
name not found.
have one configuration manager.
Explanation: A subscription was not found for the
specified profile.
User response: Reissue the command and leave off
the server parameter. It will default to use the current
configuration manager. A QUERY SUBSCRIPTION will User response: Check to see that the profile name was
display the configuration manager currently in use. specified correctly. Issue the QUERY SUBSCRIPTION
command to check to see which profiles have
subscriptions. Reissue the command with the correct
ANR3034E command: Server server cannot be used as
profile name.
this server's configuration manager.
Explanation: A server name was specified on the
ANR3039E command: No matching administrators
command which cannot be used as a configuration
found in configuration.
manager.
Explanation: No administrator definitions were found
on the configuration manager that match the admin(s)
specified on the DEFINE PROFASSOCIATION
User response: Find out the correct name for the command.
configuration manager and then reissue the command.
ANR3035I command: Subscriber subscriber name
User response: Use the QUERY ADMIN command to
deleted.
check which administrators that are defined on the
Explanation: The command has successfully deleted a server and then reissue to DEFINE
subscriber from the record kept in the configuration PROFASSOCIATION command.
manager. If the subscriber (managed server) still has a
subscription to a valid profile, the record of the
subscription will reappear when it performs its next
configuration refresh.
ANR3040I ANR3047E
ANR3040I command: All administrators associated ANR3044I command: All domains associated with
with profile profilename. profile profilename.
Explanation: The command has successfully Explanation: The command has successfully
associated all the administrators with the specified associated all the domains with the specified profile.
profile. All administrator definitions will be All domain definitions will be automatically
automatically propagated to managed servers which propagated to managed servers which subscribe to the
subscribe to the profile. If an administrator is added to profile. If a domain is added to the configuration
the configuration manager in the future, its definition manager in the future, its definition will also be
will also be automatically propagated to the managed automatically propagated to the managed servers.
servers.
ANR3045I command: Domain domain associated with
ANR3041I command: Administrator admin associated profile profilename.
with profile profilename.
Explanation: The command has successfully
Explanation: The command has successfully associated the domain with the specified profile. The
associated the administrator with the specified profile. domain definition will be automatically propagated to
The administrator definition will be automatically managed servers which subscribe to the profile.
propagated to managed servers which subscribe to the
profile.
ANR3046W command: No additional domains
associated with profile profilename.
ANR3042W command: No additional administrators
Explanation: No additional domains were associated
with the profile. The domain(s) specified are already
Explanation: No additional administrator were associated with the profile.
associated with the profile. The administrator(s)
specified are already associated with the profile.
User response: Use the QUERY DOMAIN command
to check which domains are defined on the server and
User response: Use the QUERY ADMIN command to then reissue to DEFINE PROFASSOCIATION
check which administrators are defined on the server command. The QUERY PROFASSOCIATION
and then reissue to DEFINE PROFASSOCIATION FORMAT=DETAILED can be used to see which
command. The QUERY PROFASSOCIATION domains are already associated with the profile.
FORMAT=DETAILED can be used to see which
administrators are already associated with the profile.
ANR3047E command: No matching admin schedules
ANR3043E command: No matching domains found
Explanation: No admin schedule definitions were
in configuration.
found on the configuration manager that match the
Explanation: No domain definitions were found on admin schedule(s) specified on the DEFINE
the configuration manager that match the domain(s) PROFASSOCIATION command.
command.
User response: Use the QUERY SCHEDULE
TYPE=ADMIN command to check which admin
User response: Use the QUERY DOMAIN command schedules are defined on the server and then reissue to
to check which domains that are defined on the server DEFINE PROFASSOCIATION command.
and then reissue to DEFINE PROFASSOCIATION
command.

ANR3048I ANR3055E
ANR3048I command: All admin schedules ANR3052I command: All scripts associated with
associated with profile profilename. profile profilename.
associated all the admin schedules with the specified associated all the scripts with the specified profile. All
profile. All admin schedule definitions will be script definitions will be automatically propagated to
automatically propagated to managed servers which managed servers which subscribe to the profile. If a
subscribe to the profile. If an admin schedule is added script is added to the configuration manager in the
to the configuration manager in the future, its future, its definition will also be automatically
definition will also be automatically propagated to the propagated to the managed servers.
managed servers.
ANR3053I command: Script script associated with
ANR3049I command: Admin Schedule admin schedule profile profilename.
Explanation: The command has successfully associated the script with the specified profile. The
associated the admin schedule with the specified script definition will be automatically propagated to
profile. The admin schedule definition will be managed servers which subscribe to the profile.
automatically propagated to managed servers which
subscribe to the profile.
ANR3054W command: No additional scripts
ANR3050W command: No additional admin
Explanation: No additional scripts were associated
schedules associated with profile
with the profile. The script(s) specified are already
profilename.
associated with the profile.
Explanation: No additional admin schedules were
associated with the profile. The admin schedule(s)
User response: Use the QUERY SCRIPT command to
check which scripts are defined on the server and then
reissue to DEFINE PROFASSOCIATION command. The
User response: Use the QUERY SCHEDULE QUERY PROFASSOCIATION FORMAT=DETAILED
TYPE=ADMIN command to check which admin can be used to see which scripts are already associated
schedules are defined on the server and then reissue to with the profile.
DEFINE PROFASSOCIATION command. The QUERY
PROFASSOCIATION FORMAT=DETAILED can be
ANR3055E command: No matching client option sets
used to see which admin schedules are already
Explanation: No client option set definitions were
found on the configuration manager that match the
ANR3051E command: No matching scripts found in
client option set(s) specified on the DEFINE
configuration.
PROFASSOCIATION command.
Explanation: No script definitions were found on the
configuration manager that match the script(s) specified
on the DEFINE PROFASSOCIATION command.
User response: Use the QUERY CLOPTSET command
to check which client option sets that are defined on
the server and then reissue to DEFINE
User response: Use the QUERY SCRIPT command to PROFASSOCIATION command.
check which scripts that are defined on the server and
then reissue to DEFINE PROFASSOCIATION
command.
ANR3056I ANR3063E
ANR3056I command: All client option sets ANR3060I command: All servers associated with
associated with profile profilename. profile profilename.
associated all the client option sets with the specified associated all the servers with the specified profile. All
profile. All client option set definitions will be server definitions will be automatically propagated to
automatically propagated to managed servers which managed servers which subscribe to the profile. If a
subscribe to the profile. If a client option set is added server is added to the configuration manager in the
to the configuration manager in the future, its future, its definition will also be automatically
definition will also be automatically propagated to the propagated to the managed servers.
managed servers.
ANR3061I command: Server server associated with
ANR3057I command: Client option set client option profile profilename.
set associated with profile profilename.
Explanation: The command has successfully associated the server with the specified profile. The
associated the client option set with the specified server definition will be automatically propagated to
profile. The client option set definition will be managed servers which subscribe to the profile.
automatically propagated to managed servers which
subscribe to the profile.
ANR3062W command: No additional servers
ANR3058W command: No additional client option
Explanation: No additional servers were associated
sets associated with profile profilename.
with the profile. The server(s) specified are already
Explanation: No additional client option sets were associated with the profile.
associated with the profile. The client option set(s)
User response: Use the QUERY SERVER command to
check which servers are defined on the server and then
User response: Use the QUERY CLOPTSET command reissue to DEFINE PROFASSOCIATION command. The
to check which client option sets are defined on the QUERY PROFASSOCIATION FORMAT=DETAILED
server and then reissue to DEFINE can be used to see which servers are already associated
PROFASSOCIATION command. The QUERY with the profile.
PROFASSOCIATION FORMAT=DETAILED can be
used to see which client option sets are already
ANR3063E command: No matching server groups
Explanation: No server group definitions were found
ANR3059E command: No matching servers found in
on the configuration manager that match the server
configuration.
group(s) specified on the DEFINE PROFASSOCIATION
Explanation: No server definitions were found on the command.
configuration manager that match the server(s)
command.
User response: Use the QUERY SERVERGROUP
command to check which server groups that are
defined on the server and then reissue to DEFINE
User response: Use the QUERY SERVER command to PROFASSOCIATION command.
check which servers that are defined on the server and
then reissue to DEFINE PROFASSOCIATION
command.

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

are associated with the specified profile. ANR3072I command: Domain association domain
command is not processed. Explanation: The command has successfully deleted a
domain association from the specified profile. This will
User response: Use the QUERY PROFASSOCIATION automatically delete this domain from the managed
command to check which administrators are associated servers that are subscribed to this profile.
with the profile and then reissue to DELETE
PROFASSOCIATION command. System action: The command succeeded.
ANR3073E ANR3082E

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

ANR3077I command: All script associations deleted associated with profile profile.
Explanation: No matching server definitions are
Explanation: The command has successfully deleted associated with the specified profile.
all scripts associations from the specified profile. This
will automatically delete these scripts from the System action: Server operation continues. The
managed servers that are subscribed to this profile. command is not processed.
System action: The command succeeded. User response: Use the QUERY PROFASSOCIATION

ANR3083I ANR3091E
command to check which servers are associated with

ANR3088W This command will cause the deletion
the profile and then reissue to DELETE
of objects on any managed server
subscribed to profile profile name.
Explanation: A DELETE PROFASSOCIATION
ANR3083I command: All server associations deleted
command option has been entered. This action will not
only delete the association from the profile, but it will
Explanation: The command has successfully deleted also result in the deletion of managed object(s) on any
all servers associations from the specified profile. This managed server subscribing to this profile. The deletion
will automatically delete these servers from the of these objects will occur during the next configuration
managed servers that are subscribed to this profile. refresh for that managed server.
System action: The command succeeded. System action: The system asks whether you wish to
User response: To process the DELETE
PROFASSOCATION command, enter 'Y' to continue or
ANR3084I command: Server association server 'N' to stop the command.
Explanation: The command has successfully deleted a ANR3089E command: Command failed -
server association from the specified profile. This will Server-to-server communication error
automatically delete this server definition from the with server server name.
managed servers that are subscribed to this profile.
Explanation: The specified command failed while
System action: The command succeeded. attempting to communicate with the indicated server.
User response: None. System action: Server operation continues. The
ANR3085E command: No matching server groups User response: Verify that the indicated server name
associated with profile profile. is correctly defined. Try reissuing the command. Use
Explanation: No matching server group definitions are the server PING command to see if the other server is
associated with the specified profile. up. If the problem persists, consult with your network
administrator.
ANR3090E command: Server server name is not a
User response: Use the QUERY PROFASSOCIATION configuration manager.
command to check which server groups are associated
with the profile and then reissue to DELETE Explanation: The specified command failed because it
PROFASSOCIATION command. tried to contact the specified server, and discovered that
the server is not a configuration manager.
ANR3086I command: All server group associations System action: Server operation continues. The
deleted from profile profilename. command is not processed.
Explanation: The command has successfully deleted User response: Reissue the command and specify a
all server groups associations from the specified profile. correct configuration manager name.
This will automatically delete these server groups from
the managed servers that are subscribed to this profile. ANR3091E command: Profile list not specified.
System action: The command succeeded. Explanation: The specified command failed because
User response: None. you did not specify a profile list on the command.
ANR3087I command: Server group association server command is not processed.
group deleted from profile profilename. User response: Reissue the command specifying a
Explanation: The command has successfully deleted a profile list.
server group association from the specified profile. This
will automatically delete this server group from the
managed servers that are subscribed to this profile.
ANR3092I ANR3099E
TYPE=FULL should be performed as soon as possible

ANR3092I command: Subscriber notification
and the volume history information backed up after
processing has begun.
this backup is completed. This will set a new best
Explanation: A NOTIFY SUBSCRIBER process has possible restore point if a future restore operation is
begun. The managed server(s) are being contacted, needed. If you use the Disaster Recovery Manager
asking them to immediately perform a configuration feature to track database backup volume physical
refresh. location you will have to manually track the location of
the database backup volumes which were not updated.
command succeeded.
ANR3096I The volumes used to perform this
restore operation were successfully
recorded in the server volume history.
ANR3093I command: No matching profiles or
Explanation: At the end of database restore processing
subscriptions were found.
for a point in time operation, the server database will
Explanation: No subscriptions were found for the be updated to show the volumes that were used to
profiles specified. Either the profiles do not exist, or restore the database. This is done so that a future
there are no subscriptions to the profiles. 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.
System action: Database restore processing completes.
User response: Use the QUERY PROFILE and QUERY
SUBSCRIBER command to determine which profiles User response: None.
exist and which profiles have subscribers. Reissue the
command specifying the correct profile name(s).
ANR3097W LDAPUSER must be set before you can
use LDAP password authentication.
ANR3094E The distinguished name "DN" that is
Explanation: The LDAPURL server option is set,
specified in the LDAPURL option does
however LDAP password authentication cannot
not exist on the LDAP directory server.
complete until LDAPUSER and LDAPPASSWORD are
Explanation: The distinguished name (DN) that is set.
specified in the LDAPURL server option is not found
System action: Server operations continue without
on the LDAP directory server.
LDAP authentication.
User response: Issue the SET LDAPUSER and SET
User response: Create the directory entry that is LDAPPASSWORD commands, in that order.
associated with the DN, specify a DN in the LDAPURL
that already exists, or specify another directory server
ANR3098W LDAPPASSWORD must be set before
that contains the DN that is defined in the LDAPURL
you can use LDAP password
server option. Choose one of these options and restart
authentication.
the IBM Tivoli Storage Manager server.
Explanation: The LDAPURL server option is set,
however LDAP password authentication cannot
ANR3095W Failure updating the database volume
complete until the LDAPUSER and LDAPPASSWORD
history information with the volumes
are set.
used to perform this restore operation.
System action: Server operations continue without
Explanation: At the end of database restore processing
LDAP authentication.
for a point in time operation, the server database will
be updated to show the volumes that were used to User response: Issue the SET LDAPPASSWORD
restore the database. This is done so that a future command.
restore has knowledge of this database backup and will
be able to use this if it is the best possible candidate for
ANR3099E The distinguished name "DN" specified
a future operation. Because the server failed to update
in the LDAPURL option does not have
this information, a future restore database operation
the proper syntax.
may not select the best possible database backup to use
for the operation. Explanation: The distinguished name (DN) in the
LDAPURL server option does not have the proper
System action: Database restore processing completes.
syntax. The LDAP URL must use the RFC 2255 format
User response: Once the server is restarted after the with the restriction that the LDAPURL server option
database restore is completed, a BACKUP DB can only contain ASCII characters. The DN must

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

ANR3111E The LDAPURL server option value
value and restart the server.
LDAP URL is missing the ldap:// prefix.
Explanation: When updating the LDAP URL
ANR3107E LDAPS is not allowed for the
information, use the RFC 2255 format.
LDAPURL option value LDAP URL.
System action: Server operations fail.
Explanation: LDAPS represents using a Secure Sockets
Layer (SSL) connection and sending LDAP data over an User response: Use the standard ldap:// scheme
existing SSL connection. The server only supports prefix for the LDAPURL server option and restart the
LDAP connections secured by using the standard IBM Tivoli Storage Manager server.
LDAPv3 "StartTLS" operation to establish a secure TLS
exchange on an existing LDAP connection.
ANR3112E The password cannot be reset, the
System action: Server initialization fails. LDAP directory server requires you to
provide the current password.
User response: Use the standard ldap:// scheme for
the LDAPURL server option and restart the IBM Tivoli Explanation: The LDAP directory server requires that
Storage Manager server. the user who is specified in the SET LDAPUSER
command provide the current password when
changing another user's password. The LDAPUSER
ANR3108E The distinguished name is missing from
needs to be able to reset passwords to allow IBM Tivoli
the LDAPURL server option value LDAP
Storage Manager administrators to reset passwords for
URL.
Tivoli Storage Manager nodes and administrators.
Explanation: The distinguished name (DN) is required
as part of the LDAPURL server option. When updating
the LDAP URL information, use the RFC 2255 format. User response: Change the password policy or
permission settings on the LDAP directory server to
allow the user who is specified in the SET LDAPUSER
User response: Correct the LDAPURL server option command to change passwords for LDAP users who
value and restart the IBM Tivoli Storage Manager are managed by the IBM Tivoli Storage Manager server.
server.
ANR3113E The password cannot be added or
ANR3109E The LDAPURL server option value changed, the LDAP user does not have
LDAP URL does not contain a host sufficient access rights to add or change
address and cannot be used because the password.
another LDAPURL option value
Explanation: If the current password was not
specifies a host address.
provided for the operation, a password reset is
Explanation: You cannot have multiple LDAPURL performed on the LDAP directory server by the user
server option values if one of the values does not specified in the SET LDAPUSER command. If the
specify a host address. current password was provided for the operation, for
example, in the SET PASSWORD client command, the
System action: Server initialization fails. user's password is changed on the LDAP directory
User response: Correct the LDAPURL server option server by the user. However, if the user's password
value and restart the IBM Tivoli Storage Manager expired, preventing access to the directory server, the
server. password is changed by the user specified in the SET
LDAPUSER command.
ANR3110E The distinguished names "DN" and System action: Server operation fails.
"DN" specified with the LDAPURL User response: Change the password policy and
server option do not match. access rights on the LDAP directory server to allow
Explanation: The distinguished names (DN) specified users to change their own passwords, and to allow the
on each LDAPURL server option value must be the user specified in the SET LDAPUSER command to add
same. or reset passwords for the users that are being
managed by the IBM Tivoli Storage Manager server.
User response: Correct the LDAPURL server option ANR3114E LDAP error LDAP error code (error
value and restart the IBM Tivoli Storage Manager description) occurred during operation.
server.
Explanation: The LDAP operation failed with an
unexpected error.

ANR3115E ANR3121I
System action: The server operation fails. User response: Upgrade the client program to at least
version 6.4 or do not use LDAP authentication to make
it compatible with the newer server program.
around the same time as this message to determine the
cause and impact of the error. Issue the QUERY
ACTLOG command to view the activity log and search ANR3118I The LDAP entry for node node name was
for messages. Check the status of the LDAP directory deleted.
server and examine its log files. Use LDAP utilities
Explanation: An inconsistency between the database
such as ldapsearch or ldp to isolate the problem.
of the Tivoli Storage Manager server database and the
LDAP directory server was found during AUDIT
ANR3115E The LDAP directory server returned the LDAPDIRECTORY command processing. Because you
following error message (LDAP server specified FIX=YES, the LDAP entry for the node was
message) with the LDAP error. deleted to correct this inconsistency.
Explanation: The LDAP directory server returned an System action: Server operations continue.
error message associated with an LDAP error that
occurred, providing addition information to assist in
determining the cause of the problem.
ANR3119I The LDAP entry for administrator admin
System action: The server operation fails.
name was deleted.
Explanation: An inconsistency between the database
of the Tivoli Storage Manager server database and the
LDAP directory server was found during AUDIT
LDAPDIRECTORY command processing. Because you
for messages. Check the status of the LDAP directory
specified FIX=YES, the LDAP entry for the
server and examine its log files. Use LDAP utilities
administrator was deleted to correct this inconsistency.
such as ldapsearch or ldp to isolate the problem.
ANR3116E LDAP SSL/TLS error GSKIT error code User response: None.
(error description) occurred during
operation.
ANR3120I The administrator admin name was
Explanation: An SSL/TLS error code was reported by updated because the parameter parameter
the GSKit component along with the LDAP error that for a node with the same name was
occurred. changed.
System action: The server operation fails. Explanation: Values for the AUTHENTICATION and
SSLREQUIRED parameters must be the same for nodes
and administrators that share the same name. If values
for either the node or the administrator changed, the
administrator or node sharing the same name will be
updated to keep these parameters the same.
for messages. Check for network problems. Check for
problems with the certificate used by the LDAP If the AUTHENTICATION parameter changed from
directory server or the key database containing the LDAP to LOCAL, the password was also updated.
certificates. Check the status of the LDAP directory When this happens, the password is updated to the
server and examine its log files. Use LDAP utilities same password that is used for the node.
such as ldapsearch or ldp to isolate the problem using
a TLS connection to the LDAP server. System action: The server updated the
AUTHENTICATION or SSLREQUIRED parameter of
the specified administrator.
ANR3117E Session session number for node or
administrator node/admin name (client User response: None.
platform) refused - the level of the client
does not meet the minimum required ANR3121I The node node name was updated
level for LDAP authentication. because the parameter parameter for an
Explanation: The server refuses the client session administrator with the same name was
because the client program version level is not 6.4 or changed.
later. Only version 6.4 and later clients can use LDAP Explanation: Values for the AUTHENTICATION and
authentication. SSLREQUIRED parameters must be the same for nodes
System action: The session is refused and server and administrators that share the same name. If values
operations continue. for either the node or the administrator changed, the
ANR3122E ANR3128E
node or administrator sharing the same name will be User response: An LDAP entry must be created before
updated to keep these parameters the same. this administrator can be accessed. To create a new
LDAP entry for this administrator issue the UPDATE
If the AUTHENTICATION parameter changed from
ADMIN command and provide a password. If the
LDAP to LOCAL, the password was also updated.
LDAP directory server is shared with another Tivoli
When this happens, the password is updated to the
Storage Manager server, the LDAP entry can be created
same password that is used for the administrator.
by the other Tivoli Storage Manager server instead.
System action: The server updated the
AUTHENTICATION or SSLREQUIRED parameter of
ANR3125I command: Successfully updated successful
the specified node.
updates nodes out of total update attempts
User response: None. 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
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
updated to keep these parameters the same. attempts administrators that were
targeted for updating.
Explanation: The command updated an administrator
User response: Reissue the command using an
or administrators and produced summary statistics
administrator that has system level authority.
stating how many administrators were updated
Alternatively, rename either the node or the
successfully and how many attempts were made.
administrator associated with the command such that
they do not share the same name. System action: The command succeeded.
ANR3123W An LDAP entry for node node name was
not found in the LDAP directory server.
ANR3127W You must change the password for
Explanation: The REGISTER NODE command was "LDAP user" within number day(s).
issued with AUTHENTICATION=LDAP but without
Explanation: The password is due to expire, and it
providing a password. This combination is valid.
must be changed to prevent failures.
However, this combination will not create an LDAP
entry, which is required to access the node. System action: Server operations continue.
System action: The command succeeded. User response: Change the password on the LDAP
directory server and issue the SET LDAPPASSWORD
User response: An LDAP entry must be created before
command with the new password.
this node can be accessed. To create a new LDAP entry
for this node issue the UPDATE NODE command and
provide a password. If the LDAP directory server is ANR3128E Command: The number of failover
shared with another Tivoli Storage Manager server, the servers exceeds the maximum number
LDAP entry can be created by the other Tivoli Storage allowed.
Manager server instead.
Explanation: The number failover servers that can be
defined for a node is limited to one.
ANR3124W An LDAP entry for administrator admin
name was not found in the LDAP System action: The command fails.
directory server. User response: Reissue the command specifying only
Explanation: The REGISTER ADMIN command was one registered server name.
issued with AUTHENTICATION=LDAP but without
providing a password. This combination is valid.
However, this combination will not create an LDAP
entry, which is required to access the administrator.

ANR3129I ANR3139I
MAXSTREAM parameter is greater than the mount

ANR3129I Server Fail Over high level address set
limit of the specified device class.
to address.
System action: The command is not run.
Explanation: The high level address that clients use to
communicate with this server during fail over has been User response: Rerun the commmand, specifying
set to the value indicated with the SET fewer streams.
FAILOVERHLADDRESS command.
System action: The command succeeded. ANR3136E Extractdb command: Failed to start or
failed to complete successfully.
Explanation: The database extract process was not
able to start due to an error with the command
ANR3132W Replication process with process Id
specification or other validation performed prior to
process number from server server name, is
performing the extract. Alternatively, the extract process
cancelled. Replication process source
had started but failed to complete successfully due to
process number on source server may still
an error during processing.
be active.
System action: Database extract processing did not
Explanation: A replication process on a target
process successfully.
replication server which was initiated on a source
replication server has been cancelled. User response: Review the other messages issued to
determine the cause of the failure.
User response: Check the status of the replication
ANR3137E Unable to reclaim database storage for
process on the source server. Issue the CANCEL
table space tbspace name. The error code
PROCESS command on the source server to cancel this
return code is returned.
replication operation.
Explanation: An error occurred when the database
manager was trying to reclaim space in the referenced
ANR3133E command: Server server name not defined
table space.
Explanation: The server server name is not defined to
System action: The EXTEND DBSPACE operation
the system.
fails. Server operation continues.
System action: The command proceeds howver the
User response: Review messages on the server console
server name is not used.
and in the db2diag log to try and determine the reason
User response: Use QUERY SERVER to identify a for the failure. To complete the process, you will have
valid failover server. to manually execute the steps for redistributing data
and reclaiming space. See the Administrator's Guide for
details about this task.
ANR3134E Command: The number of specified
output volumes (volume count) is less
than the number of streams specified in ANR3138I Reclaiming database storage for table
the MAXSTREAM parameter (stream space tbspace name is being started.
count).
Explanation: The database manager is reclaiming
Explanation: The number of specified output volumes storage space for the referenced table space.
is less than the number of streams specified in the
MAXSTREAM parameter, and scratch volumes are not
allowed. User response: None.
System action: The command is not run.
ANR3139I Reclaiming database storage for all table
User response: Rerun the commmand, specifying
spaces is completed .
more output volumes or fewer streams, or specify
SCRATCH=YES to allow scratch volumes to be used. Explanation: The database manager has reclaimed
space and reduced the size of all table spaces.
ANR3135E Command: The value specified for the System action: Server operation continues.
MAXSTREAM parameter (stream count)
is greater than the mount limit User response: None.
associated with device class device class
(mount limit).
Explanation: The value specified for the
ANR3140I ANR3148W
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 complet.
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.
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. See the Administrator's Guide for
details about this task.
ANR3146E command name: The list of directories
specified for database storage exceeds
ANR3142I Redistribution of data for database length limit characters.
database name on table space tblspace name
Explanation: The list of directories is too long. Specify
is starting.
a list less than or equal to the number of characters
Explanation: The database manager is creating indicated.
directories on newly added paths and redistributing
System action: The command stops.
data across all directories for the referenced table space.
User response: Consider breaking up the operation
into multiple EXTEND DBSPACE commands to reduce
User response: None. the number of directories specified on the command.
ANR3143I The following directory or directories ANR3147I Directory(ies) directory list has been
have been defined in the database defined in the database space. Database
space: directory list. However, the data was distributed and balanced
database manager might not use new across existing directories.
storage paths immediately.
Explanation: Command 'EXTEND DBSPACE'
Explanation: The EXTEND DBSPACE operation successfully added new directory(ies) into the server
successfully added new directories to the server database space and balanced data across existing
database storage space. Because RECLAIM=NO was directories.
specified on the command, data is not redistributed
System action:
across all directories. New storage paths might not be
used until existing storage is full. User response:
ANR3148W Process process number, replicating with
User response: If you decide that you want to
process source process number on server
redistribute data and reclaim space in the database, you
server name, has been inactive for minutes
can manually complete the step for these tasks. See the
of inactivity minutes.
Administrator's Guide for more information.
Explanation: A replication process on a target server

ANR3149I ANR3156E
has been inactive for a significant amount of time. It is

ANR3152I Configuration refresh started with
possible that there is a connection problem with the
configuration manager server name.
source replication server, or the source replication
process is no longer running, or the source replication Explanation: Configuration refresh processing has
server is down. started. A server-to-server session was opened to
receive configuration information from the
configuration manager. Updates will be sent for objects
User response: Verify that the source replication associated with any subscribed-to profiles.
server is still running. If the server is running, check
System action: Refresh processing continues.
that the source replication process is still active. If the
source replication process is no longer active you can User response: None.
cancel this process.
ANR3153I Configuration refresh ended
ANR3149I Server Fail Over high level address successfully with configuration manager
removed. server name.
Explanation: The high level address that clients use to Explanation: Configuration refresh processing ended
communicate with this server during fail over has been successfully. All updates have been made to managed
removed. objects associated with any subscribed-to profiles.
System action: The command succeeded. System action: Server processing continues. The next
automatic refresh will start when the configuration
refresh interval is reached.
ANR3150E Configuration refresh failed with
configuration manager server name. Will
retry in minutes minutes. ANR3154E Communication error on notify to
managed server server name. Will retry in
Explanation: While receiving configuration
minutes minutes.
information from the specified configuration manager,
processing failed because of a communications error. Explanation: While attempting a notify subscriber
request to the specified managed server, a
communications error was detected.
configuration refresh process was stopped and will be
automatically retried. System action: Server operation continues. The notify
subscriber request was stopped and will be
User response: Perhaps the configuration manager is
automatically retried.
not active. If the problem continues, contact the
administrator for the configuration manager, or contact User response: Perhaps the managed server is not
a network administrator. The refresh will automatically active. If the problem continues, contact the
retry several times and then give up until the administrator for the managed server, or contact a
configuration refresh interval is reached again. network administrator. The notify subscriber request
will automatically retry several times and then give up.
ANR3151E Configuration refresh failed with
configuration manager server name. ANR3155E Error attempting notify subscribers
request to managed server server.
information from the specified configuration manager, System action: Server operation continues. The notify
processing failed. subscriber request failed.
System action: Server operation continues. The User response: Examine the activity log for other
configuration refresh process was stopped. messages that may explain why the notify subscriber
request failed.
User response: Examine the activity log for other
messages that may explain why the configuration
refresh failed. The refresh will attempted again when ANR3156E Configuration refresh failed for
the configuration refresh interval is reached. managed server server name.
Explanation: While sending configuration information
to the specified managed server, processing failed.
configuration refresh process ended.
User response: Examine the activity log of both the
ANR3157I ANR3163E
managed server and the configuration manager for

ANR3160E Unable to receive confirmation of
other messages that may explain why the configuration
refresh from managed server server name.
refresh failed. The refresh will attempted again by the
managed server when its configuration refresh interval Explanation: While sending configuration information
is reached. to the specified managed server, a communication error
occurred when trying to receive confirmation from the
managed server that information was processed
ANR3157I Configuration refresh started for
successfully.
managed server server name.
Explanation: Configuration refresh processing has
Configuration refresh processing ended.
started. A server to server session was opened by the
managed server to receive configuration information User response: Determine if communication can be
from the configuration manager. Updates will be sent established with the managed server by using the
for objects associated with any subscribed-to profiles. server PING command. Use the NOTIFY
SUBSCRIBERS command to force the configuration
System action: Refresh processing continues.
refresh to retry.
ANR3161E Premature end of configuration refresh
ANR3158I Configuration refresh ended for managed server server server name.
successfully for managed server server
Explanation: While sending configuration information
name.
to the specified managed server, processing ended
Explanation: Configuration refresh processing ended prematurely because of on error.
successfully. All updates have been made to managed
objects associated with any subscribed-to profiles on
the managed server.
User response: Examine the activity log on the
managed server for any error messages that might
User response: None. explain why the refresh failed. Use the NOTIFY
SUBSCRIBERS command on the configuration manager
to force the configuration refresh to retry.
ANR3159E Managed server server name has newer
version for profile profile name.
ANR3162E Managed server server name aborted
Explanation: While sending configuration information configuration refresh processing due to
to the specified managed server, it has been detected a low memory condition.
that the managed server has a newer version of
configuration information for the specified profile than Explanation: While sending configuration information
does the configuration manager. This condition can to the specified managed server, processing ended
happen if the configuration manager's database has prematurely because of a low memory condition on the
been restored to an earlier point in time. Another managed server.
possibility is that the profile was deleted on the
configuration manager and a new profile by the same
name was created.
User response: Make more memory available to the
System action: Server operation continues. No
managed server.
configuration information for this profile will be sent to
the managed server until this condition is corrected.
ANR3163E Managed server server name aborted
User response: Before correcting the situation, you
configuration refresh processing due to
may want to use QUERY PROFILE to examine the
an internal error.
profile associations defined on both the configuration
manager and the managed server. To correct the Explanation: While sending configuration information
situation, on the managed server delete the to the specified managed server, processing ended
subscription to the profile and define the subscription prematurely because of an internal error on the
again. This will cause the managed server to be managed server.
refreshed at the configuration manager's current level.
User response: Examine the activity log of the
managed server for messages that explain the cause of
the internal error.

ANR3164E ANR3171E
ANR3164E Managed server server name aborted ANR3168E Configuration manager server name
configuration refresh processing due to aborted configuration refresh processing
a lock conflict. due to an internal error.
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 a lock conflict on the managed processing ended prematurely because of an internal
server. error on the configuration manager.
Configuration refresh processing ended. Configuration refresh processing ended.
User response: Use the NOTIFY SUBSCRIBERS User response: Examine the activity log of the
command to retry the configuration refresh. If this configuration manager for messages that explain the
problem persists, contact your service representative. cause of the internal error.
ANR3165E Managed server server name aborted ANR3169E Configuration manager server name
configuration refresh processing due to aborted configuration refresh processing
a protocol error. due to a lock conflict.
Explanation: While sending configuration information Explanation: While receiving configuration
to the specified managed server, processing ended information from the specified managed server,
prematurely because of a protocol error detected on the processing ended prematurely because of a lock conflict
managed server. on the configuration manager.
Configuration refresh processing ended. Configuration refresh processing ended.
User response: Use the NOTIFY SUBSCRIBERS User response: Retry the configuration refresh by
command to retry the configuration refresh. If this issuing the SET CONFIGREFRESH command (using
problem persists, contact your service representative. the current refresh interval value). If this problem
ANR3166E Unable to receive configuration refresh
information from server server name. ANR3170E Configuration manager server name
aborted configuration refresh processing
due to a protocol error.
processing ended prematurely because of a Explanation: While receiving configuration
communications error. information from the specified configuration manager,
processing ended prematurely because of a protocol
error detected on the configuration manager.
User response: Use the server PING command to see
if the configuration manager can be reached. If the
problem persists, contact your network administrator. User response: Retry the configuration refresh by
issuing the SET CONFIGREFRESH command (using
the current refresh interval value). If this problem
ANR3167E Configuration manager server name
aborted configuration refresh processing
due to a low memory condition.
ANR3171E Configuration refresh with
configuration manager server name had
to skip processing for one or more
processing ended prematurely because of a low
objects.
memory condition on the configuration manager.
it became necessary to skip the creation or deletion of
User response: Notify the administrator of the one or more objects.
configuration manager.
User response: Examine the managed server's activity
ANR3172W ANR3178E
log for earlier messages that identify the object, and System action: Server operation continues. The
take the actions identified in those messages. operation in progress fails.
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
Explanation: While receiving configuration not be refreshed from configuration
information from the configuration manager, it has manager server name.
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
been detected that the managed server has a newer User response: If the profile should no longer be
version of configuration information for the specified locked, use the UNLOCK PROFILE command to
profile than does the configuration manager. This unlock it.
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
new profile by the same name was created. Explanation: While receiving configuration refresh
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
manager and the managed server. To correct the User response: The configuration manager is at a
situation, on the managed server delete the higher release level than the managed server. The
subscription to the profile and define the subscription managed server subscribed to a profile that contains an
again. This will cause the managed server to be unsupported object. Delete the subscription to this
refreshed at the configuration manager's current level. profile until service can be applied to the server to
bring it to a higher release level.
ANR3174E Communication error with managed

server server name. ANR3178E A communication error occurred during
session session number with replication
Explanation: While receiving or sending information server server name.
to the specified managed server, a communications
error was experienced. Explanation: The communication error occurred while
the system was receiving information from or sending

ANR3179E ANR3184E
information to the specified replication server. This to specify a different server for the target of the
error can occur on a target replication server if a replication.
CANCEL REPLICATION command is issued on the
source replication server.
ANR3182W The password authentication method for
System action: The server is running, but the node node name did not change.
operation that was in progress failed.
Explanation: During replication or import processing,
User response: If this error occurs frequently, consult a node that uses an LDAP directory server to
your network administrator. Also review the activity authenticate passwords at the target was detected, but
log on the target and source replication servers for the source node authenticates passwords with the
messages that are related to replication. Tivoli Storage Manager server (LOCAL). The
Replication and Import process does not change the
node password authentication method from LDAP to
ANR3179E Server server name does not support
LOCAL.
replication or is not initialized for
replication. System action: Replication or Import processing
continues. The node password authentication method
Explanation: In response to a REPLICATE command,
did not change from LDAP to LOCAL.
the server attempted to establish a connection to the
replication target. But the target server does not User response: Change the node password
support replication, or has not been properly initialized authentication method from LDAP to LOCAL by
for replication. issuing the UPDATE NODE command with the
AUTHENTICATION=LOCAL parameter.
replication fails.
ANR3183W The password authentication method for
User response: Make sure the replication target is at
administrator admin name did not
the correct maintenance level and verify that the
change.
globally unique ID (GUID) of the target server is
properly set. Use the tivguid utility to set the GUID if Explanation: During import processing, an
not properly set. administrator ID was detected that authenticates
passwords with an LDAP directory server at the target,
but with the Tivoli Storage Manager server (LOCAL) at
ANR3180E Replication cannot occur for node node
the source. Import processing does not change an
name, file-space filespace name and copy
administrator's password authentication method from
type copytype name because the target
LDAP to LOCAL.
replication server is not set.
System action: Import processing continues. The
Explanation: In response to a REPLICATE NODE
password authentication method did not change from
command, the server was unable to establish a
LDAP to LOCAL.
connection to a target replication server because a
target server was not defined. User response: You can change the password
authentication method for the target administrator from
System action: Replication for the node and file space
LDAP to LOCAL by issuing the UPDATE ADMIN
is skipped. However, replication continues for other
command with the AUTHENTICATION=LOCAL
nodes and file spaces.
parameter.
User response: To replicate data, the target replication
server must be defined. Issue the SET REPLSERVER
ANR3184E Server server name cannot replicate with
command to set the target replication server name. The
this server
name specified in the SET REPLSERVER command
must be associated with a valid server definition. Explanation: In response to a REPLICATE command,
the server tried to establish a connection with the
replication target. The target server is at a level that
ANR3181E Replication server server name has the
cannot support replication with this server.
same replication key as this server.
System action: Server operations continue. The
Explanation: During replication initialization, the
replication fails.
server detected that the replication key of the target
server is the same as this server. Each server must have User response: Make sure that the replication target
a unique replication key. server is at a maintenance level that supports
replication with this server.
System action: Replication to the specified server is
stopped.
User response: Issue the SET REPLSERVER command
ANR3185I ANR3193I
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
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
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.
The replication of the associated node fails.
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
ANR3192I Replicate Node: Proxy agent nodes
replication
replicated: proxy nodes replicated of proxy
Explanation: During a REPLICATE NODE operation, nodes found identified. Associated
the server attempted to replicate a node that is either a authorized nodes replicated: authorized
proxy agent or referenced in a file space authorization nodes replicated of authorized nodes found
rule of a replicating node. The associated replication identified. Client option sets replicated:
node could not be replicated because it is not currently option sets replicated of option sets found
configured for replication. Associated replication nodes identified.
must have a replication mode set to SEND and a
Explanation: The replication process has completed.
replication state of ENABLED in order to be replicated
The meanings of the numbers are:
to a target server.
v Proxy agent nodes are the number of nodes which
System action: The replication operation continues. are identified as proxy agents for any of the nodes
The replication of the associated node fails. specified in the REPLICATE NODE command.
User response: To use an associated replication node v Associated authorized nodes are the number of
with a client during a failover operation configure and nodes referenced in file space authorization rules of
enable the associated replication node for replication. any of the nodes specified in the REPLICATE NODE
command.
ANR3188E Replication of associated replication v Client option sets are the number of option sets
node associated replication node name failed which are referenced by any of the nodes specified in
- the node is not enabled for replication the REPLICATE NODE command.
Explanation: During a REPLICATE NODE operation, System action: None.

the server attempted to replicate a node that is either a User response: None.
proxy agent or referenced in a file space authorization
rule of a replicating node. The associated replication
node could not be replicated because it is not currently ANR3193I Replication Preview: Proxy agent nodes
enabled for replication. Associated replication nodes identified: proxy nodes found. Associated
must have a replication mode set to SEND and a authorized nodes identified: authorized
replication state of ENABLED in order to be replicated nodes found. Client option sets identified:
to a target server. option sets found.

ANR3194I ANR3199I
Explanation: The preview replication process has

ANR3197W command: Replication of authorization
completed. The meanings of the numbers are:
rule failed for node node name, filespace
v Proxy agent nodes are the number of nodes which Id filespace id on target server target server
are identified as proxy agents for any of the nodes - a duplicate rule exists on the target
specified in the REPLICATE NODE command. server.
v Associated authorized nodes are the number of
Explanation: A file space authorization rule on this
nodes referenced in file space authorization rules of
server could not be replicated to the target server
any of the nodes specified in the REPLICATE NODE
because an identical rule already exists on the target
command.
server.
v Client option sets are the number of option sets
which are referenced by any of the nodes specified in System action: Server operation continues.
the REPLICATE NODE command. User response: A file space which is being replicated
System action: None. contains an authorization rule that exists on both the
source and target servers. Determine which
User response: None. authorization rule should be used on the target server
using the QUERY ACCESS command of the Tivoli
ANR3194I Identified node associated replication node Storage Manager client. Once you have decided which
as a proxy agent for replicated node authorization rule to use, delete the unneeded
reference node authorization rule using the DELETE ACCESS
command of the Tivoli Storage Manager client.
completed. The server has identified an associated
proxy agent node referenced by a replicated node. The ANR3198E command: The server server name
proxy agent node defintion will be replicated if the definition could not be retrieved.The
referencing node is replicated. database is in an inconsistent state.
System action: Server operations continue. Explanation: An error occurred while accessing the
server information.
ANR3195I Identified node associated replication node User response: For details and instructions to resolve
which is referenced in a file space the issue, see Technote 1598476 at http://
authorization rule for replicated node www.ibm.com/support/entry/portal/. Type 1598476 in
reference node the Search field.

completed. The server has identified an associated ANR3199I Server halt for stage stage initiated at
replication node that is referenced in a file space time.
authorization rule of a replicated node. The associated Explanation: The server HALT processing is being
node defintion will be replicated if the referencing node performed and each stage is reported with the time
is replicated. when that stage was initiated.
System action: Server operations continue. System action: None.
User response: None. User response: This message may not be logged to the
activity log. It is provided for informational purposes
ANR3196E Communication error occurred on only. The stages reported are for informational
Session session number during import purposes and only to denote progress. The sequence
from (communication method and actual stages to be performed during halt may
communication address). vary and as such will cause this not to always report in
the same fashion. The primary consideration is that the
Explanation: A communication error occurred during INIT stage and the COMPLETE stage can be used to
import from another server. calculate the time used to halt the server. These
messages are only displayed if the halt command is
System action: The import process is ended.
issued with the verbose parameter such as: "HALT
User response: Determine the cause of the VERBOSE".
communication error and retry the import.
ANR3200E ANR3208E
User response: To update this object, you can delete

ANR3200E command: Command cannot be executed
the subscription to the configuration profiles with
- domain domain name is a managed
which domain domain name is associated.
object.
Explanation: The specified command cannot be
ANR3205E command: Management class class name in
executed because it would alter the contents of the
domain domain name, policy set set name
indicated managed domain. With the exception of
is a managed object and cannot be
policy set activation, a managed domain can only be
deleted.
modified using configuration information propagated
from the configuration manager. Explanation: The indicated management class is a
managed object and cannot be deleted on the managed
server.
User response: To delete this object, you can delete
ANR3201E command: Domain domain name is a
managed object and cannot be deleted.
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.
the subscription to the configuration profiles with Explanation: The indicated management class is a
which domain domain name is associated. managed object and cannot be updated on the
managed server.
ANR3202E command: Domain domain name is a System action: The command fails and server
managed object and cannot be updated. operation continues.
Explanation: The indicated domain is a managed User response: To update this object, you can delete
object and cannot be updated on the managed server. the subscription to the configuration profiles with
ANR3207E command: Backup copy group group name
in domain domain name, policy set set
name, management class class name is a
Explanation: The indicated backup copy group is a
ANR3203E command: Policy set set name in domain
domain name is a managed object and
server.
cannot be deleted.
Explanation: The indicated policy set is a managed
ANR3208E command: Archive copy group group name
ANR3204E command: Policy set set name in domain managed object and cannot be deleted.
domain name is a managed object and
Explanation: The indicated archive copy group is a
cannot be updated.
Explanation: The indicated policy set is a managed server.
object and cannot be updated on the managed server.
System action: The command fails and server operation continues.

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

name is currently accessing the server
name is a managed object and cannot be
and cannot be discarded.
renamed.
Explanation: The indicated administrator is a
managed object and cannot be renamed on the
DISCARDOBJECTS=YES. The indicated administrator
managed server.
cannot be discarded on the managed server because it
System action: The command fails and server has an active session with the server.
System action: Administrator administrator name is not
User response: To rename this administrator, you can deleted.
User response: Quit or cancel all sessions for this
administrator before discarding the administrator
definition.
name is a managed object - authority
ANR3224E command: Command script command
cannot be granted.
script name is a managed object and
Explanation: The indicated administrator is a cannot be deleted.
managed object. Authority cannot be granted to this
Explanation: The indicated command script is a
administrator on the managed server.
System action: The command fails and server server.
User response: To grant authority to this operation continues.
administrator, you can delete the subscription to the

ANR3225E ANR3233E
User response: To delete this script, you can delete the

subscription to the configuration profiles with which
- option set optionset name is a managed
the object is associated.
object.
Explanation: The specified command cannot be
ANR3225E command: Command script command
executed because it would alter the contents of the
indicated managed option set.
cannot be updated.
Explanation: The indicated command script is a
managed server. User response: None.
operation continues. ANR3230E command: Server group group name is a
User response: To update this script, you can delete
the subscription to the configuration profiles with Explanation: The indicated server group is a managed
which the object is associated. object and cannot be deleted on the managed server.
ANR3226E command: Command script command operation continues.
User response: To delete this server group, you can
cannot be renamed.
Explanation: The indicated command script is a with which the object is associated.
managed object and cannot be renamed on the
managed server.
ANR3231E command: Server group group name is a
System action: The command fails and server managed object and cannot be updated.
Explanation: The indicated server group is a managed
User response: To rename this script, you can delete object and cannot be updated on the managed server.
User response: To update this server group, you can
ANR3227E command: Option set optionset name is a
Explanation: The indicated option set is a managed
ANR3232E command: Server group group name is a
System action: The command fails and server managed object and cannot be renamed.
Explanation: The indicated server group is a managed
User response: To delete this option set, you can object and cannot be renamed on the managed server.
User response: To rename this server group, you can
ANR3228E command: Option set optionset name is a
Explanation: The indicated option set is a managed
object and cannot be updated on the managed server.
System action: The command fails and server - server group group name is a managed
operation continues. object.
User response: To update this option set, you can Explanation: The specified command cannot be
delete the subscription to the configuration profiles executed because it would alter the membership of the
with which the object is associated. indicated managed server group.
ANR3234E ANR3240W
System action: Server server name is not deleted.

ANR3234E command: Server server name is a
managed object and cannot be deleted. User response: Before server name can be deleted, the
DELETE EVENTSERVER command must be used to
Explanation: The indicated server is a managed object
remove the event server reference to server name.
and cannot be deleted on the managed server.
ANR3238E command: This object cannot be renamed
because it is associated with one or
User response: To delete this object, you can delete more configuration profiles.
Explanation: This message is issued on a
configuration manager when an attempt is made to
rename an object that is associated with one or more
ANR3235E command: Server server name is a configuration profiles. Associated objects cannot be
managed object - one or more specified renamed because the enterprise configuration facility
attributes cannot be updated. does not support renaming of objects.
Explanation: Because the indicated server is a System action: The command fails and server
managed object, certain attributes cannot be updated operation continues.
on the managed server. These attributes are:
User response: If you must change the object name
SERVERPASSWORD, HLADDRESS, LLADDRESS,
you can delete the object, define it with a new name,
COMMMETHOD, DESCRIPTION, URL, and
and then define a profile association to the new object
ALLOWREPLACE.
(unless a wildcard profile association already exists).
System action: The command fails and server This will cause the object to be deleted and re-defined
operation continues. on managed servers with subscriptions to the profiles
with which this object is associated.
User response: You can restrict the update to
attributes that can be updated on the managed server.
For example, the PASSWORD, NODENAME, ANR3239E Error rc while creating device class device
FORCESYNC, and DELGRACEPERIOD attributes can class.
be updated, even if the server is a managed object.
Explanation: This message is issued when a device
Alternatively, you can delete the subscription to the
class could not be created, because there was an error
configuration profiles with which the object is
while processing the device configuration file.
associated, so that the server is no longer a managed
object. System action: The command fails.
User response: Look in the device configuration file
ANR3236W Server server name is currently in use for errors, and look at the activity log for any previous
and cannot be discarded. error messages that might help determine the location
of these errors in the device configuration file.
DISCARDOBJECTS=YES. The indicated server cannot ANR3240W The device class device class only has
be discarded on the managed server because server number of drives drives while the number
name is in use. This could occur if the managed server of streams requested is number of streams.
has an active connection to server name or if the
managed server has a device class with Explanation: This message is issued when a the
DEVTYPE=SERVER that refers to server name. NUMSTREAM parameter is being specified with a
value higher than the number of drives available to the
System action: Server server name is not deleted. device class.
User response: Before server name can be deleted, the System action: The command continues.
managed server must not have a connection to that
server and the managed server cannot have any User response: The value will be updated as
device-class references to that server. requested. If the number of drives available at the time
the database backup is attempted is less than the
number of streams, the database backup will be
ANR3237W Server server name is the event server performed using the number of online drives as the
and cannot be discarded. number of streams. For example, if the number of
available drives is 2 but the NUMSTREAM value had
been set to 4, than the database backup will be done
using only 2 streams.
DISCARDOBJECTS=YES. The indicated server cannot
be discarded because it is the event server for the
managed server.

ANR3241W ANR3248W
command to verify the current status of the replication

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
REMOVE REPLSERVER command.
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.
System action: The command is stopped by the
server.
ANR3246W Process process ID skipped Num Files
User response: Issue the QUERY REPLSERVER
files on volume Volume name because the
command to verify the current status of the replication
files have been deleted.
server. Verify that the replication GUID specified is
correct for the server you are deleting. Explanation: Some of the files that were encountered
during the move operation were skipped because they
have already been deleted.
ANR3243E command: Replication server server Name
is currently being deleted by a previous System action: The operation skips the files without
REMOVE REPLSERVER command. making copies and continues.
Explanation: When you issue the REPLICATE NODE User response: None.
command, the default replication server is already in
the process of being deleted as a result of a previous
ANR3247W Process process ID skipped Num Files
REMOVE REPLSERVER command.
files on volume Volume name because of
System action: The command is stopped by the pending fragments.
server.
Explanation: Some of the files that were encountered
User response: Issue the QUERY REPLSERVER during the move operation were skipped because they
command to verify the current status of the replication contained pending fragments.
server. Update the default replication server with the
System action: The operation skips the files without
SET REPLSERVER command.
making copies and continues.
User response: Retry the operation at a later time
ANR3244E Session session number for server server
when the fragments are not pending.
name error - replication server is
currently being deleted by a previous
REMOVE REPLSERVER command. ANR3248W Process process ID skipped Num Files
files on volume Volume name because it
Explanation: At the start of a REPLICATE NODE
was unable to lock all segments.
process on a target server, the replication server is
already in the process of being deleted on the target Explanation: The files were skipped because the
server as a result of a previous REMOVE REPLSERVER process was unable to lock all segments of the files.
command.
System action: The operation skips the files without
System action: The command is stopped by the making copies and continues.
server.
User response: Retry the operation.
User response: Issue the QUERY REPLSERVER
ANR3350W ANR3355W

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: If you want existing nodes to be
assigned to the domain from the configuration
manager, you can temporarily assign them to another ANR3354W Locally defined administrative schedule
domain. After the domain definition has successfully schedule name is active and cannot be
been propagated from the configuration manager, replaced with a definition from the
reassign the nodes to the new domain. Alternatively, if configuration manager.
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.
ANR3351W Managed domain domain name contains System action: Refresh processing continues, but this
at least one node and cannot be deleted administrative schedule is not replaced. The system
during configuration refresh processing. will attempt to replace the local administrative
Explanation: During configuration refresh processing, schedule during later configuration refresh operations.
the enterprise configuration facility attempted to User response: If you want this administrative
remove the indicated domain because it has been schedule to be replaced with the schedule definition
deleted from the configuration manager or because the from the configuration manager, deactivate the local
profile association no longer exists. The domain could schedule using the Update Schedule command. After
not be deleted on the managed server because it still the administrative schedule definition has successfully
contains one or more nodes. been propagated from the configuration manager, you
System action: Refresh processing continues, but this can activate the new schedule. Alternatively, if you
domain is not deleted. The system will attempt to want to prevent further attempts to replace the local
delete the domain during later configuration refresh schedule definition during configuration refresh
operations. processing, delete the subscription to the profiles with
which the schedule name is associated.
User response: Assign nodes in this domain to
another domain. Alternatively, you can delete the
subscription to the profiles with which domain domain ANR3355W Managed administrative schedule
name is associated. schedule name is active and cannot be
deleted during configuration refresh
processing.
ANR3352I Locally defined domain domain name
replaced during configuration refresh Explanation: During configuration refresh processing,
processing. the enterprise configuration facility attempted to
remove the indicated administrative schedule because it
Explanation: During configuration refresh processing, has been deleted from the configuration manager or
a local domain definition was replaced with a because the profile association no longer exists. The
definition from the configuration manager. The system schedule could not be deleted on the managed server
also deleted all policy sets, management classes, copy because the schedule is in the active state.
groups, and client schedules belonging to the locally
defined domain and added definitions from the System action: Refresh processing continues, but this
configuration manager. schedule is not deleted. The system will attempt to
delete the administrative schedule during later
System action: None. configuration refresh operations.

ANR3356I ANR3361I
User response: If you want this administrative

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

schedule name deleted during ANR3360W Managed system administrator
configuration refresh processing. administrator name is the only system
administrator - authority cannot be
Explanation: During configuration refresh processing, revoked during configuration refresh
the indicated managed administrative schedule was processing.
removed from the managed server. This occurred either
because the schedule has been deleted from the Explanation: During configuration refresh processing,
configuration manager or because the profile the enterprise configuration facility attempted to revoke
association no longer exists. authority for the indicated administrator because
authority has been revoked on the configuration
System action: None. manager. The authority of the administrator could not
User response: None. be revoked on the managed server because this is the
only system administrator.
ANR3358W Locally defined administrator System action: Refresh processing continues, but
administrator name is the only system authority is not revoked for this administrator. The
administrator and cannot be replaced system will attempt to revoke administrator during
with a definition from the configuration later configuration refresh operations.
manager. User response: Grant system authority to another
Explanation: During configuration refresh processing administrator. Alternatively, you can delete the
the indicated locally defined administrator could not be subscription to the profiles with which administrator
replaced with a definition from the configuration administrator name is associated.
manager. The administrator definition was not replaced
because it is the only system administrator and the ANR3361I Locally defined administrator
definition from the configuration manager does not administrator name replaced during
include system authority. configuration refresh processing.
System action: Refresh processing continues, but this Explanation: During configuration refresh processing,
administrator definition is not replaced. The system a local administrator definition was replaced with a
will attempt to replace the local administrator definition from the configuration manager.
definition during later configuration refresh operations.
User response: If you want this administrator
definition to be replaced with a definition from the User response: None.
configuration manager, you can grant system authority
to another administrator. Alternatively, if you want to
prevent further attempts to replace the local
administrator definition during configuration refresh
processing, delete the subscription to the profiles with
which administrator administrator name is associated.
ANR3362I ANR3369I
ANR3362I Managed administrator administrator ANR3365I Locally defined command script

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

ANR3370I ANR3376W
ANR3370I Managed server group group name ANR3374I Server group group name replaced with
deleted during configuration refresh server server name during configuration
processing. refresh processing.
Explanation: During configuration refresh processing, Explanation: During configuration refresh processing,
the indicated managed server group was removed from a server group definition was replaced with a server
the managed server. This occurred either because the definition from the configuration manager. The server
server group has been deleted from the configuration has the same name as the deleted server group.
manager or because the profile association no longer
exists.
ANR3375W Server server name is currently in use
cannot be deleted during configuration
ANR3371W Server group group name cannot be refresh processing.
defined during configuration refresh
processing because a server already
the enterprise configuration facility attempted to
exists with this name.
remove the indicated server definition because it has
Explanation: During configuration refresh processing, been deleted from the configuration manager or
the enterprise configuration facility attempted to define because the profile association no longer exists. The
the indicated server group on a managed server. The indicated server could not be deleted on the managed
server group could not be defined because a server server because server name is in use. This could occur if
definition with the same name already exists on the the managed server has an active connection to server
managed server. name or if the managed server has a device class with
DEVTYPE=SERVER that refers to server name.
System action: Refresh processing continues, but this
server group is not defined. The system will attempt to System action: Refresh processing continues, but this
define the server group during later configuration server definition is not deleted. The system will attempt
refresh operations. to delete the server during later configuration refresh
operations.
User response: You can delete the subscription to the
profile with which the indicated server group is User response: Before server name can be deleted, the
associated or delete the conflicting server definition on managed server must not have a connection to that
the managed server. Alternatively, you can rename the server and the managed server cannot have any
server group on the configuration manager, after first device-class references to that server.
deleting the profile association for that server group.
ANR3376W Server server name is the event server
ANR3372I Locally defined server server name and cannot be deleted during
replaced during configuration refresh configuration refresh processing.
processing.
Explanation: During configuration refresh processing, the enterprise configuration facility attempted to
a local server definition was replaced with a definition remove the indicated server definition because it has
from the configuration manager. been deleted from the configuration manager or
because the profile association no longer exists. The
indicated server could not be deleted on the managed
User response: None. server because it is the event server for the managed
server.
ANR3373I Server server name deleted during System action: Refresh processing continues, but this
configuration refresh processing. server definition is not deleted. The system will attempt
to delete the server during later configuration refresh
Explanation: During configuration refresh processing, operations.
the definition for managed object server name was
removed from the managed server. This occurred either User response: Before server name can be deleted, the
because server name has been deleted from the DELETE EVENTSERVER command must be used to
configuration manager or because the profile remove the event server reference to server name.
association no longer exists.
ANR3377W ANR3405I
ANR3377W Replacement of local server server name ANR3400I Command: Output stream stream used
with a definition from the configuration volume volume name.
manager is not allowed.
Explanation: The specified output stream used the
Explanation: During configuration refresh processing, specified volume.
the enterprise configuration facility attempted to
System action: The command continues.
replace the indicated server definition with a definition
from the configuration manager. This operation could User response: None.
not be performed because ALLOWREPLACE=NO for
the indicated server.
ANR3401I Command: Output stream stream did not
System action: Refresh processing continues, but this write to any output volumes.
server definition is not replaced. The system will
attempt to replace the server definition during later Explanation: The specified output stream did not
configuration refresh operations. write to any output volumes.
User response: Before the local server definition for System action: The command continues.
server name can be replaced with a definition from the User response: None.
configuration manager, the UPDATE SERVER
command must be used to set the ALLOWREPLACE
attribute to ON. ANR3402I Extractdb command: Process process
number, database extract, has completed.
ANR3378I Administrator administrator name added Explanation: The database extract process process
during configuration refresh processing. number has completed.
Explanation: During configuration refresh processing, System action: Database extract processing ends.
the indicated administrator definition was created User response: None.
based on information from the configuration manager.
System action: None. ANR3403I Extractdb command: Found number of
User response: None. database objects database objects.
ANR3379E Command: Unable to access pool pool of database objects that were found during database
name - access mode is set to "read only". extract processing.
Explanation: The command shown specifies the pool System action: Server processing continues.
whose name is displayed, but the pool cannot be User response: None.
accessed because its status is read only.
System action: The server does not process the ANR3404I Extractdb command: Processed number of
command. database objects database objects.
User response: Either reset the access state of the pool Explanation: This message indicates the total number
or choose another pool and reissue the command. of database objects that were successfully processed
during database extract processing.
ANR3380E Command: Unable to access pool pool System action: Server processing continues.
name - access mode is set to
"unavailable". User response: None.
Explanation: The command shown specifies the pool

whose name is displayed, but the pool cannot be ANR3405I Extractdb command: Skipped number of
accessed because its status is unavailable. database objects empty database objects.
System action: The server does not process the Explanation: This message indicates the total number
command. of database objects that were skipped during database
extract processing because they contained no records.
User response: Either reset the access state of the pool
or choose another pool and reissue the command. System action: Server processing continues.

ANR3406I ANR3470I

ANR3406I Extractdb command: Failed to process
number of database objects database
objects. ANR3412I Extractdb command: Terminating output
stream stream number due to error on
server server name.
of database objects that were not successfully processed
during database extract processing. 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
User response: None. used to send database information to the target server.
ANR3407I Extractdb command: Processed number of
User response: Refer to the target server's messages
database records database records.
for a description of the error. Correct the error and
Explanation: This message indicates the total number rerun the command.
of database records that were successfully extracted
during database extract processing.
ANR3413W Extractdb command: Encountered an
System action: Server processing continues. unexpected table, table name. The table
will be skipped.
Explanation: The database extract process encountered
a table that it did not expect. In most cases, an
ANR3408I Extractdb command: Wrote number of bytes
unexpected table is one that was used in an earlier
bytes.
release, but which is no longer used in the current
Explanation: This message indicates the total number release. Such tables can be safely ignored by the
of bytes that were successfully written during database database extract process. However, in rare cases, this
extract processing. may indicate a programming error. As such, you
should contact your service representative to confirm
System action: Server processing continues. whether the table may be ignored without affecting the
User response: None. success of the upgrade process.
System action: Database extract processing continues.
ANR3409I Extractdb command: Elapsed time was Data from the specified table is not extracted.
elapsed time. User response: Contact your service representative to
Explanation: This message indicates the total amount confirm whether the specified table can be safely
of time that elapsed during database extract processing. ignored.

ANR3414E Extractdb command: Process process
User response: None. number, database extract, has completed
with errors.
ANR3410I Extractdb command: Throughput was Explanation: The database extract process process
megabytes per hour megabytes per hour. number has completed, but errors were encountered by
Explanation: This message indicates the total the process.
throughput (megabytes/hour) during database extract System action: Database extract processing ends.
processing.
User response: Review any messages that were issued
System action: Server processing continues. by the process, and take corrective action as
User response: None. appropriate.
ANR3411I Extractdb command: Extracted number of ANR3470I Command: Auditing enterprise

database records database entries and configuration definitions.
wrote number of bytes bytes in elapsed time Explanation: The server has started to audit database
(megabytes per hour megabytes per hour). definitions used by the enterprise configuration facility.
Explanation: The command read the indicated System action: Server database audit operation
number of data base records, and wrote the indicated continues.
number of bytes.
ANR3471E ANR3479E
attributes. Then use the appropriate SET command to

ANR3471E Audit command: Enterprise configuration
change the attributes, if desired.
global attributes are missing.
Explanation: A database audit process finds that the
ANR3475E Audit command: Extraneous profile
global attributes used by the enterprise configuration
information found.
facility are missing.
Explanation: A database audit process finds
extraneous configuration profile information.
FIX=YES specified so that the enterprise configuration
global attributes can be recreated. User response: Reissue the audit command with
FIX=YES so that the information is deleted.
ANR3472I Audit command: Enterprise configuration
global attributes are missing - attributes ANR3476E Audit command: Extraneous profile
will be recreated using available information found - information will be
database information or default values. deleted.
Explanation: A database audit process finds that the Explanation: A database audit process finds
global attributes used by the enterprise configuration extraneous configuration profile information. Because
facility are missing. Because FIX=YES has been FIX=YES has been specified for the audit command, the
specified on the AUDIT command, these attributes will extraneous information will be deleted.
be recreated using available information from the
database or default values. System action: Audit processing continues.
System action: Audit processing continues. User response: None.
User response: When the audit completes, you can

use the QUERY STATUS command to examine the ANR3477E Audit command: Profile information is
values set for the enterprise configuration global inconsistent.
attributes. Then use the appropriate SET command to Explanation: A database audit process detects
change the attributes, if desired. inconsistent configuration profile information. This
information can be corrected.
ANR3473E Audit command: Enterprise configuration System action: Audit processing continues.
global attribute(s) are incorrect.
Explanation: A database audit process finds that FIX=YES so that the information can be corrected.
global attributes used by the enterprise configuration
facility are incorrect.
ANR3478E Audit command: Profile information is
System action: Audit processing continues. inconsistent - it will be corrected.
User response: Reissue the audit command with Explanation: A database audit process detects
FIX=YES specified so that the enterprise configuration inconsistent configuration profile information. Because
global attributes can be corrected. FIX=YES has been specified for the audit command, the
information will be corrected.
ANR3474I Audit command: Enterprise configuration System action: Audit processing continues.
global attribute(s) are incorrect -
attributes will be corrected using User response: None.
available database information or
default values. ANR3479E Audit command: Profile association
Explanation: A database audit process finds that information is missing.
global attributes used by the enterprise configuration Explanation: A database audit process detects missing
facility are incorrect. Because FIX=YES has been profile association information. This information can be
specified on the AUDIT command, these attributes will recreated.
be corrected using available information from the
database or default values. System action: Audit processing continues.
System action: Audit processing continues. User response: Reissue the audit command with
FIX=YES so that the information can be recreated.
use the QUERY STATUS command to examine the
values set for the enterprise configuration global

ANR3480E ANR3488W
ANR3480E Audit command: Profile association ANR3485E Audit command: Profile subscriptions
information is missing - it will be were found to more than one
recreated. configuration manager.
Explanation: A database audit process detects missing Explanation: A database audit process determines that
profile association information. Because FIX=YES has a managed server has subscriptions to more than one
been specified for the audit command, the information configuration manager. This may cause the enterprise
will be recreated. configuration facility to behave in an unpredictable
manner.
User response: Delete subscriptions for all but one
configuration manager. To do this, it may be necessary
to delete subscriptions to all configuration managers
association information found.
and then define the desired subscriptions.
extraneous profile association information.
ANR3486I CANCEL SESSION ALL command
System action: Audit processing continues. processing ended sooner than expected.
User response: Reissue the audit command with Explanation: It is possible that the server was unable
FIX=YES so that the information is deleted. to cancel all sessions because a session was
encountered that could not be cancelled. Some sessions
may still remain active after the command completes.
association information found - System action: Server operation completes.
information will be deleted.
User response: Specify a session_number with the
Explanation: A database audit process finds CANCEL SESSION command to cancel a specific
extraneous profile association information. Because CLIENT session. If a SERVER session is active, the
FIX=YES has been specified for the audit command, the partner server must be quiesced for the session to end.
extraneous information will be deleted. The SERVER session may be active with a Storage
Agent, Library Client, Library Server or Virtual Volume
System action: Audit processing continues. server. To prevent new sessions from starting, see the
User response: None. DISABLE SESSIONS command.
ANR3483E Audit command: Subscription information ANR3487E Command: The number of administrators
is inconsistent. exceed the maximum number allowed.
Explanation: A database audit process detects Explanation: The number of administrators that can
inconsistent profile subscription information. This receive alert summary by email is limited to three.
information can be corrected. System action: The command fails.
System action: Audit processing continues. User response: Reissue the command specifying a
User response: Reissue the audit command with maximum of three registered administrator names.
FIX=YES so that the information can be corrected.
ANR3488W Command: The administrator administrator
ANR3484E Audit command: Profile subscription name does not have an email address.
information is inconsistent - it will be Explanation: The administrator does not have an
corrected. email address defined. The specified administrator
Explanation: A database audit process detects cannot receive email from the server until a valid email
inconsistent profile subscription information. Because address is defined.
FIX=YES has been specified for the audit command, the System action: The command processing continues.
information will be corrected.
User response: Issue UPDATE ADMIN command to
System action: Audit processing continues. define the email address and reissue the command.
ANR3489I ANR3502W
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 ALERTEMAILFROMADMIN 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.
ANR3500I Backup set for node node name as set
Explanation: The specified administrator name is not name (data type data type) being
set up to receive alerts by email. Alerts cannot be sent generated.
to the administrator until it is configured to receive
alerts by email. Explanation: The named object set is being created for
the specified node.
System action: The server generates a backup set.
User response: Use QUERY ADMIN
FORMAT=DETAIL to display the current settings for User response: None.
the administrator. Verify that the administrator has
ALERT=YES and has a valid email address. Use the
ANR3501I Backup set for node name as set name
UPDATE ADMIN command to update the settings.
(data type data type) completed
successfully - processed files files.
ANR3493E Error sending an email for alert msg
Explanation: The named object set was successfully
number to the administrator with email
created for the specified node. The number of files
address email address using the SMTP
processed is specified.
server name SMTP host server and SMTP
port port number. System action: None.
Explanation: An email about an alert was not sent User response: None.
successfully to the administrator with the specified
email address.
ANR3502W Backup set for node name as set name
System action: Server operation continues. (data type data type) completed with file
processing errors - processed files files
User response: Use QUERY MONITORSETTING
with error files files skipped.
command to see the current settings for emailing an
alert. Check that the administrator's email address and Explanation: The named object set was successfully

ANR3503E ANR3510E
created for the specified node. However, during

ANR3505I Backup set for node name as set name
processing errors were encountered accessing some files
used volume volume name.
- these files were skipped.
Explanation: The named object for the specified node
used the specified volume.
User response: Evaluate other server messages for an
indication of why the files were skipped. Files can be
skipped because of failures locking those files, having User response: None.
no files to process, or for other more serious problems.
First, retry the command and see if it completes
ANR3507I Cancel in progress
without any skipped files. If you are unable to generate
the backup set without skipping files, please contact Explanation: This message is displayed in response to
your local service representative for assistance. a QUERY PROCESS command, and indicates that a
generate backupset process has been canceled. The
process will end shortly.
ANR3503E Generation of backup set for node name
as set name (data type data type) failed. System action: The process terminates and server
Explanation: The named object for the specified node
was not created. An error was encountered causing the User response: None.
creation of this object set not to complete successfully.
System action: Server operation continues. ANR3508W Generation of backup set for node name
as set name (data type data type) failed -
User response: Evaluate other messages that were
no filespaces to process.
issued and try to determine the cause of the failure.
After determining the cause of the failure, retry the Explanation: The named object for the specified node
command. If the cause can not be determined, please was not created. No filespaces were available to
contact your local service representative. process.
If ANR3504W was received, than an error occurred System action: Server operation continues.
while logging the volumes used to the server volume
history. It is possible to issue a DEFINE BACKUPSET User response: Reissue the command against a node
listing these volumes. That would cause the server to that has filespaces associated with it. If no filespaces
create the necessary entries for this backup set on this exist for a given node, than there is no file data to
server. write to the backupset.
ANR3504W Backup set for node name as set name was ANR3509E Command: Error encountered in accessing
not able to log the volumes used for this data storage - device class device class
operation to the server volume history. name is not defined.
Explanation: The named object for the specified node Explanation: During command command processing,
was created. However, when the process attempted to an error occurred because the specified device class is
add the volumes, used for this operation to the volume not defined.
history for the server, an error occurred and this could System action: The command command is ended and
not be completed. server operation continues.
System action: Server operation continues. User response: Make sure the specified device class is
User response: Review other messages issued to defined.
determine which volumes were used to generate this
backup set. The volumes can be inserted into the server ANR3510E Command: Error encountered in accessing
volume history for use by issuing a DEFINE data storage - disk volume specified.
BACKUPSET and listing these volumes. This will also
allow this backup set to be queried from a client as Explanation: During command command processing,
well since there is not a server entry for this backup an error occurred because a specified volume is a disk
set. Only issue the DEFINE BACKUPSET if this volume rather than a tape volume.
generate backup set operation completed successfully. System action: The command command is ended and
User response: Make sure that all volumes specified
for the command command are tape volumes.
ANR3511E ANR3518I
ANR3511E Command: Error encountered in accessing ANR3515E Command: Error encountered in accessing
data storage - invalid volume name data storage - volume already in use.
specified.
Explanation: During command command processing, a
Explanation: The server encounters an error in volume cannot be used because it is already defined in
accessing data storage while processing command a storage pool, or has been previously used by an
command. The error occurred because an attempt has export, database dump, or database backup operation
been made to access a volume with an invalid name. (as recorded in the volume history) or is in use by
another process.
ended and server operation continues. System action: The command command operation is
volume name. User response: Specify a volume that is not in use or
defined in a storage pool, and that has not been
previously used for an export, database dump, or
database backup operation as recorded in the server
data storage - insufficient number of
volume history information. Use the QUERY VOLUME
mount points available for removable
command to display the names of volumes that are
media.
defined to server storage pools. Use the QUERY
Explanation: During command command processing, VOLHISTORY command to display the names of
the server cannot allocate sufficient mount points. volumes that have been used for export, database
dump, or database backup operations.
User response: If necessary, make more mount points media, scratch media could not be
available. mounted.
ANR3513E Command: Output error encountered in the process encounters an out-of-space condition
accessing data storage. writing to the sequential media. Command command
Explanation: The command command operation ends ends when there is no more space on the sequential
because an error has been encountered by the server in media for storing data and SCRATCH=NO has been
writing to a device. Possible reasons include: specified on command command.
v I/O error writing to a device System action: Command command processing ends.
v No storage space. Server processing continues.
System action: The command command operation ends User response: Reissue the command and specify
and server operation continues. SCRATCH=YES or specify additional volume names on
the command.
preceding this one to determine the cause of the error.
After the problem is corrected, the command can be ANR3517E Command: Error encountered in accessing
retried. data storage - required volume was not
mounted.
ANR3514E Command: Data transfer was interrupted Explanation: During command command processing, a
in accessing data storage. required volume cannot be mounted. The mount
request may have been canceled.
command command operation failed because data System action: The command command operation is
transfer to or from data storage was interrupted by an ended and server operation continues.
external event. User response: Issue the command again and make
System action: The command command operation is sure the necessary volumes are accessible.
User response: Examine the messages issued prior to ANR3518I Command: Processing canceled before
this message to determine why the data transfer was completion.
interrupted. Reissue the command command after the Explanation: The background process to service the
problem is resolved. command command has been canceled with the

ANR3519E ANR3525W

ANR3522W Command: Retrieve or restore failed - file
was deleted from data storage during
retrieval.
message.
ANR3519E Command: Insufficient memory available retrieval is complete.
in accessing data storage.
System action: The server ends the command and
Explanation: The server encounters a memory continues operation.
shortage in accessing data storage during command
command operation.
if DELETE FILESPACE, DELETE VOLUME, or
System action: The command command operation ends inventory expiration processes are running; these
and server operation continues. processes can delete data storage files during retrieval.
Reissue the command after these processes have been
User response: See the documentation for the completed or canceled.
application.
ANR3523W Backup set command: Retrieve failed -
error on input storage device.
ANR3520E Command: Internal error encountered in
accessing data storage. Explanation: The server ends a backup set operation
for the specified session because an I/O error has been
Explanation: The server encounters an internal error encountered by the server in reading from a device.
in accessing data storage while processing command The object for which the I/O was issued is reported in
command operation. a later message.
System action: The command command operation is System action: Backup set processing skips this file,
ended and server operation continues. and continues operation.
User response: Use the QUERY ACTLOG command to User response: Query the activity log to find messages
examine messages prior to this error to determine the preceding this one that specify the device that is failing.
cause of the data storage failure. If the failure can be Storage pool volumes can be varied offline (by using
found and resolved, reissue the command command the VARY OFFLINE command), or the server may need
operation. If the failure cannot be found, contact your to be shut down with the HALT command to correct
service representative for assistance in resolving the the hardware problem.
problem.
ANR3524W Backup set command: Transaction failed -

ANR3521W BackupSet command: Data storage retrieve data transfer interrupted.
or restore failed - error detected.
Explanation: The server ends an backup set operation a backup set operation failed because data transfer to
because an error has been encountered on the server. or from data storage was interrupted by an external
Some common reasons for the error are: event.
System action: The backup set operation is ended and
v The storage pool is unavailable server operation continues.
v Data is corrupted on the input volume
v Hardware or media failure has occurred this message to determine why the data transfer was
v Database corruption interrupted. Attempt the backup set operation again
after problem is resolved.
System action: The server ends the backup set
operation and continues operation.
ANR3525W Backup set command: Transaction failed -
User response: Examine any prior error messages to
storage media inaccessible.
ACTLOG command to view the activity log and search Explanation: The server ends a transaction for an
for messages if needed. Correct the problem and try the backup set operation because storage volumes are not
restore or retrieve again. You can also refer to the available in the storage pools in which the client files
Problem Determination Guide for problem determination are to be stored.
continues to fail contact your service representative. System action: The server ends the backup set
operation and server operation continues.
ANR3526E ANR3532E
User response: An authorized administrator can issue candidate for inclusion in the backup set.
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
aggregate. AUDIT VOLUME can determine if this is the
make them available for file storage.
case, and if so, will reset the damaged state for the file.
System action: The damaged file is not added to the
ANR3526E Backup set command: Error encountered in
backupset.
accessing data storage - volume cannot
be used. User response: Audit the indicated volume with
FIX=NO to determine if the file is actually damaged.
Explanation: During backup set processing, a volume
The audit will reset the file's damaged state if the file is
has been mounted but cannot be used.
not damaged. (If the file is part of an aggregate, and
System action: The backup set operation is ended and none of the files within the aggregate are damaged, the
server operation continues. audit will also reset the entire aggregate's damaged
state.)
User response: Query the activity log for messages
preceding this one that give additional information. If the file remains in the damaged state after the audit
Make sure a usable volume is specified and mounted. completes, attempt to restore the damaged file by using
the RESTORE STGPOOL command. Note, however,
that this is only an option if the damaged file is in a
ANR3527E Backup set command operation terminated
primary storage pool that had been previously backed
- it is acting on an empty volume or
up to a copy storage pool.
volume content is not as expected.
If the audit resets the file's damaged state, or the
Explanation: The volume content this command is
damaged file was successfully restored using RESTORE
acting upon is not as expected, the volume is empty, or
STGPOOL, and it is important for this file be included
the volume cannot be found.
in the backup set, then rerun the GENERATE
System action: The command operation is ended. BACKUPSET command to generate a new backup set
containing the file.
User response: Issue the command again and make
sure the expected content is in the volumes or the
volume is not empty and exists. ANR3530E Audit command: A missing, incorrect, or,
invalid collocation group has been
detected.
ANR3528E Backup set command: Media not accessible
in accessing data storage. Explanation: A database audit process found a
missing, incorrect, or invalid collocation group.
Explanation: The server ends a transaction for a
backup set operation because storage volumes are not System action: Audit processing continues.
available in the storage pools in which the client files
User response: Issue the audit command again, and
are to be stored.
specify FIX=YES so that the error can be corrected.
System action: The server ends the backup set
operation and server operation continues.
ANR3531E Audit command: A missing or incorrect
User response: An authorized administrator can issue collocation group has been detected; it
the DEFINE VOLUME command to add storage to one will be corrected.
Explanation: A database audit process found a
missing, incorrect, or invalid collocation group. Because
FIX=YES has been specified for the audit command, the
make them available for file storage.
error will be corrected.
ANR3529W Generate backupset skipping damaged
file on volume volume name: Node node User response: None.
name, Type file type, File space filespace
name, fsId filespace id, File name file name.
ANR3532E Audit command: Missing or incorrect
Explanation: The backup set generation process collocation group identifier for
encountered a file that was previously found to be collocation group collocation group name
damaged. The process encountered the file during a has been detected.
sequential scan of all files on the storage pool volume;
Explanation: A database audit process detects an
the indicated file may or may not have been a

ANR3533E ANR3539E
invalid, missing, or incorrect collocation group

identifier.
collocation group member has been
System action: Audit processing continues. detected for collocation group ID
collocation group ID.
User response: Issue the audit command again and
specify FIX=YES so that the error can be corrected. Explanation: A database audit process detects a
missing or incorrect member for a collocation group.
ANR3533E Audit command: Missing or incorrect System action: Audit processing continues.
collocation group id detected for
User response: Issue the audit command again, and
collocation group name - it will be
corrected.
Explanation: A database audit process detects missing
or incorrect information for a collocation group.
collocation group member has been
Because FIX=YES has been specified for the audit
detected for collocation group id
command, the error will be corrected.
collocation group id - it will be corrected.
Explanation: A database audit process detects a
User response: None. missing or incorrect member for a collocation group.
collocation group name for collocation System action: Audit processing continues.
group id collocation group id has been
detected.
Explanation: A database audit process finds a missing
ANR3539E Generation of backup set for node name
or incorrect collocation group name.
as set name (data type data type) skipped
System action: Audit processing continues. shreddable data object.
User response: Issue the audit command again, and Explanation: The named object for the specified node
specify FIX=YES so that the error can be corrected. was included.
Data retrieved from a shreddable storage pool was
ANR3535E Audit command: Missing or incorrect skipped because the ALLOWSHREDDABLE=YES
collocation group name has been parameter was not specified.
detected for collocation group id
System action: Server operation is terminated.
collocation group id - it will be corrected.
User response: Check with your Storage
Administrator to ensure data retrieved from a
or incorrect information for a collocation group.
shreddable storage pool is a candidate for storing on a
backupset. Data on backupsets cannot be shredded.
Only data that resides in a shreddable storage pool can
System action: Audit processing continues. be shredded. Check whether your Storage
Administrator allows shreddable data to be stored on
User response: None. backupsets. Restart the operation and specify the
ALLOWSHREDDABLE=YES parameter.
ANR3536E Audit command: Inconsistent information A shreddable storage pool is a storage pool that has
detected in collocation group been defined with a non zero SHRED attribute.
(Aggregate.ID). Alternatively, the storage pool from which the
Explanation: A database audit process finds backupset data is retrieved can be updated as a non
inconsistent information for a collocation group. This shreddable storage pool. This requires the storage pool
problem cannot be corrected by the audit process. SHRED attribute to have a value of zero. Backupsets
generated from data retrieved from non shreddable
System action: Audit processing continues. storage pools do not require the
User response: Contact your service representative. ALLOWSHREDDABLE=YES parameter.
ANR3540E ANR3551I
User response: Check with your Storage

ANR3540E Object set set node:set name:data type was
Administrator to ensure data residing in a shreddable
not found for session session number,
storage pool is a allowed to be stored on a backupset.
node.
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
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.
User response: Correct the problem reported by if space reclamation, migration, DELETE FILESPACE,
previous messages, if possible. DELETE VOLUME, MOVE DATA, or inventory
expiration processes are running; these processes can
move or delete data storage files during retrieval.
ANR3543E Error error code occurred while sending Reissue the command after these processes have been
entries from object set set node:set completed or canceled.
name:data type for session session number,
node.
ANR3550E Definition of backup set set name for
Explanation: An error occurred while sending entries node name failed because it has an
for the indicated object set. unknown format.
System action: An error is returned to the client. Explanation: The named object for the specified node
User response: Correct the problem reported by other was not defined. It was generated on a server that is at
prior or subsequent messages related to this session, a higher level than this server and contains data that
and try the operation again. cannot be properly interpreted by this server.
ANR3544E Generation of backup set for node name User response: Define the object on a server that is
as set name (data type data type) skipped compatible with the server that generated the object, or
shreddable data object in file space upgrade this server to be compatible with the server
filespace name (fsId filespace id), file name that generated the object.
file name, type file type.
Explanation: The named data object for the specified ANR3551I The server delete batch size has been set
node was skipped while generating a backupset. to new batch size. Deletion operations
The data object resides in a shreddable storage pool that start after this point will use the
and will not be included in the backupset because the new value.
ALLOWSHREDDABLE=YES parameter was not Explanation: A SETOPT command was used to set the
specified. value for the delete batch size value. This setting
System action: Backupset generation continues. determines the maximum number of files that are

ANR3560E ANR3569E
deleted from the server in one database transaction. System action: The server ignores the command.
The setting influences inventory expiration operations.
User response: Verify the command syntax and
System action: The server uses this new setting for reissue the command.
deletion operations that are started after this message is
issued.
ANR3565E command: The parameter parameter value
User response: None. value is out of range. The minimum
value is min value and the maximum
value is max value. The following
ANR3560E command: One or more of the following
parameter values are also valid: validlist.
parameters are missing: parameters.
Explanation: The command cannot be processed as
specified.
specified.

ANR3561E command: Keyword parameter parameter
value is not recognized. The minimum
is not recognized. The following
keyword parameters are valid: validlist.
Explanation: The command cannot be processed as parameter values are also valid: validlist.
specified.
System action: The server ignores the command. specified.
User response: Verify the command syntax and System action: The server ignores the command.
value is not numeric. The minimum
ANR3567E command: The scale scale for the parameter
parameter is not recognized. The
value is max value.
following scales are valid: validlist.
Explanation: The command cannot be processed
because the specified parameter requires a numeric
specified.
value.

value is out of range. The minimum
value is max value.
value is max value.
specified.
specified.

value is too long. The maximum length
value is not recognized. The following
is max length characters.
parameter values are valid: validlist.
specified.
specified.
ANR3570E ANR3579E

User response: Verify the command syntax and value day day is out of range. The
reissue the command. minimum value is minimum and the
maximum value is maximum.
ANR3570E command: The parameter parameter value Explanation: The command cannot be processed as
is too short. The minimum length is min specified.
length characters.
specified.
User response: Verify the command syntax and ANR3576E command: The parameter parameter value
reissue the command. value year year is out of range. The
minimum value is minimum and the
value contains an invalid character Explanation: The command cannot be processed as
"character". The following characters are specified.
valid: "validlist" (excluding the quotation
marks).
specified.
ANR3577E command: The parameter parameter
User response: Verify the command syntax and relative days value value is not numeric.
ANR3572E command: The parameter parameter value value.
value is a reserved value and cannot be
specified.
specified.
User response: Verify the command syntax and relative days value value is out of range.
reissue the command. The minimum value is 0 and the
maximum value is max value.
value is not a valid date. specified.
Explanation: The command cannot be processed as System action: The server ignores the command.
specified.
System action: The server ignores the command. reissue the command.

reissue the command. ANR3579E command: The parameter parameter value
value is not a valid time.
value month month is out of range. The specified.
specified.

ANR3580E ANR3589I
ANR3580E command: The parameter parameter value ANR3585E command: The parameter parameter
value hours hours is out of range. The relative hours value value is out of
minimum value is minimum and the range. The minimum value is 0 and the
maximum value is maximum. maximum 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.
User response: Verify the command syntax and User response: Verify the command syntax and
reissue the command. reissue the command.
ANR3581E command: The parameter parameter value ANR3586E command: The parameter parameter
value minutes minutes is out of range. relative minutes value value is out of
The minimum value is minimum and the range. The minimum value is 0 and the
maximum value is maximum. maximum 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.
User response: Verify the command syntax and User response: Verify the command syntax and
reissue the command. reissue the command.
ANR3582E command: The parameter parameter value ANR3587E command: The parameter parameter is
value seconds seconds is out of range. The specified more than once.
because the specified parameter can only be entered
Explanation: The command cannot be processed as once.
specified.
User response: Verify the command syntax and reissue the command.
ANR3583E command: The parameter parameter requires the prerequisite parameter
relative hours value value is not parameter.
numeric.
Explanation: The command cannot be processed specified.
value.
ANR3589I command: For more information, issue
the HELP command command.
Explanation: One or more syntax errors were found in
relative minutes value value is not
the specified server command (see the previous
numeric.
messages). The command cannot be processed as
Explanation: The command cannot be processed specified.
value.
ANR3590E ANR3602E
ANR3590E command: Command is above the ANR3595E command: The integer portion of the
requested skill level. parameter parameter value value is out of
range. The minimum integer value is
Explanation: The specified server command has a skill
min value and the maximum integer
level above what was requested.
System action: The server ignores the command. parameter values are also valid: validlist.
User response: Reissue the command and enter the Explanation: The command cannot be processed as
proper syntax. specified.
parameter values are also valid: validlist. ANR3596E command: The parameter parameter
conflicts with the conflicting parameter
parameter.
specified.
specified.
value is not recognized. The minimum
value is min value and the maximum ANR3601W Policy Domain release failed for domain
value is max value. The following domain id due to communications failure.
parameter values are also valid: validlist.
Explanation: The storage agent was attempting to
Explanation: The command cannot be processed as inform the database server that it was finished with the
specified. domain indicated by the domain id, but was unable to
communicate with the database server. The cached
policy information will be cleaned up when the storage
User response: Verify the command syntax and server terminates or re-starts or when the database
reissue the command. server re-starts.
System action: The storage agent continues operation.
ANR3593E command: The parameter parameter value The policy information is deleted from the storage
value is not valid. One of the following agent policy cache.
scales is required: validlist.
User response: Policy caches are cleaned up on the
Explanation: The command cannot be processed as storage agent or server re-start. Network
specified. communication between the storage agent and database
server should be checked.
User response: Verify the command syntax and ANR3602E Unable to communicate with database
reissue the command. server.
Explanation: The storage agent was attempting to
ANR3594E command: The integer portion of the communicate with the database server but was unable
parameter parameter value value is out of to do so.
range. The minimum integer value is
min value and the maximum integer System action: The storage agent operation fails.
value is max value.
User response: Check the configuration of the storage
Explanation: The command cannot be processed as agent and server to ensure that communication
specified. parameters are correct. Ensure that the database server
is running and is accepting messages.

ANR3603E ANR3609E
ANR3603E Storage AgentStorage Agent name was ANR3607E The storage agent was communicating
unable to load policy information due to with the client on a restore request with
a protocol error. verb verb name and received return code
return code.
Explanation: While receiving policy information from
a database server, processing ended prematurely Explanation: The storage agent was communicating
because of a protocol error. with a client for a restore request. While
communicating using the indicated verb ( an internal
System action: Server operation continues. Policy is
request mechanism between the storage agent and
loaded from the database server database.
client ), an unexpected return code was received. The
User response: If this problem persists, contact your verb name and return code are provided for Tivoli
service representative. support personnel.
System action: Database server and storage agent
ANR3604E This command is not supported in the continue. The restore request fails, but may be retried
current operating environment. by the client.
Explanation: A command was issued that is valid User response: Check the configuration of the storage
under most circumstances, but not in the current server agent and client to ensure that communication
environment. parameters are correct. If this problem persists, contact
User response: Issue commands which are allowed in ANR3608E The storage agent was communicating
the current environment. with the database server on a restore
request. An unexpected request (id verb )
ANR3605E Unable to communicate with storage was received from the database server.
agent. Explanation: The storage agent and database server
Explanation: The database server was attempting to were coordinating a restore request. While
communicate with the storage agent but was unable to communicating, the indicated verb ( an internal request
do so. mechanism between the storage agent and database
server ), was unexpected. The verb number is provided
System action: The database server operation fails. for Tivoli support personnel.
User response: Check the configuration of the storage System action: Database server and storage agent
agent and server to ensure that communication continue. The restore request may fail, but may be
parameters are correct. retried by the client.
User response: If this problem persists, contact your
ANR3606E The storage agent was communicating service representative.
with the database server on a restore
request with verb verb name and
received return code return code. ANR3609E The storage agent was handling a
restore request. A failure occurred in
Explanation: The storage agent and database server starting a new thread. The return code
were coordinating a restore request. While return code from the failing routine may
communicating using the indicated verb ( an internal be useful to Tivoli service.
request mechanism between the storage agent and
database server ), an unexpected return code was Explanation: The storage agent was handling a restore
received. The verb name and return code are provided request. A new thread could not be started. Without the
for Tivoli support personnel. new thread the request could not be handled.
System action: Database server and storage agent System action: Database server and storage agent
continue. The restore request fails, but may be retried continue. The restore request has failed.
by the client. User response: Ensure that there is sufficient system
User response: Check the configuration of the storage memory for the storage agent to operate properly.
agent and server to ensure that communication Insufficient memory or paging/swap space can cause
parameters are correct. If this problem persists, contact problems in starting threads. If this problem persists,
your service representative. contact your service representative.
ANR3610I ANR3617E
ANR3610I Domain Identifier domain identifier was ANR3614E The server failed to connect to the
not found. database.
Explanation: The server was cleaning up cached Explanation: The server was unable to establish or
policy information after a restore request. A domain validate a connection to the database.
with the indicated identifier was not found in an
System action: The server will shutdown.
internal list.
User response: Examine the messages that were
System action: Database server and storage agent
issued before this message to determine the cause of
continue.
the failure. Start the server after the issue has been
User response: No response is required if the message resolved.
is the result of starting a storage agent. The storage
agent requests that the server purge cached information
ANR3615E The value of the DATAFORMAT
that it was using previously. It is possible that
parameter for the datamover is not
information tracking policy caching has become stale.
compatible with the NAS file server.
In this case, no response is required. If the message
occurs without a storage agent connecting to the server, Explanation: The datamover was defined with the
contact your service representative. 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 User response: Update the datamover to use the
contact the server to start a session or run a command. CELERRADump dataformat.
The storage agent was unable to contact the server to
start a transaction.
ANR3616E An error occurred. More information
System action: The storage agent continues might be available in the dsmserv.err
processing. The server may be down or there may be a file.
communications problem.
Explanation: None.
User response: No response is required if the message
is the result of stopping a server. Ensure that the server System action: Server operation continues.
with which the storage agent communicates is running User response: Review the dsmserv.err file for
and that there is connectivity between the systems. The messages that occurred at the same time as the error.
server must be restarted before you can start a new The dsmserv.err file is located in the server working
administrator session with the storage agent. directory. Correct any problems that are identified.
ANR3612E This command is not supported in the ANR3617E The server failed to start with return
Express environment. code rc because of an issue with the
Explanation: A command was issued that is valid database environment handle.
under most circumstances, but not in the current server Explanation: The server was unable to allocate a
environment. handle to the database environment.
System action: Server operation continues. System action: The server stops.
User response: Issue commands which are allowed in User response: The following are possible causes and
the current environment. solutions:
v 1. The most common cause is that the DSMSERV
ANR3613W Process process ID skipped Num Files utility is not being run as the instance owner, or the
files on volume Volume name because of user profile (db2profile) has not been sourced for the
a lock conflict with another process. current login shell. To resolve the issue, log in as the
instance user and source the DB2 profile, db2profile:
Explanation: A lock conflict was encountered while . /home/tsminst1/sqllib/db2profile Note: Ensure
moving files and the retries were exceeded. that you insert a space after the initial dot.
System action: The operation skips the files without v 2. A mismatch between the /etc/hosts file and the
making copies and continues. ~/sqllib/db2nodes.cfg file. If the host name was
recently updated, ensure that the systems host name
in the /etc/hosts file matches the host name in the
~/sqllib/db2nodes.cfg file. If the files contain the
same host name, see the db2diag.log files for more

ANR3618W ANR3625I
information. For information about the db2nodes.cfg

ANR3620I Status threshold status threshold updated.
file, see the DB2 documentation.
v 3. The database manager cannot be started due to Explanation: An UPDATE STATUSTHRESHOLD
insufficient system resources. Review the current command has updated the status threshold indicated.
operating system kernel settings and ulimit settings System action: None.
for parameters like nofiles for the user who is
starting the DSMSERV program. Increase the values User response: None.
if needed. For information about changing kernel
and ulimit values, see the documentation for your ANR3621I Status threshold status threshold deleted.
operating system. For guidelines concerning ulimit
settings on Tivoli Storage Manager servers, see the Explanation: A DELETE STATUSTHRESHOLD
information about starting the server instance on command has deleted the status threshold indicated.
AIX, HP-UX, Linux, and Solaris systems in the Tivoli
Storage Manager Information Center. For guidelines
concerning operating system kernel parameters, see User response: None.
the information about tuning kernel parameters in
the Tivoli Storage Manager Information Center.
ANR3622I Status threshold status threshold defined.
v 4. Instance entries are missing from the /etc/services
file. If the entries do not exist in the /etc/services Explanation: A DEFINE STATUSTHRESHOLD
file, re-create the entries as in this example: command has created the status threshold indicated.
DB2_tsminst1 60000/tcp DB2_tsminst1_1 60001/tcp System action: None.
DB2_tsminst1_2 60002/tcp DB2_tsminst1_END
60003/tcp As a general rule, these entries are placed User response: None.
near the end of the /etc/services file. Replace
tsminst1 with the name of the Tivoli Storage
ANR3623E Command: Status threshold status
Manager instance that is being used on the server.
threshold is already defined.
v 5. A copy of the DB2APP64.dll file is in the server
instance directory. In some cases, users mistakenly Explanation: The command indicated has attempted
copy the DB2APP64.dll file to the server instance to define a status threshold that already exists.
directory from the installation directory. By default, System action: None.
the installation directory is C:\Program
Files\Tivoli\TSM\db2\BIN. The DB2APP64.dll file User response: None.
should be in this directory only. Any additional
copies of this DLL file should be removed. ANR3624E Command: Status threshold threshold name
is not defined.
ANR3618W bad adapter number of total adapter number Explanation: The command shown specifies a status
host bus adapters cannot be opened. threshold that is not defined with the server.
Explanation: The SAN discovery function is not able System action: None.
to open all of the host bus adapters (HBAs) on the
system. User response: None.
ANR3625I Host bus adapter (HBA) API functions
User response: Tivoli Storage Manager SAN discovery are not supported by adapter adapter
may only be getting partial device information from the name.
SAN. Verify that all HBAs are configured and working
properly. Explanation: The HBAAPI function failed to retrieve
the attributes of the adapter. The reason is that this
adapter is not a Fibre Channel SCSI adapter. This
ANR3619W The user limit for limit is below the adapter might be a Serial Attached SCSI adapter.
recommended minimum value of value. Therefore, SAN discovery does not work.
Explanation: A user limit that is below the System action: The system is unable to retrieve the
recommended minimum value might cause unexpected attributes of the adapter.
behavior.
User response: Validate whether this adapter is a
System action: None. Fibre Channel SCSI adapter or not, and if it is, contact
User response: Set the user limit so that it is equal to hardware support for the adapter.
or greater than the recommended minimum value.
ANR3626W ANR3633I
System action: The only administrator with system

ANR3626W A check condition occurred during a
level authority uses LDAP authentication.
small computer system interface (SCSI)
inquiry at Fibre Channel port WWN=fc User response: Consider having one administrator
port wwn, KEY=sense key, ASC=asc, with system authority and LOCAL authentication. If
ASCQ=ascq. this is not possible, validate that the high availability
configurations for the LDAP server are sufficient.
Explanation: The host bus adapter (HBA) API
function failed to query the SCSI information of a
device located at this port. A hardware error or SCSI ANR3630E Command: The condition condition will
bus reset might have occurred during the operation. conflict with existing status threshold
threshold with condition condition.
System action: The HBAAPI inquiry function was
unable to retrieve the SCSI device information from this Explanation: The command indicated has attempted
port. to define or update a status threshold that will conflict
with an existing threshold.
User response: Verify that the adapter, device, and
Fibre Channel are connected. For more information System action: The status threshold is not defined or
about the values of the KEY, ASC, and ASCQ fields, see updated.
the SCSI specification.
User response: Either delete the existing threshold or
use a different condition.
ANR3627I Alerts cannot be sent by email.
Explanation: You must enable the alert monitor and ANR3631E The database is not intact.
email option to receive alerts by email.
Explanation: The server failed to start because the
System action: Server processing continues. database was not intact.
User response: Configure the server alert settings with System action: Server initialization fails.
the following commands:
User response: If this is a new installation or
SET ALERTMONITOR ON configuration, confirm that the DSMSERV FORMAT
step was completed successfully. If this is an existing
SET ALERTEMAIL ON
configuration that was previously working, a database
restore might be required.
ANR3628E The monitor status process has
encountered an unexpected error setting
ANR3632E command: The administrator administrator
the status of element element. The
ID is locked.
process returned error code rc.
Explanation: The administrator ID is locked and
Explanation: The process that monitors server activity
cannot be used in this command.
has detected an error setting the element status.
User response: Unlock the administrator ID and
ANR3629W All administrators with system level

ANR3633I Process process ID skipped volume
authority use LDAP authentication.
Volume Name because the volume
Administrator admin was the most recent
contains files that have not been backed
administrator with system level
up.
authority that used LOCAL
authentication. Explanation: The DEDUPREQUIRESBACKUP server
option is set to the default value of YES. If the value of
Explanation: All administrator with system level
this option is YES, files within a deduplicated storage
authority use LDAP authentication. This situation has
pool must be backed up to a non-deduplicated copy
risks, based on the availability of the LDAP server. If
storage pool before the files can be reclaimed.
required, make sure that the LDAP server has high
availability configurations implemented. For example: System action: The operation skips the volume and
clustering, mirroring, or replication. Having one continues.
system-level administrator with LOCAL authentication
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.
However, changing the option value to NO can result

ANR3634W ANR4004I
in unrecoverable data loss if a data-integrity error recover from this situation, first retry the database load
occurs. process. If the error reoccurs, check the activity log or
other system logs to determine if there is a hardware or
media error. If a hardware or media error exists, correct
ANR3634W The HBA API cannot provide tape
the error and retry the load process. If a hardware or
device information from the SAN.
media error does not exist, it is likely the dump or
System action: No action is required. unload of the server database has encountered an error
resulting in the dump/unload server database image as
User response: Check the connections between the being unusable or that there is an error in the logic for
Fibre Channel cables and the tape device settings to load db processing. Contact your service representative
ensure that the tape devices can be presented to the for assistance.
system first. Contact the HBA vendor to report
problems if the QUERY SAN command cannot retrieve
tape device information when tape devices are ANR4000I Dump command: Database dump process
presented to the system. started.
Explanation: The database dump process has started.
ANR3635I The status monitor has updated the
System action: The server dumps the contents of the
event record retention period to 14 days.
database to a file or removable media.
Explanation: To provide full functionality for the
Operations Center, the server must retain event records
for a minimum of 14 days.
ANR4001I Dump command: Database dump process
System action: Event records will be retained for 14
completed.
days.
Explanation: The database dump process has ended.
User response: Use the SET EVENTRETENTION
command if a different value is desired. System action: The server completes processing.
ANR4002I Dump command: Database dump process
platform) - the key is already defined.
terminated due to error (error indicator).
Explanation: The server ends the transaction because
Explanation: The database dump process has ended
the key is already defined in the database.
prematurely due to an error.
System action: The server ends dump processing.
User response: Make sure the key is unique.
User response: Examine previously issued messages
to determine if an error can be corrected, such as an
ANR3637W Transaction failed for session session output error. If you cannot resolve the error, contact
number for node node name (client your service representative.
platform) - the key is not defined.
Explanation: The server ends the transaction because ANR4003I Load command: Database load process
the key is already defined in the database. started.
System action: Server operation continues. Explanation: The database load process has started.
User response: Make sure the key is defined. System action: The server loads the contents of the
database from a file or removable media.
ANR3999E Failure validating database load: User response: None.
expected numRecs records and numBV bit
vectors - loaded actNumRecs records and
ANR4004I Load command: Database load process
actNumBV bit vectors.
completed.
Explanation: The database load process has ended
Explanation: The database load process has ended.
and the number of records, the number of bit vectors,
or both the number of records or number of bit vectors System action: The server completes processing.
loaded, failed to validate.
System action: The LOAD DB process completes with
a failure. The server database is not in a usable state.
User response: A number of possible causes exist. To
ANR4005E ANR4013I

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 servers 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 volumes 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
servers 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. ANR4011W Dump command: Database page page
User response: Examine previously issued messages number is invalid - it will be skipped.
to determine if there is an error that can be corrected, Explanation: The specified page is invalid, and it will
such as a syntax error. If you cannot resolve the error, not be used during dump processing.
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.
ANR4012W Dump command: Database page page

ANR4008W Load command: Database object object
number is damaged.
name does not exist.
Explanation: The specified database page is damaged;
Explanation: The database load process attempts to
it will not be dumped.
delete a database object, but the object does not exist.
System action: Database processing continues.
ANR4013I Dump command: Dumped number of

ANR4009E Load command: Database object object
entries database entries (cumulative).
name cannot be deleted because it is in
use by another process. Explanation: This message indicates the number of
database entries that have been dumped so far during
Explanation: The database load process attempts to
database dump processing.
delete a database object, but the object is currently
being used by another process. System action: Server processing continues.
System action: Database processing ends. User response: None.
User response: Reissue the command. If it fails,

ANR4014E ANR4022E
ANR4014E Load command: The specified input ANR4018E Load command: Load processing failed -
volume does not contain a server insufficient recovery log space.
database dump.
Explanation: The load process fails due to insufficient
Explanation: The specified volume does not contain a recovery log space.
dump created from the database dump command.
System action: Database load processing ends.
User response: Reinstall the server and specify a
User response: None. larger recovery log and reissue the database load
command.
ANR4015E Load command: Invalid record format
(format code) detected. ANR4019E Load command: Load processing failed -
insufficient database space.
Explanation: During processing of command load
command, an invalid record type is detected when Explanation: The load process fails due to insufficient
reading the dumped information from the dump database space.
media.
System action: Load processing ends.
User response: Reinstall the server and specify a
User response: Examine the server messages issued larger database and reissue the database load
prior to this message to determine the source of the command.
error. On MVS or VM, the LOADDB command syntax
may be specified by using a ddname or by specifying a
ANR4020E Load command: Batch database insert
device class name. You must use the same method that
failed.
was used when the database was originally dumped. If
you did not, this error message will be displayed. Try Explanation: The database load process fails when it
loading the database by using the other method of attempts to insert a batch of rows into the database.
syntax (devclass). If the error cannot be isolated and
resolved, contact your service representative. System action: Database load processing ends.
ANR4016E Load command: Invalid header sequence this one to determine if an error can be corrected. You
number detected in database dump. may wish to reinstall the server with a new recovery
Expected expected sequence number; Actual log and database and reissue the load command. If the
actual sequence number. problem persists, contact your service representative.
Explanation: During processing of command load

command, an invalid sequence number is detected when ANR4021E Dump/load command: Error (error code)
reading the dumped information from the dump occurred during an open operation.
media. Explanation: An error occurs while attempting an
System action: Processing of the command ends. open operation on the dump media for a database
dump/load operation.
User response: Examine previously issued server
messages to determine the source of the error. If the System action: Server processing continues.
error cannot be isolated and resolved, contact your User response: Refer to the other displayed messages
service representative. to determine why the operation failed; correct the
problem and restart the process.
ANR4017E Load command: Invalid record type record
type read from database dump data. ANR4022E Dump command: Error (error code)
Explanation: The server database load process occurred during a write operation.
encounters an invalid record in reading data from the Explanation: The server database dump process
dump media. encounters an error while writing to the dump media.
System action: The database load process ends. System action: Server processing continues, the dump
User response: Examine previously issued server processing ends.
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.
ANR4023E ANR4034I
ANR4023E Load command: Error (error code) occurred ANR4029I Dump command: Database checkpoint
during a read operation. started.
Explanation: The server database load process Explanation: The database dump process is flushing
encounters an error reading from the dump media. updated database pages from the database buffer pool
to stable storage so that they can be dumped.
System action: The database load operation ends.
System action: Database dump processing continues.
User response: Refer to the other displayed messages
to determine why the operation failed; correct the User response: None.
ANR4030I Dump command: Database checkpoint
ANR4025I Dumped number of pages database pages, completed.
number of bit vectors bit vectors, and
Explanation: The database dump process has flushed
number of database entries database entries;
all updated pages from the database buffer pool to
number of bad pages bad database pages
stable storage.
have been encountered; number of bytes
copied. System action: Database load processing continues.
Explanation: This message is displayed in response to User response: None.
a QUERY PROCESS command executed against an
online database dump process. The message displays
information about the progress of the dump. ANR4031I Dump/load command: Copied number of
pages database pages.
System action: Database dump processing continues.
Explanation: This message is displayed at the end of a
User response: None. You may cancel the dump server database dump or load command to indicate the
process with the CANCEL PROCESS command. number of database pages copied.
System action: Database dump or load processing
ANR4026I Dump command: Process process number, ends.
database dump has completed.
Explanation: The online server database dump process
started as process process number has completed.
ANR4032I Dump/load command: Copied number of
System action: Database dump processing ends. records database records.
User response: None. Explanation: This message is displayed at the end of a
server database dump or load command to indicate the
number of database records copied.
ANR4027I Dump command: Process process number,
database dump was canceled. System action: Database dump or load processing
ends.
Explanation: The online server database dump process
started as process process number has been canceled User response: None.
with the CANCEL PROCESS command.
System action: Database dump processing ends. ANR4033I Dump/load command: Copied number of bit
vectors bit vectors.
ANR4028I Dump command: Process process number,
number of database bit vectors copied.
Database dump terminated due to an
error (error code). System action: Database dump or load processing
ends.
Explanation: The online database dump process has
ended prematurely due to an error. User response: None.
System action: The server ends dump processing.
ANR4034I Dump/load command: Encountered number
of bad database pages bad database pages.
this message to see if an error can be corrected, such as
output error. If you cannot resolve the error, contact Explanation: This message is displayed at the end of a
your service representative. server database dump or load command to indicate the
number of invalid database pages that have been
encountered.

ANR4035I ANR4043I

ANR4040I Audit command: Auditing client node and
ends.
administrator definitions.
database audit and indicates that the client node and
ANR4035I Dump/load command: Encountered number administrator definitions are being examined by the
of bad database records bad database database audit process.
records.
number of invalid database records that have been
encountered. ANR4041I Audit command: Node node name is
assigned to Domain domain name, but
not verified by server database policy
ends.
entries.
Explanation: A database audit process finds a node
assigned to a policy domain that is not recorded
ANR4036I Dump/load command: Copied number of properly in policy database entries.
database entries database entries.
User response: If FIX=YES has not been specified for
the audit command, you may want to run this
number of database entries that have been copied.
command again, and specify FIX=YES so that the audit
System action: Database dump or load processing process can correct the policy domain assignment for
ends. the node.

ANR4042I Audit command: Node node name is
assigned to Domain domain name, but
ANR4037I Dump/load command: number of bytes not found in server database policy
copied. entries - attempting to assign the node
Explanation: This message is displayed at the end of a to domain domain name.
server database dump or load command to indicate the Explanation: A database audit process finds a node
number of bytes that have been copied. assigned to a policy domain that cannot be referenced
System action: Database dump or load processing in database policy entries. Because FIX=YES has been
ends. specified for the audit command, the audit function
will attempt to correct the policy domain assignment
User response: None. for the node.
ANR4038I Load command: Loading database
information dumped on dump date at User response: When the audit command completes,
dump time. you may want to check the domain assignment for this
node, and reassign the node to a different policy
Explanation: At the beginning of a server database domain, if desired.
load process, this message indicates the date and time
that the dump took place for the database information
that is loaded into the server. ANR4043I Audit command: Node node name
assignment failed - will attempt to
System action: Database load processing continues. assign the node to domain domain name.
User response: None. Explanation: A database audit process finds a node
assigned to a policy domain that cannot be located in
ANR4039I Load command: Loaded number of entries database policy entries. Because FIX=YES has been
database entries (cumulative). specified for the audit command, the audit function is
attempting to assign the node to an existing policy
Explanation: This message indicates the number of domain. The function attempts to assign the node to
database entries that have been loaded so far during the domain name specified.
database load processing.
System action: Database load processing continues.
User response: When the audit command completes,
ANR4044I ANR4051I
you may want to check the domain assignment for this

ANR4048I Audit command: Invalid archive delete
node, and reassign the node to a different policy
value encountered for node node name
domain, if desired.
the default value will be set.
Explanation: A database audit process encounters an
ANR4044I Audit command: Could not assign Node
invalid archive delete permission value for the node
node name to a policy domain; use the
indicated. Because FIX=YES has been specified, the
UPDATE NODE command to assign a
audit function sets the nodes archive delete permission
policy domain for this node.
value to the default value.
Explanation: A database audit process cannot find an
appropriate policy domain for assigning the specified
node. User response: If you want the archive delete value
for the specified node to be set to a value other than
the default, use the UPDATE NODE command to
User response: When the audit command completes, change the value after the audit command has
use the UPDATE NODE command to assign the completed.
specified node to an appropriate policy domain.
ANR4049I Audit command: Invalid backup delete
ANR4045I Audit command: Invalid compression value encountered for node node name.
value encountered for node node name.
Explanation: A database audit process encounters an invalid backup delete permission value for the node
invalid node compression value for the node indicated. indicated.
System action: Audit processing continues. System action: Audit processing continues.
User response: If FIX=YES has not been specified for User response: If FIX=YES has not been specified for
the audit command, you may want to run this the audit command, you may want to run this
command again, and specify FIX=YES so that the audit command again, and specify FIX=YES so that the audit
process can correct the problem. process can correct the problem.
ANR4046I Audit command: Invalid compression ANR4050I Audit command: Invalid backup delete
value encountered for node node name value encountered for node node name
the default value will be set. the default value will be set.
Explanation: A database audit process encounters an Explanation: A database audit process encounters an
invalid node compression value for the node indicated. invalid backup delete permission value for the node
Because FIX=YES has been specified, the audit function indicated. Because FIX=YES has been specified, the
sets the nodes compression value to the default value. audit function sets the nodes backup delete permission
value to the default value.
User response: If you want the compression value for
the specified node to be set to a value other than the User response: If you want the backup delete value
default, use the UPDATE NODE command to change for the specified node to be set to a value other than
the value after the audit command has completed. the default, use the UPDATE NODE command to
change the value after the audit command has
completed.
ANR4047I Audit command: Invalid archive delete
value encountered for node node name.
ANR4051I Audit command: Invalid lock state
Explanation: A database audit process encounters an encountered for node node name.
invalid archive delete permission value for the node
indicated. Explanation: A database audit process encounters an
invalid lock state value for the node indicated.
the audit command, you may want to run this User response: If FIX=YES has not been specified for
command again, and specify FIX=YES so that the audit the audit command, you may want to run this
process can correct the problem. command again, and specify FIX=YES so that the audit
process can correct the problem.

ANR4052I ANR4059E
ANR4052I Audit command: Invalid lock state ANR4056I Audit command: Invalid lock state
encountered for node node name the encountered for administrator
node will be unlocked. administrator name the administrator will
be unlocked.
invalid lock state value for the node indicated. Because Explanation: A database audit process encounters an
FIX=YES has been specified, the audit function sets the invalid lock state value for the administrator indicated.
nodes lock state to unlocked. Because FIX=YES has been specified, the audit function
sets the administrators lock state to unlocked.
User response: If you want the lock state for the
specified node to be set to a value other than unlocked, User response: If you want the lock state for the
use the LOCK NODE command to change the value specified administrator to be set to a value other than
after the audit command has completed. unlocked, use the LOCK ADMIN command to change
the value after the audit command has completed.
ANR4053I Audit command: Invalid Node conversion
state encountered for node node name. ANR4057E Audit command: Administrative global
attributes are missing.
invalid Node conversion state value for the node Explanation: A database audit process finds that the
indicated. global attributes used for server administrative
activities are missing.
the audit command, you may want to run this User response: Reissue the audit command with
command again, and specify FIX=YES so that the audit FIX=YES specified so that the administrative global
process can correct the problem. However, next time attributes can be recreated.
this node logs onto the server, the node conversion
state will be reset.
ANR4058I Audit command: Administrative global
attributes are missing - default values
ANR4054I Audit command: Invalid conversion state will be used to recreate the attributes.
encountered for node node name the
node will be reset.
global attributes used for server administrative
Explanation: A database audit process encounters an activities are missing. Because FIX=YES has been
invalid conversion state value for the node indicated. specified on the AUDIT command, default attribute
Because FIX=YES has been specified, the audit function values will be used to recreate the administrative global
resets the conversion state. attributes.
User response: None. User response: When the audit completes, you can
values set for the administrative global attributes, and
ANR4055I Audit command: Invalid lock state
use the appropriate SET command to change the
encountered for administrator
attributes, if desired.
administrator name.
ANR4059E Audit command: Administrative ID
invalid lock state value for the administrator indicated.
assignments are incorrect.
User response: If FIX=YES has not been specified for global attributes used for server administrative
the audit command, you may want to run this activities are incorrect.
process can correct the problem.
FIX=YES specified so that the administrative global
attributes can be corrected.
ANR4060I ANR4067E
ANR4060I Audit command: Administrative ID ANR4064I Audit command: Client node node number
assignments are incorrect - value(s) will created as node node name assigned to
be corrected. policy domain domain name in the server
database.
global attributes used for server administrative Explanation: A database audit process finds a client
activities are incorrect. Because FIX=YES has been node reference that is not defined correctly in the
specified on the AUDIT command, the attribute value server database. Because FIX=YES has been specified
will be corrected in the server database. for the audit command, the audit function creates a
new node definition for the node with the name
specified.
User response: After the AUDIT command completes,
ANR4061E Audit command: Administrative global
use the QUERY NODE command to examine the node
attribute(s) are incorrect.
that was added. Use the RENAME NODE command to
Explanation: A database audit process finds that the rename the corrected node and the UPDATE NODE
global attributes used for server administrative command to set attributes for the corrected node, such
activities are incorrect. as its password. You can issue the QUERY FILESPACE
command for the node, to determine which node and
System action: Audit processing continues. platform type was originally represented by the
User response: Reissue the audit command with corrected node.
FIX=YES specified so that the administrative global
attributes can be corrected. ANR4065E Audit command: Administrator
administrator number not found in the
ANR4062I Audit command: Administrative global server database.
attribute(s) are incorrect - default values Explanation: A database audit process finds an
will be set. administrator reference that is not defined correctly in
Explanation: A database audit process finds that the the server database.
global attributes used for server administrative System action: Audit processing continues.
activities are incorrect. Because FIX=YES has been
specified on the AUDIT command, default attribute User response: Reissue the audit command and
values will be used to correct the administrative global specify FIX=YES so that the error can be corrected.
attributes.
System action: Audit processing continues. ANR4066I Audit command: Administrator
administrator number not found in the
User response: When the audit completes, you can server database - reference will be
use the QUERY STATUS command to examine the removed.
values set for the administrative global attributes, and
use the appropriate SET command to change the Explanation: A database audit process finds an
attributes, if desired. administrator reference that is not defined correctly in
the server database. The invalid reference will be
removed from the database.
ANR4063E Audit command: Client node node number
not found in the server database. System action: Audit processing continues.
Explanation: A database audit process finds a client User response: After the audit command completes,
node reference that is not defined correctly in the review your administrator definitions with the QUERY
server database. ADMIN command. You can then use the REGISTER
ADMIN and UPDATE ADMIN commands to change
System action: Audit processing continues. any definitions desired.
User response: If the audit command has not been
issued with FIX=YES specified, reissue the audit ANR4067E Audit command: Domain domain name
function specifying FIX=YES so that the error can be referenced by an administrator authority
corrected. does not exist.
Explanation: A database audit process finds a policy
administrator reference to a policy domain that does
not exist.

ANR4068I ANR4076E
User response: Reissue the audit command and process can correct the problem.
ANR4072I Audit command: Invalid file aggregation
ANR4068I Audit command: Policy domain domain information encountered for node node
name referenced by an administrator name.
authority does not exist - the authority
Explanation: A database audit process encounters
will be removed.
invalid information used for controlling aggregation of
Explanation: A database audit process finds a policy files for the node indicated.
administrator reference to a policy domain that does
not exist. Because FIX=YES has been specified, the
authority will be removed. User response: If FIX=YES has not been specified for
the audit command, you may want to run this
User response: After the audit command completes, process can correct the problem.
review your administrator definitions with the QUERY
ADMIN command. You can then use the REGISTER
ANR4073I Audit command: Invalid file aggregation
ADMIN, UPDATE ADMIN, and GRANT AUTHORITY
information encountered for node node
commands to change any definitions.
name - information will be corrected.
ANR4069E Audit command: Storage pool storage pool
invalid information used for controlling aggregation of
name referenced by an administrator
files for the node specified. Because FIX=YES has been
authority does not exist.
specified, the audit function corrects the information.
Explanation: A database audit process finds a storage
administrator reference to a storage pool that does not
exist. User response: None.
ANR4074I Dump/load command: Encountered number
User response: Reissue the audit command and
of entries bad database entries.
ANR4070I Audit command: Storage pool storage pool
number of invalid database entries that have been
name referenced by an administrator
encountered.
authority does not exist - the authority
will be removed. System action: Database dump or load processing
ends.
administrator reference to a storage pool that does not User response: None.
exist. Because FIX=YES has been specified, the
authority will be removed.
ANR4075I Audit command: Auditing policy
System action: Audit processing continues. definitions.
User response: After the audit command completes, Explanation: This message is displayed during a
review your administrator definitions with the QUERY database audit and indicates that the server policy
ADMIN command. You can then use the REGISTER information (domain, policy set, management classes,
ADMIN, UPDATE ADMIN, and GRANT AUTHORITY and copy groups) are being examined by the database
commands to change any definitions. audit process.
ANR4071I Audit command: Invalid sign-on attempts
is not valid for node/administrator name. User response: None.

invalid sign-on attempts value that is not valid for the ANR4076E Audit command: Invalid client node count
node or administrator indicated. detected for policy domain domain name.
System action: Audit processing continues. Explanation: A database audit process finds that the
count of nodes recorded for the specified policy
User response: If FIX=YES has not been specified for domain do not match the actual number of nodes
the audit command, you may want to run this assigned to the domain.
ANR4077I ANR4085I
User response: Reissue the audit command and incorrect grace period retention value for the specified
specify FIX=YES so that the error can be corrected. policy domain. Because FIX=YES has been specified for
the audit command, the default value will be set.
ANR4077I Audit command: Invalid client node count System action: Audit processing continues.
detected for policy domain domain name
count will be corrected.
ANR4082E Audit command: Invalid grace period
count of nodes recorded for the specified policy
archive retention value encountered for
domain do not match the actual number of nodes
assigned to the domain. Because FIX=YES has been
specified for the command, the node count will Explanation: A database audit process finds an
automatically be corrected. incorrect grace period retention value for the specified
policy domain.
ANR4078E Audit command: Invalid activation
indicators encountered for policy
domain domain name. ANR4083I Audit command: Invalid grace period
archive retention value encountered for
Explanation: A database audit process finds incorrect
policy domain domain name - default
policy set activation entries for the specified policy
value will be set.
domain.
Explanation: A database audit process finds an
incorrect grace period retention value for the specified
User response: Reissue the audit command and policy domain. Because FIX=YES has been specified for
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
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 ANR4094E
ANR4086E Audit command: Invalid node node number ANR4090E Audit command: Active Policy set for
found assigned to domain domain name. domain domain name does not contain a
valid default management class - policy
will fail for this domain. Correct the
number assigned to a policy domain that does not
ACTIVE policy set.
reference a valid client node definition.
Explanation: A database audit process finds an active
policy set for the specified policy domain that does not
User response: Reissue the audit command and have a valid active management class specified.
ANR4087I Audit command: Invalid node node number
you must activate a new policy set for the domain with
found assigned to domain domain name
a valid default management class.
reference will be deleted.
ANR4091E Audit command: Invalid administrator
number assigned to a policy domain that does not
reference a valid client node definition. Because
policy set set name in policy domain
domain name.
reference will be deleted.
last updated information for the specified policy set.
ANR4088E Audit command: Default management
class management class name specified for
policy set policy set name in domain
domain name does not exist. ANR4092I Audit command: Invalid administrator
policy set set name in policy domain
set with a default management class specified that does
domain name - information will be
not exist.
corrected.
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. Because FIX=YES has been specified for the command,
the information is corrected.
ANR4089I Audit command: Default management System action: Audit processing continues.
class management class name specified for
policy set policy set name in domain
domain name does not exist - the
reference will be removed. ANR4093E Audit command: A management class
identifier is not defined for
set with a default management class specified that does
in policy set set name, domain domain
not exist. Because FIX=YES has been specified for the
name.
audit command, the reference will be removed from the
policy set. Explanation: A database audit process finds incorrect
information for the specified management class.
examine the policy set specified, and set a new default User response: Reissue the audit command and
management class for the set. If the policy set is the specify FIX=YES so that the error can be corrected.
ACTIVE policy set, you must activate a new policy set
for the domain with a valid default management class.
ANR4094E Audit command: A management class
identifier is not defined for
in policy set set name, domain domain
name - an identifier will be generated
for this management class.
ANR4095E ANR4102I
Explanation: A database audit process finds incorrect last updated information for the specified management
information for the specified management class. The class. Because FIX=YES has been specified for the
audit process generates an identifier, because FIX=YES command, the information is corrected.
has been specified for the audit command.
ANR4099E Audit command: Copy group copy group
ANR4095E Audit command: An invalid management name in management class management
class identifier (actual identifier) was class name, policy set set name, domain
encountered for management class domain name has an invalid name or
management class name in policy set set type.
name, domain domain name (expected
Explanation: A database audit process encounters a
expected identifier).
copy group that has an invalid name or copy group
Explanation: A database audit process finds incorrect type.
information for the specified management class.
User response: Reissue the audit command and the audit command, reissue the command specifying
specify FIX=YES so that the error can be corrected. FIX=YES so that the error can be corrected.
ANR4096E 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 management class group.
management class name in policy set set
name, domain domain name (expected
expected identifier) - the correct identifier
type. The process attempts to reinsert the definition as
will be stored.
a backup copy group.
information for the specified management class. The
audit process corrects the identifier, because FIX=YES User response: None.
has been specified for the audit command.
System action: Audit processing continues. ANR4101I Audit command: A backup copy group
already exists - the invalid copy group
will be deleted.
type. While attempting to reinsert the copy group as a
backup copy group, the process discovers that a
in policy set set name in policy domain
backup copy group already exists for the management
domain name.
class. The copy group is deleted.
last updated information for the specified management
class. User response: After the audit command completes,
you may examine the server copy groups using the
QUERY COPYGROUP command, and correct them
User response: Reissue the audit command and with the DEFINE COPYGROUP and UPDATE
specify FIX=YES so that the error can be corrected. COPYGROUP commands if desired.
ANR4098I Audit command: Invalid administrator ANR4102I Audit command: Attempting to reinsert
update information encountered for the copy group as an ARCHIVE copy
management class management class name group.
in policy set set name in policy domain
domain name - information will be
corrected.
type. The process attempts to reinsert the definition as
Explanation: A database audit process finds incorrect an archive copy group.

ANR4103I ANR4110E
User response: None. User response: For programming support, contact
ANR4103I Audit command: An archive copy group
already exists - the invalid copy group ANR4107E Audit command: An invalid copy group
will be deleted. identifier (actual identifier) was
encountered for copy group name copy
group name (expected expected identifier).
type. While attempting to reinsert the copy group as an Explanation: A database audit process finds incorrect
archive copy group, the process discovers that a backup information for the specified copy group name.
copy group already exists for the management class.
The copy group is deleted.
User response: For programming support, contact
User response: After the audit command completes,
you may examine the server copy groups using the
ANR4108E Audit command: Invalid backup copy
QUERY COPYGROUP command, and correct them
group attributes encountered for copy
with the DEFINE COPYGROUP and UPDATE
group copy group name in management
COPYGROUP commands, if desired.
class management class name, policy set set
name, domain domain name.
ANR4104E Audit command: An invalid management
class identifier (actual identifier) was
invalid backup copy group attributes for the specified
encountered for a copy group in
copy group.
management class management class name,
policy set set name, domain domain name System action: Audit processing continues.
(expected expected identifier).
Explanation: A database audit process finds incorrect the audit command, reissue the command specifying
information for the specified copy group. FIX=YES so that the inconsistency can be corrected.
ANR4109I Audit command: Invalid backup copy
group attributes encountered for copy
ANR4105E Audit command: An invalid management name, domain domain name - the copy
class identifier (actual identifier) was group will be corrected using default
encountered for a copy group in attributes.
policy set set name, domain domain name
invalid backup copy group attributes for the specified
(expected expected identifier) - the correct
copy group. Because FIX=YES has been specified for
identifier will be stored.
the command, the copy group will be corrected using
Explanation: A database audit process finds incorrect default values for the attributes found in error.
information for the specified copy group. The audit
process corrects the identifier, since FIX=YES has been
specified for the audit command. User response: After the audit command completes,
examine the copy group by using the QUERY
COPYGROUP command, and correct attributes with
User response: None. the UPDATE COPYGROUP command, if desired.
ANR4106E Audit command: An invalid copy group ANR4110E Audit command: Invalid archive copy
identifier (actual identifier) was group attributes encountered for copy
encountered for a copy group in group copy group name in management
management class management class name, class management class name, policy set set
policy set set name, domain domain name name, domain domain name.
(expected expected identifier).
Explanation: A database audit process finds incorrect invalid archive copy group attributes for the specified
information for the specified copy group. copy group.
ANR4111I ANR4117E

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

ANR4117E Audit command: Policy set set name in
domain domain name is referenced, but
copy group copy group name in
not formally defined.
policy set set name, policy domain domain Explanation: A database audit process finds a
name. reference to the specified policy set, but the set is not
formally defined in the server database.
last updated information for the specified copy group. System action: Audit processing continues.
System action: Audit processing continues. User response: Reissue the audit command and

ANR4118I ANR4126E

ANR4118I Audit command: Policy set set name in
domain domain name is referenced, but User response: Reissue the audit command and
not formally defined - a policy set with specify FIX=YES so that the error can be corrected.
this name will be created.
Explanation: A database audit process finds a ANR4123I Audit command: The instance count for
reference to the specified policy set, but the set is not management class class name does not
formally defined in the server database. Because agree with the actual management class
FIX=YES has been specified, the audit process will data (number of instances instances) - the
create a new policy set with this name. number will be corrected.
reference count for the specified management class that
User response: After the audit command has
does not match the actual number of instances for this
completed, you can view the attributes for this policy
class. The audit process corrects the count because
set by using the QUERY POLICYSET command, and
FIX=YES has been specified for the audit command.
update attributes with the UPDATE POLICYSET
command, if desired. System action: Audit processing continues.
ANR4119E Audit command: Management class class
name in policy set set name, domain
domain name is referenced, but not ANR4124E Audit command: The instance count for
formally defined. copy group copy group name does not
agree with the actual copy group data
Explanation: A database audit process finds a (number of instances instances).
reference to the specified management class, but the
class is not formally defined in the server database. Explanation: A database audit process finds a
reference count for the specified copy group that does
System action: Audit processing continues. not match the actual number of instances for this copy
group.
specify FIX=YES so that the error can be corrected. System action: Audit processing continues.
ANR4120I Audit command: Management class class specify FIX=YES so that the error can be corrected.
domain name is referenced, but not
formally defined - the management class ANR4125I Audit command: The instance count for
will be created. copy group copy group name does not
agree with the actual copy group data
Explanation: A database audit process finds a (number of instances instances) - the
reference to the specified management class, but the number will be corrected.
class is not formally defined in the server database.
Because FIX=YES has been specified for the audit Explanation: A database audit process finds a
command, the audit process defines a management reference count for the specified copy group that does
class in the server with this name. not match the actual number of instances for this copy
group. The audit process corrects the count because
System action: Audit processing continues. FIX=YES has been specified for the audit command.
User response: After the audit command has System action: Audit processing continues.
completed, you can view the attributes for this
management class by using the QUERY MGMTCLASS User response: None.
command, and update attributes with the UPDATE
MGMTCLASS command, if desired. ANR4126E Audit command: Policy global attributes
cannot be found.
ANR4122E Audit command: The instance count for Explanation: A database audit process is not able to
management class class name does not locate the global attributes for policy information in the
agree with the actual management class server database.
data (number of instances instances).
reference count for the specified management class that User response: Reissue the audit command and
did not match the actual number of instances for this specify FIX=YES so that the error can be corrected.
class.
ANR4127I ANR4133I

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

ANR4134I ANR4142I
the database if the audit volume process cannot access System action: Audit processing continues.
the files due to hardware problems (for example, dirty
tape heads).
ANR4138I Audit command: Auditing inventory
User response: If you suspect that files were backup objects.
inaccessible because of hardware problems such as
dirty tape heads, correct the hardware problem and
database audit and indicates that server information
reissue the AUDIT VOLUME FIX=NO command for
about client backup objects is currently being examined
this volume. To remove damaged file references and
by the database audit process.
update the object information, issue the AUDIT
VOLUME command and specify FIX=YES. System action: Audit processing continues.
ANR4134I AUDITDB: Processed number of entries
entries in database tables and number of
blocks blocks in bit vectors. Elapsed time ANR4139I Audit command: Auditing inventory
is elapsed time. archive objects.
Explanation: This message reports the progress of a Explanation: This message is displayed during a
database audit operation. While auditing database database audit and indicates that server information
tables, the number of entries processed will increase, about client archive objects is currently being examined
but the number of blocks processed in bit vectors will by the database audit process.
not increase. While auditing bit vectors, the number of System action: Audit processing continues.
blocks processed will increase, but the number of
entries processed will not increase. The number of User response: None.
entries and the number of blocks are cumulative for the
entire audit operation. The elapsed time of the audit ANR4140I Audit command: Database audit process
operation is reported in hours, minutes, and seconds. started.
System action: Database audit processing continues. Explanation: This message is displayed during a
User response: None. database audit and indicates that the audit process has
started.
ANR4135I Audit command: Auditing central System action: Audit processing continues.
scheduler definitions. User response: None.
database audit and indicates that the server scheduling ANR4141I Audit command: Database audit process
information is examined by the database audit process. completed.
System action: Audit processing continues. Explanation: This message is displayed during a
User response: None. database audit and indicates that the database audit
has successfully completed.
ANR4136I Audit command: Auditing server System action: Audit processing ends.
inventory. User response: None.
database audit and indicates that server information ANR4142I Audit command: Database audit process
about client file spaces is currently being examined by terminated in error.
the database audit process.
System action: Audit processing continues. database audit and indicates that the audit process
User response: None. ended prematurely due to an internal server database
error.
ANR4137I Audit command: Auditing inventory file System action: Audit processing ends.
spaces. User response: Examine the messages issued prior to
Explanation: This message is displayed during a this one to see if the error can be corrected. If the
database audit and indicates that server information situation cannot be resolved, contact your service
about client file spaces is currently being examined by representative.
the database audit process.
ANR4143E ANR4151E

ANR4143E Audit command: Central scheduler global
attributes cannot be found. User response: Reissue the audit command and
specify FIX=YES so that the administrative global
Explanation: A database audit process cannot locate
the global attributes for scheduling information in the
server database.
ANR4148I Audit command: Policy domain domain
name referenced by schedule schedule
User response: Reissue the audit command and name does not exist - the schedule will
specify FIX=YES so that the error can be corrected. be deleted.
ANR4144I Audit command: Central scheduler global schedule that references a policy domain that is not
attributes cannot be found - attributes defined in the server database. Because FIX=YES has
will be recreated. been specified for the audit command, the specified
schedule will be deleted from the server database.
Explanation: A database audit process cannot locate
the global attributes for scheduler information in the System action: Audit processing continues.
server database. Because FIX=YES has been specified
for the audit command, the attributes will be
regenerated.
ANR4149E Audit command: One or more attributes
for schedule schedule name in policy
User response: None. domain domain name are incorrect.
Explanation: A database audit process finds one or
ANR4145E Audit command: One or more central more invalid attributes for the specified schedule.
scheduler attributes are incorrect.
global attributes used for server scheduling activities
are incorrect.
User response: Reissue the audit command and ANR4150I Audit command: One or more attributes
specify FIX=YES so that the administrative global for schedule schedule name in policy
attributes can be corrected. domain domain name are incorrect -
default values will be set.
ANR4146I Audit command: One or more central Explanation: A database audit process finds one or
scheduler global attribute(s) are more invalid attributes for the specified schedule.
incorrect - default values will be set. Because FIX=YES has been specified for the audit
command the invalid attributes will be set to default
values.
global attributes used for server scheduling activities
are incorrect. Because FIX=YES has been specified on System action: Audit processing continues.
the AUDIT command, default attribute values will be
used to correct the scheduling global attributes.
use the QUERY SCHEDULE command to examine the
System action: Audit processing continues. values set for the schedule, and use the UPDATE
SCHEDULE command to change any attributes desired.
values set for the administrative global attributes, and ANR4151E Audit command: Schedule schedule name in
use the appropriate SET command to change the policy domain domain name not found,
attributes, if desired. but is referenced by a client node.
ANR4147E Audit command: Policy domain domain schedule reference from a client node for a schedule
name referenced by schedule schedule that is not defined in the server database.
name does not exist.
schedule that references a policy domain that is not

ANR4152I ANR4160I
last updated information for a schedule-node

ANR4152I Audit command: Schedule schedule name in
assignment. Because FIX=YES has been specified for
policy domain domain name not found,
the command, the information is corrected.
but is referenced by a client node - the
schedule association will be deleted. System action: Audit processing continues.
Explanation: A database audit process finds a User response: None.
schedule reference from a client node for a schedule
that is not defined in the server database. Because
FIX=YES has been specified for the audit command, the ANR4157E Audit command: Scheduling callback
schedule association will be deleted from the server address is registered for a client node
database. that does not exist.
server-prompted-scheduling callback address for a node
User response: None. that does not exist.
ANR4153E Audit command: Schedule schedule name in
policy domain domain name references a User response: Reissue the audit command and
client node that does not exist. specify FIX=YES so that the error can be corrected.

schedule that references a client node that is not ANR4158I Audit command: Scheduling callback
defined in the server database. address is registered for a client node
that does not exist - callback
System action: Audit processing continues. information will be deleted.
User response: Reissue the audit command and Explanation: A database audit process finds a
specify FIX=YES so that the administrative global server-prompted-scheduling callback address for a node
attributes can be corrected. that does not exist. Because FIX=YES has been specified
for the command, the callback information will be
deleted from the server database.
ANR4154I Audit command: Schedule schedule name in
policy domain domain name references a System action: Audit processing continues.
client node that does not exist - the
node reference will be deleted. User response: None.

schedule that references a client node that is not ANR4159I Audit command: An inventory
defined in the server database. Because FIX=YES has authorization rule specifies an invalid
been specified for the audit command, the reference node (node ID) or file space (filespace ID)
will be removed from the server database. - the rule will be deleted.
System action: Audit processing continues. Explanation: A database audit process finds that
either a node ID or file space ID is invalid for an
User response: None. authorization rule. Since FIX=YES has been specified,
the invalid authorization rule will be deleted.
ANR4155E Audit command: Invalid administrator System action: Audit processing continues.
update information encountered for a
schedule assignment. User response: None.

last updated information for a schedule-node ANR4160I Audit command: An inventory
assignment. authorization rule specifies an invalid
node (node ID) or file space (filespace ID).
Explanation: A database audit process finds that
User response: Reissue the audit command and either a node ID or file space ID is invalid for an
specify FIX=YES so that the error can be corrected. authorization rule.
ANR4156I Audit command: Invalid administrator
update information encountered for a User response: Reissue the audit command and
schedule assignment - information will specify FIX=YES so that the error can be corrected.
be corrected.
ANR4161I ANR4170I

ANR4161I Audit command: Inventory global
attributes could not be found - they will
be created. ANR4166I Audit command: An inventory node
assignment entry was not found for
Explanation: A database audit process cannot find the
node node ID.
inventory global attributes. Because FIX=YES has been
specified for the command, the information is corrected Explanation: A database audit process cannot find the
by the creation of the global attributes. node assignment entry corresponding to the specified
node.
ANR4162I Audit command: Inventory global
attributes could not be found.
ANR4167I Audit command: The file space
high-water mark for node node ID is
inventory global attributes.
incorrect - the value will be corrected.
Explanation: A database audit process finds that a file
User response: Reissue the audit command and space high-water mark is incorrect for the specified
specify FIX=YES so that the error can be corrected. node ID. Since FIX=YES has been specified for the
command, the information is corrected.
ANR4163I Audit command: Invalid object ID System action: Audit processing continues.
high-water mark encountered for
inventory global attributes - the value
will be corrected.
ANR4168I Audit command: The file space
high-water mark for node node ID is
object ID high-water mark for the inventory global
incorrect.
attributes is invalid. Because FIX=YES has been
specified for the command, the object ID high-water Explanation: A database audit process finds that a file
mark is determined by the current inventory and set space high-water mark is incorrect for the specified
accordingly. node ID.
User response: None. User response: Reissue the audit command and
ANR4164I Audit command: Invalid object ID
high-water mark encountered for ANR4169I Audit command: The file space
inventory global attributes. high-water mark for node node ID is
incorrect - the value will be corrected.
object ID high-water mark for the inventory global Explanation: A database audit process finds that an
attributes is invalid. authorization rule high-water mark is incorrect for the
specified node ID. Since FIX=YES has been specified for
the command, the information is corrected.
ANR4165I Audit command: An inventory node
assignment entry was not found for ANR4170I Audit command: The authorization rule
node node ID - an entry will be created. high-water mark for node node ID is
incorrect.
node assignment entry corresponding to the specified Explanation: A database audit process finds that an
node. Since FIX=YES has been specified for the authorization rule high-water mark is incorrect for the
command, the required inventory entry will be created specified node ID.
using default values.

ANR4171I ANR4180I
specify FIX=YES so that the error can be corrected. the information is corrected by deleting the expiring
object entry. The entry will be recreated later if it is
necessary.
ANR4171I Audit command: Primary backup entry for
an expiring object (object.ID) cannot be System action: Audit processing continues.
found - the expiring object entry will be
deleted.
ANR4176I Audit command: Invalid copy type
primary backup entry for the specified expiring object.
encountered for an expiring objects
Because FIX=YES has been specified for the command,
entry (object.ID).
the information is corrected by deleting the expiring
object entry. Explanation: A database audit process finds that the
copy type for the specified expiring object is invalid.
ANR4172I Audit command: Primary backup entry for
an expiring object (object.ID) cannot be
found. ANR4177I Audit command: Primary backup entry for
an object (object.ID) cannot be found -
entry will be deleted.
primary backup entry for the specified expiring object.
specified primary backup object. Because FIX=YES has
User response: Reissue the audit command and been specified for the command, the entry is deleted.
ANR4173I Audit command: Primary archive entry for
found - the expiring object entry will be ANR4178I Audit command: Primary backup entry for
deleted. an object (object.ID) cannot be found.
Explanation: A database audit process cannot find the Explanation: A database audit process cannot find the
primary archive entry for the specified expiring object. specified primary backup object.
the information is corrected by deleting the expiring System action: Audit processing continues.
object entry. User response: Reissue the audit command and
System action: Audit processing continues. specify FIX=YES so that the error can be corrected.

an object (object.ID) cannot be found -
ANR4174I Audit command: Primary archive entry for entry will be deleted.
found. Explanation: A database audit process cannot find the
specified primary archive object. Because FIX=YES has
Explanation: A database audit process cannot find the been specified for the command, the entry is deleted.
primary archive entry for the specified expiring object.
an object (object.ID) cannot be found.
encountered for an expiring objects Explanation: A database audit process cannot find the
entry (object.ID) - the expiring object specified primary archive object.
entry will be deleted. System action: Audit processing continues.
Explanation: A database audit process finds that the User response: Reissue the audit command and
copy type for the specified expiring object is invalid. specify FIX=YES so that the error can be corrected.
ANR4181I ANR4189I
ANR4181I Audit command: Invalid copy type ANR4185I Audit command: Object entry for backup
encountered for object object.ID - object object object.ID not found - entry will be
found as a backup object - correcting created.
the invalid copy type
Explanation: A database audit process encounters an object entry for the specified backup object. Because
invalid copy type for the specified object ID but finds a FIX=YES has been specified for the command, an object
corresponding backup object for the entry. Because entry is created using default values.
invalid copy type is corrected.
ANR4186I Audit command: Object entry for backup
object object.ID not found.
encountered for object object.ID - object
object entry for the specified backup object.
found as an archive object - correcting
the invalid copy type System action: Audit processing continues.
Explanation: A database audit process encounters an User response: Reissue the audit command and
invalid copy type for the specified object ID but finds a specify FIX=YES so that the error can be corrected.
corresponding archive object for the entry. Because
invalid copy type is corrected. ANR4187I Audit command: Inventory object fields
for object object.ID do not match the
System action: Audit processing continues. primary backup entry - the object will
be updated.
Explanation: A database audit process determines that
the object fields for the specified object ID do not
match the fields for the corresponding primary backup
encountered for object object.ID -
object. Because FIX=YES has specified for the
primary archive entry created for object
command, the incorrect object fields will be corrected.
invalid copy type for the specified object ID and is User response: None.
unable to find corresponding primary backup or
primary archive objects. Because FIX=YES has been
specified for the command, a primary archive entry is ANR4188I Audit command: Inventory object fields
created using default values. for object object.ID do not match the
primary backup entry.
User response: None. the object fields for the specified object ID do not
match the fields for the corresponding primary backup
object.
encountered for object object.ID. System action: Audit processing continues.
Explanation: A database audit process encounters an User response: Reissue the audit command and
invalid copy type for the specified object ID and is specify FIX=YES so that the error can be corrected.
unable to find corresponding primary backup or
primary archive objects.
ANR4189I Audit command: Expiring entry for
System action: Audit processing continues. inactive backup object object.ID not
found - the entry will be created.
specify FIX=YES so that the error can be corrected. Explanation: A database audit process cannot find an
expiring entry for the specified inactive backup entry.
an expiring entry will be created.

ANR4190I ANR4199I
ANR4190I Audit command: Expiring entry for ANR4195I Audit command: Expiring entry for
inactive backup object object.ID not archive object object.ID not found - the
found. entry will be created.
Explanation: A database audit process cannot find an Explanation: A database audit process cannot find an
expiring entry for the specified inactive backup entry. expiring entry for the specified archive object. Because
FIX=YES has been specified for the command, an
expiring entry will be created.
ANR4191I Audit command: Object entry for archive
object object.ID not found - entry will be ANR4196I Audit command: Expiring entry for
created. archive object object.ID not found.
Explanation: A database audit process cannot find an Explanation: A database audit process cannot find an
object entry for the specified archive object. Because expiring entry for the specified archive object.
information is corrected by creating an object entry.
ANR4197I Audit command: File space entry filespace
ANR4192I Audit command: Object entry for archive ID not found for node node ID.
Explanation: A database audit process cannot find a
Explanation: A database audit process cannot find an file space entry for the specified node.
object entry for the specified archive object.
User response: Reissue the audit command and specify FIX=YES so that the error can be corrected.
ANR4193I Audit command: Inventory object fields ID not found for node node name - an
for object object.ID do not match the entry will be created.
primary archive entry - the object will
be updated.
file space entry for the specified node. Because
Explanation: A database audit process determines that FIX=YES has been specified for the command, a file
the object fields for the specified object ID do not space entry has been created.
match the fields for the corresponding primary archive
object. Because FIX=YES has been specified for the
command, the incorrect object fields will be corrected. User response: None.
ID not found for node node ID - unable
to create an entry.
ANR4194I Audit command: Inventory object fields
for object object.ID do not match the
file space entry for the specified node ID. Because
primary archive entry.
FIX=YES has been specified for the command, the audit
Explanation: A database audit process determines that process has attempted to create a file space entry but is
the object fields for the specified object ID do not not successful.
match the fields for the corresponding primary archive
object.
User response: Contact your system administrator.
ANR4200I ANR4209I
ANR4200I Audit command: Expiring entry node ID ANR4205I Audit command: The insertion date value
and file space filespace ID does not match for archive entry object.ID is not valid.
the object entry for object ID object.ID -
the entry will be deleted.
the insertion date for the specified archive object is
Explanation: A database audit process determines that improperly formatted or contains incorrect information.
the specified expiring object entry does not match the
corresponding object entry for the specified object ID.
Because FIX=YES has been specified for the command, User response: Contact your system administrator.
the expiring object entry is deleted.
System action: Audit processing continues. ANR4206I Audit command: Object entry for expiring
object object.ID not found - expiring
object entry will be deleted.
ANR4201I Audit command: Expiring entry node ID
object entry corresponding to the specified expiring
and file space filespace ID does not match
object. Because FIX=YES has been specified for the
the object entry for object ID object.ID.
command, the expiring object entry for the specified
Explanation: A database audit process determines that object ID is deleted.
the specified expiring object entry does not match the
corresponding object entry for the specified object ID.
ANR4207I Audit command: Object entry for expiring
ANR4202I Audit command: The base date for
object entry corresponding to the specified expiring
expiration processing of entry object.ID is
object.
not valid - the entry will be deleted.
the specified expiring object has a date that is not valid. User response: Reissue the audit command and
Because FIX=YES has been specified for the command, specify FIX=YES so that the error can be corrected.
the expiring object entry is deleted.
System action: Audit processing continues. ANR4208I Audit command: An inventory node
assignment entry is not valid for node
node ID - the entry will be deleted.
Explanation: A database audit process finds that a
ANR4203I Audit command: The base date for
node assignment entry for the specified node ID is not
expiration processing of object object.ID
valid. Since FIX=YES has been specified for the
is not valid.
command, the required inventory entry is deleted.
the specified expiring object has a date value that is not
valid. User response: None.
ANR4209I Audit command: An inventory node
node node ID.
ANR4204I Audit command: One or more date values
node assignment entry for the specified node ID is not
for a backup entry object.ID is not valid.
valid.
one or more of the date values is improperly formatted
or contains incorrect information for the specified User response: Reissue the audit command and
backup object. specify FIX=YES so that the error can be corrected.
User response: Contact your system administrator.

ANR4210I ANR4218I
ANR4210I Audit command: Auditing physical ANR4215I Audit command: An object entry for
volume repository definitions. library library name and volume volume
name in the physical volume repository
is invalid.
database audit and indicates that the physical volume
repository definitions are being examined by the Explanation: A database audit process finds that a
database audit process. library inventory entry is missing a corresponding
library entry.
ANR4211I Audit command: Drive entry library name
for library drive name in the physical
volume repository is invalid. ANR4216I Audit command: An object entry for
library library name and volume volume
drive entry is missing a corresponding library entry.
is invalid - the entry will be deleted.
User response: Reissue the audit command and library inventory entry is missing a corresponding
specify FIX=YES so that the error can be corrected. library entry. Because FIX=YES has been specified for
the command, the invalid library inventory entry is
deleted.
ANR4212I Audit command: An object entry for
library library name and drive drive name System action: Audit processing continues.
in the physical volume repository is
invalid - the entry will be deleted.
ANR4217I Audit command: The volume status for
drive entry is missing a corresponding library entry.
library library name and volume volume
the invalid drive entry is deleted.
is invalid.
User response: None. volume status for the specified library and volume is
set to scratch. This is incorrect because storage agent
has a volume name for the library and volume
ANR4213I Audit command: A device type for library indicating that it should have a volume status of
library name and drive drive name in the private.
physical volume repository is invalid.
device type for the specified library and drive is User response: Reissue the audit command and
invalid. specify FIX=YES so that the error can be corrected.

ANR4218I Audit command: The volume status for
User response: Contact the system administrator so library library name and volume volume
that appropriate action may be taken. name in the physical volume repository
is invalid - the volume status will be
ANR4214I Audit command: A drive model for changed to private.
library library name and drive drive name Explanation: A database audit process finds that the
in the physical volume repository is volume status for the specified library and volume is
invalid. set to scratch. This is incorrect because storage agents
Explanation: A database audit process finds that the has a volume name for the library and volume which
drive model for the specified library and drive is indicates that it should have a volume status of private.
invalid. Because FIX=YES has been specified for the command,
the incorrect volume status is set to private.
User response: Contact the system administrator so
that appropriate action may be taken. User response: None.
ANR4219I ANR4226I
ANR4219I Audit command: A library type specified ANR4223I Audit command: An error (error code) was
for library library name in the physical found with converted archive object for
volume repository is invalid. node (node identifier), description
(description identifier), object (object.ID),
filespace (filespace identifier) - entry will
library type for the specified library is invalid.
be deleted.
Explanation: A database audit process has found an
User response: Reissue the audit command and error with the specified converted archive object.
specify FIX=YES so that the error can be corrected. Because FIX=YES has been specified for the command,
the entry is deleted.
ANR4220I Audit command: A library type specified System action: Audit processing continues.
for library library name in the physical
volume repository is invalid - the
library type has been changed to the
default of library type default. ANR4224I Audit command: An error (error code) was
found with converted archive object for
node (node identifier), description
library type for the specified library is invalid. Because
(description identifier), object (object.ID),
filespace (filespace identifier).
information is corrected by changing the library type to
the default type. Explanation: A database audit process has found an
error with the specified converted archive object.
ANR4221I Audit command: An error (error code) was
found with archive description for node
(node identifier), description (description), ANR4225I Audit command: table entry for archive
objects (old object count,new object count), object (object.ID), node (node identifier),
count (old directory count,new directory description (description), filespace
count) - entry will be deleted or updated. (filespace identifier) not found - the entry
will be created.
Explanation: A database audit process has found an
error with the specified archive description. Because Explanation: A database audit process cannot find a
FIX=YES has been specified for the command, the entry converted table table entry for the specified archive
is deleted or updated. object. Because FIX=YES has been specified for the
command, an entry will be created.
ANR4222I Audit command: An error (error code) was
found with archive description for node ANR4226I Audit command: table entry for archive
(node identifier), description (description), object (object.ID), node (node identifier),
objects (old object count,new object count), description (description), filespace
count (old directory count,new directory (filespace identifier) not found.
count).
Explanation: A database audit process has found an converted table table entry for the specified archive
error with the specified archive description. object.
User response: Reissue the audit command and User response: Reissue the audit command and
specify FIX=YES so that the error can be corrected. specify FIX=YES so that the error can be corrected.

ANR4227E ANR4236E
ANR4227E Audit command: Inconsistent information ANR4232E Audit command: Invalid device class
detected for file aggregate (Aggregate.ID). strategy strategy for device class device
class name - information will be
corrected.
inconsistent information for a file aggregate. This
problem cannot be corrected by the audit process, but Explanation: A database audit process finds a device
the file data is not deleted. class with an invalid access strategy. Because FIX=YES
has been specified for the audit command, the access
strategy will be corrected for this device class.
information detected for file aggregate
(Aggregate.ID). ANR4233E Audit command: Pool ID information is
missing or incorrect for storage pool
storage pool name.
or incorrect information for a file aggregate. This
information can be corrected. Explanation: A database audit process finds a storage
pool whose pool ID information is missing or incorrect.
specify FIX=YES so that the error can be corrected. User response: Reissue the audit command with
FIX=YES so that the access strategy can be corrected.
information detected for file aggregate ANR4234E Audit command: Pool ID information is
(Aggregate.ID) - It will be corrected. missing or incorrect for storage pool
storage pool name - information will be
created or corrected.
or incorrect information for a file aggregate. Because
FIX=YES has been specified for the audit command, the Explanation: A database audit process finds a storage
error will be corrected. pool whose pool ID information is missing or incorrect.
command, the pool ID information will be created or
User response: None. corrected for this storage pool.
ANR4230I Audit command: Auditing data storage
definitions.
ANR4235E Audit command: Device class ID
database audit and indicates that the data storage
referenced by storage pool storage pool
definitions are being examined by the database audit
name is not defined - data in this pool
process.
may not be available.
User response: None. pool which references a device class ID which is not
defined.
ANR4231E Audit command: Invalid device class System action: Audit processing continues.
strategy strategy for device class device
class name.
Explanation: A database audit process finds a device
ANR4236E Audit command: An invalid access
class with an invalid access strategy.
strategy was encountered for storage
System action: Audit processing continues. pool storage pool name.
User response: Reissue the audit command with Explanation: A database audit process encounters an
FIX=YES so that the access strategy can be corrected. invalid device access strategy for the specified storage
pool.
ANR4237E ANR4244E
FIX=YES so that the attribute can be corrected.

ANR4241E Audit command: An invalid attribute was
encountered for storage pool storage pool
ANR4237E Audit command: An invalid access name - the attribute will be assigned its
strategy was encountered for storage default value.
pool storage pool name - the strategy will
be corrected.
invalid attribute for the specified storage pool. Because
Explanation: A database audit process encounters an FIX=YES has been specified for the command, the
invalid device access strategy for the specified storage storage pool will be corrected using the default value
pool. Because FIX=YES has been specified for the for the attribute.
command, the storage pool access strategy will be
corrected.
examine the storage pool using the QUERY STGPOOL
User response: After the audit command completes, command, and correct attributes with the UPDATE
examine the storage pool using the QUERY STGPOOL STGPOOL command, if desired.
command, and verify that the correct information is
displayed for this storage pool.
ANR4238E Audit command: Storage pool storage pool storage pool storage pool name.
name specifies an undefined pool ID for
its next storage pool.
information pertaining to the last update for the
Explanation: The specified storage pool references an specified storage pool.
invalid pool ID as its next storage pool.
User response: Use the UPDATE STGPOOL command specify FIX=YES so that the error can be corrected.
to update the next pool. Alternatively, if the audit
command is reissued with FIX=YES, the reference to
the next pool will be deleted.
storage pool storage pool name -
ANR4239E Audit command: Storage pool storage pool information will be corrected.
name specifies an undefined pool ID for
its next storage pool - reference will be
information pertaining to the last update for the
deleted.
specified storage pool. Because FIX=YES has been
Explanation: The specified storage pool references an specified for the command, the information is
invalid pool ID as its next storage pool. Because corrected.
reference is deleted. The specified storage pool will not
have a next pool. User response: None.
ANR4244E Audit command: Storage pool ID
referenced by volume volume name is not
use the UPDATE STGPOOL command to assign a next
defined - data on this volume may not
storage pool, if desired.
be available.
Explanation: A database audit process finds a data
ANR4240E Audit command: An invalid attribute was
storage volume which references a storage pool ID that
encountered for storage pool storage pool
is not defined.
name.
invalid attribute for the specified storage pool. User response: You can attempt to move data on the
specified volume to other volumes using the MOVE
DATA command; then delete the specified volume and
User response: Reissue the audit command with redefine it. If this does not work, contact your service
FIX=YES so that the attribute can be corrected. representative.

ANR4245E ANR4252E

strategy was encountered for volume
corrected.
volume name.
invalid device access strategy for the specified volume.
information for storage volume volume
System action: Audit processing continues. name - information will be created or
corrected.
FIX=YES so that the strategy can be corrected. Explanation: A database audit process finds a data
storage volume for which information is missing or
incorrect. Since FIX=YES has been specified for the
audit command, the information will be created or
strategy was encountered for volume
corrected.
volume name - the strategy will be
corrected. System action: Audit processing continues.
Explanation: A database audit process encounters an User response: None.
invalid device access strategy for the specified volume.
ANR4250E Audit command: Extraneous reference
the access strategy will be corrected for this volume.
found.
User response: None. reference to a nonexistent entity such as a storage pool
or volume.
ANR4247E Audit command: Missing information for System action: Audit processing continues.
volume volume name cannot be created.
Delete the volume after optionally
FIX=YES so that the non-existant entity is recreated, if
moving any files from the volume.
possible. If recreation is not possible, the extraneous
Explanation: A database audit process encounters reference is deleted.
missing database information for the specified volume.
Since FIX=YES has been specified for the audit
ANR4251E Audit command: Extraneous reference
command, an attempt is made to create the missing
found - information will be recreated or
information where possible. However, some of the
deleted.
information cannot be created, and the volume must be
deleted. Explanation: A database audit process finds a
reference to a nonexistent entity such as a storage pool
System action: The access mode for the volume is set
or volume. Since FIX=YES has been specified for the
to UNAVAILABLE to prevent further attempts to write
audit command, the nonexistant entity will be
to this volume. Audit processing continues.
recreated, if possible. If recreation is not possible, the
User response: After audit processing completes, an extraneous information will be deleted.
administrator should take the following actions to
eliminate the volume
v (Optional) Use the UPDATE VOLUME command to User response: None.
set the access mode for the volume to READWRITE.
It may then be possible to use the MOVE DATA ANR4252E Audit command: Data storage global
command to move files from the volume so that attributes cannot be found.
these files can be accessed by the server.
v (Required) Use the DELETE VOLUME command to Explanation: A database audit process is not able to
delete the volume from the database. locate the global attributes for data storage in the
server database.
ANR4248E Audit command: Missing or incorrect System action: Audit processing continues.
information for storage volume volume User response: Reissue the audit command and
name. specify FIX=YES so that the error can be corrected.
Explanation: A database audit process finds a data
storage volume for which information is missing or
incorrect.
ANR4253E ANR4262E
ANR4253E Audit command: Data storage global ANR4258E Audit command: A data-integrity error
attributes cannot be found - attributes was detected on volume volume name -
will be recreated. the error will be corrected.
Explanation: A database audit process is not able to Explanation: A database audit process finds a
locate the global attributes for data storage in the correctable data-integrity error for a file stored on the
server database. Because FIX=YES has been specified specified volume. Because FIX=YES has been specified
for the audit command, the attributes will be for the audit command, the error will be corrected.
regenerated.
ANR4259E Audit command: Invalid data encountered
ANR4254E Audit command: Data storage high-water for a file in data storage - data can be
marks do not match the identifiers in corrected.
use.
Explanation: A database audit process finds invalid
Explanation: A database audit process finds that the data for a file in data storage. The error should be
information used to track data storage identifiers is correctable.
incorrect.
ANR4260E Audit command: Invalid data encountered
ANR4255E Audit command: Data storage high-water for a file in data storage - the error will
marks do not match the identifiers in be corrected.
use - they will be corrected.
Explanation: A database audit process finds that the data for a file in data storage. Because FIX=YES has
information used to track data storage identifiers is been specified for the audit command, the error will be
incorrect. Because FIX=YES has been specified for the corrected.
audit command, the error will be corrected.
ANR4261E Audit command: Invalid access
ANR4256I Audit command: Auditing data storage information was encountered for
definitions for disk volumes. volume volume name.
Explanation: This message is displayed during a Explanation: A database audit process encounters
database audit and indicates that the database invalid access information for the specified volume.
information relating to data storage disk volumes is
being examined by the database audit process.
User response: After audit processing has completed,
use the UPDATE VOLUME command to set the access
User response: None. information for this volume. Or reissue the audit
command with FIX=YES, which sets access to the
default value.
ANR4257E Audit command: A correctable
data-integrity error was detected on
volume volume name. ANR4262E Audit command: Invalid access
information was encountered for
volume volume name - the information
data-integrity error for a file stored on the specified
will be corrected.
volume. This error is correctable.
invalid access information for the specified volume.
User response: Reissue the audit command and Because FIX=YES has been specified for the command,
specify FIX=YES so that the error can be corrected. the information will be corrected by setting the default
value.

ANR4263I ANR4272E

ANR4268E Audit command: A storage volume
User response: After audit processing has completed, containing file data cannot be located -
use the UPDATE VOLUME command to set the access file data may not be accessible.
information for this volume, if desired.
database audit and indicates that the storage volume
ANR4263I Audit command: Auditing data storage containing a files data cannot be located or is not
definitions for sequential volumes. defined. This problem cannot be corrected by the audit
process, and the file data is deleted.
database audit and indicates that the database System action: Audit processing continues.
information relating to data storage sequential volumes
is being examined by the database audit process.
ANR4269E Audit command: Extraneous file data
User response: None. reference found.
ANR4264I Audit command: Auditing file reference to a file that no longer exists.
information.
database audit and indicates that information on stored
FIX=YES so that the information can be deleted.
files is being examined by the database audit process.
ANR4270E Audit command: Extraneous file data
User response: None. reference found - information will be
deleted.
ANR4265I Audit command: Auditing disk file Explanation: A database audit process finds a
information. reference to a file that no longer exists. Because
Explanation: This message is displayed during a information will be deleted.
database audit and indicates that information on files
stored on disk media is being examined by the System action: Audit processing continues.
database audit process.
User response: None. ANR4271E Audit command: Missing or incorrect
occupancy information detected.
ANR4266I Audit command: Auditing sequential file Explanation: A database audit process detects missing
information. or incorrect occupancy information for a data storage
pool or a data storage volume.
database audit and indicates that information on files System action: Audit processing continues.
stored on sequential media is being examined by the
System action: Audit processing continues. corrected.

occupancy information detected -
ANR4267E Audit command: A storage pool information will be created or corrected.
containing file data cannot be located -
file data may not be accessible. Explanation: A database audit process detects missing
or incorrect occupancy information for a data storage
Explanation: This message is displayed during a pool or a data storage volume. Because FIX=YES has
database audit and indicates that the storage pool been specified for the audit command, the information
containing a files data cannot be located or is not will be created or corrected.
defined. This problem cannot be corrected by the audit
process, but the file data is not deleted. System action: Audit processing continues.
ANR4273E ANR4281E
ANR4273E Audit command: A data-integrity error ANR4278E Audit command: Invalid file storage
was detected on volume volume name - information detected - It will be
Issue the AUDIT VOLUME command to corrected.
correct the error.
Explanation: A database audit process finds a file storage information for a stored file. Because
data-integrity error for a file stored on the specified FIX=YES has been specified for the audit command, the
volume. error will be corrected.
User response: Issue the AUDIT VOLUME command User response: None.
on the specified volume to correct the data-integrity
error.
ANR4279E Audit command: Administrator
administrator number assigned to more
ANR4274E Audit command: A correctable than just system authority class.
data-integrity error was detected.
Explanation: A database audit process finds that an
Explanation: A database audit process finds a administrator is assigned to other authority classes.
data-integrity error for a stored file. This error can be Being assigned with 'SYSTEM' authority supersedes all
corrected. other classes and the other privilege class entries
should be deleted.
specify FIX=YES so that the error can be corrected. User response: Reissue the audit command and
ANR4275E Audit command: A data-integrity error
was detected - it will be corrected. ANR4280I Audit command: Administrator
administrator number assigned to more
than just system authority class - the
data-integrity error for a stored file. Because FIX=YES
other class entries will be deleted.
has been specified for the audit command, the error
will be corrected. Explanation: A database audit process finds that an
administrator is assigned to other authority classes.
Being assigned with 'SYSTEM' authority supersedes all
User response: None. other classes and the other privilege class entries
should be deleted. Because FIX=YES has been specified
for the command, any authority class other than system
ANR4276E Audit command: Invalid file storage will be deleted.
information detected - file data is not
accessible. System action: Audit processing continues.
Explanation: A database audit process finds invalid User response: None.

file storage information for a stored file, and it cannot
be corrected.
ANR4281E Audit command: Administrator
System action: Audit processing continues. administrator number assigned as an
unrestricted policy administrator is also
User response: Issue the AUDIT VOLUME command assigned as a restricted administrator for
on all your volumes to correct the data-integrity error. domain domain name.
ANR4277E Audit command: Invalid file storage specified administrator is assigned as an unrestricted
information detected. policy administrator. The specified administrator is also
Explanation: A database audit process finds invalid assigned as the restricted administrator for the
file storage information for a stored file. This specified policy domain. The unrestricted policy
information can be corrected. administration class supersedes any restricted policy
class definitions for an administrator. The
System action: Audit processing continues. administrators authority needs to be corrected.
User response: Reissue the audit command and System action: Audit processing continues.

ANR4282I ANR4289E
ANR4282I Audit command: Administrator ANR4285E Audit command: A data-integrity error

administrator number assigned as an was detected on a storage volume for
unrestricted policy administrator is also object (Object.ID).
assigned as administrator for domain
domain name - restricted class entry will
data-integrity error for a file stored on a storage
be deleted.
volume, but the specific volume name is not known. If
Explanation: A database audit process finds the fix=yes was specified, the audit process will attempt to
specified administrator is assigned as an unrestricted correct the data-integrity error.
policy administrator. The specified administrator is also
assigned as the restricted administrator for the
specified policy domain. The unrestricted policy User response: None.
administration class supersedes any restricted policy
class definitions for an administrator. Because FIX=YES
has been specified for the command, the restricted ANR4286E Audit command: A correctable storage
administrator policy class will be deleted. allocation error detected for volume
volume name.
User response: None. block allocation information for the specified storage
volume; the error can be corrected.
ANR4283E Audit command: Administrator System action: Audit processing continues.
administrator number assigned as an
unrestricted storage administrator is also User response: Reissue the audit command and
assigned as a restricted administrator for specify FIX=YES so that the error can be corrected.
Explanation: A database audit process finds the ANR4287E Audit command: Storage allocation error
specified administrator is assigned as an unrestricted detected for volume volume name - It will
storage administrator. The specified administrator is be corrected.
also assigned as the restricted administrator for the Explanation: A database audit process finds incorrect
specified storage pool. The unrestricted storage block allocation information for the specified storage
administration class supersedes any restricted storage volume; the error will be corrected.
class definitions for an administrator. The
administrators authority needs to be corrected. System action: Audit processing continues.

specify FIX=YES so that the error can be corrected. ANR4288E Audit command: Multiple files allocated
the same disk storage block on volume
volume name.
ANR4284I Audit command: Administrator
administrator number assigned as an Explanation: A database audit process finds multiple
unrestricted storage administrator is also files allocated the same disk storage block on the
assigned as a restricted administrator for specified volume; this error cannot be corrected by the
storage pool storage pool name - restricted audit process.
class entry will be deleted. System action: Audit processing continues.
Explanation: A database audit process finds the User response: Contact your service representative.
specified administrator is assigned as an unrestricted
storage administrator. The specified administrator is
also assigned as the restricted administrator for the ANR4289E Audit command: Multiple files allocated
specified storage pool. The unrestricted storage the same disk storage block on volume
administration class supersedes any restricted storage volume name.
class definitions for an administrator. Because FIX=YES Explanation: A database audit process finds multiple
has been specified for the command, the restricted files allocated the same disk storage block on the
administrator storage class will be deleted. specified volume; this error cannot be corrected by the
System action: Audit processing continues. audit process.
User response: None. System action: Audit processing continues.

ANR4290I ANR4299I
ANR4290I Audit command: License global attributes ANR4295I Audit command: A license node
could not be found - they will be assignment entry was not found for
created. node node ID.
Explanation: A database audit process cannot find the Explanation: A database audit process cannot find the
license global attributes. Because FIX=YES has been node assignment entry corresponding to the specified
specified for the command, the information is corrected node.
by the creation of the global attributes.
User response: None. specify FIX=YES so that the error can be corrected.
ANR4291I Audit command: License global attributes ANR4296I Audit command: An invalid license node
could not be found. assignment entry was found for node
node ID - the entry will be deleted.
license global attributes. Explanation: A database audit process finds that the
license node assignment entry is invalid. Because
FIX=YES has been specified for the command, the node
User response: Reissue the audit command and entry is deleted.
ANR4292I Audit command: Invalid table active
column encountered for license global
attribute - the value will be corrected. ANR4297I Audit command: An invalid license node
assignment entry was found for node
node ID.
active column license global attribute is invalid.
Because FIX=YES has been specified for the command, Explanation: A database audit process finds that the
the active column is reset to a proper value. license node assignment entry is invalid.
ANR4293I Audit command: Invalid table active
column encountered for license global ANR4298I Expiration thread already processing -
attributes. unable to begin another expiration
process.
active column license global attribute is invalid. Explanation: The expiration thread is already
processing. The processing expiration thread is either
an EXPIRE INVENTORY command or is the automatic
User response: Reissue the audit command and background expiration process. In either case, another
specify FIX=YES so that the error can be corrected. expiration process cannot be started until the current
expiration process completes or is canceled.
ANR4294I Audit command: A license node System action: Current expiration process continues.
User response: Use the QUERY PROCESS command
node node ID - an entry will be created.
to determine the status of the current expiration
Explanation: A database audit process cannot find the process.
node assignment entry corresponding to the specified
node. Since FIX=YES has been specified for the
ANR4299I Audit command: Invalid audit interval
command, the required license entry will be created
encountered for license global attribute -
the value will be set to the default.
User response: None. audit interval license global attribute is invalid. Because
FIX=YES has been specified for the command, the audit
interval is reset to the default value.

ANR4300I ANR4309I

ANR4305E Audit command: object name missing entry
for cluster cluster ID.
ANR4300I Audit command: Invalid audit interval
Explanation: A database audit process is missing a
encountered for license global
corresponding entry for the specified comparison object
attributes.
and cluster ID. This indicates a data-integrity error for
Explanation: A database audit process finds that the the database cluster information.
audit interval license global attribute is invalid.
ANR4306I AUDITDB: Processed number of entries
ANR4301I Audit command: Invalid last audit date database entries (cumulative).
encountered for license global attribute -
Explanation: This message indicates the number of
the value will be set to 0.
database entries that have been processed during
Explanation: A database audit process finds that the database audit processing.
last audit date license global attribute is invalid.
System action: Database audit processing continues.
the last audit date is set to 0. The next execution of User response: None.
AUDIT LICENSES will set a new last audit date.
System action: Audit processing continues. ANR4307I Audit command: Auditing inventory
external space-managed objects.
ANR4302I Audit command: Invalid last audit date
about external space-managed client objects is currently
encountered for license global attribute.
being examined by the database audit process.
last audit date license global attribute is invalid.
ANR4308I Audit command: External space-managed
entry for node node ID and file space
filespace ID is missing a corresponding
ANR4303E Audit command: Inventory references for space-managed object entry - the
object(Object.ID) deleted. external space-managed entry will be
deleted.
Explanation: A database audit process deleted all
inventory references for the specified object ID. This Explanation: A database audit process finds that an
process corrects a data-integrity error if FIX=YES was external space-managed entry is missing a
specified. corresponding space-managed entry. Because FIX=YES
has been specified, the orphaned external
System action: Audit processing continues. space-managed entry is deleted.
User response: None. System action: Audit processing continues.
ANR4304E Audit command: object name missing entry
for cluster cluster ID - cluster entries
deleted. ANR4309I Audit command: External space-managed
entry for node node ID and file space
Explanation: A database audit process is missing a filespace ID is missing a corresponding
corresponding entry for the specified comparison object space-managed object entry.
and cluster ID. This process indicates a data-integrity
error for the database cluster information. If FIX=YES Explanation: A database audit process finds that an
was specified, the invalid cluster information will be external space-managed entry is missing a
deleted. corresponding space-managed entry.
ANR4310I ANR4318I
specify FIX=YES so that the error can be corrected. User response: Reissue the audit command and
ANR4310I Audit command: Auditing inventory
space-managed objects. ANR4315I Audit command: Space-managed object
(object ID) for node node ID and file
space filespace ID is missing the
corresponding external space managed
about space-managed client objects is currently being
entry - the entry will be created.
examined by the database audit process.
the space-managed object entry is missing a
User response: None. corresponding external space managed entry. Because
FIX=YES was specified, the missing entry will be
created.
ANR4311I Audit command: Object entry for
space-managed object object.ID not System action: Audit processing continues.
found - entry will be created.
object entry for the specified space-managed object.
ANR4316I Audit command: Space-managed object
(object ID) for node node ID and file
an object entry is created by using default values.
space filespace ID is missing the
System action: Audit processing continues. corresponding external space managed
entry.
the space-managed object entry is missing a
ANR4312I Audit command: Object entry for corresponding external space-managed entry.
space-managed object object.ID not
found. System action: Audit processing continues.
Explanation: A database audit process cannot find an User response: Reissue the audit command and
object entry for the specified backup object. specify FIX=YES so that the error can be corrected.

ANR4317I Audit command: External space-managed
User response: Reissue the audit command and object (object ID) for node node ID and
specify FIX=YES so that the error can be corrected. file space filespace ID has one or more
incorrect fields - the values will be
ANR4313I Audit command: Space-managed object corrected.
(object ID) for node node ID and file Explanation: A database audit process determined
space filespace ID has one or more that one or more field values for the specified external
incorrect fields - the values will be space-managed object is not valid. Because FIX=YES
corrected. was specified, the values will be corrected.
Explanation: A database audit process determined System action: Audit processing continues.
that one or more field values for the specified
space-managed object is not valid. Because FIX=YES User response: None.
was specified the values are corrected.
System action: Audit processing continues. ANR4318I Audit command: External space-managed
object (object ID) for node node ID and
User response: None. file space filespace ID has one or more
incorrect fields.
ANR4314I Audit command: Space-managed object Explanation: A database audit process determined
(object ID) for node node ID and file that one or more field values for the specified external
space filespace ID has one or more space-managed object is not valid.
incorrect fields.
Explanation: A database audit process determined
that one or more field values for the specified User response: Reissue the audit command and
space-managed object is not valid. specify FIX=YES so that the error can be corrected.

ANR4319I ANR4327E
technique value will be set for the management class

specified.
not found for object object.ID - object
entry will be deleted. System action: Audit processing continues.
Explanation: A database audit process cannot find a User response: Refer to the DEFINE MGMTCLASS
space-managed object entry for the specified object. command in the Administrators Reference for valid
Because FIX=YES was specified the object entry will be values.
deleted.
System action: Audit processing continues. ANR4324E Audit command: Management class class
domain name does not have a valid
AUTOMIGNONUSE value specified.
not found for object object.ID.
management class that does not have a valid value
Explanation: A database audit process cannot find a specified.
space-managed object entry for the specified object.
ANR4321I Audit command: Invalid copy type name in policy set set name, domain
encountered for object object.ID - object domain name does not have a valid
found as an space-managed object - AUTOMIGNONUSE value defined - the
correcting the invalid copy type default value will be set.
Explanation: A database audit process encounters an Explanation: A database audit process finds a
invalid copy type for the specified object ID, but finds management class that does not have a valid value
a corresponding space-managed object for the entry. specified. Because FIX=YES was specified for the
Because FIX=YES has been specified for the command, AUDITDB operation, the default AUTOMIGNONUSE
the invalid copy type is corrected. value will be set for the management class specified.
User response: None. User response: Refer to the DEFINE MGMTCLASS
command in the Administrators Reference for valid
values.
domain name does not have a valid space ANR4326E Audit command: Management class class
management technique defined. name in policy set set name, domain
domain name does not have a valid
MIGREQUIRESBKUP value specified.
specified. Explanation: A database audit process finds a
specified.
domain name does not have a valid space ANR4327E Audit command: Management class class
management technique defined - the name in policy set set name, domain
default value will be set. domain name does not have a valid
MIGREQUIRESBKUP value defined -
specified. Because FIX=YES was specified for the Explanation: A database audit process finds a
AUDITDB operation, the default space management management class that does not have a valid value
specified. Because FIX=YES was specified for the
ANR4328W ANR4335I
AUDITDB operation, the default MIGREQUIRESBKUP User response: Use the QUERY DEVCLASS command
value will be set for the management class specified. to determine which device classes are defined on the
server and reissue the RECONCILE VOLUMES
command.
User response: Refer to the DEFINE MGMTCLASS
command in the Administrators Reference for valid
ANR4332W This command will compare all volumes
values.
used by the specified device class(es)
with the actual data stored on the
ANR4328W Audit command: Storage pool storage pool associated server for those volumes and
name, specified as a space management will report any discrepancies; the data
destination for management class will be inaccessible to users until the
management class name, policy set set operation completes.
Explanation: During the execution of a RECONCILE
exist.
VOLUMES command, any data a volume named
Explanation: A database audit process encounters a would be unavailable to users.
storage pool specified for the space management
destination of the specified management class that is
continue.
not defined in the server database. If this management
class is used in an active policy set, then migration User response: Enter 'Y' to reconcile the volumes or
operations will fail when attempting to put client data 'N' to stop the process.
in the destination.
System action: Audit processing continues. ANR4333W This command will discard any
references to volumes used by the
specified device class(es) that are
use the DEFINE STGPOOL command to define the
missing from the associated server,
missing storage pool or the UPDATE MGMTCLASS
thereby rendering the data
command to update the management class to refer to
unrecoverable; the valid volumes will
an existing storage pool.
be inaccessible to users until the
operation completes.
ANR4329I Audit command: Inactive reference found
Explanation: During the execution of a RECONCILE
for active backup entry (Object.ID) - the
VOLUMES command, any data on a volume being
inactive reference will be deleted.
reconciled would be unavailable to users. After the
Explanation: A database audit process found that an command has ended, any inconsistent volumes found
active backup entry for the specified object has a will be discarded.
corresponding inactive backup entry. Since FIX=YES
was specified for the command, the information is
continue.
corrected by deleting the inactive backup object entry.
User response: Enter 'Y' to reconcile the volumes or
'N' to stop the process.
ANR4334I command (Repair) process started,
ANR4330I Audit command: Inactive reference found process ID process ID.
for active backup entry (Object.ID).
Explanation: As the result of a RECONCILE
Explanation: A database audit process found that an VOLUMES command that specified FIX=YES, the
active backup entry for the specified object has a process whose ID is displayed has begun reconciling
corresponding inactive backup entry. the volumes associated with the given device class.
System action: Audit processing continues. System action: The volumes are reconciled and
invalid volumes are displayed.
ANR4331E command process terminated, no

matching device classes. ANR4335I command (Inspect Only) process started,
process ID process ID.
Explanation: The server did not find any device class
names matching the specifications entered in the Explanation: As the result of a RECONCILE
RECONCILE VOLUMES command. VOLUMES command that specified FIX=NO, the
process whose ID is displayed has begun reconciling

ANR4336W ANR4345I
the volumes associated with the given device class. User response: Reissue the RECONCILE VOLUMES
command. If the error persists, it may indicate a
System action: The volumes are reconciled and
shortage of source server memory.
inconsistent volumes are displayed.
ANR4341W command process terminated - sufficient
memory is not available.
ANR4336W command process ended, process ID
Explanation: During processing of a RECONCILE
process ID.
VOLUMES command, the source server does not have
Explanation: The RECONCILE VOLUMES command enough memory available to complete the command.
for the specified device class has ended.
System action: The RECONCILE VOLUMES
System action: None. command is ended.
User response: For complete details on the results of User response: If necessary make more memory
the RECONCILE VOLUMES command, examine the available to the source server.
previous messages.
ANR4342W command process terminated - lock
ANR4337W command process terminated - process conflict detected.
canceled.
Explanation: During processing of a RECONCILE VOLUMES command, the source server cannot obtain a
VOLUMES command, the process performing the required lock.
reconcile was canceled.
System action: The RECONCILE VOLUMES
System action: The RECONCILE VOLUMES command is ended.
command is ended.
User response: Reissue the RECONCILE VOLUMES
User response: None. command.
ANR4338W command process terminated - sufficient ANR4343W command process terminated - internal
recovery log space is not available. server error detected.
Explanation: During processing of a RECONCILE Explanation: During processing of a RECONCILE

VOLUMES command, the source server does not have VOLUMES command, an internal server error occurs
sufficient recovery log space to continue. on the source server.
System action: The RECONCILE VOLUMES System action: The RECONCILE VOLUMES
command is ended. command is ended.
User response: If necessary, make more recovery log User response: Contact your service representative.
space available to the source server.
ANR4344I command started for device class device
ANR4339W command process terminated - sufficient class (process ID process ID).
database space is not available.
Explanation: The RECONCILE VOLUMES process
Explanation: During processing of a RECONCILE whose ID is displayed has started reconciling volumes
VOLUMES command, the source server does not have associated with the given device class.
sufficient database space to continue.
System action: The volumes are reconciled and
System action: The RECONCILE VOLUMES inconsistent volumes are displayed.
command is ended.
User response: If necessary, make more database
space available to the source server.
ANR4345I command completed for device class
device class; (process ID process ID);
ANR4340W command process terminated - thread volume count volumes inspected, volume
resource not available. count invalid volumes found, volume
count volumes deleted.
VOLUMES command, the source server cannot start a Explanation: The RECONCILE VOLUMES process
thread for the reconcile process. whose ID is displayed has finished reconciling volumes
associated with the given device class. The number of
System action: The RECONCILE VOLUMES volumes reconciled and the number of invalid volumes
command is ended.
ANR4346I ANR4357W
found or deleted are displayed. permission to reconcile volumes on the shown target
server, issue the UPDATE SERVER command with
FORCESYNC=YES to cause the target server to accept
User response: For complete details on the results of reconcile operations for the source server. Reissue the
the RECONCILE VOLUMES command for the shown RECONCILE VOLUMES command.
device class, examine the previous messages.
ANR4355W command: Volume volume name not valid,
ANR4346I command completed for device class source server missing corresponding
device class; (process ID process ID); entry for target server.
volume count volumes inspected, volume
count invalid volumes found.
VOLUMES command, the volume shown was reported
Explanation: The RECONCILE VOLUMES process by the target server and it has no matching volume on
whose ID is displayed has finished reconciling volumes the source server.
associated with the given device class. The number of
System action: The reconciliation process continues.
volumes reconciled and the number of invalid volumes
found are displayed. User response: The database on either the source or
target server has been regressed by either a RESTORE
DATABASE operation or some system facility external
User response: For complete details on the results of to the server. Investigate the action that caused one or
the RECONCILE VOLUMES command for the shown both of the databases to be regressed to there current
device class, examine the previous messages. If you condition. If a newer database images exist for that
suspect that volumes were inaccessible because of server, consider restoring the server to that point in
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
Explanation: This message is displayed in response to 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: None. System action: The reconciliation process continues.
User response: The database on either the source or
ANR4353I Cancel in progress 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

ANR4358W ANR4360W
VOLUMES command, the volume shown was found on

the target server and it is associated with the device
the size of the volume on target server
class shown. The source server has NO corresponding
does not match the size on the source
device class.
server.
User response: The database on either the source or VOLUMES command, the volume shown was found on
target server has been regressed by either an RESTORE both the source and target server, but the size of the
DATABASE operation or some system facility external volume does not match.
to the server. Investigate the action that caused one or
both of the databases to be regressed to their current
condition. If a newer database image exist for that User response: The database on either the source or
server, consider restoring the server to that point in target server has been regressed by either an RESTORE
time. In the case of a volume in the VOLHISTORY, the DATABASE operation or some system facility external
device class may have been deleted from the source to the server. Investigate the action that caused one or
server. If possible, issue the DEFINE DEVCLASS both of the databases to be regressed to there current
command to correct the situation. If the condition of condition. If a newer database image exist for that
the database on each server is acceptable and the server, consider restoring the server to that point in
RECONCILE VOLUMES command was issued with time. If the condition of the database on each server is
FIX=NO, reissue the RECONCILE VOLUMES acceptable, additional actions will have to be taken
command with FIX=Yes to have the volume deleted because RECONCILE VOLUMES FIX=YES is unable to
from the target server. correct this situation. In the case of a volume in the
VOLHISTORY, an IMPORT PREVIEW=YES or a
RESTORE DATABASE PREVIEW=YES will determine
the integrity of the volume. If the volume is in error, a
the attributes of the volume on target
DELETE VOLHISTORY will remove the volume from
server do not match the attributes on the
both the source and target servers. In the case of a
source server.
volume in a storage pool, an AUDIT VOLUME
Explanation: As the result of a RECONCILE FIX=NO will determine the integrity of the volume. If
VOLUMES command, the volume shown was found on errors are found, an AUDIT VOLUME FIX=YES may
both the source and target server, but the attributes make some data on the volume accessible. Otherwise,
describing the volume does not match. issue the DELETE VOLUME command on the source
server to remove the volume from both the source and
System action: The reconciliation process continues. target servers.
User response: The database on either the source or
target server has been regressed by either a RESTORE ANR4360W command: Volume volume name not valid,
DATABASE operation or some system facility external the type of the volume on target server
to the server. Investigate the action that caused one or does not match the type on the source
both of the databases to be regressed to there current server.
condition. If a newer database image exist for that
server, consider restoring the server to that point in Explanation: As the result of a RECONCILE
time. If the condition of the database on each server is VOLUMES command, the volume shown was found on
acceptable, additional actions will have to be taken both the source and target server, but the type of the
because RECONCILE VOLUMES FIX=YES is unable to volume does not match. For example, the volume on
correct this situation. In the case of a volume in the the target server is defined in a storage pool, but the
VOLHISTORY, an IMPORT PREVIEW=YES or a target server indicates that volume was used for a
RESTORE DATABASE PREVIEW=YES will determine DATABASE BACKUP.
the integrity of the volume. If the volume is in error, a
DELETE VOLHISTORY will remove the volume from
both the source and target servers. In the case of a User response: The database on either the source or
volume in a storage pool, an AUDIT VOLUME target server has been regressed by either an RESTORE
FIX=NO will determine the integrity of the volume. If DATABASE operation or some system facility external
errors are found, an AUDIT VOLUME FIX=YES may to the server. Investigate the action that caused one or
make some data on the volume accessible. Otherwise, both of the databases to be regressed to there current
issue the DELETE VOLUME command on the source condition. If a newer database image exists for that
server to remove the volume from both the source and server, consider restoring the server to that point in
target servers. time. If the condition of the database on each server is
acceptable, additional actions will have to be taken
because RECONCILE VOLUMES FIX=YES is unable to
correct this situation. These actions may have to be
performed on one or both servers. Use the QUERY
ANR4361W ANR4367E
VOLHISTORY and QUERY VOLUME commands on User response: Review any additional messages
both servers to determine the volume type on each issued by the RECONCILE VOLUMES command and
server. In the case of a volume in the VOLHISTORY, a correct the errors that set the volume to unavailable, or
DELETE VOLHISTORY on the appropriate server that use the DELETE VOLUME command to remove it from
will remove the volume on that server. In the case of a the system.
volume in a storage pool, the DELETE VOLUME
command on the appropriate server will remove the
ANR4364W command: Unable to connect to target
volume on that server.
server server name.
Explanation: During processing of indicated
command, the source server was unable to maintain
the target server has reported damage to
communications with the shown target server.
all or part of the volume.
System action: The command process continues.
VOLUMES command, the volume shown was found on User response: Check both the source server and the
both the source and target server, but the target server target server for any additional messages that might
has reported damage to all or part of the volume. further describe the communications problem.
ANR4365W command: Prefix for volume volume name
User response: On the target server, an audit with
does not match the device class prefix.
FIX=NO of the volumes in the storage pool used by the
source server will indicate what which volume on the Explanation: As the result of a RECONCILE
target server is damaged. This AUDIT VOLUME VOLUMES command, the volume shown was found on
command may be able to reset the damaged indicator both the source and target server, but the beginning
in the database if the damage was temporary due to portion of the high-level archive file name (the prefix)
hardware problems (for example, dirty tape heads). If on the target server does not match the prefix in the
the volume on the target server is in a primary storage device class on the source server.
pool that has previously been backed up to a copy
storage pool, attempt to correct the damage by using System action: The reconciliation process continues.
the RESTORE STGPOOL command. If attempts to User response: Verify that the prefix in the device
correct the damage on the target server fail, an AUDIT class on the source server is correct and update it if
VOLUME command FIX=YES from the source server necessary. Use the RECONCILE VOLUMES FIX=YES
will mark as damaged in the source server database command on the source server to rename the target
each file that is inaccessible and those files will not be archive objects to match the device class on the source
accessed for future operations. If the files are part of an server.
aggregate, the entire aggregate will be marked
damaged. If a usable copy of the file exists in another
storage pool, that copy may be accessed for future ANR4366I command: Prefix for volume volume name
operations involving the file. was changed to match the device class
prefix.
ANR4362W command: Invalid volume volume name Explanation: As the result of a RECONCILE
deleted from server server name for VOLUMES FIX=YES command, the beginning portion
device class device class. of the high-level archive file name (the prefix) on the
target server was changed to match the prefix in the
Explanation: As the result of a RECONCILE device class on the source server.
VOLUMES command that specified FIX=YES, the
volume shown whose information is displayed is System action: The prefix is corrected.
deleted from the target server. User response: None.
System action: The volume is deleted.
User response: None. ANR4367E Audit command: A storage volume
containing file data cannot be located -
file data may not be accessible.
ANR4363W command: Volume volume name access
changed to access mode. Explanation: This message is displayed during a
database audit and indicates that the storage volume
Explanation: As the result of a RECONCILE containing a files data cannot be located or is not
VOLUMES command that specified FIX=YES, the defined.
access mode of the source volume has been changed to
the value shown. System action: Audit processing continues.
System action: The volume's access mode is changed. User response: Reissue the audit command with

ANR4368I ANR4373E
FIX=YES and the server will attempt to recreate the the problem and retry the failing operation.
missing volume definition. If the server cannot recreate
the missing volume information, the server will delete
ANR4372E The password on the source server does
the inaccessible file data.
not match the password on target server
server name.
ANR4368I Audit command: Attributes for group
Explanation: The source server has attempted to
group.ID and member member.ID are not
update both the source password and the target
correct - the attributes are corrected.
password. An error occurred that prevented the source
Explanation: A database audit process determines that server from updating the target server. The passwords
attributes for the specified group ID and member ID do no longer match.
not match attributes for the corresponding primary
backup object. Because FIX=YES was specified for the
command, the incorrect attributes are corrected. User response: On the target server, issue the
UPDATE NODE command to change the password. On
the source server, issue the UPDATE SERVER
User response: None. command to change the password to match the new
password on the target server. Retry the failing
operation.
ANR4369I Audit command: Attributes for group
group.ID and member member.ID are not
correct. ANR4373E Session rejected by target server server
name, reason: rejection reason.
attributes for the specified group ID and member ID do Explanation: The source server tried to open a session
not match attributes for the corresponding primary with the target server. The session was rejected for the
backup object. indicated reason.
System action: Audit processing continues. System action: The operation fails.
User response: The AUDITDB process should be User response: Check both the source server and the
re-issued with FIX=YES specified. target server for any additional messages that might
further describe the reason the session was rejected. For
a reason of AUTHENTICATION FAILURE, ensure that
ANR4370E The source server is not authorized to
both the source and target servers are using the same
create volumes on target server server
password. For a reason of NO RESOURCE, ensure that
name.
the target server is enabled, has sufficient DB, LOG,
Explanation: The source server has attempted to and memory resource to support the source server
create a volume on the shown target server, but the session, and that the node name of the source server is
operation failed because the source server does not not locked or in use. If this is a routed command, check
have the authority to create volumes. to make sure that the administator id being used to
route the command is not locked or in use. For a
System action: The operation fails. reason of LICENSE FAILURE, ensure that the target
User response: If the source server should have server is properly licensed to support the source server
permission to create volumes on the shown target session. For a reason of DOWN LEVEL, ensure that the
server, issue the UPDATE SERVER command with target server program is a level new enough to support
FORCESYNC=YES to cause the target server to accept the source server session. For a reason of NODE TYPE,
volume create operations for the source server. Retry the source server is not allowed to establish a session
the failing operation. with the given target server. The NODETYPE on the
target server is CLIENT. The NODENAME parameter
of the server definition on the source server is incorrect.
ANR4371E Information on the source server does The NODETYPE parameter of the registered node on
not match information on target server the target server is incorrect and should be
server name. NODETYPE=SERVER. For a reason of INTERNAL
Explanation: The source server has determined that ERROR, use the messages on the target server to
information contained on the shown target server no determine the problem. For all reasons, if none of the
longer matches information contained on the source above are applicable, ensure that that the target server
server. has not disabled this server with the DISABLE
SESSIONS SERVER command. Retry the failing
System action: The operation fails. operation.
User response: Issue the RECONCILE VOLUMES
command to determine the problem. If possible, correct
ANR4374E ANR4381E
remove the target server from the list of replication

ANR4374E Session failure, source server detected
servers.
an internal error.
Explanation: The source server ends the session
ANR4378E For device class device class, the retry of a
because an internal logic error is detected.
session with target server server name has
System action: The source server ends the session and timed out.
User response: To determine the source of the error, re-establish a session with the shown target server, but
the administrator can examine server messages issued the RETRYPERIOD from the given device class has
prior to this message. The QUERY ACTLOG command been exceeded.
can be used to view the activity log and search for
System action: The source server ends the operation.
messages. If the error cannot be isolated and resolved,
contact your service representative. User response: Determine it the target server is
having a problem or considering increasing the
RETRYPERIOD value.
ANR4375E Session failure, source server has
ANR4379E The source server was unable to update
the password on target server server
because sufficient memory (virtual memory) is not
name.
available.
System action: The source server ends the session and
update the target password. An error occurred that
prevented the source server from updating the target
User response: See the documentation for the server.
application.
User response: On the target server, determine the
cause of the problem and correct it. It may be necessary
ANR4376E Session failure, target server server name
for an administrator to correct the passwords with the
is locked on the source server.
following actions. On the target server, issue the
Explanation: The source server ends the session UPDATE NODE command to change the password. On
because shown target server is locked from source the source server, issue the UPDATE SERVER
server access. command to change the password to match the new
password on the target server. Retry the failing
operation.
User response: Before the source server is permitted
ANR4380E The source server was unable to update
to access the target server, a properly authorized
the server validation key on target
administrator must unlock the target server.
server server name.
update it's server validation key on the target server.
is not defined on the source server.
An error occurred that prevented the source server
Explanation: The source server ends the session from updating the target server.
because shown target server is not defined on the
source server.
User response: On the target server, determine the
cause of the problem and correct it. It may be necessary
for an administrator to correct the keys with the
User response: The target server must be correctly following actions. On the source server, issue the
defined before it can be accessed by the source server. UPDATE SERVER command with FORCESYNC=YES to
Before you attempt the next operation, define the target cause an attempt to synchronize the keys on both the
server by using the DEFINE SERVER command. source and target servers. Retry the failing operation.
If the target server is a replication server and its server

definition was incorrectly deleted, redefine the server ANR4381E The source server was unable to register
by using the DEFINE SERVER command before you with target server server name.
attempt replication. However, if you intend to remove
the target server from replication because it is no longer
register with the shown target server. An error occurred
required, use the REMOVE REPLSERVER command to

ANR4382E ANR4389I
that prevented the source server from registering with

ANR4385I Session retry in progress with target
the target server.
server server name.
Explanation: The source server is attempting to
User response: Ask an authorized administrator to re-establish a session with the shown target server.
submit the request on the use of the target server using Session retry processing occurs when the source server
REGISTER NODE command. Retry the failing has lost the connection with a target server and a
operation. RETRYPERIOD value is specified,
System action: The source server attempts to contact
ANR4382E Session failure, policy information from the target server.
target server server name is incomplete,
User response: Determine if the target server is
missing policy object.
having a problem and considering canceling the
Explanation: The source server ends the session operation on the source server or correcting the
because the shown target server has provided policy problem with the target server.
information which is incomplete. The missing policy
object is shown.
ANR4386I Session retry was successful for target
System action: The source server ends the session and server server name.
Explanation: The source server has re-establish a
User response: Use the appropriate commands on the session with the shown target server.
target server to complete the policy definitions being
System action: Source server processing continues.
used by the source server. Retry the failing operation.
has aborted current transaction; reason: ANR4387E Session session number for node node
abort reason. name (client platform) refused - node
name not registered as TYPE=CLIENT.
because the shown target server has aborted the current Explanation: The server refuses a request to start a
transaction for the given reason. client session because the client node name is not
registered as a node of TYPE=CLIENT. This node name
is already in use either as a server definition as defined
by a DEFINE SERVER command or else as a node of
User response: Check both the source server and the TYPE=SERVER using the REGISTER NODE command.
target server for any additional messages that might
further describe the reason the transaction was aborted.
Retry the failing operation. 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
ANR4384E Node node name is not allowed to
should be registered using the REGISTER NODE
establish a session as a target server.
TYPE=CLIENT command and specify a name that is
Explanation: The node specified has attempted to not in use by any other nodes or server defined to this
establish a session with this system and this is not server.
permitted due to the NODETYPE for this node.
System action: The operation fails. ANR4388W No expiration process to cancel.
User response: To allow the specified node to Explanation: The CANCEL EXPIRATION command
establish a session as a target server, the node must be was issued but there were no expiration processes
registered with a NODETYPE of SERVER. Or else currently running.
change the node name on the target server to a node
name that is allowed to establish a session using a
node name that was registered with the User response: None.
NODETYPE=SERVER parameter specified.
ANR4389I Expiration process cancelled.
Explanation: The CANCEL EXPIRATION command
was issued and successfully cancelled the current
process.
ANR4390E ANR4403I

ANR4397E Audit command: An invalid data format
was encountered for storage pool storage
ANR4390E CANCEL EXPIRATION failed - unable pool name.
to cancel expiration process.
Explanation: The CANCEL EXPIRATION command invalid data format for the specified storage pool.
was issued but encountered an error. Due to this error,
the command was unable to cancel the process.
User response: Issue the command QUERY PROCESS
to determine the process number for the expiration
ANR4398E Audit command: An invalid data format
process and then issue the command CANCEL
was encountered for storage pool storage
PROCESS for that process number. This will cancel the
pool name - the data format will be
current expiration process.
assigned its default value.
ANR4391I Expiration processing node node name,
invalid data format for the specified storage pool.
filespace filespace name, fsId filespace id,
domain domain name, and management System action: Because FIX=YES has been specified
class management class name - for type for the command, the audit process assigns the default
type files. value to the data format. Audit processing continues.
Explanation: Expiration processing is currently User response: If you want the data format for the
evaluating information for the node, filespace, domain specified storage pool to be other than the default, you
name, and management class specified for the file type must delete and re-define the storage pool with the
indicated. desired type after the audit command has completed.
ANR4399E NAS file server NAS file server name is
reporting NDMP error number NDMP
error number: NDMP error description.
ANR4395I Audit command: Invalid node type
System action: The process ends.
encountered for node node name.
User response: To identify the cause of the network
data management protocol (NDMP) error, see the
invalid node type for the node indicated, and FIX=YES
documentation for the network-attached storage (NAS)
was not specified.
file server. Review the NDMP logs for the NAS file
System action: Audit processing continues. server, resolve the error, and restart the operation.
User response: You may want to run this command

again, specifying FIX=YES so that the audit process can ANR4402I Database Dump command: Database
correct the problem. update activity resumed
Explanation: Database update activities that were
ANR4396I Audit command: Invalid node type suspended by the database dump process are restarted.
encountered for node node name. The
default type will be set.
invalid node type for the node indicated. Because
FIX=YES has been specified, the audit function sets the ANR4403I Database Load command: Database dump
nodes type to the default value. image is consistent - a database audit
(AUDITDB) will NOT be required if
this load completes successfully.
User response: If you want the node type for the
Explanation: The database dump that is currently
specified node to be other than the default, you must
being loaded by the LOADDB process is a consistent
remove and re-register the node with the correct type
database image. This process implies that a database
after the audit command has completed.
audit (AUDITDB) will not be required if the load
completes successfully.
System action: Server database load processing
continues.

ANR4404I ANR4412I
User response: None

ANR4408I Audit command: Client option Client
option name sequence number option
ANR4404I Database Load command: Loaded a sequence number in optionset optionset
consistent dump image - a database name is not a valid option. The option
audit (AUDITDB) is NOT required. will be deleted.
Explanation: The database dump image loaded by the Explanation: A database audit process found that the
LOAD command was consistent. A database audit specified client option is not a valid option. The option
(AUDITDB) is not required. The server may be started is deleted.
normally.
completes.
ANR4405I Database Load command: Loaded an sequence number in optionset option set is
inconsistent dump image - a database not a valid option.
audit (AUDITDB) IS REQUIRED with
Explanation: A database audit process found that the
FIX=YES.
specified client option is not a valid option.
Explanation: The database dump image loaded by the
LOAD command was not consistent. A database audit
(AUDITDB) with FIX=YES is required to return the User response: Reissue the audit command and
database to a consistent state. specify FIX=YES so that the error can be corrected.
completes. ANR4410I Triggered space expansion will be
retried in number of seconds seconds.
User response: To check the database for
inconsistencies and correct any inconsistencies, use the Explanation: Because of a problem encountered
database audit (AUDITDB) utility as described in the during a triggered space expansion for the database
Administrators Reference. and/or recovery log, the current expansion stops but
will be retried after the time period shown.
ANR4406I Audit command: Client option Client System action: The system waits for the specified
option name sequence number option period and then retries to expand the database and/or
sequence number is not a member of an recovery log.
optionset. The option will be deleted.
User response: If possible, correct the condition that
Explanation: A database audit process found that the stopped the expansion. If the problem persists, contact
specified client option does not have a corresponding your service representative.
optionset. The option is deleted.
System action: Audit processing continues. ANR4411I Triggered space expansion retry delay
ended; checking space trigger criteria.
Explanation: Because a triggered space expansion had
been stopped due to a problem, the system waited
before retrying. The retry wait period has ended, and
the system can now retry to expand space for the
sequence number is not a member of an
database and/or recovery log.
optionset.
System action: Space expansion begins.
Explanation: A database audit process found that the
specified client option does not have a corresponding User response: None.
optionset. The option is deleted.
System action: Audit processing continues. ANR4412I Data Base and Recovery Log Space
expansion triggered.
specify FIX=YES so that the error can be corrected. Explanation: A triggered space expansion had started.
ANR4413I ANR4419W
ANR4413I Recovery Log Space expansion Is ANR4417W Unable to Create Data Base Copy
Needed, megabytes needed Megabytes Volume Data Base Copy Volume for
needed. volume Data Base Volume.
Explanation: The recovery log is above the utilization Explanation: The Data Base Space Trigger was in the
percentage defined in a DEFINE SPACETRIGGER LOG processing of expanding the data base by creating new
command. An expansion of the indicated number of database volumes. In doing so, database copy volumes
megabytes are needed to be above the space trigger are created for mirroring. The indicated database copy
utilization value. volume could not be created for the primary database
volume named.
System action: Space expansion begins if supported
on this platform. System action: Server operation continues. A database
copy volume is not created for the indicated primary
volume.
User response: Use the Query DBVOL command to
ANR4414I Data Base Space expansion Is Needed,
determine if your database volume configuration is
megabytes needed Megabytes needed.
satisfactory. You may use the DEFINE DBCOPY
Explanation: The database is above the utilization command to define additional database volume copies,
percentage defined in a DEFINE SPACETRIGGER DB if necessary.
command. An expansion of the indicated number of
megabytes are needed to be above the space trigger
ANR4418W Unable to Define Data Base Copy
utilization value.
Volume Data Base Copy Volume for
System action: Space expansion begins if supported volume Data Base Volume.
on this platform.
Explanation: The Data Base Space Trigger was in the
User response: None. processing of expanding the data base by creating new
database volumes. In doing so, database copy volumes
are created for mirroring. The indicated database copy
ANR4415I Data Base and Recovery Log Space volume was created for the primary database volume
Expansion Completed. named, but could be registered with the server.
Explanation: A triggered space expansion had System action: Server operation continues. A database
completed. copy volumes is not registered for the indicated
System action: Normal operations resume. primary volume. The database copy volume still exists
on the system.
ANR4416W Unable to Determine Maximum Number satisfactory. You may use the DEFINE DBCOPY
of Data Base Volume Copies, rc=return command to retry the definition of the database
code. volume copy, if necessary.
Explanation: The Data Base Space Trigger was in the
processing of expanding the data base by creating new ANR4419W Unable to Determine Maximum Number
database volumes. In doing so, the maximum number of Recovery Log Volume Copies,
of copy volumes for any database volume is rc=return code.
determined. The process of determining this value
failed. Explanation: The Recovery Log Space Trigger was in
the processing of expanding the recovery log by
System action: Server operation continues. No creating new recovery log volumes. In doing so, the
additional database copy volumes are created during maximum number of copy volumes for any recovery
this database space expansion. log volume is determined. The process of determining
User response: Use the Query DBVOL command to this value failed.
determine if your database volume configuration is System action: Server operation continues. No
satisfactory. You may use the DEFINE DBCOPY additional recovery log copy volumes are created
command to define additional database volume copies, during this recovery log space expansion.
if necessary.
User response: Use the QUERY LOGVOL command to
determine if your recovery log volume configuration is
satisfactory. You may use the DEFINE LOGCOPY
command to define additional recovery log volume
copies, if necessary.

ANR4420W ANR4426W
ANR4420W Unable to Create Recovery Log Copy ANR4423I AUDITDB: Insufficient database space
Volume Recovery Log Copy Volume for to continue audit processing.
volume Recovery Log Volume.
Explanation: A database audit process found that
Explanation: The Recovery Log Space Trigger was in insufficient database space is available to continue
the processing of expanding the recovery log by audit processing.
creating new database volumes. In doing so, recovery
System action: Audit processing terminates.
log copy volumes are created for mirroring. The
indicated recovery log copy volume could not be User response: Use the dsmserv extend db command
created for the primary recovery log volume named. to increase the size of the server datbase and restart the
database audit function.
System action: Server operation continues. A recovery
log copy volume is not created for the indicated
primary volume. ANR4424W Database has reached Maximum Size in
Space Trigger.
User response: Use the QUERY LOGVOL command to
determine if your recovery log volume configuration is Explanation: The Data Base Space Trigger was
satisfactory. You may use the DEFINE LOGCOPY specified with a maximum size for the data base. That
command to define additional recovery log volume value has been reached for the size of the database.
copies, if necessary.
System action: Server operation continues. No
additional database space expansion will occur as a
ANR4421W Unable to Define Recovery Log Copy result of the database space trigger.
Volume Recovery Log Copy Volume for
volume Recovery Log Volume. User response: None. You may review the space
trigger settings and use the UPDATE SPACETRIGGER
Explanation: The Recovery Log Space Trigger was in DB command to adjust space trigger values.
creating new recovery log volumes. In doing so,
recovery log copy volumes are created for mirroring. ANR4425W Recovery Log has reached Maximum
The indicated recovery log copy volume was created Size in Space Trigger.
for the primary recovery log volume named, but could Explanation: The Recovery Log Space Trigger was
be registered with the server. specified with a maximum size for the recovery log.
System action: Server operation continues. A recovery That value has been reached for the size of the recovery
log copy volume is not registered for the indicated log.
primary volume. The recovery log copy volume still System action: Server operation continues. No
exists on the system. additional recovery log expansion will occur as a result
User response: Use the QUERY LOGVOL command to of the recovery log space trigger.
determine if your recovery log volume configuration is User response: None. You may review the space
satisfactory. You may use the DEFINE LOGCOPY trigger settings and use the UPDATE SPACETRIGGER
command to retry the definition of the recovery log LOG command to adjust space trigger values.
volume copy, if necessary.
ANR4426W Recovery Log can no longer be

ANR4422I AUDITDB: Insufficient database space Expanded by the Space Trigger.
to optimze audit processing.
Explanation: The Recovery Log Space Trigger was
Explanation: A database audit process found that going to automatically expand the recovery log.
insufficient database space is available to optimize Expanding the recovery log would cause the recovery
audit processing. If the audit can process, it will take log's size to exceed 13GB, which is beyond the server
much longer to complete than if the space was maximum limit for the recovery log.
available.
System action: Audit processing continues of possible, recovery log is not automatically expanded. No
but may terminate if very little space is available. additional recovery log expansion will occur as a result
User response: Use the dsmserv extend db command of the recovery log space trigger.
to increase the size of the server datbase and restart the User response: None. You may review the space
database audit function. trigger settings and use the UPDATE SPACETRIGGER
LOG command to adjust space trigger values. You may
also backup the data base and/or setup a database
backup trigger to cause the database to be backed up
more often. Backing up the database will decrease the
ANR4427W ANR4432W
recovery log utilization and you then use the REDUCE satisfactory. You may use the DEFINE LOGCOPY
LOG and DELETE LOGVOLUME command to command to retry the definition of the recovery log
decrease the size of the recovery log. volume copy, if necessary. There will be an additional
message in the activity log prior to this message
indicating the reason for the failure.
ANR4427W One or more Recovery Log Volumes
differ in number of copy volumes.
ANR4430W Unable to Define Data Base Volume
Explanation: The Recovery Log Space Trigger was in
Data Base Volume.
creating new volumes. In doing so, copy volumes are Explanation: The Data Base Space Trigger was in the
created for mirroring, and existing volumes are processing of expanding the data base by creating new
examined for mirroring. One or more recovery log database volumes. The indicated database volume was
volumes was found to have a different number of copy created, but could not be registered with the server.
volumes than other volumes of the same type. It is
System action: Server operation continues. A database
recommended that the same number of copy volumes
volume is not registered with the server. The database
be created for each volume of the same type (database
volume still exists on the system.
or log).
User response: Use the QUERY LOGVOL command to satisfactory. You may use the DEFINE DBVOLUME
determine if your volume configuration is satisfactory. command for the database volume named, to retry the
You may use the DEFINE LOGCOPY command to definition of the database volume copy, if necessary.
define additional copy volumes, if necessary. You may There will be an additional message in the activity log
use the DELETE LOGCOPY command to delete prior to this message indicating the reason for the
unnecessary copy volumes. failure.
ANR4428W One or more Data Base Volumes differs ANR4431I Recovery Log now Eligible for
in number of copy volumes. Expansion.
Explanation: The Data Base Space Trigger was in the Explanation: The Recovery Log Space Trigger has
processing of expanding the data base by creating new previously hit a point where expanding the recovery
volumes. In doing so, copy volumes are created for log would have caused the recovery log's size to exceed
mirroring, and existing volumes are examined for 13GB, which is beyond the server maximum limit for
mirroring. One or more data base volumes was found the recovery log. This caused automatic recovery log
to have a different number of copy volumes than other expansion to be halted. The recovery log size has
volumes of the same type. It is recommended that the shrunk but once again needs expansion and is now
same number of copy volumes be created for each eligible for expansion.
volume of the same type (database or log).
System action: Server operation continues, and the
System action: Server operation continues. automatic recovery log expansion will proceed.
User response: Use the Query DBVOL command to User response: None. None.
determine if your volume configuration is satisfactory.
You may use the DEFINE DBCOPY command to define
ANR4432W Data Base can no longer be Expanded
additional copy volumes, if necessary. You may use the
by the Space Trigger.
DELETE DBCOPY command to delete unnecessary
copy volumes. Explanation: The Data Base Space Trigger was going
to automatically expand the data base. Expanding the
database would cause the size of the database to
ANR4429W Unable to Define Recovery Log Volume
exceed 500GB, which is beyond the server maximum
Recovery Log Volume.
limit for the database.
Explanation: The Recovery Log Space Trigger was in
database is not automatically expanded. No additional
creating new recovery log volumes. The indicated
database expansion will occur as a result of the
recovery log volume was created, but could not be
recovery log space trigger until the database size is less
registered with the server.
than the maximum size and the trigger attributes allow
System action: Server operation continues. A recovery it to be expanded to a size less than the maxium.
log volume is not registered with the server. The
User response: None. You may review the space
recovery log copy volume still exists on the system.
trigger settings and use the UPDATE SPACETRIGGER
User response: Use the Query LOGVOL command to DB command to adjust space trigger values. You may
determine if your recovery log volume configuration is also reduce the database size, if possible.

ANR4433I ANR4440E
ANR4433I Data Base now Eligible for Expansion. ANR4437I Audit command: Invalid password
expiration period password expiration
Explanation: The Data Base Space Trigger has
period deleted for client node node name.
previously hit a point where expanding the database
would have caused the size of the database to exceed Explanation: A database audit process finds an invalid
500GB, which is beyond the server maximum limit for password expiration period for a client node. Because
the database. This caused automatic database expansion FIX=YES has been specified for the audit command, the
to be halted. The database size has shrunk or the space audit function deletes the password expiration period,
trigger values have been adjusted to allow expansion. causing the default, global password expiration period
to take effect for the client node.
System action: Server operation continues, and
automatic database expansion may proceed. System action: Audit processing continues.
User response: None. User response: After the AUDIT command completes,
that was updated. Use the UPDATE NODE command
ANR4434E Audit command: Password expiration
to set the correct password expiration period for the
found for unknown client node node
node.
name.
ANR4438E Audit command: Password expiration
password expiration period for a client node, but the
found for unknown administrator
client node is not defined correctly in the server
administrator name.
database.
password expiration period for an administrator, but
User response: If the audit command has not been the administrator is not defined correctly in the server
issued with FIX=YES specified, reissue the audit database.
function specifying FIX=YES so that the error can be
corrected.
issued with FIX=YES specified, reissue the audit
ANR4435I Audit command: Password expiration
period deleted for unknown client node
corrected.
node name.
ANR4439I Audit command: Password expiration
password expiration period for a client node, but the
period deleted for unknown
client node is not defined correctly in the server
administrator administrator name.
database. Because FIX=YES has been specified for the
audit command, the audit function deletes the Explanation: A database audit process finds a
password expiration period. password expiration period for an administrator, but
the administrator is not defined correctly in the server
database. Because FIX=YES has been specified for the
User response: None. audit command, the audit function deletes the
password expiration period.
ANR4436E Audit command: Invalid password System action: Audit processing continues.
expiration password expiration period for
Explanation: A database audit process finds an invalid
ANR4440E Audit command: Invalid password
password expiration period for a client node.
expiration password expiration period for
System action: Audit processing continues. administrator administrator name.
User response: If the audit command has not been Explanation: A database audit process finds an invalid
issued with FIX=YES specified, reissue the audit password expiration period for an administrator.
corrected.
corrected.
ANR4441I ANR4449E
ANR4441I Audit command: Invalid password ANR4445I Context parameter set to value.
expiration period password expiration
Explanation: Determines if context reporting will be
period deleted for administrator
generated when an ANR9999D error occures. This is
administrator name.
turned on or off with the SET CONTEXT messaging
Explanation: A database audit process finds an invalid command.
password expiration period for an administrator.
command, the audit function deletes the password User response: None.
expiration period, causing the default, global password
expiration period to take effect for the administrator.
ANR4446I Audit command: Auditing address
System action: Audit processing continues. definitions.
User response: After the AUDIT command completes, Explanation: This message is displayed during a
use the QUERY ADMIN command to examine the database audit and indicates that the name address
administrator that was updated. Use the UPDATE definitions are being examined by the database audit
ADMIN command to set the correct password process.
expiration period for the administrator.
ANR4442E Audit command: Extended attribute User response: None.

extended attribute type is not a valid
attribute type. ANR4447E Audit command: An invalid data mover
Explanation: A database audit process finds an type was encountered for data mover
extended attribute type that is not supported. name.
System action: Audit processing continues. Explanation: A database audit process encounters an
invalid data mover type for the specified data mover.
issued with FIX=YES specified, reissue the audit System action: Audit processing continues.
function specifying FIX=YES so that the error can be User response: Reissue the audit command with
corrected. FIX=YES so that the attribute can be corrected.
ANR4443I Audit command: Invalid extended ANR4448E Audit command: An invalid data mover
attribute extended attribute type has been type was encountered for data mover
deleted. datamover name - the data mover entry
Explanation: A database audit process finds an will be removed.
extended attribute type that is not supported. Because Explanation: A database audit process encounters an
FIX=YES has been specified for the audit command, the invalid data mover type for the specified data mover.
audit function deletes extended attribute.
System action: Because FIX=YES has been specified
System action: Audit processing continues. for the command, the data mover entry will be
User response: None. removed. Audit processing continues.
User response: If you want the data mover entry to be
ANR4444W Command: Input volume volume name defined you must redefine this data mover after the
cannot be processed. audit command has completed.
Explanation: During a DSMSERV DISPLAY

DBBACKUPVOLUME command, the server cannot ANR4449E Audit command: An invalid data mover
display the necessary information about the specified attribute was encountered for data mover
backup volume. name.
System action: The volume is not processed. Explanation: A database audit process encountered an
Processing continues for all the volumes in the given invalid data mover attribute for the specified data
volume list. mover.
User response: Examine previous error messages for System action: Audit processing continues.
the cause of failure. User response: Reissue the audit command with

ANR4450E ANR4458I
FIX=YES has been specified for the command, the path

ANR4450E Audit command: An invalid data mover
entry will be removed.
attribute was encountered for data
mover data mover name - the data mover System action: Audit processing continues.
User response: If you want the TSM server to use this
Explanation: A database audit process encounters an path you must redefine the source name, verify the
invalid data mover attribute for the specified data destination name exists, and then redefine the path
mover. after the audit command has completed.
System action: Because FIX=YES has been specified
for the command, the data mover entry will be ANR4455E Audit command: An invalid destination
removed. Audit processing continues. attribute was encountered for source
name and destination destination name
User response: If you want the data mover entry to be
defined you must redefine this data mover after the Explanation: A database audit process encountered an
audit command has completed. invalid destination attribute in a path definiton with
the specified source name and destination name.
ANR4451E Audit command: An invalid disk attribute System action: Audit processing continues.
was encountered for disk name.
Explanation: A database audit process encountered an FIX=YES so that the attribute can be corrected.
invalid disk attribute for the specified disk.
System action: Audit processing continues. ANR4456E Audit command: An invalid destination
attribute was encountered for source
name and destination destination name -
the path entry will be removed.
ANR4452E Audit command: An invalid disk attribute
invalid destination attribute in a path definition with
was encountered for disk name - the disk
the specified source name and destination name.
Explanation: A database audit process encounters an the path entry will be removed.
invalid disk attribute for the specified disk. Because
FIX=YES has been specified for the command, the disk
entry will be removed. User response: If you want the TSM server to use this
path you must redefine the source name, verify the
destination name exists, and then redefine the path
User response: If you want the disk entry to be after the audit command has completed.
defined you must redefine this disk after the audit
command has completed.
ANR4457E Audit command: KEEPMP found for
unknown client node node name.
ANR4453E Audit command: An invalid source
KEEPMP setting for a client node, but the client node is
name and destination destination name
not defined correctly in the server database.
Explanation: A database audit process encountered an
invalid source attribute in a path definiton with the
specified source name and destination name. User response: If the audit command has not been
User response: Reissue the audit command with corrected.
ANR4458I Audit command: KEEPMP setting deleted
ANR4454E Audit command: An invalid source for unknown client node node name.
name and destination destination name -
KEEPMP setting for a client node, but the client node is
the path entry will be removed.
not defined correctly in the server database. Because
Explanation: A database audit process encounters an FIX=YES has been specified for the audit command, the
invalid source attribute in a path definition with the audit function has deleted the KEEPMP setting.
specified source name and destination name. Because
ANR4459E ANR4466I

ANR4463E Audit command: Invalid TCP name,
address or GUID length invalid length for
ANR4459E Audit command: Invalid KEEPMP setting client node node name.
KEEPMP setting for client node node
name.
invalid TCP name, address or globally unique identifer
Explanation: A database audit process found an length for a client node.
invalid KEEPMP setting for a client node.
User response: If the audit command has not been issued with FIX=YES specified, reissue the audit
issued with FIX=YES specified, reissue the audit function specifying FIX=YES so that the error can be
function specifying FIX=YES so that the error can be corrected.
corrected.
ANR4464I Audit command: Invalid TCP name,
ANR4460I Audit command: Invalid KEEPMP setting address or GUID length invalid length
KEEPMP setting deleted for client node deleted for client node node name.
node name.
Explanation: A database audit process found an invalid TCP name, address or globally unique identifer
invalid KEEPMP setting for a client node. Because length for a client node. Because FIX=YES has been
FIX=YES has been specified for the audit command, the specified for the audit command, the audit function
audit function has deleted the KEEPMP setting, causing sets the TCP name, address and GUID to blank. The
the default, KEEPMP setting to take effect for the client values will be reset when the client signs on to the
node. server.
User response: After the AUDIT command completes, User response: After the AUDIT command completes,
use the QUERY NODE command to examine the node use the QUERY NODE command to examine the node
that was updated. Use the UPDATE NODE command that was updated. The values should be blank.
to set the correct KEEPMP setting for the node.
ANR4465I Audit command: An incorrect transaction
ANR4461E Audit command: TCP name, address and group size was found for node node
GUID found for unknown client node name.
node name.
Explanation: A database audit process found a TCP invalid information used for controlling the transaction
name, address and globally unique identifer for a client group size for the node indicated.
node, but the client node is not defined correctly in the
server database.
User response: If the audit command has not been function specifying FIX=YES so that the error can be
issued with FIX=YES specified, reissue the audit corrected.
corrected.
ANR4466I Audit command: An incorrect transaction
group was found for node node name.
ANR4462I Audit command: TCP name, address and This information will be corrected.
GUID deleted for unknown client node
node name.
invalid information used for controlling the transaction
Explanation: A database audit process found a TCP group size for the node specified. Because FIX=YES has
name, address and globally unique identifer for a client been specified, the audit function corrects the
node, but the client node is not defined correctly in the information.
for the audit command, the audit function deletes the
TCP name, address and GUID. User response: None.

ANR4467E ANR4476I
ANR4467E Audit command: Data Path Type Path was ANR4473E Audit command: Node missing from
found for unknown client node node session initiation attribute for client
name. node node name.
Explanation: A database audit process found a Data Explanation: A database audit process found a session
Path setting for a client node, but the client node is not initiation value for a client node's server-prompted
defined correctly in the server database. scheduling but the node definition was missing.
User response: If the audit command has not been User response: If the audit command has not been
issued with FIX=YES specified, reissue the audit issued with FIX=YES specified, reissue the audit
function specifying FIX=YES so that the error can be function specifying FIX=YES so that the error can be
corrected. corrected.
ANR4468I Audit command: The Data Path Type Path ANR4474I Audit command: Node missing from
setting was deleted for unknown client session initiation value for
node node name. server-prompted scheduling. Attribute
deleted for client node node name.
Explanation: A database audit process found a Data
Path setting for a client node, but the client node is not Explanation: A database audit process found a value
defined correctly in the server database. Because for a client node's server-prompted session iniiating
FIX=YES has been specified for the audit command, the attributes, but the node definition was mising. Because
audit function has deleted the KEEPMP setting. FIX=YES has been specified for the audit command, the
audit function sets the value to the default. The
attribute must be redefined with the REGISTER or
User response: None. UPDATE NODE commands.
ANR4471E Audit command: Invalid TCP address (
server-prompted scheduling ) or length
invalid length for client node node name.
that was updated.
invalid TCP address or length for a client node's
ANR4475E Audit command: Node missing from
server-prompted scheduling..
client address attribute for client node
System action: Audit processing continues. node name.
User response: If the audit command has not been Explanation: A database audit process found client
issued with FIX=YES specified, reissue the audit node addressing information for a client node's
function specifying FIX=YES so that the error can be server-prompted scheduling but the node definition
corrected. was missing.
ANR4472I Audit command: Invalid TCP name or
length for server-prompted
scheduling.invalid length deleted for
corrected.
invalid TCP name or length for a client node's
ANR4476I Audit command: Node missing from
server-prompted scheduling attributes. Because
session initiation value for
server-prompted scheduling. Attribute
audit function sets the TCP information to blank. The
deleted for client node node name.
values must be reset with the UPDATE NODE
command. Explanation: A database audit process found client
node addressing information for a client node's
server-prompted scheduling but the node definition
User response: After the AUDIT command completes, was missing.
that was updated. The values should be blank.
command, the audit function deletes the value. The
information must be redefined with the REGISTER or
UPDATE NODE commands.
ANR4477E ANR4485I

ANR4481I Command: Extraneous or incorrect entry
User response: After the AUDIT command completes, found for a proxy association. Target:
use the QUERY NODE command to examine the node node_id_1 Agent: node_id_2
that was updated.
Explanation: An extraneous or incorrect entry was
found for a proxy association.
ANR4477E Audit command: An invalid data path type
path setting was found for client node
node name. User response: Issue the AUDITDB command again,
using the FIX=YES parameter.
incorrect data path setting for a client node.
ANR4482I Command: Extraneous or incorrect entry
found for a proxy association. Target:
User response: If the audit command has not been node_id_1 Agent: node_id_2
function, specifying FIX=YES so that the error can be
found for a proxy association. The entry will be
corrected.
removed.
ANR4478I Audit command: An incorrect data path
type path setting was deleted for client User response: None, because the AUDITDB
node node name. processing performed the necessary corrective action.
invalid data path setting for a client node. Because ANR4483I Node node name issued command: Set
FIX=YES has been specified for the audit command, the Access copy type file space namehigh-level
audit function has deleted the Data Path setting, addresslow-level address authorized node
causing the default Data Path setting to take effect for name ,authorized owner name.
the client node.
Explanation: The SET ACCESS command completed.
that was updated. Use the UPDATE NODE command
to set the correct data path setting for the node. ANR4484I Node node name issued command: Delete
Access copy type file space namehigh-level
addresslow-level address authorized node
ANR4479I Extraneous or incorrect entry found for a
name ,authorized owner name.
backup group member.
Explanation: The DELETE ACCESS command
completed.
found for a member of a backup group.
User response: Issue the AUDITDB command again,
using the FIX=YES parameter.
ANR4485I A storage pool space trigger has been
defined and enabled for storage pool
ANR4480I Extraneous or incorrect entry fixed for a
storage pool name.
backup group member.
Explanation: A storage pool space trigger has been
defined with a DEFINE SPACETRIGGER command for
found for a member of a backup group. If this was an
the specified storage pool.
incorrect entry, it was fixed. If this was an extraneous
entry, it was deleted. System action: None.
User response: None, becasue the AUDITDB
processing performed the necessary corrective action.

ANR4486I ANR4494I
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.
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.
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
ANR4495E ANR4502W
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

ANR4503W ANR4512E
options file, restart the server.

ANR4510E The server could not write sequential
volume history information to volume
ANR4503W The server current date current date is history file name. To restore the database,
earlier than the date in a server record access to this file is required.
server date.
Explanation: While attempting to write sequential
Explanation: The server has detected that the current volume history information to defined history files, the
system date is an earlier date than the date in a server server could not write to the specified file. The
record that is being processed. Possible causes for this database cannot be restored until this file can be
problem are the current system date is invalid, the accessed.
server was previously run with a future date, or there
System action: The server does not write volume
is an error in the server record. If the server was run
history information to the file specified
with a future date, this message will continue to appear
until that date has passed, or all records with the future User response: Examine any error messages that may
date have been deleted from the server. have been displayed prior to this message and correct
any problems. Ensure that the server has permission to
System action: Processing continues. The processing
write to the file indicated and that there is sufficient
for the current object may not occur as expected.
space in the file system for the file. On MVS, ensure
User response: On the machine on which the server is that the data set has been allocated and that the server
running, verify that the system date is correct. has permission to write to the data set. After correcting
the problem, use the BACKUP VOLHISTORY
command to write sequential volume history
ANR4504E Command: The specified point in time is information to the file.
earlier than the point in time of the base
backup set.
ANR4511E Volume history file volume history file
Explanation: The point in time specified for the name could not be opened. To restore the
differential backup set is earlier than the point in time database, access to this file is required.
of its base backup set.
Explanation: While attempting to read or write
System action: The server does not process the sequential volume history information from defined
command. history files, the server was unable to open the
User response: Reissue the command, specifying a specified file name. The database cannot be restored
later point in time. until this file can be accessed.
System action: The server does not read or write
ANR4505E Required table of contents could not be volume history information from the specified file.
created for backup set for node name as User response: Examine any error messages that may
set name (data type data type). have been displayed prior to this message and correct
Explanation: A table of contents could not be created any problems. Ensure that the server has permission to
for the named object set, but a table of contents was write to the file indicated and that there is sufficient
required (TOC=YES was specified or implied). space in the file system for the file. On MVS, ensure
that the data set has been allocated and that the server
System action: The backup set is deleted. has permission to write to the data set.
User response: Correct the problem that prevented the
table of contents from being created and generate the ANR4512E A database transaction failure was
backup set again. encountered in processing sequential
volume history information.
ANR4506W Backup set for node name as set name Explanation: While attempting to process sequential
(data type data type) requires a table of volume history information, the server encountered a
contents. database transaction error.
Explanation: The specified backup set requires a table System action: The operation fails. Usage for a
of contents, but TOC=YES was not specified. sequential volume was not properly recorded for later
System action: The server will attempt to create a reference.
table of contents for the backup set. If the table of User response: Examine error messages that may have
contents creation fails, the backup set will be deleted. been displayed prior to this message and correct any
User response: None. problems, if possible. If this does not resolve the
problem, contact your support representative.
ANR4513E ANR4520I
history information. If the current server task requires

ANR4513E A database lock conflict was
this information, the task ends.
encountered in processing sequential
volume history information. User response: Examine error messages that may have
Explanation: While attempting to process sequential
volume history information, the server encountered a
proper authority to read from the defined volume
database locking conflict.
history files. If you are doing a database restore, issue
System action: The operation fails. This usually means RESTORE DB DEVCLASS=VOL.
that usage for a sequential volume was not properly
recorded for later reference
ANR4517E No files have been defined for storing
User response: Examine error messages that may have sequential volume history information -
been displayed prior to this message and correct any information cannot be read.
problems, if possible. If this does not resolve the
Explanation: The server is attempting to read from at
problem, contact your support representative.
least one of the volume history files defined in the
server options file. Since no files were defined for this
ANR4514E Sufficient database space is not information the read operation fails.
available for the server while processing
System action: Server operation ends.
sequential volume history information.
User response: You can restore the database specifying
the volume names for each restore operation (in order)
volume history information, the server found that
up to the desired point-in-time. If a volume history file
sufficient database space was not available for updates.
is available, specify its name in the server options file
System action: The operation fails. Usage for a and retry the operation.
sequential volume was not properly recorded for later
reference.
ANR4518E Volume history file file name line line
User response: To increase the amount of database number does not have the proper format
space available to the server, an authorized - read operation fails.
Explanation: The server is attempting to read from a
DEFINE DBVOLUME command, and extend the size of
volume history file and encounters a record that does
the database by using the EXTEND DB command.
not have the proper format.
System action: Server operation terminates.
ANR4515E Sufficient recovery log space is not
available for the server while processing User response: Examine the file specified to determine
sequential volume history information. if the invalid record can be located and corrected. If the
file is corrupted or does not contain valid volume
history entries, it cannot be used for the desired
volume history information, the server finds that
operation.
sufficient recovery log space is not available for
updates.
ANR4519W Volume History File does not reflect
System action: The operation fails. Usage for a
latest Storage Agent Updates
sequential volume was not properly recorded for later
reference. Explanation: The storage agent failed to have the
volume history file on the server updated with the
latest changes from the storage agent.
administrator can add database volumes by using the System action: The storage agent continues
DEFINE LOGVOLUME command, and extend the size processing.
of the database by using the EXTEND LOG command.
User response: To bypass the problem, a BACKUP
VOLHIST command can be issued from an admin
ANR4516E Server could not read sequential volume client connected to the server. The problem may be due
history information from any defined to a temporary loss of communication with the server.
files.
Explanation: While attempting to read sequential ANR4520I Storage Pool storage pool name is being
volume history information from defined history files, skipped during a space allocation. A
the server finds that it cannot open any of the files request for request amount megabytes
defined in the server options file. was made but only available amount
megabytes were available.
System action: The server does not read volume

ANR4521E ANR4527W
Explanation: A request for storage was made in the User response: None.
indicated storage pool. The storage pool has a capacity
of the number of megabytes shown. The requested
ANR4524I Volume volume name defined in Storage
amount can not be satisfied in the storage pool being
Pool storage pool name as a result of
skipped. The next storage pool, if any, will be tried in
storage pool triggered space expansion.
an attempt to satisfy the request.
Explanation: A triggered space expansion has caused
System action: The storage server skips the indicated
the indicated volume to be created in the storage
storage pool and tries to allocate storage in a "next"
shown in the message. The volume definition is the
pool.
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
private volumes in the storage pool (use the DEFINE User response: None.
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
is function properly, or ensuring that the server is set
ANR4522E RESTORE DB failed with LOG file
up with sufficient permissions to access and create files
error.
on the file system to which Tivoli Storage Manager is
Explanation: The LOG file is not associated with the writing.
current log sequence.
System action: RESTORE DB terminates. ANR4526E Storage Pool Space trigger for storage
pool name is ended; the thread resource
User response: Issue REMOVE DB first and retry the
not available.
RESTORE DB.
Explanation: The server cannot start a thread to
handle storage pool expansion for the indicated storage
ANR4523I Storage Pool Space expansion triggered.
pool.
Storage Pool storage pool name with
capacity of capacity megabytes requires System action: Server processing continues but the
percentage percent expansion for storage pool is not expanded.
expansion amount bytes of additional
space.
Explanation: A triggered space expansion has started application.
for the indicated storage pool. The storage pool has a
capacity of the number of megabytes shown. It is being
ANR4527W Storage Pool Space trigger for storage
expanded by the indicated percentage as directed by
pool name is disabled after volume
the storage pool space trigger for this storage pool, or
definition failures expansion failures.
by the default storage space trigger if this storage pool
Insufficient space for pool expansion.
has no dedicated trigger of its own. The percentage is
represented by the additional amount of space Explanation: The server failed to complete a storage
indicated. pool expansion for the indicated storage pool. The
number of failures in pool expansion is also displayed.
ANR4528W ANR4533E
System action: Server processing continues but the started. If there has been at least one full database
storage pool is not expanded. The storage pool space backup, the backup is an incremental database backup.
trigger for the indicated storage pool is disabled. Otherwise, a full database backup is started.
User response: Allocate additional storage space to System action:
the server. For storage pools of device type FILE,
User response:
additional directories may be added to the list of
directories that the associated device class uses for
storage. If this action is taken, the corresponding ANR4530I An automatic full database backup will
storage agent directories should be added via the be started. The total space used in log
UPDATE PATH command. The storage pool space file system is log space used megabytes,
trigger may be re-enabled with the UPDATE and the total space available in the log
SPACETRIGGER STG STPOOL=xx command, where xx file system is log space available
is the storage pool for which expansion has failed ( no megabytes. The ratio is log file system
space trigger parameters need be updated ). used ratio and is greater than the
threshold log file system utilization
threshold.
ANR4528W Storage Pool Space Expansion for storage
pool name is disabled due to previous Explanation: When the space used in the log file
expansion failures. After addressing system exceeds the threshold for log file system
space requirements, an UPDATE utilization, a full database backup is started.
SPACETRIGGER STG command must
be issued to allow automatic stgpool System action:
expansion. User response:
Explanation: The server failed to complete a storage
pool expansion for the indicated storage pool. The ANR4531I An automatic full database backup will
storage pool space trigger is disabled due to previous be started. The last log number used is
expansion failures. The storage pool space trigger may last log used and the first log number
be re-enabled with the UPDATE SPACETRIGGER STG used is first log used. The log file size is
STPOOL=xx command, where xx is the storage pool for log file size megabytes. The maximum log
which expansion has failed ( no space trigger file size is maximum log file size
parameters need be updated ). megabytes.
System action: Server processing continues but the Explanation: When the log space used since the last
storage pool is not expanded. The storage pool space database backup exceeds the maximum log file size, a
trigger for the indicated storage pool remains disabled. full database backup is started.
This message is re-issued periodically when expansion
is required but the storage pool space trigger remains System action:
disabled. User response:
User response: Allocate additional storage space to
the server. For storage pools of device type FILE, ANR4532W The total DB used in DB space is log
additional directories may be added to the list of space used megabytes, and the total space
directories that the associated device class uses for available in the DB space is log space
storage. If this action is taken, the corresponding available megabytes. The ratio is log file
storage agent directories should be added via the system used ratio.
UPDATE PATH command. The storage pool space
trigger may be re-enabled with the UPDATE Explanation: The DB space used exceeds the threshold
SPACETRIGGER STG STPOOL=xx command, where xx for DB space utilization, please define more DB space
is the storage pool for which expansion has failed ( no using EXTend DBSpace command.
space trigger parameters need be updated ). System action:
User response:
ANR4529I An automatic full or incremental
database backup will be started. The
active log space used is log space used is ANR4533E Database database name is invalid and
megabytes, and the active log space cannot be created.
available is log space available megabytes.
Explanation: Follow all of these rules when choosing
The ratio, active log used ratio, exceeds the
a database name or alias:
threshold log utilization threshold.
v Character strings that represent names of a database
Explanation: When the active log space used exceeds can contain any of the following characters: a-z, A-Z,
the log utilization threshold, a database backup is 0-9, @, #, and $.

ANR4534E ANR4539E
v A database name or alias must be unique in the

ANR4537I The active log space used is log space
database instance.
used is megabytes, and the active log
v A database name or alias is one to eight characters in space available is log space available
length. megabytes. The ratio, active log used ratio,
v The first character of the name must be an alphabetic exceeds the threshold log utilization
character, or a @, a #, or a $ character. threshold.
v The first three characters of the name cannot be any Explanation: When the active log space used exceeds
of the following strings: SYS, DBM, or IBM. the log utilization threshold, the active log space must
System action: DSMSERV FORMAT processing stops. be increased.
User response: Choose a different database name System action: None.

which meets the criteria indicated above and issue the User response: Increase the size of the active log
DSMSERV FORMAT command again. space. For more information, search the Tivoli Storage
Manager Information Center on increasing the size of
ANR4534E The active log size of active log size MB the active log.
exceeds the available space active log
space MB. ANR4538E The server could not write sequential
Explanation: There is not enough space for the active volume history information to the
log size specified in the DSMSERV FORMAT command. volume history file name temporary file.
System action: None. Explanation: The server failed to write to the specified
file. The volume history file cannot be updated until
User response: Ensure that the file systems you are this temporary file can be accessed.
using for database and recovery log activities have
enough space. Reissue the DSMSERV FORMAT System action: No volume history information was
command and specify a smaller value for the active log written to the temporary file specified.
size. For more information, see the DSMSERV FORMAT User response: Examine any error messages that
command in the Administrator's Reference. might have been displayed prior to this message and
correct any problems. Ensure that the server has
ANR4535E The active log directory active log permission to write to the specified file and that the file
directory is not valid. system has sufficient space for the file.
Explanation: The active log directory that is specified

in the DSMSERV FORMAT command does not exist. ANR4539E There is a mismatch in directory count
between Device Class device class name
System action: The database format operation failed. and Path Definition for Server server
name. The device class has directory count
User response: Verify that the file systems you have
directories while the path definition has
specified for formatting the server database and
path directory count directories.
recovery log are valid. Reissue the DSMSERV FORMAT
command with a valid active log directory. For more Explanation: The server was assigning a shared FILE
information, see the DSMSERV FORMAT command in library volume to a server or storage agent. Share FILE
the Administrator's Reference. libraries require a matching number of directories in
the PATH definition for the server or storage agent's
access to FILE drives and the server's device class
ANR4536E File Processor Value Unit table xml file
definition. For example, if the server has the following
could not be found or opened for read
device class definition: DEFINE DEVCLASS SFILE
access.
DEVTYPE=FILE MOUNTL=10 SHARED=YES
Explanation: The file could not be found or opened. DIR=D:\DIR1,E:\DIR2,F:\DIR3 a FILE library name
SFILE will be created along with 10 drives named
System action: Contents of the file are not parsed and
SFILE1 to SFILE10 in shared library SFILE. Each of
loaded to the database.
these drives might have scratch volumes created in
User response: Verify that the file exists in either the directories D:\DIR1, E:\DIR2 or F:\DIR3. (For UNIX
server instance directory or the server installation Platforms, substitute UNIX style names in the
directory. If the file does exist verify permissions for example).
read access. If the file does not exist obtain a copy from
For library clients and storage agents, the appropriate
the IBM Processor Value Unit website.
directory paths from those systems must be defined
using the DEFINE PATH command. An example, in
this case, might be DEFINE PATH STA1 SFILE1
SRCTYPE=SERVER DESTTYPE=DRIVE
ANR4540E ANR4544E
DIR=V:\DIR1,W:\DIR2,X:\DIR3 LIBRARY=SFILE directory entry with a server which is either not

which means that server (or storage agent) STA1 defined or has an invalid length in the DevClass.Dirs
accesses directory D:\DIR1 using V:\DIR1 from the table. This table relates directories to device classes and
STA1 system, E:\DIR2 on the server is accessed using paths. The class ID of the table entry is shown, along
W:\DIR2 on STA1, and that F:\DIR3 is accessed using with the server name. However, if the server name has
X:\DIR3 on STA1. If the number of directories between an invalid length, only blanks are shown.
the PATH and DEVCLASS do not match, there could
be problem in accessing the resulting file in the future.
User response: If the FIX=YES parameter was
System action: Processing continues. Another
specified, the data base record with the incorrect entry
directory path is chosen. This might result in a
will be deleted. Otherwise, reissue the audit command
subsequent access failure by the storage agent.
with FIX=YES, so that the incorrect record can be
User response: Use the QUERY DEVCLASS classname deleted. After records with incorrect entries have been
F=D and the QUERY PATH pathname F=D commands removed, review directories associated with device
to compare the directory lists for the device class and classes and paths with the following commands:
the path and ensure that they are synchronized. QUERY DEVCLASS F=D QUERY PATH F=D
ANR4540E Audit command: Invalid device class ANR4543E Audit command: Mismatched server for
device class id found in DevClass.Dirs device class device class id in
table. DevClass.Dirs table. Server ID in table
is server id. Server ID in data base is
found server id.
non-existent device class or a device class with an
invalid access strategy for a record in the Explanation: A database audit process finds a
Devclasses.Dirs table. directory entry with a server which does not match the
path source name in the DevClass.Dirs table. This table
relates directories to device classes and paths. The class
User response: If the FIX=YES parameter was ID of the table entry is shown, along with the server ID
specified, the data base record with the incorrect entry in the table and the ID that was found when searching
will be deleted. Otherwise, reissue the audit command using the source name.
deleted. After records with incorrect entries have been
removed, review directories associated with Device User response: If the FIX=YES parameter was
classes and Paths with the following commands: specified, the data base record with the incorrect entry
QUERY DEVCLASS F=D QUERY PATH F=D will be deleted. Otherwise, reissue the audit command
ANR4541E Audit command: Invalid directory for
removed, review directories associated with device
device class device class id in
classes and paths with the following commands:
DevClass.Dirs table.
QUERY DEVCLASS F=D QUERY PATH F=D
directory entry whose length is longer than allowed for
ANR4544E Audit command: Invalid library for device
the indicated device class id in the DevClass.Dirs table,
class device class id in the DevClass.Dirs
which relates directories to device classes and paths.
table.
User response: If the FIX=YES parameter was directory entry with a DEST name where the associated
specified, the data base record with the incorrect entry library can not be found. This record is in the
will be deleted. Otherwise, reissue the audit command DevClass.Dirs table. This table relates directories to
with FIX=YES so that the incorrect record can be device classes and paths. The class ID of the table entry
deleted. After records with incorrect entries have been is shown.
QUERY DEVCLASS F=D QUERY PATH F=D User response: If the FIX=YES parameter was
specified, the database record with the incorrect entry
ANR4542E Audit command: Invalid server for device
class device class id in DevClass.Dirs
table. The server name in the table is
server name.
Explanation: A database audit process finds a QUERY DEVCLASS F=D QUERY PATH F=D

ANR4545E ANR4553I
User response: Only one database dump can be

ANR4545E Audit command: Invalid drive for device
started at one time. Use the QUERY PROCESS
class device class id in the DevClass.Dirs
command to monitor the dump that is in progress.
table.
When completed, issue the database dump command
Explanation: A database audit process finds a to start another database dump if required.
directory entry with a DEST name where the associated
drive (DESTNAME ) can not be found. This record is in
ANR4550I Full database backup (process process ID)
the DevClass.Dirs table. This table relates directories to
completed. Total bytes backed up: total
device classes and paths. The class ID of the table entry
DB bytes.
is shown.
Explanation: A full database backup process has
completed. The output volumes used in this backup
User response: If the FIX=YES parameter was may be used during a database restore operation.
specified, the database record with the incorrect entry
with FIX=YES, so that the incorrect record can be User response: None.
classes and paths with the following commands: ANR4551I Incremental database backup (process
QUERY DEVCLASS F=D QUERY PATH F=D process ID) completed. Total bytes
backed up: total DB bytes.
ANR4547W The clock on the remote server Explanation: An incremental database backup process
server_name differs from the clock on the has completed. The output volumes used in this
local server by seconds seconds. backup may be used in conjunction with any preceding
volumes in the backup series during a database restore
Explanation: The clocks on the local and remote operation.
servers are not consistent. This can cause various
problems such as inconsistent status reporting. System action: None.
User response: Make sure that the clocks on all

servers are set correctly. If possible, use an internet time ANR4552I Full database backup triggered; started
service to automatically synchronize the clocks. as process process ID.
Explanation: A background process, triggered by the
ANR4548W command: The specified at-risk interval LOGFULLPCT parameter on a DEFINE
of interval hours exceeds the activity DBBACKUPTRIGGER command, was started to back
summary retention of retention days. up the full contents of the database. The full database
backup process is assigned the process ID shown.
Explanation: The activity summary is used to
determine if a client has been backed up within the System action: The database backup process starts
at-risk interval. If the interval exceeds the activity and server operation continues.
summary retention, the server may not be able to find User response: The administrator may query the
a qualifying backup and would consider the client to status of the database backup process by using the
be unprotected. QUERY PROCESS command, or cancel the process by
System action: Processing continues. using the CANCEL PROCESS command.
User response: Either invoke the command again to

reduce the interval or use the SET ANR4553I Incremental database backup triggered;
SUMMARYRETENTION command to increase the started as process process ID.
activity summary retention. Explanation: A background process, triggered by the
LOGFULLPCT parameter on a DEFINE
ANR4549I Database dump command: A database DBBACKUPTRIGGER command, was started to
dump is already in progress. incrementally back up the contents of the database. The
incremental database backup process was assigned the
Explanation: This message is issued in response to a process ID shown.
database dump command and indicates that a database
dump cannot be started because a dump is already in System action: The database backup process starts
progress. and server operation continues.
System action: Server operation continues. The User response: The administrator may query the
requested database dump is not started. status of the database backup process by using the
ANR4554I ANR4562I
QUERY PROCESS command, or cancel the process by

ANR4558I Snapshot database backup (process
using the CANCEL PROCESS command.
process ID) completed. Total bytes
backed up: total DB bytes.
ANR4554I Backed up number of pages backed up of
Explanation: A differential database backup process
number of pages to back up in current
has completed. The output volumes used in this
operation database pages.
backup may be used in conjunction with preceding
Explanation: Periodically, during a database backup, volumes in the full backup during a database restore
the server displays the number of pages backed up. operation.
ANR4555I Database backup process process ID ANR4559I Backup DB is in progress.

canceled.
Explanation: The database backup in process.
Explanation: The database backup process was
canceled by an administrator with the CANCEL
PROCESS command. User response: None.
System action: The database backup process is ended.
ANR4560I Triggered database backup will be
retried in number of seconds seconds.
Explanation: Because of a problem encountered
ANR4556W Attention: the database backup
during a triggered database backup, the current backup
operation did not free sufficient
stops but will be retried after the time period shown.
recovery log space to lower utilization
below the database backup trigger. The System action: The system waits for the specified
recovery log size may need to be period and then retries a database backup.
increased or the database backup trigger
User response: If possible, correct the condition that
parameters may need to be adjusted.
stopped the database backup. If the problem persists,
Explanation: A database backup process has contact your service representative.
completed. The server is running in roll-forward mode
and the recovery log utilization remains above that
ANR4561I Triggered database backup retry delay
specified in the database backup trigger.
ended; checking database backup trigger
System action: A database backup operation will be criteria.
triggered. Unless this situation is corrected, database
Explanation: Because a triggered database backup had
backups will be triggered rapidly, one after the other.
been stopped due to a problem, the system waited
User response: If a database backup operation does before retrying. The retry wait period has ended, and
not free up enough recovery log space to reset the system can now retry the database backup.
utilization below the database backup trigger, the
System action: Database backup begins.
recovery log needs to be extended or the database
backup trigger updated to a higher log full percentage User response: None.
or a higher log free percentage or a higher minimum
interval.
ANR4562I Database backup criteria is no longer
met; triggered database backup
ANR4557I Differential database backup (process canceled.
process ID) completed.
Explanation: Because a triggered database backup had
Explanation: A snapshot database backup process has been stopped due to a problem, the system waited
completed. before retrying. The retry wait period has ended, and
the system determined that the criteria for triggering a
database backup was no longer met.
System action: The system waits until the database
backup trigger criteria is met before triggering another
database backup.

ANR4563I ANR4574E
ANR4563I Unable to trigger database backup - a ANR4571E Database backup/restore terminated -

database define, delete, extend, reduce, insufficient number of mount points
or backup operation is already in available for removable media.
progress.
Explanation: During database backup or restore, the
Explanation: A database backup was triggered, but a server cannot allocate sufficient mount points for the
command that is modifying or backing up the database volumes required.
is already active.
System action: If the database backup was started
System action: The backup stops and the server waits with the BACKUP DB command, the database backup
for the retry period to expire and then tries the is ended and server operation continues. If the database
database backup again. backup was triggered automatically, the backup stops
and the server waits for the retry period to expire and
then tries the database backup again. A database
restore is ended.
ANR4564I Unable to trigger database backup -
User response: For database backup, make more
mount points available if necessary. For database
Explanation: A database backup was triggered, but restore processing, make sure the device class has
there is not enough server memory available. sufficient mount points defined in the device
configuration information file that is pointed to in the
System action: The backup stops and the server waits server options file.
for the retry period to expire and then tries the
database backup again.
ANR4572E Database restore terminated - excessive
User response: If necessary, make more memory read errors encountered.
Explanation: During database restore, read errors
occur that prevent the restore from continuing.
ANR4565E Unable to trigger database backup -
thread resource not available. System action: Database restore processing stops.
Explanation: A database backup was triggered, but User response: Use a different device for the restore
the server cannot start a thread for the backup process. operation. If the problem persists, contact your service
representative.
System action: The backup stops and the server waits
for the retry period to expire and then tries the
database backup again. ANR4573E Database backup terminated - excessive
write errors encountered.
User response: If the error persists, it may indicate a
shortage of server memory. Allocate additional server Explanation: During database backup, write errors
memory. occur that prevent the backup from continuing.
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.
System action: If the database backup was started 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
with the BACKUP DB command, the database backup
server options file.
ANR4575E ANR4579E
then tries the database backup again. A database then tries the database backup again.
restore is ended.
User response: Specify a volume that is not in use or
User response: If possible, determine and correct the defined in a storage pool, and that has not been
cause of the interruption. If the problem cannot be previously used for an export, a database dump, or a
corrected, contact your service representative. database backup operation as recorded in the server
volume history information. The QUERY VOLUME
command may be used to display the names of
ANR4575E Database backup/restore terminated -
volumes that are defined to server storage pools. The
QUERY VOLHISTORY command may be used to
available.
display the names of volumes that have been used for
Explanation: During a database backup or restore export, database dump, or database backup operations.
operation, the server runs out of recovery log space.
System action: If the database backup was started ANR4578E Database backup/restore terminated -
with the BACKUP DB command, the database backup required volume was not mounted.
operation, a required volume cannot be mounted,
because the mount request was canceled.
restore is terminated. System action: If the database backup was started
User response: For database backup, make more
server recovery log space available, if necessary. For
database restore, contact your service representative.
ANR4576E Database backup/restore terminated - restore is terminated.
User response: Issue the command again or wait for
available.
the server to retry the backup and make sure the
Explanation: During a database backup or restore necessary volumes are accessible. If you are restoring a
operation, the server runs out of database space. database to a given date or doing a roll-forward
restore, restart the entire restore operation. If you are
System action: If the database backup was started restoring a single database backup with COMMIT=NO,
with the BACKUP DB command, the database backup reissue the restore command. If you are restoring a
is ended and server operation continues. If the database database backup with COMMIT=YES, restore the
backup was triggered automatically, the backup stops complete backup series from the beginning.
then tries the database backup again. The database
restore process attempts to set the database capacity to ANR4579E Database backup/restore terminated -
the required capacity to hold the database being thread resource not available.
restored. If this fails, the restore operation is ended.
User response: For database backup, make more operation, the server cannot start a thread for the
server database space available, if necessary. For backup process.
database restore, make sure that the size of the online
database is at least the same capacity as the database
being restored.
ANR4577E Database backup terminated - volume and the server waits for the retry period to expire and
already in use. then tries the database backup again. A database
Explanation: During a database backup operation, a
volume cannot be used because it is already defined in User response: Retry the command or wait for the
a storage pool, or has been previously used by an server to retry the backup if it was started by the
export, a database dump, or a database backup backup trigger. If the error persists, it may indicate a
operation (as recorded in the volume history) or is in shortage of server memory.

ANR4580E ANR4587E
ANR4580E Database backup/restore terminated - ANR4584E Database restore terminated -

insufficient memory available. incomplete input volume list.
Explanation: During a database backup or restore Explanation: The list of volumes needed for the
operation, there was not enough server memory restore operation was incomplete. At least one volume
available. needed for the restore operation is missing from the
end of the list.
with the BACKUP DB command, the database backup System action: The database restore is terminated.
User response: If you are using a DSMSERV
RESTORE DB command with the VOLUMENAMES
parameter specified, verify that all the volumes within
a database backup operation are included in the list.
Ensure that all the volume names are specified in the
User response: If necessary, make more memory correct sequential order. For a restore with
available to the server. COMMIT=NO, reissue the last restore command. For a
restore with COMMIT=YES, restart the restore from the
beginning of the full backup. If you are using a
ANR4581W Database backup/restore terminated -
DSMSERV RESTORE DB command with the TODATE
parameter specified, the server created a list of volumes
Explanation: During a database backup or restore needed for the restore operation. Examine the volume
operation, the server encounters an internal error. history files to try to determine the error or use a
different volume history file if available. You can also
System action: If the database backup was started restore the database by specifying the volume names
with the BACKUP DB command, the database backup for each restore operation up to the desired point in
is ended and server operation continues. If the database time.
then tries the database backup again. A database ANR4585W Volume History File does not exist -
restore is terminated. Backup/Restore DB operation requires
volume history file.
Explanation: Volume history file is needed for the
backup/restore DB operation. .
ANR4582E Database restore terminated - volume
cannot be used. System action: .
Explanation: During a database restore operation, a User response: Please specify volume history file in
volume has been mounted but cannot be used. the dsmserv.opt.
System action: The restore operation is terminated.
ANR4586E Not able to get a DB2 connection.
User response: If a volume list was specified on the Backup DB operation will be
command, make sure the correct volume is being terminated.
specified and mounted. If no volume list was specified,
contact your service representative. Explanation: DB2 connection is needed for the backup
DB operation. .
ANR4583E Database backup terminated - output System action: Backup DB operation is terminated.
media full and scratch media could not
User response: Verify database manager resources.
be mounted.
Submit command again.
Explanation: During a database backup operation, an
out-of-space condition occurred writing to the
ANR4587E Database backup or restore
sequential media, and a scratch volume cannot be
configuration is incorrect; client node
mounted.
node name was attempted to be used for
System action: The database backup is ended and this operation.
Explanation: A server database backup or restore
User response: Reissue the command and specify operation was attempted and failed. The indicated
additional volume names on the command, or specify client node was used for the operation which is
SCRATCH=YES. incorrect. The server database backup and restore
operations are a restricted protocol and require the
explicit use of client node name $$_TSMDBMGR_$$.
ANR4588E ANR4592I
System action: Database backup or restore operation connect to the DB2 database and change the
failed and is terminated. configuration, as described in the following example:
User response: Verify that the configuration of the v Start DB2: db2start
dsm.sys file used by the Tivoli Storage Manager API v Connect to TSMDB1: db2 connect to TSMDB1
for the system where the server is installed. The server v Update the DB2 database configuration: db2 update
stanza in the dsm.sys file for the database backup must db cfg using NEWLOGPATH (log path from server
be configured as follows: options, e.g. /ALOG/tsminst1)
v The NODENAME option must specify v Terminate the connection to TSMDB1: db2 terminate
$$_TSMDBMGR_$$.
v Recycle DB2: db2stop/db2start
v If the server is configured for database backup and
v Verify that the new log path is in takes effect: db2
restore using TCP/IP, the server TCP/IP address
connect to TSMDB1; db2 get db cfg | grep "Path to
must be loopback (127.0.0.1).
log files ( on UNIX ) "
v The server is configured to listen on the appropriate
v Verify that the new log path is in takes effect: db2
TCP/IP port or SHMPORT.
connect to TSMDB1; db2 get db cfg | find "Path to
For more information, review the information in the log files ( on Windows ) "
Installation Guide and the Upgrade Guide.
ANR4590I Backup type backup series backup series
ANR4588E A database backup configuration might number operation backup operation in series
be incorrect. stream backup stream within operation
(always 1) sequence backup volume
Explanation: A server database backup operation
sequence number in operation taken on date
failed. The server database backup and restore
at time.
operations are a restricted protocol and require the
explicit use of the client node name Explanation: During a DSMSERV DISPLAY
$$_TSMDBMGR_$$. DBBACKUPVOL command, the server displays the
necessary information about a backup volume.
System action: The database backup operation fails
and is ended. System action: Processing continues for all volumes in
the given volume list.
User response: Verify that the configuration of the
dsm.sys file used by the Tivoli Storage Manager API User response: You can use this information to create
for the system where the server is installed. The server a list of volumes for a database restore when a volume
stanza in the dsm.sys file for the database backup must history backup file is not available.
be configured as follows:
v The NODENAME option must specify ANR4591I Selected backup series seriesId from date
$$_TSMDBMGR_$$. and time as best candidate available for
v If the server is configured for database backup and restore database processing.
restore using TCP/IP, the server TCP/IP address
Explanation: The DSMSERV RESTORE DB command
must be loopback (127.0.0.1).
evaluates the volume history file using the criteria
v The server is configured to listen on the appropriate specified for the command to determine the best
TCP/IP port or SHMPORT. candidate database backup to use.
For more information, review the information in the System action: None.
Installation Guide and the Upgrade Guide.
User response: Evaluate the backup series, date, and
time reported to determine if this meets the desired
ANR4589W The DB2 connection was lost following restore objectives. If these do not meet the objectives,
a database restore operation. re-issue the DSMSERV RESTORE DB with additional or
Explanation: The server database was restored, but changed information in order to achieve the desired
the DB2 connection failed. For this reason, if the path recovery objectives.
to the DB2 log directory was changed as part of a DB
restore operation, the database path to the log directory ANR4592I Restore database backup series seriesId
was not updated automatically. includes eligible operation opId with
System action: The server database is restored. volume volume name having sequence
sequence and using device class device
User response: If the path to the DB2 log directory class.
did not change, no action is needed. If the path to the
DB2 log directory changed, you must manually update Explanation: The DSMSERV RESTORE DB command
the path when the server is started. To update the path, evaluates the volume history file using the criteria
specified for the command to determine the best

ANR4593E ANR4596E
candidate database backup to use. The opId and volume

ANR4595E Restore database expects a stream
name for the indicated device class are candidate
sequence stream for backup series
volumes that will be evaluated and used for the restore
seriesID and operation operationID but it
database process.
could not be found in the available
System action: None. volume history files.
User response: Evaluate the backup series, date, and Explanation: Once the DSMSERV RESTORE DB
time reported to determine if this meets the desired command selects a candidate database backup series, it
restore objectives. If these do not meet the objectives, will validate the information from the backup data
re-issue the DSMSERV RESTORE DB with additional or stream and compare it to the information available
changed information in order to achieve the desired from the volume history file. In this case, the database
recovery objectives. backup has information for the indicated stream
sequence but it has been unable to find any
information about volumes used for that stream within
ANR4593E Restore database unable to find eligible this backup series and operation.
candidate to use for processing.
Explanation: The DSMSERV RESTORE DB command
evaluates the volume history file using the criteria User response: Evaluate the volume history file and
specified for the command to determine the best available volumes to use for restore of the database. If
candidate database backup to use. No eligible additional volumes are available for this series and
candidate backup series was found. operation, than add entries to the volume history file
for these volume and retry the operation. If no other
System action: None. volumes are available, than remove all entries from the
User response: Evaluate the volume history file and volume history that are assigned to this backup series
available volumes to use for restore of the database. ID. Once those entries are removed, retry the database
Manually add entries to the volume history file for a restore operation and it will attempt to select the next
backup series and corresponding volumes to consider best candidate for processing.
for restore database processing.
ANR4596E Restore database is unable to validate
ANR4594E Restore database expects volume the selected database backup for series
volumeName for backup series seriesID seriesID and operation operationID against
and operation operationID but it could the actual data from the database
not be found in the available volume backup stream.
history files. Explanation: Once the DSMSERV RESTORE DB
Explanation: Once the DSMSERV RESTORE DB command selects a candidate database backup series, it
command selects a candidate database backup series, it will validate the information from the backup data
will validate the information from the backup data stream and compare it to the information available
stream and compare it to the information available from the volume history file. In this case, the database
from the volume history file. In this case, the database backup is missing information which is needed in order
backup requires the specified volume for restore to perform a restore of the server database.
processing of this backup series but this volume was System action: None.
not found in the available volume history file
information. User response: This is likely caused by not having all
the necessary volumes available and specified in the
System action: None. volume history file. Or this is caused by having the
User response: Evaluate the volume history file and wrong volume designated with sequence 10001. If a
available volumes to use for restore of the database. If volume in the volume history file for this backup series
the specified volume is available, than add an entry to and operation is assigned 10001, try assigning a
the volume history file for this volume and retry the different volume as sequence 10001. The volume
operation. If this volume is not available, than remove assigned sequence 10001 is expected to have the
all entries from the volume history that are assigned to self-describing validation information and signatures
this backup series ID. Once those entries are removed, that are used by the restore processing for validation of
retry the database restore operation and it will attempt a given operation for a backup series. If this
to select the next best candidate for processing. information is not found or correct, this would result in
a restore failure.
ANR4597E ANR4602E
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.
command selects a candidate database backup series, it
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, ANR4600I Processing volume history file file name.
if this volume simply does not belong to this database Explanation: During a DSMSERV RESTORE DB
backup series or operation, that would result in this command with the TODATE parameter specified, the
failure as well. Removing this entry from the volume server is processing the listed file in order to build a
history file to eliminate it from consideration for this list of volumes needed for the restore operation.
backup series and operation or correcting the operation
id and series id to an approprite value would also System action: None.
resolve this. After considering the cases above and User response: None.
taking action for one or the other of them, retry the
restore database operation.
ANR4601E Incomplete volume list found for
TODATE date time - retrying.
ANR4598I Validating database backup information
for selected backup series seriesId and Explanation: During a DSMSERV RESTORE DB
operation operationId using volume command with the TODATE parameter specified, the
volumeName. server created a list of volumes needed for the restore
operation, but the list was incomplete.
Explanation: The database backup information for the
selected backup series selected from the volume history System action: The server tries to build the list again
will be validated against the information from the using a different volume history file specified in the
database backup itself. The volume history information server options file. If no other volume history files are
will be cross-checked to insure that the backup series, available, the server stops processing.
necessary volumes, and other attributes of the database User response: If the problem persists, examine the
backup are correct and complete for this operation. volume history files to try and determine the error. You
Note that if the database restore operation includes can also restore the database by specifying the volume
incremental database backups, the validation will be names for each restore operation up to the desired
done using the volumes assigned to sequence number point in time.
10001 for operationId 0 and the operationId
representing the best candidate for restore of the
incremental database backup data. ANR4602E No volumes found for TODATE date
time.
Explanation: No volumes were found in the volume
User response: If the information is cross-checked and history files that meet the date and time parameters
validated successfully, the database restore will be specified.
attempted using this database backup series and
corresponding volumes. If the information fails to System action: The server does not process the
validate, additional messages will be issued indicating command.
what is missing or why the selected database backup
series and volumes can not be used. In the case that the

ANR4603I ANR4608E
User response: Reissue the command with a valid volume. If this volume is corrupted, restore the
date and time. 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 ANR4606E Restore database volume header backup
later was saved under another name: file series number series does not match the
name. expected backup series number of
expected series. This volume cannot be
Explanation: After an upgrade of Tivoli Storage
used to restore the database.
Manager server to V6.3 or later, if you want to revert to
the previous release, you must have the original Explanation: Each database backup volume contains a
volume history file. The reason is that the V6.3 or later Tivoli Storage Manager backup series number in the
volume history file has a different format than the volume header. A mis-matched backup series number
earlier volume history file. The newer volume history indicates that this volume is either corrupted or not
file cannot be used to restore the Tivoli Storage suitable for restoring the database.
Manager database to the previous release.
System action: The system saves the previous volume DSMSERV RESTORE DB command.
history file under another name to ensure that it is not
User response: Check the volume history file to make
overwritten.
sure this volume is valid for a database backup
User response: To restore the Tivoli Storage Manager operation. If the volume is valid, the volume history
database, use the saved volume history file. file can be modified to match this series number and
you can reissue the DSMSERV RESTORE DB command.
If the problem persists, this volume may be corrupted.
ANR4604E Restore database volume header magic
Restore the database to a different time using a
number magic does not match the
different set of backup volumes.
expected volume header magic number
of expected magic. This volume cannot be
used to restore the database. ANR4607E Restore database volume header backup
operation number operation does not
Explanation: Each volume contains a Tivoli Storage
match the expected backup operation
Manager volume header that begins with a header
number of expected operation. This
magic number. A bad magic number indicates that this
volume cannot be used to restore the
volume is either corrupted or not suitable for restoring
database.
the database.
Explanation: Each database backup volume contains a
Tivoli Storage Manager backup operation number in
the volume header. A mis-matched backup operation
User response: Check the volume history file to make number indicates that this volume is either corrupted
sure that this volume is a valid database backup or not suitable for restoring the database.
volume. If the volume is corrupted, restore the
database to a different time using a different set of
backup volumes.
User response: Check the volume history file to make
ANR4605E Restore database volume header version
operation. If the volume is valid, the volume history
number version does not match the
file can be modified to match this operation number
expected volume version number of
and you can reissue the DSMSERV RESTORE DB
expected version. This volume cannot be
command. If the problem persists, this volume may be
used to restore the database.
corrupted. Restore the database to a different time
Explanation: Each database backup volume contains a using a different set of backup volumes.
Tivoli Storage Manager version number in the volume
header. A mis-matched version number indicates that
ANR4608E Restore database volume header backup
this volume is either corrupted or not suitable for
type backup type is invalid. This volume
restoring the database. This volume may be a pre
cannot be used to restore the database.
Version 6.3.0 database backup volume. It cannot be
used to restore a Tivoli Storage Manager V6.3 database. Explanation: Each database backup volume contains a
Tivoli Storage Manager backup type code in the
volume header. An invalid backup type code indicates
that this volume is either corrupted or not suitable for
User response: Check the volume history file to make restoring the database.
sure that this volume is a valid database backup
ANR4609I ANR4615E
DSMSERV RESTORE DB command. command.
User response: Check the volume history file to make User response: Reissue the command and specify a
sure this volume is valid for a database backup point in time (TODATE/TOTIME) for restore.
operation. If this volume is corrupted, restore the
ANR4613E Meta data for restore database volume
backup volumes.
backup volume is not valid. This volume
cannot be used to restore the database.
ANR4609I Restore database process found backup
Explanation: Backup volumes contain Tivoli Storage
type database backup timestamp backup
Manager meta data. Invalid meta data indicates that
timestamp from database backup media.
this volume is either corrupted or not suitable for
Explanation: This is the backup timestamp that is restoring the database.
used for a database restore operation.
System action: DSMSERV RESTORE DB command.
User response: User response: Check the volume history file to make
ANR4610E Database volume DB volume name not
found in current configuration.
backup volumes.
Explanation: The command specified the name of a
nonexistent database volume.
ANR4614E The database backup timestamp of
System action: The server does not process the backup timestamp on media on database
command. backup media with backup type backup
type does not match the backup
User response: Reissue the command with a valid timestamp backup timestamp from volhist
database volume name. from the volume history file. This
volume cannot be used to restore the
ANR4611E Unable to restore database and roll database.
forward updates - log mode was not Explanation: Mis-matched timestamps indicates that
previously set to ROLLFORWARD. this volume is either corrupted or not suitable for
Explanation: The command specified that the database restoring the database.
be restored and all updates rolled forward to the most System action: The server does not process the
current state. This process cannot be accomplished DSMSERV RESTORE DB command.
because the server recovery log mode was not set to
ROLLFORWARD; therefore, no update information User response: Check the volume history file to make
exists. sure this volume is valid for a database backup
System action: The server does not process the database to a different time using a different set of
command. backup volumes.
point in time (TODATE/TOTIME) for restore. ANR4615E The server is unable to restore the
database due to inaccessible media.
ANR4612E Unable to restore database and roll Explanation: The database restore operation cannot be
forward updates. completed. Possible reasons include:
Explanation: The command specified that the database v The device configuration file is not correctly defined
be restored and all updates rolled forward to the most to access the media.
current state. This process cannot be accomplished v There is a problem with the media.
because the internal list of volumes for the most recent
full/incremental backup series is not available. Possible System action: The database is not restored.
reasons include:
User response: Review the information in the message
v No full backup was taken after setting the recovery explanation and take action to correct any problems
log mode to ROLLFORWARD with a SET with the device configuration file or media. Reissue the
LOGMODE command. RESTORE DB command.
v Only snapshot database backups were created.

ANR4616E ANR4626I

ANR4616E Database restore terminated because the
media header cannot be found - DB2
sqlcode sqlcode and DB2 error message ANR4624I Preview processing for a database
sqlerrmc. restore operation has completed.
Explanation: During a restore operation, the DB2 Explanation: The database restore command was
database was unable to find the media header. There issued with PREVIEW=YES specified. The server will
might be a problem with the media. evaluate the volume history information and report the
details about what it found. It will report the candidate
database backup that was selected based on the restore
User response: Check if the Tivoli Storage Manager command that was specified. If the database restore
server reports an error for the media. Ensure that the processing is unable to find a viable database backup to
media that is used for the database backup is working. use for restore or other errors occur during this
evaluation, these will also be reported.
ANR4619I Snapshot database backup series System action: None.
snapshot database backup series using
User response: Review the other messages issued to
device class device class.
determine the outcome of the database restore preview
Explanation: The device class used for the snapshot operation.
database backup is shown.
System action: None. ANR4625W Database backup failure while
attempting to use number of streams
streams, backup will be retried using
one stream.
ANR4620I Database backup series Backup series
Explanation: The database backup process failed
operation backup operation device class
while attempting the operation with the specified
device class.
number of streams. The operation will be retried with a
Explanation: The device class used for the backup is single stream.
shown.
System action: The database backup will be
System action: None. automatically retried using a single stream.
User response: None. User response: Review the other messages issued to
determine the reason for the failure of the database
backup while using multiple output streams. Also
ANR4621I Database backup device class device class. review the process completion and other message to
Explanation: The device class for the backup is determine if the retry using a single stream was
shown. successful.

ANR4626I Database backup will use number of
User response: None. streams streams for processing with the
number originally requested number
ANR4622I Volume volume sequence number in backup requested.
operation: volume name. Explanation: The database backup will be performed
Explanation: The volume sequence and name for a using the specified number of streams. The original
full or an incremental database backup are shown. number of streams requested, either through the
command or the NUMSTREAM setting for SET
System action: None. DBRECOVERY, is also displayed.
User response: None. System action: The database backup will be
performed with the indicated number of streams.
ANR4623I Stream stream number in backup operation User response: Note that if the number of streams
volume volume sequence number in backup used for the database backup differs from the number
stream: Volume name. requested, this indicates either a configuration error or
Explanation: The stream number, volume sequence that the device being used does not have as many
and name for a full or an incremental database backup drives available as was previously considered and
are shown. planned for. Review the device class and
NUMSTREAM settings used for the database backup
System action: None. command to determine if changes are needed or if
actions are needed to bring drives back online.
ANR4630I ANR4639I
the point in time of this backup.

ANR4630I Starting point-in-time database restore
(commit). System action: None.
Explanation: A point-in-time database restore with a User response: None.
specified list of volumes has started. When this restore
is complete, the database will be committed to the
point in time of this backup. ANR4635I Point-in-time database restore complete,
restore date date time.
Explanation: A point-in-time database restore with the
User response: If you inadvertently specified TODATE parameter specified has completed. The
COMMIT=YES, restart the restore process from the database is committed to the point in time of this
beginning, starting with restoring the full backup backup, which may be different than the TODATE
(backup operation 0). specified. If this is the case, an additional message will
be displayed.
ANR4631I Point-in-time database restore (commit) System action: None.
complete, restore date date time.
Explanation: A point-in-time database restore with a
specified list of volumes is complete. The date shown is
the date to which the database has been restored. ANR4636I Starting roll-forward database restore.
System action: None. Explanation: A roll-forward database restore has

begun. When this restore is complete, the database will
User response: None. be returned to its most recent state.
(no commit). User response: None.
Explanation: A point-in-time database restore with a

specified list of volumes has started. When this restore ANR4637I Roll-forward database restore complete.
is complete, the database will not yet be usable. Explanation: A roll-forward database restore has
System action: None. ended. All database backups in the most current
backup series have been restored, and all updates to
User response: To complete a database restore where the database since the most recent backup have been
a volume list is specified, specify COMMIT=YES on the rolled forward. The database has been returned to its
command when restoring the last set of backup most recent state.
volumes. If you forgot to specify COMMIT=YES on the
command, issue the last restore command again with System action: None.
COMMIT=YES. User response: None.
ANR4633I Point-in-time database restore (no ANR4638I Restore of backup series backup series
commit) complete. number operation backup operation in series
Explanation: A point-in-time database restore with a in progress.
specified list of volumes is complete. The database is Explanation: During a DSMSERV RESTORE DB, the
not yet usable. server displays the backup series and operation
System action: None. currently being restored.
User response: To complete a database restore where System action: None.

a volume list is specified, specify COMMIT=YES on the User response: None.
command when restoring the last set of backup
volumes. If you forgot to specify COMMIT=YES on the
command, issue the last restore command again with ANR4639I Restored number of pages restored of
COMMIT=YES. number of pages to restore from current
backup operation database pages.
ANR4634I Starting point-in-time database restore Explanation: Periodically, during a DSMSERV

to date date time. RESTORE DB, the server displays the number of pages
restored from the current backup being restored.
TODATE parameter specified has begun. When this System action: None.
restore is complete, the database will be committed to User response: None.

ANR4640I ANR4648I
ANR4640I Restored number of database pages pages ANR4645I The restore date reflects the most recent
from backup series backup series number backup available up to the specified
operation backup operation in series. TODATE.
Explanation: At the end of each restored backup, the Explanation: During a DSMSERV RESTORE DB with
server displays the number of database pages restored. the TODATE parameter, the date of the restored backup
was not identical to the date specified on the
command. The backup series that was restored is the
User response: None. most recent backup series up to and including the
specified date.
ANR4641I Sequential media log redo pass in System action: None.

progress.
User response: Make sure the date of the restored
Explanation: During a DSMSERV RESTORE DB, the database is satisfactory. If it is not, restore the database
process of committing incomplete database updates has again by specifying a different TODATE or by restoring
begun. individual database backups.

ANR4646I Database capacity required for restore is
User response: None. number of megabytes megabytes.
Explanation: During a point-in-time restore of a
ANR4642I Sequential media log undo pass in database, the size of the database being restored is
progress. displayed. The available capacity of the online database
Explanation: During a DSMSERV RESTORE DB, the volumes must be at least this size.
process of rolling back incomplete transactions has System action: None.
begun.
User response: None. ANR4647I Database available capacity is number of
megabytes megabytes.
ANR4643I Processed number of log records log Explanation: During a point-in-time restore of a
records. database, the available capacity of the online database
Explanation: Periodically, during the commit of a volumes is displayed. This capacity must be as large as
point-in-time restore or while rolling forward updates the size of the database being restored.
during a roll forward restore, the server displays the System action: If the available capacity of the online
number of log records processed. database volumes is not at least this size, the restore
System action: None. cannot continue.
User response: None. User response: If the available capacity of the online
database is not sufficient, reinstall the server with the
required database size, and try the restore operation
ANR4644I A full backup will be required for the again.
next database backup operation.
Explanation: During a point-in-time restore of a ANR4648I Extending database assigned capacity to
database, this message is displayed to notify the number of megabytes megabytes.
administrator that the next database backup taken
during normal operation must be a full backup. This Explanation: During a point-in-time restore of a
process is normal for point-in-time database restores. database, the assigned capacity of the online database
is smaller than that of the database being restored.
System action: None. However, the available capacity of the online database
User response: At the next server restart, do a full volumes is sufficient for restore.
database backup. A full database backup is started System action: The assigned capacity of the online
automatically if a DBBACKUPTRIGGER is defined. database is extended to the size required for restore.
ANR4649I ANR4656E
ANR4649I Reducing database assigned capacity to ANR4653E Incremental backup DB failed. Can not
number of megabytes megabytes. perform incremental DB backup without
a FULL DB backup performed first.
Explanation: During a point-in-time restore of a
database, the assigned capacity of the online database Explanation: A FULL DB backup has to be performed
is larger than that of the database being restored. at least once before any Incremental DB backup can be
performed.
System action: The assigned capacity of the online
database is reduced to the size required for restore. System action: The incremental DB backup is
terminated.
User response: Reissue the backup db command with
type=FULL.
ANR4650E Restore of backup series current series
operation current operation is not in
sequence; last restored backup was ANR4654I The restore db to most current time can
series previous series operation previous not be done since contents of the active
operation. or archive log directories have been
changed. The DB will be restored to the
Explanation: During a DSMSERV RESTORE DB, a
last full or full plus incremental state.
backup volume was mounted that is not in the correct
sequence. Explanation: The restore DB can only restore to the
last FULL backup.
System action:
User response: Ensure volume names are specified in
the correct sequential order. For a restore with User response: Do not modify contents of active or
COMMIT=NO, reissue the last restore command. For a archive log directories before attempting a dsmserv roll
restore with COMMIT=YES, restart the restore from the forward restore command.
beginning of the full backup.
ANR4655W The restore DB is completed and active
ANR4651E Restore of backup series current series log directory has been changed by DB2
operation current operation is not in from orginal active log directory to new
sequence; backup is part of another log active log directory
epoch.
Explanation: The active log directory has been
Explanation: During a DSMSERV RESTORE DB, a changed by DB2.
backup volume was mounted that is not in the correct
System action:
sequence. The current backup operation cannot be
restored in this series because it belongs to the same User response: the user can do the following: :
backup series from another point in time. v Start DB2: db2start
System action: The database restore is terminated. v Connect to TSMDB1: db2 connect to TSMDB1
User response: Restart the database restore from the v Update the DB config: db2 update db cfg using
beginning of the full backup. Omit all backups from the NEWLOGPATH (log path from server options, e.g.
offending backup and later from the restore. /ALOG/tsminst1)
v Terminate connection to TSMDB1: db2 terminate
ANR4652E No system message queues available for v Recycle DB2: db2stop/db2start
communications. v Verify new log path takes effect: db2 connect to
TSMDB1; db2 get db cfg | grep "Path to log files"
Explanation: While Tivoli Storage Manager was trying
to establish a communications session, an attempt to
acquire a system message queue failed. This usually ANR4656E Invalid key-ring file password Key Ring
means that the system-imposed limit on message password
queues has been reached.
Explanation: The specified key-ring file password
System action: The communications session is not exceeds the maximum password length of 64
initialized due to lack of system resources. characters.
User response: Increase the maximum number of System action: None
message queues on the system and try the operation
again. This is normally accomplished by increasing the User response: Specify a key-ring file password using
value in the kernel's msgmni file. 1-64 characters. Ensure that the password is the same
value that was specified with the key-ring file
password utility.

ANR4657E ANR4663W
ANR4657E SNMP: Failed to connect to server at ANR4661E SNMP communication with the
address address, port port. subagent failed because a thread
resource was not available.
Explanation: The SNMP client was attempting to run
a session with the server at the indicated address and Explanation: The server could not continue with
port number in response to an SNMP Get Request, SNMP communication to the SNMP subagent because
which causes a Server Script to be run. The subagent sufficient memory is not available for starting
failed to connect to the server. additional processes on the server.
System action: The SNMP subagent ends this attempt System action: The server discontinues SNMP
to run the script and continues operation. processing and server operation continues.
User response: Ensure that the indicated server is up User response: See the documentation for the
and able to initiate admin clients using the TCP/IP operating system about how to increase memory for an
protocol. application.
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
intentionally stopping either the subagent, no response
is required. Otherwise, ensure that the TCP/IP protocol
ANR4664W ANR4671W
stack is functioning by using the tools that come with failed. Heartbeat functions are disabled until the server
the particular TCP/IP suite on the platform in use. is re-started.
User response: Ensure that the subagent is running
ANR4664W Failure in registering with SNMP and that the TCP/IP protocol stack is functioning by
subagent. using the tools that come with the particular TCP/IP
suite on the platform in use. Re-start the server if the
Explanation: The server experienced a problem while
heartbeat function is required.
attempting to register with the SNMP subagent. This
may be due to problems with communication or the
SNMP subagent being unavailable. ANR4668I Connection successfully re-established
with SNMP subagent.
System action: Heartbeat messaging will be disabled
until the server is re-started. Explanation: The server experienced a problem while
attempting to send a heartbeat message to the SNMP
subagent.
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
losing contact. This may be due to problems with
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

ANR4672W ANR4681W
subagent and re-start it. Then stop the server and

ANR4677I Session established with server name:
re-start it if heartbeat and message forwarding
The name of the registered server..
functions are required.
Explanation: The SNMP subagent completed the
registration of the identified server.
ANR4672W SNMP message forwarding to the
SNMP subagent was not started because System action: The subagent will wait for additional
a thread resource was not available. requests from the server.
Explanation: The server could not continue with User response: None.
SNMP communication to the SNMP subagent for
message forwarding because sufficient memory is not
ANR4678I Session closed with server name: The
available for starting additional processes on the server.
name of the deregistered server..
System action: The server discontinues SNMP
Explanation: The SNMP subagent completed the
message processing and server operation continues.
deregistration of the identified server.
application. User response: None.
ANR4673E Insufficient memory for subagent ANR4679W Messages are no longer being forwarded
initialization (the portion of initialization to the SNMP subagent.
where the allocation of memory failed).
Explanation: The server has encountered multiple
Explanation: The SNMP subagent could not initialize errors in forwarding messages to the SNMP subagent.
due to the inability to obtain the required memory. Messages are no longer being forwarded.
System action: Initialization of the subagent fails. System action: The server continues operating, but
messages are no longer being forwarded.
User response: Allocate additonal storage to the
subagent. User response: Message forwarding can be
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
Explanation: The SNMP subagent could not start the re-synchronization occurs if the subagent, dsmsnmp, is
DPI thread. stopped for longer than a single heartbeat interval (the
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
User response: Contact your service representative. restarted.
ANR4675E Server/subagent protocol violation - ANR4680I DPI subagent (The subagent name.):
invalid (where the protocol breakdown "Connected" or "reconnected", ready to
occurred). receive requests.
Explanation: The SNMP subagent received an Explanation: The subagent has successfully connected
unexpected request from the server. or reconnected to the SNMP agent.
System action: The subagent will stop processing System action: The subagent is ready to receive
requests from the server sending the invalid requests. requests from servers.
User response: Contact your service representative. User response: None.
ANR4676E Unable to register another server. ANR4681W Connect to SNMP agent failed, will
keep trying.
Explanation: The SNMP subagent received a request
to register a new server and was unable to allocate the Explanation: The subagent has failed in an attempt to
memory necessary to register the new server. connect to the SNMP agent.
System action: The subagent will not register the new System action: The subagent keeps retrying the
server. connection.
User response: Contact your service representative. User response: Make sure that the SNMP daemon is
up, running and correctly configured.
ANR4682W ANR4691I
ANR4682W A SNMP agent connection error ANR4687E Server/subagent protocol violation -

occurred. Attempting to re-establish expecting registration request. Received
connection. request: The value of the request that was
received.
Explanation: An error has occurred in the
communication between the subagent and the SNMP Explanation: The SNMP subagent was expecting a
agent. registration request. It actually received something
other than a registration request.
System action: The subagent will attempt to
reconnect. System action: The subagent will stop processing
requests from the server sending the invalid requests.
User response: Make sure that the SNMP daemon is
up, running and correctly configured. User response: Contact your service representative.
ANR4683E Unable to open trace file 'file name'. ANR4688E Server/subagent protocol violation -
incorrect request header version.
Explanation: An error occurred while opening the file
for writing trace data. Explanation: The SNMP subagent received a request
from a server that was not at the same maintenance
System action: The subagent continues operation
level as the subagent.
without tracing.
System action: The subagent will stop processing
User response: Ensure there is adequate space on the
drive from which you are running the subagent and
retry the program. User response: Ensure the server and subagent are at
the same maintenance level. If they are, contact your
ANR4684E Trap request failed - RC: Return code from
the trap request. Server index: Server index
number.. ANR4689E Invalid request type received (The value
of the request that was received.).
Explanation: An error occurred while attempting to
process a trap request from a server. data. Explanation: The SNMP subagent received an
unexpected request from the server.
System action: The subagent processing continues.
User response: Make sure that the SNMP daemon is
up, running and correctly configured.
ANR4685E Insufficient memory for subagent
initialization. ANR4690E Unexpected request type (The value of the
request that was received.) in trap data
Explanation: The SNMP subagent could not initialize
header.
due to the inability to obtain the required memory.
Explanation: The SNMP subagent received an invalid
trap request from a server.
User response: Allocate additional memory to the
subagent.
ANR4686E Insufficient memory for subagent trace
initialization.
ANR4691I DPI subagent (The subagent name.):
Explanation: The SNMP subagent trace could not
connected, ready to receive requests.
initialize due to the inability to obtain the required
memory. Explanation: The subagent has successfully connected
to the SNMP agent.
System action: The subagent is ready to receive
User response: Allocate additional memory to the
request from servers.
subagent.

ANR4692I ANR4700I
ANR4692I DPI subagent (The subagent name.): ANR4697E SNMP: Failed to authenticate to server
reconnected, ready to receive requests. at address address, port port.
Explanation: The subagent has successfully Explanation: The SNMP client was attempting to run
reconnected to the SNMP agent. a session with the server at the indicated address and
port number in response to an SNMP Get Request,
System action: The subagent is ready to receive
which causes a Server Script to be run. The subagent
request from servers.
connected to the indicated server, but failed in
User response: None. authentication.
System action: The SNMP subagent ends this attempt
ANR4693I Interface Driver information will be to run the script and continues operation.
loaded in quiet mode: Only warning
User response: Ensure that the indicated server has an
and error messages will be displayed.
an administrative id of SNMPADMIN and that this
Explanation: The server is loading information needed adminstrative id has sufficient authority to run the
for the Administrative WEB Interface. To minimize script and commands it contains.
message traffic, only error and warning messages will
be displayed.
ANR4698E SNMP: Communications Failure in
System action: When the command completes, WEB Sending "verb type" verb (command).
administrative information will be loaded into the
Explanation: The SNMP client encountered a
server.
communications error in using the verb type verb to
User response: None. issue command command.
System action: The SNMP client session ends and
ANR4694E SNMP Subagent Port Confirmation Has subagent operation continues.
Failed.
Explanation: The server was communicating
configuration data to the SNMP subagent. An error
ANR4699E SNMP: Receive Buffer overflow.
occurred in the exchange. The server could not
communicate interface information to the subagent. Explanation: The SNMP client encountered an
overflow error in transferring information to or from
System action: The server continues operation. The
the server.
SNMP administrative interface is inoperative.
System action: The SNMP client session ends and
User response: The most likely cause of this problem
subagent operation continues.
is a temporary network failure. The server should be
re-started to retry the connection to the SNMP User response: Contact your service representative.
subagent. If this problem occurs repeatedly, please
contact you service representative.
ANR4700I The server move batch size has been set
to new batch size. Move operations that
ANR4695E SNMP: Communications Failure in start after this point will use the new
Receiving "verb type" verb. value.
Explanation: The SNMP client encountered a Explanation: A SETOPT commmand was used to set
communications error in using the verb type verb to the value for the move batch size value. This setting
transfer information to or from the server and an determines the maximum number of files that are
SNMP client. moved on the server in one database transaction,
dependent also on the setting for the move size
System action: The SNMP session ends and server
threshold. The setting influences file movement for
server migration, reclamation, storage pool backup, and
User response: This may not be a problem if the move data operations.
SNMP subagent was terminated while the session was
System action: The server uses this new setting for
in progress. Otherwise, ensure that TCP/IP
move operations that are started after this message is
communications is running normally.
issued.
ANR4701I ANR4708I
ANR4701I The server move size threshold has been ANR4705I The server IDL definitions have not
set to new threshold. Move operations been installed. These definitions will
that start after this point will use the need to be installed for the Web
new value. Administrator interface to work.
Explanation: A SETOPT commmand was used to set Explanation: The server attempted to query the server
the value for the move size threshold value. This IDL interface and found no definitions defined. Because
setting determines the maximum number of megabytes of this error the HTTP engine returns a 404 not found
that are moved on the server in one database message.
transaction, dependent also on the setting for the move
batch size. The setting influences file movement for
server migration, reclmation, storage pool backup, and User response: If you would like to use the server
move data operations. web administrator interface you will need to:
System action: The server uses this new setting for 1. Halt the server.
move operations that are started after this message is 2. Issue the command DSMSERV RUNFILE
issued. dsmserv.idl. For AS/400 command see next step.
User response: Contact your service representative. 3. For AS/400, issue the command STRSVRADSM
SVRMODE(*PRPWEB).
4. Restart the server.
ANR4702I The server transaction group maximum
has been set to new value. Client sessions
that are started after this point will use ANR4706W Unable to open file Filename to satisfy
the new value. web session Session ID.
Explanation: A SETOPT commmand was used to set Explanation: A web browser requested a file and the
the value for the maxmimum number of files that can server could not find the file on the local file system.
be sent from the client in a single database transaction. Special note, some files requested from the server are
not vaild and are caused by a browser error. For
System action: The server uses this new setting for
example, a request for CommandLineBeanInfo.class is
client sessions that are started after this message is
not a valid file request. However, a request of a GIF
issued.
image or HTML page should not produce this error.
User response: Verify that permission for the file are
ANR4703E Invalid key-ring filename Key Ring
set correctly and file exists.
Filename
Explanation: The key-ring filename specified did not
ANR4707E Import/Loaddb command operation
contain the .kyr extention.
terminated - incomplete input volume
System action: None. list.
User response: Rename your key-ring filename to Explanation: The list of volumes needed to process
contain the .kyr extention. Reexcute the command with the command was incomplete. At least one volume
the new filename. needed for the operation is missing from the end of the
list.
ANR4704I key-ring filename and password have System action: The command operation is ended.
been set. Restart the server to use the
User response: Issue the command again and make
new settings
sure the necessary volumes are included in the volume
Explanation: The key-ring filename have been set to list.
the new value specified in the DEFINE KEYRING
command.
ANR4708I Native SSL support has been disabled,
System action: None. please use the web proxy.
User response: Restart the server to use the new Explanation: Starting in this version of this product
key-ring information. native Secure Socket Layer support has been removed.
This feature has been replace with the web proxy.
Support for non-secure http request (COMMMETHOD
HTTP) has not been disabled.

ANR4709W ANR4717I
User response:
ANR4714I Command filename for filespace filespace
1. Remove COMMMETHOD HTTPS from your option name of node node name started as
file. process process ID.
2. Install and configure the web proxy. See Quick Start
Explanation: A file deletion process has started to
Appendices for more information on how to install
delete one or more files from the given filespace for the
and configure the web proxy.
for given node. The process is assigned the ID specified
in the message.
ANR4709W Intervention required to mount volume
Volume Name on Library Manager Server
to perform the operation in response to the DELETE
Server Name.
FILE command entered by an administrator.
Explanation: A volume mount is awaiting operator
User response: To obtain status on the file deletion
intervention on the specified library manager server.
process, issue the QUERY PROCESS command. The
System action: The volume mount operation waits for process may be canceled with the CANCEL PROCESS
operator intervention. command.
User response: Refer to the server consol and/ir

activity log on the named library manaer server to ANR4715I DELETE FILE file name (backup/archive
determine the action that needs to be performed to data) for filespace filespace name of node
complete the mount operation. node name started.
ANR4710W Library manager Server Name could not (on the server) to delete files from the given filespace
be contacted to control library Library for the given node.
Name.
System action: The background process deletes
Explanation: The specified library manager server backup and archive objects that match the given file
could not be contacted for control of the named library. name while server operation continues.
System action: The server will continue to contact the User response: To obtain status on the file deletion
named library manager server. Volume mounts in the process, issue the QUERY PROCESS command. The
library will fail until communication is successful. process may be canceled by an authorized
User response: Determine why the named server is
not running or why the network prevents
communication with te named server. ANR4716I DELETE FILE file name (backup data) for
filespace filespace name of node node name
started.
ANR4712E Command: The DEVCLASS parameter is
only valid for volume history types Explanation: A background server process has started
DBBACKUP or DBSNAPSHOT. (on the server) to delete files from the given filespace
for the given node.
volume history type was specified for the TYPE= System action: The background process deletes
parameter. backup objects that match the given file name while
System action: The command fails, and server
operation continues. User response: To obtain status on the file deletion
process, issue the QUERY PROCESS command. The
User response: Re-issue the command and specify a process may be canceled by an authorized
valid type value. administrator using the CANCEL PROCESS command.
ANR4713E Command: The "option" string is not valid ANR4717I DELETE FILE file name (archive data) for
for the Hex Filespace Field. filespace filespace name of node node name
Explanation: The command indicated specifies a value started.
that is not valid for the Hex Filespace parameter. Explanation: A background server process has started
System action: The server does not process the (on the server) to delete files from the given filespace
command. for the given node.
User response: Reissue the command with a valid System action: The background process deletes
entry for the Hex Filespace parameter. archive objects that match the given file name while
ANR4718I ANR4728E
User response: To obtain status on the file deletion client until an incremental backup is completed for the
process, issue the QUERY PROCESS command. The node.
process may be canceled by an authorized
System action: The server will continue processing.
User response: Perform an incremental backup for the
client node.
ANR4718I DELETE FILE file name canceled for
filespace filespace name of node node name
: number of objects objects deleted. ANR4725E Source file(line number): Server lock
Locktype, mode Lockmode failed.
been deleting files for the given fliespace of the given Explanation: An internal error occurred in an attempt
node is canceled by the CANCEL PROCESS command. to obtain a lock during processing.
The number of objects deleted before the cancel ended
the operation are reported in the message. System action: The activity that generated this error
fails.
operation continues. User response: Retry the process. If the process fails
User response: No action is required. An authorized
administrator can issue the DELETE FILE command to
delete the remaining files desired. ANR4726I The support module has been loaded.
Explanation: The module indicated has been
ANR4719I DELETE FILE file name complete for successfully loaded. Operations involving this module
filespace filespace name of node node name may be performed by the server.
: number of objects objects deleted. System action: Functions which depend on this
Explanation: A server process deleting file space data module may now be performed on the server.
for the node specified has completed. The total number User response: None.
of objects deleted is reported in the message.
System action: The server process is ended and server ANR4727E Server Server name is incompatible with
operation continues. this server. Please update the server to
User response: None. the same level as this storage agent.
Explanation: The storage agent attempted to connect
ANR4723E Session rejected for down level storage to a downlevel server. The server version, release, and
agent storage agent name. fix level must exactly match, otherwise data corruption
may occur. For example, a version 4.2.0.0 storage agent
Explanation: A down level storage agent attempted to cannot connect to a version 4.1.0.0 server.
connect to this server. The server can not support all
previous versions of the storage agent. System action: Upgrade the TSM server to the same
level as the storage agent.
System action: The server will not support
connections by storage agents at a specific lower User response: None.
versions of the product. Review the README for an
explanation of supported storage agent levels for this ANR4728E Server connection to file server File
server. The storage agent will not startup and will server name failed. Please check the
report ANR0454W indicating that it is down level. attributes of the file server specified
User response: None. during definition of the datamover.
Explanation: The server attempted to connect to a file
ANR4724E During the backup of node node (Node server. The connection failed because of one of the
id) filespace filespace name (filespace id) a following possible reasons:
deletion activity occurred. v One of the parameters specified during datamover
definition was incorrect: TCP/IP address of the file
Explanation: During full or incremental backup server, user id, password, TCP/IP port
processing, files were deleted from the file space. The
files were not deleted by expiration, but by some other v File server does not support requested NDMP
process. DELETE FILESPACE, DELETE VOLUME, version
AUDIT VOLUME, or some other administrator v File server is not accessible
command can cause files to be deleted. The file space v NDMP server limits the number of opened NDMP
image on the server will not be consistent with the sessions

ANR4729E ANR4734W
v An unsupported model of the filer server was

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

indicated in the message and does not effect other
is in use as a copy or active-data storage
session operation.
pool by one or more other storage pools.
Explanation: A DELETE STGPOOL command specifies
User response: The error that occured could be one of a pool that is a copy storage pool and listed as one of
many failure. Look for the following items in the active the copy storage pools of other storage pool via the
log or on the server console. 1. Is the named storage DEFINE STGPOOL or UPDATE STGPOOL's
pool currently unavailable? 2. Have any I/O error COPYSTGPOOL parameter, or, a DELETE STGPOOL
occured on the destination devices (disk or tape command specifies a pool that is an active-data storage
drives)? 3. Is the mount limit on the device class pool and listed as one of the active-data storage pools
correctly set? 4. Is the node's MAXNUMMP value of other storage pools via the DEFINE STGPOOL or
sufficient to satisfy the request? UPDATE STGPOOL's ACTIVEDATAPOOLS parameter.
ANR4735W Server-free processing is not available. command.
Initialization failed.
User response: If necessary, issue the UPDATE
Explanation: An error occurred while initializing STGPOOL command to update other storage pools so
server-free processing. Server-free data transfer is not that they do not reference the pool to be deleted, and
available to backup and restore images. reissue the command.
System action: Client backup and restore image

requests will use lan-based data transfer. ANR4739E Either the high-level address (hladdress),
low-level address (lladdress), or both
User response: Check for messages during server were entered in error.
initialization and correct the error.
Explanation: The high-level or low-level addresses
supplied are incorrect.
ANR4736E Set serverfree is not allowed when
server-free is not available. System action: The server does not process the
command.
Explanation: Server-free processing did not initialize.
Changing the status is not allowed. User response: Both the high-level address and
low-level address are required for an address to be
System action: Server processing continues. valid. For an update, both high-level address and
User response: Server-free status may be changed low-level address are required for the update to
when the status is ON or OFF. succeed. For a new definition, both high-level address
and low-level address are required when
SESSIONINIT=SERVERONLY. Either the high-level
ANR4737E Transaction failed for session session address or low-level address is missing from this
number for node node name (client command. Issue the command again and supply the
platform) - the copy continue attribute for missing address represented by a "?" in this message.
storage pool storage pool name prevented
further retries.
ANR4740W Either the high level address, low level
Explanation: During a backup session one or more address, or both were never entered for
copy storage pools associated with the indicated the specified node( nodename ) and the
storage pool had a failure. The operation was halted session initiation status is being
because the copy continue option for the indicated changed.
storage pool caused the process to stop.
Explanation: When the session initiation status of a
System action: None. node is changed by using the SESSIONINIT parameter
User response: Verify the following: 1. Does the on the UPDATE NODE command, the scheduling table
device class(es) have enough mount points to satisfy is updated to reflect the address specified with HLA
the request? 2. Was the node's MAXNUMMP value and LLA keywords of the UPDATE NODE command.
sufficient to satisfy the request? 3. Were there any If one or both of these keywords have never been used
errors reported during the transaction regarding I/O or to provide addressing information for the node,
related issues? server-initiated scheduling will not be able to contact
this node.
System action: The server does not update the
scheduling table. Subsequent server initiated sessions
with the node are likely to fail, unless an additional
UPDATE NODE command provides both the

ANR4741W ANR4745E
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 adminName. This
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 ANR4745E Server server name
SCHEDULE command to remove the schedules. (version.release.modification level.fix level) is
not compatible with storage agent
ANR4742W This command has renamed storage agent name
administrator adminName to (version.release.modification level.fix level).
newAdminName. This administrator has Explanation: The server and storage agent are not
defined or updated schedules. This will compatible. The storage agent must be at the same
cause these schedules to fail in the version and release as the server. It must also be at the
future. same modification level, or the same modification level
Explanation: A RENAME ADMINISTRATOR minus one. For example, a server at version 5.2.1
command has been entered and the administrator would allow connections from a storage agent at
renamed owns the administrative schedules. The version 5.2.1 or version 5.2.0.
schedules will fail when executed in the future because System action: If the storage agent and server are not
they do not belong to the administrator's new name. at the same version and release, update the storage
System action: The system renames the administrator. agent to the same version and release as the server.
Once the storage agent is at the same version and
User response: Use the QUERY SCHEDULE command release as the server, upgrade it to either the same
or an SQL SELECT statement on the modification level or the same modification level minus
ADMIN_SCHEDULES table to determine which one.
schedules were last updated by the administrator. Use
the UPDATE SCHEDULE command to update those User response: None.
schedules controlled by an administrator that has
authority to execute them, or use the DELETE
SCHEDULE command to remove the schedules.
ANR4746E ANR4755W
delete the corresponding cert.kdb,cert.crl,cert.rdb and

ANR4746E Session rejected for up level storage
cert.arm files from the server execution directory if they
agent storage agent name.
exist. Restart the server to generate and use the new
Explanation: An up level storage agent attempted to key-ring information.
connect to this server. The storage agent can not be at
higher level than the server.
ANR4752I REPAIR STGVOL process process number
System action: The server will not support started for number of volumes volumes.
connections by storage agents at a higher version, at
Explanation: The REPAIR STGVOL process has been
the same version with a higher release, or at the same
started as the reported process number. This will
version and release with a higher modification level.
evaluate and if needed repair the indicated number of
The storage agent will not startup and will report
volumes.
ANR0454W indicating that no resources are available.
User response: This process may be monitored using
the QUERY PROCESS command. If this process needs
ANR4747W The web administrative interface is no
to be cancelled, issue the CANCEL PROCESS
longer supported. Begin using the
command.
Integrated Solutions Console instead.
Explanation: The web administrative interface is no
ANR4753E REPAIR STGVOL process process number
longer supported. It has been replaced by an
ended, processed volumes processed of
administrative interface based on the Integrated
total volumes total volumes with repaired
Solutions Console.
volumes repaired and failed volumes
System action: The web administrative interface's web failures.
page is not displayed.
Explanation: The REPAIR STGVOL process has ended.
User response: Install the IBM Tivoli Storage Manager It processed volumes processed out of total volumes total
support for the Integrated Solutions Console and begin volumes to be processed. The repaired volumes indicates
using it to manage your servers. the number of volumes that needed database repairs
and were repaired. The failed volumes are volumes that
either failed during evaluation or during database
ANR4748E A NAS operation requiring NDMP
repair if it was needed.
Version 4 was attempted for file server
File server name , however the current System action: None.
NDMP session uses NDMP Version 3.
User response: If there were failed volumes, review the
Please verfiy that file server supports
activity log for more information about the failure.
NDMP version 4.
Explanation: A NAS operation which requires NDMP
ANR4754I REPAIR STGVOL process process number
Version 4 was attempted for a file server that is
currently configured to run NDMP Version 3.
System action: The TSM server backup/restore or volumes repaired.
other operation on the file server 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
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

ANR4756I ANR4763E
the number of volumes that needed database repairs indication of why processing for this volume failed. Try
and were repaired. issuing "REPAIR STGVOL VOLNAME=volume name" to
process this volume again. If this volume was deleted
from the server, this message can be ignored.
User response: If the volumes processed is less than the
total volumes, this may be because the process was
ANR4760I REPAIR STGVOL reset processing
cancelled before it could process all the needed
history.
volumes. Review the activity log to determine if this is
the case and re-issue the command to complete this Explanation: The REPAIR STGVOL command was
processing. Or if volumes were reclaimed or deleted issued with RESET=YES. This resets the processing
while this process was running, there may have been history. Resetting the processing allows the command
fewer actual volumes to process than what was to be rerun and causes previously evaluated volumes to
calculated when the process started. If this is the case be re-evaluated.
no further action is necessary.
User response: An administrator may want to
ANR4756I REPAIR STGVOL selected volume
periodically reset the processing history and re-evaluate
volume name.
all volume in the server as a means of validating the
Explanation: The REPAIR STGVOL selected volume server database.
name volume to process. This volume will be evaluated
for database reference errors and if any are
ANR4761E REPAIR STGVOL reset processing
encountered, they will be corrected.
history failed.
Explanation: The REPAIR STGVOL command was
User response: None. issued with RESET=YES. This resets the processing
history. However, the reset of the processing history
failed.
ANR4757I REPAIR STGVOL finished evaluating
volume volume name, no repair was System action: None.
needed.
User response: The server is likely out of memory or
Explanation: The REPAIR STGVOL finished resources. This command should be re-issued after
evaluating volume name volume. No repair actions were either halting and restarting the server or after halting
taken for the database because there were no errors the server, rebooting the server machine, and than
detected. restarting the server. If the reset still fails after these
steps, contact your IBM service representative.
ANR4762E Command: The SPACEMANAGED or
ARCHIVE type parameters are not valid
ANR4758W REPAIR STGVOL repaired volume for active data storage pool volumes.
volume name, database reference errors
Explanation: The QUERY CONTENT server command
were found and corrected.
has been entered with an invalid type parameter. The
Explanation: The REPAIR STGVOL evaluated volume SPACEMANAGED or ARCHIVE parameters are not
name volume and determined that repair actions were valid when the volume specified belongs to an
needed. The necessary repairs were done successfully. active-data type storage pool.
System action: None. System action: The server ignores the command.
User response: None. User response: Reissue the command with correct
TYPE parameter for active data storage pool.
ANR4759E REPAIR STGVOL failed to process

volume name. ANR4763E Command: Invalid parameter - parameter.
Explanation: The REPAIR STGVOL failed for volume Explanation: The specified server command has been
name volume. This process either failed while entered with an invalid parameter that is not applicable
evaluating this volume or it had determined that repair when using z/OS Media library for sequential FILE
actions were needed and it failed performing those storage.
actions.
User response: Review the activity log for an proper syntax. Neither NUMBEROFVOLUMES nor
ANR4764E ANR4770W
FORMATSIZE parameter is valid when using z/OS

ANR4767E The server was unable to change the
Media library for sequential FILE storage. The z/OS
key-ring file password using the new
Media server formats each FILE volume as it is being
password specified on the SET
filled.
SSLKEYRINGPW command along with
the old password that the server has
ANR4764E Command: Invalid length for parameter stored.
parameter - parameter value.
Explanation: The previous key-ring file password
Explanation: The length for (parameter value) specified remains in effect.
for the (parameter) parameter in command command
System action: None
exceeds the maximum allowed length.
User response: The QUERY SSLKEYRINGPW
command will display the key-ring file password that
the server is currently using. If the SET
User response: Reissue the command and specify a SSLKEYRINGPW password UPDATE=YES command is
valid length for the parameter. For information on valid unable to update the key-ring file password, the
values for the parameter for the command, refer to the key-ring file and it's password can be deleted and
Administrators Reference for your particular platform. re-created by: 1. Issuing the DELETE KEYRING
command to delete the server's record of the key-ring
file and password. 2. Stopping the server. 3. Deleting
ANR4765I The key-ring file password was set. files cert.* in the server's instance directory. 4.
Restart the server to use the new Restarting the server so that the key-ring file and it's
password. password are regenerated by the server.
Explanation: The password that is used by the server
for the key-ring file was set to a value that was ANR4768E Command: Invalid volume name - volume
specified in the SET SSLKEYRINGPW command. This name.
is typically done after the key-ring file's password is
changed using an external utility. Explanation: The command indicated contains an
invalid FILE volume name for a ZOSMEDIA library
System action: None. volume.
User response: Restart the server to use the new System action: The server does not process the
key-ring file password. command.
ANR4766E The server could not access the key-ring volume name that does not exceed 44 valid characters.
file using the password specified in the
SET SSLKEYRINGPW command.
ANR4769W Command: Alert trigger is already
Explanation: The password used by the server for the defined for message number.
key-ring file was checked for validity but was not
valid. Explanation: A DEFINE ALERTTRIGGER command
has been entered that specifies a message number that
System action: None is already defined with the server.
User response: The QUERY SSLKEYRINGPW System action: The server skips the message number
command will show you the key-ring file password and continues processing the command.
that the server is currently using. If the password was
changed with an external utility, ensure that the User response: Use the UPDATE ALERTTRIGGER
password is the same as that which was specified in command to update the alert trigger if needed.
the SET SSLKEYRINGPW command. If the password
was lost, issue the DELETE KEYRING command to
ANR4770W Command:Invalid message number
delete the current key-ring file. When you restart the
message number.
server it will generate a new key-ring file, password,
and self-signed certificate. Issue the QUERY Explanation: The message number is invalid because
SSLKEYRINGPW command to obtain the new the message number is in an incorrect format or does
password. Then use an external utility to import not exist on the server.
additional certificates again and designate one as the
System action: The server skips the specified message
new default. Restart the server to use the additional
number and continues to process the rest of the
certificates.
command.
User response: Verify that the format of the message
number is correct and exists on the server. Reissue the

ANR4771W ANR4780I
command specifying the correct message number.

ANR4776I Command: Administrator admin name for
message number is action.
ANR4771W Command: Administrator admin name
Explanation: The command has performed the action
cannot be processed because it is not
and added or deleted the administrator name
registered or is locked.
successfully for the specified alert trigger.
the indicated administrator name. The administrator
name is not registered or is locked. User response: None.
System action: The indicated administrator name is
not processed. The server continues to process the other ANR4777I Command: Administrator admin name is
administrator names specified with the command. already defined to alert message number.
User response: If the administrator name was Explanation: The command specifies an administrator
specified incorrectly, reissue the command with the name already defined to the alert.
correct name. If the administrator name is locked,
System action: The server skips the administrator
determine if it can be unlocked. Use the UNLOCK
name and continues processing the command.
ADMIN command to unlock it, and reissue the
command specifying the administrator name. User response: None.
ANR4772I Alert trigger message number defined. ANR4778E Command: Alert alert identifer could not
be found.
Explanation: The requested alert trigger has been
added to the server in response to the command. Explanation: The specified alert was not found in the
server database.
System action: The specified alert identifier is
skipped. The server continues to process the next alert
identifier that is specified in the command.
ANR4773I Alert trigger message number deleted.
User response: Reissue the command, specifying an
Explanation: The requested alert trigger has been alert identifier for an alert that has not been closed or
deleted from the server. deleted on the server. To display a list of existing alerts,
issue the QUERY ALERTSTATUS command.
ANR4779E Command: The requested update for alert
id, alert identifer, is invalid. The alert is
ANR4774I Command command processed. not changed.
Explanation: The specified command was processed. Explanation: The specified update request is invalid
or not correct for the alert. You can change the status of
System action: None. an alert from active to inactive or closed, or, from
User response: Review previous messages. Correct the inactive to closed. If you are specifying the ASSIGNED
problem and reissue the command. or RESOLVEDBY parameters the value must be a
registered administrator name that is not locked.
ANR4775W Command: Alert trigger message number is System action: The server does not process the
not defined. command.
Explanation: The specified message number does not User response: Reissue the command specifying a
refer to a defined alert trigger in the server database. valid status for the alert. Issue the QUERY
ALERTSTATUS command to display a list of existing
System action: The server skips the specified message alerts and status.
number and continues to process the rest of the
command.
ANR4780I Node group node group name defined.
message number that is defined as an alert trigger. Explanation: A DEFINE NODEGROUP command has
Issue the QUERY ALERTTRIGGER command to display created the node group indicated.
a list of defined message numbers. System action: None.
ANR4781E ANR4789I
ANR4781E Command: Invalid node group name - ANR4785I Node group node group name deleted.
node group name.
Explanation: Server processing for the command NODEGROUP command, the node group node group
command fails because the node group name node group name has been deleted from the server database.
name specified does not contain valid characters or
contains too many characters.
command is not successful in changing the server ANR4786E Command: Node group node group name
database. still contains at least one node.
User response: Issue the command again and specify Explanation: Server processing for the delete
a node group name that conforms to the name command command fails because the node group node
requirements. For information on the character and group name specified refers to a node group that still
length specifications for valid node group names, refer contains at least one node. A node group cannot be
to the Administrators Reference. deleted if one or more client nodes are still assigned to
the node group.
ANR4782E Command: Description exceeds maximum System action: Database changes for the command are
length of length limit characters. rolled back and server operation continues. The
database.
command fails because the description specified is
longer than the length limit number of characters User response: To remove remaining nodes from the
allowed. node group, issue the DELETE NODEGROUPMEMBER
command. After all nodes are removed, issue the delete
command again.
database. ANR4787I Command: number of nodes members
defined in the node group node group
name.
a shorter description.
Explanation: A DEFINE NODEGROUPMEMBER
command has created the specified number of members
ANR4783E Command: Node group node group name is
in the indicated node group.
not defined.
command fails because the node group name node group User response: None.
name specified does not refer to a defined node group
in the server database.
ANR4788I Command: number of nodes members
System action: Database changes for the command are deleted from node group node group
rolled back and server operation continues. The name.
database. Explanation: A DELETE NODEGROUPMEMBER
command has deleted the specified number of
User response: Issue the command again, specifying a members from the indicated node group.
node group name that is defined in the server database.
For a list of the names of defined node groups in the System action: None.
server database, issue the QUERY NODEGROUP User response: None.
command.
ANR4789I Node node name associated to node

ANR4784I Node group node group name updated. group node group name.
Explanation: In response to the UPDATE Explanation: This message is displayed in response to
NODEGROUP command, the node group node group the DEFINE NODEGROUPMEMBER command. Node
name has been updated in the server database. node name is associated with the node group name node
System action: Server operation continues. group name.
User response: None. System action: Server operation continues.


ANR4790I ANR4796E
NDMPCONTROLPORT option. If this value requires

ANR4790I Node node name disassociated from node
change, the server will have to be restarted after setting
group node group name.
the option in the server options file.
the DELETE NODEGROUPMEMBER command. Node
ANR4794E The NAS file server File server name
node name is no longer associated with the node group
failed to open an NDMP data
name node group name.
connection to the TSM tape server.
System action: Server operation continues. Please verify that the file server is
capable of outbound data connections.
Explanation: During a NAS filer-to-server backup
operation the data connection from the file server to the
ANR4791E Command: Node group node group name is
TSM server failed. This may occur because a firewall
already defined.
exists between the file server and the TSM server and
Explanation: Server processing for the command is preventing outbound network connections on the file
command fails because the node group name node group server. This may also occur if the network configuration
name specified refers to a node group that is already of the system running the TSM server is reporting an
defined in the server database. invalid TCP/IP host address, for example "127.0.0.1".
System action: Database changes for the command are System action: The TSM server backup operation on
rolled back and server operation continues. The the file server fails.
User response: Verify that the NAS file server is
database.
capable of starting outbound network connections to
User response: Issue the command again, specifying a the TSM server. Verify that the file server supports
node group name that is not defined in the server NDMP 3-way operations. Verify that the network
database. For a list of the names of defined node configuration of the system running the TSM server is
groups in the server database, issue the QUERY reporting a valid TCP/IP host address. .
NODEGROUP command.
ANR4795E The TSM tape server failed to open an
ANR4792E NDMP Tape server unable to initialize NDMP data connection to the NAS file
due to error in LISTENing on port Port server File server name .
Explanation: The server failed in attempting to listen Explanation: During a NAS filer-to-server restore
for session requests on the server's internal tape server. operation the data connection from the TSM server to
the NAS file server failed. This may occur if the NAS
System action: Server operation continues, but NDMP file server is not properly configured to support NDMP
operations may fail. 3-way restore operations.
User response: Ensure that the System action: The TSM server restore operation on
NDMPCONTROLPORT option defaults to or is set to a the file server fails.
port number which is available in the system. The
QUERY OPTION command can be used to determine User response: Verify that the file server supports
the port number associated with the NDMP 3-way restore operations. .
NDMPCONTROLPORT option. If this value requires
change, the server will have to be restarted after setting
ANR4796E The TSM tape server failed to open a
the option in the server options file.
listening socket for accepting an NDMP
data connection from a NAS file server
ANR4793E NDMP Tape server is terminating due to using the network interface network host
an error in accepting a new session on name .
Port Port
Explanation: During a NAS filer-to-server backup
Explanation: The server failed in attempting to accept operation the TSM tape server failed to open a TCP/IP
a new session on the server's internal tape server. socket in order to listen for NDMP data connections
from a NAS file server. This may occur if the network
System action: Server operation continues, but NDMP interface chosen for NDMP data connections is not
operations may fail. running or does not support IP Version 4.
User response: Ensure that the System action: The TSM server backup operation of
NDMPCONTROLPORT option defaults to or is set to a the file server fails.
port number which is available in the system. The
QUERY OPTION command can be used to determine User response: Verify that the network interface
the port number associated with the specified in the NDMPPREFDATAINTERFACE server
option is properly configured and running. .
ANR4797E ANR4803I
ANR4797E Drive driveName is missing path ANR4800E The server-free operation from device
information. Please check that all source name through data mover data
related paths are defined properly. mover name to device target name
encountered an I/O error. The following
Explanation: A drive does not have sufficient path
information was returned from sense
information for the operation to complete. This is
device name: KEY=Key value ASC=Asc
typically due to a path not being defined.
value ASCQ=Ascq value SENSE=Sense info
System action: The server fails the storage operation.
Explanation: The server-free process did not complete
User response: Verify that all applicable paths are due to an I/O error.
defined for the drive. Also verify that the information
System action: The server will attempt to recover
contained in the paths is correct.
from the error and if possible retry the server-free data
transfer.
ANR4798E Server-free operation type operation had a
User response: The device reference manual provided
target failure. Please refer to
with the device usually contains tables that explain the
accompanying messages and Message
values of the KEY, ASC, and ASCQ fields. If the
Reference Manual for further
problem persists, contact your device service
information.
representative and provide the internal code values and
Explanation: The server-free operation encountered a sense data from this message.
target failure. This is typically due to one of three
conditions: 1. A SCSI error was encountered in either
ANR4801E The server-free operation from device
the source, target or datamover. 2. There was a problem
source name through data mover data
with the HBA issuing the SCSI command 3. An I-O
mover name to device target name
error caused the operation to time out.
encountered an error. This sense
System action: The server does not complete the information is typically generated by
server-free operation and attempts to trigger a failover configuration issues, please verify the
operation by the client. device definitions.
User response: If a SCSI error was encountered, please Explanation: The server-free process did not complete
refer to the sense information and correct for the due to the target being unreachable.
indicated problem. If the HBA had an error while
System action: The server will fail the transfer.
issuing command, please refer to the accompanying
message for appropriate action. If the operation timed User response: For the devices involved in this
out, please verify the datamover operation and SAN operation, please verify that the device and path
connections. defintions are correct. If this message has been issued
after the definitions have been verified, please verify
that the hardware is operating correctly and that the
ANR4799E The server-free operation type from device
data mover can see both target devices.
source name through data mover data
mover name to device target name failed
after issue. ANR4802I Password expiration period for node
node name has been reset.
Explanation: The server-free operation failed after
issuing the SCSI command. This might be because the Explanation: The node's password expiration period
value for the HBA (host bus adapter) scatter-gather list has been reset to the common password expiration
is not large enough. period.
System action: The server does not perform the System action: None.
server-free operation. The server will attempt either a
LAN-free or classic LAN operation.
User response: Perform either, or both, of the
ANR4803I Password expiration period for
following steps to allow server-free operations:
administrator administrator name has
v Change the serverfree batchsize to a lower value. been reset.
v Change the MAXIMUMSGLIST value for the HBA
Explanation: The administrator's password expiration
within the Windows registry, or run the DSMMAXSG
period has been reset to the common password
utility to change the MaximumSGList value to
expiration period.
0x41(65) for all HBAs.

ANR4804I ANR4813I
ANR4804I Node node name already uses the ANR4809I Audit command: Node group node group
common password expiration period. name has the same name as a node. The
node group entry must be corrected.
Explanation: The node's password expiration period is
currently set to the common password expiration Explanation: During Audit processing, a node group
period. was found with the same name as an existing node.
Because FIX=NO has been specified for the command,
the node group entry is not corrected.
uses the common password expiration
period. ANR4810I Audit command: Nodeid nodeid found for
missing node group node group name.
The node group entry must be corrected.
period is currently set to the common password
expiration period. Explanation: During Audit processing, a node was
found for a node group that does not exist. Because
FIX=NO has been specified for the command, the node
User response: None. group entry is not corrected.
ANR4806W The password expiration period for node
name cannot be reset to the common
password expiration period.
ANR4811I Audit command: Nodeid Node Id in node
Explanation: The node's password expiration period
group node group name does not exist.
could not be reset to the common password expiration
period at this time.
Explanation: During Audit processing, a node was
found in a node group, but the node does not exist.
User response: Attempt to reset the node's password Because FIX=NO has been specified for the command,
expiration period at a later time. the node group entry is not corrected.
ANR4807W The server is unable to reset
administrator name password expiration
period to the common password
expiration period. ANR4812I Audit command: Nodeid nodeid found in
inconsistent node group node group name.
period could not be reset to the common password
expiration period at this time. Explanation: During Audit processing, a node was
found in a node group that is inconsistent. Because
FIX=NO has been specified for the command, the node
User response: Attempt to reset the node's password group entry is not corrected.
expiration period at a later time.
ANR4808W The password expiration period for all
administrators and nodes has been reset
to the common password expiration ANR4813I Audit command: Node group node group
period. name has the same name as a node. The
node group entry will be corrected.
Explanation: All administrators not managed by a
profile and nodes on this server have had their Explanation: During Audit processing, a node group
password expiration period reset to the common was found with the same name as an existing node.
password expiration period. Because FIX=YES has been specified for the command,
the node group entry is deleted.
ANR4814I ANR4822E
v Scheduling problems
ANR4814I Audit command: Nodeid nodeid found in
missing node group node group name. v Event record problems
The node group entry will be corrected. v Password expiration problems
found for a node group that does not exist. Because ANR4818E The text cannot be formatted and
FIX=YES has been specified for the command, the node written to the server console. The text is
group entry is deleted. text. Try setting a wider screen width.
System action: Audit processing continues. 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
text of the output exceeds the size of the window.
ANR4815I Audit command: Nodeid Node Id in node
System action: The server will not write the output to
group node group name does not exist.
the console. The server continues operation.
The node group entry will be corrected.
User response: Increase the width of your window
and try the command again.
found in a node group, but the node does not exist.
the node group entry is deleted. ANR4819E Session session number for node node
name is not authorized to a table of
contents session.
Explanation: A client attempted to work with a table
of contents (TOC) session, but the node lacks proper
ANR4816I Audit command: Nodeid nodeid found in authorization. The server will not perform the request.
inconsistent node group node group name.
System action: The server will not perform the
The node group entry will be corrected.
request.
User response: Complete the work using a node with
found in a node group that is inconsistent. Because
proper authorization.
FIX=YES has been specified for the command, the node
group entry is deleted.
ANR4820E Command The creation date and creation
time are both required to be specified.
Explanation: The server-free process did not complete
due to the target being unreachable.
ANR4817E Command Command: Administrator
System action: The server will fail the command.
admin is not allowed to issue this
command while the system date is User response: Reissue the command, specifying both
suspect. Correct the system date or use creation date and creation time, or neither of them.
the ACCEPT DATE command to
establish the current date as valid.
ANR4821E Command: The creation date - date. is not
Explanation: The server has noted that the current valid
system date is suspect. An admin client session may
issue the ACCEPT DATE command to establish the Explanation: The specified command has been issued
current date as valid. No other commands are allowed with an invalid creation date.
until the system date is corrected or the current date is System action: Server operation continues, but the
established as valid. command is not processed.
System action: The server will fail the command. User response: Issue the command with a valid
User response: If the current system date is not valid, creation date.
reset the date. Otherwise, use the ACCEPT DATE
command to establish the current date as valid on the ANR4822E Command: The creation time date is not
server. Reissue the command. valid.
Accepting an invalid date can cause any of the Explanation: The specified command has been issued
following problems: with an invalid creation time.
v Premature deletion of data
v Excessive retention of data command is not processed.

ANR4823E ANR4830E
User response: Issue the command with a valid User response: Make sure a correct TOC object is
creation time. specified.
ANR4823E The loading or reading of a table of ANR4827E The loading of a table of contents for
contents for node node name, file space node node name, file space file space name
file space name failed because sufficient failed because a thread resource not
memory is not available. available.
Explanation: The server ends a table of contents Explanation: The server ends a table of contents
(TOC) loading or reading for the specified node and (TOC) loading for the specified node and file space
file space because sufficient memory is not available on because sufficient memory is not available for starting
the server. additional processes on the server.
System action: The TOC loading or reading is ended System action: The TOC loading is ended and server
and server operation continues. operation continues.
User response: See the documentation for the User response: See the documentation for the
operating system about how to increase memory for an operating system about how to increase memory for an
application. application.
ANR4824E The loading or reading of a table of ANR4828E 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 because of a lock file space name failed because an internal
conflict. server error was detected.
Explanation: The server ends a table of contents Explanation: The server ends a table of contents
(TOC) loading or reading for the specified node and (TOC) loading or reading for the specified node and
file space because the requested resource is already in 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.
User response: Try the operation again at a later time. prior to this message to determine the source of the
ANR4825E More than one table of contents is
requested but they are not for the same
representative.
node node name and same file space file
space name.
ANR4829E The loading or reading of a table of
Explanation: The server ends a table of contents
contents for node node name, file space
(TOC) loading for the requested TOCs. The requested
file space name failed. The transaction is
TOCs have to be for the same file space in the same
stopped.
node name.
User response: Try the TOC loading specifying the failed transaction.
TOCs in the same node for the same filespace.
System action: The table of contents (TOC) loading or
reading is ended and server operation continues.
ANR4826E The object for the table of contents is
not found in the server for node node
name, file space file space name.
Explanation: The server ends a table of contents contact your service representative.
(TOC) loading or reading for the object in the specified
node and file space, because the server cannot find the
object for the TOC.
System action: The TOC loading or reading is ended file space name failed. Insufficient mount
and server operation continues. The TOC object could points are available to satisfy the
be deleted from the server during server expiration or request.
volume deletion operation.
ANR4831E ANR4837I

sufficient mount points to read the table of contents
(TOC).
file space name failed. The data transfer is
System action: The TOC loading or reading is ended interrupted.
User response: If necessary, make more mount points (TOC) loading or reading for the specified node and
available. file space because data transfer to or from data storage
was interrupted by an external event.
ANR4831E The loading or reading of a Table of System action: The TOC reading is ended and server
Contents for node node name, file space operation continues.
file space name failed. The input volume
is already in use.
Explanation: During the TOC loading or reading interrupted. Attempt the operation again if the problem
operation, the requested input volume is already in use can be resolved.
by another process.
System action: The TOC loading or reading is ended ANR4835E The reading of a table of contents for
and server operation continues. node node name, file space file space name
failed. A data integrity error was
User response: Try the operation again at a later time. detected.
Explanation: The server stops reading a table of
ANR4832E The loading or reading of a table of contents (TOC) for the specified node and file space
contents for node node name, file space because a data integrity has been encountered on the
file space name failed. The required server.
volume was not mounted.
System action: The TOC reading is ended and server
Explanation: During the table of contents (TOC) operation continues.
loading or reading operation, a required volume cannot
be mounted. The mount request may have been User response: Examine the messages issued prior to
canceled. this message and contact your service representative.
and server operation continues. ANR4836E The reading of a table of contents for
node node name, file space file space name
User response: Try the TOC loading or reading again failed. There was an error in reading
and make sure the necessary volumes are accessible. from a device.
ANR4833W The loading or reading of a table of (TOC) reading for the specified node and file space
contents for node node name, file space because an I/O error has been encountered by the
file space name failed. The file was server in reading from a device.
deleted from server storage.
System action: The TOC reading is ended and server
Explanation: During the table of contents (TOC) operation continues.
loading or reading operation the file has been deleted
from server storage by another process before the User response: Examine the messages issued prior to
loading or reading is complete. this message that specify the device that is failing. The
server may need to be shut down with a HALT
System action: The TOC loading or reading is ended command to correct the hardware problem.
User response: Contact your administrator to find out ANR4837I The loading for the table of contents for
if DELETE FILESPACE, DELETE VOLUME, or node node name, file space file space name
inventory expiration processes are running; these started.
processes can delete files in server storage during TOC
loading or reading. Explanation: The loading for the table of contents
(TOC) in the specified node and file space has been
started.

ANR4838I ANR4845E
User response: The file space could be deleted during

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

server operation continues. ANR4844I Command: The specified table of
User response: None. file space name contains no entries.
Explanation: The specified table of contents (TOC)
ANR4841E The loading for the table of contents for exists, but it is empty. No entries are displayed.
failed. An invalid object type detected. System action: Server operation continues.
Explanation: The loading for the table of contents User response: None.
(TOC) in the specified node and file space failed
because the object type given is different than the one ANR4845E The writing of the of the table of
in the server database. contents for node node name, file space
System action: The TOC loading is ended and the file space name failed: a directory path
server operation continues. exceeds max characters bytes in length.
File: lowLevel name, NDMP Node ID:
User response: Re-try the Table of Contents loading, node id hi .node id lo, NDMP Parent Node
specifying a valid object type. ID:Parent id hi. Parent id lo.
Explanation: During a backup of a NAS filesystem,
ANR4842E The loading of a table of contents for the server received a file history record from the NAS
node node name failed. The file space device with a directory path length which exceeded the
name was not found. maximum length supported by ITSM. The server is
Explanation: The server ends a table of contents unable to create a TOC for a NAS filesystem which
(TOC) loading for the specified node because the server contains directory that is longer than 1024 bytes. If the
could not find the file space name for the TOC object to TOC parameter on the BACKUP NODE command is
be loaded. PREFERRED, the backup continues. If the TOC
parameter was YES, the backup fails.
System action: The TOC loading is ended and server
ANR4846E ANR4854I
System action: The TOC creation is ended and server

ANR4850I Audit command: An email address
associated with node node name is
User response: If TOC=YES was specified on the invalid. The email entry will be
BACKUP NODE command, retry the command with corrected.
TOC=NO.
Explanation: During Audit processing, an invalid
email address was found for the specified node.
ANR4846E Operation process process ID terminated - Because FIX=YES has been specified for the command,
The server is unable to create a table of the email address entry is deleted.
file space.
Explanation: While attempting to create a table of
contents (TOC) for the specified node and file space in
the indicated TOC destination pool, a failure occurred. ANR4851I Audit command: Invalid adminid admin id
found during email address audit. The
System action: The operation fails because TOC
email entry must be corrected.
creation is set to YES.
Explanation: During Audit processing, a non-existent
User response: Look for previous messages giving a
adminid was found associated with an email address.
specific reason for the failure. Take corrective action as
Because FIX=NO has been specified for the command,
appropriate.
the email address entry is not corrected.
ANR4847I Audit command: Invalid nodeid nodeid
found during email address audit. The User response: None.
email entry must be corrected.
Explanation: During Audit processing, a non-existent ANR4852I Audit command: An email address
nodeid was found associated with an email address. associated with administrator
Because FIX=NO has been specified for the command, administrator is invalid. The email entry
the email address entry is not corrected. must be corrected.
System action: Audit processing continues. Explanation: During Audit processing, an invalid
email address was found for the specified
administrator. Because FIX=NO has been specified for
the command, the email address entry is not corrected.
ANR4848I Audit command: An email address
associated with node node name is
invalid. The email entry must be User response: None.
corrected.
Explanation: During Audit processing, an invalid ANR4853I Audit command: Invalid adminid adminid
email address was found for the specified node. found during email address audit. The
Because FIX=NO has been specified for the command, email entry will be corrected.
the email address entry is not corrected.
Explanation: During Audit processing, a non-existent
System action: Audit processing continues. adminid was found associated with an email address.
the email address entry is deleted.
ANR4849I Audit command: Invalid nodeid nodeid
found during email address audit. The User response: None.
email entry will be corrected.
Explanation: During Audit processing, a non-existent ANR4854I Audit command: An email address
nodeid was found associated with an email address. associated with administrator
Because FIX=YES has been specified for the command, administrator is invalid. The email entry
the email address entry is deleted. will be corrected.
System action: Audit processing continues. Explanation: During Audit processing, an invalid
email address was found for the specified
administrator. Because FIX=YES has been specified for
the command, the email address entry is deleted.

ANR4855I ANR4861W

ANR4859I Parameter parameter name on the
command command name is no longer
ANR4855I Command command subcommand is no supported.
longer supported and there is no direct
Explanation: The function that was provided by this
replacement for this capability.
parameter is no longer necessary
Explanation: The functions that were provided by this
command are no longer neccessary.
User response: Review information about product
changes in the IBM Tivoli Storage Manager Information
User response: Review information about product Center.
Center.
ANR4860W The correct value of ARCHRETENTION
for domain domain name will not be sent
ANR4856I Command command subcommand is no to the managed servers. Please upgrade
longer supported. The following the managed servers to be at least the
commands provide similar functions: same level as that of the configuration
newcommand. See the Tivoli Storage manager.
Manager Information Center for details
Explanation: The configuration manager has an
on commands, or issue HELP command
ARCHRETENTION value that is greater than the
for the replacement commands.
managed server can manage. This is because the
Explanation: The functions formerly provided by this managed server is at a lower level than the
command are now provided by one or more new configuration manager. The value of the
commands ARCHRETENTION for the indicated domain is set to
the maximum value that the managed server can
System action: System operation continues. process.
User response: Review information about product System action: The server operation continues.
Center. User response: To correctly send the value of the
ARCHRETENTION to the managed servers, please
upgrade the managed servers to at least the same level
ANR4857I Command command subcommand is no as that of the configuration manager.
longer supported. The following options
provide similar functions: newoptions.
See the Tivoli Storage Manager ANR4861W The correct value of RETVER for the
Information Center for details on the archive copy group domain name policy set
options or issue the HELP command for name mgmt class name cg name will not be
the replacement options. sent to the managed servers. Upgrade
the managed servers to at least the same
Explanation: The functions formerly provided by this level as that of the configuration
command are now provided by one or more new manager.
options
Explanation: The configuration manager has a
System action: System operation continues. RETVER value that is greater than what the managed
User response: Review information about product server can process. This is because the managed server
changes in the IBM Tivoli Storage Manager Information is at a lower level than the configuration manager. The
Center. value of the RETVER for the indicated copy group is
set to NOLIMIT in the managed server.
ANR4858I Option option name is no longer System action: The server operation continues.
supported and there is no direct User response: To correctly send the value of RETVER
replacement for this capability. for the copy group to the managed servers, please
Explanation: The funtions formerly provided by this upgrade the managed servers to at least the same level
option are no longer necessary as that of the configuration manager.

User response: Review information about product
Center.
ANR4862W ANR4867I
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 If the backup-archive
the release level of the managed server
client is not able to authenticate with the Tivoli Storage
is earlier than the release level of the
Manager server then scheduled operations for that
configuration manager.
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 Tivoli Storage Manager server.
level of the managed server is earlier than release level
of the configuration manager. User response: Either change the Tivoli Storage
Manager server name back to the original name, or
reset the password on the server using the UPDATE
User response: Upgrade the managed server to the NODE command to a known password and then use
same release level or later than that of the configuration dsm, dsmc, or dsmcutil to manually set the password
manager. on all Windows backup-archive clients that use
"passwordaccess generate".
ANR4863W The value of the
ACTIVEDESTINATION parameter for ANR4866I Node node name is not a member of a
domain domain name that was received domain that is configured to use active
from the configuration manager will not data pool active data pool name.
be used on the managed server.
Explanation: The primary storage pool to which the
Explanation: The received value of the client node will write data is capable of using an active
ACTIVEDESTINATION parameter contains active-data data pool. However the client node is not a member of
storage pool IDs that cannot be managed by the a domain that is authorized to write to the active data
managed server. The problem is that the release level of pool.
the configuration manager is earlier than the release
System action: Data from the node is not written to
level of the managed server.
the active data pool.
User response: If the client node data must be written
User response: Upgrade the configuration manager to to an active data pool, move the client node to a
the same release level or later than that of the managed domain that is authorized for this action or update the
server. current domain for active data pool processing.
ANR4864E The module name support module was ANR4867I Session session number for node node
not loaded. name (client platform) terminated - session
retry failed.
Explanation: The indicated support module was not
loaded. Explanation: The specified client session is ended by
the server because a previous error has been detected
System action: The server cannot perform functions
on the server. Retry attempts were not able to resume
that require this module.
the session.
User response: Restart the Tivoli Storage Manager
System action: The session is ended and server
server and retry the operation. If the support module
does not load, contact your service representative.
User response: If the session is a proxied LAN-Free
session for a storage agent, this error might be the
ANR4865W The server name has been changed.
result of a mount point or volume preemption on the
Windows clients that use
storage agent. Review the messages logged by the
"passwordaccess generate" may be
storage agent to determine if a storage agent action
unable to authenticate with the server.
caused the error. Review the messages logged by this
Explanation: After the name of a Tivoli Storage session to determine alternate causes.
Manager server is changed, the generated password on
Windows backup-archive clients is not usable. The
password is generated on backup-archive clients that
use "passwordaccess generate". The generated
password is not usable because the generated password

ANR4868I ANR4876W
length specifications for valid collocation group names,

ANR4868I Canceling the Database Backup session
refer to the Administrators Reference.
session number for node node name is not
allowed.
ANR4873E Command: Collocation group description
Explanation: The server cannot cancel the session that
exceeds maximum length of length limit
is specified in the CANCEL SESSION command.
characters.
User response: Database Backup sessions cannot be command fails because the collocation group description
cancelled with the CANCEL SESSION command. Issue specified is longer than the length limit number of
the CANCEL PROCESS command to terminate the characters allowed.
Database Backup operation.
ANR4870W Audit command: Storage pool storage pool command is not successful in changing the server
name, specified as a Table of Contents database.
(TOC) destination for copy group copy
group name in management class
a shorter collocation group description.
management class name, policy set set
exist. ANR4874I Collocation group collocation group name
updated.
pool specified for the Table of Contents (TOC) Explanation: In response to the UPDATE
destination of the specified copy group that is not COLLOCGROUP command, the collocation group
defined in the server database. If this copy group is collocation group name has been updated in the server
used in an active policy set, then the NDMP backup database.
with a TOC creation operation may fail when
attempting to put TOC entries in the destination. System action: Server operation continues.

use the DEFINE STGPOOL command to define the ANR4875I Collocation group collocation group name
missing storage pool, or the UPDATE COPYGROUP deleted.
command to update the copy group to refer to an Explanation: In response to the DELETE
existing storage pool. COLLOCGROUP command, the collocation group
collocation group name has been deleted from the server
ANR4871I Collocation group collocation group name database.
defined. System action: Server operation continues.
Explanation: A DEFINE COLLOCGROUP command User response: None.
has created the collocation group indicated.
System action: None. ANR4876W Command: Node node name cannot be
User response: None. processed because it is not registered.
ANR4872E Command: Invalid collocation group the indicated node. The node is not registered. The
name - collocation group name. other nodes can be processed if specified by the
command.
command fails because the collocation group name System action: The indicated node is not processed,
collocation group name specified does not contain valid but other nodes can be processed if specified by this
characters or contains too many characters. command.
System action: Database changes for the command are User response: If the node name was entered
rolled back and server operation continues. The incorrectly, issue the command again with the correct
command is not successful in changing the server node name.
database.
a collocation group name that conforms to the name
ANR4877E ANR4885E

ANR4877E Command: Collocation group collocation
database.
group name is not defined.
collocation group name that is not defined in the server
command fails because the collocation group name
database. For a list of the names of defined collocation
collocation group name specified does not refer to a
groups in the server database, issue the QUERY
defined collocation group in the server database.
COLLOCGROUP command.
ANR4882E Command: Collocation group collocation
group name still contains at least one
database.
node.
Explanation: Server processing for the delete
collocation group name that is defined in the server
command command fails because the collocation group
database. For a list of the names of defined collocation
collocation group name specified refers to a collocation
groups in the server database, issue the QUERY
group that still contains at least one node. A collocation
COLLOCGROUP command.
group cannot be deleted if one or more client nodes are
still assigned to the collocation group.
defined in the collocation group
Explanation: A DEFINE COLLOCMEMBER command database.
has created the specified number of members in the
User response: To remove remaining nodes from the
indicated collocation group.
collocation group, issue the DELETE
System action: None. COLLOCMEMBER command. After all nodes are
removed, issue the delete command again.
ANR4883I Node node name associated to collocation

group collocation group name.
deleted from collocation group collocation
group name. Explanation: This message is displayed in response to
Explanation: A DELETE COLLOCMEMBER command
name is associated with the collocation group name
has deleted the specified number of members from the
indicated collocation group.
ANR4884W Node node name already associated to

the DELETE COLLOCMEMBER command. Node node
name is already associated with the collocation group
name is no longer associated with the collocation group
name collocation group name. The indicated node is not
name collocation group name.
processed. The other nodes can be processed if
System action: Server operation continues. specified by the command.
User response: None. System action: Server operation continues.

User response: If the node name was entered
ANR4881E Command: Collocation group collocation incorrectly, issue the command again with the correct
group name is already defined. node name.

command fails because the collocation group name ANR4885E Command: Either node name or
collocation group name specified refers to a collocation collocation group name must be
group that is already defined in the server database. specified.
System action: Database changes for the command are Explanation: The indicated command failed because
rolled back and server operation continues. The neither node name nor collocation group name is

ANR4886E ANR4893I
specified or the node name and the collocation group

ANR4890I Audit command: Inventory name object
name both are specified.
(name.ID) belonging to node NodeId and
System action: The indicated command fails. The filespace FilespaceId has a missing
server operation continues. database element. It will be corrected if
FIX=YES was specified for the
User response: Issue the command again, by DSMSERV AUDITDB command.
specifying either the node name or the collocation
group name. Explanation: A database audit process found an
inventory name object that is incomplete. If FIX=YES
has been specified for the command, the inventory
ANR4886E Audit command: A missing or incorrect entry will be corrected.
collocation group id has been detected
for node node id. System action: Audit processing continues.
Explanation: A database audit process detects missing User response: None.

or incorrect collocation group identifier for the specified
node member.
ANR4891I Audit command: Inventory name reverse
System action: Audit processing continues. lookup object (name.ID) belonging to
node NodeId and filespace FilespaceId has
User response: Issue the audit command again, and a missing database element. It will be
specify FIX=YES so that the error can be corrected. corrected if FIX=YES was specified for
the DSMSERV AUDITDB command.
ANR4887E Audit command: A missing or incorrect Explanation: A database audit process found an
collocation group id has been detected inventory name object that is incomplete. If FIX=YES
for node node id - it will be corrected. has been specified for the command, the inventory
Explanation: A database audit process detects missing entry will be corrected.
or incorrect collocation group identifier for the specified System action: Audit processing continues.
node member. Because FIX=YES has been specified for
the audit command, the error will be corrected. User response: None.

ANR4892I Audit command: Inventory name object
User response: None. (name.ID) belonging to node NodeId and
filespace FilespaceId has a missing parent
ANR4888E Audit command: Collocation group global element. If FIX=YES was specified for
high-water mark does not match the the DSMSERV AUDITDB command,
identifier in use. the name entry will be related to the
root directory for the file space.
attribute used to track collocation group identifiers are Explanation: A database audit process found an
incorrect. inventory name object that has no parent entry. To
ensure that the object is restorable, the entry will be
System action: Audit processing continues. linked to the root directory for the file space if FIX=YES
User response: Issue the audit command again, and was specified for the DSMSERV AUDITDB command.
specify FIX=YES so that the error can be corrected. The user should query the server to determine which
objects have been moved to the root directory. The next
backup operation from the client will create objects
ANR4889E Audit command: Collocation group global with the correct path name.
high-water mark does not match the
identifiers in use; it will be corrected. System action: Audit processing continues.
Explanation: A database audit process finds the User response: None.

attributes used to track collocation group identifiers are
incorrect. Because FIX=YES has been specified for the ANR4893I Audit command: An inventory backup
audit command, the attributes will be corrected. object corresponding to name ID nameId
System action: Audit processing continues. belonging to node NodeId and filespace
FilespaceId has a missing name. If
User response: None. FIX=YES was specified for the
DSMSERV AUDITDB command, the
name entry will be related to the root
directory as object name for the file
space.
ANR4894I ANR4900W

ANR4897I Database restore of operation operation
inventory backup object that has no name entry. To
ID will use device class device class name
ensure that the object is restorable, the entry will be
and attempt to use number of streams
linked to the root directory for the file space if FIX=YES
streams.
was specified for the DSMSERV AUDITDB command.
The user should query the server to determine which Explanation: The server restore database process for
objects have been moved to the root directory. The next the operation ID will be performed for the device class
backup operation from the client will create objects and number of streams indicated.
with the correct path name.
System action: The server performs the database
System action: Audit processing continues. restore operation.
ANR4894I Audit command: Auditing inventory ANR4898W This is a pre-release server_version Tivoli
names. Storage Manager server (driver
driver_number, build build_id). It is not
supported for commercial or production
use.
about client backup object names is currently being
examined by the database audit process. Explanation: The Tivoli Storage Manager server is
running a pre-release program. The program can be
used to test or evaluate new features, but it can neither
User response: None. be used for any commercial purpose nor placed into
production.
ANR4895E Deduplicated bitfile bitfile id on volume System action: No action is taken.

volname has invalid links.
User response: If the Tivoli Storage Manager server is
Explanation: While reading a deduplicated bitfile, the being used to evaluate new features, no action is
server detected invalid deduplication information. required. If the server will be used in a production
environment or for a commercial purpose, contact your
System action: If the operation is a server data IBM sales representative or authorized business partner
movement, the inconsistent bitfile is marked invalid to obtain a fully-supported, released version.
and skipped, but the operation continues. If, however,
the operation is a client restore or retrieve, the bitfile is
marked as damaged. ANR4899E The server database was formatted
using a pre-release server_version Tivoli
User response: If the volume is in a primary storage Storage Manager server (driver
pool, run a RESTORE VOLUME command to fix the driver_number, build build_id). The server
invalid bitfile. If the volume is in a copy storage pool, is not supported for commercial or
run a DELETE VOLUME DISCARDDATA=YES production use.
command to delete the volume, then backup the
primary storage pool again. Explanation: The server database was created using
an unsupported, pre-release version of the Tivoli
To see what files may have been marked as damaged, Storage Manager server. The server can be used to test
use the QUERY CONTENT DAMAGED=YES or evaluate new features, but it can neither be used for
command. any commercial purpose nor placed into production.
System action: No action is taken.
ANR4896I Inventory client file expiration is
restarting process process num from User response: If the server is being used to evaluate
startdate. new features, no action is required. If the server will be
used in a production environment or for a commercial
Explanation: The server is in the process of restarting purpose, remove the database. Create a new database
a previously cancelled expiration process. using a fully-supported, released version.
System action: The server will continue expiring
eligible objects. ANR4900W EMC Centera Software Development Kit
User response: None. (SDK) libraries failed to load or are
missing.
Explanation: The libraries are required to ensure that
the Tivoli Storage Manager server can operate devices
with the defined CENTERA device class.

ANR4911E ANR4919W
System action: None. finding any snapshot volumes.

User response: Ensure that the EMC Centera SDK is System action: None.
installed on the system and that all libraries and
associated links have the read permission.

ANR4911E File name is too long, the server is
snapshot to date date time.
unable to build a table of contents for
node node name, file space file space name, Explanation: A point-in-time database restore with the
file name file name, node identifier node TODATE parameter and source snapshot specified has
id, parent node identifier parent node id. begun. When this restore is complete, the database will
Table of contents creation fails. be committed to the point in time of this backup.
Explanation: The file name must be 512 bytes or less. System action: None.
If the size is larger than 512 bytes, the Tivoli Storage
Manager server cannot create a table of contents (TOC) User response: None.
for a Network Appliance file server.
System action: The TOC creation fails. ANR4917I Point-in-time database restore with
snapshot complete, restore date date time.
User response: Rename the file with a shorter name.
For more information about the file name or the node Explanation: A point-in-time database restore with the
identifier, including locating and correcting the file or TODATE parameter specified has completed. The
directory, refer to Network Appliance documentation. database is committed to the point in time of this
backup, which may be different than the TODATE
Once the problem has been corrected, try the operation specified. If this is the case, an additional message will
again. be displayed.
ANR4912I Database restore type byte count.
Explanation: A database restore is in progress.
System action: None. ANR4918W The filespace filespace name (filespace id)
for node node name will not be included
in the backupset backupset name (data
type data type) because it was not created
ANR4913I Database restore completed for restore by the backup/archive client and cannot
to date date time. No backup volume be restored from the backupset.
found.
Explanation: Data from the filespace will not be
Explanation: A point-in-time database restore has been included in the backupset because the filespace was not
completed without finding any backup volumes. created by the backup/archive client and it cannot be
restored from the backupset.
ANR4914I Point-in-time database restore
completed, no backup volume found for ANR4919W The filespace filespace name (filespace id)
restore date date time. for node node name will not be included
in the backupset backupset name (data
type data type) because it is not a
TODATE parameter specified has completed without
supported application type.
finding any backup volumes.
included in the backupset because the filespace does
User response: None. not belong to a supported application type.
ANR4915I Point-in-time database restore with
snapshot completed, no snapshot
volume found for restore date date time.
Explanation: A snapshot database restore with the
TODATE parameter specified has completed without
ANR4920E ANR4929E
containing data has not reached the low migration

ANR4920E Command: Administrator administrator
threshold.
name is not authorized to issue this
command for storage pool pool name. System action: The server does not process the
command.
the indicated command, but this administrator does not User response: Re-issue the command when migration
have the proper authority necessary to run the is needed for the pool.
command for the indicated pool. The indicated pool
could be the storage pool being migrated or being
reclaimed, or the storage pool to which files are ANR4925W Migration process process ID terminated
migrated or reclaimed. for storage pool storage pool name -
duration exceeded.
command. Explanation: During migration for the indicated
storage pool, a process performing the migration has
User response: Issue the command from a properly been terminated because the migration duration has
authorized administrator ID, or contact the system exceeded.
the current administrator ID. System action: The migration process is terminated.
ANR4921E Command: Primary storage pool pool name
does not have a target pool. ANR4926W Migration terminated for volume volume
Explanation: The specified primary storage pool does name - duration exceeded.
not have a target storage pool for the specified Explanation: During migration for the indicated
operation. volume, the duration for the migration has been
System action: The server does not process the exceeded.
command. System action: The volume migration is terminated.
User response: Define a target storage pool for the User response: None.
pool specified on the command and re-issue the
command.
ANR4927W Reclamation terminated for volume
volume name - duration exceeded.
ANR4922E Command: Migration is currently
running for the storage pool pool name. Explanation: During reclamation for the indicated
volume, the duration for the reclamation has been
Explanation: The migration operation is already exceeded.
running for the specified storage pool.
System action: The volume reclamation is terminated.
User response: Re-issue the command when migration

is not running. ANR4928E Command: Reclamation is not allowed
for the storage pool pool name.
ANR4923E Command: Reclamation is currently Explanation: The high reclamation threshold

running for the storage pool pool name. (percentage) is set to 100 to prevent reclamation for the
specified storage pool.
Explanation: The reclamation operation is already
running for the specified storage pool. System action: The server does not process the
command.
command. User response: Re-issue the command when migration
is needed for the pool.
User response: Re-issue the command when
reclamation is not running.
ANR4929E Command: The storage pool pool name is
not a sequential-access pool.
ANR4924I Command: Migration is not needed for
the storage pool pool name. Explanation: The specified storage pool is not a
sequential-access storage media for the specified
Explanation: Either the current percentage utilization operation. The specified operation only applies to a
of the specified storage pool is less than the low sequential-access storage media.
migration threshold or the number of volumes

ANR4930I ANR4937E

ANR4934I Offsite reclamation ended for storage
command.
pool pool name, Number Processes
User response: Re-issue the command for a number of processes, Number Volumes
sequential-access storage media. Reclaimed number of volume reclaimed,
Elapsed Time seconds seconds.
ANR4930I Reclamation process process ID started Explanation: Offsite reclamation ended successfully.
for primary storage pool storage pool
name automatically or manually,
threshold=threshold value, User response: None.
duration=duration.
Explanation: Because the high reclamation threshold ANR4935I The migration of the primary pool name
for the storage pool shown has been exceeded, a primary storage pool is complete.
process has been started to reclaim files from the Number of files migrated: number of
storage pool. Note: a duration value of None means migrated files. Number of bytes migrated:
that the duration is not specified and hence the number of migrated bytes. Number of
reclamation runs without duration. deduplicated migrated bytes: number of
migrated dedup bytes. Number of
System action: Data is moved from this storage pool
unreadable files: number of unreadable
to the same pool or to the reclaim storage pool.
files.
Explanation: Migration processing for the specified
storage pool ended with the displayed results.
ANR4931I Reclamation process process ID started
for copy storage pool storage pool name
automatically or manually, User response: Examine previous messages to
threshold=threshold value, determine whether all migration processes ended
offsiteRclmLimit=limit value, successfully.
duration=duration.
Explanation: Because the high reclamation threshold ANR4936I The reclamation of the pool name storage
for the storage pool shown has been exceeded, a pool is complete. Number of files
process has been started to reclaim files from the reclaimed: number of reclaimed files.
storage pool. Note: a duration value of None means Number of reclaimed bytes: number of
that the duration is not specified and hence the reclaimed bytes. Number of reclaimed
reclamation runs without duration. deduplicated bytes: number of reclaimed
dedup bytes. Number of reconstructed
System action: Data is moved from this storage pool
files: number of reconstructed files. Number
to the same pool or to the reclaim storage pool.
of unreadable files: number of unreadable
User response: None. files.
Explanation: Reclamation processing for the specified
ANR4932I Reclamation process process ID ended for storage pool ended with the displayed results.
Explanation: A reclamation process for the named
User response: Examine previous messages to
storage pool ends. This action can occur because the
determine whether all reclamation processes ended
threshold for the storage pool has been reached or
successfully.
because the duration has been exceeded.
ANR4937E Command: Reclamation will not run -
User response: None. delete filespace is currently running.
Explanation: A delete filespace operation is running.
ANR4933I Space reclamation ended for offsite To Avoid the resource contention, reclamation will not
volume volume name. run when delete filespace is running.
Explanation: Space reclamation for the named offsite System action: The server does not process the
volume is complete. command.
System action: None. User response: Re-issue the command when delete
filespace is not running.
ANR4938E ANR4944E
Storage Manager is running.

ANR4938E Command: Administrator administrator
name is not authorized to issue this Verify that the reported Unicode name is valid. Note
command for target storage pool pool that the Unicode name is encoded in little-endian
name. UCS-2 and is reported in hexadecimal notation. If the
Unicode name is not valid, the problem may usually be
corrected by deleting or renaming the corresponding
the indicated command, but this administrator does not
file or directory on the Network Appliance file server.
have the proper authority necessary to run the
The node identifier and parent node identifier are
command for the indicated pool. The indicated pool is
provided by the Network Appliance NDMP server.
the pool that to which files are migrated or reclaimed.
Their values are NDMP-server implementation
System action: The server does not process the dependent but will typically be the inode number of
command. the file or directory. For more information about the
Unicode name or the node identifiers, including using
User response: Issue the command from a properly
them to locate and correct the invalid file or directory,
authorized administrator ID, or contact the system
contact Network Appliance for support.
the current administrator ID. If possible, configure the Network Appliance file server
to always encode file and directory names as UTF-8.
For additional information about using international
characters with Network Appliance file servers, see the
valid for a DISK storage pool.
:cit.ADSM Administrators Guide:ecit. for your
Explanation: The command indicated specifies an particular platform.
option that is not valid for a DISK storage pool.
Once the problem has been corrected, try the operation
System action: The server does not process the again.
command.
User response: Reissue the command with options ANR4942E Command: Volume volume name is not
appropriate for a DISK storage pool. defined. The file name does not exist or
has no space.
ANR4940E Reclamation is ended for storage pool Explanation: A define volume command was issued
storage pool name. There is an insufficient for the indicated volume name. The volume name was
number of mount points available for specified without the FORMATSIZE parameter, but it
removable media. either does not exist or exists as a file of size 0.
Explanation: During reclamation for the indicated System action: The volume definition fails.
storage pool the server could not allocate sufficient
User response: Use the FORMATSIZE parameter to
mount points in the storage pool.
have the server pre-allocate space for the new volume.
System action: Reclamation stops.
User response: If necessary, make more mount points ANR4943E Command: Volumes cannot be deleted
available. from
RECLAMATIONTYPE=SNAPLOCK
storage pools.
ANR4941E The server is unable to translate the
Unicode name while building table of Explanation: Deleting volumes from
contents for node node name, file space RECLAMATIONTYPE=SNAPLOCK storage pools is
file space name, Unicode name unicode not allowed. Rather, deletion of empty volumes occurs
name node identifier node id, parent node automatically during reclamation processing.
identifier parent node id. Table of
contents creation fails.
User response: Allow deletion of empty volumes to
Explanation: While creating a table of contents (TOC)
be done automatically during reclamation processing.
for a Network Appliance file server, the TSM server
attempted to translate the Unicode name in the file
history message from UCS-2 to UTF-8. The translation ANR4944E Command: Volumes cannot be defined in
failed. RECLAMATIONTYPE=SNAPLOCK
storage pools.
System action: The TOC creation fails.
Explanation: Defining volumes on
User response: Verify that the required support for
RECLAMATIONTYPE=SNAPLOCK storage pools is
translations between UCS-2 and UTF-8 is properly
not allowed. Rather, the MAXSCRATCH parameter on
installed and configured on the system where the Tivoli
the DEFINE and UPDATE STGPOOL commands is

ANR4945E ANR4951E
used to make storage pool space available for these Storage Manager is running. Try the operation again.
storage pools.
System action: The operation fails. ANR4948E The list file named list file name contains
more than max entry count entries.
User response: Use the MAXSCRATCH parameter on
the DEFINE and UPDATE STGPOOL commands to Explanation: While reading a list file, the server
create space in the storage pool. detects that the number of entries exceeds the
maximum allowed.
ANR4945E Command:The volume named volume System action: The operation fails.
name is larger than is allowed for a
User response: Consider breaking up the operation
volume on your system.
into multiple commands, each handling a subset of the
Explanation: While attempting to define a volume on required entries.
volume name the server detected that the volume size
exceeds the maximum allowed.
ANR4949E The server is unable to write to table
System action: The operation fails. table name because there is not enough
temporary space in the database. Table
User response: Consider defining 2 smaller volumes.
of contents operation for node node
name, file space file space name fails.
ANR4946W The character encoding of NDMP file
Explanation: While operating on a table of contents
history messages for node node name, file
(TOC), the server attempted to insert data into the
system file system name is unknown. The
specified temporary database table, but there is not
Tivoli Storage Manager server will use
enough temporary space in the servers database.
the UTF-8 encoding to build a table of
contents. System action: The TOC operation fails.
Explanation: While initializing a backup with a table User response: Ensure that sufficient temporary space
of contents (TOC) for the specified node and file is available in the server's database.
system, the TSM server determines that the character
encoding of file history information from the NAS file
ANR4950E The server is unable to retrieve NDMP
server is unknown. The Tivoli Storage Manager server
file history information while building
will assume file history information is encoded as
table of contents for node node name, file
UTF-8 in order to build a TOC.
space file space name. NDMP node ID is
If the character encoding is not UTF-8 and non-English NDMP node ID. Table of contents
characters are present, the names will be improperly creation fails.
displayed and probably unreadable, making recovery
Explanation: While creating a table of contents (TOC),
difficult.
the server attempted to retrieve information contained
System action: The operation continues. in a previous NDMP file history message. The
information was not found. This could be caused by a
User response: Verify that the encoding of file history
problem with the NAS file server that is sending file
information is UTF-8. For Network Appliance NAS file
history messages. The NDMP node ID reported in the
servers, verify that the volume language for the
message is the node ID referenced in the current
specified node and file space is UTF-8, or a subset of
NDMP file history message.
UTF-8 (for example 7-bit ASCII).
System action: The TOC creation fails.
ANR4947E The server is unable to translate the User response: Verify that the NDMP server is
Unicode path name while building table properly sending file history information. Otherwise,
of contents for node node name, file contact your service representative.
space file space name. Table of contents
creation fails.
ANR4951E The writing of a table of contents for
Explanation: While creating a table of contents (TOC), node node name, file space file space name
the server attempted to translate the Unicode path failed. The object is excluded from
name in the file history message from UCS-2 to UTF-8. storage pool pool name and all successor
The translation failed. pools because of its size.
System action: The TOC creation fails. Explanation: The server ends a table of contents
(TOC) creation for the specified node. The size of the
User response: Verify that the required support for
TOC is larger than that allowed in the storage pool
translations between UCS-2 and UTF-8 is properly
specified by the TOC destination attribute of the
installed and configured on the system where the Tivoli
ANR4952E ANR4957E
assigned management class backup copy group. No System action: The TOC creation is ended and server
successor storage pools to the one specified on the copy operation continues.
group can accept the large TOC.
System action: The TOC creation is ended and server this message to determine why the data transfer was
operation continues. interrupted. Attempt the operation again if the problem
can be resolved.
User response: Increase the maximum file size for one
or more of the storage pools in the storage hierarchy to
accommodate the TOC. An authorized administrator ANR4955E The writing of a table of contents for
can increase the MAXSIZE parameter by issuing the node node name, file space file space name
UPDATE STGPOOL command. failed. The storage media is not
available.
ANR4952E The writing of a table of contents for 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. No space is available in storage volumes are not available in the storage pools in which
pool pool name and all successor pools. the TOC is to be stored.
Explanation: The server ends a table of contents System action: The TOC creation is ended and server
(TOC) creation for the specified node. The storage pool operation continues.
specified by the TOC destination attribute of the
backup copy group in the assigned management class
does not contain enough free space to hold the TOC.
No successor storage pools to the one specified on the
copy group contain enough free space.
System action: The TOC creation is ended and server make them available for TOC storage.
User response: An authorized administrator can issue ANR4956E The writing of a table of contents for
the DEFINE VOLUME command to add storage to one node node name, file space file space name
or more storage pools in the storage hierarchy. This failed. The server does not have
action may also involve creating storage space by using sufficient recovery log space.
an operating system-specific utility.
(TOC) creation for the specified node because sufficient
ANR4953E The writing of a table of contents for log space is not available on the server.
failed. The server encountered an error
when writing to the storage device.
(TOC) creation for the specified node because an I/O
error has been encountered by the server in writing to
a device.
volumes are used.
User response: Query the activity log to find messages node node name, file space file space name
preceding this one that specify the failing device. failed. The server does not have
Storage pool volumes can be varied offline (by using sufficient database space.
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.
failed. The data transfer was User response: An authorized administrator can issue
interrupted. the DEFINE DBVOLUME command to add volumes
for use by the database. Also,an administrator can issue
the EXTEND DB command to extend the size of the
(TOC) creation for the specified node because data
database so that the new volumes are used.
external event.

ANR4958E ANR4965E

failed. The server is unable to start a
new thread.
memory is not available for starting additional
failed. The server does not have
processes on the server.
sufficient mount points available to
System action: The TOC creation is ended and server satisfy the request.
User response: See the documentation for the sufficient mount points to write the table of contents
operating system about how to increase memory for an (TOC).
application.
available.
failed. The server does not have
sufficient memory.
failed. See previous messages.
(TOC) creation for the specified node because a
previous error has occurred.
application.
failed. The server detected an internal
error.
representative.
(TOC) creation for the specified node because an
ANR4964I Space reclamation deleted number of
internal logic error is detected.
volumes WORM FILE volumes for
System action: The TOC creation is ended and server storage pool storage pool name.
Explanation: During reclamation for the indicated
User response: Examine the server messages issued storage pool, the server deleted the indicated number
prior to this message to determine the source of the of empty WORM FILE volumes that have exceeded
error. Issue the QUERY ACTLOG command to view the their retention date.
System action: Reclamation and server operations
continue.
representative.
node node name, file space file space name ANR4965E operation is ended for storage pool storage
failed. The server could not commit the pool name. Sufficient database space is
transaction. not available.
Explanation: An error was detected during transaction Explanation: Insufficient server database space has
commit. This message should be preceded by other been encountered during the indicated operation for
messages that give additional information about the the indicated storage pool.
failed transaction.
System action: Either the Migration or Reclamation
System action: The table of contents (TOC) creation is stops, or the operation specified in the message stops.
ANR4966E ANR4972I
User response: To increase the amount of database operating system conversion tool or missing code page
space available to the server, an authorized conversion tool might cause this problem. The server
administrator can add database volumes using the will attempt to recover from the situation. However, the
DEFINE DBVOLUME command and can extend the recovery might result in unreadable characters or no
size of the database using the EXTEND DB command. output to appear on the web interface or interfaces that
use the administrative API. Consult the language
support information of the operating system for
ANR4966E operation is ended for storage pool storage
information on how to install UTF-8 code page,
pool name; sufficient recovery log space
conversion tool support, and ICONV support.
is not available.
System action: The server operation continues without
Explanation: Insufficient server recovery log space has
converting the command output from the server's code
been encountered during the indicated operation for
page to UTF-8.
the indicated storage pool.
User response: Install the UTF-8 code page support on
System action: Either the Migration or Reclamation
the operating system. This is normally available by
stops, or the operation specified in the message stops.
installing the UTF-8 locale for your language.
User response: To increase the amount of recovery log
administrator can add log volumes using the DEFINE
reclamation retention date for WORM
LOGVOLUME command and can extend the size of the
FILE volume volume name; run AUDIT
log volumes using the EXTEND LOG command.
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
Explanation: During space reclamation, the server FIX=YES command for the indicated volume. During
detected the retention of the indicated WORM FILE AUDIT VOLUME processing, the server will indeed
volume has expired but the volume still contains valid have interface to the Network Appliance filer to obtain
data. The data on the volume will not be protected. the retention date of the SnapLock Log Volume for
correction of the missing or incorrect date.
System action: Reclamation continues.
User response: Examine the server activity logs to
find out why the reclamation does not move the valid User response: Issue the AUDIT VOLUME command
data to another WORM FILE volume for protection. with FIX=YES, so that the reclamation retention date
can be created or corrected.
ANR4968W Reclamation failed on WORM FILE

volume volume name. ANR4971E Audit command: Missing or incorrect
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
User response: Examine the server activity logs to has been specified for the audit command, the date will
find out why the reclamation does not move the valid be created or corrected.
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 User response: None.
volume.
ANR4972I Command: Migration is not needed for
ANR4969W Conversion from the server code page to the storage pool pool name.
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

ANR4973I ANR4980I
v If the specified storage pool uses random-access disk

ANR4976W The device class DevClassName is not the
or sequential-access disk, the data capacity utilization
same as device class DevClassName
is less than the low migration threshold.
defined for the serverbackup node
v If the specified storage pool uses tape or optical $$_TSMDBMGR_$$.
media, the ratio of volumes that contain data to the
total number of volumes in the storage pool is less Explanation: The device class in this command is not
than the low migration threshold. the same as the device class defined in the server
backup node.
command. System action: The server will still process the
command.
User response: Re-issue the command when migration
is needed for the pool. User response:
ANR4973I Command: Reclamation is not allowed ANR4977W The filespace filespace name (filespace id)
for the storage pool pool name. for node node name will not be included
in the backupset because it was not
Explanation: The high reclamation threshold created by the backup/archive client and
(percentage) is set to 100 to prevent reclamation for the cannot be restored from the backupset.
specified storage pool.
System action: The server does not process the included in the backupset because the filespace was not
command. created by the backup/archive client and it cannot be
User response: Re-issue the command when migration restored from the backupset.
is needed for the pool. System action: The filespace is skipped.
ANR4974W The writing of a table of contents for
was cancelled. ANR4978W The filespace filespace name (filespace id)
for node node name will not be included
Explanation: The server ends a table of contents in the backupset because it is not a
(TOC) creation for the specified node because the supported application type.
process was cancelled.
System action: The TOC creation is ended and server included in the backupset because the filespace does
operation continues. not belong to a supported application type.
User response: None. System action: The filespace is skipped.
ANR4975E No Tcp port available for backup from
NAS node to server.
ANR4979W Use of environment variable
Explanation: The server was unable to set up a DSMSERV_DIR is no longer supported.
TCP/IP port for use in backing up or restoring from or
to NAS nodes and the server. The server uses a range Explanation: The DSMSERV_DIR environment
of ports as defined by the NDMPPORTRANGE option. variable was required in prior versions of TSM to find
If none of these ports can be set up for use, backups or loadable modules and language files. Now, however,
restores from or to NAS nodes and server native the directory is determined automatically and this
storage pools will fail. If the NDMPPORTRANGE variable is ignored.
option is not specified, the server uses ephemeral ports System action: Server operation continues, using the
( ports that the operating system assigns from a directory containing the server executable as the base
dynamic pool ). If the system runs out of usable ports, server directory.
operations to or from NAS nodes and server native
storage pools will fail. User response: None.
System action: The specific operation is ended and

server operation continues. ANR4980I Auditing Interface Driver definitions.
User response: Operating specific utilities, e.g. netstat, Explanation: The server is beginning an audit of the
may be used to examine ports which are in use. It may definitions for Web interface.
be necessary to specify the NDMPPORTRANGE option System action: The server will audit all definitions for
( which requires a server restart ), to provide a the Web interface and report any problems.
sufficient number of ports.
ANR4981E ANR4991I

ANR4986I Auditing Interface Driver Classes.
Explanation: The server is auditing the driver classes.
ANR4981E Interface Driver audit completed -
Inconsistencies were found. System action: The server will audit the driver classes
and proceed to the next step.
Explanation: The server found errors during the audit
of the definitions for Web interface. User response: None.
System action: The Web Interface is not correctly
installed. The Web Admin will not work correctly, but ANR4987E Audit processing failed: sufficient
the server may be run without any problems. memory is not available for processing.
User response: Ensure you are using the correct IDL Explanation: At RUNFILE time, the server is unable
file for the server level you are running. Examine error to process the IDL data due to insufficient memory.
messages that may have been displayed before and/or
System action: Server runfile stops.
after this message and correct any problems, if possible.
If the cause of this can not be determined or resolved, User response: Restart the server runfile process with
contact your support representative. more memory available.
ANR4982I Interface Driver audit completed - ANR4988I Auditing Interface Driver Complex
definitions are consistent. Class containers.
Explanation: The server successfully completed the Explanation: The server is auditing the driver class
installation of the definitions for the Web interface. containers.
System action: The Web Interface is now installed. System action: The server will audit the driver class
The server may be run without any problems. containers and proceed to the next step.
ANR4983I Auditing Interface Driver Groups. ANR4989I Auditing Interface Driver Operations.
Explanation: The server is auditing the driver groups. Explanation: The server is auditing the driver
operations.
System action: The server will audit the driver groups
and proceed to the next step. System action: The server will audit the driver
operations and proceed to the next step.
ANR4984E Error description
ANR4990I Auditing Interface Driver Operation
Explanation: The server found errors during the audit
Parameters.
of the definitions for Web interface.
Explanation: The server is auditing the driver
System action: The audit will fail.
operation parameters.
User response: Ensure you are using the correct IDL
System action: The server will audit the driver
file for the server level you are running. Examine error
operation parameters and proceed to the next step.
messages that may have been displayed before this
message and correct any problems, if possible. If the User response: None.
cause of this can not be determined or resolved, contact
your support representative. If you contact your
support representative, the entire text of this message ANR4991I Auditing Interface Driver Tasks.
should be reported. Explanation: The server is auditing the driver tasks.
System action: The server will audit the driver tasks
ANR4985I Auditing Interface Driver Group and proceed to the next step.
Members.
Explanation: The server is auditing the driver group
members.
System action: The server will audit the driver group
members and proceed to the next step.

ANR4992I ANR6205I
ANR4992I Auditing Interface Driver Task ANR6202I Command name: Verifying candidates
Members. from last audit.
Explanation: The server is auditing the driver task Explanation: A compression audit has started to verify
members. the client file candidates that were identified in a
previous compression audit execution. The verification
System action: The server will audit the driver task
process eliminates compression candidates that are now
members and proceed to the next step.
found to be expired by policy on the server.
System action: The audit operation continues.
ANR4993E The client platform platform name is
currently not supported by the TSM
Storage Agent. ANR6203I Command name: Starting level audit level
compression audit from qualifying
Explanation: At this point in time the storage agent
entries in the candidates list.
does not accept the incomming client platform.
Explanation: A compression audit is starting to check
qualifying candidates from the candidates list for the
User response: None. audit level specified. Client files that were identified as
compression candidates at a lower level will be tested,
subject to the qualifications that were specified for the
ANR4994E Query whether the volume volume name command.
is in the library library name failed.
System action: The audit operation continues.
Explanation: An attempt to query if the indicated
volume is in the specified library failed. It could be the User response: The compression candidate list can be
library is offline or the library manager is down in a displayed with the QUERY COMPRESSION command.
library sharing environment. The QUERY PROCESS command can be used to
monitor the progress of the audit operation.
System action: The requested operation failed.
User response: Re-attempt the request when the ANR6204I Command name: Process process ID, level
library is brought up or when the library manager is audit level audit, ended successfully -
up and running in a library sharing environment. compression suspects = total number of
compression suspects.
ANR6200I Command name: Level compression audit Explanation: A compression audit ended and is
level compression audit started as reporting the total number of suspect client files that
process process ID. have been found.
Explanation: A compression audit at the specified System action: The audit operation completes.
level has been started as a background server process
with the process identifier reported. User response: The compression candidate list can be
displayed with the QUERY COMPRESSION command.
background audit attempts to identify client files that
may be affected by the client compression problem. ANR6205I Command name: Process process ID,
continuing Level 1 compression audit
User response: None. with object object ID high order
number.object ID low order number.
ANR6201I Command name: Level compression audit Explanation: A level 1 compression audit is starting to
level compression audit starting as evaluate client files for signs that they may be affected
background process process ID. by the client compression problem. Since a previous
Explanation: A compression audit at the specified level 1 audit has been executed, this audit will continue
level was started as a background server process where the last audit stopped starting with the object
having the process identifier reported. whose identifier is specified.
System action: Server operation continues. The System action: The audit operation continues.
background audit attempts to identify client files that User response: The compression candidate list can be
may be affected by the client compression problem. displayed with the QUERY COMPRESSION command.
User response: None. The QUERY PROCESS command can be used to
ANR6206I ANR6212I
System action: The audit operation ends.

ANR6206I Command name: Process process ID,
starting base level 1 compression audit. User response: The compression candidate list can be
Explanation: A level 1 compression audit is starting to
evaluate client files for signs that they may be affected
by the client compression problem. The audit starts ANR6210I Command name: Process process ID, level
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
were found.
System action: The audit operation continues
Explanation: A compression audit operation
User response: The compression candidate list can be
completed successfully. The number of candidate files
that have been found are displayed.
The QUERY PROCESS command can be used to
monitor the progress of the audit operation. System action: The audit operation ends.
ANR6207I Command name: Process process ID, level displayed with the QUERY COMPRESSION command.
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
System action: The audit operation continues. VERBOSE=YES parameter specified.
User response: The compression candidate list can be System action: The audit operation continues.
The QUERY PROCESS command can be used to User response: The compression candidate list can be
monitor the progress of the audit operation. displayed with the QUERY COMPRESSION command.
The QUERY PROCESS command can be used to
ANR6208I Command name: Process process ID, was
cancelled - number of candidate files
candidate files were found in number of ANR6212I Command name: Process process ID, level
files examined files examined prior to audit level analysis eliminated level
cancellation. candidate level candidate file object name
in filespace client filespace name for node
Explanation: A compression audit operation was client node name from candidate status.
canceled with the CANCEL PROCESS command before
completion. The number of candidate files that were Explanation: A compression audit at the level
found prior to the cancellation are displayed. specified has eliminated a candidate file through
further analysis. The name of the client node, file space,
System action: The audit operation ends. and file are displayed. This message is issued whenever
a candidate file is eliminated from consideration during
User response: The compression audit may be
a compression audit that was started with the
restarted with the AUDIT COMPRESSION command.
VERBOSE=YES parameter specified.
The compression candidate list can be displayed with
the QUERY COMPRESSION command. System action: The audit operation continues.
ANR6209I Command name: Process process ID, level displayed with the QUERY COMPRESSION command.
audit level audit completed successfully - The QUERY PROCESS command can be used to
number of candidate files candidate files monitor the progress of the audit operation.
were found in number of files examined
files examined.
Explanation: A compression audit operation
completed successfully. The number of candidate files
that were found are displayed.

ANR6213I ANR6224I
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
candidates at level audit level, number of ANR6220I Delete compression operation started as
files eliminated files were eliminated as process process ID.
candidates, and number of files expired
candidates were eliminated because they Explanation: A compression deletion operation was
were found to be expired on the server. started as a background server process with the
indicated identifier.
Explanation: A compression audit operation was
cancelled with the CANCEL PROCESS command System action: Server operation continues.
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
found to be expired before the cancellation are ANR6221I Force backup operation started as
reported. process process ID.
System action: The audit operation ends. Explanation: A force backup operation was started as
a background server process with the indicated
User response: The compression audit can be restarted identifier.
with the AUDIT COMPRESSION command. The
compression candidate list can be displayed with the System action: Server operation continues.
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
of files eliminated files were eliminated as Explanation: The indicated process was cancelled
candidates, and number of files expired prior to completion. This message displays the
candidates were eliminated because they indicated number of files that were processed before
were found to be expired on the server. the operation was cancelled.
Explanation: A compression audit operation System action: The process ends.

completed successfully. The number of candidate files User response: The operation may be restarted by
that were promoted as candidates at this level of audit, reissuing the indicated command.
found to be expired are reported.
ANR6223I Delete compression process process ID
System action: The audit operation ends. has completed - number of files files were
User response: The compression candidate list can be deleted.
displayed with the QUERY COMPRESSION command. Explanation: The indicated process has completed
processing. All database references have been deleted
ANR6215I Command name: Backup for file high-level for the indicated number of files.
object name low-level object name in System action: The process ends.
filespace client filespace name for node
client node name could not be forced. User response: None.
Explanation: It is not possible to force a backup for
the specified file using the FORCE BACKUP command. ANR6224I Force backup process process ID has
This file was either backed up using an API client or by completed - number of files files were
an ADSM version 2 client or higher. marked for forced backup.
System action: The force backup operation continues, Explanation: The indicated process has completed
the state of the compression record for this file is processing. The indicated number of files have been
updated. marked for forced backup. These files will be backed
up during the next incremental backup.
User response: If the file was backed up using a
Version 2 client, or higher, you may remove this entry System action: The process ends.
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.
ANR6225I ANR6303E

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
concerning files with possible compression errors. Explanation: A compression testing routine cannot
Other database information concerning the file is not continue because sufficient memory is not available on
affected. the server.
System action: Server operation continues. System action: The operation fails.
User response: None. 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
Explanation: A compression cleanup operation has memory may also be made available by limiting server
been started to remove compression candidate activity (sessions, migration, and other activities) while
information and temporary database entries from the this operation is processing.
server database. Client files are not affected by this
operation.
ANR6301E Command name: Invalid LEVEL specified.
System action: Server operation continues. This command only supports a value of
1 or 2 for the LEVEL parameter.
User response: The CANCEL PROCESS command can
be used to cancel the compression cleanup operation. Explanation: An invalid LEVEL= parameter has been
The QUERY PROCESS command may be used to query specified for the command.
the status of the operation.
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
User response: The CANCEL PROCESS command can were found prior to the failure are displayed.
be used to cancel the compression cleanup operation.
The QUERY PROCESS command may be used to query
the status of the operation. User response: Examine message that appear before
this message on the server console or in the activity log
to determine the source of the failure. If the error can
ANR6228W Cleanup process name: Process process ID
be corrected, re-execute the compression audit. If the
has been cancelled - cleanup processing
failure cannot be determined or corrected, contact your
is incomplete.
service representative. The compression candidate list
Explanation: A compression cleanup operation has can be displayed with the QUERY COMPRESSION
been cancelled prior to successful completion. command.
ANR6303E Command name: Process process ID, failed
User response: The CLEANUP COMPRESSION
- number of files promoted candidate files
command can be used to restart the cleanup operation.
were promoted as candidates at level
audit level, number of files eliminated files
ANR6229I Cleanup process name: Process process ID were eliminated as candidates, and
completed successfully. number of files expired candidates were
eliminated because they were found to
Explanation: A compression cleanup operation has be expired on the server.
successfully completed.
Explanation: A compression audit operation failed
System action: The cleanup process ends. before completion. The number of candidate files that

ANR6304E ANR6604E
were promoted as candidates at this level of audit,

ANR6600E Command: Invalid machine name -
machine name.
found to be expired before the audit failure are
reported. Explanation: The machine name specified in the
command is invalid.
User response: Examine message that appear before
command.
this message on the server console or in the activity log
to determine the source of the failure. If the error can User response: Issue the command again and specify
be corrected, re-execute the compression audit. If the a valid machine name.
failure cannot be determined or corrected, contact your
service representative. The compression candidate list
ANR6601E Command: Description information
can be displayed with the QUERY COMPRESSION
exceeds maximum length characters.
command.
Explanation: The description specified in the
command exceeds the maximum length of allowable
ANR6304E Command name: Command cannot be
characters.
processed until compression audit is
performed. System action: The server does not process the
command.
Explanation: The indicated command cannot be
processed until a compression audit is performed using User response: Issue the command again and specify
the AUDIT COMPRESSION command. a valid description.
ANR6602E Command: Recovery instructions file
User response: Issue the AUDIT COMPRESSION
name exceeds maximum length characters.
command and then repeat the attempted operation.
Explanation: The recovery instructions file name
specified in the command exceeds the maximum length
ANR6305E Command name: File identifier is not a
of allowable characters.
suspect for compression errors.
Explanation: The file with the specified identifier is
command.
not listed in the database as a suspect for compression
errors. The file cannot be removed from the suspect list. User response: Issue the command again and specify
a valid recovery instructions file name.
User response: Use the QUERY COMPRESSION
ANR6603E Command: Characteristics file name
command to obtain the correct identifier for the file to
be removed.
Explanation: The characteristics file name specified in
the command exceeds the maximum length of
ANR6306E Cleanup process name: Process process ID
allowable characters.
failed due to server error - cleanup
processing is incomplete. System action: The server does not process the
command.
Explanation: A compression cleanup operation has
failed before successful completion. User response: Issue the command again and specify
a valid characteristics file name.
System action: The cleanup process ends.
User response: Examine messages that appear on the
ANR6604E Command: Invalid building identifier -
server console or in the server activity log prior to this
building.
message to determine the cause of the error. If the error
can be identified and corrected, restart the cleanup Explanation: The building identifier specified in the
operation with the CLEANUP COMPRESSION command is invalid.
command. If the error cannot be corrected, contact your
service representative. System action: The server does not process the
command.
a valid building identifier.
ANR6605E ANR6616E

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
System action: The server does not process the maximum length characters.
command.
Explanation: The location specified in the command
User response: Issue the command again and specify exceeds the maximum length of allowable characters.
a valid floor identifier.
command.
ANR6606E Command: Invalid room identifier - room.
Explanation: The room identifier specified in the a valid location.
command is invalid.
System action: The server does not process the ANR6612I Machine machine name updated.
command.
Explanation: An UPDATE MACHINE command has
User response: Issue the command again and specify updated one or more attributes of a machine.
a valid room identifier.
ANR6607E Command: Machine machine name is
already defined.
ANR6613I Machine machine name deleted.
Explanation: The machine specified in the command
is already defined to the server. Explanation: A DELETE MACHINE command has
deleted the requested machine from the server.
User response: Issue the command again and specify User response: None.
another machine.
ANR6614E Command: Machine machine name is not
ANR6608E Command: A machine containing a server defined.
is already defined.
Explanation: The ADSMSERVER=YES parameter is not defined to the server.
specified in the command is invalid because another
machine has already been defined with this parameter. System action: The server does not process the
Only one machine can be defined to the server as command.
containing a server. User response: Issue the command again and specify
System action: The server does not process the a valid machine.
command.
User response: Issue the command again and do not ANR6615E Command: Failed to open input file - file
specify ADSMSERVER=YES as a parameter. name.
Explanation: The input file specified in the command
ANR6609I Machine machine name defined. cannot be opened by the server.
Explanation: A DEFINE MACHINE command has System action: The server does not process the
added the requested machine to the server. command.
System action: None. User response: Issue the command again and specify
an input file that is in a file system accessible by the
User response: None. server.
ANR6610E Command: Invalid recovery media name - ANR6616E Command: Invalid sequence number -
recovery media name. sequence number.
Explanation: The recovery media name specified in Explanation: The sequence number specified in the
the command is invalid. command is invalid.
command. command.

ANR6617W ANR6626E

ANR6622E Command: Recovery media recovery media
a valid sequence number.
name is not defined.
Explanation: The recovery media specified in the
ANR6617W Command: Node node name cannot be
command is not defined to the server.
processed because it is not registered.
Explanation: The node indicated in the message
command.
cannot be processed because it is not registered.
System action: The indicated node is not processed,
a valid recovery media.
but another node can be processed if specified by this
command.
ANR6623W Command: Machine machine name cannot
be processed because it is not defined.
a valid registered node.
Explanation: The machine indicated in the message is
not defined to the server.
ANR6618E Command: No matching node registered.
System action: The indicated machine is not
Explanation: The node specified in the command does
processed, but another machine can be processed if
not match any node registered to the server.
specified by this command.
command.
a valid machine.
a valid node.
ANR6624E Command: No matching machine
defined.
ANR6619I Node node name associated with machine
machine name.
does not match any machine defined to the server.
Explanation: A DEFINE MACHNODEASSOCIATION
command has associated the specified node with the
command.
specified machine. The node node name is associated
with the machine machine name. User response: Issue the command again and specify
a valid machine.
ANR6625I Machine machine name associated with
recovery media recovery media name.
ANR6620E Command: Machine and node association
Explanation: A DEFINE
is already defined.
RECOVERYMEDIAMACHASSOCIATION command
Explanation: The machine and node association has associated the specified machine with the specified
specified in the command is already defined to the recovery media. The machine machine name is
server. associated with the recovery media recovery media name.
System action: The server operation continues, but the System action: None.
a valid node.
ANR6626E Command: Recovery media/machine
association is already defined.
Explanation: The recovery media/machine association
machine machine name.
specified in the command is already defined to the
Explanation: A DELETE MACHNODEASSOCIATION server.
command has deleted the requested association from
System action: The server operation continues, but the
the server. The node node name is not associated with
the machine machine name.
a valid machine.
ANR6627I ANR6637E
ANR6627I Machine machine name disassociated ANR6632I Recovery media recovery media name
from recovery media recovery media name. defined.
Explanation: A DELETE Explanation: A DEFINE RECOVERYMEDIA command
RECOVERYMEDIAMACHASSOCIATION command has defined the recovery media to the server.
has deleted the requested association from the server.
Machine machine name is not associated with the
recovery media recovery media name. User response: None.
ANR6633I Recovery media recovery media name
updated.
Explanation: An UPDATE RECOVERYMEDIA
ANR6628E Command: Volume list exceeds maximum
command has updated one or more attributes of the
length characters.
recovery media.
Explanation: The volume list specified in the
characters. User response: None.
command. ANR6634I Recovery media recovery media name
deleted.
a valid volume list. Explanation: A DELETE RECOVERYMEDIA
command has deleted the requested recovery media
from the server.
ANR6629E Command: Product name exceeds
maximum length characters. System action: None.
Explanation: The product name specified in the User response: None.
characters.
ANR6635E Command: Recovery media recovery media
System action: The server does not process the name is already defined.
command.
Explanation: The recovery media specified in the
User response: Issue the command again and specify command is already defined to the server.
a valid product name.
command.
ANR6630E Command: Product information exceeds
maximum length characters. User response: Issue the command again and specify
a different recovery media.
Explanation: The product information specified in the
characters. ANR6636E Command: The characteristics specified
for machine machine name exceeds
System action: The server does not process the maximum length characters.
command.
Explanation: The characteristics specified in the
User response: Issue the command again and specify command exceeds the maximum length of allowable
valid product information. characters.
ANR6631E Command: Missing volume list for boot command.
recovery media.
Explanation: Boot recovery media cannot be defined valid characteristics.
to the server without specifying a volume list.
System action: The server does not process the ANR6637E Command: The recovery instructions
command. specified for machine machine name
the volume list for the boot recovery media. Explanation: The recovery instructions specified in the
characters.

ANR6638E ANR6646I
System action: The server does not process the System action: Server operation continues, but the
command. command has no effect.
User response: Issue the command again and specify User response: Issue the command again and specify
valid recovery instructions. a valid machine and node pair.
ANR6638E Command: The characteristics for ANR6642E Command: No association found for
machine machine name are already recovery media and machine pair
defined. specified.
Explanation: The characteristics for the machine Explanation: No association found for the recovery
specified in the command are already defined to the media and machine pair specified in the command.
server.
System action: The server does not process the command has no effect.
command.
User response: If the specified machine is defined to a valid recovery media and machine pair.
the server, issue an UPDATE MACHINE command to
update the existing characteristics. If the machine is not
ANR6643E Command: Invalid parameter value -
defined to the server, run AUDIT DRM FIX to delete
parameter value.
the characteristics.
Explanation: The parameter issued in the command is
invalid.
ANR6639E Command: The recovery instructions for
machine machine name are already System action: The server does not process the
defined. command.
Explanation: The recovery instructions for the User response: Issue the command again and specify
machine specified in the command are already defined a valid parameter.
to the server.
System action: The server does not process the ANR6644E Command: A character string must be
command. specified.
User response: If the specified machine is defined to Explanation: The INSERT command is invalid. A
the server, issue an UPDATE MACHINE command to character string must be specified.
update the existing recovery instructions. If the
machine is not defined to the server, run AUDIT DRM System action: The server does not process the
FIX to delete the recovery instructions. command.
ANR6640E Command: Cannot delete volume list for a valid character string.
boot recovery media.
Explanation: A volume list cannot be deleted for boot ANR6645W Node node name has already been
recovery media. A volume list must exist for each boot associated with machine machine name.
recovery media defined to the server. Explanation: The node specified in the DEFINE
System action: The server does not process the MACHNODEASSOCIATION command is invalid. The
command. node is already associated with another machine shown
in the message. A node can only be associated with one
User response: To delete the volume list, issue an machine.
UPDATE RECOVERYMEDIA command and specify a
recovery media type of OTHER and VOLUMES="". To System action: The indicated node is not processed,
change the recovery media type to BOOT, issue an but another node can be processed if specified by the
UPDATE RECOVERYMEDIA command and specify the command.
volume list containing the boot recovery media and User response: Issue the command again and specify
TYPE=BOOT. a valid node name.
ANR6641E Command: No association found for ANR6646I Audit command: Auditing disaster
machine and node pair specified. recovery manager definitions.
Explanation: No association found for the machine Explanation: This message is displayed during a
and node pair specified in the command. database audit and indicates that the disaster recovery
ANR6647E ANR6655I
manager definitions are being examined by the

ANR6651I Audit command: Invalid priority value
encountered for machine machine name.
User response: None. invalid priority value for the machine indicated.
ANR6647E Audit command: DRM global attributes
are missing.
FIX=YES to correct the priority. Or, issue an UPDATE
Explanation: A database audit process finds that the MACHINE command and specify a new priority value.
global attributes used for server DRM activities are
missing.
ANR6652I Audit command: Invalid priority value
System action: Audit processing continues. encountered for machine machine name -
FIX=YES to recreate the DRM global attributes. Explanation: A database audit process encounters an
invalid machine priority value for the machine
indicated. Because FIX=YES has been specified, the
ANR6648I Audit command: DRM global attributes audit function sets the machine priority value to the
are missing - default values will be used default value.
to recreate the attributes.
global attributes used for server DRM activities are User response: To override the default value, issue an
missing. Because FIX=YES has been specified on the UPDATE MACHINE command to change the value
AUDIT command, default attribute values will be used after the audit command has completed.
to recreate the administrative global attributes.
System action: Audit processing continues. ANR6653I Audit command: Invalid building value
invalid building value for the machine indicated.
ANR6649E Audit command: DRM machine ID
assignments are incorrect. System action: Audit processing continues.
Explanation: A database audit process finds that the User response: Issue the command again and specify
global attributes machine ID used for server DRM FIX=YES to correct the building value. Or, issue an
activities are incorrect. UPDATE MACHINE command and specify a new
building value.
User response: Reissue the audit command with ANR6654I Audit command: Invalid building value
FIX=YES specified so that the DRM global attributes encountered for machine machine name -
can be corrected. the building value will be removed.
ANR6650I Audit command: DRM machine ID invalid building value for the machine indicated.
Assignments are incorrect - values will Because FIX=YES has been specified, the audit function
be corrected. removes the machine building value.
Explanation: A database audit process finds that the System action: Audit processing continues.
global attributes machine ID used for server DRM
activities are incorrect. Since FIX=YES has been User response: To set the building value to another
specified on the AUDIT command, the attribute value value, issue an UPDATE MACHINE command after the
will be corrected in the server database. audit command has completed.
ANR6655I Audit command: Invalid floor value
User response: None encountered for machine machine name.
invalid floor value for the machine indicated.

ANR6656I ANR6663I
FIX=YES to correct the floor value. Or, issue an

ANR6660I Audit command: Invalid server value
UPDATE MACHINE command and specify a new floor
encountered for machine machine name -
value.
ANR6656I Audit command: Invalid floor value
invalid server value for the machine indicated. Because
encountered for machine machine name -
FIX=YES has been specified, the audit function sets the
the floor value will be removed.
machine server value to the default value.
invalid floor value for the machine indicated. Because
FIX=YES has been specified, the audit function removes User response: To override the default value, issue an
the machine floor value. UPDATE MACHINE command to change the value
User response: To set the floor value to another value,
ANR6661I Audit command: Multiple machines are
issue an UPDATE MACHINE command after the audit
indicated as servers. Only one machine
command has completed.
should have the server indicator set to
YES.
ANR6657I Audit command: Invalid room value
more than one machine with the server indicator set to
Explanation: A database audit process encounters an YES.
invalid room value for the machine indicated.
User response: For a list of machines with the server
User response: Issue the command again and specify indicator set to YES, issue a QUERY MACHINE
FIX=YES to correct the room value. Or, issue an ADSMSERVER=YES command. Issue an UPDATE
UPDATE MACHINE command and specify a new MACHINE command for each machine that is not a
room value. server.
ANR6658I Audit command: Invalid room value ANR6662I Audit command: Characteristics for
encountered for machine machine name - machine machine name not found.
the room value will be removed.
Explanation: A database audit process encounters an characteristics reference from a machine for
invalid room value for the machine indicated. Because characteristics that are not in the server database.
FIX=YES has been specified, the audit function removes
the machine room value.
User response: Issue an UPDATE MACHINE
command to load the characteristics into the database
User response: To set the room value for the specified after the audit command has completed.
machine to another value, use the UPDATE MACHINE
command after the audit command has completed.
ANR6663I Audit command: Recovery instructions for
machine machine name not found.
ANR6659I Audit command: Invalid server value
recovery instructions reference from a machine for
Explanation: A database audit process encounters an recovery instructions that are not in the server
invalid server value for the machine indicated. database.
User response: Issue the command again and specify User response: Issue an UPDATE MACHINE
FIX=YES to correct the server value. Or, issue an command to load the recovery instructions into the
UPDATE MACHINE command and specify a new database after the audit command has completed.
server value.
ANR6664I ANR6672E
ANR6664I Audit command: Invalid access value ANR6668E Audit command: Machine is not found for
encountered for recovery media recovery internal machine ID machine ID, which
media name. is referenced by recovery media.
Explanation: A database audit process encounters an Explanation: A database audit process finds recovery
invalid access value for the recovery media indicated. media that references a machine that is not defined in
the server database.
FIX=YES to correct the access value. Or, issue an User response: Issue the command again and specify
UPDATE RECOVERYMEDIA command and specify a FIX=YES to correct recovery media attributes.
new access value.
ANR6669I Audit command: Machine is not found for
ANR6665I Audit command: Invalid access value internal machine ID machine ID, which
encountered for recovery media recovery is referenced by recovery media - the
media name - the default value will be machine reference will be deleted.
set.
Explanation: A database audit process finds recovery
Explanation: A database audit process encounters an media that references a machine that is not defined in
invalid access value for the recovery media indicated. the server database. Because FIX=YES has been
Because FIX=YES has been specified, the audit function specified for the audit command, the reference will be
sets the recovery media access value to the default removed from the server database.
value.
User response: To override the default value, issue an
UPDATE RECOVERYMEDIA command to change the
ANR6670E Audit command: Recovery media not
value after the audit command has completed.
found for internal recovery media ID
recovery media ID, which is referenced by
ANR6666I Audit command: Invalid type value a machine.
encountered for recovery media recovery
Explanation: A database audit process finds a machine
media name.
that references recovery media that is not defined in the
Explanation: A database audit process encounters an server database.
invalid type value for the recovery media indicated.
User response: Issue the command again and specify FIX=YES to correct the recovery media attributes.
FIX=YES to correct the type value. Or, issue an
UPDATE RECOVERYMEDIA command and specify a
ANR6671I Audit command: Recovery media not
new type value.
found for internal recovery media ID
recovery media ID, which is referenced by
ANR6667I Audit command: Invalid type value a machine - the recovery media
encountered for recovery media recovery reference will be deleted.
media name - the default value will be
Explanation: A database audit process finds m
set.
machine that references recovery media that is not
Explanation: A database audit process encounters an defined in the server database. Because FIX=YES has
invalid type value for the recovery media indicated. been specified for the audit command, the reference
Because FIX=YES has been specified, the audit function will be deleted from the server database.
sets the recovery media type value to the default value.
User response: To override the default value, issue an
UPDATE RECOVERYMEDIA command to change the
ANR6672E Audit command: Client node not found
for internal node ID node ID, which is
referenced by a machine.
Explanation: A database audit process finds a machine

ANR6673I ANR6681I
that references a client node that is not defined in the

ANR6677I Audit command: Machine not found for
server database.
internal machine ID machine ID, which
System action: Audit processing continues. is referenced by characteristics - the
machine reference will be deleted.
FIX=YES to correct the machine attributes. Explanation: A database audit process finds
characteristics that reference a machine that is not
defined in the server database. Because FIX=YES has
ANR6673I Audit command: Client node not found been specified for the audit command, the reference
for internal node ID node ID, which is will be removed from the server database.
referenced by a machine - the client
node reference will be deleted. System action: Audit processing continues.
Explanation: A database audit process finds a machine User response: None.

that references a client node that is not defined in the
ANR6678E Audit command: Machine not found for
for the audit command, the reference will be removed
from the server database.
is referenced by recovery instructions.
Explanation: A database audit process finds recovery
User response: None. instructions that reference a machine that is not defined
in the server database.
ANR6674E Audit command: Machine not found for System action: Audit processing continues.
is referenced by a client node.
FIX=YES to correct the machine attributes.
Explanation: A database audit process finds a client
node that references a machine that is not defined in
ANR6679I Audit command: Machine not found for
the server database.
System action: Audit processing continues. is referenced by recovery instructions -
the machine reference will be deleted.
FIX=YES to correct the machine attributes. Explanation: A database audit process finds recovery
instructions that reference a machine that is not defined
in the server database. Because FIX=YES has been
ANR6675I Audit command: Machine not found for specified for the audit command, the reference will be
internal machine ID machine ID, which removed from the server database.
is referenced by a client node - the
machine reference will be deleted. System action: Audit processing continues.
Explanation: A database audit process finds a client User response: None.

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

ANR6686E Command: Volume volume name in use.
Explanation: The MOVE DRMEDIA *
WHERESTATE=MOUNTABLE command displays the
ANR6682I Command command ended: number of message. Volume volume name is used for another
volumes volumes processed. operation.
Explanation: The indicated command ended. The total System action: The command is not processed if the
number of volumes successfully processed is shown in volume is explicitly specified on the command. If a
the message. volume pattern is specified on the command, the
indicated volume is not processed, but the other
System action: The indicated command ends. volumes are processed.
User response: None. User response: Wait until the conflicting volume
activity has completed, and then reissue the command.
ANR6683I Command: Volume volume name was If the volume is currently mounted, but idle, dismount
moved from from state state to to state. the volume by using a DISMOUNT VOLUME
command and then retry this operation.
Explanation: Volume volume name is successfully
moved from state1 to state2 by the indicated command.
ANR6687E Command: Executable command string
System action: The indicated volume is moved to the exceeds maximum length characters.
destination state.
Explanation: The length of the executable command
User response: None. string specified with the CMD parameter exceeds the
maximum length of allowable characters (255).
ANR6684I Command: Volume volume name was System action: The server stops processing the
deleted. command.
Explanation: The MOVE DRMEDIA * User response: Issue the command again and specify
WHERESTATE=COURIERRETRIEVE command a valid executable command with the CMD parameter.
displays the message. Volume volume name is deleted
from the server database. For database backup volume,
after its expiration days have elapsed, the volume ANR6688E command: The specified command failed
history record is deleted when it is returned onsite. For because the entry/exit port of library
an empty scratch copy storage pool volume, or library name is full. Please remove the
active-data storage pool volume, the volume record is volume(s) from the entry/exit port and
deleted when it is returned onsite. re-issue the command name command.
System action: The volume record is deleted from the Explanation: The indicated operation has failed
server database. because the entry/exit port of the specified library is
full.
User response: Issue the CHECKIN LIBVOLUME
command for each volume returned onsite if the System action: The command fails.
volume is reused by the server. User response: Remove the volume(s) from the
entry/exit port and re-issue the command to process
ANR6685E Command: Volume volume name not any remaining eligible volumes.
defined.
Explanation: Volume volume name is not defined to the ANR6690E Command: Copy storage pool cstgp name
server. not defined for Offsite Recovery Media.
System action: The indicated command is not Explanation: The MOVE DRMEDIA or QUERY
processed if the volume name is explicitly specified on DRMEDIA command displays the message. The
the command. If a volume pattern is specified on the indicated command was issued with a copy storage
command, the volume shown is not processed, but the pool name specified, but the specified pool name is not
other volumes are processed. defined to DRM for Offsite Recovery Media.
User response: Reissue the command specifying a System action: The indicated command is not
valid volume name. processed.
User response: Reissue the command, after defining
the specified copy storage pool to DRM for Offsite
Recovery Media.

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

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

value encountered. ANR6718I Audit command: Extraneous DRM global
attribute encountered - the attribute will
Explanation: A database audit process encounters an be deleted.
invalid check label value.
System action: Audit processing continues. nonexistent DRM global attribute. Since FIX=YES has
been specified, the extraneous attribute will be deleted.
FIX=YES to correct the check label value. Or, issue a System action: Audit processing continues.
SET DRMCHECKLABEL command and specify a new
check label value. User response: None.
ANR6719E ANR6728I
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.
Explanation: A database audit process finds no entries
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
ANR6727E Audit command: Postfix for DRM
in the server database for the recovery media ID
replacement volumes names not found.
assignments.
in server database for DRM postfix definitions for
User response: None. replacement volumes names.
ANR6723E Audit command: Prefix for DRM recovery
plan not found.
in server database for DRM recovery plan prefix
ANR6728I Audit command: Postfix for DRM
definitions.
replacement volumes names not found -
System action: Audit processing continues. entry will be created.
User response: Issue the audit command again and Explanation: A database audit process finds no entries
specify FIX=YES to correct the error. in server database for DRM postfix definitions for
replacement volumes names. Because FIX=YES has

ANR6729E ANR6736I
been specified for the audit command, the audit SET DRMCOPYSTGPOOL command to change the
function creates an entry using the default value in the value after the audit command has completed.
server database for the replacement volumes postfix.
System action: Audit processing continues. ANR6733E Command: Cannot complete initialization
for process name process.
SET DRMPLANVPOSTFIX command to change the Explanation: The indicated process fails during
value after the audit command has completed. process initialization.
System action: The indicated command is ended and
ANR6729E Audit command: Primary storage pools to server processing continues.
be restored by DRM not found.
User response: This usually indicates that sufficient
Explanation: A database audit process finds no entries server memory is not available on the server.
in server database for primary storage pools to be
restored by DRM.
User response: Issue the audit command again and ANR6734E Command: Volume volume name not
specify FIX=YES to correct the error. processed: library library name not
defined.
ANR6730I Audit command: Primary storage pools to Explanation: The indicated volume is not processed
be restored by DRM not found - entry since the designated library has not been defined or has
will be created. been deleted.
Explanation: A database audit process finds no entries 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.
the primary storage pools to be restored by DRM.
ANR6735E Audit command: Courier information for
ORM not found.
SET DRMPRIMSTGPOOL command to change the
in server database for courier name definitions used by
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. ANR6736I Audit command: Courier information for
ORM not found - entry will be created.
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
ANR6732I Audit command: Copy storage pools to be function creates an entry using the default value in the
managed by DRM not found - entry server database for the courier name definitions.
will be created.
in server database for copy storage pools to be
SET DRMCOURIERNAME command to change the
managed by DRM. Because FIX=YES has been specified
for the audit command, the audit function creates an
the copy storage pools to be managed by DRM.
ANR6737E ANR6745E
ANR6737E Audit command: Vault name for ORM not ANR6741E Audit command: Check label indicator for
found. ORM not found.
in server database for vault name definitions used by in server database for check label definitions used by
DRM Offsite Recovery Media (ORM). DRM Offsite Recovery Media (ORM).
User response: Issue the audit command again and User response: Issue the audit command again and
specify FIX=YES to correct the error. specify FIX=YES to correct the error.
ANR6738I Audit command: Vault name for ORM not ANR6742I Audit command: Check label indicator for
found - entry will be created. ORM not found - entry will be created.
in server database for vault name definitions used by in server database for check label definitions used by
DRM Offsite Recovery Media (ORM). Because FIX=YES DRM Offsite Recovery Media (ORM ). Because
has been specified for the audit command, the audit FIX=YES has been specified for the audit command, the
function creates an entry using the default value in the audit function creates an entry using the default value
server database for the vault name definitions. in the server database for the check label definitions.
User response: To override the default value, issue a User response: To override the default value, issue a
SET DRMVAULTNAME command to change the value SET DRMCHECKLABEL command to change the value
after the audit command has completed. after the audit command has completed.
ANR6739E Audit command: Database backup series ANR6743E Audit command: File process indicator for
expiration days for ORM not found. ORM not found.
in server database for database backup series expiration in server database for file process definitions used by
days definitions used by DRM Offsite Recovery Media DRM Offsite Recovery Media (ORM).
(ORM).
User response: Issue the audit command again and specify FIX=YES to correct the error.
ANR6744I Audit command: File process indicator for
ANR6740I Audit command: Database backup series ORM not found - entry will be created.
expiration days for ORM not found -
entry will be created.
in server database for file process definitions used by
Explanation: A database audit process finds no entries DRM Offsite Recovery Media (ORM). Because FIX=YES
in server database for database backup series expiration has been specified for the audit command, the audit
days definitions used by DRM Offsite Recovery Media function creates an entry using the default value in the
(ORM). Because FIX=YES has been specified for the server database for the file process definitions.
audit command, the audit function creates an entry
using the default value in the server database for the
database backup series expiration days definitions. User response: To override the default value, issue a
SET DRMFILEPROCESS command to change the value
SET DRMDBBACKUPEXPIREDAYS command to
ANR6745E Audit command: DRM recovery media ID
assignments are incorrect.
completed.
global attributes recovery media id used for server
DRM activities are incorrect.

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

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

ANR6763I ANR6772I

ANR6768E command: Prefix exceeds maximum
a valid destination state for the volume name shown.
characters characters.
Explanation: The prefix specified for recovery plan
ANR6763I Command: The specified command has
files or for plan instructions files exceeds the maximum
been written to file 'file name'.
valid length. The maximum valid length is shown in
Explanation: The command string specified with the the message.
CMD parameter on the command shown is written to
the indicated file for each volume successfully
command.
processed.
valid prefix.
User response: Execute the commands written to the
file.
ANR6769E Audit command: Not mountable name
information for ORM not found.
ANR6764E command: Command file name exceeds
in server database for not mountable location name
Explanation: The file name specified for containing definitions used by DRM Offsite Recovery Media
the executable commands generated by DRM exceeds (ORM).
the maximum valid length shown.
command.
valid file name.
ANR6770I Audit command: Not mountable name
information for ORM not found - entry
ANR6765E Command: Invalid not mountable will be created.
location name - not mountable name.
Explanation: The indicated command has been in server database for not mountable location name
entered with an invalid not mountable location name. definitions used by DRM Offsite Recovery Media
(ORM). Because FIX=YES has been specified for the
System action: The server does not process the audit command, the audit function creates an entry
command. using the default value in the server database for the
User response: Reissue the command with a valid not courier name definitions.
mountable location name. System action: Audit processing continues.
ANR6766E Command: No command string is SET DRMNOTMOUNTABLENAME command to
specified for FORMAT=CMD. change the value after the audit command has
Explanation: The indicated command has been completed.
entered with a FORMAT=CMD to write a command
string to a file, but no command string is specified. ANR6771E Audit command: Command file name
System action: The server does not process the information for ORM not found.
command. Explanation: A database audit process finds no entries
User response: Reissue the command specifying a in server database for command file name definitions
command string to be written to a file. used by DRM Offsite Recovery Media (ORM).
ANR6767E Command: Invalid command file name - User response: Issue the audit command again and
command file name. specify FIX=YES to correct the error.
entered with an invalid command file name. ANR6772I Audit command: Command file name
System action: The server does not process the information for ORM not found - entry
command. will be created.
User response: Reissue the command with a valid Explanation: A database audit process finds no entries
command file name. in server database for command file name definitions
ANR6773E ANR6779E
used by DRM Offsite Recovery Media (ORM). Because the true state of the volume. For MOVE DRMEDIA,
FIX=YES has been specified for the audit command, the rerun the command after determining the cause of the
audit function creates an entry using the default value error. For MOVE MEDIA, an update volume command
in the server database for the command file name should be issued setting the access of the volume to
definitions. read only.
System action: Audit processing continues. If this message is issued by a MOVE or QUERY
DRMEDIA command and the volume record has been
deleted from the server database, you can not use the
SET DRMCMDFILENAME command to change the
MOVE or QUERY DRMEDIA commands to create the
command file entry for this volume. In this case, you
must manually issue the proper command.
ANR6773E Command: Unable to open file 'command
file name' for output.
ANR6776E Command: Could not delete file: file name
Explanation: An error occurred while opening the
Explanation: The indicated command failed but the
command file name shown. The file name shown in the
file created could not be deleted.
message is specified with the indicated command, the
SET command, or the default name generated by the System action: None.
indicated command.
User response: Delete the file shown.
indicated command.
ANR6777E Command: Command file 'file name'
User response: Examine error messages that may have already in use.
command file name that is in use. The command file
proper authority to write to the file indicated. In AIX,
name shown is selected for use by the server in the
make sure that the file name specified in the command
following order:
or in the SET command is a full path file name, not a
directory path name. In MVS, make sure that the file v The file name specified on the indicated command.
name specified in the command or in the SET v The file name specified on the SET command.
command is a valid MVS file name. Reissue the v The file name generated by the server (AIX only).
command after determining the cause of the error.
command.
ANR6774E Command: Invalid volume transition
states - from 'specified WHERESTATE' User response: Reissue the command at a later time
state to 'specified TOSTATE' state. or reissue the command specifying a different
command file name.
Explanation: The TOSTATE specified is an invalid
destination state for the WHERESTATE specified.
ANR6778E Command: Volume volume name not
System action: The server does not process the processed: device type device type not
command. supported.
User response: Issue the command again and specify Explanation: The indicated volume is not processed
a valid destination state. because the device type shown is not supported by the
function.
ANR6775E Command: Error writing to file 'file name' System action: The indicated volume is not processed.
for volume volume name.
file name shown for the indicated volume.
ANR6779E Disaster recovery manager operation
System action: The server stops processing the command being processed is denied -
command. disaster recovery manager support is not
User response: Examine error messages that may have available for server platform.
been displayed prior to this message and correct any Explanation: The server refuses a disaster recovery
problems, if possible. Make sure that the server has manager operation because disaster recovery manager
proper authority to write to the file indicated. Reissue support is not available for the server platform.
the command after determining the cause of the error.
In the case where volumes are being ejected from the
library, it is possible the server database does not reflect User response: None.

ANR6780E ANR6902I
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
Explanation: A database audit process encounters an QUERY PROCESS command for a MOVE DRMEDIA
invalid value for recovery plan file expiration days. command.
System action: Audit processing continues. System action: Server operation continues.
User response: Issue the command again and specify User response: None.
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 Tivoli
ANR6781I Audit command: An invalid recovery plan Disaster Recovery Manager. The ADSM
file expiration days encountered - the V3 DRM Disk Image Restore function
default value will be set. has been stabilized with no new
maintenance or hardware support
planned.
invalid value for recovery plan file expiration days.
Because FIX=YES has been specified, the audit function Explanation: None.
sets the expiration days value to the default value.
System action: DRM Disk Image Dump and Restore
System action: Audit processing continues. function continues.
User response: To override the default value, issue a User response: None.
SET DRMRPFEXPIREDAYS command to change the
ANR6900I Command: The recovery plan file file
name was created.
ANR6782E Audit command: Recovery plan file
Explanation: The recovery plan file was created.
expiration days not found.
in server database for recovery plan file expiration days User response: None.
definitions.
System action: Audit processing continues. ANR6901I Number of plan stanzas processed:
number.
specify FIX=YES to correct the error. Explanation: The PREPARE command has processed
the number of stanzas displayed. This message may be
ANR6783I Audit command: Recovery plan file
for a PREPARE command.
expiration days not found - entry will
be created. System action: Server operation continues.
Explanation: A database audit process finds no entries User response: None.
in server database for recovery plan file expiration days
definitions. Because FIX=YES has been specified for the
audit command, the audit function creates an entry ANR6902I Number of plan stanzas processed:
using the default value in the server database for the number. Currently processing stanza:
recovery plan file expiration days definitions. recovery plan stanza name.
System action: Audit processing continues. Explanation: The PREPARE command displays the
number of stanzas already processed and the name of
User response: To override the default value, issue a the stanza currently being processed. This message may
SET DRMRPFEXPIREDAYS command to change the be displayed in response to a QUERY PROCESS
value after the audit command has completed. command for a PREPARE command.
volumes processed. Volumes sent to library User response: None.
library name for checkout: number volumes
sent.
processed the number of volumes shown. Currently, the
ANR6903I ANR6920W
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: Stanzas in the recovery plan do not
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.
ANR6913W Command: No volumes with backup data System action: The recovery plan will not contain
exist in copy storage pool storage pool recovery instructions.
name.
User response: To get recovery instructions in the
Explanation: A copy storage pool does not contain recovery plan, ensure the corresponding instructions
any volumes with usable data. source file exists. If it does, check authorizations to the
file.
include recovery information for any volumes in the
storage pool. ANR6920W Command: S volume name is not valid for
server device type device type. Original
User response: Determine why this storage pool has volume name: volume name. Stanza is
no volumes with usable data. stanza name.
Explanation: Appending the replacement volume
name postfix (as defined with SET
DRMPLANVPOSTFIX) to the original volume name

ANR6921W ANR6927W
has created a name that is not valid for the server

ANR6924W Command: No recovery instructions
device type shown.
defined for machine machine name.
System action: Replacement volume name is used in
Explanation: No recovery instructions have been
the recovery plan stanza.
defined to the server for the specified machine.
User response: Devise a naming convention that
System action: The recovery plan file does not contain
allows the use of the replacement volume name postfix
the machine recovery instructions stanza.
or at restore time manually update the generated
recovery plan with a legal replacement name. For User response: If you want to include the machine
additional information and related commands, refer to recovery instructions in the recovery plan file, issue the
the Administrator's Reference for your particular INSERT command. Reissue the PREPARE command
platform. after the appropriate commands have been issued to
define the recovery media. For additional information
and related commands, refer to the Administrator's
ANR6921W Command: Cannot locate server options
file 'file name'.
Explanation: The Prepare command cannot open the
ANR6925W Command: No machine characteristics
specified server options file.
defined for machine machine name.
System action: VOLHISTORY and DEVCONFIG
Explanation: No characteristics have been defined to
options are added to the recovery plan file stanza
the server for the specified machine.
DSMSERV.OPT.FILE.
the machine characteristics stanza.
User response: If you want to include the machine
ANR6922W Command: No machine information was
recovery instructions in the recovery plan file, issue the
defined for the machine that contains
INSERT command. Reissue the PREPARE command
server server name.
after the appropriate commands have been issued to
Explanation: The machine information has not been define the recovery media. For additional information
saved in the server data base. and related commands, refer to the Administrator's
the machine and recovery media information stanzas.
ANR6926W Command: There is at least one invalid
User response: If you want to include the machine generated volume name associated with
information in the recovery plan file, issue the DEFINE storage pool storage pool server device
MACHINE command to save the machine information type device type in stanza stanza name.
in the server data base and reissue the PREPARE
command. Explanation: Appending the replacement volume
name postfix (as defined with SET
DRMPLANVPOSTFIX) to the original volume name
ANR6923W Command: No recovery media defined has created a name that is not valid for the server
for machine machine name. device type shown.
Explanation: No recovery media has been defined to System action: Replacement volume name is used in
the server for the specified machine. the recovery plan stanza.
System action: The recovery plan file does not contain User response: Devise a naming convention that
the machine recovery media stanza. allows the use of the replacement volume name postfix
User response: If you want to include the machine or at restore time manually update the generated
recovery media information in the recovery plan file, recovery plan with a legal replacement name. For
issue the DEFINE RECOVERYMEDIA command. additional information and related commands, refer to
Reissue the PREPARE command after the appropriate the Administrator's Reference for your particular
commands have been issued to define the recovery platform.
media. For additional information and related
commands, refer to the Administrator's Reference for ANR6927W Command: Primary storage pool storage
your particular platform. pool name, storage pool data format, is not
managed by DRM.
Explanation: A SET DRMPRIMSTGPOOL or the
PREPARE command specified a primary storage pool
that is used for backing up NAS file servers, using
ANR6928W ANR6942E
NDMP. DRM does not manage a storage pool with this System action: The server does not process the
data format. command.
System action: Stanzas in the recovery plan do not User response: Reissue the command with the
include recovery information for the storage pool. parameter from the web.
User response: Correct the storage pool specification.
ANR6938I No information found for stanza stanza
name.
ANR6928W Command: No eligible primary storage
pools match the specified storage pool Explanation: No information found for recovery plan
name storage pool name . file stanza shown.
Explanation: The storage pool specified by the SET System action: The server does not display the
DRMPRIMSTGPOOL or on PREPARE command does information for the stanza.
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
classes use the CENTERA device type. Explanation: The specified recovery plan file stanza
v The name specified does not match eligible primary name is invalid.
storage pool names. System action: The server does not process the
System action: Stanzas in the recovery plan do not command.
include recovery information for the storage pools. User response: Issue the command again and specify
User response: Correct the storage pool specification a valid recovery plan file stanza name.
or define eligible storage pools to the server.
ANR6940E command command not allowed from
ANR6929W Command: No eligible primary storage server console.
pools are defined to the server. Explanation: The indicated command is not allowed
Explanation: The server has no eligible primary to be issued from the server console.
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
ANR6930W Command: Primary storage pool storage device class name.
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.
DRM does not manage storage pools that use the User response: Respond to any mount requests.
CENTERA device type.
System action: Stanzas in the recovery plan do not ANR6942E Query recovery plan file content is
include recovery information for the storage pool. waiting for access to input volume
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.

ANR6943E ANR6951E
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. You can also refer to the
User response: Respond to any mount requests. Problem Determination Guide for problem determination
continues to fail contact your service representative.
ANR6944E Command: Invalid recovery plan file
name - recovery plan file name.
ANR6948E Command: Cannot find the recovery plan
Explanation: The recovery plan file name specified in
file for Recovery plan file name.
the command is invalid.
Explanation: The server cannot find the specified
recovery plan file.
command.
command.
a valid recovery plan file name.
a valid recovery plan file name. Use the QUERY
ANR6945E Command: Cannot find filespace filespace
RPFILE command to view the name of the recovery
name for recovery plan file recovery plan
plan file that you are interested in displaying its
file name.
content.
Explanation: The server cannot find the filespace
(ADSM.SERVER) for recovery plan file specified in the
ANR6949E Command: No matching device class
server.
defined.
System action: The retrieve operation ends, and the
Explanation: The device class specified in the
command does not match any device class defined to
User response: Issue QUERY FILESPACE command the server.
on the target server to see if there is any filespaces
created for the recovery plan file. The filespace name
command.
for the recovery plan file is ADSM.SERVER.
a valid device class.
ANR6946E Command: Retrieve failed for recovery
plan file name - error on input storage
device. ANR6950E Command: The recovery plan file was not
created.
Explanation: The server ends an retrieve operation
because an I/O error has been encountered by the Explanation: Due to a processing error, a recovery
server in reading from a device. plan file was not created.
System action: The retrieve operation ends, and the System action: Recovery plan file not created.
User response: Query the activity log to find messages been displayed prior to this message and correct any
preceding this one that specify the device that is failing. problems, if possible. Reissue the command, after
The server may need to be shut down with the HALT determining the cause of the error.
command to correct the hardware problem.
ANR6951E Command: Recovery plan file file name
ANR6947E Command: Data storage retrieve failed was not created.
for recovery plan file name - error detected.
Explanation: Due to a processing error, a recovery
Explanation: The server ends the retrieve operation plan file was not created.
because an error has been encountered on the server.
System action: Recovery plan file not created.
Some common reasons for the error are:
v Data is corrupted on the input volume User response: Examine error messages that may have
v Hardware or media failure has occurred
ANR6952E ANR6966E

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

ANR6967E ANR6976E
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.
Explanation: An server database query error occurred.
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
determining the cause of the error.
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.
System action: The command process ends and 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.
ANR6977E ANR7800I (AIX)

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
the process encounters an out-of-space condition
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: 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.
ANR7800I (AIX) DSMSERV generated at time on date.

ANR6980E Command: Prefix prefix exceeds maximum
characters characters. Explanation: The server module was generated at the
indicated date and time.
Explanation: The command shown has been entered
and specifies a plan or instructions prefix that is too System action: Server operation continues.
long. The maximum valid length is shown in the User response: None.
message.
command.
shorter prefix.

ANR7800I (HP-UX) ANR7804E (AIX)

ANR7800I (HP-UX) DSMSERV generated at time on
date. User response: None.
Explanation: The server module was generated at the
indicated date and time. 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. User response: None.
indicated date and time. ANR7802E (AIX) Shared memory segments for a
server running in the current directory
already exist. The -F parameter can be
User response: None. used to overwrite.
Explanation: Shared memory segments are created for
ANR7800I (Solaris) DSMSERV generated at time on each instance of the server based on the current
date. directory. This message indicates that the shared
memory segments already exist. A server is presently
running from the current directory or a server running
indicated date and time.
from the current directory ended abnormally.
System action: The server terminates.
User response: If the server running in the current
directory terminated abnormally, start dsmserv with the
ANR7800I (Windows) DSMSERV generated at time -F parameter to force the existing shared memory
on date. segments to be overwritten. If you want to run
multiple instances of the server, each instance must be
Explanation: The server module was generated at the run from a separate directory with a separate
indicated date and time. dsmserv.dsk file and have separate log, database, and
System action: Server operation continues. storage volumes.

ANR7803E (AIX) Attempt to overwrite a shared
memory segment, as directed with the -F
ANR7801I (AIX) Subsystem process ID is process parameter, FAILED.
identifier.
Explanation: The server has been started with the -F
Explanation: The server process has the indicated parameter and unsuccessfully attempted to overwrite
process identifier. existing shared memory segments. This error occurs
System action: Server operation continues. when the user that starts the server with -F parameter
is not the owner of the shared memory segments and
User response: None. lacks the required authority.
System action: Server terminates.
ANR7801I (HP-UX) Subsystem (master) process ID is
process identifier. User response: Resolve the authorization problem and
restart the server.
Explanation: The server's master HP-UX process has
the indicated process identifier.
ANR7804E (AIX) Error reason.
Explanation: The server attempted to open,lock, or
User response: None. write to the specified file The open, lock, or write
operation failed. These are some common reasons for
ANR7801I (Linux) Subsystem process ID is process the failure. Another server is already running from this
identifier. directory and has the file open or locked. The instance
user ID does not have enough write access to the file.
Explanation: The server process has the indicated The file system is full.
process identifier.
ANR7804E (HP-UX) ANR7805E (AIX)
User response: Examine the contents of the lock file.

ANR7804E (Solaris) Error reason.
The process ID for the server that is running is
recorded in this file. Two servers cannot be started from Explanation: The server attempted to open,lock, or
the same directory. You can remove the lock file and write to the specified file The open, lock, or write
attempt to start the server only if the recorded process operation failed. These are some common reasons for
ID is not currently running dsmserv. The 'ps -e' AIX the failure. Another server is already running from this
command can be used to display processes that are directory and has the file open or locked. The instance
currently running. Check the permissions of the user ID does not have enough write access to the file.
directory and file system and ensure that there is The file system is full.
appropriate permission for the instance user ID to write
to the file. Check that there is enough space in the file
system. User response: Examine the contents of the lock file.
recorded in this file. Two servers cannot be started from
ANR7804E (HP-UX) Error reason.
the same directory. You can remove the lock file and
Explanation: The server attempted to open,lock, or attempt to start the server only if the recorded process
write to the specified file The open, lock, or write ID is not currently running dsmserv. The 'ps -e'
operation failed. These are some common reasons for command can be used to display processes that are
the failure. Another server is already running from this currently running. Check the permissions of the
directory and has the file open or locked. The instance directory and file system and ensure that there is
user ID does not have enough write access to the file. appropriate permission for the instance user ID to write
The file system is full. to the file. Check that there is enough space in the file
system.
ANR7804E (Windows) Error reason.
recorded in this file. Two servers cannot be started from Explanation: The server attempted to open,lock, or
the same directory. You can remove the lock file and write to the specified file The open, lock, or write
attempt to start the server only if the recorded process operation failed. These are some common reasons for
ID is not currently running dsmserv. The 'ps -e' the failure. Another server is already running from this
command can be used to display processes that are directory and has the file open or locked. The instance
currently running. Check the permissions of the user ID does not have enough write access to the file.
directory and file system and ensure that there is The file system is full.
appropriate permission for the instance user ID to write
to the file. Check that there is enough space in the file
system. User response: Examine the contents of the lock file.
recorded in this file. Two servers cannot be started from
ANR7804E (Linux) Error reason.
the same directory. You can remove the lock file and
Explanation: The server attempted to open,lock, or attempt to start the server only if the recorded process
write to the specified file The open, lock, or write ID is not currently running dsmserv. Check the
operation failed. These are some common reasons for permissions of the directory and file system and ensure
the failure. Another server is already running from this that there is appropriate permission for the instance
directory and has the file open or locked. The instance user ID to write to the file. Check that there is enough
user ID does not have enough write access to the file. space in the file system.
The file system is full.
System action: Server terminates. ANR7805E (AIX) Volume volume name is in use by
another server.
The process ID for the server that is running is Explanation: The server has attempted to open a disk
recorded in this file. Two servers cannot be started from volume but has discovered that the volume is in use by
the same directory. You can remove the lock file and another server.
attempt to start the server only if the recorded process
System action: The open operation fails for the
ID is not currently running dsmserv. The 'ps -e'
volume.
command can be used to display processes that are
currently running. Check the permissions of the User response: To prevent concurrent RAW volume
directory and file system and ensure that there is access by more than one server, files are created in the
appropriate permission for the instance user ID to write /tmp directory to 'lock' these volumes. The names of
to the file. Check that there is enough space in the file these temporary files are /tmp/
system. adsm.disk.dev.<volumename> where <volumename> is
the name of the RAW volume defined in the /dev

ANR7805E (Linux) ANR7806W (Linux)
directory. Please note that the name for the logical with a leading 'r' character (for example, a raw volume
volume as defined in SMIT is represented in the /dev defined in Solaris on a regular SCSI drive as
directory with a leading 'r' character (for example, a dsk/c0t0d0s0 will be represented in the /dev directory
raw volume defined in SMIT as dsmstg1 will be as the file /dev/rdsk/c0t0d0s0). For a REGULAR DISK
represented in the /dev directory as the file volume, the server automatically locks/unlocks a
/dev/rdsmstg1). volume. Different linked file names pointing to the
same volume will cause this message since the server
You may use the AIX 'ps -e' command to determine if
locks the linked volume, not the link name itself.
other dsmserv processes are running. You may remove
the temporary lock files and attempt to re-start the You may use the Solaris 'ps -ef | grep dsmserv'
server ONLY if there are no other dsmserv processes command to determine if other dsmserv processes are
running running. You may remove the temporary lock files for
RAW volumes and attempt to re-start the server ONLY
if there are no other dsmserv processes are running.
ANR7805E (Linux) Volume volume name is in use by
another server.
ANR7806W (AIX) Unable to open file file.
Explanation: The server has attempted to open a disk
volume but has discovered that the volume is in use by Explanation: The server was unable to open the
another server. indicated file.
System action: The open operation fails for the System action: The operation that was to use the
volume. indicated file fails. A subsequent unnumbered message
had details from the system.
User response: To prevent concurrent RAW volume
access by more than one server, files are created in the User response: Determine the reason for being unable
/tmp directory to 'lock' these volumes. The names of to open the file and re-attempt the operation. Common
these temporary files are /tmp/ reasons for being unable to open the file include
adsm.disk.dev.<volumename> where <volumename> is providing the wrong name, having insufficient
the name of the RAW volume defined in the /dev authorization to open the file and not being the file's
directory. Please note that the name for a RAW logical owner.
volume as defined in Solaris is in the /dev directory
with a leading 'r' character (for example, a raw volume
ANR7806W (HP-UX) Unable to open file file.
defined in Solaris on a regular SCSI drive as
dsk/c0t0d0s0 will be represented in the /dev directory Explanation: The server was unable to open the
as the file /dev/rdsk/c0t0d0s0). For a REGULAR DISK indicated file.
volume, the server automatically locks/unlocks a
volume. Different linked file names pointing to the System action: The operation that was to use the
same volume will cause this message since the server indicated file fails. A subsequent unnumbered message
locks the linked volume, not the link name itself. had details from the system.
You may use the Solaris 'ps -ef | grep dsmserv' User response: Determine the reason for being unable
command to determine if other dsmserv processes are to open the file and re-attempt the operation. Common
running. You may remove the temporary lock files for reasons for being unable to open the file include
RAW volumes and attempt to re-start the server ONLY providing the wrong name, having insufficient
if there are no other dsmserv processes are running. authorization to open the file and not being the file's
owner.
ANR7805E (Solaris) Volume volume name is in use by

another server. ANR7806W (Linux) Unable to open file file.
Explanation: The server has attempted to open a disk Explanation: The server was unable to open the
volume but has discovered that the volume is in use by indicated file.
another server. System action: The operation that was to use the
System action: The open operation fails for the indicated file fails. A subsequent unnumbered message
volume. had details from the system.
User response: To prevent concurrent RAW volume User response: Determine the reason for being unable
access by more than one server, files are created in the to open the file and re-attempt the operation. Common
/tmp directory to 'lock' these volumes. The names of reasons for being unable to open the file include
these temporary files are /tmp/ providing the wrong name, having insufficient
adsm.disk.dev.<volumename> where <volumename> is authorization to open the file and not being the file's
the name of the RAW volume defined in the /dev owner.
directory. Please note that the name for a RAW logical
volume as defined in Solaris is in the /dev directory
ANR7806W (Solaris) ANR7808W (AIX)
authorization to open the file and not being the file's

ANR7806W (Solaris) Unable to open file file.
owner.
Explanation: The server was unable to open the
indicated file.
ANR7807W (Linux) Unable to get information for
System action: The operation that was to use the file file.
indicated file fails. A subsequent unnumbered message
Explanation: The server was unable to get information
had details from the system.
about the indicated file.
User response: Determine the reason for being unable
System action: The operation that was to use the
to open the file and re-attempt the operation. Common
indicated file fails. A subsequent, unnumbered message
reasons for being unable to open the file include
has details from the system.
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
include providing the wrong name, having insufficient
ANR7806W (Windows) Unable to open file file.
authorization to open the file, not being the file's
Explanation: The server was unable to open the owner, or too many soft links to the file. If trying to
indicated file. access a RAW partition, the server must be started with
superuser privileges.
indicated file fails. A subsequent unnumbered message
had details from the system. ANR7807W (Solaris) Unable to get information for
file file.
to open the file and re-attempt the operation. Common Explanation: The server was unable to get information
reasons for being unable to open the file include about the indicated file.
owner. The file may be already opened by the server or
another program.
to access the file and re-attempt the operation.
ANR7807W (AIX) Unable to get information for file
file.
Explanation: The server was unable to get information authorization to open the file, not being the file's
about the indicated file. owner, or too many soft links to the file. If trying to
access a RAW partition, the server must be started with
superuser privileges.
ANR7807I (Windows) Sun Microsystems Library
Attach module module name has been
to access the file and re-attempt the operation.
loaded.
include providing the wrong name, having insufficient Explanation: The module indicated has been
authorization to open the file and not being the file's successfully loaded. Operations involving this module
owner. may now be performed by the server.
System action: The server now supports ACSLS
ANR7807W (HP-UX) Unable to get information for functions that depend on this module.
file file.
Explanation: The server was unable to get information
about the indicated file.
ANR7808W (AIX) root user authority required for
System action: The operation that was to use the non-default scheduling policy.
Explanation: The server was unable to use the
scheduling policy specified in the options file. The
User response: Determine the reason for being unable server must be running with root authority to use any
to access the file and re-attempt the operation. scheduling policy other than the default.
System action: Operation continues but with the
default scheduling policy.

ANR7808W (Windows) ANR7811E (Solaris)
User response: Run the server with root authority or

ANR7810E (Linux) Error creating console input
don't specify a scheduling policy in the options file.
thread.
Explanation: Unable to start console input thread.
ANR7808W (Windows) Sun Microsystems Library
Attach module module name is not System action: Server operation stops.
available from the system.
User response: See other issued messages.
Explanation: The server attempted to load the Library
Attach module. However, this module is not installed
ANR7810E (Solaris) Error creating console input
to the system.
thread.
Explanation: Unable to start console input thread.
without ACSLS function.
User response: Ensure that the Library Attach module
is installed to the system. User response: See other issued messages.
ANR7809I (AIX) Using scheduling policy policy. ANR7811I (AIX) Using instance directory instance
directory.
Explanation: All threads in the server will use the
specified scheduling policy. Explanation: The server is operating out of the
indicated directory.
System action: Operations continue.
User response: None
ANR7810W (AIX) Unable to create a new child
process. ANR7811E (HP-UX) Insufficient memory for console
initialization.
Explanation: The server cannot create a new child
thread. Explanation: The server is unable to allocate enough
memory for console initialization.
System action: Server processing continues. Other
error messages from the server component are System action: Server operation stops.
displayed.
User response: Ensure that there is sufficient paging
User response: Ensure that sufficient paging space is space for HP-UX. It may be necessary to reduce the
available for AIX. If the server has been started from a maximum number of client sessions by changing the
non-root user ID, ensure that the AIX process limit per MAXSESSIONS option in the server options file.
user is sufficient for the server. The server requires
approximately 24 processes, in addition to one process
per client session, and one process for each background ANR7811E (Linux) Insufficient memory for console
operation. Each thread started by the server is an AIX initialization.
process. To change the number of processes per user, Explanation: The server is unable to allocate enough
use the SMIT menus for System Environment, and memory for console initialization.
choose Change / Show Characteristics of Operating
System. You may also use SMIT to determine if the System action: Server operation stops.
number of applications is causing a memory shortage. User response: Ensure that there is sufficient paging
It may be necessary to decrease the maximum number space. It may be necessary to reduce the maximum
of client sessions by changing the MAXSESSIONS number of client sessions by changing the
option in the server options file. MAXSESSIONS option in the server options file.
ANR7810E (HP-UX) Error creating console input ANR7811E (Solaris) Insufficient memory for console
thread. initialization.
Explanation: Unable to start console input thread. Explanation: The server is unable to allocate enough
System action: Server operation stops. memory for console initialization.
User response: See other issued messages. System action: Server operation stops.
space for Sun Solaris. It may be necessary to reduce the
maximum number of client sessions by changing the
MAXSESSIONS option in the server options file.
ANR7812E (HP-UX) ANR7814I (HP-UX)
User response: Ensure that sufficient swap space is

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

ANR7814I (Linux) ANR7821I (Solaris)
ANR7814I (Linux) Using instance directory instance ANR7820S (Solaris) Server thread thread ID
directory. terminated in response to program
abort.
Explanation: The server is operating out of the
indicated directory. Explanation: The thread has ended due to a program
abort.
System action: The server completes termination
processing.
User response: Note the associated messages and call
ANR7814I (Solaris) Using instance directory instance
directory.
Explanation: The server is operating out of the
ANR7820W (Windows) Insufficient Space Available
indicated directory.
for file file name.
Explanation: The server was attempting to create a file
User response: None. with the indicated name. There was insufficient space
for the file on the disk.
ANR7820E (AIX) Insufficient memory to buffer System action: Server processing continues. The file
console input; the following input line creation request fails.
User response: Free additional space on the drive to
Explanation: An error occurs during an attempt to accomodate the file, specify a file name on a drive with
allocate a buffer large enough to read console input. sufficient space, or change the space request to a value
consistent with the drive. Retry the operation.
User response: Ensure that sufficient paging space is ANR7821I (HP-UX) Server thread thread ID
available for AIX. You may also use SMIT to determine terminated in response to external
if the number of applications is causing a memory signal.
shortage. It may be necessary to decrease the maximum
number of client sessions by changing the Explanation: The thread has ended due to an external
MAXSESSIONS option in the server options file. signal.
ANR7820S (HP-UX) Server thread thread ID processing.
terminated in response to program
abort.
Explanation: The thread has ended due to a program
ANR7821I (Linux) Thread thread ID terminated in
abort.
response to external signal.
Explanation: The thread has ended due to an external
processing.
signal.
User response: Note the associated messages and
processing.
ANR7820S (Linux) Thread thread ID terminated in
response to program abort.
ANR7821I (Solaris) Server thread thread ID
Explanation: The thread has ended due to a program
terminated in response to external
abort.
signal.
processing.
signal.
User response: Note the associated messages and call
processing.
ANR7821W (Windows) ANR7824E (AIX)
User response: Specify a new file name. The server

ANR7821W (Windows) Unable to create directory
will not use an existing file name when creating a file.
when creating volume file name.
ANR7823E (AIX) Insufficient memory for console
with the indicated name. A new directory was being
initialization.
created as well, but its creation failed.
Explanation: Unable to allocate enough memory for
System action: Server processing continues. The file
console initialization.
creation request fails.
User response: Specify a file name in an existing
directory or change the name request to specify a User response: Ensure that sufficient paging space is
different directory name. available for AIX. You may also use SMIT to determine
if the number of applications is causing a memory
ANR7822E (AIX) Error creating console input thread.
Explanation: Unable to start console input thread. MAXSESSIONS option in the server options file.
ANR7823S (Linux) Internal error internal error
User response: See other issued messages.
detected.
Explanation: An internal error is detected during
ANR7822I (HP-UX) Server thread thread ID
server initialization or operation.
terminated in response to server
shutdown. System action: Server operation stops.
Explanation: The thread has ended due to a server User response: Review additional information that is
shutdown. available for this message in one of the following
locations:
processing. v The problem determination section in the Tivoli
Storage Manager Information Center:
User response: None. http://publib.boulder.ibm.com/infocenter/tsminfo/
v6r3/topic/com.ibm.itsm.nav.doc/t_probdeterm.html
ANR7822I (Linux) Thread thread ID terminated in Find relevant information by entering the message
response to server shutdown. number in the Search field and selecting from topics
in the search results.
Explanation: The thread has ended due to a server
shutdown. v Tivoli Storage Manager Problem Determination Guide, a
book in PDF format that is available for download
System action: The server completes termination from the IBM Publications Center:
processing. http://www.ibm.com/shop/publications/order/
ANR7823W (Windows) Unable to create file file name.
ANR7822I (Solaris) Server thread thread ID Explanation: The server was attempting to create a file
terminated in response to server with the indicated name. The system reported an error
shutdown. in creating the file.
Explanation: The thread has ended due to a server System action: The server continues processing. The
shutdown. file creation request fails.
System action: The server completes termination User response: Specify a new file name.
processing.
User response: None. ANR7824E (AIX) Error loading Async I/O support
module.
ANR7822W (Windows) File Already exists when Explanation: The server attempted to load the Async
creating volume file name. I/O support module, but the load failed. Refer to
accompanying error message for details on the load
failure.
with the indicated name. The file already exists.
System action: Server processing continues. The file
without Async I/O support.
creation request fails.
User response: Ensure that the correct support

ANR7824S (HP-UX) ANR7830E (Solaris)
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 (a Sun 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.
System action: Server operation stops. Explanation: The server was attempting to create a file
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.
ANR7824S (Solaris) Server operation terminated.
System action: The server continues processing. The
Explanation: An error occurs that causes server file creation request fails.
operation to stop.
User response: Specify a new file name. The return
System action: Server operation stops. code may also be provided to your service
User response: Contact your service representative. representative for interpretation.
ANR7824W (Windows) Unable to write volume file ANR7826W (Windows) Creation of Volume file name
name. failed. Process was cancelled.
Explanation: The server was attempting to create a file Explanation: The server was attempting to create a file
with the indicated name. The server was able to with the indicated name. The attempt was cancelled by
partially write to the file before running out of space. a cancel process command.
System action: The server continues processing. The System action: The server continues processing. The
file creation request fails. The file is still present on the file creation request fails.
system. User response: The DEFINE command may be
User response: Specify a new file name where there is re-entered.
sufficient space.
ANR7830E (Linux) Invalid RAW Partition Name: A
ANR7825E (Linux) Server unable to allocate a shared valid raw partition name is in the form
memory segment of size Client requested of /dev/.../rdsk/.../* , where ... means 0 or
shared memory size. more directories.
Explanation: A shared memory client has requested a Explanation: Use the proper format for specifying a
shared memory segment size that Solaris is unable to Raw partition. The ... means zero or more directories.
fulfill. System action: Inform the user to use the right RAW
System action: Client is not allowed to logon partition specification.
User response: See the shared memory tuning guide User response: Have user reenter the RAW partition
for Solaris (a Sun document). You may need to increase with the proper partition name.
the number/size of shared memory segments and/or
message queues. ANR7830E (Solaris) Invalid RAW Partition Name: A
valid raw partition name is in the form
of /dev/.../rdsk/.../* , where ... means 0 or
more directories.
Explanation: Use the proper format for specifying a
Raw partition. The ... means zero or more directories.
ANR7831E (Linux) ANR7833E (Linux)
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
ANR7831E (Linux) raw partition name has an existing likely crash the whole operating system.
filesystem.
System action: Disallow access to this raw partition.
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
System action: Warn the user that an existing your partition name tag is labeled incorrectly as / or
filesystem for the raw partition specified may be /usr.
destroyed if written to.
User response: Determine if user still wants the valid ANR7832E (Solaris) raw partition name corresponds to
filesystem data. If not, user needs to destroy the a protected filesystem, such as / or /usr.
filesystem by either formatting the partition, create a
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
format() command. The user can read the format() System action: Disallow access to this raw partition.
function in the Sun manuals for further details on
User response: Have user specify another RAW
filesystems.
partition that is not the / or /usr. It may be possible
that this is not the actual / or /usr partition of the boot
ANR7831E (Solaris) raw partition name has an existing disk. Check, using the Solaris format() command, if
filesystem. your partition name tag is labeled incorrectly as / or
/usr.
existing Solaris file system on it. Writing to this
partition will most likely destroy this filesystem. ANR7833S (AIX) The process thread ID terminated in
response to program abort.
System action: Warn the user that an existing
filesystem for the raw partition specified may be Explanation: The thread has ended due to a program
destroyed if written to. abort.
User response: Determine if user still wants the valid System action: The server completes termination
filesystem data. If not, user needs to destroy the processing.
filesystem by either formatting the partition, create a
program to destroy the filesystem header information
so that the server will not be able to detect the
filesystem header information, or rearrange the starting ANR7833E (Linux) symbolic links has too many
and ending blocks of a partition by using the Solaris symbolic links - the maximum
format() command. The user can read the format() allowable is 10.
function in the Sun manuals for further details on
filesystems. Explanation: The file specified has too many symbolic
links. The server will follow at most 10 links before
ending this symbolic link name resolution.
ANR7832I (AIX) The thread process ID terminated
with exit code program exit code. System action: Disallow access to this file.
Explanation: The process has ended with the User response: Have the user specify the actual file,
indicated exit code. This error is due to the problem where the file is not a symbolic link. Using ls -l, one
caused and indicated by a preceding message. can see if the file is a symbolic link.

processing.

ANR7833E (Solaris) ANR7835I (Windows)

ANR7833E (Solaris) symbolic links has too many
symbolic links - the server only
supports a maximum of 10. ANR7835I (AIX) The server thread thread ID
terminated in response to server
Explanation: The file specified has too many symbolic
shutdown.
links. The server will follow at most 10 links before
ending this symbolic link name resolution. Explanation: The thread has ended due to a server
shutdown.
System action: Disallow access to this file
User response: Have the user specify the actual file,
processing.
where the file is not a symbolic link. Using ls -l, one
can see if the file is a symbolic link. User response: None.
ANR7834I (AIX) The thread thread ID terminated in ANR7835E (Linux) Specified raw partition name raw
response to external signal. partition is too big for this operating
system to handle.
signal. Explanation: The raw partition specified has greater
than 2GB and the operating system is running below
Solaris 2.6. Operating system below Solaris 2.6 cannot
processing.
handle files natively more than 2GB. For operating
User response: None. system that is at Solaris 2.6 or above, the limit is 1TB.
System action: Disallow access to this raw partition.
ANR7834E (Linux) Specified raw partition name raw
User response: Have the system administrator change
partition cannot contain the 0th disk
the RAW partition size to be less than 2GB (4194303
cylinder.
512-byte disk blocks) for Solaris 2.5.1 or below, less
Explanation: The raw partition specified has the 0th than 1TB (2147483647 512-byte disk blocks) for Solaris
disk cylinder. The server should not be allowed to 2.6 and above.
write into the 0th cylinder. If allowed, the disk label
would be corrupted.
ANR7835E (Solaris) Specified raw partition name raw
System action: Disallow access to this raw partition. partition is too big for this operating
system to handle.
the starting cylinder of this partition to a number Explanation: The raw partition specified has greater
greater than 0. than 2GB and the operating system is running below
Solaris 2.6. Operating system below Solaris 2.6 cannot
handle files natively more than 2GB. For operating
ANR7834E (Solaris) Specified raw partition name raw
system that is at Solaris 2.6 or above, the limit is 1TB.
partition cannot contain the 0th disk
cylinder. System action: Disallow access to this raw partition
Explanation: The raw partition specified has the 0th User response: Have the system administrator change
disk cylinder. The server should not be allowed to the RAW partition size to be less than 2GB (4194303
write into the 0th cylinder. It allowed, the disk label 512-byte disk blocks) for Solaris 2.5.1 or below, less
would be corrupted. than 1TB (2147483647 512-byte disk blocks) for Solaris
2.6 and above.
System action: Disallow access to this raw partition
ANR7835I (Windows) The server thread thread ID (tid
the starting cylinder of this partition to a number
Windows NT thread ID) terminated in
greater than 0.
response to server shutdown.
Explanation: The thread has terminated due to a
ANR7834I (Windows) The server thread thread ID (tid
server shutdown.
Windows NT thread ID) terminated in
response to external signal. System action: The server completes termination
processing.
Explanation: The thread has terminated due to an
external signal. User response: None.
processing.
ANR7836S (AIX) ANR7843W (HP-UX)
ANR7836S (AIX) Server initialization terminated. ANR7838S (AIX) Server operation terminated.
Explanation: An error occurs that causes server Explanation: An error occurs that causes server
initialization to end. operation to stop.
System action: Server operation stops. System action: Server operation stops.
User response: Contact your service representative. User response: Contact your service representative.
ANR7837S (AIX) Internal error internal error was ANR7841S (AIX) Insufficient kernel memory
detected. available.
Explanation: An internal error was detected during Explanation: An error occurs due to insufficient kernel
server initialization or operation. memory.
System action: The server stops. System action: Server operation stops.
User response: You must extend the log file when you User response: Contact your service representative.
receive ANR7837S, LOGSEG871 errors. Review
additional information that is available for this message
ANR7842S (AIX) Monitor kernel extension not
in one of the following locations:
initialized.
v The problem determination section in the Tivoli
Storage Manager Information Center: Explanation: The monitor kernel extension is not
http://publib.boulder.ibm.com/infocenter/tsminfo/ initialized.
v6r3/topic/com.ibm.itsm.nav.doc/t_probdeterm.html System action: Server operation stops.
Find relevant information by entering the message
number in the Search field and selecting from topics User response: Contact your service representative.
in the search results.
v Tivoli Storage Manager Problem Determination Guide, a ANR7843W (AIX) Unable to determine real memory
book in PDF format that is available for download size.
from the IBM Publications Center:
Explanation: The server checks the amount of real
http://www.ibm.com/shop/publications/order/
memory in the system to optimize use of storage in the
database buffer pool. The server uses Object Data
ANR7837S (Windows) Internal error internal error was Manager (ODM) to determine how much real memory
detected. is installed on the system. The routines used to call
ODM failed or were unable to return the real memory
Explanation: An internal error was detected during size.
server initialization or operation.
System action: Server operation continues. The server
System action: The server stops. 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. Review User response: The server may need to run as a root
additional information that is available for this message user to obtain this information.
in one of the following locations:
v The problem determination section in the Tivoli
Storage Manager Information Center: ANR7843W (HP-UX) Unable to determine real
http://publib.boulder.ibm.com/infocenter/tsminfo/ memory size.
v6r3/topic/com.ibm.itsm.nav.doc/t_probdeterm.html Explanation: The server checks the amount of real
Find relevant information by entering the message memory in the system to optimize use of storage in the
number in the Search field and selecting from topics database buffer pool. The routines used to obtain this
in the search results. information returned a failing return code or were
v Tivoli Storage Manager Problem Determination Guide, a unable to return the real memory size.
book in PDF format that is available for download System action: Server operation continues. The server
from the IBM Publications Center: allows the data base buffer pool size to grow withoug
http://www.ibm.com/shop/publications/order/ taking into account real memory.
User response: The server may need to run as a root
user to obtain this information.

ANR7843W (Linux) ANR7855W (Windows)
ANR7843W (Linux) Unable to determine real ANR7850I (AIX) The process process ID has
memory size. terminated on signal signal number (signal
name).
Explanation: The server checks the amount of real
memory in the system to optimize use of storage in the Explanation: The specified process has ended due to
database buffer pool. The server uses Object Data the specified signal.
Manager (ODM) to determine how much real memory
is installed on the system. The routine s used to call
ODM failed or were unable to return the real memory User response: Contact your service representative.
size.
System action: Server operation continues. The server ANR7851S (AIX) Error resetting handler for signal
allows the data base buffer pool size to grow withoug signal number (signal name).
taking into account real memory.
Explanation: An error occurs resetting the specified
User response: The server may need to run as a root signal handler.
ANR7843W (Solaris) Unable to determine real User response: Contact your service representative.
memory size.
Explanation: The server checks the amount of real ANR7852I (Windows) The current process affinity
memory in the system to optimize use of storage in the mask is: 0xThe process affinity mask..
database buffer pool. The routines used to obtain this Explanation: The server is running on the processors
information returned a failing return code or were indicated by the mask.
unable to return the real memory size.
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 ANR7853W (Windows) Could not obtain the current
user to obtain this information. process affinity mask. Reason: NT return
code..
ANR7843W (Windows) Unable to determine real Explanation: A problem was encounterd while
memory size. obtaining the current process affinity.
Explanation: The server checks the amount of real System action: Server operation continues.
memory in the system to optimize use of storage in the User response: None.
database buffer pool. The routines used to obtain this
information returned a failing return code or were
unable to return the real memory size. ANR7854W (Windows) The process affinity mask
(0xAffinity mask.) specified in
System action: Server operation continues. The server dsmserv.opt is out of range.
allows the data base buffer pool size to grow withoug
taking into account real memory. Explanation: The affinity mask value was out of
range.
User response: The server may need to run as a root
user to obtain this information. System action: Server operation continues.
ANR7849I (AIX) Server operation terminated - kernel
extension has been reset. ANR7855W (Windows) Could not set new process
Explanation: The kernel extension has been affinity mask. Reason: NT return code.
reinitialized by the server in response to a previous Explanation: A problem was encounterd in setting a
condition for which a message has been issued. new process affinity mask.
System action: Server operation stops. System action: Server operation continues.
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: An error occurs during an attempt to
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.
file creation request fails.
foreground.
accomodate the file, specify a file name on a drive with
ANR7859W (HP-UX) Error reading from standard
sufficient space, or change the space request to a value
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) Insufficient Space Available for
file file name.
directory or or change the name request to specify a
with the indicated name. There was insufficient space
different directory name.
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.
different directory name.
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
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.
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.
User response: Specify a new file name.
ANR7863W (HP-UX) ANR7865W (Linux)
ANR7863W (HP-UX) Unable to create file file name. ANR7864W (Linux) Unable to write volume file name.
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
partially write to the file before running out of space.
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.
partially write to the file before running out of space.
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) ANR7871W (AIX)
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
ANR7870W (AIX) Unable to initialize odm query.
existing data to other volumes. The volume can then be
Error message from odm is odm message.
deleted and re-created using a multiple of the disk's
block size. Explanation: The server uses the AIX Object Data
Manager (ODM) to check information about AIX. For
example, the server uses ODM to detemine how much
ANR7868E (AIX) The server is unable to open or
real memory is installed on the system. The routine
used to initialize an ODM query failed. ODM returned
Explanation: The server attempted to open or lock the an error message as indicated.
instance lock file. The open or lock operation failed.
System action: Server initialization fails. makes assumptions concerning information it could not
obtain.
User response: Ensure that the server is being
initialized from the correct instance directory and that User response: The server may need to run as a root
this server instance is not running. Ensure that the user to obtain this information.
ANR7871W (AIX) Unable to complete odm query.
Error message from odm is odm message.
ANR7868E (HP-UX) The server is unable to open or
Explanation: The server uses the AIX Object Data
Manager (ODM) to check information about AIX. For
Explanation: The server attempted to open or lock the example, the server uses ODM to detemine how much
instance lock file. The open or lock operation failed. real memory is installed on the system. The routine
used to perform and ODM query failed. ODM returned
an error message as indicated.
User response: Ensure that the server is being
initialized from the correct instance directory and that
makes assumptions concerning information it could not
this server instance is not running. Ensure that the
obtain.
and write files on the specified path. User response: The server may need to run as a root

ANR8195I (AIX) ANR8196I (Windows)
ANR8195I (AIX) The SSL TCP/IP Version 4 driver is ANR8196I (AIX) The SSL TCP/IP administrative
ready for connection with clients on driver is ready for connection with
port port number. clients on port port number.
Explanation: The server can now accept sessions with Explanation: The server can now accept sessions with
clients using the SSL TCP/IP protocol on the indicated administrative clients using the SSL TCP/IP protocol
port number. on the indicated port number.
ANR8195I (HP-UX) The SSL TCP/IP Version 4 driver ANR8196I (HP-UX) The SSL TCP/IP administrative
is ready for connection with clients on driver is ready for connection with
ANR8195I (Linux) The SSL TCP/IP Version 4 driver ANR8196I (Linux) The SSL TCP/IP administrative
ANR8195I (Solaris) The SSL TCP/IP Version 4 driver ANR8196I (Solaris) The SSL TCP/IP administrative
ANR8195I (Windows) The SSL TCP/IP Version 4 ANR8196I (Windows) The SSL TCP/IP
driver is ready for connection with administrative driver is ready for
clients on port port number. connection with clients on port port
number.
Explanation: The server can now accept sessions with
clients using the SSL TCP/IP protocol on the indicated Explanation: The server can now accept sessions with
port number. administrative clients using the SSL TCP/IP protocol
on the indicated port number.
ANR8197W (HP-UX) ANR8199E (Windows)
ANR8197W (HP-UX) A TCP/IP driver is unable to set ANR8198E (Windows) The SSL environment was not
the window size to TCPWindowsize for a established. The GSK module gsk module
master socket on which the server return code is gsk return code.
listens. The server will use the default
Explanation: Initialization of the SSL environment has
window size for listening to sessions.
failed. Connections to SSL ports are not possible.
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. User response: Stop and restart the server.
System action: Server operation continues with the
default window size. ANR8199E (AIX) The SSL TCP/IP driver was not
initialized on port port number.
User response: If necessary, restart the server with a
smaller window size in the options file. To determine Explanation: A problem with the SSL environment
the setting of the server window size prevents Tivoli Storage Manager from establishing the
(TCPWindowsize), issue the QUERY OPTION SSL protocol on the indicated port number.
command.
ANR8198E (AIX) The SSL environment was not User response: None
established. The GSK module gsk module
return code is gsk return code. ANR8199E (HP-UX) The SSL TCP/IP driver was not
Explanation: Initialization of the SSL environment has initialized on port port number.
failed. Connections to SSL ports are not possible. Explanation: A problem with the SSL environment
System action: Server operation continues. prevents Tivoli Storage Manager from establishing the
SSL protocol on the indicated port number.
User response: Stop and restart the server.
ANR8198E (HP-UX) The SSL environment was not User response: None
return code is gsk return code. ANR8199E (Linux) The SSL TCP/IP driver was not
ANR8198E (Linux) The SSL environment was not User response: None
return code is gsk return code. ANR8199E (Solaris) The SSL TCP/IP driver was not
ANR8198E (Solaris) The SSL environment was not User response: None
return code is gsk return code. ANR8199E (Windows) The SSL TCP/IP driver was
Explanation: Initialization of the SSL environment has not initialized on port port number.
User response: None

ANR8200I (AIX) ANR8201E (Solaris)
ANR8200I (AIX) TCP/IP Version 4 driver ready for ANR8201W (AIX) Unable to initialize TCP/IP driver
connection with clients on port port - insufficient memory.
number.
Explanation: Because the operating system rejects a
Explanation: The server can now accept sessions with memory allocation request, the server cannot start
clients using the TCP/IP Version 4 protocol on the communications through TCP/IP.
indicated port number.
System action: Server operation continues. server cannot accept sessions from clients using the
TCP/IP protocol.
User response: Ensure that sufficient paging space is
available for AIX. You may also use SMIT to determine
ANR8200I (HP-UX) TCP/IP Version 4 driver ready
for connection with clients on port port
number.
Explanation: The server is now able to accept sessions MAXSESSIONS option in the server options file.
with clients using the TCP/IP Version 4 protocol on the
ANR8201E (HP-UX) Unable to initialize TCP/IP
System action: Server operation continues. driver - socket creation failed; error error
code.
Explanation: The server is unable to initialize the
TCP/IP driver due to a socket creation error.
ANR8200I (Linux) TCP/IP Version 4 driver ready for
connection with clients on port port System action: Server operation continues, but
number. TCP/IP support is inoperative.
Explanation: The server can now accept sessions with User response: Ensure that TCP/IP is operational on
clients using the TCP/IP Version 4 protocol on the your system by using the ping command with your
indicated port number. TCP/IP address as a target. If TCP/IP is not active on
your system, you must activate it; then halt and restart
System action: Server operation continues. the server.
ANR8201E (Linux) Unable to initialize TCP/IP driver
ANR8200I (Solaris) TCP/IP Version 4 driver ready - socket creation failed; error error code.
for connection with clients on port port Explanation: The server is unable to initialize the
number. TCP/IP driver due to a socket creation error.
Explanation: The server can now accept sessions with System action: Server operation continues, but
clients using the TCP/IP Version 4 protocol on the TCP/IP support is inoperative.
User response: Ensure that TCP/IP is operational on
System action: Server operation continues. your system by using the ping command with your
User response: None. TCP/IP address as a target. If TCP/IP is not active on
the server.
ANR8200I (Windows) TCP/IP Version 4 driver ready
number. ANR8201E (Solaris) Unable to initialize TCP/IP
driver - socket creation failed; error error
Explanation: The server can now accept sessions with code.
clients using the TCP/IP Version 4 protocol on the
indicated port number. Explanation: The server is unable to initialize the
TCP/IP driver due to a socket creation error.
User response: None. TCP/IP support is inoperative.
your system by using the ping command with your
TCP/IP address as a target. If TCP/IP is not active on
the server.
ANR8201W (Windows) ANR8203W (AIX)
TCP/IP support is inoperative.

ANR8201W (Windows) Unable to initialize TCP/IP
driver - insufficient memory. User response: Ensure that TCP/IP is operational on
Explanation: The server is unable to communicate by
way of TCP/IP. A memory allocation request has been
rejected by the operating system.
the server. This message may also result from more
System action: Server operation continues, but the than one server running on the same machine with the
server cannot accept sessions from clients using the same TCP/IP port number. Make sure that the
TCP/IP protocol. dsmserv.opt file TCPPort option is different for each
server. Make sure TCPPORT and TCPADMINPORT do
User response: Ensure that there is sufficient space for
not specify or default to the same values.
the Windows paging file. Click on the system icon in
the Windows control panel and then click on the
virtual memory button. Refer to the online help for ANR8202E (Solaris) Unable to initialize TCP/IP
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.
Explanation: Because TCP/IP rejects a request for a
socket on which to listen, the server cannot start
communications through TCP/IP.
System action: Server operation continues, but the your system, you must activate it; then halt and restart
server cannot accept sessions from clients using the the server. This message may also result from more
TCP/IP protocol. than one server running on the same machine with the
same TCP/IP port number. Make sure that the
dsmserv.opt file TCPPort option is different for each
server.
TCP/IP address as a target. If TCP/IP is not started,
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.
Reason code reason code.
ANR8202E (HP-UX) Unable to initialize TCP/IP
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
socket on which the server listens.
TCP/IP driver due to a socket binding error. System action: Server operation continues, but the
server cannot accept sessions from clients using the
TCP/IP protocol.
TCP/IP address as a target. If TCP/IP is not started,
issue the HALT command to stop the server, and then
restart the server.
the server. This message may also result from more
than one server running on the same machine with the
same TCP/IP port number. Make sure that the ANR8203W (AIX) Unable to establish TCP
dsmserv.opt file TCPPort option is different for each connection - accept error.
server.
Explanation: The server cannot accept a client session
due to a failure in TCP/IP.
ANR8202E (Linux) TCP/IP driver unable to initialize
due to error in using port TCP port
number; error error code.
TCP/IP protocol.
TCP/IP driver due to a socket binding error.
System action: Server operation continues, but TCP/IP address as a target. If TCP/IP is not started,

ANR8203E (HP-UX) ANR8204W (Windows)
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 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.
ANR8203E (Solaris) Unable to initialize TCP/IP
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.
User response: This error often results from a lack of
memory. Ensure that your system has sufficient paging
space to support the current activities.
ANR8204E (Solaris) Unable to initialize TCP/IP
driver - thread creation failed.
the server. Explanation: The server is unable to initialize the
TCP/IP driver due to an error creating a server thread.
ANR8203W (Windows) Unable to establish TCP System action: Server operation continues, but
connection - accept error. TCP/IP support is inoperative.
Explanation: The server cannot accept a client session User response: This error often results from a lack of
due to failure in TCP/IP. memory. Ensure that your system has sufficient paging
space to support the current activities.
TCP/IP protocol. ANR8204W (Windows) Unable to establish TCP
connection - insufficient memory.
your system by using the ping command with your Explanation: The server is unable to accept a client
TCP/IP address as a target. If TCP/IP is not started, session due to a memory allocation request failure.
ANR8205W (AIX) ANR8206E (Linux)
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
virtual memory button. Refer to the online help for
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.
ANR8206E (Linux) Unable to establish TCP/IP
session - invalid host address IP host
User response: Ensure that TCP/IP is operational on address (port port number).
session because the designated address or port number
is not valid.
the server.
ANR8205E (Solaris) 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
application.

ANR8206E (Solaris) ANR8208W (AIX)
ANR8206E (Solaris) Unable to establish TCP/IP ANR8207E (Linux) 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 (Solaris) Unable to establish TCP/IP
application.
session with IP host address due to
memory shortage.
ANR8206I (Windows) TCP/IP Version 4
administrative driver ready for
session because of a memory shortage condition.
connection with clients on port port
number. System action: Server operation continues.
Explanation: The server can now accept sessions with User response: Ensure that your system has sufficient
administrative clients using the TCP/IP Version 4 paging space to support the current level of system
protocol on the indicated port number. activities.
ANR8207W (Windows) TCP/IP driver unable to
initialize due to socket initialization
error. Reason code reason code.
ANR8207W (AIX) TCP/IP driver unable to initialize
Explanation: While initializing TCP/IP
due to socket initialization error. Reason
communications, the server has failed to set up an
code reason code.
interface with TCP/IP for Windows.
communications, the server fails to set up an interface
with TCP/IP.
TCP/IP protocol.
User response: Ensure that TCP/IP is properly
installed on your system. Ensure that TCP/IP has been
TCP/IP protocol.
started on your system. Issue the TCP/IP ping
User response: Ensure that TCP/IP has been started command to your own address to verify that TCP/IP is
and is active on your system. You may issue the both installed and active.
TCP/IP ping command to your own address to verify
that TCP/IP is both started and active.
due to error in using port port, reason
ANR8207E (HP-UX) Unable to establish TCP/IP code reason code.
session with IP host address due to
memory shortage.
communications, the server fails to connect to a master
Explanation: The server is unable to establish a socket on which to listen for clients. The reason code is
session because of a memory shortage condition. the return code from the TCP/IP bind API.
System action: Server operation continues. System action: Server operation continues, but the
User response: Ensure that your system has sufficient
TCP/IP protocol.
paging space to support the current level of system
activities. User response: Ensure that no other application is
using the port number specified in the server options
file with the TCPPORT option by issuing the TCP/IP
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
before the port can be freed.
ANR8208E (HP-UX) ANR8209E (Solaris)
then restart the server. If that does not work, it may be

necessary to restart Windows.
session with IP host address - socket
creation failed; error error code.
due to error in LISTENing on the
session because of a socket creation error.
specified Port, reason code reason code.
Explanation: While attempting to listen for session
User response: Ensure that TCP/IP is operational on requests from clients using TCP/IP, TCP/IP returns an
your system by using the ping command with your error. The reason code is the return code from the
TCP/IP address as a target. If TCP/IP is not active on TCP/IP listen API.
the server.
server cannot accept additional sessions from clients
using the TCP/IP protocol.
User response: Ensure that TCP/IP is running
properly by issuing the TCP/IP netstat -s and ping
commands to other nodes on your network. It may be
Explanation: The server is unable to establish a possible to bring the server down and restart it to
session because of a socket creation error. allow additional client sessions to start.
session with IP host address - connection
refused.
your system, you must activate it; then halt and restart Explanation: The server is unable to establish a
the server. session because the remote system refused the
connection request.
ANR8208E (Solaris) Unable to establish TCP/IP System action: Server operation continues.
User response: Ensure that the specified remote
system is operational and is properly configured to run
Explanation: The server is unable to establish a TCP/IP. Ensure that the client options file specifies the
session because of a socket creation error. correct TCPServeraddress and TCPPort of the server
you are attempting to contact.
refused.
the server. Explanation: The server is unable to establish a
session because the remote system refused the
connection request.
initialize due to error in using Port port, System action: Server operation continues.
reason code reason code.
Explanation: While initializing TCP/IP system is operational and is properly configured to run
communications, the server has failed to connect to a TCP/IP. Ensure that the client options file specifies the
master socket on which to listen for clients. The reason correct TCPServeraddress and TCPPort of the server
code is the return code from the TCP/IP bind API. you are attempting to contact.
server cannot accept sessions from clients using the ANR8209E (Solaris) Unable to establish TCP/IP
TCP/IP protocol. session with IP host address - connection
refused.
User response: Ensure that no other application is
using the port number specified in the server options Explanation: The server is unable to establish a
file with the TCPPORT option. If the server is brought session because the remote system refused the
down and then started immediately, you may be within connection request.
the TCP/IP one minute timeout period for port
reusage. Bring down the server, wait one minute, and

ANR8209W (Windows) ANR8210W (Windows)

TCP/IP. Ensure that the client options file specifies the
request timed out.
correct TCPServeraddress and TCPPort of the server
you are attempting to contact. Explanation: The server is unable to establish a
session because the remote system did not respond to
the connection request.
initialize due to error in LISTENing on System action: Server operation continues.
the specified Port, reason code reason
User response: Ensure the following:
code.
v The specified remote system is operational and is
Explanation: While attempting to listen for session properly configured to run TCP/IP.
requests from clients using TCP/IP, TCP/IP returns an
v The client options file specifies the correct
error. The reason code is the return code from the
TCPServeraddress and TCPPort of the server you are
TCP/IP listen API.
attempting to contact.
System action: Server operation continues, but the v Necessary gateways and routers are functioning
server cannot accept additional sessions from clients properly.
using the TCP/IP protocol.
User response: Ensure that TCP/IP is running ANR8210E (Solaris) Unable to establish TCP/IP
properly. This may be done by issuing the TCP/IP session with IP host address - connection
netstat -s and ping commands to other nodes on your request timed out.
network. It may be possible to correct this condition by
restarting the server. Explanation: The server is unable to establish a
session because the remote system did not respond to
ANR8210W (AIX) TCP/IP driver is terminating due
to error in accepting a new session, System action: Server operation continues.
reason code reason code. User response: Ensure the following:
Explanation: While attempting to accept a session v The specified remote system is operational and is
request from a client using TCP/IP, TCP/IP returns an properly configured to run TCP/IP.
error. The reason code is the return code from the v The client options file specifies the correct
TCP/IP accept API. TCPServeraddress and TCPPort of the server you are
System action: Server operation continues, but the attempting to contact.
server cannot accept additional sessions from clients v Necessary gateways and routers are functioning
using the TCP/IP protocol. properly.
properly. This may be done by issuing the TCP/IP ANR8210W (Windows) TCP/IP driver is terminating
netstat -s and ping commands to other nodes on your due to error in accepting a new session,
network. It may be possible to bring the server down reason code reason code.
and restart it to allow additional client sessions to start.
Explanation: While attempting to accept a session
request from a client using TCP/IP, TCP/IP returns an
ANR8210E (HP-UX) Unable to establish TCP/IP error. The reason code is the return code from the
session with IP host address - connection TCP/IP accept API.
request timed out.
Explanation: The server is unable to establish a server cannot accept additional sessions from clients
session because the remote system did not respond to using the TCP/IP protocol.
System action: Server operation continues. 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 bring the server down
v The specified remote system is operational and is and restart it to allow additional client sessions to start.
properly configured to run TCP/IP.
v The client options file specifies the correct
TCPServeraddress and TCPPort of the server you are
attempting to contact.
v Necessary gateways and routers are functioning
properly.
ANR8211W (AIX) ANR8212E (Linux)
ANR8211W (AIX) TCP/IP driver is terminating due ANR8211W (Windows) TCP/IP driver is terminating
to error in creating a new thread. due to error in creating a new thread.
Explanation: The server cannot initialize due to the Explanation: The server cannot initialize due its
inability to create a new thread of execution. inability to create a new thread of execution.
System action: Server operation continues, but 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 User response: The most likely cause is a lack of
memory. Ensure that sufficient paging space is available memory. Ensure that there is sufficient space for the
for AIX. You may also use SMIT to determine if the Windows paging file. Click on the system icon in the
number of applications is causing a memory shortage. Windows NT control panel and then click on the
You may also decrease the maximum number of virtual memory button. Refer to the online help for
sessions that the server can accept with the instructions on how to increase the amount of virtual
MAXSESSIONS option in the server options file. memory. You may also wish to cut down on the
options file.
session with IP host address -
system/network unreachable.
ANR8212W (AIX) Unable to resolve address for node
name.
session because the remote system or network is
unreachable. Explanation: The server attempts to obtain a TCP/IP
address for the indicated node name. The attempt is
unsuccessful.
System action: The attempt to communicate with the
indicated node fails. Server operation continues.
TCP/IP. Also, ensure that necessary gateways and
routers are functioning properly. User response: Ensure that the node name is properly
specified and that it is accessible over the network. Use
the TCP/IP ping command for this purpose.
session with IP host address -
system/network unreachable. ANR8212E (HP-UX) Unable to establish TCP/IP
session with IP host address - connect
failed; error error code.
session because the remote system or network is
unreachable. Explanation: The server is unable to establish a
session because of a connection error.
system is operational and is properly configured to run User response: Ensure that the specified remote
TCP/IP. Also, ensure that necessary gateways and system is operational and is properly configured to run
routers are functioning properly. TCP/IP.
ANR8211E (Solaris) Unable to establish TCP/IP ANR8212E (Linux) 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
routers are functioning properly.

ANR8212E (Solaris) ANR8214E (HP-UX)

ANR8212E (Solaris) Unable to establish TCP/IP
TCP/IP.
session with IP host address - connect
failed; error error code.
ANR8213E (Solaris) 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.
System action: The session with the remote system is
TCP/IP.
ended.
ANR8212W (Windows) Unable to resolve address for
node name.
TCP/IP.
Explanation: The server attempts to obtain a TCP/IP
ANR8213W (Windows) Session open with node name
unsuccessful.
timed out.
Explanation: The server attempts to contact the
indicated node name. The attempt is unsuccessful.
User response: Ensure that the node name is properly
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
ANR8214E (AIX) Session open with IP host address
indicated node name. The attempt is unsuccessful.
failed due to connection refusal.
session because the remote system refused the
User response: Ensure that the node name is properly connection request.
ANR8213E (HP-UX) Session Session identifier aborted
TCP/IP. Ensure that the client options file specifies the
due to send error; error error code.
correct TCPServeraddress and TCPPort of the server
Explanation: The session between the server and the you are attempting to contact.
specified client system experienced a disruptive error
sending data.
ANR8214E (HP-UX) The session stopped when no
System action: The session with the remote system is data was read on socket socket number.
ended.
Explanation: The server is unable to read data on the
User response: Ensure that the specified remote indicated socket. This might be a normal event if either
system is operational and is properly configured to run side of the connection is abruptly ended.
TCP/IP.
continues.
ANR8213E (Linux) Socket Socket identifier aborted due
to send error; error error code.
intentionally stopping either the client or server, no
Explanation: The session between the server and the response is required. Otherwise, ensure that the client
specified client system experienced a fatal error sending and server can communicate through such means as
data. Telnet or FTP applications, which are part of the
TCP/IP suite.
ended.
ANR8214E (Linux) ANR8216W (AIX)
ANR8214E (Linux) Session terminated when no data ANR8215E (HP-UX) Session Session identifier aborted
was read on socket socket number. due to receive error; error error code.
Explanation: The server is unable to read data on the Explanation: The session between the server and the
indicated socket. This may be a normal event if either specified client system experienced a disruptive error
side of the connection is abruptly ended. receiving data.
System action: The session is ended. Server operation System action: The session with the remote system is
continues. ended.
User response: If the session is ended as a result of User response: Ensure that the specified remote
intentionally stopping either the client or server, no system is operational and is properly configured to run
response is required. Otherwise, ensure that the client TCP/IP.
and server can communicate through such means as
Telnet or FTP applications, which are part of the
ANR8215E (Linux) Session Session identifier aborted
TCP/IP suite.
due to receive error; error error code.
Explanation: The session between the server and the
ANR8214E (Solaris) Session terminated when no
specified client system experienced a fatal error
data was read on socket socket number.
receiving data.
indicated socket. This may be a normal event if either
ended.
side of the connection is abruptly ended.
continues.
TCP/IP.
ANR8215E (Solaris) Session Session identifier aborted
response is required. Otherwise, ensure that the client
due to receive error; error error code.
and server can communicate through such means as
Telnet or FTP applications, which are part of the Explanation: The session between the server and the
TCP/IP suite. specified client system experienced a fatal error
receiving data.
ANR8214E (Windows) Session open with IP host System action: The session with the remote system is
address failed due to connection refusal. ended.
Explanation: The server is unable to establish a User response: Ensure that the specified remote
session because the remote system refused the system is operational and is properly configured to run
connection request. TCP/IP.
ANR8215W (Windows) Session open with IP host
address failed as unreachable.
TCP/IP. Ensure that the client options file specifies the Explanation: The server is unable to establish a
correct TCPServeraddress and TCPPort of the server session because the remote system is unreachable.
you are attempting to contact.
ANR8215W (AIX) Session open with IP host address User response: Ensure that the IP host address is
failed as unreachable. properly specified and that it is accessible over the
network. Use the TCP/IP ping command for this
Explanation: The server is unable to establish a purpose.
session because the remote system is unreachable.
System action: Server operation continues. ANR8216W (AIX) The server experienced a TCP/IP
error while sending data on socket socket
User response: Ensure that the IP host address is
number. Reason return code.
properly specified and that it is accessible over the
network. Use the TCP/IP ping command for this Explanation: A communication error occurred on the
purpose. indicated socket. This may be a normal event if either
continues.

ANR8216E (HP-UX) ANR8217W (Solaris)

ANR8217W (AIX) The server experienced a TCP/IP
error while receiving data on socket
action is required. Otherwise, ensure that the client and
socket number. Reason return code.
server can communicate using Telnet or FTP
applications, which are part of the TCP/IP suite. Explanation: A communication error occurred on the
session with IP host address due to thread System action: The session is ended. Server operation
creation error. continues.
Explanation: The server is unable to establish a User response: If the session is ended as a result of
session because of an error creating a thread. intentionally stopping either the client or server, no
User response: Ensure that your system has sufficient applications, which are part of the TCP/IP suite.
paging space to support the current level of system
activities.
ANR8217W (HP-UX) TCP/IP driver is unable to set
the window size to TCPWindowsize for
ANR8216E (Linux) Unable to establish TCP/IP client client. The default value will be
session with IP host address due to thread used.
creation error.
Explanation: The server cannot set the window size
Explanation: The server is unable to establish a for the indicated client to the requested size shown.
session because of an error creating a thread. The server uses the default window size for the
indicated session. There may be a lack of memory for
System action: Server operation continues. TCP/IP buffers.
User response: Ensure that your system has sufficient System action: Server operation continues and the
paging space to support the current level of system session continues with the default window size.
activities.
User response: Retry the session with a smaller
window size in the options file. Issue the QUERY
ANR8216E (Solaris) Unable to establish TCP/IP OPTION command to determine the setting of the
session with IP host address due to thread server TCPWindowsize.
creation error.
Explanation: The server is unable to establish a ANR8217W (Linux) Unable to initialize TCP/IP
session because of an error creating a thread. driver - insufficient memory.
System action: Server operation continues. Explanation: Because the operating system rejects a
User response: Ensure that your system has sufficient memory allocation request, the server cannot start
paging space to support the current level of system communications through TCP/IP.
activities. System action: Server operation continues, but the
ANR8216W (Windows) Error sending data on socket TCP/IP protocol.
socket number. Reason return code. User response: Ensure that sufficient paging space is
Explanation: The server experiences an error return available for Solaris. You may also use ps -ef to
code from TCP/IP while sending data over the determine if the number of applications is causing a
indicated socket. This may be a normal event if either memory shortage. It may be necessary to decrease the
side of the connection is abruptly ended. maximum number of client sessions by changing the
continues.
ANR8217W (Solaris) Unable to initialize TCP/IP
User response: If the session is ended as a result of driver - insufficient memory.
response is required. Otherwise, ensure that the client Explanation: Because the operating system rejects a
and server can communicate through such means as memory allocation request, the server cannot start
Telnet or FTP applications, which are part of the communications through TCP/IP.
TCP/IP suite. System action: Server operation continues, but the
TCP/IP protocol.
User response: Ensure that sufficient paging space is server representative on request.
available for Solaris. You may also use ps -ef to
determine if the number of applications is causing a
ANR8218W (Linux) Unable to resolve address for
memory shortage. It may be necessary to decrease the
node name.
MAXSESSIONS option in the server options file. Explanation: The server attempts to obtain a TCP/IP
unsuccessful.
ANR8217W (Windows) Error receiving data on
socket socket number. Reason return code. System action: The attempt to communicate with the
Explanation: The server experiences an error return
code from TCP/IP while receiving data on the User response: Ensure that the node name is properly
indicated socket. This may be a normal event if either specified and that it is accessible over the network. Use
side of the connection is abruptly ended. the TCP/IP ping command for this purpose.
continues. ANR8218W (Solaris) Unable to resolve address for
node name.
intentionally stopping either the client or server, no Explanation: The server attempts to obtain a TCP/IP
response is required. Otherwise, ensure that the client address for the indicated node name. The attempt is
and server can communicate through such means as unsuccessful.
Telnet or FTP applications, which are part of the
TCP/IP suite. System action: The attempt to communicate with the
ANR8218W (AIX) Session terminated when no data User response: Ensure that the node name is properly
was read on socket socket number. specified and that it is accessible over the network. Use
side of the connection is abruptly ended. ANR8218W (Windows) Session terminated when no
data read on socket socket number.
continues. Explanation: The server cannot read on the indicated
socket. This may be a normal event if either side of the
User response: If the session is ended as a result of connection is abruptly ended.
response is required. Otherwise, ensure that the client System action: The session is ended. Server operation
and server can communicate through such means as continues.
Telnet or FTP applications, which are part of the User response: If the session is ended as a result of
TCP/IP suite. intentionally stopping either the client or server, no
response is required. Otherwise, ensure that the client
ANR8218W (HP-UX) TCP/IP driver is unable to use and server can communicate through such means as
the TCP/IP NODELAY option for client Telnet or FTP applications, which are part of the
client. TCP/IP suite.
Explanation: The server cannot set TCP/IP NODELAY

for the indicated client. The session proceeds with ANR8219W (AIX) TCP/IP driver is unable to accept a
TCP/IP Delay processing in effect. This causes TCP/IP new session with client at address
to buffer data prior to sending it to clients. TCP/IP address due to an error in creating
a new thread.
System action: Server operation continues and the
session continues with the delay processing on. Explanation: The server cannot accept a client session
with the client at the indicated address due to an
User response: Further details for use in contacting inability to create a new thread.
your service representative can be obtained by issuing
the following trace commands from an administrative System action: Server operation continues, the session
session or from the server console (proper request fails.
administrative authority is required): TRACE ENABLE User response: The most likely cause is lack of
TCPINFO TRACE BEGIN tcptrace.out. After a session memory. Ensure that sufficient paging space is available
starts and displays message ANR8218W, issue the for AIX. You may also use SMIT to determine if the
following commands: TRACE FLUSH TRACE END. number of applications is causing a memory shortage.
This will create trace data in file tcptrace.out and will You may also decrease the maximum number of
terminate the trace. This file should be supplied to your

sessions that the server can accept with the memory. Ensure that there is sufficient space for the
MAXSESSIONS option in the server options file. Windows paging file. Click on the system icon in the
Windows NT control panel and then click on the
ANR8219W (HP-UX) Unable to initialize TCP/IP
instructions on how to increase the amount of virtual
driver - insufficient memory.
memory. You may also wish to to cut down on the
Explanation: Because the operating system rejects a maximum number of sessions that the server can
memory allocation request, the server cannot start accept with the MAXSESSIONS option in the server
communications through TCP/IP. options file.

server cannot accept sessions from clients using the ANR8220W (AIX) TCP/IP driver is unable to set the
TCP/IP protocol. window size to TCPWindowsize for client
session. The default value will be used.
available for HP-UX. You may also use SMIT to Explanation: The server cannot set the window size
determine if the number of applications is causing a for the indicated session to the requested size shown or
memory shortage. It may be necessary to decrease the cannot set the rfc1323 attribute when the window size
maximum number of client sessions by changing the is greater than 65535 bytes. The server uses the default
MAXSESSIONS option in the server options file. window size for the indicated session. There may be a
lack of memory for TCP/IP buffers.
ANR8219W (Linux) Unable to establish TCP System action: Server operation continues and the
connection - insufficient memory. session continues with the default window size.
Explanation: The server cannot accept a client session User response: Retry the session with a smaller
due to a memory allocation request failure. window size in the options file. Issue the QUERY
OPTION command to determine the setting of the
System action: Server operation continues, but the server TCPWindowsize.
User response: Ensure that sufficient paging space is ANR8220W (HP-UX) Unable to establish TCP
available for Solaris. You may also use 'swap -l' to connection - insufficient memory.
determine the amount of swap available. You may also
decrease the maximum number of sessions that the Explanation: The server cannot accept a client session
server can accept with the MAXSESSIONS option in due to a memory allocation request failure.
the server options file.
ANR8219W (Solaris) Unable to establish TCP
connection - insufficient memory.
available for HP-UX. You may also use SMIT to
Explanation: The server cannot accept a client session determine if the number of applications is causing a
due to a memory allocation request failure. memory shortage. You may also decrease the maximum
number of sessions that the server can accept with the
System action: Server operation continues, but the MAXSESSIONS option in the server options file.
User response: Ensure that sufficient paging space is ANR8220W (Linux) TCP/IP driver is unable to set
available for Solaris. You may also use 'swap -l' to the window size to TCPWindowsize for
determine the amount of swap available. You may also client client. The default value will be
decrease the maximum number of sessions that the used.
server can accept with the MAXSESSIONS option in
the server options file. 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
ANR8219W (Windows) TCP/IP driver is unable to indicated session. There may be a lack of memory for
accept a new session due to error in TCP/IP buffers.
creating a new thread.
Explanation: The server cannot accept a client session session continues with the default window size.
due to the inability to create a new thread.
System action: Server operation continues, the session window size in the options file. Issue the QUERY
request fails. OPTION command to determine the setting of the
User response: The most likely cause is a lack of server TCPWindowsize.
ANR8220W (Solaris) ANR8221W (Solaris)
ANR8220W (Solaris) TCP/IP driver is unable to set ANR8221I (HP-UX) TCP/IP Version 4 administrative
the window size to TCPWindowsize for driver ready for connection with clients
client client. The default value will be on port port number.
used.
Explanation: The server cannot set the window size administrative clients using the TCP/IP Version 4
for the indicated client to the requested size shown. protocol on the indicated port number.
The server uses the default window size for the
indicated session. There may be a lack of memory for
TCP/IP buffers. User response: None.
session continues with the default window size. ANR8221W (Linux) TCP/IP driver is unable to use
the TCP/IP NODELAY option for client
client.
window size in the options file. Issue the QUERY
OPTION command to determine the setting of the Explanation: The server cannot set TCP/IP NODELAY
server TCPWindowsize. 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 (Windows) TCP/IP driver is unable to
contact node name due to an output System action: Server operation continues and the
socket initialization error. Reason code session continues with delay processing on.
reason code
User response: Further details for use when
Explanation: The server attempts to contact the contacting your service representative can be obtained
indicated node name. The attempt is unsuccessful due by issuing the following trace commands from an
to the inability to initialize a local socket. administrative session or from the console (proper
administrative authority is required): TRACE ENABLE
TCPINFO TRACE BEGIN tcptrace.out. After a session
starts and displays message ANR8221W, issue the
User response: Ensure that TCP/IP is operating following commands: TRACE FLUSH TRACE END.
properly on this node and that it can communicate This will create trace data in file tcptrace.out and will
remotely. Use the TCP/IP ping command for this terminate the trace. This file should be supplied to your
purpose. service representative on request.
ANR8221W (AIX) TCP/IP driver is unable to use the ANR8221W (Solaris) TCP/IP driver is unable to use
TCP/IP NODELAY option for client the TCP/IP NODELAY option for client
client. client.
Explanation: The server cannot set TCP/IP NODELAY Explanation: The server cannot set TCP/IP NODELAY
for the indicated client. The session proceeds with for the indicated client. The session proceeds with
TCP/IP Delay processing in effect. This causes TCP/IP TCP/IP Delay processing in effect. This causes TCP/IP
to buffer data prior to sending it to clients. to buffer data prior to sending it to clients.
System action: Server operation continues and the System action: Server operation continues and the
session continues with the delay processing on. session continues with the delay processing on.
User response: Further details for use in contacting User response: Further details for use in contacting
your service representative can be obtained by issuing your service representative can be obtained by issuing
the following trace commands from an administrative the following trace commands from an administrative
session or from the server console (proper session or from the server console (proper
administrative authority is required): TRACE ENABLE administrative authority is required): TRACE ENABLE
TCPINFO TRACE BEGIN. After a session starts and TCPINFO TRACE BEGIN tcptrace.out After a session
displays message ANR8221W, issue the commands starts and displays message ANR8221W, issue the
TRACE FLUSH TRACE END. This will create trace following commands: TRACE FLUSH TRACE END
data in file tcptrace.out and will terminate the trace. This will create trace data in file tcptrace.out and will
This file should be supplied to your service terminate the trace. This file should be supplied to your
representative on request. service representative on request.

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.
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
administrative authority is required): TRACE ENABLE
ANR8222W (HP-UX) The TCP/IP administrative TCPINFO TRACE BEGIN tcptrace.out After a session
driver was unable to initialize due to starts and displays message ANR8222W, issue the
error using Port port, reason code reason following commands: TRACE FLUSH TRACE END
code. This will create trace data in file tcptrace.out and will
terminate the trace. This file should be supplied to your
Explanation: While initializing TCP/IP service representative on request.
communications for administrative sessions, the server
failed to connect to a master socket to listen for clients.
The reason code is the return code from the TCP/IP ANR8223W (AIX) Unable to connect to remote
bind API. system RemoteSystem due to unexpected
return code ReturnCode
server cannot accept administrative sessions from Explanation: The server was unable to connect to a
clients using the TCP/IP protocol. This also includes remote system due to an unexpected return code from
server-server sessions, storage agent to server sessions, the connect Application Programming Interface.
and library client to server sesssions. Common return code are handled with specific
messages. This return code was unexpected.
using the port number specified in the server options System action: Server operation continues but the
file with the TCPADMINPORT option. If the server was connection to the remote system fails.
brought down and client sessions were active, it can be User response: TCP/IP return code are listed in file
necessary to end the client sessions on the client /usr/include/sys/errno.h and may provide a pointer
systems before the port can be freed. to the underlying problem. /usr/include/sys/errno.h
is part of fileset bos.adt.include.
ANR8223W (HP-UX) The TCP/IP driver is unable to ANR8223W (Windows) Failed to connect to system at
accept a new session with the client at address address port port.
address TCP/IP address, due to an error
Explanation: The server attempted to contact the
in creating a new thread.
indicated node name at the specified port. The attempt
Explanation: The server cannot accept a client session is unsuccessful. The target port is not valid at the target
with the client at the indicated address due to an node.
inability to create a new thread.
System action: Server operation continues, but the indicated node fails. Server operation continues.
session request fails.
User response: Ensure that the node name still has
User response: The cause is probably lack of memory. TCP/IP running and that the client is active in
Ensure that sufficient paging space is available for AIX. SCHEDULE mode. If the server is attempting contact
You might also use SMIT to determine if the number of with the SNMP subagent, ensure that the hostname and
applications is causing a memory shortage. You might port number for the subagent is correct in the server
also decrease the maximum number of sessions that the options file.
server can accept with the MAXSESSIONS option in
the server options file.
ANR8224W (AIX) TCP/IP Administrative driver was
unable to initialize due to error in using
ANR8223W (Linux) TCP/IP driver is unable to accept port port, reason code reason code.
a new session with client at address
TCP/IP address due to an error in creating
a new thread.
has failed to connect to a master socket on which to
Explanation: The server cannot accept a client session listen for clients. The reason code is the return code
with the client at the indicated address due to an from the TCP/IP bind API.
System action: Server operation continues, the session server cannot accept administrative sessions from
request fails. clients using the TCP/IP protocol. This also includes
server to server sessions, storage agent to server
User response: The most likely cause is lack of
sessions, and library client to server sesssions.
memory. Ensure that sufficient paging space is available
for Solaris. You may also use ps -ef to determine if the User response: Ensure that no other application is
number of applications is causing a memory shortage. using the port number specified in the server options
You may also decrease the maximum number of file with the TCPADMINPORT or TCPPORT options. If
sessions that the server can accept with the the server was brought down and client sessions were
MAXSESSIONS option in the server options file. active, it may be necessary to terminate the client
sessions on the client systems before the port can be
freed.
ANR8223W (Solaris) TCP/IP driver is unable to
accept a new session with client at
address TCP/IP address due to an error in ANR8224E (HP-UX) The server is unable to open the
creating a new thread. file due to the system limit .
Explanation: The server cannot accept a client session Explanation: An error occurs when the server
with the client at the indicated address due to an attempts to open a file.
System action: Server operation continues, but files
System action: Server operation continues, the session cannot be opened until the problem is fixed.
request fails.
User response: Use the System Administrator
User response: The most likely cause is lack of Manager (SAM) program to increase the value of the
memory. Ensure that sufficient paging space is available maxfiles parameter. This value determines the
for Solaris. You may also use ps -ef to determine if the maximum number of files a process is allowed to open
number of applications is causing a memory shortage. at one time. For proper server operation, increase the
You may also decrease the maximum number of maxfiles value to at least 512.
sessions that the server can accept with the
ANR8224W (Linux) TCP/IP driver is unable to set
the server master socket. The default
value will be used.

ANR8224W (Solaris) ANR8226E (AIX)
for the socket on which the server listens to the System action: Server operation continues.
requested size shown. The server uses the default
window size for listening for sessions. There may be a
ANR8225W (Linux) TCP/IP Administrative driver
System action: Server operation continues with the
was unable to initialize due to error in
default window size.
using port port, reason code reason code.
User response: Restart the server with a smaller
window size in the options file if necessary. Issue the
QUERY OPTION command to determine the setting of
the server TCPWindowsize.
listen for clients. The reason code is the return code
from the TCP/IP bind API.
ANR8224W (Solaris) TCP/IP driver is unable to set
server cannot accept administrative sessions from
the server master socket. The default
clients using the TCP/IP protocol. This also includes
value will be used.
server to server sessions, storage agent to server
Explanation: The server cannot set the window size sessions, and library client to server sesssions.
for the socket on which the server listens to the
requested size shown. The server uses the default
window size for listening for sessions. There may be a
file with the TCPADMINPORT or TCPPORT options. If
the server was brought down and client sessions were
System action: Server operation continues with the active, it may be necessary to terminate the client
default window size. sessions on the client systems before the port can be
freed.
User response: Restart the server with a smaller
window size in the options file if necessary. Issue the
QUERY OPTION command to determine the setting of ANR8225I (Solaris) TCP/IP Version 4 administrative
the server TCPWindowsize. driver ready for connection with clients
on port port number.
ANR8224W (Windows) TCP/IP Administrative driver Explanation: The server can now accept sessions with
was unable to initialize due to error in administrative clients using the TCP/IP Version 4
using Port port, reason code reason code. protocol on the indicated port number.
Explanation: While initializing TCP/IP System action: Server operation continues.
listen for clients. The reason code is the return code
from the TCP/IP bind API. ANR8225I (Windows) TCP/IP Version 6 driver ready
number.
clients using the TCP/IP protocol. This also includes Explanation: The server can now accept sessions with
server to server sessions, storage agent to server clients using the TCP/IP Version 6 protocol on the
sessions, and library client to server sessions. indicated port number.
User response: Ensure that no other application is System action: Server operation continues.
file with the TCPADMINPORT option. If the server is User response: None.
brought down and then started immediately, you can
be within the TCP/IP one minute timeout period for ANR8226E (AIX) Error errno detecting version of
port reusage. Bring down the server, wait one minute, HBA-API library.
and then restart the server. If that does not work, it
may be necessary to restart Windows. Explanation: The server attempted to determine the
level of the devices.common.IBM.fc.hba-api fileset and
encountered an error.
ANR8225I (AIX) TCP/IP Version 4 administrative
driver ready for connection with clients System action: Server operation continues, but
on port port number. without accurate SAN device mapping.
Explanation: The server can now accept sessions with User response: None.
administrative clients using the TCP/IP Version 4
protocol on the indicated port number.
ANR8226I (Linux) ANR8227W (Windows)
ANR8226I (Linux) TCP/IP Version 4 administrative ANR8227E (AIX) Fileset devices.common.IBM.fc.hba-

driver ready for connection with clients api is not at the required level.
Explanation: The specified fileset is at a level that is
Explanation: The server can now accept sessions with incompatible with TSM operations. Install the latest
administrative clients using the TCP/IP Version 4 maintenance for this fileset if you use SAN devices.
System action: Server operation continues. without accurate SAN device mapping.
ANR8226W (Solaris) TCP/IP Administrative driver ANR8227W (Linux) Unable to connect to remote
was unable to initialize due to error in system RemoteSystem due to unexpected
using port port, reason code reason code. return code ReturnCode
Explanation: The TCP/IP administrative driver was Explanation: The server was unable to connect to a
unable to initialize due to an error in running the BIND remote system due to an unexpected return code from
API to port port, reason code reason code. the connect Application Programming Interface.
Common return code are handled with specific
clients using the TCP/IP protocol. This also includes System action: Server operation continues but the
server to server sessions, storage agent to server connection to the remote system fails.
sessions, and library client to server sesssions.
User response: TCP/IP return code are listed in file
System action: Server operation continues, but the /usr/include/asm/errno.h and may provide a pointer
server cannot accept administrative sessions from to the underlying problem.
clients using the TCP/IP protocol. This also includes
server-server sessions, storage agent to server sessions,
ANR8227W (Solaris) Unable to connect to remote
and library client-server sesssions.
system RemoteSystem due to unexpected
User response: Ensure that no other application is return code ReturnCode
Explanation: The server was unable to connect to a
file with the TCPADMINPORT or TCPPORT options. If
remote system due to an unexpected return code from
the server was brought down and client sessions were
the connect Application Programming Interface.
active, it can be necessary to terminate the client
Common return code are handled with specific
sessions on the client systems before the port can be
freed.
System action: Server operation continues but the
connection to the remote system fails.
ANR8226W (Windows) Unable to initialize
NETBIOS driver on adapter network User response: TCP/IP return code are listed in file
adapter number. /usr/include/sys/errno.h and may provide a pointer
to the underlying problem.
Explanation: The server cannot obtain sufficient
NETBIOS resources to initialize communications on the
indicated network adapter. ANR8227W (Windows) NETBIOS connection
terminated - insufficient memory,
network adapter network adapter number.
server will not accept sessions from clients that use the
NETBIOS protocol. Explanation: The server cannot listen for client
sessions on the specified network adapter due to a
User response: Ensure that NETBIOS is configured on
memory allocation request failure.
the system. Ensure that all NETBIOS resources are not
already in use. If the LAN Server or LAN Requester System action: Server operation continues, but the
application is running, you have NETBIOS configured. sessions will not be accepted on the specified adapter.
In that case, starting the server prior to starting LAN Other network adapters remain unaffected.
Server or LAN Requester may allow the server to
obtain the necessary NETBIOS resources. User response: The most likely cause is a lack of
memory. Ensure that there is sufficient space for the
Windows paging file. Click on the system icon in the


ANR8230I (Linux) TCP/IP Version 6 driver ready for
memory.
number.
ANR8228W (Windows) NETBIOS connection
terminated - server HALT in progress.
Explanation: The server cannot accept a client session indicated port number.
ANR8230I (Solaris) TCP/IP Version 6 driver ready
ANR8229W (Windows) Unable to add server name number.
server name to adapter network adapter
number.
Explanation: The server cannot initialize indicated port number.
communications processing using the NETBIOS
protocol on the indicated network adapter because the
server name cannot be added as a NETBIOS name on User response: None.
the adapter.
System action: Server operation continues, but client ANR8230W (Windows) Insufficient memory to start
sessions from clients using the NETBIOS protocol will NETBIOS session on adapter network
not be accepted on this adapter. Other adapters are not adapter number.
affected.
User response: The most likely cause for this message due to a memory allocation request failure on the
is the presence of another system on the network that specified adapter.
is using the same name for NETBIOS communications.
This may be another server or client or a LAN
Requester node. Changing or adding the
NETBIOSNAME option for this adapter in your server User response: The most likely cause is a lack of
options file and restarting the server may allow this memory. Ensure that there is sufficient space for the
adapter to be used with NETBIOS communications. Windows paging file. Click on the system icon in the
ANR8230I (AIX) TCP/IP Version 6 driver ready for
memory. You may also wish to cut down on the
number.
Explanation: The server can now accept sessions with accept with the MAXSESSIONS or the
clients using the TCP/IP Version 6 protocol on the NETBIOSSESSIONS option, or both, in the server
indicated port number. options file.
ANR8231W (Windows) Unable to create thread to
accept NETBIOS sessions.
Explanation: The server cannot initialize due to the
ANR8230I (HP-UX) The TCP/IP Version 6 driver is
inability to create a new thread of execution.
ready for connection with clients on
port port number. System action: Server operation continues, but
NETBIOS communications is inoperative.
Explanation: The server is now able to accept sessions
with clients using the TCP/IP Version 6 protocol on the User response: The most likely cause is a lack of
indicated port number. memory. Ensure that there is sufficient space for the
User response: None. virtual memory button. Refer to the online help for
ANR8232W (Windows) ANR8234I (AIX)
accept with the MAXSESSIONS or the

ANR8233E (Linux) Unable to acquire local port
NETBIOSSESSIONS option, or both, in the server
information. getaddrinfo return code
options file.
return code.
Explanation: The server or storage agent used the
system getaddrinfo API to determine which TCP/IP
listen for NETBIOS sessions on adapter
protocols could be used. A failure occurred, as
network adapter number.
indicated by the system error code that is shown. The
Explanation: The server cannot initialize due to the server was initializing TCP/IP communications.
inability to create a new thread of execution to monitor
System action: TCP/IP communications is inoperatve.
the indicated network adapter.
User response: System information concerning return
codes from the getaddrinfo system API should be
NETBIOS communications is inoperative on the
consulted. Ensure that TCP/IP networking for either
indicated adapter. Other adapters remain unaffected.
TCP/IP version 4 or version 6 is operating correctly.
User response: The most likely cause is a lack of
ANR8233E (Solaris) Unable to acquire local port
return code.
instructions on how to increase the amount of virtual Explanation: The server or storage agent used the
memory. You may also wish to cut down on the system getaddrinfo API to determine which TCP/IP
maximum number of sessions that the server can protocols could be used. A failure occurred, as
accept with the MAXSESSIONS or the indicated by the system error code that is shown. The
NETBIOSSESSIONS option, or both, in the server server was initializing TCP/IP communications.
options file.
ANR8233E (AIX) Unable to acquire local port
return code.
handle NETBIOS session session number
on adapter network adapter number.
server was initializing TCP/IP communications.
Explanation: The server cannot start a new client
session on the indicated adapter due to an inability to
User response: System information concerning return start a separate thread of execution for the indicated
codes from the getaddrinfo system API should be session.
System action: Server operation continues, but this
ANR8233E (HP-UX) Unable to acquire local port
return code.
Explanation: The server or storage agent used the virtual memory button. Refer to the online help for
system getaddrinfo API to determine which TCP/IP instructions on how to increase the amount of virtual
protocols could be used. A failure occurred, as memory. You may also wish to cut down on the
indicated by the system error code that is shown. The maximum number of sessions that the server can
server was initializing TCP/IP communications. accept with the MAXSESSIONS or the
NETBIOSSESSIONS option, or both, in the server
options file.
ANR8234I (AIX) TCP/IP Version 6 administrative
driver ready for connection with clients

ANR8234I (HP-UX) ANR8236W (Windows)
protocol on the indicated port number. parameter of the server options file or, if this option is
not specified, by the MAXSESSIONS option.
maximum number of NETBIOS sessions is limited to
the number of sessions that are acquired.
ANR8234I (HP-UX) The TCP/IP Version 6
User response: Ensure that the required number of
administrative driver is ready for
NETBIOS resources are not already in use. If the LAN
Server or LAN Requester application is running, you
number.
have NETBIOS configured. In that case, starting the
Explanation: The server can now accept sessions with server prior to starting LAN Server or LAN Requester
administrative clients using the TCP/IP Version 6 may allow the server to obtain the requested NETBIOS
protocol on the indicated port number. resources.

ANR8236W (Windows) Failure while listening for
User response: None. NETBIOS sessions on adapter network
adapter number, NETBIOS listen return
ANR8234I (Linux) TCP/IP Version 6 administrative code=listen return code.
driver ready for connection with clients Explanation: The server cannot listen for NETBIOS
on port port number. sessions on the indicated adapter. The indicated listen
Explanation: The server can now accept sessions with return code was received from the NETBIOS listen API.
administrative clients using the TCP/IP Version 6 If the return code is 24, (hex 18), the listen is retried.
protocol on the indicated port number. System action: Server operation continues. If the
System action: Server operation continues. return code is 24 (hex 18), a new listen is setup because
return code 24 indicates a temporary failure. Otherwise,
User response: None. no additional NETBIOS sessions will start using the
indicated adapter until the problem is corrected and the
ANR8234I (Solaris) TCP/IP Version 6 administrative server is restarted.
driver ready for connection with clients User response: A NETBIOS listen failure is an
on port port number. indication of a network problem, an adapter problem,
Explanation: The server can now accept sessions with or a NETBIOS configuration problem. The following
administrative clients using the TCP/IP Version 6 system configuration and system environment listen
protocol on the indicated port number. return codes (in hex) and resolution actions for a listen
failure are found in the IBM Local Area Network
System action: Server operation continues. Technical Reference:
Return Code Description
11 The local session table is full. The
ANR8234I (Windows) TCP/IP Version 6 maximum number of sessions are in
administrative driver ready for use. Change NETBIOS configuration to
connection with clients on port port increase the maximum number of
number. sessions.
19 Name conflict. Ensure that the Server
NETBIOS name is not in use elsewhere
on the network.
22 There are too many commands pending.
System action: Server operation continues. The maximum number of sessions are in
use. Change NETBIOS configuration to
increase the maximum number of
sessions.
ANR8235W (Windows) Requested number of 35 The operating system resources are
NETBIOS sessions are not available on exhausted. A reboot is probably
adapter network adapter number, required.
proceeding with available sessions.
Explanation: The server cannot acquire the requested
number of NETBIOS sessions for the indicated adapter.
The server attempts to acquire the number of NETBIOS
sessions as indicated by the NETBIOSSESSIONS
ANR8237E (Windows) ANR8266W (Windows)

ANR8237E (Windows) Unable to acquire local port
options file.
return code.
ANR8263W (Windows) Error sending data on Named
Pipes, session session number.WriteFile
Return code is return code.
server was initialize TCP/IP communications. Explanation: The server experiences an error return
code from the WriteFile Windows NT API while
writing data to Named Pipes over the indicated
User response: System information concerning return session. This may be a normal event if either side of the
codes from the getaddrinfo system API should be connection is abruptly ended.
continues.
ANR8260I (Windows) Named Pipes driver ready for
connection with clients.
with clients using the Named Pipes protocol.
ANR8264W (Windows) Error reading data on Named
System action: Server operation continues. Pipes, session session number. ReadFile
return code is return code.
code from the ReadFile Windows API while reading
ANR8261W (Windows) Named Pipes connection
data from Named Pipes in the indicated session. This
terminated - insufficient memory.
may be a normal event if either side of the connection
Explanation: The server cannot accept a client session is ended abruptly.
due to a memory allocation request failure.
System action: Server operation continues. Named continues.
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

code when trying to complete a connection on the User response: Consider the reason text and take
indicated Named Pipes name for Named Pipes appropriate action. Stop and restart the server to
communication with a client. The return code shown is reenable Named Pipes communications.
returned by the Windows ConnectNamedPipe API.
System action: The session is ended. Server operation ANR8273I (Windows) Shared memory driver ready
continues. Named Pipes communications is inoperative. for connection with clients on port port
number.
User response: A system problem may be preventing
use of Named Pipes. Stop and restart the server to Explanation: The server is now able to accept sessions
reenable Named Pipes communications. with clients using the shared memory protocol on the
indicated port.
ANR8267W (Windows) Error initializing a security System action: Server operation continues.
descriptor for Named Pipes Named Pipes
name, reason: System message.
ANR8274W (Windows) Shared memory
code when trying to initialize the indicated Named
communications driver is terminating
Pipe for Named Pipes communication with a client.
due to error in creating a new thread.
The reason shown is returned by the Windows
FormatMessage API. Explanation: The server cannot initialize due to the
inability to create a new thread of execution.
continues. Named Pipes communications is inoperative. System action: Server operation continues, but shared
memory communications is inoperative.
User response: Administrator Privileges are required.
Login using an account wit h Administrator privileges User response: The most likely cause is a lack of
and restart the server to reenable Named Pipes memory. Ensure that there is sufficient space for the
communications. Windows paging file. Click on the system icon in the
ANR8268W (Windows) Named Pipe communications
were not enabled due to an error
memory.
looking up the following Windows
group name: Windows group name. Use
the Windows User manager to add the ANR8275W (Windows) Shared memory connection
specified group. Members of the group terminated - insufficient memory.
will then use Windows unified logon to
access the server over Named pipes. Explanation: The server cannot accept a client session
code when trying to initialize the indicated Named System action: Server operation continues. Shared
Pipe for Named Pipes communication with a client. memory communications is inoperative.
The system could not find the Windows Account name User response: The most likely cause is a lack of
specified in the server options file. memory. Ensure that there is sufficient space for the
System action: The session is ended. Server operation Windows paging file. Click on the system icon in the
continues. Named Pipes communications is inoperative. Windows NT control panel and then click on the
User response: To use Windows unified logon specify instructions on how to increase the amount of virtual
the name of a valid Windows account or group name. memory. You may also wish to cut down on the
Restart the server to reenable Named Pipes maximum number of sessions that the server can
communications. accept with the MAXSESSIONS option in the server
options file.
ANR8269W (Windows) Error opening Named Pipe
Named Pipes name, reason: System message. ANR8276W (Windows) Shared memory connection
terminated - unable to initialize. Key
channel key, Reason: reason code.
code when trying to open the indicated Named Pipe
name for Named Pipes communication with a client. Explanation: The server cannot accept a client session
The reason shown is returned by the Windows due being unable to initialize shared memory.
FormatMessage API.
System action: Server operation continues. Shared
System action: The session is ended. Server operation memory communications are inoperative.
continues. Named Pipes communications is inoperative.
ANR8277E (Windows) ANR8284E (AIX)
User response: Try a different shared memory session. TCP/IP is also in use for client sessions, ensure that the
same port number is not specified for TCP/IP
communications and SNMP communications. This may
ANR8277E (Windows) Shared memory unable to
be done by issuing the TCP/IP netstat command.
initialize - Port: shm port number, Reason:
reason code.
ANR8283W (Linux) SNMP driver unable to initialize
due to error in BINDing to Port port,
because it could not intialize a communication channel.
reason code reason code.
Make sure no other server or storage agent running on
the same machine is using the same shm port number. Explanation: While initializing TCP/IP
communications, the server has failed to connect to a
System action: Server operation continues. Shared
master TCP/IP socket on which to listen to SNMP
memory communications are inoperative.
subagents. The reason code is the return code from the
User response: Try a different shared memory session. TCP/IP bind API.
ANR8282I (HP-UX) SNMP driver ready for server cannot accept sessions from SNMP subagents to
connection with subagent on port port run macro commands.
number.
Explanation: The server can now accept sessions with using the port number specified in the server options
SNMP subagents on the indicated port number. file with the PORT option. If TCP/IP is also in use for
client sessions, ensure that the same port number is not
System action: Server operation continues. specified for TCP/IP and SNMP communications.
ANR8283W (Solaris) SNMP driver unable to
ANR8282I (Linux) SNMP driver ready for connection initialize due to error in BINDing to
with subagent on port port number. Port port, reason code reason code.
Explanation: The server can now accept sessions with Explanation: While initializing TCP/IP
SNMP subagents on the indicated port number. communications, the server has failed to connect to a
System action: Server operation continues. subagents. The reason code is the return code from the
User response: None. TCP/IP bind API.
ANR8282I (Solaris) SNMP driver ready for server cannot accept sessions from SNMP subagents to
connection with subagent on port port run macro commands.
number. User response: Ensure that no other application is
Explanation: The server can now accept sessions with using the port number specified in the server options
SNMP subagents on the indicated port number. file with the PORT option. If TCP/IP is also in use for
System action: Server operation continues. specified for TCP/IP communications and SNMP
User response: None. communications.
ANR8283W (HP-UX) SNMP driver unable to ANR8284E (AIX) The Shared Memory
initialize due to error in using Port port, Communications Protocol could not
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.
subagents. The reason code is the return code from the System action: Server operation continues without
TCP/IP bind API. Shared Memory Communications.
System action: Server operation continues, but the User response: Examine previous error messages for
server cannot accept sessions from SNMP subagents to the cause of the failure.
run macro commands.
file with the SNMPSUBAGENT PORT option. If

ANR8284E (HP-UX) ANR8286W (HP-UX)
ANR8284E (HP-UX) The Shared Memory ANR8285I (Linux) Shared Memory driver ready for
Communications Protocol could not connection with clients on port port
initialize.
Explanation: The server was unable to initialize the with clients using the Shared Memory protocol.
Shared Memory Communications Protocol due to an
error.
System action: Server operation continues without
Shared Memory Communications.
ANR8285I (Solaris) Shared Memory driver ready for
User response: Examine previous error messages for
the cause of the failure.
with clients using the Shared Memory protocol.
ANR8284E (Linux) The Shared Memory
Communications Protocol could not System action: Server operation continues.
initialize.
Explanation: The server was unable to initialize the
Shared Memory Communications Protocol due to an
error. ANR8285I (Windows) SNMP driver ready for
connection with subagent on port port
System action: Server operation continues without number.
Shared Memory Communications.
User response: Examine previous error messages for SNMP subagents on the indicated port number.
the cause of the failure.
ANR8284E (Solaris) The Shared Memory User response: None.

Communications Protocol could not
initialize. ANR8286W (AIX) Unable to initialize Shared
Explanation: The server was unable to initialize the Memory driver - insufficient memory.
Shared Memory Communications Protocol due to an Explanation: Because the operating system rejected a
error. memory allocation request, the server cannot start
System action: Server operation continues without communications through the Shared Memory protocol.
Shared Memory Communications. System action: Server operation continues, but the
User response: Examine previous error messages for server cannot accept sessions from clients using the
the cause of the failure. Shared Memory protocol.
ANR8285I (AIX) Shared Memory driver ready for space for AIX. You may also use SMIT to determine if
connection with clients on port port the number of applications is causing a memory
shortage. It may be necessary to cut down on the
Explanation: The server is now able to accept sessions maximum number of client sessions by changing the
with clients using the Shared Memory protocol. MAXSESSIONS option in the server options file.
ANR8286W (HP-UX) Unable to initialize Shared
Memory driver - insufficient memory.
Explanation: Because the operating system rejected a
ANR8285I (HP-UX) Shared Memory driver ready for
memory allocation request, the server cannot start
communications through the Shared Memory protocol.
with clients using the Shared Memory protocol.
System action: Server operation continues. Shared Memory protocol.
User response: None. User response: Ensure that there is sufficient paging
space for HP-UX. You may also use SAM to determine
shortage. It may be necessary to cut down on the
ANR8286W (Linux) ANR8287W (Solaris)

ANR8287W (AIX) Unable to initialize Shared
Memory driver - error creating acceptor
ANR8286W (Linux) Unable to initialize Shared socket. Reason code reason code.
Explanation: Because TCP/IP rejected a request for a
Explanation: Because the operating system rejected a socket on which to listen, the server cannot start
memory allocation request, the server cannot start communications through Shared Memory.
System action: Server operation continues, but the server cannot accept sessions from clients using the
server cannot accept sessions from clients using the Shared Memory protocol.
Shared Memory protocol.
User response: If TCP/IP is not started, use the HALT
User response: Ensure that there is sufficient swap command from any server prompt to stop the server,
space for Solaris. It may be necessary to cut down on and restart it.
the maximum number of client sessions by changing
the MAXSESSIONS option in the server options file.
ANR8287W (HP-UX) Unable to initialize Shared
ANR8286W (Solaris) Unable to initialize Shared socket. Reason code reason code.
Explanation: Because the operating system rejected a socket on which to listen, the server cannot start
memory allocation request, the server cannot start communications through Shared Memory.
System action: Server operation continues, but the server cannot accept sessions from clients using the
server cannot accept sessions from clients using the Shared Memory protocol.
User response: Ensure that there is sufficient swap command from any server prompt to stop the server,
space for Solaris. It may be necessary to cut down on and restart it.
the maximum number of client sessions by changing
the MAXSESSIONS option in the server options file.
ANR8287W (Linux) Unable to initialize Shared
ANR8286W (Windows) SNMP driver unable to socket. Reason code reason code.
initialize due to error in BINDing to
Port port, reason code reason code.
socket on which to listen, the server cannot start
Explanation: While initializing TCP/IP communications through Shared Memory.
communications, the server has failed to connect to a
subagents. The reason code is the return code from the
TCP/IP bind API.
command from any prompt to stop the server, and
server cannot accept sessions from SNMP subagents to
restart it.
run macro commands.
ANR8287W (Solaris) Unable to initialize Shared
file with the PORT option. If TCP/IP is also in use for
socket. Reason code reason code.
specified for TCP/IP communications and SNMP Explanation: Because TCP/IP rejected a request for a
communications. This may be done by issuing the socket on which to listen, the server cannot start
TCP/IP netstat -s command. If the server is brought communications through Shared Memory.
down and then started immediately, you may be within
the TCP/IP one minute timeout period for port
reusage. Bring down the sever, wait one minute, and
then restart the server. If that does not work, it may be
necessary to restart Windows. User response: If TCP/IP is not started, use the HALT
command from any server prompt to stop the server,
and restart it.

ANR8288W (AIX) ANR8289W (Solaris)
the maximum number of sessions that the server can

ANR8288W (AIX) Unable to establish Shared
Memory connection - insufficient
options file.
memory.
ANR8289W (AIX) Shared Memory driver is
terminating due to error in creating a
System action: Server operation continues, but the new thread.
User response: Ensure that there is sufficient paging inability to create a new thread of execution.
space for AIX. You may also use SMIT to determine if
System action: Server operation continues, but Shared
the number of applications is causing a memory
Memory communications is inoperative.
shortage. You may also wish to cut down on the
maximum number of sessions that the server can User response: The most likely cause is a lack of
accept with the MAXSESSIONS option in the server memory. Ensure that there is sufficient paging space for
options file. AIX. You may also use SMIT to determine if the
number of applications is causing a memory shortage.
You may also wish to cut down on the maximum
ANR8288W (HP-UX) Unable to establish Shared
memory.
ANR8289W (HP-UX) Shared Memory driver is
User response: Ensure that there is sufficient paging inability to create a new thread of execution.
space for HP-UX. You may also use SAM to determine
shortage. You may also wish to cut down on the
maximum number of sessions that the server can User response: The most likely cause is a lack of
accept with the MAXSESSIONS option in the server memory. Ensure that there is sufficient paging space for
options file. HP-UX. You may also use SAM to determine if the
number of applications is causing a memory shortage.
You may also wish to cut down on the maximum
ANR8288W (Linux) Unable to establish Shared
memory.
ANR8289W (Linux) Shared Memory driver is
User response: Ensure that there is sufficient swap inability to create a new thread of execution.
space for Solaris. You may also wish to cut down on
the maximum number of sessions that the server can
options file. 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
ANR8288W (Solaris) Unable to establish Shared
memory.
options file.
ANR8289W (Solaris) Shared Memory driver is
System action: Server operation continues, but the terminating due to error in creating a
session request for this session fails. new thread.
User response: Ensure that there is sufficient swap Explanation: The server cannot initialize due to the
space for Solaris. You may also wish to cut down on inability to create a new thread of execution.
ANR8290W (AIX) ANR8291W (Linux)
System action: Server operation continues, but Shared System action: The session is ended. Server operation
Memory communications is inoperative. continues.
User response: The most likely cause is a lack of User response: If the session is ended as a result of
memory. Ensure that there is sufficient swap space for intentionally stopping either the client or server, no
Solaris. You may also wish to cut down on the response is required.
ANR8290I (Windows) IPX/SPX driver ready for
options file.
connection with clients on socket IPX
socket number.
ANR8290W (AIX) Error sending data through Shared
Memory. Reason return code.
with clients using the IPX/SPX protocol on the
Explanation: The server experienced an error return indicated socket number.
code while sending data through shared memory. This
may be a normal event if either side of the connection
is abruptly ended. User response: None.
continues. ANR8291W (AIX) Error receiving data through
Shared Memory. Reason return code.
intentionally stopping either the client or server, no Explanation: The server experienced an error return
response is required. 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 (HP-UX) Error sending data through
Shared Memory. Reason return code. System action: The session is ended. Server operation
continues.
code while sending data through shared memory. This User response: If the session is ended as a result of
may be a normal event if either side of the connection intentionally stopping either the client or server, no
is abruptly ended. response is required.
continues. ANR8291W (HP-UX) Error receiving data through
ANR8290W (Linux) Error sending data through
continues.
continues. ANR8291W (Linux) Error receiving data through
ANR8290W (Solaris) Error sending data through
continues.

ANR8291W (Solaris) Error receiving data through ANR8292W (Linux) Session terminated when no data
Shared Memory. Reason return code. was read through Shared Memory.
Explanation: The server experienced an error return Explanation: The server is unable to read data from
code while receiving data through the Shared Memory Shared Memory. This may be a normal event if either
protocol. This may be a normal event if either side of side of the connection is abruptly ended.
System action: The session is ended. Server operation continues.
continues.
User response: If the session is ended as a result of intentionally stopping either the client or server, no
intentionally stopping either the client or server, no response is required.
ANR8292W (Solaris) Session terminated when no
ANR8291W (Windows) Unable to bind to IPX/SPX data was read through Shared Memory.
master socket. Return code = return code.
Explanation: The server is unable to read data from
Explanation: The server cannot initiate Shared Memory. This may be a normal event if either
communications on the socket number designated for side of the connection is abruptly ended.
its use.
System action: Server operation continues, but continues.
communications using the IPX/SPX protocol is
inoperative.
User response: Ensure that SPX has been configured response is required.
to run on this system through the requester
configuration program. Ensure that there is no other
ANR8292W (Windows) IPX/SPX connection
instance of the server running on the same system that
terminated - insufficient memory.
is using the same socket number. This is likely to be the
case if the return code is zero. Also ensure that the Explanation: The server cannot accept a client session
number of SPX sessions (as specified in your NET.CFG due to a memory allocation request failure.
file) has not been exceeded through other applications
using the IPX/SPX protocol. System action: Server operation continues.
ANR8292W (AIX) Session terminated when no data memory. Ensure that there is sufficient space for the
was read through Shared Memory. Windows paging file. Click on the system icon in the
Explanation: The server is unable to read data from virtual memory button. Refer to the online help for
Shared Memory. This may be a normal event if either instructions on how to increase the amount of virtual
side of the connection is abruptly ended. memory. You may also wish to cut down on the
continues.
options file.
ANR8293W (AIX) Shared Memory driver unable to
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
Explanation: The server is unable to read data from with TCP/IP.
Shared Memory. This may be a normal event if either
System action: The session is ended. Server operation Shared Memory protocol.
continues.
User response: Ensure that TCP/IP has been started
User response: If the session is ended as a result of and is active on your system. You may issue the
intentionally stopping either the client or server, no TCP/IP ping command to your own address to verify
response is required. that TCP/IP is both started and active.
ANR8293W (HP-UX) ANR8294W (Solaris)
User response: Ensure that IPX/SPX is still running

ANR8293W (HP-UX) Shared Memory driver unable
properly and that it has not been intentionally or
to initialize due to socket initialization
unintentionally stopped. This may be done by using
error.
the getipxad command to determine if an endpoint can
Explanation: While initializing Shared Memory still be opened and bound; also determine if you can
communications, the server failed to set up an interface still connect to a NetWare server.
with TCP/IP.
System action: Server operation continues, but the ANR8294W (AIX) Shared Memory session unable to
server cannot accept sessions from clients using the initialize.
Explanation: While initializing a Shared Memory
User response: Ensure that TCP/IP has been started communications session, an error occurred during
and is active on your system. You may issue the initial setup.
TCP/IP ping command to your own address to verify
session is terminated.
User response: Contact your service representative for
ANR8293W (Linux) Shared Memory driver unable to
assistance in resolving the error.
error.
ANR8294W (HP-UX) Shared Memory session unable
to initialize.
with TCP/IP. Explanation: While initializing a Shared Memory
communications session, an error occurred during
initial setup.
Shared Memory protocol. System action: Server operation continues, but the
and is active on your system. You may issue the User response: Contact your service representative for
TCP/IP ping command to your own address to verify assistance in resolving the error.
ANR8294W (Linux) Shared Memory session unable

ANR8293W (Solaris) Shared Memory driver unable to initialize.
to initialize due to socket initialization
error. Explanation: While initializing a Shared Memory
Explanation: While initializing Shared Memory initial setup.
with TCP/IP. System action: Server operation continues, but the
server cannot accept sessions from clients using the User response: Contact your service representative for
Shared Memory protocol. assistance in resolving the error.

and is active on your system. You may issue the ANR8294W (Solaris) Shared Memory session unable
TCP/IP ping command to your own address to verify to initialize.
that TCP/IP is both started and active. Explanation: While initializing a Shared Memory
ANR8293W (Windows) IPX/SPX driver unable to initial setup.
initialize due to error in LISTENing on System action: Server operation continues, but the
the master socket, return code = return session is terminated.
code.
Explanation: While attempting to listen for session assistance in resolving the error.
requests from clients using IPX/SPX, the server
encountered an error.
using the IPX/SPX protocol.

ANR8294W (Windows) Unable to establish IPX/SPX ANR8295W (Linux) Shared Memory driver unable to
connection - accept error. Return code = initialize due to error in BINDing to
tli error. Port port, reason code reason code.
Explanation: The server cannot accept a client session Explanation: While initializing Shared Memory
due to a failure in accepting the connection from communications, the server failed to connect to a
IPX/SPX. master socket on which to listen for clients. The reason
code is the return code from the TCP/IP bind API.
System action: Server operation continues, but this
session request fails. System action: Server operation continues, but the
User response: Ensure that SPX has been configured
to run on this system through the requester
configuration program. Ensure that there is no other User response: Ensure that no application is using the
instance of the server running on the same system that port number specified in the server options file with
is using the same socket number. Also ensure that the the SHMPORT option by issuing the TCP/IP netstat
number of SPX sessions has not been exceeded through command. If the server was brought down and client
other applications using the IPX/SPX protocol, such as sessions were active, it may be necessary to terminate
NetWare applications. the client sessions on the client systems before the port
can be freed.
initialize due to error in BINDing to ANR8295W (Solaris) Shared Memory driver unable
Port port, reason code reason code. to initialize due to error in BINDing to
Port port, reason code reason code.
communications, the server failed to connect to a Explanation: While initializing Shared Memory
master socket on which to listen for clients. The reason communications, the server failed to connect to a
code is the return code from the TCP/IP bind API. master socket on which to listen for clients. The reason
code is the return code from the TCP/IP bind API.
server cannot accept sessions from clients using the System action: Server operation continues, but the
Shared Memory protocol. server cannot accept sessions from clients using the
User response: Ensure that no application is using the
port number specified in the server options file with User response: Ensure that no application is using the
the SHMPORT option by issuing the TCP/IP netstat port number specified in the server options file with
command. If the server was brought down and client the SHMPORT option by issuing the TCP/IP netstat
sessions were active, it may be necessary to terminate command. If the server was brought down and client
the client sessions on the client systems before the port sessions were active, it may be necessary to terminate
can be freed. the client sessions on the client systems before the port
can be freed.
ANR8295W (HP-UX) Shared Memory driver unable
to initialize due to error in using Port ANR8295W (Windows) Error sending data on session
port, reason code reason code. session number. Reason return code.
Explanation: While initializing Shared Memory Explanation: The server experiences an error return
communications, the server failed to connect to a code from IPX/SPX while sending data on the
master socket on which to listen for clients. The reason indicated session. This may be a normal event if either
code is the return code from the TCP/IP bind API. side of the connection is abruptly ended.
System action: Server operation continues, but the System action: The session is ended. Server operation
server cannot accept sessions from clients using the continues.
User response: Ensure that no application is using the intentionally stopping either the client or server, no
port number specified in the server options file with response is required. Otherwise, ensure that IPX/SPX is
the SHMPORT option by issuing the TCP/IP netstat still active.
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
initialize due to error in LISTENing on
can be freed.
the specified Port, reason code reason
code.
Explanation: While attempting to listen for session
requests from clients using TCP/IP, TCP/IP returns an System action: Server operation continues, but the
error. The reason code is the return code from the server cannot accept additional sessions from clients
TCP/IP listen API. using the Shared Memory protocol.
System action: Server operation continues, but the User response: Ensure that TCP/IP is running
server cannot accept additional sessions from clients properly by issuing the TCP/IP netstat -s and ping
using the Shared Memory protocol. commands to other nodes on your network. It may be
possible to bring the server down and restart it to
allow additional client sessions to start.
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
allow additional client sessions to start. terminating due to error in accepting a
new session, reason code reason code.
ANR8296W (HP-UX) Shared Memory driver unable Explanation: While attempting to accept a session
to initialize due to error in LISTENing request from a client using the Shared Memory
on the specified Port, reason code reason protocol, TCP/IP returns an error. The reason code is
code. the return code from the TCP/IP accept API.
Explanation: While attempting to listen for session System action: Server operation continues, but the
requests from clients using TCP/IP, TCP/IP returns an server cannot accept additional sessions from clients
error. The reason code is the return code from the using the Shared Memory protocol.
TCP/IP listen API.
System action: Server operation continues, but the properly. This may be done by issuing the TCP/IP
server cannot accept additional sessions from clients netstat -s and ping commands to other nodes on your
using the Shared Memory protocol. network. It may be possible to bring the server down
commands to other nodes on your network. It may be ANR8297W (HP-UX) Shared Memory driver is
possible to bring the server down and restart it to terminating due to error in accepting a
allow additional client sessions to start. new session, reason code reason code.
ANR8296W (Linux) Shared Memory driver unable to request from a client using the Shared Memory
initialize due to error in LISTENing on protocol, TCP/IP returns an error. The reason code is
the specified Port, reason code reason the return code from the TCP/IP accept API.
code.
Explanation: While attempting to listen for session server cannot accept additional sessions from clients
requests from clients using TCP/IP, TCP/IP returns an using the Shared Memory protocol.
TCP/IP listen API.
properly. This may be done by issuing the TCP/IP
System action: Server operation continues, but the netstat -s and ping commands to other nodes on your
server cannot accept additional sessions from clients network. It may be possible to bring the server down
using the Shared Memory protocol. and restart it to allow additional client sessions to start.
properly by issuing the TCP/IP netstat -s and ping ANR8297W (Linux) Shared Memory driver is
commands to other nodes on your network. It may be terminating due to error in accepting a
possible to bring the server down and restart it to new session, reason code reason code.
allow additional client sessions to start.
request from a client using the Shared Memory
ANR8296W (Solaris) Shared Memory driver unable protocol, TCP/IP returns an error. The reason code is
to initialize due to error in LISTENing the return code from the TCP/IP accept API.
on the specified Port, reason code reason
code.
Explanation: While attempting to listen for session using the Shared Memory protocol.
requests from clients using TCP/IP, TCP/IP returns an
properly. This may be done by issuing the TCP/IP
TCP/IP listen API.
netstat -s and ping commands to other nodes on your

ANR8297W (Solaris) ANR8299W (HP-UX)
network. It may be possible to bring the server down System action: The session is ended. Server operation
and restart it to allow additional client sessions to start. continues.
ANR8297W (Solaris) Shared Memory driver is intentionally stopping either the client or server, no
terminating due to error in accepting a action is required. Otherwise, ensure that the client and
new session, reason code reason code. server can communicate using Telnet or FTP
applications, which are part of the TCP/IP suite.
request from a client using the Shared Memory
protocol, TCP/IP returns an error. The reason code is ANR8298W (Solaris) The server experienced a
the return code from the TCP/IP accept API. TCP/IP error while writing data on
socket socket number. Reason return code.
server cannot accept additional sessions from clients Explanation: An error occurred during negotiation for
using the Shared Memory protocol. a shared memory session. This may be a normal event
if either side of the connection is abruptly ended.
properly. This may be done by issuing the TCP/IP System action: The session is ended. Server operation
netstat -s and ping commands to other nodes on your continues.
network. It may be possible to bring the server down
ANR8298W (AIX) The server experienced a TCP/IP server can communicate using Telnet or FTP
error while writing data on socket socket applications, which are part of the TCP/IP suite.
Explanation: An error occurred during negotiation for ANR8299W (AIX) The server experienced a TCP/IP
a shared memory session. This may be a normal event error while reading data on socket socket
if either side of the connection is abruptly ended. number. Reason return code.
System action: The session is ended. Server operation Explanation: An error occurred during negotiation for
continues. a shared memory session. This may be a normal event
if either side of the connection is abruptly ended or if
the client is configured incorrectly.
action is required. Otherwise, ensure that the client and System action: The session is ended. Server operation
server can communicate using Telnet or FTP continues.
ANR8298W (HP-UX) The server experienced a action is required. Otherwise, ensure that the client and
TCP/IP error while writing data on server can communicate using Telnet or FTP
socket socket number. Reason return code. applications, which are part of the TCP/IP suite.
Explanation: An error occurred during negotiation for Check the client options file to ensure that the server's
a shared memory session. This may be a normal event shared memory port is set up and is not being
if either side of the connection is abruptly ended. 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
continues.
memory communications.
ANR8299W (HP-UX) The server experienced a
TCP/IP error while reading 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
ANR8298W (Linux) The server experienced a TCP/IP
error while writing data on socket socket
continues.
if either side of the connection is abruptly ended. User response: If the session is ended as a result of
ANR8299W (Linux) ANR8303E

ANR8300E I/O error on library library name
(OP=internal code, CC=internal code,
KEY=internal code, ASC=internal code,
ASCQ=internal code, SENSE= sense data,
Check the client options file to ensure that the server's Description=error description). Refer to
shared memory port is set up and is not being the Tivoli Storage Manager
confused with the server's TCP/IP port. The shared documentation on I/O error code
memory port is a TCP/IP port that the server uses to descriptions.
initiate communications, then switches to shared
Explanation: An I/O error has occurred while
operating on the specified library.
ANR8299W (Linux) The server experienced a TCP/IP
error while reading data on socket socket User response: Ensure that the DEVICE parameter
number. Reason return code. associated with the library was identified correctly in
the DEFINE PATH command and that the library is
currently powered on and ready. If the library has an
access door, make sure it is closed. The library
reference manual usually contains tables that explain
the values of the KEY, ASC, and ASCQ fields.
continues.
ANR8301E I/O error on library library name
User response: If the session is ended as a result of (OP=internal code, SENSE=internal code).
operating on the specified library.
applications, which are part of the TCP/IP suite. System action: The operation fails.
Check the client options file to ensure that the server's User response: Ensure that the DEVICE parameter
shared memory port is set up and is not being associated with the library was identified correctly in
confused with the server's TCP/IP port. The shared the DEFINE PATH command and that the library is
memory port is a TCP/IP port that the server uses to currently powered on and ready. If the library has an
initiate communications, then switches to shared access door, make sure it is closed.
ANR8302E I/O error on drive drive name with
ANR8299W (Solaris) The server experienced a volume volume name (OP=internal code,
TCP/IP error while reading data on Error Number=internal code, CC=internal
socket socket number. Reason return code. code, rc = return code, KEY= internal code,
ASC=internal code, ASCQ= internal code,
SENSE=sense data, Description=error
description). Refer to the Tivoli Storage
Manager documentation on I/O error
code descriptions.
continues.
operating on the specified drive.
action is required. Otherwise, ensure that the client and User response: Ensure that the DEVICE parameter
server can communicate using Telnet or FTP associated with the drive was identified correctly in the
applications, which are part of the TCP/IP suite. 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.
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 ANR8303E I/O error on drive drive name
memory communications. (OP=internal code, SENSE=internal code).
operating on the specified drive.

ANR8304E ANR8309E

ANR8307I Request number: Remove device type
User response: Ensure that the DEVICE parameter volume volume name from slot with
associated with the drive was identified correctly in the element number slot name of library
DEFINE PATH command and that the drive is library name; issue 'REPLY' along with
currently powered on and ready. the request ID when ready.
Explanation: A CHECKOUT LIBVOLUME command
ANR8304E Time out error on drive drive name in has completed. You can remove the volume from the
library library name. slot with the specified element number and store it
outside the library. For the slot and element number
Explanation: A time out condition occurred while diagram of your library, refer to the documentation
waiting for the given drive to become ready so that provided with the current ptf level or refer to the
automated library operations could be performed. Administrator's Guide manual for your release and
System action: The operation fails. platform.
User response: Ensure that the DEVICE parameter System action: The server waits until a REPLY
associated with the drive was identified correctly in the command is issued.
DEFINE PATH command, and that the device is User response: Remove the volume from the slot and
currently powered on and ready. store it in a safe place. Issue a REPLY command, along
with the request ID, to tell the server that the volume
ANR8305E Library library name is not ready or not has been removed. The volume can be returned to the
operational. library with the CHECKIN LIBVOLUME command.
Explanation: The specified automated library device is

either not ready or not in an operational state. ANR8308I Request number: device type volume volume
name is required for use in library library
System action: Initialization of the library device fails. name; CHECKIN LIBVOLUME required
User response: Ensure that the library is powered on within time limit minutes.
and ready for automated operations. Further Explanation: A mount request has been made for a
initialization attempts for the given library will usually volume that is defined in a storage pool, but which is
be postponed until the next attempt is made to access currently checked out of the given library.
the library for an automated operation. During server
startup, however, initialization may be retried after a System action: The server waits until it detects that
short waiting period. the volume has been checked into the library, or the
time limit expires.
ANR8306I Request number: Insert device type volume User response: Obtain the required volume, and insert
volume name mount mode into the slot it into the library by issuing a CHECKIN LIBVOLUME
with element number slot element of command. Use the SWAP=YES option of the CHECKIN
library library name within time limit LIBVOLUME command if the library is currently full;
minutes; issue 'REPLY' along with the this process allows the server to select an appropriate
request ID when ready. volume to be swapped out in order to make room for
the required volume.
Explanation: A CHECKIN LIBVOLUME or a LABEL
LIBVOLUME command is in progress, and the
specified volume is needed. The server expects the ANR8309E Mount attempt failed - library library
volume to be inserted into the slot with the specified name is not defined.
element number of the given library within the time Explanation: An attempt has been made to mount a
limit specified in the message. For the slot and element volume, but the attempt fails because the specified
number diagram of your library, refer to the library is not defined.
documentation provided with the current ptf level or
refer to the Administrator's Guide for your release and System action: The operation fails.
platform.
User response: Ensure that the LIBRARY attribute of
System action: The server waits until a REPLY the device class associated with the mount operation
command is issued, or until the time limit expires. identifies a defined library. If not, correct the value of
the LIBRARY attribute, or define the specified library
User response: Insert the volume into the slot and and retry the operation.
issue a REPLY command, along with the request ID, to
tell the server that the volume has been inserted.
ANR8310E ANR8318I
command. Retry the mount request.

ANR8310E An I/O error occurred while accessing
library library name.
ANR8314E Library library name is full.
Explanation: An I/O error occurs while accessing the
designated library. Explanation: A library operation fails because all of
the librarys storage locations are occupied.
User response: Ensure that the DEVICE parameter
associated with the library is identified correctly in the User response: Issue a CHECKOUT LIBVOLUME
DEFINE PATH command, and that the library is command to make room in the library. Retry the library
currently powered on and ready. If the library has an operation.
access door, make sure it is closed. After checking and
correcting these potential problems, retry the operation.
ANR8315E Command: The device type of drive drive
name is not supported in library type
ANR8311E An I/O error occurred while accessing libraries.
drive drive name for low-level operation
operation, errno = drive errno, rc = return Explanation: Drives of the type identified in the
code. command are not supported in the given type of
library.
Explanation: An I/O error occurs while performing
the operation on the specified drive. System action: The command is not processed.
System action: The operation fails. User response: Determine whether the drive and
library combination is supported by the installed level
User response: Ensure that the DEVICE parameter of the server. If so, contact your service representative.
associated with the drive is identified correctly in the
DEFINE PATH command, and that the drive is
currently powered on and ready. After checking and ANR8316E Selecting swap volume to be checked
correcting these potential problems, retry the operation. out of library library name.
For more information on I/O error codes, search on Explanation: A CHECKIN LIBVOL command was
I/O error code descriptions for server messages in the issued for a library that has no empty slots to hold the
Tivoli Storage Manager Information Center. new cartridge. The SWAP=YES parameter was included
in the command.
ANR8312E Volume volume name could not be System action: A CHECKOUT LIBVOL command will
located in library library name. be automatically be issued, specifying either a scratch
Explanation: The designated volume cannot be found volume or, if there are none, a volume with the lowest
at its expected location in the given library. number of mounts.
System action: The operation fails. User response: Use a supported type of drive. volume
from the library and store it in a safe place. Issue a
User response: Perform an AUDIT LIBRARY REPLY command to tell the server that the volume has
operation on the designated library, which forces the been removed. The volume can be introduced back into
server to reevaluate its inventory information for the library with the CHECKIN LIBVOLUME command.
volumes in the library.
ANR8317I The volume in device type drive drive

ANR8313E Volume volume name is not present in name must be manually ejected.
Explanation: This device type does not automatically
Explanation: A mount request is made for the given eject the volume when it is dismounted and requires
volume in the specified library, but the volume is not that the volume be manually ejected from the drive.
currently checked into the library.
System action: The mount operation fails. If the
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 Explanation: The server requires that the specified

ANR8319I ANR8325I
volume be mounted as requested. Since the volume is to the library with the CHECKIN LIBVOLUME
two-sided, this message specifies which side (A or B) is command.
needed by the server for I/O operations.
System action: The server waits for the volume to be ANR8322I Request number: Remove device type
mounted. volume volume name from entry/exit port
of library library name; issue 'REPLY'
User response: Mount the volume in the specified
along with the request ID when ready.
drive.
Explanation: A CHECKOUT LIBVOLUME command
has completed. You can remove the specified volume
ANR8319I Request number: Insert device type volume
from the entry/exit port of the given library and store
volume name mount mode into library
it elsewhere.
library name within time limit minute(s).
System action: The server waits until a REPLY
Explanation: A CHECKIN LIBVOLUME command is
command is issued.
in progress, and the specified volume is needed. The
server expects the volume to be inserted into the User response: Remove the volume from the library
library with the convenience I/O station mechanism. and store it in a safe place. Issue a REPLY command,
along with the request ID, to tell the server that the
System action: The server waits until the volume is in
volume has been removed. The volume can be returned
the library, or until the time limit expires.
to the library with the CHECKIN LIBVOLUME
User response: Insert the specified volume into the command.
library. If the volume has already been inserted into the
library, no user action is necessary.
ANR8323I Request number: Insert device type volume
volume name mount mode into entry/exit
ANR8320I Request number: Insert device type volume port of library library name within time
volume name mount mode in drive drive limit minute(s); issue 'REPLY' along with
name of library library name within time the request ID when ready.
limit minute(s); issue 'REPLY ' along
Explanation: A CHECKIN LIBVOLUME or a LABEL
with the request ID when ready.
LIBVOLUME command is in progress, and the
Explanation: A CHECKIN LIBVOLUME or a LABEL specified volume is needed. Mount the volume in the
LIBVOLUME command is in progress, and the entry/exit port of the given library within the time
specified volume is needed. The server expects the limit specified in the message.
volume to be inserted in the designated drive of the
given library within the time limit specified in the
command is issued, or until the time limit expires.
message.
User response: Insert the volume into the librarys
entry/exit port; and issue a REPLY command, along
command is issued, or until the time limit expires.
with the request ID, to tell the server that the volume
User response: Insert the volume into the drive, and has been inserted.
then issue a REPLY command, along with the request
ID, to tell the server that the volume has been inserted.
ANR8324I Device type volume volume name is
expected to be mounted (mount mode).
Explanation: The specified volume is expected to be
volume volume name from drive drive
mounted in the near future so the server can access it
name of library library name; issue
for reading or writing.
'REPLY' along with the request ID when
ready. System action: None.
Explanation: A CHECKOUT LIBVOLUME or a User response: If the volume is stored offline, retrieve
LABEL LIBVOLUME command has completed. You can it so that it is readily accessible when the server
remove the specified volume from the designated drive requests that it be mounted.
and store it outside the library.
System action: The server waits until a REPLY ANR8325I Dismounting volume volume name -
command is issued. mount retention period minute mount
retention expired.
User response: Remove the volume from the drive
and store it in a safe place. Issue a REPLY command, Explanation: The specified volume is dismounted
along with the request ID, to tell the server that the because the given mount retention period has expired.
volume has been removed. The volume can be returned
System action: The volume is dismounted.
ANR8326I ANR8335I
User response: None. in use, meaning that read or write operations, or both,
are being performed.
ANR8326I Request number: Mount device type volume System action: None.
volume name mount mode in drive drive
name of library library name within time
limit minutes.
Explanation: If the volume name includes the names
mounted mount mode in drive drive name,
EXP, IMP, DUMP, or DBBK, the request is for a scratch
status: DISMOUNTING.
volume.
Explanation: In response to a QUERY MOUNT
System action: The server waits for the volume to be
command, the server indicates that the given volume is
mounted.
mounted in the specified drive. The volume is currently
User response: Mount the volume in the specified being dismounted by the server.
drive.
ANR8327E Command: Cannot cancel request request
number.
Explanation: The request, whose number is specified
mounted mount mode, status: IDLE.
by the given command, cannot be canceled. The
requested operation must be completed. Explanation: In response to a QUERY MOUNT
System action: The cancel request command is not
mounted for I/O operations. The volume is currently
processed.
idle, meaning no active operations are being performed.
User response: Proceed with the requested operation. If the volume remains in the idle state for the amount
of time specified by the device class mount retention
period, it will be automatically dismounted.
ANR8328I Request number: device type volume volume
name mounted in drive drive name. System action: None.
Explanation: The server verifies that a requested User response: None.
volume has been mounted properly in the given drive.
System action: The volume is accessed for reading or ANR8333I Device type volume volume name is
writing, or both. mounted mount mode, status: IN USE.
User response: None. Explanation: In response to a QUERY MOUNT
mounted for I/O operations. The volume is currently in
use, meaning that read or write operations, or both are
being performed.
status: IDLE.
command, the server indicates that the given volume is User response: None.
mounted in the specified drive. The volume is currently
ANR8334I Number of matches matches found.
If the volume remains in the idle state for the amount
of time specified by the device class mount retention Explanation: This is a summary message for the
period, it will be automatically dismounted. QUERY MOUNT command. It indicates the total
number of mount points that have been reported in the
command output.
status: IN USE. ANR8335I Request number: Verifying label of device
type volume volume name in drive drive
name.
mounted in the specified drive. The volume is currently Explanation: The server verifies the label of the
volume that has been requested by an earlier mount

ANR8336I ANR8345E
message. This is done to ensure that the correct volume

ANR8340I Device type volume volume name
has been mounted by the operator.
mounted.
System action: The server reads the volume label and
Explanation: The server has mounted the given
checks it for validity.
volume.
System action: Read or write operations, or both, will
commence for the volume.
ANR8336I Verifying label of device type volume
volume name in drive drive name.
Explanation: The server verifies the label of a volume
ANR8341I End-of-volume reached for device type
that is needed for read or write operations, or both.
volume volume name.
This is done to ensure that the correct volume has been
mounted. Explanation: The server has detected an
end-of-volume condition for the given volume.
System action: The server reads the volume label and
checks it for validity. System action: The volume is marked full. If more
data must be stored, the server will access another
volume for it.
ANR8337I Device type volume volume name mounted
in drive drive name.
ANR8342I Request request number for volume
Explanation: The server verifies that the specified
volume name canceled by administrator
mount request has been completed properly. Read or
name.
write operations, or both, can be performed on the
volume. Explanation: A mount request is canceled by the given
administrator.
System action: The label of the volume has been
verified. System action: The system cancels the mount request.
ANR8338E Device type volume volume name cannot ANR8343I Request request number for volume
be overwritten by EXPORT operation. volume name canceled (PERMANENT) by
administrator name.
Explanation: The specified volume already exists or
contains data, so that the server cannot allow new Explanation: A mount request is successfully canceled
export data to be written to it. with the PERMANENT option.
System action: The server detects that the given System action: The system cancels the mount request
volume already contains some data that would be and marks the volume as unavailable.
overwritten by the requested export operation.
User response: If the specified volume does not
contain any valuable data, delete it and retry the export
ANR8344E Command: Invalid request number -
operation.
request number.
Explanation: A command has been entered with an
ANR8339E Device type volume intended volume name
incorrect request number.
in drive drive name was replaced with
volume incorrect volume name. System action: The server does not process the
command.
Explanation: The server detects that a previously
mounted and verified volume (the desired volume) has User response: Issue the command with the correct
been replaced with a different volume (the incorrect request number.
volume). No further read or write operations, or both,
can occur on the given drive, because data corruption
may occur. ANR8345E Command: No match found for this
request number.
System action: The server dismounts the volume from
the drive. Explanation: The request number specified by the
command is not in the list of outstanding mount
User response: Mount the correct volume again if it is requests.
in a manual library and retry the operation.
ANR8346I ANR8354E

ANR8351E Request number: Mount request for
command.
volume volume name has timed out.
User response: Issue the command with the correct
Explanation: The mount request has not been satisfied
request number.
in the requested time.
System action: The server fails the mount request.
ANR8346I Command: No requests are outstanding.
User response: Retry the mount request and ensure
Explanation: A QUERY REQUEST or CANCEL
that the volume is mounted within the time limit for
REQUEST command has been entered although no
the manual library. For an automated library, retry the
mount requests are outstanding.
mount request and increase the mount wait time for
System action: Server operation continues. the device class.

ANR8352I Requests outstanding:
ANR8347E Command: Volume volume not found. Explanation: This message provides a list of currently
outstanding mount requests.
Explanation: A DISMOUNT VOLUME command is
issued, but the volume to be dismounted cannot be System action: The server lists all outstanding mount
found. requests or the one specified on the QUERY REQUEST
command.
User response: Ensure that the correct volume name is
entered.
ANR8353E Request number: I/O error reading label
of volume in drive drive name.
ANR8348E Command: Volume volume is not "Idle".
Explanation: The server detects an error while reading
Explanation: A DISMOUNT VOLUME command has the volume label from the volume in the specified
been issued, but the volume is still in use and cannot drive.
be dismounted.
System action: The volume is ejected, and the server
System action: Server operation continues. continues to wait for the requested volume to be
User response: If it is necessary to dismount the mounted.
volume, cancel the session or process that is using the User response: Ensure the following:
volume, and reissue the command.
v The requested volume is properly inserted in the
designated drive.
ANR8349E Command: Device device not found. v The volume has been labeled by using the
Explanation: A DISMOUNT DEVICE command has DSMLABEL utility program before you attempt to
been issued, but the device to be dismounted cannot be use it with the server.
found. v The DEVICE parameter associated with the drive is
identified correctly in the DEFINE PATH command,
and the drive is currently powered on and ready.
User response: Ensure that the correct device has been
After checking and correcting these potential problems,
specified.
retry the operation.
ANR8350E Command: Device device is not "Idle".

ANR8354E Request number: Incorrect volume (volume
Explanation: A DISMOUNT DEVICE command has name) mounted in drive drive name.
been issued, but the device is still in use and cannot be
Explanation: The user has inserted the named volume
dismounted.
into the indicated drive, but it is not the one requested
System action: Server operation continues. by the server.
User response: If it is necessary to dismount the System action: The volume is ejected, and the server
device, cancel the session or process that is using the continues to wait for the requested volume to be
device, and reissue the command. mounted.
User response: Ensure that the requested volume is
inserted properly into the designated drive.

ANR8355E ANR8363E
an AUDIT LIBRARY command is issued against the

ANR8355E I/O error reading label for volume
library.
volume name in drive drive name.
User response: Issue an AUDIT LIBRARY command
Explanation: The server detects an error while
against the library.
reading/verifying the volume label for the volume in
the specified drive.
ANR8359E Media fault detected on device type
System action: The volume is dismounted by the
volume volume name in drive drive name
server.
of library library name.
Explanation: The server encounters a media fault
v Check the integrity of the data on the volume by while accessing the given volume using the specified
issuing an AUDIT VOLUME command. If this error drive.
occurs on a volume that is stored inside a VTL or
SCSI library, the library itself may need to be audited System action: The operation that is attempting to
by using the AUDIT LIBRARY command. access the volume will fail, and the volume will be
immediately dismounted from the drive.
v The DEVICE parameter associated with the drive is
identified correctly in the DEFINE PATH command, User response: In some cases, the server will
and the drive is currently powered on and ready. automatically mark the volume readonly. This will
prevent the server from trying to write to the volume.
After checking and correcting these potential problems,
Issue an AUDIT VOLUME command to determine if
retry the operation.
any data has been lost due to the media failure.
ANR8356E Incorrect volume mounted volume name

ANR8360I Volume volume name has been deleted
was mounted instead of volume expected
from MANUAL library library name.
volume name in library library name.
Explanation: The specified volume has been deleted
Explanation: The incorrect volume has been mounted
by the server. It can be returned to a scratch pool by
in the designated library. This error can occur if the
the mount operator if desired.
library inventory has been altered due to manual
intervention or movement of volumes, or both. System action: The volume is removed from the
servers inventory.
System action: The volume is dismounted; the
expected volume may be marked unavailable if this User response: None.
error occurs during normal volume mount activity.
User response: Use the AUDIT LIBRARY command to ANR8361E Command: Device type not specified.
force the library to reevaluate its inventory of volumes.
Explanation: The specified command requires that the
DEVTYPE parameter be supplied.
ANR8357I Error reading label of volume from
slot-element element address in drive drive System action: The command is not processed.
name of library library name. User response: Reissue the command, and specify a
Explanation: While processing a search-mode valid DEVTYPE parameter.
CHECKIN LIBVOLUME command for the designated
library, the server finds a volume whose label cannot be ANR8362E Command: The parameter parameter is
read. invalid for device type device type.
System action: The volume is dismounted and is not Explanation: The specified parameter is not valid for a
checked into the library. device class with the given device type.
User response: Remove the volume from the library System action: The command is not processed.
and ensure that it is properly labeled. After doing so,
the volume can be checked into the library. User response: Reissue the command with a correct
parameter.
ANR8358E Audit operation is required for library

library name. ANR8363E Command: The parameter parameter is
required for device type device type.
Explanation: The server encounters a problem
managing the given library, and determines that an Explanation: The specified command requires that the
AUDIT LIBRARY operation should be performed. given parameter be supplied when the indicated device
type is used.
System action: The server may continue to access the
library, but some volumes may not be accessible until System action: The command is not processed.
ANR8364E ANR8372I
User response: Reissue the command, providing the

ANR8368E Request number: Incorrect side (side) of
required parameter value.
volume volume name mounted in drive
drive name.
ANR8364E Command: Cannot reduce MOUNTLIMIT
Explanation: The user inserted the wrong side of the
below number of volumes currently
requested volume into the indicated drive.
mounted.
System action: The volume is ejected, and the server
Explanation: The MOUNTLIMIT value cannot be
continues to wait for the requested side of the volume
reduced below the number of currently mounted
to be mounted.
volumes.
User response: Insert the correct side of the requested
volume into the designated drive.
User response: Wait until the server finishes using
some of the mounted volumes, or force the server to
ANR8369E Library library name is not defined.
dismount idle volumes using the DISMOUNT
VOLUME command, then retry this command. Explanation: The designated library is not defined,
but has been referenced in a mount request.
ANR8365E Command: The parameter parameter System action: The mount request is rejected.
cannot be changed.
User response: Define the given library, or update the
Explanation: The specified parameter cannot be LIBRARY parameter of the device class that references
changed from the value that was provided with the it.
associated DEFINE command.
System action: The command is not processed. ANR8370I Device type volume volume name is
mounted mount mode, status: RETRY.
User response: If it is necessary to use a different
value for the given parameter, the associated object Explanation: In response to a QUERY MOUNT
must be deleted and then redefined using the new command, the server indicates that the given volume is
parameter value. mounted for I/O operations. The volume is currently in
RETRY, meaning an attempt is being made to
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
not allowed.
Explanation: The designated parameter is specified
volume volume name from drive drive
more than once in the command; this is not allowed.
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.

ANR8373I ANR8381E
User response: Remove the volume from the drive User response: None.
and store it in a safe place.
ANR8373I Request number: Fill the bulk entry/exit mounted mount mode, status:
port of library library name with all device DISMOUNTING.
type volumes to be processed within time
limit minute(s); issue 'REPLY' along with
the request ID when ready.
currently being dismounted.
Explanation: A CHECKIN LIBVOLUME or LABEL
LIBVOL command with SEARCH=BULK is in progress.
Load all volumes to be processed into the multi-slot User response: None.
entry/exit port of the given library within the time
limit specified in the message.
System action: The server waits until a REPLY mounted mount mode, status: RETRY
command is issued, or until the time limit expires. DISMOUNT FAILURE.
User response: Insert the volumes into the librarys Explanation: In response to a QUERY MOUNT
entry/exit port; and issue a REPLY command, along command, the server indicates that it is currently
with the request ID, to tell the server that the volumes retrying the dismount of the given volume because of a
have been inserted. failure during the previous dismount.
ANR8374E Unable to unmount mountpoint
mountpoint name. User response: None.
Explanation: A removable file device class mountpoint

had to be unmounted using the operating system ANR8379I Mount point in device class Device class
unmount function. The server did not have permission name is waiting for the volume mount to
to unmount the directory specified. complete, status: WAITING FOR
VOLUME.
System action: The server continues, but cannot use
the mountpoint for removable file support until the Explanation: In response to a QUERY MOUNT
directory is unmounted. command, the server indicates that there is a mount
point in the given device class waiting for the volume
User response: It may be necessary to run the server mount to complete.
as a root user to mounted directories to be unmounted.
ANR8375E Device type volume volume name cannot User response: None.
be overwritten by BACKUPSET
operation. ANR8380I Device type volume volume name is
Explanation: The specified volume already exists or mounted mount mode in drive drive name,
contains data, so that the server cannot allow new status: RETRY DISMOUNT FAILURE.
backup set data to be written to it. Explanation: Because of the failure of a previous
System action: The server detects that the given dismount, the server is retrying the dismount of the
volume already contains some data that would be specified volume from the specified drive. In response
overwritten by the requested backup set operation. to a QUERY MOUNT command, the server indicates
that the volume is mounted in the drive.
contain any valuable data, delete it and retry the System action: None.
backup set operation. User response: None.
ANR8376I Mount point reserved in device class ANR8381E Device type volume volume name could
Device class name, status: RESERVED. not be mounted in drive drive name.
Explanation: In response to a QUERY MOUNT Explanation: The server could not complete the
command, the server indicates that there is a mount specified mount request due to an error. Examine
point reserved for future I/O operations in the given previous messages for additional information regarding
device class. the specified volume and the operation.
System action: None. System action: The requested operation fails.
ANR8382W ANR8388E
User response: Examine previous messages for inserted properly into the designated location in the
additional information regarding the specified volume library.
and the operation.
ANR8385E All entry/exit ports of library library
ANR8382W Library library name is now full. name are empty.
Explanation: During a library check-in operation from Explanation: The entry/exit ports of the library do not
a multi-slot entry/exit station, the last storage location contain a volume that can be processed.
was filled before checking the remainder of the
entry/exit slots.
User response: Ensure that the volume is inserted
System action: The operation stops, but is considered
properly into the entry/exit port of the library and that
successful if at least one volume is checked in.
the library indicates the volume is inserted and issue
User response: If more volumes remain to be checked the command again. Contact the hardware vendor if
in, issue a CHECKOUT LIBVOLUME command to the volume is inserted correctly and this error occurs.
make room in the library. Retry the library operation.
ANR8386W Slot element number of library library
ANR8383E Device class device class name directory name is inaccessible.
directory name is not a SnapLock
Explanation: The slot in the library could not be
directory.
physically accessed at this time.
Explanation: When processing the named device class,
System action: The slot is skipped and processing
it was discovered that a directory was specified for the
continues with the next slot.
device class that is not a NetApp SnapLock WORM
Volume. All directories used by a device class for a User response: If there is a volume in the slot that
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
directories from the device class DIR list. If you modify System action: The server waits until the operator
an existing device class, you need to ensure that no performs the actions requested.
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
ANR8384E Request number: Incorrect volume (volume the library's documentation on how to make the
name) inserted into library library name. entry/exit port accessible. If the library is incorrectly
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
inserted. Explanation: When processing the named device class,
which is referenced by a storage pool of type
User response: Ensure that the requested volume is RECLAMATIONTYPE=SNAPLOCK, it was discovered

ANR8389E ANR8392E
that there were no directories specified for it. One or that only one type of storage pool uses the device class.
more directories must be specified for a device class If you wish to have storage pools of both reclamation
that is used by a storage pool with types pointing to the same directory structure, you may
RECLAMATIONTYPE=SNAPLOCK, and all directories create two device classes with the same directory
must be NetApp SnapLock WORM Volumes. structure, and have storage pools of one reclamation
type use one device class while storage pools of the
other reclamation type uses the other device class.
User response: A device class that is referenced by a
If you have made updates to the storage pools and
storage pool of type
device classes and the problem is not resolved, you
RECLAMATIONTYPE=SNAPLOCK needs to specify
may need to restart the Tivoli Storage Manager server.
one or more directories which are NetApp SnapLock
WORM Volumes. Use the UPDATE DEVCLASS
command to define appropriate directories to the ANR8390W Failure connecting to library client
device class and retry your request. library client to manage volume volume.
Explanation: The library manager failed to contact the
ANR8389E Device class device class name has storage designated library client for a management operation
pools using it with inconsistent for the specified volume.
RECLAMATIONTYPE parameters, or
System action: The library management operation
invalid directories specified in it.
fails.
Explanation: When processing the named device class,
User response: Review the other messages in the
it was discovered that it was not configured properly. A
activity log relating to this library client and this
device class can be referenced by storage pools of type
volume to determine which operations were affected by
this failure.
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
name is not available.
System action: If the Tivoli Storage Manager server is
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.
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 Tivoli does not have executable permission.
Storage Manager 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 System action: The library management operation
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=SNAPLOCK are using the
device class. If storage pools of both types are using the
device class, modify the storage pool definitions such
ANR8393E ANR8401E
ANR8393E Failed to communicate with the external ANR8397E Library name (library name) is too long to
library library name through it's defined use as the default PREFIX value. An
external library manager path. explicit PREFIX value is required.
Explanation: The external library manager executable Explanation: The PREFIX value must be specified
file did not start or exited immediately. with 25 characters or less. If a PREFIX value is not
specified, the library name is used by default. However,
if the library name is longer than 25 characters, it
fails.
cannot be used for the PREFIX parameter. Instead, the
User response: Verify the path and the file name of PREFIX value must be specified explicitly.
this library's external library manager. If it is correct,
verify that the file is present on the system and that the
the file permissions allow the server to invoke the file. User response: Reissue the PERFORM LIBACTION
The path and file name can be found by using the command and specify the PREFIX parameter with a
QUERY PATH command. value that contains 25 characters or less.
ANR8394E The device class,device class ANR8398E The REMOVE=UNTILEEFULL option is

name,directory parameter is too long. not supported with the MOVE
DRMEDIA command for librarylibrary
Explanation: The directory parameter for the define
name with library type library type.
device class command is too long.
Explanation: The MOVE DRMEDIA command does
not support the option as REMOVE=UNTILEEFULL for
User response: Reissue the command, specifying a this library type.
valid DIRECTORY parameter. The directory parameter
System action: The operation will fail.
must be between 0 and 1400 characters.
User response: This option is only supported with the
library type SCSI. Remove the
ANR8395E Command: The parameters specified are
REMOVE=UNTILEEFULL option and perform the
only valid for a device class defined
operation again.
with a ZosMedia library.
Explanation: The specified parameter is not valid for a
ANR8399E The TSM server receives a status as acsls
device class unless a ZosMedia library is specified in
statuse from ACSLS server.
the Library parameter of the device class.
Explanation: The ACSLS CSI media server does not
receive a response from TSM server.
User response: Reissue the command with a correct
parameter.
User response: This is a communication problem.
Check configurations of the network adapter and its
ANR8396E Command: Library library name is not
driver and then perform the operation again.
capable of discovering the drives that it
owns.
ANR8400I Library library name defined.
Explanation: The PERFORM LIBACTION command
failed. Either the library lacks the SCSI capability to Explanation: The designated library has been
determine the serial and element numbers of its own successfully defined.
drives, or SAN Discovery failed to translate the serial
System action: The library is defined and recorded in
number to the drive's special file name.
the database.
User response: Correct any issues with SAN
Discovery and reissue the PERFORM LIBACTION
ANR8401E Command: Invalid library name library
command. If the command cannot be processed, drive
name.
and drive path definitions for this library will need to
be defined manually, one drive at a time. Explanation: The designated library name is invalid;
either it contains too many characters, or some of the
characters are invalid.

ANR8402E ANR8412I
User response: Reissue the command using a valid

ANR8407E Command: The MODEL parameter is
library name.
required for this command.
Explanation: The MODEL parameter has not been
ANR8402E Command: Library library name is already
provided; it is required.
defined.
Explanation: The designated library cannot be defined
because it already exists. User response: Reissue the command using the
MODEL parameter.
User response: If you want to define an additional
ANR8408E Command: The DEVICE parameter is
library, reissue the command with a different library
name.
Explanation: The DEVICE parameter has not been
provided; it is required.
ANR8403E Command: Operation not allowed for
library type libraries. System action: The command is not processed.
Explanation: The requested operation is not allowed User response: Reissue the command using the
for libraries of the given type. DEVICE parameter.
defined.
Explanation: The designated library has not been
ANR8404I Drive Drive name defined in library
defined.
library name.
Explanation: The designated drive has been
successfully defined as a member of the specified User response: Reissue the command using a different
library. library name, or define the library before retrying the
command.
System action: The drive is defined and recorded in
the database.
ANR8410I Library library name deleted.
Explanation: The designated library has been deleted
successfully.
ANR8405E Command: Invalid drive name drive name.
System action: The library is deleted.
Explanation: The designated drive name is invalid;
either it contains too many characters, or some of the User response: None.
characters are invalid.
System action: The command is not processed. ANR8411E Command: One or more drives are still
defined in library library name.
User response: Reissue the command using a valid
drive name. Explanation: The command failed because there are
drives defined to the designated library. For the
DELETE LIBRARY and PERFORM LIBACTION
ANR8406E Command: Drive drive name is already
(ACTION=DEFINE) commands, the specified library
cannot have drives currently defined within the library.
Explanation: The designated drive cannot be defined
because it has already been defined for the specified
library. User response: Delete all drives from the library, and
ANR8412I Drive drive name deleted from library
drive, reissue the command with a different drive
library name.
name.
Explanation: The designated drive has been deleted
successfully from the specified library.
System action: The drive is deleted.
ANR8413E ANR8422I
ANR8413E Command: Drive drive name is currently ANR8418E Command: An I/O error occurred while
in use. accessing library library name.
Explanation: The designated drive cannot be deleted Explanation: An I/O error occurs while accessing the
or updated because it is currently in use. designated library.
System action: The command is not processed. System action: The operation fails.
User response: Wait until the drive is no longer in User response: Ensure that the DEVICE parameter
use, and reissue the command. associated with the library is identified correctly in the
DEFINE PATH command, and that the library is
currently powered on and ready. If the library has an
ANR8414E Command: Drive drive name is not
access door, make sure it is closed. After checking and
correcting these potential problems, retry the operation.
Explanation: The designated drive has not been
defined in the given library.
ANR8419E Command: The drive or element conflicts
System action: The command is not processed. with an existing drive in library library
name.
drive name. If appropriate, define the drive before Explanation: Either there are no more physical drives
retrying the command. in the library, or the specified ELEMENT parameter
conflicts with an existing defined drive in the given
library.
required for this command. System action: The command is not processed.
Explanation: The specified parameter must be User response: Specify a valid ELEMENT parameter
provided when processing the given command. that is not used by any other drive in the library.

ANR8420E Command: An I/O error occurred while
User response: Reissue the command, providing the accessing drive drive name.
required parameter value.
Explanation: An I/O error occurs while accessing the
specified drive.
invalid for library type library type. System action: The operation fails.
Explanation: The specified parameter is not valid for User response: Ensure that the DEVICE parameter
libraries of the given type. The scratch category must associated with the drive is identified correctly in the
be at lest 2 less than the private category for 349x DEFINE PATH command, and that the drive is
libraries. currently powered on and ready. After checking and
correcting these potential problems, retry the command.
User response: Reissue the command, using only the ANR8421E Command: Unable to start a process for
proper parameters. If using the scratch category make this command.
sure it is at least 2 less than the private category.
Explanation: The server cannot start a background
process to carry out the designated command.
invalid for drives in library type libraries. System action: The operation fails.
Explanation: The specified parameter is not allowed User response: Check for and correct memory
when defining or updating drives in a library of the shortages or other server resource constraints, and
given type. reissue the command.
ANR8422I Command: Operation for library library
User response: Reissue the command, using only the name started as process process ID.
proper parameters.
Explanation: A volume check-in process has been
started to handle the insertion of a volume into the
given library. The process is assigned the ID specified
in the message.
to perform the operation in response to the CHECKIN

ANR8423I ANR8431I
LIBVOLUME command entered by an administrator.

ANR8427I CHECKIN LIBVOLUME for volume
User response: To obtain status on the process, issue volume name in library library name
the QUERY PROCESS command. The process may be completed successfully.
canceled with the CANCEL PROCESS command.
Explanation: The specified volume was successfully
checked in to the library during processing of a
ANR8423I CHECKIN LIBVOLUME process for CHECKIN LIBVOLUME or LABEL LIBVOLUME
library library name has been canceled. command.
Explanation: A background server process that has System action: The volume is made available for
been working to check in one or more volumes for the mounting in the given library.
given library is canceled by the CANCEL PROCESS
command.
ANR8428E Command: The STATUS parameter is
Explanation: The STATUS parameter must be
provided with the given command.
ANR8424I Checking in volume volume name in
User response: Reissue the command, and provide a
Explanation: In response to a QUERY PROCESS
valid STATUS parameter value.
command, this message displays the status for a
CHECKIN LIBVOLUME process on the server. The
given volume is being checked in to the designated ANR8429E Command: No drives are currently
library. defined in library library name.
System action: The background process operation Explanation: The command cannot be issued until at
continues. least one drive has been defined in the given library.
User response: None. The process may be canceled by System action: The command is not processed.
an authorized administrator using the CANCEL
User response: Define a drive in the library, using the
PROCESS command.
DEFINE DRIVE command, as well as a path to the
drive, using the DEFINE PATH command. Then retry
ANR8425I Checking in volumes in search mode in the failed command.
Explanation: In response to a QUERY PROCESS ANR8430I Volume volume name has been checked
command, this message displays the status for a into library library name.
CHECKIN LIBVOLUME process on the server. Volumes
Explanation: A search-mode CHECKIN LIBVOLUME
are being checked into the given library automatically
process has found the given volume and automatically
using a search for previously-unknown volumes.
checked it into the library.
System action: The background process operation
System action: The volume is added to the given
continues.
librarys inventory.
User response: None. The process may be canceled by
PROCESS command.
ANR8431I CHECKIN LIBVOLUME process
completed for library library name; volume
ANR8426E CHECKIN LIBVOLUME for volume
count volume(s) found.
volume name in library library name failed.
Explanation: A search-mode CHECKIN LIBVOLUME
Explanation: The background process for a CHECKIN
process is completed. The specified number of volumes
LIBVOLUME command has failed.
have been successfully added to the librarys inventory.
System action: The background process ends, but the
System action: The volumes are made available for
volume has not been checked into the library.
use by the server.
User response: Make sure the library and drive
devices associated with this command are powered on
and ready, and then reissue the command.
ANR8432E ANR8440E
ANR8432E Command: Volume volume name is already ANR8436I Checking out volume volume name from
present in library library name. library library name.
Explanation: The specified volume cannot be checked Explanation: In response to a QUERY PROCESS
into the given library because it is already present. command, this message displays the status for a
CHECKOUT LIBVOLUME process on the server.
User response: Provide the name of a volume that is
continues.
not already present in the given library. Use the
QUERY LIBVOLUME command to obtain a full list of User response: None. The process may be canceled by
volumes that have already been checked into the an authorized administrator using the CANCEL
library. PROCESS command.
ANR8433E Command: Volume volume name is not ANR8437E CHECKOUT LIBVOLUME for volume
present in library library name. volume name in library library name failed.
Explanation: The specified volume cannot be checked Explanation: The background process for a
out of the given library because it is not present. CHECKOUT LIBVOLUME command has failed.
System action: The command is not processed. System action: The background process ends, but the
volume has not been checked out of the library.
User response: Provide the name of a volume that is
present in the given library. Use the QUERY User response: Make sure the library and drive
LIBVOLUME command to obtain a full list of volumes devices associated with this command are powered on
that reside in the library. and ready, then retry the command.
ANR8434I Command: Operation for volume volume ANR8438I CHECKOUT LIBVOLUME for volume
name in library library name started as volume name in library library name
process process ID. completed successfully.
Explanation: A volume check-out process has been Explanation: The background process for a
started to handle the removal of a volume from the CHECKOUT LIBVOLUME command has completed
given library. The process is assigned the ID specified successfully.
in the message.
System action: The volume is either deleted from the
System action: The server starts a background process librarys inventory (if its status is something other than
to perform the operation in response to the DATA) or marked not present (if its status is DATA).
CHECKOUT LIBVOLUME command entered by an
administrator.
User response: To obtain status on the process, issue
ANR8439I library type library library name is ready
the QUERY PROCESS command. The process may be
for operations.
Explanation: The initialization process for the given
library has completed successfully, and the library is
ANR8435I CHECKOUT LIBVOLUME for volume
ready for use.
volume name in library library name has
been canceled. System action: The library is made ready for use.
Explanation: A background server process that has User response: None.
been working to check out the volume from the given
library is canceled by the CANCEL PROCESS
command. ANR8440E Initialization failed for library type
library library name; will retry in delay
System action: The server process is ended and server time minute(s).
User response: None. 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
door, make sure it is in the closed position.

ANR8441E ANR8448E
System action: The library volume inventory is

ANR8441E Initialization failed for library type
updated.
library has failed, and will not be retried until the next
time the server needs to access the library. ANR8446W Manual intervention required for library
library name.
System action: The library is made temporarily
unavailable. Explanation: The specified library requires manual
intervention.
User response: Make sure the library is powered on
and attached. System action: Current library activity will be delayed
until the required intervention occurs.
ANR8442E Command: Volume volume name in library User response: If the library has an access door, make
library name is currently in use. sure it is in the closed position. If it has a cartridge
carousel, make sure the carousel is installed. The server
automatically detects when the appropriate action has
because the specified volume is already being used for
been taken; it will then continue its operations.
another operation.
ANR8447E No drives are currently available in
User response: Wait until the conflicting volume library library name.
activity has completed, and then reissue the command.
Explanation: The attempted operation cannot be
If the volume is currently mounted, but idle, you can
completed on the specified library because there are no
dismount it with the DISMOUNT VOLUME command
available drives. A drive may be unavailable because
and then retry this operation.
an application other than the server may have the
driver opened. This message may also be issued if a
ANR8443E Command: Volume volume name in library CHECKIN or LABEL command is issued and no drive
library name cannot be assigned a status is available to service the operation. This can be
of SCRATCH. because all the drives are mounted by other processes
or sessions, or the device type was incorrectly specified.
Explanation: The volume cannot be assigned to the
given librarys scratch pool because there is a storage System action: The attempted operation is terminated.
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
librarys scratch pool might result in a destructive
drives taken offline by the server at the time specified
overwrite of the volumes data.
because of hardware failures or the inability to open
System action: The command is not processed. 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
ANR8444E Command: Library library name is DISMOUNT VOLUME command to free its drive, and
currently unavailable. retry the original operation.
Explanation: The requested operation cannot be

completed because the specified library is unavailable ANR8448E Scratch volume volume name from library
for I/O operations. The library may still be carrying library name rejected - volume name is
out its initialization operations. already in use.
System action: The command is not processed. Explanation: The designated volume has been used to
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
ANR8445I Volume volume name in library library file.
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
ANR8449E ANR8457I
volume that caused the name conflict.

ANR8454E Mismatch detected between external
label (volume name from external label) and
ANR8449E Scratch volume volume name rejected - media label (volume name from media label)
volume name is already in use. in 349X library library name.
Explanation: The designated volume has been used to Explanation: The external label of a volume was
satisfy a scratch mount, but the volume is already found to differ from its media label in the designated
defined in a storage pool, or has been used to store library.
server export, database dump, or database backup
System action: The volume will not be accessed.
information as recorded in the server volume history
file. User response: Remove the volume from the library
and ensure that it is properly labeled.
System action: The volume is rejected.
User response: Use a volume that is not in use, or
ANR8455E Volume volume name could not be
rename the rejected volume or delete the existing
located during audit of library library
volume that caused the name conflict.
name. Volume has been removed from
the library inventory.
ANR8450E Command: Library library name is
Explanation: While processing an AUDIT LIBRARY
currently in use.
command for the given library, the server cannot find
Explanation: The designated library cannot be deleted the given volume in the library.
or updated because it is currently in use for an I/O
System action: The volume is removed from the
operation.
library inventory.
User response: If the volume is needed, it should be
User response: Wait until the library is no longer in located and checked into the library using the
use, and then retry the command. CHECKIN LIBVOLUME command.
ANR8451I 349X library library name is ready for ANR8456E Multiple volumes named volume name
operations. were found during audit of library
library name.
library has completed successfully, and the library is Explanation: While processing an AUDIT LIBRARY
ready for use. command for the given library, multiple physical
volumes are found to have the same name.
System action: The library is made ready for use.
System action: The first instance of the volume is
User response: None. retained in the server inventory; all other instances are
ignored.
ANR8452E Initialization failed for 349X library User response: Remove all of the redundant instances
library name; will retry in delay time of the volume from the library. If the volume which the
minute(s). server retained is found to be the incorrect one, it can
Explanation: The initialization process for the given be checked out with the CHECKOUT LIBVOLUME
library has failed. It is retried automatically after the command; then the correct instance can be checked into
specified amount of time has elapsed. the library with a CHECKIN LIBVOLUME command.

User response: Ensure that the library device is name started as process process ID.
powered on and ready.
Explanation: A library audit process has been started
for the given library. The process is assigned the ID
ANR8453E Initialization failed for 349X library specified in the message.
library name.
Explanation: The initialization process for the given to perform the operation in response to the AUDIT
library has failed and will not be retried until the next LIBRARY command entered by an administrator.
time the server needs to access the library.
System action: The library is made temporarily the QUERY PROCESS command. The process may be
unavailable. canceled with the CANCEL PROCESS command.

ANR8458I ANR8466E
ANR8458I AUDIT LIBRARY process for library ANR8463E Device type volume volume name is write
library name has been canceled. protected.
Explanation: A background server process that has Explanation: The server has detected a write-protect
been working to audit the given library is canceled by condition for the given volume.
System action: The server will dismount the volume
System action: The server process is ended and server and continue processing with another volume.
User response: Adjust the write-protect switch on the
User response: None. volume so that writing is allowed. If the write-protect
switch on the volume allows writing, verify that the
device special file for the drive has proper read and
ANR8459I Auditing volume inventory for library
write permissions, at the operating system layer, for the
library name.
user who is starting the dsmserv process. If the volume
Explanation: In response to a QUERY PROCESS is an optical volume and the write-protect switch is
command, this message displays the status for an already set to allow writing, use the MOVE DATA
AUDIT LIBRARY process on the server. command to move the data off of the volume.
Rewritable volumes may be reformatted and reused
System action: Server operation continues. after the data is moved to another volume.
User response: None. The process may be canceled by
an authorized administrator using the CANCEL ANR8464E command: Invalid update request for
PROCESS command. library library name.
Explanation: An invalid update request has been
ANR8460E AUDIT LIBRARY process for library made for the given library. This can occur if a new
library name failed. device name is given and the characteristics of the
Explanation: The background process for an AUDIT device do not match the characteristics of the original
LIBRARY command has failed. device.
System action: The background process ends. System action: The server does not process the
command.
devices associated with this command are powered on User response: If a different type of library device has
and ready, then reissue the command. been installed, the old library definition must be
deleted with a DELETE LIBRARY command, and a
new library must be defined. The UPDATE LIBRARY
ANR8461I AUDIT LIBRARY process for library command cannot be used in this case.
library name completed successfully.
Explanation: The background process for an AUDIT ANR8465I Library library name updated.
LIBRARY command has completed successfully.
Explanation: An UPDATE LIBRARY request has been
System action: The library inventory is updated to successfully processed for the given library.
match the contents of the library as found during the
audit operation. System action: The server updates its information
about the library.
ANR8462I End-of-side reached for device type

volume volume name. ANR8466E command: Invalid update request for
drive drive name in library library name.
Explanation: The server has detected an end-of-side
condition for the given two sided volume. Explanation: An invalid update request has been
made for the given drive. This can occur if a new
System action: The server will access the second side device name is given and the characteristics of the
of the volume. device do not match the characteristics of the original
User response: None. device.
command.
User response: If a different type of drive has been
installed, the old drive definition must be deleted with
a DELETE DRIVE operation, and a new drive must be
ANR8467I ANR8473I
defined. The UPDATE DRIVE command cannot be

ANR8471E Server no longer polling drive drive name
used in this case.
in library library name - path path will be
marked off-line.
ANR8467I Drive drive name in library library name
Explanation: The server is unable to use the
updated.
mentioned drive via the specified path. This may be for
Explanation: An UPDATE DRIVE request has been the following reasons:
successfully processed for the given drive. v The drive cannot be opened
System action: The server updates its information v In the case of a 3494 or a library that can be
about the drive. partitioned, the drive may be unavailable to the
library manager, may be in use by another
User response: None. application, or may be loaded with a cartridge not
labeled for server use.
ANR8468I device type volume volume name System action: The path to the drive is offline and is
dismounted from drive drive name in not used for tape operations.
User response: Determine the reason the path to the
Explanation: The specified volume has been drive is inaccessible, such as hardware errors reported
dismounted from the given drive. in the system logs. Render any needed corrections to
System action: None. the hardware. Then the path may be made online by
issuing the UPDATE PATH command with the
User response: If the type of the given library is ONLINE=YES option.
MANUAL, the operator may elect to remove the
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.
System action: None. User response: Remove the volume from the library
and ensure that it is properly labeled. After doing so,
User response: If the type of the given library is the volume can be checked into the library.
MANUAL, the volume can be manually ejected and
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
drive.
ANR8470W Initialization failure on drive drive name
in library library name. Explanation: The specified volume was found in the
storage slot of a cleaner cartridge. After it was loaded
Explanation: The specified drive could not be into a drive for cleaning, TSM determined that it is not
initialized at this time. a cleaner cartridge. TSM encountered an error trying to
System action: The initialization of the specified move the cartridge back to the storage slot of the
library continues. cleaner cartridge. If the volume is a storage pool
volume, TSM already attempted to make it unavailable.
User response: An internal validation of the specified Review the output of the QUERY VOLUME F=D
drive and its path failed. Ensure that the drive's path command for storage pool volumes. Review the output
definition to the local server is correct. Examine all of the QUERY VOLHISTORY command for non-storage
previous messages for information regarding the pool volumes.
specified drive. If necessary, delete and redefine the
path from the local server to the specified drive. After System action: None.
redefining the path or correcting any issues that were User response: Verify all other cleaner cartridges are
reported by related error messages, the drive's in the correct storage slots. Issue the QUERY
initialization is retried on the next attempt to mount the LIBVOLUME command to obtain the storage slots of
specified drive. all the cartridges currently checked into TSM. Remove
the cartridge in the storage slot identified in the

ANR8474E ANR8482E
ANR8911W message. Remove the specified volume

ANR8478W Invalid home slot address in inventory
from the drive. Issue an AUDIT LIBRARY command
for library library name; volume = volume
against the library.
name;slot = slot number.
Explanation: The specified volume's home slot in the
ANR8474E Command: One or more paths are still
library inventory does not match the database
defined to library library name.
inventory.
Explanation: The designated library cannot be deleted
because there are still paths defined to it.
User response: Run 'audit library' against the
specified library.
User response: Delete all paths to this library, and
ANR8479W Unable to audit slot-element slot-element
of library library name.
ANR8475I Dismount of volume volume name failed.
Explanation: The library audit process was unable to
It may still be in the drive.
audit storage slot with the specified element address.
Explanation: The specified volume could not be This is probably due to no drive device being available
dismounted. TSM encountered an error trying to into which to load the cartridge. It can also be due to
dismount the volume. If the volume is a storage pool library or drive I/O errors occurring during the audit
volume, TSM already attempted to make it unavailable. process.
Review the output of the QUERY VOLUME F=D
System action: The AUDIT LIBRARY command fails.
command for storage pool volumes. Review the output
of the QUERY VOLHISTORY command for non-storage User response: Verify that for every type of cartridge
pool volumes. in the library at least one drive is defined that can read
the media, and that the drive is online and working
properly. Check the activity log for I/O errors related
User response: Review message ANR8469E in the to hardware failure and repair.
activity log. Check if the volume is still loaded in the
drive. If the volume is not in the drive, determine
ANR8480E The drive Drive Name was not found for
where the volume is located in the library.
library Library Name.
Explanation: The missing drive needs to be defined to
ANR8476E Operation is not supported for the
successfully run the current operation.
libtype of library library name.
Explanation: The operation failed because the libtype
of the library is not supported for the operation. User response: Make sure that the drive is defined. If
macros are being used, the COMMIT command needs
to be issued after the DEFINE DRIVE. Otherwise, this
User response: Use a different libtype such as could indicate a server internal error.
MANUAL to perform the operation.
ANR8481I The library library name already has an
ANR8477E Device type device type is incorrect for AUDIT LIBRARY operation pending
drive drive name. mount activity.
Explanation: The device type of the specified drive on Explanation: Libraries of type SHARED can only have
the library client is not compatible with the device type one AUDIT LIBRARY operation waiting on mount
for the same drive on the library manager. activity. All subsequent AUDIT LIBRARY operations
will be canceled.
User response: Delete the drive definition on the operation continues.
library client, and re-define the drive specifying the
correct device. If this does not correct the problem, User response: None.
contact your service representative for assistance.
ANR8482E The checkout volume volume name failed
because the entry/exit port of library
library name is full. Please remove the
volume(s) from the entry/exit port and
re-issue the command.
ANR8483W ANR8489I
Explanation: The indicated operation has failed connected to the host system. If the device is not
because the entry/exit port of the specified library is removed or is powered off, do a power cycle to
full. reinitialize this device and make sure this device is in a
normal state. If this device is still not in a normal state,
call device's vendor support to fix the problem.
User response: Remove the volume(s) from the
entry/exit port and re-issue the command to process
ANR8486I Mount point in device class Device class
any remaining eligible volumes.
name is reserved -- owning server: owner
name, status: RESERVED (session: session
ANR8483W A device class can not be found for the ID, process: process number).
Explanation: A library client audits a SHARED type command, the server indicates that there is a mount
Library, but there is no device class defined for that point reserved for future I/O operations in the given
library. device class. The session and process values are relative
to the server that owns this mount point.
System action: The AUDIT LIBRARY command fails.
User response: Define or update a device class for the
library using the DEFINE DEVCLASS or UPDATE User response: None.
DEVCLASS command.
ANR8487I Mount point in device class Device class
ANR8484E No drives are available to be mounted name is waiting for the volume mount to
in MODE mode with format FORMAT in complete -- owning server: owner name,
library LIBRARY NAME. status: WAITING FOR VOLUME
(session: session ID, process: process
Explanation: The attempted operation cannot be number).
completed on the specified library. Either there are no
available drives with the specified format, or the Explanation: In response to a QUERY MOUNT
volume has the wrong access mode. A drive can be command, the server indicates that there is a mount
unavailable because another application opened the point in the given device class waiting for the volume
drive. This message can also be issued if a CHECKIN mount to complete. The session and process values are
or LABEL command is issued and no drive is available relative to the server that owns this mount point.
to service the operation. This can occur when all drives
are mounted by other processes or sessions, or the
device type was incorrectly specified. User response: None.
System action: The attempted operation ends.
mounted mount mode in drive drive name
check the online status of the drives. Drives that are
-- owning server: owner name, status: IN
marked "Unavailable since hh:mm yy/mm/dd" are
USE (session: session ID, process: process
drives taken offline by the server at the time specified
number).
because of hardware failures or the inability to open
the drive. Use the QUERY MOUNT command to query Explanation: In response to a QUERY MOUNT
mounted drives and their mount mode. If there are command, the server indicates that the given volume is
mounted volumes with an IDLE status, use the mounted in the specified drive. The volume is currently
DISMOUNT VOLUME command to free the drive, and in use, meaning that read or write operations, or both,
retry the original operation. 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 System action: None.
name, error code=error value set by server.
Explanation: The indicated SCSI device cannot be
opened by the server. The error code is set by Tivoli
Storage Manager. It indicates that this device does not
respond the open system function call. This can be
-- owning server: owner name, status:
caused by an inexistent device, a device with powered
IDLE (session: session ID, process: process
off, or a device with firmware/hardware problems.
number).
System action: The transaction needing the drive fails.
User response: Make sure the device is online and command, the server indicates that the given volume is

ANR8490I ANR8497E
mounted in the specified drive. The volume is currently User response: None.
If the volume remains in the idle state for the amount
ANR8493I device type volume volume name mounted
of time specified by the device class mount retention
in drive drive name in library library
period, it will be automatically dismounted. The
name.
session and process values are relative to the server
that owns this mount point. Explanation: The specified volume has been mounted
in the specified drive.
User response: For automated libraries, this message
is purely informational.
-- owning server: owner name, status: ANR8494E Command: An option specified is not
DISMOUNTING (session: session ID, valid for library type libraries.
process: process number).
Explanation: A requested option is not valid for
Explanation: In response to a QUERY MOUNT libraries of the given type for the specified command.
mounted in the specified drive. The volume is currently System action: The command is not processed.
being dismounted by the server. The session and User response: None.
process values are relative to the server that owns this
mount point.
ANR8495E Device type volume volume name cannot
System action: None. be written by BACKUP DB operation.
User response: None. Explanation: The specified volume already exists or
contains data, so that the server cannot allow new
ANR8491I Device type volume volume name is BACKUP DB data to be written to it. Or there is no
mounted mount mode in drive drive name space available on the destination filespace to write this
-- owning server: owner name, status: backup to.
RETRY DISMOUNT FAILURE (session: System action: The server detects that the given
session ID, process: process number). volume already contains some data that would be
Explanation: In response to a QUERY MOUNT 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 User response: If the specified volume does not
failure during the previous dismount from the specified contain any valuable data, delete it and retry the
drive. The session and process values are relative to the BACKUP DB command.
server that owns this mount point.
System action: None. ANR8496E Device class device class not defined in
User response: None. device configuration information file.
Explanation: The command that has been issued
ANR8492I Device type volume volume name is requires that the specified device class be defined in the
mounted mount mode in drive drive name 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). System action: The command is not processed.
Explanation: In response to a QUERY MOUNT User response: Reissue the command, and specify a
command, the server indicates that the given volume is valid device class. Refresh your device configuration
mounted for I/O operations. The volume is currently in information file by issuing the BACKUP DEVCONFIG
RETRY, meaning an attempt is being made to command.
re-establish communications with another server. If the
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 Explanation: The specified command requires that the
to the server that owns this mount point. specified library be defined in the device configuration
System action: None. information file. This definition was not found or the
ANR8498E ANR8503E
statements in the file are in the wrong order. and the file name may be the same when the server
experiences a failure in opening the file.
System action: The volume is not opened.
User response: Refresh your device configuration
information file by issuing the BACKUP DEVCONFIG User response: The server or storage agent can
command. Make sure a library is defined for the device recover from some failures by requesting access to
class. Reissue the command. different volumes. If there is a directory definition
problem, this message may be displayed multiple times
during retries with different volumes. The directory
ANR8498E Drive not defined for library library in
names associated with the device class definition in the
device configuration information file.
server should be checked for correctness in the number
Explanation: The specified command requires that the and names of directory entries. PATH definitions for
specified drive be defined in the device configuration each of the FILE drives should be checked that the
information file for the specified library. This definition number of directories in the PATH definition match the
was not found or the statements in the file are in the number in the server's device class definition and that
wrong order. directories exist and are accessible to servers and
storage agents accessing server directories via their
System action: The command is not processed. own path names. For example, if the server has the
User response: Refresh your device configuration following definition:
information file by issuing the BACKUP DEVCONFIG DEFINE DEVCLASS FILE DEVTYPE=FILE
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
ANR8499I Command accepted. DESTTYPE=DRIVE LIBRARY=FILE DEVICE=FILE
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
System action: The server processes the command. the correct destinations on the storage agent and that
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
definition was not found, or the statements in the file System action: If you were trying to define a storage
are in the wrong order. pool or update a device class associated with a storage
pool, the command fails. If this error is encountered
System action: The command is not processed. during server initialization, server initialization
User response: Refresh your device configuration continues, but operations involving this storage pool
information file by issuing the BACKUP DEVCONFIG 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
received. The actual volume name corresponds to the System action: The server or storage agent stops
file name that the server uses. The server volume name writing to the specified volume.

ANR8504E ANR8505I
User response: The server or storage agent can problem, this message may be displayed multiple times
recover from some failures by requesting access to during retries with different volumes. The directory
different volumes. If there is a directory definition names associated with the device class definition in the
problem, this message may be displayed multiple times server should be checked for correctness in the number
during retries with different volumes. The directory and names of directory entries.
names associated with the device class definition in the
The permissions associated with newly created files
server should be checked for correctness in the number
should be checked to ensure the server and storage
and names of directory entries.
agent can write to newly created files. Depending on
The permissions associated with newly created files the system, a mask value may need to be adjusted. The
should be checked to ensure the server and storage system error or event log should be checked for
agent can write to newly created files. Depending on indications of hardware or software errors from file
the system, a mask value may need to be adjusted. The systems.
system error or event log should be checked for
For a remotely mounted file system, ensure that the
indications of hardware or software errors from file
remote file system is mounted and useable to the
systems.
storage agent. The file system should be checked to
For a remotely mounted file system, ensure that the ensure that sufficient space is available. While the
remote file system is mounted and useable to the server checks space, multiple device classes or servers
storage agent. The file system should be checked to using the same file system can cause the server's space
ensure that sufficient space is available. While the checking to underestimate available space.
server checks space, multiple device classes or servers
For storage agents, PATH definitions for each of the
using the same file system can cause the server's space
FILE drives should be checked to ensure that the
checking to underestimate available space.
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
DEFINE DEVCLASS FILE DEVTYPE=FILE
own path names. For example, if the server has the
DIR=K:\FILECLASS\DIR1,L:\FILECLASS\DIR2 and a
following definition:
storage agent has the following PATH definition:
DEFINE DEVCLASS FILE DEVTYPE=FILE DEFINE PATH STA FILE1 SRCTYPE=SERVER
DIR=K:\FILECLASS\DIR1,L:\FILECLASS\DIR2 and a DESTTYPE=DRIVE LIBRARY=FILE DEVICE=FILE
storage agent has the following PATH definition: DIR=X:\DIR1,X:\DIR2 then system STA must have
DEFINE PATH STA FILE1 SRCTYPE=SERVER drive X set to access directory L:\FILECLASS on the
DESTTYPE=DRIVE LIBRARY=FILE DEVICE=FILE server so that directories DIR1 and DIR2 correspond to
DIR=X:\DIR1,X:\DIR2 then system STA must have the correct destinations on the storage agent and that
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 correct destinations on the storage agent and that
the number of directories match between the PATH and
ANR8505I Verifying path definitions for library
the DEVCLASS definitions.
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
System action: The server processes the verification
server was attempting to synchronize its progress of
for the specified library.
data written with that of the file system. If the file
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
connectivity and configuration of the primary library
System action: The server or storage agent stops
manager paths. Check the library manager of the last
writing to the specified volume. The transaction in
storage agent displayed in the library path verification
progress is rolled back.
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 ANR8511E
compatible drives are online.

ANR8506E The library library name is not
compatible with stand-alone, utility System action: The attempted operation fails.
operations.
User response: Use the QUERY DEVCLASS command
Explanation: The specified library cannot operate in to check the device class's FORMAT and DEVTYPE
stand-alone mode such as DUMP DB or RESTORE DB. values. Compare these values with the equivalent
values for QUERY DRIVE F=D. There must be at least
one online drive with DEVTYPE and FORMAT values
User response: If this is a FILE library, use a device that are compatible with the device class attempting
class that does not use a FILE library. A FILE device this operation. If there are no compatible drives, correct
class does not need a library, and thus, can be updated this configuration and retry the operation.
with LIBRARY="" and SHARED=NO. Update your
device configuration file appropriately for the
ANR8510E No valid path is defined for the
stand-alone operation, and then if needed, return the
ZOSMEDIA library library name .
device class to its original state using a FILE library or
with SHARED=YES when the server is running. Explanation: The storage operation requires that a
path be defined to the ZOSMEDIA library. Without a
PATH defined to the library, the mount request cannot
ANR8507W Volume volume name is using an
resolve the z/OS Media server name.
encryption key that is not unique and
therefore is not secure. System action: The mount request is not processed.
Explanation: Each volume should have a unique User response: Define a library path and specify the
encryption key. This volume inappropriately shares an z/OS Media server with the ZOSMEDIASERVER
encryption key with other volumes. parameter. For instance: consider a ZOSMEDIA library
named ZLIB1 and a TSM server name of SERVER1. The
System action: The operation completes.
z/OS Media server that is accessible using IP address
User response: Moving the data from this volume to of 9.8.7.6 and is listening on port 1492 and is named is
new volume will create a unique encryption key for the ZMEDSRV1. The following commands properly
new volume and make the data more secure. Before configure server SERVER1 for accessing ZLIB1. .
moving the data, mark this volume READONLY to DEFINE LIBRARY ZLIB1 LIBTYPE=ZOSMEDIA
prevent Tivoli Storage Manager from appending data to DEFINE SERVER ZMEDSRV1 SERVERPASS=SECRET
the volume. Then, use the MOVE DATA command to HLA=9.8.7.6 LLA=1492 DEFINE PATH SERVER1 ZLIB1
move the data from this volume to a new volume in SRCTYPE=SERVER DESTTYPE=LIBRARY
your encryption storage pool. ZOSMEDIASERVER=ZMEDSRV1 .
ANR8508E Device type volume volume name cannot ANR8511E Unable to resolve ZOSMEDIASERVER
be written by DB2's archive log mediaservername from the library path.
operation.
Explanation: The storage operation requires that a
Explanation: The specified volume already exists or server defintion exist that matches the
contains data, so that the server cannot allow new ZOSMEDIASERVER name of the library path. Without
archive log data to be written to it. Or there is no space a SERVER defined, the storage operation can not be
available on the destination filespace to write this completed because the request is unable to determine
backup to. the z/OS Media servers HLA and LLA.
System action: The server detects that the given System action: The mount request is not processed.
volume already contains some data that would be
User response: Determine the High Level Address (
overwritten by the DB's archive log operation, or that
HLA ) and Low Level Address ( LLA ) of the z/OS
there is not enough space available.
Media server and use DEFINE SERVER command to
User response: If the specified volume does not build a server definition that represents the z/OS
contain any valuable data, delete it. Media server. The servername that is used to define the
z/OS Media server must match the
ZOSMEDIASERVER name of the library PATH. For
ANR8509E No compatible drives are available for
instance: consider a ZOSMEDIA library named ZLIB1
device class devclass name.
and a TSM server name of SERVER1. The z/OS Media
Explanation: The attempted operation cannot be server that is accessible using IP address of 9.8.7.6 and
completed for the specified device class because there is listening on port 1492 and is named is ZMEDSRV1.
are no available drives. This message can indicate an The following commands properly configure server
invalid FORMAT or DEVTYPE value for the specified SERVER1 for accessing ZLIB1. . DEFINE LIBRARY
device class. The message can also indicate that the ZLIB1 LIBTYPE=ZOSMEDIA DEFINE SERVER
FORMAT and DEVTYPE values are valid, but no ZMEDSRV1 SERVERPASS=SECRET HLA=9.8.7.6

ANR8512E ANR8518E
LLA=1492 DEFINE PATH SERVER1 ZLIB1 assignment based on the data set name.
SRCTYPE=SERVER DESTTYPE=LIBRARY
ZOSMEDIASERVER=ZMEDSRV1
ANR8515W The deletion of volume belonging to
z/OS Media library is imminent,
ANR8512E Cannot specify RETENTION with however the z/OS Media server is
EXPIRATION during DEFINE or unreachable resulting in the TSM Server
UPDATE DEVCLASS. volume inventory reflecting the deleted
volume.
Explanation: The DEFINE DEVCLASS cannot specify
both RETENTION and EXPIRATION, they are conflict Explanation: The z/OS Media server cannot be
parameters. reached during a volume deletion request. The TSM
server continues the operation even though the z/OS
System action: The command request is not
Media server cannot be reached.
processed.
System action: The volume is not deleted on the z/OS
User response: If a device class has an existing
Media server.
EXPIRATION value, the devclass cannot update if
RETENTION is specified. If a device class has existing User response: Deremine why the z/OS Media server
RETENTION value, the device class cannot update if cannot be contacted. Examine the TSM activity log for
EXPIRATION is specified. The two parameters message ANR8515W and carefully consider removing
(RETENTION and EXPIRATION ) are mutually the associated dataset on the z/OS system.
exclusive.
ANR8516W The z/OS Media server is unreachable at
ANR8513E zOS Media Server (server name) HLA and LLA .
password is too long to use for
Explanation: The z/OS Media server cannot be
authentication with TSM for z/OS
reached during a ZOSMEDIA library request. The TSM
Media. The password cannot exceed 16
server may continue the operation even though the
characters.
z/OS Media server cannot be reached.
Explanation: The SERVERPASSWORD must be
System action: The operation likely fails.
specified with 16 characters or less. The password must
match the passphrase option on the target z/OS Media User response: Determine why the z/OS Media server
server. cannot be contacted.
System action: The operation is not processed.
ANR8517E The z/OS Media server is reachable at
User response: Issue the UPDATE SERVER command
HLA and LLA however fails to connect
and specify a SERVERPASSWORD that does not exceed
because of an authentication failure..
16 characters and ensure it contains characters that
match the passphrase option on the z/OS Media server. Explanation: The z/OS Media server could be reached
during a ZOSMEDIA library request. However,
authentication could not be completed. The TSM server
ANR8514W TSM for z/OS Media server (server name)
will not continue the operation because the z/OS
could not extend the FILE volume
Media server connection can be authenticated.
volume name.
Explanation: The z/OS Media server made an attempt
to EXTEND the VSAM LDS FILE volume using the User response: Determine why the z/OS Media server
SECONDARYALLOCATION value from the FILE connection cannot be authenticated. Check to ensure
device class and failed. the PASSPHRASE option on the TSM z/OS Media
server matches the serverpassword of the media server
System action: The WRITE operation fails and the
definiton on the TSM Server. The password cannot
FILE volume is marked "read-only".
exceed 16 characters.
User response: Allow TSM for z/OS Media server to
create EA-enabled VSAM linear data set volumes. 1.
ANR8518E command: Invalid update request for
Use SMS to manage the VSAM Linear data sets that are
drive drive name in library library name.
associated with the prefix attribute of the FILE device
class. 2. Associate the data sets with a data class (an Explanation: An invalid request has been made for
SMS construct) that specifies the extended format and the specified drive. This drive is part of a virtual tape
extended addressability options. To make this library(VTL). The requested operation does not apply
association between data sets and the data class, use an for drives in a VTL.
automatic class selection (ACS) routine to assign the
TSM for z/OS Meida VSAM linear data sets to the System action: The server does not process the
relevant SMS data class. The ACS routine does the command.
ANR8519E ANR8525E
User response: Do not attempt to change cleaning connection cannot be established. Check to ensure the
settings for virtual drives. If this library is not a VTL, z/OS Media server is listening on the target IP address
use the UPDATE LIBRARY command to change the and port address. The protocol violation indicates an
library type to SCSI and retry the operation. application is listening on the target HLA port,
however the application program is not a z/OS Media
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.
TSM server fails the operation.
Explanation: Ensure the z/OS Media server is running
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 TSM Server by searching for z/OS Media
from the system for ACSLS libraries.
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
TSM server fails the operation. specify a value for the element=address paramenter.

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 Tivoli Storage Manager 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 TSM server will update the MOUNTRETENTION parameter value to 0.
not continue the operation because the z/OS Media This will ensure that the mounted volume is
server connection can be established. dismounted after each use.

User response: Determine why the z/OS Media server

ANR8526W ANR8550E (Linux)
System action: The transaction that requires this

ANR8526W The IBM Tape Device Driver settings
library fails.
have been updated and need to be
restarted. The device driver can be User response: Inspect the library. Ensure that the
restarted by either restarting windows library is turned on and ready. Ensure that the library
or reinstalling the IBM Tape Device is configured correctly for the host system.
Driver.
Explanation: The IBM Tape Device Driver settings ANR8530W Volume volume name in drive drive name
have been changed to not automatically reserve the in library library name is not labeled.
drive. By allowing TSM to manage the reservations this
will elminate some reservation warnings and potential Explanation: The label is blank.
mount failures. This is a one time change that requires System action: This volume might be labeled
the device driver to be re-initalized. Reinitalizing the automatically if the AUTOLABEL parameter is set to
device driver can be accomplished by either restarting YES and the library supports automatic labeling.
windows or reinstalling the IBM Tape Device Driver.
Restarting windows is simpler; reinstalling the IBM User response: To label the volume manually, issue
Tape Device Driver is less disruptive. the LABEL LIBVOLUME command. Check the volume
in by issuing the CHECKIN LIBVOLUME command.
System action: Possible reservation conflicts between
hosts.
ANR8550E (AIX) Error opening filespec.
User response: Restart windows or reinstall the IBM
Tape Device Driver to cause the IBM Device Driver to Explanation: An error occurs while attempting an
detect the registry change. open operation.
ANR8527E The default cartridge access port (CAP) User response:
ID is invalid for library library name.
v Refer to the other displayed messages to determine
Explanation: The default CAP ID was specified in the why the open operation has failed. Correct the
CHECKOUT LIBVOLUME command. If the default problem and restart the process.
CAP ID is specified, the CAP priority value must be set v If you have entered a file name ensure that the file
to a nonzero value. name is correct and that it exists.
System action: The system failed to eject the tape
volumes. ANR8550E (HP-UX) Error opening file name.
User response: To verify the CAP priority value, issue Explanation: An error occurs while the server
the QUERY CAP command. If the priority value is 0, attempts a file open operation.
set the CAP priority to a nonzero value and reissue the
CHECKOUT LIBVOLUME command. System action: Server processing continues.
User response:
ANR8528E The slot element address slot element v Refer to the other displayed messages to determine
address is invalid for the library name why the open operation has failed. Correct the
library. problem and restart the process.
Explanation: The slot element address is no longer v If you have entered a file name ensure that the file
valid. This issue might occur when a library is turned name is correct and that it exists.
off or during a hardware malfunction. For a virtual
library, this problem also might occur after the library ANR8550E (Linux) Error opening file name.
is reconfigured or its firmware is updated.
Explanation: An error occurs while the server
System action: The slot in this library is unavailable. attempts a file open operation.
User response: Ensure that the library is turned on System action: Server processing continues.
and that no hardware problems are evident. To verify
the slot element address, use the device driver tool or User response:
virtual library configuration tool. v Refer to the other displayed messages to determine
why the open operation has failed. Correct the
ANR8529E Command: Unable to open library library problem and restart the process.
name by using an open system call. v If you have entered a file name ensure that the file
name is correct and that it exists.
Explanation: Tivoli Storage Manager cannot open the
library.
ANR8550E (Solaris) ANR8552E (Linux)
ANR8550E (Solaris) Error opening file name. ANR8551E (Solaris) An error (error code) occurred
attempts a file open operation. Explanation: An error occurs while the server
attempts a write operation.
User response:
v Refer to the other displayed messages to determine User response: Refer to the other displayed messages
why the open operation has failed. Correct the to determine why the write operation failed. Correct
problem and restart the process. the problem and restart the process.
v If you have entered a file name ensure that the file
name is correct and that it exists. ANR8551E (Windows) An error (error code) occurred
ANR8550E (Windows) Error opening filespec. Explanation: The server detects an error while
attempting a write operation.
attempting an open operation. System action: Server processing continues.
System action: Server processing continues. User response: Refer to the other displayed messages
to determine why the write operation has failed.
User response:
Correct the problem and restart the process.
v Refer to the other displayed messages to determine
why the open operation has failed. Correct the
problem and restart the process. ANR8552E (AIX) An error (error code) occurred during
a read operation.
v If you have entered a file name ensure that the file
name is correct and that it exists. Explanation: An error occurs while attempting a read
operation.
ANR8551E (AIX) An error (error code) occurred during System action: Server processing continues.
a write operation.
Explanation: An error occurs while attempting a write to determine why the read operation failed; correct the
operation. problem and restart the process.
ANR8552E (HP-UX) An error (error code) occurred
during a read operation.
to determine why the write operation failed; correct the
problem and restart the process. Explanation: An error occurs while the server
attempts a read operation.
ANR8551E (HP-UX) An error (error code) occurred System action: Server processing continues.
Explanation: An error occurs while the server to determine why the read operation failed. Correct the
attempts a write operation. problem and restart the process.
ANR8552E (Linux) An error (error code) occurred
to determine why the write operation failed. Correct
the problem and restart the process. Explanation: An error occurs while the server
ANR8551E (Linux) An error (error code) occurred System action: Server processing continues.
Explanation: An error occurs while the server to determine why the read operation failed; correct the
attempts a write operation. problem and restart the process.
to determine why the write operation failed; correct the

ANR8552E (Solaris) ANR8554W (AIX)
System action: The server has detected that the given

ANR8552E (Solaris) An error (error code) occurred
volume already contains data that would be
overwritten by the requested DUMPDB operation.
contain any valuable data, delete it and retry the
System action: Server processing continues. DUMPDB operation, or specify a different volume
name.
to determine why the read operation failed. Correct the
problem and restart the process. ANR8553E (Solaris) Device type volume volume name
cannot be overwritten by DUMPDB
operation.
ANR8552E (Windows) An error (error code) occurred
during a read operation. Explanation: The specified volume already exists or
DUMPDB data to be written to it.
attempting a read operation.
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.
DUMPDB operation, or specify a different volume
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.
System action: The server detects that the given
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.
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
contain any valuable data, delete it and retry the process assumes the device class is devtype=FILE and
DUMPDB operation, or specify a different volume writes to or reads from a file.
name.
to determine why the device class is not defined.
ANR8553E (Linux) Device type volume volume name Correct the problem and restart the command if you do
cannot be overwritten by DUMPDB not wish to write to or read from a file.
operation.
ANR8554W (HP-UX) ANR8556E (AIX)
User response: Correct the problem and start the

ANR8554W (HP-UX) Dump/load command: Device
process again.
class device class name not defined.
Devtype of FILE is assumed.
ANR8555E (HP-UX) An error (error code, error string)
Explanation: The specified device class name is not
occurred during a read operation from
defined with the DUMPLOADDB DEVCLASS option,
disk disk 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.
Correct the problem and restart the command if you do
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, User response: Correct the problem and restart the
to the server in the server options file or the server is process.
not able to define the specified device class.
System action: Processing continues. The dump/load ANR8555E (Solaris) An error (error code, error string)
process assumes the device class is devtype=FILE and occurred during a read operation from
writes to or reads from a file. disk disk name.
User response: Refer to the other displayed messages Explanation: An error occured while attempting a
to determine why the device class is not defined. read from disk.
Correct the problem and restart the command if you do
not wish to write to or read from a file. System action: Server processing continues.
User response: Correct the problem and restart the
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 Explanation: An error occured while attempting a
not able to define the specified device class. read from disk.
System action: Processing continues. The dump/load System action: Server processing continues.
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.
Correct the problem and restart the command if you do ANR8556E (AIX) Error error code (error string)
not wish to write to or read from a file. occurred during a write operation to
disk disk name.
ANR8555E (AIX) Error error code (error string) Explanation: An error occured while attempting a
occurred during a read operation from write to disk.
disk disk name. System action: Server processing continues.
Explanation: An error occured while attempting a User response: Correct the problem and restart the
read from disk. process.

ANR8556E (HP-UX) ANR8577E (Linux)
ANR8556E (HP-UX) An error (error code, error string) ANR8558E (AIX) I/O vector element bufP: buffer
occurred during a write operation to address, len: buffer length, offset: file offset,
disk disk name. errno: errno.
Explanation: An error occured while attempting a Explanation: This is a diagnostic message showing
write to disk. details of an AIO request which had an error. This
message is normally proceeded by ANR8555E or
ANR8556E and offers additional information related to
User response: Correct the problem and restart the the I/O error.
process.
User response: Correct the problem and start the
ANR8556E (Linux) An error (error code, error string)
process again.
occurred during a write operation to
disk disk name.
ANR8577E (AIX) Tivoli Storage Manager was not
Explanation: An error occured while attempting a
able to open the SSL key-ring file file
write to disk.
name. The GSKit return code is return
System action: Server processing continues. code.
User response: Correct the problem and restart the Explanation: Initialization of the SSL environment
process. failed. Connections to SSL ports are not possible.
ANR8556E (Solaris) An error (error code, error string)
User response: Verify that the correct SSL key-ring file
occurred during a write operation to
is in the server instance directory. If the password was
disk disk name.
changed with an external utility, use the SET
Explanation: An error occured while attempting a SSLKEYRINGPW command to resynchronize the
write to disk. key-ring file password with the value that the server
uses. If the problem persists then delete the key-ring
System action: Server processing continues. file and run the DELETE KEYRING server command so
User response: Correct the problem and restart the that the server can generate a new key-ring file.
process.
ANR8577E (HP-UX) Tivoli Storage Manager was not
ANR8556E (Windows) An error (error code) occurred able to open the SSL key-ring file file
during a write operation to disk disk name. The GSKit return code is return
name. code.
Explanation: An error occured while attempting a Explanation: Initialization of the SSL environment
write to disk. failed. Connections to SSL ports are not possible.
System action: Server processing continues. System action: Server operation continues.
User response: Correct the problem and restart the User response: Verify that the correct SSL key-ring file
process. is in the server instance directory. If the password was
SSLKEYRINGPW command to resynchronize the
ANR8557W (AIX) Retrying failed I/O operation for key-ring file password with the value that the server
disk disk name, error number number. uses. If the problem persists then delete the key-ring
Explanation: An error occured while attempting an file and run the DELETE KEYRING server command so
I/O operation on a disk volume. The request will be that the server can generate a new key-ring file.
retried.
System action: The failed I/O operation is attempted ANR8577E (Linux) Tivoli Storage Manager was not
again. able to open the SSL key-ring file file
name. The GSKit return code is return
User response: Correct the problem being reported to code.
avoid more errors in the future, or contact AIX support
for assistance. Explanation: Initialization of the SSL environment
is in the server instance directory. If the password was failed. Connections to SSL ports are not possible.
key-ring file password with the value that the server User response: Delete the key-ring file so that TSM
uses. If the problem persists then delete the key-ring can generate a new one.
file and run the DELETE KEYRING server command so
that the server can generate a new key-ring file.
ANR8578E (Linux) The Tivoli Storage Manager
database does not have a password for
ANR8577E (Solaris) Tivoli Storage Manager was not the SSL key-ring file.
able to open the SSL key-ring file file
name. The GSKit return code is return Explanation: Initialization of the SSL environment has
code. failed. Connections to SSL ports are not possible.
Explanation: Initialization of the SSL environment System action: Server operation continues.
failed. Connections to SSL ports are not possible. User response: Delete the key-ring file so that TSM
System action: Server operation continues. can generate a new one.

is in the server instance directory. If the password was ANR8578E (Solaris) The Tivoli Storage Manager
changed with an external utility, use the SET database does not have a password for
SSLKEYRINGPW command to resynchronize the 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
that the server can generate a new key-ring file. System action: Server operation continues.
User response: Delete the key-ring file so that TSM
ANR8577E (Windows) Tivoli Storage Manager was can generate a new one.
not able to open the SSL key-ring file
file name. The GSKit return code is return ANR8578E (Windows) The Tivoli Storage Manager
code. database does not have a password for
Explanation: Initialization of the SSL environment the SSL key-ring file.
failed. Connections to SSL ports are not possible. Explanation: Initialization of the SSL environment has
System action: Server operation continues. failed. Connections to SSL ports are not possible.
User response: Verify that the correct SSL key-ring file System action: Server operation continues.
is in the server instance directory. If the password was User response: Delete the keyring file so that TSM can
changed with an external utility, use the SET generate a new one.
key-ring file password with the value that the server
uses. If the problem persists then delete the key-ring ANR8579E (AIX) The SSL key ring file does not
file and run the DELETE KEYRING server command so exist, but the Tivoli Storage Manager
that the server can generate a new key-ring file. database contains a password for it.
ANR8578E (AIX) The Tivoli Storage Manager failed. Connections to SSL ports are not possible.
database does not have a password for System action: Server operation continues.
the SSL key-ring file.
User response: Restore a copy of the key ring file or
Explanation: Initialization of the SSL environment has use DELETE KEYRING so that Tivoli Storage Manager
failed. Connections to SSL ports are not possible. can generate a new keyring file and password.
User response: Delete the key-ring file so that TSM ANR8579E (HP-UX) The SSL key ring file does not
can generate a new one. exist, but the Tivoli Storage Manager
database contains a password for it.
ANR8578E (HP-UX) The Tivoli Storage Manager Explanation: Initialization of the SSL environment has
database does not have a password for failed. Connections to SSL ports are not possible.
the SSL key-ring file. System action: Server operation continues.
Explanation: Initialization of the SSL environment has User response: Restore a copy of the key ring file or

use DELETE KEYRING so that Tivoli Storage Manager

ANR8580E (Linux) An SSL write error occurred on
can generate a new keyring file and password.
session session. The GSKit return code is
gsk return code.
ANR8579E (Linux) The SSL key ring file does not
Explanation: An error occurred during an SSL write
exist, but the Tivoli Storage Manager
operation.
failed. Connections to SSL ports are not possible. User response: Retry the operation.
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
exist, but the Tivoli Storage Manager System action: Server operation continues.
ANR8580E (Windows) An SSL write error occurred
System action: Server operation continues. on session session. The GSKit return
code is gsk return code.
use DELETE KEYRING so that Tivoli Storage Manager Explanation: An error occurred during an SSL write
can generate a new keyring file and password. operation.
ANR8579E (Windows) The SSL key ring file does
not exist, but the Tivoli Storage
Manager database contains a password
for it. ANR8581E (AIX) An SSL read error occurred on
gsk return code.
Explanation: An error occurred during an SSL read
operation.
can generate a new keyring file and password. User response: Retry the operation.
ANR8580E (AIX) An SSL write error occurred on ANR8581E (HP-UX) An SSL read error occurred on
session session. The GSKit return code is session session. The GSKit return code is
gsk return code. gsk return code.
Explanation: An error occurred during an SSL write Explanation: An error occurred during an SSL read
operation. operation.
User response: Retry the operation. User response: Retry the operation.
ANR8580E (HP-UX) An SSL write error occurred on ANR8581E (Linux) An SSL read error occurred on
session session. The GSKit return code is session session. The GSKit return code is
gsk return code. gsk return code.
Explanation: An error occurred during an SSL write Explanation: An error occurred during an SSL read
operation. operation.
ANR8581E (Solaris) ANR8583E (Windows)
ANR8581E (Solaris) An SSL read error occurred on ANR8582E (Windows) 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.
ANR8581E (Windows) An SSL read error occurred on ANR8583E (AIX) An SSL socket-initialization 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. 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
return code is gsk return code.
socket-open operation.
handshake process.
ANR8582E (Linux) An SSL open-socket error
ANR8583E (Solaris) An SSL socket-initialization
error occurred on session session. The
GSKit return code is gsk return code.
User response: Retry the operation. handshake process.
ANR8582E (Solaris) An SSL open-socket error
ANR8583E (Windows) An SSL socket-initialization
error occurred on session session. The
System action: Server operation continues. GSKit return code is gsk return code.
User response: Retry the operation. Explanation: An error occurred during an SSL
handshake process.

ANR8584I (AIX) ANR8585I (Windows)

ANR8585I (AIX) The SSL TCP/IP Version 6 driver is
User response: Verify that the client is properly ready for connection with administrative
configured for SSL and retry the operation. clients on port port number.
ANR8584I (AIX) The SSL TCP/IP Version 6 driver is administrative clients using the SSL TCP/IP protocol
ready for connection with clients on on the indicated port number.
port port number.
clients using the SSL TCP/IP protocol on the indicated
port number.
ANR8585I (HP-UX) The SSL TCP/IP Version 6 driver
is ready for connection with
User response: None administrative clients on port port
number.
ANR8584I (HP-UX) The SSL TCP/IP Version 6 driver Explanation: The server can now accept sessions with
is 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.
port number.
ANR8585I (Linux) The SSL TCP/IP Version 6 driver
User response: None is ready for connection with
administrative clients on port port
number.
ANR8584I (Linux) The SSL TCP/IP Version 6 driver
is ready for connection with clients on Explanation: The server can now accept sessions with
port port number. administrative clients using the SSL TCP/IP protocol
on the indicated port number.
clients using the SSL TCP/IP protocol on the indicated System action: Server operation continues.
port number.
User response: None ANR8585I (Solaris) The SSL TCP/IP Version 6 driver
is ready for connection with
administrative clients on port port
ANR8584I (Solaris) 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
administrative clients using the SSL TCP/IP protocol
Explanation: The server can now accept sessions with on the indicated port number.
port number. System action: Server operation continues.
User response: None

ANR8585I (Windows) The SSL TCP/IP Version 6
driver is ready for connection with
ANR8584I (Windows) The SSL TCP/IP Version 6 administrative clients on port port
driver is ready for connection with number.
clients on 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
ANR8586E (AIX) ANR8587E (Windows)
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.
ANR8586E (Solaris) The server was not able to create ANR8587E (Solaris) The server was not able to create
code. return code.
ANR8586E (Windows) The server was not able to ANR8587E (Windows) The server was not able to
create the key-ring file file name. The create the SSL self-signed certificate.
GSKit key-management return code is The GSKit key management return code
return code. is return code.

ANR8588E (AIX) ANR8589E (Solaris)
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 Tivoli Storage Manager clients. Explanation: The GSKit key-management subsystem
could not be initialized.
User response: Verify that permissions to the server
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 Tivoli Storage Manager 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
ANR8589E (Linux) The server was not able to
initialize the GSKit key-management
System action: Server operation continues. key-management return code is return
code.
instance directory are correct. Explanation: The GSKit key-management subsystem
could not be initialized.
ANR8588E (Solaris) The server was not able to System action: Server operation continues.
file name. The GSKit key-management
correct.
ANR8589E (Solaris) The server was not able to
System action: Server operation continues. initialize the GSKit key-management
User response: Verify that permissions to the server key-management return code is return
instance directory are correct. code.
ANR8588E (Windows) The server was not able to could not be initialized.
file name. The GSKit key-management System action: Server operation continues.
Explanation: The certificate export file could not be GSKit key management dynamic-link libraries are
generated for use by the Tivoli Storage Manager clients. correct.

instance directory are correct.
ANR8589E (Windows) ANR8592I (Solaris)

ANR8589E (Windows) The server was not able to
initialize the GSKit key-management User response: None
key-management return code is return
code. ANR8591E (Windows) IBM GSKit version 8 must be
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
number.
Explanation: An SSL connection was established using
the listed SSL version and cipher specification. Explanation: An SSL connection was established using
the listed SSL version, cipher specification, and
System action: Server operation continues. certificate serial number.
User response: None System action: Server operation continues.
ANR8590I (HP-UX) Session session connection is
using SSL version SSL version, cipher
specification cipher specification. ANR8592I (HP-UX) Session session connection is
Explanation: An SSL connection was established using specification cipher specification,
the listed SSL version and cipher specification. certificate serial number certificate serial
number.
User response: None
certificate serial number.
ANR8590I (Linux) Session session connection is using
SSL version SSL version, cipher
specification cipher specification. User response: None.
the listed SSL version and cipher specification. ANR8592I (Linux) Session session connection is using
specification cipher specification certificate
User response: None serial number certificate serial number.
ANR8590I (Solaris) Session session connection is the listed SSL version, cipher specification and
using SSL version SSL version, cipher ceritificate serial number.
specification cipher specification.
User response: None
the listed SSL version and cipher specification.
ANR8592I (Solaris) Session session connection is
User response: None using SSL version SSL version, cipher
specification cipher specification,
certificate serial number certificate serial
ANR8590I (Windows) Session session connection is
number.
specification cipher specification. Explanation: An SSL connection was established using
cerificate serial number.
the listed SSL version and cipher specification.

ANR8592I (Windows) ANR8594I (AIX)
System action: Server operation continues. may be incorrect or the specified new password may
not be acceptable as a new password.
ANR8592I (Windows) Session session connection is User response: To have the server generate a new
using SSL version SSL version, cipher key-ring file password, issue the DELETE KEYRING
specification cipher specification, command; then halt and restart the server. Any 3rd
certificate serial number certificate serial pary certificates which had been imported to the
number. key-ring file previously must be re-imported.
the listed SSL version, cipher specification, and ANR8593E (Solaris) Failure to update key-ring file
cerificate serial number. password.
System action: Server operation continues. Explanation: A SET SSLKEYRINGPW password
UPDATEPW=YES command was issued to change the
key-ring file password. The server was unable to
change the key-ring file's password to the specified
ANR8593E (AIX) Failure to update key-ring file new password. The server's record of the password
password. may be incorrect or the specified new password may
Explanation: A SET SSLKEYRINGPW password
UPDATEPW=YES command was issued to change the System action: Server operation continues.
User response: To have the server generate a new
key-ring file password, issue the DELETE KEYRING
new password. The server's record of the password
command; then halt and restart the server. Any 3rd
may be incorrect or the specified new password may
pary certificates which had been imported to the
key-ring file previously must be re-imported.
User response: To have the server generate a new ANR8593E (Windows) Failure to update key-ring file
key-ring file password, issue the DELETE KEYRING password.
ANR8593E (HP-UX) Failure to update key-ring file new password. The server's record of the password
password. may be incorrect or the specified new password may
UPDATEPW=YES command was issued to change the System action: Server operation continues.
User response: To have the server generate a new
key-ring file password, issue the DELETE KEYRING
may be incorrect or the specified new password may
User response: To have the server generate a new ANR8594I (AIX) Session to address session is using
key-ring file password, issue the DELETE KEYRING SSL version SSL version, cipher
command; then halt and restart the server. Any 3rd specification cipher specification.
Explanation: An outbound SSL connection is being
established to the indicated address using the listed
SSL version and cipher specification.
ANR8593E (Linux) Failure to update key-ring file
password.
User response: None
ANR8594I (HP-UX) ANR8596E (AIX)
ANR8594I (HP-UX) Session to address session is ANR8595I (HP-UX) Session to address session is
using SSL version SSL version, cipher using SSL version SSL version, cipher
specification cipher specification. specification cipher specification,
number.
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 (Linux) Session to address session is using
specification cipher specification. ANR8595I (Linux) Session to address session is using
number.
Explanation: An SSL connection is being established
User response: None to the indicated address using the listed SSL version,
ANR8594I (Solaris) Session to address session is System action: Server operation continues.
specification cipher specification.
ANR8595I (Solaris) Session to address session is
System action: Server operation continues. certificate serial number certificate serial
number.
User response: None
Explanation: An SSL connection is being established
ANR8594I (Windows) 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 (Windows) 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 (AIX) Session to address session is using Explanation: An SSL connection is being established
SSL version SSL version, cipher to the indicated address using the listed SSL version,
specification cipher specification, cipher specification, and cerificate serial number.
number. System action: Server operation continues.
Explanation: An SSL connection is being established User response: None.
ANR8596E (AIX) The certificate identity could not be
System action: Server operation continues. verified.
User response: None. Explanation: The server was unable to open an SSL
connection to the server at address address because the
certificate identity could not be verified. Lack of
verification happens when the certificate ownership

information does not match the domain name or IP parameter of the DEFINE SERVER command) is
address. correct. If you are using a self-signed certificate, ensure
that it was created on a server at the same address as
System action: The session ends.
specified in the DEFINE SERVER command.
User response: Ensure that the server domain name or
the IP address (the value of the HLADDRESS
ANR8596E (Windows) The certificate identity could
parameter of the DEFINE SERVER command) is
not be verified.
correct. If you are using a self-signed certificate, ensure
that it was created on a server at the same address as Explanation: The server was unable to open an SSL
specified in the DEFINE SERVER command. connection to the server at address address because the
ANR8596E (HP-UX) The certificate identity could not
information does not match the domain name or IP
be verified.
address.
Explanation: The server was unable to open an SSL
certificate identity could not be verified. Lack of User response: Ensure that the server domain name or
verification happens when the certificate ownership the IP address (the value of the HLADDRESS
information does not match the domain name or IP parameter of the DEFINE SERVER command) is
address. correct. If you are using a self-signed certificate, ensure
specified in the DEFINE SERVER command.
the IP address (the value of the HLADDRESS
ANR8597E (AIX) Certificate information could not
parameter of the DEFINE SERVER command) is
be retrieved.
that it was created on a server at the same address as Explanation: The server was unable to obtain
specified in the DEFINE SERVER command. certificate inforamtion for an SSL connection to the
server at address address.
ANR8596E (Linux) The certificate identity could not System action: The session ends.
be verified.
User response: Ensure that the certificate for the target
Explanation: The server was unable to open an SSL server was imported to this server's key-ring file. If you
connection to the server at address address because the are using a 3rd-party certificate, you can test it with a
certificate identity could not be verified. Lack of session to the target server's SSL port with a browser
verification happens when the certificate ownership such as Firefox.
information does not match the domain name or IP
address.
ANR8597E (HP-UX) Certificate information could not
System action: The session ends. be retrieved.
User response: Ensure that the server domain name or Explanation: The server was unable to obtain
the IP address (the value of the HLADDRESS certificate inforamtion for an SSL connection to the
parameter of the DEFINE SERVER command) is server at address address.
specified in the DEFINE SERVER command. User response: Ensure that the certificate for the target
server was imported to this server's key-ring file. If you
are using a 3rd-party certificate, you can test it with a
ANR8596E (Solaris) The certificate identity could not
session to the target server's SSL port with a browser
be verified.
such as Firefox.
Explanation: The server was unable to open an SSL
ANR8597E (Linux) Certificate information could not
be retrieved.
information does not match the domain name or IP Explanation: The server was unable to obtain
address. certificate inforamtion for an SSL connection to the
server at address address.
the IP address (the value of the HLADDRESS 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
such as Firefox. Explanation: The server is enabled to run SSL sessions
from the server to other servers during node
replication.
ANR8597E (Solaris) Certificate information could not
be retrieved. System action: Processing continues.
Explanation: The server was unable to obtain User response: None. The server can communicate via
certificate inforamtion for an SSL connection to the SSL to other servers. Prior to starting the server,
server at address address. certificates must be loaded in the server's keyring file
(cert.kdb).
ANR8598I (Solaris) 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 (Windows) Certificate information could System action: Processing continues.
not 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 (Windows) Outbound SSL Services were
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.
ANR8598I (AIX) Outbound SSL Services were
loaded.
SSL to other servers. Prior to starting the server,
Explanation: The server is enabled to run SSL sessions certificates must be loaded in the server's keyring file
from the server to other servers during node (cert.kdb).
replication.
System action: Processing continues. ANR8675E (AIX) File name: File already exists for File
or Filetext Exit.
SSL to other servers. Prior to starting the server, Explanation: The specified file already exists and the
certificates must be loaded in the server's keyring file file-exit option was set to PRESERVE.
(cert.kdb).
System action: Server continues running.
User response: Specify a non-existent file.
ANR8598I (HP-UX) Outbound SSL Services were
loaded.
ANR8675E (HP-UX) File name with environment variable
Explanation: The server is enabled to run SSL sessions
DSMSERV_DIR: File already exists for
from the server to other servers during node
File or FileText Exit.
replication.
Explanation: The specified file already exists and the
file-exit option was set to PRESERVE.
SSL to other servers. Prior to starting the server,
certificates must be loaded in the server's keyring file User response: Specify a non-existent file.
(cert.kdb).

ANR8675E (Linux) ANR8677E (Windows)
continues running if already up.

ANR8675E (Linux) File name with environment variable
DSMSERV_DIR: File already exists for User response: Use the server supplied sample
File/FileText Exit, overwrite option not makefile and export files to compile-link the user-exit
set to YES. module. Make sure the export.ref file contains the
server-defined function name, and the module actually
Explanation: The specified file already exists and the
contains the server-defined function name, with one
overwrite option was not set to Yes.
void parameter declared.
User response: Specify another file or set the ANR8677E (Linux) User specified module, with
overwrite option to YES in the server options file. environment variable DSMSERV_DIR:
Cannot load into server, system errno =
Error number generated by Solaris.
ANR8675E (Solaris) File name with environment variable
DSMSERV_DIR: File already exists for Explanation: The server was unable to load the
File/FileText Exit, overwrite option not module specified. The module is not a properly
set to YES. C-compiled and linked dynamic module.
Explanation: The specified file already exists and the System action: Server continues running.
overwrite option was not set to Yes.
User response: Use the supplied sample makefile, c ,
System action: Server continues running. and h files to generate the user-exit module. Make sure
the module contains product-defined function name
User response: Specify another file or set the
adsmV3UserExit, and the module actually contains the
overwrite option to YES in the server options file.
product-defined function name, with one void *
parameter declared, and returns void.
ANR8675E (Windows) File name with path within
registry.: File already exists for File or
ANR8677E (Solaris) User specified module, with
FileText Exit.
environment variable DSMSERV_DIR:
Explanation: The specified file already exists and the Cannot load into server, system errno =
File/FileText exit option was set to PRESERVE. Error number generated by Solaris.
System action: Server continues running. Explanation: The server was unable to load the
module specified. The module is not a properly
User response: Specify a non-existent file. C-compiled and linked dynamic module.
ANR8677E (AIX) User specified module: Cannot load
into server, AIX system error number User response: Use the server supplied sample
number. makefile, c, and h files to generate the user-exit
module. Make sure the module contains server-defined
Explanation: The server was unable to load the function name adsmV3UserExit, and the module
module specified. The module is not a properly actually contains the server-defined function name,
C-compiled and linked dynamic module. with one void * parameter declared, and returns void.
System action: Server initialization stops or server
continues running if already up. ANR8677E (Windows) User specified module, with path
User response: Use the server supplied sample within registry: Cannot load into server,
makefile and export files to compile-link the user-exit system errno = Error number generated by
module. Make sure the export.ref file contains the Windows.
server-defined function name, and the module actually Explanation: The server was unable to load the
contains the server-defined function name, with one module specified. The module is not a properly
void parameter declared. C-compiled and linked dynamic module.
ANR8677E (HP-UX) User specified module, with
environment variable DSMSERV_DIR: User response: Use the server supplied sample
Cannot load into server, system errno = makefile compile-link the user-exit module.
Error number generated by HP-UX.
Explanation: The server was unable to load the
module specified. The module is not a properly
C-compiled and linked dynamic module.
ANR8678E (AIX) ANR8679W (Linux)
User response: Use the server supplied sample

ANR8678E (AIX) Cannot bind User specified module
makefile, c and header files to create the user exit
into server. AIX system error number.
module. Make sure the shared library module contains
Explanation: The server was unable to bind with the a function named adsmV3UserExit of type void, with
module specified. one parameter of a void *.
continues running if already up. ANR8678E (Windows) Cannot find/set User specified
function name within DLL. in User specified
DLL library name, with registry path,
makefile and export files to compile-link the user-exit
system errno = Error number generated by
module. Make sure the export.ref file contains the
Windows.
contains the server-defined function name, with 1 void Explanation: The server was unable to find and/or
parameter declared. The module may contain a global bind with the function name in the DLL specified.
variable name that conflicts with the server's.
ANR8678E (HP-UX) Cannot bind User specified
makefile to compile-link the user-exit module. Make
module, with environment variable
sure there is a function name in the DLL as specified in
DSMSERV_DIR into server, system errno
the server options file. Make sure the function only
= Error number generated by HP-UX.
accepts one argument, a void pointer.
Explanation: The server was unable to bind with the
module specified.
ANR8679W (AIX) A user-exit module is already
System action: Server initialization stops or server loaded.
Explanation: A user-exit module was loaded
User response: Use the server supplied sample previously. Another user-exit module cannot be loaded.
makefile and export files to compile-link the user-exit
System action: Server initilization stops or server
module. Make sure the export.ref file contains the
contains the server-defined function name, with one User response: To load a new user-exit module, halt
void parameter declared. The module may contain a the server and then restart the server with the new
global variable name that conflicts with the server's. user-exit module.
ANR8678E (Linux) Cannot bind User specified module, ANR8679W (HP-UX) There is already an user-exit
with environment variable DSMSERV_DIR loaded.
into server, system errno = Error number
generated by Solaris. Explanation: There was a previous successful load of
an user-exit module, thus server cannot load another
Explanation: The server was unable to bind with the one.
module specified. The server could not find a function
named adsmV3UserExit in the module. System action: Server initialization stops or server
User response: To load a new user-exit module, the
User response: Use the supplied sample makefile, c server must be halted and then restart the server with
and header files to create the user exit module. Make the new user-exit module.
sure the shared library module contains a function
named adsmV3UserExit of type void, with one
parameter of a void *. ANR8679W (Linux) Unable to unload user exit
module: system errno = Error number
generated by Solaris.
ANR8678E (Solaris) Cannot bind User specified module,
with environment variable DSMSERV_DIR Explanation: The server was not able to unload the
into server, system errno = Error number user-exit module.
generated by Solaris. System action: Server continues running.
Explanation: The server was unable to bind with the User response: The server should be stopped at the
module specified. The server could not find a function earliest possible time before the user exit is to be
named adsmV3UserExit in the module. reactivated.

ANR8679W (Solaris) ANR8681I (Linux)
ANR8679W (Solaris) Unable to unload user exit ANR8680W (Solaris) There is already a named file
module: system errno = Error number used for the file or filetext exit.
generated by Solaris.
Explanation: There was a previous file open for the
Explanation: The server was not able to unload the file or filetext exit. The server cannot open another one.
user-exit module.
System action: Server continues running. continues running if already up.
User response: The server should be stopped at the User response: To start a new file for the file or the
earliest possible time before the user exit is to be filetext exit, halt the server, then restart the server with
reactivated. a new file name.
ANR8679W (Windows) There is already an user-exit ANR8680W (Windows) There is already a file used
loaded. for the file or filetext exit.
Explanation: There was a previous successful load of Explanation: There was a previous file open for the
an user-exit module, thus server cannot load another file or filetext exit. The server cannot open another one.
one.
User response: To start a new file for the exit, halt the
User response: To load a new user-exit module, halt server, then restart the server with a new file name.
the server and then restart the server with the new
user-exit module.
ANR8681I (AIX) Connected to Tivoli event server at
node name on port port.
ANR8680W (AIX) A file used for the file or filetext
Explanation: The server successfully established a
exit is already opened.
connection with the Tivoli event server on the specified
Explanation: A file for the file or filetext exit was node name and port.
previously opened. The server cannot open another
System action: The server sends events to the Tivoli
one.
event server using this connection.
User response: To start a new file for the file or
ANR8681I (HP-UX) Connected to Tivoli event server
filetext exit, halt the server, then restart the server with
at node name on port port.
the new file name.
ANR8680W (HP-UX) There is already a file used for
node name and port.
the file or filetext exit.
file or filetext exit. The server cannot open another one.
ANR8681I (Linux) Connected to Tivoli event server
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. Explanation: The server successfully established a
node name and port.
ANR8680W (Linux) There is already a file used for
the file or filetext exit. System action: The server sends events to the Tivoli
file or filetext exit. The server cannot open another one. User response: None.
User response: To start a new file for the exit, halt the
server, then restart the server with a new file name.
ANR8681I (Solaris) ANR8683E (HP-UX)
User response: Ensure that the Tivoli event server is

ANR8681I (Solaris) Connected to Tivoli event server
running on the specified system. If the system on
which the event server is running does not support the
Explanation: The server successfully established a TCP/IP Portmapper, then ensure that TECPORT is
connection with the Tivoli event server on the specified specified in the server options file.
node name and port.
System action: The server sends events to the Tivoli ANR8682E (Solaris) Unable to determine port of
event server using this connection. Tivoli event server on node name.
User response: None. Explanation: The server was unable to determine the
TCP/IP port on which the Tivoli event server on node
name is listening.
ANR8681I (Windows) Connected to Tivoli event
server at node name on port port. System action: Event logging to the Tivoli event
server is disabled.
connection with the Tivoli event server on the specified User response: Ensure that the Tivoli event server is
node name and port. running on the specified system. If the system on
TCP/IP Portmapper, then ensure that TECPORT is
specified in the server options file.
ANR8682E (Windows) Unable to determine port of
ANR8682E (AIX) Unable to determine port of Tivoli Tivoli event server on node name.
event server on node node name.
Explanation: The server was unable to determine the
Explanation: The server was unable to determine the TCP/IP port on which the Tivoli event server on node
TCP/IP port for the Tivoli event server on node node name is listening.
name.
System action: Event logging to the Tivoli event
System action: Event logging to the Tivoli event server is disabled.
server is disabled.
User response: Ensure that the Tivoli event server is running on the specified system. If the system on
running on the specified system. If the system on which the event server is running does not support the
which the event server is running does not support the TCP/IP Portmapper, then ensure that TECPORT is
TCP/IP Portmapper, then ensure that TECPORT is specified in the server options file.
specified in the server options file.
ANR8683E (AIX) Unable to connect to the Tivoli
ANR8682E (HP-UX) Unable to determine port of event server at node node name on port
Tivoli event server on node name. port.
Explanation: The server was unable to determine the Explanation: The server was unable to establish a
TCP/IP port on which the Tivoli event server on node TCP/IP connection with the Tivoli event server on
name is listening. node node name at port port.
System action: Event logging to the Tivoli event System action: Event logging to the Tivoli event
server is disabled. server is disabled.
User response: Ensure that the Tivoli event server is User response: Ensure that the Tivoli event server is
running on the specified system. If the system on running on the specified system. If the system on
which the event server is running does not support the which the event server is running does not support the
TCP/IP Portmapper, then ensure that TECPORT is TCP/IP Portmapper, then ensure that the value
specified in the server options file. specified for TECPORT in the server options file is
correct.
ANR8682E (Linux) Unable to determine port of

Tivoli event server on node name. ANR8683E (HP-UX) Unable to connect to the Tivoli
event server at node name on port port.
Explanation: The server was unable to determine the
TCP/IP port on which the Tivoli event server on node Explanation: The server was unable to establish a
name is listening. TCP/IP connection with the Tivoli event server on node
name at port port.
server is disabled.


ANR8684E (AIX) Unable to connect to the Tivoli
server is disabled.
event server because TCP/IP is not
User response: Ensure that the Tivoli event server is available.
Explanation: The server was unable to establish a
TCP/IP connection with the Tivoli event server because
TCP/IP Portmapper, then ensure that the value
TCP/IP services were not available.
specified for TECPORT in the server options file is
correct. System action: Event logging to the Tivoli event
server is disabled.
ANR8683E (Linux) Unable to connect to the Tivoli User response:
event server at node name on port port. v Ensure that COMMMETHOD TCPIP is specified in
Explanation: The server was unable to establish a the server options file.
TCP/IP connection with the Tivoli event server on node v If COMMMETHOD TCPIP was specified, use the
name at port port. BEGIN EVENTLOGGING TIVOLI command to
manually start event logging to the Tivoli event
server once server initialization has completed.
server is disabled.
ANR8684E (HP-UX) Unable to connect to the Tivoli
event server because TCP/IP is not
available.
specified for TECPORT in the server options file is Explanation: The server was unable to establish a
correct. TCP/IP connection with the Tivoli event server because
ANR8683E (Solaris) Unable to connect to the Tivoli System action: Event logging to the Tivoli event
event server at node name on port port. server is disabled.
Explanation: The server was unable to establish a User response:
TCP/IP connection with the Tivoli event server on node v Ensure that COMMMETHOD=TCPIP is specified in
name at port port. the server options file, or that
System action: Event logging to the Tivoli event COMMMETHOD=NONE is not specified.
server is disabled. v If COMMMETHOD=TCPIP was specified, use the
BEGIN EVENTLOGGING TIVOLI command to
specified for TECPORT in the server options file is ANR8684E (Linux) Unable to connect to the Tivoli
correct. event server because TCP/IP is not
available.
ANR8683E (Windows) Unable to connect to the Explanation: The server was unable to establish a
Tivoli event server at node name on port TCP/IP connection with the Tivoli event server because
port. TCP/IP services were not available.
Explanation: The server was unable to establish a System action: Event logging to the Tivoli event
TCP/IP connection with the Tivoli event server on node server is disabled.
name at port port.
User response:
System action: Event logging to the Tivoli event v Ensure that COMMMETHOD=TCPIP is specified in
server is disabled. the server options file, or that
User response: Ensure that the Tivoli event server is COMMMETHOD=NONE is not specified.
running on the specified system. If the system on v If COMMMETHOD=TCPIP was specified, use the
which the event server is running does not support the BEGIN EVENTLOGGING TIVOLI command to
TCP/IP Portmapper, then ensure that the value manually start event logging to the Tivoli event
specified for TECPORT in the server options file is server once server initialization has completed.
correct.
ANR8684E (Solaris) ANR8743E
ANR8684E (Solaris) Unable to connect to the Tivoli ANR8687E (AIX) Error generating core dump, errno
event server because TCP/IP is not system errno.
available.
Explanation: The server was unable to generate the
Explanation: The server was unable to establish a requested core dump. The errno indicates the reason
TCP/IP connection with the Tivoli event server because AIX was unable to complete the request.
server is disabled.
User response:
ANR8740W Number of automated library slots (slots
v Ensure that COMMMETHOD=TCPIP is specified in in use) exceeds license terms (slots
the server options file, or that licensed).
COMMMETHOD=NONE is not specified.
Explanation: The number of slots in use within
v If COMMMETHOD=TCPIP was specified, use the
automated libraries exceeds the licensed value.
manually start event logging to the Tivoli event System action: The operation completes.
User response: Contact your service representative to
update license values for slots in automated libraries,
ANR8684E (Windows) Unable to connect to the or reduce the number of slots in use by issuing
Tivoli event server because TCP/IP is CHECKOUT LIBVOLUME commands as necessary.
not available.
Explanation: The server was unable to establish a ANR8741E CHECKIN LIBVOLUME not permitted
TCP/IP connection with the Tivoli event server because with current license terms.
Explanation: The CHECKIN LIBVOLUME operation is
System action: Event logging to the Tivoli event not permitted because the current license terms do not
server is disabled. allow it.
User response: System action: The command fails.
v Ensure that COMMMETHOD=TCPIP is specified in User response: Contact your service representative to
the server options file, or that update license values for slots in automated libraries,
COMMMETHOD=NONE is not specified. or reduce the number of slots in use by issuing
v If COMMMETHOD=TCPIP was specified, use the CHECKOUT LIBVOLUME commands as necessary.
server once server initialization has completed. ANR8742E This server is not licensed to support
the device type device type. Device
Support Module module number is
ANR8685I (AIX) Core dump being generated to file required.
core dump file
Explanation: A DEFINE DRIVE command or a
Explanation: The server has started generating a volume mount operation cannot be processed because
coredump to the specified file as a result of a user the server is not licensed to support the required device
request. type.
System action: Server operation continues. System action: The operation fails.
User response: None. User response: Contact your service representative to
update the server license terms so that support for the
required device type is enabled.
ANR8686I (AIX) Core dump successfully generated
Explanation: The server has successfully generated the
ANR8743E This server is not licensed to support
requested core dump.
library device name. Device Support
System action: Server operation continues. Module module number is required.
User response: None. Explanation: Either a DEFINE LIBRARY command, a
volume mount operation, or library initialization cannot
be processed because the server is not licensed to
support the given library.

ANR8744E ANR8751W

ANR8748I Checking in volumes in search mode in
library library name- CANCEL
given library device is enabled.
PENDING.
ANR8744E Command: Current license terms do not
permit this operation.
CHECKIN LIBVOLUME process on the server. Volumes
Explanation: The specified command failed because were being checked into the given library in search
the current license terms do not permit it. mode, but the process was canceled by an
administrator.
System action: The background process operation is
User response: Contact your service representative to being terminated.
update the server license terms so that the requested
operation can be processed. User response: None.
ANR8745E Support for the 3590 device type is ANR8749E Library order sequence check on library
disabled for library library name. library name.
Explanation: The requested operation fails because Explanation: An attempt has been made to mount or
support for the 3590 device type is not currently demount a volume, but the attempt fails for one of the
enabled for the specified library. following reasons:
System action: The operation fails. v Mount is already in progress or a volume is already
mounted.
User response: Make sure the ENABLE3590LIBRARY v Mount is already pending.
option is specified in the server options file, and that
the scratch category number for 3590 volumes does not v Demount is already pending.
conflict with the private category or the CARTRIDGE v Demount was requested but no volume is mounted.
volume scratch category.
User response: This error usually occurs when a
ANR8746E Device type device type is not supported
demount fails and a cartridge is left in the drive. All
in this release.
subsequent mounts fail while attempting to insert
Explanation: The specified device type cannot be used another cartridge into the same drive. Demount the
by this release/platform of the server. cartridge using the library manager or perform an
AUDIT LIBRARY operation on the designated library.
System action: The device cannot be used. Retry the operation.
User response: Contact your sales or service
representative to upgrade to the latest release of the ANR8750E Volume is incompatible with specified
server. device type in library library name.
Explanation: An attempt has been made to mount or
ANR8747I Checking in volume volume name in check in a volume, but the attempt fails because the
library library name- CANCEL cartridge being mounted is not compatible with the
PENDING. drive (For example, attempting to mount a 3590
Explanation: In response to a QUERY PROCESS cartridge on a 3490 drive).
command, this message displays the status for a System action: The operation fails.
CHECKIN LIBVOLUME process on the server. The
given volume was being checked in to the designated User response: Ensure the DEVTYPE parameter on
library, but the process was canceled by an the CHECKIN command matches the device type of
administrator. the drive. Retry the operation.
System action: The background process operation is in
a wait queue. When the process comes off the queue, it ANR8751W This server is not licensed to support
will be terminated. the device type device type. Managed
Library license is required.
Explanation: This message is issued when a DEFINE
DRIVE command or a volume mount operation uses a
device class that is not licensed on the server.
System action: The operation fails if this is a
try-and-buy server. For purchased servers, this message
ANR8752W ANR8759W
is to warn you that you are not in compliance with

ANR8756E For optical libraries, you must specify
registered license terms.
CHECKLABEL=YES.
Explanation: Optical libraries require the
CHECKLABEL parameter to be set to YES
ANR8752W This server is not licensed to support User response: Reissue the command and specify the
library device type. Managed Library CHECKLABEL=YES option.
license is required.
Explanation: This message is issued when a DEFINE ANR8757W This server is not licensed to support
LIBRARY command or a volume mount operation uses library device type. Extended Edition
a device class that is not licensed on the server. license is required.
System action: The operation fails if this is a Explanation: This message is issued when a DEFINE
try-and-buy server. For purchased servers, this message LIBRARY command or a volume mount operation uses
is to warn you that you are not in compliance with a device class that is not licensed on the server.
registered license terms.
System action: The operation fails if this is a
User response: Contact your service representative to try-and-buy server. For purchased servers, this message
update the server license terms so that support for the is to warn you that you are not in compliance with
required device type is enabled. registered license terms.
ANR8753W This server is not licensed to support update the server license terms so that support for the
library library name. Library Sharing is required device type is enabled.
required.
Explanation: This message is issued when a DEFINE ANR8758W The number of online drives in the VTL
LIBRARY command or library initialization for a library library name does not match the
library that requires library sharing and library sharing number of online drive paths for source
is not licensed on the server. source name.
System action: The operation fails if this is a Explanation: If the number of online drives in the
try-and-buy server. For purchased servers, this message library does not match the number of online paths to
is to warn you that you are not in compliance with drives in the library for any applicable source, it might
registered license terms. cause the server to choose a drive that lacks a valid
path definition. The server will then retry the mount
operation and any retry could adversely affect mount
performance.
System action: The operation continues, but receiving
this message indicates that there might be a possible
ANR8754E Command: There is already a request to
mount retry if the selected drive does not have a valid,
delete library libary name.
online path defined.
Explanation: The designated library cannot be deleted
User response: Evaluate all drive path definitions.
or updated because there is a request to delete the
Define drive paths for any drives that lack a path
library already.
definition for any applicable source (for example
System action: The command is not processed. storage agents). Validate that all drive path definitions
are online. If a drive path is offline for a hardware
User response: None. reason, resolve the hardware issue and update the path
so that it is back online.
ANR8755E Command: There is already a request to
update library library name. ANR8759W The drive name drive in the lib name
Explanation: The designated library cannot be deleted library is owned by owner name.
because there is a request to update the library already. Explanation: If a drive is owned by a library client or
System action: The command is not processed. a storage agent, the library manager does not verify the
drive access and readiness during the library manager
User response: None. initialization.

ANR8760I ANR8766I
User response: In a shared library environment, the

owner of a tape drive can change. If a tape drive is
processed: library library name not
owned by a library client or storage agent, the library
defined.
manager cannot access the tape drive. For example, if a
library client or storage agent owns a tape drive, but Explanation: The indicated volume is not processed
the library manager halts or fails to respond, on since the designated library has not been defined or has
startup, the library manager remembers the library been deleted.
client or storage agent that owns the drive, and skips
System action: The volume is not processed.
processing this drive. If the library client or storage
agent is not synchronized with the library manager and User response: Reissue the command using a different
has no record of owning the drive, this can result in an library name, or define the library before retrying the
inability to use the drive. In this case, you might need command.
to reset the drive reservation from the host machine of
the library client or storage agent.
processed: the operation is not allowed
ANR8760I Cancel in progress. for library type library type.
Explanation: The MOVE MEDIA command has been Explanation: The indicated volume is not processed
canceled and will end when resources have been freed since the requested operation is not allowed for
for the background process. This message may be libraries of the given type.
for a MOVE MEDIA command. System action: The volume is not processed.

ANR8765I Request number: device type volume volume
name in location location name is required
ANR8761I Number of volumes processed: number for use in library library name; CHECKIN
LIBVOLUME required within time limit
Explanation: The MOVE MEDIA command has
minutes.
processed the number of volumes displayed. This
message may be displayed in response to a QUERY Explanation: A mount request has been made for a
PROCESS command for a MOVE MEDIA command. volume that is defined in a storage pool, but which is
currently checked out of the given library and stored in
the location shown.
System action: The server waits until it detects that
the volume has been checked into the library, or the
ANR8762E The drive drive name in the library library time limit expires.
name was unable to obtain an encryption
User response: Obtain the required volume from the
key from the encryption key
indicated location, and insert it into the library by
management.
issuing a CHECKIN LIBVOLUME command. Use the
Explanation: The encryption key manager did not SWAP=YES option of the CHECKIN LIBVOLUME
respond to the drive or library that is managed by the command if the library is currently full; this process
Tivoli Storage Manager server. Since Tivoli Storage allows the server to select an appropriate volume to be
Manager is not managing the encryption keys, there is swapped out in order to make room for the required
an issue with the encryption key manager, the drive, or volume.
the library.
System action: The operation fails. ANR8766I MOVE MEDIA command: CHECKOUT
LIBVOLUME command for volume volume
User response: This is most likely a problem with the
name in library library name completed
encryption key manager (for example, a timeout or
successfully; Place the ejected volume in
communication failure between the encryption key
location location name.
manager and the drive or library). Correct any issues
with the encryption key manager and try the operation Explanation: The CHECKOUT LIBVOLUME operation
again. If the problem persists, contatct IBM hardware has completed successfully for the indicated volume in
support. the given library. Place the ejected volume in the
indicated location.
System action: The volume is either deleted from the
library inventory (if its status is something other than
DATA) or marked not present (if its status is DATA).
ANR8767I ANR8774W
User response: If an *UNKNOWN* location is defined but the server cannot load the external library
displayed, issue UPDATE STGPOOL OVFLOCATION manager.
command to define an overflow location name to be
System action: The server continues, but the external
used on the subsequent MOVE MEDIA command. For
library cannot be accessed.
the volumes ejected with an *UNKNOWN* location,
use UPDATE VOLUME LOCATION command to User response: Verify that the EXTERNALMANAGER
update its location to your overflow location name. parameter for the external library is specified correctly
on the DEFINE LIBRARY or UPDATE LIBRARY
command.
volumes processed. Volumes sent to library
library name for checkout: number volumes ANR8771E Volume volume name in library library
sent. name is deleted. External Library is not
synchronized with the server. Audit
Explanation: The MOVE MEDIA command has
required.
processed the number of volumes shown. Currently, the
MOVE MEDIA command has sent for processing the Explanation: The server deleted a volume from its
number of volumes shown to the library shown. This inventory, and its attempt to inform the external library
message may be displayed in response to a QUERY manager has failed.
PROCESS command for a MOVE MEDIA command.
System action: The server may continue to access the
System action: Server operation continues. library, but some volumes may not be accessible until
the external library is synchronized with the server.
User response: Perform the appropriate type of
processing on the external library in order to
ANR8768E File file name on volume drive name could
synchronize it with the server.
not be found.
Explanation: The server was unable to find the
ANR8772I Moving volume volume name (if known)
specified file name on the indicated volume. For
from drive drive name to slot slot element
removable file device classes, each volume maintains
number in library library name.
data using a file name which is the same as the volume
name and the label value on the volume. Explanation: A volume found in the drive during
library initialization is being moved to the slot.
System action: The volume is moved from the drive
User response: Ensure that the proper volume has
to the slot.
been placed into the drive. If you are creating a
removable file device class volume by copying data User response: None.
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
have the same name as the label. CHECKLABEL=NO and SEARCH=YES
for library type library.
ANR8769E External media management function Explanation: If a barcode reader is not installed and
request type returned result=result. detected by the server, the server requires the ability to
check the tape label when searching for new volumes
Explanation: A request of the indicated function type in a VTL or SCSI tape library. The CHECKLABEL=NO
was sent to the external library manager program, and SEARCH=YES parameters on the CHECKIN
which returned a result code which was not SUCCESS. LIBVOL command are not compatible.
System action: The server continues, but the server System action: The command fails.
operation that was being attempted fails.
User response: Reissue the CHECKIN LIBVOL
User response: Consult the documentation for the command and specify CHECKLABEL=YES.
external media management program to determine how
to recover from the error condition. Then attempt the
server operation again. ANR8774W Volume volume name not checked into
library library name but is using category
category number.
ANR8770W Unable to load external library manager
filespec. Explanation: While processing a DEFINE LIBRARY or
AUDIT LIBRARY command for the given library, the
Explanation: A library of LIBTYPE=EXTERNAL is server found a volume that was not checked into the
library (with the CHECKIN LIBVOL command), but is

ANR8775I ANR8779E
assigned to one of the categories in use by that library.

ANR8777E Mount for volume volume name failed;
System action: If the volume category equals the media performance is degraded.
value of the library SCRATCHCAT the category is
Explanation: The VCR data on the volume is lost or
changed to the value of the library PRIVATECAT. This
corrupted, resulting in degraded tape positioning. The
is to prevent the library from loading the volume when
mount fails because the tape drive was configured to
a scratch volume is requested.
fail mounts that indicate this condition.
User response: If the volume is to be used by the
System action: The client command fails and the
server, it does not have to be reassigned but it must be
transaction is rolled back.
checked into the library with the CHECKIN LIBVOL
command. If the volume is not to be used by the User response: Until the VCR data can be restored,
server, use the mtlib program to reassign the volume to the user can issue the UPDATE VOLUME command to
its correct category. For details about the mtlib make the volume unavailable. There are two methods
program, refer to the documentation provided with the to restore the VCR data. The first method uses the
library device. MOVE DATA command to move the data off the tape
and to return the tape to scratch or empty status. The
VCR data is rebuilt when the empty tape is rewritten
ANR8775I Drive drive name unavailable at library
from the beginning-of-tape. The second method
manager.
rebuilds the VCR by loading the tape and locating
Explanation: The specified drive availability status at directly to the end-of-data. This is done by the server in
the library manager has changed from available to normal use whenever data is appended to the end of
unavailable. the tape. It can also be done independent of the server
by loading the tape in an unused drive and using the
System action: The drive status on the server is tapeutil program. Select the tapeutil option "Space to
updated to reflect the availability to that of the library End-of-Data".
manager. The drive will not be considered as a
candidate for the mount or demount request.
ANR8778W Scratch volume volume name changed to
User response: Contact your service representative to Private Status to prevent re-access.
determine the cause of the drive becoming unavailable.
Once the service representative has determined the Explanation: The scratch volume encountered an error
cause and changed the availability status to available at during mount processing that makes it unusable. The
the library manager, the server will resume use of the status of the volume is changed to private so that it is
drive. not selected for future scratch mounts. (Although the
status has become private, it is not defined to a storage
pool.)
ANR8776W Volume volume name in drive drive name
contains lost VCR data; performance System action: Processing continues with another
may be degraded. scratch volume.
Explanation: The Vital Cartridge Records of the User response: See previous error messages to
cartridge in the drive are lost or corrupted. This results determine the cause of the mount failure, and correct
in the inability of the drive to do fast locates to file the problem. If the problem is a mislabeled volume or
positions on the cartridge, which causes the locate unreadable label, relabel the scratch volume using the
performance for read or append operations to become dsmlabel utility with the "-overwrite" option. If the
degraded. volume is missing from its home slot, issue the AUDIT
LIBRARY command against the library. If the volume
System action: The server continues the operation. has lost or corrupted VCR-data, relabel the volume.
User response: There are two methods to restore the (This reinitializes the VCR-data by writing to the
VCR data. The first method uses the MOVE DATA volume from beginning-of-tape.) Once the problem is
command to move the data off the tape and to return corrected, update the status of the volume to scratch by
the tape to scratch or empty status. The VCR data is using the UPDATE LIBVOL command.
rebuilt when the empty tape is rewritten from the
beginning-of-tape. The second method rebuilds the ANR8779E Unable to open drive drive name, error
VCR by loading the tape and locating directly to the number= errno value from open system call.
end-of-data. This is done by the server in normal use
when new data is appended to the end of the tape. It Explanation: The drive cannot be opened by the
can also be done independent of the server by loading server. On UNIX and Linux systems, an error number
the tape in an unused drive and using the tapeutil is a value of an errno returned by the operating system.
program. Select the tapeutil option "Space to On Windows, an error number is a Windows error
End-of-Data". message number.
ANR8780E ANR8786I
System action: The transaction that needs the drive

ANR8783E Label on volume in drive drive name
fails.
could not be read.
User response: Use the error number in conjunction
Explanation: The server was unable to read the label
with operating system documentation to narrow the
on the indicated drive.
scope of the cause. Inspect the drive. Ensure that the
drive is powered on and ready, that the cables are System action: The volume is rejected.
properly connected and terminated, and that the device
User response: Use the appropriate labeling utility to
is properly configured to the operating system.
label the media. In Windows NT, the LABEL command
is used to label removable disk cartridges, diskettes and
ANR8780E Volume in drive drive name has no label. other media which appear as drive letters. This label
must still conform to server requirements.
Explanation: The volume in the indicated drive does
not have a label. The server requires that all media be
uniquely labeled. ANR8784E File file name on volume drive name could
not be created.
System action: The volume is rejected and the server
prompts for a new volume. Explanation: The server was unable to create the
indicated file on the indicated volume. The server
creates a file on removable media in which to store
data.
other media which appear as drive letters. System action: The volume is rejected.
User response: Ensure that the media is not defective,
ANR8781E Volume in drive drive name has invalid and is properly formatted. Ensure that there are not
label label. large numbers of files already in the root of the file
system. Some file systems have limits on the number of
Explanation: The volume in the indicated drive has
files that may be created in the root directory.
the label shown. The name does not conform with
server requirements. The server requires that all media
be uniquely labeled and, for removable media, that the ANR8785E Out-of-space in file system for device
label with file naming conventions. The label found type volume volume name.
exceeded the maximum label size for removable media
Explanation: The server detected an out-of-space
or did not conform to server labeling requirements. If
condition for the file system in which the given volume
????? is shown for the label, it indicates that server was
resides.
unable to read the label.
User response: The file system must be expanded to
accommodate volume growth.
other media which appear as drive letters. This label ANR8786I Request number: Remove device type
must still conform to server requirements. volume from entry/exit port; insert
volume volume name mount mode into
entry/exit port of library library name
ANR8782E Volume volume name could not be
within time limit minute(s); issue 'REPLY'
accessed by library library name.
along with the request ID when ready.
Explanation: The designated volume is in the
Explanation: A CHECKIN LIBVOLUME command is
inventory of the Library Manager, but the physical
in progress, and the specified volume is needed.
location is either inaccessible or unknown.
However, there is a volume awaiting to be removed
System action: The operation fails. The access mode of from the entry/exit port before the specified volume is
the volume is changed to UNAVAILABLE. inserted into the port of the given library.
User response: Ensure that the cartridge is physically System action: The server waits until a REPLY
in the library, and reinventory the library. If the volume command is issued.
location is resolved, restore the access mode of the
User response: Remove the volume from the library
volume to its previous value using the UPDATE
and insert the correct volume into the entry/exit port.
VOLUME command.
Issue a REPLY command, along with the request ID, to
tell the server that the volume has been removed and a
new volume has been inserted.

ANR8787W ANR8794E
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
label from the tape. Cleaning cartridges have no System action: The originating process terminates.
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
User response: Cancel the process if you do not want problem. If the problem is an unreadable label, any
to load all of the cartridges into the library's drives. data on the volume may be lost.
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
functioning properly, if necessary. Explanation: The drive has been determined to be
faulty because of recurrent failures.
ANR8788W Unable to read the barcode of cartridge System action: The drive is now marked offline.
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
User response: Cancel the process if you do not want not associated with the transaction which is driving the
to load any cartridges into the library's drives. Examine recovery. In addition, the maximum number of drives
the cartridge to ensure it has a barcode label and that it that can have dynamic drive recovery performed at the
is compatible with the barcode reader. Not all vendors' same time is one less than the number of drives. This is
labels are readable by all libraries. Check that the to prevent deadlock from occurring between two
barcode reader is configured and is functioning recovering transactions. One of these criteria has failed.
properly, if necessary. System action: No DDR is performed and the
transaction fails.
ANR8789W Dynamic drive recovery being attempted User response: Restart the transaction.
on device type volume volume name due to
errors.
ANR8794E Retry of operation name operation failed
Explanation: Due to a drive or media fault, the server for device type volume volume name.
is moving the volume to a new drive.
Explanation: After successfully mounting the volume
System action: Read or write operations resume on on another drive, due to an I/O error, the original
the volume once it is remounted. operation fails when retried.
User response: None. System action: No further recovery is performed and
the transaction fails.
ANR8790I device type volume volume name User response: Restart the transaction.
re-mounted in drive drive name.
Explanation: Due to a drive or media fault, the server
has moved the volume to the specified drive. Read or
write operations resume on the volume.
ANR8795I ANR8802E
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.
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: The drive may be made online by
the QUERY PROCESS command. The process may be
issuing the UPDATE DRIVE command with the
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 background process to LABEL a
mentioned drive. This may be for the following
volume has succeeded.
reasons:
v The drive cannot be opened. System action: The volume's label has been rewritten.
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
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.
system logs. Render any needed corrections to the
drive. The drive will be brought online automatically
when the polling process detects that is has become ANR8802E LABEL LIBVOLUME process process Id
accessible. for library library name failed.
Explanation: The Label process terminated with a
ANR8798W Drive drive name in library library name is failure.
busy; some transactions may fail. System action: The process ends.
Explanation: The drive being made offline is currently User response: See previous error messages to
mounted with an open tape volume. If the transaction determine the cause of the failure, and correct the
using the volume requires subsequent tape mounts and problem.
is unable to acquire a drive, the transaction will fail.
System action: If this tape volume is one of a
sequence of volumes that are required to process a
transaction, a drive must be available for each mount.

ANR8803I ANR8810I
ANR8803I LABEL VOLUME process process Id for ANR8807W Could not write label volume name on
library library name has been canceled; the volume in drive drive name of library
count of labeled volumes volume(s) labeled, library name because volume is already
count of checked in volumes volume(s) labeled existing volume name.
checked-in.
Explanation: The check in or label process could not
Explanation: A background server process that has write the label on the tape specified because the
been working to label the volumes for the given library volume is already labeled.
is canceled by the CANCEL PROCESS command. The
System action: The check in process will not overwrite
counts provided are for any volumes processed prior to
volumes that are already labeled, and the label process
the cancel.
will only overwrite volumes when OVERWRITE=YES
System action: The server process is ended and server is specified. The volume is not labeled and cannot be
operation continues. checked in to the library. If SEARCH=YES, the process
continues to the next volume. For an individual
volume, the process ends.
ANR8804I Labeling volume volume name in library
parameters.
library name.
ANR8808E Could not write label label name on the
volume in drive drive name of library
LABEL process on the server.
library name because that volume is
System action: The background process continues. already labeled with volume name which
is still defined in a storage pool or
User response: None. The process may be canceled by volume history.
PROCESS command. Explanation: An attempt was made to overwrite the
label of a volume that is still defined to a storage pool
or is still found in the volume history file. Such a
ANR8805I Labeling volumes in library library name; volume may still contain valid data.
volume count volume(s) labeled.
Explanation: In response to a QUERY PROCESS operation continues.
command, this message displays the status of a LABEL
process with the SEARCH option. User response: It is usually not necessary to re-label
volumes. If the volume must be relabeled, that volume
System action: The background process continues. must first be removed from the storage pool or volume
User response: None. The process may be canceled by history file where it is defined.
PROCESS command. ANR8809I Request number: Please provide the label
name for the volume in slot element slot
ANR8806E Could not write volume label volume element number of library library name by
name on the tape in library library name. issuing REPLY n LABEL=xxx within time
limit minutes, where n is the request ID
Explanation: The Label process could not write the and xxx is the desired label name.
label on the tape specified.
Explanation: A LABEL LIBVOLUME command is in
System action: For a LABEL operation with progress, and the name of the next volume is needed.
SEARCH=YES, the background process continues to the
next volume. For an individual volume, the process System action: The server waits until a REPLY
ends. The volume is not labeled and is not checked into command is issued.
the library. User response: Issue a REPLY command, along with
User response: Make sure the library and drive the request ID, and the volume name for the next
devices associated with this command are powered on cartridge.
and ready, and then reissue the command.
ANR8810I Volume volume name has been labeled in
Explanation: The Label process with the search option
has found and labeled a volume.
System action: The process ends.
ANR8811E ANR8818E

ANR8815I Remove volume Volume name from port
element Port element number of library
ANR8811E Command: The LABELSOURCE Library name.
parameter is required when using
Explanation: LABEL LIBVOLUME has ended for the
SEARCH with this command.
specified volume and that volume must be removed
Explanation: The LABELSOURCE parameter must be from the library because either it was not checked in or
provided with the given command. there was an error.
System action: The command is not processed. System action: The server continues normal operation.
User response: Reissue the command, and provide a User response: Remove the specified volume from the
valid LABELSOURCE parameter value. library.
ANR8812E Command: The SEARCH parameter is ANR8816E command: Volume Volume name in library
required when using LABELSOURCE Library name cannot be labeled because
with this command. it is currently defined in a storage pool
or in the volume history file.
Explanation: When using the LABELSOURCE option
with this command, the SEARCH parameter must be Explanation: During command command processing, a
also provided. volume cannot be used because there is a storage pool
volume defined or a volume in the volume history file
System action: The command is not processed. with this volume name. Such a volume may still
User response: Reissue the command, and provide a contain valid data. Applying the volume name to the
valid SEARCH parameter value. cartridge can overwrite data and or cause library
inventory corruption. If the volume is in the volume
history file, it has been previously used by for an
ANR8813W Unable to read the barcode of cartridge export, database dump, database backup operation, or
in slot element Element number of slot in by a library client (as recorded in the volume history).
System action: If the SEARCH=YES option was
Explanation: The library barcode reader is unable to specified, the current volume is skipped and command
read the label of a tape cartridge. The cartridge is processing continues with the next volume found. If
found in the slot with the given element number. SEARCH=NO was specified, command processing
System action: When LABELSOURCE=BARCODE is terminates.
specified on the LABEL LIBVOLUME command, User response: If the volume is present in an
volumes without a barcode cannot be labeled. When automated library, it should either be removed or
the VOLRANGE or VOLLIST option is specified on the checked into the library's inventory in the PRIVATE
CHECKIN LIBVOLUME command, volumes without a category.
barcode cannot be checked in.
User response: Examine the cartridge to ensure it has ANR8817E Name length for volume "Volume name"
a barcode label and that it is compatible with the invalid; max is Maximum name length.
barcode reader. Not all vendors' labels are readable by
all libraries. Check that the barcode reader is Explanation: During LABEL LIBVOL processing, the
configured and is functioning properly, if necessary. volume name provided to be written on the label
exceeds the maximum length for the type of cartridge.
ANR8814I Remove volume Volume name from slot System action: The label process fails for that
element Slot element number of library cartridge.
Library name. User response: Reissue the LABEL LIBVOL command
Explanation: LABEL LIBVOLUME has ended for the and provide a volume name that is not longer than the
specified volume and that volume must be removed maximum listed.
from the library because either it was not checked in or
there was an error. ANR8818E I/O Error on library library name; request
System action: The server continues normal operation. for op. operation/function to the 3494
Library Manager has timed out.
User response: Remove the specified volume from the
library. Explanation: A command for the operation was issued
to the Library Manager and a response was not
received within the maximum timeout period.
System action: The operation and the transaction fails.

ANR8819E ANR8826E
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
User response: Enter a volume name that is within
Manager Control Point device driver. If the problem
the length constraints for the media type being labeled,
persists, provide your service representative with the
and which contains only alphanumeric characters.
3494 Library Manager transaction logs.
ANR8823E Hardware configuration error in library

ANR8819E Unable to read the barcode label(s) in
library name: number of drives drives,
number of storage slots storage slots.
Explanation: A LABEL command was issued with the
Explanation: The library device returned a count of
LABELSOURCE=BARCODE option. The library was
zero for either the drives or the slots. The drives may
unable to detect that the cartridges had valid barcode
have not yet been configured to the operating system,
labels or the library did not have a barcode reader. If a
or to the library. The library must have at least one
barcode reader is present the reader might be disabled
drive and multiple slots when properly configured in
or it is unable to read the labels.
order to be defined to the server.
System action: Examine the cartridges to ensure they
have barcode labels and they are compatible with the
barcode reader. Not all vendors' labels are readable by User response: Configure the drives to the operating
all libraries. Check that the barcode reader is system, and reinitialize the library.
configured and functioning properly.
User response: None. ANR8824E I/O Error on library library name; request
request id for operation operation/function
to the 3494 Library Manager been lost.
ANR8820W Repairing VCR data for Volume volume
name in drive drive name; dismount may Explanation: A command for the operation was issued
be delayed. to the Library Manager and a response was not
received within the maximum timeout period.
Explanation: The Vital Cartridge Records of the
cartridge in the drive are lost or corrupted, which System action: The operation and the transaction fails.
results in the inability of the drive to do fast locates to
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
transaction logs and the request id from the failed
System action: The server continues the dismount operation.
operation. There may be a long delay because the VCR
is rebuilt by spacing the tape forward to the
end-of-data. ANR8825E 'Volume range' is not a valid volume
range.
Explanation: The specified string is not a valid
volume range.
ANR8821E Barcode of element slot element address,
'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
being labeled, and which contains only alphanumeric
System action: The barcode is not considered valid characters. The volume names of the beginning and
and will not be used for the server process. ending volume must be the same in length and the
incrementals must be in digits.
User response: Replace the cartridge's barcode with
one that is supported by the library and whose number
of characters does not exceed the maximum length. ANR8826E No Entry/Exit found on library library
name.
ANR8822E 'Volume name' is not a valid volume Explanation: A CHECKIN LIBVOLUME
name. SEARCH=BULK command was issued on a library that
has no Entry/Exit ports.
Explanation: The specified string is not a valid
volume name. System action: None.
ANR8827E ANR8834E

ANR8831W Because of media errors for volume
Volume name, data should be removed as
ANR8827E No Entry/Exit port is available on soon as possible.
Explanation: Errors previously encountered on the
Explanation: A CHECKOUT LIBVOL command was volume leave the access to the data in a questionable
issued on a library where all its Entry/Exit Ports were state. The errors may be permanent temporary media
found to be full or inaccessible. failures such as the corruption of the Volume Control
Region of a Magstar drive.
User response: Empty all the entry/exit ports on the
library, close the entry/exit port door, make sure the User response: Move the data off the volume. This
ports are accessible, and try the command again. can be done with the MOVE DATA command. In some
cases the tape is reusable by returning it to scratch.
Check system error logs for entries made by the device
ANR8828E Slot element number of library library relative to media errors. If the errors cannot be isolated
name is inaccessible. ore resolved, contact your support representative.
Explanation: The slot in the library could not be Return the tape to scratch or dispose of it.
physically accessed at this time.
System action: None. ANR8832E CHECKIN LIBVOLUME for volumes in
search mode in library library name
User response: Verify that the Entry/Exit door is failed.
closed and the device has not logged any device errors
before trying the command again. Explanation: The background process for a CHECKIN
LIBVOLUME command has failed.
ANR8829I Remove volume volume name from slot System action: The background process ends, but
element number of library library name at volumes have not been checked into the library.
your convenience. User response: Make sure the library and drive
Explanation: A volume has been checked out from the devices associated with this command are powered on
library and placed in a multiple entry/exit port library. and ready, and then reissue the command.
The volume needs to be removed from the library, but
the operation is not critical. ANR8833E Command: Volume volume name in library
System action: None. library name is currently being checked
in or checked out.
User response: Remove the volume from the
entry/exit slot. Explanation: The command cannot be processed
because the specified volume is being checked in or
checked out of the library.
ANR8830E Internal Device type drive diagnostics
detect excessive media failures for System action: The command is not processed.
volume Volume name (MIM MIM Code). User response: Wait until the conflicting checkin or
Access mode is now set to "read-only". checkout has completed, and then reissue the
Explanation: The tape drive's microcode performed an command.
analysis of the media during the prior mount of the
volume and determined that the number of temporary ANR8834E Library volume volume name is still
errors and other indicators exceed the threshold for present in library library name drive drive
reliable data recording. name, and must be removed manually.
System action: The volume is made read-only. Explanation: Library operations cannot be performed
User response: Check system error logs for entries using the drive because a volume is still mounted in it.
made by the device relative to media errors. It is This may be due to a prior dismount failure that
recommended to move the data off the volume in order occurred on the drive.
to minimize the impact of future errors and further System action: The command fails. The drive may be
damage to the media. taken offline.
User response: See previous error messages and the
system error logs to determine the cause of the
dismount failure or any other reason the volume would
still be loaded in the drive. Hardware diagnostics may

ANR8835W ANR8841I
be required. If necessary, remove the volume manually System action: The operation fails.
and place it in its storage cell. If the storage cell is
User response: See accompanying error messages and
unknown, place the volume in any cell and issue the
the system error logs to determine any reason for the
AUDIT LIBRARY command. Use the QUERY DRIVE
drive failure. Hardware diagnostics may be required. It
command to determine the online status of the drive. If
may be necessary to manually unload the volume and
the drive is still functioning, change the status with the
mark the drive offline with the UPDATE DRIVE
UPDATE DRIVE command.
command.
ANR8835W Error returning volume volume name to

ANR8839W Drive drive name of library library name is
scratch.
accessible.
Explanation: The server external library manager sent
Explanation: The server is now able to use the
a RELEASE request to the external agent for the named
mentioned drive that was inaccessible. However, the
volume, but the external agent was unable comply with
administrator has marked the drive offline while the
the request. The server, however, marked the volume
drive was being polled.
scratched in its inventory; consequently, the server
inventory and the external agent inventory are not System action: The drive is left offline and is not used
consistent. This message is issued to inform the for tape operations.
customer that the external agent inventory must be
made consistent with the server inventory using the User response: Issue the UPDATE DRIVE command
facilities of the external agent. to bring the drive back online.
System action: The server has returned the volume to

scratch status. ANR8840E Unable to open device device name with
error number error number and PVRRC
User response: Consult the documentation for the return code.
external agent and take the appropriate action to make
the agent inventory consistent with the server Explanation: The library is not accessible. As a result,
inventory. an open request failed. This in turn causes the pending
request to fail.
ANR8836E Function RSM_function failed in System action: A drive is marked inaccessible. The
server_function processing, return return server polls the drive to determine if both the library
code, call call number. and drive are inaccessible. In most case, the library had
a temporary failure and recovers. When the server
Explanation: The library function that uses the API to determines that the library is available, the drive is
the Windows NT Removable Storage Manager failed brought back on-line.
with a return code from the API. The call number
represents the exact API call issued in the program. User response: Use the error number in conjunction
with operating system documentation to narrow the
System action: The function fails. scope of the cause. Inspect the library. Ensure that the
library is powered on and ready, that the cables are
User response: Use the RSM documentation to
properly connected, and that the device is properly
determine the source of the problem.
configured to the system.
ANR8837E RSM Library Library Name not supported

ANR8841I Remove volume from slot element number
on this Windows platform.
of library library name at your
Explanation: The libtype=RSM was used on a convenience.
Windows platform that does not support RSM.
Explanation: A volume has been placed in a multiple
System action: The function fails. entry/exit port library because the volume should be
placed back in the entry/exit port as result of the
User response: Use another library type to define the
successful completion of a server command, or there
library.
was a problem during a server command. The volume
needs to be removed from the library, but the operation
ANR8838E I/O error on drive drive name: excessive is not critical.
unit attentions received from device.
Explanation: An operation to the drive failed with a
User response: Remove the volume from the
device unit attention. These are normally cleared when
entry/exit slot. Examine previous messages for
the operation is retried, but in this case subsequent
additional information regarding the specified volume
recover and retry attempts persistently fail with unit
and the command.
attention. This indicates a device failure.
ANR8842E ANR8847E
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
ANR8843E Initialization failed for library type
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 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
properly connected and terminated, and the device is LABEL command, use the QUERY MOUNT command
properly configured to the operating system. to determine if all the drives in the library are mounted
and wait until one of these is available. If there are
mounted volumes with an IDLE status, use the
ANR8845E Loadable module module name is DISMOUNT VOLUME command to free its drive, and
required for remote operation. retry the original operation. Finally, the DEVTYPE
Explanation: The indicated loadable module is parameter is required for CHECKIN and LABEL
required by the server to perform an operation on a commands specifying 3590 volumes in a 349X library
remote drive or library, but the module has not loaded. that also contains 3490 drives. This is because this
library also supports 3490 volumes, and the default

ANR8848W ANR8856E
device type on CHECKIN and LABEL commands is

ANR8852E Initialization failed for ACSLS library
CART (3490).
library name.
ANR8848W Drive drive name of library library name is
library has failed and will not be retried until the next
inaccessible; server has begun polling
time the server needs to access the library.
drive.
System action: The library is made temporarily
unavailable.
mentioned drive. This may be for the following
reasons: User response: None.
v The drive cannot be opened
v In the case of a 3494 or a library that can be ANR8853E Incompatible options
partitioned, the drive may be unavailable to the CHECKLABEL=NO and SEARCH=YES
library manager, may be in use by another for ACSLS libraries.
application, or may be loaded with a cartridge not
Explanation: The CHECKLABEL=NO and
SEARCH=YES parameters on the CHECKIN LIBVOL
System action: The drive is temporarily made offline command are not compatible.
and is not used for tape operations. The server polls
the drive at one-half minute intervals to check if the
condition has cleared. Once the drives is accessible User response: Reissue the CHECKIN LIBVOL
again, the drive is brought online. command and specify CHECKLABEL=YES.
User response: Determine the reason the drive is
inaccessible, such as hardware errors reported in the ANR8854E ACSAPI(command name) invocation
system logs. Render any needed corrections to the failed, status= acs status.
drive. The drive will be brought online automatically
when the polling process detects that is has become Explanation: The ACSLS library API invocation for
accessible. the given command failed.
System action: Depends on the server function and
ANR8849E Command: There is already a request to command, library may be unavailable.
delete drive drive name. User response: Contact your ACS System
Explanation: The designated drive cannot be deleted Administrator and perform ACSLS library problem
or updated because there is a request to delete the determination.
drive already.
System action: The command is not processed. ANR8855E ACSAPI(command name) response with
unsuccessful status, status=acs status.
Explanation: The ACSLS library API responded with
an unsuccessful status as indicated.
ANR8850I ACSLS library library name is ready for
operations. System action: Depends on the server function and
command, library may be unavailable.
library has completed successfully, and the library is User response: If the status indicates
ready for use. STATUS_CAP_IN_USE, it might be CAP priorities not
set to non-zero. It might also be CAPs are not set to
System action: The library is made ready for use. 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
perform ACSLS library problem determination.
ANR8851E Initialization failed for ACSLS library
library name; will retry in delay time
ANR8856E ACSAPI sequence(sequence number)
minute(s).
request (request number) timed out,
Explanation: The initialization process for the given elapse time=hours: minutes:seconds.
library has failed. It is retried automatically after the
Explanation: The ACSLS client has received no
specified amount of time has elapsed.
response from the ACSLS server for the period as
System action: The initialization will be retried later. indicated in the elapsed time. The ACSLS library API
function with the associated sequence number is
User response: Ensure that the library device is
canceled if the request number is non-zero.
powered on and ready.
ANR8857I ANR8865W

ANR8861I Wait and monitor the ACSSA console
command, library may be unavailable.
message to remove volume volume id
User response: Contact your ACS System from CAP.
Administrator and perform ACSLS library problem
Explanation: The specified volume is about to put into
determination.
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
User response: Monitor the ACSSA console and wait.
command and volume access control is set the user_id
as indicated.
ANR8862I Unable to access ACS volume volume id.
Explanation: The specified ACSLS volume can not be
User response: Ensure the indicated user_id is the
accessed in the library. The possible reasons might be
same as specified in the environment variable
the volume is in use, the user is not authorized, the
ACSAPI_USER_ID.
volume does not exist in the library.
ANR8858W Unable to lock drive drive id,drive id,
command, library volume is unavailable.
drive id,drive id, status= acs status.
User response: Contact your ACS System
Explanation: The ACSLS library function
acs_lock_drive failed for the specified drive.
determination if the problem persist..
command, library drive may be unavailable. or may be
ANR8863I Unlocking library library name volumes
temporary unavailable in a shared library environment.
from the ACSLS server.
Explanation: The volumes of the specified library are
being unlocked from the ACSLS server.
determination if the problem persists.
System action: The operation continues. The process
may take a while depends on the number of volumes
ANR8859W Unable to lock volume volume id, status=
in the library.
acs status.
Explanation: The ACSLS library function
acs_lock_volume failed for the specified volume.
ANR8864I ACSLS library library name is being
re-initialized.
command, library volume is unavailable.
Explanation: The specified ACSLS library is being
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
ANR8860W Volume volume id is already locked by
locked.
user id.
Explanation: The specified volume is already locked
by other user or has a different lock id.
ANR8865W Volume volume name bypassed for
System action: Depends on the function, the volume
command, status=acs_status.
maybe bypassed or the process maybe terminated.
Explanation: The specified volume is bypassed. The
User response: This may not be an error in a shared
volume is not in a valid status for the specified
configuration. However, if the existing volume lock is
function.
not needed. contact your ACSLS system administrator
to clear the lock the volume. System action: The operation continues.
User response: Determine the volume status from the
ACSSA and re-issue the command if necessary.

ANR8866E ANR8875E

ANR8866E Incompatible option REMOVE=BULK
for ACSLS libraries.
ANR8872E No path is available for drive drive name
Explanation: The REMOVE=BULK option is not
- could not unload volume volume name
supported for ACSLS libraries. The final response of
from drive.
ACSAPI acs_eject does not return to the application
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
to the drive is offline. The indicated volume may be
User response: Reissue the CHECKOUT LIBVOL still on the drive.
command and specify REMOVE=YES or NO.
System action: The drive is inaccessible.
User response: Ensure that a path is defined to the
ANR8867I Processing volume volume id for the
drive. If there is a path defined to the drive, make sure
command command.
that the path is online and that the source of the path is
Explanation: The specified volume is being processed also online. Run the AUDIT LIBRARY command after
for the specified command. the problem is corrected.
ANR8873E The path from source source name to
destination drive name is taken offline.
Explanation: There is problem using the indicated
ANR8868E Ejecting Volume volume name Failed,
path. The path is now marked offline.
status = acs_status .
System action: The path is inaccessible.
Explanation: The volume is failed to be ejected from
the library due to the status as indicated User response: Determine the reason the path is
inaccessible, such as hardware problem. Render any
System action: The operation continues.
needed corrections. Then, the path may be made online
User response: Determine the volume status from the by issuing the UPDATE PATH command with the
message and do something as needed ONLINE=YES option.
ANR8869E Command: There is already a request to ANR8874E The type of device used by the media in
update drive drive name. element element number of library library
name cannot be determined by the
Explanation: The designated drive cannot be deleted hardware. Volume is not processed.
because there is a request to update the drive already.
Explanation: The library's mechanism for determining
System action: The command is not processed. the type of media in a slot or EE port failed. This is
User response: None. usually the barcode reader or some other sensor that is
part of the robotics.
ANR8870E The path to the library library name is System action: The volume is skipped by the process.
unavailable. User response: Determine the reason the library could
Explanation: There is no path to the given library, or not determine the media type, such as deteriorated
the path to the library is offline, or the source entity of barcode, scanner failure, or other hardware problem as
the path to the library is offline. determined by system engineer. If the barcode label is
replaced on a private volume containing data, it must
System action: The library is inaccessible. be with a label having the volume name. Scratch
User response: Ensure that a path is defined to the volumes or empty private volumes can be replaced
library. If there is path defined to the library, make sure with any barcode but they must be re-labeled if the
the path is online and the source entity of the path is barcode name changes.
also online.
ANR8875E An illegal move was attempted
ANR8871I The device name device name specified involving the media in element element
has been changed to device name. number of library library name. Its type is
incompatible with the destination
Explanation: The specified device name on the element element number.
DEFINE PATH or UPDATE PATH command has been
changed to recommended device name. Explanation: The server tried to move one type of
volume into a drive or slot of another type that is
ANR8876E ANR8882I
incompatible. This is most likely because another

ANR8879E Failed to close the SCSI session for the
volume has taken its slot, or the server's information
remote library library name(device name).
for this volume has otherwise been corrupted.
Explanation: An attempt to close a SCSI session for a
System action: The process fails.
remote Library device attached to a NAS File Server
User response: Issue the AUDIT LIBRARY command, failed.
and retry the operation.
User response: Examine previous messages for
ANR8876E The media in element element number of
additional information regarding the specified library.
library library name is a cleaner.
Explanation: The library hardware has determined
ANR8880W Device type of drive Drive name in
that the media in the stated slot is a cleaner cartridge.
library Library name was determined to
It cannot be processed by the CHECKIN command
be GENERIC_TAPE.
without the STATUS=CLEANER parameter, and it
cannot be labeled by the LABEL command. Explanation: The device type of a drive is determined
when the path for that drive is defined. If the wrong
System action: The process skips the media, or if it is
device file was used in the device parameter of
the only media being processed the process fails.
DEFINE PATH the device type of the drive will often
User response: Issue the AUDIT LIBRARY command, be GENERIC_TAPE. If you are using the TSM device
and retry the operation. driver or the IBMTape device driver, then you should
not have a device type of GENERIC_TAPE. You should
only have a device type of GENERIC_TAPE if you are
ANR8877E Volume volume name is incompatible using the native OS device driver.
type with device class devclass name in
library library name. System action: None.
Explanation: An attempt has been made to service a User response: Verify that GENERIC_TAPE is the
mount request, but the attempt fails because the media desired device type for this drive. While the device
type of the cartridge being mounted is not compatible type GENERIC_TAPE is valid, it is often a mistake, and
with the devclass requesting the mount. This is usually thus, should be verified that it is the intended device
a conflict between WORM and Read-Write type. If GENERIC_TAPE is not the intended device
characteristics. type, all paths for this drive and the drive itself will
have to be deleted and redefined.
User response: If this is not a 3592 device or media, ANR8881W Insufficient space for new volume in
The volume was probably not checked in with the directory directory for device class device
CHECKLABEL=YES parameter of the CHECKIN class name.
command. Check the volume out (the REMOVE=NO
may be useful) and check the volume back into the Explanation: The server found that the indicated
library with this parameter to ensure that the directory had insufficient space in which to create a
mediatype is determined and saved. If this is a 3592 new volume.
device or media, the volume probably has an incorrect
System action: Other directories available to the
barcode label indicating that it had the wrong WORM
device class are used, if any. If no directories with
property. The label needs to be swapped for the
space are available, the operation fails. This message is
opposite WORM type (e.g. WORM to non-WORM or
issued periodically as requests are made for space in
non-WORM to WORM) or simply removed entirely
this directory.
from the library.
User response: The file system must be expanded to
accommodate volume growth.
ANR8878E Failed to close the remote library library
name (device name).
ANR8882I Request number: Please provide the label
Explanation: An attempt to close a remote Library
name for the volume in drive drive name
device attached to a NAS File Server failed.
of library library name by issuing REPLY
System action: The operation fails. n LABEL=xxx within time limit minutes,
where n is the request ID and xxx is the
User response: Examine previous messages for desired label name.
additional information regarding the specified library.
Explanation: A mount is in progress with
AUTOLABEL, and the name of the volume is needed.

ANR8883W ANR8903E

ANR8886E Element address mismatch: Element
command is issued.
element number of library library name is
User response: Issue a REPLY command, along with reported by the library to be element
the request ID, and the volume name for the cartridge. element number.
Explanation: The library configuration appears to
ANR8883W The volume volume name in slot element have changed. Verify that no other management
number is in the library library name but interfaces are modifying the library inventory.
not in the TSM's inventory database.
Please either check in this volume or
remove it from the library. User response: Examine previous messages for
additional information regarding the specified volume
Explanation: .
and the command that was issued. Retry the operation.
System action: . It may be necessary to audit the library using the
AUDIT LIBRARY command
User response: The Audit Library command found
this volume in this library but they are not in TSM's
inventory database. This volume can be either checked ANR8901E Command: Incompatible options
in or removed from this library. STATUS=CLEANER and
CHECKLABEL=YES.
ANR8884W Attempted to label a written WORM Explanation: Cleaner cartridges do not have internal
medium in the drive drive name with labels that can be checked by loading them into the
volume volume name (OP=internal code, drive.
Error Number=internal code, CC=internal
code, KEY=internal code, ASC=internal
code, ASCQ=internal code, SENSE=sense User response: Reissue the CHECKIN LIBVOL
data, Description=error description). Refer command and include the parameter,
to the Tivoli Storage Manager CHECKLABEL=BARCODE (with SEARCH=YES
documentation on I/O error code specified), or include the parameter
descriptions. CHECKLABEL=NO (with the required volume name
specified in the CHECKIN command).
Explanation: An I/O error has occurred while labeling
on the written WORM medium.
ANR8902W Unable to read the barcode of cleaner
cartridge in slot-id Element number of slot
User response: Ensure the WORM medium in the in library library name; cleaner not
drive is not a written WROM medium. checked in.
Explanation: The library barcode reader is unable to
ANR8885W The device type of drive Device Name is read the label of a cartridge that is checked in as a
determined to be GENERICTAPE. cleaner. The cartridge is found in the slot with the
given element number.
Explanation: You have specified GENERICTAPE=Yes
when defining a path to this drive. The tape drive is System action: The cartridge is not checked in. If the
supported and we recommend using with the Tivoli library is being searched, the checkin process continues
Storage Manager tape format instead of the generic with the next volume.
tape format. To use the Tivoli Storage Manager tape
User response: Examine the cartridge to ensure it has
format, do not specify GENERICTAPE=Yes when
a barcode label and that it is compatible with the
defining a path to the drive.
barcode reader. Not all vendors' labels are readable by
System action: None. all libraries. Check that the barcode reader is
configured and is functioning properly. The cleaner
User response: Verify that GENERICTAPE is the cartridge can be checked in without use of the barcode
desired device type for this drive. While the label by issuing the CHECKIN LIBVOL command.
GENERICTAPE device type is valid, it is not
recommended for a tape drive that is supported by the
Tivoli Storage Manager server. If GENERICTAPE is not ANR8903E Command: Missing CLEANINGS
the intended device type, delete all paths to this drive parameter for cleaner cartridge checkin.
and delete the drive itself. Then redefine the drive and
Explanation: When checking in a cleaner cartridge, the
a path without specifying GENERICTAPE=Yes.
CLEANINGS parameter is required.
ANR8904I ANR8911W
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.
terminated.
ANR8905I CLEAN DRIVE process for drive drive
name in library library name is been
canceled.
ANR8910I No cleaner, or no cleaner with cleanings
Explanation: A background server process is has been
left, found in library library name.
working to clean the specified drive and is canceled by
the CANCEL PROCESS command. Explanation: A drive is selected to be loaded with a
cleaner cartridge, but no cleaner, or cleaner with
System action: The cleaning process is ended.
cleanings left, is found in the library's inventory.
System action: The drive is available for normal
library operations.
ANR8906I Cleaning drive drive name in library
User response: A cleaner should be checked in to the
library name.
library by issuing the CHECKIN LIBVOL command.
ANR8911W The cartridge in storage element slot
CLEAN DRIVE process on the server. The given
element address in library library name is
volume is being checked in to the designated library.
not a cleaner cartridge as was expected.
Explanation: The cartridge is listed in the library's
continues. The process may be canceled by an
inventory with a cleaner volume status. After loading
authorized administrator using the CANCEL PROCESS
the cartridge in the specified storage cell into a drive
command.
for cleaning, it is determined that it is not a cleaner
User response: None. The process may be canceled by cartridge.
System action: The drive is available for normal
PROCESS command.
library operations.
User response: Verify all other cleaner cartridges are
ANR8907E CLEAN DRIVE for drive drive name in
in the correct storage cells. Issue the QUERY
library library name failed.
LIBVOLUME command to obtain the storage cells of all
Explanation: The background process for a CLEAN the cartridges currently checked into TSM. The
DRIVE fails. cartridge should be checked out of the library by
issuing the CHECKOUT LIBVOL command if the
System action: The background process ends, but the
cartridge is still listed in the library's inventory with a
drive is not cleaned.
cleaner volume status. If necessary a cleaner cartridge
User response: Make sure the library and drive should be checked in to replace it.
and ready. Reissue the command.

ANR8912E ANR8919I
User response: As the cleaner is used, monitor the

ANR8912E Unable to verify the label of volume
number of cleanings that remain with the QUERY
from slot-element element-address in drive
LIBVOL command. Remove the cleaner when all
drive name in library library name.
cleanings are exhausted. A new cleaner may be checked
Explanation: The volume from the slot that is in so that the library is not left without a useful cleaner
identified by the element address is loaded into a drive. when the old cleaner is exhausted.
The drive cannot be opened following the load. The
label cannot be read to process the volume.
ANR8916I Drivemapping for drive Drive name in
System action: The volume is stored, and processing library library name on storage agent
continues with the next available slot. storage agent name defined.
User response: Check the system error logs for errors Explanation: A drive mapping has been successfully
reported by the drive that are related to this volume. defined for the specified drive.
Make sure that the cartridge is not a cleaner cartridge
System action: The drivemapping is defined and
that would have been loaded by mistake. If the
recorded in the database.
cartridge is a cleaner, issue the QUERY LIBVOL
command to get the correct storage slot for the cleaner User response: None.
and move the cleaner to that slot. If the cleaner is not
in the library's inventory, use the CHECKIN LIBVOL to
check the cleaner in. During Audit Library, remove the ANR8917I Drive mapping for drive Drive name in
bad volume from the reported slot and run Audit library library name on storage agent
Library again. storage agent name updated.
Explanation: An UPDATE DRIVEMAPPING request
ANR8913I Drive drive name in library library name is has been successfully processed for the given drive.
currently busy; Cleaning flag is set and System action: The server updates its information
will be cleared when the drive has been about the drive mapping.
successfully cleaned.
Explanation: A background process to clean the drive
is unable to acquire the drive because the drive is busy.
ANR8918I Drive mapping for drive Drive name in
System action: The background process operation library library name on storage agent
completes. The drive cleaning flag is set and will be storage agent name deleted.
cleaned.
Explanation: The drive mapping for the specified
User response: None. storage agent, library, and drive has been deleted
successfully.
ANR8914I Drive drive name in library library name System action: The drive mapping is deleted.
needs to be cleaned.
Explanation: The drive has returned indicating to the
server that it needs to be cleaned.
ANR8919I Initialization and recovery has started
System action: The server marks the drive to be for shared library library name.
cleaned. If the drive is enabled for server-managed
cleaning, and a cleaner cartridge is checked into the Explanation: The shared library has started to
library, the server will load the cleaner into the drive initialize or recover to resynchronize the library
after the current volume is dismounted. See the manager and library client.
DEFINE DRIVE and QUERY DRIVE commands for System action: None.
information on enabling server-managed cleaning. See
the CHECKIN LIBVOL command for checking a User response: This process should resynchronize all
cleaner into the library. of the drives that are currently being used by this
library client. This process might also start after a
User response: None. communication error or if the library client has not
been able to verify drive status with the library
ANR8915I Cleaning cartridge cleaner name in library manager.
library name is near end of life; has
cleanings left uses left.
Explanation: A cleaner cartridge is found and used,
but its number of uses it has left is nearly exhausted.
System action: The cleaning operation continues.
ANR8920I ANR8928W
the library client for the given interval to verify that the
ANR8920I Initialization and recovery has ended for
library client is still using the drive. At this point the
shared library library name.
error recovery logic of the library manager will reclaim
Explanation: Initialization or recovery has ended the the drive (including dismounting the client's volume if
library manager and library client should be possible) and allow other to use the drive.
synchronized.
User response: Verify that the library client with the
User response: The drives previously owned by the above server name is still running. Verify that the
library client should now indicate they are free on the sessions have not been disabled and the network is still
library manager. Verify this with the QUERY DRIVE working between the two host machines. Verify that
command on the library manager. If ownership of the the server definition (QUERY SERVER) on both the
drives is still in question restart the library client and library manger and the library client are correct.
library manager.
ANR8926W An Error was encountered while
ANR8921E Unable to start library polling thread. confirming the use of drive drive name in
shared library library name.
Explanation: Library sharing requires that this polling
thread starts. This thread keeps the library manager Explanation: The library client was unable to confirm
and library client synchronized with regards to drive the usage of the drive to the with the library manager.
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
User response: Since the polling thread did not start, two host machines. Verify that the server definition
the user must restart the server in order for library (QUERY SERVER) on both the library manger and the
sharing to correctly work. Failure to restart the server library client are correct.
and get these polling services running can cause
unusual results for library clients.
ANR8927W This library client has been unable to
contact the library manager for elapsed
ANR8922I A device class for library library name time seconds. Releasing ownership of all
was not found. drives in the shared library library name.
Explanation: A library client request a mount Explanation: The library client was unable to confirm
operation to be performed by the library manager. The the usage of the drive with the library manager. The
library manager is missing a device class definition for library client will now dismount all volumes that it
that library. currently owns.
User response: Define a device class for the library User response: Verify that the sessions have not been
using the DEFINE DEVCLASS command. disabled and the network is still working between the
two host machines. Verify that the server definition
(QUERY SERVER) on both the library manger and the
ANR8923I Dismount failed because drive drive
library client are correct.
name in library library name is not
currently owned by drive owner name.
ANR8928W Library library name specified for shared
Explanation: A library client attempted to dismount a
file device class device class name was not
drive that was not currently owned by the library
defined as shared. The device class will
client.
not be shareable unless the library is
System action: None. updated.
User response: None. Explanation: A pre-existing library was specified for a

new shared file device class. However, files in the
device class cannot be shared unless the library is also
ANR8925W Drive drive name in library library name shared.
has not been confirmed for use by
server server name for over elapsed time System action: None.
seconds. Drive will be reclaimed for use
User response: Issue the UPDATE LIBRARY libname
by others.
SHARED=YES command to make the library shared.
Explanation: The library server was unable to contact

ANR8929E ANR8934W
System action: The server continues operation.

ANR8929E Library library name specified for shared
file device class device class name was not User response: Use the QUERY DRIVE command to
defined as a FILE library. get the names of the drives associated with the library.
Use the QUERY DEVCLASS deviceclass F=D command
Explanation: A pre-existing library was specified for a
to find the mount limit of the associated device class.
new shared file device class. However, the existing
Use the DELETE DRIVE command to delete drives
library was not created with the LIBTYPE=FILE
until the number of drives in the library corresponds to
parameter.
the device class's mount limit.
System action: None. The device class is not created.
User response: Specify a library name that was ANR8932W The drive map for server servername,
created with the LIBTYPE=FILE and SHARED=YES library library name, drive name drive
parameters, or specify a library name which does not name has directory directory which is
exist, in which case, the library will be created. You can different than other drive maps for
also not specify the LIBRARY parameter, a library name drives within the same library.
will be created.
Explanation: A shared file was about to be created. In
doing so, it was determined that there are differing
ANR8930W An attempt to define drives to create definitions for the directories associated with the drive
drives failed for library library name. The maps between the indicated drive map and other drive
device class has a mount limit of mount maps for drives in the same library. This could cause
limit but the number of drives in the data to be written in unanticipated locations or may
associated library is less than the mount prevent data from being written.
limit.
System action: The server continues operation using
Explanation: When a shared device class is created or the indicated directory.
updated, an attempt is made to define additional file
User response: Use the QUERY DRIVEMAP command
drives in the associated library up to the mount limit, if
with the F=D parameter to list the directories
the number of drives is less than the mount limit. One
associated with drive maps for drives in the indicated
or more failures occurred in defining additional drives.
library and ensure that the directories are correct and
The number of drives does not correspond to the
identical. Use the UPDATE DRIVEMAP command to
mount limit for the associated device class. This can
update any incorrect directory entries.
cause resource balancing problems between the server
and storage agents.
ANR8933W File volumename in library library does
not exist in the expected directory.
Explanation: A FILE volume was being dismounted
get the names of the drives associated with the library.
from a file drive. The file does not exist in the directory
Use the QUERY DEVCLASS deviceclass F=D command
in which it was expected to be found.
to find the mount limit of the associated device class.
Use the DEFINE DRIVE command along with the System action: The server continues operation.
DEFINE PATH command for this new drive with
DEVICE=FILE to define additional drives in the file User response: It is possible that a drive mapping is
library to match the mountlimit of the associated device incorrect and that a storage agent is using a valid, but
class. different directory than that of the server. In this case,
the storage agent can access the file, but the server
cannot. Use the QUERY PATH command with the F=D
ANR8931W An attempt to delete drives to delete parameter to list the directories associated with drive
drives failed for library library name. The maps for drives in the indicated library and ensure that
device class has a mount limit of mount the directories are correct and identical. Use the
limit but the number of drives in the UPDATE PATH command to update any incorrect
associated library is greater than the directory entries. To move the file into the correct
mount limit. directory, use the Windows move command or the
Unix mv command, depending on your platform.
Explanation: When a shared device class is updated
and the number of drives in the associated library is
greater than the mount limit of the device class, an ANR8934W File volumename in library library
attempt is made to delete drives so that there are as associated with device class device class
many drives as the mount limit. One or more failures could not be inserted into the library
occurred in deleting drives. The number of drives does inventory.
not correspond to the mount limit for the associated
device class. This can cause resource balancing Explanation: A FILE volume was being inserted into
problems between the server and storage agents. the library inventory. The file was not found in the
ANR8935E ANR8940E
directory associated with the device class that

ANR8938E Initialization failed for Shared library
references the library. However, an entry for the
library name; will retry within delay time
indicated file name is already in the library inventory.
minute(s).
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
cannot. Use the QUERY DRIVEMAP command with User response: Ensure that the library manager server
the F=D parameter to list the directories associated is running, and the library is initialized.
with drive maps for drives in the indicated library and
ensure that the directories are correct and identical. Use
ANR8939E The adapter for tape drive drive name
the UPDATE DRIVEMAP command to update any
cannot handle the block size needed to
incorrect directory entries. To move the file into the
use the volume.
correct directory, use the Windows move command or
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
ANR8935E A compatible device class for shared
less than hex 41.
library library name on server server name
was not found. System action: The volume will not be mounted in
the drive.
Explanation: The library client server has a device
class definition that is not compatible with the device User response: The adapter must be updated to
class definition on this server. The device type and handle a larger block size. The setting is usually
recording format need to be the same on both servers MAXIMUMSGLIST in the Windows registry under:
or one of the servers can have a device type of generic
tape. HKEY_LOCAL_MACHINE->SYSTEM->Current Control
Set->Services->{vendor device name}->Parameters-
>Device
ANR8936W The path conversion of drive drive name
in library library name with device name Note that "{vendor device name}" should be substituted
device name failed. UPDATE DRIVE with the name of the vendors device. For example, the
required. Qlogic 2200 would use "Ql2200" for the respective
vendor device name.
Explanation: During the initialization of a library, the
server finds that the drive path was removed. MAXIMUMSGLIST should be set to hex 41 to work
properly with Tivoli Storage Manager.
System action: The drive will not be accessible by the
library during tape operations. You can also run the DSMMAXSG utility to set the
MaximumSGList value to 0x41(65) for all HBAs.
User response: The drive may be made accessible by
issuing the UPDATE DRIVE command with the For additional information, see the HBA documentation
DEVICE= option. or contact the vendor for the HBA.
For additional questions, contact IBM support.
ANR8937W The device name for drive drive name in
library library name is missing. UPDATE ANR8940E Path definition for file drive drive name
DRIVE required. in library library name for server server or
Explanation: The device name for a drive was found storage agent name does not have a
to be missing. matching directory in the device class
directory attribute for volume volume
System action: The drive will not be accessible by the name.
server for tape operations.
Explanation: A library client or storage agent
User response: The drive may be made accessible by requested a mount of a file volume in a drive that is
issuing the UPDATE DRIVE command with the contained in a file library but the path definition does
DEVICE= option. not contain a matching directory name. There must be
a matching directory in the PATH definition for each
drive in a file library and the corresponding directories
in the device class associated with the library. The
directories in the PATH definition must point to the
same storage as those of the device class definition,

ANR8941W ANR8947W
from the perspective of the specific server or storage access door, make sure it is closed. If a cleaning
agent. The list of directories must have entries for each threshold is exceeded for a tape drive in this library,
directory in which file volumes are to be read or clean the tape drive. For more information about the
written by the specified server or storage agent. values of the KEY, ASC, and ASCQ fields, see the
library and drive reference manuals.
User response: Ensure that DIRECTORY attribute of
ANR8944E Hardware or media error on drive drive
the above path definition contains matching directories
name with volume volume
for each of the directories in the server's device class
name(OP=internal code, Error Number=
definition.
internal code, CC=internal code,
KEY=internal code, ASC=internal code,
ANR8941W The volume from slot-element ASCQ=internal code, SENSE=sense data,
element-address in drive drive name in Description=error description). Refer to
library library name is blank. the Tivoli Storage Manager
documentation on I/O error code
Explanation: The volume in the slot is not labeled and descriptions.
is blank.
Explanation: A hardware or media error has occurred
System action: The volume is skipped, and processing while operating on the specified drive.
continues with the next available slot. If the volume is
checked in, it is removed from the inventory. System action: The operation fails.
User response: Label the volume using LABEL User response: Ensure that the DEVICE parameter
LIBVOL, and check it in using CHECKIN LIBVOL. 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
ANR8942E Could not move volume volume name manual usually contains tables that explain the values
from slot-element element-address to of the KEY, ASC, and ASCQ fields.
slot-element element-address.
Explanation: Could Not move volume from slot to ANR8945W Scratch volume mount failed volume
slot. name.
System action: Move volume operation failed. Explanation: Scratch volume mount failed.
User response: This message indicates a hardware System action: Scratch volume mount operation
failure. For assistance, contact IBM hardware support. If failed.
the volume was physically removed from the library,
you can re-insert the volume into the drive after it is User response: None.
fixed or replaced and issue the AUDIT LIBRARY
command. This command restores the library volume
ANR8946W There were more labels in the vollist
inventory to a consistent state with the volumes that
than volumes available to label.
physically reside in the library. If the volume was not
removed from the library, no further action is necessary. Explanation: Label Libvolume command still finishes
without error, but the last labels provided were not
used. Labeling finished when there were no more
ANR8943E A hardware or media error occurred
volumes available.
during an operation on library library
name (OP=internal code, CC=internal code, System action: All available volumes were labeled,
KEY=internal code, ASC=internal code, but additional volume names were not utilized from
ASCQ=internal code, SENSE=sense data, the vollist.
Description=error description). Refer to
the Tivoli Storage Manager
documentation on I/O error code
description. ANR8947W There were less labels in the vollist than
volumes available.
Explanation: A hardware or media error occurred
during an operation on the specified library. Explanation: Label Libvolume command still finishes
without error, but volumes are left unlabeled.
System action: Additional volumes were left
User response: Ensure that the DEVICE parameter
unlabeled.
that is associated with the library is identified correctly
in the DEFINE PATH command and that the library User response: None.
device is turned on and ready. If the library has an
ANR8948S ANR8954E
ANR8948S Device device, volume volume name has ANR8951I Device device, volume volume has issued
issued the following Critical TapeAlert: the following Information TapeAlert:
alertmessage alertmessage
Explanation: The specified device while loaded with Explanation: The specified device while loaded with
the named volume has issued a TapeAlert critical the named volume has issued a TapeAlert information
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 TSM server. It is surfaced at is from the device, not the TSM server. It is surfaced at
the termination of the current operation but is the termination of the current operation but is
independent of the operation. 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.
ANR8949E Device device, volume volume has issued ANR8952E Library serial number does not match
the following Critical TapeAlert: that defined for library name .
alertmessage
Explanation: The serial number defined for the
Explanation: The specified device regardless loaded or specified library does not match the serial number
not without the named volume has issued a TapeAlert discovered. The pending operation will fail.
critical message. This message is a feature of the
System action: The library is taken offline when the
hardware and is from the host interface, not the TSM
mismatch is discovered. Verify the serial number and
server. It is surfaced at the termination of the current
the device name for the library against those defined. If
operation but is independent of the operation.
they do not match, the definitions for the library are
System action: The operation will fail. The TapeAlert incorrect and need updated. Once the serial number is
message does not by itself indicate failure. See other updated, the library will be brought back online.
messages related to the device or volume in the activity
User response: Update the serial number or device
log.
name for the specified library with the correct values.
User response: Proper response may be indicated in
the text of the TapeAlert. The context of the TapeAlert
ANR8953I Library library name with serial number
may need to be determined from other activity log
serial number is updated with the newly
messages in order to follow its recommendations.
discovered serial number serial number.
Explanation: The serial number for the library defined
ANR8950W Device device, volume volume has issued
does not match with the serial number discovered. The
the following Warning TapeAlert:
newly discovered serial number will replace the
alertmessage
existing definition for this library since autodetect is on.
Explanation: The specified device without the volume
System action: The existing serial number for the
name has issued a TapeAlert Warning message. This
specified library is replaced by the newly discovered
message is a feature of the hardware and is from the
serial number.
device, not the TSM server. It is surfaced at the
termination of the current operation but is independent User response: None.
of the operation.
System action: The operation will fail. See other ANR8954E Failed to obtain a path for drive drive
messages related to the device or volume in the activity name for library library name.
log.
Explanation: An attempt to acquire a path for the
User response: Proper response may be indicated in drive failed. This most likely means that a path is not
the text of the TapeAlert. The context of the TapeAlert defined for this drive.
may need to be determined from other activity log
messages in order to follow its recommendations. System action: The operation fails.
User response: Ensure that a path is defined for this

ANR8955I ANR8963E
drive. If one is defined, make sure it is defined

ANR8958E Command: Autodetect is OFF and the
correctly with the correct source and destination type.
serial number reported by the drive did
If the drive is in a shared FILE library:
not match the serial number in the drive
Ensure that the number of paths defined for the storage definition.
agent is the same as the number of drives within the
Explanation: An invalid value has been provided for
library.
the specified parameter.
Ensure that the directories are correct in the server
device-class definition and the storage-agent path
definitions. User response: Reissue the command, and specify a
valid parameter value.
Ensure that the number and order of directories for
each path for the storage agent is the same as the
number and order of directories in the device-class ANR8959W Path to the library or the device does
directory definition. not exist.
Explanation: A path to the library or the device does
ANR8955I Drive drive name in library library name not exist yet.
with serial number serial number is
System action: This may not be an error.
updated with the newly discovered
serial number serial number. User response: None.
Explanation: The serial number for the drive defined
does not match with the serial number discovered. The ANR8960I Command: The display of Tape Alerts
newly discovered serial number will replace the from SCSI devices is status.
existing definition for this drive since autodetect is on.
Explanation: Whether the status of Tape Alerts from
System action: SCSI devices will be display.
User response: None. System action: The command is processed.
ANR8956E Serial number defined for library library
name does not match the discovered
serial number. ANR8961E Serial number defined for library library
name and drive drive name is blank and
Explanation: The serial number for the library defined does not match the discovered drive
does not match the serial number discovered due to serial number serial number.
autodetect is set to NO. The pending operation will fail.
Explanation: A device has been swapped and we are
System action: A mismatch between the serial number not able to get the new path.
for library and the newly discovered serial number is
detected. System action: .
User response: Update the serial number for the User response: None.
specified library with the correct values.
ANR8962E Unable to find path to match the serial
ANR8957E Command: The serial number reported number defined for library library name.
by the library did not match the serial Explanation: Either a device has hardware problems
number in the library definition. or a device path has been changed and the TSM server
Explanation: The serial number of the library in the cannot find the new path with the SAN Discovery
database did not match the serial number of the library option set to ON.
found using the device special file specified. UPDATE System action: .
PATH cannot be used to change libraries, and thus, the
new device must have the same serial number as User response: None.
stored in the database unless the serial number in the
database is empty. ANR8963E Unable to find path to match the serial
System action: The command is not processed. number defined for drive drive name in
User response: Reissue the command, and specify a
valid DEVICE parameter value. If this is a new or Explanation: A device may have hardware problems
different library with a different serial number, a new or a device path may have been changed and the TSM
library and path should be defined with DEFINE server cannot find the new path with the SAN
LIBRARY and DEFINE PATH. Discovery option set to ON. The TSM server cannot get
ANR8964W ANR8970E
device information when it cannot open the device. User response: Determine the reason the drive is
Therefore, the TSM server cannot validate the drive inaccessible, such as hardware errors reported in the
serial number to see if this drive with the failed open system logs or an invalid device name was specified
operation is the same drive as it previously used. The for the drive. Render any needed corrections to the
causes of this failed open device may be a bad cable, a drive. The drive will be brought online automatically
bad drive or a bad HBA card. However, if an incorrect when the polling process detects that is has become
drive is used (for example, an incorrect device path) accessible.
and with the SAN discovery option set to OFF or
UNSCANNEDPATHOFF, the TSM server will not
ANR8967E Command: The drive serial conflicts with
search the SAN environment to get a proper device.
an existing drive in library library name.
System action: The TSM server may mark this device
Explanation: The serial number already exists in the
offline for SAN Discovery option ON or
drives in the given library.
UNSCANNEDPATHOFF.
User response: Users should check the TSM server
option file first. If SAN discovery option is set to OFF User response: Specify a valid serial parameter for
or UNSCANNEDPATHOFF, set it to ON and check for this drive.
hardware errors on the device. If the SAN discovery
option is set to ON, then check the device to see if
there is a hardware problem. ANR8968E Unable to create path for device device.
Explanation: An attempt to contact the drive with a
ANR8964W Unable to update the path in the given device name failed. This probably means the
database path source name and drive drive device name is incorrect, but this attempt can also fail
name. for other reasons.
Explanation: The system is not able to update the System action: Operation failed.
path information in the database. User response: The device parameter is probably not
System action: . valid. This could be temporary, but not necessarily. If
this occurs while upgrading from Tivoli Storage
User response: None. Manager Version 4.1 or previous (where paths were not
used), then the drive needs to be deleted, redefined,
and a new path needs to be defined with a valid device
ANR8965W The server is unable to obtain the serial
parameter. If this occurs on a Tivoli Storage Manager
number of the SCSI device device name.
server that already has paths (Version 4.2 or higher),
Explanation: The server cannot detect a device serial then just update the drive to online. The device
number from the HBAAPI or the device itself, so the parameter on the drive path can also be updated before
server is not able to automatically correct the path for the drive is turned online, if you know the device
the device. parameter should be changed.
ANR8969E The owner of volume Volume name can
User response: Verify the following:
not be updated to owner Owner name.
v The device name in the path definition is correct.
Explanation: A command was issued updating
v The correct version of the HBAAPI is installed to the
ownership of a volume. The owner of this particular
system.
volume can not be changed.
v The SANdiscovery option is set to ON in the options
file. System action: The command is not processed.
ANR8966E Cannot get device number for the drive
drive name. ANR8970E Unable to open special file specialfile for
Explanation: The server is unable to obtain the device tracing parameter device driver; errno =
number for the specified drive. This could occur if an errno.
invalid device name is specified for the drive or if there Explanation: The special file created by the device
is hardware errors. driver for tracing purposes could not be opened by the
System action: The drive is temporarily made offline server. This file should be created when the device
and is not used for tape operations. The server polls driver is configured on the system
the drive at one-half minute intervals to check if the System action: Device driver tracing could not be
condition has cleared. Once the drives is accessible started.
again, the drive is brought online.

ANR8971E ANR8977W
User response: Make sure that the special file exists

ANR8974I Found new path for path source name and
and can be accessed by the server. If the device driver
target name target name old path old path
has not been completely configured and special files
name new path new path name. Path
created for all devices, do so. The device driver can
information will be updated remotely.
also be traced by specifying the name of a library or
drive that has been defined to the TSM Server. Explanation: A new path has been found for the
device on the library client or storage agent. Will try to
update the path information on the library manager.
ANR8971E Unable to validate directory name
directory name for parameter command. System action: .
Explanation: The specified directory name was being User response: The path change may be caused by
used in the indicated command. The server attempted system reboot or cable swap or device addition or
to validate that the directory was accessible so that it removal.
could be used in the command definition. The server
was unable to validate that the directory was
ANR8975I Found new path for path source name and
accessible.
target name target name old path old path
System action: The command fails. The server name new path new path name. Path
continues. information is updated.
User response: Make sure that the directory exists and Explanation: A new path has been found for the
can be accessed by the server. device and the path information has been updated.
System action: .
ANR8972E command: Unable to find the element
User response: The path change may be caused by
number for drive drive name in library
system reboot or cable swap or device addition or
library name.
removal.
Explanation: Because the drive serial number does not
match any drive serial number in the serial/element
ANR8976E Unable to open special file specialfile for
number map reported by the library, the element
LUN reset with errno = errno.
number cannot be determined.
Explanation: The special file created by the device
driver for LUN reset purposes could not be opened by
User response: Make sure the serial number entered the server. This file should be created when the device
for the drive is correct if AUTODETECT is not active. If driver is configured on the system
AUTODETECT is active, the drive serial number might
System action: LUN reset could not be started.
be incorrect or the library reported an incorrect
serial/element number map. Contact your service User response: Make sure that the special file exists
representative. 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
ANR8973E Reset has failed to break the reservation
configuration.
set by another system for device device
name with path path name.
ANR8977W The volume loaded into library library
Explanation: The attempt to reset the device
name did not have a valid label. Please
reservation set by another system has failed.
load a scratch volume with a valid label.
System action: .
Explanation: During normal operations a MANUAL
User response: If this tape device is a Fibre Channel library will prompt the user for the desired volume
direct attached device on Windows 2003, please make name if the volume does not have a valid label and the
sure the HBA driver is a StorPort driver by checking AUTOLABEL parameter is turned on. However, the
the HBA vendor's support web site. The device reset utility mode of DUMPDB cannot prompt the user for a
(LUN Reset) on Windows 2003 requires StorPort driver. desired volume name.
Otherwise, the device may have to be rebooted to reset
System action: The server unloads the volume and
the reservation. If not rebooted, this device will not be
asks for a new scratch volume with a valid label.
accessible. If "RESETDrive" keyword for the update
library command is set to NO, device reset will not be User response: The user needs to insert scratch
attempted. volumes with valid labels or reissue the DUMPDB
command and specify the desired volume name on the
command line with the VOLUMENAMES parameter.
See the DUMPDB documentation.
ANR8978W ANR8985E
and ready, then reissue the command.

ANR8978W The number of drives in library library
name has been increased from original
drive count to new drive count Please ANR8983I SCAN LIBRARY process for library
restart the TSM server to update the library name completed successfully.
configuration;
Explanation: The background process for an SCAN
Explanation: The number of drives in the library has LIBRARY command has completed successfully.
been increased. The new configuration will be recorded
if TSM server is restarted. System action: The library has been scaned.
System action: . User response: None.
User response: Number of drives in the library has

been increased. The user needs to restart the TSM ANR8984E The drive drive name in library library
server to capture the new configuration. name is incapable of performing any
drive encryption operations.
ANR8979I Command: Operation for library library Explanation: The server queried the drive's encryption
name started as process process ID. capability, and the query failed or the query showed
that the drive does not have encryption capabilities.
Explanation: A sacn library process has been started
for the given library. The process is assigned the ID System action: The mount operation fails.
specified in the message. User response: If this message occurs on a scratch
System action: The server starts a background process mount and drive encryption has not been utilized yet,
to perform the operation in response to the SCAN you can turn drive encryption off by updating the
LIBRARY command entered by an administrator. DRIVEENCRYPTION parameter on the device class.
Otherwise, verify your hardware configuration. First,
User response: To obtain status on the process, issue verify that all the drives in this logical library support
the QUERY PROCESS command. The process may be drive encryption. Second, verify that the device driver
canceled with the CANCEL PROCESS command. controlling all of the drives in this library also supports
drive encryption. If both the drives and the device
driver support drive encryption, call your drive
ANR8980I SCAN LIBRARY process for library
hardware support.
library name has been canceled.
ANR8985E The drive drive name in library library
been working to scan the given library is canceled by
name is using an encryption method that
is incompatible with the current server
System action: The server process is ended and server settings.
Explanation: The server requires the drive to use
User response: None. various drive encryption methods based on the
DRIVEENCRYPTION device class parameter for empty
volumes or based on the previous encryption method
ANR8981I Scanning for library library name.
used for filling volumes. The server is unable to
Explanation: In response to a QUERY PROCESS properly handle the volume's encryption key without
command, this message displays the status for an resolving this conflict.
SCAN LIBRARY process on the server.
System action: The mount operation fails.
User response: If this message occurs while mounting
User response: None. The process may be canceled by an empty volume the encryption method setup in your
an authorized administrator using the CANCEL hardware environment is incompatible with the
PROCESS command. DRIVEENCRYPTION setting in your device class.
Either update the device class or your hardware's
encryption method such that these setting no longer
ANR8982E SCAN LIBRARY process for library conflict. If this message occurs while mounting a filling
library name failed. volume, either update your hardware configuration to
Explanation: The background process for an SCAN the same method used while originally backing up this
LIBRARY command has failed. volume, which can be determined by the QUERY
VOLUME FORMAT=DETAIL command, or update this
System action: The background process ends. volume's access to UNAVAILABLE.

ANR8986E ANR8992E
manager. The library manager was found to be

ANR8986E The server currently doesn't allow AES
unavailable at this time.
encryption which is required for drive
encryption support with the System action: None.
DRIVEENCRYPTION=ON parameter on
the device class. User response: Verify the primary library manager is
up and operational. Once the server is verified to be
Explanation: Without AES encryption support the operational, retry the operation.
server cannot generate adequately strong enough
encryption keys for drive encryption.
ANR8990E Device Device Name is not supported by
System action: The mount operation fails. the Tivoli Storage Manager server.
User response: Update the DRIVEENCRYPTION Explanation: The device product identification is not
parameter on the device class to a value other than recognized by the Tivoli Storage Manager server.
ON.
ANR8987W The server will not encrypt the volume User response: Determine if the installed level of the
volume name. server supports the device by visiting the Tivoli Storage
Manager Supported Devices for AIX, HP-UX, Solaris,
Explanation: Drive encryption with the device class and Windows document at http://ibm.co/Ykot3r.
parameter setting of DRIVEENCRYPTION=ON will
only encrypt storage pool volumes. Thus, backupsets, If the device is a tape drive and is not supported, you
DB backups, and export volumes will not be encrypted. can use it with the generic tape format. To use the
drive, specify GENERICTAPE=Yes when defining a
System action: The mount continues, but encryption is path to the drive. If the device is supported and this
not used. message is received, search the Tivoli Storage Manager
Support Web site for known solutions:
User response: If encryption is needed for this volume
or other backupsets, DB backups, or export volumes, http://www.ibm.com/software/sysmgmt/products/
use a different method of encryption: use a device class support/IBMTivoliStorageManager.html
parameter of DRIVEENCRYPTION=ALLOW and a
hardware method of 'Library' or 'System' (do not use If no solution is found, report the issue to Tivoli
the 'Application' method). Storage Manager Support.
ANR8988W Library Library Name failed to relabel ANR8991E The GENERICTAPE format is not
volume Volume Name after it returned to supported with drive Device Name.
scratch. Explanation: The device driver does not support all
Explanation: The RELABELSCRATCH option is features required for the GENERICTAPE format.
enabled, and while attempting to relabel the volume System action: None.
the operation failed.
User response: Make sure the tape drive is controlled
System action: None. by the native device driver. The Tivoli Storage Manager
User response: This warning may be issued if the device driver does not support the generic tape format.
relabeling operation attempts to relabel the same If the drive is controlled by the Tivoli Storage Manager
volume as another library volume operation: LABEL device driver and you intend to use the Tivoli Storage
LIBVOLUME, CHECKIN LIBVOLUME, CHECKOUT Manager tape format with the drive, do not specify
LIBVOLUME, or another relabeling operation. For GENERICTAPE=Yes when defining a path to the drive.
example, suppose two relabeling operations run on the
same volume. If the first relabeling operation succeeds ANR8992E The library state refresh for library name
and the second operation fails, no action is required. failed.
Verify the volume is still checked into the library with Explanation: The operation to re-initialize the library's
the QUERY LIBVOL command. If it is not checked in, state failed.
use LABEL LIBVOL or CHECKIN LIBVOL to check the
volume back into the library. System action: None.
User response: To refresh the library state, halt and
ANR8989E Unable to establish a communication restart the Tivoli Storage Manager server.
session with the primary library
manager.
Explanation: The requested operation required that a
communication session be established with a library
ANR8993I ANR9000E
meet the version requirement to support append-only

ANR8993I The library state refresh for library name
mode.
was successful.
System action: The server will not enable append-only
Explanation: The server successfully re-initialized the
mode on the tape drive for data overwrite protection.
library's state.
User response: Upgrade the device driver for the
drive to the required version.
ANR8998W Encryption has been disabled for drive
ANR8994W Append-only mode is not supported on drive name in library library name.
drive Drive Name.
Explanation: The server determined that the drive's
Explanation: The server attempted to enable encryption method was Application Managed
Append-Only mode on the tape drive for data Encryption (AME). Since the server is assumed
overwrite protection. However, the tape drive does not responsibility for encryption settings when device class
support Append-Only mode. uses DRIVEENCRYPT=ALLOW and the drive uses
AME, encryption has been disabled.
System action: The server will not enable append-only
mode on the tape drive for data overwrite protection. System action: The mount continues with encryption
disabled.
User response: No action is required. You can set the
server option CHECKTAPEPOS to No or TSMonly if User response: If encryption is intended to be used
you do not wish the server to use append-only mode for this operation, with TSM managing the encryption
for data overwrite protection on the tape drives that keys, then the DRIVEENCRYPT parameter should be
support append-only mode. set to ON. If encryption is intended to be used for this
operation, without TSM managing the encryption keys
(for example, NEC, Fujitsu, and SpectraLogic provide
ANR8995E Unable to write to volume Volume Name
AME encryption solutions without TSM managing
in drive Drive Name.
encryption), then the DRIVEENCRYPT parameter
Explanation: The server is unable to write to the should be set to EXTERNAL. In either of these
volume because the drive is in append-only mode and situations, data on the volume used in this operation
the volume is write-protected. will need to be moved to a new volume with the
correct settings to encrypt the data.
System action: The server will dismount the volume
and continue processing with another volume.
ANR8999E Directory name directory name has been
User response: Contact your service representative for duplicated in parameter command.
assistance.
Explanation: When defining or updating multiple
directories for a device class, you can only specify a
ANR8996W Unable to query or enable append-only directory name once in the command.
mode on drive Drive Name.
System action: The command fails. The server
Explanation: The server was unable to query or continues.
enable append-only mode on the tape drive.
User response: Ensure that the directory name is
System action: The server will not enable append-only specified only once in the command.
mode for the volume during this mount. The server
will attempt to enable append-only mode the next time
a volume is mounted if the server option ANR9000E Drive drive name does not support
CHECKTAPEPOS is set to Yes or DRIVEonly. logical block protection.
User response: If the problem persists, contact your Explanation: The LBPROTECT parameter associated
service representative for assistance. If you do not want with the device class is set to enable logical block
the server to use append-only mode for data overwrite protection. However, the tape drive does not support
protection, you can set the server option logical block protection.
CHECKTAPEPOS to No or TSMonly.
User response: Update drive firmware to the level
ANR8997W The current version of the device driver
that supports logical block protection.
for drive Drive Name is Driver Version. To
enable append-only mode, version
Required Version or later is required.
Explanation: The device driver for the drive does not

ANR9001W ANR9007E
root user to locate and delete the st device special files.

ANR9001W Volume volume name does not have
Then, retry the operation. For more information about
logical block protection.
this issue, see the Administrator's Guide in the
Explanation: The server cannot enable logical block Information Center.
protection for this volume. Data that is already on the
volume does not have logical block protection, or the
ANR9005E Command: Library library name has an
media type is not compatible with logical block
active relabel process and can not be
protection.
deleted.
System action: The operation will continue without
Explanation: The designated library can not be
logical block protection enabled on the volume.
deleted or updated because it is currently in use for a
User response: If the media type supports logical relabel operation.
block protection, mark the volume access to
READONLY so that the server cannot write to the
volume. User response: Wait until the relabel operation
completes, and then retry the command.
ANR9002E The version of the device driver for
drive Drive Name is Driver Version. Driver ANR9006E Tape volumes must be physically
version Required Version or later is removed from an ACSLS cartridge
required for logical block protection. access port (CAP).
Explanation: The device driver for the drive does not Explanation: Tape volumes are located in the ACSLS
meet the version requirement for logical block CAP. The ACSLS server requires users to physically
protection. remove these volumes from the CAP within 30
minutes. When REMOVE=YES is set for the
CHECKOUT LIBVOLUME command, a tape ejection
User response: Upgrade the device driver for the operation is scheduled. If the user fails to remove the
drive to the required version. tape from the CAP within 30 minutes, the ACSLS
server sets a failure status for the tape ejection
operation.
ANR9003E The block CRC validation failed on
volume volume name in drive drive name. System action: The ACSLS library ejected tape
volumes and relocated them to a CAP.
Explanation: The data block was corrupted while it
was transferred to or from the drive. User response: Remove the volumes from the CAP. If
there are no tape cartridges in the CAP, check the
ACSLS library to ensure that no tapes are lodged there.
User response: Restart the operation to try the volume
in a different drive. If the problem persists, check the
ANR9007E Command: The library cartridge access
hardware connections and the tape drive.
port (CAP) ID is invalid for library
library name.
ANR9004E The server has detected that drive name
Explanation: Tape volumes were not ejected from the
can also be accessed by other
ACSLS library because the library CAP ID was not
applications through the st device
specified in the CHECKOUT LIBVOLUME command.
special file device name. All st device
By default, all CAPs initially have a priority value of 0,
special files for this drive must be
which means that the ACSLS server does not
deleted.
automatically select a CAP.
Explanation: When more than one device driver can
System action: The system failed to eject the tape
access a drive, tape labels or other data can be
volumes.
overwritten. To prevent possible data integrity issues,
you must delete all st device special files for this tape User response: To verify the CAP priority value, issue
drive. the QUERY CAP command. If the priority value is 0,
reissue the CHECKOUT LIBVOLUME command with a
System action: The operation fails or the drive is
CAP ID. Alternatively, set the CAP priority to a
temporarily taken offline and is not available for tape
non-zero value and reissue the CHECKOUT
operations. The server polls the drive at thirty second
LIBVOLUME command.
intervals to verify that all of the st device special files
for the tape drive have been deleted. Once all files have
been deleted, the drive is brought back online.
User response: Run the rmstdev utility with -d as the
ANR9008E ANR9014E
available Tivoli Storage Manager information centers.

ANR9008E Unable to determine the drive type for
Device of type Device Inquiry String.
ANR9012E There is no drive available for the
Explanation: The drive could not be opened. This
database restore operation for device
version of Tivoli Storage Manager may not support the
class device class name.
drive type.
Explanation: The database restore operation cannot be
System action: The system failed to identify the drive
completed. There are no available mount points.
type.
Possible reasons include:
User response: Verify that the drive type is supported. v The device configuration file is not correctly defined
See the Tivoli Storage Manager Supported Devices web to acccess the media.
page at: http://www.ibm.com/software/sysmgmt/
v There is a problem with the media.
products/support/
IBM_TSM_Supported_Devices_for_AIXHPSUNWIN. System action: The database restore operation fails.
html or http://www.ibm.com/software/sysmgmt/
products/support/ User response: Review the information in the message
IBM_TSM_Supported_Devices_for_Linux.html. explanation and take action to correct any problems
with the device configuration file or media. Reissue the
RESTORE DB command.
ANR9009E The cartridge access port (CAP) for
library library name is not available. The
CAP status is cap status. ANR9013W The library library name does not use
RESETDRIVES.
Explanation: An error occurs in the CAP while
accessing the specified library. Explanation: In a cluster failover environment when
running the DEFINE LIBRARY command, you must set
System action: The operation fails. the RESETDRIVES parameter to YES when the
SHARED parameter value is NO (a default value).
User response: Ensure that the CAP is empty, all tape
volumes are removed from the CAP, and the CAP door The RESETDRIVES parameter specifies that the server
is closed. cleans up the reservation in tape drives after a cluster
failover occurrs. For example, host A is a primary host
system and host B is a secondary host system in a
ANR9010W Unable to verify drive drive name.
cluster failover environment. Before failover occurs,
Explanation: The mount operation fails because the host A uses a tape drive. After failover occurrs from
SANDISCOVERY option is not enabled. Therefore, the host A to host B, host A continues to reserves this tape
SAN discovery function did not verify whether the drive. If the RESETDRIVES parameter is set to NO,
specified drive must be opened. host B does not clean up the reservation from this tape
drive. Host B no longer has access to this tape drive. If
System action: The SAN discovery function is not
the RESETDRIVES parameter is set to YES, host B
turned on.
cleans up the reservation from this tape drive and can
User response: Verify the SANDISCOVERY option has access to this drive. For more information on the
value in the dsmserv.opt file. If the value is set to OFF RESETDRIVES parameter, see the DEFINE LIBRARY
or UNSCANNEDPATHOFF, change the value to ON. command.
System action: A server cannot access tape drives that
ANR9011E Position error: the volume volume name are reserved by another server in a cluster failover
in drive drive name is not at the expected environment after a failover has occurred.
expected position : The actual volume
User response: Issue the UPDATE LIBRARY
position is: expected volume position.
command and specify the RESETDRIVES=YES option.
Explanation: The CHECKTAPEPOS server option has
determined that there is a volume position error Tivoli
ANR9014E Volume volume name is incompatible
Storage Manager has not repositioned the tape. Writing
with drive drive name.
is halted to prevent data loss.
Explanation: The drive cannot read the volume
System action: The write operation fails.
format. This can be attributed to a different generation
User response: Refer to documentation about media format or an encrypted tape.
preventing tape label overwrites in the Tivoli Storage
Manager Information Center and follow the steps for
your operating system. See Tivoli Documentation User response: Make sure that the volume is correctly
Central at https://www.ibm.com/developerworks/ formatted for this drive, and validate the device class
wikis/display/tivolidoccentral/Tivoli for links to settings for this operation. If it is encrypted, the drive

ANR9015E ANR9581W (Solaris)
must be configured to decrypt the cartridge. The replacement name can be another raw partition
name or a regular file name.
ANR9015E The device device name path symlink
appears to be circular. ANR9580W (Solaris) Command: Generated
replacement volume name volume name
Explanation: When the server attempts to validate the
may not be a valid raw partition name.
device path the symlink is too long.
Original volume name:volume name.
System action: A server cannot access the device due Stanza is stanza name.
to a device symlink problem.
Explanation: Appending the replacement volume
User response: Issue the autoconf script to re-establish name postfix to the original volume name has created a
the links. name that may not be a valid raw partition name.
System action: Replacement volume name is used in
ANR9579W (HP-UX) Command: The file file name the recovery plan stanza.
cannot be found.
User response: Manually update the generated
Explanation: The specified file cannot be found. recovery plan stanza with a legal replacement name.
The replacement name can be another raw partition
System action: For the default server executable file, name or a regular file name.
the PREPARE command uses /opt/IBMadsm-s/bin/
dsmserv.
ANR9581W (HP-UX) Command: Volume file name not
User response: Determine why the file does not exist found while building stanza recovery
and create it if necessary. plan stanza name.
Explanation: This volume is defined to the server but
ANR9579W (Linux) Command: The file file name does not exist. The device class associated with the
cannot be found. volume is DISK or the device class device type is FILE.
Explanation: The specified file cannot be found. System action: The entry for the volume is not
System action: For the default server executable file, included in the recovery plan stanza.
the PREPARE command uses /opt/IBMadsm-s/bin/ User response: Determine why file does not exist;
dsmserv. create if necessary.
User response: Determine why the file does not exist
and create it if necessary. ANR9581W (Linux) command: Volume file name not
found while building stanza recovery
ANR9579W (Solaris) Command: The file file name plan stanza name.
cannot be found. Explanation: This volume is defined to the server but
Explanation: The specified file cannot be found. does not exist. The device class associated with the
volume is DISK or the device class device type is FILE.
System action: For the default server executable file,
the PREPARE command uses /opt/IBMadsm-s/bin/ System action: The entry for the volume is not
dsmserv. included in the recovery plan stanza.
User response: Determine why the file does not exist User response: Determine why file does not exist;
and create it if necessary. create if necessary.
ANR9580W (Linux) Command: Generated replacement ANR9581W (Solaris) Command: Volume file name not
volume name volume name may not be a found while building stanza recovery
valid raw partition name. Original plan stanza name.
volume name:volume name. Stanza is Explanation: This volume is defined to the server but
stanza name. does not exist. The device class associated with the
Explanation: Appending the replacement volume volume is DISK or the device class device type is FILE.
name postfix to the original volume name has created a System action: The entry for the volume is not
name that may not be a valid raw partition name. included in the recovery plan stanza.
System action: Replacement volume name is used in User response: Determine why file does not exist;
the recovery plan stanza. create if necessary.
User response: Manually update the generated
recovery plan stanza with a legal replacement name.
v SET DRMPLANPREFIX
ANR9582E (HP-UX) Command: Generated file name
too long. Length of directory or prefix v SET DRMINSTRPREFIX
'prefix' plus 'name' exceeds maximum v PREPARE
characters characters.
Explanation: The file name generated is too long. The ANR9583E (Linux) command: Cannot generate fully
maximum valid length is shown in the message. qualified file name for 'name'.
System action: The recovery plan file was not created. Explanation: A failure occurred expanding the
specified file name.
valid prefix. The following commands are used to System action: Recovery plan file not created.
specify the prefix:
v SET DRMPLANPREFIX valid prefix. The following commands are used to
v SET DRMINSTRPREFIX specify the prefix:
v PREPARE v SET DRMPLANPREFIX
v SET DRMINSTRPREFIX
ANR9582E (Linux) command: Generated file name too v PREPARE
long. Length of directory or prefix
'prefix' plus 'name' exceeds maximum
characters characters. ANR9583E (Solaris) Command: Cannot generate fully
qualified file name for 'name'.
Explanation: The file name generated is too long. The
maximum valid length is shown in the message. Explanation: A failure occurred expanding the
valid prefix. The following commands are used to User response: Reissue the command specifying a
specify the prefix: valid prefix. The following commands are used to
specify the prefix:
v SET DRMPLANPREFIX
v SET DRMPLANPREFIX
v PREPARE
v PREPARE
ANR9582E (Solaris) Command: Generated file name

too long. Length of directory or prefix ANR9584E (HP-UX) command: Cannot generate server
'prefix' plus 'name' exceeds maximum options file name.
characters characters. Explanation: A failure occurred generating the server
Explanation: The file name generated is too long. The options file name.
maximum valid length is shown in the message. System action: Recovery plan file not created.
System action: The recovery plan file was not created. User response: See accompanying messages for more
User response: Reissue the command specifying a information.
valid prefix. The following commands are used to
specify the prefix: ANR9584E (Linux) command: Cannot generate server
v SET DRMPLANPREFIX options file name.
v SET DRMINSTRPREFIX Explanation: A failure occurred generating the server
v PREPARE options file name.
ANR9583E (HP-UX) Command: Cannot generate fully
qualified file name for 'name'.
information.
Explanation: A failure occurred expanding the
ANR9584E (Solaris) Command: Cannot generate
System action: Recovery plan file not created. server options file name.
User response: Reissue the command specifying a Explanation: A failure occurred generating the server
valid prefix. The following commands are used to options file name.
specify the prefix:

User response: See accompanying messages for more User response: See accompanying messages for more
information. information.
ANR9585E (HP-UX) Command: Cannot generate a ANR9600E (AIX) Invalid information passed to
volume history file name. NETLS license interface.
Explanation: A failure occurred generating the volume Explanation: The server licensing functions
history file name. encountered an internal error in accessing license
information for the server storage capacity and number
of registered clients.
System action: Server operation continues. New
information.
licensing information is not used by the server.
ANR9585E (Linux) command: Cannot generate a
volume history file name.
Explanation: A failure occurred generating the volume
ANR9600E (Solaris) Failed to allocate memory for
history file name.
shared memory communications. Error:
System action: Recovery plan file not created. error text.
User response: See accompanying messages for more Explanation: An error has occurred when attempting
information. to get memory for the shared communications option.
System action: Shared memory communications will
ANR9585E (Solaris) Command: Cannot generate a not be activated.
User response: The maximum shared memory is, most
Explanation: A failure occurred generating the volume likely, too small. To increase on SUN, update
history file name. "/etc/system" with "set
shmsys:shminfo_shmmax=268435456" (a recommended
System action: Recovery plan file not created. size).
information. ANR9601E (AIX) The NETLS license interface was
not initialized properly.
ANR9586E (HP-UX) Command: Cannot generate a Explanation: The server licensing functions
device configuration file name. encountered an internal error in accessing license
Explanation: A failure occurred generating the device information for the server storage capacity and number
configuration file name. of registered clients.
System action: Recovery plan file not created. System action: Server operation continues. New
information. User response: Contact your service representative for
ANR9586E (Linux) command: Cannot generate a

device configuration file name. ANR9601E (Solaris) Failed to allocate message queue
for the shared memory communications
Explanation: A failure occurred generating the device Error: error text.
configuration file name.
Explanation: An error has occurred when attempting
System action: Recovery plan file not created. to get memory for the shared communications option.
User response: See accompanying messages for more System action: Shared memory communications will
information. not be activated.
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) ANR9609E (AIX)
ANR9602E (AIX) Invalid JOB information passed to ANR9605E (AIX) An invalid vendor ID was passed
the NETLS Interface. to NETLS.
Explanation: The server licensing functions Explanation: The server licensing functions
encountered an internal error in accessing license encountered an internal error in accessing license
information for the server storage capacity and number information for the server storage capacity and number
of registered clients. of registered clients.
System action: Server operation continues. New System action: Server operation continues. New
licensing information is not used by the server. licensing information is not used by the server.
User response: Contact your service representative for User response: Contact your service representative for
assistance in resolving the error. assistance in resolving the error.
ANR9602E (Solaris) Error errno while attaching ANR9606E (AIX) NETLS failed to find socket
memory segment for shared memory families to contact a server.
communications.
Explanation: The server licensing functions
Explanation: An error occurred while attempting to encountered an internal error in accessing license
attach a shared memory segment for a shared information for the server storage capacity and number
communications session. of registered clients.
System action: The shared memory communications System action: Server operation continues. New
session does not initialize. licensing information is not used by the server.
User response: Check the SUN documentation for the User response: Contact your service representative for
shmat subroutine and determine what the errno assistance in resolving the error.
indicates, and take the appropriate action to correct the
error.
ANR9607E (AIX) No NETLS Servers found.
Explanation: The server licensing functions
ANR9603E (AIX) The NETLS Nodelock file could
encountered an internal error in accessing license
not be created.
Explanation: The server was not able to create the file of registered clients.
/usr/lib/netls/conf/nodelock which is used for storing
license password information.
User response: If the server is not running with root
authority, make sure that directory authorities in the
ANR9608E (AIX) A NETLS Security Breach was
/usr/lib/netls/conf path are set so that the user ID
encountered.
under which the server is running can create, read, and
write to the /usr/lib/netls/conf/nodelock file. If the Explanation: The server licensing functions
server is running with root authority, contact your encountered an internal error in accessing license
service representative for assistance in resolving this information for the server storage capacity and number
problem. of registered clients.
ANR9604E (AIX) The NETLS license interface licensing information is not used by the server.
encountered an internal error.
Explanation: The server licensing functions assistance in resolving the error.
encountered an internal error in accessing license
of registered clients. ANR9609E (AIX) Incorrect license entered: Password
entered = password Annotation entered =
System action: Server operation continues. New annotation.
Explanation: The license information entered for a
User response: Contact your service representative for REGISTER LICENSE command is not correct.
User response: Register the license again with the

ANR9610E (AIX) ANR9613W (HP-UX)
REGISTER LICENSE command. Be sure to correctly /usr/lib/netls/conf path are set so that the user ID
enter the license information. under which the server is running can create, read, and
write to the /usr/lib/netls/conf/nodelock file. If the
server is running with root authority, contact your
ANR9610E (AIX) Unable to create directory: directory.
service representative for assistance in resolving this
Explanation: The REGISTER LICENSE command is problem.
unable to either create or verify the specified directory
structure.
ANR9612E (AIX) Error writing to NODELOCK file.
Explanation: The REGISTER LICENSE command fails
User response: If the server is not running with root writing to the nodelock file.
/usr/lib/netls/conf path are set so that the user ID
under which the server is running can create, read, and User response: If the server is not running with root
write to the /usr/lib/netls/conf/nodelock file. If the authority, make sure that directory authorities in the
server is running with root authority, contact your /usr/lib/netls/conf path are set so that the user ID
service representative for assistance in resolving this under which the server is running can create, read, and
problem. write to the /usr/lib/netls/conf/nodelock file. If the
server is running with root authority, contact your
service representative for assistance in resolving this
ANR9610E (Linux) Unable to create directory:
problem.
directory.
Explanation: The REGISTER LICENSE command is
ANR9613W (AIX) Error loading modname for
Licensing function: error string.
structure.
Explanation: The server cannot load file module
modname to initialize licensing functions due to error
User response: If the server is not running with root error string.
System action: Server operation continues. Default
given directory path are set so that the user under
licensing values are in effect for running the server.
which the server is running can create, read, and write
to the server's license file. If the server is running with User response: The dsmreg.lic module is accessed as
root authority, contact your service representative for part of the load process for licensing. It should be in
assistance in resolving this problem. the same directory as the dsmserv executable or it must
be in a directory that is pointed to by the
DSMSERV_DIR environment variable. The dsmreg.lic
ANR9610E (Solaris) Unable to create directory:
module is only installed when you purchase the
directory.
product.
ANR9613W (HP-UX) Error loading modname for
structure.
User response: If the server is not running with root modname to initialize licensing functions due to error
authority, make sure that directory authorities in the error string.
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 User response: The dsmreg.lic module is accessed as
assistance in resolving this problem. part of the load process for licensing. It should be in
the same directory as the dsmserv executable or it must
be in a directory that is pointed to by the
ANR9611E (AIX) Unable to open NODELOCK file:
DSMSERV_DIR environment variable. The dsmreg.lic
file.
module is only installed when you purchase the
Explanation: The REGISTER LICENSE command is product.
unable to either create or open the nodelock file.
User response: If the server is not running with root
ANR9613W (Linux) ANR9615E (Solaris)
ANR9613W (Linux) Error loading modname for ANR9614E (Solaris) Unable to open license file: file.
Licensing function.
Explanation: The server cannot load file module unable to either create or open the server license file.
modname to initialize licensing functions.
User response: Make sure that the user ID under
which the server is running has the authority required
User response: dsmreg.lic is accessed as part of the to create or write, or both, to the license file in the
load process for licensing. It should be in the same directory in which the server is running. If this does
directory as the dsmserv executable file or it must be in not resolve the problem, contact your service
a directory that is pointed to by the DSMSERV_DIR representative for assistance.
environment variable. The dsmreg.lic module is only
installed when you purchase the product.
ANR9615E (AIX) Error writing to adsmserv.licenses
file.
ANR9613W (Solaris) Error loading modname for
writing to the server license file.
modname to initialize licensing functions due to error
error string. User response: Make sure that the user ID under
to create or write, or both, to the license file in the
directory in which the server is running. Also, ensure
User response: dsmreg.lic is accessed as part of the that free space is available in the file system so that the
load process for licensing. It should be in the same license information can be written to the file. If this
directory as the dsmserv executable file or it must be in does not resolve the problem, contact your service
a directory that is pointed to by the DSMSERV_DIR representative for assistance.
environment variable. The dsmreg.lic module is only
installed when you purchase the product.
ANR9615E (Linux) Error writing to adsmserv.licenses
file.
ANR9614E (AIX) Unable to open license file: file.
Explanation: The REGISTER LICENSE command is writing to the server license file.
unable to create or open the server license file.
User response: Make sure that the userid under which
User response: Make sure that the user ID under the server is running has the authority required to
which the server is running has the authority required create and/or write to the license file in the directory in
to create or write, or both, to the license file in the which the server is running. Also ensure that there is
directory in which the server is running. If this does free space available in the filesystem so that the license
not resolve the problem, contact your service information can be written to the file. If this does not
representative for assistance. resolve the problem contact your service representative
for assistance.
ANR9614E (Linux) Unable to open license file: file.
ANR9615E (Solaris) Error writing to
adsmserv.licenses file.
unable to either create or open the server license file.
writing to the server license file.
User response: Make sure that the user ID under
to create or write, or both, to the license file in the User response: Make sure that the userid under which
directory in which the server is running. If this does the server is running has the authority required to
not resolve the problem, contact your service create and/or write to the license file in the directory in
representative for assistance. 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.

ANR9616I (AIX) ANR9618E (Linux)
ANR9616I (AIX) Invalid license record record value ANR9617W (Linux) Invalid license authorization:
found in license file - it will be authorization string.
skipped.
Explanation: The license authorization specified for a
Explanation: The license manager found an invalid REGISTER LICENSE command is not valid.
record in the server license file (adsmserv.licenses). The
System action: Server operation continues; licensing
record is ignored.
terms are not changed by the REGISTER LICENSE
System action: The invalid record is ignored. command.
User response: Erase the adsmserv.licenses file and User response: Examine the license authorization that
reregister your licenses. was entered using the REGISTER LICENSE command.
Reenter the command if the license authorization was
not specified correctly. If the license authorization has
ANR9616W (Linux) Invalid license record record value
been specified correctly, contact your service
found in license file - it will be ignored.
representative.
Explanation: The license manager found an invalid
record in the server license file (adsmserv.licenses). The
ANR9617W (Solaris) Invalid license authorization:
record is ignored.
authorization string.
System action: The invalid record is ignored.
Explanation: The license authorization specified for a
User response: Erase the adsmserv.licenses file and REGISTER LICENSE command is not valid.
reregister your licenses. Refer to the licenses provided
to you to ensure that only valid licenses are specified
with the REGISTER LICENSE command.
command.
User response: Examine the license authorization that
ANR9616W (Solaris) Invalid license record record
was entered using the REGISTER LICENSE command.
value found in license file - it will be
Reenter the command if the license authorization was
ignored.
not specified correctly. If the license authorization has
Explanation: The license manager found an invalid been specified correctly, contact your service
record in the server license file (adsmserv.licenses). The representative.
record is ignored.
System action: The invalid record is ignored. ANR9618E (AIX) License registration is not
supported on this server.
User response: Erase the adsmserv.licenses file and
reregister your licenses. Refer to the licenses provided Explanation: The REGISTER LICENSE command fails
to you to ensure that only valid licenses are specified because the license authorization module cannot be
with the REGISTER LICENSE command. found.
ANR9617I (AIX) Invalid license authorization: terms are not changed by the REGISTER LICENSE
authorization string. command.
Explanation: The license authorization specified for a User response: The license authorization file is
REGISTER LICENSE command is not valid. required for formal licensing for the AIX/6000 server.
The file is delivered when the product is purchased,
System action: Server operation continues; licensing but it is not available in the product service stream or
terms are not changed by the REGISTER LICENSE with demonstration copies of the server. If you have
command. purchased the server, contact your service
User response: Examine the license authorization representative for assistance in resolving this problem.
string that was entered with the REGISTER LICENSE
command. Reenter the command if the license ANR9618E (Linux) License registration is not
authorization was not specified correctly. If the license supported on this server.
authorization has been specified correctly, contact your
service representative. Explanation: The REGISTER LICENSE command
failed because the license authorization module could
not be found.
command.
ANR9618E (Solaris) ANR9624I (HP-UX)
User response: The license authorization file is System action: The Tivoli Disaster Recovery Manager
required for formal licensing for the server. The file is license allows customers to store information in the
delivered when the product is purchased, but is not server regarding machines and recovery media, allows
available in the product service stream or with management of offsite recovery media, collects and
demonstration copies of the server. If you have stores information in the server for server recovery and
purchased the server, please contact your service allows data base and storage pool backups to a device
representation for assistance in resolving this problem. class of type server. The server checks this license when
machines or recovery media are defined to the server,
when PREPARE or MOVE DRMMEDIA are invoked
ANR9618E (Solaris) License registration is not
and when a data base backup or storage pool backup
to a device class of type server are performed to ensure
Explanation: The REGISTER LICENSE command that the server is licensed to perform this function.
failed because the license authorization module could
User response: If you are interested in using the
not be found.
server, contact your service representative to obtain
System action: Server operation continues; licensing formal licenses for the server before the evaluation
terms are not changed by the REGISTER LICENSE period has elapsed. Without formal licenses, the server
command. will not support Tivoli Disaster Recovery Manager after
the expiration date shown.
User response: The license authorization file is
required for formal licensing for the server. The file is
delivered when the server is purchased, but is not ANR9624E (AIX) Unexpected error encountered in
available in the product service stream or with iFor/LS (SystemView License Use
demonstration copies of the server. If you have Management) routine license interface
purchased the server, please contact your service name status=xreported status code.
representation for assistance in resolving this problem.
Explanation: The server encountered an unexpected
error in accessing the SystemView License Use
ANR9622I (AIX) An EVALUATION LICENSE for Management function specified.
support of Tivoli Space Management
System action: The server license monitoring
will expire on expiration date.
operation fails
Explanation: The AIX/6000 server is distributed with
User response: The SystemView License Use
an evaluation license for Tivoli Space Management
Management product is installed during normal AIX
support. If no formal license is found for the server and
server installation. Check to make sure that server was
the evaluation period has not lapsed, this message is
installed correctly. If the installation was successful,
displayed each time the server checks the server license
re-boot your AIX system and re-start the server. If this
terms.
message continues to be issued, contact your service
System action: The Tivoli Space Management license representative.
allows clients to utilize the server for storing files
migrated during space management. The server checks
ANR9624I (HP-UX) An EVALUATION LICENSE for
this license when files are migrated to the server from
client nodes to ensure that the server is licensed to
perform this function.
Explanation: The server is distributed with an
evaluation license for Tivoli Space Management
formal licenses for the server before the evaluation
period has elapsed. Without formal licenses, the server
will not support Tivoli Space Management after the
terms.
expiration date shown.
System action: The Tivoli Space Management license
ANR9623I (AIX) An EVALUATION LICENSE for
support of Tivoli Disaster Recovery
Manager will expire on expiration date.
Explanation: The AIX/6000 server is distributed with perform this function.
an evaluation license for Tivoli 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.

ANR9624I (Linux) ANR9625I (HP-UX)
will not support Tivoli Space Management after the System action: The Tivoli Space Management license
expiration date shown. allows clients to utilize the server for storing files
ANR9624I (Linux) An EVALUATION LICENSE for
terms.
ANR9625E (AIX) Could not open file file name.
migrated during space management. The server checks Explanation: The server could not open the license
this license when files are migrated to the server from certificate file specified.
System action: The license registration command fails.
User response: Examine the file specification entered,
including wildcard characters, to determine if it names
the license certificate file(s) you intended to use. If an
error is found, re-try the command with the corrected
specification. If an error cannot be found, contact your
ANR9625I (HP-UX) An EVALUATION LICENSE for

ANR9624I (Solaris) An EVALUATION LICENSE for
support of Tivoli Disaster Recovery
evaluation license for Tivoli Disaster Recovery Manager
terms.
terms.
System action: The Tivoli 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
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
User response: If you are interested in using the machines or recovery media are defined to the server,
server, contact your service representative to obtain when PREPARE or MOVE DRMMEDIA are invoked
formal licenses for the server before the evaluation and when a data base backup or storage pool backup
period has elapsed. Without formal licenses, the server to a device class of type server are performed to ensure
will not support Tivoli Space Management after the that the server is licensed to perform this function.
ANR9624I (Windows) An EVALUATION LICENSE formal licenses for the server before the evaluation
for support of Tivoli Space Management period has elapsed. Without formal licenses, the server
will expire on expiration date. will not support Tivoli Disaster Recovery Manager after
the expiration date shown.
terms.
ANR9625I (Linux) ANR9627E (AIX)
ANR9625I (Linux) An EVALUATION LICENSE for ANR9625I (Windows) An EVALUATION LICENSE

support of Tivoli Disaster Recovery for support of Tivoli Disaster Recovery
Manager will expire on expiration date. Manager will expire on expiration date.
Explanation: The server is distributed with an Explanation: The server is distributed with an
evaluation license for Tivoli Disaster Recovery Manager evaluation license for Tivoli Disaster Recovery Manager
support. If no formal license is found for the server, support. If no formal license is found for the server and
and the evaluation period has not lapsed, this message the evaluation period has not lapsed, this message is
is displayed each time the server checks the server displayed each time the server checks the server license
license terms. terms.
System action: The Tivoli Disaster Recovery Manager System action: The Tivoli Disaster Recovery Manager
license allows customers to store information in the license allows customers to store information in the
server regarding machines and recovery media, allows server 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 Tivoli Disaster Recovery Manager after will not support Tivoli Disaster Recovery Manager after
the expiration date shown. the expiration date shown.
ANR9625I (Solaris) An EVALUATION LICENSE for ANR9626E (AIX) Invalid license certificate file: file
support of Tivoli Disaster Recovery name.
Explanation: The specified file does not contain valid
Explanation: The server is distributed with an license certificate information.
evaluation license for Tivoli Disaster Recovery Manager
System action: The license registration command
ignores the contents of the file.
displayed each time the server checks the server license User response: Examine the file specification entered,
terms. including wildcard characters, to determine if it names
System action: The Tivoli 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
stores information in the server for server recovery and
allows data base and storage pool backups to a device ANR9627E (AIX) Cannot access node license lock
class of type server. The server checks this license when file: file name.
machines or recovery media are defined to the server,
when PREPARE or MOVE DRMMEDIA are invoked Explanation: The server was not able to access the
and when a data base backup or storage pool backup specified file. The node lock file contains licensing
to a device class of type server are performed to ensure information for the server.
that the server is licensed to perform this function. System action: The license function fails.
User response: If you are interested in using the User response: Examine the file specification
server, contact your service representative to obtain displayed and ensure that the file attributes will allow
formal licenses for the server before the evaluation the server to access the file. The location of the file is
period has elapsed. Without formal licenses, the server either in the directory from which the server is started,
will not support Tivoli Disaster Recovery Manager after or in the directory specified by the DSMSERV_DIR
the expiration date shown. environment variable. Re-specify the DSMSERV_DIR
environment variable if this specification is in error.
Also ensure that there is sufficient space on the drive

ANR9628E (Windows) ANR9634E (HP-UX)
specified for the file. If the problem persists after these displayed and ensure that the file attributes will allow
corrections have been made, contact your service the server to access the file. The location of the file is
representative. either in the directory from which the server is started,
or in the directory specified by the DSMSERV_DIR
environment variable. Re-specify the DSMSER-DIR
ANR9628E (Windows) Unexpected error encountered
in iFor/LS (SystemView License Use
Management) routine license interface
specified for the file. If the problem persists after these
name status=xreported status code.
corrections have been made, contact your service
Explanation: The server encountered an unexpected representative.
Management function specified.
ANR9632I (Windows) Cannot load licensing DLL
System action: The server license monitoring library: DLL file name : the server will
operation fails assume evaluation licensing mode.
User response: The SystemView License Use Explanation: The server was not able to load the
Management product is installed during normal server specified dynamic link library.
installation. Check to make sure that the product was
System action: Server licensing asumes Try and Buy
mode with licenses for 180 days.
re-boot your system and re-start the server. If this
message continues to be issued, contact your service User response: The named DLL library(ies) are
representative. required for the server to support feature licensing. If
you are running an evaluation copy of the server, this
message should not cause concern and is normal. If the
ANR9629E (Windows) Could not open file file name.
libraries are installed and this message continues to be
Explanation: The server could not open the license issued, contact a support representative for assistance.
certificate file specified.
System action: The license registration command fails. ANR9634E (AIX) command name: No license certificate
files were found with the file name
User response: Examine the file specification entered, specification specification.
the license certificate file(s) you intended to use. If an Explanation: The server did not find any license
error is found, re-try the command with the corrected certificate file(s) with the file name specification
specification. If an error cannot be found, contact your entered.
ANR9630E (Windows) Invalid license certificate file:
file name.
the license certificate file(s) you intended to use. The
Explanation: The specified file does not contain valid file name specification indicates the fully qualified file
license certificate information. name the server was trying to read. The directory used
to locate the license certificate files when no explicit
System action: The license registration command path is provided is determined as follows:
v The directory path pointed by the environmental
User response: Examine the file specification entered, variable DSMSERV_DIR if this variable is defined
including wildcard characters, to determine if it names v The current working directory of the server process if
the license certificate file(s) you intended to use. If an the DSMSERV_DIR variable is not defined
specification. If an error cannot be found, contact your If an error is found, re-try the command with the
service representative. corrected specification. If an error cannot be found,
ANR9631E (Windows) Cannot access node license

lock file: file name. ANR9634E (HP-UX) command name: No license
certificate files were found with the file
Explanation: The server was not able to access the name specification specification.
specified file. The node lock file contains licensing
information for the server. Explanation: The server did not find any license
certificate file(s) with the file name specification
System action: The license function fails. entered.
User response: Examine the file specification System action: The license registration command fails.
ANR9634E (Linux) ANR9636E (HP-UX)
User response: Examine the file specification entered, System action: The license registration command
including wildcard characters, to determine if it names ignores the contents of the file.
ANR9634E (Linux) command name: No license service representative.
name specification specification.
ANR9635E (Linux) Invalid license certificate file: file
Explanation: The server did not find any license name.
entered.
license certificate information.
User response: Examine the file specification entered, ignores the contents of the file.
ANR9634E (Solaris) command name: No license
ANR9635E (Solaris) Invalid license certificate file: file
name.
Explanation: The server did not find any license
entered.
ANR9634E (Windows) command name: No license

ANR9635E (Windows) Invalid license certificate file:
file name.
Explanation: The server did not find any license
entered. System action: The license registration command
ANR9636E (HP-UX) Could not open file file name.

ANR9635E (HP-UX) Invalid license certificate file:
file name. Explanation: The server could not open the license
license certificate information. System action: The license registration command fails.

ANR9636E (Linux) ANR9637E (Windows)
User response: Examine the file specification entered, environment variable if this specification is in error.
including wildcard characters, to determine if it names Also ensure that there is sufficient space on the drive
the license certificate file(s) you intended to use. If an specified for the file. If the problem persists after these
error is found, re-try the command with the corrected corrections have been made, contact your service
specification. If an error cannot be found, contact your representative.
ANR9637E (Linux) Cannot access node license lock
ANR9636E (Linux) Could not open file file name. file: file name.
Explanation: The server could not open the license Explanation: The server was not able to access the
certificate file specified. specified file. The node lock file contains licensing
information for the server.
System action: The license function fails.
including wildcard characters, to determine if it names User response: Examine the file specification
the license certificate file(s) you intended to use. If an displayed and ensure that the file attributes will allow
error is found, re-try the command with the corrected the server to access the file. The location of the file is
specification. If an error cannot be found, contact your either in the directory from which the server is started,
service representative. or in the directory specified by the DSMSERV_DIR
environment variable. Re-specify the DSMSERV-DIR
ANR9636E (Solaris) Could not open file file name.
Explanation: The server could not open the license specified for the file. If the problem persists after these
certificate file specified. corrections have been made, contact your service
representative.
User response: Examine the file specification entered, ANR9637E (Solaris) Cannot access node license lock
including wildcard characters, to determine if it names file: file name.
error is found, re-try the command with the corrected 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.
ANR9636E (Windows) Could not open file file name.
User response: Examine the file specification
Explanation: The server could not open the license displayed and ensure that the file attributes will allow
certificate file specified. 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. or in the directory specified by the DSMSERV_DIR
User response: Examine the file specification entered, environment variable. Re-specify the DSMSERV-DIR
including wildcard characters, to determine if it names environment variable if this specification is in error.
the license certificate file(s) you intended to use. If an Also ensure that there is sufficient space on the drive
error is found, re-try the command with the corrected specified for the file. If the problem persists after these
specification. If an error cannot be found, contact your corrections have been made, contact your service
service representative. representative.
ANR9637E (HP-UX) Cannot access node license lock ANR9637E (Windows) Cannot access node license
file: file name. lock file: file name.
Explanation: The server was not able to access the Explanation: The server was not able to access the
specified file. The node lock file contains licensing specified file. The node lock file contains licensing
information for the server. information for the server.
System action: The license function fails. System action: The license function fails.
User response: Examine the file specification User response: Examine the file specification
displayed and ensure that the file attributes will allow displayed and ensure that the file attributes will allow
the server to access the file. The location of the file is the server to access the file. The location of the file is
either in the directory from which the server is started, either in the directory from which the server is started,
or in the directory specified by the DSMSERV_DIR or in the directory specified by the DSMSERV_DIR
environment variable. Re-specify the DSMSERV_DIR environment variable. Re-specify the DSMSER-DIR
ANR9638W (HP-UX) ANR9639W (Solaris)

ANR9638W (Windows) License registration is not
representative. Explanation: The REGISTER LICENSE command fails
because the license authorization module cannot be
found.
ANR9638W (HP-UX) License registration is not
supported on this server. System action: Server operation continues; licensing
command.
because the license authorization module cannot be
found. User response: The license authorization file is
required for formal licensing for the Windows server.
The file is delivered when the product is purchased,
but it is not available in the product service stream or
command.
with demonstration copies of the server. If you have
User response: The license authorization file is purchased the server, contact your service
required for formal licensing for the HP-UX server. The representative for assistance in resolving this problem.
file is delivered when the server is purchased, but it is
not available in the product service stream or with
ANR9639W (HP-UX) Unable to load shared library
demonstration copies of the server. If you have
shared library.
purchased the server, contact your service
representative for assistance in resolving this problem. Explanation: The server module is unable to load the
indicated shared library.
ANR9638W (Linux) License registration is not System action: Server operation continues, but the
supported on this server. function that requires the shared library will be
inoperative.
because the license authorization module cannot be User response: Ensure that the shared library is
found. 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 with purchased
servers. The server licensing will assume "Try and Buy"
command.
mode with sample licensed options for a period of
User response: The license authorization file is time.
required for formal licensing for the server. The file is
delivered when the product is purchased, but it is not
ANR9639W (Linux) Unable to load Shared License
available in the product service stream or with
File shared library.
purchased the server, contact your service Explanation: The server was unable to loaded the
representative for assistance in resolving this problem. shared library.
ANR9638W (Solaris) License registration is not functions that require the shared library will be
supported on this server. inoperative.
Explanation: The REGISTER LICENSE command fails User response: Make sure the shared library is
because the license authorization module cannot be accessible/readable. This message is normal for those
found. servers in the Try-N-Buy mode.
terms are not changed by the REGISTER LICENSE ANR9639W (Solaris) Unable to load Shared License
command. File shared library.
User response: The license authorization file is Explanation: The server was unable to loaded the
required for formal licensing for the Sun Solaris server. shared library.
The file is delivered when the server is purchased, but
it is not available in the product service stream or with
functions that require the shared library will be
inoperative.
purchased the server, contact your service
representative for assistance in resolving this problem. User response: Make sure the shared library is
accessible/readable. This message is normal for those
servers in the Try and Buy mode.

re-registering the proper licenses. If this message

ANR9640E (HP-UX) Unable to load procedure
address from shared library shared
library.
ANR9641W (Linux) One or more EVALUATION
Explanation: The server module is unable to load the
LICENSES will expire on expiration date.
address of a routine in the indicated shared library.
function that requires the shared library will be User response: Halt the server and erase the nodelock
inoperative. file in the server startup directory. After restarting the
server, use the REGISTER LICENSE command to define
User response: Ensure that the shared library is
the licensed features that you have purchased with
accessible. If the problem persists, contact your service
your server. These licenses should NOT have an
representative.
expiration date, so this message should not appear after
re-registering the proper licenses. If this message
ANR9640E (Linux) Unable to load procedure address persists, contact your service representative.
from shared library shared library license
module.
ANR9641W (Solaris) One or more EVALUATION
Explanation: The server module is unable to load the LICENSES will expire on expiration date.
address of a routine in the indicated shared library for
license loading.
User response: Halt the server and erase the nodelock
file in the server startup directory. After restarting the
function that requires the shared library will be
inoperative.
User response: Ensure that the shared library is your server. These licenses should NOT have an
accessible. If the problem persists, contact your expiration date, so this message should not appear after
Customer Service Representative. re-registering the proper licenses. If this message
ANR9640E (Solaris) Unable to load procedure
address from shared library shared library ANR9642E (HP-UX) The specified license
license module. authorization code (license authorization
code) is invalid.
address of a routine in the indicated shared library for Explanation: The license authorization code which
license loading. you entered using the REGISTER LICENSE command is
invalid.
function that requires the shared library will be System action: No additional licenses are registered.
inoperative. Server operation continues.
User response: Ensure that the shared library is User response: Obtain a valid license authorization
accessible. If the problem persists, contact your code and try the command again.
customer service representative.
ANR9642E (Linux) The specified license
ANR9641W (HP-UX) One or more EVALUATION authorization code (license authorization
LICENSES will expire on expiration date. code) is invalid.
Explanation: Although you are running with a Explanation: The license authorization code which
purchased version of the server, there are one or more you entered using the REGISTER LICENSE command is
licenses registered that will expire on the date specified. invalid.
This is usually the case when you have been using
System action: No additional licenses are registered.
evaluation licenses prior to purchasing the product.
Server operation continues.
User response: Obtain a valid license authorization
User response: Halt the server and erase the nodelock code and try the command again.
file in the server startup directory. After restarting the
your server. These licenses should NOT have an
expiration date, so this message should not appear after

ANR9653E (HP-UX) Unexpected error encountered in
iFor/LS (SystemView License Use
name status=xreported status code.
ANR9655E (HP-UX) Invalid license certificate file:
file name.
Management function specified. Explanation: The specified file does not contain valid
System action: The server license monitoring
operation fails System action: The license registration command
User response: The SystemView License Use
Management product is installed during normal AIX User response: Examine the file specification entered,
server installation. Check to make sure that server was including wildcard characters, to determine if it names
installed correctly. If the installation was successful, the license certificate file(s) you intended to use. If an
re-boot your AIX system and re-start the server. If this error is found, re-try the command with the corrected
message continues to be issued, contact your service specification. If an error cannot be found, contact your
representative. service representative.
ANR9653E (Solaris) Unexpected error encountered in ANR9655E (Solaris) Invalid license certificate file: file
iFor/LS (SystemView License Use name.
name status=xreported status code. Explanation: The specified file does not contain valid
error in accessing the SystemView License Use System action: The license registration command
Management function specified. ignores the contents of the file.
System action: The server license monitoring User response: Examine the file specification entered,
operation fails including wildcard characters, to determine if it names
User response: The SystemView License Use error is found, re-try the command with the corrected
Management product is installed during normal AIX specification. If an error cannot be found, contact your
server installation. Check to make sure that server was service representative.
re-boot your AIX system and re-start the server. If this
message continues to be issued, contact your service ANR9656E (HP-UX) Cannot access node license lock
representative. file: file name.
Explanation: The server was not able to access the
ANR9654E (HP-UX) Could not open file file name. specified file. The node lock file contains licensing
information for the server.
Explanation: The server could not open the license
certificate file specified. System action: The license function fails.
System action: The license registration command fails. User response: Examine the file specification
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 DSMSERV_DIR
specification. If an error cannot be found, contact your environment variable if this specification is in error.
service representative. Also ensure that there is sufficient space on the drive
ANR9654E (Solaris) Could not open file file name.
representative.
Explanation: The server could not open the license
ANR9656E (Solaris) Cannot access node license lock
System action: The license registration command fails. file: file name.
User response: Examine the file specification entered, Explanation: The server was not able to access the
including wildcard characters, to determine if it names specified file. The node lock file contains licensing
the license certificate file(s) you intended to use. If an information for the server.

ANR9676E (AIX) ANR9678E (HP-UX)
System action: The license function fails. shmat subroutine and determine what the error
number indicates. On AIX, if the error number is
User response: Examine the file specification
EMFILE, make sure the EXTSHM environment variable
displayed and ensure that the file attributes will allow
is set to ON before starting the server. This allows the
the server to access the file. The location of the file is
server to support more than 3 concurrent shared
either in the directory from which the server is started,
memory sessions.
or in the directory specified by the DSMSERV_DIR
environment variable. Re-specify the DSMSERV_DIR
environment variable if this specification is in error. ANR9677E (AIX) Failed to allocate memory for
Also ensure that there is sufficient space on the drive shared memory communications. Error:
specified for the file. If the problem persists after these error text.
representative.
to get memory for the shared communications option.
ANR9676E (AIX) Error errno attaching memory
not be activated.
segment for shared memory
communications.
ANR9677E (HP-UX) Failed to allocate memory for
Explanation: An error occurred while attempting to
shared memory communications. Error:
attach a shared memory segment for a shared
error text.
communications session.
System action: The shared memory communications
session does not initialize.
User response: Check the AIX documentation for the
not be activated.
shmat subroutine and determine what the error
number indicates. On AIX, if the error number is User response: None.
is set to ON before starting the server. This allows the
server to support more than 3 concurrent shared ANR9677E (Linux) Failed to allocate memory for
memory sessions. shared memory communications. Error:
error text.
ANR9676E (HP-UX) Error errno attaching memory Explanation: An error has occurred when attempting
segment for shared memory to get memory for the shared communications option.
communications. System action: Shared memory communications will
Explanation: An error occurred while attempting to not be activated.
attach a shared memory segment for a shared User response: None.
communications session.
System action: The shared memory communications ANR9678E (AIX) Failed to allocate message queue
session does not initialize. for the shared memory communications
User response: Check the AIX documentation for the Error: error text.
shmat subroutine and determine what the error Explanation: An error has occurred when attempting
number indicates. On AIX, if the error number is to get memory for the shared communications option.
is set to ON before starting the server. This allows the System action: Shared memory communications will
server to support more than 3 concurrent shared not be activated.
memory sessions.
ANR9678E (HP-UX) Failed to allocate message queue
ANR9676E (Linux) Error errno attaching memory for the shared memory communications
segment for shared memory Error: error text.
communications. Explanation: An error has occurred when attempting
Explanation: An error occurred while attempting to to get memory for the shared communications option.
attach a shared memory segment for a shared System action: Shared memory communications will
communications session. not be activated.
System action: The shared memory communications User response: None.
session does not initialize.
User response: Check the AIX documentation for the
ANR9678E (Linux) ANR9681W (AIX)
another error message which contains the ODM error

ANR9678E (Linux) Failed to allocate message queue
code.
for the shared memory communications
Error: error text.
ANR9680W (HP-UX) Command: Could not obtain
logical volume information for volume
name while building stanza recovery plan
System action: Shared memory communications will stanza name.
not be activated.
User response: None. PREPARE can not obtain logical volume information
for it.
ANR9678W (Windows) File name used for server System action: The entry for the volume is not
executable. A server is currently running included in the recovery plan stanza.
as a service.
User response: This message should be preceded by
Explanation: The name of the executable used when another error message which contains an error code.
the server is running as a service cannot be used in the
plan file.
ANR9680W (Solaris) Command: Could not obtain
System action: PREPARE uses file name identified in logical volume information for volume
the message within the plan file and generation of the name while building stanza recovery plan
plan file continues. stanza name.
User response: None. Explanation: This volume is defined to the server but
PREPARE can not obtain logical volume information
for it.
ANR9679W (AIX) Command: The file file name cannot
be found. System action: The entry for the volume is not
included in the recovery plan stanza.
Explanation: The specified file cannot be found.
System action: For the default server executable file,
another error message which contains an error code.
the PREPARE command uses /opt/IBMadsm-s/bin/
dsmserv.
ANR9680W (Windows) Unable to locate path for
User response: Determine why the file does not exist
component in registry.
and create it if necessary.
Explanation: The path to the component could not be
found in the registry.
ANR9679W (Windows) Command: Unable to locate
file file name. System action: PREPARE uses the following default
path names in the plan file:
Explanation: The specified file cannot be found.
v For the components installation directory the default
System action: PREPARE uses the following default is c:\progra~1\tivoli\tsm\server\
file names in the plan file:
v For the administrative command line client the
v For the server executable the default is default is c:\progra~1\tivoli\tsm\baclient\
c:\progra~1\tivoli\tsm\server\dsmserv.
v For the disk formatting utility the default is
User response: Determine why file does not exist; c:\progra~1\tivoli\tsm\utils\
create if necessary.
User response: Determine why path does not exist;
install components if necessary.
ANR9680W (AIX) Command: Could not obtain AIX
logical volume information for volume
ANR9681W (AIX) Command: Volume file name not
name while building stanza recovery plan
found while building stanza recovery
stanza name.
plan stanza name.
PREPARE can not obtain AIX logical volume
does not exist. The device class associated with the
information for it from the AIX Object Data Manager
(ODM).
System action: The entry for the volume is not
User response: Determine why the file does not exist;
create it if necessary.

ANR9681W (Windows) ANR9685E (Windows)
ANR9681W (Windows) Command: Volume file name ANR9683E (Windows) Command: Cannot generate
not found while building stanza recovery fully qualified file name for 'name'.
plan stanza name.
Explanation: This volume is defined to the server but specified file name.
does not exist. The device class associated with the
specify the prefix:
User response: Determine why file does not exist; v SET DRMPLANPREFIX
create if necessary.
v PREPARE
ANR9682E (AIX) Command: Generated file name too
long. Length of directory or prefix
'prefix' plus 'name' exceeds maximum ANR9684E (AIX) Command: Cannot generate server
characters characters. options file name.
Explanation: The file name generated is too long. The Explanation: A failure occurred generating the server
maximum valid length is shown in the message. options file name.
System action: The recovery plan file was 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 ANR9684E (Windows) Command: Cannot generate
v SET DRMINSTRPREFIX server options file name.
v PREPARE Explanation: A failure occurred generating the server
options file name.
ANR9682E (Windows) Command: Generated file System action: Recovery plan file not created.
name too long. Length of directory or
prefix 'prefix' plus 'name' exceeds User response: See accompanying messages for more
maximum characters characters. information.
Explanation: The file name generated is too long. The

maximum valid length is shown in the message. ANR9685E (AIX) Command: Cannot generate a
Explanation: A failure occurred generating the volume
User response: Reissue the command specifying a history file name.
specify the prefix: System action: Recovery plan file not created.
v SET DRMPLANPREFIX User response: See accompanying messages for more

v SET DRMINSTRPREFIX information.
v PREPARE
ANR9685E (Windows) Command: Cannot generate a
ANR9683E (AIX) Command: Cannot generate fully
qualified file name for 'name'. Explanation: A failure occurred generating the volume
history file name.
specified file name. System action: Recovery plan file not created.
System action: Recovery plan file not created. User response: See accompanying messages for more
information.
specify the prefix:
v SET DRMPLANPREFIX
v PREPARE
ANR9686E (AIX) ANR9774W
ANR9686E (AIX) Command: Cannot generate a device ANR9758W Error mounting volume 'volume name'.
Explanation: An error occurs while mounting the
Explanation: A failure occurred generating the device volume to the drive. This may not be an error since the
configuration file name. volume or drive maybe in use or locked in a shared
environment.
System action: The specified volume is bypassed for
labeling.
information.
User response: Ensure that the volume is not locked
or in use if label is required.
ANR9686E (Windows) Command: Cannot generate a
device configuration file name.
ANR9761E The path of drive drive name in library
Explanation: A failure occurred generating the device
library name has been changed from
original drive path to new drive path The
System action: Recovery plan file not created. new path will not be updated because
we can not get the model type using
User response: See accompanying messages for more new path.
information.
Explanation: The drive's new path can not be updated
because we detect a different device type compared to
ANR9687W (Windows) Cannot load the Microsoft the Database using this new path. The problem may be
dll NTMSAPI.DLL. Removable Media the new path has an incorrect format for the device
Support will not be available. driver.
Explanation: The Microsoft dll NTMSAPI.DLL is System action: .
required for removable media. It is usually found in the
Windows System32 directory but can be removed if the User response: The user needs to check if there are
Windows feature called Removable Media is turned off. two device special file names for the same drive. For
In Windows 2008, Removable Media is off by default. AIX, please make sure the IBM drive is /dev/rmt and
TSM drive is /dev/mt. For Solaris, please make sure
System action: Processing continues. the Solaris native device driver is not installed.
User response: Ignore this message if storing to a
drive or turn on the Removable Media feature in ANR9771E Volume volume name has an incorrect
Windows. barcode label describing the volume's
WORM type.
ANR9751E The volume in drive 'drive name' is not Explanation: In an attempt to CHECKIN or LABEL a
compatible with the drive. volume it was discovered that the volume's true
Explanation: The volume cannot be used in the drive. WORM characteristic didn't match that described by its
It is most likely an outdated media type that the drive barcode label.
cannot write. System action: The volume is not checked in.
System action: The volume is not labeled. User response: The volume was probably mislabeled.
User response: Remove the volume; replace it with a Find the volume in the library. Simply remove the
different type known to work in the drive, or press volume, or swap the barcode label with a label of the
ENTER to end the program. opposite WORM characteristic (WORM for non-WORM
or vice versa) and retry the check in command.
ANR9756I No volumes were found.

ANR9774W Volume volume name should be freed of
Explanation: No volumes are found in the library. data as soon as possible.
This means that in a 349x ATL, no volumes were found
in the insert category (xFF00), and that in a SCSI Explanation: The server has received an indication
autochanger, no cartridges were loaded into the library. from the 3995 that the indicated volume is out of spare
sectors for re-allocation. Spare sectors are reserved to
System action: The program terminates normally. take the place of sectors that experience I/O problems.
User response: Insert cartridges into the library. For a The re-allocation can take place on either a read or
349x ATL, this may involve changing the category of write.
previously inserted cartridges to be relabeled. System action: The indicated volume is marked
read-only by the server.

ANR9775E ANR9783E
User response: A MOVE DATA command should be v A communication error occurred during the request
used as soon as possible to move the data from this to mount a volume.
cartridge to other cartridges in the library. This v The requested volume was not present in the library
cartridge should NOT be marked read-write again manager's inventory
through the UPDATE VOLUME command.
ANR9775E Error while writing on volume volume User response: Verify that a drive is available on the
name (RC=internal code). library manager side and the drive is currently not
busy or marked offline on the library client. Set the
Explanation: An I/O error has occurred while writing mount retention on the device class on the library
on the specified volume. manager and the library clients to a lower value. Using
System action: The operation fails. a lower mount retention value can free up drives.
User response: Ensure that the 3995 volume is

accessible and that the media is usable. Diagnostics ANR9780E Volume volume name is not mounted in
may have to be run on the 3995 with the specified drive from the library drive name.
volume. If the problem persists, contact your service Explanation: A communication error occurred while
representative and provide the internal code values dismount the volume.
from this message. The internal code is returned to the
server from the OS/2 operating system. System action: None.
User response: Verify the library manager is up and
ANR9776I File file name is being erased and operational. Verify that the library manager and library
deleted. Data erasure may take several client can communicate using command routing.
minutes.
Explanation: A file is being deleted from an optical ANR9781E Volser volume name was not found to be
library cartridge. The file is deleted when a LAN3995 mounted on the library manager.
device class volume is deleted. File deletion includes Explanation: According to the library manager the
erasure of data. The erasure process can take several requested volume is no longer mounted. The can
minutes to complete. occurred if the library manager forced the volume to be
System action: The operation continues. dismounted because of a communication error.

User response: Verify that the volume has been
ANR9778E Unable to establish a communication dismounted.
session with the primary library
manager. ANR9782E Primary Library Manager primary library
Explanation: The requested operation required that a manager name is NOT defined as a
communication session be established with a library server.
manager. The library manager was found to be Explanation: The primary library manager server has
unavailable at this time. not be defined to this server.
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. System action: None.
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
marked offline or is currently busy with another
process.
ANR9784E ANR9793I
because the secondary library manager is not defined

ANR9784E Secondary Library Manager secondary
as a server to this server.
library manager name is NOT defined as a
server. System action: The command is not processed.
Explanation: The secondary library manager server User response: Define the server to this server using
name has not be defined to this server. the DEFINE SERVER command.
ANR9790W Request to mount volume Volume Name
User response: Define the server to this server using
for library client Library Client Name
the DEFINE SERVER command.
failed.
Explanation: A library client requested a volume to be
ANR9785E Drive drive name, is not defined on the
mount by the library manager, which in turn failed.
library manager.
Explanation: A drive is being defined that does not
exist or is being managed by the library manager. User response: Verify the status of all drives are
currently online and not in use by other library clients
or the library manager itself. Free up drive resources as
User response: Verify drive name with the library needed.
manager.
ANR9791I Volume Volume Name in library Library
ANR9786E A communication error has occurred. Name ownership is changing from
Operation ending. Current volume owner to New Volume
owner.
Explanation: A communication error occurred.
Explanation: In a shared library, the volume
ownership has been changed from current owner to
User response: Verify the library manager is up and new owner.
operational. Verify that the library manager and library
client can communicate using command routing.
ANR9787E The owner name specified is not
defined to this server. ANR9792E Library Library Name on library manager
Library Manager Name is currently not
Explanation: A command was issued specifying
being shared.
ownership of a volume. The name of the owner given
was not defined to this server. Explanation: A define library command attempted to
define a shared library that was not being shared by
the library manager.
User response: Define the server to this server using
User response: Verify the library on the library
manager is being shared. If the library is not being
shared, update the library shared status to yes.
defined - the primary library manager
not defined.
ANR9793I process name in library library name-
Explanation: The designated library is not defined
CANCEL PENDING.
because the primary library manager is not defined as a
server to this server. Explanation: In response to a QUERY PROCESS
process on the server. The command was started, but
User response: Define the server to this server using the process was canceled by an administrator.
being terminated.
defined - the secondary library manager
not defined.
Explanation: The designated library is not defined

ANR9794E ANR9810I (Windows)
User response: Delete all paths for the drive, and

ANR9794E Unable to load the RSM dynamic link
library dynamic link library.
ANR9799E Command: Library Library Name is
indicated dynamic link library.
currently not being shared.
Explanation: The command attempted to perform an
function that requires the dynamic link library will be
operation that is not allowed unless the library is
inoperative.
allowed to be shared.
User response: Ensure that the installed Windows
version supports RSM. Ensure that the Removable
Storage Manager is installed and the system DLL is User response: Verify the library on the library
accessible. manager is being shared. If the library is not being
shared, update the library shared parameter to yes.
ANR9795E Command: Invalid storage agent name
storage agent name. ANR9800E Library Library Name is currently not
being shared and attempted an
Explanation: The designated storage agent name is
operation only allowed for shared
invalid; either it contains too many characters, or some
libraries.
of the characters are invalid.
Explanation: The command attempted to perform an
operation that is not allowed unless the library is
User response: Reissue the command using a valid allowed to be shared.
storage agent name.
User response: Verify the library on the library
ANR9796E Command: Drive mapping is already
manager is being shared. If the library is not being
defined for drive drive name in library
shared, update the library shared parameter to yes.
library name on storage agent storage agent
name.
ANR9801I (Windows) ANR9801: Ready for
Explanation: The designated drive mapping cannot be
operations.
defined because it has already been defined for the
specified drive, library, and storage agent. Explanation: The device driver has successfully
initialized and is ready to accept requests from the
server.
drive mapping, reissue the command with a different
drive name. User response: None.
ANR9797E Command: Drive mapping for drive drive ANR9803W (Windows) ANR9803: ERROR!
name is not defined in library library Insufficient free memory to initialize
name on storage agent storage agent name. driver.
Explanation: The designated drive map has not been Explanation: The server device driver is unable to
defined for the given drive in the given library on the initialize due to an inability to acquire dynamic storage.
given storage agent.
System action: Processing continues. The device
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.
ANR9820I (Windows) ANR9901W (Solaris)

ANR9900W (Windows) Attention -- Accounting
records could not be written to the file:
ANR9820I (Windows) ANR9820: SCSI Autochanger filespec.
Device Driver Initializing...
Explanation: The server detects an error while trying
Explanation: The server SCSI automatic changer to open the accounting file.
device driver has been invoked by the system and is
initializing.
User response: Ensure that there is sufficient disk
space and that the accounting file is not marked as
User response: None. read-only.
ANR9900W (AIX) Attention -- Accounting records ANR9901W (AIX) Attention -- Accounting records
could not be written to the file: filespec. could not be written to the file: filespec.
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. System action: Server processing continues.
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.
ANR9900W (HP-UX) Attention -- Accounting records ANR9901W (HP-UX) Attention -- Accounting records
could not be written to the file: file name. could not be written to the file: file name.
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 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 (Linux) Attention -- Accounting records
ANR9900W (Linux) 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 to write an accounting record.
to open the accounting file.
System action: Server processing continues, but no
User response: Ensure that there is sufficient disk read-only.
read-only.
ANR9901W (Solaris) Attention -- Accounting records
ANR9900W (Solaris) Attention -- Accounting records
to write an accounting record.
to open the accounting file.
System action: Server processing continues, but no
read-only.
read-only.

ANR9901W (Windows) Attention -- Accounting ANR9902W (Windows) Attention -- Accounting

records could not be written to the file: records could not be written to the file:
filespec. filespec.
to write an accounting record. to close the accounting file.
System action: Server processing continues. System action: Server processing continues.
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.
ANR9902W (AIX) Attention -- Accounting records ANR9903W (HP-UX) Create thread failed. Your
could not be written to the file: filespec. system is configured for a maximum of
thread count threads. Consider
configuring a maximum of 1024 threads.
to close the accounting file.
Explanation: The server is unable to create a new
thread.
User response: Ensure that sufficient disk space is
available and that the accounting file is not marked as
read-only. User response: Consider increasing the maximum
thread count on the system.
ANR9902W (HP-UX) Attention -- Accounting records
could not be written to the file: file name. ANR9904W (AIX) Need to run as root for function
function to open the HBA for failover
support.
Explanation: There will be no tape failover support
function since this TSM server does not run as root.
read-only. User response: Ensure to login as root for TSM tape
failver function to open HBA.
ANR9902W (Linux) Attention -- Accounting records
could not be written to the file: file name. ANR9904W (HP-UX) Create thread failed. Try the
operation again later.
to close the accounting file. Explanation: The server is unable to create a new
thread due to resource constraints.
space and that the accounting file is not marked as User response: Try the operation again later.
read-only.
ANR9905W (AIX) Unable to open file file. Error
ANR9902W (Solaris) Attention -- Accounting records message generated by AIX
Explanation: The server detects an error while trying indicated file.
System action: Server processing continues. indicated file fails.
User response: Ensure that there is sufficient disk User response: Determine the reason for being unable
space and that the accounting file is not marked as to open the file and re-attempt the operation. Common
read-only. reasons for being unable to open the file include
owner.
ANR9905W (HP-UX) ANR9953E (Windows)
ANR9905W (HP-UX) Unable to open file file. Error ANR9906E (AIX) The volume named volume name is
message generated by HP-UX. larger than is allowed for a volume on
your system. Maximum allowed size is
allowed size.
indicated file.
Explanation: While attempting to open a volume the
server detected that the volume size exceeds the
indicated file fails.
maximum allowed.
reasons for being unable to open the file include User response: Define multiple smaller volumes.
ANR9950W (Windows) Attention -- License option
owner.
could not be written to the file: filespec.
ANR9905W (Linux) Unable to open file file. Error
to write to the options file.
message generated by Linux.
indicated file. User response: Ensure that there is sufficient disk
space and that the options file is not marked as
read-only.
indicated file fails.
ANR9951W (Windows) Attention -- License option
could not be written to the file: filespec.
providing the wrong name, having insufficient Explanation: The server detects an error while trying
authorization to open the file and not being the file's to close the options file.
owner.
ANR9905W (Solaris) Unable to open file file. Error User response: Ensure that there is sufficient disk
message generated by Solaris. space and that the options file is not marked as
read-only.
indicated file.
ANR9952E (Windows) Command: Invalid value
System action: The operation that was to use the specified for licensed storage capacity -
indicated file fails. value.
User response: Determine the reason for being unable Explanation: The specified command has been issued
to open the file and re-attempt the operation. Common with an invalid value.
providing the wrong name, having insufficient System action: Server operation continues, but the
authorization to open the file and not being the file's command is not processed.
owner. User response: Issue the command using a valid
value.
ANR9905W (Windows) Unable to open file file. Error
message generated by Windows. ANR9953E (Windows) Command: Invalid value
Explanation: The server was unable to open the specified for number of licensed clients
indicated file. - value.
System action: The operation that was to use the Explanation: The specified command has been issued
indicated file fails. with an invalid value.
User response: Determine the reason for being unable System action: Server operation continues, but the
to open the file and re-attempt the operation. Common command is not processed.
reasons for being unable to open the file include User response: Issue the command using a valid
providing the wrong name, having insufficient value.
owner.


ANR9955W (Windows) Unable to load dynamic link
library dynamic link library. User response: None.
indicated dynamic link library. ANR9959W (Windows) Node entry node name was
not removed from this server's
definition in Active Directory.
function that requires the dynamic link library will be
inoperative. Explanation: In response to a REMOVE NODE
command, the requested backup-archive node has not
User response: Ensure that the dynamic link library
been removed from this server's definition in Active
directories are accessible. If this is an evaluation copy
Directory.
of the server, then this message is normal for the
DSMREG library, since the library is only provided System action: None.
with purchased Windows servers. The server licensing
will assume "Try and Buy" mode with sample licensed User response: To remove a node entry in the Active
options for a period of time. Directory, the option "adunregister" has to be set to
"yes" in the server options file. A domain controller
must also be available. The Active Directory
ANR9956E (Windows) Unable to load procedure Configuration wizard can be used to manually update
address from dynamic link library the server definition.
dynamic link library.
Explanation: The server module is unable to load the ANR9960W (Windows) Node entry node name has
address of a routine in the indicated dynamic link been added to this server's definition in
library. Active Directory.
System action: Server operation continues, but the Explanation: The requested backup-archive node entry
function that requires the dynamic link library will be has been added to this server's definition in Active
inoperative. Directory in response to a REGISTER NODE command.
User response: Ensure that the dynamic link library System action: None.
directories are accessible. If the problem persists,
contact you service representative. User response: None.
ANR9957W (Windows) One or more EVALUATION ANR9961W (Windows) Node entry node name has not
LICENSES will expire on expiration date. been added to this server's definition in
Active Directory.
Explanation: Although you are running with a
purchased version of the server, there are one or more Explanation: The requested backup-archive node entry
licenses registered that will expire on the date specified. has not been added to this server's definition in Active
This i usually the case when you have been using Directory in response to a REGISTER NODE command.
evaluation licenses prior to purchasing the server for System action: None.
Windows.
User response: To register a node entry in the Active
System action: Server operation continues. Directory, the option "adregister" has to be set to "yes"
User response: Halt the server and erase the nodelock in the server options file. A domain controller must also
file in the server startup directory. After restarting the be available. The Active Directory Configuration wizard
server, use the REGISTER LICENSE command to define can be used to manually update the server definition.
your Windows server. These licenses should NOT have ANR9962W (Windows) Node entry node name was
an expiration date, so this message should not appear renamed in this server's definition in
after re-registering the proper licenses. If this message Active Directory.
Explanation: In response to a RENAME NODE
command, the requested backup-archive node has been
ANR9958W (Windows) Node entry node name was renamed to the new name shown.
removed from this server's definition in
Active Directory. System action: None.
Explanation: In response to a REMOVE NODE User response: None.

command, the requested backup-archive node has been
removed from this server's definition in Active
Directory.
ANR9963W (Windows) ANR9999D
ANR9963W (Windows) Node entry node name was ANR9968I (Windows) Success accessing Active
not renamed in this server's definition Directory.
in Active Directory.
Explanation: Active Directory Server could be
Explanation: In response to a RENAME NODE contacted.
command, the requested backup-archive node has not
System action:
been renamed.
User response: To Rename Node in the Active
ANR9969E (Windows) Unable to open volume
Directory, the options "adregister" and "adunregister"
volume name. The most likely reason is
have to be set to "yes" in the server options file. A
that another TSM server is running and
domain controller must also be available. The Active
has the volume allocated.
Directory Configuration wizard can be used to
manually update the server definition. Explanation: Only one TSM server can have a given
volume open at a time.
ANR9964W (Windows) Failed to access Active System action: The TSM server does not start.
Directory. RC: return code
User response: See if another TSM server is already
Explanation: Could not communicate with an Active running and if so use it.
Directory server.
System action: Server operation continues. ANR9999D (component)(code):(text)
User response: Try using the option "adsetdc" in the Explanation: The diagnostic text of this message is
server options file to explicitly provide the TCP/IP related to a server process or algorithm. The
address of the domain controller where Active information is intended for reporting processing
Directory is located. exceptions and other non-standard situations that occur
on the server. The (component), (code), and (text) vary,
and server processing may continue, depending upon
ANR9965W (Windows) Could not create the inital
the cause of the message and the server process or
node list in Active Directory for this
algorithm issuing the message.
server.
System action: Issue the SET CONTEXTMESSAGING
Explanation: At startup the server's registered nodes
command and set the message context reporting to ON.
could not be added to the server definition in Active
This allows you to receive additional information when
Directory
the server produces its message. See the Administrators
System action: Server operation continues. Reference for more information.
User response: Try using the option "adsetdc" in the User response: Examine any error messages that were
server options file to explicitly provide the TCP/IP displayed before or after this message and correct any
address of the domain controller where Active problems, if possible. If you cannot determine or
Directory is located. resolve the cause of this message, contact your support
representative. Report the entire text of this message
when contacting your support representative.
ANR9966I (Windows) NodeName node name.
Explanation: The NodeName is registered in Active
Directory.
ANR9967I (Windows) Server server name was defined

in Active Directory.
Explanation: The server is registered in Active
Directory.

Chapter 4. Descriptions of I/O codes in server messages
IBM Tivoli Storage Manager messages can contain I/O (input/output) codes. The
codes can be operation codes, completion codes, ASC and ASCQ codes.
Code descriptions are provided for I/O error messages from the Tivoli Storage
Manager 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 REW (rewind)
v FLUSH (flush)
v GET_MEDIUM_INFO (get medium information)
v LOAD_DISPLAY (load display)
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. See Completion code and operation code
values overview on page 748 for a list of completion codes. See the IBM
TotalStorage Tape Device Drivers Installation and User's Guide for information
about tape library system calls and error descriptions for the library I/O
control requests.
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 = equal compare on SEARCH DATA command
D = volume overflow
E = miscompare
F = reserved
ASC/ASCQ
Additional sense codes (ASC) and additional sense code qualifiers (ASCQ)
are bytes 12 and 13 of the sense bytes. See the sense byte number along
with the value for a complete description of standard ASC and ASCQ
codes. 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 752 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, Solaris, and Linux platforms, view the errno.h file in
the /usr/include/sys directory. This file provides definitions for error
codes.
On Windows platforms, contact Microsoft Support at
http://support.microsoft.com/ for help with error messages.
Completion code and operation code values overview

IBM Tivoli Storage Manager device drivers provide operation codes and
completion codes. Tivoli Storage Manager messages can contain device driver
operation codes and completion codes.
Device drivers completion codes: Common codes

Tivoli Storage Manager device drivers provide completion codes that are common
to all device classes.
The following table shows common completion code values for Tivoli Storage
Manager 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 Tivoli Storage Manager
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.
Table 1. Completion code values common to all device classes (continued)
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.
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 Tivoli Storage Manager
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
Tivoli Storage Manager Support.
Device drivers completion codes: Media changers

Tivoli Storage Manager device drivers provide completion codes that are specific to
media changer devices.
The following table shows completion code values for Tivoli Storage Manager
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.
Chapter 4. I/O code descriptions in server messages 749

Table 2. Completion code values for media changers (continued)
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.
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 Contact Tivoli Storage Manager
Support.
308 X'134' Entry/exit port not present Contact Tivoli Storage Manager
Support.
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 Contact Tivoli Storage Manager
Support.
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
the AUDIT LIBRARY command.
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
the AUDIT LIBRARY command.
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 Tivoli Storage Manager
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 Tivoli Storage Manager
Support.
Table 2. Completion code values for media changers (continued)
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.
321 X'141' Read element status mismatch Contact Tivoli Storage Manager
Support.
322 X'142' Initialize range failed Contact Tivoli Storage Manager
Support.
Device drivers completion codes: Tape drives

Tivoli Storage Manager device drivers provide completion codes that are specific to
tape drives.
The following table shows completion code values for Tivoli Storage Manager
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 Tivoli Storage Manager
Support.
402 X'192' Media corrupted Ensure that the heads are clean and the
media is not physically damaged or too
old.
403 X'193' Media failure Ensure that the heads are clean and the
old.
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. ContactTivoli
Storage Manager 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 that is not too old.
409 X'199' Media fault Clean the heads and ensure that the
old.
410 X'19A' Cleaning complete Try the failing operation again.
411 X'19B' Logical end of media encountered ContactTivoli Storage Manager Support.
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 ContactTivoli Storage Manager Support.

Table 3. Completion code values for tape drives (continued)
414 X'19E' Erase failure Clean the drive heads.
415 X'19F' Attempted to overwrite written WORM Internal server error. ContactTivoli
media Storage Manager 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 ContactTivoli Storage Manager Support.
418 X'1A2' Open write only ContactTivoli Storage Manager 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.
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 and tape drive.
426 X'1AB' A CRC mismatch occurred Try the operation again.
Descriptions of standard ASC and ASCQ codes

Standard ASC and ASCQ codes are described.
This section provides descriptions of standard ASC (Additional Sense Code) and
ASCQ (Additional Sense Code Qualifier) codes. 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
Table 4. Descriptions of standard ASC and ASCQ codes (continued)
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
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
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 Windows Event Log

ASC and ASCQ codes are displayed in the Windows Event Log.
The ASC (Additional Sense Code) and ASCQ (Additional Sense Code Qualifier)
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
Tivoli Storage Manager AdsmScsi device driver. Entries from the AdsmScsi device
driver or any Windows tape device driver contains the following information. Byte
3E is the sense key, byte 3D is the ASC, and 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
Tivoli Storage Manager logs some device errors in the AIX system error log.
Device codes in the AIX system error log are described.

DEVICE ERROR and ERROR DESCRIPTION
ADSM_DD_LOG1 (0xAC3AB953)
DEVICE DRIVER SOFTWARE ERROR
This error is logged by the Tivoli Storage Manager device driver when a
problem is suspected in theTivoli Storage Manager device driver software.
If the Tivoli Storage Manager 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 Tivoli Storage
Manager 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 Tivoli Storage Manager Support.
ADSM_DD_LOG2 (0x5680E405)
HARDWARE/COMMAND-ABORTED ERROR
This error is logged by the Tivoli Storage Manager 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 Tivoli Storage Manager 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 Tivoli Storage Manager 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 Tivoli Storage Manager support
personnel.
The sense data consists of information that can determine the cause of the
error. Report all data in the error entry to Tivoli Storage Manager 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 Tivoli Storage
Manager Suppport.
The sense data consists of information that can determine the reason for
the message. Report all data in the entry to Tivoli Storage Manager
Support.
Appendix A. Tivoli support information
You can find support information for Tivoli and other IBM products from various
sources.
From the IBM Support Portal at http://www.ibm.com/support/entry/portal/, you

can select the products that you are interested in and search for a wide variety of
relevant information.
Communities and other learning resources

In addition to product documentation, many forms of assistance are available to
help you get started as you deploy and use the Tivoli Storage Manager family of
products. These resources can also help you to solve problems that you might
have.
You can use forums, wikis, and other social media tools to ask questions, talk to
experts, and learn from others.
User groups
Tivoli Global Storage Virtual User Group
Access this user group at http://www.tivoli-ug.org/storage.
This group makes it possible for individuals from many different industries
and types of organizations to share information and work directly with the
IBM product experts. Local chapters also exist where members meet in
person to share experiences and hear from guest speakers.
ADSM.ORG
Access this mailing list at http://adsm.org.
This independently managed Storage Management discussion forum
started when Tivoli Storage Manager was known as ADSTAR Distributed
Storage Manager (ADSM). The members of this forum have many years of
experience with Tivoli Storage Manager in almost every type of IT
environment.
To subscribe to the forum, send an email to listserv@vm.marist.edu. The
body of the message must contain the following text: SUBSCRIBE ADSM-L
your_first_name your_family_name.
Tivoli Storage Manager community on Service Management

Connect
Access Service Management Connect at http://www.ibm.com/developerworks/

servicemanagement. In the Storage Management community of Service
Management Connect, you can connect with IBM in the following ways:
v Become involved with transparent development, an ongoing, open engagement
between users and IBM developers of Tivoli products. You can access early
designs, sprint demonstrations, product roadmaps, and prerelease code.
v Connect one-on-one with the experts to collaborate and network about Tivoli
and the Tivoli Storage Manager community.
v Read blogs to benefit from the expertise and experience of others.

v Use wikis and forums to collaborate with the broader user community.
Tivoli Storage Manager wiki on developerWorks
Access this wiki at https://www.ibm.com/developerworks/servicemanagement/

sm/index.html.
Find the latest best practices, white papers, and links to videos and other
resources. When you log on, you can comment on content, or contribute your own
content.
Tivoli Support Technical Exchange
Find information about upcoming Tivoli Support Technical Exchange webcasts at

http://www.ibm.com/software/sysmgmt/products/support/supp_tech_exch.html.
Replays of previous webcasts are also available.
Learn from technical experts who share their knowledge and then answer your
questions. The sessions are designed to address specific technical issues and
provide in-depth but narrowly focused training.
Other social media sites

LinkedIn
You can join groups on LinkedIn, a social media site for professionals. For
example:
v Tivoli Storage Manager Professionals: http://www.linkedin.com/
groups/Tivoli-Storage-Manager-Professionals-54572
v TSM: http://www.linkedin.com/groups?gid=64540
Twitter
Follow @IBMStorage on Twitter to see the latest news about storage and
storage software from IBM.
Tivoli education resources
Use these education resources to help you increase your Tivoli Storage Manager
skills:
Tivoli Education and Certification website
View available education at http://www.ibm.com/software/tivoli/
education.
Use the Search for Training link to find local and online offerings of
instructor-led courses for Tivoli Storage Manager.
Education Assistant
Access resources at http://publib.boulder.ibm.com/infocenter/ieduasst/
tivv1r0/index.jsp.
Scroll to view the list of available training videos. Recorded product
demonstrations are also available on a YouTube channel.
Searching knowledge bases
If a problem occurs while you are using one of the Tivoli Storage Manager family
of products, you can search several knowledge bases.
Begin by searching the Tivoli Storage Manager Information Center at

http://pic.dhe.ibm.com/infocenter/tsminfo/v7r1. Within the information center,
you can enter words, phrases, or message numbers in the Search field to find
relevant topics.
Searching the Internet

If you cannot find an answer to your question in the Tivoli Storage Manager
information center, search the Internet for the information that might help you
resolve the problem.
To search multiple Internet resources, go to the IBM support website at

http://www.ibm.com/support/entry/portal/. You can search for information
without signing in.
Sign in using your IBM ID and password if you want to customize the site based
on your product usage and information needs. If you do not already have an IBM
ID and password, click Sign in at the top of the page and follow the instructions
to register.
From the support website, you can search various resources:

v IBM technotes.
v IBM downloads.
v IBM Redbooks publications.
v IBM Authorized Program Analysis Reports (APARs). Select the product and click
Downloads to search the APAR list.
Using IBM Support Assistant

IBM Support Assistant is a complimentary software product that can help you with
problem determination. It is available for some Tivoli Storage Manager and Tivoli
Storage FlashCopy Manager products.
IBM Support Assistant helps you gather support information when you must open
a problem management record (PMR), which you can then use to track the
problem. The product-specific plug-in modules provide you with the following
resources:
v Support links
v Education links
v Ability to submit problem management reports
You can find more information and download the IBM Support Assistant web page
at http://www.ibm.com/software/support/isa.
You can also install the stand-alone IBM Support Assistant application on any
workstation. You can then enhance the application by installing product-specific
plug-in modules for the IBM products that you use. Find add-ons for specific
products at http://www.ibm.com/support/docview.wss?uid=swg27012689.
Appendix A. Tivoli support information 761

Finding product fixes
A product fix to resolve a software problem might be available from the IBM
software support website.
Procedure
Determine what fixes are available by checking the IBM software support website
at http://www.ibm.com/support/entry/portal/.
If you previously customized the site based on your product usage:
1. Click the link for the product, or a component for which you want to
find a fix.
2. Click Downloads, and then click Search for recommended fixes.
If you have not previously customized the site:
Click Downloads and search for the product.
Receiving notification of product fixes

You can receive notifications about fixes, flashes, upgrades, and other news about
IBM products.
Procedure
1. From the support page at http://www.ibm.com/support/entry/portal/, click
Sign in and sign in using your IBM ID and password. If you do not have an
ID and password, click register now and complete the registration process.
2. Click Manage all my subscriptions in the Notifications pane.
3. Click the Subscribe tab, and then click Tivoli.
4. Select the products for which you want to receive notifications and click
Continue.
5. Specify your notification preferences and click Submit.
Contacting IBM Software Support

You can contact IBM Software Support if you have an active IBM subscription and
support contract, and if you are authorized to submit problems to IBM.
Procedure
1. Ensure that you have completed the following prerequisites:
a. Set up a subscription and support contract.
b. Determine the business impact of the problem.
c. Describe the problem and gather background information.
2. Follow the instructions in Submitting the problem to IBM Software Support
on page 764.
Setting up and managing support contracts
You can set up and manage your Tivoli support contracts by enrolling in IBM
Passport Advantage. The type of support contract that you need depends on the
type of product you have.
Procedure
Enroll in IBM Passport Advantage in one of the following ways:

v Online: Go to the Passport Advantage website at http://www.ibm.com/
software/lotus/passportadvantage/, click How to enroll, and follow the
instructions.
v By telephone: For critical, system-down, or high-severity issues, you can call
1-800-IBMSERV (1-800-426-7378) in the United States. For the telephone number
to call in your country, go to the IBM Software Support Handbook web page at
http://www14.software.ibm.com/webapp/set2/sas/f/handbook/home.html
and click Contacts.
Determining the business impact

When you report a problem to IBM, you are asked to supply a severity level.
Therefore, you must understand and assess the business impact of the problem
you are reporting.
Severity level Description

Severity 1 Critical business impact: You are unable to use the program,
resulting in a critical impact on operations. This condition
requires an immediate solution.
Severity 2 Significant business impact: The program is usable but is
severely limited.
Severity 3 Some business impact: The program is usable with less
significant features (not critical to operations) unavailable.
Severity 4 Minimal business impact: The problem causes little impact on
operations, or a reasonable circumvention to the problem has
been implemented.
Describing the problem and gathering background information

When explaining a problem to IBM, it is helpful to be as specific as possible.
Include all relevant background information so that IBM Software Support
specialists can help you solve the problem efficiently.
To save time, know the answers to these questions:

v What software versions were you running when the problem occurred?
v Do you have logs, traces, and messages that are related to the problem
symptoms? IBM Software Support is likely to ask for this information.
v Can the problem be re-created? If so, what steps led to the failure?
v Have any changes been made to the system? For example, hardware, operating
system, networking software, and so on.
v Are you using a workaround for this problem? If so, be prepared to explain it
when you report the problem.
Appendix A. Tivoli support information 763

Submitting the problem to IBM Software Support
You can submit the problem to IBM Software Support online or by telephone.
Online
Go to the IBM Software Support website at http://www.ibm.com/
support/entry/portal/Open_service_request/Software/
Software_support_(general). Sign in to access IBM Service Requests and
enter your information into the problem submission tool.
By telephone
For critical, system-down, or severity 1 issues, you can call 1-800-IBMSERV
(1-800-426-7378) in the United States. For the telephone number to call in
your country, go to the IBM Software Support Handbook web page at
http://www14.software.ibm.com/webapp/set2/sas/f/handbook/
home.html and click Contacts.
Appendix B. Accessibility features for the Tivoli Storage
Manager product family
Accessibility features help users who have a disability, such as restricted mobility
or limited vision to use information technology products successfully.
Accessibility features
The IBM Tivoli Storage Manager family of products includes the following
accessibility features:
v Keyboard-only operation using standard operating-system conventions
v Interfaces that support assistive technology such as screen readers
The command-line interfaces of all products in the product family are accessible.
Tivoli Storage Manager Operations Center provides the following additional

accessibility features when you use it with a Mozilla Firefox browser on a
Microsoft Windows system:
v Screen magnifiers and content zooming
v High contrast mode
The Operations Center and the Tivoli Storage Manager Server can be installed in
console mode, which is accessible.
The Tivoli Storage Manager Information Center is enabled for accessibility. For
information center accessibility information, see Accessibility features in the
information center ( http://pic.dhe.ibm.com/infocenter/tsminfo/v7r1/topic/
com.ibm.help.ic.doc/iehs36_accessibility.html).
Vendor software
The Tivoli Storage Manager 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 the accessibility
information about its products.
IBM and accessibility
See the IBM Human Ability and Accessibility Center (http://www.ibm.com/able)

for information about the commitment that IBM has to accessibility.

Notices
This information was developed for products and services offered in the U.S.A.
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
Armonk, NY 10504-1785
U.S.A.
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
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
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 states 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 want 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 Corporation
2Z4A/101
11400 Burnet Road
Austin, TX 78758
U.S.A.
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 information 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.
Any performance data contained herein was determined in a controlled

environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurements may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.
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 is for planning purposes only. The information herein is subject to
change before the products described become available.
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_.
If you are viewing this information in softcopy, the photographs and color
illustrations may not appear.
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 http://www.ibm.com/legal/copytrade.shtml.
Linux is a registered trademark of Linus Torvalds in the United States, other

countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of
Microsoft Corporation in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
JavaTM and all Java-based trademarks and logos are trademarks or

registered trademarks of Oracle and/or its affiliates.
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 offerings 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.
Notices 769
For more information about the use of various technologies, including cookies, for
these purposes, see IBMs Privacy Policy at http://www.ibm.com/privacy and
IBMs Online Privacy Statement at http://www.ibm.com/privacy/details 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
This glossary provides terms and definitions for backup data. See also server storage,
Tivoli Storage Manager, Tivoli Storage FlashCopy storage pool, storage pool volume.
Manager, and associated products.
active file system
A file system to which space management
The following cross-references are used in this
has been added. With space management,
glossary:
tasks for an active file system include
v See refers you from a nonpreferred term to the automatic migration, reconciliation,
preferred term or from an abbreviation to the selective migration, and recall. See also
spelled-out form. inactive file system.
v See also refers you to a related or contrasting
active policy set
term.
The activated policy set that contains the
policy rules currently in use by all client
For other terms and definitions, see the IBM
nodes assigned to the policy domain. See
Terminology website at www.ibm.com/software/
also policy domain, policy set.
globalization/terminology.
active version
The most recent backup copy of a file
A stored. The active version of a file cannot
absolute mode be deleted until a backup process detects
In storage management, a backup that the user has either replaced the file
copy-group mode that specifies that a file with a newer version or has deleted the
is considered for incremental backup even file from the file server or workstation.
if the file has not changed since the last See also backup version, inactive version.
backup. See also mode, modified mode. activity log
access control list (ACL) A log that records normal activity
In computer security, a list associated messages that are generated by the server.
with an object that identifies all the These messages include information about
subjects that can access the object and server and client operations, such as the
their access rights. start time of sessions or device I/O errors.
access mode adaptive subfile backup

An attribute of a storage pool or a storage A type of backup that sends only changed
volume that specifies whether the server portions of a file to the server, instead of
can write to or read from the storage pool sending the entire file. Adaptive subfile
or storage volume. backup reduces network traffic and
increases the speed of the backup.
ACK See acknowledgment.
administrative client
acknowledgment (ACK) A program that runs on a file server,
The transmission of acknowledgment workstation, or mainframe that
characters as a positive response to a data administrators use to control and monitor
transmission. the server. See also backup-archive client.
ACL See access control list. administrative command schedule
activate A database record that describes the
To validate the contents of a policy set planned processing of an administrative
and then make it the active policy set. command during a specific time period.
See also central scheduler, client schedule,
active-data pool schedule.
A named set of storage pool volumes that
contain only active versions of client administrative privilege class
See privilege class.

administrative session node and a client schedule. An association
A period of time during which an identifies the name of a schedule, the
administrator user ID communicates with name of the policy domain to which the
a server to perform administrative tasks. schedule belongs, and the name of a
See also client node session, session. client node that performs scheduled
operations.
administrator
A person responsible for administrative audit To check for logical inconsistencies
tasks such as access authorization and between information that the server has
content management. Administrators can and the actual condition of the system.
also grant levels of authority to users. The storage manager can audit
information about items such as volumes,
agent node
libraries, and licenses. For example, when
A client node that has been granted proxy
a storage manager audits a volume, the
authority to perform operations on behalf
server checks for inconsistencies between
of another client node, which is the target
information about backed-up or archived
node.
files that are stored in the database and
aggregate the actual data that are associated with
An object, stored in one or more storage each backup version or archive copy in
pools, consisting of a group of logical files server storage.
that are packaged together. See also
authentication rule
logical file, physical file.
A specification that another user can use
aggregate data transfer rate to either restore or retrieve files from
A performance statistic that indicates the storage.
average number of bytes that were
authority
transferred per second while processing a
The right to access objects, resources, or
given operation.
functions. See also privilege class.
application client
authorization rule
A program that is installed on a system to
A specification that permits another user
protect an application. The server
to either restore or retrieve a user's files
provides backup services to an
from storage.
application client.
authorized user
archive
A user who has administrative authority
To copy programs, data, or files to
for the client on a workstation. This user
another storage media, usually for
changes passwords, performs open
long-term storage or security. See also
registrations, and deletes file spaces.
retrieve.
AutoFS
archive copy
See automounted file system.
A file or group of files that was archived
to server storage automatic detection
A feature that detects, reports, and
archive copy group
updates the serial number of a drive or
A policy object containing attributes that
library in the database when the path
control the generation, destination, and
from the local server is defined.
expiration of archived files. See also copy
group. automatic migration
The process that is used to automatically
archive-retention grace period
move files from a local file system to
The number of days that the storage
storage, based on options and settings
manager retains an archived file when the
that are chosen by a root user on a
server is unable to rebind the file to an
workstation. See also demand migration,
appropriate management class. See also
threshold migration.
bind.
automounted file system (AutoFS)
association
A file system that is managed by an
The defined relationship between a client
automounter daemon. The automounter
daemon monitors a specified directory
path, and automatically mounts the file
system to access data.
B
backup-archive client
A program that runs on a workstation or
file server and provides a means for users
to back up, archive, restore, and retrieve
files. See also administrative client.
backup copy group
A policy object containing attributes that
control the generation, destination, and
expiration of backup versions of files. A
backup copy group belongs to a
management class. See also copy group.
backup retention grace period
The number of days the storage manager
retains a backup version after the server
is unable to rebind the file to an
appropriate management class.
backup set
A portable, consolidated group of active
versions of backup files that are generated
for a backup-archive client.
backup set collection
A group of backup sets that are created at
the same time and which have the same
backup set name, volume names,
description, and device classes. The server
identifies each backup set in the collection
by its node name, backup set name, and
file type.
backup version
A file or directory that a client node
backed up to storage. More than one
backup version can exist in storage, but
only one backup version is the active
version. See also active version, copy
group, inactive version.
bind To associate a file with a management
class name. See also archive-retention
grace period, management class, rebind.
Glossary 773
the server and used on client nodes in
C conjunction with client options files.
cache To place a duplicate copy of a file on client options file
random access media when the server An editable file that identifies the server
migrates a file to another storage pool in and communication method, and
the hierarchy. provides the configuration for backup,
cache file archive, hierarchical storage management,
A snapshot of a logical volume created by and scheduling.
Logical Volume Snapshot Agent. Blocks client-polling scheduling mode
are saved immediately before they are A method of operation in which the client
modified during the image backup and queries the server for work. See also
their logical extents are saved in the cache server-prompted scheduling mode.
files.
client schedule
CAD See client acceptor daemon. A database record that describes the
central scheduler planned processing of a client operation
A function that permits an administrator during a specific time period. The client
to schedule client operations and operation can be a backup, archive,
administrative commands. The operations restore, or retrieve operation, a client
can be scheduled to occur periodically or operating system command, or a macro.
on a specific date. See also administrative See also administrative command
command schedule, client schedule. schedule, central scheduler, schedule.
client A software program or computer that client/server
requests services from a server. See also Pertaining to the model of interaction in
server. distributed data processing in which a
program on one computer sends a request
client acceptor to a program on another computer and
A service that serves the Java applet for awaits a response. The requesting
the web client to web browsers. On program is called a client; the answering
Windows systems, the client acceptor is program is called a server.
installed and run as a service. On AIX,
UNIX, and Linux systems, the client client system-options file
acceptor is run as a daemon. A file, used on AIX, UNIX, or Linux
system clients, containing a set of
client acceptor daemon (CAD) processing options that identify the
See client acceptor. servers to be contacted for services. This
client domain file also specifies communication methods
The set of drives, file systems, or volumes and options for backup, archive,
that the user selects to back up or archive hierarchical storage management, and
data, using the backup-archive client. scheduling. See also client user-options
file, options file.
client node
A file server or workstation on which the client user-options file
backup-archive client program has been A file that contains the set of processing
installed, and which has been registered options that the clients on the system use.
to the server. The set can include options that
determine the server that the client
client node session contacts, and options that affect backup
A session in which a client node operations, archive operations,
communicates with a server to perform hierarchical storage management
backup, restore, archive, retrieve, migrate, operations, and scheduled operations.
or recall requests. See also administrative This file is also called the dsm.opt file.
session. For AIX, UNIX, or Linux systems, see also
client option set client system-options file. See also client
A group of options that are defined on system-options file, options file.
closed registration copy backup
A registration process in which only an A full backup in which the transaction log
administrator can register workstations as files are not deleted so that backup
client nodes with the server. See also open procedures that use incremental or
registration. differential backups are not disrupted.
collocation copy group
The process of keeping all data belonging A policy object containing attributes that
to a single-client file space, a single client control how backup versions or archive
node, or a group of client nodes on a copies are generated, where backup
minimal number of sequential-access versions or archive copies are initially
volumes within a storage pool. located, and when backup versions or
Collocation can reduce the number of archive copies expire. A copy group
volumes that must be accessed when a belongs to a management class. See also
large amount of data must be restored. archive copy group, backup copy group,
backup version,management class.
collocation group
A user-defined group of client nodes copy storage pool
whose data is stored on a minimal A named set of volumes that contain
number of volumes through the process copies of files that reside in primary
of collocation. storage pools. Copy storage pools are
used only to back up the data that is
commit point
stored in primary storage pools. A copy
A point in time when data is considered
storage pool cannot be a destination for a
to be consistent.
backup copy group, an archive copy
communication method group, or a management class (for
The method by which a client and server space-managed files). See also destination,
exchange information. See also primary storage pool, server storage,
Transmission Control Protocol/Internet storage pool, storage pool volume.
Protocol.
communication protocol D
A set of defined interfaces that permit
computers to communicate with each daemon
other. A program that runs unattended to
perform continuous or periodic functions,
compression such as network control.
A function that removes repetitive
characters, spaces, strings of characters, or damaged file
binary data from the data being processed A physical file in which read errors have
and replaces characters with control been detected.
characters. Compression reduces the database backup series
amount of storage space that is required One full backup of the database, plus up
for data. to 32 incremental backups made since
configuration manager that full backup. Each full backup that is
A server that distributes configuration run starts a new database backup series.
information, such as policies and A number identifies each backup series.
schedules, to managed servers according See also database snapshot, full backup.
to their profiles. Configuration database snapshot
information can include policy and A complete backup of the entire database
schedules. See also enterprise to media that can be taken off-site. When
configuration, managed server, profile. a database snapshot is created, the current
conversation database backup series is not interrupted.
A connection between two programs over A database snapshot cannot have
a session that allows them to incremental database backups associated
communicate with each other while with it. See also database backup series,
processing a transaction. See also session. full backup.
Glossary 775
data center out-of-space condition on a file system for
In a virtualized environment, a container which hierarchical storage management
that holds hosts, clusters, networks, and (HSM) is active. Files are migrated to
data stores. server storage until space usage drops to
the low threshold that was set for the file
data deduplication
system. If the high threshold and low
A method of reducing storage needs by
threshold are the same, one file is
eliminating redundant data. Only one
migrated. See also automatic migration,
instance of the data is retained on storage
selective migration, threshold migration.
media. Other instances of the same data
are replaced with a pointer to the retained desktop client
instance. The group of backup-archive clients that
includes clients on Microsoft Windows,
data manager server
Apple, and Novell NetWare operating
A server that collects metadata
systems.
information for client inventory and
manages transactions for the storage destination
agent over the local area network. The A copy group or management class
data manager server informs the storage attribute that specifies the primary storage
agent with applicable library attributes pool to which a client file will be backed
and the target volume identifier. up, archived, or migrated. See also copy
storage pool.
data mover
A device that moves data on behalf of the device class
server. A network-attached storage (NAS) A named set of characteristics that are
file server is a data mover. applied to a group of storage devices.
Each device class has a unique name and
data storage-management application-
represents a device type of disk, file,
programming interface (DSMAPI)
optical disk, or tape.
A set of functions and semantics that can
monitor events on files, and manage and device configuration file
maintain the data in a file. In an HSM 1. For a storage agent, a file that contains
environment, a DSMAPI uses events to the name and password of the storage
notify data management applications agent, and information about the
about operations on files, stores arbitrary server that is managing the
attribute information with a file, supports SAN-attached libraries and drives that
managed regions in a file, and uses the storage agent uses.
DSMAPI access rights to control access to
2. For a server, a file that contains
a file object.
information about defined device
data store classes, and, on some servers, defined
In a virtualized environment, the location libraries and drives. The information
where virtual machine data is stored. is a copy of the device configuration
information in the database.
deduplication
The process of creating representative disaster recovery manager (DRM)
records from a set of records that have A function that assists in preparing and
been identified as representing the same using a disaster recovery plan file for the
entities. server.
default management class disaster recovery plan
A management class that is assigned to a A file that is created by the disaster
policy set. This class is used to govern recover manager (DRM) that contains
backed up or archived files when a file is information about how to recover
not explicitly associated with a specific computer systems if a disaster occurs and
management class through the scripts that can be run to perform some
include-exclude list. recovery tasks. The file includes
information about the software and
demand migration
The process that is used to respond to an
hardware that is used by the server, and failure of an operation, a user action, or
the location of recovery media. the change in state of a process. See also
enterprise logging, receiver.
domain
A grouping of client nodes with one or event record
more policy sets, which manage data or A database record that describes actual
storage resources for the client nodes. See status and results for events.
also policy domain.
event server
DRM See disaster recovery manager. A server to which other servers can send
events for logging. The event server
DSMAPI
routes the events to any receivers that are
See data storage-management
enabled for the sending server's events.
application-programming interface.
exabyte (EB)
dynamic serialization
For processor, real and virtual storage
Copy serialization in which a file or
capacities and channel volume, 2 to the
folder is backed up or archived on the
power of 60 or 1 152 921 504 606 846 976
first attempt regardless of whether it
bytes. For disk storage capacity and
changes during a backup or archive. See
communications volume, 1 000 000 000
also shared dynamic serialization, shared
000 000 000 bytes.
static serialization, static serialization.
exclude
The process of identifying files in an
E include-exclude list. This process prevents
EA See extended attribute. the files from being backed up or
migrated whenever a user or schedule
EB See exabyte. enters an incremental or selective backup
EFS See Encrypted File System. operation. A file can be excluded from
backup, from space management, or from
Encrypted File System (EFS) both backup and space management.
A file system that uses file system-level
encryption. exclude-include list
See include-exclude list.
enterprise configuration
A method of setting up servers so that the expiration
administrator can distribute the The process by which files, data sets, or
configuration of one of the servers to the objects are identified for deletion because
other servers, using server-to-server their expiration date or retention period
communication. See also configuration has passed.
manager, managed server, profile, expiring file
subscription. A migrated or premigrated file that has
enterprise logging been marked for expiration and removal
The process of sending events from a from storage. If a stub file or an original
server to a designated event server. The copy of a premigrated file is deleted from
event server routes the events to a local file system, or if the original copy
designated receivers, such as to a user of a premigrated file is updated, the
exit. See also event. corresponding migrated or premigrated
file is marked for expiration the next time
error log reconciliation is run.
A data set or file that is used to record
error information about a product or extend
system. To increase the portion of available space
that can be used to store database or
estimated capacity recovery log information.
The available space, in megabytes, of a
storage pool. extended attribute (EA)
Names or value pairs that are associated
event An occurrence of significance to a task or with files or directories. There are three
system. Events can include completion or
Glossary 777
classes of extended attributes: user management support that is required. If
attributes, system attributes, and trusted no space management support is
attributes. required, the operation is passed to the
operating system, which performs its
external library
normal functions. The file system
A collection of drives that is managed by
migrator is mounted over a file system
the media-management system other than
when space management is added to the
the storage management server.
file system.
file system state
F The storage management mode of a file
file access time system that resides on a workstation on
On AIX, UNIX, or Linux systems, the which the hierarchical storage
time when the file was last accessed. management (HSM) client is installed. A
file system can be in one of these states:
file age native, active, inactive, or global inactive.
For migration prioritization purposes, the
number of days since a file was last frequency
accessed. A copy group attribute that specifies the
minimum interval, in days, between
file device type incremental backups.
A device type that specifies the use of
sequential access files on disk storage as FSID See file space ID.
volumes. FSM See file system migrator.
file server full backup
A dedicated computer and its peripheral The process of backing up the entire
storage devices that are connected to a server database. A full backup begins a
local area network that stores programs new database backup series. See also
and files that are shared by users on the database backup series, database
network. snapshot, incremental backup.
file space fuzzy backup
A logical space in server storage that A backup version of a file that might not
contains a group of files that have been accurately reflect what is currently in the
backed up or archived by a client node, file because the file was backed up at the
from a single logical partition, file system, same time as it was being modified.
or virtual mount point. Client nodes can
restore, retrieve, or delete their file spaces fuzzy copy
from server storage. In server storage, A backup version or archive copy of a file
files belonging to a single file space are that might not accurately reflect the
not necessarily stored together. original contents of the file because it was
backed up or archived the file while the
file space ID (FSID) file was being modified.
A unique numeric identifier that the
server assigns to a file space when it is
stored in server storage. G
file state GB See gigabyte.
The space management mode of a file
General Parallel File System (GPFS)
that resides in a file system to which
A high-performance shared-disk file
space management has been added. A file
system that can provide data access from
can be in one of three states: resident,
nodes in a clustered system environment.
premigrated, or migrated. See also
See also information lifecycle
migrated file, premigrated file, resident
management.
file.
gigabyte (GB)
file system migrator (FSM)
For processor storage, real and virtual
A kernel extension that intercepts all file
storage, and channel volume, 10 to the
system operations and provides any space
power of nine or 1,073,741,824 bytes. For
disk storage capacity and communications
volume, 1,000,000,000 bytes.
global inactive state
The state of all file systems to which
space management has been added when
space management is globally deactivated
for a client node.
Globally Unique Identifier (GUID)
An algorithmically determined number
that uniquely identifies an entity within a
system. See also Universally Unique
Identifier.
GPFS See General Parallel File System.
GPFS node set
A mounted, defined group of GPFS file
systems.
group backup
The backup of a group containing a list of
files from one or more file space origins.
GUID See Globally Unique Identifier.
H
hierarchical storage management (HSM)
A function that automatically distributes
and manages data on disk, tape, or both
by regarding devices of these types and
potentially others as levels in a storage
hierarchy that range from fast, expensive
devices to slower, cheaper, and possibly
removable devices. The objectives are to
minimize access time to data and
maximize available media capacity. See
also hierarchical storage management
client, recall, storage hierarchy.
hierarchical storage management client (HSM
client) A client program that works with the
server to provide hierarchical storage
management (HSM) for a system. See also
hierarchical storage management,
management class.
HSM See hierarchical storage management.
HSM client
See hierarchical storage management
client.
Glossary 779
systems. An inode contains the node,
I type, owner, and location of a file.
ILM See information lifecycle management. inode number
image A file system or raw logical volume that A number specifying a particular inode
is backed up as a single object. file in the file system.
image backup IP address
A backup of a full file system or raw A unique address for a device or logical
logical volume as a single object. unit on a network that uses the Internet
Protocol standard.
inactive file system
A file system for which space
management has been deactivated. See J
also active file system.
job file
inactive version A generated file that contains
A backup version of a file that is either configuration information for a migration
not the most recent backup version, or job. The file is XML format and can be
that is a backup version of a file that no created and edited in the hierarchical
longer exists on the client system. Inactive storage management (HSM) client for
backup versions are eligible for expiration Windows client graphical user interface.
processing according to the management See also migration job.
class assigned to the file. See also active
journal-based backup
version, backup version.
A method for backing up Windows clients
include-exclude file and AIX clients that exploits the change
A file containing statements to determine notification mechanism in a file to
the files to back up and the associated improve incremental backup performance
management classes to use for backup or by reducing the need to fully scan the file
archive. See also include-exclude list. system.
include-exclude list journal daemon
A list of options that include or exclude On AIX, UNIX, or Linux systems, a
selected files for backup. An exclude program that tracks change activity for
option identifies files that should not be files residing in file systems.
backed up. An include option identifies
journal service
files that are exempt from the exclusion
In Microsoft Windows, a program that
rules or assigns a management class to a
tracks change activity for files residing in
file or a group of files for backup or
file systems.
archive services. See also include-exclude
file.
incremental backup
K
The process of backing up files or KB See kilobyte.
directories, or copying pages in the
database, that are new or changed since kilobyte (KB)
the last full or incremental backup. See For processor storage, real and virtual
also selective backup. storage, and channel volume, 2 to the
power of 10 or 1,024 bytes. For disk
individual mailbox restore storage capacity and communications
See mailbox restore. volume, 1,000 bytes.
information lifecycle management (ILM)
A policy-based file-management system
for storage pools and file sets. See also
General Parallel File System.
inode The internal structure that describes the
individual files on AIX, UNIX, or Linux
local shadow volume
L Data that is stored on shadow volumes
LAN See local area network. localized to a disk storage subsystem.
LAN-free data movement LOFS See loopback virtual file system.
The movement of client data between a logical file
client system and a storage device on a A file that is stored in one or more server
storage area network (SAN), bypassing storage pools, either by itself or as part of
the local area network. an aggregate. See also aggregate, physical
LAN-free data transfer file, physical occupancy.
See LAN-free data movement. logical occupancy
leader data The space that is used by logical files in a
Bytes of data, from the beginning of a storage pool. This space does not include
migrated file, that are stored in the file's the unused space created when logical
corresponding stub file on the local file files are deleted from aggregate files, so it
system. The amount of leader data that is might be less than the physical
stored in a stub file depends on the stub occupancy. See also physical occupancy.
size that is specified. logical unit number (LUN)
library In the Small Computer System Interface
1. A repository for demountable (SCSI) standard, a unique identifier used
recorded media, such as magnetic to differentiate devices, each of which is a
disks and magnetic tapes. logical unit (LU).
2. A collection of one or more drives, logical volume
and possibly robotic devices A portion of a physical volume that
(depending on the library type), which contains a file system.
can be used to access storage volumes. logical volume backup
library client A back up of a file system or logical
A server that uses server-to-server volume as a single object.
communication to access a library that is Logical Volume Snapshot Agent (LVSA)
managed by another storage management Software that can act as the snapshot
server. See also library manager. provider for creating a snapshot of a
library manager logical volume during an online image
A server that controls device operations backup.
when multiple storage management loopback virtual file system (LOFS)
servers share a storage device. See also A file system that is created by mounting
library client. a directory over another local directory,
local also known as mount-over-mount. A
1. Pertaining to a device, file, or system LOFS can also be generated using an
that is accessed directly from a user automounter.
system, without the use of a LUN See logical unit number.
communication line. See also remote.
LVSA See Logical Volume Snapshot Agent.
2. For hierarchical storage management
products, pertaining to the destination
of migrated files that are being
moved. See also remote.
local area network (LAN)
A network that connects several devices
in a limited area (such as a single
building or campus) and that can be
connected to a larger network.
Glossary 781
storage for Tivoli Storage Manager servers
M that run on operating systems other than
macro file z/OS.
A file that contains one or more storage megabyte (MB)
manager administrative commands, For processor storage, real and virtual
which can be run only from an storage, and channel volume, 2 to the
administrative client using the MACRO 20th power or 1,048,576 bytes. For disk
command. See also Tivoli Storage storage capacity and communications
Manager command script. volume, 1,000,000 bytes.
mailbox restore metadata
A function that restores Microsoft Data that describes the characteristics of
Exchange Server data (from IBM Data data; descriptive data.
Protection for Microsoft Exchange
backups) at the mailbox level or migrate
mailbox-item level. To move data to another location, or an
application to another computer system.
managed object
A definition in the database of a managed migrated file
server that was distributed to the A file that has been copied from a local
managed server by a configuration file system to storage. For HSM clients on
manager. When a managed server UNIX or Linux systems, the file is
subscribes to a profile, all objects that are replaced with a stub file on the local file
associated with that profile become system. On Windows systems, creation of
managed objects in the database of the the stub file is optional. See also file state,
managed server. premigrated file, resident file, stub file.
managed server migration

A server that receives configuration The process of moving data from one
information from a configuration manager computer system to another, or an
using a subscription to one or more application to another computer system.
profiles. Configuration information can migration job
include definitions of objects such as A specification of files to migrate, and
policy and schedules. See also actions to perform on the original files
configuration manager, enterprise after migration. See also job file, threshold
configuration, profile, subscription. migration.
management class migration threshold
A policy object that users can bind to each High and low capacities for storage pools
file to specify how the server manages the or file systems, expressed as percentages,
file. The management class can contain a at which migration is set to start and
backup copy group, an archive copy stop.
group, and space management attributes.
See also bind, copy group, hierarchical mirroring
storage management client, policy set, The process of writing the same data to
rebind. multiple disks at the same time. The
mirroring of data protects it against data
maximum transmission unit (MTU) loss within the database or within the
The largest possible unit of data that can recovery log.
be sent on a given physical medium in a
single frame. For example, the maximum mode A copy group attribute that specifies
transmission unit for Ethernet is 1500 whether to back up a file that has not
bytes. been modified since the last time the file
was backed up. See also absolute mode,
MB See megabyte. modified mode.
media server modified mode
In a z/OS environment, a program that In storage management, a backup
provides access to z/OS disk and tape copy-group mode that specifies that a file
is considered for incremental backup only storage (NAS) file server. Data for the
if it has changed since the last backup. A NAS node is transferred by a NAS file
file is considered a changed file if the server that is controlled by the network
date, size, owner, or permissions of the data management protocol (NDMP). A
file have changed. See also absolute NAS node is also called a NAS file server
mode, mode. node.
mount limit native file system
The maximum number of volumes that A file system that is locally added to the
can be simultaneously accessed from the file server and is not added for space
same device class. The mount limit management. The hierarchical storage
determines the maximum number of manager (HSM) client does not provide
mount points. See also mount point. space management services to the file
system.
mount point
A logical drive through which volumes native format
are accessed in a sequential access device A format of data that is written to a
class. For removable media device types, storage pool directly by the server. See
such as tape, a mount point is a logical also non-native data format.
drive associated with a physical drive. For
NDMP
the file device type, a mount point is a
See Network Data Management Protocol.
logical drive associated with an I/O
stream. See also mount limit. NetBIOS (Network Basic Input/Output System)
A standard interface to networks and
mount retention period
personal computers that is used on local
The maximum number of minutes that
area networks to provide message,
the server retains a mounted
print-server, and file-server functions.
sequential-access media volume that is
Application programs that use NetBIOS
not being used before it dismounts the
do not have to handle the details of LAN
sequential-access media volume.
data link control (DLC) protocols.
mount wait period
network-attached storage file server (NAS file
The maximum number of minutes that
server)
the server waits for a sequential-access
A dedicated storage device with an
volume mount request to be satisfied
operating system that is optimized for
before canceling the request.
file-serving functions. A NAS file server
MTU See maximum transmission unit. can have the characteristics of both a
node and a data mover.
N Network Basic Input/Output System
See NetBIOS.
Nagle algorithm
An algorithm that reduces congestion of Network Data Management Protocol (NDMP)
TCP/IP networks by combining smaller A protocol that allows a network
packets and sending them together. storage-management application to
control the backup and recovery of an
named pipe NDMP-compliant file server, without
A type of interprocess communication installing vendor-acquired software on
that permits message data streams to pass that file server.
between peer processes, such as between
a client and a server. network data-transfer rate
A rate that is calculated by dividing the
NAS file server total number of bytes that are transferred
See network-attached storage file server. by the data transfer time. For example,
NAS file server node this rate can be the time that is spent
See NAS node. transferring data over a network.
NAS node node A file server or workstation on which the
A client node that is a network-attached
Glossary 783
backup-archive client program has been contacting for space management services.
installed, and which has been registered For example, a stub file can be orphaned
to the server. when the client system-options file is
modified to contact a server that is
node name
different than the one to which the file
A unique name that is used to identify a
was migrated.
workstation, file server, or PC to the
server.
node privilege class
P
A privilege class that gives an packet In data communication, a sequence of
administrator the authority to remotely binary digits, including data and control
access backup-archive clients for a specific signals, that are transmitted and switched
client node or for all clients in a policy as a composite whole.
domain. See also privilege class.
page A defined unit of space on a storage
non-native data format medium or within a database volume.
A format of data that is written to a
storage pool that differs from the format partial-file recall mode
that the server uses for operations. See A recall mode that causes the hierarchical
also native format. storage management (HSM) function to
read just a portion of a migrated file from
storage, as requested by the application
O accessing the file.
offline volume backup password generation
A backup in which the volume is locked A process that creates and stores a new
so that no other system applications can password in an encrypted password file
access it during the backup operation. when the old password expires.
Automatic generation of a password
online volume backup
prevents password prompting.
A backup in which the volume is
available to other system applications path An object that defines a one-to-one
during the backup operation. relationship between a source and a
destination. Using the path, the source
open registration
accesses the destination. Data can flow
A registration process in which users can
from the source to the destination, and
register their workstations as client nodes
back. An example of a source is a data
with the server. See also closed
mover (such as a network-attached
registration.
storage [NAS] file server), and an
operator privilege class example of a destination is a tape drive.
A privilege class that gives an
pattern-matching character
administrator the authority to disable or
See wildcard character.
halt the server, enable the server, cancel
server processes, and manage removable physical file
media. See also privilege class. A file that is stored in one or more
storage pools, consisting of either a single
options file
logical file, or a group of logical files that
A file that contains processing options.
are packaged together as an aggregate.
See also client system-options file, client
See also aggregate, logical file, physical
user-options file.
occupancy.
originating file system
physical occupancy
The file system from which a file was
The amount of space that is used by
migrated. When a file is recalled, it is
physical files in a storage pool. This space
returned to its originating file system.
includes the unused space that is created
orphaned stub file when logical files are deleted from
A file for which no migrated file can be aggregates. See also logical file, logical
found on the server that the client node is occupancy, physical file.
plug-in primary storage pool
A separately installable software module A named set of volumes that the server
that adds function to an existing program, uses to store backup versions of files,
application, or interface. archive copies of files, and files migrated
from client nodes. See also copy storage
policy domain
pool, server storage, storage pool, storage
A grouping of policy users with one or
pool volume.
more policy sets, which manage data or
storage resources for the users. The users privilege class
are client nodes that are associated with A level of authority that is granted to an
the policy domain. See also active policy administrator. The privilege class
set, domain. determines which administrative tasks the
administrator can perform. See also
policy privilege class
authority, node privilege class, operator
privilege class, policy privilege class,
administrator the authority to manage
storage privilege class, system privilege
policy objects, register client nodes, and
class.
schedule client operations for client
nodes. Authority can be restricted to profile
certain policy domains. See also privilege A named group of configuration
class. information that can be distributed from a
configuration manager when a managed
policy set
server subscribes. Configuration
A group of rules in a policy domain. The
information can include registered
rules specify how data or storage
administrator IDs, policies, client
resources are automatically managed for
schedules, client option sets,
client nodes in the policy domain. Rules
administrative schedules, storage manager
can be contained in management classes.
command scripts, server definitions, and
See also active policy set, management
server group definitions. See also
class.
configuration manager, enterprise
premigrated file configuration, managed server.
A file that has been copied to server
profile association
storage, but has not been replaced with a
On a configuration manager, the defined
stub file on the local file system. An
relationship between a profile and an
identical copy of the file resides both on
object such as a policy domain. Profile
the local file system and in server storage.
associations define the configuration
Premigrated files occur on UNIX and
information that is distributed to a
Linux file systems to which space
managed server when it subscribes to the
management has been added. See also file
profile.
state, migrated file, resident file.
premigrated files database
A database that contains information
Q
about each file that has been premigrated quota
to server storage. 1. For HSM on AIX, UNIX, or Linux
premigration systems, the limit (in megabytes) on
The process of copying files that are the amount of data that can be
eligible for migration to server storage, migrated and premigrated from a file
but leaving the original file intact on the system to server storage.
local file system. 2. For HSM on Windows systems, a
premigration percentage user-defined limit to the space that is
A space management setting that controls occupied by recalled files.
whether the next eligible candidates in a
file system are premigrated following
threshold or demand migration.
Glossary 785
During the reconciliation process, data
R that is identified as no longer needed is
randomization removed.
The process of distributing schedule start recovery log
times for different clients within a A log of updates that are about to be
specified percentage of the schedule's written to the database. The log can be
startup window. used to recover from system and media
raw logical volume failures. The recovery log consists of the
A portion of a physical volume that is active log (including the log mirror) and
comprised of unallocated blocks and has archive logs.
no journaled file system (JFS) definition. register
A logical volume is read/write accessible To define a client node or administrator
only through low-level I/O functions. ID that can access the server.
rebind registry
To associate all backed-up versions of a A repository that contains access and
file with a new management class name. configuration information for users,
For example, a file that has an active systems, and software.
backup version is rebound when a later
version of the file is backed up with a remote
different management class association. For hierarchical storage management
See also bind, management class. products, pertaining to the origin of
migrated files that are being moved. See
recall To copy a migrated file from server also local.
storage back to its originating file system
using the hierarchical storage resident file
management client. See also selective On a Windows system, a complete file on
recall. a local file system that might also be a
migrated file because a migrated copy can
receiver exist in server storage. On a UNIX or
A server repository that contains a log of Linux system, a complete file on a local
server and client messages as events. For file system that has not been migrated or
example, a receiver can be a file exit, a premigrated, or that has been recalled
user exit, or the server console and from server storage and modified. See
activity log. See also event. also file state.
reclamation restore
The process of consolidating the To copy information from its backup
remaining data from many location to the active storage location for
sequential-access volumes onto fewer, use. For example, to copy information
new sequential-access volumes. from server storage to a client
reclamation threshold workstation.
The percentage of space that a retention
sequential-access media volume must The amount of time, in days, that inactive
have before the server can reclaim the backed-up or archived files are kept in the
volume. Space becomes reclaimable when storage pool before they are deleted.
files are expired or are deleted. Copy group attributes and default
reconciliation retention grace periods for the domain
The process of ensuring consistency define retention.
between the original data repository and retrieve
the larger system where the data is stored To copy archived information from the
for backup. Examples of larger systems storage pool to the workstation for use.
where the data is stored for backup are The retrieve operation does not affect the
storage servers or other storage systems. archive version in the storage pool. See
also archive.
root user selective recall
A system user who operates without The process of copying user-selected files
restrictions. A root user has the special from server storage to a local file system.
rights and privileges needed to perform See also recall, transparent recall.
administrative tasks.
serialization
The process of handling files that are
S modified during backup or archive
processing. See also shared dynamic
SAN See storage area network. serialization, shared static serialization,
schedule static serialization.
A database record that describes client server A software program or a computer that
operations or administrative commands to provides services to other software
be processed. See also administrative programs or other computers. See also
command schedule, client schedule. client.
scheduling mode server options file
The type of scheduling operation for the A file that contains settings that control
server and client node that supports two various server operations. These settings
scheduling modes: client-polling and affect such things as communications,
server-prompted. devices, and performance.
scratch volume server-prompted scheduling mode
A labeled volume that is either blank or A client/server communication technique
contains no valid data, that is not defined, where the server contacts the client node
and that is available for use. See also when tasks must be done. See also
volume. client-polling scheduling mode.
script A series of commands, combined in a file, server storage
that carry out a particular function when The primary, copy, and active-data storage
the file is run. Scripts are interpreted as pools that are used by the server to store
they are run. See also Tivoli Storage user files such as backup versions, archive
Manager command script. copies, and files migrated from
Secure Sockets Layer (SSL) hierarchical storage management client
A security protocol that provides nodes (space-managed files). See also
communication privacy. With SSL, active-data pool, copy storage pool,
client/server applications can primary storage pool, storage pool
communicate in a way that is designed to volume, volume.
prevent eavesdropping, tampering, and session
message forgery. A logical or virtual connection between
selective backup two stations, software programs, or
The process of backing up certain files or devices on a network that allows the two
directories from a client domain. The files elements to communicate and exchange
that are backed up are those that are not data for the duration of the session. See
excluded in the include-exclude list. The also administrative session.
files must meet the requirement for session resource usage
serialization in the backup copy group of The amount of wait time, processor time,
the management class that is assigned to and space that is used or retrieved during
each file. See also incremental backup. a client session.
selective migration shadow copy
The process of copying user-selected files A snapshot of a volume. The snapshot
from a local file system to server storage can be taken while applications on the
and replacing the files with stub files on system continue to write data to the
the local file system. See also demand volumes.
migration, threshold migration.
Glossary 787
shadow volume special file
The data stored from a snapshot of a On AIX, UNIX, or Linux systems, a file
volume. The snapshot can be taken while that defines devices for the system, or
applications on the system continue to temporary files that are created by
write data to the volumes. processes. There are three basic types of
special files: first-in, first-out (FIFO);
shared dynamic serialization
block; and character.
A value for serialization that specifies that
a file must not be backed up or archived SSL See Secure Sockets Layer.
if it is being modified during the
stabilized file space
operation. The backup-archive client
A file space that exists on the server but
retries the backup or archive operation a
not on the client.
number of times; if the file is being
modified during each attempt, the stanza A group of lines in a file that together
backup-archive client will back up or have a common function or define a part
archive the file on its last try. See also of the system. Stanzas are usually
dynamic serialization, serialization, shared separated by blank lines or colons, and
static serialization, static serialization. each stanza has a name.
shared library startup window
A library device that is used by multiple A time period during which a schedule
storage manager servers. See also library. must be initiated.
shared static serialization static serialization
A copy-group serialization value that A copy-group serialization value that
specifies that a file must not be modified specifies that a file must not be modified
during a backup or archive operation. The during a backup or archive operation. If
client attempts to retry the operation a the file is in use during the first attempt,
number of times. If the file is in use the backup-archive client cannot back up
during each attempt, the file is not backed or archive the file. See also dynamic
up or archived. See also dynamic serialization, serialization, shared dynamic
serialization, serialization, shared dynamic serialization, shared static serialization.
serialization, static serialization.
storage agent
snapshot A program that enables the backup and
An image backup type that consists of a restoration of client data directly to and
point-in-time view of a volume. from storage attached to a storage area
network (SAN).
space-managed file
A file that is migrated from a client node storage area network (SAN)
by the hierarchical storage management A dedicated storage network tailored to a
(HSM) client. The HSM client recalls the specific environment, combining servers,
file to the client node on demand. systems, storage products, networking
products, software, and services.
space management
See hierarchical storage management. storage hierarchy
A logical order of primary storage pools,
space monitor daemon
as defined by an administrator. The order
A daemon that checks space usage on all
is typically based on the speed and
file systems for which space management
capacity of the devices that the storage
is active, and automatically starts
pools use. The storage hierarchy is
threshold migration when space usage on
defined by identifying the next storage
a file system equals or exceeds its high
pool in a storage pool definition. See also
threshold.
storage pool.
sparse file
storage pool
A file that is created with a length greater
A named set of storage volumes that is
than the data it contains, leaving empty
the destination that is used to store client
spaces for the future addition of data.
data. See also active-data pool, copy
storage pool, primary storage pool,
storage hierarchy.
storage pool volume
A volume that has been assigned to a
storage pool. See also active-data pool,
copy storage pool, primary storage pool,
server storage, volume.
storage privilege class
administrator the authority to control how
storage resources for the server are
allocated and used, such as monitoring
the database, the recovery log, and server
storage. See also privilege class.
stub A shortcut on the Windows file system
that is generated by the hierarchical
storage management (HSM) client for a
migrated file that allows transparent user
access. A stub is the sparse file
representation of a migrated file, with a
reparse point attached.
stub file
A file that replaces the original file on a
local file system when the file is migrated
to storage. A stub file contains the
information that is necessary to recall a
migrated file from server storage. It also
contains additional information that can
be used to eliminate the need to recall a
migrated file. See also migrated file,
resident file.
stub file size
The size of a file that replaces the original
file on a local file system when the file is
migrated to server storage. The size that
is specified for stub files determines how
much leader data can be stored in the
stub file. The default for stub file size is
the block size defined for a file system
minus 1 byte.
subscription
In a storage environment, the process of
identifying the subscribers to which the
profiles are distributed. See also
enterprise configuration, managed server.
system privilege class
administrator the authority to issue all
server commands. See also privilege class.
Glossary 789
tombstone object
T A small subset of attributes of a deleted
tape library object. The tombstone object is retained
A set of equipment and facilities that for a specified period, and at the end of
support an installation's tape the specified period, the tombstone object
environment. The tape library can include is permanently deleted.
tape storage racks, mechanisms for Transmission Control Protocol/Internet Protocol
automatic tape mounting, a set of tape (TCP/IP)
drives, and a set of related tape volumes An industry-standard, nonproprietary set
mounted on those drives. of communication protocols that provides
tape volume prefix reliable end-to-end connections between
The high-level-qualifier of the file name applications over interconnected networks
or the data set name in the standard tape of different types. See also communication
label. method.
target node transparent recall
A client node for which other client nodes The process that is used to automatically
(called agent nodes) have been granted recall a migrated file to a workstation or
proxy authority. The proxy authority file server when the file is accessed. See
allows the agent nodes to perform also selective recall.
operations such as backup and restore on trusted communications agent (TCA)
behalf of the target node, which owns the A program that handles the sign-on
data. password protocol when clients use
TCA See trusted communications agent. password generation.
TCP/IP
See Transmission Control U
Protocol/Internet Protocol.
UCS-2 A 2-byte (16-bit) encoding scheme based
threshold migration on ISO/IEC specification 10646-1. UCS-2
The process of moving files from a local defines three levels of implementation:
file system to server storage based on the Level 1-No combining of encoded
high and low thresholds that are defined elements allowed; Level 2-Combining of
for the file system. See also automatic encoded elements is allowed only for
migration, demand migration, migration Thai, Indic, Hebrew, and Arabic; Level
job, selective migration. 3-Any combination of encoded elements
are allowed.
throughput
In storage management, the total bytes in UNC See Universal Naming Convention.
the workload, excluding overhead, that
Unicode
are backed up or restored, divided by
A character encoding standard that
elapsed time.
supports the interchange, processing, and
timeout display of text that is written in the
A time interval that is allotted for an common languages around the world,
event to occur or complete before plus many classical and historical texts.
operation is interrupted.
Unicode-enabled file space
Tivoli Storage Manager command script Unicode file space names provide support
A sequence of Tivoli Storage Manager for multilingual workstations without
administrative commands that are stored regard for the current locale.
in the database of the Tivoli Storage
Universally Unique Identifier (UUID)
Manager server. The script can run from
The 128-bit numeric identifier that is used
any interface to the server. The script can
to ensure that two components do not
include substitution for command
have the same identifier. See also Globally
parameters and conditional logic. See also
Unique Identifier.
macro file, script.
Universal Naming Convention (UNC) volume history file
The server name and network name A file that contains information about
combined. These names together identify volumes that have been used by the
the resource on the domain. server for database backups and for
export of administrator, node, policy, or
UTF-8 Unicode Transformation Format, 8-bit
server data. The file also has information
encoding form, which is designed for ease
about sequential-access storage pool
of use with existing ASCII-based systems.
volumes that have been added, reused, or
The CCSID value for data in UTF-8
deleted. The information is a copy of
format is 1208. See also UCS-2.
volume information that is recorded in
UUID See Universally Unique Identifier. the server database.
Volume Shadow Copy Service (VSS)
V A set of Microsoft application-
programming interfaces (APIs) that are
validate used to create shadow copy backups of
To check a policy set for conditions that volumes, exact copies of files, including
can cause problems if that policy set all open files, and so on.
becomes the active policy set. For
example, the validation process checks VSS See Volume Shadow Copy Service.
whether the policy set contains a default VSS Backup
management class. A backup operation that uses Microsoft
version Volume Shadow Copy Service (VSS)
A backup copy of a file stored in server technology. The backup operation
storage. The most recent backup copy of a produces an online snapshot
file is the active version. Earlier copies of (point-in-time consistent copy) of
the same file are inactive versions. The Microsoft Exchange data. This copy can
number of versions retained by the server be stored on local shadow volumes or on
is determined by the copy group Tivoli Storage Manager server storage.
attributes in the management class. VSS Fast Restore
virtual file space An operation that restores data from a
A representation of a directory on a local snapshot. The snapshot is the VSS
network-attached storage (NAS) file backup that resides on a local shadow
system as a path to that directory. volume. The restore operation retrieves
the data by using a file-level copy
virtual mount point method.
A directory branch of a file system that is
defined as a virtual file system. The VSS Instant Restore
virtual file system is backed up to its own An operation that restores data from a
file space on the server. The server local snapshot. The snapshot is the VSS
processes the virtual mount point as a backup that resides on a local shadow
separate file system, but the client volume. The restore operation retrieves
operating system does not. the data by using a hardware assisted
restore method (for example, a FlashCopy
virtual volume operation).
An archive file on a target server that
represents a sequential media volume to a VSS offloaded backup
source server. A backup operation that uses a Microsoft
Volume Shadow Copy Service (VSS)
volume hardware provider (installed on an
A discrete unit of storage on disk, tape or alternate system) to move IBM Data
other data recording medium that Protection for Microsoft Exchange data to
supports some form of identifier and the Tivoli Storage Manager server. This
parameter list, such as a volume label or type of backup operation shifts the
input/output control. See also scratch backup load from the production system
volume, server storage, storage pool, to another system.
storage pool volume.
Glossary 791
VSS Restore
A function that uses a Microsoft Volume
Shadow Copy Service (VSS) software
provider to restore VSS Backups (IBM
Data Protection for Microsoft Exchange
database files and log files) that reside on
Tivoli Storage Manager server storage to
their original location.
workstation
W A terminal or personal computer at which
wildcard character a user can run applications and that is
A special character such as an asterisk (*) usually connected to a mainframe or a
or a question mark (?) that can be used to network.
represent one or more characters. Any worldwide name (WWN)
character or set of characters can replace A 64-bit, unsigned name identifier that is
the wildcard character. unique.
workload partition (WPAR) WPAR See workload partition.
A partition within a single operating
system instance. WWN See worldwide name.
Glossary 793

Product Number: 5608-E01

5608-E02
5608-E03
5608-E07
Printed in USA

B Msgs Server PDF

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

B Msgs Server PDF

Transféré par

Droits d'auteur :

Formats disponibles

IBM Tivoli Storage Manager

Server Messages and Error Codes

Server Messages and Error Codes

First edition (December 2013)

Chapter 2. ANE messages . . . . . . . 5 Notices . . . . . . . . . . . . . . 767

Copyright IBM Corp. 1993, 2013 iii

Copyright IBM Corp. 1993, 2013 v

Who should read this publication

To search across all publications or to download PDF versions of individual

Copyright IBM Corp. 1993, 2013 vii

Tivoli Storage Manager server and client messages format

Code Severity Meaning

Copyright IBM Corp. 1993, 2013 1

v Message text that is displayed on screen and written to message logs.

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 Tivoli Storage Manager: Server Messages and Error Codes

Example two for DEFINE VOLUME command

Chapter 1. Introduction to messages 3

ANE messages list

volume label, and retry the operation.

User response: If the drive is a floppy drive, place a

Copyright IBM Corp. 1993, 2013 5

User response: Select the appropriate action for this

ANE4007E Error processing 'filespace ANE4012E 'filespace namepath-namefile-name' already

User response: Check and see if file is locked by other

6 IBM Tivoli Storage Manager: Server Messages and Error Codes

System action: File is skipped.

ANE4017E Error processing 'filespace

ANE4022E Error processing 'filespace

Chapter 2. ANE messages 7

User response: Ensure that the drive is operational, Windows ME (FAT32)

8 IBM Tivoli Storage Manager: Server Messages and Error Codes

backed up and compressed on another client

Windows XP/2000/2003 ANE4036E An error occurred saving the registry

System action: Processing stopped.

Chapter 2. ANE messages 9

10 IBM Tivoli Storage Manager: Server Messages and Error Codes

workstation, another object name was encountered with

Chapter 2. ANE messages 11

encryption key, required to decrypt the file, is not

12 IBM Tivoli Storage Manager: Server Messages and Error Codes

ANE4057I The secondary server is configured as System action: Processing continues.

Chapter 2. ANE messages 13

v If a backup copy of the file is not necessary, you can

14 IBM Tivoli Storage Manager: Server Messages and Error Codes

Chapter 2. ANE messages 15

additional assistance. Your TSM administrator can help

System action: Processing continues. System action: Processing continues.

User response: None required. User response: None required.

16 IBM Tivoli Storage Manager: Server Messages and Error Codes

ANE4113I Waiting for dsmautomig ANE4119I Premigrated candidates : Number of

Chapter 2. ANE messages 17

ANE4124I NO INFORMATION AVAILABLE ANE4130I Scanned Number of objects objects per

18 IBM Tivoli Storage Manager: Server Messages and Error Codes

System action: Processing continues.

System action: Processing continues. User response: None required.

User response: None required.